Google Git
Sign in
eclipse/platform/eclipse.platform.common/a24242dedd4a2dc7fc73e0940e0aaddddfcb169b^!/.
commit
a24242dedd4a2dc7fc73e0940e0aaddddfcb169b
[log]
author
cvs2svn <platform-releng-dev@eclipse.org>
Thu Apr 13 17:30:37 2006 +0000
committer
cvs2svn <platform-releng-dev@eclipse.org>
Thu Apr 13 17:30:37 2006 +0000
tree
81fff0ed5163fe59a44e2266d36a53a34179443c
parent
331961f0ba5f9b964d813259026f034747fa8060 [diff]
This commit was manufactured by cvs2svn to create branch 'RC1_32_branch'.

Sprout from master 2006-04-13 17:30:35 UTC John Arthorne <johna> 'Updated org.eclipse.core.* for 3.2 stream I-build'
Delete:
    bundles/org.eclipse.jdt.doc.isv/.cvsignore
    bundles/org.eclipse.jdt.doc.isv/.project
    bundles/org.eclipse.jdt.doc.isv/META-INF/MANIFEST.MF
    bundles/org.eclipse.jdt.doc.isv/aaa-how-to-add-things.txt
    bundles/org.eclipse.jdt.doc.isv/about.html
    bundles/org.eclipse.jdt.doc.isv/about.ini
    bundles/org.eclipse.jdt.doc.isv/about.mappings
    bundles/org.eclipse.jdt.doc.isv/about.properties
    bundles/org.eclipse.jdt.doc.isv/book.css
    bundles/org.eclipse.jdt.doc.isv/build.properties
    bundles/org.eclipse.jdt.doc.isv/build.xml
    bundles/org.eclipse.jdt.doc.isv/buildDoc.xml
    bundles/org.eclipse.jdt.doc.isv/cpy.png
    bundles/org.eclipse.jdt.doc.isv/eclipse32.png
    bundles/org.eclipse.jdt.doc.isv/guide/images/annotation_processing.png
    bundles/org.eclipse.jdt.doc.isv/guide/images/compiler_dialog.png
    bundles/org.eclipse.jdt.doc.isv/guide/images/factory_path.png
    bundles/org.eclipse.jdt.doc.isv/guide/images/javanavigator.png
    bundles/org.eclipse.jdt.doc.isv/guide/images/openables.png
    bundles/org.eclipse.jdt.doc.isv/guide/images/sourceelements.png
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_api.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_classpath.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_codeassist.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_compile.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_editors.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_junit.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_manip.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_open_editor.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_options.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_prompter.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_render.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_run.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_search.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_utility.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_wizards.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_write_jar_file.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_apt_building_with_apt.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_apt_getting_started.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_int.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_apt.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_core.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_debug.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_junit.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_model.htm
    bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_ui.htm
    bundles/org.eclipse.jdt.doc.isv/jdtOptions.txt
    bundles/org.eclipse.jdt.doc.isv/jdtaptOptions.txt
    bundles/org.eclipse.jdt.doc.isv/notices.html
    bundles/org.eclipse.jdt.doc.isv/plugin.properties
    bundles/org.eclipse.jdt.doc.isv/plugin.xml
    bundles/org.eclipse.jdt.doc.isv/questions/index.html
    bundles/org.eclipse.jdt.doc.isv/reference/.cvsignore
    bundles/org.eclipse.jdt.doc.isv/reference/extension-points/index.html
    bundles/org.eclipse.jdt.doc.isv/reference/misc/index.html
    bundles/org.eclipse.jdt.doc.isv/reference/misc/overview-jdt.html
    bundles/org.eclipse.jdt.doc.isv/samples/samples.html
    bundles/org.eclipse.jdt.doc.isv/schema.css
    bundles/org.eclipse.jdt.doc.isv/toc.xml
    bundles/org.eclipse.jdt.doc.isv/topics_Guide.xml
    bundles/org.eclipse.jdt.doc.isv/topics_Questions.xml
    bundles/org.eclipse.jdt.doc.isv/topics_Reference.xml
    bundles/org.eclipse.jdt.doc.isv/topics_Samples.xml
    bundles/org.eclipse.jdt.doc.user/.project
    bundles/org.eclipse.jdt.doc.user/META-INF/MANIFEST.MF
    bundles/org.eclipse.jdt.doc.user/about.html
    bundles/org.eclipse.jdt.doc.user/about.ini
    bundles/org.eclipse.jdt.doc.user/about.mappings
    bundles/org.eclipse.jdt.doc.user/about.properties
    bundles/org.eclipse.jdt.doc.user/book.css
    bundles/org.eclipse.jdt.doc.user/build.properties
    bundles/org.eclipse.jdt.doc.user/build.xml
    bundles/org.eclipse.jdt.doc.user/concepts/cbrkpnts.htm
    bundles/org.eclipse.jdt.doc.user/concepts/cbuildcp.htm
    bundles/org.eclipse.jdt.doc.user/concepts/cclsspthv.htm
    bundles/org.eclipse.jdt.doc.user/concepts/clocdbug.htm
    bundles/org.eclipse.jdt.doc.user/concepts/cnls.htm
    bundles/org.eclipse.jdt.doc.user/concepts/concepts-1.htm
    bundles/org.eclipse.jdt.doc.user/concepts/concepts-10.htm
    bundles/org.eclipse.jdt.doc.user/concepts/concepts-11.htm
    bundles/org.eclipse.jdt.doc.user/concepts/concepts-3.htm
    bundles/org.eclipse.jdt.doc.user/concepts/concepts-4.htm
    bundles/org.eclipse.jdt.doc.user/concepts/concepts-5.htm
    bundles/org.eclipse.jdt.doc.user/concepts/concepts-6.htm
    bundles/org.eclipse.jdt.doc.user/concepts/concepts-7.htm
    bundles/org.eclipse.jdt.doc.user/concepts/concepts-8.htm
    bundles/org.eclipse.jdt.doc.user/concepts/concepts-9.htm
    bundles/org.eclipse.jdt.doc.user/concepts/cquickassists.htm
    bundles/org.eclipse.jdt.doc.user/concepts/cquickfix.htm
    bundles/org.eclipse.jdt.doc.user/concepts/cremdbug.htm
    bundles/org.eclipse.jdt.doc.user/concepts/ctemplates.htm
    bundles/org.eclipse.jdt.doc.user/concepts/filters.htm
    bundles/org.eclipse.jdt.doc.user/concepts/rules.htm
    bundles/org.eclipse.jdt.doc.user/contexts_APT.xml
    bundles/org.eclipse.jdt.doc.user/contexts_Debugger.xml
    bundles/org.eclipse.jdt.doc.user/contexts_JDT.xml
    bundles/org.eclipse.jdt.doc.user/contexts_JDT_Debugger.xml
    bundles/org.eclipse.jdt.doc.user/contexts_JDT_JUnit.xml
    bundles/org.eclipse.jdt.doc.user/cpy.png
    bundles/org.eclipse.jdt.doc.user/eclipse32.png
    bundles/org.eclipse.jdt.doc.user/gettingStarted/intro/overview.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-10.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-11.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-12.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-13.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-14.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-15.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-2.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-3.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-4.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-6.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-7.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-8.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-9.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-AddMethod.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-BasicTutorial.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-Browsing.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ContentAssist.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-DetectingExistingLayout.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-EditorTemplates.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ExtractMethod.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-LocalHistory.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-Navigate.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OpenJavaEditor.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OrganizeImports.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OrganizingSources.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ProjectConfiguration.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout1.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout2.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout3.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout4.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout5.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout6.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-junit.htm
    bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-with-j2se50.htm
    bundles/org.eclipse.jdt.doc.user/images/add_linked_source_to_buildpath.png
    bundles/org.eclipse.jdt.doc.user/images/c-quickfix.png
    bundles/org.eclipse.jdt.doc.user/images/classpathVar.png
    bundles/org.eclipse.jdt.doc.user/images/contentassist.png
    bundles/org.eclipse.jdt.doc.user/images/j2se50/autobox-coloring.png
    bundles/org.eclipse.jdt.doc.user/images/j2se50/autobox.png
    bundles/org.eclipse.jdt.doc.user/images/j2se50/enum.png
    bundles/org.eclipse.jdt.doc.user/images/j2se50/filter-incompatible.png
    bundles/org.eclipse.jdt.doc.user/images/j2se50/filter-inexact.png
    bundles/org.eclipse.jdt.doc.user/images/j2se50/foo.png
    bundles/org.eclipse.jdt.doc.user/images/j2se50/foreach-inserted.png
    bundles/org.eclipse.jdt.doc.user/images/j2se50/foreach-proposal.png
    bundles/org.eclipse.jdt.doc.user/images/j2se50/infer-generic.png
    bundles/org.eclipse.jdt.doc.user/images/j2se50/inferred-generic.png
    bundles/org.eclipse.jdt.doc.user/images/j2se50/new-project.png
    bundles/org.eclipse.jdt.doc.user/images/j2se50/no-filters.png
    bundles/org.eclipse.jdt.doc.user/images/j2se50/override.png
    bundles/org.eclipse.jdt.doc.user/images/j2se50/quick-fix.png
    bundles/org.eclipse.jdt.doc.user/images/j2se50/suppress-applied.png
    bundles/org.eclipse.jdt.doc.user/images/j2se50/suppress-proposed.png
    bundles/org.eclipse.jdt.doc.user/images/j2se50/unused-warning.png
    bundles/org.eclipse.jdt.doc.user/images/ngrelc.png
    bundles/org.eclipse.jdt.doc.user/images/ngrelr.png
    bundles/org.eclipse.jdt.doc.user/images/ngrelt.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/changevariablevalue_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/collapseall.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/copy_edit_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/copyviewtoclipboard_tsk.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/debuglast_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_hide.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_right.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_under.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/disabled_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/disconnect_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/edtsrclkup_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/enabled_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/lock_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/memoryreset_tsk.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/metharg_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/monitorexpression_tsk.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/printview_tsk.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/rem_all_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/rem_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/removememory_tsk.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/resume_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/runlast_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/runtoline_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/skip_brkp.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepbystep_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepinto_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepover_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepreturn_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/suspend_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/synced.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_all_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_rem_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/tnames_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/toggledetailpane_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/var_cntnt_prvdr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/debug_exc.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/environment_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/profile_exc.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/run_exc.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/term_restart.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/watch_exp.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/changevariablevalue_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/collapseall.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/copy_edit_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/copyviewtoclipboard_tsk.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/debuglast_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_hide.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_right.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_under.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/disabled_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/disconnect_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/dissolve_group.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/drop_to_frame.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/edtsrclkup_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/enabled_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/expandall.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/hierarchicalLayout.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/lock_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/memoryreset_tsk.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/metharg_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/monitorexpression_tsk.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/new_con.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/pin.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/printview_tsk.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/rem_all_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/rem_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/removememory_tsk.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/resume_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/runlast_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/runtoline_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/skip_brkp.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepbystep_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepinto_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepover_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepreturn_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/suspend_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/synced.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_all_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_rem_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/tnames_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/toggledetailpane_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/var_cntnt_prvdr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/debug_exc.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/environment_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/profile_exc.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/run_exc.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/term_restart.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/watch_exp.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/breakpoint_view.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/debug_persp.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/debug_view.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/details_view.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/memory_view.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/register_view.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/variable_view.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/watchlist_view.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/brkp_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/brkpd_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugt_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugts_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugtt_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/expression_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/genericvariable_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/inst_ptr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/inst_ptr_top.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/ldebug_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/lrun_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/osprc_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/osprct_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/readwrite_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/stckframe_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/stckframe_running_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/terminatedlaunch_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/thread_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/threads_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/ovr16/error.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/ovr16/stcksync_ov.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/addsrcloc_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/debug_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/edtsrclkup_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/profile_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/run_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/at_breakpoint.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/constant_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/deadlock_view.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/exc_catch.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/final_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/monitor_view.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/resume_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/sethitcount_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/static_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/suspend_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/thread_view.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/debug_exc.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/disp_sbook.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/insp_sbook.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_app.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_applet.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_attach.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/newsbook_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/run_exc.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/run_sbook.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/term_sbook.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/watch_exp.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/constant_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/deadlock_view.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/exc_catch.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/final_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/monitor_view.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/resume_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/sethitcount_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/static_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/suspend_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/thread_view.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/empty_jpage.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/debug_exc.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/disp_sbook.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/insp_sbook.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_app.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_applet.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_attach.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/newsbook_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/run_exc.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/run_sbook.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/term_sbook.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/watch_exp.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/eview16/thread_and_monitor_view.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/eview16/variable_tab.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/example_display.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/example_display_result.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/example_inspect.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/example_inspect_result.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/executable.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/jpage_wizard.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/brkpi_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/class_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/classpath_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/contended_monitor_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/envvar_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/insp_sbook.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jar_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexcept_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexception_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexceptiond_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jline_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jload_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jmeth_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jrtexception_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jsbook_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jsbook_run_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jspbrkpt_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jwatch_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/library_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/localvariable_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/monitor_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/owned_monitor_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/package_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/prj_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/read_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/readwrite_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/thread_and_monitor_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/thread_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/write_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/caught_ovr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/caught_ovr_disabled.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/conditional_ovr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/conditional_ovr_disabled.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/contention_ovr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/contentionformonitor_ovr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/deadlock_ovr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/entry_ovr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/entry_ovr_disabled.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/error_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/exit_ovr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/exit_ovr_disabled.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/installed_ovr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/installed_ovr_disabled.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/owned_ovr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/ownsmonitor_ovr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/scoped_ovr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/scoped_ovr_disabled.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/sync_ovr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/uncaught_ovr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/uncaught_ovr_disabled.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/warning_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/remove_all_terminated.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/run_as.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/run_dialog.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/run_drop_down.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/run_history.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/scrap_assist.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/scrap_display.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/scrapbook.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/select_main_type.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/set_breakpoint.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/test_runner_args.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/test_runner_console.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/test_runner_debug_view.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/test_runner_output.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/var_view.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/java_app_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/java_attach_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/library_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/newsbook_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/cfilter.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/compare.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/lock.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/relaunch.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/relaunchf.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/select_next.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/select_prev.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/stop.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/th_automatic.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/th_horizontal.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/th_vertical.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dtool16/debugjunit.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dtool16/new_testcase.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dtool16/new_testsuite.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dtool16/runjunit.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/cfilter.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/compare.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/lock.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/relaunch.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/relaunchf.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/select_next.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/select_prev.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/stop.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_automatic.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_horizontal.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_vertical.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/debugjunit.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/new_testcase.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/new_testsuite.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/runjunit.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junit.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/juniterr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/juniterrq.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junitsucc.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junitsuccq.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/stackframe.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/exc_catch.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/faillist.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/failures.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/julaunch.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/stkfrm_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/test.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testerr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testfail.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testhier.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testok.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testrun.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuite.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiteerror.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuitefail.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiteok.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiterun.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/error_ovr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/failed_ovr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/success_ovr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff1.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff2.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff3.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff4.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff5.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff6.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff7.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff8.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff9.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss1.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss2.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss3.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss4.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss5.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss6.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss7.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss8.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss9.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/wizban/newsuite_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/wizban/newtest_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/add_as_source_folder.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/add_exc.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/add_linked_source_to_buildpath.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/add_to_buildpath.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/alphab_sort_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/ch_callees.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/ch_callers.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/ch_cancel.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/class_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/clear_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/collapseall.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/configure_build_path.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/configure_buildpath_filters.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/configure_output_folder.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/default_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/definingtype_sort_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/exc_catch.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/exclude_from_buildpath.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/exclusion_filter_attrib.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/fields_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/file_mode.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/filter_ps.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/flatLayout.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/gointo_toplevel_type.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/goto_input.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/hide_externalized.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/hide_ignored.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/hide_internalized.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/hierarchicalLayout.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/hierarchy_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/history_list.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/impl_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/include_on_buildpath.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/inclusion_filter_attrib.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/inher_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/localtypes_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/metharg_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/newpackfolder_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/output_folder_attrib.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/pack_empty_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/package_mode.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/private_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/prj_mode.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/protected_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/public_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/refresh_nav.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/remove_as_source_folder.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/remove_exc.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/remove_from_buildpath.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/removea_exc.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/search_sortmatch.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/smartmode_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/static_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/sub_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/super_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/synced.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/text_edit.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/th_automatic.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/th_horizontal.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/th_showqualified.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/th_single.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/th_vertical.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/type_mode.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/view_menu.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/comment_edit.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/exportapp_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/exportjar_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/importjar_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/java_app.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/java_attach.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/javadoc.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/jdoc_hover_edit.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/mark_occurrences.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newannotation_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newclass_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newenum_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newint_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newjprj_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newjworkingSet_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newpack_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newpackfolder_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newsbook_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/opentype.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/segment_edit.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/shift_l_edit.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/shift_r_edit.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_as_source_folder.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_exc.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_linked_source_to_buildpath.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_to_buildpath.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/alphab_sort_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_callees.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_callers.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_cancel.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/class_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/clear_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/collapseall.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_build_path.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_buildpath_filters.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_output_folder.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/default_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/definingtype_sort_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exc_catch.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exclude_from_buildpath.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exclusion_filter_attrib.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/fields_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/file_mode.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/filter_ps.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/flatLayout.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/gointo_toplevel_type.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/goto_input.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/help.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_externalized.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_ignored.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_internalized.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hierarchicalLayout.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hierarchy_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/history_list.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/impl_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/include_on_buildpath.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/inclusion_filter_attrib.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/inher_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/localtypes_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/metharg_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/pack_empty_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/package_mode.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/private_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/prj_mode.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/protected_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/public_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/refresh_nav.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_as_source_folder.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_exc.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_from_buildpath.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/removea_exc.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/search_sortmatch.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/smartmode_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/static_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/sub_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/super_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/synced.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_automatic.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_horizontal.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_showqualified.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_single.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_vertical.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/type_mode.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/view_menu.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/comment_edit.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/exportapp_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/exportjar_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/importjar_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/java_app.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/java_attach.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/javadoc.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/jdoc_hover_edit.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/mark_occurrences.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newannotation_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newclass_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newenum_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newint_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newjprj_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newjworkingSet_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newpack_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newpackfolder_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newsbook_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/opentype.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/segment_edit.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/shift_l_edit.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/shift_r_edit.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/browse_persp.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/call_hierarchy.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/class_hi.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/classfilegeneration_tab.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/errorwarning_tab.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/hierch_persp.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/javadoc.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/jdkcompliance_tab.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/jperspective.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/members.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/package.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/packages.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/projects.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/source.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/types.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/access_restriction_attrib.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/add_correction.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_alt_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_default_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_private_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_protected_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/brkpi_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/change.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/class_default_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/class_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classf_generate.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classf_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classfo_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/collapsed.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/compare_field.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/compare_method.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/composite_change.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_cast.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_change.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_delete_import.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_move.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_rename.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cp_order_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cu_change.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cu_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_logical_package_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_pack_fldr_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_pack_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_alt_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_default_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_private_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_protected_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/envvar_nonexist_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/envvar_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/error_gray_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/error_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/exclusion_filter_attrib.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/expanded.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/externalize.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/fatalerror_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_default_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_private_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_protected_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_public_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/file_change.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/file_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/history_working_set_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/html_tag_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/ignore.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/imp_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/impc_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/implm_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/inclusion_filter_attrib.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/info_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_default_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_private_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_protected_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_public_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_default_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_private_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_protected_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_public_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/int_default_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/int_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/internalize.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/intf_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_desc_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_l_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_lsrc_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_nonexist_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_src_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/java_model_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/javadoc_location_attrib.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jcu_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jcu_resource_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jdoc_tag_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jexception_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jexceptiond_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jrtexception_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jsbook_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jsearch_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jworkingSet_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/library_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/localvariable_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/logical_package_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methdef_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpri_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpro_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpub_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/native_lib_path_attrib.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/never_translate.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/nls_search_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/no_breakpoint.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_match.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_read.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_write.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/output_folder_attrib.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/over_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/package_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/packagefolder_nonexist_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/packagefolder_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/packd_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/prjct_nonexist_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickassist_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickfix_error_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickfix_warning_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/remove_correction.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/search_decl_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/search_ref_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/searchm_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/skip.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/source_attach_attrib.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/template_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/text_edit.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/translate.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/type_separator.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/typevariable_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/unknown_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/warning_gray_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/warning_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/abstract_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/callee_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/caller_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/constr_ovr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/deprecated.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/error_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/final_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/focus_ovr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/implm_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/java_ovr.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/maxlevel_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/native_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/over_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/read.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/recursive_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/run_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/static_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/sync_impl.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/sync_over.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/synch_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/volatile_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/warning_co.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/write.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/addlibrary_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/coderefact_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/compunitrefact_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/export_javadoc_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/exportapp_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/extstr_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/fieldrefact_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/jar_pack_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/java_app_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/java_attach_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/java_workingset_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/methrefact_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newannotation_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newclass_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newenum_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newfield_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newint_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newjprj_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newmeth_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newpack_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newsbook_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newsrcfldr_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/packrefact_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/pullup_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/refactor_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/typerefact_wiz.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/collapseall.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/expandall.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/flatLayout.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/hierarchicalLayout.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_goto.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_history.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_next.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_prev.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_rem.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_remall.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_sortmatch.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/stop.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/tsearch_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dtool16/group_by_file.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dtool16/group_by_folder.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dtool16/group_by_project.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dtool16/search.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/collapseall.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/expandall.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/flatLayout.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/hierarchicalLayout.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_goto.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_history.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_next.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_prev.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_rem.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_remall.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_sortmatch.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/stop.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/tsearch_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/etool16/group_by_file.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/etool16/group_by_folder.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/etool16/group_by_project.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/etool16/search.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/eview16/searchres.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/obj16/searchm_obj.png
    bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/obj16/tsearch_dpdn_obj.png
    bundles/org.eclipse.jdt.doc.user/images/qs-1.png
    bundles/org.eclipse.jdt.doc.user/images/qs-10.png
    bundles/org.eclipse.jdt.doc.user/images/qs-11.png
    bundles/org.eclipse.jdt.doc.user/images/qs-12.png
    bundles/org.eclipse.jdt.doc.user/images/qs-13.png
    bundles/org.eclipse.jdt.doc.user/images/qs-13a.png
    bundles/org.eclipse.jdt.doc.user/images/qs-14.png
    bundles/org.eclipse.jdt.doc.user/images/qs-15.png
    bundles/org.eclipse.jdt.doc.user/images/qs-15a.png
    bundles/org.eclipse.jdt.doc.user/images/qs-16.png
    bundles/org.eclipse.jdt.doc.user/images/qs-17.png
    bundles/org.eclipse.jdt.doc.user/images/qs-17a.png
    bundles/org.eclipse.jdt.doc.user/images/qs-17b.png
    bundles/org.eclipse.jdt.doc.user/images/qs-17c.png
    bundles/org.eclipse.jdt.doc.user/images/qs-17c1.png
    bundles/org.eclipse.jdt.doc.user/images/qs-17c2.png
    bundles/org.eclipse.jdt.doc.user/images/qs-17d.png
    bundles/org.eclipse.jdt.doc.user/images/qs-17e.png
    bundles/org.eclipse.jdt.doc.user/images/qs-17f.png
    bundles/org.eclipse.jdt.doc.user/images/qs-18.png
    bundles/org.eclipse.jdt.doc.user/images/qs-19.png
    bundles/org.eclipse.jdt.doc.user/images/qs-2.png
    bundles/org.eclipse.jdt.doc.user/images/qs-20.png
    bundles/org.eclipse.jdt.doc.user/images/qs-21.png
    bundles/org.eclipse.jdt.doc.user/images/qs-22.png
    bundles/org.eclipse.jdt.doc.user/images/qs-23.png
    bundles/org.eclipse.jdt.doc.user/images/qs-24.png
    bundles/org.eclipse.jdt.doc.user/images/qs-25.png
    bundles/org.eclipse.jdt.doc.user/images/qs-26.png
    bundles/org.eclipse.jdt.doc.user/images/qs-27.png
    bundles/org.eclipse.jdt.doc.user/images/qs-28.png
    bundles/org.eclipse.jdt.doc.user/images/qs-29.png
    bundles/org.eclipse.jdt.doc.user/images/qs-3.png
    bundles/org.eclipse.jdt.doc.user/images/qs-30.png
    bundles/org.eclipse.jdt.doc.user/images/qs-31.png
    bundles/org.eclipse.jdt.doc.user/images/qs-32.png
    bundles/org.eclipse.jdt.doc.user/images/qs-33.png
    bundles/org.eclipse.jdt.doc.user/images/qs-33a.png
    bundles/org.eclipse.jdt.doc.user/images/qs-33b.png
    bundles/org.eclipse.jdt.doc.user/images/qs-34.png
    bundles/org.eclipse.jdt.doc.user/images/qs-35.png
    bundles/org.eclipse.jdt.doc.user/images/qs-36.png
    bundles/org.eclipse.jdt.doc.user/images/qs-37.png
    bundles/org.eclipse.jdt.doc.user/images/qs-37a.png
    bundles/org.eclipse.jdt.doc.user/images/qs-37b.png
    bundles/org.eclipse.jdt.doc.user/images/qs-38.png
    bundles/org.eclipse.jdt.doc.user/images/qs-39.png
    bundles/org.eclipse.jdt.doc.user/images/qs-40.png
    bundles/org.eclipse.jdt.doc.user/images/qs-41.png
    bundles/org.eclipse.jdt.doc.user/images/qs-42.png
    bundles/org.eclipse.jdt.doc.user/images/qs-43.png
    bundles/org.eclipse.jdt.doc.user/images/qs-43a.png
    bundles/org.eclipse.jdt.doc.user/images/qs-43b.png
    bundles/org.eclipse.jdt.doc.user/images/qs-43c.png
    bundles/org.eclipse.jdt.doc.user/images/qs-43d.png
    bundles/org.eclipse.jdt.doc.user/images/qs-43e.png
    bundles/org.eclipse.jdt.doc.user/images/qs-43f.png
    bundles/org.eclipse.jdt.doc.user/images/qs-44.png
    bundles/org.eclipse.jdt.doc.user/images/qs-46.png
    bundles/org.eclipse.jdt.doc.user/images/qs-47.png
    bundles/org.eclipse.jdt.doc.user/images/qs-48.png
    bundles/org.eclipse.jdt.doc.user/images/qs-49.png
    bundles/org.eclipse.jdt.doc.user/images/qs-5.png
    bundles/org.eclipse.jdt.doc.user/images/qs-50.png
    bundles/org.eclipse.jdt.doc.user/images/qs-52.png
    bundles/org.eclipse.jdt.doc.user/images/qs-53.png
    bundles/org.eclipse.jdt.doc.user/images/qs-54.png
    bundles/org.eclipse.jdt.doc.user/images/qs-55.png
    bundles/org.eclipse.jdt.doc.user/images/qs-56.png
    bundles/org.eclipse.jdt.doc.user/images/qs-6.png
    bundles/org.eclipse.jdt.doc.user/images/qs-7.png
    bundles/org.eclipse.jdt.doc.user/images/qs-8.png
    bundles/org.eclipse.jdt.doc.user/images/qs-9.png
    bundles/org.eclipse.jdt.doc.user/images/qs-DetectingExistingLayout1.png
    bundles/org.eclipse.jdt.doc.user/images/qs-DetectingExistingLayout2.png
    bundles/org.eclipse.jdt.doc.user/images/qs-DetectingExistingLayout3.png
    bundles/org.eclipse.jdt.doc.user/images/qs-DetectingExistingLayout4.png
    bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources1.png
    bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources2.png
    bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources3.png
    bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources4.png
    bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources5.png
    bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources6.png
    bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources7.png
    bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources8.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout10.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout11.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout12.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout13.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout14.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout20.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout21.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout22.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout23.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout24.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout25.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout26.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout27.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout30.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout31.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout32.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout33.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout34.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout35.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout36.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout40.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout41.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout42.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout43.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout44.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout45.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout46.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout47.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout5.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout50.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout51.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout52.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout53.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout54.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout55.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout56.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout57.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout58.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout59.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout5A.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout5B.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout60.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout61.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout62.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout63.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout64.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout65.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout66.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout67.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout68.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout69.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout6a.png
    bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout6b.png
    bundles/org.eclipse.jdt.doc.user/images/qs-browsing1.png
    bundles/org.eclipse.jdt.doc.user/images/qs-jun1.png
    bundles/org.eclipse.jdt.doc.user/images/qs-jun2.png
    bundles/org.eclipse.jdt.doc.user/images/qs-jun3.png
    bundles/org.eclipse.jdt.doc.user/images/qs-jun4.png
    bundles/org.eclipse.jdt.doc.user/images/qs-jun5.png
    bundles/org.eclipse.jdt.doc.user/images/qs-jun6.png
    bundles/org.eclipse.jdt.doc.user/images/qs-newjavaproject.png
    bundles/org.eclipse.jdt.doc.user/images/tasks-160a.png
    bundles/org.eclipse.jdt.doc.user/images/tasks-163a.png
    bundles/org.eclipse.jdt.doc.user/images/tasks-166a.png
    bundles/org.eclipse.jdt.doc.user/images/tasks-166b.png
    bundles/org.eclipse.jdt.doc.user/images/tasks-168a.png
    bundles/org.eclipse.jdt.doc.user/images/tasks-170a.png
    bundles/org.eclipse.jdt.doc.user/images/tasks-189a.png
    bundles/org.eclipse.jdt.doc.user/images/tasks-190a.png
    bundles/org.eclipse.jdt.doc.user/images/tasks-199a.png
    bundles/org.eclipse.jdt.doc.user/images/tasks-208a.png
    bundles/org.eclipse.jdt.doc.user/images/tasks-208b.png
    bundles/org.eclipse.jdt.doc.user/images/tasks-209a.png
    bundles/org.eclipse.jdt.doc.user/images/tasks-27.png
    bundles/org.eclipse.jdt.doc.user/images/tasks-28.png
    bundles/org.eclipse.jdt.doc.user/images/tasks-29.png
    bundles/org.eclipse.jdt.doc.user/images/tasks-30.png
    bundles/org.eclipse.jdt.doc.user/images/tasks-31.png
    bundles/org.eclipse.jdt.doc.user/images/tasks-32.png
    bundles/org.eclipse.jdt.doc.user/images/tasks-46.png
    bundles/org.eclipse.jdt.doc.user/images/tasks-8.png
    bundles/org.eclipse.jdt.doc.user/images/tasks_200a.png
    bundles/org.eclipse.jdt.doc.user/images/tasks_201a.png
    bundles/org.eclipse.jdt.doc.user/images/tasks_205a.png
    bundles/org.eclipse.jdt.doc.user/notices.html
    bundles/org.eclipse.jdt.doc.user/plugin.properties
    bundles/org.eclipse.jdt.doc.user/plugin.xml
    bundles/org.eclipse.jdt.doc.user/reference/brkAccess.htm
    bundles/org.eclipse.jdt.doc.user/reference/brkEntry.htm
    bundles/org.eclipse.jdt.doc.user/reference/brkExit.htm
    bundles/org.eclipse.jdt.doc.user/reference/brkMod.htm
    bundles/org.eclipse.jdt.doc.user/reference/brkProperties.htm
    bundles/org.eclipse.jdt.doc.user/reference/brkSelectAll.htm
    bundles/org.eclipse.jdt.doc.user/reference/brkShowSupported.htm
    bundles/org.eclipse.jdt.doc.user/reference/brkSuspendPolicy.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-11.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-115.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-117.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-117a.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-117b.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-12.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-121.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-123.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-123b.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-124.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-125.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-126.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-126b.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-127.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-127b.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-128.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-129.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-13.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-131.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-143.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-148.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-149.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-15.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-150.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-152.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-154.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-155.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-156.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-17.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-18.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-19.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-2.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-21.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-22.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-24.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-3.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-34.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-35.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-36.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-37.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-38.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-39.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-4.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-40.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-41.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-42.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-43.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-44.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-44a.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-45.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-45b.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-46.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-47.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-48.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-49.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-50.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-51.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-51a.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-51b.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-51c.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-51d.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-52.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-53.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-54.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-55.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-56.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-56a.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-56b.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-56c.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-56d.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-56e.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-57.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-58.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-59.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-6.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-60.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-62.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-63.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-64.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-65.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-67.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-68.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-69.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-7.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-70.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-71.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-72.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-73.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-74.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-74a.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-75.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-76.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-78.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-8.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-80.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-81.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-9.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-apt-automaticProcessorOptions.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-apt-config.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-apt-factoryPath.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-apt-factoryPathOptions.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-apt-processorOptionsInput.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-gettersetter.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-java-element-filters.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-javadoc-location.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-override-method.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-export-jar.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-export-javadoc.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor-quickfix.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-menu-edit.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-menu-file.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-menu-navigate.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-menu-project.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-menu-refactor.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-menu-search.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-menu-source.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-appearance.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-code-generation.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-code-templates.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-compiler.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-junit.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-task-tags.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-templates.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-properties-compiler.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-properties-task-tags.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-showdetailpane.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-type-hierarchy.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-view-outline.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-view-package-explorer.htm
    bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-externalize-strings.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-100.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-101.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-102.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-103.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-104.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-105.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-106.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-107.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-108.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-109.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-109a.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-109b.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-11.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-110.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-111.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-112.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-113.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-114.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-115.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-115a.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-116.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-117.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-118.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-12.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-120.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-121.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-122.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-123.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-124.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-126.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-13.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-130.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-130a.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-131.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-133.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-134.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-135.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-136.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-137.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-138.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-14.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-141.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-142.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-144.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-144a.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-144b.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-144c.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-145.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-146.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-147.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-149.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-15.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-150.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-151.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-152.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-153.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-154.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-155.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-156.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-157.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-158.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-159.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-160.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-161.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-162.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-163.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-164.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-165.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-166.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-167.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-168.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-169.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-17.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-170.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-171.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-172.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-173.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-174.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-175.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-176.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-177.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-178.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-179.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-17b.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-18.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-180.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-181.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-182.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-183.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-184.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-185.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-186.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-187.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-188.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-189.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-19.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-190.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-191.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-192.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-193.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-194.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-195.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-196.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-199.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-2.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-20.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-200.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-201.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-202.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-203.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-204.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-205.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-206.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-207.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-208.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-209.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-21.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-210.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-211.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-212.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-213.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-214.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-216.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-217.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-218.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-219.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-21b.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-220.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-221.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-222.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-223.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-224.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-225.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-226.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-23.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-230.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-231.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-232.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-233.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-234.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-24.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-25.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-26.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-27.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-3.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-30.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-31.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-32.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-33.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-34.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-35.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-36.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-37.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-38.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-39.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-4.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-40.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-41.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-42.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-44.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-45.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-47.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-5.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-51.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-54.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-57.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-58.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-59.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-6.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-60.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-61.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-62.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-63.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-63a.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-64.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-65.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-66.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-67.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-68.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-69.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-7.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-70.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-71.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-72.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-73.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-74.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-75.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-76.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-77.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-78.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-79.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-80.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-81.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-82.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-83.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-84.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-85.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-86.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-87.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-88.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-89.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-9.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-90.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-91.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-92.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-93.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-94.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-95.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-96.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-97.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-98.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-99.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-JREs.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-consoleAppearance.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-debug-launch.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-deleteJRE.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-executionArgs.htm
    bundles/org.eclipse.jdt.doc.user/tasks/tasks-java-local-configuration.htm
    bundles/org.eclipse.jdt.doc.user/tips/images/3.1_tag.png
    bundles/org.eclipse.jdt.doc.user/tips/images/DeclarationView.png
    bundles/org.eclipse.jdt.doc.user/tips/images/JavadocView.png
    bundles/org.eclipse.jdt.doc.user/tips/images/advanced-highlighting.png
    bundles/org.eclipse.jdt.doc.user/tips/images/annotation-navigation.png
    bundles/org.eclipse.jdt.doc.user/tips/images/assign-to-casted-quickfix.png
    bundles/org.eclipse.jdt.doc.user/tips/images/build-path-actions.png
    bundles/org.eclipse.jdt.doc.user/tips/images/call_hierarchy.png
    bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-add-constructor.png
    bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-anonym.png
    bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-argument-proposal-inserted.png
    bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-argument-proposal.png
    bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-fieldname.png
    bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-javadoc2.png
    bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-newmethod.png
    bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-type-arg-guessing.png
    bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-type-arg-guessing2.png
    bundles/org.eclipse.jdt.doc.user/tips/images/code-assist.png
    bundles/org.eclipse.jdt.doc.user/tips/images/code-templates.png
    bundles/org.eclipse.jdt.doc.user/tips/images/codeassist-getter.png
    bundles/org.eclipse.jdt.doc.user/tips/images/compare-java.png
    bundles/org.eclipse.jdt.doc.user/tips/images/compare-properties.png
    bundles/org.eclipse.jdt.doc.user/tips/images/compiler-projectspecific.png
    bundles/org.eclipse.jdt.doc.user/tips/images/compress-packages1.png
    bundles/org.eclipse.jdt.doc.user/tips/images/compress-packages2.png
    bundles/org.eclipse.jdt.doc.user/tips/images/create-getter-setter.png
    bundles/org.eclipse.jdt.doc.user/tips/images/debug-drop-down.png
    bundles/org.eclipse.jdt.doc.user/tips/images/delegate-method.png
    bundles/org.eclipse.jdt.doc.user/tips/images/editor-code-hover.png
    bundles/org.eclipse.jdt.doc.user/tips/images/editor-hover-window.png
    bundles/org.eclipse.jdt.doc.user/tips/images/editor-link-style-open.png
    bundles/org.eclipse.jdt.doc.user/tips/images/ff4.png
    bundles/org.eclipse.jdt.doc.user/tips/images/folding-preferences.png
    bundles/org.eclipse.jdt.doc.user/tips/images/hierarchy-lockview.png
    bundles/org.eclipse.jdt.doc.user/tips/images/hovergenericsignature.png
    bundles/org.eclipse.jdt.doc.user/tips/images/inplace_outline.png
    bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-location.png
    bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-prefs.png
    bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-quickfix.png
    bundles/org.eclipse.jdt.doc.user/tips/images/juniterr.png
    bundles/org.eclipse.jdt.doc.user/tips/images/junitsucc.png
    bundles/org.eclipse.jdt.doc.user/tips/images/localhistory-replace.png
    bundles/org.eclipse.jdt.doc.user/tips/images/localhistory-restore.png
    bundles/org.eclipse.jdt.doc.user/tips/images/mark-occurrences-toolbar.png
    bundles/org.eclipse.jdt.doc.user/tips/images/mark-occurrences.png
    bundles/org.eclipse.jdt.doc.user/tips/images/mark-return-occurrences.png
    bundles/org.eclipse.jdt.doc.user/tips/images/matching-brackets.png
    bundles/org.eclipse.jdt.doc.user/tips/images/name-conventions.png
    bundles/org.eclipse.jdt.doc.user/tips/images/new-class.png
    bundles/org.eclipse.jdt.doc.user/tips/images/new-scrapbook-button.png
    bundles/org.eclipse.jdt.doc.user/tips/images/open-type-camel-case.png
    bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/args_tab.png
    bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/assign_value.png
    bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/breakpoint_condition.png
    bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/breakpoint_menu.png
    bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/code_assist.png
    bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/context_menu_launch.png
    bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/deadlock.png
    bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/def_vm_args.png
    bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/detail_formatter.png
    bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/env_tab.png
    bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/inspect_popup.png
    bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/logical_structure_toggle.png
    bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/pin_console.png
    bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/process_properties.png
    bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/scrapbook.png
    bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/stack_trace.png
    bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/step_into_selection.png
    bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/stop_in_main.png
    bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/variable_hover.png
    bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/watchpoint_properties.png
    bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/word_wrap.png
    bundles/org.eclipse.jdt.doc.user/tips/images/override-method.png
    bundles/org.eclipse.jdt.doc.user/tips/images/package-explorer.png
    bundles/org.eclipse.jdt.doc.user/tips/images/packages-compound.png
    bundles/org.eclipse.jdt.doc.user/tips/images/packages-flat.png
    bundles/org.eclipse.jdt.doc.user/tips/images/packages-hierarchical.png
    bundles/org.eclipse.jdt.doc.user/tips/images/parameter-hints.png
    bundles/org.eclipse.jdt.doc.user/tips/images/problems-in-javadoc.png
    bundles/org.eclipse.jdt.doc.user/tips/images/project-specific-jre.png
    bundles/org.eclipse.jdt.doc.user/tips/images/project-specific-settings.png
    bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-assign-statement.png
    bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-assign-statement2.png
    bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-catch-to-throws.png
    bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-create-field.png
    bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-remove-surrounding.png
    bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-shortcuts.png
    bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-create-method.png
    bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-localrename.png
    bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-uncaught-exception.png
    bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-unimplemented-methods.png
    bundles/org.eclipse.jdt.doc.user/tips/images/quick-outline-inherited.png
    bundles/org.eclipse.jdt.doc.user/tips/images/quick-refactoring-menu.png
    bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast1.png
    bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast2.png
    bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast3.png
    bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-change-signature.png
    bundles/org.eclipse.jdt.doc.user/tips/images/search-returntype.png
    bundles/org.eclipse.jdt.doc.user/tips/images/search.png
    bundles/org.eclipse.jdt.doc.user/tips/images/smart-javadoc.png
    bundles/org.eclipse.jdt.doc.user/tips/images/sort-by-def.png
    bundles/org.eclipse.jdt.doc.user/tips/images/spelling-correction-proposal.png
    bundles/org.eclipse.jdt.doc.user/tips/images/ss4.png
    bundles/org.eclipse.jdt.doc.user/tips/images/suppresswarningsR31.png
    bundles/org.eclipse.jdt.doc.user/tips/images/surroundwith.png
    bundles/org.eclipse.jdt.doc.user/tips/images/template-for-iter.png
    bundles/org.eclipse.jdt.doc.user/tips/images/templates-create-method.png
    bundles/org.eclipse.jdt.doc.user/tips/images/todo-example.png
    bundles/org.eclipse.jdt.doc.user/tips/images/type-access-rules.png
    bundles/org.eclipse.jdt.doc.user/tips/images/type-filter.png
    bundles/org.eclipse.jdt.doc.user/tips/images/type-hierarchy-structured-view.png
    bundles/org.eclipse.jdt.doc.user/tips/images/typing-preferences.png
    bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-i.png
    bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-opt.png
    bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-x.png
    bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-x2.png
    bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-y.png
    bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-y2.png
    bundles/org.eclipse.jdt.doc.user/tips/images/warn-privates.png
    bundles/org.eclipse.jdt.doc.user/tips/jdt_tips.html
    bundles/org.eclipse.jdt.doc.user/toc.xml
    bundles/org.eclipse.jdt.doc.user/topics_Concepts.xml
    bundles/org.eclipse.jdt.doc.user/topics_GettingStarted.xml
    bundles/org.eclipse.jdt.doc.user/topics_Reference.xml
    bundles/org.eclipse.jdt.doc.user/topics_Tasks.xml
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/EnumConstantQuickFix.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/FirstContact.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/NewEnumAnnWizards.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/SerialVersionID.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/UnusedLocalWarning.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/UnusedLocalWarningSuppressed.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/access-restrictionR31.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/accessrulesR31.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/add_typeparam.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/advan-qas1.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/assignmenthasnoeffectR31.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/augment-after.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/augment-before.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/autoboxing_proposals.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/book.css
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/buildpath-menu.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/change-compliance-quickfix.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/completeannotationattributeR31.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/completiononemptyword.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/cpy.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/ctrl-click.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/deprecated_member_highlighting.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/enhanced-for-2.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/enhanced-for.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/enumidentifierR31.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/externalize_strings_wizard.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/folding.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/formatter.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/header_folding.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/implementsannotationR31.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/import-static-groups.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/inferdialog.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/interface_refactoring.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/javadoc-quickfix.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/javasearchfilter.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/line-wrap.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/mark-implement-occurrences.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/missingdeprecatedannotationR31.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/missingenumconstantR31.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/missingoverrideannotationR31.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/mixed-indents.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/move-refactoring.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/navigatorlocaltypeR31.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/new-type-wizard.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/new_for_loop.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/nls-hover.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/open-type.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/deadlock.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/edit_jre.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/edit_value.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/logical_structures.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/stack_trace_console.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/tostring_inline.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/override_method.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/package-explorer.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/packageinfosupportR31.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/perprojectlink.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/project-settings.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/properties-file-compare.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/property-key-navigation.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist-shortcuts.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist1.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist1b.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist2.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist3.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist4.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist5.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/rename-type-parameter.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/rerunfailed.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/selectinjavadoc.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/sourcefolderwizard.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/staticimportcodeassistR31.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/supertype.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/suppresswarningsR31.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/suppresswarningsTokenR31.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/syntax_coloring.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/type-argument-completion.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/typeparameterhidingtypeR31.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/unboxingwarningR31.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/undo.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/varargsneedcastR31.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/images/visibility-adjustment.png
    bundles/org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html
    bundles/org.eclipse.pde.doc.user/.classpath
    bundles/org.eclipse.pde.doc.user/.project
    bundles/org.eclipse.pde.doc.user/META-INF/MANIFEST.MF
    bundles/org.eclipse.pde.doc.user/aaa-how-to-add-things.txt
    bundles/org.eclipse.pde.doc.user/about.html
    bundles/org.eclipse.pde.doc.user/about.ini
    bundles/org.eclipse.pde.doc.user/about.mappings
    bundles/org.eclipse.pde.doc.user/about.properties
    bundles/org.eclipse.pde.doc.user/book.css
    bundles/org.eclipse.pde.doc.user/build.properties
    bundles/org.eclipse.pde.doc.user/build.xml
    bundles/org.eclipse.pde.doc.user/buildDoc.xml
    bundles/org.eclipse.pde.doc.user/contexts_PDE.xml
    bundles/org.eclipse.pde.doc.user/cpy.png
    bundles/org.eclipse.pde.doc.user/eclipse32.png
    bundles/org.eclipse.pde.doc.user/guide/book.css
    bundles/org.eclipse.pde.doc.user/guide/dynamic-classpaths.htm
    bundles/org.eclipse.pde.doc.user/guide/feature_based_product.htm
    bundles/org.eclipse.pde.doc.user/guide/images/accessible.PNG
    bundles/org.eclipse.pde.doc.user/guide/images/actionSet-1.png
    bundles/org.eclipse.pde.doc.user/guide/images/binary-import1.png
    bundles/org.eclipse.pde.doc.user/guide/images/binary-import2.png
    bundles/org.eclipse.pde.doc.user/guide/images/binary-projects.png
    bundles/org.eclipse.pde.doc.user/guide/images/build-editor.png
    bundles/org.eclipse.pde.doc.user/guide/images/build-source.PNG
    bundles/org.eclipse.pde.doc.user/guide/images/classpath-update.png
    bundles/org.eclipse.pde.doc.user/guide/images/compiler_discouraged.PNG
    bundles/org.eclipse.pde.doc.user/guide/images/content_assist_discouraged.PNG
    bundles/org.eclipse.pde.doc.user/guide/images/convert-java.png
    bundles/org.eclipse.pde.doc.user/guide/images/convert.PNG
    bundles/org.eclipse.pde.doc.user/guide/images/default-codegen.png
    bundles/org.eclipse.pde.doc.user/guide/images/discourage_pref.PNG
    bundles/org.eclipse.pde.doc.user/guide/images/discouraged.PNG
    bundles/org.eclipse.pde.doc.user/guide/images/errorLog.png
    bundles/org.eclipse.pde.doc.user/guide/images/feature-advanced.png
    bundles/org.eclipse.pde.doc.user/guide/images/feature-content.png
    bundles/org.eclipse.pde.doc.user/guide/images/feature-dependencies.PNG
    bundles/org.eclipse.pde.doc.user/guide/images/feature-export.png
    bundles/org.eclipse.pde.doc.user/guide/images/feature-jar.png
    bundles/org.eclipse.pde.doc.user/guide/images/feature-overview-info.png
    bundles/org.eclipse.pde.doc.user/guide/images/feature-overview.png
    bundles/org.eclipse.pde.doc.user/guide/images/feature-synchronizing.png
    bundles/org.eclipse.pde.doc.user/guide/images/forbidden_pref.PNG
    bundles/org.eclipse.pde.doc.user/guide/images/fragment-content.png
    bundles/org.eclipse.pde.doc.user/guide/images/fragment-overview.png
    bundles/org.eclipse.pde.doc.user/guide/images/friends.PNG
    bundles/org.eclipse.pde.doc.user/guide/images/hello-world-page.png
    bundles/org.eclipse.pde.doc.user/guide/images/included-features.PNG
    bundles/org.eclipse.pde.doc.user/guide/images/initial-structure.png
    bundles/org.eclipse.pde.doc.user/guide/images/install-site-features.png
    bundles/org.eclipse.pde.doc.user/guide/images/install-update-sites.png
    bundles/org.eclipse.pde.doc.user/guide/images/java-interface.png
    bundles/org.eclipse.pde.doc.user/guide/images/jnlp.PNG
    bundles/org.eclipse.pde.doc.user/guide/images/launch-dialog.png
    bundles/org.eclipse.pde.doc.user/guide/images/launch-plugins.png
    bundles/org.eclipse.pde.doc.user/guide/images/launch-tracing.png
    bundles/org.eclipse.pde.doc.user/guide/images/manifest-source.PNG
    bundles/org.eclipse.pde.doc.user/guide/images/manifest-validate.png
    bundles/org.eclipse.pde.doc.user/guide/images/ngrelc.png
    bundles/org.eclipse.pde.doc.user/guide/images/ngrelt.png
    bundles/org.eclipse.pde.doc.user/guide/images/pdeperspective.png
    bundles/org.eclipse.pde.doc.user/guide/images/plugin-dependencies.png
    bundles/org.eclipse.pde.doc.user/guide/images/plugin-expoint.png
    bundles/org.eclipse.pde.doc.user/guide/images/plugin-export.png
    bundles/org.eclipse.pde.doc.user/guide/images/plugin-overview.png
    bundles/org.eclipse.pde.doc.user/guide/images/plugin-runtime.png
    bundles/org.eclipse.pde.doc.user/guide/images/plugin-source.png
    bundles/org.eclipse.pde.doc.user/guide/images/preferences.png
    bundles/org.eclipse.pde.doc.user/guide/images/product-branding.PNG
    bundles/org.eclipse.pde.doc.user/guide/images/product-configuration-features.PNG
    bundles/org.eclipse.pde.doc.user/guide/images/product-configuration-plugins.PNG
    bundles/org.eclipse.pde.doc.user/guide/images/product-export.PNG
    bundles/org.eclipse.pde.doc.user/guide/images/product-overview.PNG
    bundles/org.eclipse.pde.doc.user/guide/images/product_config_wizard.PNG
    bundles/org.eclipse.pde.doc.user/guide/images/project-codegen.png
    bundles/org.eclipse.pde.doc.user/guide/images/project-structure.png
    bundles/org.eclipse.pde.doc.user/guide/images/properties.PNG
    bundles/org.eclipse.pde.doc.user/guide/images/rcp_content.PNG
    bundles/org.eclipse.pde.doc.user/guide/images/rcp_mail.PNG
    bundles/org.eclipse.pde.doc.user/guide/images/rcp_mail_app.PNG
    bundles/org.eclipse.pde.doc.user/guide/images/registry.png
    bundles/org.eclipse.pde.doc.user/guide/images/restriction-dialog.png
    bundles/org.eclipse.pde.doc.user/guide/images/schema-1.png
    bundles/org.eclipse.pde.doc.user/guide/images/schema-2.png
    bundles/org.eclipse.pde.doc.user/guide/images/schema-outline.png
    bundles/org.eclipse.pde.doc.user/guide/images/schema-usage.png
    bundles/org.eclipse.pde.doc.user/guide/images/site-description.png
    bundles/org.eclipse.pde.doc.user/guide/images/site-features.png
    bundles/org.eclipse.pde.doc.user/guide/images/site-new.png
    bundles/org.eclipse.pde.doc.user/guide/images/source-locations.png
    bundles/org.eclipse.pde.doc.user/guide/images/xyz-tracing.png
    bundles/org.eclipse.pde.doc.user/guide/intro/pde_overview.htm
    bundles/org.eclipse.pde.doc.user/guide/parsers.htm
    bundles/org.eclipse.pde.doc.user/guide/pde.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_build_editor.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_configuring.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_convert.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_creating.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_deploy.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_feature_generating.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_feature_generating_ant.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_feature_generating_antcommandline.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_feature_generating_build.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_feature_manifest.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_feature_setup.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_feature_synchronizing.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_features.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_fragment.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_fragment_example.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_manifest.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_manifest_dependencies.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_manifest_extensionpoints.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_manifest_extensions.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_manifest_overview.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_manifest_runtime.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_manifest_source.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_running.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_running_debugging.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_running_plugins.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_running_tracing.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_schema.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_schema_editor.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_schema_using.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_setup.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_site_building.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_site_editor.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_site_previewing.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_site_setup.htm
    bundles/org.eclipse.pde.doc.user/guide/pde_sites.htm
    bundles/org.eclipse.pde.doc.user/guide/plugins_as_jars.htm
    bundles/org.eclipse.pde.doc.user/guide/product_configuration.htm
    bundles/org.eclipse.pde.doc.user/guide/product_editor.htm
    bundles/org.eclipse.pde.doc.user/guide/product_export.htm
    bundles/org.eclipse.pde.doc.user/guide/rcp_project.htm
    bundles/org.eclipse.pde.doc.user/guide/restrictions.htm
    bundles/org.eclipse.pde.doc.user/guide/schema.css
    bundles/org.eclipse.pde.doc.user/notices.html
    bundles/org.eclipse.pde.doc.user/pdeOptions
    bundles/org.eclipse.pde.doc.user/pdeOptions.txt
    bundles/org.eclipse.pde.doc.user/plugin.properties
    bundles/org.eclipse.pde.doc.user/plugin.xml
    bundles/org.eclipse.pde.doc.user/reference/extension-points/index.html
    bundles/org.eclipse.pde.doc.user/reference/misc/index.html
    bundles/org.eclipse.pde.doc.user/reference/misc/overview-pde.html
    bundles/org.eclipse.pde.doc.user/schema.css
    bundles/org.eclipse.pde.doc.user/tips/images/package-prefix.png
    bundles/org.eclipse.pde.doc.user/tips/pde_tips.htm
    bundles/org.eclipse.pde.doc.user/toc.xml
    bundles/org.eclipse.pde.doc.user/topics_Reference.xml
    bundles/org.eclipse.pde.doc.user/whatsNew/images/book.css
    bundles/org.eclipse.pde.doc.user/whatsNew/images/bundlizer.png
    bundles/org.eclipse.pde.doc.user/whatsNew/images/compilers.PNG
    bundles/org.eclipse.pde.doc.user/whatsNew/images/cpy.png
    bundles/org.eclipse.pde.doc.user/whatsNew/images/cross.png
    bundles/org.eclipse.pde.doc.user/whatsNew/images/export.png
    bundles/org.eclipse.pde.doc.user/whatsNew/images/overview.png
    bundles/org.eclipse.pde.doc.user/whatsNew/images/plugins.PNG
    bundles/org.eclipse.pde.doc.user/whatsNew/images/pluginwizard.png
    bundles/org.eclipse.pde.doc.user/whatsNew/images/product-editor.png
    bundles/org.eclipse.pde.doc.user/whatsNew/images/project_pref.PNG
    bundles/org.eclipse.pde.doc.user/whatsNew/images/restricted.png
    bundles/org.eclipse.pde.doc.user/whatsNew/images/rich_client.PNG
    bundles/org.eclipse.pde.doc.user/whatsNew/images/runtime.png
    bundles/org.eclipse.pde.doc.user/whatsNew/images/signed.png
    bundles/org.eclipse.pde.doc.user/whatsNew/images/templates.PNG
    bundles/org.eclipse.pde.doc.user/whatsNew/images/validate.PNG
    bundles/org.eclipse.pde.doc.user/whatsNew/images/validation.png
    bundles/org.eclipse.pde.doc.user/whatsNew/pde_whatsnew.htm
    bundles/org.eclipse.pde.doc.user/workbench.png
    bundles/org.eclipse.platform.doc.isv/.classpath
    bundles/org.eclipse.platform.doc.isv/.cvsignore
    bundles/org.eclipse.platform.doc.isv/.project
    bundles/org.eclipse.platform.doc.isv/.settings/org.eclipse.pde.prefs
    bundles/org.eclipse.platform.doc.isv/META-INF/MANIFEST.MF
    bundles/org.eclipse.platform.doc.isv/aaa-how-to-add-things.txt
    bundles/org.eclipse.platform.doc.isv/about.html
    bundles/org.eclipse.platform.doc.isv/book.css
    bundles/org.eclipse.platform.doc.isv/build.properties
    bundles/org.eclipse.platform.doc.isv/buildDoc.xml
    bundles/org.eclipse.platform.doc.isv/customBuildCallbacks.xml
    bundles/org.eclipse.platform.doc.isv/guide/adding_interfaces.htm
    bundles/org.eclipse.platform.doc.isv/guide/ant.htm
    bundles/org.eclipse.platform.doc.isv/guide/ant_contributing_task.htm
    bundles/org.eclipse.platform.doc.isv/guide/ant_developing.htm
    bundles/org.eclipse.platform.doc.isv/guide/ant_eclipse_tasks.htm
    bundles/org.eclipse.platform.doc.isv/guide/ant_expanding_classpath.htm
    bundles/org.eclipse.platform.doc.isv/guide/ant_running_buildfiles_programmatically.htm
    bundles/org.eclipse.platform.doc.isv/guide/arch.htm
    bundles/org.eclipse.platform.doc.isv/guide/arch_struct.htm
    bundles/org.eclipse.platform.doc.isv/guide/compare.htm
    bundles/org.eclipse.platform.doc.isv/guide/compare_beyond.htm
    bundles/org.eclipse.platform.doc.isv/guide/compare_contentviewer.htm
    bundles/org.eclipse.platform.doc.isv/guide/compare_streammerger.htm
    bundles/org.eclipse.platform.doc.isv/guide/compare_structureviewer.htm
    bundles/org.eclipse.platform.doc.isv/guide/component_framework.htm
    bundles/org.eclipse.platform.doc.isv/guide/component_implementation.htm
    bundles/org.eclipse.platform.doc.isv/guide/debug.htm
    bundles/org.eclipse.platform.doc.isv/guide/debug_breakpoints.htm
    bundles/org.eclipse.platform.doc.isv/guide/debug_debug.htm
    bundles/org.eclipse.platform.doc.isv/guide/debug_expressions.htm
    bundles/org.eclipse.platform.doc.isv/guide/debug_launch.htm
    bundles/org.eclipse.platform.doc.isv/guide/debug_launch_adding.htm
    bundles/org.eclipse.platform.doc.isv/guide/debug_launch_comparators.htm
    bundles/org.eclipse.platform.doc.isv/guide/debug_launch_java.htm
    bundles/org.eclipse.platform.doc.isv/guide/debug_launch_processfactories.htm
    bundles/org.eclipse.platform.doc.isv/guide/debug_launch_sourcelocators.htm
    bundles/org.eclipse.platform.doc.isv/guide/debug_launch_status.htm
    bundles/org.eclipse.platform.doc.isv/guide/debug_launch_ui.htm
    bundles/org.eclipse.platform.doc.isv/guide/debug_launch_uiimages.htm
    bundles/org.eclipse.platform.doc.isv/guide/debug_launch_uishortcuts.htm
    bundles/org.eclipse.platform.doc.isv/guide/debug_model.htm
    bundles/org.eclipse.platform.doc.isv/guide/debug_presentation.htm
    bundles/org.eclipse.platform.doc.isv/guide/debug_ui.htm
    bundles/org.eclipse.platform.doc.isv/guide/dialogs.htm
    bundles/org.eclipse.platform.doc.isv/guide/dialogs_applications.htm
    bundles/org.eclipse.platform.doc.isv/guide/dialogs_settings.htm
    bundles/org.eclipse.platform.doc.isv/guide/dialogs_standard.htm
    bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards.htm
    bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_exportWizards.htm
    bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_extensions.htm
    bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_importWizards.htm
    bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_multipage.htm
    bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_newWizards.htm
    bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_wizarddialogs.htm
    bundles/org.eclipse.platform.doc.isv/guide/editors.htm
    bundles/org.eclipse.platform.doc.isv/guide/editors_actions.htm
    bundles/org.eclipse.platform.doc.isv/guide/editors_annotations.htm
    bundles/org.eclipse.platform.doc.isv/guide/editors_contentassist.htm
    bundles/org.eclipse.platform.doc.isv/guide/editors_documents.htm
    bundles/org.eclipse.platform.doc.isv/guide/editors_highlighting.htm
    bundles/org.eclipse.platform.doc.isv/guide/editors_hover.htm
    bundles/org.eclipse.platform.doc.isv/guide/editors_jface.htm
    bundles/org.eclipse.platform.doc.isv/guide/editors_sourceviewers.htm
    bundles/org.eclipse.platform.doc.isv/guide/editors_utilities.htm
    bundles/org.eclipse.platform.doc.isv/guide/editors_workbench.htm
    bundles/org.eclipse.platform.doc.isv/guide/editors_workbench_outliner.htm
    bundles/org.eclipse.platform.doc.isv/guide/firstplugin.htm
    bundles/org.eclipse.platform.doc.isv/guide/firstplugin_btb.htm
    bundles/org.eclipse.platform.doc.isv/guide/firstplugin_create.htm
    bundles/org.eclipse.platform.doc.isv/guide/firstplugin_manifest.htm
    bundles/org.eclipse.platform.doc.isv/guide/firstplugin_minimal.htm
    bundles/org.eclipse.platform.doc.isv/guide/firstplugin_run.htm
    bundles/org.eclipse.platform.doc.isv/guide/firstplugin_view.htm
    bundles/org.eclipse.platform.doc.isv/guide/forms.htm
    bundles/org.eclipse.platform.doc.isv/guide/forms_colors.htm
    bundles/org.eclipse.platform.doc.isv/guide/forms_controls.htm
    bundles/org.eclipse.platform.doc.isv/guide/forms_controls_form.htm
    bundles/org.eclipse.platform.doc.isv/guide/forms_controls_link.htm
    bundles/org.eclipse.platform.doc.isv/guide/forms_controls_section.htm
    bundles/org.eclipse.platform.doc.isv/guide/forms_controls_text.htm
    bundles/org.eclipse.platform.doc.isv/guide/forms_controls_text_markup.htm
    bundles/org.eclipse.platform.doc.isv/guide/forms_editors.htm
    bundles/org.eclipse.platform.doc.isv/guide/forms_layouts.htm
    bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_column.htm
    bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_table.htm
    bundles/org.eclipse.platform.doc.isv/guide/forms_managed.htm
    bundles/org.eclipse.platform.doc.isv/guide/forms_master_details.htm
    bundles/org.eclipse.platform.doc.isv/guide/images/DefaultContextView.PNG
    bundles/org.eclipse.platform.doc.isv/guide/images/MultiplexAllView.PNG
    bundles/org.eclipse.platform.doc.isv/guide/images/NameViewNew.PNG
    bundles/org.eclipse.platform.doc.isv/guide/images/OverrideInstanceView.PNG
    bundles/org.eclipse.platform.doc.isv/guide/images/RedirectAllView.PNG
    bundles/org.eclipse.platform.doc.isv/guide/images/RedirectContextView.PNG
    bundles/org.eclipse.platform.doc.isv/guide/images/about.png
    bundles/org.eclipse.platform.doc.isv/guide/images/actionseteditorretargets.png
    bundles/org.eclipse.platform.doc.isv/guide/images/actionsetoutlineretargets.png
    bundles/org.eclipse.platform.doc.isv/guide/images/actionsets.png
    bundles/org.eclipse.platform.doc.isv/guide/images/arch-npi.jpg
    bundles/org.eclipse.platform.doc.isv/guide/images/arch.jpg
    bundles/org.eclipse.platform.doc.isv/guide/images/basicIntro.png
    bundles/org.eclipse.platform.doc.isv/guide/images/browserexample.png
    bundles/org.eclipse.platform.doc.isv/guide/images/cheatsheets.png
    bundles/org.eclipse.platform.doc.isv/guide/images/common_tab.png
    bundles/org.eclipse.platform.doc.isv/guide/images/components_diagram.png
    bundles/org.eclipse.platform.doc.isv/guide/images/composite_view.PNG
    bundles/org.eclipse.platform.doc.isv/guide/images/cvsdecorators.png
    bundles/org.eclipse.platform.doc.isv/guide/images/dependencies_view.PNG
    bundles/org.eclipse.platform.doc.isv/guide/images/editorAction.png
    bundles/org.eclipse.platform.doc.isv/guide/images/editorInputLabel.png
    bundles/org.eclipse.platform.doc.isv/guide/images/editormenu.png
    bundles/org.eclipse.platform.doc.isv/guide/images/editoroutlineretargets.png
    bundles/org.eclipse.platform.doc.isv/guide/images/editorretargets.png
    bundles/org.eclipse.platform.doc.isv/guide/images/editortoolbar.png
    bundles/org.eclipse.platform.doc.isv/guide/images/emptyworkbench.png
    bundles/org.eclipse.platform.doc.isv/guide/images/exportwizard.png
    bundles/org.eclipse.platform.doc.isv/guide/images/filetypes.png
    bundles/org.eclipse.platform.doc.isv/guide/images/filtersmenu.png
    bundles/org.eclipse.platform.doc.isv/guide/images/filtersselection.png
    bundles/org.eclipse.platform.doc.isv/guide/images/firstpluginpde.png
    bundles/org.eclipse.platform.doc.isv/guide/images/genericoutliner.png
    bundles/org.eclipse.platform.doc.isv/guide/images/help_contents.png
    bundles/org.eclipse.platform.doc.isv/guide/images/ignore.png
    bundles/org.eclipse.platform.doc.isv/guide/images/importwizard.png
    bundles/org.eclipse.platform.doc.isv/guide/images/infopops.png
    bundles/org.eclipse.platform.doc.isv/guide/images/javacheatsheet.png
    bundles/org.eclipse.platform.doc.isv/guide/images/javacontentassist.png
    bundles/org.eclipse.platform.doc.isv/guide/images/javacontentoutline.png
    bundles/org.eclipse.platform.doc.isv/guide/images/javacontextassist.png
    bundles/org.eclipse.platform.doc.isv/guide/images/javaeditor.png
    bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorcontextmenu.png
    bundles/org.eclipse.platform.doc.isv/guide/images/javaeditoroverviewruler.png
    bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorsquiggly.png
    bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorverticalruler.png
    bundles/org.eclipse.platform.doc.isv/guide/images/javarulerhover.png
    bundles/org.eclipse.platform.doc.isv/guide/images/javatexthover.png
    bundles/org.eclipse.platform.doc.isv/guide/images/keybindings.png
    bundles/org.eclipse.platform.doc.isv/guide/images/launch.jpg
    bundles/org.eclipse.platform.doc.isv/guide/images/launchImage.png
    bundles/org.eclipse.platform.doc.isv/guide/images/lcd.png
    bundles/org.eclipse.platform.doc.isv/guide/images/markerquickfixmenu.png
    bundles/org.eclipse.platform.doc.isv/guide/images/markerresolution.png
    bundles/org.eclipse.platform.doc.isv/guide/images/navigator.png
    bundles/org.eclipse.platform.doc.isv/guide/images/newwizardlist.png
    bundles/org.eclipse.platform.doc.isv/guide/images/newwizardmenu.png
    bundles/org.eclipse.platform.doc.isv/guide/images/perspectivemenu.png
    bundles/org.eclipse.platform.doc.isv/guide/images/preferences.png
    bundles/org.eclipse.platform.doc.isv/guide/images/projectset.png
    bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionset.png
    bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionsetmenu.png
    bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionsettool.png
    bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionsettoolbar.png
    bundles/org.eclipse.platform.doc.isv/guide/images/readmedialog.png
    bundles/org.eclipse.platform.doc.isv/guide/images/readmemarkerhelp.png
    bundles/org.eclipse.platform.doc.isv/guide/images/readmemarkermenu.png
    bundles/org.eclipse.platform.doc.isv/guide/images/readmeoutliner.png
    bundles/org.eclipse.platform.doc.isv/guide/images/readmeoutlinerpopup.png
    bundles/org.eclipse.platform.doc.isv/guide/images/readmeoverview.png
    bundles/org.eclipse.platform.doc.isv/guide/images/readmepopupmenu.png
    bundles/org.eclipse.platform.doc.isv/guide/images/readmepreferences.png
    bundles/org.eclipse.platform.doc.isv/guide/images/readmeproperties.png
    bundles/org.eclipse.platform.doc.isv/guide/images/readmeview.png
    bundles/org.eclipse.platform.doc.isv/guide/images/readmeviewaction.png
    bundles/org.eclipse.platform.doc.isv/guide/images/readmewizard.png
    bundles/org.eclipse.platform.doc.isv/guide/images/sdk-arch.jpg
    bundles/org.eclipse.platform.doc.isv/guide/images/showview.png
    bundles/org.eclipse.platform.doc.isv/guide/images/singleclick.png
    bundles/org.eclipse.platform.doc.isv/guide/images/team-version_controlled.png
    bundles/org.eclipse.platform.doc.isv/guide/images/team_synchronize_example_localhistory_overview.png
    bundles/org.eclipse.platform.doc.isv/guide/images/teamdecorators.png
    bundles/org.eclipse.platform.doc.isv/guide/images/teamintegration.png
    bundles/org.eclipse.platform.doc.isv/guide/images/teamprefs.png
    bundles/org.eclipse.platform.doc.isv/guide/images/texteditor.png
    bundles/org.eclipse.platform.doc.isv/guide/images/textencoding.png
    bundles/org.eclipse.platform.doc.isv/guide/images/ua_cheatsheet.png
    bundles/org.eclipse.platform.doc.isv/guide/images/ua_help.png
    bundles/org.eclipse.platform.doc.isv/guide/images/ua_intro.png
    bundles/org.eclipse.platform.doc.isv/guide/images/win_only.png
    bundles/org.eclipse.platform.doc.isv/guide/images/wiz_arch.jpg
    bundles/org.eclipse.platform.doc.isv/guide/images/workbench.png
    bundles/org.eclipse.platform.doc.isv/guide/images/workbench_decomposed.png
    bundles/org.eclipse.platform.doc.isv/guide/images/workbenchdecorators.png
    bundles/org.eclipse.platform.doc.isv/guide/images/workbenchwithhello.png
    bundles/org.eclipse.platform.doc.isv/guide/images/workingSetTypes.png
    bundles/org.eclipse.platform.doc.isv/guide/images/workingset.png
    bundles/org.eclipse.platform.doc.isv/guide/implementing_components.htm
    bundles/org.eclipse.platform.doc.isv/guide/initializers.htm
    bundles/org.eclipse.platform.doc.isv/guide/instantiating_parts.htm
    bundles/org.eclipse.platform.doc.isv/guide/int.htm
    bundles/org.eclipse.platform.doc.isv/guide/int_eclipse.htm
    bundles/org.eclipse.platform.doc.isv/guide/int_goal.htm
    bundles/org.eclipse.platform.doc.isv/guide/int_who.htm
    bundles/org.eclipse.platform.doc.isv/guide/java_web_start.htm
    bundles/org.eclipse.platform.doc.isv/guide/jface.htm
    bundles/org.eclipse.platform.doc.isv/guide/jface_actions.htm
    bundles/org.eclipse.platform.doc.isv/guide/jface_operations.htm
    bundles/org.eclipse.platform.doc.isv/guide/jface_resources.htm
    bundles/org.eclipse.platform.doc.isv/guide/jface_viewers.htm
    bundles/org.eclipse.platform.doc.isv/guide/multiplexing_interface.htm
    bundles/org.eclipse.platform.doc.isv/guide/nesting.htm
    bundles/org.eclipse.platform.doc.isv/guide/part_interfaces.htm
    bundles/org.eclipse.platform.doc.isv/guide/passing_arguments.htm
    bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs.htm
    bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_contribute.htm
    bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_fieldeditors.htm
    bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_implement.htm
    bundles/org.eclipse.platform.doc.isv/guide/preferences_prop_contribute.htm
    bundles/org.eclipse.platform.doc.isv/guide/preferences_prop_implement.htm
    bundles/org.eclipse.platform.doc.isv/guide/product.htm
    bundles/org.eclipse.platform.doc.isv/guide/product_config_install.htm
    bundles/org.eclipse.platform.doc.isv/guide/product_configfeature.htm
    bundles/org.eclipse.platform.doc.isv/guide/product_configproduct.htm
    bundles/org.eclipse.platform.doc.isv/guide/product_def.htm
    bundles/org.eclipse.platform.doc.isv/guide/product_def_extpt.htm
    bundles/org.eclipse.platform.doc.isv/guide/product_def_feature.htm
    bundles/org.eclipse.platform.doc.isv/guide/product_def_nl.htm
    bundles/org.eclipse.platform.doc.isv/guide/product_def_plugins.htm
    bundles/org.eclipse.platform.doc.isv/guide/product_def_primary.htm
    bundles/org.eclipse.platform.doc.isv/guide/product_extension.htm
    bundles/org.eclipse.platform.doc.isv/guide/product_update.htm
    bundles/org.eclipse.platform.doc.isv/guide/rcp.htm
    bundles/org.eclipse.platform.doc.isv/guide/rcp_actions.htm
    bundles/org.eclipse.platform.doc.isv/guide/rcp_advisor.htm
    bundles/org.eclipse.platform.doc.isv/guide/rcp_browser.htm
    bundles/org.eclipse.platform.doc.isv/guide/rcp_define.htm
    bundles/org.eclipse.platform.doc.isv/guide/rcp_dynamic.htm
    bundles/org.eclipse.platform.doc.isv/guide/rcp_extensions.htm
    bundles/org.eclipse.platform.doc.isv/guide/rcp_perspective.htm
    bundles/org.eclipse.platform.doc.isv/guide/rcp_view.htm
    bundles/org.eclipse.platform.doc.isv/guide/resAdv_batching.htm
    bundles/org.eclipse.platform.doc.isv/guide/resAdv_builders.htm
    bundles/org.eclipse.platform.doc.isv/guide/resAdv_concurrency.htm
    bundles/org.eclipse.platform.doc.isv/guide/resAdv_derived.htm
    bundles/org.eclipse.platform.doc.isv/guide/resAdv_events.htm
    bundles/org.eclipse.platform.doc.isv/guide/resAdv_hooks.htm
    bundles/org.eclipse.platform.doc.isv/guide/resAdv_markers.htm
    bundles/org.eclipse.platform.doc.isv/guide/resAdv_modify.htm
    bundles/org.eclipse.platform.doc.isv/guide/resAdv_natures.htm
    bundles/org.eclipse.platform.doc.isv/guide/resAdv_refresh.htm
    bundles/org.eclipse.platform.doc.isv/guide/resAdv_saving.htm
    bundles/org.eclipse.platform.doc.isv/guide/resInt.htm
    bundles/org.eclipse.platform.doc.isv/guide/resInt_content.htm
    bundles/org.eclipse.platform.doc.isv/guide/resInt_filesystem.htm
    bundles/org.eclipse.platform.doc.isv/guide/resInt_linked.htm
    bundles/org.eclipse.platform.doc.isv/guide/resInt_preferences.htm
    bundles/org.eclipse.platform.doc.isv/guide/resInt_properties.htm
    bundles/org.eclipse.platform.doc.isv/guide/resInt_workspace.htm
    bundles/org.eclipse.platform.doc.isv/guide/runtime.htm
    bundles/org.eclipse.platform.doc.isv/guide/runtime_content.htm
    bundles/org.eclipse.platform.doc.isv/guide/runtime_content_contributing.htm
    bundles/org.eclipse.platform.doc.isv/guide/runtime_content_using.htm
    bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs.htm
    bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_locks.htm
    bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_progress.htm
    bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_rules.htm
    bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_scheduling.htm
    bundles/org.eclipse.platform.doc.isv/guide/runtime_model.htm
    bundles/org.eclipse.platform.doc.isv/guide/runtime_model_bundles.htm
    bundles/org.eclipse.platform.doc.isv/guide/runtime_preferences.htm
    bundles/org.eclipse.platform.doc.isv/guide/runtime_registry.htm
    bundles/org.eclipse.platform.doc.isv/guide/search.htm
    bundles/org.eclipse.platform.doc.isv/guide/search_page.htm
    bundles/org.eclipse.platform.doc.isv/guide/search_result.htm
    bundles/org.eclipse.platform.doc.isv/guide/site_interfaces.htm
    bundles/org.eclipse.platform.doc.isv/guide/sites_work.htm
    bundles/org.eclipse.platform.doc.isv/guide/swt.htm
    bundles/org.eclipse.platform.doc.isv/guide/swt_error.htm
    bundles/org.eclipse.platform.doc.isv/guide/swt_graphics.htm
    bundles/org.eclipse.platform.doc.isv/guide/swt_layouts.htm
    bundles/org.eclipse.platform.doc.isv/guide/swt_layouts_custom.htm
    bundles/org.eclipse.platform.doc.isv/guide/swt_threading.htm
    bundles/org.eclipse.platform.doc.isv/guide/swt_widgets.htm
    bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_controls.htm
    bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_custom.htm
    bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_events.htm
    bundles/org.eclipse.platform.doc.isv/guide/team.htm
    bundles/org.eclipse.platform.doc.isv/guide/team_howto.htm
    bundles/org.eclipse.platform.doc.isv/guide/team_provider_repository.htm
    bundles/org.eclipse.platform.doc.isv/guide/team_resources.htm
    bundles/org.eclipse.platform.doc.isv/guide/team_resources_filetypes.htm
    bundles/org.eclipse.platform.doc.isv/guide/team_resources_linked.htm
    bundles/org.eclipse.platform.doc.isv/guide/team_resources_private.htm
    bundles/org.eclipse.platform.doc.isv/guide/team_resources_projects.htm
    bundles/org.eclipse.platform.doc.isv/guide/team_synchronize.htm
    bundles/org.eclipse.platform.doc.isv/guide/team_synchronize_beyond_basics.htm
    bundles/org.eclipse.platform.doc.isv/guide/team_synchronize_localhistory_example.htm
    bundles/org.eclipse.platform.doc.isv/guide/team_ui.htm
    bundles/org.eclipse.platform.doc.isv/guide/team_ui_actions.htm
    bundles/org.eclipse.platform.doc.isv/guide/team_ui_decorators.htm
    bundles/org.eclipse.platform.doc.isv/guide/team_ui_prefs.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite_content.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_simple.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_anchors.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_filters.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_includes.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_help.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_help_content.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_action.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_debug.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_invoke.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command_authoring.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_files.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_manifest.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_nested.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_toc.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_xhtml.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_help_context.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_dynamic.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_id.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_infopops.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_xml.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_help_search.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_help_search_types.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_intro.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_intro_cust_intro_part.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_intro_cust_static.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_intro_define_content.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining_config.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_custom_url.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_standbypart.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending_content.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_intro_hello_world.htm
    bundles/org.eclipse.platform.doc.isv/guide/ua_intro_xhtml.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_actionfilters.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_activities.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_contexts.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_decorators.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_elementFactories.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_perspectiveExtension.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_perspectives.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_resourceFilters.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_actionSetPartAssociations.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_actionSets.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_editorActions.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_editors.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_popupMenus.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_viewActions.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_views.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_guiding.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_jobs.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_menupaths.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_menus.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_perspectives.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_plugin.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_resources.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_scalability.htm
    bundles/org.eclipse.platform.doc.isv/guide/workbench_structure.htm
    bundles/org.eclipse.platform.doc.isv/guide/wrkAdv.htm
    bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_accessibility.htm
    bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_encoding.htm
    bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings.htm
    bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelConfig.htm
    bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelSet.htm
    bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_actionDef.htm
    bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_contexts.htm
    bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerhelp.htm
    bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerresolution.htm
    bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markers.htm
    bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget.htm
    bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute.htm
    bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute_actionsets.htm
    bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute_editors.htm
    bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_setting.htm
    bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_singleclick.htm
    bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_undo.htm
    bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_workingsets.htm
    bundles/org.eclipse.platform.doc.isv/notices.html
    bundles/org.eclipse.platform.doc.isv/platformOptions.txt
    bundles/org.eclipse.platform.doc.isv/plugin.properties
    bundles/org.eclipse.platform.doc.isv/plugin.xml
    bundles/org.eclipse.platform.doc.isv/porting/3.0/faq.html
    bundles/org.eclipse.platform.doc.isv/porting/3.0/incompatibilities.html
    bundles/org.eclipse.platform.doc.isv/porting/3.0/recommended.html
    bundles/org.eclipse.platform.doc.isv/porting/3.1/faq.html
    bundles/org.eclipse.platform.doc.isv/porting/3.1/incompatibilities.html
    bundles/org.eclipse.platform.doc.isv/porting/3.1/recommended.html
    bundles/org.eclipse.platform.doc.isv/porting/3.2/faq.html
    bundles/org.eclipse.platform.doc.isv/porting/3.2/incompatibilities.html
    bundles/org.eclipse.platform.doc.isv/porting/3.2/recommended.html
    bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_0_porting_guide.html
    bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_1_porting_guide.html
    bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_2_porting_guide.html
    bundles/org.eclipse.platform.doc.isv/questions/index.html
    bundles/org.eclipse.platform.doc.isv/reference/.cvsignore
    bundles/org.eclipse.platform.doc.isv/reference/extension-points/index.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/Idea.jpg
    bundles/org.eclipse.platform.doc.isv/reference/misc/about_customization.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/api-usage-rules.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/bidi.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/bidi.png
    bundles/org.eclipse.platform.doc.isv/reference/misc/buddy_loading.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/bundle_manifest.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/eclipse-install.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/eclipsestarter.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/feature_archive.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/feature_manifest.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/help_infocenter.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/help_infocenter_update.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/help_preferences.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/help_product_index.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/help_standalone.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/index.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/message_bundles.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/multi_user_installs.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/naming.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/overview-platform.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_archive.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_dtd.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_manifest.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/preference_store.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/project_description_file.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/terminology.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/ui_accessibility_tips.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/update_platform_xml.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/update_policy.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/update_sitemap.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/update_standalone.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/web_triggered_updates.html
    bundles/org.eclipse.platform.doc.isv/reference/misc/win_only.png
    bundles/org.eclipse.platform.doc.isv/samples/samples.html
    bundles/org.eclipse.platform.doc.isv/schema.css
    bundles/org.eclipse.platform.doc.isv/src/org/eclipse/platform/doc/isv/activeHelp/ActiveHelpOpenDialogAction.java
    bundles/org.eclipse.platform.doc.isv/toc.xml
    bundles/org.eclipse.platform.doc.isv/topics_Guide.xml
    bundles/org.eclipse.platform.doc.isv/topics_Porting.xml
    bundles/org.eclipse.platform.doc.isv/topics_Questions.xml
    bundles/org.eclipse.platform.doc.isv/topics_Reference.xml
    bundles/org.eclipse.platform.doc.isv/topics_Samples.xml
    bundles/org.eclipse.platform.doc.isv/workbench.png
    bundles/org.eclipse.platform.doc.user/.project
    bundles/org.eclipse.platform.doc.user/.settings/org.eclipse.pde.prefs
    bundles/org.eclipse.platform.doc.user/META-INF/MANIFEST.MF
    bundles/org.eclipse.platform.doc.user/about.html
    bundles/org.eclipse.platform.doc.user/book.css
    bundles/org.eclipse.platform.doc.user/build.properties
    bundles/org.eclipse.platform.doc.user/concepts/accessibility/accessmain.htm
    bundles/org.eclipse.platform.doc.user/concepts/accessibility/colordialog.htm
    bundles/org.eclipse.platform.doc.user/concepts/accessibility/fontsandcolors.htm
    bundles/org.eclipse.platform.doc.user/concepts/accessibility/keyboardshortcuts.htm
    bundles/org.eclipse.platform.doc.user/concepts/accessibility/navigation.htm
    bundles/org.eclipse.platform.doc.user/concepts/cbookmrk.htm
    bundles/org.eclipse.platform.doc.user/concepts/cdecorations.htm
    bundles/org.eclipse.platform.doc.user/concepts/chelpsys.htm
    bundles/org.eclipse.platform.doc.user/concepts/chelpview.htm
    bundles/org.eclipse.platform.doc.user/concepts/cnav.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-11.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-12.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-13.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-17.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-17a.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-18.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-2.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-21.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-22.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-25.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-26.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-27.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-27b.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-27c.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-29.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-30.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-4.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-5.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-6.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-6a.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-activites.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-antsupport.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-cvs-watch.htm
    bundles/org.eclipse.platform.doc.user/concepts/concepts-exttools.htm
    bundles/org.eclipse.platform.doc.user/concepts/coutline.htm
    bundles/org.eclipse.platform.doc.user/concepts/cpathvars.htm
    bundles/org.eclipse.platform.doc.user/concepts/cprbview.htm
    bundles/org.eclipse.platform.doc.user/concepts/cpropview.htm
    bundles/org.eclipse.platform.doc.user/concepts/csearchview.htm
    bundles/org.eclipse.platform.doc.user/concepts/ctskview.htm
    bundles/org.eclipse.platform.doc.user/concepts/cworkset.htm
    bundles/org.eclipse.platform.doc.user/concepts/no_help_exists.htm
    bundles/org.eclipse.platform.doc.user/contexts_AntUI.xml
    bundles/org.eclipse.platform.doc.user/contexts_Compare.xml
    bundles/org.eclipse.platform.doc.user/contexts_ExternalTools.xml
    bundles/org.eclipse.platform.doc.user/contexts_Help.xml
    bundles/org.eclipse.platform.doc.user/contexts_Search.xml
    bundles/org.eclipse.platform.doc.user/contexts_Team.xml
    bundles/org.eclipse.platform.doc.user/contexts_Team_CVS.xml
    bundles/org.eclipse.platform.doc.user/contexts_Update.xml
    bundles/org.eclipse.platform.doc.user/contexts_Workbench.xml
    bundles/org.eclipse.platform.doc.user/cpy.png
    bundles/org.eclipse.platform.doc.user/customBuildCallbacks.xml
    bundles/org.eclipse.platform.doc.user/doc.html
    bundles/org.eclipse.platform.doc.user/gettingStarted/gs_htmldoc_book.book
    bundles/org.eclipse.platform.doc.user/gettingStarted/intro/overview.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/no_help_exists.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-01.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02a.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02b.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02d.xhtml
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02e.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07a.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07b.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07c.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07d.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-10b.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12b.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12c.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12d.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-13.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-24a.xhtml
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-24c.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31a.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31b.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31c.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-32.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34a.xhtml
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34b.xhtml
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34c.xhtml
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34d.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35b.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35c.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35d.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36a.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36b.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2b.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2d.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2d2.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2f.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3b.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3c.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3e.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3f.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39c.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39d.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39e.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39f.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39g.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40a.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40b.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43b.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43c.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43e.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43f.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52c.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52d.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52e.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-55.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-55b.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-60_team.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-60a_setup.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61c_offline.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61d_repoloca.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61d_repolocb.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61e_whatisloc.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61f_syncproject.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-62b_sync.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-62c_releasing.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64a_another.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64b_fredadd.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64b_fredmod.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_mod.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_sync2.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_sync3_rel.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_sync_view.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-70_replace.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-74_review.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-74_version.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-80_ant.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-81_basics.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-82_create.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-83_edit.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-84_run_ant.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-85_ant_configs.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-85a_ant_view.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-86_use_cases.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-87_plugin_deploy.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-88_create_plugin.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-89_generate_buildxml.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-90_build_jar.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-91_build_options.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-92_project_builders.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-93_project_builder.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-94_run_pj.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-95_external_tools.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-96_non_ant_pjs.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-97_standalone_ets.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-content.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs-responsiveUI.htm
    bundles/org.eclipse.platform.doc.user/gettingStarted/qs_activites.htm
    bundles/org.eclipse.platform.doc.user/images/Image1.png
    bundles/org.eclipse.platform.doc.user/images/Image11_new_wizard.png
    bundles/org.eclipse.platform.doc.user/images/Image12_new_project_wizard.png
    bundles/org.eclipse.platform.doc.user/images/Image13_project_in_nav.png
    bundles/org.eclipse.platform.doc.user/images/Image14_new_folder_wizard.png
    bundles/org.eclipse.platform.doc.user/images/Image15_new_button.png
    bundles/org.eclipse.platform.doc.user/images/Image15_project_depend.png
    bundles/org.eclipse.platform.doc.user/images/Image16_new_pulldown.png
    bundles/org.eclipse.platform.doc.user/images/Image17_save_button.png
    bundles/org.eclipse.platform.doc.user/images/Image17b_unsaved_changes.png
    bundles/org.eclipse.platform.doc.user/images/Image18_created_resources.png
    bundles/org.eclipse.platform.doc.user/images/Image19_close_on_tab.png
    bundles/org.eclipse.platform.doc.user/images/Image201_filetype.png
    bundles/org.eclipse.platform.doc.user/images/Image202_editorsel.png
    bundles/org.eclipse.platform.doc.user/images/Image203_actionset.png
    bundles/org.eclipse.platform.doc.user/images/Image206_persp_saveas.png
    bundles/org.eclipse.platform.doc.user/images/Image207_persp_sel.png
    bundles/org.eclipse.platform.doc.user/images/Image208_view_sel.png
    bundles/org.eclipse.platform.doc.user/images/Image209_workspace.png
    bundles/org.eclipse.platform.doc.user/images/Image20_nav_with_resources.png
    bundles/org.eclipse.platform.doc.user/images/Image210_filefilter.png
    bundles/org.eclipse.platform.doc.user/images/Image211_fastview.png
    bundles/org.eclipse.platform.doc.user/images/Image211_perspective.png
    bundles/org.eclipse.platform.doc.user/images/Image214_toobar_rsrc.png
    bundles/org.eclipse.platform.doc.user/images/Image215_toolbar_view.png
    bundles/org.eclipse.platform.doc.user/images/Image216_history_view.png
    bundles/org.eclipse.platform.doc.user/images/Image217_pref_wb.png
    bundles/org.eclipse.platform.doc.user/images/Image218_pref_app.png
    bundles/org.eclipse.platform.doc.user/images/Image219_pref_cv.png
    bundles/org.eclipse.platform.doc.user/images/Image21_task_view.png
    bundles/org.eclipse.platform.doc.user/images/Image220_pref_dte.png
    bundles/org.eclipse.platform.doc.user/images/Image221_pref_fe.png
    bundles/org.eclipse.platform.doc.user/images/Image222_pref_lh.png
    bundles/org.eclipse.platform.doc.user/images/Image223_pref_persp.png
    bundles/org.eclipse.platform.doc.user/images/Image224_pref_build.png
    bundles/org.eclipse.platform.doc.user/images/Image225_pref_help.png
    bundles/org.eclipse.platform.doc.user/images/Image229_editor_popup.png
    bundles/org.eclipse.platform.doc.user/images/Image229_view_popup.png
    bundles/org.eclipse.platform.doc.user/images/Image230_editor_area.png
    bundles/org.eclipse.platform.doc.user/images/Image231_marker_bar.png
    bundles/org.eclipse.platform.doc.user/images/Image232_marker_context.png
    bundles/org.eclipse.platform.doc.user/images/Image237_search_view.png
    bundles/org.eclipse.platform.doc.user/images/Image239_help_view.png
    bundles/org.eclipse.platform.doc.user/images/Image240_props_view.png
    bundles/org.eclipse.platform.doc.user/images/Image241_nav_view.png
    bundles/org.eclipse.platform.doc.user/images/Image242_repo_view.png
    bundles/org.eclipse.platform.doc.user/images/Image243_tasks_view.png
    bundles/org.eclipse.platform.doc.user/images/Image244_bmark_view.png
    bundles/org.eclipse.platform.doc.user/images/Image245_sync_view.png
    bundles/org.eclipse.platform.doc.user/images/Image246_file_wiz.png
    bundles/org.eclipse.platform.doc.user/images/Image247_projsel_wiz.png
    bundles/org.eclipse.platform.doc.user/images/Image248_folder_wiz.png
    bundles/org.eclipse.platform.doc.user/images/Image249_repo_wiz.png
    bundles/org.eclipse.platform.doc.user/images/Image251_proj_wiz.png
    bundles/org.eclipse.platform.doc.user/images/Image252_projref_page.png
    bundles/org.eclipse.platform.doc.user/images/Image258_perps_custom.png
    bundles/org.eclipse.platform.doc.user/images/Image261_import_sel.png
    bundles/org.eclipse.platform.doc.user/images/Image262_import_file.png
    bundles/org.eclipse.platform.doc.user/images/Image262_import_preferences.png
    bundles/org.eclipse.platform.doc.user/images/Image263_import_cvs.png
    bundles/org.eclipse.platform.doc.user/images/Image263_import_zip.png
    bundles/org.eclipse.platform.doc.user/images/Image264_existing_project.png
    bundles/org.eclipse.platform.doc.user/images/Image264_export_sel.png
    bundles/org.eclipse.platform.doc.user/images/Image264_external_feature.png
    bundles/org.eclipse.platform.doc.user/images/Image264_plugins_fragments.png
    bundles/org.eclipse.platform.doc.user/images/Image265_export_file.png
    bundles/org.eclipse.platform.doc.user/images/Image265_team_project.png
    bundles/org.eclipse.platform.doc.user/images/Image266_export_ant.png
    bundles/org.eclipse.platform.doc.user/images/Image266_export_feature.png
    bundles/org.eclipse.platform.doc.user/images/Image266_export_javadoc.png
    bundles/org.eclipse.platform.doc.user/images/Image266_export_plugins.png
    bundles/org.eclipse.platform.doc.user/images/Image266_export_preferences.png
    bundles/org.eclipse.platform.doc.user/images/Image266_export_product.png
    bundles/org.eclipse.platform.doc.user/images/Image266_export_zip.png
    bundles/org.eclipse.platform.doc.user/images/Image267_export_jar.png
    bundles/org.eclipse.platform.doc.user/images/Image268_export_team.png
    bundles/org.eclipse.platform.doc.user/images/Image269_merge_init.png
    bundles/org.eclipse.platform.doc.user/images/Image273_local_hist.png
    bundles/org.eclipse.platform.doc.user/images/Image273_nav-decorators.png
    bundles/org.eclipse.platform.doc.user/images/Image274_fonts_preference.png
    bundles/org.eclipse.platform.doc.user/images/Image274_fonts_preference2.png
    bundles/org.eclipse.platform.doc.user/images/Image275_startup_preference.png
    bundles/org.eclipse.platform.doc.user/images/Image276_search_preference.png
    bundles/org.eclipse.platform.doc.user/images/Image2_active_editor.png
    bundles/org.eclipse.platform.doc.user/images/Image2_active_view.png
    bundles/org.eclipse.platform.doc.user/images/Image30_goto_resource.png
    bundles/org.eclipse.platform.doc.user/images/Image31_go_into.png
    bundles/org.eclipse.platform.doc.user/images/Image33_into_buttons.png
    bundles/org.eclipse.platform.doc.user/images/Image35umd_extprevu.png
    bundles/org.eclipse.platform.doc.user/images/Image36_linkedresources.png
    bundles/org.eclipse.platform.doc.user/images/Image37drop.png
    bundles/org.eclipse.platform.doc.user/images/Image38_import.png
    bundles/org.eclipse.platform.doc.user/images/Image39_import_tree.png
    bundles/org.eclipse.platform.doc.user/images/Image3_single.png
    bundles/org.eclipse.platform.doc.user/images/Image3_tabbed.png
    bundles/org.eclipse.platform.doc.user/images/Image400_filterbutton.png
    bundles/org.eclipse.platform.doc.user/images/Image40_import_target.png
    bundles/org.eclipse.platform.doc.user/images/Image41_import_combo.png
    bundles/org.eclipse.platform.doc.user/images/Image42_export.png
    bundles/org.eclipse.platform.doc.user/images/Image43_export_tree.png
    bundles/org.eclipse.platform.doc.user/images/Image44_confirm_state.png
    bundles/org.eclipse.platform.doc.user/images/Image45_file_search.png
    bundles/org.eclipse.platform.doc.user/images/Image45_setup.png
    bundles/org.eclipse.platform.doc.user/images/Image48_move.png
    bundles/org.eclipse.platform.doc.user/images/Image48_rename.png
    bundles/org.eclipse.platform.doc.user/images/Image48_rename_done.png
    bundles/org.eclipse.platform.doc.user/images/Image49_3_way_compare.png
    bundles/org.eclipse.platform.doc.user/images/Image4_showview.png
    bundles/org.eclipse.platform.doc.user/images/Image50_search.png
    bundles/org.eclipse.platform.doc.user/images/Image51_choose_ext.png
    bundles/org.eclipse.platform.doc.user/images/Image51_search_hover.png
    bundles/org.eclipse.platform.doc.user/images/Image51_search_it.png
    bundles/org.eclipse.platform.doc.user/images/Image51_search_next.png
    bundles/org.eclipse.platform.doc.user/images/Image51_search_progress.png
    bundles/org.eclipse.platform.doc.user/images/Image51_search_reduced.png
    bundles/org.eclipse.platform.doc.user/images/Image51_search_switching.png
    bundles/org.eclipse.platform.doc.user/images/Image51_search_view.png
    bundles/org.eclipse.platform.doc.user/images/Image52_new_task.png
    bundles/org.eclipse.platform.doc.user/images/Image53_add_task_dlg.png
    bundles/org.eclipse.platform.doc.user/images/Image53_marker1.png
    bundles/org.eclipse.platform.doc.user/images/Image53_newtask.png
    bundles/org.eclipse.platform.doc.user/images/Image53_task_updated.png
    bundles/org.eclipse.platform.doc.user/images/Image54_bookmark1.png
    bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_added.png
    bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_added2.png
    bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_del1.png
    bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_goto.png
    bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_menu.png
    bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_oneleft.png
    bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_remove2.png
    bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_two.png
    bundles/org.eclipse.platform.doc.user/images/Image55_reset.png
    bundles/org.eclipse.platform.doc.user/images/Image57_two_editors.png
    bundles/org.eclipse.platform.doc.user/images/Image5_text_editor.png
    bundles/org.eclipse.platform.doc.user/images/Image602_tar_assist.png
    bundles/org.eclipse.platform.doc.user/images/Image603_run_dialog.png
    bundles/org.eclipse.platform.doc.user/images/Image606_refresh_tab.png
    bundles/org.eclipse.platform.doc.user/images/Image607_buildxml.png
    bundles/org.eclipse.platform.doc.user/images/Image608_buildxml_outline.png
    bundles/org.eclipse.platform.doc.user/images/Image609_project_builder.png
    bundles/org.eclipse.platform.doc.user/images/Image60_fast_view1.png
    bundles/org.eclipse.platform.doc.user/images/Image60_switch_editor.png
    bundles/org.eclipse.platform.doc.user/images/Image60_tabs.png
    bundles/org.eclipse.platform.doc.user/images/Image60_tabs2.png
    bundles/org.eclipse.platform.doc.user/images/Image610_et_options_tab.png
    bundles/org.eclipse.platform.doc.user/images/Image611_et_main_tab.png
    bundles/org.eclipse.platform.doc.user/images/Image612_et_refresh_tab.png
    bundles/org.eclipse.platform.doc.user/images/Image613_project_properties.png
    bundles/org.eclipse.platform.doc.user/images/Image614_et_type_dialog.png
    bundles/org.eclipse.platform.doc.user/images/Image615_program_builder.png
    bundles/org.eclipse.platform.doc.user/images/Image616_et_dropdown.png
    bundles/org.eclipse.platform.doc.user/images/Image617_jar_inspector.png
    bundles/org.eclipse.platform.doc.user/images/Image619_ole.png
    bundles/org.eclipse.platform.doc.user/images/Image61_fast_minimize.png
    bundles/org.eclipse.platform.doc.user/images/Image61_fast_options.png
    bundles/org.eclipse.platform.doc.user/images/Image61_fast_restore.png
    bundles/org.eclipse.platform.doc.user/images/Image61_nav_fast.png
    bundles/org.eclipse.platform.doc.user/images/Image6_two_editors.png
    bundles/org.eclipse.platform.doc.user/images/Image70_select_pers.png
    bundles/org.eclipse.platform.doc.user/images/Image70_shortcut1.png
    bundles/org.eclipse.platform.doc.user/images/Image70_shortcut2.png
    bundles/org.eclipse.platform.doc.user/images/Image70_shortcut3.png
    bundles/org.eclipse.platform.doc.user/images/Image70_shortcut4.png
    bundles/org.eclipse.platform.doc.user/images/Image71_pers_customize.png
    bundles/org.eclipse.platform.doc.user/images/Image71_pers_pref.png
    bundles/org.eclipse.platform.doc.user/images/Image71_pers_reset.png
    bundles/org.eclipse.platform.doc.user/images/Image71_pers_rundebug.png
    bundles/org.eclipse.platform.doc.user/images/Image71_pers_save.png
    bundles/org.eclipse.platform.doc.user/images/Image7_view_pulldown.png
    bundles/org.eclipse.platform.doc.user/images/Image80_compare.png
    bundles/org.eclipse.platform.doc.user/images/Image80_compare_after.png
    bundles/org.eclipse.platform.doc.user/images/Image80_compare_change2.png
    bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor.png
    bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor2.png
    bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor3.png
    bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor_next.png
    bundles/org.eclipse.platform.doc.user/images/Image80_compare_rl.png
    bundles/org.eclipse.platform.doc.user/images/Image81_local.png
    bundles/org.eclipse.platform.doc.user/images/Image82_import2_project_fred.png
    bundles/org.eclipse.platform.doc.user/images/Image82_import3_project_fred.png
    bundles/org.eclipse.platform.doc.user/images/Image82_import4_project_fred.png
    bundles/org.eclipse.platform.doc.user/images/Image82_import_project_fred.png
    bundles/org.eclipse.platform.doc.user/images/Image82_nav.png
    bundles/org.eclipse.platform.doc.user/images/Image82_repo_new.png
    bundles/org.eclipse.platform.doc.user/images/Image82_repo_new3.png
    bundles/org.eclipse.platform.doc.user/images/Image82_repo_rel5.png
    bundles/org.eclipse.platform.doc.user/images/Image82_repo_release.png
    bundles/org.eclipse.platform.doc.user/images/Image82_repo_release2.png
    bundles/org.eclipse.platform.doc.user/images/Image82_repo_res.png
    bundles/org.eclipse.platform.doc.user/images/Image82_repo_sync1.png
    bundles/org.eclipse.platform.doc.user/images/Image82_repo_sync2.png
    bundles/org.eclipse.platform.doc.user/images/Image82_repo_syncview.png
    bundles/org.eclipse.platform.doc.user/images/Image82_repo_team.png
    bundles/org.eclipse.platform.doc.user/images/Image82_repo_view1.png
    bundles/org.eclipse.platform.doc.user/images/Image83_cvs_savedpasswords.png
    bundles/org.eclipse.platform.doc.user/images/Image83_fred1.png
    bundles/org.eclipse.platform.doc.user/images/Image83_fred2.png
    bundles/org.eclipse.platform.doc.user/images/Image83_fred3_add.png
    bundles/org.eclipse.platform.doc.user/images/Image83_fred_verson.png
    bundles/org.eclipse.platform.doc.user/images/Image83_fred_verson2.png
    bundles/org.eclipse.platform.doc.user/images/Image83_jane-history.png
    bundles/org.eclipse.platform.doc.user/images/Image83_jane-sync.png
    bundles/org.eclipse.platform.doc.user/images/Image83_jane1.png
    bundles/org.eclipse.platform.doc.user/images/Image83_jane2b.png
    bundles/org.eclipse.platform.doc.user/images/Image83_jane3_conflict.png
    bundles/org.eclipse.platform.doc.user/images/Image83_jane3_conflict2.png
    bundles/org.eclipse.platform.doc.user/images/Image83_jane3_status.png
    bundles/org.eclipse.platform.doc.user/images/Image83_jane4.png
    bundles/org.eclipse.platform.doc.user/images/Image83_jane5a.png
    bundles/org.eclipse.platform.doc.user/images/Image83_jane6a.png
    bundles/org.eclipse.platform.doc.user/images/Image84_decorator_preferenc.png
    bundles/org.eclipse.platform.doc.user/images/Image84_decorator_preference.png
    bundles/org.eclipse.platform.doc.user/images/Image84_jane.png
    bundles/org.eclipse.platform.doc.user/images/Image84_relmode.png
    bundles/org.eclipse.platform.doc.user/images/Image84_replace2.png
    bundles/org.eclipse.platform.doc.user/images/Image84_reshist.png
    bundles/org.eclipse.platform.doc.user/images/Image84_status.png
    bundles/org.eclipse.platform.doc.user/images/Image85_version2.png
    bundles/org.eclipse.platform.doc.user/images/Image87_workset_sel.png
    bundles/org.eclipse.platform.doc.user/images/Image88_workset_new_type.png
    bundles/org.eclipse.platform.doc.user/images/Image89_workset_new_res.png
    bundles/org.eclipse.platform.doc.user/images/Image8_view.png
    bundles/org.eclipse.platform.doc.user/images/Image90_locked_toolbar.png
    bundles/org.eclipse.platform.doc.user/images/Image90_unlocked_toolbar.png
    bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_1.png
    bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_2.png
    bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_3.png
    bundles/org.eclipse.platform.doc.user/images/Image9_viewdownarrow.png
    bundles/org.eclipse.platform.doc.user/images/Image_auto_up.png
    bundles/org.eclipse.platform.doc.user/images/Image_filecon_pref.png
    bundles/org.eclipse.platform.doc.user/images/Image_ignore_pref.png
    bundles/org.eclipse.platform.doc.user/images/Image_pref_inup.png
    bundles/org.eclipse.platform.doc.user/images/Image_team_pref.png
    bundles/org.eclipse.platform.doc.user/images/accessibility_new_project.png
    bundles/org.eclipse.platform.doc.user/images/activity_menu.png
    bundles/org.eclipse.platform.doc.user/images/activity_toolbar.png
    bundles/org.eclipse.platform.doc.user/images/addbkmrk_co.png
    bundles/org.eclipse.platform.doc.user/images/addbkmrk_tsk.png
    bundles/org.eclipse.platform.doc.user/images/addtask.png
    bundles/org.eclipse.platform.doc.user/images/alpha_mode.png
    bundles/org.eclipse.platform.doc.user/images/annotations-preferences.png
    bundles/org.eclipse.platform.doc.user/images/ant-view.png
    bundles/org.eclipse.platform.doc.user/images/ant_code_assist.png
    bundles/org.eclipse.platform.doc.user/images/ant_editor_appearance.png
    bundles/org.eclipse.platform.doc.user/images/ant_editor_folding.png
    bundles/org.eclipse.platform.doc.user/images/ant_editor_problems.png
    bundles/org.eclipse.platform.doc.user/images/ant_editor_syntax.png
    bundles/org.eclipse.platform.doc.user/images/ant_formatter.png
    bundles/org.eclipse.platform.doc.user/images/ant_prefs.png
    bundles/org.eclipse.platform.doc.user/images/ant_run_dialog.png
    bundles/org.eclipse.platform.doc.user/images/ant_runtime_properties.png
    bundles/org.eclipse.platform.doc.user/images/ant_templates.png
    bundles/org.eclipse.platform.doc.user/images/ant_view.png
    bundles/org.eclipse.platform.doc.user/images/arch-npi.jpg
    bundles/org.eclipse.platform.doc.user/images/backward_nav.png
    bundles/org.eclipse.platform.doc.user/images/bookmark_obj.png
    bundles/org.eclipse.platform.doc.user/images/build_exec.png
    bundles/org.eclipse.platform.doc.user/images/cap-conf.png
    bundles/org.eclipse.platform.doc.user/images/cap-pref-advanced.png
    bundles/org.eclipse.platform.doc.user/images/cap-pref.png
    bundles/org.eclipse.platform.doc.user/images/capabilities.png
    bundles/org.eclipse.platform.doc.user/images/change.png
    bundles/org.eclipse.platform.doc.user/images/cheatsheet_composite_running.png
    bundles/org.eclipse.platform.doc.user/images/cheatsheet_composite_start.png
    bundles/org.eclipse.platform.doc.user/images/close_view.png
    bundles/org.eclipse.platform.doc.user/images/compare-editor.png
    bundles/org.eclipse.platform.doc.user/images/confadd_ov.png
    bundles/org.eclipse.platform.doc.user/images/confauto_ov.png
    bundles/org.eclipse.platform.doc.user/images/confchg_ov.png
    bundles/org.eclipse.platform.doc.user/images/confdel_ov.png
    bundles/org.eclipse.platform.doc.user/images/container_obj.png
    bundles/org.eclipse.platform.doc.user/images/content_type.png
    bundles/org.eclipse.platform.doc.user/images/contenttype-pref-charset.png
    bundles/org.eclipse.platform.doc.user/images/copy_edit.png
    bundles/org.eclipse.platform.doc.user/images/cut_edit.png
    bundles/org.eclipse.platform.doc.user/images/cvs-checkout1.png
    bundles/org.eclipse.platform.doc.user/images/cvs-checkout2.png
    bundles/org.eclipse.platform.doc.user/images/cvs-checkout3.png
    bundles/org.eclipse.platform.doc.user/images/cvs-checkout4.png
    bundles/org.eclipse.platform.doc.user/images/cvs-checkout5.png
    bundles/org.eclipse.platform.doc.user/images/cvs-connection.png
    bundles/org.eclipse.platform.doc.user/images/cvs-console-prefs.png
    bundles/org.eclipse.platform.doc.user/images/cvs-console.png
    bundles/org.eclipse.platform.doc.user/images/cvs-decoration-general.png
    bundles/org.eclipse.platform.doc.user/images/cvs-decoration-icon.png
    bundles/org.eclipse.platform.doc.user/images/cvs-decoration-text.png
    bundles/org.eclipse.platform.doc.user/images/cvs-ext.png
    bundles/org.eclipse.platform.doc.user/images/cvs-files.png
    bundles/org.eclipse.platform.doc.user/images/cvs-general.png
    bundles/org.eclipse.platform.doc.user/images/cvs-merge-sync.png
    bundles/org.eclipse.platform.doc.user/images/cvs-password.png
    bundles/org.eclipse.platform.doc.user/images/cvs-prompting.png
    bundles/org.eclipse.platform.doc.user/images/cvs-share1.png
    bundles/org.eclipse.platform.doc.user/images/cvs-share2.png
    bundles/org.eclipse.platform.doc.user/images/cvs-share3.png
    bundles/org.eclipse.platform.doc.user/images/cvs-share4.png
    bundles/org.eclipse.platform.doc.user/images/cvs-ssh2-general.png
    bundles/org.eclipse.platform.doc.user/images/cvs-ssh2-hosts.png
    bundles/org.eclipse.platform.doc.user/images/cvs-ssh2-key.png
    bundles/org.eclipse.platform.doc.user/images/cvs-ssh2-proxy.png
    bundles/org.eclipse.platform.doc.user/images/cvs-sync-compare.png
    bundles/org.eclipse.platform.doc.user/images/cvs-watch-edit.png
    bundles/org.eclipse.platform.doc.user/images/cvs_folder_rep.png
    bundles/org.eclipse.platform.doc.user/images/cvs_module_rep.png
    bundles/org.eclipse.platform.doc.user/images/cvs_synch.png
    bundles/org.eclipse.platform.doc.user/images/debug_exec.png
    bundles/org.eclipse.platform.doc.user/images/defaults_ps.png
    bundles/org.eclipse.platform.doc.user/images/delete_edit.png
    bundles/org.eclipse.platform.doc.user/images/description.png
    bundles/org.eclipse.platform.doc.user/images/dirty_ov.png
    bundles/org.eclipse.platform.doc.user/images/drop_bottom_source.png
    bundles/org.eclipse.platform.doc.user/images/drop_invalid_source.png
    bundles/org.eclipse.platform.doc.user/images/drop_left_source.png
    bundles/org.eclipse.platform.doc.user/images/drop_offscreen.png
    bundles/org.eclipse.platform.doc.user/images/drop_right_source.png
    bundles/org.eclipse.platform.doc.user/images/drop_stack.png
    bundles/org.eclipse.platform.doc.user/images/drop_top_source.png
    bundles/org.eclipse.platform.doc.user/images/e_maximize.png
    bundles/org.eclipse.platform.doc.user/images/e_restore.png
    bundles/org.eclipse.platform.doc.user/images/e_show_all.png
    bundles/org.eclipse.platform.doc.user/images/e_synch_nav.png
    bundles/org.eclipse.platform.doc.user/images/e_synch_toc_nav.png
    bundles/org.eclipse.platform.doc.user/images/edited_ov.png
    bundles/org.eclipse.platform.doc.user/images/et_dialog.png
    bundles/org.eclipse.platform.doc.user/images/et_dropdown.png
    bundles/org.eclipse.platform.doc.user/images/export_wiz.png
    bundles/org.eclipse.platform.doc.user/images/external_tools.png
    bundles/org.eclipse.platform.doc.user/images/external_tools_prefs.png
    bundles/org.eclipse.platform.doc.user/images/filter_ps.png
    bundles/org.eclipse.platform.doc.user/images/first_anteditor.png
    bundles/org.eclipse.platform.doc.user/images/forward_nav.png
    bundles/org.eclipse.platform.doc.user/images/gotoobj_tsk.png
    bundles/org.eclipse.platform.doc.user/images/help_manifest.png
    bundles/org.eclipse.platform.doc.user/images/help_no_manifest.png
    bundles/org.eclipse.platform.doc.user/images/help_search_w.png
    bundles/org.eclipse.platform.doc.user/images/helpview-all.png
    bundles/org.eclipse.platform.doc.user/images/helpview-bookmarks.png
    bundles/org.eclipse.platform.doc.user/images/helpview-related.png
    bundles/org.eclipse.platform.doc.user/images/helpview-search.png
    bundles/org.eclipse.platform.doc.user/images/home_nav.png
    bundles/org.eclipse.platform.doc.user/images/image618-add-ant-search.png
    bundles/org.eclipse.platform.doc.user/images/image618-add-ant.png
    bundles/org.eclipse.platform.doc.user/images/image618-ant-run.png
    bundles/org.eclipse.platform.doc.user/images/image92-begin.png
    bundles/org.eclipse.platform.doc.user/images/image92-check.png
    bundles/org.eclipse.platform.doc.user/images/image92-close.png
    bundles/org.eclipse.platform.doc.user/images/image92-collapse.png
    bundles/org.eclipse.platform.doc.user/images/image92-complete.png
    bundles/org.eclipse.platform.doc.user/images/image92-expand.png
    bundles/org.eclipse.platform.doc.user/images/image92-help.png
    bundles/org.eclipse.platform.doc.user/images/image92-hide.png
    bundles/org.eclipse.platform.doc.user/images/image92-opencheat.png
    bundles/org.eclipse.platform.doc.user/images/image92-perform.png
    bundles/org.eclipse.platform.doc.user/images/image92-redo.png
    bundles/org.eclipse.platform.doc.user/images/image92-restart.png
    bundles/org.eclipse.platform.doc.user/images/image92-save.png
    bundles/org.eclipse.platform.doc.user/images/image92-select.png
    bundles/org.eclipse.platform.doc.user/images/image92-skip-mark.png
    bundles/org.eclipse.platform.doc.user/images/image92-skip.png
    bundles/org.eclipse.platform.doc.user/images/image92-tutorial.png
    bundles/org.eclipse.platform.doc.user/images/import_wiz.png
    bundles/org.eclipse.platform.doc.user/images/keys1.png
    bundles/org.eclipse.platform.doc.user/images/keys2.png
    bundles/org.eclipse.platform.doc.user/images/keys6.png
    bundles/org.eclipse.platform.doc.user/images/last_edit_pos.png
    bundles/org.eclipse.platform.doc.user/images/mark_occurrences.png
    bundles/org.eclipse.platform.doc.user/images/max.png
    bundles/org.eclipse.platform.doc.user/images/merged_ov.png
    bundles/org.eclipse.platform.doc.user/images/minus.png
    bundles/org.eclipse.platform.doc.user/images/new_persp.png
    bundles/org.eclipse.platform.doc.user/images/new_wiz.png
    bundles/org.eclipse.platform.doc.user/images/newfile_wiz.png
    bundles/org.eclipse.platform.doc.user/images/newfolder_wiz.png
    bundles/org.eclipse.platform.doc.user/images/newprj_wiz.png
    bundles/org.eclipse.platform.doc.user/images/next_nav.png
    bundles/org.eclipse.platform.doc.user/images/ngback.png
    bundles/org.eclipse.platform.doc.user/images/ngnext.png
    bundles/org.eclipse.platform.doc.user/images/ngrelc.png
    bundles/org.eclipse.platform.doc.user/images/ngrelr.png
    bundles/org.eclipse.platform.doc.user/images/ngrelt.png
    bundles/org.eclipse.platform.doc.user/images/no_remotedir_ov.png
    bundles/org.eclipse.platform.doc.user/images/open_persp.png
    bundles/org.eclipse.platform.doc.user/images/openseparate_co.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/add_co.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/ant_targets.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/properties.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/refresh.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/removeAll_co.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/remove_co.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/run_tool.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/search.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/ctool16/external_tools.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/cview16/ant_view.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant_buildfile.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant_target_err.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/build_tab.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/classpath.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/defaulttarget_obj.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/import_obj.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/invalid_build_tool.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/jar_l_obj.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/macrodef_obj.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/main_tab.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/prop_ps.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/property_obj.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/targetinternal_obj.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/targetpublic_obj.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/task_obj.png
    bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/type.png
    bundles/org.eclipse.platform.doc.user/images/outline_hello.png
    bundles/org.eclipse.platform.doc.user/images/paste_edit.png
    bundles/org.eclipse.platform.doc.user/images/performanceview.png
    bundles/org.eclipse.platform.doc.user/images/pin_editor.png
    bundles/org.eclipse.platform.doc.user/images/pin_view.png
    bundles/org.eclipse.platform.doc.user/images/prbfil.png
    bundles/org.eclipse.platform.doc.user/images/pref_helpserver.png
    bundles/org.eclipse.platform.doc.user/images/prev_nav.png
    bundles/org.eclipse.platform.doc.user/images/print_edit.png
    bundles/org.eclipse.platform.doc.user/images/printer.png
    bundles/org.eclipse.platform.doc.user/images/prob.png
    bundles/org.eclipse.platform.doc.user/images/question_ov.png
    bundles/org.eclipse.platform.doc.user/images/r_inadd_ov.png
    bundles/org.eclipse.platform.doc.user/images/r_inchg_ov.png
    bundles/org.eclipse.platform.doc.user/images/r_indel_ov.png
    bundles/org.eclipse.platform.doc.user/images/r_outadd_ov.png
    bundles/org.eclipse.platform.doc.user/images/r_outchg_ov.png
    bundles/org.eclipse.platform.doc.user/images/r_outdel_ov.png
    bundles/org.eclipse.platform.doc.user/images/redo_edit.png
    bundles/org.eclipse.platform.doc.user/images/ref-1.png
    bundles/org.eclipse.platform.doc.user/images/ref-10.png
    bundles/org.eclipse.platform.doc.user/images/ref-11.png
    bundles/org.eclipse.platform.doc.user/images/ref-12.png
    bundles/org.eclipse.platform.doc.user/images/ref-15.png
    bundles/org.eclipse.platform.doc.user/images/ref-16.png
    bundles/org.eclipse.platform.doc.user/images/ref-17.png
    bundles/org.eclipse.platform.doc.user/images/ref-18.png
    bundles/org.eclipse.platform.doc.user/images/ref-2.png
    bundles/org.eclipse.platform.doc.user/images/ref-20.png
    bundles/org.eclipse.platform.doc.user/images/ref-21.png
    bundles/org.eclipse.platform.doc.user/images/ref-22.png
    bundles/org.eclipse.platform.doc.user/images/ref-23.png
    bundles/org.eclipse.platform.doc.user/images/ref-24.png
    bundles/org.eclipse.platform.doc.user/images/ref-25.png
    bundles/org.eclipse.platform.doc.user/images/ref-27.png
    bundles/org.eclipse.platform.doc.user/images/ref-3.png
    bundles/org.eclipse.platform.doc.user/images/ref-4.png
    bundles/org.eclipse.platform.doc.user/images/ref-5.png
    bundles/org.eclipse.platform.doc.user/images/ref-50.png
    bundles/org.eclipse.platform.doc.user/images/ref-52.png
    bundles/org.eclipse.platform.doc.user/images/ref-7.png
    bundles/org.eclipse.platform.doc.user/images/ref-79.png
    bundles/org.eclipse.platform.doc.user/images/ref-8.png
    bundles/org.eclipse.platform.doc.user/images/ref-81.png
    bundles/org.eclipse.platform.doc.user/images/ref-9.png
    bundles/org.eclipse.platform.doc.user/images/ref-accessibility.png
    bundles/org.eclipse.platform.doc.user/images/ref-annotationspref.png
    bundles/org.eclipse.platform.doc.user/images/ref-quickdiffpref.png
    bundles/org.eclipse.platform.doc.user/images/ref-spellingpref.png
    bundles/org.eclipse.platform.doc.user/images/ref-texteditorpref.png
    bundles/org.eclipse.platform.doc.user/images/ref-webbrowserpref.png
    bundles/org.eclipse.platform.doc.user/images/refresh_nav.png
    bundles/org.eclipse.platform.doc.user/images/res.png
    bundles/org.eclipse.platform.doc.user/images/res_blocked.png
    bundles/org.eclipse.platform.doc.user/images/res_build.png
    bundles/org.eclipse.platform.doc.user/images/res_details.png
    bundles/org.eclipse.platform.doc.user/images/res_otherjobs.png
    bundles/org.eclipse.platform.doc.user/images/res_pref.png
    bundles/org.eclipse.platform.doc.user/images/run_exec.png
    bundles/org.eclipse.platform.doc.user/images/save_edit.png
    bundles/org.eclipse.platform.doc.user/images/saveall_edit.png
    bundles/org.eclipse.platform.doc.user/images/saveas_edit.png
    bundles/org.eclipse.platform.doc.user/images/search_src.png
    bundles/org.eclipse.platform.doc.user/images/searchm_obj.png
    bundles/org.eclipse.platform.doc.user/images/segment_edit.png
    bundles/org.eclipse.platform.doc.user/images/sinfocenter_obj.png
    bundles/org.eclipse.platform.doc.user/images/slocalhelp_obj.png
    bundles/org.eclipse.platform.doc.user/images/stop_nav.png
    bundles/org.eclipse.platform.doc.user/images/sweb_obj.png
    bundles/org.eclipse.platform.doc.user/images/synced.png
    bundles/org.eclipse.platform.doc.user/images/synch_participants.png
    bundles/org.eclipse.platform.doc.user/images/tasks-1.png
    bundles/org.eclipse.platform.doc.user/images/tasks-3.png
    bundles/org.eclipse.platform.doc.user/images/tasks-7.png
    bundles/org.eclipse.platform.doc.user/images/tasks-96b-module_rep.png
    bundles/org.eclipse.platform.doc.user/images/team-file-content.png
    bundles/org.eclipse.platform.doc.user/images/team-ignore.png
    bundles/org.eclipse.platform.doc.user/images/team-prefs.png
    bundles/org.eclipse.platform.doc.user/images/team_contents_icon.png
    bundles/org.eclipse.platform.doc.user/images/toc_closed.png
    bundles/org.eclipse.platform.doc.user/images/toc_open.png
    bundles/org.eclipse.platform.doc.user/images/topic_small.png
    bundles/org.eclipse.platform.doc.user/images/tree_mode.png
    bundles/org.eclipse.platform.doc.user/images/undo_edit.png
    bundles/org.eclipse.platform.doc.user/images/up_nav.png
    bundles/org.eclipse.platform.doc.user/images/version_controlled.png
    bundles/org.eclipse.platform.doc.user/images/view_menu.png
    bundles/org.eclipse.platform.doc.user/images/viewer.png
    bundles/org.eclipse.platform.doc.user/images/win_only.png
    bundles/org.eclipse.platform.doc.user/images/xml.png
    bundles/org.eclipse.platform.doc.user/no_help_exists.htm
    bundles/org.eclipse.platform.doc.user/notices.html
    bundles/org.eclipse.platform.doc.user/plugin.properties
    bundles/org.eclipse.platform.doc.user/plugin.xml
    bundles/org.eclipse.platform.doc.user/quickstart.htm
    bundles/org.eclipse.platform.doc.user/reference/no_help_exists.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-10.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-11.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-12.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-13.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-14.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-14b.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-15.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-16.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-17.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-18.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-19.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-console.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-decorations.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-ext.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-password.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-ssh2.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-sync.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-watch-edit.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-19cvs.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-2.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-20-fileContent.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-20.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-21.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-21a.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-22.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-23.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-24.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-25.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-26.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-27.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-28.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-29.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-3.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-30.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-30a.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-31.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-31a.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-32.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-32a.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-32b.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-33.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-33a.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-34.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-35.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-36.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-37.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-38.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-39.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-39a.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-3a.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-4.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-40.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-40a.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-40b.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-41a.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-42.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-43.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-45.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-47.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-48a.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-5.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-56.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-57.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-58.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-59.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-6.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-60.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-61.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-65.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-66.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-67.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-68.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-6a.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-7.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-70.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-71.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-72.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-8.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-9.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-activites.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-activitiespref.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-antcodeassist.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-anteditor.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-anteditorprefs.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-antformatter.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-anticons.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-antprefs.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-antruntimeprefs.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-anttemplates.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-antview.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-capabilities.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-cheatsheets.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-composite-cheatsheets.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-content-type.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-cvs-decorations.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-decorations.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-exttoolsprefs.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-fonts.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-helpserver.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-keybindings.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-search.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-startup.htm
    bundles/org.eclipse.platform.doc.user/reference/ref-texteditorprefs.htm
    bundles/org.eclipse.platform.doc.user/tasks/antRunner.htm
    bundles/org.eclipse.platform.doc.user/tasks/no_help_exists.htm
    bundles/org.eclipse.platform.doc.user/tasks/running_eclipse.htm
    bundles/org.eclipse.platform.doc.user/tasks/taccess.htm
    bundles/org.eclipse.platform.doc.user/tasks/task-team-cmdlineclient.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-1.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-100.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-100a.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-100b.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-100d.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-100d1.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-100d1b.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-100d2.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-101.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-103.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-105.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-105a.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-105b.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-105c.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-107b.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-110.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-113.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-113b.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-114.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-115.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-117.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-117a.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-117b.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-118.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-119.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-14.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-16.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-17.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-18.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-1a.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-1b.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-1c.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-1d.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-1e.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-1f.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-1g.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-1h.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-1i.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-1j.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-1k.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-2.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-20.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-24.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-28.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-3.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-31.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-33.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-34.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-35.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-36.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-37.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-37a.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-38.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-3e.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-3g.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-3h.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-3i.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-42.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-42b.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-43.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-44.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-45.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-46.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-46ag.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-46bg.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-47.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-48.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-48b.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-49.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-51.xhtml
    bundles/org.eclipse.platform.doc.user/tasks/tasks-52.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-53.xhtml
    bundles/org.eclipse.platform.doc.user/tasks/tasks-55.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-55bg.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-57.xhtml
    bundles/org.eclipse.platform.doc.user/tasks/tasks-59.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-59ag.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-63.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-63cg.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-66.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-67.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-68.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-68b.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-68bg.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-68c.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-68dg.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-70.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-73.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-75.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-77.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-77b.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-78.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-79.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-81.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-81b.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-82.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-84.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-84b.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-87.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-87b.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-88.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-9.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-92.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-93.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-94.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-95.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-95a.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-96.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-96a.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-96b.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-9b.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-9c.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-9d.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-9f.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-9i.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-9j.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-9k.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-activites.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-addtasksandtypes.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-classpath.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-running.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-version.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-10.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-11.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-16.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-annotate.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-passwords.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-project-set.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-quickdiff.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-ssh2.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-watch.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-exttools-running.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-importproject.htm
    bundles/org.eclipse.platform.doc.user/tasks/tasks-team-1.htm
    bundles/org.eclipse.platform.doc.user/tasks/tchgbrws.htm
    bundles/org.eclipse.platform.doc.user/tasks/tf1help.htm
    bundles/org.eclipse.platform.doc.user/tasks/tfonts.xhtml
    bundles/org.eclipse.platform.doc.user/tasks/timpandexp.htm
    bundles/org.eclipse.platform.doc.user/tasks/tkeybindings.htm
    bundles/org.eclipse.platform.doc.user/tasks/topenmode.htm
    bundles/org.eclipse.platform.doc.user/tasks/tquickfix.htm
    bundles/org.eclipse.platform.doc.user/tasks/tsearch.htm
    bundles/org.eclipse.platform.doc.user/tasks/ttoolbars.htm
    bundles/org.eclipse.platform.doc.user/tips/images/3.0_tag.png
    bundles/org.eclipse.platform.doc.user/tips/images/3.1_tag.png
    bundles/org.eclipse.platform.doc.user/tips/images/add_bkmrk.png
    bundles/org.eclipse.platform.doc.user/tips/images/annotations-preferences.png
    bundles/org.eclipse.platform.doc.user/tips/images/backgroundpref.png
    bundles/org.eclipse.platform.doc.user/tips/images/backward_nav.png
    bundles/org.eclipse.platform.doc.user/tips/images/bookmarks_view.png
    bundles/org.eclipse.platform.doc.user/tips/images/capabilities-page.png
    bundles/org.eclipse.platform.doc.user/tips/images/changelog-obj.gif
    bundles/org.eclipse.platform.doc.user/tips/images/collapse-all.png
    bundles/org.eclipse.platform.doc.user/tips/images/compare-merge-button.png
    bundles/org.eclipse.platform.doc.user/tips/images/compare-showancestor.png
    bundles/org.eclipse.platform.doc.user/tips/images/editor-tiles.png
    bundles/org.eclipse.platform.doc.user/tips/images/fastview-drag.png
    bundles/org.eclipse.platform.doc.user/tips/images/help-working-set.png
    bundles/org.eclipse.platform.doc.user/tips/images/key-assist.png
    bundles/org.eclipse.platform.doc.user/tips/images/key-bindings.png
    bundles/org.eclipse.platform.doc.user/tips/images/keyboard-shortcut.png
    bundles/org.eclipse.platform.doc.user/tips/images/last_edit_pos.png
    bundles/org.eclipse.platform.doc.user/tips/images/link-with-editor.png
    bundles/org.eclipse.platform.doc.user/tips/images/mini-view.png
    bundles/org.eclipse.platform.doc.user/tips/images/path-vars.png
    bundles/org.eclipse.platform.doc.user/tips/images/pb-context-menu.png
    bundles/org.eclipse.platform.doc.user/tips/images/perspective-other.png
    bundles/org.eclipse.platform.doc.user/tips/images/pin-editor.png
    bundles/org.eclipse.platform.doc.user/tips/images/props-view.png
    bundles/org.eclipse.platform.doc.user/tips/images/quickdiff-hover.png
    bundles/org.eclipse.platform.doc.user/tips/images/restore-local.png
    bundles/org.eclipse.platform.doc.user/tips/images/show-in.png
    bundles/org.eclipse.platform.doc.user/tips/images/team-project-set.png
    bundles/org.eclipse.platform.doc.user/tips/images/team_contents_icon.png
    bundles/org.eclipse.platform.doc.user/tips/images/userdialog.png
    bundles/org.eclipse.platform.doc.user/tips/platform_tips.html
    bundles/org.eclipse.platform.doc.user/toc.xml
    bundles/org.eclipse.platform.doc.user/topics_Concepts.xml
    bundles/org.eclipse.platform.doc.user/topics_GettingStarted.xml
    bundles/org.eclipse.platform.doc.user/topics_Reference.xml
    bundles/org.eclipse.platform.doc.user/topics_Tasks.xml
    bundles/org.eclipse.platform.doc.user/whatsNew/images/advanced_gc.jpg
    bundles/org.eclipse.platform.doc.user/whatsNew/images/ant-external-documentation.gif
    bundles/org.eclipse.platform.doc.user/whatsNew/images/ant-hyperlink.gif
    bundles/org.eclipse.platform.doc.user/whatsNew/images/ant_dep_callstack.gif
    bundles/org.eclipse.platform.doc.user/whatsNew/images/ant_folding.gif
    bundles/org.eclipse.platform.doc.user/whatsNew/images/attributes.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/bidi.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/book.css
    bundles/org.eclipse.platform.doc.user/whatsNew/images/branching.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/breakpoint_workingsets.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/build_targets.gif
    bundles/org.eclipse.platform.doc.user/whatsNew/images/capabilities.gif
    bundles/org.eclipse.platform.doc.user/whatsNew/images/changelog-obj.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/colon-slash.gif
    bundles/org.eclipse.platform.doc.user/whatsNew/images/commit-wizard.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/contenttypes.gif
    bundles/org.eclipse.platform.doc.user/whatsNew/images/control.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/cpy.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/cvsfail.gif
    bundles/org.eclipse.platform.doc.user/whatsNew/images/demo.gif
    bundles/org.eclipse.platform.doc.user/whatsNew/images/detachview1.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/detachview2.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/dynamic-help.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/export-targz.gif
    bundles/org.eclipse.platform.doc.user/whatsNew/images/file-types.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/gc-caps-joins.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/help-view.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/hyperlinking.gif
    bundles/org.eclipse.platform.doc.user/whatsNew/images/importmultiple.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/importwiz.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/intro-launch-bar.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/jard_plugins.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/keycompletions.gif
    bundles/org.eclipse.platform.doc.user/whatsNew/images/line-delimiter.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/linkwidget.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/mirrors.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/moveable.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/multi-line-search.gif
    bundles/org.eclipse.platform.doc.user/whatsNew/images/new-plugin-rcp.gif
    bundles/org.eclipse.platform.doc.user/whatsNew/images/occur.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/outgoing-commit-sets.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/perf-example.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/platform01.gif
    bundles/org.eclipse.platform.doc.user/whatsNew/images/platform02.gif
    bundles/org.eclipse.platform.doc.user/whatsNew/images/pref.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/preferences.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/rename.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/select-required.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/shared-preferences.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/sites-import-export.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/spinner_float.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/strike_underline.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/swtlauncher.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/tag-filtering.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/team-decorators.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/templates.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/treetable.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/undo_history_size.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/undosample.png
    bundles/org.eclipse.platform.doc.user/whatsNew/images/workspace.gif
    bundles/org.eclipse.platform.doc.user/whatsNew/images/xpbuttons.png
    bundles/org.eclipse.platform.doc.user/whatsNew/platform_whatsnew.html
    bundles/org.eclipse.platform.doc.user/workbench.png
diff --git a/bundles/org.eclipse.jdt.doc.isv/.cvsignore b/bundles/org.eclipse.jdt.doc.isv/.cvsignore
deleted file mode 100644
index f29a4cb..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/.cvsignore
+++ /dev/null

@@ -1,2 +0,0 @@
-jdtOptions.tmp.txt
-jdtaptOptions.tmp.txt

diff --git a/bundles/org.eclipse.jdt.doc.isv/.project b/bundles/org.eclipse.jdt.doc.isv/.project
deleted file mode 100644
index 22a4808..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/.project
+++ /dev/null

@@ -1,11 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
-	<name>org.eclipse.jdt.doc.isv</name>
-	<comment></comment>
-	<projects>
-	</projects>
-	<buildSpec>
-	</buildSpec>
-	<natures>
-	</natures>
-</projectDescription>

diff --git a/bundles/org.eclipse.jdt.doc.isv/META-INF/MANIFEST.MF b/bundles/org.eclipse.jdt.doc.isv/META-INF/MANIFEST.MF
deleted file mode 100644
index 75a40c3..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/META-INF/MANIFEST.MF
+++ /dev/null

@@ -1,8 +0,0 @@
-Manifest-Version: 1.0
-Bundle-ManifestVersion: 2
-Bundle-Name: %pluginName
-Bundle-SymbolicName: org.eclipse.jdt.doc.isv; singleton:=true
-Bundle-Version: 3.2.0.qualifier
-Bundle-Vendor: %providerName
-Bundle-Localization: plugin
-Eclipse-LazyStart: true

diff --git a/bundles/org.eclipse.jdt.doc.isv/aaa-how-to-add-things.txt b/bundles/org.eclipse.jdt.doc.isv/aaa-how-to-add-things.txt
deleted file mode 100644
index d72d234..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/aaa-how-to-add-things.txt
+++ /dev/null

@@ -1,40 +0,0 @@
-Last revised January 30, 2006
-(This file is for information only; it is not included in the release.)
-
-ADDING NEW PLUGINS:
---------------------------
-
-To add new plug-ins you need to make changes in several places in
-this doc plug-in:
-
-1) jdtOptions.txt
-- the plug-in's source folder(s) must be included on the -sourcepath
-- code of required plug-ins must be added on the -classpath (the JAR(s)for non-JARed plug-ins and <plugin>/@dot for JARed plug-ins
-- the API package names must be included in the (alphabetical) package list at the end of the file
-
-2) buildDoc.xml
- - If a plug-in contributes extension points, it should be added to the list of
-   plug-ins in the <convertSchemaToHTML> task in the buildDoc.xml of the
-   corresponding documentation plug-in.
-
-3) plugin.xml
- -If your plugin has javadoc API, add a line to plugin.xml under the 
- org.eclipse.pde.core.javadoc extension to associate your plugin's javadoc with
- the reference section for this doc plugin.
- 
-ADDING NEW API PACKAGES:
----------------------------------
-
-1) topics_Reference.xml
-- add a line for each API package
-
-2) check whether overview-jdt.html is affected
-
-ADDING NEW EXTENSION POINTS:
---------------------------------------
-
-1) reference/extension-points/index.html
-- add a line for each extension point
-
-2) topics_Reference.xml
-- add a line for each extension point

diff --git a/bundles/org.eclipse.jdt.doc.isv/about.html b/bundles/org.eclipse.jdt.doc.isv/about.html
deleted file mode 100644
index 49d4470..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/about.html
+++ /dev/null

@@ -1,23 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
-<title>About</title>
-</head>
-<body lang="EN-US">
-<h2>About This Content</h2>
- 
-<p>February 24, 2005</p>	
-<h3>License</h3>
-
-<p>The Eclipse Foundation makes available all content in this plug-in (&quot;Content&quot;).  Unless otherwise indicated below, the Content is provided to you under the terms and conditions of the
-Eclipse Public License Version 1.0 (&quot;EPL&quot;).  A copy of the EPL is available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
-For purposes of the EPL, &quot;Program&quot; will mean the Content.</p>
-
-<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is being redistributed by another party (&quot;Redistributor&quot;) and different terms and conditions may
-apply to your use of any object code in the Content.  Check the Redistributor's license that was provided with the Content.  If no such license exists, contact the Redistributor.  Unless otherwise
-indicated below, the terms and conditions of the EPL still apply to any source code in the Content.</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.isv/about.ini b/bundles/org.eclipse.jdt.doc.isv/about.ini
deleted file mode 100644
index 4164f9a..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/about.ini
+++ /dev/null

@@ -1,24 +0,0 @@
-# about.ini
-# contains information about a feature
-# java.io.Properties file (ISO 8859-1 with "\" escapes)
-# "%key" are externalized strings defined in about.properties
-# This file does not need to be translated.
-
-# Property "aboutText" contains blurb for "About" dialog (translated)
-aboutText=%blurb
-
-# Property "windowImage" contains path to window icon (16x16)
-# needed for primary features only
-
-# Property "featureImage" contains path to feature image (32x32)
-featureImage=eclipse32.png
-
-# Property "aboutImage" contains path to product image (500x330 or 115x164)
-# needed for primary features only
-
-# Property "appName" contains name of the application (not translated)
-# needed for primary features only
-
-# Property "welcomePage" contains path to welcome page (special XML-based format)
-# optional
-

diff --git a/bundles/org.eclipse.jdt.doc.isv/about.mappings b/bundles/org.eclipse.jdt.doc.isv/about.mappings
deleted file mode 100644
index bddaab4..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/about.mappings
+++ /dev/null

@@ -1,6 +0,0 @@
-# about.mappings
-# contains fill-ins for about.properties
-# java.io.Properties file (ISO 8859-1 with "\" escapes)
-# This file does not need to be translated.
-
-0=@build@
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.isv/about.properties b/bundles/org.eclipse.jdt.doc.isv/about.properties
deleted file mode 100644
index 4271494..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/about.properties
+++ /dev/null

@@ -1,24 +0,0 @@
-###############################################################################
-# Copyright (c) 2000, 2005 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-# about.properties
-# contains externalized strings for about.ini
-# java.io.Properties file (ISO 8859-1 with "\" escapes)
-# fill-ins are supplied by about.mappings
-# This file should be translated.
-
-blurb=Eclipse Java Development Tooling Plug-in Developers Guide\n\
-\n\
-Version: {featureVersion}\n\
-Build id: {0}\n\
-\n\
-(c) Copyright IBM Corp. and others 2000, 2004.  All rights reserved.\n\
-Visit http://www.eclipse.org/jdt
-

diff --git a/bundles/org.eclipse.jdt.doc.isv/book.css b/bundles/org.eclipse.jdt.doc.isv/book.css
deleted file mode 100644
index 84d8880..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/book.css
+++ /dev/null

@@ -1 +0,0 @@
-@import "../PRODUCT_PLUGIN/book.css";

diff --git a/bundles/org.eclipse.jdt.doc.isv/build.properties b/bundles/org.eclipse.jdt.doc.isv/build.properties
deleted file mode 100644
index 88dc9e4..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/build.properties
+++ /dev/null

@@ -1,12 +0,0 @@
-###############################################################################
-# Copyright (c) 2000, 2005 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-# use provided build.xml
-custom=true

diff --git a/bundles/org.eclipse.jdt.doc.isv/build.xml b/bundles/org.eclipse.jdt.doc.isv/build.xml
deleted file mode 100644
index ce40684..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/build.xml
+++ /dev/null

@@ -1,80 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<project name="org.eclipse.jdt.doc.isv" default="build.jars" basedir=".">
-
-	<path id="path_bootclasspath">
-		<fileset dir="${java.home}/lib">
-			<include name="*.jar"/>
-		</fileset>
-	</path>
-	<property name="bootclasspath" refid="path_bootclasspath"/>
-
-	<target name="init">
-		<property name="plugin" value="org.eclipse.jdt.doc.isv"/>
-		<property name="version.suffix" value="3.2.0"/>
-		<property name="full.name" value="${plugin}_${version.suffix}"/>
-		<property name="temp.folder" value="${basedir}/temp.folder"/>
-		<property name="plugin.destination" value="${basedir}"/>
-		<property name="build.result.folder" value="${basedir}"/>
-	</target>
-
-	<target name="build.update.jar" depends="init">
-		<delete dir="${temp.folder}"/>
-		<mkdir dir="${temp.folder}"/>
-		<antcall target="build.jars"/>
-		<antcall target="gather.bin.parts">
-			<param name="destination.temp.folder" value="${temp.folder}/"/>
-		</antcall>
-		<zip zipfile="${plugin.destination}/${full.name}.jar" basedir="${temp.folder}/${full.name}" filesonly="false"/>
-		<delete dir="${temp.folder}"/>
-	</target>
-
-	<target name="gather.bin.parts" depends="init" if="destination.temp.folder">
-		<ant antfile="buildDoc.xml" />
-		<mkdir dir="${destination.temp.folder}/${full.name}"/>
-		<copy todir="${destination.temp.folder}/${full.name}">
-			<fileset dir="${basedir}" includes="concepts/, gettingStarted/, images/, reference/, tasks/,samples/,guide/,questions/,*.properties,*.xml,*.zip,*.html,*.htm,*.png,*.css,META-INF/,index/" excludes="build.properties,build.xml,buildDoc.xml"/>
-		</copy>
-		<eclipse.versionReplacer path="${destination.temp.folder}/${full.name}" version="${version.suffix}"/>
-	</target>
-
-	<target name="build.jars" depends="init">
-	</target>
-
-	<target name="gather.sources" depends="init" if="destination.temp.folder">
-	</target>
-
-	<target name="build.sources" depends="init">
-	</target>
-
-	<target name="gather.logs" depends="init" if="destination.temp.folder">
-	</target>
-
-	<target name="clean" depends="init">
-		<delete file="${plugin.destination}/${full.name}.jar"/>
-		<delete file="${plugin.destination}/${full.name}.zip"/>
-		<delete dir="${temp.folder}"/>
-	</target>
-
-	<target name="refresh" depends="init" if="eclipse.running">
-		<eclipse.refreshLocal resource="${plugin}" depth="infinite"/>
-	</target>
-
-	<target name="zip.plugin" depends="init">
-		<delete dir="${temp.folder}"/>
-		<mkdir dir="${temp.folder}"/>
-		<antcall target="build.jars"/>
-		<antcall target="build.sources"/>
-		<antcall target="gather.bin.parts">
-			<param name="destination.temp.folder" value="${temp.folder}/"/>
-		</antcall>
-		<antcall target="gather.sources">
-			<param name="destination.temp.folder" value="${temp.folder}/"/>
-		</antcall>
-		<delete>
-			<fileset dir="${temp.folder}" includes="**/*.bin.log"/>
-		</delete>
-		<zip zipfile="${plugin.destination}/${full.name}.zip" basedir="${temp.folder}" filesonly="true"/>
-		<delete dir="${temp.folder}"/>
-	</target>
-
-</project>
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.isv/buildDoc.xml b/bundles/org.eclipse.jdt.doc.isv/buildDoc.xml
deleted file mode 100644
index 280a2a2..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/buildDoc.xml
+++ /dev/null

@@ -1,131 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<project name="Jdt Doc Isv Build" default="all"  basedir="." >
-
-	<target name="init">
-		<available file="${basedir}/index" property="index.present"/>
-	</target>
-
-	<target name="all" depends="init" unless="index.present">
-		<antcall target="convertSchemaToHtml" />
-		<antcall target="examplesDocCopy" />
-		<antcall target="generateJavadoc" />
-		<antcall target="build.index" />
-		<!--antcall target="createDocZip" /-->
-	</target>
-
-
-	<target name="build.index" description="Builds search index for the plug-in: org.eclipse.jdt.doc.isv" if="eclipse.running">
-		<help.buildHelpIndex manifest="${basedir}/plugin.xml" destination="${basedir}"/>
-	</target>
-
-	<target name="convertSchemaToHtml" if="eclipse.running">
-		<property name="dest" value="reference/extension-points" />
-		<record name="${basedir}/jdtconvert.txt" action="start"/>
-
-		<pde.convertSchemaToHTML manifest="../org.eclipse.jdt.core/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.jdt.debug/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.jdt.debug.ui/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.jdt.junit/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.jdt.launching/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.jdt.ui/plugin.xml" destination="${dest}" />
-
-		<record name="${basedir}/jdtconvert.txt" action="stop"/>
-	</target>
-
-	<target name="examplesDocCopy" >
-		<copy todir="samples">
-			<fileset dir="..">
-				<include name="org.eclipse.jdt.ui.examples.projects/doc-html/"/>
-			</fileset>
-		</copy>
-	</target>
-
-
-	<target name="getJavadocPath">
-		<available file="${java.home}/../bin/javadoc.exe" property="javadoc" value="${java.home}/../bin/javadoc.exe"/>
-		<available file="${java.home}/../bin/javadoc" property="javadoc" value="${java.home}/../bin/javadoc" />
-	</target>
-
-
-	<target name="generateJavadoc" depends="getJavadocPath" if="javadoc">
-
-		<!--HACK to ensure the platform doc is built before JDT - call to this script should be moved to build.jars target-->
-		<available file="../org.eclipse.platform.doc.isv/index" property="platform.index.present"/>
-		<antcall target="buildPlatformDoc" />
-
-		<property name="optionsFile" value="jdtOptions.tmp.txt" />
-		<copy file="jdtOptions.txt" tofile="${optionsFile}" overwrite="true" />
-		
-		<condition property="argsListDelimiter" value=":">
-			<os family="unix" />
-		</condition>
-		<condition property="argsListDelimiter" value=";">
-			<os family="windows" />
-		</condition>
-
-		<replaceregexp file="${basedir}/${optionsFile}" flags="g" match="(\r\n?|\n);" replace="${argsListDelimiter}" />
-		<replace file="${basedir}/${optionsFile}" token="@rt@" value="${bootclasspath}" />
-		<replace file="${basedir}/${optionsFile}" token="@baseLocation@" value="${baseLocation}" />
-
-
-		<!--scrub isv plugin directories of any preexisting api doc content-->
-		<delete dir="reference/api"/>
-		<mkdir dir="reference/api"/>
-
-		<exec dir="." executable="${javadoc}" output="doc.bin.log">
-			<arg line="@${basedir}/${optionsFile} -J-Xmx500M" />
-		</exec>
-		<antcall target="generateJdtAptJavadoc" />
-	</target>
-	
-	<target name="generateJdtAptJavadoc">
-		<property name="javadoc15" value="${javadoc}" />
-		
-		<property name="jdtaptoptionsFile" value="jdtaptOptions.tmp.txt" />
-		<copy file="jdtaptOptions.txt" tofile="${jdtaptoptionsFile}" overwrite="true" />
-		
-		<condition property="argsListDelimiter" value=":">
-			<os family="unix" />
-		</condition>
-		<condition property="argsListDelimiter" value=";">
-			<os family="windows" />
-		</condition>
-
-		<replaceregexp file="${basedir}/${jdtaptoptionsFile}" flags="g" match="(\r\n?|\n);" replace="${argsListDelimiter}" />
-		<replace file="${basedir}/${jdtaptoptionsFile}" token="@rt@" value="${bootclasspath}" />
-
-		<!--scrub isv plugin directories of any preexisting api doc content-->
-		<delete dir="reference/apt" />
-		<mkdir dir="reference/apt" />
-
-		<exec dir="." executable="${javadoc15}" output="jdtapt.doc.bin.log">
-			<arg line="@${basedir}/${jdtaptoptionsFile} -J-Xmx500M" />
-		</exec>
-	</target>
-
-	<target name="buildPlatformDoc" unless="platform.index.present">
-		<ant antfile="buildDoc.xml" dir="../org.eclipse.platform.doc.isv" />
-	</target>
-
-	<target name="createDocZip">
-		<zip zipfile="${basedir}/doc.zip"
-		basedir="${basedir}"
-		includes="book.css, cpy.png, notices.html, about.html, no_help_exists.htm, concepts/**, gettingStarted/**, images/**, reference/**, tasks/**,samples/**,guide/**,questions/**"
-	/>
-	</target>
-
-</project>
-
-
-
-
-
-
-
-
-
-
-
-
-
-

diff --git a/bundles/org.eclipse.jdt.doc.isv/cpy.png b/bundles/org.eclipse.jdt.doc.isv/cpy.png
deleted file mode 100644
index a0f8775..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/cpy.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.isv/eclipse32.png b/bundles/org.eclipse.jdt.doc.isv/eclipse32.png
deleted file mode 100644
index 4983d64..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/eclipse32.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/images/annotation_processing.png b/bundles/org.eclipse.jdt.doc.isv/guide/images/annotation_processing.png
deleted file mode 100644
index dba9f3e..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/images/annotation_processing.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/images/compiler_dialog.png b/bundles/org.eclipse.jdt.doc.isv/guide/images/compiler_dialog.png
deleted file mode 100644
index 501bbd4..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/images/compiler_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/images/factory_path.png b/bundles/org.eclipse.jdt.doc.isv/guide/images/factory_path.png
deleted file mode 100644
index a97447f..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/images/factory_path.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/images/javanavigator.png b/bundles/org.eclipse.jdt.doc.isv/guide/images/javanavigator.png
deleted file mode 100644
index 3c52fac..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/images/javanavigator.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/images/openables.png b/bundles/org.eclipse.jdt.doc.isv/guide/images/openables.png
deleted file mode 100644
index d56dbdb..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/images/openables.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/images/sourceelements.png b/bundles/org.eclipse.jdt.doc.isv/guide/images/sourceelements.png
deleted file mode 100644
index 0a99274..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/images/sourceelements.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api.htm
deleted file mode 100644
index f32f286..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>JDT structure and API</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h1>JDT structure and API</h1>
-<p>Given that the JDT supplies a full featured Java IDE, why would you need to 
-  use the JDT API?</p>
-<p>If you are building a plug-in that interacts with Java programs or resources 
-  as part of its function, you may need to do one or more of the following things:</p>
-<ul>
-  <li> Programmatically manipulate Java resources, such as creating projects, 
-    generating Java source code, performing builds, or detecting problems in code.</li>
-  <li> Programmatically launch a Java program from the platform</li>
-  <li> Provide a new type of VM launcher to support a new family of Java runtimes</li>
-  <li> Add new functions and extensions to the Java IDE itself</li>
-</ul>
-<p>If you want to use JDT API in your plug-in, you must include the JDT plug-ins 
-  as prerequisites in your plug-in.xml.</p>
-<ul>
-  <li><b>org.eclipse.jdt.core</b> is the plug-in that defines the core Java elements 
-    and API. You should always list this plug-in as a prerequisite.</li>
-  <li><b>org.eclipse.jdt.ui</b> is the plug-in that defines the Java UI API. You 
-    should list this plug-in as a prerequisite if you are using the JDT UI classes.</li>
-  <li><b>org.eclipse.jdt.junit</b> is the plug-in that defines the JUnit integration API. You 
-    should list this plug-in as a prerequisite if you are using the JUnit integration classes.</li>
-  <li><b>org.eclipse.jdt.launching</b> is the plug-in that defines the Java launching 
-    and runtime support. You should list this plug-in as a prerequisite if you 
-    need to launch Java virtual machines programmatically.</li>
-  <li><b>org.eclipse.jdt.debug</b> is the plug-in that defines the Java debug 
-    model. You should list this plug-in as a prerequisite if you need to programmatically 
-    access objects in a program being debugged.</li>
-  <li><b>org.eclipse.jdt.debug.ui</b> is the plug-in that defines the Java debug 
-    UI extensions. You should list this plug-in as a prerequisite if you need 
-    to programmatically access the prompting source locator or Java launch configuration 
-    tabs.</li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_classpath.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_classpath.htm
deleted file mode 100644
index 6bd49ee..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_classpath.htm
+++ /dev/null

@@ -1,293 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>
-<HEAD>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Setting the Java build path</title>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY>
-<h2>
-Setting the Java build path</h2>
-<P>
-
-This section describes how to set the Java build path.&nbsp; The build path is
-the classpath that is used for building a Java project (<b><a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html">IJavaProject</a></b>).
-</p>
-<P>
-A classpath is simply an array of classpath entries (<b><a href="../reference/api/org/eclipse/jdt/core/IClasspathEntry.html">IClassPathEntry</a></b>)
-that describe the types that are available.&nbsp; The types can appear in source
-or binary form and the ordering of the entries on the path defines the lookup
-order for resolving types during a build.
-</p>
-
-<P>
-The Java build path is reflected in the structure of a Java project
-element.&nbsp; You can query a project for its package fragment roots (<b><a href="../reference/api/org/eclipse/jdt/core/IPackageFragmentRoot.html">IPackageFragmentRoot</a></b>).&nbsp;
-Each classpath entry maps to one or more package fragment roots, each of which
-further contains a set of package fragments.</p>
-<P>This discussion of the
-build path does not involve the Java runtime path, which can be defined
-separately from the build path.&nbsp; (See <b><a href="../guide/jdt_api_run.htm">Running
-Java code</a></b> for a discussion of the runtime classpath.</p>
-
-<h3>
-Changing the build path</h3>
-<P>
-You can programmatically change a project's build path using <b><a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html#setRawClasspath(org.eclipse.jdt.core.IClasspathEntry[], org.eclipse.core.runtime.IProgressMonitor)">
-setRawClasspath</a></b> on the corresponding project's Java element.&nbsp; The
-following code sets the classpath for a project resource:
-
-	<font color='#4444CC'><pre>
-	IProject project = ... // get some project resource
-	IJavaProject javaProject = JavaCore.create(project);
-	IClasspathEntry[] newClasspath = ...;
-	javaProject.setRawClasspath(newClasspath, someProgressMonitor);
-	</pre></font>
-</p>	
-<P>(Note:&nbsp; The use of the term &quot;raw&quot; classpath is used to
-emphasize the fact that any variables used to describe entry locations have not
-been resolved.)
-</p>
-<P>
-The Java build path is persisted into a file named '.classpath' in the project's
-file structure.&nbsp; The purpose of this file is to provide a way to share Java build path settings with others through 
-some source code repository. In particular, this file should not be manually edited, since it may get corrupted.
-</p> 
-<H3>
-Classpath entries</H3>
-<P>
-Classpath entries can be defined using factory methods defined on <b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html">JavaCore</a></b>.&nbsp;
-Classpath entries can reference any of the following:</p>
-
-<ul>
-<li><b>a source folder</b> - 
-a folder containing source compilation units organized under their corresponding package directory structure. Source folders are used to better structure 
-source files in large projects, and may only be referenced within the containing project.
-  The corresponding factory method is 
-<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#newSourceEntry(org.eclipse.core.runtime.IPath)">newSourceEntry</a></b>.
-Inside a given source folder, each compilation unit is expected to be nested in the appropriate folder structure according to its package
-  statement.&nbsp; For example, compilation unit 'X.java' in package 'p1' 
-must be located inside sub-folder 'p1' of a source folder.
-It is possible to use multiple source folders, as long as they don't overlap. A
-  source folder may be assigned its own output location which determines where
-  generated class files should be placed.&nbsp; If none is specified, then class
-  files will be placed in the containing project's output location
-  (see <b><a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html#setOutputLocation(org.eclipse.core.runtime.IPath, org.eclipse.core.runtime.IProgressMonitor)">IJavaProject.setOutputLocation</a></b>).<P>The
-  following is an example classpath entry that denotes the source folder 'src' of project
-  'MyProject':
-	<font color='#4444CC'><pre>   IClassPathEntry srcEntry = JavaCore.newSourceEntry(new Path(&quot;/MyProject/src&quot;));</pre></font></p>
-</li>
-<li><b>a binary library</b> - either a class file folder (contained inside the workspace) or a class file archive file (contained inside or outside the workspace).
-Archive libraries can have attached source archives, which are extracted when asking a class file element  for
-  its source (<b><a href="../reference/api/org/eclipse/jdt/core/ISourceReference.html#getSource()">getSource</a></b>).
-The factory method for libraries is 
-<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#newLibraryEntry(org.eclipse.core.runtime.IPath, org.eclipse.core.runtime.IPath, org.eclipse.core.runtime.IPath, boolean)">newLibraryEntry</a></b>.
-<P>
-The following is an example classpath entry that denotes the class file folder 'lib' of  'MyProject':
-	<font color='#4444CC'><pre>
-  IClassPathEntry libEntry = JavaCore.newLibraryEntry(
-    new Path(&quot;/MyProject/lib&quot;), 
-    null, //no source
-    null, //no source
-    false); //not exported
-	</pre></font>
-  The following classpath entry has a source attachment:
-	<font color='#4444CC'><pre>
-  IClassPathEntry libEntry = JavaCore.newLibraryEntry(
-    new Path(&quot;d:/lib/foo.jar&quot;), // library location
-    new Path(&quot;d:/lib/foo_src.zip&quot;), //source archive location
-    new Path(&quot;src&quot;), //source archive root path
-    true); //exported
-	</pre></font></p><p>The source archive root path describes the location of the
-  root within the source archive.&nbsp; If set to null, the root of the archive
-  will be inferred dynamically.</p>
-  <br></li>
-<li><b>a prerequisite project</b> - another Java project.&nbsp; A prerequisite project always contributes its source folders to dependent projects.
-It can also optionally contribute any of its classpath entries which are tagged as exported (see factory methods supporting
-  the extra boolean argument 'isExported').
-This means that in addition to contributing its source to its dependents, a project will also export all classpath entries tagged as
-  such.&nbsp; This allows prerequisite projects to better hide their own
-  structure changes.&nbsp; For example, a given project may choose to switch from using a source folder to exporting a library.&nbsp;
-  This can be done without requiring its dependent projects to change their classpath.
-The factory method for a project prerequisite is 
-<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#newProjectEntry(org.eclipse.core.runtime.IPath, boolean)">newProjectEntry</a></b>.
-<P>
-The following classpath entry denotes a prerequisite project 'MyFramework'.
-	<font color='#4444CC'><pre>
-  IClassPathEntry prjEntry = JavaCore.newProjectEntry(new Path(&quot;/MyFramework&quot;), true); //exported
-	</pre></font> </p>
-</li>
-<li><b>an indirect reference to a project or library, using some classpath variable</b> -
-  The location of projects or libraries can be dynamically resolved relative to a
-classpath variable, which is specified as the first segment of the entry path. The rest of the entry path is then appended to the resolved variable path.
-The factory method for a classpath variable is 
-<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#newVariableEntry(org.eclipse.core.runtime.IPath, org.eclipse.core.runtime.IPath, org.eclipse.core.runtime.IPath)">newVariableEntry</a></b>.
-Classpath variables are global to the workspace, and can be manipulated through JavaCore methods 
-<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#getClasspathVariable(java.lang.String)">getClasspathVariable</a></b> and
-<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#setClasspathVariable(java.lang.String, org.eclipse.core.runtime.IPath, org.eclipse.core.runtime.IProgressMonitor)">setClasspathVariable</a></b>.&nbsp;
-  <p>
-It is possible to register an automatic <b><a href="../reference/api/org/eclipse/jdt/core/ClasspathVariableInitializer.html">classpath variable initializer</a></b>
-which is invoked through the extension point <b><a href="../reference/extension-points/org_eclipse_jdt_core_classpathVariableInitializer.html">org.eclipse.jdt.core.classpathVariableInitializer</a></b> 
-when the workspace is started.</p>
-<P>
-The following classpath entry denotes a library whose location is kept in the
-variable 'HOME'.&nbsp; The source attachment is defined using the
-variables&nbsp; 'SRC_HOME' and 'SRC_ROOT' :
-	<font color='#4444CC'><pre>
-  IClassPathEntry varEntry = JavaCore.newVariableEntry(
-    new Path(&quot;HOME/foo.jar&quot;), // library location
-    new Path(&quot;SRC_HOME/foo_src.zip&quot;), //source archive location
-    new Path(&quot;SRC_ROOT&quot;), //source archive root path
-    true); //exported	
-  JavaCore.setClasspathVariable(&quot;HOME&quot;, new Path(&quot;d:/myInstall&quot;), null); // no progress
-	 </pre></font> </p>
-</li>
-<li><b>entry denoting a classpath container</b> - an indirect reference to a structured set of project or libraries.
-  Classpath containers are used to refer to a set of classpath entries that
-  describe a complex library structure.&nbsp; Like classpath variables,
-  classpath containers <b><a href="../reference/api/org/eclipse/jdt/core/IClasspathContainer.html">(IClasspathContainer)</a></b>
-are dynamically resolved.&nbsp; Classpath containers may be used by different
-  projects, causing their path entries to resolve to distinct values per
-  project.&nbsp; They also provide meta information about the library that they
-  represent (name, kind, description of library.)&nbsp; Classpath containers can be manipulated through JavaCore methods 
-<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#getClasspathContainer(org.eclipse.core.runtime.IPath, org.eclipse.jdt.core.IJavaProject)">getClasspathContainer</a></b> and
-<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#setClasspathContainer(org.eclipse.core.runtime.IPath, org.eclipse.jdt.core.IJavaProject[], org.eclipse.jdt.core.IClasspathContainer[], org.eclipse.core.runtime.IProgressMonitor)">setClasspathContainer</a></b>.&nbsp;
-  <p>
-It is possible to register an automatic <b><a href="../reference/api/org/eclipse/jdt/core/ClasspathContainerInitializer.html">classpath container initializer</a></b>
-which is lazily invoked through the extension point <b><a href="../reference/extension-points/org_eclipse_jdt_core_classpathContainerInitializer.html">org.eclipse.jdt.core.classpathContainerInitializer</a></b>
-when the container needs to be bound.</p>
-  <P>The following classpath entry denotes a system class library container:
-	<font color='#4444CC'><pre>
-  IClassPathEntry varEntry = JavaCore.newContainerEntry(
-    new Path(&quot;JDKLIB/default&quot;), // container 'JDKLIB' + hint 'default'
-    false); //not exported	
-	                             
-  JavaCore.setClasspathContainer(
-    new Path(&quot;JDKLIB/default&quot;), 
-    new IJavaProject[]{ myProject }, // value for 'myProject'
-    new IClasspathContainer[] {
-      new IClasspathContainer() {
-        public IClasspathEntry[] getClasspathEntries() {
-          return new IClasspathEntry[]{ 
-            JavaCore.newLibraryEntry(new Path(&quot;d:/rt.jar&quot;), null, null, false);
-          }; 
-        }
-        public String getDescription() { return &quot;Basic JDK library container&quot;; }
-        public int getKind() { return IClasspathContainer.K_SYSTEM; }
-        public IPath getPath() { return new Path(&quot;JDKLIB/basic&quot;); }
-      }			
-    }, 
-    null);	                             
-</pre></font></p>
-</li>
-</ul>
-
-<h3>
-Exclusion patterns</h3>
-
-<p>A classpath source entry may be assigned an exclusion pattern, which prevents
-certain resources in a source folder from being visible on the classpath.&nbsp;
-Using a pattern allows
-specified portions of the resource tree to be filtered out.&nbsp; Each exclusion
-pattern path is relative to the classpath entry and uses a pattern mechanism
-similar to Ant.&nbsp; Exclusion patterns can be used to specify nested source
-folders as long as the outer pattern excludes the inner pattern.</p>
-
-<p> See <b><a href="../reference/api/org/eclipse/jdt/core/IClasspathEntry.html#getExclusionPatterns()">getExclusionPatterns()</b></a> for
-more detail on exclusion patterns.</p>
-
-<p>
-The Java project API <b><a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html#isOnClasspath(IResource)">isOnClasspath</a>
-</b> checks both inclusion and exclusion patterns before determining
-whether a particular resource is on the classpath.</p>
-
-<P>
-Remarks:
-<ul>
-<li>
-Exclusion patterns have higher precedence than inclusion patterns; in other
-words, exclusion patterns can remove files for the ones that are to be included, not the
-other way around.
-</li>
-<li>
-A nested source folder excluded from build path can be set as an output location.
- The following is an example classpath entry that denotes the source folder 'src' of project
- 'MyProject' with an excluded nested source folder used as an output location:
-	<font color='#4444CC'><pre>
-  IPath sourceFolder = new Path(&quot;/MyProject/src&quot;);
-  IPath outputLocation = sourceFolder.append(&quot;bin&quot;);
-  IClassPathEntry srcEntry = JavaCore.newSourceEntry(
-    sourceFolder, // source folder location
-    new Path[] { outputLocation }, // excluded nested folder
-    outputLocation); // output location
-    </pre></font>
-</li>
-</ul>
-</p>
-<h3>
-Inclusion patterns</h3>
-
-<p>A classpath source entry may also be assigned an inclusion pattern, which explicitly
- defines resources to be visible on the classpath.&nbsp;
-When no inclusion patterns are specified, the source entry includes all relevant files
- in the resource tree rooted at this source entry's path.
-Specifying one or more inclusion patterns means that only the specified portions of
- the resource tree are to be included. Each path specified must be a relative path,
- and will be interpreted relative to this source entry's path. File patterns are
- case-sensitive. A file matched by one or more of these patterns is included in
- the corresponding package fragment root unless it is excluded by one or more of
- this entry's exclusion patterns.</p>
-
-<p> See <b><a href="../reference/api/org/eclipse/jdt/core/IClasspathEntry.html#getExclusionPatterns()">getExclusionPatterns()</b></a>
- for a discussion of the syntax and semantics of path patterns. The absence of any inclusion patterns
- is semantically equivalent to the explicit inclusion pattern <code>**</code>.</p>
-
-<p>
-The Java project API <b><a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html#isOnClasspath(IResource)">isOnClasspath</a>
-</b> checks both inclusion and exclusion patterns before determining
-whether a particular resource is on the classpath.</p>
-
-<p>
-Examples:
-<ul>
-<li>
-The inclusion pattern <code>src/**</code> by itself includes all files under a root
- folder named <code>src</code>.
-</li>
-<li>
-The inclusion patterns <code>src/**</code> and <code>tests/**</code>
- includes all files under the root folders named <code>src</code> and <code>tests</code>.
-</li>
-<li>
-The inclusion pattern <code>src/**</code> together with the exclusion pattern
- <code>src/**/Foo.java</code> includes all files under a root folder named
- <code>src</code> except for ones named <code>Foo.java</code>.
-</li>
-</ul>
-</p>
-
-<H2>
-Classpath resolution</H2>
-
-Since classpath variables and containers allow you to define dynamically bound
-classpath entries, the classpath API distinguishes between a raw and a resolved
-classpath.&nbsp;&nbsp; The raw classpath is the one originally
-set on the Java project using 
-<b><a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html#setRawClasspath(org.eclipse.jdt.core.IClasspathEntry[], org.eclipse.core.runtime.IProgressMonitor)">setRawClasspath</a></b>,
-and can be further queried by asking the project for
-<b><a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html#getRawClasspath()">getRawClasspath</a></b>.&nbsp;
-The resolved classpath can be queried using 
-<b><a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html#getResolvedClasspath(boolean)">getResolvedClasspath</a></b>. 
-This operation triggers initialization of any variables and containers necessary
-to resolve the classpath.&nbsp; Many Java Model operations
-implicitly cause the Java build path to be resolved.&nbsp; For example,
-computing a project's package fragment roots requires the build path to be
-resolved.
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_codeassist.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_codeassist.htm
deleted file mode 100644
index d93386c..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_codeassist.htm
+++ /dev/null

@@ -1,177 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>
-<HEAD>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Performing code assist on Java code</title>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY>
-<h2>Performing code assist on Java code</h2>
-<P>
-The JDT API allows other plug-ins to perform code assist or code select on some Java elements. 
-Elements that allow this manipulation should implement <b><a href="../reference/api/org/eclipse/jdt/core/ICodeAssist.html"> ICodeAssist</a></b>.</p>
-<P>
-There are two kinds of manipulation:
-<ul>
-<li>Code completion - compute the completion of a Java token.</li>
-<li>Code selection - answer the Java element indicated by the selected text of a
-  given offset and length.</li>
-</ul></p>
-<p>
-In the Java model there are two elements that implement this interface: <b><a href="../reference/api/org/eclipse/jdt/core/IClassFile.html"> IClassFile</a></b> and <b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html"> ICompilationUnit</a></b>.&nbsp;
-Code completion and code selection only answer results for a class file if it has attached source.</p>
-<H3>
-Code completion</h3>
-
-<H4>
-Performing a code completion
-</h4>
-<P>
-The only way to programmatically perform code completion is to invoke <b><a href="../reference/api/org/eclipse/jdt/core/ICodeAssist.html#codeComplete(int, org.eclipse.jdt.core.ICompletionRequestor)">ICodeAssist.codeComplete</a></b>.
-You specify the offset in the compilation unit after which the code completion
-is desired.&nbsp; You must also supply an instance of <b><a href="../reference/api/org/eclipse/jdt/core/ICompletionRequestor.html"> ICompletionRequestor</a></b> to accept the possible completions.</P>
-
-<P>Each method in <b><a href="../reference/api/org/eclipse/jdt/core/ICompletionRequestor.html"> ICompletionRequestor</a>
-</b>accepts a different kind of proposal for code completion.&nbsp; The
-parameters of each method include text that describes the proposed element (its
-name, declaring type, etc.), its proposed position for insertion in the
-compilation unit, and its relevance.&nbsp;&nbsp;</P>
-
-<P>A completion requester can accept many different types
-of completions including the insertion of the following elements:</P>
-
-<ul>
-  <li>anonymous types</li>
-  <li>classes</li>
-  <li>fields</li>
-  <li>interfaces</li>
-  <li>keywords</li>
-  <li>labels</li>
-  <li>local variables</li>
-  <li>method call</li>
-  <li>method declaration</li>
-  <li>modifier</li>
-  <li>package import or reference</li>
-  <li>type</li>
-  <li>variable name</li>
-</ul>
-<p>The completion requester must also be able to accept compilation
-errors.&nbsp;&nbsp;</p>
-<p>If your plug-in is not interested in every kind of code completion, a <b><a href="../reference/api/org/eclipse/jdt/core/CompletionRequestorAdapter.html">CompletionRequestorAdapter</a></b>
-can be used so that you need only implement the kinds of completions you are
-interested in.&nbsp; The following example shows an adapter that is only used to
-accept class completions.</p>
-<font color='#4444CC'><pre>
-   // Get the compilation unit
-   ICompilationUnit unit = ...;
-   
-   // Get the offset
-   int offset = ...;
-   
-   // Create the requester
-   ICompletionRequestor requestor = new CompletionRequestorAdapter() {
-      public void acceptClass(
-         char[] packageName,
-         char[] className,
-         char[] completionName,
-         int modifiers,
-         int completionStart,
-         int completionEnd,
-         int relevance) {
-         System.out.println(&quot;propose a class named &quot; + new String(className));
-      }
-   };
-   
-   // Compute proposals
-   unit.codeComplete(offset, requestor);</font>
-</pre><h4>Completion relevance
-</h4>
-
-<p>Because there may be many different possible completions, the notion of
-relevance is used to compare the relevance of a suggested completion to other
-proposals.&nbsp; Relevance is represented by a positive integer.&nbsp; The value
-has no implicit meaning except to be used relative to the value for other
-proposals.&nbsp; The relevance of a code completion candidate can be affected by
-the expected type of the expression, as it relates to the types in the
-surrounding code, such as variable types, cast types, return types, etc.&nbsp;
-The presence of an expected prefix or suffix in a completion also affects its
-relevance.
-</p>
-
-<H4>
-Code completion options
-</h4>
-
-<P>
-The JDT Core plug-in defines options that control the behavior of code
-completion.&nbsp; These options can be changed by other plug-ins.&nbsp;&nbsp;</P>
-<ul>
-<li>Activate Visibility Sensitive Completion<br>
-  When this option is active, code completion will not answer elements that are
-  not visible in the current context.&nbsp; (For example, it will not answer
-  private methods of a super class.)</li>
-<li>Automatic Qualification of Implicit Members<br>
-  When this option is active, completion automatically qualifies completion on implicit field references and message expressions.</li>
-</ul>
-
-<p>Additional options allow you to specify prefixes and suffixes for the
-proposed completion names for fields, static fields, local variables, and method
-arguments.&nbsp;&nbsp;</p>
-
-<p> See&nbsp;<a href="jdt_api_options.htm##codeassist"> JDT Core Code Assist
-Options</a>
-for more information about the code assist options and their defaults.</p>
-
-<H3>
-Code selection</h3>
-
-<H4>
-Performing a code selection
-</h4>
-<P>Code selection is used to find the Java element represented by a range of
-text (typically the selected text) in a compilation unit.&nbsp; To programmatically perform code selection,
-you must invoke <b><a href="../reference/api/org/eclipse/jdt/core/ICodeAssist.html#codeSelect(int, int)">ICodeAssist.codeSelect</a></b>.
-You must supply the starting index location of the selection and its
-length. The result is an array of Java elements. Most of the time there is only one element in the array, but if the selection is ambiguous then all the possible elements are returned.</p><P>In
-the following example, code select is invoked for a compilation unit.
-
-<font color='#4444CC'><pre>   // Get the compilation unit
-   ICompilationUnit unit = ...;
-   
-   // Get the offset and length
-   int offset = ...;
-   int length = ...;
-   
-   // perform selection
-   IJavaElement[] elements = unit.codeSelect(offset, length);
-   System.out.println(&quot;the selected element is &quot; + element[0].getElementName());
-</pre></font></p>
-
-<H4>
-Selection at cursor location
-</h4>
-<P>
-When the selection length is specified as 0, a selection will be computed by
-finding the complete token that encloses the specified offset.&nbsp; Consider
-the following example method:</P>
-
-<P>
-
-<code>&nbsp;&nbsp; public void fooMethod(Object) {<br>
-&nbsp;&nbsp; }<br>
-</P>
-
-</code>
-If you specify an offset after the first character of <i>fooMethod</i>, and you
-specify a length of 0,&nbsp; then the selection will be computed to include the
-entire token <i>fooMethod</i>. If instead, you specify a length of 5, the
-selection will considered as <i>ooMet</i>.
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_compile.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_compile.htm
deleted file mode 100644
index bb96e8e..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_compile.htm
+++ /dev/null

@@ -1,698 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-     
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-     
-  <meta http-equiv="Content-Style-Type" content="text/css">
-      
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-  <title>Compiling Java code</title>
-          
-  <link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2> Compiling Java code</h2>
-<p> The JDT plug-ins include an incremental and batch Java compiler for building 
-Java .class files from source code. There is no direct API provided by the 
-compiler. It is installed as a builder on Java projects. Compilation is triggered 
-using standard platform build mechanisms.</p>
-<p> The platform build mechanism is described in detail in <a href="../../org.eclipse.platform.doc.isv/guide/resAdv_builders.htm" class="XRef">
- Incremental project builders</a> .</p>
-<h3> Compiling code</h3>
-<p> You can programmatically compile the Java source files in a project using 
-the build API.</p>
-<font color="#4444cc"><pre>
-   IProject myProject;
-   IProgressMonitor myProgressMonitor;
-   myProject.build(IncrementalProjectBuilder.INCREMENTAL_BUILD, myProgressMonitor);
-</pre></font>
-<p> For a Java project, this invokes the Java incremental project builder
- (along with any other incremental project builders that have been added
-to  the project's build spec). The generated .class files are written to
-the designated output folder. Additional resource files are also copied to the output folder.&nbsp;</p>
-<p> In the case of a full batch build, all the
-.class files in the output folder may be 'scrubbed' to ensure that no stale
-files are found. This is controlled using a JDT Core Builder Option (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_JAVA_BUILD_CLEAN_OUTPUT_FOLDER">CORE_JAVA_BUILD_CLEAN_OUTPUT_FOLDER</a>).&nbsp;
-The default for this option is to clean output folders.&nbsp; Unless this option
-is reset, you must ensure that you place all .class files for which
-you do not have corresponding source files in a separate class file folder
-on the classpath  instead of the output folder.</p>
-<p>The
-incremental and batch builders can be configured with other options that
-control which resources are copied to the output folder.&nbsp; The following sample shows how to set up a resource filter so that files ending with '.ignore' and folders named 'META-INF',
-are not copied to the output folder:
-<font color="#4444cc">
-<pre>   Hashtable options = JavaCore.getOptions();
-   options.put(JavaCore.CORE_JAVA_BUILD_RESOURCE_COPY_FILTER, &quot;*.ignore,META-INF/&quot;);
-   JavaCore.setOptions(options);
-</pre>
-</font></p>
-<p> Filenames are filtered if they match one of the supplied patterns. Entire 
-folders are filtered if their name matches one of the supplied folder names 
-which end in a path separator.</p>
-<p> The incremental and batch builders can also be configured to only generate
- a single error when the .classpath file has errors. This option is set by
- default and eliminates numerous errors.&nbsp; See <a href="jdt_api_options.htm#builder">JDT
-Core Builder Options</a> for a complete list of builder-related options and
-their defaults. </p>
-<p>The compiler can also be configured using <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html"><b>JavaCore</b></a>
-options.&nbsp; For example, you can define the severity that should be used for
-different kinds of problems that are found during compilation.&nbsp; See <a href="jdt_api_options.htm#compiler">JDT
-Core Compiler Options </a>for a complete list of compiler-related options and their defaults. </p>
-<p>When programmatically configuring options for the builder or compiler, you
-should determine the scope of the option.&nbsp; For example, setting up a
-resource filter may only apply to a particular project.&nbsp; The following example sets up
-the same resource filter shown earlier, but sets it only the individual
-project. </p>
-<font color="#4444cc">
-<pre>   
-   Hashtable options = myProject.getOptions(false);  // get only the options set up in this project
-   options.put(JavaCore.CORE_JAVA_BUILD_RESOURCE_COPY_FILTER, &quot;*.ignore,META-INF/&quot;);
-   myProject.setOptions(options);
-</pre>
-</font>
-<h3>Using the batch compiler</h3>
-
-<h4>Finding the batch compiler</h4>
-
-<p>The batch compiler class is located in the internal classes of the
-JDT/Core plug-in. So it is in the <i>jdtcore.jar</i> file in the directory
-<i>plugins/org.eclipse.jdt.core</i>.
-The name of the class is <i>org.eclipse.jdt.internal.compiler.batch.Main</i>.
-</p>
-<h4>Running the batch compiler</h4>
-<ul>
-<li>Using the main method.</li>
-Using the main method. The Main class has a main method. This
-is the classical way to invoke the batch compiler on a command-line.
-<ul>
-<li>
-For example on a command-line:
-<p><code><font color="#3366FF">java -classpath org.eclipse.jdt.core_3.1.0.jar org.eclipse.jdt.internal.compiler.batch.Main
--classpath rt.jar A.java</font></code></p>
-<p>or:</p>
-<p><code><font color="#3366FF">java -jar org.eclipse.jdt.core_3.1.0.jar -classpath rt.jar A.java</font></code></p>
-</li>
-<li>For example in a java source:
-<p><code><font color="#3366FF">org.eclipse.jdt.internal.compiler.batch.Main.main(new
-String[] {"-classpath", "rt.jar", "A.java"});</font></code></p>
-</li></ul>
-<li>
-Using the static compile(String) method.
-<p>The <code>compile(String)</code> method is a convenient method to invoke
-the batch compiler in a java application. Instead of 
-<code><font color="#3366FF">org.eclipse.jdt.internal.compiler.batch.Main.main(new
-String[] {"-classpath", "rt.jar", "A.java"});</font></code>
-you can simply write <code><font color="#3366FF">org.eclipse.jdt.internal.compiler.batch.Main.compile("-classpath
-rt.jar A.java");</font></code></p></li>
-</ul>
-
-<h4>Which options are available?</h4>
-<p>
-With the orange background, these are suggested options.
-</p>
-<table BORDER CELLSPACING=2 CELLPADDING=2 COLS=2>
-<tr>
-<th>Name</th>
-<th>Usage</th>
-</tr>
-<tr>
-<th colspan="2">Classpath options</th>
-</tr>
-<tr>
-<td valign=top bgcolor="#FFCCAA" width="250">-bootclasspath &lt;dir&nbsp;1&gt;;&lt;dir&nbsp;2&gt;;...;&lt;dir&nbsp;P&gt;</td>
-<td valign=top bgcolor="#FFCCAA">This is a list of directory or jar files used to bootstrap the class files used by the compiler. By default the libraries of the running
-VM are used. Entries are separated by the platform path separator.
-<br>Each directory or file can specify access rules for types between '[' and ']'.
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#FFCCAA" width="250">-cp<br>-classpath &lt;dir&nbsp;1&gt;;&lt;dir&nbsp;2&gt;;...;&lt;dir&nbsp;P&gt;</td>
-<td valign=top bgcolor="#FFCCAA">This is a list of directory or jar files used to compile the source files. The default value is the value of the property "java.class.path".
- Entries are separated by the platform path separator.
-<br>Each directory or file can specify access rules for types between '[' and ']' (e.g. [-X] to forbid access to type X, [~X] to 
-discourage access to type X, [+p/X:-p/*] to forbid access to all types in package p but allow access to p/X).
-</td>
-</tr>
-<tr>
-<td valign=top width="250">-extdirs &lt;dir&nbsp;1&gt;;&lt;dir&nbsp;2&gt;;...;&lt;dir&nbsp;P&gt;</td>
-<td valign=top>This is a list of directory used to specify the location of extension zip/jar files. Entries are separated by the platform path separator.</td>
-</tr>
-<tr>
-<td valign=top width="250">-sourcepath &lt;dir&nbsp;1&gt;;&lt;dir&nbsp;2&gt;;...;&lt;dir&nbsp;P&gt;</td>
-<td valign=top>This is a list of directory used to specify the source files. Entries are separated by the platform path separator.
-<br>Each directory can specify access rules for types between '[' and ']'.</td>
-</tr>
-<tr>
-<td valign=top bgcolor="#FFCCAA" width="250">-d &lt;dir 1&gt;|none</td>
-<td bgcolor="#FFCCAA">This is used to specify in which directory the generated .class files should be dumped. If it is omitted, no package directory structure is created.<br>
-If you don't want to generate .class files, use <font color="#3366FF">-d none</font>.</td>
-</tr>
-<tr>
-<td valign=top width="250">-encoding &lt;encoding name&gt;</td>
-<td>Specify default source encoding format (custom encoding can also be specified on a per file basis by suffixing each input source file/folder name with <font color="#3366FF">[encoding &lt;encoding name&gt;]</font>).</td>
-</tr>
-<tr>
-<th colspan="2">Compliance options</th>
-</tr>
-<tr>
-<td valign=top width="250">-target 1.1|1.2|1.3|1.4|1.5|5|5.0|1.6|6|6.0</td>
-<td>This specifies the .class file target setting.
-The possible value are:
-<ul>
-<li><font color="#3366FF">1.1</font> (major version: 45 minor: 3)</li>
-<li><font color="#3366FF">1.2</font> (major version: 46 minor: 0)</li>
-<li><font color="#3366FF">1.3</font> (major version: 47 minor: 0)</li>
-<li><font color="#3366FF">1.4</font> (major version: 48 minor: 0)</li>
-<li><font color="#3366FF">1.5</font>, <font color="#3366FF">5</font> or <font color="#3366FF">5.0</font> (major version: 49 minor: 0)</li>
-<li><font color="#3366FF">1.6</font>, <font color="#3366FF">6</font> or <font color="#3366FF">6.0</font> (major version: 50 minor: 0)</li>
-</ul>
-Defaults are:
-<ul>
-<li><font color="#3366FF">1.1</font> in <font color="#3366FF">-1.3</font> mode</li>
-<li><font color="#3366FF">1.2</font> in <font color="#3366FF">-1.4</font> mode</li>
-<li><font color="#3366FF">1.5</font> in <font color="#3366FF">-1.5</font> mode</li>
-<li><font color="#3366FF">1.6</font> in <font color="#3366FF">-1.6</font> mode</li>
-</ul>
-</td>
-</tr>
-<tr>
-<td valign=top>-1.3</td>
-<td>Set compliance level to <font color="#3366FF">1.3</font>. Implicit -source 1.3 -target 1.1.</td>
-</tr>
-<tr>
-<td valign=top>-1.4</td>
-<td>Set compliance level to <font color="#3366FF">1.4</font> (default). Implicit -source 1.3 -target 1.2.</td>
-</tr>
-<tr>
-<td valign=top>-1.5</td>
-<td>Set compliance level to <font color="#3366FF">1.5</font>. Implicit -source 1.5 -target 1.5.</td>
-</tr>
-<tr>
-<td valign=top>-1.6</td>
-<td>Set compliance level to <font color="#3366FF">1.6</font>. Implicit -source 1.6 -target 1.6.</td>
-</tr>
-<tr>
-<td valign=top width="250">-source 1.3|1.4|1.5|5|5.0|1.6|6|6.0</td>
-<td>This is used to enable the source level of the compiler.<br>
-The possible value are:
-<ul>
-<li><font color="#3366FF">1.3</font></li>
-<li><font color="#3366FF">1.4</font></li>
-<li><font color="#3366FF">1.5</font>, <font color="#3366FF">5</font> or <font color="#3366FF">5.0</font></li>
-<li><font color="#3366FF">1.6</font>, <font color="#3366FF">6</font> or <font color="#3366FF">6.0</font></li>
-</ul>
-Defaults are:
-<ul>
-<li><font color="#3366FF">1.3</font> in <font color="#3366FF">-1.3</font> mode</li>
-<li><font color="#3366FF">1.3</font> in <font color="#3366FF">-1.4</font> mode</li>
-<li><font color="#3366FF">1.5</font> in <font color="#3366FF">-1.5</font> mode</li>
-<li><font color="#3366FF">1.6</font> in <font color="#3366FF">-1.6</font> mode</li>
-</ul>
-In <font color="#3366FF">1.4</font>, <font color="#3366FF"><I>assert</I></font> is treated as a keyword. In <font color="#3366FF">1.5</font>, <font color="#3366FF"><I>enum</I></font> and <font color="#3366FF"><i>assert</i></font> are treated as a keyword.</td>
-</tr>
-<tr>
-<th colspan="2">Warning options</th>
-</tr>
-<tr>
-<td valign=top width="250">-warn:<blockquote>allDeprecation<br>allJavadoc<br><font color="#FF0000">assertIdentifier</font><br>boxing<br><font color="#FF0000">charConcat</font><br>conditionAssign<br><font color="#FF0000">constructorName</font>
-<br>dep-ann<br><font color="#FF0000">deprecation</font><br><font color="#FF0000">discouraged</font><br>emptyBlock<br>enumSwitch<br>fieldHiding<br>finalBound<br><font color="#FF0000">finally</font>
-<br><font color="#FF0000">forbidden</font><br>hiding<br>incomplete-switch<br>indirectStatic
-<br><font color="#FF0000">intfAnnotation</font><br><font color="#FF0000">intfNonInherited</font><br>javadoc<br>localHiding
-<br><font color="#FF0000">maskedCatchBlocks</font><br>nls<br><font color="#FF0000">noEffectAssign</font><br>null<br>over-ann<br><font color="#FF0000">pkgDefaultMethod</font><br>semicolon<br><font color="#FF0000">serial</font><br>
-specialParamHiding<br>static-access<br><font color="#FF0000">staticReceiver</font><br><font color="#FF0000">suppress</font><br>synthetic-access<br>syntheticAccess<br>tasks(&lt;task1&gt;|...|&lt;taskN&gt;)<br>
-<font color="#FF0000">typeHiding</font><br><font color="#FF0000">unchecked</font><br>unnecessaryElse<br>unqualified-field-access<br>unqualifiedField<br>uselessTypeCheck
-<br>unused<br>unusedArgument<br><font color="#FF0000">unusedImport</font><br><font color="#FF0000">unusedLocal</font><br><font color="#FF0000">unusedPrivate</font><br>unusedThrown
-<br><font color="#FF0000">varargsCast</font><br><font color="#FF0000">warningToken</font>
-</blockquote>
-</td>
-<td valign=top>Set warning level.<br>e.g. <font color="#3366FF">-warn:unusedLocals,deprecation</font><br>
-<p>In <font color="#FF0000">red</font> are the default settings.</p>
-<p>
-<pre>
-    -warn:&lt;warnings separated by ,&gt;    enable exactly the listed warnings
-    -warn:+&lt;warnings separated by ,&gt;   enable additional warnings
-    -warn:-&lt;warnings separated by ,&gt;   disable specific warnings
-</pre>
-<table>
-<tr>
-<th align=left valign=top>allDeprecation</th>
-<td valign=top>deprecation even inside deprecated code</td>
-</tr>
-<tr>
-<th align=left valign=top>allJavadoc</th>
-<td valign=top>invalid or missing javadoc</td>
-</tr>
-<tr>
-<th align=left valign=top>assertIdentifier</th>
-<td valign=top>occurrence of <i>assert</i> used as identifier</td>
-</tr>
-<tr>
-<th align=left valign=top>boxing</th>
-<td valign=top>autoboxing conversion</td>
-</tr>
-<tr>
-<th align=left valign=top>charConcat</th>
-<td valign=top>when a char array is used in a string concatenation without being converted explicitly to 
-a string</td>
-</tr>
-<tr>
-<th align=left valign=top>conditionAssign</th>
-<td valign=top>possible accidental boolean assignment</td>
-</tr>
-<tr>
-<th align=left valign=top>constructorName</th>
-<td valign=top>method with constructor name</td>
-</tr>
-<tr>
-<th align=left valign=top>dep-ann</th>
-<td valign=top>missing @Deprecated annotation</td>
-</tr>
-<tr>
-<th align=left valign=top>deprecation</th>
-<td valign=top>usage of deprecated type or member outside deprecated code</td>
-</tr>
-<tr>
-<th align=left valign=top>discouraged</th>
-<td valign=top>use of types matching a discouraged access rule</td>
-</tr>
-<tr>
-<th align=left valign=top>emptyBlock</th>
-<td valign=top>undocumented empty block</td>
-</tr>
-<tr>
-<th align=left valign=top>enumSwitch,<br>incomplete-switch</th>
-<td valign=top>incomplete enum switch</td>
-</tr>
-<tr>
-<th align=left valign=top>fieldHiding</th>
-<td valign=top>field hiding another variable</td>
-</tr>
-<tr>
-<th align=left valign=top>finalBound</th>
-<td valign=top>type parameter with final bound</td>
-</tr>
-<tr>
-<th align=left valign=top>finally</th>
-<td valign=top>finally block not completing normally</td>
-</tr>
-<tr>
-<th align=left valign=top>forbidden</th>
-<td valign=top>use of types matching a forbidden access rule</td>
-</tr>
-<tr>
-<th align=left valign=top>hiding</th>
-<td valign=top>macro for fieldHiding, localHiding, typeHiding and maskedCatchBlock</td>
-</tr>
-<tr>
-<th align=left valign=top>indirectStatic</th>
-<td valign=top>indirect reference to static member</td>
-</tr>
-<tr>
-<th align=left valign=top>intfAnnotation</th>
-<td valign=top>annotation type used as super interface</td>
-</tr>
-<tr>
-<th align=left valign=top>intfNonInherited</th>
-<td valign=top>interface non-inherited method compatibility</td>
-</tr>
-<tr>
-<th align=left valign=top>javadoc</th>
-<td valign=top>invalid javadoc</td>
-</tr>
-<tr>
-<th align=left valign=top>localHiding</th>
-<td valign=top>local variable hiding another variable</td>
-</tr>
-<tr>
-<th align=left valign=top>maskedCatchBlocks</th>
-<td valign=top>hidden catch block</td>
-</tr>
-<tr>
-<th align=left valign=top>nls</th>
-<td>non-nls string literals (lacking of tags //$NON-NLS-&lt;n&gt;)</td>
-</tr>
-<tr>
-<th align=left valign=top>noEffectAssign</th>
-<td valign=top>for assignment with no effect</td>
-</tr>
-<tr>
-<th align=left valign=top>null</th>
-<td>missing or redundant null check</td>
-</tr>
-<tr>
-<th align=left valign=top>over-ann</th>
-<td>missing @Override annotation</td>
-</tr>
-<tr>
-<th align=left valign=top>pkgDefaultMethod</th>
-<td valign=top>attempt to override package-default method</td>
-</tr>
-<tr>
-<th align=left valign=top>serial</th>
-<td valign=top>missing serialVersionUID</td>
-</tr>
-<tr>
-<th align=left valign=top>semicolon</th>
-<td valign=top>unnecessary semicolon or empty statement</td>
-</tr>
-<tr>
-<th align=left valign=top>specialParamHiding</th>
-<td valign=top>constructor or setter parameter hiding another field</td>
-</tr>
-<tr>
-<th align=left valign=top>static-access</th>
-<td valign=top>macro for indirectStatic and staticReceiver</td>
-</tr>
-<tr>
-<th align=left valign=top>staticReceiver</th>
-<td valign=top>if a non static receiver is used to get a static field or call a static method</td>
-</tr>
-<tr>
-<th align=left valign=top>suppress</th>
-<td valign=top>enable @SuppressWarnings</td>
-</tr>
-<tr>
-<th align=left valign=top>syntheticAccess,<br>synthetic-access</th>
-<td valign=top>when performing synthetic access for innerclass</td>
-</tr>
-<tr>
-<th align=left valign=top>tasks</th>
-<td valign=top>enable support for tasks tags in source code</td>
-</tr>
-<tr>
-<th align=left valign=top>typeHiding</th>
-<td valign=top>type parameter hiding another type</td>
-</tr>
-<tr>
-<th align=left valign=top>unchecked</th>
-<td valign=top>unchecked type operation</td>
-</tr>
-<tr>
-<th align=left valign=top>unnecessaryElse</th>
-<td valign=top>unnecessary else clause</td>
-</tr>
-<tr>
-<th align=left valign=top>unqualified-field-access,<br>unqualifiedField</th>
-<td valign=top>unqualified reference to field</td>
-</tr>
-<tr>
-<th align=left valign=top>unused</th>
-<td valign=top>macro for unusedArgument, unusedImport, unusedLocal, unusedPrivate and unusedThrown</td>
-</tr>
-<tr>
-<th align=left valign=top>unusedArgument</th>
-<td valign=top>unused method argument</td>
-</tr>
-<tr>
-<th align=left valign=top>unusedImport</th>
-<td valign=top>unused import reference</td>
-</tr>
-<tr>
-<th align=left valign=top>unusedLocal</th>
-<td valign=top>unused local variable</td>
-</tr>
-<tr>
-<th align=left valign=top>unusedPrivate</th>
-<td valign=top>unused private member declaration</td>
-</tr>
-<tr>
-<th align=left valign=top>unusedThrown</th>
-<td valign=top>unused declared thrown exception</td>
-</tr>
-<tr>
-<th align=left valign=top>uselessTypeCheck</th>
-<td valign=top>unnecessary cast/instanceof operation</td>
-</tr>
-<tr>
-<th align=left valign=top>varargsCast</th>
-<td valign=top>varargs argument need explicit cast</td>
-</tr>
-<tr>
-<th align=left valign=top>warningToken</th>
-<td valign=top>unhandled warning token in @SuppressWarnings</td>
-</tr>
-</table>
-</p>
-</td>
-</tr>
-<tr>
-<td valign=top>-nowarn</td>
-<td>No warning (equivalent to <font color="#3366FF">-warn:none</font>)</td>
-</tr>
-<tr>
-<td valign=top>-deprecation</td>
-<td>Equivalent to <font color="#3366FF">-warn:deprecation</font>.</td>
-</tr>
-<tr>
-<th colspan="2">Debug options</th>
-</tr>
-<tr>
-<td valign=top>-g[:none|:lines,vars,source]
-</td>
-<td>Set the debug attributes level<br>
-<table>
-<tr>
-<th align=left>-g</th>
-<td>All debug info (equivalent to <font color="#3366FF">-g:lines,vars,source</font>)
-</td>
-</tr>
-<tr>
-<th align=left>-g:none</th>
-<td>No debug info</td>
-</tr>
-<tr>
-<th align=left>-g:[lines,vars,source]</th>
-<td>Selective debug info</td>
-</tr>
-</table>
-</td>
-</tr>
-<tr>
-<td valign=top>-preserveAllLocals</td>
-<td>Explicitly request the compiler to preserve all local variables (for debug purpose). If omitted, the compiler will removed unused locals.</td>
-</tr>
-<tr>
-<th colspan="2">Advanced options</th>
-</tr>
-<tr>
-<td>@&lt;file&gt;</td>
-<td valign=top>Read command-line arguments from file</td>
-</tr>
-<tr>
-<td>-maxProblems&nbsp;&lt;n&gt;</td>
-<td valign=top>Max number of problems per compilation unit (100 by default)</td>
-</tr>
-<tr>
-<td valign=top>-log &lt;filename&gt;</td>
-<td>Specify a log file in which all output from the compiler will be dumped. This is really useful if you want to debug the batch
-compiler or get a file which contains all errors and warnings from a batch build. If the extension is <b>.xml</b>, the generated log
-will be a xml file.
-</td>
-</tr>
-<tr>
-<td valign=top>-proceedOnError</td>
-<td>Keep compiling when error, dumping class files with problem methods or problem types. This is recommended only if you want
-to be able to run your application even if you have remaining errors.</td>
-</tr>
-<tr>
-<td valign=top>-verbose</td>
-<td>Print accessed/processed compilation units in the console or the log file if specified.</td>
-</tr>
-<tr>
-<td valign=top>-referenceInfo</td>
-<td>Compute reference info. This is useful only if connected to the builder. The reference infos are useless otherwise.</td>
-</tr>
-<tr>
-<td valign=top>-progress</td>
-<td>Show progress (only in -log mode)</td>
-</tr>
-<tr>
-<td valign=top>-time
-</td>
-<td>Display speed information</td>
-</tr>
-<tr>
-<td valign=top>-noExit</td>
-<td>Do not call <font color="#3366FF">System.exit(n)</font> at end of compilation (<font color="#3366FF">n=0</font> if no error)</td>
-</tr>
-<tr>
-<td valign=top>-repeat &lt;n&gt;
-</td>
-<td>Repeat compilation process <font color="#3366FF">&lt;n&gt;</font> times (perf analysis).</td>
-</tr>
-<tr>
-<td valign=top>-inlineJSR</td>
-<td>Inline JSR bytecode (implicit if target >= 1.5)</td>
-</tr>
-<tr>
-<td valign=top>-enableJavadoc</td>
-<td>Consider references inside javadoc</td>
-</tr>
-<tr>
-<th colspan="2">Helping options</th>
-</tr>
-<tr>
-<td>-? -help</td>
-<td valign=top>Display the help message</td>
-</tr>
-<tr>
-<td valign=top>-v -version</td>
-<td>Display the build number of the compiler. This is very useful to report a bug.</td>
-</tr>
-<tr>
-<td valign=top>-showversion</td>
-<td>Display the build number of the compiler and continue. This is very useful to report a bug.</td>
-</tr>
-</table>
-<h4>Examples</h4>
-<table>
-<tr>
-<td valign=top><code><font color="#3366FF">d:\temp -classpath rt.jar -time -g -d d:/tmp</font></code>
-</td>
-<td valign=top>It compiles all source files in d:\temp and its subfolders. The classpath is simply rt.jar. It generates all debug
-attributes and all generated .class files are dumped in d:\tmp. The speed of the compiler will be displayed once the batch process
-is completed.</td>
-</tr>
-<tr>
-<td valign=top><code><font color="#3366FF">d:\temp\Test.java -classpath d:\temp;rt.jar -g:none</font></code>
-</td>
-<td valign=top>It compiles only Test.java and it will retrieve any dependant files from d:\temp. The classpath is rt.jar and d:\temp, which means that all necessary classes
-are searched first in d:\temp and then in rt.jar. It generates no debug attributes and all generated .class files are dumped in d:\tmp.</td>
-</tr>
-</table>
-<h3>Using the ant javac adapter</h3>
-  The Eclipse compiler can be used inside an Ant script using the javac adapter. 
-In order to use the Eclipse compiler, you simply need to define the <b>build.compiler</b>
-  property in your script. Here is a small example. <font color="#4444cc">
-<pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
-&lt;project name=&quot;compile&quot; default=&quot;main&quot; basedir=&quot;../.&quot;&gt;
-
-	<b>&lt;property name=&quot;build.compiler&quot; value=&quot;org.eclipse.jdt.core.JDTCompilerAdapter&quot;/&gt;</b>
-
-	&lt;property name=&quot;root&quot; value=&quot;${basedir}/src&quot;/&gt;
-
-	&lt;property name=&quot;destdir&quot; value=&quot;d:/temp/bin&quot; /&gt;
-
-	&lt;target name=&quot;main&quot;&gt;
-		&lt;javac srcdir=&quot;${root}&quot; destdir=&quot;${destdir}&quot; debug=&quot;on&quot; nowarn=&quot;on&quot; extdirs=&quot;d:/extdirs&quot; source=&quot;1.4&quot;&gt;
-		    &lt;classpath&gt;
-		      &lt;pathelement location=&quot;${basedir}/../org.eclipse.jdt.core/bin&quot;/&gt;
-		    &lt;/classpath&gt;
-		&lt;/javac&gt;		
-	&lt;/target&gt;
-&lt;/project&gt;
-</pre>
-</font> The syntax used for the javac Ant task can be found in the <a href="http://jakarta.apache.org/ant/manual/CoreTasks/javac.html">
- Ant javac task documentation</a>. The current adapter supports the Javac Ant task 1.4.1 up to 1.6.5 versions.
-<p>If you are using a version above 1.5.0, you can use the nested compiler argument element to specify compiler
-specific options.
-</p>
-<font color="#4444cc">
-<pre>...
-&lt;javac srcdir=&quot;${root}&quot; destdir=&quot;${destdir}&quot; debug=&quot;on&quot; nowarn=&quot;on&quot; extdirs=&quot;d:/extdirs&quot; source=&quot;1.4&quot;&gt;
-    &lt;classpath&gt;
-      &lt;pathelement location=&quot;${basedir}/../org.eclipse.jdt.core/bin&quot;/&gt;
-    &lt;/classpath&gt;
-    &lt;compilerarg compiler=&quot;org.eclipse.jdt.core.JDTCompilerAdapter&quot; line=&quot;-1.5 -warn:+boxing&quot;/&gt;
-&lt;/javac&gt;		
-...
-</pre>
-</font>
-<p>To prevent from getting compiler dependant scripts, we advice you to use the compiler argument set to <code>org.eclipse.jdt.core.JDTCompilerAdapter</code>.
-If this is not set, the script can only be used with the Eclipse compiler. If set, the nested compiler argument is ignored if the name is different from the 
-compiler name specified by the <code>build.compiler</code> property.</p>
-<h3> Problem determination</h3>
-<p> JDT Core defines a specialized marker (marker type "<b>org.eclipse.jdt.core.problem</b>
-  ") to denote compilation problems. To programmatically discover problems
- detected by the compiler, the standard platform marker protocol should be
- used. See <a href="../../org.eclipse.platform.doc.isv/guide/resAdv_markers.htm" class="XRef">
- Resource Markers</a>
-  for an overview of using markers.</p>
-<p> The following snippet finds all Java problem markers in a compilation 
-unit.</p>
-<font color="#4444cc">
-<pre>   public IMarker[] findJavaProblemMarkers(ICompilationUnit cu) 
-      throws CoreException {
-      IResource javaSourceFile = cu.getUnderlyingResource();
-      IMarker[] markers = 
-         javaSourceFile.findMarkers(IJavaModelMarker.JAVA_MODEL_PROBLEM_MARKER,
-            true, IResource.DEPTH_INFINITE);
-   }
-</pre>
-</font>
-<p> Java problem markers are maintained by the Java project builder and are 
-removed automatically as problems are resolved and the Java source is recompiled.</p>
-<p>The problem id value is set by one of the constants in <b><a href="../reference/api/org/eclipse/jdt/core/compiler/IProblem.html">
- IProblem</a>
-</b>. The problem's id is reliable, but the message is localized and therefore 
-can be changed according to the default locale. The constants defined in <b><a href="../reference/api/org/eclipse/jdt/core/compiler/IProblem.html">
- IProblem</a>
-</b> are self-descriptive. </p>
-<p>An implementation of <b><a href="../reference/api/org/eclipse/jdt/core/IProblemRequestor.html">
- IProblemRequestor</a>
-</b> should be defined to collect the problems discovered during a Java operation. 
-  Working copies can be reconciled with problem detection if a <b><a href="../reference/api/org/eclipse/jdt/core/IProblemRequestor.html">
- IProblemRequestor</a>
-</b> has been supplied for the working copy creation. To achieve this, you 
-can use the <b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#reconcile(int, boolean, org.eclipse.jdt.core.WorkingCopyOwner, org.eclipse.core.runtime.IProgressMonitor)">
- reconcile</a></b> method. Here is an example: <font color="#4444cc">
-<pre>
-  ICompilationUnit unit = ..; // get some compilation unit
-			
-  // create requestor for accumulating discovered problems
-  IProblemRequestor problemRequestor = new IProblemRequestor() {
-    public void acceptProblem(IProblem problem) {
-      System.out.println(problem.getID() + &quot;: &quot; + problem.getMessage());
-    }
-    public void beginReporting() {}
-    public void endReporting() {}
-    public boolean isActive() {	return true; } // will detect problems if active
-  };
-    
-  // use working copy to hold source with error
-  ICompilationUnit workingCopy = unit.getWorkingCopy(new WorkingCopyOwner() {}, problemRequestor, null);
-  ((IOpenable)workingCopy).getBuffer().setContents(&quot;public class X extends Zork {}&quot;);
-
-  // trigger reconciliation			
-  workingCopy.reconcile(NO_AST, true, null, null);
-</pre></font> You can add an action on the reported problems in the acceptProblem(IProblem) 
-method. In this example, the reported problem will be that <b>Zork cannot 
-be resolved or is not a valid superclass</b> and its id is <b>IProblem.SuperclassNotFound</b>.
-</p>
-<h3>Excluding warnings using <code>SuppressWarnings</code></h3>
-<p>Java 5.0 offers the option to the user to disable compilation warnings relative to a subset of a compilation unit using
-the annotation <code>java.lang.SuppressWarning</code>.</p>
-<pre>
-	@SuppressWarning("unused") public void foo() {
-		String s;
-	}
-</pre>
-<p>Without the annotation, the compiler would complain that the local variable <code>s</code> is never used.
-With the annotation, the compiler silently ignore this warning locally to the the <code>foo</code> method. This enables to
-keep the warnings in other locations of the same compilation unit or the same project.</p>
-<p>The list of tokens that can be used inside an <code>SuppressWarning</code> annotation is:</p>
-<ul>
-<li><font color="green">all</font> to suppress all warnings</li>
-<li><font color="green">boxing</font> to suppress warnings relative to boxing/unboxing operations</li>
-<li><font color="green">cast</font> to suppress warnings relative to cast operations</li>
-<li><font color="green">dep-ann</font> to suppress warnings relative to deprecated annotation</li>
-<li><font color="green">deprecation</font> to suppress warnings relative to deprecation</li>
-<li><font color="green">fallthrough</font> to suppress warnings relative to missing breaks in switch statements</li>
-<li><font color="green">finally</font> to suppress warnings relative to finally block that don't return</li>
-<li><font color="green">hiding</font> to suppress warnings relative to locals that hide variable</li>
-<li><font color="green">incomplete-switch</font> to suppress warnings relative to missing entries in a switch statement (enum case)</li>
-<li><font color="green">nls</font> to suppress warnings relative to nls warnings</li>
-<li><font color="green">null</font> to suppress warnings relative to null analysis</li>
-<li><font color="green">restriction</font> to suppress warnings relative to usage of discouraged or forbidden references</li>
-<li><font color="green">serial</font> to suppress warnings relative to missing serialVersionUID field for a serializable class</li>
-<li><font color="green">static-access</font> to suppress warnings relative to incorrect static access</li>
-<li><font color="green">synthetic-access</font> to suppress warnings relative to unoptimized access from inner classes</li>
-<li><font color="green">unchecked</font> to suppress warnings relative to unchecked operations</li>
-<li><font color="green">unqualified-field-access</font> to suppress warnings relative to field access unqualified</li>
-<li><font color="green">unused</font> to suppress warnings relative to unused code</li>
-</ul>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_editors.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_editors.htm
deleted file mode 100644
index f752c5b..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_editors.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Customizing Java editors</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2> Customizing Java editors</h2>
-<p>The JDT tools implement a fully-functioning Java editor.&nbsp; They also
-define API so you can assign Java text editing features to your own editors or
-enhance the Java editor with your plug-in specific features.</p>
-<h3> Java text editing</h3>
-<p><a href="../reference/api/org/eclipse/jdt/ui/text/JavaSourceViewerConfiguration.html"><b>JavaSourceViewerConfiguration</b></a>
-describes the configuration for a viewer that displays Java code.&nbsp; Given a
-source code viewer, this class provides access to the instances of the utility
-classes that add Java specific behavior to the viewer, such as coloring,
-scanning of tokens, content assist, etc.&nbsp; The viewer configuration depends
-on <a href="../reference/api/org/eclipse/jdt/ui/text/JavaTextTools.html"><b> 
-    JavaTextTools</b></a>  to provide this information.&nbsp;&nbsp; <a href="../reference/api/org/eclipse/jdt/ui/text/JavaTextTools.html"><b>JavaTextTools</b></a>
-is a utility class that provides the scanners and managers for Java text and
-ensures that these classes are configured appropriately when the Java editor
-preferences change.</p>
-<h3> Java text hovers</h3>
-<p>When you implement a plug-in that provides additional capabilities associated
-with Java code, you may want to implement new hover behavior in the editor, so
-that information about your model elements will be shown as the user hovers over
-Java code.&nbsp; For example, the debugger uses a customized hover to show
-variable values when the user hovers over variable names in the editor.</p>
-<p>The extension point <a href="../reference/extension-points/org_eclipse_jdt_ui_javaEditorTextHovers.html"> 
-    <b> 
-    org.eclipse.jdt.ui.javaEditorTextHovers</b></a>  allows you to register your
-own hover implementation.&nbsp; You are responsible for implementing the <a href="../reference/api/org/eclipse/jdt/ui/text/java/hover/IJavaEditorTextHover.html"><b>IJavaEditorTextHover</b></a> 
-and registering your implementation class in the extension definition.&nbsp; You
-also provide a label for your hover type so that the user can enable and disable
-the different types of hovers from the editor preferences page.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_junit.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_junit.htm
deleted file mode 100644
index deeacba..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_junit.htm
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Observing JUnit test runs</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2>Observing JUnit test runs</h2>
-<p>The JDT JUnit plug-in defines an extension point that allows you to observe
-JUnit test runs and implement a reporting scheme in your plug-in. This extension point is useful if you are
-implementing test or build tools that must report the results of automated test
-runs. </p>
-<p>To observe test runs, you must implement <a href="../reference/api/org/eclipse/jdt/junit/ITestRunListener.html"><b>ITestRunListener</b></a>.&nbsp;
-This listener is notified when test runs are started and ended, and as
-individual tests are started and ended.&nbsp; Failures are reported individually
-along with the stack trace at failure time. </p>
-<p>Your listener is registered using the <b><a href="../reference/extension-points/org_eclipse_jdt_junit_testRunListeners.html">org.eclipse.jdt.junit.testRunListeners</a></b>
-extension point.&nbsp; Your plug-in's markup should supply the name of the
-listener class that implements <a href="../reference/api/org/eclipse/jdt/junit/ITestRunListener.html"><b>ITestRunListener</b></a><b>.</b> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_manip.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_manip.htm
deleted file mode 100644
index 6103951..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_manip.htm
+++ /dev/null

@@ -1,490 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>
-<HEAD>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Manipulating Java code</title>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY>
-<h2>Manipulating Java code</h2>
-<P>
-Your plug-in can use the JDT API to create classes or interfaces, add methods to existing types, or alter the methods for types. </P>
-<P>
-The simplest way to alter Java objects is to use the Java element API. More general techniques can be used to work with the raw source code for a Java element.</P>
-
-<H3>
-Code modification using Java elements</h3>
-
-<H4>
-Generating a compilation unit
-</h4>
-<P>
-The easiest way to programmatically generate a compilation unit is to use 
-<b><a href="../reference/api/org/eclipse/jdt/core/IPackageFragment.html#createCompilationUnit(java.lang.String, java.lang.String, boolean, org.eclipse.core.runtime.IProgressMonitor)">IPackageFragment.createCompilationUnit</a></b>. 
-You specify the name and contents of the compilation unit. The compilation unit is created inside the package and the new
-<b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html"> ICompilationUnit</a></b> is returned. </P>
-<P>
-A compilation unit can be created generically by creating a file resource whose extension is &quot;<b>.java&quot;</b> in the appropriate folder that corresponds to the package directory. Using the generic resource API is a back door to the Java tooling, so the Java model is not updated until the generic resource change listeners are
-notified and the JDT listeners update the Java model with the new compilation unit.</P>
-
-
-<H4>
-Modifying a compilation unit
-</h4>
-<P>
-Most simple modifications of Java source can be done using the Java element API.</P>
-<P>
-For example, you can query a type from a compilation unit. Once you have the <a href="../reference/api/org/eclipse/jdt/core/IType.html"><b>IType</b></a>, you can use protocols such as
-<a href="../reference/api/org/eclipse/jdt/core/IType.html#createField(java.lang.String, org.eclipse.jdt.core.IJavaElement, boolean, org.eclipse.core.runtime.IProgressMonitor)"><b>createField</b></a>, 
-<a href="../reference/api/org/eclipse/jdt/core/IType.html#createInitializer(java.lang.String, org.eclipse.jdt.core.IJavaElement, org.eclipse.core.runtime.IProgressMonitor)"><b>createInitializer</b></a>,
-<a href="../reference/api/org/eclipse/jdt/core/IType.html#createMethod(java.lang.String, org.eclipse.jdt.core.IJavaElement, boolean, org.eclipse.core.runtime.IProgressMonitor)"><b>createMethod</b></a>, 
-or <a href="../reference/api/org/eclipse/jdt/core/IType.html#createType(java.lang.String, org.eclipse.jdt.core.IJavaElement, boolean, org.eclipse.core.runtime.IProgressMonitor)"><b>createType</b></a> 
-to add source code members to the type. The source code and information about the location of the member is supplied in these methods.</P>
-<P>
-The <b><a href="../reference/api/org/eclipse/jdt/core/ISourceManipulation.html"> ISourceManipulation</a></b> interface defines common source manipulations for Java elements. This includes methods for renaming, moving, copying, or deleting a type's member. </P>
-
-
-<H4>
-Working copies
-</h4>
-<P>
-Code can be modified by manipulating the compilation unit (and thus the underlying 
-<a HREF="../../org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/resources/IFile.html"><b>IFile</b></a> is modified) or
-one can modify an in-memory copy of the compilation unit called a working copy. </P>
-<P>
-A working copy is obtained from a compilation unit using the 
-<b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#getWorkingCopy(org.eclipse.core.runtime.IProgressMonitor)">getWorkingCopy</a></b>
-method. (Note that the compilation unit does not need to exist in the Java model
-in order for a working copy to be created.)&nbsp; Whoever creates such a working copy is responsible for discarding it when not needed any longer using the
-<b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#discardWorkingCopy()">discardWorkingCopy</a></b>
-method. </P>
-<P>
-Working copies modify an in-memory buffer. The <b>getWorkingCopy()</b> method creates a default buffer, but
-clients can provide their own buffer implementation using the
-<b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#getWorkingCopy(org.eclipse.jdt.core.WorkingCopyOwner, org.eclipse.jdt.core.IProblemRequestor, org.eclipse.core.runtime.IProgressMonitor)">getWorkingCopy(WorkingCopyOwner, IProblemRequestor, IProgressMonitor)</a></b>
-method. Clients can manipulate the text of this buffer directly. If they do so, they must synchronize the working copy with
-the buffer from time to time using either the
-<b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#reconcile(int, boolean, org.eclipse.jdt.core.WorkingCopyOwner, org.eclipse.core.runtime.IProgressMonitor)">reconcile(int, boolean, WorkingCopyOwner, IProgressMonitor)</a></b>
-method.  </P>
-<P>
-Finally a working copy can be saved to disk (replacing the original compilation unit) using the
-<b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#commitWorkingCopy(boolean, org.eclipse.core.runtime.IProgressMonitor)">commitWorkingCopy</a></b>
-method.&nbsp;&nbsp; </P>
-<P>
-For example the following code snippet creates a working copy on a compilation unit using a custom working copy owner. The snippet
-modifies the buffer, reconciles the changes, commits the changes to disk and finally discards the working copy. </P>
-<font color='#4444CC'><pre>
-    // Get original compilation unit
-    ICompilationUnit originalUnit = ...;
-    
-    // Get working copy owner
-    WorkingCopyOwner owner = ...;
-    
-    // Create working copy
-    ICompilationUnit workingCopy = originalUnit.getWorkingCopy(owner, null, null);
-    
-    // Modify buffer and reconcile
-    IBuffer buffer = ((IOpenable)workingCopy).getBuffer();
-    buffer.append(&quot;class X {}&quot;);
-    workingCopy.reconcile(NO_AST, false, null, null);
-    
-    // Commit changes
-    workingCopy.commitWorkingCopy(false, null);
-    
-    // Destroy working copy
-    workingCopy.discardWorkingCopy();
-</pre></font>
-<P>
-Working copies can also be shared by several clients using a working copy owner. A working copy can be later retrieved using the
-<b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#findWorkingCopy(org.eclipse.jdt.core.WorkingCopyOwner)">findWorkingCopy</a></b>
-method. A shared working copy is thus keyed on the original compilation unit and on a working copy owner.</P>
-<P>
-The following shows how client 1 creates a shared working copy, client 2 retrieves this working copy, client 1 discards the
-working copy, and client 2 trying to retrieve the shared working copy notices it does not exist any longer: </P>
-<font color='#4444CC'><pre>
-    // Client 1 &amp; 2: Get original compilation unit
-    ICompilationUnit originalUnit = ...;
-    
-    // Client 1 &amp; 2: Get working copy owner
-    WorkingCopyOwner owner = ...;
-    
-    // Client 1: Create shared working copy
-    ICompilationUnit workingCopyForClient1 = originalUnit.getWorkingCopy(owner, null, null);
-    
-    // Client 2: Retrieve shared working copy
-    ICompilationUnit workingCopyForClient2 = originalUnit.findWorkingCopy(owner);
-     
-    // This is the same working copy
-    assert workingCopyForClient1 == workingCopyForClient2;
-    
-    // Client 1: Discard shared working copy
-    workingCopyForClient1.discardWorkingCopy();
-    
-    // Client 2: Attempt to retrieve shared working copy and find out it's null
-    workingCopyForClient2 = originalUnit.findWorkingCopy(owner);
-    assert workingCopyForClient2 == null;
-</pre></font>
-
-<H3>Code modification using the DOM/AST API</h3>
-
-
-There are three ways to create a <b><a href="../reference/api/org/eclipse/jdt/core/dom/CompilationUnit.html">CompilationUnit</a></b>.
-The first one is to use <b><a href="../reference/api/org/eclipse/jdt/core/dom/ASTParser.html">ASTParser</a></b>.
-The second is to use <b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#reconcile(int, boolean, org.eclipse.jdt.core.WorkingCopyOwner, org.eclipse.core.runtime.IProgressMonitor)">ICompilationUnit#reconcile(...)</a></b>.
-The third is to start from scratch using the factory methods on <b><a href="../reference/api/org/eclipse/jdt/core/dom/AST.html">AST</a></b> (Abstract Syntax Tree).
-
-<h4>
-Creating an AST from existing source code
-</h4>
-
-An instance of <b><a href="../reference/api/org/eclipse/jdt/core/dom/ASTParser.html">ASTParser</a></b> must be created with <a href="../reference/api/org/eclipse/jdt/core/dom/ASTParser.html#newParser(int)">ASTParser.newParser(int)</a>.<br>
-<br>
-The source code is given to the <b><a href="../reference/api/org/eclipse/jdt/core/dom/ASTParser.html">ASTParser</a></b> with one of the following methods:
-<ul>
-<li><a href="../reference/api/org/eclipse/jdt/core/dom/ASTParser.html#setSource(char[])">setSource(char[])</a>: to create the AST from source code</li>
-<li><a href="../reference/api/org/eclipse/jdt/core/dom/ASTParser.html#setSource(org.eclipse.jdt.core.IClassFile)">setSource(IClassFile)</a>: to create the AST from a classfile</li>
-<li><a href="../reference/api/org/eclipse/jdt/core/dom/ASTParser.html#setSource(org.eclipse.jdt.core.ICompilationUnit)">setSource(ICompilationUnit)</a>: to create the AST from a compilation unit</li>
-</ul>
-
-Then the AST is created by calling <a href="../reference/api/org/eclipse/jdt/core/dom/ASTParser.html#createAST(org.eclipse.core.runtime.IProgressMonitor)">createAST(IProgressMonitor)</a>.<br>
-<br>
-The result is an AST with correct source positions for each node.
-The resolution of bindings has to be requested before the creation of the tree with <a href="../reference/api/org/eclipse/jdt/core/dom/ASTParser.html#setResolveBindings(boolean)">setResolveBindings(boolean)</a>.
-Resolving the bindings is a costly operation and should be done only when necessary.
-As soon as the tree has been modified, all positions and bindings are lost.
-
-<h4>
-Creating an AST by reconciling a working copy
-</h4>
-If a working copy is not consistent (has been modified) then an AST can be created by calling the method <a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#reconcile(int, boolean, org.eclipse.jdt.core.WorkingCopyOwner, org.eclipse.core.runtime.IProgressMonitor)">reconcile(int, boolean, WorkingCopyOwner, IProgressMonitor)</a>.
-To request AST creation, call the <a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#reconcile(int, boolean, org.eclipse.jdt.core.WorkingCopyOwner, org.eclipse.core.runtime.IProgressMonitor)">reconcile(...)</a>
- method with <a href="../reference/api/org/eclipse/jdt/core/dom/AST.html#JLS2">AST.JLS2</a> as first parameter.<br>
-<br>
-Its bindings are computed only if the problem requestor is active, or if the problem detection is forced.
-Resolving the bindings is a costly operation and should be done only when necessary. As soon as the tree has been modified, all positions and
-bindings are lost.
-
-<h4>
-From scratch
-</h4>
-<P>It is possible to create a <b><a href="../reference/api/org/eclipse/jdt/core/dom/CompilationUnit.html">CompilationUnit</a></b> from scratch using the factory methods on <b><a href="../reference/api/org/eclipse/jdt/core/dom/AST.html">AST</a></b>.
-These method names start with <b>new...</b>. The following is an example that creates a <b>HelloWorld</b> class.
-</P>
-<P>The first snippet is the generated output:
-<font color='#4444CC'><pre>
-	package example;
-	import java.util.*;
-	public class HelloWorld {
-		public static void main(String[] args) {
-			System.out.println(&quot;Hello&quot; + &quot; world&quot;);
-		}
-	}
-</pre></font></p>
-<P>The following snippet is the corresponding code that generates the output.
-<font color='#4444CC'><pre>
-		AST ast = new AST();
-		CompilationUnit unit = ast.newCompilationUnit();
-		PackageDeclaration packageDeclaration = ast.newPackageDeclaration();
-		packageDeclaration.setName(ast.newSimpleName(&quot;example&quot;));
-		unit.setPackage(packageDeclaration);
-		ImportDeclaration importDeclaration = ast.newImportDeclaration();
-		QualifiedName name = 
-			ast.newQualifiedName(
-				ast.newSimpleName(&quot;java&quot;),
-				ast.newSimpleName(&quot;util&quot;));
-		importDeclaration.setName(name);
-		importDeclaration.setOnDemand(true);
-		unit.imports().add(importDeclaration);
-		TypeDeclaration type = ast.newTypeDeclaration();
-		type.setInterface(false);
-		type.setModifiers(Modifier.PUBLIC);
-		type.setName(ast.newSimpleName(&quot;HelloWorld&quot;));
-		MethodDeclaration methodDeclaration = ast.newMethodDeclaration();
-		methodDeclaration.setConstructor(false);
-		methodDeclaration.setModifiers(Modifier.PUBLIC | Modifier.STATIC);
-		methodDeclaration.setName(ast.newSimpleName(&quot;main&quot;));
-		methodDeclaration.setReturnType(ast.newPrimitiveType(PrimitiveType.VOID));
-		SingleVariableDeclaration variableDeclaration = ast.newSingleVariableDeclaration();
-		variableDeclaration.setModifiers(Modifier.NONE);
-		variableDeclaration.setType(ast.newArrayType(ast.newSimpleType(ast.newSimpleName(&quot;String&quot;))));
-		variableDeclaration.setName(ast.newSimpleName(&quot;args&quot;));
-		methodDeclaration.parameters().add(variableDeclaration);
-		org.eclipse.jdt.core.dom.Block block = ast.newBlock();
-		MethodInvocation methodInvocation = ast.newMethodInvocation();
-		name = 
-			ast.newQualifiedName(
-				ast.newSimpleName(&quot;System&quot;),
-				ast.newSimpleName(&quot;out&quot;));
-		methodInvocation.setExpression(name);
-		methodInvocation.setName(ast.newSimpleName(&quot;println&quot;)); 
-		InfixExpression infixExpression = ast.newInfixExpression();
-		infixExpression.setOperator(InfixExpression.Operator.PLUS);
-		StringLiteral literal = ast.newStringLiteral();
-		literal.setLiteralValue(&quot;Hello&quot;);
-		infixExpression.setLeftOperand(literal);
-		literal = ast.newStringLiteral();
-		literal.setLiteralValue(&quot; world&quot;);
-		infixExpression.setRightOperand(literal);
-		methodInvocation.arguments().add(infixExpression);
-		ExpressionStatement expressionStatement = ast.newExpressionStatement(methodInvocation);
-		block.statements().add(expressionStatement);
-		methodDeclaration.setBody(block);
-		type.bodyDeclarations().add(methodDeclaration);
-		unit.types().add(type);
-</pre></font></p>
-<h4>Retrieving extra positions</h4>
-The DOM/AST node contains only a pair of positions (the starting position and the length of the node). This is not always
-sufficient. In order to retrieve intermediate positions, the <b><a href="../reference/api/org/eclipse/jdt/core/compiler/IScanner.html">IScanner</a></b> API should be used. For example,
-we have an <b><a href="../reference/api/org/eclipse/jdt/core/dom/InstanceofExpression.html">InstanceofExpression</a></b> for which we want to know the 
-positions of the <i>instanceof</i> operator.
-We could write the following method to achieve this:
-<font color='#4444CC'><pre>
-	private int[] getOperatorPosition(Expression expression, char[] source) {
-		if (expression instanceof InstanceofExpression) {
-			IScanner scanner = ToolFactory.createScanner(false, false, false, false);
-			scanner.setSource(source);
-			int start = expression.getStartPosition();
-			int end = start + expression.getLength();
-			scanner.resetTo(start, end);
-			int token;
-			try {
-				while ((token = scanner.getNextToken()) != ITerminalSymbols.TokenNameEOF) {
-					switch(token) {
-						case ITerminalSymbols.TokenNameinstanceof:
-							return new int[] {scanner.getCurrentTokenStartPosition(), scanner.getCurrentTokenEndPosition()};
-					}
-				}
-			} catch (InvalidInputException e) {
-			}
-		}
-		return null;
-	}
-</pre></font>
-The <b><a href="../reference/api/org/eclipse/jdt/core/compiler/IScanner.html">IScanner</a></b> is used to divide the input source into tokens.
-Each token has a specific value that is defined in the <b><a href="../reference/api/org/eclipse/jdt/core/compiler/ITerminalSymbols.html">ITerminalSymbols</a></b> interface. It is 
-fairly simple to iterate and retrieve the right token. We also recommend that you use the scanner if you want to find the 
-position of the <i>super</i> keyword in a 
-<b><a href="../reference/api/org/eclipse/jdt/core/dom/SuperMethodInvocation.html">SuperMethodInvocation</a></b>.
-
-<h4>Source code modifcations</h4>
-
-<P>
-Some source code modifications are not provided via the Java element API.
-A more general way to edit source code (such as changing the source code for existing elements) is accomplished using the compilation unit's raw source code and the rewrite API of the DOM/AST.</P>
-<P>
-To perform DOM/AST rewriting, there two set of API: the descriptive rewriting and the modifying rewriting.
-</p>
-<p>
-The descriptive API does not modify the AST but use <b><a href="../reference/api/org/eclipse/jdt/core/dom/rewrite/ASTRewrite.html">ASTRewrite</a></b> API to generate the descritions of modifications.
-The AST rewriter collects descriptions of modifications to nodes and translates these descriptions into text edits that can then be applied to the original source.
-
-<font color='#4444CC'><pre>
-   // creation of a Document
-   ICompilationUnit cu = ... ; // content is "public class X {\n}"
-   String source = cu.getBuffer().getContents();
-   Document document= new Document(source);
-
-   // creation of DOM/AST from a ICompilationUnit
-   ASTParser parser = ASTParser.newParser(AST.JLS2);
-   parser.setSource(cu);
-   CompilationUnit astRoot = (CompilationUnit) parser.createAST(null);
-
-   // creation of ASTRewrite
-   ASTRewrite rewrite = new ASTRewrite(astRoot.getAST());
-
-   // description of the change
-   SimpleName oldName = ((TypeDeclaration)astRoot.types().get(0)).getName();
-   SimpleName newName = astRoot.getAST().newSimpleName("Y");
-   rewrite.replace(oldName, newName, null);
-
-   // computation of the text edits
-   TextEdit edits = rewrite.rewriteAST(document, cu.getJavaProject().getOptions(true));
-
-   // computation of the new source code
-   edits.apply(document);
-   String newSource = document.get();
-
-   // update of the compilation unit
-   cu.getBuffer().setContents(newSource);
-</pre></font></p>
-
-<p>
-The modifying API allows to modify directly the AST:
-<ul>
-<li>Request the recording of modifications (<b><a href="../reference/api/org/eclipse/jdt/core/dom/CompilationUnit.html#recordModifications()">CompilationUnit.recordModifications()</a></b>).</li>
-<li>Perform the modifications on the AST Nodes.</li>
-<li>And when the modifications are finished, generate text edits that can then be applied to the original source (<b><a href="../reference/api/org/eclipse/jdt/core/dom/CompilationUnit.html#rewrite(org.eclipse.jface.text.IDocument, java.util.Map)">CompilationUnit.rewrite(...)</a></b>).</li>
-</ul>
-<font color='#4444CC'><pre>
-   // creation of a Document
-   ICompilationUnit cu = ... ; // content is "public class X {\n}"
-   String source = cu.getBuffer().getContents();
-   Document document= new Document(source);
-
-   // creation of DOM/AST from a ICompilationUnit
-   ASTParser parser = ASTParser.newParser(AST.JLS2);
-   parser.setSource(cu);
-   CompilationUnit astRoot = (CompilationUnit) parser.createAST(null);
-
-   // start record of the modifications
-   astRoot.recordModifications();
-
-   // modify the AST
-   TypeDeclaration typeDeclaration = (TypeDeclaration)astRoot.types().get(0)
-   SimpleName newName = astRoot.getAST().newSimpleName("Y");
-   typeDeclaration.setName(newName);
-
-   // computation of the text edits
-   TextEdit edits = astRoot.rewrite(document, cu.getJavaProject().getOptions(true));
-
-   // computation of the new source code
-   edits.apply(document);
-   String newSource = document.get();
-
-   // update of the compilation unit
-   cu.getBuffer().setContents(newSource);
-</pre></font></p>
-
-<H3>
-<a name="javadeltas">
-Responding to changes in Java elements</a></h3>
-<P>
-If your plug-in needs to know about changes to Java elements after the fact, you can register a Java
-<a href="../reference/api/org/eclipse/jdt/core/IElementChangedListener.html"><b> IElementChangedListener</b></a> with
-<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html"><b>JavaCore</b></a>.</P>
-<font color='#4444CC'><pre>
-   JavaCore.addElementChangedListener(new MyJavaElementChangeReporter());
-</pre></font>
-<P>
-You can be more specific and specify the type of events you're interested in using 
-<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#addElementChangedListener(org.eclipse.jdt.core.IElementChangedListener, int)"><b> addElementChangedListener(IElementChangedListener, int)</b></a>. </P>
-<P>
-For example, if you're only interested in listening for events during a reconcile operation: </P>
-<font color='#4444CC'><pre>
-   JavaCore.addElementChangedListener(new MyJavaElementChangeReporter(), ElementChangedEvent.POST_RECONCILE);
-</pre></font>
-<P>
-There are two kinds of events that are supported by <b>JavaCore</b>:
-<ul>
-<li><a href="../reference/api/org/eclipse/jdt/core/ElementChangedEvent.html#POST_CHANGE"><b>POST_CHANGE</b></a>: 
-      Listeners of this event kind will get notified during the corresponding 
-      <a HREF="../../org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/resources/IResourceChangeEvent.html#POST_CHANGE"><b>POST_CHANGE</b></a> 
-      resource change notification.</li>
-<li><a href="../reference/api/org/eclipse/jdt/core/ElementChangedEvent.html#POST_RECONCILE"><b>POST_RECONCILE</b></a>: 
-      Listeners of this event kind will get notified at the end of a reconcile operation on a working copy
-      (see <a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#reconcile(int, boolean, org.eclipse.jdt.core.WorkingCopyOwner, org.eclipse.core.runtime.IProgressMonitor)"><b>ICompilationUnit.reconcile(int, boolean, WorkingCopyOwner, IProgressMonitor)</b></a>).</li>
-</ul>
-</p><P>
-Java element change listeners are similar conceptually to resource change listeners
-(described in
-<a HREF="../../org.eclipse.platform.doc.isv/guide/resAdv_events.htm" CLASS="XRef">tracking resource changes</a>). The following snippet implements a Java element change reporter that prints the element deltas to the system console.</P>
-<font color='#4444CC'><pre>
-   public class MyJavaElementChangeReporter implements IElementChangedListener {
-      public void elementChanged(ElementChangedEvent event) {
-         IJavaElementDelta delta= event.getDelta();
-         if (delta != null) {
-            System.out.println(&quot;delta received: &quot;);
-            System.out.print(delta);
-         }
-      }
-   }
-</pre></font>
-<P>
-The <a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html"><b> IJavaElementDelta</b></a> includes the 
-<a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html#getElement()">element</a> that was
-changed and <a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html#getFlags()">flags</a> describing 
-the kind of change that occurred. Most of the time the delta tree is rooted at the Java Model level. Clients must then navigate
-this delta using <a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html#getAffectedChildren()"><b>getAffectedChildren</b></a> 
-to find out what projects have changed. </P>
-<P>
-The following example method traverses a delta and prints the elements that have been added, removed and changed:</P>
-<font color='#4444CC'><pre>
-    void traverseAndPrint(IJavaElementDelta delta) {
-        switch (delta.getKind()) {
-            case IJavaElementDelta.ADDED:
-                System.out.println(delta.getElement() + &quot; was added&quot;);
-                break;
-            case IJavaElementDelta.REMOVED:
-                System.out.println(delta.getElement() + &quot; was removed&quot;);
-                break;
-            case IJavaElementDelta.CHANGED:
-                System.out.println(delta.getElement() + &quot; was changed&quot;);
-                if ((delta.getFlags() &amp; IJavaElementDelta.F_CHILDREN) != 0) {
-                    System.out.println(&quot;The change was in its children&quot;);
-                }
-                if ((delta.getFlags() &amp; IJavaElementDelta.F_CONTENT) != 0) {
-                    System.out.println(&quot;The change was in its content&quot;);
-                }
-                /* Others flags can also be checked */
-                break;
-        }
-        IJavaElementDelta[] children = delta.getAffectedChildren();
-        for (int i = 0; i &lt; children.length; i++) {
-            traverseAndPrint(children[i]);
-        }
-    }
-</pre></font>
-
-<P>
-Several kinds of operations can trigger a Java element change notification. Here are some examples:
-<ul>
-<li>Creating a resource, e.g. <a href="../reference/api/org/eclipse/jdt/core/IPackageFragment.html#createCompilationUnit(java.lang.String, java.lang.String, boolean, org.eclipse.core.runtime.IProgressMonitor)"><b>IPackageFragment.createCompilationUnit</b></a> 
-      (the delta indicates the <a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html#ADDED">addition</a> of the compilation unit)</li>
-<li>Modifying a resource, e.g. <a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#createType(java.lang.String, org.eclipse.jdt.core.IJavaElement, boolean, org.eclipse.core.runtime.IProgressMonitor)"><b>ICompilationUnit.createType</b></a> 
-     (the delta indicates that the compilation unit has <a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html#CHANGED">changed</a> and that a type was 
-     <a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html#getAddedChildren()"> added as a child</a> of this compilation unit)</li>
-<li>Modifying a project's classpath, e.g. <a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html#setRawClasspath(org.eclipse.jdt.core.IClasspathEntry[], org.eclipse.core.runtime.IProgressMonitor)"><b>IJavaProject.setRawClasspath</b></a>
-     (the delta indicates that package fragment roots have been <a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html#F_ADDED_TO_CLASSPATH">added to the classpath</a>, 
-     <a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html#F_REMOVED_FROM_CLASSPATH">removed from the classpath</a>, or
-     <a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html#F_CLASSPATH_REORDER">reordered on the classpath</a>)</li>
-<li>Modifying a classpath variable value, e.g. <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#setClasspathVariable(java.lang.String, org.eclipse.core.runtime.IPath, org.eclipse.core.runtime.IProgressMonitor)"><b>JavaCore.setClasspathVariable</b></a>
-     (the delta also indicates that package fragment roots have been affected)</li>
-<li>Changing the source attachment of a .jar file, e.g. <a href="../reference/api/org/eclipse/jdt/core/IPackageFragmentRoot.html#attachSource(org.eclipse.core.runtime.IPath, org.eclipse.core.runtime.IPath, org.eclipse.core.runtime.IProgressMonitor)"><b>IPackageFragmentRoot.attachSource</b></a>
-     (the delta indicates that the source was <a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html#F_SOURCEDETACHED">detached</a>
-     then <a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html#F_SOURCEATTACHED">attached</a>)</li>
-<li>Reconciling a working copy with its buffer, e.g. <a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#reconcile(int, boolean, org.eclipse.jdt.core.WorkingCopyOwner, org.eclipse.core.runtime.IProgressMonitor)"><b>ICompilationUnit.reconcile</b></a></li>
-<li>Modifying an <a HREF="../../org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/resources/IFile.html"><b>IFile</b></a> that ends with ".java" and that is on the
-      project's classpath, e.g. using <b>IFile.setContents</b> (the delta indicates that a compilation unit was changed, but 
-      <a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html#F_FINE_GRAINED">no finer-grained information</a>
-      is provided as this was not done through a Java Model operation)</li>
-</ul>
-</p><P>Similar to <a HREF="../../org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/resources/IResourceDelta.html"><b>IResourceDelta</b></a> 
-the Java element deltas can be batched using an 
-<a HREF="../../org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/resources/IWorkspaceRunnable.html"><b>IWorkspaceRunnable</b></a>. 
-The deltas resulting from several Java Model operations that are run inside a <b>IWorkspaceRunnable</b> are merged and reported at once.&nbsp;&nbsp; </P>
-<P><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html"><b>JavaCore</b></a><b>
-</b>provides a <b>run</b> method for batching Java element changes. </P>
-<P>
-For example, the following code fragment will trigger 2 Java element change events: </P>
-<font color='#4444CC'><pre>
-    // Get package
-    IPackageFragment pkg = ...;
-    
-    // Create 2 compilation units
-    ICompilationUnit unitA = pkg.createCompilationUnit(&quot;A.java&quot;, &quot;public class A {}&quot;, false, null);
-    ICompilationUnit unitB = pkg.createCompilationUnit(&quot;B.java&quot;, &quot;public class B {}&quot;, false, null);
-</pre></font>
-<P>
-Whereas the following code fragment will trigger 1 Java element change event: </P>
-<font color='#4444CC'><pre>
-    // Get package
-    IPackageFragment pkg = ...;
-    
-    // Create 2 compilation units
-    JavaCore.run(
-        new IWorkspaceRunnable() {
- 	        public void run(IProgressMonitor monitor) throws CoreException {
- 	            ICompilationUnit unitA = pkg.createCompilationUnit(&quot;A.java&quot;, &quot;public class A {}&quot;, false, null);
- 	            ICompilationUnit unitB = pkg.createCompilationUnit(&quot;B.java&quot;, &quot;public class B {}&quot;, false, null);
- 	        }
-        },
-        null);
-</pre></font>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_open_editor.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_open_editor.htm
deleted file mode 100644
index 79b65a7..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_open_editor.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Opening a Java editor</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h3>Opening a Java editor</h3>
-<p>The following snippet shows how <b><a href="../reference/api/org/eclipse/jdt/ui/JavaUI.html"> 
-  JavaUI</a></b> can be used to open a Java editor and display a specific member of a 
-  Java compilation unit.</p>
-<pre><font color="#4444cc">    void showMethod(IMember member) {
-        ICompilationUnit cu = member.getCompilationUnit();
-        IEditorPart javaEditor = JavaUI.openInEditor(cu);
-        JavaUI.revealInEditor(javaEditor, member);
-    }
-</font></pre>
-<p> The methods <code>openInEditor</code> and <code>revealInEditor</code> also 
-  work for class files and for members contained in class files. </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_options.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_options.htm
deleted file mode 100644
index 7fa7a85..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_options.htm
+++ /dev/null

@@ -1,3957 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>
-<HEAD>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>JDT Core options</title>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY>
-<h2>JDT Core options</h2>
-<P>
-JDT Core options control the behavior of core features such as the Java
-compiler, code formatter, code assist, and other core behaviors.&nbsp; The APIs
-for accessing the options are defined in <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html"><b>JavaCore</b></a>.&nbsp;
-Options can be accessed as a group as follows:
-<ul>
-<li><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#getDefaultOptions()">JavaCore.getDefaultOptions()</a> - Answers the default value of the options.</li>
-<li><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#getOptions()">JavaCore.getOptions()</a> - Answers the current values of the options.</li>
-<li><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#setOptions(java.util.Hashtable)">JavaCore.setOptions(Hashtable newOptions)</a> - Replaces the options values by new values.</li>
-</ul>
-</p>
-<p>Options can also be accessed individually by a string name.</P>
-
-<ul>
-<li><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#getOption(java.lang.String)">JavaCore.getOption(String optionName)</a> - Answers the value of a specific option.</li>
-</ul>
-<p>Options are stored as a hash table of all known configurable options with their values.
-Helper constants have been defined on <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html"><b>JavaCore</b></a> for each option ID and its possible constant values.</P>
-
-<P>
-The following code fragment restores the value of all core options to their
-defaults except for one (<code>COMPILER_PB_DEPRECATION</code>), which is set specifically.
-<font color='#4444CC'><pre>
-   // Get the current options
-   Hashtable options = JavaCore.getDefaultOptions();
-   
-   // Change the value of an option
-   options.put(JavaCore.COMPILER_PB_DEPRECATION, JavaCore.ERROR);
-   
-   // Set the new options
-   JavaCore.setOptions(options);
-</pre></font>
-
-The following code fragment keeps the value of the current options and modifies
-only one (<code>COMPILER_PB_DEPRECATION</code>):
-
-<font color='#4444CC'><pre>
-   // Get the current options
-   Hashtable options = JavaCore.getOptions();
-   
-   // Change the value of an option
-   options.put(JavaCore.COMPILER_PB_DEPRECATION, JavaCore.ERROR);
-   
-   // Set the new options
-   JavaCore.setOptions(options);
-</pre></font></p>
-
-<H3>Project specific options</h3>
-
-<p>The values of options can be overridden per project using protocol in <a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html"><b>IJavaProject</b></a>.</p>
-
-<p>The following code fragment retrieves the value of an option (<code>COMPILER_PB_DEPRECATION</code>)
-for a specific project in two different ways.&nbsp; The boolean parameter
-controls whether only the project-specific options should be returned in a query
-or whether the project's option values should be merged with the values in
-JavaCore.</p>
-
-<font color="#4444CC"><pre>
-   // Get the project
-   IJavaProject project = ...;
-
-   // See if the value of an option has been set in this project
-   String value = project.getOption(JavaCore.COMPILER_PB_DEPRECATION, <b>false</b>);
-   if (value == null) {
-     // no specific option was set on the project
-     ...
-   }
-   
-   // Get the value of an option from this project.  Use the value from 
-   // JavaCore value if none is specified for the project
-   String value = project.getOption(JavaCore.COMPILER_PB_DEPRECATION, <b>true</b>);</pre></font>
-
-<H3>Major change in default JDT Core 3.0 options </h3>
-
-<p>Default compliance level has been changed. Now default compliance level is <code>1.4</code> instead of <code>1.3</code> and default target
-platform is <code>1.2</code> instead of <code>1.1</code>.</p>
-
-<H3>JDT Core options descriptions</h3>
-
-<P>
-The following tables describe the available JDT Core options.&nbsp; The option
-id is shown in parentheses and the default value is shown in bold italics. </P>
-
-<H4>Options categories</h4>
-<ul>
-<li><a href="#compiler">Compiler options</a></li>
-<li><a href="#builder">Builder options</a></li>
-<li><a href="#javacore">JavaCore options</a></li>
-<li><a href="#formatter">Formatter options</a></li>
-<li><a href="#codeassist">CodeAssist options</a></li>
-</ul>
-
-<H4><a name="compiler">Compiler options</a></h4>
-
-<table BORDER="1" CELLSPACING=2 CELLPADDING=2 COLS=2 WIDTH="100%" >
-<tr>
-<th>Description</th>
-<th width=140>Values</th>
-</tr>
-
-<tr>
-<td colspan=2><b>Inline JSR Bytecode Instruction</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_CODEGEN_INLINE_JSR_BYTECODE">COMPILER_CODEGEN_INLINE_JSR_BYTECODE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, the compiler will no longer generate JSR instructions, but rather inline corresponding
-subroutine code sequences (mostly corresponding to try finally blocks). The generated code will thus
-get bigger, but will load faster on virtual machines since the verification process is then much simpler. 
-This mode is anticipating support for the Java Specification Request 202.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Defining Target Java Platform</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_CODEGEN_TARGET_PLATFORM">COMPILER_CODEGEN_TARGET_PLATFORM</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>For binary compatibility reason, .class files can be tagged with certain VM versions and later.
-Note that the "1.4" target requires you to toggle the compliance mode to "1.4" also.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_1">VERSION_1_1</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_2"><b><i>VERSION_1_2</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_3">VERSION_1_3</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_4">VERSION_1_4</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Preserving Unused Local Variables</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_CODEGEN_UNUSED_LOCAL">COMPILER_CODEGEN_UNUSED_LOCAL</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Unless requested to preserve unused local variables (i.e. never read), the compiler will optimize them out, potentially altering debugging.</td>
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#PRESERVE">PRESERVE</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#OPTIMIZE_OUT">OPTIMIZE_OUT</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Setting Compliance Level</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_COMPLIANCE">COMPILER_COMPLIANCE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Select the compliance level for the compiler. In "1.3" mode, source and target settings should not go beyond "1.3" level.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_3">VERSION_1_3</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_4"><b><i>VERSION_1_4</i></b></a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Javadoc Comment Support</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_DOC_COMMENT_SUPPORT">COMPILER_DOC_COMMENT_SUPPORT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When this support is disabled, the compiler will ignore all javadoc problems options settings
-and will not report any javadoc problem. It will also not find any reference in javadoc comment and
-DOM AST Javadoc node will be only a flat text instead of having structured tag elements.</td>
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Generating Line Number Debug Attribute</b>  (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_LINE_NUMBER_ATTR">COMPILER_LINE_NUMBER_ATTR</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When generated, this attribute will enable source code highlighting in the debugger (.class file is then bigger).</td>
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#GENERATE">GENERATE</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_GENERATE">DO_NOT_GENERATE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Generating Local Variable Debug Attribute</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_LOCAL_VARIABLE_ATTR">COMPILER_LOCAL_VARIABLE_ATTR</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When generated, this attribute will enable local variable names to be displayed in the debugger, only in places where variables are definitely assigned (.class file is then bigger)</td>
-<td><i><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#GENERATE">GENERATE</a></b></i></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_GENERATE">DO_NOT_GENERATE</a></td>
-</tr>								  
-
-<tr>
-<td colspan=2><b>Reporting Use of Annotation Type as Super Interface</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_ANNOTATION_SUPER_INTERFACE">COMPILER_PB_ANNOTATION_SUPER_INTERFACE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever an annotation type is used as a super-interface. Though legal, this is discouraged.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Boxing/Unboxing Conversion</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_ASSERT_IDENTIFIER">COMPILER_PB_ASSERT_IDENTIFIER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever a boxing or an unboxing conversion is performed.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Usage of 'assert' Identifier</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_AUTOBOXING">COMPILER_PB_AUTOBOXING</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever 'assert' is used as an identifier (reserved keyword in 1.4)</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Usage of char[] Expressions in String Concatenations</b>
-  (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_CHAR_ARRAY_IN_STRING_CONCATENATION">COMPILER_PB_CHAR_ARRAY_IN_STRING_CONCATENATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning
-  whenever a char[] expression is used in String concatenations (e.g.
-  &quot;hello&quot; + new char[]{'w','o','r','l','d'}),</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><b><i>WARNING</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Deprecation</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_DEPRECATION">COMPILER_PB_DEPRECATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will signal use of deprecated API either as an error or a warning.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Deprecation Inside Deprecated Code</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_DEPRECATION_IN_DEPRECATED_CODE">COMPILER_PB_DEPRECATION_IN_DEPRECATED_CODE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, the compiler will signal use of deprecated API either as an error or a warning.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Deprecation When Overriding Deprecated Method</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_DEPRECATION_WHEN_OVERRIDING_DEPRECATED_METHOD">COMPILER_PB_DEPRECATION_WHEN_OVERRIDING_DEPRECATED_METHOD</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, the compiler will signal the declaration of a method overriding a deprecated one.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Discouraged Reference to Type with Restricted Access</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_DISCOURAGED_REFERENCE">COMPILER_PB_DISCOURAGED_REFERENCE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning when referring to a type with discouraged access, as defined according to the access rule specifications.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Empty Statements and Unnecessary Semicolons</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_EMPTY_STATEMENT">COMPILER_PB_EMPTY_STATEMENT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning if an empty statement or a
-  unnecessary semicolon is encountered.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Usage of 'enum' Identifier</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_ENUM_IDENTIFIER">COMPILER_PB_ENUM_IDENTIFIER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever 'enum' is used as an identifier (reserved keyword in 1.5)</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Field Declaration Hiding another Variable</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_FIELD_HIDING">COMPILER_PB_FIELD_HIDING</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever a field
-  declaration is hiding some field or local variable (either locally, inherited or defined in enclosing type).</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting final Bound for Type Parameter</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_FINAL_PARAMETER_BOUND">COMPILER_PB_FINAL_PARAMETER_BOUND</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever a generic type parameter is associated with a 
-bound corresponding to a final type; since final types cannot be further extended, the parameter is pretty useless.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Finally Blocks Not Completing Normally</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_FINALLY_BLOCK_NOT_COMPLETING">COMPILER_PB_FINALLY_BLOCK_NOT_COMPLETING</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning when a finally block does not complete normally.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><b><i>WARNING</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></td>
-</tr>
-						
-<tr>
-<td colspan=2><b>Reporting Finally Blocks Not Completing Normally</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_FINALLY_BLOCK_NOT_COMPLETING">COMPILER_PB_FINALLY_BLOCK_NOT_COMPLETING</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning when a finally block does not complete normally.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><b><i>WARNING</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Forbidden Reference to Type with Restricted Access</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_FORBIDDEN_REFERENCE">COMPILER_PB_FORBIDDEN_REFERENCE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning when referring to a type that is non accessible, as defined according to the access rule specifications.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><b><i>WARNING</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Hidden Catch Block</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_HIDDEN_CATCH_BLOCK">COMPILER_PB_HIDDEN_CATCH_BLOCK</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>Local to a try statement, some catch blocks may hide others , e.g.
-<pre>
-   try {
-      throw new java.io.CharConversionException();
-   } catch (java.io.CharConversionException e) {
-   } catch (java.io.IOException e) {}.
-</pre>
-When enabling this option, the compiler will issue an error or a warning for hidden catch blocks corresponding to checked exceptions</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Interface Method not Compatible with non-Inherited Methods</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_INCOMPATIBLE_NON_INHERITED_INTERFACE_METHOD">COMPILER_PB_INCOMPATIBLE_NON_INHERITED_INTERFACE_METHOD</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning
-  whenever an interface defines a method incompatible with a non-inherited
-  Object one.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><b><i>WARNING</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Incomplete Enum Switch</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_INCOMPLETE_ENUM_SWITCH">COMPILER_PB_INCOMPLETE_ENUM_SWITCH</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever an enum constant has no corresponding case label in an enum switch statement
-type has no case label matching an enum constant.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><b><i>IGNORE</i></b></a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Indirect Reference to a Static Member</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_INDIRECT_STATIC_ACCESS">COMPILER_PB_INDIRECT_STATIC_ACCESS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever a static field
-  or method is accessed in an indirect way. A reference to a static member should
-  preferably be qualified with its declaring type name.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><b><i>IGNORE</i></b></a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Invalid Javadoc Comment</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_INVALID_JAVADOC">COMPILER_PB_INVALID_JAVADOC</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>This is the generic control for the severity of Javadoc problems.
-  When enabled, the compiler will issue an error or a warning for a problem in Javadoc.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><b><i>IGNORE</i></b></a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Invalid Javadoc Tags</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_INVALID_JAVADOC_TAGS">COMPILER_PB_INVALID_JAVADOC_TAGS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, the compiler will signal unbound or unexpected reference tags in Javadoc.
-  A 'throws' tag referencing an undeclared exception would be considered as unexpected.
-  <br>Note that this diagnosis can be enabled based on the visibility of the construct associated with the Javadoc;
-  also see the setting "org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsVisibility".</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED"><b><i>ENABLED</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Invalid Javadoc Tags with Deprecated References</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_INVALID_JAVADOC_TAGS__DEPRECATED_REF">COMPILER_PB_INVALID_JAVADOC_TAGS__DEPRECATED_REF</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Specify whether the compiler will report deprecated references used in Javadoc tags.
-<br>Note that this diagnosis can be enabled based on the visibility of the construct associated with the Javadoc; also see the setting "org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsVisibility".</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED"><b><i>ENABLED</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Invalid Javadoc Tags with Not Visible References</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_INVALID_JAVADOC_TAGS__NOT_VISIBLE_REF">COMPILER_PB_INVALID_JAVADOC_TAGS__NOT_VISIBLE_REF</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Specify whether the compiler will report non-visible references used in Javadoc tags.
-<br>Note that this diagnosis can be enabled based on the visibility of the construct associated with the Javadoc;
-also see the setting "org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsVisibility".</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED"><b><i>ENABLED</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Visibility Level For Invalid Javadoc Tags</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_INVALID_JAVADOC_TAGS_VISIBILITY">COMPILER_PB_INVALID_JAVADOC_TAGS_VISIBILITY</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Set the minimum visibility level for Javadoc tag problems. Below this level problems will be ignored.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#PUBLIC">PUBLIC</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#PROTECTED">PROTECTED</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DEFAULT">DEFAULT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#PRIVATE"><b><i>PRIVATE</i></b></a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Local Variable Declaration Hiding another Variable</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_LOCAL_VARIABLE_HIDING">COMPILER_PB_LOCAL_VARIABLE_HIDING</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever a local variable
-  declaration is hiding some field or local variable (either locally, inherited or defined in enclosing type).</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><b><i>IGNORE</i></b></a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Maximum number of problems reported per compilation unit</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MAX_PER_UNIT">COMPILER_PB_MAX_PER_UNIT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>Specify the maximum number of problems reported on each compilation unit (if the maximum is zero then all problems are reported).</td>
-<td>a positive integer. <br><b><i>Default value is 100</i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Method With Constructor Name</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_METHOD_WITH_CONSTRUCTOR_NAME">COMPILER_PB_METHOD_WITH_CONSTRUCTOR_NAME</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>Naming a method with a constructor name is generally considered poor style programming. When enabling this option, the compiler will signal such scenarios either as an error or a warning.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Missing @Deprecated Annotation</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_DEPRECATED_ANNOTATION">COMPILER_PB_MISSING_DEPRECATED_ANNOTATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever encountering a declaration carrying a @deprecated doc tag but has no corresponding @Deprecated annotation.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><b><i>IGNORE</i></b></a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Missing Javadoc Comments</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_JAVADOC_COMMENTS">COMPILER_PB_MISSING_JAVADOC_COMMENTS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>This is the generic control for the severity of missing Javadoc comment problems.
-  When enabled, the compiler will issue an error or a warning when Javadoc comments are missing.
-  <br>Note that this diagnosis can be enabled based on the visibility of the construct associated with the expected Javadoc.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><b><i>IGNORE</i></b></a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Missing Javadoc Comments on Overriding Methods</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_JAVADOC_COMMENTS_OVERRIDING">COMPILER_PB_MISSING_JAVADOC_COMMENTS_OVERRIDING</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Specify whether the compiler will verify overriding methods in order to report missing Javadoc comment problems.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED"><b><i>ENABLED</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Missing @Override Annotation</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_OVERRIDE_ANNOTATION">COMPILER_PB_MISSING_OVERRIDE_ANNOTATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever encountering a method declaration which overrides a superclass method but has no @Override annotation.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><b><i>IGNORE</i></b></a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Visibility Level For Missing Javadoc Comments</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_JAVADOC_COMMENTS_VISIBILITY">COMPILER_PB_MISSING_JAVADOC_COMMENTS_VISIBILITY</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Set the minimum visibility level for missing Javadoc problems. Below this level problems will be ignored.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#PUBLIC"><b><i>PUBLIC</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#PROTECTED">PROTECTED</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DEFAULT">DEFAULT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#PRIVATE">PRIVATE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Missing Javadoc Tags</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_JAVADOC_TAGS">COMPILER_PB_MISSING_JAVADOC_TAGS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>This is the generic control for the severity of Javadoc missing tag problems.
-  When enabled, the compiler will issue an error or a warning when tags are missing in Javadoc comments.
-  <br>Note that this diagnosis can be enabled based on the visibility of the construct associated with the Javadoc.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><b><i>IGNORE</i></b></a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Missing Javadoc Tags on Overriding Methods</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_JAVADOC_TAGS_OVERRIDING">COMPILER_PB_MISSING_JAVADOC_TAGS_OVERRIDING</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Specify whether the compiler will verify overriding methods in order to report Javadoc missing tag problems.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED"><b><i>ENABLED</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Visibility Level For Missing Javadoc Tags</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_JAVADOC_TAGS_VISIBILITY">COMPILER_PB_MISSING_JAVADOC_TAGS_VISIBILITY</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Set the minimum visibility level for Javadoc missing tag problems. Below this level problems will be ignored.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#PUBLIC">PUBLIC</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#PROTECTED">PROTECTED</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DEFAULT">DEFAULT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#PRIVATE"><b><i>PRIVATE</i></b></a></td>
-</tr> 
-
-<tr>
-<td colspan=2><b>Reporting Missing @Override Annotation</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_OVERRIDE_ANNOTATION">COMPILER_PB_MISSING_OVERRIDE_ANNOTATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever encountering a method declaration which overrides a superclass method but has no @Override annotation.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><b><i>IGNORE</i></b></a></td>
-</tr>							  
-
-<tr>
-<td colspan=2><b>Reporting Missing Declaration of serialVersionUID Field on Serializable Class</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_SERIAL_VERSION">COMPILER_PB_MISSING_SERIAL_VERSION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever a serializable class is missing a local declaration of a serialVersionUID field. This field must be declared as static final and be of type long.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><b><i>WARNING</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Assignment with No Effect</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_NO_EFFECT_ASSIGNMENT">COMPILER_PB_NO_EFFECT_ASSIGNMENT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning
-  whenever an assignment has no effect (e.g. 'x = x').</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><b><i>WARNING</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Non-Externalized String Literal</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_NON_NLS_STRING_LITERAL">COMPILER_PB_NON_NLS_STRING_LITERAL</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning for non externalized String literal (i.e. non tagged with //$NON-NLS-&lt;n&gt;$)</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Attempt to Override Package-Default Method</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_OVERRIDING_PACKAGE_DEFAULT_METHOD">COMPILER_PB_OVERRIDING_PACKAGE_DEFAULT_METHOD</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>A package default method is not visible in a different package, and thus cannot be overridden. When enabling this option, the compiler will signal such scenarios either as an error or a warning.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Possible Accidental Boolean Assignment</b>(   <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_POSSIBLE_ACCIDENTAL_BOOLEAN_ASSIGNMENT">COMPILER_PB_POSSIBLE_ACCIDENTAL_BOOLEAN_ASSIGNMENT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning if a boolean assignment is acting as the condition
-  of a control statement  (where it probably was meant to be a boolean comparison).</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><b><i>IGNORE</i></b></a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Special Parameter Hiding another Field</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_SPECIAL_PARAMETER_HIDING_FIELD">COMPILER_PB_SPECIAL_PARAMETER_HIDING_FIELD</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, the compiler will signal cases where a constructor or setter method parameter declaration 
-  is hiding some field (either locally, inherited or defined in enclosing type).</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED"><b><i>DISABLED</i></b></a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Non-Static Reference to a Static Member</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_STATIC_ACCESS_RECEIVER">COMPILER_PB_STATIC_ACCESS_RECEIVER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning
-  whenever a static field or method is accessed with an expression receiver.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><b><i>WARNING</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Determining Effect of @SuppressWarnings</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_SUPPRESS_WARNINGS">COMPILER_PB_SUPPRESS_WARNINGS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, the @SuppressWarnings annotation can be used to suppress some compiler warnings. 
-<br>When disabled, all @SupressWarnings annotations are ignored; i.e., warnings are reported.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED"><b><i>ENABLED</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED></a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Synthetic Access Emulation</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_SYNTHETIC_ACCESS_EMULATION">COMPILER_PB_SYNTHETIC_ACCESS_EMULATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever it emulates access to a non-accessible member of an enclosing type. Such access can have performance implications.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Type Parameter Declaration Hiding another Type</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_TYPE_PARAMETER_HIDING">COMPILER_PB_TYPE_PARAMETER_HIDING</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever a type parameter declaration is hiding some type.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><b><i>WARNING</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unchecked Type Operation</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNCHECKED_TYPE_OPERATION">COMPILER_PB_UNCHECKED_TYPE_OPERATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever an operation involves generic types, and potentially
-invalidates type safety since involving raw types (e.g. invoking #foo(X&lt;String&gt;) with arguments (X)).</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><b><i>WARNING</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Undocumented Empty Block</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNDOCUMENTED_EMPTY_BLOCK">COMPILER_PB_UNDOCUMENTED_EMPTY_BLOCK</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning when an empty block is detected and it is not
-  documented with any comment.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><b><i>IGNORE</i></b></a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unhandled Warning Token for @SuppressWarnings</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNHANDLED_WARNING_TOKEN">COMPILER_PB_UNHANDLED_WARNING_TOKEN</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning when encountering a token it cannot handle inside a @SuppressWarnings annotation.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><b><i>WARNING</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unnecessary Else</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNNECESSARY_ELSE">COMPILER_PB_UNNECESSARY_ELSE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning when a statement is unnecessarily
-  nested within an else clause (in situation where then clause is not completing normally).</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unnecessary Type Check</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNNECESSARY_TYPE_CHECK">COMPILER_PB_UNNECESSARY_TYPE_CHECK</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning when a cast or an instanceof operation 
-  is unnecessary.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unqualified Access to Field</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNQUALIFIED_FIELD_ACCESS">COMPILER_PB_UNQUALIFIED_FIELD_ACCESS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning when a field is access without any qualification.
-  In order to improve code readability, it should be qualified, e.g. 'x' should rather be written 'this.x'.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><b><i>IGNORE</i></b></a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unused Declared Thrown Exception</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION">COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning when a method or a constructor is declaring a
-  thrown checked exception, but never actually raises it in its body.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><b><i>IGNORE</i></b></a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unused Declared Thrown Exception in Overriding Method</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_WHEN_OVERRIDING">COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_WHEN_OVERRIDING</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When disabled, the compiler will not include overriding methods in its diagnosis for unused declared
-  thrown exceptions.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED"><b><i>DISABLED</i></b></a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unused Import</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_IMPORT">COMPILER_PB_UNUSED_IMPORT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning for unused import reference </td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><i><b>WARNING</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unused Local</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_LOCAL">COMPILER_PB_UNUSED_LOCAL</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning for unused local variables (i.e. variables never read from)</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unused Parameter</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_PARAMETER">COMPILER_PB_UNUSED_PARAMETER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning for unused method parameters (i.e. parameters never read from)</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unused Parameter if Implementing Abstract Method</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_PARAMETER_WHEN_IMPLEMENTING_ABSTRACT">COMPILER_PB_UNUSED_PARAMETER_WHEN_IMPLEMENTING_ABSTRACT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, the compiler will signal unused parameters in
-  abstract method implementations.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unused Parameter if Overriding Concrete Method</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_PARAMETER_WHEN_OVERRIDING_CONCRETE">COMPILER_PB_UNUSED_PARAMETER_WHEN_OVERRIDING_CONCRETE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, the compiler will signal unused parameters in
-  methods overriding concrete ones.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unused Private Members </b>(<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_PRIVATE_MEMBER">COMPILER_PB_UNUSED_PRIVATE_MEMBER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning
-  whenever a private method or field is declared but never used within the same
-  unit. </td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Varargs Argument Needing a Cast in Method/Constructor Invocation </b>(<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_VARARGS_ARGUMENT_NEED_CAST">COMPILER_PB_VARARGS_ARGUMENT_NEED_CAST</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever a varargs arguments should be cast
-when passed to a method/constructor invocation. (e.g. Class.getMethod(String name, Class ... args )  
-invoked with arguments ("foo", null)).</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><b><i>WARNING</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Setting Source Compatibility Mode</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_SOURCE">COMPILER_SOURCE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Specify whether source is 1.3 or 1.4 compatible. From 1.4 on, 'assert' is a keyword reserved for assertion support. Also note, than when toggling to 1.4 mode, the target VM level should be set to "1.4" and the compliance mode should be "1.4".</td>
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_3">VERSION_1_3</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_4">VERSION_1_4</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Generating Source Debug Attribute</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_SOURCE_FILE_ATTR">COMPILER_SOURCE_FILE_ATTR</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When generated, this attribute will enable the debugger to present the corresponding source code.</td>
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#GENERATE">GENERATE</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_GENERATE">DO_NOT_GENERATE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Determine whether task tags are case-sensitive</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_TASK_CASE_SENSITIVE">COMPILER_TASK_CASE_SENSITIVE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, task tags are considered in a case-sensitive way.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED"><b><i>ENABLED</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Define the Automatic Task Priorities</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_TASK_PRIORITIES">COMPILER_TASK_PRIORITIES</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1><p>In parallel with the Automatic Task Tags, this list defines the
-  priorities (high, normal or low) of the task markers issued by the
-  compiler.</p><p>If the default is specified, the priority of each task marker
-  is &quot;NORMAL&quot;.</p>
-  <p>Possible priorities are "<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_TASK_PRIORITY_HIGH">HIGH</a>", "<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_TASK_PRIORITY_NORMAL">NORMAL</a>" or
-   "<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_TASK_PRIORITY_LOW">LOW</a>".</p></td>
-<td>{&lt;priority&gt;[,&lt;priority&gt;]*}.<br><b><i>Default value is "NORMAL,HIGH,<br>NORMAL"</i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Define the Automatic Task Tags</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_TASK_TAGS">COMPILER_TASK_TAGS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>When the tag is non empty, the compiler will issue a task marker
-  whenever it encounters one of the corresponding tag inside any comment in Java
-  source code.&nbsp; Generated task messages will include the tag, and range
-  until the next line separator or comment ending, and will be trimmed.</td>
-<td>{&lt;tag&gt;[,&lt;tag&gt;]*}.<br><b><i>Default value is "TODO,FIXME,<br>XXX"</i></b></td>
-</tr>
-</table>
-
-<H4><a name="builder">Builder options</a></h4>
-
-<table BORDER CELLSPACING=2 CELLPADDING=2 COLS=2 WIDTH="100%" >
-
-<tr>
-<th>Description</th>
-<th width=150>Values</th>
-</tr>
-
-<tr>
-<td colspan=2><b>Cleaning Output Folder(s)</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_JAVA_BUILD_CLEAN_OUTPUT_FOLDER">CORE_JAVA_BUILD_CLEAN_OUTPUT_FOLDER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Indicate whether the JavaBuilder is allowed to clean the output
-  folders when performing full build operations.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CLEAN"><b><i>CLEAN</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Duplicate Resources</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_JAVA_BUILD_DUPLICATE_RESOURCE">CORE_JAVA_BUILD_DUPLICATE_RESOURCE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Instruct the builder to abort if the classpath is invalid</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Abort if Invalid Classpath</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_JAVA_BUILD_INVALID_CLASSPATH">CORE_JAVA_BUILD_INVALID_CLASSPATH</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Instruct the builder to abort if the classpath is invalid</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ABORT">ABORT</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Computing Project Build Order</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_JAVA_BUILD_ORDER">CORE_JAVA_BUILD_ORDER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Indicate whether JavaCore should enforce the project build order to be based on the classpath prerequisite chain. When requesting to compute, this takes over the platform default order (based on project references).</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPUTE">COMPUTE</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Specifying Filters for Resource Copying Control</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_JAVA_BUILD_RESOURCE_COPY_FILTER">CORE_JAVA_BUILD_RESOURCE_COPY_FILTER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>Specify filters to control the resource copy process. (&lt;name&gt; is a file name pattern (only * wild-cards allowed) or the name of a folder which ends with '/')</td>
-<td>{&lt;name&gt;[,&lt;name&gt;]*}.<br><b><i>Default value is ""</i></b></td>
-</tr>
-
-</table>
-
-<H4><a name="javacore">JavaCore options</a></h4>
-
-<table BORDER CELLSPACING=2 CELLPADDING=2 COLS=2 WIDTH="100%" >
-
-<tr>
-<th>Description</th>
-<th width=120>Values</th>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Classpath Cycle</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_CIRCULAR_CLASSPATH">CORE_CIRCULAR_CLASSPATH</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Indicate the severity of the problem reported when a project is
-  involved in a cycle.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR"><b><i>ERROR</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Enabling Usage of Classpath Exclusion Patterns</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_ENABLE_CLASSPATH_EXCLUSION_PATTERNS">CORE_ENABLE_CLASSPATH_EXCLUSION_PATTERNS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When set to &quot;disabled&quot;, no entry on a project classpath
-  can be associated with an exclusion or inclusion pattern.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED"><b><i>ENABLED</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Enabling Usage of Classpath Multiple Output Locations</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_ENABLE_CLASSPATH_MULTIPLE_OUTPUT_LOCATIONS">CORE_ENABLE_CLASSPATH_MULTIPLE_OUTPUT_LOCATIONS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When set to &quot;disabled&quot;, no entry on a project classpath
-  can be associated with a specific output location, preventing thus usage of
-  multiple output locations</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED"><b><i>ENABLED</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Specify Default Source Encoding Format</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_ENCODING">CORE_ENCODING</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>Get the encoding format for compiled sources. This setting is read-only, it is equivalent to <a HREF="../../org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/resources/ResourcesPlugin.html#getEncoding()">ResourcesPlugin.getEncoding()</a>.</td>
-<td>any of the supported encoding name. <br><b><i>Default value is platform default</i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Incompatible JDK Level for Required Binaries</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_INCOMPATIBLE_JDK_LEVEL">CORE_INCOMPATIBLE_JDK_LEVEL</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>Indicate the severity of the problem reported when a project prerequisites another project 
-  or library with an incompatible target JDK level (e.g. project targeting 1.1 vm, but compiled against 1.4 libraries).</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><b><i>IGNORE</i></b></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Reporting Incomplete Classpath</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_INCOMPLETE_CLASSPATH">CORE_INCOMPLETE_CLASSPATH</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Indicate the severity of the problem reported when an entry on the
-  classpath doesn't exist, is not legitimate, or is not visible (e.g. a
-  referenced project is closed).</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR"><b><i>ERROR</i></b></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Set the timeout value for retrieving the method's parameter names from javadoc</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#TIMEOUT_FOR_PARAMETER_NAME_FROM_ATTACHED_JAVADOC">TIMEOUT_FOR_PARAMETER_NAME_FROM_ATTACHED_JAVADOC</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Timeout in milliseconds to retrieve the method's parameter names from javadoc.<br>If the value is 0, the parameter names are not fetched and the raw names are returned.</td>
-<td rowspan=2>A positive integer<br>Default is <b><i>"50"</i></b></td>
-</tr>
-</table>
-
-<H4><a name="formatter">Formatter options</a></h4>
-
-<table BORDER CELLSPACING=2 CELLPADDING=2 COLS=2 WIDTH="100%" >
-<tr>
-<th>Description</th>
-<th width=80>Values</th>
-</tr>
-<tr>
-<td colspan=2><b>Option to align type members of a type declaration on column</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGN_TYPE_MEMBERS_ON_COLUMNS">FORMATTER_ALIGN_TYPE_MEMBERS_ON_COLUMNS</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of arguments in allocation expression</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_ARGUMENTS_IN_ALLOCATION_EXPRESSION">FORMATTER_ALIGNMENT_FOR_ARGUMENTS_IN_ALLOCATION_EXPRESSION</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of arguments in enum constant</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_ARGUMENTS_IN_ENUM_CONSTANT">FORMATTER_ALIGNMENT_FOR_ARGUMENTS_IN_ENUM_CONSTANT</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of arguments in explicit constructor call</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_ARGUMENTS_IN_EXPLICIT_CONSTRUCTOR_CALL">FORMATTER_ALIGNMENT_FOR_ARGUMENTS_IN_EXPLICIT_CONSTRUCTOR_CALL</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of arguments in method invocation</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_ARGUMENTS_IN_METHOD_INVOCATION">FORMATTER_ALIGNMENT_FOR_ARGUMENTS_IN_METHOD_INVOCATION</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of arguments in qualified allocation expression</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_ARGUMENTS_IN_QUALIFIED_ALLOCATION_EXPRESSION">FORMATTER_ALIGNMENT_FOR_ARGUMENTS_IN_QUALIFIED_ALLOCATION_EXPRESSION</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of binary expression</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_BINARY_EXPRESSION">FORMATTER_ALIGNMENT_FOR_BINARY_EXPRESSION</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of compact if</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_COMPACT_IF">FORMATTER_ALIGNMENT_FOR_COMPACT_IF</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_ONE_PER_LINE, INDENT_BY_ONE)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of conditional expression</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_CONDITIONAL_EXPRESSION">FORMATTER_ALIGNMENT_FOR_CONDITIONAL_EXPRESSION</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_ONE_PER_LINE, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of enum constants</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_ENUM_CONSTANTS">FORMATTER_ALIGNMENT_FOR_ENUM_CONSTANTS</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_NO_SPLIT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of expressions in array initializer</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_EXPRESSIONS_IN_ARRAY_INITIALIZER">FORMATTER_ALIGNMENT_FOR_EXPRESSIONS_IN_ARRAY_INITIALIZER</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of multiple fields</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_MULTIPLE_FIELDS">FORMATTER_ALIGNMENT_FOR_MULTIPLE_FIELDS</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of parameters in constructor declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_PARAMETERS_IN_CONSTRUCTOR_DECLARATION">FORMATTER_ALIGNMENT_FOR_PARAMETERS_IN_CONSTRUCTOR_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of parameters in method declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_PARAMETERS_IN_METHOD_DECLARATION">FORMATTER_ALIGNMENT_FOR_PARAMETERS_IN_METHOD_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of selector in method invocation</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_SELECTOR_IN_METHOD_INVOCATION">FORMATTER_ALIGNMENT_FOR_SELECTOR_IN_METHOD_INVOCATION</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of superclass in type declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_SUPERCLASS_IN_TYPE_DECLARATION">FORMATTER_ALIGNMENT_FOR_SUPERCLASS_IN_TYPE_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_NEXT_SHIFTED, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of superinterfaces in enum declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_SUPERINTERFACES_IN_ENUM_DECLARATION">FORMATTER_ALIGNMENT_FOR_SUPERINTERFACES_IN_ENUM_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of superinterfaces in type declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_SUPERINTERFACES_IN_TYPE_DECLARATION">FORMATTER_ALIGNMENT_FOR_SUPERINTERFACES_IN_TYPE_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of throws clause in constructor declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_THROWS_CLAUSE_IN_CONSTRUCTOR_DECLARATION">FORMATTER_ALIGNMENT_FOR_THROWS_CLAUSE_IN_CONSTRUCTOR_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of throws clause in method declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_THROWS_CLAUSE_IN_METHOD_DECLARATION">FORMATTER_ALIGNMENT_FOR_THROWS_CLAUSE_IN_METHOD_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to add blank lines after the imports declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BLANK_LINES_AFTER_IMPORTS">FORMATTER_BLANK_LINES_AFTER_IMPORTS</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to add blank lines after the package declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BLANK_LINES_AFTER_PACKAGE">FORMATTER_BLANK_LINES_AFTER_PACKAGE</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to add blank lines at the beginning of the method body</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BLANK_LINES_AT_BEGINNING_OF_METHOD_BODY">FORMATTER_BLANK_LINES_AT_BEGINNING_OF_METHOD_BODY</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to add blank lines before a field declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BLANK_LINES_BEFORE_FIELD">FORMATTER_BLANK_LINES_BEFORE_FIELD</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to add blank lines before the first class body declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BLANK_LINES_BEFORE_FIRST_CLASS_BODY_DECLARATION">FORMATTER_BLANK_LINES_BEFORE_FIRST_CLASS_BODY_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to add blank lines before the imports declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BLANK_LINES_BEFORE_IMPORTS">FORMATTER_BLANK_LINES_BEFORE_IMPORTS</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to add blank lines before a member type declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BLANK_LINES_BEFORE_MEMBER_TYPE">FORMATTER_BLANK_LINES_BEFORE_MEMBER_TYPE</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to add blank lines before a method declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BLANK_LINES_BEFORE_METHOD">FORMATTER_BLANK_LINES_BEFORE_METHOD</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to add blank lines before a new chunk</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BLANK_LINES_BEFORE_NEW_CHUNK">FORMATTER_BLANK_LINES_BEFORE_NEW_CHUNK</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to add blank lines before the package declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BLANK_LINES_BEFORE_PACKAGE">FORMATTER_BLANK_LINES_BEFORE_PACKAGE</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to add blank lines between type declarations</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BLANK_LINES_BETWEEN_TYPE_DECLARATIONS">FORMATTER_BLANK_LINES_BETWEEN_TYPE_DECLARATIONS</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to position the braces of an annotation type declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BRACE_POSITION_FOR_ANNOTATION_TYPE_DECLARATION">FORMATTER_BRACE_POSITION_FOR_ANNOTATION_TYPE_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#END_OF_LINE"><b><i>END_OF_LINE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE">NEXT_LINE</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_SHIFTED">NEXT_LINE_SHIFTED</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_ON_WRAP">NEXT_LINE_ON_WRAP</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to position the braces of an anonymous type declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BRACE_POSITION_FOR_ANONYMOUS_TYPE_DECLARATION">FORMATTER_BRACE_POSITION_FOR_ANONYMOUS_TYPE_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#END_OF_LINE"><b><i>END_OF_LINE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE">NEXT_LINE</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_SHIFTED">NEXT_LINE_SHIFTED</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_ON_WRAP">NEXT_LINE_ON_WRAP</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to position the braces of an array initializer</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BRACE_POSITION_FOR_ARRAY_INITIALIZER">FORMATTER_BRACE_POSITION_FOR_ARRAY_INITIALIZER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#END_OF_LINE"><b><i>END_OF_LINE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE">NEXT_LINE</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_SHIFTED">NEXT_LINE_SHIFTED</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_ON_WRAP">NEXT_LINE_ON_WRAP</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to position the braces of a block</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BRACE_POSITION_FOR_BLOCK">FORMATTER_BRACE_POSITION_FOR_BLOCK</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#END_OF_LINE"><b><i>END_OF_LINE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE">NEXT_LINE</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_SHIFTED">NEXT_LINE_SHIFTED</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_ON_WRAP">NEXT_LINE_ON_WRAP</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to position the braces of a block in a case statement when the block is the first statement following</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BRACE_POSITION_FOR_BLOCK_IN_CASE">FORMATTER_BRACE_POSITION_FOR_BLOCK_IN_CASE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#END_OF_LINE"><b><i>END_OF_LINE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE">NEXT_LINE</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_SHIFTED">NEXT_LINE_SHIFTED</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_ON_WRAP">NEXT_LINE_ON_WRAP</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to position the braces of a constructor declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BRACE_POSITION_FOR_CONSTRUCTOR_DECLARATION">FORMATTER_BRACE_POSITION_FOR_CONSTRUCTOR_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#END_OF_LINE"><b><i>END_OF_LINE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE">NEXT_LINE</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_SHIFTED">NEXT_LINE_SHIFTED</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_ON_WRAP">NEXT_LINE_ON_WRAP</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to position the braces of an enum constant</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BRACE_POSITION_FOR_ENUM_CONSTANT">FORMATTER_BRACE_POSITION_FOR_ENUM_CONSTANT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#END_OF_LINE"><b><i>END_OF_LINE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE">NEXT_LINE</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_SHIFTED">NEXT_LINE_SHIFTED</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_ON_WRAP">NEXT_LINE_ON_WRAP</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to position the braces of an enum declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BRACE_POSITION_FOR_ENUM_DECLARATION">FORMATTER_BRACE_POSITION_FOR_ENUM_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#END_OF_LINE"><b><i>END_OF_LINE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE">NEXT_LINE</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_SHIFTED">NEXT_LINE_SHIFTED</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_ON_WRAP">NEXT_LINE_ON_WRAP</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to position the braces of a method declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BRACE_POSITION_FOR_METHOD_DECLARATION">FORMATTER_BRACE_POSITION_FOR_METHOD_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#END_OF_LINE"><b><i>END_OF_LINE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE">NEXT_LINE</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_SHIFTED">NEXT_LINE_SHIFTED</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_ON_WRAP">NEXT_LINE_ON_WRAP</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to position the braces of a switch statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BRACE_POSITION_FOR_SWITCH">FORMATTER_BRACE_POSITION_FOR_SWITCH</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#END_OF_LINE"><b><i>END_OF_LINE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE">NEXT_LINE</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_SHIFTED">NEXT_LINE_SHIFTED</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_ON_WRAP">NEXT_LINE_ON_WRAP</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to position the braces of a type declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BRACE_POSITION_FOR_TYPE_DECLARATION">FORMATTER_BRACE_POSITION_FOR_TYPE_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#END_OF_LINE"><b><i>END_OF_LINE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE">NEXT_LINE</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_SHIFTED">NEXT_LINE_SHIFTED</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_ON_WRAP">NEXT_LINE_ON_WRAP</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to control whether blank lines are cleared inside comments</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_CLEAR_BLANK_LINES">FORMATTER_COMMENT_CLEAR_BLANK_LINES</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE">TRUE</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE"><b><i>FALSE</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to control whether comments are formatted</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_FORMAT">FORMATTER_COMMENT_FORMAT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><b><i>TRUE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to control whether the header comment of a Java source file is formatted</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_FORMAT_HEADER">FORMATTER_COMMENT_FORMAT_HEADER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE">TRUE</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE"><b><i>FALSE</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to control whether HTML tags are formatted.</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_FORMAT_HTML">FORMATTER_COMMENT_FORMAT_HTML</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><b><i>TRUE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to control whether code snippets are formatted in comments</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_FORMAT_SOURCE">FORMATTER_COMMENT_FORMAT_SOURCE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><b><i>TRUE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to control whether description of Javadoc parameters are indented</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_INDENT_PARAMETER_DESCRIPTION">FORMATTER_COMMENT_INDENT_PARAMETER_DESCRIPTION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><b><i>TRUE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to control whether Javadoc root tags are indented.</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_INDENT_ROOT_TAGS">FORMATTER_COMMENT_INDENT_ROOT_TAGS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><b><i>TRUE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert an empty line before the Javadoc root tag block</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_INSERT_EMPTY_LINE_BEFORE_ROOT_TAGS">FORMATTER_COMMENT_INSERT_EMPTY_LINE_BEFORE_ROOT_TAGS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line after Javadoc root tag parameters</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_INSERT_NEW_LINE_FOR_PARAMETER">FORMATTER_COMMENT_INSERT_NEW_LINE_FOR_PARAMETER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to specify the line length for comments.</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_LINE_LENGTH">FORMATTER_COMMENT_LINE_LENGTH</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"80"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to compact else/if</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMPACT_ELSE_IF">FORMATTER_COMPACT_ELSE_IF</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><b><i>TRUE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to set the continuation indentation</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_CONTINUATION_INDENTATION">FORMATTER_CONTINUATION_INDENTATION</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"2"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to set the continuation indentation inside array initializer</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_CONTINUATION_INDENTATION_FOR_ARRAY_INITIALIZER">FORMATTER_CONTINUATION_INDENTATION_FOR_ARRAY_INITIALIZER</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"2"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to indent body declarations compare to its enclosing annotation declaration header</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INDENT_BODY_DECLARATIONS_COMPARE_TO_ANNOTATION_DECLARATION_HEADER">FORMATTER_INDENT_BODY_DECLARATIONS_COMPARE_TO_ANNOTATION_DECLARATION_HEADER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><b><i>TRUE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to indent body declarations compare to its enclosing enum constant header</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INDENT_BODY_DECLARATIONS_COMPARE_TO_ENUM_CONSTANT_HEADER">FORMATTER_INDENT_BODY_DECLARATIONS_COMPARE_TO_ENUM_CONSTANT_HEADER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><b><i>TRUE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to indent body declarations compare to its enclosing enum declaration header</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INDENT_BODY_DECLARATIONS_COMPARE_TO_ENUM_DECLARATION_HEADER">FORMATTER_INDENT_BODY_DECLARATIONS_COMPARE_TO_ENUM_DECLARATION_HEADER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><b><i>TRUE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to indent body declarations compare to its enclosing type header</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INDENT_BODY_DECLARATIONS_COMPARE_TO_TYPE_HEADER">FORMATTER_INDENT_BODY_DECLARATIONS_COMPARE_TO_TYPE_HEADER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><b><i>TRUE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to indent breaks compare to cases</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INDENT_BREAKS_COMPARE_TO_CASES">FORMATTER_INDENT_BREAKS_COMPARE_TO_CASES</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><b><i>TRUE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to indent statements inside a block</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INDENT_STATEMENTS_COMPARE_TO_BLOCK">FORMATTER_INDENT_STATEMENTS_COMPARE_TO_BLOCK</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><b><i>TRUE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to indent statements inside the body of a method or a constructor</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INDENT_STATEMENTS_COMPARE_TO_BODY">FORMATTER_INDENT_STATEMENTS_COMPARE_TO_BODY</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><b><i>TRUE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to indent switch statements compare to cases</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INDENT_SWITCHSTATEMENTS_COMPARE_TO_CASES">FORMATTER_INDENT_SWITCHSTATEMENTS_COMPARE_TO_CASES</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><b><i>TRUE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to indent switch statements compare to switch</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INDENT_SWITCHSTATEMENTS_COMPARE_TO_SWITCH">FORMATTER_INDENT_SWITCHSTATEMENTS_COMPARE_TO_SWITCH</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><b><i>TRUE</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to specify the equivalent number of spaces that represents one indentation</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INDENTATION_SIZE">FORMATTER_INDENTATION_SIZE</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"4"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line after an annotation</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_AFTER_ANNOTATION">FORMATTER_INSERT_NEW_LINE_AFTER_ANNOTATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line after the opening brace in an array initializer</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_AFTER_OPENING_BRACE_IN_ARRAY_INITIALIZER">FORMATTER_INSERT_NEW_LINE_AFTER_OPENING_BRACE_IN_ARRAY_INITIALIZER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line at the end of the current file if missing</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_AT_END_OF_FILE_IF_MISSING">FORMATTER_INSERT_NEW_LINE_AT_END_OF_FILE_IF_MISSING</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line before the catch keyword in try statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_BEFORE_CATCH_IN_TRY_STATEMENT">FORMATTER_INSERT_NEW_LINE_BEFORE_CATCH_IN_TRY_STATEMENT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line before the closing brace in an array initializer</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_BEFORE_CLOSING_BRACE_IN_ARRAY_INITIALIZER">FORMATTER_INSERT_NEW_LINE_BEFORE_CLOSING_BRACE_IN_ARRAY_INITIALIZER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line before the else keyword in if statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_BEFORE_ELSE_IN_IF_STATEMENT">FORMATTER_INSERT_NEW_LINE_BEFORE_ELSE_IN_IF_STATEMENT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line before the finally keyword in try statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_BEFORE_FINALLY_IN_TRY_STATEMENT">FORMATTER_INSERT_NEW_LINE_BEFORE_FINALLY_IN_TRY_STATEMENT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line before while in do statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_BEFORE_WHILE_IN_DO_STATEMENT">FORMATTER_INSERT_NEW_LINE_BEFORE_WHILE_IN_DO_STATEMENT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line in an empty annotation declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_IN_EMPTY_ANNOTATION_DECLARATION">FORMATTER_INSERT_NEW_LINE_IN_EMPTY_ANNOTATION_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line in an empty anonymous type declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_IN_EMPTY_ANONYMOUS_TYPE_DECLARATION">FORMATTER_INSERT_NEW_LINE_IN_EMPTY_ANONYMOUS_TYPE_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line in an empty block</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_IN_EMPTY_BLOCK">FORMATTER_INSERT_NEW_LINE_IN_EMPTY_BLOCK</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line in an empty enum constant</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_IN_EMPTY_ENUM_CONSTANT">FORMATTER_INSERT_NEW_LINE_IN_EMPTY_ENUM_CONSTANT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line in an empty enum declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_IN_EMPTY_ENUM_DECLARATION">FORMATTER_INSERT_NEW_LINE_IN_EMPTY_ENUM_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line in an empty method body</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_IN_EMPTY_METHOD_BODY">FORMATTER_INSERT_NEW_LINE_IN_EMPTY_METHOD_BODY</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line in an empty type declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_IN_EMPTY_TYPE_DECLARATION">FORMATTER_INSERT_NEW_LINE_IN_EMPTY_TYPE_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after and in wilcard</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_AND_IN_TYPE_PARAMETER">FORMATTER_INSERT_SPACE_AFTER_AND_IN_TYPE_PARAMETER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after an assignment operator</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_ASSIGNMENT_OPERATOR">FORMATTER_INSERT_SPACE_AFTER_ASSIGNMENT_OPERATOR</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after at in annotation</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_AT_IN_ANNOTATION">FORMATTER_INSERT_SPACE_AFTER_AT_IN_ANNOTATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after at in annotation type declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_AT_IN_ANNOTATION_TYPE_DECLARATION">FORMATTER_INSERT_SPACE_AFTER_AT_IN_ANNOTATION_TYPE_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after a binary operator</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_BINARY_OPERATOR">FORMATTER_INSERT_SPACE_AFTER_BINARY_OPERATOR</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the closing angle bracket in type arguments</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_CLOSING_ANGLE_BRACKET_IN_TYPE_ARGUMENTS">FORMATTER_INSERT_SPACE_AFTER_CLOSING_ANGLE_BRACKET_IN_TYPE_ARGUMENTS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the closing angle bracket in type parameters</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_CLOSING_ANGLE_BRACKET_IN_TYPE_PARAMETERS">FORMATTER_INSERT_SPACE_AFTER_CLOSING_ANGLE_BRACKET_IN_TYPE_PARAMETERS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the closing brace of a block</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_CLOSING_BRACE_IN_BLOCK">FORMATTER_INSERT_SPACE_AFTER_CLOSING_BRACE_IN_BLOCK</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the closing parenthesis of a cast expression</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_CLOSING_PAREN_IN_CAST">FORMATTER_INSERT_SPACE_AFTER_CLOSING_PAREN_IN_CAST</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the colon in an assert statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COLON_IN_ASSERT">FORMATTER_INSERT_SPACE_AFTER_COLON_IN_ASSERT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after colon in a case statement when a opening brace follows the colon</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COLON_IN_CASE">FORMATTER_INSERT_SPACE_AFTER_COLON_IN_CASE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the colon in a conditional expression</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COLON_IN_CONDITIONAL">FORMATTER_INSERT_SPACE_AFTER_COLON_IN_CONDITIONAL</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after colon in a for statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COLON_IN_FOR">FORMATTER_INSERT_SPACE_AFTER_COLON_IN_FOR</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the colon in a labeled statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COLON_IN_LABELED_STATEMENT">FORMATTER_INSERT_SPACE_AFTER_COLON_IN_LABELED_STATEMENT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in an allocation expression</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_ALLOCATION_EXPRESSION">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_ALLOCATION_EXPRESSION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in annotation</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_ANNOTATION">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_ANNOTATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in an array initializer</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_ARRAY_INITIALIZER">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_ARRAY_INITIALIZER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in the parameters of a constructor declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_CONSTRUCTOR_DECLARATION_PARAMETERS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_CONSTRUCTOR_DECLARATION_PARAMETERS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in the exception names in a throws clause of a constructor declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_CONSTRUCTOR_DECLARATION_THROWS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_CONSTRUCTOR_DECLARATION_THROWS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in the arguments of an enum constant</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_ENUM_CONSTANT_ARGUMENTS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_ENUM_CONSTANT_ARGUMENTS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in enum declarations</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_ENUM_DECLARATIONS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_ENUM_DECLARATIONS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in the arguments of an explicit constructor call</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_EXPLICIT_CONSTRUCTOR_CALL_ARGUMENTS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_EXPLICIT_CONSTRUCTOR_CALL_ARGUMENTS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in the increments of a for statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_FOR_INCREMENTS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_FOR_INCREMENTS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in the initializations of a for statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_FOR_INITS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_FOR_INITS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in the parameters of a method declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_METHOD_DECLARATION_PARAMETERS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_METHOD_DECLARATION_PARAMETERS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in the exception names in a throws clause of a method declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_METHOD_DECLARATION_THROWS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_METHOD_DECLARATION_THROWS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in the arguments of a method invocation</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_METHOD_INVOCATION_ARGUMENTS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_METHOD_INVOCATION_ARGUMENTS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in multiple field declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_MULTIPLE_FIELD_DECLARATIONS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_MULTIPLE_FIELD_DECLARATIONS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in multiple local declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_MULTIPLE_LOCAL_DECLARATIONS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_MULTIPLE_LOCAL_DECLARATIONS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in parameterized type reference</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_PARAMETERIZED_TYPE_REFERENCE">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_PARAMETERIZED_TYPE_REFERENCE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in superinterfaces names of a type header</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_SUPERINTERFACES">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_SUPERINTERFACES</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in type arguments</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_TYPE_ARGUMENTS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_TYPE_ARGUMENTS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in type parameters</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_TYPE_PARAMETERS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_TYPE_PARAMETERS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after ellipsis</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_ELLIPSIS">FORMATTER_INSERT_SPACE_AFTER_ELLIPSIS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening angle bracket in parameterized type reference</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_ANGLE_BRACKET_IN_PARAMETERIZED_TYPE_REFERENCE">FORMATTER_INSERT_SPACE_AFTER_OPENING_ANGLE_BRACKET_IN_PARAMETERIZED_TYPE_REFERENCE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening angle bracket in type arguments</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_ANGLE_BRACKET_IN_TYPE_ARGUMENTS">FORMATTER_INSERT_SPACE_AFTER_OPENING_ANGLE_BRACKET_IN_TYPE_ARGUMENTS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening angle bracket in type parameters</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_ANGLE_BRACKET_IN_TYPE_PARAMETERS">FORMATTER_INSERT_SPACE_AFTER_OPENING_ANGLE_BRACKET_IN_TYPE_PARAMETERS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening brace in an array initializer</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_BRACE_IN_ARRAY_INITIALIZER">FORMATTER_INSERT_SPACE_AFTER_OPENING_BRACE_IN_ARRAY_INITIALIZER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening bracket inside an array allocation expression</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_BRACKET_IN_ARRAY_ALLOCATION_EXPRESSION">FORMATTER_INSERT_SPACE_AFTER_OPENING_BRACKET_IN_ARRAY_ALLOCATION_EXPRESSION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening bracket inside an array reference</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_BRACKET_IN_ARRAY_REFERENCE">FORMATTER_INSERT_SPACE_AFTER_OPENING_BRACKET_IN_ARRAY_REFERENCE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in annotation</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_ANNOTATION">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_ANNOTATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in a cast expression</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_CAST">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_CAST</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in a catch</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_CATCH">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_CATCH</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in a constructor declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_CONSTRUCTOR_DECLARATION">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_CONSTRUCTOR_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in enum constant</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_ENUM_CONSTANT">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_ENUM_CONSTANT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in a for statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_FOR">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_FOR</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in an if statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_IF">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_IF</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in a method declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_METHOD_DECLARATION">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_METHOD_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in a method invocation</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_METHOD_INVOCATION">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_METHOD_INVOCATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in a parenthesized expression</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_PARENTHESIZED_EXPRESSION">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_PARENTHESIZED_EXPRESSION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in a switch statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_SWITCH">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_SWITCH</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in a synchronized statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_SYNCHRONIZED">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_SYNCHRONIZED</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in a while statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_WHILE">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_WHILE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after a postfix operator</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_POSTFIX_OPERATOR">FORMATTER_INSERT_SPACE_AFTER_POSTFIX_OPERATOR</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after a prefix operator</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_PREFIX_OPERATOR">FORMATTER_INSERT_SPACE_AFTER_PREFIX_OPERATOR</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after question mark in a conditional expression</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_QUESTION_IN_CONDITIONAL">FORMATTER_INSERT_SPACE_AFTER_QUESTION_IN_CONDITIONAL</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after question mark in a wildcard</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_QUESTION_IN_WILDCARD">FORMATTER_INSERT_SPACE_AFTER_QUESTION_IN_WILDCARD</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after semicolon in a for statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_SEMICOLON_IN_FOR">FORMATTER_INSERT_SPACE_AFTER_SEMICOLON_IN_FOR</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after an unary operator</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_UNARY_OPERATOR">FORMATTER_INSERT_SPACE_AFTER_UNARY_OPERATOR</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before and in wildcard</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_AND_IN_TYPE_PARAMETER">FORMATTER_INSERT_SPACE_BEFORE_AND_IN_TYPE_PARAMETER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before an assignment operator</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_ASSIGNMENT_OPERATOR">FORMATTER_INSERT_SPACE_BEFORE_ASSIGNMENT_OPERATOR</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before at in annotation type declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_AT_IN_ANNOTATION_TYPE_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_AT_IN_ANNOTATION_TYPE_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before an binary operator</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_BINARY_OPERATOR">FORMATTER_INSERT_SPACE_BEFORE_BINARY_OPERATOR</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing angle bracket in parameterized type reference</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_ANGLE_BRACKET_IN_PARAMETERIZED_TYPE_REFERENCE">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_ANGLE_BRACKET_IN_PARAMETERIZED_TYPE_REFERENCE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing angle bracket in type arguments</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_ANGLE_BRACKET_IN_TYPE_ARGUMENTS">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_ANGLE_BRACKET_IN_TYPE_ARGUMENTS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing angle bracket in type parameters</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_ANGLE_BRACKET_IN_TYPE_PARAMETERS">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_ANGLE_BRACKET_IN_TYPE_PARAMETERS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing brace in an array initializer</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_BRACE_IN_ARRAY_INITIALIZER">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_BRACE_IN_ARRAY_INITIALIZER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing bracket in an array allocation expression</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_BRACKET_IN_ARRAY_ALLOCATION_EXPRESSION">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_BRACKET_IN_ARRAY_ALLOCATION_EXPRESSION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing bracket in an array reference</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_BRACKET_IN_ARRAY_REFERENCE">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_BRACKET_IN_ARRAY_REFERENCE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in annotation</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_ANNOTATION">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_ANNOTATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in a cast expression</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_CAST">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_CAST</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in a catch</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_CATCH">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_CATCH</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in a constructor declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_CONSTRUCTOR_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_CONSTRUCTOR_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in enum constant</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_ENUM_CONSTANT">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_ENUM_CONSTANT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in a for statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_FOR">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_FOR</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in an if statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_IF">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_IF</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in a method declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_METHOD_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_METHOD_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in a method invocation</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_METHOD_INVOCATION">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_METHOD_INVOCATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in a parenthesized expression</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_PARENTHESIZED_EXPRESSION">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_PARENTHESIZED_EXPRESSION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in a switch statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_SWITCH">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_SWITCH</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in a synchronized statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_SYNCHRONIZED">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_SYNCHRONIZED</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in a while statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_WHILE">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_WHILE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before colon in an assert statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_ASSERT">FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_ASSERT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before colon in a case statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_CASE">FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_CASE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before colon in a conditional expression</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_CONDITIONAL">FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_CONDITIONAL</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before colon in a default statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_DEFAULT">FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_DEFAULT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before colon in a for statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_FOR">FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_FOR</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before colon in a labeled statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_LABELED_STATEMENT">FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_LABELED_STATEMENT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in an allocation expression</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_ALLOCATION_EXPRESSION">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_ALLOCATION_EXPRESSION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in annotation</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_ANNOTATION">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_ANNOTATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in an array initializer</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_ARRAY_INITIALIZER">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_ARRAY_INITIALIZER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in the parameters of a constructor declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_CONSTRUCTOR_DECLARATION_PARAMETERS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_CONSTRUCTOR_DECLARATION_PARAMETERS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in the exception names of the throws clause of a constructor declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_CONSTRUCTOR_DECLARATION_THROWS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_CONSTRUCTOR_DECLARATION_THROWS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in the arguments of enum constant</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_ENUM_CONSTANT_ARGUMENTS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_ENUM_CONSTANT_ARGUMENTS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in enum declarations</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_ENUM_DECLARATIONS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_ENUM_DECLARATIONS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in the arguments of an explicit constructor call</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_EXPLICIT_CONSTRUCTOR_CALL_ARGUMENTS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_EXPLICIT_CONSTRUCTOR_CALL_ARGUMENTS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in the increments of a for statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_FOR_INCREMENTS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_FOR_INCREMENTS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in the initializations of a for statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_FOR_INITS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_FOR_INITS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in the parameters of a method declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_METHOD_DECLARATION_PARAMETERS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_METHOD_DECLARATION_PARAMETERS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in the exception names of the throws clause of a method declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_METHOD_DECLARATION_THROWS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_METHOD_DECLARATION_THROWS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in the arguments of a method invocation</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_METHOD_INVOCATION_ARGUMENTS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_METHOD_INVOCATION_ARGUMENTS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in a multiple field declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_MULTIPLE_FIELD_DECLARATIONS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_MULTIPLE_FIELD_DECLARATIONS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in a multiple local declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_MULTIPLE_LOCAL_DECLARATIONS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_MULTIPLE_LOCAL_DECLARATIONS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in parameterized type reference</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_PARAMETERIZED_TYPE_REFERENCE">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_PARAMETERIZED_TYPE_REFERENCE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in the superinterfaces names in a type header</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_SUPERINTERFACES">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_SUPERINTERFACES</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in type arguments</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_TYPE_ARGUMENTS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_TYPE_ARGUMENTS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in type parameters</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_TYPE_PARAMETERS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_TYPE_PARAMETERS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before ellipsis</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_ELLIPSIS">FORMATTER_INSERT_SPACE_BEFORE_ELLIPSIS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening angle bracket in parameterized type reference</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_ANGLE_BRACKET_IN_PARAMETERIZED_TYPE_REFERENCE">FORMATTER_INSERT_SPACE_BEFORE_OPENING_ANGLE_BRACKET_IN_PARAMETERIZED_TYPE_REFERENCE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening angle bracket in type arguments</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_ANGLE_BRACKET_IN_TYPE_ARGUMENTS">FORMATTER_INSERT_SPACE_BEFORE_OPENING_ANGLE_BRACKET_IN_TYPE_ARGUMENTS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening angle bracket in type parameters</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_ANGLE_BRACKET_IN_TYPE_PARAMETERS">FORMATTER_INSERT_SPACE_BEFORE_OPENING_ANGLE_BRACKET_IN_TYPE_PARAMETERS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening brace in an annotation type declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_ANNOTATION_TYPE_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_ANNOTATION_TYPE_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening brace in an anonymous type declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_ANONYMOUS_TYPE_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_ANONYMOUS_TYPE_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening brace in an array initializer</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_ARRAY_INITIALIZER">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_ARRAY_INITIALIZER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening brace in a block</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_BLOCK">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_BLOCK</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening brace in a constructor declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_CONSTRUCTOR_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_CONSTRUCTOR_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening brace in an enum constant</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_ENUM_CONSTANT">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_ENUM_CONSTANT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening brace in an enum declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_ENUM_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_ENUM_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening brace in a method declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_METHOD_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_METHOD_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening brace in a switch statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_SWITCH">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_SWITCH</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening brace in a type declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_TYPE_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_TYPE_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening bracket in an array allocation expression</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACKET_IN_ARRAY_ALLOCATION_EXPRESSION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACKET_IN_ARRAY_ALLOCATION_EXPRESSION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening bracket in an array reference</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACKET_IN_ARRAY_REFERENCE">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACKET_IN_ARRAY_REFERENCE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening bracket in an array type reference</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACKET_IN_ARRAY_TYPE_REFERENCE">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACKET_IN_ARRAY_TYPE_REFERENCE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in annotation</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_ANNOTATION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_ANNOTATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in annotation type member declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_ANNOTATION_TYPE_MEMBER_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_ANNOTATION_TYPE_MEMBER_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in a catch</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_CATCH">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_CATCH</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in a constructor declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_CONSTRUCTOR_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_CONSTRUCTOR_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in enum constant</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_ENUM_CONSTANT">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_ENUM_CONSTANT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in a for statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_FOR">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_FOR</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in an if statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_IF">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_IF</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in a method declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_METHOD_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_METHOD_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in a method invocation</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_METHOD_INVOCATION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_METHOD_INVOCATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in a parenthesized expression</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_PARENTHESIZED_EXPRESSION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_PARENTHESIZED_EXPRESSION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in a switch statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_SWITCH">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_SWITCH</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in a synchronized statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_SYNCHRONIZED">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_SYNCHRONIZED</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in a while statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_WHILE">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_WHILE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before a postfix operator</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_POSTFIX_OPERATOR">FORMATTER_INSERT_SPACE_BEFORE_POSTFIX_OPERATOR</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before a prefix operator</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_PREFIX_OPERATOR">FORMATTER_INSERT_SPACE_BEFORE_PREFIX_OPERATOR</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before question mark in a conditional expression</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_QUESTION_IN_CONDITIONAL">FORMATTER_INSERT_SPACE_BEFORE_QUESTION_IN_CONDITIONAL</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><b><i>INSERT</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before question mark in a wildcard</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_QUESTION_IN_WILDCARD">FORMATTER_INSERT_SPACE_BEFORE_QUESTION_IN_WILDCARD</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before semicolon</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_SEMICOLON">FORMATTER_INSERT_SPACE_BEFORE_SEMICOLON</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before semicolon in for statement</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_SEMICOLON_IN_FOR">FORMATTER_INSERT_SPACE_BEFORE_SEMICOLON_IN_FOR</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before unary operator</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_UNARY_OPERATOR">FORMATTER_INSERT_SPACE_BEFORE_UNARY_OPERATOR</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space between brackets in an array type reference</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BETWEEN_BRACKETS_IN_ARRAY_TYPE_REFERENCE">FORMATTER_INSERT_SPACE_BETWEEN_BRACKETS_IN_ARRAY_TYPE_REFERENCE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space between empty braces in an array initializer</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_BRACES_IN_ARRAY_INITIALIZER">FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_BRACES_IN_ARRAY_INITIALIZER</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space between empty brackets in an array allocation expression</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_BRACKETS_IN_ARRAY_ALLOCATION_EXPRESSION">FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_BRACKETS_IN_ARRAY_ALLOCATION_EXPRESSION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space between empty parenthesis in an annotation type member declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_PARENS_IN_ANNOTATION_TYPE_MEMBER_DECLARATION">FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_PARENS_IN_ANNOTATION_TYPE_MEMBER_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space between empty parenthesis in a constructor declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_PARENS_IN_CONSTRUCTOR_DECLARATION">FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_PARENS_IN_CONSTRUCTOR_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space between empty parenthesis in enum constant</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_PARENS_IN_ENUM_CONSTANT">FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_PARENS_IN_ENUM_CONSTANT</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space between empty parenthesis in a method declaration</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_PARENS_IN_METHOD_DECLARATION">FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_PARENS_IN_METHOD_DECLARATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space between empty parenthesis in a method invocation</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_PARENS_IN_METHOD_INVOCATION">FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_PARENS_IN_METHOD_INVOCATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><b><i>DO_NOT_INSERT</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to keep else statement on the same line</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_KEEP_ELSE_STATEMENT_ON_SAME_LINE">FORMATTER_KEEP_ELSE_STATEMENT_ON_SAME_LINE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE">TRUE</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE"><b><i>FALSE</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to keep empty array initializer one one line</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_KEEP_EMPTY_ARRAY_INITIALIZER_ON_ONE_LINE">FORMATTER_KEEP_EMPTY_ARRAY_INITIALIZER_ON_ONE_LINE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE">TRUE</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE"><b><i>FALSE</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to keep guardian clause on one line</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_KEEP_GUARDIAN_CLAUSE_ON_ONE_LINE">FORMATTER_KEEP_GUARDIAN_CLAUSE_ON_ONE_LINE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE">TRUE</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE"><b><i>FALSE</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to keep simple if statement on the one line</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_KEEP_SIMPLE_IF_ON_ONE_LINE">FORMATTER_KEEP_SIMPLE_IF_ON_ONE_LINE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE">TRUE</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE"><b><i>FALSE</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to keep then statement on the same line</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_KEEP_THEN_STATEMENT_ON_SAME_LINE">FORMATTER_KEEP_THEN_STATEMENT_ON_SAME_LINE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE">TRUE</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE"><b><i>FALSE</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to specify the length of the page. Beyond this length, the formatter will try to split the code</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_LINE_SPLIT">FORMATTER_LINE_SPLIT</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"80"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to specify the number of empty lines to preserve</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_NUMBER_OF_EMPTY_LINES_TO_PRESERVE">FORMATTER_NUMBER_OF_EMPTY_LINES_TO_PRESERVE</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to specify whether or not empty statement should be on a new line</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_PUT_EMPTY_STATEMENT_ON_NEW_LINE">FORMATTER_PUT_EMPTY_STATEMENT_ON_NEW_LINE</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE">TRUE</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE"><b><i>FALSE</b></i></a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to specify the tabulation size</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_TAB_CHAR">FORMATTER_TAB_CHAR</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#TAB"><b><i>TAB</b></i></a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#SPACE">SPACE</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#MIXED">MIXED</a></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to specify the equivalent number of spaces that represents one tabulation</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_TAB_SIZE">FORMATTER_TAB_SIZE</a>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"4"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to use tabulations only for leading indentations</b> (<a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_USE_TABS_ONLY_FOR_LEADING_INDENTATIONS">FORMATTER_USE_TABS_ONLY_FOR_LEADING_INDENTATIONS</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE">TRUE</a></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE"><b><i>FALSE</b></i></a></td>
-</tr>
-</table>
-
-<H4><a name="codeassist">CodeAssist options</a></h4>
-
-<table BORDER CELLSPACING=2 CELLPADDING=2 COLS=2 WIDTH="100%" >
-<tr>
-<th>Description</th>
-<th width=80>Values</th>
-</tr>
-
-<tr>
-<td colspan=2><b>Define the Prefixes for Argument Name</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_ARGUMENT_PREFIXES">CODEASSIST_ARGUMENT_PREFIXES</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>When the prefixes is non empty, completion for argument name will
-  begin with one of the proposed prefixes.</td>
-<td>{&lt;prefix&gt;[,&lt;prefix&gt;]*}.<br><b><i>Default value is ""</i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Define the Suffixes for Argument Name</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_ARGUMENT_SUFFIXES">CODEASSIST_ARGUMENT_SUFFIXES</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>When the suffixes is non empty, completion for argument name will end
-  with one of the proposed suffixes.</td>
-<td>{&lt;suffix&gt;[,&lt;suffix&gt;]*}.<br><b><i>Default value is ""</i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Activate Discouraged Reference Sensitive Completion</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_DISCOURAGED_REFERENCE_CHECK">CODEASSIST_DISCOURAGED_REFERENCE_CHECK</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When active, completion doesn't show that have discouraged reference.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Define the Prefixes for Field Name</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_FIELD_PREFIXES">CODEASSIST_FIELD_PREFIXES</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>When the prefixes is non empty, completion for field name will
-  begin with one of the proposed prefixes.</td>
-<td>{&lt;prefix&gt;[,&lt;prefix&gt;]*}.<br><b><i>Default value is ""</i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Define the Suffixes for Field Name</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_FIELD_SUFFIXES">CODEASSIST_FIELD_SUFFIXES</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>When the suffixes is non empty, completion for field name will end
-  with one of the proposed suffixes.</td>
-<td>{&lt;suffix&gt;[,&lt;suffix&gt;]*}.<br><b><i>Default value is ""</i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Activate Forbidden Reference Sensitive Completion</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_FORBIDDEN_REFERENCE_CHECK">CODEASSIST_FORBIDDEN_REFERENCE_CHECK</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When active, completion doesn't show that have forbidden reference.</td>
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Automatic Qualification of Implicit Members</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_IMPLICIT_QUALIFICATION">CODEASSIST_IMPLICIT_QUALIFICATION</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When active, completion automatically qualifies completion on implicit field references and message expressions.</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Define the Prefixes for Local Variable Name</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_LOCAL_PREFIXES">CODEASSIST_LOCAL_PREFIXES</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>When the prefixes is non empty, completion for local variable name will
-  begin with one of the proposed prefixes.</td>
-<td>{&lt;prefix&gt;[,&lt;prefix&gt;]*}.<br><b><i>Default value is ""</i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Define the Suffixes for Local Variable Name</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_LOCAL_SUFFIXES">CODEASSIST_LOCAL_SUFFIXES</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>When the suffixes is non empty, completion for local variable name will end
-  with one of the proposed suffixes.</td>
-<td>{&lt;suffix&gt;[,&lt;suffix&gt;]*}.<br><b><i>Default value is ""</i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Define the Prefixes for Static Field Name</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_STATIC_FIELD_PREFIXES">CODEASSIST_STATIC_FIELD_PREFIXES</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>When the prefixes is non empty, completion for static field name will
-  begin with one of the proposed prefixes.</td>
-<td>{&lt;prefix&gt;[,&lt;prefix&gt;]*}.<br><b><i>Default value is ""</i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Define the Suffixes for Static Field Name</b> (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_STATIC_FIELD_SUFFIXES">CODEASSIST_STATIC_FIELD_SUFFIXES</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>When the suffixes is non empty, completion for static field name will end
-  with one of the proposed suffixes.</td>
-<td>{&lt;suffix&gt;[,&lt;suffix&gt;]*}.<br><b><i>Default value is ""</i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Activate Visibility Sensitive Completion</b>   (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_VISIBILITY_CHECK">CODEASSIST_VISIBILITY_CHECK</a>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When active, completion doesn't show that you can not see (e.g. you can not see private methods of a super class).</td>
-<td><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></i></b></td>
-</tr>
-
-</table>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_prompter.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_prompter.htm
deleted file mode 100644
index 6c6a50d..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_prompter.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Creating Java specific prompter dialogs</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h3>Creating Java specific prompter dialogs</h3>
-<p> The following snippet uses the <b><a href="../reference/api/org/eclipse/jdt/ui/JavaUI.html">JavaUI</a> </b>class to open the Open Type dialog:</p>
-<pre><font color="#4444cc">    public IType selectType() throws JavaModelException {
-        SelectionDialog dialog= JavaUI.createTypeDialog(
-            parent, new ProgressMonitorDialog(parent),
-            SearchEngine.createWorkspaceScope(),
-            IJavaElementSearchConstants.CONSIDER_ALL_TYPES, false);
-        dialog.setTitle(&quot;My Dialog Title&quot;);
-        dialog.setMessage(&quot;My Dialog Message&quot;);
-        if (dialog.open() == IDialogConstants.CANCEL_ID)
-            return null;
-
-        Object[] types= dialog.getResult();
-        if (types == null || types.length == 0)
-            return null;
-        return (IType)types[0];
-    }</font></pre>
-<p> <a href="../reference/api/org/eclipse/jdt/ui/JavaUI.html"><b>JavaUI</b></a> 
-  provides additional methods for creating Open Package and Open Main Type dialogs. 
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_render.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_render.htm
deleted file mode 100644
index d9b4cc5..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_render.htm
+++ /dev/null

@@ -1,115 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Presenting Java elements in a JFace viewer</title>
-</head>
-<body>
-<h2>Presenting Java elements in a JFace viewer</h2>
-<p> The JDT UI API provides classes that allow you to present the Java model or parts 
-  of it in a standard JFace viewer. This functionality is provided primarily by: 
-</p>
-<ul>
-  <li><a href="../reference/api/org/eclipse/jdt/ui/StandardJavaElementContentProvider.html"> 
-    <b> 
-    StandardJavaElementContentProvider</b></a>  - translates the Java element hierarchy 
-    into a data structure accessible by a tree, table or list viewer</li>
-  <li><a href="../reference/api/org/eclipse/jdt/ui/JavaElementLabelProvider.html"> 
-    <b> 
-    JavaElementLabelProvider</b></a>  - provides corresponding images and labels 
-    for a standard JFace viewer</li>
-	<li><a
-		href="../reference/api/org/eclipse/jdt/ui/JavaElementLabels.html">JavaElementLabels</a> - provides corresponding text labels for Java elements</li>
-</ul>
-<p>Content and label providers for JFace viewers are described in detail in <a href="../../org.eclipse.platform.doc.isv/guide/jface_viewers.htm" class="XRef">JFace
-viewers</a>.</p>
-If you understand the basic platform mechanism, then putting the Java content
-and label providers together is quite simple:
-<pre><font color="#4444cc">    ...
-    TreeViewer viewer= new TreeViewer(parent);
-    // Provide members of a compilation unit or class file, but no working copy elements
-    ITreeContentProvider contentProvider= new StandardJavaElementContentProvider(true, false);
-    viewer.setContentProvider(contentProvider);
-    // There are more flags defined in class JavaElementLabelProvider
-    ILabelProvider labelProvider= new JavaElementLabelProvider(
-        JavaElementLabelProvider.SHOW_DEFAULT |
-        JavaElementLabelProvider.SHOW_QUALIFIED |
-        JavaElementLabelProvider.SHOW_ROOT);
-    viewer.setLabelProvider(labelProvider);
-    // Using the Java model as the viewers input present Java projects on the first level.
-    viewer.setInput(JavaCore.create(ResourcesPlugin.getWorkspace().getRoot()));
-    ...</font></pre>
-<p>The example above uses aJava model (<a href="../reference/api/org/eclipse/jdt/core/IJavaModel.html"><b>IJavaModel</b></a>)
-as the input element for the viewer.&nbsp; The <a href="../reference/api/org/eclipse/jdt/ui/StandardJavaElementContentProvider.html"><b>StandardJavaElementContentProvider</b></a>
-also supports <a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html"><b> 
-      IJavaProject</b></a>, <a href="../reference/api/org/eclipse/jdt/core/IPackageFragmentRoot.html"><b> 
-      IPackageFragmentRoot</b></a>, <a href="../reference/api/org/eclipse/jdt/core/IPackageFragment.html"><b> 
-      IPackageFragment</b></a>, and <b>IFolder</b> as input elements: 
-</p>
-<h3>Overlaying images with Java information</h3>
-        <p><a href="../reference/api/org/eclipse/jdt/ui/JavaElementImageDescriptor.html"><b> 
-    JavaElementImageDescriptor</b></a> can be used to create an image based on an 
-    arbitrary base image descriptor and a set of flags specifying which Java specific 
-    adornments (e.g. static, final, synchronized, ....) are to be superimposed 
-    on the image.</p>
-<h3>Adding problem and override decorators</h3>
-When a viewer is supposed to include problem annotations, the JFace <b>DecoratingLabelProvider</b> 
-together with the <a href="../reference/api/org/eclipse/jdt/ui/ProblemsLabelDecorator.html"> 
-<b> 
-ProblemsLabelDecorator</b></a> is used. The snippet below illustrates the use of
-a problem label decorator.
-<pre><font color="#4444cc">    ...
-    DecoratingLabelProvider decorator= new DecoratingLabelProvider(labelProvider, new ProblemsLabelDecorator());
-    viewer.setLabelProvider(decorator);
-    ...</font></pre>
-<p> In the same way the <a href="../reference/api/org/eclipse/jdt/ui/OverrideIndicatorLabelDecorator.html"> 
-  <b> 
-  OverrideIndicatorLabelDecorator</b></a> can be used to decorate a normal label provider 
-  to show the implement and override indicators for methods. </p>
-<h3>Updating the presentation on model changes</h3>
-<p> Neither the <a href="../reference/api/org/eclipse/jdt/ui/OverrideIndicatorLabelDecorator.html"><b> 
-  OverrideIndicatorLabelDecorator</b></a><b> </b>nor the <a href="../reference/api/org/eclipse/jdt/ui/ProblemsLabelDecorator.html"><b> 
-ProblemsLabelDecorator</b></a><b> </b>listen to model changes. Hence, the viewer doesn't update its presentation if 
-  the Java or resource marker model changes. The reason for pushing the update 
-  onto the client for these classes is that there isn't yet a generic implementation 
-  that fulfills all performance concerns. Handling Java model delta inspection 
-  and viewer refreshing in each label decorator or provider would lead to multiple 
-  delta inspections and unnecessary viewer updates.</p>
-<p> So what does the client need to do in order to update their viewers ?</p>
-<ul>
-  <li><a href="../reference/api/org/eclipse/jdt/ui/OverrideIndicatorLabelDecorator.html"><b> 
-  OverrideIndicatorLabelDecorator</b></a>: the client must listen to 
-    Java model changes (see <a href="jdt_api_manip.htm#javadeltas">Responding to
-    changes in Java elements</a>) 
-    and decide if the change(s) described by the delta invalidates the override 
-    indicator of elements presented in the viewer. If so, the class inspecting 
-    the delta should trigger a repaint of the corresponding Java elements using 
-    the standard JFace viewer API (see update methods on StructuredViewer).</li>
-  <li><a href="../reference/api/org/eclipse/jdt/ui/ProblemsLabelDecorator.html"><b> 
-ProblemsLabelDecorator</b></a>: the client should listen to changes 
-    notified by the decorator via a <a href="../reference/api/org/eclipse/jdt/ui/ProblemsLabelDecorator.ProblemsLabelChangedEvent.html"> 
-    <b> 
-    ProblemsLabelChangedEvent</b></a> (see also <a href="../reference/api/org/eclipse/jdt/ui/ProblemsLabelDecorator.html#addListener(org.eclipse.jface.viewers.ILabelProviderListener)"> 
-    <b> 
-    ProblemsLabelDecorator.addListener</b></a> ). Since the marker model is resource 
-    based, the listener has to map the resource notifications to its underlying 
-    data model. For an example showing how to do this for viewers presenting Java 
-    elements see the internal classes <code>ProblemTreeViewer.handleLabelProviderChanged.</code></li>
-</ul>
-<p> For the same reasons enumerated for label decorators the <a href="../reference/api/org/eclipse/jdt/ui/StandardJavaElementContentProvider.html"><b>StandardJavaElementContentProvider</b></a><b>
-</b>doesn't listen to model changes. If the viewer needs to update its presentation 
-  according to Java model changes, then the client should add a corresponding 
-  listener to JavaCore. If the change described by the delta invalidates the structure 
-  of the elements presented in the viewer then the client should update the viewer 
-  using the standard JFace API (see refresh methods on StructuredViewer, and the 
-  add and remove methods on TableViewer and AbstractTreeViewer). </p>
-<h3>Sorting the viewer</h3>
-<p> <a href="../reference/api/org/eclipse/jdt/ui/JavaElementSorter.html"><b> 
-    JavaElementSorter</b></a> can be plugged into a JFace viewer to sort Java elements 
-    according to the Java UI sorting style. </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_run.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_run.htm
deleted file mode 100644
index 36c2128..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_run.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-     
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-     
-  <meta http-equiv="Content-Style-Type" content="text/css">
-      
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-  <title>Running a Java program</title>
-          
-  <link rel="stylesheet" type="text/css" href="../book.css">
-</head>
- <body>
-<h2>Running a Java program</h2>
-<p> The JDT Debug component includes facilities for launching a Java program using the 
-VM install that is currently configured by the user for a Java project.&nbsp;&nbsp;</p>
-<h3> Launching a compiled Java program</h3>
-<p> Java programs that have been compiled in a Java project can be run by 
-getting the appropriate <a href="../reference/api/org/eclipse/jdt/launching/IVMRunner.html"><b>
- IVMRunner</b></a>
-  for the Java project and running the class by name. The following code
-snippet shows how the class <b>MyClass</b> inside <b>myJavaProject</b> can
-be launched.</p>
-<font color="#4444cc">
-<pre>   IVMInstall vmInstall = JavaRuntime.getVMInstall(myJavaProject);
-   if (vmInstall == null)
-      vmInstall = JavaRuntime.getDefaultVMInstall();
-   if (vmInstall != null) {
-      IVMRunner vmRunner = vmInstall.getVMRunner(ILaunchManager.RUN_MODE);
-      if (vmRunner != null) {
-         String[] classPath = null;
-         try {
-            classPath = JavaRuntime.computeDefaultRuntimeClassPath(myJavaProject);
-         } catch (CoreException e) { }
-         if (classPath != null) {
-            VMRunnerConfiguration vmConfig = 
-               new VMRunnerConfiguration(&quot;MyClass&quot;, classPath);
-            ILaunch launch = new Launch(null, ILaunchManager.RUN_MODE, null);
-            vmRunner.run(vmConfig, launch, null);
-         }
-      }
-   }
-</pre>
-</font>
-<p> Another way to launch a Java program is to create a <b>Java application</b>
-  launch configuration, and launch it. The following snippet shows how the 
-class <b>MyClass</b> inside <b> myJavaProject</b> can be launched using a 
-simple launch configuration. By default, the resulting running application
- uses the JRE and classpath associated with <b>myJavaProject</b>. </p>
-<font color="#4444cc">
-<pre>   ILaunchManager manager = DebugPlugin.getDefault().getLaunchManager();
-   ILaunchConfigurationType type = manager.getLaunchConfigurationType(IJavaLaunchConfigurationConstants.ID_JAVA_APPLICATION);
-   ILaunchConfigurationWorkingCopy wc = type.newInstance(null, &quot;SampleConfig&quot;);
-   wc.setAttribute(IJavaLaunchConfigurationConstants.ATTR_PROJECT_NAME, &quot;myJavaProject&quot;);
-   wc.setAttribute(IJavaLaunchConfigurationConstants.ATTR_MAIN_TYPE_NAME, &quot;myClass&quot;);
-   ILaunchConfiguration config = wc.doSave();	
-   config.launch(ILaunchManager.RUN_MODE, null);
-</pre>
-</font>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_search.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_search.htm
deleted file mode 100644
index c8d56e3..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_search.htm
+++ /dev/null

@@ -1,178 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><html><head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"><title>Using the Java search engine</title>
-
-
-<link rel="stylesheet" type="text/css" href="../book.css"></head>
-<body>
-<h2>Using the Java search engine</h2>
-<p> Your plug-in can use the JDT API to search Java projects in the workspace
-for Java elements, such as method references, field declarations, implementors
-of an interface, etc. </p>
-<p>
-The entry point for Java search is the <b><a href="../reference/api/org/eclipse/jdt/core/search/SearchEngine.html">SearchEngine</a></b> class. You can search for particular
-patterns inside a Java element and scope the search to specific elements.&nbsp;
-Search patterns can be created using <b><a href="../reference/api/org/eclipse/jdt/core/search/SearchPattern.html#createPattern(org.eclipse.jdt.core.IJavaElement, int)">createPattern</a></b>.&nbsp;
-A pattern is scoped using <b><a href="../reference/api/org/eclipse/jdt/core/search/SearchEngine.html#createJavaSearchScope(org.eclipse.jdt.core.IJavaElement[])">createJavaSearchScope</a></b>.&nbsp;
-Once a pattern and scope are defined, the <b><a href="../reference/api/org/eclipse/jdt/core/search/SearchEngine.html#search(org.eclipse.jdt.core.search.SearchPattern, org.eclipse.jdt.core.search.SearchParticipant[], org.eclipse.jdt.core.search.IJavaSearchScope, org.eclipse.jdt.core.search.SearchRequestor, org.eclipse.core.runtime.IProgressMonitor)">search</a></b>
- method is used to collect the results. </p>
-
-<p>
-Search results are reported to a  <b><a href="../reference/api/org/eclipse/jdt/core/search/SearchRequestor.html">SearchRequestor</a></b> which you must
-extend in order to access the results. </p>
-
-<h3>
-Preparing for search</h3>
-<p> A search operation will use both a pattern for describing the nature
-of the search, and a scope for restraining the range of investigation. </p>
-
-<h4>
-Creating a Java search pattern
-</h4>
-<p>
-A search pattern defines how search results are found. You can either create a search pattern from a Java element (see
-<b><a href="../reference/api/org/eclipse/jdt/core/search/SearchPattern.html#createPattern(org.eclipse.jdt.core.IJavaElement, int)">createPatternPattern(IJavaElement, int)</a></b>) 
-or from a string (see <b><a href="../reference/api/org/eclipse/jdt/core/search/SearchPattern.html#createPattern(java.lang.String, int, int, int)">createPattern(String, int, int, int)</a></b>.)
-The last method supports wildcards (i.e. '*') and can be used to widen the search results.</p>
-<p>
-For example, creating a search pattern for searching for references to a given method is done as follows:</p>
-<font color="#4444cc"><pre>
-    // Get the method
-    IMethod method = ...;
-    
-    // Create search pattern
-    SearchPattern pattern = SearchPattern.createPattern(method, IJavaSearchConstants.REFERENCES);
-</pre></font>
-<p>
-Or creating a search pattern for searching for declarations of all types starting with "Obj":</p>
-<font color="#4444cc"><pre>
-    // Create search pattern
-    SearchPattern pattern = SearchPattern.createPattern(&quot;Obj*&quot;, IJavaSearchConstants.TYPE, IJavaSearchConstants.DECLARATIONS, SearchPattern.R_PATTERN_MATCH | SearchPattern.R_CASE_SENSITIVE);
-</pre></font>
-<p>
-The following search patterns are supported:
-</p><ul>
-<li>Package declarations</li>
-<li>Type declarations</li>
-<li>Field declarations</li>
-<li>Method (and constructor) declarations</li>
-<li>Package references</li>
-<li>Type references</li>
-<li>Interface implementors</li>
-<li>Field references</li>
-<li>Field write accesses</li>
-<li>Field read accesses</li>
-<li>Method (and constructor) references</li>
-<li>Combinations of the above patterns using the OR pattern (see
-<b><a href="../reference/api/org/eclipse/jdt/core/search/SearchPattern.html#createOrPattern(org.eclipse.jdt.core.search.SearchPattern, org.eclipse.jdt.core.search.SearchPattern)">createOrPattern</a></b>)</li>
-</ul>
-
-
-<h4>
-Creating a Java search scope
-</h4>
-<p>
-If you are interested in search results in a given project or even in a given package, or if you know that search results
-can be only in a hierarchy of a given type, you can create the appropriate search scope using 
-<b><a href="../reference/api/org/eclipse/jdt/core/search/SearchEngine.html#createJavaSearchScope(org.eclipse.jdt.core.IJavaElement[])">createJavaSearchScope(IJavaElement[])</a></b>
-or <b><a href="../reference/api/org/eclipse/jdt/core/search/SearchEngine.html#createHierarchyScope(org.eclipse.jdt.core.IType)">createHierarchyScope(IType)</a></b>.</p>
-<p>
-For example, creating a search scope on a given package is done as follows:</p>
-<font color="#4444cc"><pre>
-    // Get the package
-    IPackageFragment pkg = ...;
-
-    // Create search scope
-    IJavaSearchScope scope = SearchEngine.createJavaSearchScope(new IJavaElement[] {pkg});
-</pre></font>
-<p>
-Or creating a search scope on the hierarchy of a given type is:</p>
-<font color="#4444cc"><pre>
-    // Get the type
-    IType type = ...;
-
-    // Create search scope
-    IJavaSearchScope scope = SearchEngine.createHierarchyScope(type);
-</pre></font>
-<p>
-Finally, you can create a search scope on the entire workspace:</p>
-<font color="#4444cc"><pre>
-    // Create search scope
-    IJavaSearchScope scope = SearchEngine.createWorkspaceScope();
-</pre></font>
-
-<h3>
-Searching</h3>
-<p>
-Once you have created a search pattern and a search scope, and you have extended 
-<b><a href="../reference/api/org/eclipse/jdt/core/search/SearchRequestor.html">SearchRequestor</a></b>,
-you can start a search query as follows: </p>
-<font color="#4444cc"><pre>
-    // Get the search pattern
-    SearchPattern pattern = ...;
-
-    // Get the search scope
-    IJavaSearchScope scope = ...;
-
-    // Get the search requestor
-    SearchRequestor requestor = ...;
-
-    // Search
-    SearchEngine searchEngine = new SearchEngine();
-    searchEngine.search(pattern, new SearchParticipant[] {SearchEngine.getDefaultSearchParticipant()}, scope, requestor, null);
-</pre></font>
-<p>
-A notification that the search starts is sent to your search requestor using the
-<b><a href="../reference/api/org/eclipse/jdt/core/search/SearchRequestor.html#beginReporting()">beginReporting</a></b>
-method. &nbsp;Then, each search result is reported using the 
-<b><a href="../reference/api/org/eclipse/jdt/core/search/SearchRequestor.html#acceptSearchMatch(org.eclipse.jdt.core.search.SearchMatch)">acceptSearchMatch</a></b>
-method. Finally 
-<b><a href="../reference/api/org/eclipse/jdt/core/search/SearchRequestor.html#endReporting()">endReporting</a></b>
-indicates that the search has ended.</p>
-
-<h3>
-Collecting search results</h3>
-<p>
-Search results are reported using the 
-<b><a href="../reference/api/org/eclipse/jdt/core/search/SearchRequestor.html#acceptSearchMatch(org.eclipse.jdt.core.search.SearchMatch)">acceptSearchMatch</a></b>
-method. Paragraphs below detail the search match. </p>
-
-<h4>
-Resources and Java elements</h4>
-<p>
-A search result can correspond to a Java element (e.g. a type declaration) or it can be contained in a Java element
-(e.g. a reference to a type inside a method). The search engine always tries to find the innermost Java element that
-corresponds to or that contains the search result. For example, searching for references to a method could find
-such a reference in an initializer. The initializer that contains this method reference is the element of the search match. </p>
-<p>
-The search engine also tries to find the resource that contains the Java element. So if the Java
-element is a method in a compilation unit, the resource is the corresponding 
-<a HREF="../../org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/resources/IFile.html"><b>IFile</b></a>. 
-If the element is contained in a .jar file, the resource is the .jar file, if this .jar file is in the workspace. If it is an external 
-.jar file, then the resource is <b>null</b>. </p>
-
-<h4>
-Source positions</h4>
-<p> Source positions are given relative to the compilation unit that contains
-the search result. If the search result is contained in  a .jar file, the
-source positions are relative to the attached source. They are (-1, -1) if
-there is no source attached to  the .jar file. </p>
-
-<h4>
-Accurate versus inaccurate search results</h4>
-<p>
-In most cases search results are accurate, meaning that the search engine was able to determine that the given
-match is what was asked for. However in some cases the search engine is unable to do so, in such cases the match is
-inaccurate. Some possible reasons why a match could be inaccurate are:
-</p><ul>
-<li>The classpath on the project that contains the result is not properly set. For example, it refers to a project that is
-      not accessible, a jar on the classpath requires another jar that is not on the classpath, etc.</li>
-<li>The user code would not compile. For example, it refers to a class that is not yet defined.</li>
-</ul> 
-
-
-
-</body></html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_utility.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_utility.htm
deleted file mode 100644
index 0757581..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_utility.htm
+++ /dev/null

@@ -1,19 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>JavaUI utilities</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2>JavaUI utilities</h2>
-<p><a href="../reference/api/org/eclipse/jdt/ui/JavaUI.html"><b>JavaUI</b></a> 
-    is the main access point to the Java user interface components. It allows 
-    you to programmatically open editors on Java elements, open a Java or Java 
-    Browsing perspective,&nbsp; and open package and type prompter dialogs. </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_wizards.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_wizards.htm
deleted file mode 100644
index 34a81da..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_wizards.htm
+++ /dev/null

@@ -1,163 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Java wizard pages</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2>Java wizard pages</h2>
-<p> The <a href="../reference/api/org/eclipse/jdt/ui/wizards/package-summary.html"><b>org.eclipse.jdt.ui.wizards</b></a> 
-  package provides wizard pages for creating and configuring Java
-elements.&nbsp; Several
-prefabricated pages are provided for your use.</p>
-<h3> Configuring Java build settings</h3>
-<p><a href="../reference/api/org/eclipse/jdt/ui/wizards/JavaCapabilityConfigurationPage.html"><b>JavaCapabilityConfigurationPage</b></a> supports editing the Java build settings 
-    (source folder setup, referenced projects and, referenced and exported libraries).&nbsp;&nbsp;</p>
-<p>If you need to provide a wizard that configures a project for your plug-in
-while also configuring it with the Java nature and other Java project
-capabilities, you should use this page (rather than subclassing <a href="../reference/api/org/eclipse/jdt/ui/wizards/NewJavaProjectWizardPage.html"><b>NewJavaProjectWizardPage</b></a>).</p>
-<h3><b>Creating new Java elements</b></h3>
-<p>A hierarchy of wizard pages support the creation of new Java
-elements.&nbsp;&nbsp;</p>
-<p><a href="../reference/api/org/eclipse/jdt/ui/wizards/NewElementWizardPage.html"><b>NewElementWizardPage</b></a>
-is the abstract class that defines the basic operation of the wizard.&nbsp;
-Additional abstract classes are provided in the hierarchy for making
-customizations to the functionality provided by the concrete wizards.</p>
-<p>The concrete creation wizards can be used directly and generally are not
-intended to be subclassed.&nbsp;</p>
-<ul>
-  <li> 
-    <a href="../reference/api/org/eclipse/jdt/ui/wizards/NewClassWizardPage.html"><b>NewClassWizardPage</b></a>
-    allows users to define a new Java class. To customize the behavior for
-    this wizard, you should subclass <a href="../reference/api/org/eclipse/jdt/ui/wizards/NewTypeWizardPage.html"><b>NewTypeWizardPage</b></a>.</li>
-  <li> 
-    <a href="../reference/api/org/eclipse/jdt/ui/wizards/NewInterfaceWizardPage.html"><b>NewInterfaceWizardPage</b></a>
-    allows users to define a new Java interface. To customize the behavior
-    for this wizard, you should subclass <a href="../reference/api/org/eclipse/jdt/ui/wizards/NewTypeWizardPage.html"><b>NewTypeWizardPage</b></a>.</li>
-  <li> 
-    <a href="../reference/api/org/eclipse/jdt/ui/wizards/NewEnumWizardPage.html"><b>NewEnumWizardPage</b></a>
-    allows users to define a new Java enumeration.&nbsp;To customize the behavior
-    for this wizard, you should subclass <a
-		href="../reference/api/org/eclipse/jdt/ui/wizards/NewTypeWizardPage.html"><b>NewTypeWizardPage</b></a>.</li>
-  <li> 
-    <a href="../reference/api/org/eclipse/jdt/ui/wizards/NewAnnotationWizardPage.html"><b>NewAnnotationWizardPage</b></a>
-    allows users to define a new Java annotations.&nbsp;To customize the behavior
-    for this wizard, you should subclass <a
-		href="../reference/api/org/eclipse/jdt/ui/wizards/NewTypeWizardPage.html"><b>NewTypeWizardPage</b></a>.</li>
-	<li>
-	 <a href="../reference/api/org/eclipse/jdt/ui/wizards/NewJavaProjectWizardPage.html"><b>NewJavaProjectWizardPage</b></a>
-	allows users to create a new Java project.&nbsp; To create a different
-	kind of project with Java capabilities, you should use <a
-		href="../reference/api/org/eclipse/jdt/ui/wizards/JavaCapabilityConfigurationPage.html"><b>JavaCapabilityConfigurationPage</b></a>
-	<b> </b>where possible rather than subclassing this class.</li>
-	<li> 
-    <a href="../reference/api/org/eclipse/jdt/ui/wizards/NewPackageWizardPage.html"><b>NewPackageWizardPage</b></a>
-    allows users to create a new Java package. To customize the behavior for
-    this wizard, you should subclass <a href="../reference/api/org/eclipse/jdt/ui/wizards/NewContainerWizardPage.html"><b>NewContainerWizardPage</b></a>
-    rather than this class.&nbsp;</li>
-</ul>
-<h3>Contributing a classpath container wizard page</h3>
-<p>The interface <a href="../reference/api/org/eclipse/jdt/ui/wizards/IClasspathContainerPage.html"><b>IClasspathContainerPage</b></a>
-defines a structure for contributing a wizard page that allows a user to define
-a new classpath container entry or edit an existing one.&nbsp; If your plug-in
-has defined its own type of classpath container using the JDT Core <b><a href="../reference/extension-points/org_eclipse_jdt_core_classpathContainerInitializer.html">org.eclipse.jdt.core.classpathContainerInitializer</a></b>
- extension point, then you will probably want to define a corresponding wizard
-page for editing and creating classpath containers of this type.</p>
-<p>Your plug-in's markup should provide an extension <b><a href="../reference/extension-points/org_eclipse_jdt_core_classpathContainerInitializer.html">org.eclipse.jdt.ui.classpathContainerPage</a>.&nbsp;
-</b>In the extension markup, you provide the name of your class that implements <a href="../reference/api/org/eclipse/jdt/ui/wizards/IClasspathContainerPage.html"><b>IClasspathContainerPage</b></a>.&nbsp;
-If you want to provide additional information in your wizard page about a
-classpath's context when it is selected, you can implement <a href="../reference/api/org/eclipse/jdt/ui/wizards/IClasspathContainerPageExtension.html"><b>IClasspathContainerPageExtension</b></a><b>
-</b>to initialize any state that depends on the entries selected in the current
-classpath.</p>
-<h3> Customizing a wizard page</h3>
-<p> Besides using 
-  prefabricated pages, you can subclass the wizard pages to 
-  add your own input fields or to influence the code generation.&nbsp; You
-should use the abstract classes in the <a href="../reference/api/org/eclipse/jdt/ui/wizards/NewElementWizardPage.html"><b>NewElementWizardPage</b></a><b>
-</b>hierarchy to customize a wizard rather than subclassing the concrete
-classes.</p>
-<p> Below is a sample 
-  of a new type wizard page that is customized to create JUnit test case classes. 
-  The page initializes the super class field with &quot;junit.framework.TestCase&quot; 
-  and adds a checkbox that controls whether method stubs for the <code>setUp()</code> and <code>tearDown()</code>
-  method are to be created.</p>
-<pre><font color="#4444CC">public class TestCaseWizardPage extends NewTypeWizardPage {
-    private Button fCreateStubs;
-
-    public TestCaseWizardPage() {
-        super(true, &quot;TestCaseWizardPage&quot;);
-    }
-
-    /**
-     * The wizard managing this wizard page must call this method
-     * during initialization with a corresponding selection.
-     */   
-    public void init(IStructuredSelection selection) {
-        IJavaElement jelem= getInitialJavaElement(selection);
-        initContainerPage(jelem);
-        initTypePage(jelem);
-        doStatusUpdate();
-    }
-
-    private void doStatusUpdate() {
-        // define the components for which a status is desired
-        IStatus[] status= new IStatus[] {
-            fContainerStatus,
-            isEnclosingTypeSelected() ? fEnclosingTypeStatus : fPackageStatus,
-            fTypeNameStatus,
-        };
-        updateStatus(status);
-    }
-
-
-    protected void handleFieldChanged(String fieldName) {
-        super.handleFieldChanged(fieldName);
-
-        doStatusUpdate();
-    }
-	
-    public void createControl(Composite parent) {
-        initializeDialogUnits(parent);
-        Composite composite= new Composite(parent, SWT.NONE);
-        int nColumns= 4;
-        GridLayout layout= new GridLayout();
-        layout.numColumns= nColumns;
-        composite.setLayout(layout);
-
-        // Create the standard input fields
-        createContainerControls(composite, nColumns);
-        createPackageControls(composite, nColumns);
-        createSeparator(composite, nColumns);
-        createTypeNameControls(composite, nColumns);
-        createSuperClassControls(composite, nColumns);
-
-        // Create the checkbox controlling whether we want stubs
-        fCreateStubs= new Button(composite, SWT.CHECK);
-        fCreateStubs.setText(&quot;Add 'setUp()' and 'tearDown()' to new class&quot;);
-        GridData gd= new GridData();
-        gd.horizontalSpan= nColumns;
-        fCreateStubs.setLayoutData(gd);
-
-        setControl(composite);
-
-        // Initialize the super type field and mark it as read-only
-        setSuperClass(&quot;junit.framework.TestCase&quot;, false);
-    }
-
-    protected void createTypeMembers(IType newType, ImportsManager imports, IProgressMonitor monitor) throws CoreException {
-        if (fCreateStubs.getSelection()) {
-            String setUpMathod= &quot;public void setUp() {}&quot;;
-            newType.createMethod(setUpMathod, null, false, null);
-
-            String tearDownMathod= &quot;public void setUp() {}&quot;;
-            newType.createMethod(tearDownMathod, null, false, null); 
-        }
-   }
-}</font></pre>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_write_jar_file.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_write_jar_file.htm
deleted file mode 100644
index e5b1c00..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_write_jar_file.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Programmatically Writing a Jar file</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2>Programmatically Writing a Jar file</h2>
-<p> The <a href="../reference/api/org/eclipse/jdt/ui/jarpackager/package-summary.html"> 
-  <b> 
-  org.eclipse.ui.jarpackager</b></a> package provides utility classes to programmatically 
-  export files to a Jar file. Below is a code snippet that outlines the use of 
-  the <a href="../reference/api/org/eclipse/jdt/ui/jarpackager/JarPackageData.html"><b>JarPackageData</b></a> 
-  class:</p>
-<pre><font color="#4444cc">    void createJar(IType mainType, IFile[] filestoExport) {
-        Shell parentShell= ...;
-        JarPackageData description= new JarPackageData();
-        IPath location= new Path(&quot;C:/tmp/myjar.jar&quot;);
-        description.setJarLocation(location);
-        description.setSaveManifest(true);
-        description.setManifestMainClass(mainType);
-        description.setElements(filestoExport);
-        IJarExportRunnable runnable= description.createJarExportRunnable(parentShell);
-        try {
-            new ProgressMonitorDialog(parentShell).run(true,true, runnable);
-        } catch (InvocationTargetException e) {
-            // An error has occurred while executing the operation
-        } catch (InterruptedException e) {
-            // operation has been canceled.
-        }
-    }</font></pre>
-<p> Additional API is provided to create a plug-in specific subclass of <a href="../reference/api/org/eclipse/jdt/ui/jarpackager/JarPackageData.html"><b>JarPackageData</b></a>. 
-  This allows other plug-ins to implement their own Jar export/import wizards 
-  and to save the content of the <a href="../reference/api/org/eclipse/jdt/ui/jarpackager/JarPackageData.html"><b>JarPackageData</b></a>
-object to a corresponding Jar 
-  description file.</p>
-<p> Once the JAR is described by a <a href="../reference/api/org/eclipse/jdt/ui/jarpackager/JarPackageData.html"><b>JarPackageData</b></a>,
-it can be programmatically written using a <a href="../reference/api/org/eclipse/jdt/ui/jarpackager/JarWriter2.html"><b>JarWriter2</b></a>.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_apt_building_with_apt.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_apt_building_with_apt.htm
deleted file mode 100644
index b5ae967..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_apt_building_with_apt.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <title>Headless Building with APT in Eclipse</title>
-</head>
-
-<body>
-<h1>Headless Building with APT in Eclipse</h1>
-<h2>Instructions for building workspaces from the command-line directly or with ant</h2>
-
-<p>
-The APT plugin can be used in conjunction with Eclipse to build your preconfigured 
-workspace, either directly from the command-line or via ant with its built-in ant task.
-</p>
-
-<h3>Building from the command-line</h3>
-Given an installation of Eclipse with the APT plugin installed, you can invoke the command-line builder
-with the following command (with no line breaks):
-
-<pre>
-java -cp %ECLIPSE_HOME%/startup.jar org.eclipse.core.launcher.Main
-   -noupdate -application org.eclipse.jdt.apt.core.aptBuild -data %WORKSPACE%
-</pre>
-
-This invokes Eclipse in headless mode and builds the workspace as provided on the command-line.
-Any configuration for the provided workspace will be observed in the build. 
-<p>
-
-<h3>Building with Ant</h3>
-Again, you will need an installation of Eclipse with the APT plugin installed. Given this, the "apt"
-task can be invoked with the following xml in your build.xml file:
-
-<pre>
-&lt;project name="test_eclipse" default="build" basedir=".">
-
-    &lt;taskdef name="apt" classname="org.eclipse.jdt.apt.core.build.JdtApt"/>
-    
-    &lt;target name="build">
-        &lt;apt workspace="%WORKSPACE%" eclipseHome="%ECLIPSE_HOME%"/>
-    &lt;/target>
-    
-&lt;/project>
-</pre>
-
-You will need to add the jar for APT to your ant installation's <b>lib</b> directory, or place it on 
-the classpath when invoking ant. The jar lives in 
-<pre>%ECLIPSE_HOME%/plugins/org.eclipse.jdt.apt.core_X/aptcore.jar</pre>
-

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_apt_getting_started.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_apt_getting_started.htm
deleted file mode 100644
index 37163e3..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_apt_getting_started.htm
+++ /dev/null

@@ -1,85 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <title>Getting started with APT in Eclipse</title>
-</head>
-
-<body>
-<h1>Getting Started</h1>
-<h2>APT in Eclipse</h2>
-
-<p>
-The APT plugin adds Java 5 annotation processing support to Eclipse, by running annotation
-processors written to use the 
-<a href="http://java.sun.com/j2se/1.5.0/docs/guide/apt/mirror/index.html">Mirror APIs</a>
-inside Eclipse.
-<p>
-These annotation processors will then get triggered as you type inside Eclipse, provide
-errors and warnings directly inside the editor, and producing normal build artifacts
-just as if you were running Sun's apt tool from the commandline.
-
-<p>
-For more detailed information about how the plugin works, 
-you can view the <a href="http://www.eclipse.org/jdt/apt/index.html">JDT-APT project web site</a>.
-</p>
-
-<h3>Turning on Annotation Processing</h3>
-You must have your project's compiler configured to use Java 5.0-level compliance
-in the preferences, under Java->Compiler:
-<p>
-<img src="images/compiler_dialog.png">
-<p>
-Next you need to enable annotation processing under Java->Compiler->Annotation Processing:
-<p>
-<img src="images/annotation_processing.png">
-<p>
-In this dialog you can also specify the generated source directory if desired,
-and provide any processor options that are necessary.
-<p>
-<b>Note: "-Aclasspath" and "-Asourcepath" options are automatically passed
-to all your processors by eclipse, so it is unnecessary to provide those.</b>
-
-<h3>Adding Annotation Processors</h3>
-You can add annotation processors to your project under Java->Compiler->Annotation Processing->Factory Path:
-
-<p>
-<img src="images/factory_path.png">
-<p>
-
-<h3>Factory Path and Source Control</h3>
-
-The factory path is similar to the classpath in the way it interacts with source control.
-In order to avoid hard-coding paths to factory jars, you can either use project-relative jars
-via the "Add Jars..." button, or use a classpath variable via the "Add Variable..." button.
-<p>
-
-<h3>Processor Options and Source Control</h3>
-
-You may need to use paths as some of the options passed to your annotation processors.
-Again, by avoiding hard-coding of absolute paths you'll be able to share your configuration
-in source control.
-
-<p>
-To do this, we support classpath variables inside of processor options.
-Variables must be delimited on both sides by %, and must be the 
-first segment of a path.
-<p>
-
-So, if FOO is a classpath variable that points to d:/foo, then %FOO%/bar.txt 
-will resolve to d:/foo/bar.txt.  Classpath resolution depends on the existence 
-of the classpath variable; if it doesn't exist, the raw string will be added to 
-the environment options.  However, bar.txt (in this example) does not need to 
-exist.
-<p>
-
-The reserved variable ROOT is given special meaning: it is the workspace root, 
-and introduces a project resource.  So, for instance, if quux is the name of a 
-project, then %ROOT%/quux will resolve to the absolute path of quux and %
-ROOT%/quux/.classpath will resolve to the absolute path to quux/.classpath.  When 
-using ROOT, the first segment of the path must actually exist: in the example, 
-the project quux must exist, but .classpath need not.
-
-
-
-

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int.htm
deleted file mode 100644
index 4e2db15..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>JDT Programmer's Guide</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h1>JDT Programmer's Guide</h1>
-<p>The Eclipse platform is delivered with a full featured Java integrated development 
-  environment (IDE). Java development tooling (JDT) allows users to write, compile, 
-  test, debug, and edit programs written in the Java programming language.</p>
-<p>The JDT makes use of many of the platform extension points and frameworks described 
-  in the Platform Plug-in Developer Guide.&nbsp; It's easiest to think of 
-  the JDT as a set of plug-ins that add Java specific behavior to the generic 
-  platform resource model and contribute Java specific views, editors, and actions 
-  to the workbench.</p>
-<p> This guide discusses the extension points and API provided by the JDT. 
-  We assume that you already understand the concepts of plug-ins, extension points, 
-  workspace resources, and the workbench UI.&nbsp; </p>
-<p>Given that the JDT supplies a full featured Java IDE, why would you need to 
-  use the JDT API?&nbsp; If you are building a plug-in that interacts with Java programs or resources 
-  as part of its function, you may need to do one or more of the following things:</p>
-<ul>
-  <li> Programmatically manipulate Java resources, such as creating projects, 
-    generating Java source code, performing builds, or detecting problems in code.</li>
-  <li> Programmatically launch a Java program from the platform</li>
-  <li> Provide a new type of VM launcher to support a new family of Java runtimes</li>
-  <li> Add new functions and extensions to the Java IDE itself</li>
-</ul>
-<p> The JDT is structured into three major components:</p>
-<ul>
-  <li><a href="jdt_int_core.htm">JDT Core</a> - the headless infrastructure for compiling and manipulating Java
-    code.</li>
-  <li><a href="jdt_int_ui.htm">JDT UI</a> - the user interface extensions that provide the IDE.</li>
-  <li><a href="jdt_int_debug.htm">JDT Debug</a> - program launching and debug support specific to the Java programming language.</li>
-</ul>
-<p>We'll examine each component's structure and the API it provides.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_apt.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_apt.htm
deleted file mode 100644
index 4393c48..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_apt.htm
+++ /dev/null

@@ -1,20 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) BEA Systems 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>JDT Core</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2>JDT Annotation Processing</h2>
-<p> JDT Annotation Processing (APT) (<b>org.eclipse.jdt.apt.core</b>) is the plug-in that supports compile-time 
-    processing of Java annotations.  You should only need to list this plug-in as a dependency if your plugin is an
-    annotation processor.</p>
-<p> For an introduction to working with APT, see 
-	<a href="jdt_apt_getting_started.htm">Getting Started with APT</a>.  For information on how to access APT
-	during command-line builds, see <a href="jdt_apt_building_with_apt.htm">Headless Building With APT</a>.</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_core.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_core.htm
deleted file mode 100644
index 8284046..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_core.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>JDT Core</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2>JDT Core</h2>
-<p> JDT Core (<b>org.eclipse.jdt.core</b>) is the plug-in that defines the core Java elements 
-    and API. You should always list this plug-in as a prerequisite when you are
-developing Java specific features.</p>
-<p> JDT Core packages give you access to the Java model objects and headless
-Java IDE infrastructure.&nbsp; The JDT Core packages include:</p>
-<ul>
-  <li><b><a href="../reference/api/org/eclipse/jdt/core/package-summary.html">org.eclipse.jdt.core</a></b>
-    - defines the classes that describe the Java model.
-  </li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/core/compiler/package-summary.html">org.eclipse.jdt.core.compiler</a>
-    </b> - defines API for the compiler infrastructure.
-  </li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/core/dom/package-summary.html">org.eclipse.jdt.core.dom</a> </b>
-    - supports Abstract Syntax Trees (AST) that 
-    can be used for examining the structure of a compilation unit down to the 
-    statement level.
-  </li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/core/eval/package-summary.html">org.eclipse.jdt.core.eval</a></b>
-    - supports
-    the evaluation of code snippets in a scrapbook or inside the debugger.
-  </li>
-  <li><a href="../reference/api/org/eclipse/jdt/core/jdom/package-summary.html"><b> 
-    org.eclipse.jdt.core.jdom</b></a> - supports a Java Document Object Model (DOM) 
-    that can be used for walking the structure of a Java compilation unit.
-  </li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/core/search/package-summary.html"> 
-    org.eclipse.jdt.core.search</a></b> - supports searching the workspace's Java
-    model for Java elements match a particular description.&nbsp;&nbsp;
-  </li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/core/util/package-summary.html">org.eclipse.jdt.core.util</a>
-    </b>- provides
-    utility classes for manipulating .class files and Java model elements.
-  </li>
-</ul>
-<p>Manipulation of the structure of a compilation unit should be done using <code>org.eclipse.jdt.core.dom</code> instead of <code>org.eclipse.jdt.core.jdom</code>.
-<code>org.eclipse.jdt.core.jdom</code> will be deprecated in the 2.2. stream and replaced with <code>org.eclipse.jdt.core.dom</code>.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_debug.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_debug.htm
deleted file mode 100644
index 2d0b7b4..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_debug.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>JDT Debug</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2>JDT Debug</h2>
-<p> JDT Debug is comprised of several plug-ins that support the running and
-debugging of Java code.</p>
-<ul>
-  <li><b>org.eclipse.jdt.launching</b> is the plug-in that defines the Java launching 
-    and runtime support. You will require this plug-in if you 
-    need to launch Java virtual machines programmatically.&nbsp; The JDT
-    launching is closely tied to the platform launching facility, which is
-    described in <a href="../../org.eclipse.platform.doc.isv/guide/debug_launch.htm">Launching
-    a program</a>.
-    <p>The package <a href="../reference/api/org/eclipse/jdt/launching/package-summary.html"><b>org.eclipse.jdt.launching </b></a> provides classes for launching Java runtimes 
-    from the platform.&nbsp; <b><a href="../reference/api/org/eclipse/jdt/launching/JavaRuntime.html">JavaRuntime</a> </b> implements static methods to access registered VMs and 
-    compute runtime classpaths and source lookup paths.&nbsp; A family of VM's 
-    (such as the JDK) is represented by the <a href="../reference/api/org/eclipse/jdt/launching/IVMInstallType.html"><b> 
-    IVMInstallType</b></a> class. <a href="../reference/api/org/eclipse/jdt/launching/IVMInstall.html"><b> 
-    IVMInstall</b></a> represents particular installations within a family.&nbsp; 
-    The <a href="../reference/api/org/eclipse/jdt/launching/IVMRunner.html"><b> 
-    IVMRunner</b></a> is used to start a particular Java VM and register its processes 
-    with the debug plug-in.</p>
-    <p>The package <a href="../reference/api/org/eclipse/jdt/launching/sourcelookup/containers/package-summary.html"><b>org.eclipse.jdt.launching.sourcelookup.containers 
-      </b></a>defines classes for locating source code elements in the file system.<br></p>
-  </li>
-  <li><b>org.eclipse.jdt.debug</b> is the plug-in that defines the Java debug 
-    model. You will require this plug-in if you need to programmatically 
-    access objects in a program being debugged.&nbsp; The JDT debug model is
-    closely tied to the platform debug model, which is described in <a href="../../org.eclipse.platform.doc.isv/guide/debug_model.htm">Platform
-    debug model</a>.
-    <p>The package <a href="../reference/api/org/eclipse/jdt/debug/core/package-summary.html"><b>org.eclipse.jdt.debug.core</b></a> supports a Java debug model based on
-    JDI/JDWP 
-    that can be used for controlling a Java program under debug.</p>
-    <p>The package <a href="../reference/api/org/eclipse/jdt/debug/eval/package-summary.html"><b>org.eclipse.jdt.debug.eval</b></a> provides infrastructure for evaluating
-    Java expressions and reporting results.</p>
-  </li>
-  <li><b>org.eclipse.jdt.debug.ui</b> is the plug-in that defines the Java debug 
-    UI extensions. Most of the debugger API is provided by the platform debugger
-    infrastructure described in <a href="../../org.eclipse.platform.doc.isv/guide/debug_presentation.htm">Debug
-    model presentation</a> and <a href="../../org.eclipse.platform.doc.isv/guide/debug_ui.htm">Debug
-    UI utility classes</a>.&nbsp; The Java debug UI API focuses on accessing the prompting source locator
-    and Java launch configuration 
-    tabs.&nbsp;&nbsp;
-    <p>The package <a href="../reference/api/org/eclipse/jdt/debug/ui/launchConfigurations/package-summary.html"><b> 
-    org.eclipse.jdt.debug.ui.launchConfigurations</b></a> defines the launch
-    configuration tabs for local and remote Java applications.</p></li>
-</ul>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_junit.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_junit.htm
deleted file mode 100644
index 3800737..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_junit.htm
+++ /dev/null

@@ -1,18 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>JDT JUnit integration</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2>JDT JUnit integration</h2>
-<p><a href="http://www.junit.org">JUnit</a> is a simple test framework used to
-write repeatable tests.&nbsp; </p>
-<p>The JDT tools include a plug-in that integrates JUnit into the Java
-IDE.&nbsp; The JUnit plug-in allows you to define regression tests for your code
-and run them from the Java IDE. </p></body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_model.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_model.htm
deleted file mode 100644
index ba6c2b6..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_model.htm
+++ /dev/null

@@ -1,195 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Java model</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2>Java model</h2>
-<p> The Java model is the set of classes that model the objects associated with 
-  creating, editing, and building a Java program. The Java model classes are defined 
-  in <b><a href="../reference/api/org/eclipse/jdt/core/package-summary.html"> 
-  org.eclipse.jdt.core</a></b>.&nbsp; These classes implement Java specific 
-  behavior for resources and further decompose Java resources into model elements.</p>
-<h3> Java elements</h3>
-<p> The package <a href="../reference/api/org/eclipse/jdt/core/package-summary.html"><b> 
-  org.eclipse.jdt.core</b></a> defines the classes that model the elements that 
-  compose a Java program. The JDT uses an in-memory object model to represent 
-  the structure of a Java program. This structure is derived from the project's class path.
-  The model is hierarchical. Elements of a program can be decomposed into child elements.</p>
-<p> Manipulating Java elements is similar to manipulating resource objects.&nbsp; When you work with a Java 
-  element, you are actually working with a <b>handle</b> to some underlying model 
-  object.&nbsp; You must use the <b>exists()</b> protocol to determine whether 
-  the element is actually present in the workspace.&nbsp;</p>
-<p> The following table summarizes the different kinds of Java elements.</p>
-<table border="1">
-  <tbody> 
-  <tr> 
-    <th rowspan="1" colspan="1"> Element </th>
-    <th rowspan="1" colspan="1"> Description </th>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IJavaModel.html"><b> IJavaModel</b></a> 
-    </td>
-    <td> Represents the root Java element, corresponding to the workspace. The 
-      parent of all projects with the Java nature. It also gives you access to the projects without the java nature.</td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html"><b> 
-      IJavaProject</b></a> </td>
-    <td> Represents a Java project in the workspace. (Child of <a href="../reference/api/org/eclipse/jdt/core/IJavaModel.html"><b> 
-      IJavaModel</b></a>) </td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IPackageFragmentRoot.html"><b> 
-      IPackageFragmentRoot</b></a> </td>
-    <td> Represents a set of package fragments, and maps the fragments to an underlying 
-      resource which is either a folder, JAR, or ZIP file. (Child of <a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html"><b> 
-      IJavaProject</b></a>) </td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IPackageFragment.html"><b> 
-      IPackageFragment</b></a> </td>
-    <td> Represents the portion of the workspace that corresponds to an entire 
-      package, or a portion of the package. (Child of <a href="../reference/api/org/eclipse/jdt/core/IPackageFragmentRoot.html"><b> 
-      IPackageFragmentRoot</b></a> )</td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html"><b> 
-      ICompilationUnit</b></a> </td>
-    <td> Represents a Java source (<b>.java</b>) file. (Child of <a href="../reference/api/org/eclipse/jdt/core/IPackageFragment.html"><b> 
-      IPackageFragment</b></a> )</td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IPackageDeclaration.html"><b> 
-      IPackageDeclaration</b></a> </td>
-    <td> Represents a package declaration in a compilation unit. (Child of <a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html"><b> 
-      ICompilationUnit</b></a> )</td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IImportContainer.html"><b> 
-      IImportContainer</b></a> </td>
-    <td> Represents the collection of package import declarations in a compilation 
-      unit. (Child of <a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html"><b> 
-      ICompilationUnit</b></a> )</td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IImportDeclaration.html"><b> 
-      IImportDeclaration</b></a> </td>
-    <td> Represents a single package import declaration. (Child of <a href="../reference/api/org/eclipse/jdt/core/IImportContainer.html"><b> 
-      IImportContainer</b></a> )</td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IType.html"><b> IType</b></a> 
-    </td>
-    <td> Represents either a source type inside a compilation unit, or a binary 
-      type inside a class file. </td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IField.html"><b> IField</b></a> 
-    </td>
-    <td> Represents a field inside a type. (Child of <a href="../reference/api/org/eclipse/jdt/core/IType.html"><b> 
-      IType</b></a> )</td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IMethod.html"><b> IMethod</b></a> 
-    </td>
-    <td> Represents a method or constructor inside a type. (Child of <a href="../reference/api/org/eclipse/jdt/core/IType.html"><b> 
-      IType</b></a> )</td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IInitializer.html"><b> 
-      IInitializer</b></a> </td>
-    <td> Represents a static or instance initializer inside a type. (Child of 
-      <a href="../reference/api/org/eclipse/jdt/core/IType.html"><b> IType</b></a> 
-      )</td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IClassFile.html"><b> IClassFile</b></a> 
-    </td>
-    <td> Represents a compiled (binary) type.&nbsp; (Child of <a href="../reference/api/org/eclipse/jdt/core/IPackageFragment.html"><b> 
-      IPackageFragment</b></a> )</td>
-  </tr>
-  </tbody> 
-</table>
-<p> All Java elements support the <a href="../reference/api/org/eclipse/jdt/core/IJavaElement.html"><b> 
-  IJavaElement</b></a> interface. </p>
-<p> Some of the elements are shown in the Packages view.&nbsp; These elements 
-  implement the <b><a href="../reference/api/org/eclipse/jdt/core/IOpenable.html"> 
-  IOpenable</a> </b> interface, since they must be opened before they can be navigated. 
-  The figure below shows how these elements are represented in the Packages view.</p>
-<p><img src="images/openables.png"  border="0" alt="Packages View showing elements implementing the IOpenable interface"> 
-</p>
-<p>The Java elements that implement <b><a href="../reference/api/org/eclipse/jdt/core/IOpenable.html"> 
-  IOpenable</a> </b> are created primarily from information found in the underlying 
-  resource files.&nbsp; The same elements are represented generically in the resource 
-  navigator view.</p>
-<p><img src="images/javanavigator.png"  border="0" alt="Resource Navigator showing elements implementing the IOpenable interface"> 
-</p>
-<p> Other elements correspond to the items that make up a Java compilation unit. 
-  The figure below shows a Java compilation unit and a content outliner that displays 
-  the source elements in the compilation unit.</p>
-<img src="images/sourceelements.png"  border="0" alt="An editor and a content outliner illustrating the relation between corresponding source elements"> 
-<p> These elements implement the <a href="../reference/api/org/eclipse/jdt/core/ISourceReference.html"><b> 
-  ISourceReference</b></a> interface, since they can provide corresponding source 
-  code. (As these elements are selected in the content outliner, their corresponding 
-  source code is shown in the Java editor).</p>
-<h3> Java elements and their resources</h3>
-<p> Many of the Java elements correspond to generic resources in the workspace.&nbsp; 
-  When you want to create Java elements from a generic resource the class <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html"><b> 
-  JavaCore</b></a> is the best starting point. The following code snippet shows 
-  how to get Java elements from their corresponding resources.</p>
-<font color="#4444cc"> <pre>    
-        private void createJavaElementsFrom(IProject myProject, IFolder myFolder, IFile myFile) {
-        IJavaProject myJavaProject= JavaCore.create(myProject);
-        if (myJavaProject == null)
-            // the project is not configured for Java (has no Java nature)
-            return;
-            
-        // get a package fragment or package fragment root
-        IJavaElement myPackageFragment= JavaCore.create(myFolder);
-        
-        // get a .java (compilation unit), .class (class file), or
-        // .jar (package fragment root)
-        IJavaElement myJavaFile = JavaCore.create(myFile);
-    }</pre></font> 
-<p>Once you have a Java element, you can use the JDT API to traverse and query
-the model.&nbsp; You may also query the non-Java resources contained in a Java
-element.&nbsp;</p>
-<font color="#4444cc"><pre>         private void createJavaElementsFrom(IProject myProject, IFolder myFolder, IFile myFile) {
-        ...
-        // get the non Java resources contained in my project.
-        Object[] nonJavaChildren = myJavaProject.getNonJavaResources();
-        ...
-            </font></pre> 
-<h3> Java projects</h3>
-<p>When you create a Java project from a simple project, <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html"><b> 
-  JavaCore</b></a> will check to see if the project is configured with the Java 
-  nature.&nbsp; The JDT plug-in uses a project nature to designate a project as 
-  having Java behavior.&nbsp; This nature (<b>org.eclipse.jdt.core.JavaCore#NATURE_ID</b> 
-  ) is assigned to a project when the "New Java project" wizard creates a project.&nbsp; 
-  If the Java nature is not configured on a project, <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html"><b> 
-  JavaCore</b></a> will return null when asked to create the project.</p>
-<p><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html"><b>JavaCore</b></a> 
-  is also used to maintain the Java class path, including locations for finding 
-  source code and libraries, and locations for generating output binary (<b>.class</b>) 
-  files.</p>
-<p> What are the unique characteristics of Java projects? They record their classpath 
-  in a "<b>.classpath</b>" file and add the Java incremental project builder to 
-  the project's build spec.&nbsp; Otherwise, they are just regular projects and 
-  can be configured with other natures (and other incremental builders) by plug-ins. 
-  Plug-ins that want to configure projects with Java behavior in addition to their 
-  own behavior typically use the <b><a href="../reference/api/org/eclipse/jdt/ui/wizards/NewJavaProjectWizardPage.html"> 
-  NewJavaProjectWizardPage</a> </b> to assign the Java nature to the project in 
-  addition to their own custom natures or behavior.</p>
-<p><a href="../reference/api/org/eclipse/jdt/core/IJavaModel.html"><b> IJavaModel</b></a> 
-  can be considered the parent of all projects in the workspace that have the 
-  Java project nature (and therefore can be treated as an <a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html"><b> 
-  IJavaProject</b></a>).</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_ui.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_ui.htm
deleted file mode 100644
index c43caa4..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_ui.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>JDT UI</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2>JDT UI</h2>
-<p>JDT UI (<b>org.eclipse.jdt.ui</b>) is the plug-in implementing the Java specific user interface 
-  classes that manipulate Java elements. The packages in the JDT UI implement
-the Java-specific extensions to the workbench.&nbsp;&nbsp;&nbsp; The JDT UI
-packages include:</p>
-<ul>
-  <li> <b><a href="../reference/api/org/eclipse/jdt/ui/package-summary.html"> 
-    org.eclipse.jdt.ui</a> </b> - provides support classes for presenting Java 
-    elements in the user interface.&nbsp; This package exposes constants for retrieving 
-    Java user interface parts from the workbench registry and for retrieving preference 
-    settings from the Java preferences.&nbsp; Programming interfaces <a href="../reference/api/org/eclipse/jdt/ui/ITypeHierarchyViewPart.html"><b>ITypeHierarchyViewPart</b></a> 
-    and <a href="../reference/api/org/eclipse/jdt/ui/IPackagesViewPart.html"> 
-    <b> IPackagesViewPart</b></a> are provided for interacting with Java views. 
-  </li>
-  <li> <b><a href="../reference/api/org/eclipse/jdt/ui/actions/package-summary.html">org.eclipse.jdt.ui.actions</a> 
-    </b>- provides actions and action groups to populate tool bars, global menu 
-    bars and context menus with JDT specific functionality. You should use action 
-    groups to populate menus and tool bars instead of adding actions directly. 
-    This shields you from missing newly added actions or from using outdated menu 
-    structures. </li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/ui/jarpackager/package-summary.html"> 
-    org.eclipse.jdt.ui.jarpackager</a> </b> - provides classes and interfaces 
-    to generate a JAR file. </li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/ui/refactoring/package-summary.html">org.eclipse.jdt.ui.refactoring</a></b> 
-    - provides support for running rename refactorings</li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/ui/search/package-summary.html">org.eclipse.jdt.ui.search</a></b> 
-    - provides classes and interfaces to contribute participants to a Java search</li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/ui/text/package-summary.html"> 
-    org.eclipse.jdt.ui.text</a> </b> - provides support classes for presenting 
-    Java text.&nbsp; </li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/ui/text/folding/package-summary.html">org.eclipse.jdt.ui.text.folding</a></b> - provides interfaces to implement code folding strategies for the Java editor.</li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/ui/text/java/package-summary.html">org.eclipse.jdt.ui.text.java</a></b> - provides interfaces to implement code completion processors.</li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/ui/text/java/hover/package-summary.html"> 
-    org.eclipse.jdt.ui.text.java.hover</a> </b> - provides implementations for 
-    presenting text hovers in Java editors.&nbsp; </li>
-  <li><a href="../reference/api/org/eclipse/jdt/ui/wizards/package-summary.html"> 
-    <b> org.eclipse.jdt.ui.wizards</b></a> - provides wizard pages for creating 
-    and configuring Java elements. </li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/jdtOptions.txt b/bundles/org.eclipse.jdt.doc.isv/jdtOptions.txt
deleted file mode 100644
index c6b9be3..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/jdtOptions.txt
+++ /dev/null

@@ -1,123 +0,0 @@
--quiet
--encoding "iso-8859-1"
--charset "iso-8859-1"
--sourcepath "../org.eclipse.jdt.core/antadapter
-;../org.eclipse.jdt.core/batch
-;../org.eclipse.jdt.core/codeassist
-;../org.eclipse.jdt.core/compiler
-;../org.eclipse.jdt.core/dom
-;../org.eclipse.jdt.core/eval
-;../org.eclipse.jdt.core/formatter
-;../org.eclipse.jdt.core/model
-;../org.eclipse.jdt.core/search
-;../org.eclipse.jdt.debug/model
-;../org.eclipse.jdt.debug/jdi
-;../org.eclipse.jdt.debug/eval
-;../org.eclipse.jdt.debug.ui/ui
-;../org.eclipse.jdt.junit/src
-;../org.eclipse.jdt.junit.runtime/src
-;../org.eclipse.jdt.launching/launching
-;../org.eclipse.jdt.ui/ui
-;../org.eclipse.jdt.ui/core refactoring
-;../org.eclipse.jdt.ui/ui refactoring
-;../org.eclipse.jdt.ui/core extension
-;../org.eclipse.jdt.core.manipulation/refactoring
-;../org.eclipse.jdt.core.manipulation/common
-;../org.eclipse.jdt.apt.core/src"
--d reference/api
--classpath @rt@
-;../../baseLocation/plugins/com.ibm.icu_3.4.3.jar
-;../org.eclipse.jdt.apt.core/mirrorapi.jar
-;../org.apache.ant/lib/ant.jar
-;../org.eclipse.compare/@dot
-;../org.eclipse.core.commands/@dot
-;../org.eclipse.core.contenttype/@dot
-;../org.eclipse.core.expressions/@dot
-;../org.eclipse.core.filebuffers/@dot
-;../org.eclipse.core.filesystem/@dot
-;../org.eclipse.core.jobs/@dot
-;../org.eclipse.core.resources/@dot
-;../org.eclipse.core.runtime/@dot
-;../org.eclipse.core.runtime.content/@dot
-;../org.eclipse.core.runtime.jobs/@dot
-;../org.eclipse.core.runtime.preferences/@dot
-;../org.eclipse.core.variables/@dot
-;../org.eclipse.debug.core/@dot
-;../org.eclipse.debug.ui/@dot
-;../org.eclipse.equinox.common/@dot
-;../org.eclipse.equinox.preferences/@dot
-;../org.eclipse.equinox.registry/@dot
-;../org.eclipse.equinox.supplement/@dot
-;../org.eclipse.help/@dot
-;../org.eclipse.help.ui/@dot
-;../org.eclipse.jdt.core.manipulation/@dot
-;../org.eclipse.jdt.debug/jdi.jar
-;../org.eclipse.jdt.junit/@dot
-;../org.eclipse.jface/@dot
-;../org.eclipse.jface.text/@dot
-;../org.eclipse.ltk.core.refactoring/@dot
-;../org.eclipse.ltk.ui.refactoring/@dot
-;../org.eclipse.osgi.services/@dot
-;../org.eclipse.osgi.util/@dot
-;../org.eclipse.osgi/@dot
-;../org.eclipse.search/@dot
-;../org.eclipse.swt.win32.win32.x86/@dot
-;../org.eclipse.team.core/@dot
-;../org.eclipse.team.ui/@dot
-;../org.eclipse.text/@dot
-;../org.eclipse.ui/@dot
-;../org.eclipse.ui.console/@dot
-;../org.eclipse.ui.editors/@dot
-;../org.eclipse.ui.forms/@dot
-;../org.eclipse.ui.ide/@dot
-;../org.eclipse.ui.navigator/@dot
-;../org.eclipse.ui.views/@dot
-;../org.eclipse.ui.workbench.texteditor/@dot
-;../org.eclipse.ui.workbench/@dot
--breakiterator
--use
--splitIndex
--windowtitle "Eclipse JDT API Specification"
--doctitle "Eclipse JDT API Specification"
--header "<b>Eclipse JDT</b><br>Release 3.2"
--bottom "Copyright (c) IBM Corp. and others 2000, 2006.  All Rights Reserved."
--group "Java Development Tools Core Plug-in Packages" "org.eclipse.jdt.core
-;org.eclipse.jdt.core.*"
--group "Java Development Tools UI Plug-in Packages" "org.eclipse.jdt.ui
-;org.eclipse.jdt.ui.*"
--link http://java.sun.com/j2se/1.5/docs/api
--linkoffline ./../../../org.eclipse.platform.doc.isv/reference/api ../org.eclipse.platform.doc.isv/reference/api
--link http://bundles.osgi.org/javadoc/r4
-
-org.eclipse.jdt.core
-org.eclipse.jdt.core.compiler
-org.eclipse.jdt.core.dom
-org.eclipse.jdt.core.dom.rewrite
-org.eclipse.jdt.core.eval
-org.eclipse.jdt.core.formatter
-org.eclipse.jdt.core.jdom
-org.eclipse.jdt.core.util
-org.eclipse.jdt.core.search
-org.eclipse.jdt.core.refactoring
-org.eclipse.jdt.core.manipulation
-org.eclipse.jdt.debug.core
-org.eclipse.jdt.debug.eval
-org.eclipse.jdt.debug.ui
-org.eclipse.jdt.debug.ui.launchConfigurations
-org.eclipse.jdt.launching
-org.eclipse.jdt.launching.environments
-org.eclipse.jdt.launching.sourcelookup
-org.eclipse.jdt.launching.sourcelookup.containers
-org.eclipse.jdt.ui
-org.eclipse.jdt.ui.actions
-org.eclipse.jdt.ui.dialogs
-org.eclipse.jdt.ui.jarpackager
-org.eclipse.jdt.ui.refactoring
-org.eclipse.jdt.ui.search
-org.eclipse.jdt.ui.text
-org.eclipse.jdt.ui.text.folding
-org.eclipse.jdt.ui.text.java
-org.eclipse.jdt.ui.text.java.hover
-org.eclipse.jdt.ui.wizards
-org.eclipse.jdt.junit
-

diff --git a/bundles/org.eclipse.jdt.doc.isv/jdtaptOptions.txt b/bundles/org.eclipse.jdt.doc.isv/jdtaptOptions.txt
deleted file mode 100644
index ef62a7e..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/jdtaptOptions.txt
+++ /dev/null

@@ -1,99 +0,0 @@
--quiet
--encoding "iso-8859-1"
--charset "iso-8859-1"
--sourcepath "../org.eclipse.jdt.core/antadapter
-;../org.eclipse.jdt.core/batch
-;../org.eclipse.jdt.core/codeassist
-;../org.eclipse.jdt.core/compiler
-;../org.eclipse.jdt.core/dom
-;../org.eclipse.jdt.core/eval
-;../org.eclipse.jdt.core/formatter
-;../org.eclipse.jdt.core/model
-;../org.eclipse.jdt.core/search
-;../org.eclipse.jdt.debug/model
-;../org.eclipse.jdt.debug/jdi
-;../org.eclipse.jdt.debug/eval
-;../org.eclipse.jdt.debug.ui/ui
-;../org.eclipse.jdt.junit/src
-;../org.eclipse.jdt.junit.runtime/src
-;../org.eclipse.jdt.launching/launching
-;../org.eclipse.jdt.ui/ui
-;../org.eclipse.jdt.ui/core refactoring
-;../org.eclipse.jdt.ui/ui refactoring
-;../org.eclipse.jdt.ui/core extension
-;../org.eclipse.jdt.core.manipulation/refactoring
-;../org.eclipse.jdt.core.manipulation/common
-;../org.eclipse.jdt.apt.core/src"
--d reference/apt
--classpath ${bootclasspath}
-;../../baseLocation/plugins/com.ibm.icu_3.4.3.jar
-;../org.eclipse.jdt.apt.core/mirrorapi.jar
-;../org.apache.ant/lib/ant.jar
-;../org.eclipse.compare/@dot
-;../org.eclipse.core.commands/@dot
-;../org.eclipse.core.contenttype/@dot
-;../org.eclipse.core.expressions/@dot
-;../org.eclipse.core.filebuffers/@dot
-;../org.eclipse.core.filesystem/@dot
-;../org.eclipse.core.jobs/@dot
-;../org.eclipse.core.resources/@dot
-;../org.eclipse.core.runtime/@dot
-;../org.eclipse.core.runtime.content/@dot
-;../org.eclipse.core.runtime.jobs/@dot
-;../org.eclipse.core.runtime.preferences/@dot
-;../org.eclipse.core.variables/@dot
-;../org.eclipse.debug.core/@dot
-;../org.eclipse.debug.ui/@dot
-;../org.eclipse.equinox.common/@dot
-;../org.eclipse.equinox.preferences/@dot
-;../org.eclipse.equinox.registry/@dot
-;../org.eclipse.equinox.supplement/@dot
-;../org.eclipse.help/@dot
-;../org.eclipse.help.ui/@dot
-;../org.eclipse.jdt.core.manipulation/@dot
-;../org.eclipse.jdt.debug/jdi.jar
-;../org.eclipse.jdt.junit/@dot
-;../org.eclipse.jface/@dot
-;../org.eclipse.jface.text/@dot
-;../org.eclipse.ltk.core.refactoring/@dot
-;../org.eclipse.ltk.ui.refactoring/@dot
-;../org.eclipse.osgi.services/@dot
-;../org.eclipse.osgi.util/@dot
-;../org.eclipse.osgi/@dot
-;../org.eclipse.search/@dot
-;../org.eclipse.swt.win32.win32.x86/@dot
-;../org.eclipse.team.core/@dot
-;../org.eclipse.team.ui/@dot
-;../org.eclipse.text/@dot
-;../org.eclipse.ui/@dot
-;../org.eclipse.ui.console/@dot
-;../org.eclipse.ui.editors/@dot
-;../org.eclipse.ui.forms/@dot
-;../org.eclipse.ui.ide/@dot
-;../org.eclipse.ui.navigator/@dot
-;../org.eclipse.ui.views/@dot
-;../org.eclipse.ui.workbench.texteditor/@dot
-;../org.eclipse.ui.workbench/@dot
-;../org.eclipse.jdt.core/@dot
-;../org.eclipse.jdt.core.manipulation/@dot
--breakiterator
--use
--splitIndex
--windowtitle "Eclipse JDT API Specification"
--doctitle "Eclipse JDT API Specification"
--header "<b>Eclipse JDT</b><br>Release 3.2"
--bottom "Copyright (c) IBM Corp. and others 2000, 2006.  All Rights Reserved."
--group "Java Development Tools APT Plug-in Packages" "org.eclipse.jdt.apt.core
-;org.eclipse.jdt.apt.core.*"
--link http://java.sun.com/j2se/1.5/docs/api
--linkoffline ./../../../org.eclipse.platform.doc.isv/reference/api ../org.eclipse.platform.doc.isv/reference/api
--linkoffline ./../../../org.eclipse.jdt.doc.isv/reference/api ./reference/api
--link http://bundles.osgi.org/javadoc/r4
-
-org.eclipse.jdt.apt.core.build
-org.eclipse.jdt.apt.core.env
-org.eclipse.jdt.apt.core.util
-com.sun.mirror.apt
-com.sun.mirror.declaration
-com.sun.mirror.type
-com.sun.mirror.util

diff --git a/bundles/org.eclipse.jdt.doc.isv/notices.html b/bundles/org.eclipse.jdt.doc.isv/notices.html
deleted file mode 100644
index 03ff544..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/notices.html
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <LINK REL="STYLESHEET" HREF="book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Legal Notices</title>
-</head>
-<body>
-
-<h3>
-<a NAME="Notices"></a>Notices</h3>
-<p>
-The material in this guide is Copyright (c) IBM Corporation and others 2000, 2005.
-</p>
-<p>
-<a href="about.html">Terms and conditions regarding the use of this guide.</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/plugin.properties b/bundles/org.eclipse.jdt.doc.isv/plugin.properties
deleted file mode 100644
index ae49064..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/plugin.properties
+++ /dev/null

@@ -1,12 +0,0 @@
-###############################################################################
-# Copyright (c) 2000, 2005 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-pluginName=Eclipse JDT Plug-in Developer Guide
-providerName=Eclipse.org

diff --git a/bundles/org.eclipse.jdt.doc.isv/plugin.xml b/bundles/org.eclipse.jdt.doc.isv/plugin.xml
deleted file mode 100644
index 368982d..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/plugin.xml
+++ /dev/null

@@ -1,49 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?eclipse version="3.0"?>
-
-<!-- ===================================================== -->
-<!-- Declare the documentation for the JDT ISV Guide       -->
-<!-- We will declare only one infoset (book)               -->
-<!-- ===================================================== -->
-
-<plugin>
-
-
-<!-- ============================================================================= -->
-<!-- Define primary TOC                                                            -->
-<!-- ============================================================================= -->
-
-   <extension point="org.eclipse.help.toc"> 
-       <toc file="toc.xml" primary="true" />
-       <index path="index"/>
-   </extension>
-
-<!-- ============================================================================= -->
-<!-- Define TOCs                                                                   -->
-<!-- ============================================================================= -->
-
-   <extension point="org.eclipse.help.toc"> 
-       <toc file="topics_Guide.xml" />   
-       <toc file="topics_Reference.xml" />   
-       <toc file="topics_Questions.xml" />   
-       <toc file="topics_Samples.xml" />   
-   </extension>
-   
-<!-- ============================================================================= -->
-<!-- Define Javadoc locations                                                      -->
-<!-- ============================================================================= -->
-   <extension point="org.eclipse.pde.core.javadoc">
-       <javadoc path="reference/api">
-           <plugin id="org.eclipse.jdt.core"/>
-           <plugin id="org.eclipse.jdt.core.manipulation"/>
-           <plugin id="org.eclipse.jdt.debug"/>
-           <plugin id="org.eclipse.jdt.debug.ui"/>
-           <plugin id="org.eclipse.jdt.launching"/>
-           <plugin id="org.eclipse.jdt.ui"/>
-           <plugin id="org.eclipse.jdt.apt.ui"/>
-           <plugin id="org.eclipse.jdt.apt.core"/>
-           <plugin id="org.eclipse.jdt.junit"/>
-       </javadoc>
-   </extension>
-   
-</plugin>

diff --git a/bundles/org.eclipse.jdt.doc.isv/questions/index.html b/bundles/org.eclipse.jdt.doc.isv/questions/index.html
deleted file mode 100644
index 2567fc3..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/questions/index.html
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta name="Author" content="OTI">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>JDT Questions Index</title>
-</head>
-<body>
-<h1>JDT Questions Index</h1>
-<h2> JDT Core</h2>
-<ul>
-  <li><a href="../guide/jdt_int_core.htm">What is available in the JDT Core 
-    API Packages?</a> </li>
-  <li><a href="../guide/jdt_api_run.htm">How do I launch a Java program from the 
-    platform?</a> </li>
-  <li><a href="../guide/jdt_api_compile.htm">How do I programmatically compile 
-    a Java program?</a> </li>
-  <li><a href="../guide/jdt_api_classpath.htm">How do I setup a project's classpath?</a> 
-  </li>
-  <li><a href="../guide/jdt_api_manip.htm">How do I manipulate Java code?</a> 
-  </li>
-  <li><a href="../guide/jdt_api_search.htm">How do I use the Java search engine?</a> 
-  </li>
-  <li><a href="../guide/jdt_api_options.htm">What are the JDT Core options? </a> 
-  </li>
-  <li><a href="../guide/jdt_api_codeassist.htm">How do I programmatically use 
-    CodeAssist and CodeSelect?</a> </li>
-  <li><a href="../guide/jdt_int_model.htm">How are Java projects, folders, 
-    and files different from regular resources?</a> </li>
-</ul>
-<h2> JDT UI</h2>
-<ul>
-  <li><a href="../guide/jdt_int_ui.htm">What is available in the JDT UI packages?</a> 
-  </li>
-  <li><a href="../guide/jdt_api_open_editor.htm">How do I programmatically open 
-    a Java editor and display a specific Java element in the editor?</a> </li>
-  <li><a href="../guide/jdt_api_prompter.htm">How do I programmatically open 
-    the Open Type dialog?</a> <br>
-  </li>
-  <li><a href="../guide/jdt_api_render.htm">How do I present Java elements in 
-    a standard JFace viewer?</a></li>
-  <li><a href="../guide/jdt_api_write_jar_file.htm">How do I write a Jar file?</a></li>
-  <li><a href="../guide/jdt_api_wizards.htm">How do I create a customized 
-    new Java element wizard page?</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/reference/.cvsignore b/bundles/org.eclipse.jdt.doc.isv/reference/.cvsignore
deleted file mode 100644
index a5939d2..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/reference/.cvsignore
+++ /dev/null

@@ -1,2 +0,0 @@
-apt
-api

diff --git a/bundles/org.eclipse.jdt.doc.isv/reference/extension-points/index.html b/bundles/org.eclipse.jdt.doc.isv/reference/extension-points/index.html
deleted file mode 100644
index 6c96ed1..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/reference/extension-points/index.html
+++ /dev/null

@@ -1,42 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>JDT Extension Points</title>
-<link rel="stylesheet" type="text/css" HREF="../../book.css">
-</head>
-<body>
-<h1>JDT Extension Points</h1>
-<p>The following extension points can be used to extend the capabilities of the 
-  JDT infrastructure: </p>
-<ul>
-  <li><a href="org_eclipse_jdt_core_classpathVariableInitializer.html">org.eclipse.jdt.core.classpathVariableInitializer</a> 
-  </li>
-  <li><a href="org_eclipse_jdt_core_classpathContainerInitializer.html">org.eclipse.jdt.core.classpathContainerInitializer</a> 
-  </li>
-  <li><a href="org_eclipse_jdt_core_codeFormatter.html">org.eclipse.jdt.core.codeFormatter</a> 
-  </li>
-  <li><a href="org_eclipse_jdt_debug_javaLogicalStructures.html">org.eclipse.jdt.debug.javaLogicalStructures</a> </li>  
-  <li><a href="org_eclipse_jdt_debug_ui_vmInstallTypePage.html">org.eclipse.jdt.debug.ui.vmInstallTypePage</a> </li>
-  <li><a href="org_eclipse_jdt_junit_junitLaunchConfigs.html">org.eclipse.jdt.junit.junitLaunchConfigs</a> </li>
-  <li><a href="org_eclipse_jdt_junit_testRunListeners.html">org.eclipse.jdt.junit.testRunListeners</a> </li>
-  <li><a href="org_eclipse_jdt_launching_classpathProviders.html">org.eclipse.jdt.launching.classpathProviders</a></li>
-  <li><a href="org_eclipse_jdt_launching_runtimeClasspathEntries.html">org.eclipse.jdt.launching.runtimeClasspathEntries</a> </li>
-  <li><a href="org_eclipse_jdt_launching_runtimeClasspathEntryResolvers.html">org.eclipse.jdt.launching.runtimeClasspathEntryResolvers</a> </li>
-  <li><a href="org_eclipse_jdt_launching_vmConnectors.html">org.eclipse.jdt.launching.vmConnectors</a></li>
-  <li><a href="org_eclipse_jdt_launching_vmInstallTypes.html">org.eclipse.jdt.launching.vmInstallTypes</a></li>
-  <li><a href="org_eclipse_jdt_ui_classpathContainerPage.html">org.eclipse.jdt.ui.classpathContainerPage</a></li>
-  <li><a href="org_eclipse_jdt_ui_foldingStructureProviders.html">org.eclipse.jdt.ui.foldingStructureProviders</a></li>
-  <li><a href="org_eclipse_jdt_ui_javaCompletionProposalComputer.html">org.eclipse.jdt.ui.javaCompletionProposalComputer</a></li>
-  <li><a href="org_eclipse_jdt_ui_javaCompletionProposalSorters.html">org.eclipse.jdt.ui.javaCompletionProposalSorters</a></li>
-  <li><a href="org_eclipse_jdt_ui_javadocCompletionProcessor.html">org.eclipse.jdt.ui.javadocCompletionProcessor</a></li>
-  <li><a href="org_eclipse_jdt_ui_javaEditorTextHovers.html">org.eclipse.jdt.ui.javaEditorTextHovers</a></li>
-  <li><a href="org_eclipse_jdt_ui_javaElementFilters.html">org.eclipse.jdt.ui.javaElementFilters</a></li>
-  <li><a href="org_eclipse_jdt_ui_queryParticipants.html">org.eclipse.jdt.ui.queryParticipants</a></li>
-  <li><a href="org_eclipse_jdt_ui_quickAssistProcessors.html">org.eclipse.jdt.ui.quickAssistProcessors</a></li>
-  <li><a href="org_eclipse_jdt_ui_quickFixProcessors.html">org.eclipse.jdt.ui.quickFixProcessors</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/reference/misc/index.html b/bundles/org.eclipse.jdt.doc.isv/reference/misc/index.html
deleted file mode 100644
index cfd0558..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/reference/misc/index.html
+++ /dev/null

@@ -1,20 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta name="Author" content="OTI">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Other Reference Information</title>
-</head>
-<body>
-<h1>Other Reference Information</h1>
-<p>The following specifications, white papers, and design notes describe various 
-  aspects of the Java development tooling. </p>
-<ul>
-  <li><a href="overview-jdt.html">Map of Eclipse Java Development Tooling Plug-ins</a> 
-  </li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/reference/misc/overview-jdt.html b/bundles/org.eclipse.jdt.doc.isv/reference/misc/overview-jdt.html
deleted file mode 100644
index 78890ad..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/reference/misc/overview-jdt.html
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta name="Author" content="OTI">
-<title>JDT Overview - Map of JDT Plug-ins</title>
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-</head>
-<body>
-<h1>JDT Overview - Map of JDT Plug-ins</h1>
-<p>The Eclipse Java development tooling provides a comprehensive Java development 
-  environment. </p>
-<p>The Java development tooling itself is divided up into a number of separate 
-  plug-ins. The following table shows which API packages are found in which plug-ins as of
-Eclipse 3.0. This table is useful 
-  for determining which plug-ins a given plug-in should include as prerequisites. 
-</p>
-<table border="1" width="80%" align="center">
-  <tbody> 
-  <tr> 
-    <td><b>API Package</b></td>
-    <td><b>Required plug-in id</b></td>
-  </tr>
-  <tr> 
-    <td><tt>com.sun.jdi[.*]<br>
-      org.eclipse.jdi[.*]<br>
-      org.eclipse.jdt.debug[.*]</tt></td>
-    <td><tt>org.eclipse.jdt.debug</tt></td>
-  </tr>
-  <tr> 
-    <td><tt>org.eclipse.jdt.debug.ui[.*]</tt></td>
-    <td><tt>org.eclipse.jdt.debug.ui</tt><br>
-    </td>
-  </tr>
-  <tr> 
-    <td><tt>org.eclipse.jdt.core[.*]</tt></td>
-    <td><tt>org.eclipse.jdt.core</tt></td>
-  </tr>
-  <tr> 
-    <td><tt>org.eclipse.jdt.launching[.*]</tt></td>
-    <td><tt>org.eclipse.jdt.launching</tt></td>
-  </tr>
-  <tr> 
-    <td><tt>org.eclipse.jdt.ui[.*]</tt></td>
-    <td><tt>org.eclipse.jdt.ui</tt></td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.jdt.junit[.*]</tt></td>
-    <td><tt>org.eclipse.jdt.junit</tt></td>
-  </tr>
-  <tr>
-    <td><tt>junit.*</tt></td>
-    <td><tt>org.junit</tt></td>
-  </tr>
-  </tbody> 
-</table>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/samples/samples.html b/bundles/org.eclipse.jdt.doc.isv/samples/samples.html
deleted file mode 100644
index 1b8100c..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/samples/samples.html
+++ /dev/null

@@ -1,20 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Installing the examples</title>
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-</head>
-<body>
-<h1>Installing the examples</h1>
-To install the examples, download the zip file containing the examples.&nbsp; 
-<p> The workbench should not be running while the examples are being&nbsp; installed.&nbsp; 
-  Extract the contents of the zip file to the root directory&nbsp; of your Eclipse 
-  installation.</p>
-<p> For example, if you installed the Eclipse Project SDK on <b> d:\eclipse-sdk</b> 
-  then extract the contents of the examples zip file to <b>d:\eclipse-sdk</b>.</p>
-<p>Start the workbench. The example plug-ins should be installed.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/schema.css b/bundles/org.eclipse.jdt.doc.isv/schema.css
deleted file mode 100644
index 4efbf26..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/schema.css
+++ /dev/null

@@ -1,66 +0,0 @@
-H6.CaptionFigColumn#header {

-	font-size:16px; 

-	display:inline

-}

-

-P.Note#copyright {

-	font-size: smaller; 

-	font-style: normal;

-	color: #336699; 

-	display:inline;

-	margin-top: 3.000000pt;

-	margin-bottom: 11.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 0.000000pt;

-}

-

-P.Code#dtd {

-	color: #800000; 

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 10.000000pt;

-}

-

-P.Code#dtdAttlist {

-	color: #800000; 

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 20.000000pt;

-}

-

-P.Code#tag {

-	color: #000080; 

-	display:inline;

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 0.000000pt;

-}

-

-P.Code#cstring {

-	color: #008000; 

-	display:inline;

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 0.000000pt;	

-}

-

-.ConfigMarkup#elementDesc {

-	color: black;

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 10.000000pt;

-}

-

-.ConfigMarkup#attlistDesc {

-	color: black;

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 32.000000pt;

-}

-


diff --git a/bundles/org.eclipse.jdt.doc.isv/toc.xml b/bundles/org.eclipse.jdt.doc.isv/toc.xml
deleted file mode 100644
index 79528c2..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/toc.xml
+++ /dev/null

@@ -1,21 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define the top level topics                                                   -->
-<!-- ============================================================================= -->
-
-<toc label="JDT Plug-in Developer Guide">
-	<topic label="Programmer&apos;s Guide" href="guide/jdt_int.htm">
-		<link toc="topics_Guide.xml" />
-	</topic>
-	<topic label="Reference">
-		<link toc="topics_Reference.xml" />
-	</topic>
-	<topic label="Examples Guide">
-		<link toc="topics_Samples.xml" />
-	</topic>
-	<topic label="Questions Index" href="questions/index.html">
-		<link toc="topics_Questions.xml" />
-	</topic>
-	<topic label="Legal" href="notices.html"/>
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.isv/topics_Guide.xml b/bundles/org.eclipse.jdt.doc.isv/topics_Guide.xml
deleted file mode 100644
index 853b9b2..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/topics_Guide.xml
+++ /dev/null

@@ -1,36 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define topics for the main guide                                              -->
-<!-- ============================================================================= -->
-<toc label="Guide">
-	<topic label="JDT Core" href="guide/jdt_int_core.htm">
-		<topic label="Java model" href="guide/jdt_int_model.htm" />
-		<topic label="Manipulating Java code" href="guide/jdt_api_manip.htm" />
-		<topic label="Setting the Java build path" href="guide/jdt_api_classpath.htm" />
-		<topic label="Compiling Java code" href="guide/jdt_api_compile.htm" />
-		<topic label="Using the Java search engine" href="guide/jdt_api_search.htm" />
-		<topic label="Performing code assist on Java code" href="guide/jdt_api_codeassist.htm" />
-		<topic label="JDT Core options" href="guide/jdt_api_options.htm" />
-	</topic>
-	<topic label="JDT UI" href="guide/jdt_int_ui.htm">
-		<topic label="JavaUI utilities" href="guide/jdt_api_utility.htm">
-			<topic label="Opening a Java editor" href="guide/jdt_api_open_editor.htm" />
-			<topic label="Creating Java specific prompter dialogs" href="guide/jdt_api_prompter.htm" />
-		</topic>
-		<topic label="Presenting Java elements in a JFace viewer" href="guide/jdt_api_render.htm" />
-		<topic label="Java wizard pages" href="guide/jdt_api_wizards.htm" />
-		<topic label="Customizing Java editors" href="guide/jdt_api_editors.htm" />
-		<topic label="Writing Jar files" href="guide/jdt_api_write_jar_file.htm" />
-	</topic>
-	<topic label="JDT Debug" href="guide/jdt_int_debug.htm">
-		<topic label="Running Java code" href="guide/jdt_api_run.htm" />
-	</topic>
-	<topic label="JDT JUnit integration" href="guide/jdt_int_junit.htm">
-		<topic label="Observing JUnit test runs" href="guide/jdt_api_junit.htm" />
-	</topic>
-	<topic label="JDT Annotation Processing" href="guide/jdt_int_apt.htm">
-		<topic label="Getting Started" href="guide/jdt_apt_getting_started.htm"/>
-		<topic label="Headless Build" href="guide/jdt_apt_building_with_apt.htm"/>
-	</topic>
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.isv/topics_Questions.xml b/bundles/org.eclipse.jdt.doc.isv/topics_Questions.xml
deleted file mode 100644
index ad5a504..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/topics_Questions.xml
+++ /dev/null

@@ -1,7 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define topics for the questions index                                         -->
-<!-- ============================================================================= -->
-<toc label="Questions">
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.isv/topics_Reference.xml b/bundles/org.eclipse.jdt.doc.isv/topics_Reference.xml
deleted file mode 100644
index be0e6b5..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/topics_Reference.xml
+++ /dev/null

@@ -1,77 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define topics for the references                                              -->
-<!-- ============================================================================= -->
-<toc label="Reference">
-	<topic label="API Reference" href="reference/api/overview-summary.html">
-       <topic label="org.eclipse.jdt.core" href="reference/api/org/eclipse/jdt/core/package-summary.html"/>
-       <topic label="org.eclipse.jdt.core.compiler" href="reference/api/org/eclipse/jdt/core/compiler/package-summary.html"/>
-       <topic label="org.eclipse.jdt.core.dom" href="reference/api/org/eclipse/jdt/core/dom/package-summary.html"/>
-       <topic label="org.eclipse.jdt.core.dom.rewrite" href="reference/api/org/eclipse/jdt/core/dom/rewrite/package-summary.html"/>
-       <topic label="org.eclipse.jdt.core.eval" href="reference/api/org/eclipse/jdt/core/eval/package-summary.html"/>
-       <topic label="org.eclipse.jdt.core.formatter" href="reference/api/org/eclipse/jdt/core/formatter/package-summary.html"/>
-       <topic label="org.eclipse.jdt.core.jdom" href="reference/api/org/eclipse/jdt/core/jdom/package-summary.html"/>
-       <topic label="org.eclipse.jdt.core.util" href="reference/api/org/eclipse/jdt/core/util/package-summary.html"/>
-       <topic label="org.eclipse.jdt.core.search" href="reference/api/org/eclipse/jdt/core/search/package-summary.html"/>
-       <topic label="org.eclipse.jdt.debug.core" href="reference/api/org/eclipse/jdt/debug/core/package-summary.html"/>
-       <topic label="org.eclipse.jdt.debug.eval" href="reference/api/org/eclipse/jdt/debug/eval/package-summary.html"/>
-       <topic label="org.eclipse.jdt.debug.ui" href="reference/api/org/eclipse/jdt/debug/ui/package-summary.html"/>
-       <topic label="org.eclipse.jdt.debug.ui.launchConfigurations" href="reference/api/org/eclipse/jdt/debug/ui/launchConfigurations/package-summary.html"/>
-       <topic label="org.eclipse.jdt.launching" href="reference/api/org/eclipse/jdt/launching/package-summary.html"/>
-       <topic label="org.eclipse.jdt.launching.environments" href="reference/api/org/eclipse/jdt/launching/environments/package-summary.html"/>
-       <topic label="org.eclipse.jdt.launching.sourcelookup" href="reference/api/org/eclipse/jdt/launching/sourcelookup/package-summary.html"/>
-       <topic label="org.eclipse.jdt.launching.sourcelookup.containers" href="reference/api/org/eclipse/jdt/launching/sourcelookup/containers/package-summary.html"/>
-       <topic label="org.eclipse.jdt.ui" href="reference/api/org/eclipse/jdt/ui/package-summary.html"/>
-       <topic label="org.eclipse.jdt.ui.actions" href="reference/api/org/eclipse/jdt/ui/actions/package-summary.html"/>
-       <topic label="org.eclipse.jdt.ui.jarpackager" href="reference/api/org/eclipse/jdt/ui/jarpackager/package-summary.html"/>
-       <topic label="org.eclipse.jdt.ui.refactoring" href="reference/api/org/eclipse/jdt/ui/refactoring/package-summary.html"/>
-       <topic label="org.eclipse.jdt.ui.search" href="reference/api/org/eclipse/jdt/ui/search/package-summary.html"/>
-       <topic label="org.eclipse.jdt.ui.text" href="reference/api/org/eclipse/jdt/ui/text/package-summary.html"/>
-       <topic label="org.eclipse.jdt.ui.text.folding" href="reference/api/org/eclipse/jdt/ui/text/folding/package-summary.html"/>
-       <topic label="org.eclipse.jdt.ui.text.java" href="reference/api/org/eclipse/jdt/ui/text/java/package-summary.html"/>
-       <topic label="org.eclipse.jdt.ui.text.java.hover" href="reference/api/org/eclipse/jdt/ui/text/java/hover/package-summary.html"/>
-       <topic label="org.eclipse.jdt.ui.wizards" href="reference/api/org/eclipse/jdt/ui/wizards/package-summary.html"/>
-       <topic label="org.eclipse.jdt.junit" href="reference/api/org/eclipse/jdt/junit/package-summary.html"/>
-	</topic>
-
-	<topic label="APT API Reference" href="reference/apt/overview-summary.html">
-       <topic label="com.sun.mirror.apt" href="reference/apt/com/sun/mirror/apt/package-summary.html"/>
-       <topic label="com.sun.mirror.declaration" href="reference/apt/com/sun/mirror/declaration/package-summary.html"/>
-       <topic label="com.sun.mirror.type" href="reference/apt/com/sun/mirror/type/package-summary.html"/>
-       <topic label="com.sun.mirror.util" href="reference/apt/com/sun/mirror/util/package-summary.html"/>
-       <topic label="org.eclipse.jdt.apt.core.build" href="reference/apt/org/eclipse/jdt/apt/core/build/package-summary.html"/>
-       <topic label="org.eclipse.jdt.apt.core.env" href="reference/apt/org/eclipse/jdt/apt/core/env/package-summary.html"/>
-       <topic label="org.eclipse.jdt.apt.core.util" href="reference/apt/org/eclipse/jdt/apt/core/util/package-summary.html"/>
-	</topic>
-
-	<topic label="Extension Points Reference" href="reference/extension-points/index.html">
-         <topic label="org.eclipse.jdt.core.classpathVariableInitializer" href="reference/extension-points/org_eclipse_jdt_core_classpathVariableInitializer.html"/>
-         <topic label="org.eclipse.jdt.core.classpathContainerInitializer" href="reference/extension-points/org_eclipse_jdt_core_classpathContainerInitializer.html"/>
-         <topic label="org.eclipse.jdt.core.codeFormatter" href="reference/extension-points/org_eclipse_jdt_core_codeFormatter.html"/>
-         <topic label="org.eclipse.jdt.debug.javaLogicalStructures" href="reference/extension-points/org_eclipse_jdt_debug_javaLogicalStructures.html"/>
-         <topic label="org.eclipse.jdt.debug.ui.vmInstallTypePage" href="reference/extension-points/org_eclipse_jdt_debug_ui_vmInstallTypePage.html"/>
-         <topic label="org.eclipse.jdt.junit.junitLaunchConfigs" href="reference/extension-points/org_eclipse_jdt_junit_junitLaunchConfigs.html"/>
-         <topic label="org.eclipse.jdt.junit.testRunListeners" href="reference/extension-points/org_eclipse_jdt_junit_testRunListeners.html"/>
-         <topic label="org.eclipse.jdt.launching.classpathProviders" href="reference/extension-points/org_eclipse_jdt_launching_classpathProviders.html"/>
-         <topic label="org.eclipse.jdt.launching.executionEnvironments" href="reference/extension-points/org_eclipse_jdt_launching_executionEnvironments.html"/>
-         <topic label="org.eclipse.jdt.launching.runtimeClasspathEntries" href="reference/extension-points/org_eclipse_jdt_launching_runtimeClasspathEntries.html"/>
-         <topic label="org.eclipse.jdt.launching.runtimeClasspathEntryResolvers" href="reference/extension-points/org_eclipse_jdt_launching_runtimeClasspathEntryResolvers.html"/>
-         <topic label="org.eclipse.jdt.launching.vmConnectors" href="reference/extension-points/org_eclipse_jdt_launching_vmConnectors.html"/>
-         <topic label="org.eclipse.jdt.launching.vmInstalls" href="reference/extension-points/org_eclipse_jdt_launching_vmInstalls.html"/>
-         <topic label="org.eclipse.jdt.launching.vmInstallTypes" href="reference/extension-points/org_eclipse_jdt_launching_vmInstallTypes.html"/>
-         <topic label="org.eclipse.jdt.ui.classpathContainerPage" href="reference/extension-points/org_eclipse_jdt_ui_classpathContainerPage.html"/>
-         <topic label="org.eclipse.jdt.ui.foldingStructureProviders" href="reference/extension-points/org_eclipse_jdt_ui_foldingStructureProviders.html"/>
-         <topic label="org.eclipse.jdt.ui.javaCompletionProposalComputer" href="reference/extension-points/org_eclipse_jdt_ui_javaCompletionProposalComputer.html"/>
-         <topic label="org.eclipse.jdt.ui.javaCompletionProposalSorters" href="reference/extension-points/org_eclipse_jdt_ui_javaCompletionProposalSorters.html"/>
-         <topic label="org.eclipse.jdt.ui.javadocCompletionProcessor" href="reference/extension-points/org_eclipse_jdt_ui_javadocCompletionProcessor.html"/>
-         <topic label="org.eclipse.jdt.ui.javaEditorTextHovers" href="reference/extension-points/org_eclipse_jdt_ui_javaEditorTextHovers.html"/>
-         <topic label="org.eclipse.jdt.ui.javaElementFilters" href="reference/extension-points/org_eclipse_jdt_ui_javaElementFilters.html"/>
-         <topic label="org.eclipse.jdt.ui.queryParticipants" href="reference/extension-points/org_eclipse_jdt_ui_queryParticipants.html"/>
-         <topic label="org.eclipse.jdt.ui.quickAssistProcessors" href="reference/extension-points/org_eclipse_jdt_ui_quickAssistProcessors.html"/>
-         <topic label="org.eclipse.jdt.ui.quickFixProcessors" href="reference/extension-points/org_eclipse_jdt_ui_quickFixProcessors.html"/>
-	</topic>
-	<topic label="Other Reference Information" href="reference/misc/index.html">
-      	<topic label="JDT Plug-ins Map" href="reference/misc/overview-jdt.html"/>
-	</topic>
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.isv/topics_Samples.xml b/bundles/org.eclipse.jdt.doc.isv/topics_Samples.xml
deleted file mode 100644
index c38cf71..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/topics_Samples.xml
+++ /dev/null

@@ -1,10 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define topics for the samples                                                 -->
-<!-- ============================================================================= -->
-<toc label="Examples" >
-   <topic label="Installing the Examples" href="samples/samples.html" />
-   <topic label="Java Example Projects" href="samples/org.eclipse.jdt.ui.examples.projects/doc-html/jdt_projects_ex.html" />
-	 
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.user/.project b/bundles/org.eclipse.jdt.doc.user/.project
deleted file mode 100644
index 682c2c2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/.project
+++ /dev/null

@@ -1,11 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
-	<name>org.eclipse.jdt.doc.user</name>
-	<comment></comment>
-	<projects>
-	</projects>
-	<buildSpec>
-	</buildSpec>
-	<natures>
-	</natures>
-</projectDescription>

diff --git a/bundles/org.eclipse.jdt.doc.user/META-INF/MANIFEST.MF b/bundles/org.eclipse.jdt.doc.user/META-INF/MANIFEST.MF
deleted file mode 100644
index d8f999b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/META-INF/MANIFEST.MF
+++ /dev/null

@@ -1,8 +0,0 @@
-Manifest-Version: 1.0
-Bundle-ManifestVersion: 2
-Bundle-Name: %pluginName
-Bundle-SymbolicName: org.eclipse.jdt.doc.user; singleton:=true
-Bundle-Version: 3.2.0.qualifier
-Bundle-Vendor: %providerName
-Bundle-Localization: plugin
-Eclipse-LazyStart: true

diff --git a/bundles/org.eclipse.jdt.doc.user/about.html b/bundles/org.eclipse.jdt.doc.user/about.html
deleted file mode 100644
index e336131..0000000
--- a/bundles/org.eclipse.jdt.doc.user/about.html
+++ /dev/null

@@ -1,23 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<title>About</title>
-<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
-</head>
-<body lang="EN-US">
-<h2>About This Content</h2>
- 
-<p>February 24, 2005</p>	
-<h3>License</h3>
-
-<p>The Eclipse Foundation makes available all content in this plug-in (&quot;Content&quot;).  Unless otherwise indicated below, the Content is provided to you under the terms and conditions of the
-Eclipse Public License Version 1.0 (&quot;EPL&quot;).  A copy of the EPL is available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
-For purposes of the EPL, &quot;Program&quot; will mean the Content.</p>
-
-<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is being redistributed by another party (&quot;Redistributor&quot;) and different terms and conditions may
-apply to your use of any object code in the Content.  Check the Redistributor's license that was provided with the Content.  If no such license exists, contact the Redistributor.  Unless otherwise
-indicated below, the terms and conditions of the EPL still apply to any source code in the Content.</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.user/about.ini b/bundles/org.eclipse.jdt.doc.user/about.ini
deleted file mode 100644
index df1510b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/about.ini
+++ /dev/null

@@ -1,24 +0,0 @@
-# about.ini
-# contains information about a feature
-# java.io.Properties file (ISO 8859-1 with "\" escapes)
-# "%key" are externalized strings defined in about.properties
-# This file does not need to be translated.
-
-# Property "aboutText" contains blurb for "About" dialog (translated)
-aboutText=%blurb
-
-# Property "windowImage" contains path to window icon (16x16)
-# needed for primary features only
-
-# Property "featureImage" contains path to feature image (32x32)
-featureImage=eclipse32.png
-
-# Property "aboutImage" contains path to product image (500x330 or 115x164)
-# needed for primary features only
-
-# Property "appName" contains name of the application (translated)
-# needed for primary features only
-
-# Property "welcomePage" contains path to welcome page (special XML-based format)
-# optional
-

diff --git a/bundles/org.eclipse.jdt.doc.user/about.mappings b/bundles/org.eclipse.jdt.doc.user/about.mappings
deleted file mode 100644
index bddaab4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/about.mappings
+++ /dev/null

@@ -1,6 +0,0 @@
-# about.mappings
-# contains fill-ins for about.properties
-# java.io.Properties file (ISO 8859-1 with "\" escapes)
-# This file does not need to be translated.
-
-0=@build@
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.user/about.properties b/bundles/org.eclipse.jdt.doc.user/about.properties
deleted file mode 100644
index 4f3adf5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/about.properties
+++ /dev/null

@@ -1,24 +0,0 @@
-###############################################################################
-# Copyright (c) 2000, 2005 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-# about.properties
-# contains externalized strings for about.ini
-# java.io.Properties file (ISO 8859-1 with "\" escapes)
-# fill-ins are supplied by about.mappings
-# This file should be translated.
-
-blurb=Eclipse Java Development Tooling User Guide\n\
-\n\
-Version: {featureVersion}\n\
-Build id: {0}\n\
-\n\
-(c) Copyright IBM Corp. and others 2000, 2004.  All rights reserved.\n\
-Visit http://www.eclipse.org/jdt
-

diff --git a/bundles/org.eclipse.jdt.doc.user/book.css b/bundles/org.eclipse.jdt.doc.user/book.css
deleted file mode 100644
index aaa2f1e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/book.css
+++ /dev/null

@@ -1,13 +0,0 @@
-@import "../PRODUCT_PLUGIN/book.css";
-
-span.control {
-  font-weight: bold;
-}
-
-span.name {
-  font-style: italic;
-}
-
-span.code {
-  font-family: monospace;
-}

diff --git a/bundles/org.eclipse.jdt.doc.user/build.properties b/bundles/org.eclipse.jdt.doc.user/build.properties
deleted file mode 100644
index 527729e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/build.properties
+++ /dev/null

@@ -1,12 +0,0 @@
-###############################################################################
-# Copyright (c) 2000, 2005 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-# use provided build.xml
-custom=true
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.user/build.xml b/bundles/org.eclipse.jdt.doc.user/build.xml
deleted file mode 100644
index e3719aa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/build.xml
+++ /dev/null

@@ -1,96 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<project name="org.eclipse.jdt.doc.user" default="build.jars" basedir=".">
-
-	<property name="version.suffix" value="3.2.0"/>
-	<property name="full.name" value="org.eclipse.jdt.doc.user_${version.suffix}"/>
-	<property name="bootclasspath" value=""/>
-	<property name="basews" value="${ws}"/>
-	<property name="baseos" value="${os}"/>
-	<property name="basearch" value="${arch}"/>
-	<property name="basenl" value="${nl}"/>
-	<property name="javacFailOnError" value="false"/>
-	<property name="javacDebugInfo" value="on"/>
-	<property name="javacVerbose" value="true"/>
-	<property name="javacSource" value="1.3"/>
-	<property name="javacTarget" value="1.1"/>
-
-	<target name="init" depends="properties">
-		<property name="temp.folder" value="${basedir}/temp.folder"/>
-		<property name="plugin.destination" value="${basedir}"/>
-		<property name="build.result.folder" value="${basedir}"/>
-		<available file="${basedir}/doc.zip" property="doc.zip.present"/>
-	</target>
-
-	<target name="properties" if="eclipse.running">
-		<property name="build.compiler" value="org.eclipse.jdt.core.JDTCompilerAdapter"/>
-	</target>
-
-	<target name="build.update.jar" depends="init" description="Build the plug-in: org.eclipse.jdt.doc.user for an update site.">
-		<delete dir="${temp.folder}"/>
-		<mkdir dir="${temp.folder}"/>
-		<antcall target="build.jars"/>
-		<antcall target="gather.bin.parts">
-			<param name="destination.temp.folder" value="${temp.folder}/"/>
-		</antcall>
-		<zip zipfile="${plugin.destination}/${full.name}.jar" basedir="${temp.folder}/${full.name}" filesonly="false" whenempty="skip"/>
-		<delete dir="${temp.folder}"/>
-	</target>
-
-	<target name="gather.bin.parts" depends="init" if="destination.temp.folder">
-		<antcall target="build.index"/>		
-		<mkdir dir="${destination.temp.folder}/${full.name}"/>
-		<copy todir="${destination.temp.folder}/${full.name}">
-			<fileset dir="${basedir}" includes="*.properties,*.xml,*.zip,*.html,*.htm,*.png,*.css,META-INF/**,index/**,concepts/**, gettingStarted/**, images/**, reference/**, tasks/**, tips/**, whatsNew/**" excludes="build.properties,build.xml"/>
-		</copy>
-		<eclipse.versionReplacer path="${destination.temp.folder}/${full.name}" version="${version.suffix}"/>
-	</target>
-
-	<target name="build.jars" depends="init" description="Build all the jars for the plug-in: org.eclipse.jdt.doc.user.">
-	</target>
-	
-	<target name="build.index" depends="init" description="Builds search index for the plug-in: org.eclipse.jdt.doc.user." if="eclipse.running">
-		<help.buildHelpIndex manifest="plugin.xml" destination="."/>
-	</target>
-
-	<target name="build.sources" depends="init">
-	</target>
-
-	<target name="build.zips" depends="init">
-	</target>
-
-	<target name="gather.sources" depends="init" if="destination.temp.folder">
-	</target>
-
-	<target name="gather.logs" depends="init" if="destination.temp.folder">
-	</target>
-
-	<target name="clean" depends="init" description="Clean the plug-in: org.eclipse.jdt.doc.user of all the zips, jars and logs created.">
-		<delete file="${plugin.destination}/${full.name}.jar"/>
-		<delete file="${plugin.destination}/${full.name}.zip"/>
-		<delete dir="${temp.folder}"/>
-	</target>
-
-	<target name="refresh" depends="init" if="eclipse.running" description="Refresh this folder.">
-		<eclipse.convertPath fileSystemPath="D:/30workspace/org.eclipse.jdt.doc.user/" property="resourcePath"/>
-		<eclipse.refreshLocal resource="${resourcePath}" depth="infinite"/>
-	</target>
-
-	<target name="zip.plugin" depends="init" description="Create a zip containing all the elements for the plug-in: org.eclipse.jdt.doc.user." if="eclipse.running">
-		<delete dir="${temp.folder}"/>
-		<mkdir dir="${temp.folder}"/>
-		<antcall target="build.jars"/>
-		<antcall target="build.sources"/>
-		<antcall target="gather.bin.parts">
-			<param name="destination.temp.folder" value="${temp.folder}/"/>
-		</antcall>
-		<antcall target="gather.sources">
-			<param name="destination.temp.folder" value="${temp.folder}/"/>
-		</antcall>
-		<delete>
-			<fileset dir="${temp.folder}" includes="**/*.bin.log"			/>
-		</delete>
-		<zip zipfile="${plugin.destination}/${full.name}.zip" basedir="${temp.folder}" filesonly="true" whenempty="skip"/>
-		<delete dir="${temp.folder}"/>
-	</target>
-
-</project>

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/cbrkpnts.htm b/bundles/org.eclipse.jdt.doc.user/concepts/cbrkpnts.htm
deleted file mode 100644
index 076c4d9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/cbrkpnts.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Breakpoints</title>
-  </head>
-
-  <body>
-    <h1>Breakpoints</h1>
-
-    <p>A breakpoint causes the execution of a program thread to suspend at the location where the breakpoint is set.</p>
-
-    <p>Breakpoints can be enabled and disabled via their context menus in the Breakpoints view.</p>
-
-    <ul>
-      <li>When a breakpoint is enabled, it will cause a thread to suspend whenever
-        the breakpoint is reached. Enabled breakpoints are indicated with a blue circle. Enabled breakpoints
-        are shown with a checkmark overlay after their class is loaded by the VM
-        and the breakpoint is successfully installed.</li>
-
-      <li>When a breakpoint is disabled, it will not cause threads to suspend. Disabled breakpoints are indicated with a white circle.</li>
-    </ul>
-
-    <p>Breakpoints are displayed in the vertical editor ruler and in the Breakpoints view.</p>
-
-    <p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-    <p>
-     <a href="../tasks/tasks-144.htm">Adding breakpoints</a><br>
-     <a href="../tasks/tasks-135.htm">Resuming the execution of suspended threads</a><br>
-     <a href="../tasks/tasks-126.htm">Running and debugging</a><br>
-     <a href="../tasks/tasks-134.htm">Suspending threads</a></p>
-
-    <p><img border="0" src="../images/ngrelr.png" alt="Related reference" ></p>
-    <p>
-     <a href="../reference/ref-11.htm">Debug preferences</a><br>
-     <a href="../reference/ref-51.htm">Debug view</a><a href="../reference/ref-4.htm"><br>
-    Run menu</a><br>
-     <a href="../reference/ref-4.htm">Run and debug actions</a><br>
-     <a href="../reference/ref-35.htm">Breakpoints view</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/cbuildcp.htm b/bundles/org.eclipse.jdt.doc.user/concepts/cbuildcp.htm
deleted file mode 100644
index 6168384..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/cbuildcp.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Build classpath</title>
-  </head>
-
-  <body>
-    <h1>Build classpath</h1>
-
-    <p>The build classpath is the path which is used to find classes that are
-    referenced by your source code. During compilation, this path is used
-    to search for classes outside of your project. The build classpath is
-    specified for each project. In the project properties, it is referred
-    to as the &quot;Java Build Path.&quot;</p>
-
-    <p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ></p>
-    <p>
-     <a href="concepts-4.htm">Java builder</a><br>
-     <a href="cclsspthv.htm">Classpath variable</a><br>
-     <a href="filters.htm">Exclusion and inclusion filters</a><br>
-     <a href="rules.htm">Access rules</a>
-    </p>
-
-    <p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-    <p>
-     <a href="../tasks/tasks-113.htm">Adding a JAR file to the build path</a><br>
-     <a href="../tasks/tasks-112.htm">Adding a class folder to the build path</a><br>
-     <a href="../tasks/tasks-106.htm">Building a Java program</a><br>
-     <a href="../tasks/tasks-108.htm">Building automatically</a><br>
-     <a href="../tasks/tasks-109.htm">Building manually</a><br>
-     <a href="../tasks/tasks-111.htm">Viewing and editing a project's build path</a><br>
-     <a href="../tasks/tasks-110.htm">Working with build paths</a><br>
-	 <a href="../tasks/tasks-221.htm">Creating a new source folder with exclusion filter</a><br>
-	 <a href="../tasks/tasks-222.htm">Creating a new source folder with specific output folder</a>
-    </p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-     <a href="../reference/ref-15.htm">Classpath Variables preferences</a><br>
-     <a href="../reference/ref-123.htm">Java Build Path properties</a><br>
-    </p>
-
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/cclsspthv.htm b/bundles/org.eclipse.jdt.doc.user/concepts/cclsspthv.htm
deleted file mode 100644
index 080668a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/cclsspthv.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Classpath variables</title>
-  </head>
-
-  <body>
-    <h1>Classpath variables</h1>
-
-    <p>The build path for a Java project can include source code files, other
-    Java projects, and JAR files. JAR files can be specified using file
-    system paths, or by using variables that refer to locations on the
-    network.&nbsp;</p>
-
-    <p>Classpath variables allow you to avoid references to the location of a JAR
-    file on your local file system. By using a classpath variable, you can
-    specify a JAR file or library using only a variable name, such as JRE_LIB,
-    rather than specifying the location of the JRE on your workstation. In
-    this way, you can share build paths across teams and define the variables to
-    refer to the correct location for your particular computer.</p>
-
-    <p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ></p>
-    <p>
-     <a href="concepts-1.htm">Java development tools (JDT)</a><br>
-     <a href="cbuildcp.htm">Build classpath</a></p>
-
-    <p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-    <p>
-     <a href="../tasks/tasks-114.htm">Adding a variable classpath entry</a><br>
-     <a href="../tasks/tasks-116.htm">Attaching source to a classpath variable</a><br>
-     <a href="../tasks/tasks-117.htm">Defining a classpath variable</a><br>
-     <a href="../tasks/tasks-118.htm">Deleting a classpath variable</a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ></p>
-    <p>
-     <a href="../reference/ref-15.htm">Classpath Variables preferences</a><br>
-     <a href="../reference/ref-123.htm">Java Build Path properties</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/clocdbug.htm b/bundles/org.eclipse.jdt.doc.user/concepts/clocdbug.htm
deleted file mode 100644
index 4a947c5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/clocdbug.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Local debugging</title>
-  </head>
-
-  <body>
-    <h1>Local debugging</h1>
-
-    <p>The Java debugger has a client/server design so that it can be used to
-    debug programs that run locally (on the same workstation as the debugger) or
-    remotely (on another computer on the network).</p>
-
-    <p>Local debugging is the simplest and most common kind of debugging.&nbsp;
-    After you have finished editing and building your Java program, you can
-    launch the program on your workstation using the <strong>Run &gt; Debug...</strong> menu item
-    on the workbench.&nbsp; Launching the program in this way will establish a
-    connection between the debugger client and the Java program that you are
-    launching.&nbsp; You may then use breakpoints, stepping, or expression
-    evaluation to debug your program.</p>
-
-    <p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ></p>
-    <p>
-    <a href="cbrkpnts.htm">Breakpoints</a></p>
-    <p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-    <p>
-    <a href="../tasks/tasks-144.htm">Adding breakpoints</a><br>
-    <a href="../tasks/tasks-135.htm">Resuming the execution of suspended threads</a><br>
-    <a href="../tasks/tasks-126.htm">Running and debugging</a><br>
-    <a href="../tasks/tasks-134.htm">Suspending threads</a></p>
-    <p><img border="0" src="../images/ngrelr.png" alt="Related reference" ></p>
-    <p>
-    <a href="../reference/ref-11.htm">Debug preferences</a><br>
-    <a href="../reference/ref-51.htm">Debug view</a><br>
-    <a href="../reference/ref-4.htm">Run and debug actions</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/cnls.htm b/bundles/org.eclipse.jdt.doc.user/concepts/cnls.htm
deleted file mode 100644
index 4af31c9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/cnls.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>String externalization</title>
-  </head>
-
-  <body>
-    <h1>String externalization</h1>
-
-    <p>The Java tools help you to develop applications that can be run on
-    international platforms. An important facet of designing a program for
-    use in different countries is the localization, or externalization, of text
-    that is displayed by the program. By externalizing strings, the text
-    can be translated for different countries and languages without rebuilding
-    the Java program.</p>
-
-    
-<p>The JDT provides the following support for internationalization and string 
-  externalization:</p>
-
-    
-<ul>
-  <li> A compiler option lets you mark non-externalized strings as compile-time 
-    warnings or errors. 
-    <ul>
-      <li>See the <span class="control">Window &gt; Preferences &gt; Java &gt; 
-        Compiler &gt; Errors/Warnings &gt; Code style &gt; Usage of non-externalized strings</span> preference</li>
-    </ul>
-  </li>
-  <li>Tools that allow you to find strings that have not been externalized.</li>
-  <li>A wizard that will guide you through externalizing the strings.</li>
-  <li>Tools that help you to find unused and incorrectly used keys for strings 
-    located in property files.</li>
-</ul>
-
-    <p>Comments can be used to denote strings that should not be externalized
-    and should not result in compile-time warnings or errors. These comments are of form <code>//$NON-NLS-n$</code>
-    where n is the 1-based index of the string in a line of code.</p>
-    <p>Additional information about internationalized applications can be found
-    in the following documents:</p>
-
-    <ul>
-      <li><a href=
-      "http://eclipse.org/articles/Article-Internationalization/how2I18n.html">http://eclipse.org/articles/Article-Internationalization/how2I18n.html</a></li>
-
-      <li><a href="http://java.sun.com/docs/books/tutorial/i18n/intro/index.html" target="_blank">http://java.sun.com/docs/books/tutorial/i18n/intro/index.html</a></li>
-    </ul>
-
-    <p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-    <p>
-     <a href="../tasks/tasks-188.htm">Finding strings to externalize</a><br>
-     <a href="../tasks/tasks-202.htm">Finding unused and incorrectly used keys in property files</a><br>
-     <a href="../tasks/tasks-180.htm">Using the Externalize Strings wizard</a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ></p>
-    <p>
-     <a href="../reference/ref-menu-source.htm">Source menu</a><br>
-     <a href="../reference/ref-wizard-externalize-strings.htm">Externalize Strings wizard</a><br>
-     <a href="../reference/ref-preferences-compiler.htm">Java Compiler preferences</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concepts-1.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concepts-1.htm
deleted file mode 100644
index b43ebeb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concepts-1.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Java development tools (JDT)</title>
-  </head>
-
-  <body>
-    <h1>Java development tools (JDT)</h1>
-
-    <p>The Java development tools (JDT) are a set of extensions to the workbench that
-    allow you to edit, compile, and run Java programs.</p>
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-    <p>
-     <a href="cbuildcp.htm">Build classpath</a><br>
-     <a href="../concepts/cclsspthv.htm">Classpath variables</a><br>
-     <a href="../concepts/concepts-10.htm">Debugger</a><br>
-     <a href="../concepts/concepts-4.htm">Java builder</a><br>
-     <a href="../concepts/concepts-7.htm">Java editor</a><br>
-     <a href="../concepts/concepts-3.htm">Java projects</a><br>
-     <a href="../concepts/concepts-5.htm">Java perspectives</a><br>
-     <a href="../concepts/concepts-6.htm">Java views</a><br>
-     <a href="../concepts/concepts-8.htm">Java search</a><br>
-     <a href="../concepts/concepts-9.htm">Refactoring support</a><br>
-     <a href="../concepts/concepts-11.htm">Scrapbook</a></p>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-    <p>
-     <a href="../tasks/tasks-31.htm">Adding source code as individual files</a><br>
-     <a href="../tasks/tasks-11.htm">Creating Java elements</a><br>
-     <a href="../tasks/tasks-66.htm">Formatting Java code</a><br>
-     <a href="../tasks/tasks-64.htm">Restoring a deleted workbench element</a><br>
-     <a href="../tasks/tasks-2.htm">Showing and hiding files</a><br>
-     <a href="../tasks/tasks-JREs.htm">Working with JREs</a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ></p>
-    <p>
-     <a href="../reference/ref-2.htm">JDT actions</a><br>
-     <a href="../reference/ref-152.htm">Frequently asked questions on JDT</a><br>
-     <a href="../reference/ref-155.htm">JDT glossary</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concepts-10.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concepts-10.htm
deleted file mode 100644
index d9e495f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concepts-10.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Debugger</title>
-  </head>
-
-  <body>
-    <h1>Debugger</h1>
-
-    <p>The JDT includes a debugger that enables you to detect and diagnose errors in your programs running either locally or remotely.</p>
-
-    <p>The debugger allows you to control the execution of your program by setting breakpoints, suspending
-    launched programs, stepping through your code, and examining the contents of
-    variables.</p>
-
-    <p>The debugger has a client/server design so you can debug programs running remotely on other systems in the network as well as programs running locally on your workstation.
-    The debug client runs inside the workbench on your workstation.&nbsp; The debugger server runs on the same system as the program you want to
-    debug.&nbsp; This could be a program launched on your workstation (local debugging) or a
-    program started on a computer that is accessible through a
-    network (remote debugging).</p>
-
-    <p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ></p>
-    <p>
-     <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a><br>
-     <a href="../concepts/cbrkpnts.htm">Breakpoints</a><br>
-     <a href="cremdbug.htm">Remote debugging</a><br>
-     <a href="clocdbug.htm">Local debugging</a></p>
-
-    <p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-    <p>
-     <a href="../tasks/tasks-144.htm">Adding breakpoints</a><br>
-     <a href="../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-     <a href="../tasks/tasks-141.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-     <a href="../tasks/tasks-142.htm">Disconnecting from a VM</a><br>
-     <a href="../tasks/tasks-138.htm">Evaluating expressions</a><br>
-     <a href="../tasks/tasks-130.htm">Launching a Java program</a><br>
-     <a href="../tasks/tasks-133.htm">Preparing to debug</a><br>
-     <a href="../tasks/tasks-135.htm">Resuming the execution of suspended threads</a><br>
-     <a href="../tasks/tasks-126.htm">Running and debugging</a><br>
-     <a href="../tasks/tasks-134.htm">Suspending threads</a><br>
-    </p>
-
-    <p><img border="0" src="../images/ngrelr.png" alt="Related reference" ></p>
-    <p>
-     <a href="../reference/ref-11.htm">Debug preferences</a><br>
-     <a href="../reference/ref-51.htm">Debug view</a><br>
-     <a href="../reference/ref-4.htm">Run and debug actions</a><br>
-    </p>
-
-    <p><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concepts-11.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concepts-11.htm
deleted file mode 100644
index 65950af..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concepts-11.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Scrapbook</title>
-  </head>
-
-  <body>
-    <h1>Scrapbook</h1>
-
-    <p>The JDT contributes a scrapbook facility that can be used to experiment and evaluate Java
-    code snippets before building a complete Java program. Snippets are edited and evaluated in the Scrapbook page
-    editor, with resultant problems reported in the editor.</p>
-
-    <p>From a Java scrapbook editor, you can select a code snippet, evaluate it, and display the result as a string.
-    You can also show the object that results from evaluating a code snippet in the debugger's expressions view.</p>
-
-    <p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ></p>
-    <p>
-     <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a><br>
-     <a href="../concepts/concepts-10.htm">Debugger</a></p>
-
-    <p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-    <p>
-     <a href="../tasks/tasks-149.htm">Creating a Java scrapbook page</a><br>
-     <a href="../tasks/tasks-151.htm">Displaying the result of evaluating an expression</a><br>
-     <a href="../tasks/tasks-150.htm">Inspecting the result of evaluating an expression</a><br>
-     <a href="../tasks/tasks-65.htm">Using content/code assist</a><br>
-     <a href="../tasks/tasks-107.htm">Viewing compilation errors and warnings</a></p>
-
-    <p><img border="0" src="../images/ngrelr.png" alt="Related reference" ></p>
-    <p>
-     <a href="../reference/ref-129.htm">New Java Scrapbook Page wizard</a><br>
-     <a href="../reference/ref-34.htm">Java scrapbook page</a><br>
-     <a href="../reference/ref-56.htm">Expressions view</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concepts-3.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concepts-3.htm
deleted file mode 100644
index 1217ab7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concepts-3.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Java projects</title>
-  </head>
-
-  <body>
-    <h1>Java projects</h1>
-
-    <p>A Java project contains source code and related files for building a Java
-    program. It has an associated Java builder that can incrementally compile Java source files as they are changed.</p>
-
-    <p>A Java project also maintains a model of its contents. This model
-    includes information about the type hierarchy, references and declarations of Java elements.
-    This information is constantly updated as the user changes
-    the Java source code. The updating of the internal Java project model is independent of the
-    Java builder; in particular, when performing code modifications, if auto-build is turned
-    off, the model will still reflect the present project contents.</p>
-
-    <p>You can organize Java projects in two different ways:</p>
-
-    <ul>
-      <li><span>Using the project as the source container. This is the recommended organization for simple projects.</span></li>
-
-      <li><span>Using source folders inside the project as the source container. This is the recommended organization for more complex projects. It allows you to subdivide packages into
-      groups.</span></li>
-    </ul>
-
-    <p><img  src="../images/ngrelc.png" alt="Related concepts" border="0"></p>
-    <p>
-     <a href="concepts-4.htm">Java builder</a><br>
-     <a href="../concepts/concepts-9.htm">Refactoring support</a></p>
-
-    <p><img border="0"  src="../images/ngrelt.png" alt="Related tasks"></p>
-    <p>
-     <a href="../tasks/tasks-12.htm">Creating a new Java project</a><br>
-     <a href="../tasks/tasks-13.htm">Creating a Java project as its own source container</a><br>
-     <a href="../tasks/tasks-14.htm">Creating a Java project with source folders</a><br>
-     <a href="../tasks/tasks-26.htm">Creating a new source folder</a><br>
-     <a href="../tasks/tasks-11.htm">Creating Java elements</a><br>
-     <a href="../tasks/tasks-85.htm">Copying and moving Java elements</a><br>
-     <a href="../tasks/tasks-57.htm">Generating getters and setters</a><br>
-     <a href="../tasks/tasks-47.htm">Filtering elements</a><br>
-    </p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ></p>
-    <p>
-     <a href="../reference/ref-121.htm">New Java Project wizard</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concepts-4.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concepts-4.htm
deleted file mode 100644
index dbd98d1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concepts-4.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Java builder</title>
-  </head>
-
-  <body>
-    <h1>Java builder</h1>
-
-    <p>The Java builder builds Java programs using a compiler that implements the Java Language Specification.&nbsp;
-    The Java builder can build programs incrementally as individual Java files are saved.</p>
-
-    <p>Problems detected by the compiler are classified as either warnings or errors. The existence of a warning does not affect the execution of the program; the code executes as
-    if it were written correctly. Compile-time errors (as specified by the Java Language Specification) are always reported as errors by the Java compiler. For some other types of
-    problems you can, however, specify if you want the Java compiler to report them as warnings, errors or to ignore them. To change the default settings, use the <span class=
-    "control">Window &gt; Preferences &gt; Java &gt; Compiler &gt; Errors/Warnings</span> preference page.</p>
-
-    <p>The Java compiler can create CLASS files even in presence of compilation errors. However, in the case of serious errors (for example, references to inconsistent binaries,
-    most likely related to an invalid build path), the Java builder does not produce any CLASS
-    files.</p>
-
-    <p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ></p>
-    <p>
-     <a href="cbuildcp.htm">Build classpath</a><br>
-     <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a></p>
-
-    <p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-    <p>
-     <a href="../tasks/tasks-106.htm">Building a Java program</a><br>
-     <a href="../tasks/tasks-108.htm">Building automatically</a><br>
-     <a href="../tasks/tasks-109.htm">Building manually</a><br>
-     <a href="../tasks/tasks-107.htm">Viewing compilation errors and warnings</a><br>
-     <a href="../tasks/tasks-110.htm">Working with build paths</a>
-     <a href="../tasks/tasks-111.htm">Viewing and editing a project's build path</a><br>
-     <a href="../tasks/tasks-113.htm">Adding a JAR file to the build path</a><br>
-     <a href="../tasks/tasks-112.htm">Adding a class folder to the build path</a><br>
-	</p>
-	
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ></p>
-    <p>
-     <a href="../reference/ref-123.htm">Java Build Path properties</a><br>
-     <a href="../reference/ref-preferences-compiler.htm">Java Compiler preferences</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concepts-5.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concepts-5.htm
deleted file mode 100644
index d0a1f60..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concepts-5.htm
+++ /dev/null

@@ -1,100 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Java perspectives</title>
-  </head>
-
-  <body>
-    <h1>Java perspectives</h1>
-
-    The Java development tools contribute the following perspectives to the workbench:
-
-    <h2>Java</h2>
-
-    <p>A perspective designed for working with Java projects. It consists of an editor area and the following views:</p>
-
-    <ul>
-      <li><span>Package Explorer</span></li>
-
-      <li><span>Hierarchy</span></li>
-
-      <li><span>Outline</span></li>
-
-      <li><span>Search</span></li>
-
-      <li><span>Console</span></li>
-
-      <li><span>Tasks</span></li>
-    </ul>
-
-    <h2>Java Browsing</h2>
-
-    <p>A perspective designed for browsing the structure of Java projects. It consists of an editor area and the following views:</p>
-
-    <ul>
-      <li><span>Projects</span></li>
-
-      <li><span>Packages</span></li>
-
-      <li><span>Types</span></li>
-
-      <li><span>Members</span></li>
-    </ul>
-
-    <h2>Java Type Hierarchy</h2>
-
-    <p>A perspective designed for exploring a type hierarchy. It can be opened on types, compilation units, packages, projects or source folders and consists of the Hierarchy
-    view and an editor.</p>
-
-    <h2>Debug</h2>
-
-    <p>A perspective designed for debugging your Java program. It includes an editor area and the following views.</p>
-
-    <ul>
-      <li><span>Debug</span></li>
-
-      <li><span>Breakpoints</span></li>
-
-      <li><span>Expressions</span></li>
-
-      <li><span>Variables</span></li>
-
-      <li><span>Display</span></li>
-
-      <li><span>Outline</span></li>
-
-      <li><span>Console</span></li>
-    </ul>
-
-    <p><img  src="../images/ngrelc.png" alt="Related concepts" border="0"></p>
-    <p>
-     <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a><br>
-     <a href="../concepts/concepts-6.htm">Java views</a></p>
-
-    <p><img border="0"  src="../images/ngrelt.png" alt="Related tasks"></p>
-    <p>
-     <a href="../tasks/tasks-144.htm">Adding breakpoints</a><br>
-     <a href="../tasks/tasks-42.htm">Opening a type hierarchy in its own perspective</a><br>
-     <a href="../tasks/tasks-134.htm">Suspending threads</a></p>
-
-    <p><img border="0"  src="../images/ngrelr.png" alt="Related reference"></p>
-    <p>
-     <a href="../reference/ref-35.htm">Breakpoints view</a><br>
-     <a href="../reference/ref-45.htm">Console view</a><br>
-     <a href="../reference/ref-51.htm">Debug view</a><br>
-     <a href="../reference/ref-52.htm">Display view</a><br>
-     <a href="../reference/ref-56.htm">Expressions view</a><br>
-     <a href="../reference/ref-view-outline.htm">Java outline</a><br>
-     <a href="../reference/ref-view-package-explorer.htm">Package Explorer view</a><br>
-     <a href="../reference/ref-type-hierarchy.htm">Type Hierarchy view</a><br>
-     <a href="../reference/ref-74.htm">Variables view</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concepts-6.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concepts-6.htm
deleted file mode 100644
index 787d5e7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concepts-6.htm
+++ /dev/null

@@ -1,82 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Java views</title>
-  </head>
-
-  <body>
-    <h1>Java views</h1>
-
-    <p>The Java development tools contribute the following views to the workbench:</p>
-
-    <h2>Package Explorer view</h2>
-
-    <p>The Package Explorer view shows the Java element hierarchy of the Java projects in your workbench.
-    It provides you with a Java-specific view of the resources shown in the
-    Navigator. The element hierarchy is derived from the project's build class paths.
-    <br>For each project, its source folders and referenced libraries are shown in the tree.
-    You can open and browse the contents of both internal and external JAR files.</p>
-
-    <h2>Hierarchy view</h2>
-
-    <p>The Hierarchy view allows you to look at the complete hierarchy for a
-    type, only its subtypes, or only its supertypes.</p>
-
-    <h2>Projects view</h2>
-
-    <p>The Projects view shows Java projects, source folders, external and internal libraries.
-    <br>
-    Note: source folders and libraries (both internal and external) presented in this view are not expandable.
-    When they are selected, their contents are shown in the Packages view.</p>
-
-    <h2>Packages view</h2>
-
-    <p>The Packages view shows a list of Java packages from the currently selected Java projects, source folders or libraries.
-    Typically, the Projects view is used to make this selection.
-    </p>
-
-    <h2>Types view</h2>
-
-    <p>The Types view shows a list of Java types from the currently selected packages.
-    Typically, the Packages view is used to make this selection.
-    </p>
-
-    <h2>Members view</h2>
-
-    <p>The Members shows the content of a type, compilation unit or CLASS file.
-    Typically, the Types view is used to make this selection.
-    </p>
-
-    <p><img  src="../images/ngrelc.png" alt="Related concepts" border="0"></p>
-    <p>
-     <a href="../concepts/concepts-5.htm">Java perspectives</a></p>
-
-    <p><img border="0"  src="../images/ngrelt.png" alt="Related tasks"></p>
-    <p>
-     <a href="../tasks/tasks-consoleAppearance.htm">Changing the appearance of the Console view</a><br>
-     <a href="../tasks/tasks-38.htm">Changing the appearance of the Hierarchy view</a></p>
-
-    <p><img border="0"  src="../images/ngrelr.png" alt="Related reference"></p>
-    <p>
-     <a href="../reference/ref-35.htm">Breakpoints view</a><br>
-     <a href="../reference/ref-45.htm">Console view</a><br>
-     <a href="../reference/ref-51.htm">Debug view</a><br>
-     <a href="../reference/ref-52.htm">Display view</a><br>
-     <a href="../reference/ref-56.htm">Expressions view</a><br>
-     <a href="../reference/ref-view-outline.htm">Java outline</a><br>
-     <a href="../reference/ref-view-package-explorer.htm">Package Explorer view</a><br>
-     <a href="../reference/ref-type-hierarchy.htm">Type Hierarchy view</a><br>
-     <a href="../reference/ref-74.htm">Variables view</a><br>
-     <a href="../reference/ref-24.htm">Views and editors</a><br>
-    <br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concepts-7.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concepts-7.htm
deleted file mode 100644
index 387b061..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concepts-7.htm
+++ /dev/null

@@ -1,78 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Java editor</title>
-  </head>
-
-  <body>
-    <h1>Java editor</h1>
-
-    <p>The Java editor provides specialized features for editing Java code.</p>
-
-    <p>Associated with the editor is a Java-specific Outline view, which shows the structure of the active Java compilation unit.
-    It is updated as the user edits the compilation unit.</p>
-
-    <p>The Java editor can be opened on binary CLASS files.
-    If a JAR file containing the CLASS files has a source attachment,
-    then the editor shows the corresponding source.</p>
-
-    <p>The editor includes the following features:</p>
-
-    <ul>
-      <li>Syntax highlighting</li>
-
-      <li>Content/code assist</li>
-
-      <li>Code formatting</li>
-
-      <li>Import assistance</li>
-      
-      <li>Quick fix</li>
-
-      <li>Integrated debugging features</li>
-    </ul>
-
-    <p>The Java editor can be configured to either show an entire compilation unit or a single Java element only.
-    To change the setting, use the toolbar button <span class="control">Show Source of Selected Element Only</span>.
-    </p>
-
-    <p>The most common way to invoke the Java editor is to open a Java file from
-    the Navigator or Package explorer using pop-up menus or by clicking the file
-    (single or double-click depending on the user preferences). You can
-    also open the editor by opening Java elements, such as types, methods, or
-    fields, from other views.</p>
-
-    <p><img  src="../images/ngrelc.png" alt="Related concepts" border="0"></p>
-    <p>
-     <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a></p>
-
-    <p><img border="0"  src="../images/ngrelt.png" alt="Related tasks"></p>
-    <p>
-     <a href="../tasks/tasks-73.htm">Opening an editor for a selected element</a><br>
-     <a href="../tasks/tasks-54.htm">Using the Java editor</a><br>
-     <a href="../tasks/tasks-65.htm">Using content/code assist</a><br>
-     <a href="../tasks/tasks-66.htm">Formatting Java code</a><br>
-     <a href="../tasks/tasks-59.htm">Adding required import statements</a><br>
-     <a href="../tasks/tasks-57.htm">Generating getters and setters</a><br>
-     <a href="../tasks/tasks-107.htm">Viewing compilation errors and warnings</a><br>
-     <a href="../tasks/tasks-156.htm">Viewing runtime exceptions</a><br>
-     <a href="../tasks/tasks-138.htm">Evaluating expressions</a><br>
-    </p>
-
-    <p><img border="0"  src="../images/ngrelr.png" alt="Related reference"></p>
-    <p>
-     <a href="../reference/ref-java-editor.htm">Java editor actions</a><br>
-     <a href="../reference/ref-21.htm">Java editor preferences</a><br>
-     <a href="../reference/ref-view-outline.htm">Java outline</a><br>
-     <a href="../reference/ref-24.htm">Views and editors</a>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concepts-8.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concepts-8.htm
deleted file mode 100644
index 080a3c8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concepts-8.htm
+++ /dev/null

@@ -1,126 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Java search</title>
-  </head>
-
-  <body>
-    <h1>Java search</h1>
-
-    <p><span>The Java searching support allows you to find declarations, references and occurrences of Java elements
-    (packages, types, methods, fields). Searching is supported by an index that
-    is kept up to date in the background as the resources corresponding to Java elements are changed.
-    The Java search operates on workspaces independent of their build state. For
-    example, searches can be conducted when auto-build is turned off.</span></p>
-
-    <p>The following searches can be initiated from the pop-up menus of Java elements:</p>
-
-    <table border="1" cellspacing="0" cellpadding="5" summary="Java search actions">
-      <thead>
-        <tr>
-          <td>
-            <p><span class="control">Command</span></p>
-          </td>
-
-          <td>
-            <p><span class="control">Description</span></p>
-          </td>
-        </tr>
-      </thead>
-
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>References</p>
-          </td>
-
-          <td valign="top">
-            <p>Finds all references to the selected Java element</p>
-          </td>
-        </tr>
-
-        <tr>
-          <td valign="top">
-            <p>Declarations</p>
-          </td>
-
-          <td valign="top">
-            <p>Finds all declarations of the selected Java element</p>
-          </td>
-        </tr>
-
-        <tr>
-          <td valign="top">
-            <p>Implementors</p>
-          </td>
-
-          <td valign="top">
-            <p>Finds all implementors of the selected Java interface</p>
-          </td>
-        </tr>
-
-        <tr>
-          <td valign="top">
-            <p>Read Access</p>
-          </td>
-
-          <td valign="top">
-            <p>Finds all read accesses to the selected Java field</p>
-          </td>
-        </tr>
-
-        <tr>
-          <td valign="top">
-            <p>Write Access</p>
-          </td>
-
-          <td valign="top">
-            <p>Finds all write accesses to the selected Java field</p>
-          </td>
-        </tr>
-
-        <tr>
-          <td valign="top">
-            <p>Occurrences in File</p>
-          </td>
-
-          <td valign="top">
-            <p>Finds all occurrences of the selected Java element in its file</p>
-          </td>
-        </tr>
-
-      </tbody>
-    </table>
-
-    <p>The scope of the search is defined as:</p>
-
-    <p><span class="control">Workspace</span> - all projects and files in the workspace are included in this search</p>
-
-    <p><span class="control">Enclosing Projects</span> - the projects enclosing the currently selected elements</p>
-
-    <p><span class="control">Hierarchy</span> - only the type hierarchy of the selected element is included in this search</p>
-
-    <p><span class="control">Working Set</span> - only resources that belong to the chosen working set are included in this search</p>
-
-    <p><img  src="../images/ngrelc.png" alt="Related concepts" border="0"></p>
-    <p>
-     <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a></p>
-
-    <p><img border="0"  src="../images/ngrelt.png" alt="Related tasks"></p>
-    <p>
-     <a href="../tasks/tasks-79.htm">Searching Java code</a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ></p>
-    <p>
-     <a href="../reference/ref-menu-search.htm">Search actions</a><br>
-     <a href="../reference/ref-131.htm">Java Search tab</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concepts-9.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concepts-9.htm
deleted file mode 100644
index e021453..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concepts-9.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Refactoring support</title>
-  </head>
-
-  <body>
-    <h1>Refactoring support</h1>
-
-    <p>The goal of Java program refactoring is to make system-wide code changes without affecting the behavior of the
-    program. The Java tools provide assistance in easily refactoring code.
-    </p>
-
-    <p>The refactoring tools support a number of transformations described in Martin Fowler's
-    book <span class="name">Refactoring: Improving the Design of Existing Code</span>, Addison Wesley
-    1999, such as <span class="name">Extract Method</span>, <span class="name">Inline Local
-    Variable, etc.</span></p>
-
-    <p>When performing a refactoring operation, you can optionally preview all
-    of the changes resulting from a refactoring action before you choose to carry them out.
-    When previewing a refactoring operation, you will be notified of potential
-    problems and will be presented with a list of the changes the
-    refactoring action will perform. If you do not preview a refactoring
-    operation, the change will be made in its entirety and any resultant
-    problems will be shown. If a problem is detected that does not allow
-    the refactoring to continue, the operation will be halted and a list of
-    problems will be displayed.</p>
-
-    <p>Refactoring commands are available from the context menus of several Java views (e.g. Package Explorer, Outline) and editors.
-    Many &quot;apparently simple&quot; commands, such as <strong>Move</strong> and <strong>Rename</strong>, are
-    actually refactoring operations, since moving and renaming Java elements
-    often require changes in dependent files.
-    </p>
-
-    <p><img  src="../images/ngrelc.png" alt="Related concepts" border="0"></p>
-    <p>
-     <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a></p>
-
-    <p><img border="0"  src="../images/ngrelt.png" alt="Related tasks"></p>
-    <p>
-     <a href="../tasks/tasks-80.htm">Refactoring</a><br>
-     <a href="../tasks/tasks-82.htm">Refactoring without preview</a><br>
-     <a href="../tasks/tasks-83.htm">Refactoring with preview</a><br>
-     <a href="../tasks/tasks-84.htm">Previewing refactoring changes</a><br>
-     <a href="../tasks/tasks-100.htm">Undoing a refactoring operation</a><br>
-     <a href="../tasks/tasks-101.htm">Redoing a refactoring operation</a><br>
-    </p>
-
-    <p><img border="0"  src="../images/ngrelr.png" alt="Related reference"></p>
-    <p>
-     <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-     <a href="../reference/ref-117.htm">Refactoring wizard</a><br>
-     <a href="../reference/ref-13.htm">Java preferences</a><br>
-     <a href="../reference/ref-154.htm">Extract Method Errors</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/cquickassists.htm b/bundles/org.eclipse.jdt.doc.user/concepts/cquickassists.htm
deleted file mode 100644
index e5db348..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/cquickassists.htm
+++ /dev/null

@@ -1,337 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="content-type">
-  <link rel="stylesheet" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>List of Quick Assists</title>
-</head>
-<body>
-<h1>List of Quick Assists</h1>
-
-<p>Quick assists  perform local code transformations. They are invoked on a selection or a single cursor in the Java editor and use the same shortcut is used as for quick fixes (Ctrl +1), but quick assist are usually hidden when an error is around.<br>
-<br>
-A selection of quick assist can be assigned to a direct shortcut. By default these are:</p><ul>
-	<li>Rename in file: Ctrl + 2 + R</li>
-	<li>Assign to local: Ctrl + 2 + L</li>
-	<li>Assign to field: Ctrl + 2 + F</li>
-</ul>
-<p>Assign more shortcuts or change the  default shortcuts on the keys preference page.
-<br>
-<br>
-A quick assist light bulb can be turned on on the Java Editor preference page.<br>
-</p>
-<table style="width: 100%; text-align: left;" border="1" cellpadding="5">
-  <tbody>
-    <tr>
-      <th style="vertical-align: top;" width="15%">Name</th>
-      <th colspan="3" rowspan="1"
- style="vertical-align: top; text-align: center;">Code example</th>
-      <th style="vertical-align: top;" width="15%">Invocation location</th>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Inverse if statement</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>if (x) a(); else b();</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>if (!x) b(); else a();</code></td>
-      <td style="vertical-align: top;" width="15%">on 'if' statements with 'else'
-block</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Inverse boolean expression</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>a &amp;&amp;
-!b </code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>!a || b</code></td>
-      <td style="vertical-align: top;" width="15%">on a boolean expression</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Remove extra parentheses</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>if ((a == b)
-&amp;&amp; (c != d)&nbsp; {}</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>if (a == b &amp;&amp; c !=
-d)&nbsp; {}</code></td>
-      <td style="vertical-align: top;" width="15%">on selected expressions</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Add paranoidal parentheses</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>if (a == b
-&amp;&amp; c != d)&nbsp; {}</code> </td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>if ((a == b) &amp;&amp; (c != d)</code></td>
-      <td style="vertical-align: top;" width="15%">on selected expressions</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Join nested if statements</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>if (a) { if
-(b) {} }</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>if (a &amp;&amp; b) {}</code></td>
-      <td style="vertical-align: top;" width="15%">on a nested if statement</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Swap nested if statements</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>if (a) { if
-(b) {} }</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>if (b) { if (a) {} }</code></td>
-      <td style="vertical-align: top;" width="15%">on a nested if statement</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Split if statement with and'ed
-expression</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>if (a
-&amp;&amp; b) {}</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>if (a) { if (b) {} }</code></td>
-      <td style="vertical-align: top;" width="15%">on an and'ed expression in a 'if'</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Split if statement with or'd
-expression</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>if (a || b)
-x();</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code> if (a) x();&nbsp; if (b) x();</code></td>
-      <td style="vertical-align: top;" width="15%">on an or'd expression in a 'if'</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Inverse conditional expression</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>x ? b : c</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>!x ? c : b</code></td>
-      <td style="vertical-align: top;" width="15%">on a conditional expression</td>
-    </tr>
-		<tr>
-			<td style="vertical-align: top" width="15%">Pull negation up</td>
-			<td style="vertical-align: top; text-align: right" width="34%"><code>b &amp;&amp; c</code></td>
-			<td style="vertical-align: top">&gt;</td>
-			<td style="vertical-align: top" width="34%"><code>!(!b || !c)</code></td>
-			<td style="vertical-align: top" width="15%">On a boolean expression</td>
-		</tr>
-		<tr>
-			<td style="vertical-align: top" width="15%">Push negation down</td>
-			<td style="vertical-align: top; text-align: right" width="34%">!(<code>b
-			&amp;&amp; c)</code></td>
-			<td style="vertical-align: top">&gt;</td>
-			<td style="vertical-align: top" width="34%">!<code>b || !c</code></td>
-			<td style="vertical-align: top" width="15%">On a negated boolean expression</td>
-		</tr>
-		<tr>
-      <td style="vertical-align: top;" width="15%">If-else assignment to
-conditional expression</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>if (a) x= 1;
-else x= 2;</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>x= a ? 1 : 2;</code></td>
-      <td style="vertical-align: top;" width="15%">on an 'if' statement</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">If-else return to conditional
-expression</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>if (a) return
-1; <br>
-			else return 2;</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>return a ? 1 : 2;</code></td>
-      <td style="vertical-align: top;" width="15%">on an 'if' statement</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Conditional expression
-assignment to If-else</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>x= a ? 1 : 2;</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code> if (a) x= 1; else x= 2;</code></td>
-      <td style="vertical-align: top;" width="15%">on a conditional expression</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Conditional expression return to
-If-else</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>return&nbsp;
-a ? 1 : 2;</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>if (a) return 1; else return 2;</code></td>
-      <td style="vertical-align: top;" width="15%">on a conditional expression</td>
-    </tr>
-		<tr>
-			<td style="vertical-align: top" width="15%">Switch to If-else</td>
-			<td style="vertical-align: top; text-align: right" width="34%"><code>switch (kind) {<br>case 1: return -1;<br>case 2: return -2;<br>}</code>
-			</td>
-			<td style="vertical-align: top">&gt;</td>
-			<td style="vertical-align: top" width="34%"><code>if (kind == 1) {<br>&nbsp;&nbsp;return  
-			-1;<br>} else if (kind == 2) {<br>&nbsp;&nbsp;return -2;<br>}</code>
-			</td>
-			<td style="vertical-align: top" width="15%">on a switch statement</td>
-		</tr>
-		<tr>
-      <td style="vertical-align: top;" width="15%">Exchange operands</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>a + b</code>
-      </td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>b + a</code></td>
-      <td style="vertical-align: top;" width="15%">on an infix operation</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Cast and assign</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>if (obj
-instanceof Vector) {<br>
-			}</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code> if (obj instanceof Vector) {<br>
-&nbsp;Vector vec= (Vector)obj;</code><br>
-}</td>
-      <td style="vertical-align: top;" width="15%">on a instanceof expression in an 'if' or 'while' statement</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Pick out string</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>"abcdefgh"</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>"abc" + "de" + "fgh"</code></td>
-      <td style="vertical-align: top;" width="15%">select a part of a string literal</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Split variable</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>int i= 0;</code>
-      </td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code> int i; i= 0;</code></td>
-      <td style="vertical-align: top;" width="15%">On a variable with initialization</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Join variable</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>int i; i= 0;</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code> int i= 0</code></td>
-      <td style="vertical-align: top;" width="15%">On a variable without
-initialization</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Assign to variable</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>foo()</code>
-      </td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>X x= foo();</code></td>
-      <td style="vertical-align: top;" width="15%">On an expression statement</td>
-    </tr>
-		<tr>
-			<td style="vertical-align: top" width="15%">Extract to local</td>
-			<td style="vertical-align: top; text-align: right" width="34%"><code>foo(<u>getColor()</u>);</code></td>
-			<td style="vertical-align: top">&gt;</td>
-			<td style="vertical-align: top" width="34%"><code>Color color= getColor();<br>foo(color);</code>
-			</td>
-			<td style="vertical-align: top" width="15%">On an expression</td>
-		</tr>
-		<tr>
-      <td style="vertical-align: top;" width="15%">Assign parameter to field</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>public A(int
-color) {}</code>
-      </td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>Color fColor;<br>
-public A(int color) {<br>
-&nbsp;&nbsp;&nbsp; fColor= color;<br>
-}</code></td>
-      <td style="vertical-align: top;" width="15%">On a parameter</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Add finally block</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>try {<br>
-} catch (Expression e) {<br>
-}<br>
-      </code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>try {<br>
-} catch (Expression e) {<br>
-} finally {}</code></td>
-      <td style="vertical-align: top;" width="15%">On a try/catch statement</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Add else block</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>if (a) b();</code>
-      </td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>if (a) b(); else { }</code></td>
-      <td style="vertical-align: top;" width="15%">On a if statement</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Replace statement with block</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>f (a) b();</code>
-      </td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code> if (a) { b(); }</code></td>
-      <td style="vertical-align: top;" width="15%">On a if statement </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Invert equals</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>a.equals(b)</code>
-      </td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>b.equals(a)</code></td>
-      <td style="vertical-align: top;" width="15%">On a invocation of 'equals'</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Array initializer to Array
-creation</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>int[]
-i=&nbsp; { 1, 2, 3 }</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>int[] i= new int[] { 1, 2, 3 }</code></td>
-      <td style="vertical-align: top;" width="15%">On an array initializer</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Convert to 'enhanced for loop'
-(J2SE 5.0)</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>for (Iterator
-i= c.iterator();i.hasNext();) {<br>
-}<br>
-      </code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>for (x : c) {<br>
-}</code></td>
-      <td style="vertical-align: top;" width="15%">On a for loop</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Create method in super class</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code></code>
-      <br>
-			</td>
-      <td style="vertical-align: top;"><br>
-      </td>
-      <td style="vertical-align: top;" width="34%"><code></code><br>
-			</td>
-      <td style="vertical-align: top;" width="15%">On a method declaration</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Unwrap blocks</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>{ a() }</code>
-      </td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>a()</code></td>
-      <td style="vertical-align: top;" width="15%">On blocks, if/while/for
-statements</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Rename in file</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><br>
-			<code></code>
-      </td>
-      <td style="vertical-align: top;"><br>
-      </td>
-      <td style="vertical-align: top;" width="34%"><code></code><br>
-      </td>
-      <td style="vertical-align: top;" width="15%">On identifiers</td>
-    </tr>
-  </tbody>
-</table>
-
-<p><img src="../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p><a href="concepts-7.htm">Java editor</a><br>
-<a href="cquickfix.htm">Quick Fix</a></p>
-
-<p><img src="../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="../reference/ref-2.htm">JDT actions</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/cquickfix.htm b/bundles/org.eclipse.jdt.doc.user/concepts/cquickfix.htm
deleted file mode 100644
index 010467e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/cquickfix.htm
+++ /dev/null

@@ -1,159 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Quick Fix</title>
-  </head>
-
-  <body>
-    <h1>Quick Fix</h1>
-
-    <p>The Java editor offers corrections to problems found while typing and after compiling. To show that
-    correction proposals are available for a problem or warning, a 'light bulb' is visible on the editor's annotation bar.<br><br>
-Left click on the light bulb or invoking <b>Ctrl+1 (Edit &gt; Quick Fix)</b> brings up the proposals for the problem at the cursor position.<br>
-Each quick fix show a preview when selected in the proposal window.<br>
-<br>
-Some selected quick fixes can also be assigned with direct shortcuts. You can configure these shortcuts on the keys preference page. <br></p>
-<p><img src="../images/c-quickfix.png"  border="0" alt="Quick fix selection dialog"></p>
-
-<p>The following quick fixes are available:</p>
-<table border="0" cellpadding="10" cellspacing="0" width="700">
-	<tbody>
-		<tr>
-			<td width="20%" valign="top" align="right"><b>Package Declaration</b></td>
-			<td width="80%" valign="top" align="left">
-			<ul>
-				<li>Add missing package declaration or correct package declaration</li>
-				<li>Move compilation unit to package that corresponds to the package declaration</li>
-			</ul>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="right"><b>Imports</b></td>
-			<td valign="top" align="left">
-			<ul>
-				<li>Remove unused, unresolvable or non-visible import</li>
-				<li>Invoke 'Organize imports' on problems in imports</li>
-			</ul>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="right"><b>Types</b></td>
-			<td valign="top" align="left">
-			<ul>
-				<li>Create new class, interface, enum, annotation or type variable for references to types that can not be resolved</li>
-				<li>Change visibility for types that are accessed but not visible</li>
-				<li>Rename to a similar type for references to types that can not be resolved</li>
-				<li>Add import statement for types that can not be resolved but	exist in the project</li>
-				<li>Add explicit import statement for ambiguous type references (two import-on-demands for the same type)</li>
-				<li>If the type name is not matching with the compilation unit name either rename the type or rename the compilation unit</li>
-				<li>Remove unused private types</li>
-			</ul>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="right"><b>Constructors</b></td>
-			<td valign="top" align="left">
-			<ul>
-				<li>Create new constructor for references to constructors that can not be resolved (this, super or new class creation)</li>
-				<li>Reorder, add or remove arguments for constructor references that mismatch parameters</li>
-				<li>Change method with constructor name to constructor (remove return type)</li>
-				<li>Change visibility for constructors that are accessed but not visible</li>
-				<li>Remove unused private constructor</li>
-				<li>Create constructor when super call of the implicit default constructor is undefined, not visible or throws an exception</li>
-				<li>If type contains unimplemented methods, change type modifier to 'abstract' or add the method to implement</li>
-			</ul>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="right"><b>Methods</b></td>
-			<td valign="top" align="left">
-			<ul>
-				<li>Create new method for references to methods that can not be resolved</li>
-				<li>Rename to a similar method for references to methods that can not be resolved</li>
-				<li>Reorder or remove arguments for method references that mismatch parameters</li>
-				<li>Correct access (visibility, static) of referenced methods</li>
-				<li>Remove unused private methods</li>
-				<li>Correct return type for methods that have a missing return type or where the return type does not match the return statement</li>
-				<li>Add return statement if missing</li>
-				<li>For non-abstract methods with no body change to 'abstract' or add body</li>
-				<li>For an abstract method in a non-abstract type remove abstract modifier of the method or make type abstract</li>
-				<li>For an abstract/native method with body remove the abstract or native modifier or remove body</li>
-				<li>Change method access to 'static' if method is invoked inside a constructor invocation (super, this)</li>
-				<li>Change method access to default access to avoid emulated method access</li>
-			</ul>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="right"><b>Fields and variables</b></td>
-			<td valign="top" align="left">
-			<ul>
-				<li>Correct access (visibility, static) of referenced fields</li>
-				<li>Create new  fields, parameters,  local variables or constants for references to  variables that can not be resolved</li>
-				<li>Rename to a  variable with similar name for references that can not be resolved</li>
-				<li>Remove unused private fields</li>
-				<li>Correct non-static access of static fields</li>
-				<li>Add 'final' modifier to  local variables accessed in outer types</li>
-				<li>Change field access to default access to avoid emulated method access</li>
-				<li>Change local variable type to fix a type mismatch</li>
-				<li>Initialize a variable that has not been initialized</li>
-			</ul>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="right"><b>Exception Handling</b></td>
-			<td valign="top" align="left">
-			<ul>
-				<li>Remove unneeded catch block</li>
-				<li>Handle uncaught exception by surrounding with try/catch or adding catch block to a surrounding try block</li>
-				<li>Handle uncaught exception by adding a throw declaration to the parent method or by generalize an existing throw declaration</li>
-			</ul>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="right"><b>Build Path Problems</b></td>
-			<td valign="top" align="left">
-			<ul>
-				<li>Add a missing JAR or library for an unresolvable type</li>
-				<li>Open the build path dialog for access restriction problems or missing binary classes.</li>
-				<li>Change project compliance and JRE to 5.0</li>
-				<li>Change workspace compliance and JRE to 5.0</li>
-			</ul>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="right"><b>Others</b></td>
-			<td valign="top" align="left">
-			<ul>
-				<li>Add cast or change cast to fix type mismatches</li>
-				<li>Let a type implement an interface to fix type mismatches</li>
-				<li>For non-NLS strings open the NLS wizard or mark as non-NLS</li>
-				<li>Add missing @Override, @Deprecated annotations</li>
-				<li>Suppress a warning using @SuppressWarning</li>
-			</ul>
-			</td>
-		</tr>
-	</tbody>
-</table>
-
-
-
-<p>Quick Assists are proposals available even if there is no problem or warning. See the <a href='cquickassists.htm'>Quick Assist</a> page for more information.</p>
-<p>
-	<img src="../images/ngrelc.png"  alt="Related concepts" border="0"></p>
-	<p>
-	<a href="../concepts/concepts-7.htm">Java editor</a><br>
-<a href="cquickassists.htm">Quick Assist</a></p>
-	
-	<p><img src="../images/ngrelr.png"  alt="Related reference" border="0"></p>
-	<p>
-    <a href="../reference/ref-2.htm">JDT actions</a>
-</p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/cremdbug.htm b/bundles/org.eclipse.jdt.doc.user/concepts/cremdbug.htm
deleted file mode 100644
index c9cb0f7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/cremdbug.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Remote debugging</title>
-  </head>
-
-  <body>
-    <h1>Remote debugging</h1>
-
-    <p>The client/server design of the Java debugger allows you to launch a Java
-    program from computer on your network and debug it from the workstation
-    running the platform.&nbsp; This is particularly useful when you are
-    developing a program for a device that cannot host the development
-    platform.&nbsp; It is also useful when debugging programs on dedicated
-    machines such as web servers.&nbsp; </p>
-
-    <p>Note:&nbsp; To use remote debugging, you must be using a Java VM that
-    supports this feature.</p>
-
-    <p>To debug a program remotely, you must be able to launch the program in
-    debug mode on the remote machine so that it will wait for a connection from
-    your debugger.&nbsp; The specific technique for launching the program and
-    connecting the debugger are VM-specific.&nbsp; The basic steps are as
-    follows:</p>
-
-    <ol>
-      <li>Ensure that you are building your Java program with available debug
-        information.&nbsp; (You can control these attributes from <strong>Window
-        &gt; Preferences &gt; Java &gt; Compiler</strong>).&nbsp; </li>
-      <li>After you build your Java program, install it to the target
-        computer.&nbsp; This involves copying the .CLASS files or .JAR files to
-        the appropriate location on the remote computer.</li>
-      <li>Invoke the Java program on the remote computer using the appropriate
-        VM arguments to specify debug mode and a communication port for the
-        debugger.</li>
-      <li>Start the debugger using a remote launch configuration and specify the
-        address and port of the remote computer.</li>
-    </ol>
-    <p>More specific instructions for setting up a launch configuration for
-    remote debugging should be obtained from your VM provider.&nbsp; </p>
-    <p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-    <p>
-    <a href="../tasks/tasks-141.htm">Using the remote Java application launch configuration</a><br>
-    <a href="../tasks/tasks-142.htm">Disconnecting from a VM</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/ctemplates.htm b/bundles/org.eclipse.jdt.doc.user/concepts/ctemplates.htm
deleted file mode 100644
index 1cf9b4f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/ctemplates.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Templates</title>
-  </head>
-
-  <body>
-    <h1>Templates</h1>
-
-    <p>Templates are a structured description of coding patterns that reoccur in
-    source code. The Java editor supports the use of templates to fill in
-    commonly used source patterns. Templates are inserted using content
-    assist (<strong>Ctrl+Space</strong>).</p>
-
-    <p>For example, a common coding pattern is to iterate over the elements of
-    an array using a for loop that indexes into the array. By using a
-    template for this pattern, you can avoid typing in the complete code for the
-    loop. Invoking content assist after typing the word <code>for</code> will present
-    you with a list of possible templates for a for loop.  You can choose the appropriate
-    template by name (<code>iterate over array</code>). Selecting this template will
-    insert the code into the editor and position your cursor so that you can
-    edit the details.</p>
-
-    <p>Many common templates are already defined. These can be browsed in
-    <strong>Window &gt; Preferences &gt; Java &gt; Editor &gt; Templates</strong>.
-    You can also create your own templates or edit the existing ones.</p>
-
-    <p><img border="0"  src="../images/ngrelt.png" alt="Related tasks"></p>
-    <p>
-     <a href="../tasks/tasks-171.htm">Using templates</a><br>
-     <a href="../tasks/tasks-203.htm">Writing your own templates</a>
-    </p>
-
-    <p><img border="0" src="../images/ngrelr.png" alt="Related reference" ></p>
-    <p>
-     <a href="../reference/ref-menu-edit.htm">Edit menu</a><br>
-     <a href="../reference/ref-143.htm">Java Content Assist</a><br>
-     <a href="../reference/ref-preferences-templates.htm">Templates preferences</a><br>
-    </p>
-
-    <p><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/filters.htm b/bundles/org.eclipse.jdt.doc.user/concepts/filters.htm
deleted file mode 100644
index a481165..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/filters.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Exclusion and inclusion filters</title>
-  </head>
-
-  <body>
-    <h1>Exclusion and inclusion filters</h1>
-
-    <p>Exclusion and inclusion filters are Ant file patterns that further define 
-    the set of source files to be considered by the Java builder and 
-    other JDT tools. To allow nesting of source folders inside each other, 
-    or simply to exclude parts of a source tree, one can associate exclusion 
-    filters to a source folder. Symmetrically inclusion filters can be used to inlude
-    another part of a source tree. The Java builder will ignore source files
-    that are excluded, and the ones that are not included.
-    </p>
-
-    <p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ></p>
-    <p>
-     <a href="concepts-4.htm">Java builder</a><br>
-     <a href="rules.htm">Access rules</a><br>
-    </p>
-
-    <p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-    <p>
-     <a href="../tasks/tasks-106.htm">Building a Java program</a><br>
-     <a href="../tasks/tasks-111.htm">Viewing and editing a project's build path</a><br>
-     <a href="../tasks/tasks-110.htm">Working with build paths</a><br>
-	 <a href="../tasks/tasks-221.htm">Creating a new source folder with exclusion filter</a><br>
-    </p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-     <a href="../reference/ref-123.htm">Java Build Path properties</a><br>
-    </p>
-
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/rules.htm b/bundles/org.eclipse.jdt.doc.user/concepts/rules.htm
deleted file mode 100644
index 0d27e54..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/rules.htm
+++ /dev/null

@@ -1,48 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Access rules</title>
-  </head>
-
-  <body>
-    <h1>Access rules</h1>
-
-    <p>Access rules are Ant patterns defined on build classpath entries 
-    that tells the compiler to signal the use of types matching the patterns.
-    <ul>
-    <li>Non-accessible rules define types that must not be referenced.</li>
-    <li>Discouraged rules define types that should not be referenced.</li>
-    <li>Accessible rules define types that can be referenced.</li>
-    </ul>
-    </p>
-
-    <p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ></p>
-    <p>
-     <a href="concepts-4.htm">Java builder</a><br>
-     <a href="filters.htm">Exclusion and inclusion filters</a>
-    </p>
-
-    <p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-    <p>
-     <a href="../tasks/tasks-113.htm">Adding a JAR file to the build path</a><br>
-     <a href="../tasks/tasks-112.htm">Adding a class folder to the build path</a><br>
-     <a href="../tasks/tasks-106.htm">Building a Java program</a><br>
-     <a href="../tasks/tasks-111.htm">Viewing and editing a project's build path</a><br>
-     <a href="../tasks/tasks-110.htm">Working with build paths</a><br>
-    </p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-     <a href="../reference/ref-123.htm">Java Build Path properties</a><br>
-    </p>
-
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/contexts_APT.xml b/bundles/org.eclipse.jdt.doc.user/contexts_APT.xml
deleted file mode 100644
index ff3ddec..0000000
--- a/bundles/org.eclipse.jdt.doc.user/contexts_APT.xml
+++ /dev/null

@@ -1,28 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-
-    <!-- Dialogs -->
-
-    <context id="advanced_factory_path_options_dialog_context">
-    	<description>A dialog for configuring factory path options that do not normally need to be changed.</description>
-    	<topic label="Advanced factory path options dialog" href="reference/ref-apt-factoryPathOptions.htm"/>
-    </context>
-    <context id="processor_option_input_dialog_context">
-    	<description>A dialog for adding or editing an annotation processor option.</description>
-    	<topic label="Processor option input dialog" href="reference/ref-apt-processorOptionsInput.htm"/>
-    </context>
-    
-    <!-- Preference pages -->
-
-    <context id="apt_configuration_preference_page_context">
-        <description>Configure general Java annotation processing settings.</description>
-        <topic label="Java annotation processing preferences" href="reference/ref-apt-config.htm"/>
-    </context>
-    <context id="factory_path_preference_page_context">
-        <description>Configure the factory path for Java annotation processing.</description>
-        <topic label="Java annotation processing factory path preferences" href="reference/ref-apt-factoryPath.htm"/>
-    </context>
-    
-</contexts>
-    

diff --git a/bundles/org.eclipse.jdt.doc.user/contexts_Debugger.xml b/bundles/org.eclipse.jdt.doc.user/contexts_Debugger.xml
deleted file mode 100644
index 43adbd4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/contexts_Debugger.xml
+++ /dev/null

@@ -1,664 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-
-<!-- Actions -->
-   <context  id="debug_action_context" >
-      <description>This command allows you to run the selected executable under debugger control.</description>
-      <topic label="Run/Debug Actions" href="reference/ref-4.htm"/> 
-      <topic label="Debugger Concepts" href="concepts/concepts-10.htm"/>
-      <topic label="Debugging Locally" href="concepts/clocdbug.htm"/>
-      <topic label="Remote debugging" href="concepts/cremdbug.htm"/>
-    </context>
-
-  <context id="variable_selection_dialog_context">
-    <description>This dialog allows you to select variables to be used as launch configuration parameters. Variables are evaluated each time you launch your configuration, which can give your configuration dynamic behavior. Variables specifying 'Selected Resource...' are evaluated to the resource currently selected in the navigator or packages view, etc. at the time the configuration is launched.</description>
-  </context>
-    
-   <context  id="debug_last_action_context" >
-      <description>This command re-launches the most recently launched application in debug mode.</description>
-    </context>    
-    
-   <context  id="open_debug_configurations_action_context" >
-      <description>This command opens the launch configuration dialog in debug mode.</description>
-    </context>    
-
-   <context  id="run_action_context" >
-      <description>This command allows you to run the selected executable.</description>
-      <topic label="Running a Java Program" href="tasks/tasks-130.htm"/>
-      <topic label="Run/Debug Actions" href="reference/ref-4.htm" /> 
-    </context>
-    
-   <context  id="run_last_action_context" >
-      <description>This command re-launches the most recently launched application in run mode.</description>
-    </context>    
-    
-   <context  id="open_run_configurations_action_context" >
-      <description>This command opens the launch configuration dialog in run mode.</description>
-    </context>    
-    
-   <context  id="profile_action_context" >
-      <description>This command allows you to profile the selected executable.</description>
-    </context>        
-
-   <context  id="profile_last_action_context" >
-      <description>This command re-launches the most recently launched application in profile mode.</description>
-    </context>    
-    
-   <context  id="open_profile_configurations_action_context" >
-      <description>This command opens the launch configuration dialog in profile mode.</description>
-    </context>     
-    
-   <context  id="inspect_action_context" >
-      <description>This command allows you to inspect the result of evaluating the selected expression.</description>
-      <topic label="Inspecting in the Display View" href="reference/ref-55.htm" /> 
-      <topic label="Display View" href="reference/ref-52.htm" />
-      <topic label="Inspecting in the Expressions View" href="reference/ref-64.htm" /> 
-      <topic label="Expressions View" href="reference/ref-56.htm"/>
-      <topic label="Inspecting in the Variables View" href="reference/ref-80.htm" /> 
-      <topic label="Variables View" href="reference/ref-74.htm"/>
-      <topic label="Debugging Locally" href="concepts/clocdbug.htm"/>
-    </context>
-
-   <context  id="change_value_action_context" >
-      <description>This command allows you to change the value of the selected variable.</description>
-      <topic label="Change Variable Values in the Expressions View" href="reference/ref-65.htm" /> 
-      <topic label="Expressions View" href="reference/ref-56.htm"/>
-      <topic label="Change Variable Values in the Variables View" href="reference/ref-81.htm" /> 
-      <topic label="Variables View" href="reference/ref-74.htm"/>
-    </context>
-
-   <context  id="clear_console_action_context" >
-      <description>This command clears the console.</description>
-      <topic label="Clear" href="reference/ref-46.htm"/>
-      <topic label="Console View" href="reference/ref-45.htm"/>
-     </context>
-
-   <context  id="copy_to_clipboard_action_context" >
-      <description>This command copies the selection to the OS clipboard.</description>
-      <topic label="Copy" href="reference/ref-47.htm" />
-      <topic label="Console View" href="reference/ref-45.htm"/> 
-   </context>
-
-   <context  id="disconnect_action_context" >
-      <description>This command disconnects the debugger from the selected debug target.</description>
-      <topic label="Disconnect" href="reference/ref-68.htm" />
-      <topic label="Debug View" href="reference/ref-51.htm" />
-     </context>
-	
-	<context  id="enable_disable_breakpoint_action_context" >
-      <description>This command toggles the breakpoint in the editor ruler.</description>
-      <topic label="Debugger" href="concepts/concepts-10.htm" />
-   </context>
-
-   <context  id="enable_breakpoint_action_context" >
-      <description>This command enables the selected breakpoints.</description>
-      <topic label="Enable" href="reference/ref-44.htm" />
-      <topic label="Breakpoints View" href="reference/ref-35.htm"/>
-      <topic label="Line Breakpoints" href="tasks/tasks-144.htm" />
-      <topic label="Debugger" href="concepts/concepts-10.htm" />
-   </context>
-   
-   <context  id="disable_breakpoint_action_context" >
-      <description>This command disables the selected breakpoints.</description>
-      <topic label="Disable" href="reference/ref-44a.htm" />
-      <topic label="Breakpoints View" href="reference/ref-35.htm"/>
-      <topic label="Line Breakpoints" href="tasks/tasks-144.htm" />
-      <topic label="Debugger" href="concepts/concepts-10.htm" />
-   </context>
-
-   <context  id="open_breakpoint_action_context" >
-      <description>This command opens an editor for the file containing the selected breakpoint.</description>
-      <topic label="Go to File for Breakpoint" href="reference/ref-38.htm" />
-      <topic label="Breakpoints View" href="reference/ref-35.htm"/>
-   </context>
-
-   <context  id="relaunch_action_context" >
-      <description>This command relaunches the selected debug target or process.</description>
-      <topic label="Relaunch" href="reference/ref-72.htm" />
-      <topic label="Debug View" href="reference/ref-51.htm" />
-   </context>
-
-   <context  id="relaunch_history_action_context" >
-      <description>This command allows you to select a previous launch from the launch history.</description>
-      <topic label="Relaunching a Previously-launched Program" href="tasks/tasks-131.htm" />
-      <topic label="Relaunch" href="reference/ref-72.htm" />
-      <topic label="Debug View" href="reference/ref-51.htm" />
-   </context>
-
-   <context  id="remove_action_context" >
-      <description>This command removes the selected launch from the view.</description>
-      <topic label="Debug View" href="reference/ref-51.htm" />
-   </context>
-
-   <context  id="remove_all_action_context" >
-      <description>This command removes all terminated launches from the view.</description>
-      <topic label="Remove All Terminated Launches" href="reference/ref-69.htm" /> 
-      <topic label="Debug View" href="reference/ref-51.htm" />
-   </context>
-
-   <context  id="resume_action_context" >
-      <description>This command resumes the selected thread or the thread containing the selected stack frame.</description>
-      <topic label="Debug View" href="reference/ref-51.htm" />
-      <topic label="Resuming" href="tasks/tasks-135.htm" />
-   </context>
-
-   <context  id="run_to_line_action_context" >
-      <description>This command resumes execution to the selected line.</description>   
-   </context>
-
-   <context  id="show_types_action_context" >
-      <description>This option can be toggled to show or hide type names of variables in the view.</description>
-      <topic label="Show Type Names in Expressions View" href="reference/ref-57.htm" /> 
-      <topic label="Expressions View" href="reference/ref-56.htm"/>
-      <topic label="Show Type Names in Variables View" href="reference/ref-75.htm" />
-      <topic label="Variables View" href="reference/ref-74.htm"/>
-   </context>
-
-   <context  id="step_with_filters_action_context" >
-	<description>This command toggles step filters on/off, which are applied to the step into, over, and return commands.</description>
-   </context>
-   
-   <context  id="step_into_action_context" >
-	<description>This command steps into the highlighted statement.</description>
-      <topic label="Debug View" href="reference/ref-51.htm" />
-      <topic label="Stepping" href="tasks/tasks-136.htm" /> 
-     <topic label="Debugging Locally" href="concepts/clocdbug.htm"/>
-   </context>
-
-   <context  id="step_over_action_context" >
-        <description>This command steps over the highlighted statement. Execution will continue at the next line either in the same method or (if you are at the end of a method) it will continue in the method from which the current method was called.</description>
-      <topic label="Debug View" href="reference/ref-51.htm" />
-      <topic label="Stepping" href="tasks/tasks-136.htm" /> 
-      <topic label="Debugging Locally" href="concepts/clocdbug.htm"/>
-   </context>
-
-   <context  id="step_return_action_context" >
-      <description>This command steps out of the current method. The execution stops after exiting the current method.</description>
-      <topic label="Debug View" href="reference/ref-51.htm" />
-      <topic label="Stepping" href="tasks/tasks-136.htm" /> 
-      <topic label="Debugging Locally" href="concepts/clocdbug.htm"/>
-   </context>
-
-   <context  id="suspend_action_context" >
-	<description>This command suspends the selected debug target so that you can browse or modify code, inspect data, step, and so on.</description>
-	<topic label="Debug View" href="reference/ref-51.htm" />
-	<topic label="Suspending" href="tasks/tasks-134.htm"/>
-	<topic label="Debugging Locally" href="concepts/clocdbug.htm"/>
-   </context>
-
-   <context  id="terminate_action_context" >
-      <description>This command terminates the selected debug target.</description>
- 	<topic label="Terminate" href="reference/ref-67.htm"/>
-	<topic label="Connecting to a remote VM with the Remote Java application launch configuration" href="tasks/tasks-141.htm"/>
-	<topic label="Debug View" href="reference/ref-51.htm"/>
-   </context>
-
-   <context  id="terminate_all_action_context" >
-      <description>This command terminates all active debug targets.</description>
-	<topic label="Terminate All" href="reference/ref-71.htm"/>
-	<topic label="Debug View" href="reference/ref-51.htm"/>
-   </context>
-
-   <context  id="terminate_and_remove_action_context" >
-      <description>This command terminates the selected process or debug target and removes it from the view.</description>
- 	<topic label="Terminate and Remove" href="reference/ref-70.htm"/>
-	<topic label="Debug View" href="reference/ref-51.htm"/>
-   </context>
-
-   <context  id="select_all_breakpoints_action_context" >
-      <description>This command selects all breakpoint in the view.</description>
-   </context>
-   
-   <context  id="remove_breakpoint_action_context" >
-      <description>This command deletes the selected breakpoints.</description>
-   </context>
-   
-   <context  id="remove_all_breakpoints_action_context" >
-      <description>This command deletes all breakpoints in the view.</description>
-   </context>
-   
-   <context  id="select_all_variables_action_context" >
-      <description>This command selects all variables in the view.</description>
-   </context>
-   
-  <context  id="copy_variables_to_clipboard_action_context" >
-      <description>This command copies a textual representation of the selected variables to the clipboard.</description>
-   </context>   
-   
-   <context  id="select_all_expressions_action_context" >
-      <description>This command selects all expressions in the view.</description>
-   </context>         
-      
-   <context  id="remove_expression_action_context" >
-      <description>This command deletes the selected expressions.</description>
-   </context>      
-   
-   <context  id="remove_all_expressions_action_context" >
-      <description>This command deletes all expressions in the view.</description>
-   </context> 
-   
-   <context  id="edit_launch_configuration_action_context" >
-      <description>This command opens the launch configuration dialog on the launch configuration associated with the selection.</description>
-   </context>
-   
-   <context  id="open_launch_configuration_action_context" >
-      <description>This command opens the launch configuration dialog in the context of the specified launch group.</description>
-   </context> 
-   
-   <context  id="detail_pane_word_wrap_action_context" >
-      <description>This command toggles word wrap on and off in the details text area.</description>
-   </context>    
-   
-   <context  id="variables_content_providers_action_context" >
-      <description>This command toggles the display of logical variable structure.</description>
-   </context>
-
-   <context  id="ResetBaseAddressContextAction_context" >
-      <description>Go to the base address of the memory block.</description>
-   </context>
-   <context  id="FormatColumnAction_context" >
-      <description>Format the table to the selected column size.</description>
-   </context>
-   <context  id="TableRenderingPrefAction_context" >
-      <description>This command opens the dialog for modifying preferences in table renderings.</description>
-   </context>
-   <context  id="PrintViewTabContextAction_context" >
-      <description>Print the memory monitor or rendering.</description>
-   </context>
-   <context  id="GoToAddressAction_context" >
-      <description>Go to an address in the memory block.</description>
-   </context>
-   <context  id="CopyViewTabToClipboardContextAction_context" >
-      <description>Copy selected tab to clipboard.</description>
-   </context>
-   <context  id="RemoveMemoryBlockAction_context" >
-      <description>Remove selected memory block.</description>
-    </context>   
-    
-   <context  id="RemoveAllMemoryBlocksAction_context" >
-      <description>Remove all memory monitors from the workbench.</description>
-   </context>   
-
-   <context   id="DefaultColumnSizePrefAction_context">
-	   <description>This command sets the default column size for a memory monitor. </description>
-   </context>
-   
-   <context id="RemoveRenderingContextAction_context">
-   	  <description>This command removes the top visible rendering from the Memory Rendering pane. </description>
-   </context>
-
-   <context id="AddRenderingContextAction_context">
-   	  <description>This command adds a rendering to the selected Memory Rendering pane. </description>
-   </context>   
-   
-   <context id="LittleEndianAction_context">
-   	  <description>This command formats a rendering as little endian. </description>
-   </context>   
-
-   <context id="BigEndianAction_context">
-   	  <description>This command formats a rendering as big endian. </description>
-   </context>   
-
-   <context id="RestoreDefEndianessAction_context">
-   	  <description>This command formats a rendering with its default endianess. </description>
-   </context>   
-   
-   <context id="ReformatAction_context">
-   	  <description>This command resizes all columns to fit the content of the table. </description>
-   </context>   
-
-   <context id="ShowAddressColumnAction_context">
-   	  <description>This command toggles the visibility of the Address column. </description>
-   </context>   
-   
-   <context id="SelectCodePagesAction_context">
-   	  <description>This command opens the dialog for setting up codepage preferences in the Memory View </description>
-   </context>
-   
-   <context id="CodePagesPrefDialog_context">
-   	  <description>On this page, you can set codepage preferences in the Memory View</description>
-   </context>
-   
-   <context id="SelectCodepageDialog_context">
-   	  <description>This page sets the codepage for the selected preference.</description>
-   </context>
-
-   <context id="SetPaddedStrAction_context">
-   	  <description>This commands opens the dialog for setting up the padded string used in memory renderings.</description>
-   </context>
-   
-   <context id="SetPaddedStrDialog_context">
-   	  <description>On this page, you can set the padded string in memory renderings.</description>
-   </context>
-
-   <context id="NextPageAction_context">
-   	  <description>This command loads the next page of memory.</description>
-   </context>
-   
-   <context id="PrevPageAction_context">
-   	  <description>This command loads the previous page of memory.</description>
-   </context>
-   
-   <context id="find_element_context">
-   	  <description>This command finds a element by name.</description>
-   </context>
-   
-   <context id="configure_columns_context">
-   	  <description>This command sets the visible columns in the associated view.</description>
-   </context>   
-   
-   	<context  id="assign_value_context">
-		<description>This command attempts to assign a new value to the selected variable.</description>
-	</context>
-
-   	<context  id="variable_watch_action_context">
-		<description>This command creates a watch expression from the selected variable.</description>
-	</context>           
-
-   	<context  id="add_watch_expression_context">
-		<description>This command adds a watch expression to the Expressions View.</description>
-	</context> 
-	
-   	<context  id="reevaluate_watch_expression_context">
-		<description>This command reevaluates a watch expression.</description>
-	</context> 
-	
-   	<context  id="disable_watch_expression_context">
-		<description>This command disables a watch expression.</description>
-	</context> 
-
-   	<context  id="enable_watch_expression_context">
-		<description>This command enables a watch expression.</description>
-	</context> 			
-
-   	<context  id="edit_watch_expression_context">
-		<description>This command allows for editing of watch expressions.</description>
-	</context> 
-
-   	<context  id="edit_watch_expression_context">
-		<description>This command allows for editing of watch expressions.</description>
-	</context> 
-
-   	<context  id="edit_source_lookup_path_context">
-		<description>This command allows you to edit the source lookup path.</description>
-	</context> 
-
-   	<context  id="lookup_source_context">
-		<description>Forces source lookup.</description>
-	</context> 
-	
-   	<context  id="console_terminate_action_context">
-		<description>Terminates the process associated with the console.</description>
-	</context> 
-	
-   	<context  id="console_remove_all_terminated_context">
-		<description>Removes all terminated processes.</description>
-	</context> 	
-
-	<context  id="console_scroll_lock_action_context" >
-      <description>This command enables and disables scroll lock.</description>
-    </context>
-    
-  	<context  id="switchToAction_context" >
-      <description>This command displays the renderings associated with the selected memory monitor.</description>
-    </context>
-    
-    <context  id="switchMemoryBlockAction_context" >
-      <description>This command displays the renderings associated with the next memory monitor.</description>
-    </context>
-
-    <context  id="resetMemoryMonitor_context" >
-      <description>This command resets the renderings associated with the selected memory monitors.</description>
-    </context>
-    
-    <context  id="FormatTableRenderingAction_context" >
-      <description>This command allows you to format the selected rendering.</description>
-    </context>
-    
-    <context  id="MemoryViewPreferences_context" >
-      <description>This command allows you to open the preference dialog for the Memory View.</description>
-    </context>  
-    
-    <context  id="memory_view_pane_orientation_action_context" >
-      <description>This command allows you set the Memory View to the selected orientation.</description>
-    </context>  
-
-<!-- Views -->
-   <context  id="debug_view_context" >
-      <description>This view displays system processes and the threads and stack frames for each target you are debugging.</description>
- 	<topic label="Debug View" href="reference/ref-51.htm"/>
-	<topic label="Debugger Concepts" href="concepts/concepts-10.htm"/>
-	<topic label="Copy Stack" href="reference/ref-51c.htm" />
-	<topic label="Disconnect" href="reference/ref-68.htm" />
-	<topic label="Drop to Frame" href="reference/ref-51d.htm" />
-	<topic label="Open on Declaring Type" href="reference/ref-51a.htm" />
-	<topic label="Open on Receiving Type" href="reference/ref-51b.htm" />
-	<topic label="Relaunch" href="reference/ref-72.htm" />
-	<topic label="Remove All Terminated Launches" href="reference/ref-69.htm" />
-	<topic label="Resuming" href="tasks/tasks-135.htm" />
-	<topic label="Show Qualified Names" href="reference/ref-58.htm" />
-	<topic label="Stepping" href="tasks/tasks-136.htm" />
-	<topic label="Suspending" href="tasks/tasks-134.htm"/>
-	<topic label="Terminate" href="reference/ref-67.htm"/>
-	<topic label="Terminate All" href="reference/ref-71.htm"/>
-	<topic label="Terminate and Remove" href="reference/ref-70.htm"/>
-   </context>
-
-   <context  id="variable_view_context" >
-      <description>This view displays the variables in your program.</description>
-		<topic label="Variables View" href="reference/ref-74.htm"/>
-		<topic label="Inspecting Values" href="tasks/tasks-137.htm"/>
-      	<topic label="Show Qualified Names in Variables View" href="reference/ref-76.htm" />
-      	<topic label="Show Type Names in Variables View" href="reference/ref-75.htm" />
-      	<topic label="Show Detail Pane in Variables View" href="reference/ref-showdetailpane.htm" />
-      	<topic label="Add/Remove Watchpoint" href="reference/ref-74a.htm" />
-      	<topic label="Show Static Fields in Variables View" href="reference/ref-62.htm" />
-      	<topic label="Show Constants in Variables View" href="reference/ref-63.htm" />
-      	<topic label="Change Variable Values in the Variables View" href="reference/ref-81.htm" /> 
-      	<topic label="Inspect in the Variables View" href="reference/ref-80.htm" /> 
-   </context>
-
-   <context  id="expression_view_context" >
-	<description>This view shows the results of inspecting an expression or variable.</description>
-	<topic label="Expressions View" href="reference/ref-56.htm"/>
-	<topic label="Select All in the Expressions View" href="reference/ref-56a.htm"/>
-	<topic label="Copy Variables in the Expressions View" href="reference/ref-56b.htm"/>
-	<topic label="Remove Selected Expressions" href="reference/ref-59.htm" />
-    <topic label="Remove All Expressions" href="reference/ref-60.htm" />
-    <topic label="Change Variable Values in the Expressions View" href="reference/ref-65.htm" /> 
-    <topic label="Show Constants in the Expressions View" href="reference/ref-63.htm" />
-    <topic label="Show Static Fields in the Expressions View" href="reference/ref-62.htm" />
-    <topic label="Show Qualified Names in the Expressions View" href="reference/ref-58.htm" />
-	<topic label="Show Type Names in the Expressions View" href="reference/ref-57.htm" /> 
-    <topic label="Show Detail Pane for the Expressions View" href="reference/ref-56c.htm" /> 
-    <topic label="Add/Remove Watchpoint" href="reference/ref-56d.htm" /> 
-    <topic label="Inspect" href="reference/ref-64.htm" /> 
-    <topic label="Open Declared Type" href="reference/ref-56e.htm" /> 
-   </context>
-
-   <context  id="breakpoint_view_context" >
-	<description>The Breakpoints view lists all the breakpoints you have set.</description>
-	<topic label="Breakpoints View" href="reference/ref-35.htm"/>
-	<topic label="Go to File for Breakpoint" href="reference/ref-38.htm" />
-	<topic label="Add Java Exception Breakpoint" href="reference/ref-40.htm" />
-	<topic label="Suspend Policy" href="reference/brkSuspendPolicy.htm" />
-	<topic label="Hit Count" href="reference/ref-43.htm" />
-	<topic label="Uncaught" href="reference/ref-41.htm" />
-	<topic label="Caught" href="reference/ref-42.htm" />
-	<topic label="Modification" href="reference/brkMod.htm" />
-	<topic label="Access" href="reference/brkAccess.htm" />
-	<topic label="Exit" href="reference/brkExit.htm" />
-	<topic label="Entry" href="reference/brkEntry.htm" />
-	<topic label="Select All" href="reference/brkSelectAll.htm" />
-	<topic label="Enable" href="reference/ref-44.htm" />
-	<topic label="Disable" href="reference/ref-44a.htm" />
-	<topic label="Remove Selected Breakpoints" href="reference/ref-36.htm" />
-	<topic label="Remove All Breakpoints" href="reference/ref-37.htm" />
-    <topic label="Show Qualified Names in Breakpoints View" href="reference/ref-39.htm" /> 
-    <topic label="Show Supported Breakpoints" href="reference/brkShowSupported.htm" /> 
-    <topic label="Breakpoint Properties" href="reference/brkProperties.htm" /> 
-   </context>
-
-   <context  id="console_view_context" >
-	<description>This view shows a collection of available consoles.</description>
-   </context>
-   
-   <context  id="process_console_context" >
-	<description>This console shows the output of the execution of your program and allows you to enter any necessary user input.</description>
-	<topic label="Console View" href="reference/ref-45.htm"/>
-	<topic label="Copy" href="reference/ref-47.htm"/>
-	<topic label="Select All" href="reference/ref-48.htm"/>
-	<topic label="Find/Replace" href="reference/ref-49.htm"/>
-	<topic label="Go To Line" href="reference/ref-50.htm"/>
-	<topic label="Clear the Console" href="reference/ref-46.htm"/>
-	<topic label="Terminate" href="reference/ref-45b.htm"/>
-   </context>   
-
-	<context  id="MemoryView_context" >
-      <description>This view displays renderings of memory monitors.</description>
-   </context>
-
-   <context  id="GoToAddressDialog_context" >
-      <description>This dialog lets you jump to an address in the memory block.</description>
-   </context>       
-   
-   <context  id="MemoryViewPreferencePage_context" >
-      <description>Preference page for setting the default column size when a new memory monitor is added. </description>
-   </context>
-
-   <context  id="MonitorMemoryBlockDialog_context" >
-      <description>This dialog allows you to add a memory block to the Memory View</description>
-   </context>
-   
-   <context  id="FormatTableRenderingDialog_context" >
-      <description>This dialog allows you to format the selected rendering.</description>
-   </context>
-
-<!-- Preference pages -->
-   <context  id="debug_preference_page_context" >
-      <description>On this page, you can set preferences for debugging your programs.</description>
-	<topic label="Debug Preferences" href="reference/ref-11.htm"/>
-	<topic label="Debugger Concepts" href="concepts/concepts-10.htm"/>
-  </context>
-
-   <context id="console_preference_page_context" >
-      <description>On this page, you can set the preferences for the debug console.</description>
-	<topic label="Console Preferences" href="reference/ref-12.htm"/>
- 	<topic label="Debugger Concepts" href="concepts/concepts-10.htm"/>
-   </context>
-   
-   <context id="launch_history_preference_page_context" >
-      <description>On this page, you can modify launch history and favorites.</description>
-	<topic label="Launch History Preferences" href="reference/ref-11.htm"/>
-   </context>
-   
-   <context id="debug_action_groups_views_preference_page_context" >
-      <description>On this page, you can enable and disable actions associated with a debugger. When a group of actions is disabled, the actions will not appear in debug views.</description>
-   </context>
-  
-  <context id="simple_variable_preference_page_context">
-   	 <description>One this page, you can create and configure simple launch variables which you can reference in launch configurations that support variables.</description>
-  </context>
-
-   <context  id="table_renderings_preference_page_context">
-      <description>On this page, you can configure the memory loading mode in table renderings.   </description>
-   </context>
-   
-   <context  id="perspective_preference_page_context">
-      <description>On this page, you can configure the perspectives used when running and debugging.</description>
-   </context>
-     
-    <context  id="launching_preference_page_context">
-      <description>On this page, you can configure launch options.</description>
-   </context>
-   
-   <context  id="launch_configuration_preference_page_context">
-      <description>On this page, you can configure the filters used in the launch dialog and migrate launch configurations.</description>
-   </context>
-  
-   <context  id="view_management_preference_page_context">
-      <description>On this page, you can select the perspectives that debug related views will be opened in automatically.</description>
-   </context>
-   
-   <context  id="resetMemoryMonitor_preference_page_context" >
-      <description>On this page, you can configure the reset memory monitor behavior. </description>
-   </context>
-	
-<!-- Property pages -->
-  <context id="process_property_page_context" >
-     <description>This page displays the command line used to launch a process.</description>
-  </context>
-  
-  <context id="TableRenderingPropertiesPage_context" >
-     <description>This page displays properties from the selected memory.</description>
-  </context>
-  
-<!-- Launch configuration tabs -->
-  <context id="launch_configuration_dialog_perspective_tab" >
-     <description>This tab allows you to set the perspective that is switched to/opened when a configuration is launched. A perspective may be associated with each supported launch mode.</description>
-  </context>
-  
-  <context id="launch_configuration_dialog refresh_tab" >
-	 <description>This tab allows you to choose which resources are refreshed when a launch configuration is executed.</description>
-  </context>
-  
-  <context id="launch_configuration_dialog_common_tab" >
-     <description>This tab allows you to set the type of the launch configuration, which favorites menu it will be displayed within and whether to launch the configuration in the background.</description>
-     <topic label="Java application launch configuration" href=" tasks\tasks-java-local-configuration.htm"/>
-  </context>
-  
-  <context id="launch_configuration_dialog_environment_tab" >
-     <description>This tab allows you to create and configure the environment variables that will be passed into the launch configuration when it is executed.</description>
-  </context>
-
-<!-- Dialogs -->
-  <context id="launch_configuration_dialog" >
-     <description>This dialog allows you to manage aspects of launching programs from within Eclipse.</description>
-  </context> 
-  
-  <context id="edit_source_lookup_path_dialog" >
-     <description>This dialog allows you to edit the current source lookup path.</description>
-  </context>
-  
-  <context id="single_launch_configuration_dialog" >
-     <description>This dialog allows you to edit a launch configuration.</description>
-  </context>
-  
-  <context id="export_breakpoints_wizard_page_context" >
-     <description>This wizard page allows you to select breakpoints to export to the local filesystem.</description>
-  </context>
-  
-  <context id="import_breakpoints_wizard_page_context" >
-     <description>This wizard page allows you to import breakpoints into your workspace from a previously exported file.</description>
-  </context> 
-  
-  <context id="find_variables_dialog_context" >
-     <description>This dialog allows you to search for variables by name.</description>
-  </context>
-  
-    <context id="find_expressions_dialog_context" >
-     <description>This dialog allows you to search for expressions by name.</description>
-  </context>
-  
-    <context id="add_watch_expression_dialog_context" >
-     <description>This dialog allows you to create a new watch expression.</description>
-  </context>
-  
-    <context id="edit_watch_expression_dialog_context" >
-     <description>This dialog allows you to edit an existing watch expression.</description>
-  </context>
-  
-  <context id="find_element_dialog_context">
-   	  <description>This dialog allows you to search for an element by name.</description>
-   </context>
-   
-  <context id="configure_columns_dialog_context">
-   	  <description>This dialog allows you to select the columns to display in a view.</description>
-   </context> 
-
-  <context  id="AddMemoryRenderingDialog_context" >
-      <description>This dialog allows you to add memory rendering.</description>
-  </context>
-</contexts>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/contexts_JDT.xml b/bundles/org.eclipse.jdt.doc.user/contexts_JDT.xml
deleted file mode 100644
index a75f667..0000000
--- a/bundles/org.eclipse.jdt.doc.user/contexts_JDT.xml
+++ /dev/null

@@ -1,1750 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-
-    <!-- Actions -->
-
-    <context id="add_unimplemented_constructors_action_context">
-        <description>This command copies the constructors of the super class to the selected class.</description>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="getter_setter_action_context">
-        <description>This command generates getter and setter methods for the selected field.</description>
-        <topic label="Generating getters and setters" href="tasks/tasks-57.htm"/>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="add_methodbreakpoint_action_context">
-        <description>This command adds a method entry breakpoint for the selected method.</description>
-        <topic label="Adding breakpoints" href="tasks/tasks-144.htm"/>
-        <topic label="Removing breakpoints" href="tasks/tasks-144a.htm"/>
-        <topic label="Enabling and disabling breakpoints" href="tasks/tasks-144b.htm"/>
-        <topic label="Setting method breakpoints" href="tasks/tasks-145.htm"/>
-        <topic label="Applying hit counts" href="tasks/tasks-146.htm"/>
-        <topic label="Managing conditional breakpoints" href="tasks/tasks-144c.htm"/>
-        <topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-        <topic label="Breakpoints view" href="reference/ref-35.htm"/>
-        <topic label="Debugger" href="concepts/concepts-10.htm"/>
-        <topic label="Remote debugging" href="concepts/cremdbug.htm"/>
-    </context>
-
-    <context id="add_methodstub_action_context">
-        <description>This command creates a method stub for the selected method.</description>
-        <topic label="Type Hierarchy view" href="reference/ref-type-hierarchy.htm"/>
-    </context>
-
-    <context id="add_unimplemented_methods_action_context">
-        <description>Allows you to override methods from a superclass or to implement a method from an interface.</description>
-        <topic label="Override Methods dialog" href="reference/ref-dialog-override-method.htm"/>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="show_in_packageview_action_context">
-        <description>Displays the selected element in the Package Explorer.</description>
-        <topic label="Showing a Type&apos;s Compilation Unit in the Package Explorer" href="tasks/tasks-74.htm"/>
-        <topic label="Package Explorer view" href="reference/ref-view-package-explorer.htm"/>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="show_in_hierarchyview_action_context">
-        <description>This command opens the Hierarchy view on the selected element.</description>
-        <topic label="Hierarchy view" href="reference/ref-type-hierarchy.htm"/>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="add_imports_on_selection_action_context">
-        <description>This command adds an import statement for the selected type to the compilation unit.</description>
-        <topic label="Adding required import statements" href="tasks/tasks-59.htm"/>
-        <topic label="Setting the order of import statements" href="tasks/tasks-61.htm"/>
-    </context>
-
-    <context id="organize_imports_action_context">
-        <description>This command generates the import statements for this type. It adds all required import statements and removes those that are not required.</description>
-        <topic label="Organizing existing import statements" href="tasks/tasks-60.htm"/>
-        <topic label="Setting the order of import statements" href="tasks/tasks-61.htm"/>
-    </context>
-
-    <context id="run_to_line_action_context">
-        <description>While debugging, this command allows you to run the program to the location of the cursor.</description>
-        <topic label="Run to Line" href="reference/ref-4.htm"/>
-        <topic label="Stepping" href="tasks/tasks-136.htm"/>
-        <topic label="Debug view" href="reference/ref-51.htm"/>
-        <topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-        <topic label="Debugger" href="concepts/concepts-10.htm"/>
-        <topic label="Remote debugging" href="concepts/cremdbug.htm"/>
-    </context>
-
-    <context id="toggle_presentation_action_context">
-        <description>Allows you to toggle the editor between displaying the whole compilation unit and the code for just the selected element.</description>
-        <topic label="Showing single elements or whole Java files" href="tasks/tasks-6.htm"/>
-        <topic label="Java editor concepts" href="reference/ref-java-editor.htm"/>
-    </context>
-
-    <context id="toggle_texthover_action_context">
-        <description>Allows you to switch the hover hints on and off for Javadoc and Debug.</description>
-        <topic label="Java editor reference" href="reference/ref-java-editor.htm"/>
-        <topic label="Java editor concepts" href="concepts/concepts-7.htm"/>
-    </context>
-
-    <context id="toggle_mark_occurrences_action_context">
-        <description>Allows you to switch mark occurrences on and off.</description>
-    </context>
-
-    <context id="display_action_context">
-        <description>This command evaluates the selected expression and shows the result in the Display view.</description>
-        <topic label="Displaying the result of evaluating an expression" href="tasks/tasks-151.htm"/>
-        <topic label="Evaluating expressions" href="tasks/tasks-138.htm"/>
-        <topic label="Display view" href="reference/ref-52.htm"/>
-        <topic label="Run and Debug Actions" href="reference/ref-4.htm"/>
-    </context>
-
-    <context id="focus_on_selection_action">
-        <description>This command allows you to select a type visible in the Hierarchy view to become the new focus of the Hierarchy view.</description>
-        <topic label="Type Hierarchy view" href="reference/ref-type-hierarchy.htm"/>
-        <topic label="Java views" href="concepts/concepts-6.htm"/>
-    </context>
-
-    <context id="focus_on_type_action">
-        <description>This command allows you to choose any type and opens it in the Hierarchy view.</description>
-        <topic label="Type Hierarchy view" href="reference/ref-type-hierarchy.htm"/>
-        <topic label="Java views" href="concepts/concepts-6.htm"/>
-    </context>
-
-    <context id="typehierarchy_history_action">
-        <description>Allows you to switch back to previously shown type hierarchies.</description>
-        <topic label="Type Hierarchy view" href="reference/ref-type-hierarchy.htm"/>
-    </context>
-
-    <context id="filter_public_action">
-        <description>This filter removes all non-public members from the presentation.</description>
-        <topic label="Showing and hiding members in Java views" href="tasks/tasks-191.htm"/>
-    </context>
-
-    <context id="filter_fields_action">
-        <description>This filter removes all fields from the presentation.</description>
-        <topic label="Showing and hiding members in Java views" href="tasks/tasks-191.htm"/>
-    </context>
-
-    <context id="filter_static_action">
-        <description>This filter removes all static members from the presentation.</description>
-        <topic label="Showing and hiding members in Java views" href="tasks/tasks-191.htm"/>
-    </context>
-
-    <context id="show_inherited_action">
-        <description>This option will display all members inherited from the super types.</description>
-        <topic label="Finding overridden methods" href="tasks/tasks-44.htm"/>
-        <topic label="Type Hierarchy view" href="reference/ref-type-hierarchy.htm"/>
-        <topic label="Java views" href="concepts/concepts-6.htm"/>
-    </context>
-
-    <context id="show_supertypes_action">
-        <description>This option will display all super types. </description>
-        <topic label="Finding overridden methods" href="tasks/tasks-44.htm"/>
-        <topic label="Type Hierarchy view" href="reference/ref-type-hierarchy.htm"/>
-        <topic label="Java views" href="concepts/concepts-6.htm"/>
-    </context>
-
-    <context id="show_subtypes_action">
-        <description>This option will display all subtypes.</description>
-        <topic label="Finding overridden methods" href="tasks/tasks-44.htm"/>
-        <topic label="Type Hierarchy view" href="reference/ref-type-hierarchy.htm"/>
-        <topic label="Java views" href="concepts/concepts-6.htm"/>
-    </context>
-
-    <context id="show_hierarchy_action">
-        <description>This option displays the class hierachy.</description>
-        <topic label="Finding overridden methods" href="tasks/tasks-44.htm"/>
-        <topic label="Type Hierarchy view" href="reference/ref-type-hierarchy.htm"/>
-        <topic label="Java views" href="concepts/concepts-6.htm"/>
-    </context>
-
-    <context id="enable_methodfilter_action">
-        <description>This option displays all types in the current hierarchy that define or implement the selected method.</description>
-        <topic label="Finding overridden methods" href="tasks/tasks-44.htm"/>
-        <topic label="Type Hierarchy view" href="reference/ref-type-hierarchy.htm"/>
-        <topic label="Java views" href="concepts/concepts-6.htm"/>
-    </context>
-
-    <context id="open_class_wizard_action">
-        <description>This action opens a wizard for creating a new class.</description>
-        <topic label="Creating a new Java class" href="tasks/tasks-17.htm"/>
-        <topic label="Creating a top-level class" href="tasks/tasks-18.htm"/>
-        <topic label="Creating a nested class" href="tasks/tasks-19.htm"/>
-        <topic label="Creating a new class in an existing compilation unit" href="tasks/tasks-20.htm"/>
-        <topic label="New Class wizard reference" href="reference/ref-126.htm"/>
-    </context>
-
-    <context id="open_enum_wizard_action">
-        <description>This action opens a wizard for creating a new enum.</description>
-        <topic label="Creating a new Java enum" href="tasks/tasks-17b.htm"/>
-        <topic label="New Enum wizard reference" href="reference/ref-126b.htm"/>
-    </context>
-
-    <context id="open_interface_wizard_action">
-        <description>This action opens a wizard for creating a new interface.</description>
-        <topic label="Creating a new Java interface" href="tasks/tasks-21.htm"/>
-        <topic label="Creating a top-level interface" href="tasks/tasks-23.htm"/>
-        <topic label="Creating a nested interface" href="tasks/tasks-24.htm"/>
-        <topic label="Creating a new interface in an existing compilation unit" href="tasks/tasks-25.htm"/>
-        <topic label="New Interface wizard reference" href="reference/ref-127.htm"/>
-    </context>
-
-    <context id="open_annotation_wizard_action">
-        <description>This action opens a wizard for creating a new annotation.</description>
-        <topic label="Creating a new Java annotation" href="tasks/tasks-21b.htm"/>
-        <topic label="New Annotation wizard reference" href="reference/ref-127b.htm"/>
-    </context>
-
-    <context id="open_package_wizard_action">
-        <description>This action opens a wizard for creating a new package.</description>
-        <topic label="Creating a new Java package" href="tasks/tasks-15.htm"/>
-        <topic label="New Package wizard reference" href="reference/ref-125.htm"/>
-    </context>
-
-    <context id="open_project_wizard_action">
-        <description>This action opens a wizard for creating a new Java project.</description>
-        <topic label="Creating a new Java project" href="tasks/tasks-12.htm"/>
-        <topic label="Creating a Java project as its own source container" href="tasks/tasks-13.htm"/>
-        <topic label="Creating a Java project with source folders" href="tasks/tasks-14.htm"/>
-		<topic label="Creating a new source folder with exclusion filter" href="tasks/tasks-221.htm"/>
-		<topic label="Creating a new source folder with specific output folder" href="tasks/tasks-222.htm"/>
-        <topic label="New Java Project wizard reference" href="reference/ref-121.htm"/>
-        <topic label="Java projects" href="concepts/concepts-3.htm"/>
-    </context>
-
-    <context id="open_snippet_wizard_action">
-        <description>This action opens a wizard for creating a new Java scrapbook page.</description>
-        <topic label="Creating a Java scrapbook page" href="tasks/tasks-149.htm"/>
-        <topic label="New Scrapbook wizard reference" href="reference/ref-129.htm"/>
-        <topic label="Scrapbook" href="concepts/concepts-11.htm"/>
-    </context>
-
-    <context id="clear_working_set_action">
-        <description>This action removes the currently installed working set filter.</description>
-        <topic label="Package Explorer view" href="reference/ref-view-package-explorer.htm"/>
-    </context>
-
-    <context id="goto_marker_action">
-        <description>This action shows the search result in a Java editor.</description>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Java search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="java_search_action_context">
-        <description>This command opens the Java search page in the search dialog.</description>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Java search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="goto_package_action">
-        <description>This action allows you to choose any package and selects it in the Package Explorer.</description>
-        <topic label="Showing an element in the Package Explorer" href="tasks/tasks-74.htm"/>
-        <topic label="Package Explorer view" href="reference/ref-view-package-explorer.htm"/>
-        <topic label="Java views" href="concepts/concepts-6.htm"/>
-    </context>
-
-    <context id="history_list_action">
-        <description>Choose and switch back to a previously shown type hierarchy.</description>
-        <topic label="Changing the appearance of the Hierarchy view" href="tasks/tasks-38.htm"/>
-        <topic label="Opening a type hierarchy on a Java element" href="tasks/tasks-39.htm"/>
-        <topic label="Opening a type hierarchy on the current text selection" href="tasks/tasks-40.htm"/>
-        <topic label="Opening a type hierarchy in its own perspective" href="tasks/tasks-42.htm"/>
-        <topic label="Type Hierarchy view" href="reference/ref-type-hierarchy.htm"/>
-        <topic label="Java views" href="concepts/concepts-6.htm"/>
-    </context>
-
-    <context id="lexical_sorting_outline_action">
-        <description>Displays the elements in alphabetical order.</description>
-        <topic label="Sorting elements in Java views" href="tasks/tasks-195.htm"/>
-    </context>
-
-    <context id="lexical_sorting_browsing_action">
-        <description>Displays the elements in aphabetical order.</description>
-        <topic label="Sorting elements in Java views" href="tasks/tasks-195.htm"/>
-    </context>
-
-    <context id="open_java_perspective_action">
-        <description>This action opens the Java Perspective.</description>
-        <topic label="Java perspectives" href="concepts/concepts-5.htm"/>
-    </context>
-
-    <context id="open_java_browsing_perspective_action">
-        <description>This action opens the Java Browsing Perspective.</description>
-        <topic label="Java perspectives" href="concepts/concepts-5.htm"/>
-    </context>
-
-    <context id="open_project_action">
-        <description>This action opens a previously closed project.</description>
-        <topic label="Java projects" href="concepts/concepts-3.htm"/>
-        <topic label="Project actions" href="reference/ref-menu-project.htm"/>
-    </context>
-
-    <context id="open_type_action">
-        <description>Choose a type and open it in a Java editor.</description>
-        <topic label="Opening an editor on a type" href="tasks/tasks-76.htm"/>
-        <topic label="Opening an editor for a selected element" href="tasks/tasks-73.htm"/>
-        <topic label="Open type dialog" href="reference/ref-148.htm"/>
-    </context>
-
-    <context id="open_type_in_hierarchy_action">
-        <description>Choose a type and open it in the Hierarchy view and in a Java editor.</description>
-        <topic label="Opening a type hierarchy on a Java element" href="tasks/tasks-39.htm"/>
-        <topic label="Opening a type hierarchy on the current text selection" href="tasks/tasks-40.htm"/>
-        <topic label="Opening a type hierarchy in its own perspective" href="tasks/tasks-42.htm"/>
-        <topic label="Open type dialog" href="reference/ref-148.htm"/>
-        <topic label="Type Hierarchy view" href="reference/ref-type-hierarchy.htm"/>
-    </context>
-
-    <context id="add_javadoc_stub_action">
-        <description>This action generates a Javadoc skeleton for the selected member. The skeleton contains all the information that can be derived from the member&apos;s signature.</description>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="add_task_action">
-        <description>Adds a new task.</description>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="externalize_strings_action">
-        <description>Finds and supports externalizing of all strings that are not externalized.</description>
-        <topic label="Finding strings to externalize" href="tasks/tasks-188.htm"/>
-        <topic label="Using the Externalize Strings wizard" href="tasks/tasks-180.htm"/>
-        <topic label="String externalization" href="concepts/cnls.htm"/>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="extract_method_action">
-        <description>Support for extracting a method from a code selection.</description>
-        <topic label="Extracting a method" href="tasks/tasks-87.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="extract_temp_action">
-        <description>Support for extracting a temporary variable from a code selection.</description>
-        <topic label="Extracting a local variable" href="tasks/tasks-159.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="find_declarations_in_workspace_action">
-        <description>Searches for all declarations of a selected element.</description>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_declarations_in_project_action">
-        <description>Searches for all declarations of a selected element in the project enclosing the element.</description>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_declarations_in_hierarchy_action">
-        <description>Searches for all declarations of a selected element in the element&apos;s type hierarchy.</description>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_declarations_in_working_set_action">
-        <description>Searches for all declarations of a selected element in a specified working set.</description>
-        <topic label="Conducting a Java search using the search dialog" href="tasks/tasks-103.htm"/>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_references_in_workspace_action">
-        <description>Searches for all references to a selected element.</description>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_references_in_project_action">
-        <description>Searches for all references to a selected element in the project enclosing the element..</description>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_references_in_hierarchy_action">
-        <description>Searches for all references to a selected element in the element&apos;s type hierarchy.</description>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_references_in_working_set_action">
-        <description>Searches for all references to a selected element in a specified working set.</description>
-        <topic label="Conducting a Java search using the search dialog" href="tasks/tasks-103.htm"/>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_implementors_in_workspace_action">
-        <description>Searches for all implementors of a selected element.</description>
-        <topic label="Conducting a Java search using the search dialog" href="tasks/tasks-103.htm"/>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-     <context id="find_implementors_in_project_action">
-        <description>Searches for all implementors of a selected element in the project enclosing the element.</description>
-        <topic label="Conducting a Java search using the search dialog" href="tasks/tasks-103.htm"/>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
- 
-    <context id="find_implementors_in_working_set_action">
-        <description>Searches for all implementors of a selected element in a specified working set.</description>
-        <topic label="Conducting a Java search using the search dialog" href="tasks/tasks-103.htm"/>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_read_references_action">
-        <description>Searches for all locations where the selected field is read.</description>
-        <topic label="Conducting a Java search using the search dialog" href="tasks/tasks-103.htm"/>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_read_references_in_workspace_action">
-        <description>Searches for all locations where the selected field is read.</description>
-        <topic label="Conducting a Java search using the search dialog" href="tasks/tasks-103.htm"/>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_read_references_in_project_action">
-        <description>Searches in the project enclosing the selected field for all locations where the selected field is read.</description>
-        <topic label="Conducting a Java search using the search dialog" href="tasks/tasks-103.htm"/>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_read_references_in_hierarchy_action">
-        <description>Searches in the type hierarchy for all locations where the selected field is read.</description>
-        <topic label="Conducting a Java search using the search dialog" href="tasks/tasks-103.htm"/>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_write_references_in_hierarchy_action">
-        <description>Searches in the type hierarchy for all locations where the selected field is modified.</description>
-        <topic label="Conducting a Java search using the search dialog" href="tasks/tasks-103.htm"/>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_read_references_in_working_set_action">
-        <description>Searches in a working set for all locations where the selected field is read.</description>
-        <topic label="Conducting a Java search using the search dialog" href="tasks/tasks-103.htm"/>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_write_references_in_working_set_action">
-        <description>Searches in a working set for all locations where the selected field is modified.</description>
-        <topic label="Conducting a Java search using the search dialog" href="tasks/tasks-103.htm"/>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_write_references_in_workspace_action">
-        <description>Searches for all locations where the selected field is modified.</description>
-        <topic label="Conducting a Java search using the search dialog" href="tasks/tasks-103.htm"/>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_write_references_in_project_action">
-        <description>Searches in the project enclosing the selected field for all locations where the selected field is modified.</description>
-        <topic label="Conducting a Java search using the search dialog" href="tasks/tasks-103.htm"/>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_write_references_action">
-        <description>Searches for all locations where the selected field is modified.</description>
-        <topic label="Conducting a Java search using the search dialog" href="tasks/tasks-103.htm"/>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_occurrences_in_file_action">
-        <description>Searches for all locations of the selected element in its file.</description>
-        <topic label="Conducting a Java search using the search dialog" href="tasks/tasks-103.htm"/>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="working_set_find_action">
-        <description>Searches for a selected Java element in a working set.</description>
-        <topic label="Conducting a Java search using the search dialog" href="tasks/tasks-103.htm"/>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search" href="concepts/concepts-8.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_strings_to_externalize_action">
-        <description>Searches for all strings that are not externalized.</description>
-        <topic label="String externalization" href="concepts/cnls.htm"/>
-        <topic label="Finding strings to externalize" href="tasks/tasks-188.htm"/>
-        <topic label="Externalize Strings wizard" href="reference/ref-wizard-externalize-strings.htm"/>
-    </context>
-
-    <context id="inline_temp_action">
-        <description>This action removes a local variable and replaces all occurrences with its computing expression.</description>
-        <topic label="Inlining a local variable" href="tasks/tasks-161.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="modify_parameters_action">
-        <description>Supports changing the signature of a method.</description>
-        <topic label="Change method signature" href="tasks/tasks-98.htm"/>
-        <topic label="Changing method signature" href="tasks/tasks-157.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="open_action">
-        <description>Opens the selected element in a Java editor.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="open_external_javadoc_action">
-        <description>Opens the selected element&apos;s Javadoc in the default external HTML browser.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-        <topic label="Javadoc location" href="reference/ref-dialog-javadoc-location.htm"/>
-    </context>
-
-    <context id="open_super_implementation_action">
-        <description>This action opens the method in the super class that is overridden by the selected method.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="pull_up_action">
-        <description>Supports moving members up in the type hierarchy.</description>
-        <topic label="Pulling members up to superclass" href="tasks/tasks-165.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="refresh_action">
-        <description>Refreshes the contents from the local file system.</description>
-        <topic label="File actions" href="reference/ref-menu-file.htm"/>
-    </context>
-
-    <context id="rename_action">
-        <description>Supports renaming Java elements.</description>
-        <topic label="Renaming a package" href="tasks/tasks-90.htm"/>
-        <topic label="Renaming a compilation unit" href="tasks/tasks-92.htm"/>
-        <topic label="Renaming a type" href="tasks/tasks-94.htm"/>
-        <topic label="Renaming a method" href="tasks/tasks-96.htm"/>
-        <topic label="Renaming a field" href="tasks/tasks-169.htm"/>
-        <topic label="Renaming a local variable" href="tasks/tasks-204.htm"/>
-        <topic label="Renaming method parameters" href="tasks/tasks-98.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="self_encapsulate_action">
-        <description>Modifies code by replacing a field&apos;s read and write accesses with corresponding calls to getter and setter methods.</description>
-        <topic label="Self encapsulating a field" href="tasks/tasks-162.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="show_in_navigator_action">
-        <description>Shows the selected element in the Navigator view.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="surround_with_try_catch_action">
-        <description>Wraps the code selection into a try/catch block. Handles all exceptions that would cause a compilation error.</description>
-        <topic label="Using Surround with try/catch" href="tasks/tasks-179.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="open_resource_action">
-        <description>Opens the selected element in a Java editor.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="select_working_set_action">
-        <description>This filter removes all elements from the view that are not part of the working set.</description>
-        <topic label="Package Explorer view" href="reference/ref-view-package-explorer.htm"/>
-    </context>
-
-    <context id="structured_selection_history_action">
-        <description>Restores the last structured selection.</description>
-        <topic label="Using Structured Selection" href="tasks/tasks-176.htm"/>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="structured_select_enclosing_action">
-        <description>Extends the selection according to the Java grammar, to the enclosing syntactic container.</description>
-        <topic label="Using Structured Selection" href="tasks/tasks-176.htm"/>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="structured_select_next_action">
-        <description>Extends the selection according to the Java grammar, to include the next neighboring syntactic element.</description>
-        <topic label="Using Structured Selection" href="tasks/tasks-176.htm"/>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="structured_select_previous_action">
-        <description>Extends the selection according to the Java grammar, to include the previous neighboring syntactic element.</description>
-        <topic label="Using Structured Selection" href="tasks/tasks-176.htm"/>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="toggle_orientations_action">
-        <description>Changes the orientation of the panes of the Hierarchy view.</description>
-        <topic label="Using the Hierarchy view" href="tasks/tasks-37.htm"/>
-        <topic label="Changing the appearance of the Hierarchy view" href="tasks/tasks-38.htm"/>
-        <topic label="Type Hierarchy view" href="reference/ref-type-hierarchy.htm"/>
-    </context>
-
-    <context id="cut_action">
-        <description>Deletes the selected elements and copies them onto the clipboard.</description>
-        <topic label="Edit actions" href="reference/ref-menu-edit.htm"/>
-    </context>
-
-    <context id="copy_action">
-        <description>Copies the selected element into the clipboard.</description>
-        <topic label="Copying and moving Java elements" href="tasks/tasks-85.htm"/>
-        <topic label="Edit actions" href="reference/ref-menu-edit.htm"/>
-    </context>
-
-    <context id="paste_action">
-        <description>Pastes the elements currently on the clipboard at the insertion point.</description>
-        <topic label="Copying and moving Java elements" href="tasks/tasks-85.htm"/>
-        <topic label="Edit actions" href="reference/ref-menu-edit.htm"/>
-    </context>
-
-    <context id="delete_action">
-        <description>Deletes the selected elements.</description>
-        <topic label="Edit actions" href="reference/ref-menu-edit.htm"/>
-    </context>
-
-    <context id="open_type_hierarchy_action">
-        <description>Opens the Hierarchy view for the selected element.</description>
-        <topic label="Using the Hierarchy view" href="tasks/tasks-37.htm"/>
-        <topic label="Changing the appearance of the Hierarchy view" href="tasks/tasks-38.htm"/>
-        <topic label="Opening a type hierarchy on a Java element" href="tasks/tasks-39.htm"/>
-        <topic label="Opening a type hierarchy on the current text selection" href="tasks/tasks-40.htm"/>
-        <topic label="Type Hierarchy view" href="reference/ref-type-hierarchy.htm"/>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <!-- Dialogs -->
-    <context id="maintype_selection_dialog_context">
-        <description>Choose a type from all types defining a main method.</description>
-        <topic label="Launching a Java program" href="tasks/tasks-130.htm"/>
-        <topic label="Defining the JAR file&apos;s manifest" href="tasks/tasks-35.htm"/>
-    </context>
-
-    <context id="open_type_dialog_context">
-        <description>This dialog allows you to choose a type from the workspace.</description>
-        <topic label="Open Type Dialog" href="reference/ref-148.htm"/>
-        <topic label="Opening on a Type" href="tasks/tasks-76.htm"/>
-        <topic label="Open Type" href="reference/ref-148.htm"/>
-        <topic label="Type Hierarchy view" href="reference/ref-type-hierarchy.htm"/>
-        <topic label="Java Actions" href="reference/ref-3.htm"/>
-    </context>
-
-    <context id="edit_jre_dialog_context">
-        <description>Edit an existing JRE definition.</description>
-        <topic label="Choosing a JRE for Launching a Project" href="tasks/tasks-124.htm"/>
-        <topic label="Working with JREs" href="tasks/tasks-JREs.htm"/>
-        <topic label="Working with Build Paths" href="tasks/tasks-110.htm"/>
-        <topic label="Building" href="concepts/concepts-4.htm"/>
-        <topic label="JRE Installations Preferences" href="reference/ref-19.htm"/>
-    </context>
-
-    <context id="source_attachment_dialog_context">
-        <description>Attach source code to the selected JAR file.</description>
-        <topic label="Attaching Source to a JAR File" href="tasks/tasks-115.htm"/>
-        <topic label="Working with Build Paths" href="tasks/tasks-110.htm"/>
-        <topic label="JRE Installations Preferences" href="reference/ref-19.htm"/>
-    </context>
-
-    <context id="variable_selection_dialog_context">
-        <description>Select a classpath variable to be added to the build class path.</description>
-        <topic label="Adding a Variable Class Path Entry" href="tasks/tasks-114.htm"/>
-        <topic label="Working with Build Paths" href="tasks/tasks-110.htm"/>
-        <topic label="Classpath Variables Preferences" href="reference/ref-15.htm"/>
-        <topic label="Classpath Variables Concepts" href="concepts/cclsspthv.htm"/>
-    </context>
-
-    <context id="variable_creation_dialog_context">
-        <description>Define a new classpath variable.</description>
-        <topic label="Defining a Class Path Variable" href="tasks/tasks-117.htm"/>
-        <topic label="Working with Build Paths" href="tasks/tasks-110.htm"/>
-        <topic label="Classpath Variables Preferences" href="reference/ref-15.htm"/>
-        <topic label="Classpath Variables Concepts" href="concepts/cclsspthv.htm"/>
-    </context>
-
-    <context id="advanced_dialog_context">
-        <description>A dialog for adding the listed entries to the class path.</description>
-        <topic label="Adding a library folder to the build path" href="tasks/tasks-112.htm"/>
-        <topic label="Build classpath" href="concepts/cbuildcp.htm"/>
-    </context>
-
-    <context id="confirm_save_modified_resources_dialog_context">
-        <description>Confirm that you want to save the modifed resource.</description>
-        
-    </context>
-
-    <context id="new_variable_dialog_context">
-        <description>A dialog for adding class path variables to the class path.</description>
-        <topic label="Viewing and editing a project&apos;s build path" href="tasks/tasks-111.htm"/>
-        <topic label="Adding a variable class path entry" href="tasks/tasks-114.htm"/>
-        <topic label="Attaching source to variables" href="tasks/tasks-116.htm"/>
-        <topic label="Attaching source to a classpath variable" href="tasks/tasks-116.htm"/>
-        <topic label="Defining a class path variable" href="tasks/tasks-117.htm"/>
-        <topic label="Deleting a class path variable" href="tasks/tasks-118.htm"/>
-        <topic label="Classpath Variables Preferences" href="reference/ref-15.htm"/>
-        <topic label="Classpath Variables Concepts" href="concepts/cclsspthv.htm"/>
-    </context>
-
-    <context id="nonnls_dialog_context">
-        <description>Lists all locations of strings that are not externalized.</description>
-        <topic label="String externalization" href="concepts/cnls.htm"/>
-        <topic label="Finding strings to externalize" href="tasks/tasks-188.htm"/>
-        <topic label="Using the Externalize Strings wizard" href="tasks/tasks-180.htm"/>
-        <topic label="Externalize Strings Wizard" href="reference/ref-wizard-externalize-strings.htm"/>
-        <topic label="Externalize Strings Concepts" href="concepts/cnls.htm"/>
-    </context>
-
-    <context id="multi_main_type_selection_dialog_context">
-        <description>Lists all classes with a main method.</description>
-        <topic label="Launching a Java program" href="tasks/tasks-130.htm"/>
-        <topic label="Defining the JAR file&apos;s manifest" href="tasks/tasks-35.htm"/>
-    </context>
-
-    <context id="multi_type_selection_dialog_context">
-        <description>A dialog for selecting one or more types from a list of types.</description>
-        <topic label="Opening a type in the Package Explorer view" href="tasks/tasks-75.htm"/>
-        <topic label="Opening an editor on a type" href="tasks/tasks-76.htm"/>
-    </context>
-
-    <context id="super_interface_selection_dialog_context">
-        <description>A dialog for selecting a super interface from a displayed list.</description>
-        <topic label="Creating a new Java class" href="tasks/tasks-17.htm"/>
-        <topic label="Creating a new Java interface" href="tasks/tasks-21.htm"/>
-        <topic label="New Java Class Wizard" href="reference/ref-126.htm"/>
-        <topic label="New Java Interface Wizard" href="reference/ref-127.htm"/>
-    </context>
-
-    <context id="override_tree_selection_dialog_context">
-        <description>A dialog where you can mark all methods that should be overridden.</description>
-        <topic label="Finding overridden methods" href="tasks/tasks-44.htm"/>
-        <topic label="Source Actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="move_destination_dialog_context">
-        <description>A dialog for selecting the move destination of an element.</description>
-        <topic label="Copying and moving Java elements" href="tasks/tasks-85.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-    </context>
-
-    <context id="choose_variable_dialog_context">
-        <description>A dialog for selecting template variables from a displayed list.</description>
-        <topic label="Templates" href="concepts/ctemplates.htm"/>
-        <topic label="Writing your own templates" href="tasks/tasks-203.htm"/>
-        <topic label="Templates Preferences" href="reference/ref-preferences-templates.htm"/>
-        <topic label="Templates Concepts" href="concepts/ctemplates.htm"/>
-    </context>
-
-    <context id="edit_template_dialog_context">
-        <description>A dialog for editing a template.</description>
-        <topic label="Templates" href="concepts/ctemplates.htm"/>
-        <topic label="Writing your own templates" href="tasks/tasks-203.htm"/>
-        <topic label="Templates Preferences" href="reference/ref-preferences-templates.htm"/>
-        <topic label="Templates Concepts" href="concepts/ctemplates.htm"/>
-    </context>
-
-    <context id="history_list_dialog_context">
-        <description>A dialog for re-opening previously opened type hierarchies.</description>
-        <topic label="Changing the appearance of the Hierarchy view" href="tasks/tasks-38.htm"/>
-        <topic label="Opening a type hierarchy on a Java element" href="tasks/tasks-39.htm"/>
-        <topic label="Opening a type hierarchy on the current text selection" href="tasks/tasks-40.htm"/>
-        <topic label="Opening a type hierarchy in its own perspective" href="tasks/tasks-42.htm"/>
-        <topic label="Finding overridden methods" href="tasks/tasks-44.htm"/>
-        <topic label="Type Hierarchy View" href="reference/ref-type-hierarchy.htm"/>
-    </context>
-
-    <context id="import_organize_input_dialog_context">
-        <description>A dialog for adding a new package to the Organize Imports preferences page.</description>
-        <topic label="Adding required import statements" href="tasks/tasks-59.htm"/>
-        <topic label="Organizing existing import statements" href="tasks/tasks-60.htm"/>
-        <topic label="Setting the order of import statements" href="tasks/tasks-61.htm"/>
-        <topic label="Organize Imports Preferences" href="reference/ref-22.htm"/>
-        <topic label="Source Actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="javadoc_property_dialog_context">
-        <description>A dialog where you can specify the Javadoc location for a selected jar file.</description>
-        <topic label="Javadoc Location Properties" href="reference/ref-dialog-javadoc-location.htm"/>
-        <topic label="Creating Javadoc documentation" href="tasks/tasks-196.htm"/>
-    </context>
-
-    <context id="new_container_dialog_context">
-        <description>A dialog where you can specify a new source folder.</description>
-        <topic label="Build classpath" href="concepts/cbuildcp.htm"/>
-        <topic label="Creating a new source folder" href="tasks/tasks-26.htm"/>
-		<topic label="Creating a new source folder with exclusion filter" href="tasks/tasks-221.htm"/>
-		<topic label="Creating a new source folder with specific output folder" href="tasks/tasks-222.htm"/>
-        <topic label="Adding a library folder to the build path" href="tasks/tasks-112.htm"/>
-    </context>
-
-    <context id="nls_search_page_context">
-        <description>A dialog where you can select options for searching the specifics of string externalizations.</description>
-        <topic label="String externalization" href="concepts/cnls.htm"/>
-        <topic label="Finding unused and incorrectly used keys in property files" href="tasks/tasks-202.htm"/>
-    </context>
-
-    <context id="java_editor_context">
-        <description>The Java editor provides you with Java specific text editing support.</description>
-        <topic label="Java editor concepts" href="concepts/concepts-7.htm"/>
-        <topic label="Using the Java editor" href="tasks/tasks-54.htm"/>
-        <topic label="Java editor reference" href="reference/ref-java-editor.htm"/>
-        <topic label="Opening a Java editor" href="gettingStarted/qs-OpenJavaEditor.htm"/>
-        <topic label="Using content assist" href="gettingStarted/qs-ContentAssist.htm"/>
-        <topic label="Identifying problems in your code" href="gettingStarted/qs-7.htm"/>
-        <topic label="Using code templates" href="gettingStarted/qs-EditorTemplates.htm"/>
-        <topic label="Organizing import statements" href="gettingStarted/qs-OrganizeImports.htm"/>
-        <topic label="Java editor preferences" href="reference/ref-21.htm"/>
-    </context>
-
-    <context id="compare_dialog_context">
-        <description>A dialog displaying the results of comparing Java elements.</description>
-    </context>
-
-    <context id="add_element_from_history_dialog_context">
-        <description>A dialog that lets you restore deleted Java elements from the local history.</description>
-        <topic label="Restoring a deleted workbench element" href="tasks/tasks-64.htm"/>
-        <topic label="Using the local history" href="tasks/tasks-62.htm"/>
-    </context>
-
-    <context id="compare_element_with_history_dialog_context">
-        <description>A dialog that lets you compare a Java element with entries from the local history.</description>
-        <topic label="Comparing a Java element with a local history edition" href="tasks/tasks-63a.htm"/>
-        <topic label="Using the local history" href="tasks/tasks-62.htm"/>
-    </context>
-
-    <context id="replace_element_with_history_dialog_context">
-        <description>A dialog that lets you replace Java elements with entries from the local history.</description>
-        <topic label="Replacing a Java element with a local history edition" href="tasks/tasks-63.htm"/>
-        <topic label="Using the local history" href="tasks/tasks-62.htm"/>
-    </context>
-
-    <!-- View parts -->
-
-    <context id="package_view_context" title="About Package Explorer">
-        <description>This view displays the workspace&apos;s Java projects and lets you explore their contents.</description>
-        <topic label="Browsing Java elements" href="gettingStarted/qs-4.htm"/>
-        <topic label="Java views" href="concepts/concepts-6.htm"/>
-        <topic label="Package explorer view" href="reference/ref-view-package-explorer.htm"/>
-        <topic label="Java element filters dialog" href="reference/ref-dialog-java-element-filters.htm"/>
-    </context>
-    
-    <context id="type_hierarchy_view_context" title="About Hierarchy view">
-        <description>This view displays a type&apos;s hierarchy.</description>
-        <topic label="Using the Hierarchy view" href="tasks/tasks-37.htm"/>
-        <topic label="Type Hierarchy View" href="reference/ref-type-hierarchy.htm"/>
-        <topic label="Viewing the Type Hierarchy" href="gettingStarted/qs-6.htm"/>
-        <topic label="Java Views" href="concepts/concepts-6.htm"/>
-    </context>
-
-    <context id="projects_view_context" title="About Projects view">
-        <description>Displays all Java projects according to the current filter settings.</description>
-        <topic label="Java views" href="concepts/concepts-6.htm"/>
-    </context>
-
-    <context id="packages_browsing_view_context" title="About Packages view">
-        <description>Displays all packages of the selected Java project according to the current filter settings.</description>
-        <topic label="Java views" href="concepts/concepts-6.htm"/>
-    </context>
-
-    <context id="types_view_context" title="About Types view">
-        <description>Displays all types of the selected package according to the current filter settings.</description>
-        <topic label="Java views" href="concepts/concepts-6.htm"/>
-    </context>
-
-    <context id="members_view_context" title="About Members view">
-        <description>Displays all members of the selected type according to the current filter settings.</description>
-        <topic label="Java views" href="concepts/concepts-6.htm"/>
-    </context>
-    
-    <context id="call_hierarchy_view_context" title="About Call Hierarchy view">
-        <description>The Call Hierarchy shows all callers or callees of the given method.</description>
-        <topic label="Java views" href="concepts/concepts-6.htm"/>
-    </context>
-    
-    <context id="javadoc_view_context" title="About Javadoc view">
-        <description>Displays the Javadoc for the selected Java element.</description>
-        <topic label="Java views" href="concepts/concepts-6.htm"/>
-    </context>
-    
-    <context id="source_view_context" title="About Declarations view">
-        <description>Displays the source for the selected Java element.</description>
-        <topic label="Java views" href="concepts/concepts-6.htm"/>
-    </context>
-
-
-
-    <!-- Preference pages -->
-
-    <context id="build_path_property_page_context">
-        <description>This page is where you can define the project&apos;s build path.</description>
-        <topic label="Viewing and Editing a Project&apos;s Build Path" href="tasks/tasks-111.htm"/>
-        <topic label="Building" href="concepts/concepts-4.htm"/>
-        <topic label="Java Settings Page" href="reference/ref-123.htm"/>
-    </context>
-
-    <context id="cp_variables_preference_page_context">
-        <description>This page is where you can create and manage classpath variables for the workbench.</description>
-        <topic label="Classpath Variables Preferences" href="reference/ref-15.htm"/>
-        <topic label="Adding a Variable Class Path Entry" href="tasks/tasks-114.htm"/>
-        <topic label="Deleting a Class Path Variable" href="tasks/tasks-118.htm"/>
-        <topic label="Classpath Variables" href="concepts/cclsspthv.htm"/>
-        <topic label="Installed JREs" href="reference/ref-18.htm"/>
-    </context>
-
-    <context id="codeformatter_preference_page_context">
-        <description>This page is where you can set preferences for formatting Java code.</description>
-        <topic label="Code Formatter Preferences" href="reference/ref-17.htm"/>
-        <topic label="Formatting Java Code" href="tasks/tasks-66.htm"/>
-    </context>
-
-    <context id="source_attachment_property_page_context">
-        <description>This page is where you can attach source code to a JAR file.</description>
-        <topic label="Source Attachment Properties" href="reference/ref-124.htm"/>
-        <topic label="Attaching Source to a JAR File" href="tasks/tasks-115.htm"/>
-        <topic label="Attaching Source to a Classpath Variable" href="tasks/tasks-116.htm"/>
-    </context>
-
-    <context id="jre_preference_page_context">
-        <description>This page is where you can add, remove, and edit JREs install definitions.</description>
-        <topic label="JRE Installations Preferences" href="reference/ref-19.htm"/>
-        <topic label="Working with JREs" href="tasks/tasks-JREs.htm"/>
-        <topic label="Choosing a JRE for Launching a Project" href="tasks/tasks-124.htm"/>
-        <topic label="Preparing the Workbench" href="gettingStarted/qs-2.htm"/>
-    </context>
-
-    <context id="source_lookup_property_page_context">
-        <description>When debugging the projects specified on this page are used to look up a type&apos;s source.</description>
-    </context>
-
-    <context id="launch_jre_property_page_context">
-        <description>Select the JRE to be used when launching from this project. This option should only be used when this project&apos;s JRE is different from the default JRE selected in the preferences.</description>
-        <topic label="Choosing a JRE for Launching a Project" href="tasks/tasks-124.htm"/>
-        <topic label="Working with JREs" href="tasks/tasks-JREs.htm"/>
-        <topic label="JRE Installations Preferences" href="reference/ref-19.htm"/>
-    </context>
-
-    <context id="code_manipulation_preference_context">
-        <description>Specify the behavior of all code generation actions.</description>
-        <topic label="Code Style Preferences" href="reference/ref-preferences-code-generation.htm"/>
-        <topic label="Code Template Preferences" href="reference/ref-preferences-code-templates.htm"/>
-        <topic label="Generating getters and setters" href="tasks/tasks-57.htm"/>
-    </context>
-
-    <context id="compiler_preference_page_context">
-        <description>Specify the behavior of the JDT Java compiler.</description>
-        <topic label="Java Compiler Preferences" href="reference/ref-preferences-compiler.htm"/>
-        <topic label="Java Builder" href="concepts/concepts-4.htm"/>
-        <topic label="Building a Java program" href="tasks/tasks-106.htm"/>
-    </context>
-
-    <context id="template_preference_page_context">
-        <description>Define and manage your code templates.</description>
-        <topic label="Java Templates Preferences" href="reference/ref-preferences-templates.htm"/>
-        <topic label="Using templates" href="tasks/tasks-171.htm"/>
-        <topic label="Writing your own templates" href="tasks/tasks-203.htm"/>
-        <topic label="Templates Concepts" href="concepts/ctemplates.htm"/>
-    </context>
-
-    <context id="new_java_project_preference_page_context">
-        <description>Specify the path for the application for generating Javadoc.</description>
-        <topic label="Creating a new Java project" href="tasks/tasks-12.htm"/>
-        <topic label="Creating a Java project as its own source container" href="tasks/tasks-13.htm"/>
-        <topic label="Creating a Java project with source folders" href="tasks/tasks-14.htm"/>
-		<topic label="Creating a new source folder with exclusion filter" href="tasks/tasks-221.htm"/>
-		<topic label="Creating a new source folder with specific output folder" href="tasks/tasks-222.htm"/>
-        <topic label="Java Projects" href="concepts/concepts-3.htm"/>
-    </context>
-
-    <context id="java_element_info_page_context">
-        <description>Displays file system information about the selected Java element.</description>
-        
-    </context>
-
-
-    <!-- Wizard pages -->
-
-    <context id="new_javaproject_wizard_page_context">
-        <description>This wizard helps you create a new Java project.</description>
-        <topic label="Java projects" href="concepts/concepts-3.htm"/>
-        <topic label="Creating a Java project as its own source container" href="tasks/tasks-13.htm"/>
-        <topic label="Creating a Java project with source folders" href="tasks/tasks-14.htm"/>
-		<topic label="Creating a new source folder with exclusion filter" href="tasks/tasks-221.htm"/>
-		<topic label="Creating a new source folder with specific output folder" href="tasks/tasks-222.htm"/>
-        <topic label="Creating your first Java project" href="gettingStarted/qs-3.htm"/>
-        <topic label="New Java Project Wizard" href="reference/ref-121.htm"/>
-    </context>
-    <context id="new_snippet_wizard_page_context">
-        <description>This wizard helps you create a new Java scrapbook page.</description>
-        <topic label="Creating a scrapbook page" href="tasks/tasks-149.htm"/>
-        <topic label="New Java Scrapbook Page Wizard" href="reference/ref-129.htm"/>
-    </context>
-    <context id="new_package_wizard_page_context">
-        <description>This wizard helps you create a new Java package.</description>
-        <topic label="Creating a new Java package" href="tasks/tasks-15.htm"/>
-        <topic label="New Java Package Wizard" href="reference/ref-125.htm"/>
-    </context>
-    <context id="new_class_wizard_page_context">
-        <description>This wizard helps you create a new Java class.</description>
-        <topic label="Creating a top-level class" href="tasks/tasks-18.htm"/>
-        <topic label="Creating a nested class" href="tasks/tasks-19.htm"/>
-        <topic label="Creating a class in an existing compilation unit" href="tasks/tasks-20.htm"/>
-        <topic label="New Java Class Wizard" href="reference/ref-126.htm"/>
-    </context>
-    <context id="new_enum_wizard_page_context">
-        <description>This wizard helps you create a new Java enum.</description>
-        <topic label="Creating a new Java enum" href="tasks/tasks-17b.htm"/>
-        <topic label="New Java Enum Wizard" href="reference/ref-126b.htm"/>
-    </context>
-    <context id="new_interface_wizard_page_context">
-        <description>This wizard helps you create a new Java interface.</description>
-        <topic label="Creating a top-level interface" href="tasks/tasks-23.htm"/>
-        <topic label="Creating a nested interface" href="tasks/tasks-24.htm"/>
-        <topic label="Creating a new interface in an existing compilation unit" href="tasks/tasks-25.htm"/>
-        <topic label="New Java Interface Wizard" href="reference/ref-127.htm"/>
-    </context>
-    <context id="new_annotation_wizard_page_context">
-        <description>This wizard helps you create a new Java annotation.</description>
-        <topic label="Creating a new Java annotation" href="tasks/tasks-21b.htm"/>
-        <topic label="New Java Annotation Wizard" href="reference/ref-127b.htm"/>
-    </context>
-
-    <context id="new_packageroot_wizard_page_context">
-        <description>This wizard helps you create a new Java source folder.</description>
-        <topic label="Creating a new Java project" href="tasks/tasks-12.htm"/>
-        <topic label="Creating a new source folder" href="tasks/tasks-26.htm"/>
-		<topic label="Creating a new source folder with exclusion filter" href="tasks/tasks-221.htm"/>
-		<topic label="Creating a new source folder with specific output folder" href="tasks/tasks-222.htm"/>
-        <topic label="New Source Folder Wizard" href="reference/ref-128.htm"/>
-    </context>
-    
-    <context id="edit_inclusion_exlusion_filter_wizard_page_context">
-        <description>This wizard helps you to add or remove Inclusion and Exclusion filters to a source folder.</description>
-        <topic label="Inclusion and Exclusion filters" href="concepts/filters.htm"/>
-    </context>
-
-    <context id="java_application_page_context">
-        <description>This wizard displays a list of launchable elements where you can select an element to be launched.</description>
-        <topic label="Running a Java program" href="tasks/tasks-130.htm"/>
-        <topic label="Run and Debug Actions" href="reference/ref-4.htm"/>
-    </context>
-
-    <context id="jdi_attach_launcher_page_context">
-        <description>This wizard helps you configure the settings for launching a remote Java application.</description>
-        <topic label="Connecting to a remote VM with the Remote Java application launch configuration" href="tasks/tasks-141.htm"/>
-        <topic label="Run and Debug Actions" href="reference/ref-4.htm"/>
-    </context>
-
-    <context id="jar_packager_wizard_page_context">
-        <description>This wizard helps you set packaging options for exporting resources to a JAR file.</description>
-        <topic label="Creating a new JAR file" href="tasks/tasks-33.htm"/>
-        <topic label="Creating JAR files" href="tasks/tasks-32.htm"/>
-        <topic label="Export JAR Wizard" href="reference/ref-export-jar.htm"/>
-    </context>
-
-    <context id="jar_manifest_wizard_page_context">
-        <description>This wizard helps you create or locate the manifest file for the created JAR file.</description>
-        <topic label="Defining the JAR File&apos;s Manifest" href="tasks/tasks-35.htm"/>
-        <topic label="Creating JAR files" href="tasks/tasks-32.htm"/>
-        <topic label="Export JAR Wizard" href="reference/ref-export-jar.htm"/>
-    </context>
-
-    <context id="jar_options_wizard_page_context">
-        <description>This wizard helps you configure the settings for managing export problems. It includes the option to save a description of the JAR file in the workbench.</description>
-        <topic label="Setting advanced options" href="tasks/tasks-34.htm"/>
-        <topic label="Creating JAR files" href="tasks/tasks-32.htm"/>
-        <topic label="Export JAR Wizard" href="reference/ref-export-jar.htm"/>
-    </context>
-
-   <context  id="java_working_set_page_context" >
-      <description>Create a new working set by selecting the Java elements that will belong to it.</description>
-   </context>
-
-    <context id="classpath_container_default_page_context">
-        <description>Allows you to edit a container entry of the class path. A container entry has the format &quot;container name/container specific arguments&quot;.</description>
-        <topic label="Build classpath" href="concepts/cbuildcp.htm"/>
-        <topic label="Viewing and editing a project&apos;s build path" href="tasks/tasks-111.htm"/>
-        <topic label="Adding a library folder to the build path" href="tasks/tasks-112.htm"/>
-        <topic label="Adding a JAR file to the build path" href="tasks/tasks-113.htm"/>
-        <topic label="Adding a variable class path entry" href="tasks/tasks-114.htm"/>
-        <topic label="Attaching source to a JAR file" href="tasks/tasks-115.htm"/>
-        <topic label="Attaching source to variables" href="tasks/tasks-116.htm"/>
-        <topic label="Attaching source to a classpath variable" href="tasks/tasks-116.htm"/>
-        <topic label="Defining a class path variable" href="tasks/tasks-117.htm"/>
-        <topic label="Deleting a class path variable" href="tasks/tasks-118.htm"/>
-        <topic label="Java Build Path Properties" href="reference/ref-123.htm"/>
-        <topic label="Classpath Variables Preferences" href="reference/ref-15.htm"/>
-    </context>
-    
-    <context id="select_clean_ups_wizard_page_context">
-        <description>This wizard helps you to clean up your code.</description>
-        <topic label="Code Clean Up" href="tasks/tasks-233.htm"/>
-        <topic label="The Clean Up Wizard" href="tasks/tasks-234.htm"/>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-    </context>
-
-    <context id="javadoc_standard_page_context">
-        <description>Allows you to select the options for generating Javadoc using the standard doclet.</description>
-        <topic label="Configuring Javadoc arguments for standard doclet" href="tasks/tasks-200.htm"/>
-        <topic label="Export Javadoc Wizard" href="reference/ref-export-javadoc.htm"/>
-    </context>
-
-    <context id="javadoc_specifics_page_context">
-        <description>Allows you to textually specify further arguments passed to the Javadoc generator.</description>
-        <topic label="Configuring Javadoc arguments" href="tasks/tasks-201.htm"/>
-        <topic label="Export Javadoc Wizard" href="reference/ref-export-javadoc.htm"/>
-    </context>
-
-    <context id="javadoc_tree_page_context">
-        <description>Select the elements for which Javadoc will be created.</description>
-        <topic label="Selecting types for Javadoc generation" href="tasks/tasks-199.htm"/>
-        <topic label="Export Javadoc Wizard" href="reference/ref-export-javadoc.htm"/>
-    </context>
-
-
-    <!-- Refactoring Preview Pages-->
-
-    <context id="refactoring_preview_wizard_page_context">
-        <description>This dialog presents a preview of the impending refactoring changes.</description>
-        <topic label="Previewing proposed refactoring changes" href="tasks/tasks-84.htm"/>
-        <topic label="Refactoring with preview" href="tasks/tasks-83.htm"/>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-	<!-- Refactoring Error Wizard Pages -->
-	
-    <context id="refactoring_error_wizard_page_context">
-        <description>Displays errors that occurred while executing the refactoring.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="rename_params_wizard_page">
-        <description>This dialog helps you rename a method parameter. References to the parameter inside the method are updated to refer to the new name.</description>
-        <topic label="Renaming method parameters" href="tasks/tasks-98.htm"/>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="extract_method_wizard_page_context">
-        <description>This dialog helps you extract the selected statements into a new method.</description>
-        <topic label="Extracting a method" href="tasks/tasks-87.htm"/>
-        <topic label="Opening a Java editor" href="gettingStarted/qs-OpenJavaEditor.htm"/>
-        <topic label="Adding new methods" href="gettingStarted/qs-AddMethod.htm"/>
-        <topic label="Using content assist" href="gettingStarted/qs-ContentAssist.htm"/>
-        <topic label="Identifying problems in your code" href="gettingStarted/qs-7.htm"/>
-        <topic label="Using code templates" href="gettingStarted/qs-EditorTemplates.htm"/>
-        <topic label="Organizing import statements" href="gettingStarted/qs-OrganizeImports.htm"/>
-        <topic label="Using the local history" href="gettingStarted/qs-LocalHistory.htm"/>
-        <topic label="Extracting a new method" href="gettingStarted/qs-ExtractMethod.htm"/>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="rename_package_wizard_page_context">
-        <description>This dialog helps you rename a Java package. References to the old package name are updated to refer to the new name.</description>
-        <topic label="Renaming a package" href="tasks/tasks-90.htm"/>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="rename_cu_wizard_page_context">
-        <description>This dialog helps you rename a compilation unit. References to the compilation unit&apos;s public type are updated to refer to the new name.</description>
-        <topic label="Renaming a compilation unit" href="tasks/tasks-92.htm"/>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="rename_method_wizard_page_context">
-        <description>This dialog helps you rename a method.</description>
-        <topic label="Renaming a method" href="tasks/tasks-96.htm"/>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="rename_type_wizard_page_context">
-        <description>This dialog helps you rename a type.</description>
-        <topic label="Renaming a type" href="tasks/tasks-94.htm"/>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="rename_field_wizard_page_context">
-        <description>This dialog helps you rename a field.</description>
-        <topic label="Renaming a field" href="tasks/tasks-169.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="externalize_wizard_keyvalue_page_context">
-        <description>Supports you in defining the keys for looking up externalized strings.</description>
-        <topic label="String externalization" href="concepts/cnls.htm"/>
-        <topic label="Key/value page" href="tasks/tasks-189.htm"/>
-        <topic label="Externalize strings wizard" href="reference/ref-wizard-externalize-strings.htm"/>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="externalize_wizard_properties_file_page_context">
-        <description>Supports you in specifying the properties file used to externalize strings.</description>
-        <topic label="String externalization" href="concepts/cnls.htm"/>
-        <topic label="Property file page" href="tasks/tasks-190.htm"/>
-        <topic label="Externalize strings wizard" href="reference/ref-wizard-externalize-strings.htm"/>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="extract_method_temp_page_context">
-        <description>This dialog helps you extract a local variable.</description>
-        <topic label="Extracting a local variable" href="tasks/tasks-159.htm"/>
-        <topic label="Parameters page" href="tasks/tasks-160.htm"/>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="modify_parameters_wizard_page_context">
-        <description>This dialog helps you modify the signature of a method.</description>
-        <topic label="Renaming method parameters" href="tasks/tasks-98.htm"/>
-        <topic label="Renaming method parameters - parameters page" href="tasks/tasks-99.htm"/>
-        <topic label="Changing method signature" href="tasks/tasks-157.htm"/>
-        <topic label="Changing method signature - parameters page" href="tasks/tasks-158.htm"/>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="move_members_wizard_page_context">
-        <description>This dialog helps you move static members from one type to another.</description>
-        <topic label="Moving static members between types" href="tasks/tasks-167.htm"/>
-        <topic label="Parameters page" href="tasks/tasks-168.htm"/>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="pull_up_wizard_page_context">
-        <description>This dialog helps you move members up the type hierarchy.</description>
-        <topic label="Pulling members up to superclass" href="tasks/tasks-165.htm"/>
-        <topic label="Parameters page" href="tasks/tasks-166.htm"/>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="rename_local_variable_wizard_page_context">
-        <description>This dialog helps you rename a local variable.</description>
-        <topic label="Renaming a local variable" href="tasks/tasks-204.htm"/>
-        <topic label="Parameters page" href="tasks/tasks-205.htm"/>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="self_encapsulate_field_wizard_page_context">
-        <description>This dialog helps you insert calls to setter and getter methods at all locations where the selected field is set or read.</description>
-        <topic label="Self encapsulating a field" href="tasks/tasks-162.htm"/>
-        <topic label="Parameters page" href="tasks/tasks-163.htm"/>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <!-- Reused UI Blocks -->
-
-    <context id="build_paths_context">
-        <description>A page for defining the build classpath for the project.</description>
-        <topic label="Build class path" href="concepts/concepts-4.htm"/>
-        <topic label="Viewing and editing a project&apos;s build path" href="tasks/tasks-111.htm"/>
-        <topic label="Preparing the workbench" href="gettingStarted/qs-2.htm"/>
-        <topic label="Java build path properties" href="reference/ref-123.htm"/>
-        <topic label="Classpath variables preferences" href="reference/ref-15.htm"/>
-    </context>
-    <context id="source_attachment_context">
-        <description>Allows you to attach a source code archive to a JAR file.</description>
-        <topic label="Build class path" href="concepts/concepts-4.htm"/>
-        <topic label="Attaching source to a JAR file" href="tasks/tasks-115.htm"/>
-        <topic label="Attaching source to a classpath variable" href="tasks/tasks-116.htm"/>
-        <topic label="Attaching source to JAR files and variables" href="reference/ref-124.htm"/>
-    </context>
-
-
-    <!-- Preference pages -->
-
-    <context id="organizeimports_preference_page_context">
-        <description>On this page you can define the sort order of import statements.</description>
-        <topic label="Organize imports preferences" href="reference/ref-22.htm"/>
-        <topic label="Adding required import statements" href="tasks/tasks-59.htm"/>
-        <topic label="Organizing existing import statements" href="tasks/tasks-60.htm"/>
-        <topic label="Setting the order of import statements" href="tasks/tasks-61.htm"/>
-    </context>
-
-    <context id="java_base_preference_page_context">
-        <description>On this page you can indicate your preferences for the general Java tooling settings.</description>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="refactoring_preference_page_context">
-        <description>On this page you can indicate your preferences when performing a refactoring.</description>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactoring reference" href="reference/ref-115.htm"/>
-        <topic label="Refactoring tasks" href="tasks/tasks-80.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="java_editor_preference_page_context">
-        <description>On this page you can indicate your preferences for using the Java editor.</description>
-        <topic label="Java editor preferences" href="reference/ref-21.htm"/>
-        <topic label="Java editor concepts" href="concepts/concepts-7.htm"/>
-        <topic label="Java editor reference" href="reference/ref-java-editor.htm"/>
-        <topic label="Using the Java editor" href="tasks/tasks-54.htm"/>
-    </context>
-
-
-    <!-- Search -->
-
-    <context id="java_search_page_context">
-        <description>On this page you can search for references to and declarations of Java elements.</description>
-        <topic label="Java Searching" href="concepts/concepts-8.htm"/>
-        <topic label="Searching the workbench" href="gettingStarted/qs-11.htm"/>
-        <topic label="Conducting a Java search using the search dialog" href="tasks/tasks-103.htm"/>
-        <topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"/>
-        <topic label="Java search tab" href="reference/ref-131.htm"/>
-        <topic label="Search menu" href="reference/ref-menu-search.htm"/>
-    </context>
-
-
-    <!-- Custom Filters -->
-
-    <context id="open_custom_filters_dialog_context">
-        <description>On this page you can activate and deactivate filters.</description>
-        <topic label="Filtering elements" href="tasks/tasks-47.htm"/>
-        <topic label="Showing and hiding system files" href="tasks/tasks-3.htm"/>
-        <topic label="Showing and hiding CLASS files generated for inner" href="tasks/tasks-4.htm"/>
-        <topic label="Showing and hiding libraries" href="tasks/tasks-5.htm"/>
-        <topic label="Showing and hiding empty packages " href="tasks/tasks-183.htm"/>
-        <topic label="Showing and hiding empty parent packages " href="tasks/tasks-184.htm"/>
-        <topic label="Showing and hiding Java files " href="tasks/tasks-185.htm"/>
-        <topic label="Showing and hiding non-Java elements" href="tasks/tasks-186.htm"/>
-    </context>
-
-
-    <!-- NEW CONTEXT IDs -->
-
-    <context id="sort_members_action">
-        <description>This command sorts the members in this compilation unit.</description>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="quick_fix_action">
-        <description>This command helps you to correct Java problems.</description>
-        <topic label="Edit actions" href="reference/ref-menu-edit.htm"/>
-    </context>
-
-    <context id="format_action">
-        <description>This command formats the selected text.</description>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="add_delegate_methods_action">
-        <description>This command lets you create delegate methods for a set of fields.(Delegate methods are methods that delegate to a method provided by a field.)</description>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="history_action">
-        <description>This action is used to switch between previously displayed type hierarchies.</description>
-        <topic label="Type Hierarchy view" href="reference/ref-type-hierarchy.htm"/>
-    </context>
-
-    <context id="go_into_top_level_type_action">
-        <description>This command modifies the Java outline view to show only the members of the compilation unit's main type.</description>
-    </context>
-
-    <context id="tasktags_property_page_context">
-        <description>This page is where you can define the project-specific task tags.</description>
-    </context>
-
-    <context id="compiler_property_page_context">
-        <description>This page is where you can define the project-specific compiler settings.</description>
-    </context>
-
-    <context id="replace_with_previous_from_history_action">
-        <description>This command lets you replace the selected element with a version from the local history.</description>
-        <topic label="Using the local history" href="tasks/tasks-62.htm"/>
-    </context>
-
-    <context id="compare_with_history_action">
-        <description>This command lets you compare the selected element with a version from the local history.</description>        
-        <topic label="Using the local history" href="tasks/tasks-62.htm"/>
-    </context>
-
-    <context id="add_from_history_action">
-        <description>This command adds elements from the local history.</description>
-        <topic label="Using the local history" href="tasks/tasks-62.htm"/>
-    </context>
-
-    <context id="replace_with_history_action">
-        <description>This command replaces the selected element with a version from the local history.</description>
-        <topic label="Using the local history" href="tasks/tasks-62.htm"/>
-    </context>
-
-    <context id="comment_action">
-        <description>This command lets you comment out a sequence of lines in Java code.</description>        
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="uncomment_action">
-        <description>This command uncomments a sequence of lines that are commented out.</description>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="extract_temp_page_context">
-        <description>This dialog helps you to extract a local variable from a selected expression.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="previous_problem_action">
-        <description>This command navigates to the previous problem in the active editor.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="sort_order_preference_page_context">
-        <description>On this page you can indicate your preferences for sorting elements in views.  The same settings are also used by the Sort Members command.</description>
-        <topic label="Sorting elements in Java views" href="tasks/tasks-195.htm"/>
-    </context>
-
-    <context id="tasktags_preference_page_context">
-        <description>On this page you can create new tags (e.g. TODO, FIXME) for which task markers will be created.</description>
-    </context>
-
-    <context id="appearance_preference_page_context">
-        <description>On this page you can indicate your preferences for the appearence of Java views.</description>
-    </context>
-
-    <context id="addjtoclasspath_action_context">
-        <description>This command adds the selected JAR to the project's classpath.</description>
-        <topic label="Build classpath" href="concepts/cbuildcp.htm"/>
-    </context>
-
-    <context id="removefromclasspath_action_context">
-        <description>This command removes an entry from the project's classpath.</description>        
-        <topic label="Build classpath" href="concepts/cbuildcp.htm"/>
-    </context>
-
-    <context id="push_down_action">
-        <description>This command opens a dialog that will help you to push down members of a class to the class's subclasses.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="inline_method_wizard_page_context">
-        <description>This dialog helps you to inline a method.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="move_action">
-        <description>This command moves elements.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="next_change_action">
-        <description>This command navigates to the next change.</description>
-    </context>
-
-    <context id="previous_change_action">
-        <description>This command navigates to the previous change.</description>
-    </context>
-
-    <context id="goto_next_member_action">
-        <description>This command moves the caret to the next member.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="goto_previous_member_action">
-        <description>This command moves the caret to the previous member.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="show_qualified_names_action">
-        <description>This command shows the qualified names for types.</description>
-        <topic label="Type Hierarchy view" href="reference/ref-type-hierarchy.htm"/>
-    </context>
-
-    <context id="open_structure_action">
-        <description>This command opens the outline of the selected element.</description>
-    </context>
-
-    <context id="inline_action">
-        <description>This command opens a dialog that will help you to inline a method, local variable or constant.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="extract_interface_action">
-        <description>This command opens a dialog that will help you to extract an interface from the selected type.  You can optionally change references to the selected type into references to the new interface.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="promote_temp_to_field_page_context">
-        <description>This dialog helps you convert a local variable to a field.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="move_inner_to_top_level_action">
-        <description>This command opens a dialog that will help you to convert a nested type to a top level type.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="use_supertype_wizard_page_context">
-        <description>This dialog helps you to replace references to a type with references to one of the type's supertypes.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="parameter_hints_action">
-        <description>This command shows hints for method call parameters.</description>
-        <topic label="Edit actions" href="reference/ref-menu-edit.htm"/>
-    </context>
-
-    <context id="convert_anonymous_to_nested_action">
-        <description>This command opens a dialog that will help you to convert an anonymous inner class to a nested class.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="goto_resource_dialog">
-        <description>This dialog helps you to find and navigate to a workspace resource.</description>
-    </context>
-
-    <context id="extract_constant_page_context">
-        <description>This dialog helps you to extract a selected expression to a constant.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="extract_constant_action">
-        <description>This command opens a dialog that will help you to extract a constant from the selected expression.  You can optionally replace all matching expressions with references to the new constant.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="link_editor_action">
-        <description>This command links the view with an editor.</description>
-        <topic label="Java views" href="concepts/concepts-6.htm"/>
-    </context>
-
-    <context id="use_supertype_action">
-        <description>This command opens a dialog that will help you to replace references to a type with references to one of the type's supertypes.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="inline_constant_wizard_page_context">
-        <description>This dialog helps you to inline a constant.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="goto_matching_bracket_action">
-        <description>This command moves the caret to the matching bracket.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="goto_type_action">
-        <description>This command finds a selected type in the workspace and opens its code in the editor.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="java_select_marker_ruler_action">
-        <description>This command activates Quick Fix.</description>
-        <topic label="Edit actions" href="reference/ref-menu-edit.htm"/>
-    </context>
-
-    <context id="show_outline_action">
-        <description>This command shows an in-place outline of the currently edited file.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="goto_resource_action">
-        <description>This command finds and navigates to a selected resource in the workspace.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="convert_anonymous_to_nested_page_context">
-        <description>This dialog helps you to convert an anonymous inner class to a nested class.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="next_problem_action">
-        <description>This command navigates to the next problem in the Java editor.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="content_assist_action">
-        <description>This command opens content assist.</description>
-        <topic label="Edit actions" href="reference/ref-menu-edit.htm"/>
-    </context>
-
-    <context id="layout_flat_action">
-        <description>This command changes the view to a flat layout.</description>
-        <topic label="Package Explorer view" href="reference/ref-view-package-explorer.htm"/>
-        <topic label="Java views" href="concepts/concepts-6.htm"/>
-    </context>
-
-    <context id="layout_hierarchical_action">
-        <description>This command changes the view to a hierarchical layout.</description>
-        <topic label="Package Explorer view" href="reference/ref-view-package-explorer.htm"/>
-        <topic label="Java views" href="concepts/concepts-6.htm"/>
-    </context>
-
-    <context id="show_javadoc_action">
-        <description>This command shows Javadoc for the selected element.</description>
-        <topic label="Javadoc location" href="reference/ref-dialog-javadoc-location.htm"/>
-    </context>
-
-    <context id="output_location_dialog_context">
-        <description>This dialog helps you to edit the output folder of a project or a source folder.</description>
-        <topic label="Build classpath" href="concepts/cbuildcp.htm"/>
-        <topic label="Java Settings Page" href="reference/ref-123.htm"/>
-    </context>
-
-    <context id="sort_by_defining_type_action">
-        <description>This command sorts the members by their declaring type.</description>
-        <topic label="Type Hierarchy view" href="reference/ref-type-hierarchy.htm"/>
-    </context>
-
-    <context id="edit_working_set_action">
-        <description>This command lets you edit a working set.</description>
-    </context>
-
-    <context id="move_inner_to_top_wizard_page_context">
-        <description>This dialog helps you to convert a nested type to a top level type.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="push_down_wizard_page_context">
-        <description>This dialog helps you to push down class members to their subclasses.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="promote_temp_to_field_action">
-        <description>This command opens a dialog that will help you to convert a local variable to a field.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="exclusion_pattern_dialog_context">
-        <description>This dialog excludes selected source files within a source folder from being compiled.</description>
-        <topic label="Build classpath" href="concepts/cbuildcp.htm"/>
-        <topic label="Java Settings Page" href="reference/ref-123.htm"/>
-    </context>
-
-    <context id="extract_interface_temp_page_context">
-        <description>This dialog helps you to extract an interface from a type.  You can optionally change references to the type into references to the new interface.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-117.htm"/>
-        <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/ref-13.htm"/>
-    </context>
-
-    <context id="select_all_action">
-        <description>This command selects all elements in the active view.</description>
-        <topic label="Java views" href="concepts/concepts-6.htm"/>
-    </context>
-    
-    <context id="generate_javadoc_action">
-        <description>This command generates Javadoc for a project.</description>
-        <topic label="Javadoc Location Properties" href="reference/ref-dialog-javadoc-location.htm"/>
-        <topic label="Creating Javadoc documentation" href="tasks/tasks-196.htm"/>
-    </context>
-    
-</contexts>

diff --git a/bundles/org.eclipse.jdt.doc.user/contexts_JDT_Debugger.xml b/bundles/org.eclipse.jdt.doc.user/contexts_JDT_Debugger.xml
deleted file mode 100644
index ebf478b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/contexts_JDT_Debugger.xml
+++ /dev/null

@@ -1,346 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-
-<!-- Actions -->  
-	<context  id="shortcut_local_java_application" >
-		<description>This command launches the selected main type as a Java application.</description>
-	</context> 
-	  
-	<context  id="shortcut_java_applet" >
-		<description>This command launches the selected applet in an applet viewer.</description>
-	</context>   
-	
-	<context  id="manage_watchpoint_action_context" >
-		<description>This command adds or removes a watchpoint on the selected field.</description>
-	</context>  
-	
-	<context  id="manage_method_breakpoint_action_context" >
-		<description>This command adds or removes a method breakpoint on the selected method.</description>
-	</context>	
-	
-	<context  id="manage_breakpoint_action_context" >
-		<description>This command adds or removes a breakpoint on the current line.</description>
-	</context> 	 	
-	
-	<context  id="add_exception_action_context" >
-		<description>This command opens a dialog to create a Java exception breakpoint.</description>
-	</context> 	 		
-	
-	<context  id="step_into_selection_action_context" >
-		<description>This command steps into the selected method on the current line of execution. Method selection is determined by the selected text or cursor location in the Java editor.</description>
-	</context> 	
-	
-	<context  id="run_to_line_action_context" >
-		<description>This command resumes execution to the line on which the cursor is located in the Java editor.</description>
-	</context>
-	
-	<context  id="execute_action_context" >
-		<description>This command executes the selected code snippet.</description>
-	</context>	
-	
-	<context  id="display_action_context" >
-		<description>This command executes the selected code snippet and displays a textual result.</description>
-	</context>		
-	
-	<context  id="inspect_action_context" >
-		<description>This command executes the selected code snippet and shows the resulting object or primitive in the Expressions view.</description>
-	</context>	
-	
-	<context  id="watch_action_context" >
-		<description>This command creates a watch item for the selected text or variable, and places it in the Expressions view.</description>
-	</context>
-	
-	<context  id="breakpoint_suspend_policy_toggle_action_context" >
-		<description>This command toggles a breakpoint's suspend policy between suspending all threads in a VM or onlt the thread in which the breakpoint was encountered.</description>
-	</context>				
-	
-	<context  id="hit_count_action_context" >
-		<description>This command opens a dialog to configure a breakpoint's hit count.</description>
-	</context>	
-	
-	<context  id="breakpoint_properties_action_context" >
-		<description>This command opens a dialog to configure a breakpoint's properties.</description>
-	</context>
-	
-	<context  id="exception_caught_toggle_action_context" >
-		<description>When checked, this command configures an exception breakpoint to suspend execution in caught locations.</description>
-	</context>
-	
-	<context  id="exception_uncaught_toggle_action_context" >
-		<description>When checked, this command configures an exception breakpoint to suspend execution in uncaught locations.</description>
-	</context>	
-	
-	<context  id="access_toggle_action_context" >
-		<description>When checked, this command configures a watchpoint to suspend execution when a field is accessed (read).</description>
-	</context>				
-
-	<context  id="modification_toggle_action_context" >
-		<description>When checked, this command configures a watchpoint to suspend execution when a field is modified (written).</description>
-	</context>	
-	
-	<context  id="entry_toggle_action_context" >
-		<description>When checked, this command configures a method breakpoint to suspend execution when a method is entered.</description>
-	</context>				
-
-	<context  id="exit_toggle_action_context" >
-		<description>When checked, this command configures a method breakpoint to suspend execution when a method is exited.</description>
-	</context>				
-	
-   <context  id="show_qualified_action_context" >
-      <description>This option can be toggled to show or hide qualified names in the view.</description>
-      <topic label="Show Qualified Names in Breakpoints View" href="reference/ref-39.htm" /> 
-      <topic label="Breakpoints View" href="reference/ref-35.htm"/>
-      <topic label="Show Qualified Names in Expressions View" href="reference/ref-58.htm" />
-      <topic label="Expressions View" href="reference/ref-56.htm"/>
-      <topic label="Show Qualified Names in Variables View" href="reference/ref-76.htm" />
-      <topic label="Variables View" href="reference/ref-74.htm"/>
-   </context>	
-   
-   <context  id="show_constants_action_context" >
-      <description>This option can be toggled to show or hide constants (static final variables) in the view.</description>
-   </context>   
-   
-   <context  id="show_static_action_context" >
-      <description>This option can be toggled to show or hide static variables in the view.</description>
-   </context>      
-   	
-	<context  id="clear_display_view_action_context" >
-		<description>This command clears the contents of the Display view.</description>
-	</context>
-	
-	<context  id="add_watch_expression_context" >
-		<description>This command opens a dialog to create a new Java watch expression.</description>
-	</context>
-	
-	<context  id="reevaluate_watch_expression_context" >
-		<description>This command re-evaluates the value of the selected watch expression.</description>
-	</context>
-	
-	<context  id="edit_watch_expression_context" >
-		<description>This command opens a dialog to edit the selected watch expression.</description>
-	</context>
-		
-	<context  id="convert_to_watch_expression_context" >
-		<description>This command replaces the selected object with an equivalent watch expression.</description>
-	</context>
-			
-	<context  id="variable_inspect_action_context" >
-		<description>This command adds the selected object or primitive value to the Expressions view.</description>
-	</context>
-	
-	<context  id="variable_watch_action_context" >
-		<description>This command creates a Java watch expression based on the name of the selected variable.</description>
-	</context>
-	
-	<context  id="new_detail_formatter_action_context" >
-		<description>This command opens a dialog to define a detail formatter for the class of the selected variable.</description>
-	</context>
-										
-	<context  id="edit_detail_formatter_action_context" >
-		<description>This command opens a dialog to edit an existing detail formatter for the class of the selected variable.</description>
-	</context>
-	
-	<context  id="remove_detail_formatter_action_context" >
-		<description>This command removes the existing detail formatter for the class of the selected variable.</description>
-	</context>
-
-	<context  id="open_variable_concrete_type_hierarchy_action_context" >
-		<description>This command opens a Type Hierarchy view on the type of the selected object.</description>
-	</context>	
-	
-	<context  id="open_variable_concrete_type_action_context" >
-		<description>This command opens a Java editor on the type of the selected object.</description>
-	</context>				
-	
-	<context  id="open_variable_declared_type_hierarchy_action_context" >
-		<description>This command opens a Type Hierarchy view on the declared type of the selected variable.</description>
-	</context>
-		
-	<context  id="open_on_variable_type_action_context" >
-		<description>This command opens a Java editor on the declared type of the selected variable.</description>
-	</context>
-	
-	<context  id="open_on_receiving_type_action_context" >
-		<description>This command opens a Java editor on the type of the receiver of the selected stack frame.</description>
-	</context>		
-	
-	<context  id="open_receiving_type_hierarchy_action_context" >
-		<description>This command opens a Type Hierarchy view on the type of the receiver of the selected stack frame.</description>
-	</context>	
-	
-	<context  id="open_on_declaring_type_action_context" >
-		<description>This command opens a Java editor on the type in which the method of the selected stack frame is defined.</description>
-	</context>		
-	
-	<context  id="open_declaring_type_hierarchy_action_context" >
-		<description>This command opens a Type Hierarchy view on the type in which the method of the selected stack frame is defined.</description>
-	</context>	
-	
-	<context  id="add_package_step_filter_action_context" >
-		<description>This command creates a step filter for the package associated with the receiver of the selected stack frame.</description>
-	</context>	
-	
-	<context  id="add_type_step_filter_action_context" >
-		<description>This command creates a step filter for the type associated with the receiver of the selected stack frame.</description>
-	</context>	
-	
-	<context  id="edit_step_filters_action_context" >
-		<description>This command opens the Java step filters preference page.</description>
-	</context>
-		
-	<context  id="drop_to_frame_action_context" >
-		<description>This command resets the instruction pointer to the first line of the method associated with the selected stack frame. All frames above the selected stack frame are removed from the stack.</description>
-	</context>	
-	
-	<context  id="monitor_trace_action_context" >
-		<description>This command suspends all non-system threads in the selected VM, to display monitor information.</description>
-	</context>			
-		
-	<context  id="monitor_quit_action_context" >
-		<description>This command resumes all non-system threads in the selected VM.</description>
-	</context>	
-	
-	<context  id="terminate_scrapbook_vm_action_context" >
-		<description>This command terminates the VM performing evaluations for this snippet editor.</description>
-	</context>	
-	
-	<context  id="scrapbook_imports_action_context" >
-		<description>This command opens a dialog to configure the imports associated with this snippet editor.</description>
-	</context>
-	
-	<context  id="show_system_threads_context" >
-		<description>This command toggles the display of non-suspended system threads.</description>
-	</context>
-	
-	<context  id="show_thread_groups_context" >
-		<description>This command toggles the display of thread groups.</description>
-	</context>	
-	
-   <context  id="console_remove_launch_context" >
-      <description>Removes the selected launch.</description>
-   </context>
-   
-   <context  id="edit_variable_preferences" >
-      <description>Opens preferences to configure settings related to variables in the Java debugger.</description>
-   </context>
-	
-			
-<!-- Views --> 
-    <context  id="display_view_context" >
-    <description>This view displays the result of expression evaluations. It allows you to select an expression and evaluate it. The result is shown as a string in the Display view.</description>
-   	<topic label="Display View" href="reference/ref-52.htm"/>
-   	<topic label="Evaluating Expressions" href="tasks/tasks-138.htm"/>
-   	<topic label="Inspect" href="reference/ref-55.htm"/>
-	<topic label="Display" href="reference/ref-54.htm"/>
-	<topic label="Clear" href="reference/ref-53.htm"/>		
-   </context>
-   
-<!-- Consoles -->
-
-	<context  id="stack_trace_console_context" >
-      <description>You can paste, format, and navigate Java stack traces in this console.</description>
-   </context>
-
-<!-- Preference pages -->
-
-   <context  id="jre_preference_page_context" >
-      <description>On this page, you can add, remove, and edit JRE configurations.</description>
-      <topic label="Working with JREs" href="tasks/tasks-JREs.htm"/>
-   </context>
-   
-    <context  id="jre_profiles_page_context" >
-      <description>On this page, you can specify a default JRE to use for each JRE profile.</description>
-   </context>
-   
-    <context  id="java_breakpoint_preference_page_context" >
-      <description>On this page, you can modify the properties of a Java breakpoint.</description>
-   </context>
-   
-    <context  id="java_detail_formatter_preference_page_context" >
-      <description>On this page, you can define code snippets used to display the details for variables and expressions in the Variables and Expressions view details area.</description>
-   </context>   
- 
-    <context  id="java_debug_preference_page_context" >
-      <description>On this page, you can configure Java debugging preferences for suspending execution, hot code replace, and communication timeouts.</description>
-   </context> 
-   
-   <context  id="java_step_filter_preference_page_context" >
-      <description>On this page, you can configure the step filters for the Java debugger.</description>
-   </context>  
-   
-   <context  id="java_primitives_preference_page_context   " >
-      <description>On this page, you can configure display options for primitive variables in the Java debugger.</description>
-   </context>  
-   
-<!-- Dialogs -->     
-
-   <context  id="edit_jre_dialog_context" >
-      <description>This dialog allows you to configure the location, name, and libraries associated with a JRE. Source and javadoc can be configured for each library.</description>
-   </context>
-   
-   <context  id="jre_details_dialog_context" >
-      <description>This dialog allows you to view the read-only properties of a JRE contributed by a plug-in.</description>
-   </context>
-   
-   <context  id="edit_detail_formatter_dialog_context" >
-      <description>This dialog allows you to configure the detail formatter code snippet associated with a Java class.</description>
-   </context>
-   
-  <context  id="instance_breakpoint_selection_dialog_context" >
-      <description>This dialog allows you to restrict breakpoints to a specific object.</description>
-   </context>    
-   
-  <context  id="add_watch_expression_dialog_context" >
-      <description>This dialog allows you to define a new watch expression.</description>
-   </context>      
-   
-  <context  id="edit_watch_expression_dialog_context" >
-      <description>This dialog allows you to edit an existing watch expression.</description>
-   </context> 
-   
-  <context  id="snippet_imports_dialog_context" >
-      <description>This dialog allows you to configure the imports associated with a snippet editor.</description>
-   </context>
-   
-   <!-- Launch configuration tabs -->
-  <context  id="launch_configuration_dialog_arguments_tab" >
-     <description>This tab allows you to specify the program and virtual machine arguments for the launch associated with this launch configuration as well as the working directory</description>
-     <topic label="Java application launch configuration" href=" tasks\tasks-java-local-configuration.htm"/>
-     <topic label="Setting execution arguments" href="tasks/tasks-executionArgs.htm"/>
-  </context>
-  
-  <context  id="launch_configuration_dialog_classpath_tab" >
-	 <description>This tab allows you to specify the classpath for the launch associated with this launch configuration</description>
-	 <topic label="Java application launch configuration" href=" tasks\tasks-java-local-configuration.htm"/>
-  </context>
-  
-  <context  id="launch_configuration_dialog_connect_tab" >
-     <description>This tab allows you to set specific information for remote debugging</description>
-     <topic label="Remote debugging" href="concepts/cremdbug.htm"/>
-  </context>
-  
-  <context  id="launch_configuration_dialog_jre_tab" >
-     <description>This tab allows you to define the JRE used to run or debug the application</description>
-     <topic label="Java application launch configuration" href=" tasks\tasks-java-local-configuration.htm"/>
-     <topic label="Working with JREs" href="tasks/tasks-JREs.htm"/>
-  </context>
-  
-  <context  id="launch_configuration_dialog_main_tab" >
-     <description>This tab allows you specify parameters associated with the main type for the launch.</description>
-     <topic label="Java application launch configuration" href=" tasks\tasks-java-local-configuration.htm"/>
-  </context>
-  
-  <context  id="launch_configuration_dialog_source_tab" >
-     <description>This tab allows you to define the location of source files used to display source when debugging a Java application.</description>
-     <topic label="Java application launch configuration" href=" tasks\tasks-java-local-configuration.htm"/>
-     <topic label="Source Attachments" href="reference/ref-124.htm"/>
-  </context>
-
- 	<context id="new_snippet_wizard_page_context">
-    	<description>This wizard helps you create a new Java scrapbook page.</description>
-    	<topic label="Creating a scrapbook page" href="tasks/tasks-149.htm"/>
-    	<topic label="New Java Scrapbook Page Wizard" href="reference/ref-129.htm"/>
-	</context>
-</contexts>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/contexts_JDT_JUnit.xml b/bundles/org.eclipse.jdt.doc.user/contexts_JDT_JUnit.xml
deleted file mode 100644
index 173cdfd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/contexts_JDT_JUnit.xml
+++ /dev/null

@@ -1,66 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-    <!-- Actions -->
-    <context id="goto_referenced_test_action_context">
-        <description>This command navigates to the tests that reference this Java element.</description>
-    </context>
-    <context id="enable_filter_action_context">
-        <description>Toggles the filtering of the stack trace entries as defined in the JUnit preference page.</description>
-        <topic label="JUnit Preferences" href="reference/ref-preferences-junit.htm"/>
-    </context>
-    <context id="junit_tab_group">
-        <description>This launch configuration runs JUnit tests.</description>
-        <topic label="Using JUnit" href="gettingStarted/qs-junit.htm"/>
-    </context>
-    <context id="launch_shortcut">
-        <description>This command launches JUnit tests. When a class is selected its tests are run. When a project, package or source folder is selected then all contained tests are run. When a single test method is selected then the selected test is run.
-		</description>
-         <topic label="Using JUnit" href="gettingStarted/qs-junit.htm"/>
-    </context>
-    <context id="copy_trace_action_context">
-        <description>This command copies the stack trace to the clipboard.</description>
-    </context>
-    <context id="open_test_action_context">
-        <description>This command opens the corresponding test case.</description>
-    </context>
-    <context id="open_editor_atline_action_context">
-        <description>This commands opens the corresponding test method.</description>
-    </context>
-    <context id="rerun_test_action_context">
-        <description>Reruns the selected test.</description>
-    </context>
-    <context id="scroll_lock">
-        <description>Locks the test result view so that the currently executed tests isn't automatically revealed.</description>
-    </context>
-    <!-- View parts -->
-    <context id="results_view_context">
-        <description>This view displays the test results.</description>
-        <topic label="Using JUnit" href="gettingStarted/qs-junit.htm"/>
-    </context>
-    <!-- Wizard pages -->
-    <context id="new_testcase_wizard_page_context">
-        <description>This wizard helps you to create a new test case and to generate test stubs for existing methods.</description>
-        <topic label="Using JUnit" href="gettingStarted/qs-junit.htm"/>
-    </context>
-    <context id="new_testcase_wizard_page2_context">
-        <description>This wizard helps you to create a new test case and to generate test stubs for existing methods.</description>
-        <topic label="Using JUnit" href="gettingStarted/qs-junit.htm"/>
-    </context>
-    <context id="new_testsuite_wizard_page2_context">
-        <description>This wizard helps you to create a new test suite.</description>
-        <topic label="Using JUnit" href="gettingStarted/qs-junit.htm"/>
-    </context>
-    <context id="test_selection_context">
-        <description>Dialog for selecting a test.</description>
-   </context>
-    <context id="result_compare_context">
-        <description>This dialog compares the expected with the actual test result in a text compare view.</description>
-   </context>
-    <!-- Preference pages -->
-    <context id="junit_preference_page_context">
-        <description>This page is where you can set JUnit preferences.</description>
-        <topic label="Using JUnit" href="gettingStarted/qs-junit.htm"/>
-        <topic label="JUnit Preferences" href="reference/ref-preferences-junit.htm"/>
-    </context>
-</contexts>

diff --git a/bundles/org.eclipse.jdt.doc.user/cpy.png b/bundles/org.eclipse.jdt.doc.user/cpy.png
deleted file mode 100644
index a0f8775..0000000
--- a/bundles/org.eclipse.jdt.doc.user/cpy.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/eclipse32.png b/bundles/org.eclipse.jdt.doc.user/eclipse32.png
deleted file mode 100644
index 4983d64..0000000
--- a/bundles/org.eclipse.jdt.doc.user/eclipse32.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/intro/overview.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/intro/overview.htm
deleted file mode 100644
index 616c4af..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/intro/overview.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-    <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>Java Development Overview</title>
-   <script language="JavaScript" src="../../../org.eclipse.help/livehelp.js"> </script>
-   <script type="text/javaScript">
-	function openRelatedLink(rel) {
-		var href = '/org.eclipse.jdt.doc.user/'+rel;
-		if (self.name=="ContentViewFrame") {
-			showTopicInContents(href);
-			window.location = '../../'+rel;
-		}
-		else {
-			window.location = 'http://org.eclipse.ui.intro/showHelpTopic?id='+href;
-		}
-	}
-   </script>
-   </head>
-   
-  <body>
-    <h1>
-      Java Development Overview</h1>
-    <p>
-		The JDT project provides the tool plug-ins that implement a Java IDE supporting the development of any Java application, including Eclipse plug-ins. It adds a Java project nature and Java perspective to the Eclipse Workbench as well as a number of views, editors, wizards, builders, and code merging and refactoring tools. The JDT project allows Eclipse to be a development environment for itself.</p>
-	<p>
-		Try the <a href="javaScript:openRelatedLink('gettingStarted/qs-BasicTutorial.htm')">
-		Basic tutorial</a> to get a first impression. Discover more in the <a href="javaScript:openRelatedLink('tips/jdt_tips.html')">
-		Tips and Tricks</a> section and learn about the latest features in <a href="javaScript:openRelatedLink('whatsNew/jdt_whatsnew.html')">
-		What's new in 3.1</a>
-	</p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-10.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-10.htm
deleted file mode 100644
index 883bf66..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-10.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
-<meta name="Author" content="MAe">
-<title>Moving and copying Java elements</title>
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-</head>
-<body>
-<h1>Moving and copying Java elements</h1>
-<p> In this section, you will use refactoring to move a resource between Java packages.&nbsp;
-Refactoring actions change the structure of your code without changing its
-semantic behavior. </p>
-<ol>
-  <li> In the Package Explorer view, select the <em>MyTestCase.java</em> 
-    file from the <em>test</em> package and drag it into the <em>junit.samples</em> package. 
-    Dragging and dropping the file is similar to selecting the file and
-    choosing <strong>Refactor &gt; Move </strong>from the context menu.
-  </li>
-  <li> You will be prompted to select whether or not to update references to the
-    file you are moving. Typically, you will want to do this to avoid compile errors. You can
-    press the <strong>Preview </strong>button to see the list of changes that
-    will be made as a result of the move.
-  </li>
-  <li>
-<p>Press <strong>OK</strong>. The file 
-    is moved, and its package declaration changes to reflect the new location.</p>
-    <p> <img src="../images/qs-44.png"  alt="File moved to junit.samples package"> 
-    </p>
-    </li>
-    <li><p>Use <strong>Edit &gt; Undo</strong> to undo the move.</p></li>
-  </ol>
-  <p>The context menu is an alternative to using drag and drop.&nbsp; When
-  using the menu, you must specify a target package in the Move dialog, in
-  addition to selecting the update references options you've already seen.</p>
-  <ol>
-  <li> 
-    Select the <em>MyTestCase.java</em> file and from its context menu, select <strong>Refactor 
-    &gt; Move</strong>.</li>
-    <li> In the Move dialog, expand the hierarchy to browse the 
-    possible new locations for the resource. Select the <em>junit.samples</em> 
-    package, then click <strong>OK</strong>. The class is moved, and its 
-    package declaration is updated to the new location. 
-    <p> <img src="../images/qs-46.png"  alt="Move destination dialog"> 
-    </p>
- </li>
-</ol>
-<img src="../images/ngrelc.png"  alt="Related concepts" border="0"> 
-<p> <a href="../concepts/concepts-6.htm">Java views</a><br>
-  <a href="../concepts/concepts-9.htm">Refactoring support</a> </p>
-<p> <img src="../images/ngrelt.png"  alt="Related tasks" border="0"> 
-</p>
-<p> <a href="../tasks/tasks-80.htm">Refactoring</a><br>
-  <a href="../tasks/tasks-85.htm">Copying and moving Java elements</a><br>
-  <a href="../tasks/tasks-51.htm">Moving folders, packages and files</a> </p>
-<p> <img src="../images/ngrelr.png"  alt="Related reference" border="0"> 
-</p>
-<p> <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-  <a href="../reference/ref-117.htm">Refactoring wizard</a><br>
-  <a href="../reference/ref-13.htm">Java preferences</a> </p>
-
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-11.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-11.htm
deleted file mode 100644
index 5e6024e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-11.htm
+++ /dev/null

@@ -1,122 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
-<title> Searching the workbench </title>
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-</head>
-<body>
-<h1> Searching the workbench </h1>
-<p> In this section, you will search the workbench for Java elements. </p>
-<p> In the Search dialog, you can perform file, text or Java searches. Java searches 
-  operate on the structure of the code. File searches operate on the files 
-  by name and/or text content. Java searches are faster, since there is an
-underlying indexing structure for the code structure.  Text searches allow
-you to find matches inside comments and strings. 
-</p>
-<h2> Performing a Java search from the workbench </h2>
-<ol>
-  <li> In the Java perspective, click the <strong>Search</strong> 
-    (<img src="../images/org.eclipse.search/etool16/search.png" alt="Search">) button 
-    in the workbench toolbar or use <strong>Search &gt; Java</strong> from 
-    the menu bar. </li>
-  <li> If it is not already selected, select the <strong>Java Search</strong> 
-    tab. </li>
-  <li> In the <strong>Search string</strong> field, type <em>runTest</em>. 
-    In the <em>Search For</em> area, select <strong>Method</strong>, and in the <em>Limit 
-    To</em> area, select <strong>References</strong>.<br>
-    Verify that the Scope is set to <strong>Workspace</strong>. 
-    <p> <img src="../images/qs-47.png"  alt="Java Search page"> 
-    </p>
-    Then click <strong>Search</strong>. While searching you may click <strong>Cancel</strong> 
-    at any time to stop the search. Partial results will be shown. </li>
-  <li> In the Java perspective, the Search view shows the search results. 
-    <p> <img src="../images/qs-48.png"  alt="Search results view"> 
-    </p>
-    Use the <strong>Show Next Match</strong> 
-    (<img src="../images/org.eclipse.search/elcl16/search_next.png" alt="Show Next Match">) and <strong>Show Previous 
-    Match</strong> (<img src="../images/org.eclipse.search/elcl16/search_prev.png" alt="Show Previous Match">) buttons to navigate to each match. If the file in which the 
-    match was found is not currently open, it is opened in an editor. </li>
-  <li> When you navigate to a search match using the Search view buttons, 
-    the file opens in the editor at the position of the match. Search matches 
-    are tagged with a search marker in the vertical ruler. 
-    <p> <img src="../images/qs-49.png"  alt="Editor with Search marker"> 
-    </p>
-  </li>
-</ol>
-<h2> Searching from a Java view </h2>
-<p> Java searches can also be performed from specific views, including the Outline, 
-  Hierarchy view and the Package Explorer view. </p>
-<ol>
-  <li> In the Package Explorer view, double-click <em>junit.framework.Assert.java</em> 
-    to open it in an editor. </li>
-  <li> In the Outline view, select the fail(String) method, and from its context 
-    menu, select&nbsp;<strong>References &gt; Workspace</strong>. 
-    <p> <img src="../images/qs-50.png"  alt="Search context menu in Outline view"> 
-    </p>
-  </li>
-</ol>
-<h2> Searching from an editor </h2>
-<p> From the Package Explorer view, open <em>junit.framework.TestCase.java</em>. 
-  In the editor, select the class name <em>TestCase</em> and from the context 
-  menu, select <strong>  References &gt; Workspace</strong>. 
-  </p>
-    <img src="../images/qs-52.png"  alt="Search context menu in editor"> 
-<h2> Continuing a search from the search view </h2>
-<p> The Search Results view shows the results for the TestCase search. Select 
-  a search result and open the context menu. You can continue searching the selected 
-  element's references and declarations. </p>
-<img src="../images/qs-53.png"  alt="Search context menu in Search results view"> 
-<h2> Performing a file search </h2>
-<ol>
-  <li> In the Java perspective, click the&nbsp;<strong>Search</strong> button 
-    in the workbench toolbar or select <strong>Search &gt; File</strong> from the menu bar. </li>
-  <li> If it is not already selected, select the <strong>File Search</strong> 
-    tab.</li>
-  <li> In the <strong>Containing text</strong> field, type <em>TestCase</em>.
-    Make sure that the <strong>File name patterns</strong>  field is set 
-    to <em>*.java</em>. The Scope should be set to <em>Workspace</em>.
-    Then click <strong>Search</strong>.
-    <p> <img src="../images/qs-54.png"  alt="File search tab"> 
-    </p>
-  </li>
-  <li> To find all files of a given file name pattern, leave the Containing 
-    Text field empty. </li>
-</ol>
-<h2> Viewing previous search results </h2>
-<p> In the Search Results view, click the arrow next to the<strong> Previous 
-  Search Results</strong> toolbar button to see a menu containing the list of the most 
-  recent searches. You can choose items from this menu to view previous
-searches.&nbsp; The list can be cleared by choosing <strong>Clear History</strong>. 
-</p>
-<img src="../images/qs-55.png"  alt="Previous search results menu"> 
-<p> 
-The <strong>Previous Search Results</strong> button will display a dialog 
-  with the list of all previous searches from the current session. 
-  </p>
-<img src="../images/qs-56.png"  alt="Previous search results dialog"> 
-<p> 
-Selecting a previous search from this dialog will let you view that search. 
-</p>
-<img src="../images/ngrelc.png"  alt="Related concepts" border="0"> 
-<p> 
-
-<a href="../concepts/concepts-8.htm">Java search</a> </p>
-<p> <img src="../images/ngrelt.png"  alt="Related tasks" border="0"> 
-</p>
-<p> <a href="../tasks/tasks-103.htm">Conducting a Java search using the search 
-  dialog</a><br>
-  <a href="../tasks/tasks-104.htm">Conducting a Java search using pop-up menus</a> 
-</p>
-<p> <img src="../images/ngrelr.png"  alt="Related reference" border="0"> 
-</p>
-<p> <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-  <a href="../reference/ref-117.htm">Refactoring wizard</a><br>
-  <a href="../reference/ref-13.htm">Java preferences</a> </p>
-
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-12.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-12.htm
deleted file mode 100644
index 1990ca3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-12.htm
+++ /dev/null

@@ -1,96 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title> Running your programs </title>
-</head>
-<body>
-<h1> Running your programs </h1>
-<p> In this section, you will learn more about running Java programs in the workbench. 
-</p>
-<ol>
-  <li> In the Package Explorer view, find <em>junit.textui.TestRunner.java</em> 
-    and double-click it to open it in an editor. </li>
-  <li> In the Outline view, notice that the TestRunner class has an icon which 
-    indicates that the class defines a <code>main</code> method. 
-    <p> <img src="../images/org.eclipse.jdt.debug.ui/executable.png"  alt="Outline view with selected TestRunner class"> 
-    </p>
-  </li>
-  <li> Right click on TestRunner.java in the Package Explorer and select
-    <strong>Run As</strong> > <strong>Java Application</strong>. This will launch the
-    selected class as a local Java application. The <strong>Run As</strong>
-    context menu item is also available in other places, such as the Outline view.
-    <p> <img src="../images/org.eclipse.jdt.debug.ui/run_as.png"  alt="Run context menu"> </p>
-  </li>
-  <li> Notice that the program has finished running and the following message appears in the 
-    Console view telling you that the program needs an execution argument.&nbsp;
-    Running class from the Package Explorer as a Java Application uses the default settings for
-    launching the selected class and does not allow you to specify any
-    arguments. 
-    <p> <img src="../images/org.eclipse.jdt.debug.ui/test_runner_console.png"  alt="Console with error message: Usage: TestRunner [-wait] testCaseName, where name is the name of the TestCase class"> 
-    </p>
-  </li>
-  <li> To specify arguments, use the drop-down <strong>Run</strong> menu in the
-    toolbar and select <strong>Run...</strong>. 
-    <p> <img src="../images/org.eclipse.jdt.debug.ui/run_drop_down.png"  alt="Run menu of the toolbar"> </p>
-  </li>
-  <li> This time, the Launch Configurations dialog opens with the TestRunner launch configuration selected.
-    A launch configuration allows you to configure how a program is launched,
-    including its arguments, classpath, and other options.&nbsp; (A default
-    launch configuration was created for you when you chose <strong>Run &gt;
-    Java Application</strong>). 
-    <p> <img src="../images/org.eclipse.jdt.debug.ui/run_dialog.png"  alt="Launch configuration dialog showing the Main tab"> 
-    </p>
-  </li>
-  <li> Select the Arguments tab and type <em>junit.samples.VectorTest</em> in 
-    the Program arguments area. 
-    <p> <img src="../images/org.eclipse.jdt.debug.ui/test_runner_args.png"  alt="Arguments tab of the launch configuration dialog"> 
-    </p>
-  </li>
-  <li> Click <strong>Run</strong>. This time the program runs correctly, indicating 
-    the number of tests that were run. 
-    <p> <img src="../images/org.eclipse.jdt.debug.ui/test_runner_output.png"  alt="Console showing program output"> </p>
-  </li>
-  <li> <p>Switch to the Debug perspective. In the Debug view, notice that a process
-    for the last program launch was registered when the program was run.</p>
-    <p>By default, the Debug view automatically removes any terminated launches when
-    a new launch is created. This preference can be configured on the <strong>Launching</strong>
-    preference page located under the <strong>Run/Debug</strong> preference page.</p>
-    <p> <img src="../images/org.eclipse.jdt.debug.ui/test_runner_debug_view.png"  alt="Debug view showing two terminated run launches"> 
-    </p>
-    <em>Note: You can relaunch a terminated process by selecting <strong>Relaunch</strong> 
-    from its context menu.</em> </li>
-  <li> Select the drop-down menu from the <strong>Run</strong> button in the workbench 
-    toolbar. This list contains the previously launched programs. These programs
-    can be relaunched by selecting them in the history list. 
-    <p> <img src="../images/org.eclipse.jdt.debug.ui/run_history.png"  alt="Run drop down menu from the workbench toolbar"> 
-    </p>
-  </li>
-  <li> From the context menu in the Debug view (or the equivalent toolbar button), 
-    select <strong>Remove All Terminated</strong> to clear the view of terminated
-    launch processes. 
-    <p> <img src="../images/org.eclipse.jdt.debug.ui/remove_all_terminated.png"  alt="Debug view showing context menu"> 
-    </p>
-  </li>
-</ol>
-
-    <p><img src="../images/ngrelt.png"  border="0" alt="Related tasks"><br>
-     <a href="../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-     <a href="../tasks/tasks-141.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-     <a href="../tasks/tasks-142.htm">Disconnecting from a VM</a><br>
-     <a href="../tasks/tasks-130.htm">Launching a Java program</a><br>
-     <a href="../tasks/tasks-126.htm">Running and debugging</a><br>
-    </p>
-
-    <p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-     <a href="../reference/ref-51.htm">Debug view</a><br>
-     <a href="../reference/ref-4.htm">Run and debug actions</a><br>
-    </p>
-
-
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-13.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-13.htm
deleted file mode 100644
index b73514b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-13.htm
+++ /dev/null

@@ -1,115 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title> Debugging your programs </title>
-</head>
-<body>
-<h1> Debugging your programs </h1>
-<p> In this section, you will debug a Java program. </p>
-<ol>
-  <li> In the Package Explorer view in the Java perspective, double-click <em>junit.samples.VectorTest.java</em> 
-    to open it in an editor. </li>
-  <li> Place your cursor on the vertical ruler along the left edge of the editor
-    area on the following line in the setUp() method: 
-    <p> <code>fFull.addElement (new Integer(1));</code> </p>
-    <p> and double-click on the ruler to set a breakpoint. </p>
-    <p> <img src="../images/org.eclipse.jdt.debug.ui/set_breakpoint.png"  alt="VectorTest.java editor showing added breakpoint"> 
-    </p>
-    The breakpoint icon indicates the status of the breakpoint.&nbsp; The plain
-    blue breakpoint icon indicates that the breakpoint has been set, but not yet
-    installed.&nbsp;&nbsp;
-    <p>
-    <em>Note: Once the class is loaded by the Java VM, the breakpoint will be
-    installed and a checkmark overlay will be displayed on the breakpoint icon.</em> </p></li>
-  <li> In the Package Explorer view, select the <em>junit.samples</em> package 
-    and select Debug As, and then Java 
-    Application.&nbsp; When you run a program from a package, you will be
-    prompted to choose a type from all classes in the package that define a <code>main
-    </code>method.&nbsp; </li>
-  <li> Select the <em>VectorTest</em> item in the dialog, 
-    then click <strong>OK</strong>. 
-    <p> <img src="../images/org.eclipse.jdt.debug.ui/select_main_type.png"  alt="Type selection dialog"> </p>
-  </li>
-  <li> The program will run until the breakpoint is reached.&nbsp; When the breakpoint is hit, execution 
-    is suspended, and you are asked whether to open the Debug perspective.  Click <strong>Yes</strong>.
-    Notice that the process is still active (not terminated) in 
-    the Debug view. Other threads might still be running. 
-    <p> <img src="../images/org.eclipse.jdt.debug.ui/at_breakpoint.png"  alt="Debug perspective"> </p>
-    <em>Note: The breakpoint now has a checkmark overlay since the class
-    VectorTest was loaded in the Java VM.</em> </li>
-  <li> In the editor in the Debug perspective, select <code>new Vector()</code> from the line above
-    where the breakpoint is set, and from its context menu, select <strong>Inspect</strong>. 
-    <p> <img src="../images/org.eclipse.jdt.debug.ui/example_inspect.png"  alt="VectorTest.java editor with selected breakpoint line showing context menu"> 
-    </p>
-  </li>
-  <li> The expression is evaluated in the context of the current stack frame, 
-    and a pop-up appears which displays the results. You can send a result to
-    the Expressions view by pressing the key binding displayed in the pop-up.
-  </li>
-  <li> Expressions that you evaluate while debugging a program will be listed in
-    this view. To delete an expression after working with it, select the
-    expression and choose <strong>Remove</strong> from its context menu. 
-  </li>
-  <li> The Variables view (available on a tab along with the Expressions view) displays the values of the variables in the selected 
-    stack frame. Expand the this.fFull tree in the Variables view until you can see 
-    elementCount. 
-  </li>
-  <li> The variables (e.g., elementCount) in the Variables view will change when
-    you step 
-    through VectorTest in the Debug view.&nbsp; To step through the code, click the 
-    <strong>Step Over</strong> (<img src="../images/org.eclipse.debug.ui/elcl16/stepover_co.png" alt="Step Over" >) button.&nbsp;
-    Execution will continue at the next line in the same method 
-      (or, if you are at the end of a method, it will continue in the method from 
-      which the current method was called).
-    <p> <img src="../images/org.eclipse.jdt.debug.ui/var_view.png"  alt="Variables view"> </p>
-  </li>
-  <li> Try some other step buttons 
-    (<strong>Step Into <img src="../images/org.eclipse.debug.ui/elcl16/stepinto_co.png" alt="Step Into" >, 
-    Step Return <img src="../images/org.eclipse.debug.ui/elcl16/stepreturn_co.png" alt="Step Return" >) </strong>to
-    step through the code.&nbsp; Note the differences in stepping techniques.
-  </li>
-  <li> You can end a debugging session by allowing the program to run to
-    completion or by terminating it.
-    <ul>
-      <li>You can continue to step over the code with the <strong>Step </strong>buttons
-        until the program completes.</li>
-      <li>You can click the&nbsp; <strong>Resume </strong>  
-      (<img src="../images/org.eclipse.debug.ui/elcl16/resume_co.png" alt="Resume" >) button to allow the
-        program to run until the next breakpoint is encountered or until the
-        program is completed.</li>
-      <li>You can select 
-    <strong>Terminate</strong> from the context menu of the program's
-        process in the Debug view to terminate the program.</li>
-    </ul>
-  </li>
-</ol>
-
-    <p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-     <a href="../concepts/cbrkpnts.htm">Breakpoints</a><br>
-     <a href="../concepts/cremdbug.htm">Remote debugging</a><br>
-     <a href="../concepts/clocdbug.htm">Local debugging</a></p>
-
-    <p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-     <a href="../tasks/tasks-144.htm">Adding breakpoints</a><br>
-     <a href="../tasks/tasks-135.htm">Resuming the execution of suspended threads</a><br>
-     <a href="../tasks/tasks-126.htm">Running and debugging</a><br>
-     <a href="../tasks/tasks-134.htm">Suspending threads</a></p>
-
-    <p><img src="../images/ngrelr.png"  border="0" alt="Related reference"><br>
-     <a href="../reference/ref-11.htm">Debug preferences</a><br>
-     <a href="../reference/ref-51.htm">Debug view</a><br>
-     <a href="../reference/ref-4.htm">Run and debug actions</a><br>
-     <a href="../reference/ref-35.htm">Breakpoints view</a><br>
-     <a href="../reference/ref-45.htm">Console view</a><br>
-     <a href="../reference/ref-52.htm">Display view</a><br>
-     <a href="../reference/ref-56.htm">Expressions view</a><br>
-     <a href="../reference/ref-74.htm">Variables view</a></p>
-
-
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-14.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-14.htm
deleted file mode 100644
index 8087d47..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-14.htm
+++ /dev/null

@@ -1,61 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title> Evaluating expressions </title>
-</head>
-<body>
-<h1> Evaluating expressions </h1>
-<p> In this section, you will evaluate expressions in the context of your
-running Java program. </p>
-<ol>
-  <li> Debug <em>junit.samples.VectorTest.java</em> to the breakpoint in the
-    <code>setUp()</code> method and select <b>Step Over</b> twice to populate <code>fFull</code>.&nbsp; (See the <a href="qs-13.htm">Debugging your Programs</a> section for full
-    details.)<br>
-  </li>
-  <li>Open the Display view by selecting <b>Window &gt; Show View &gt; Display</b> 
-    and type the following line in the view:
-    <p> <code>fFull.size()</code></p>
-  </li>
-  <li> Select the text you just typed, and from its context menu, select <strong>Display</strong>.&nbsp;
-    (You can also choose <strong>Display Result of Evaluating Selected Text </strong> (<img src="../images/org.eclipse.jdt.debug.ui/etool16/disp_sbook.png" alt="Display" >) from
-    the Display view toolbar.) 
-    <p> <img src="../images/org.eclipse.jdt.debug.ui/example_display.png"  alt="Display view with fFull.size selected and showing context menu"> 
-    </p>
-  </li>
-  <li> The expression is evaluated and the result is displayed in the Display
-    view. 
-    <p> <img src="../images/org.eclipse.jdt.debug.ui/example_display_result.png"  alt="Display view showing evaluation result: (int) 2"> 
-    </p>
-  </li>
-  <li> On a new line in the Display view, type the following line: 
-    <p> <code>fFull.toArray()</code> </p>
-  </li>
-  <li> Select this line, and select <strong>Inspect</strong> from the context
-    menu.&nbsp; (You can also choose <strong>Inspect Result of Evaluating
-    Selected Text </strong> (<img src="../images/org.eclipse.jdt.debug.ui/etool16/insp_sbook.png" alt="Inspect" >) from the Display view toolbar.) </li>
-  <li>A lightweight window opens with the value of the evaluated expression. 
-    <p> <img src="../images/org.eclipse.jdt.debug.ui/example_inspect_result.png"  alt="Pop-up containing fFull.toArray() expression"> 
-    </p>
-  </li> 
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-10.htm">Debugger</a></p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-     <a href="../tasks/tasks-138.htm">Evaluating expressions</a><br>
-<a href="../tasks/tasks-151.htm">Displaying the result of evaluating an
-expression</a><br>
-<a href="../tasks/tasks-150.htm">Inspecting the result of evaluating an
-expression</a><br>
-<a href="../tasks/tasks-107.htm">Viewing compilation errors and warnings</a></p>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-56.htm">Expressions view</a></p>
-
-
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-15.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-15.htm
deleted file mode 100644
index 58e411e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-15.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title> Evaluating snippets </title>
-</head>
-<body>
-<h1> Evaluating snippets </h1>
-<p> In this section, you will evaluate Java expressions using the Java scrapbook.
-Java scrapbook pages allow you to experiment with Java code fragments before
-putting them in your program. </p>
-<ol>
-  <li> In the File menu select <STRONG>New &gt; Other &gt; Java &gt;
-	Java Run/Debug &gt; Scrapbook Page</STRONG>. You will be prompted for a folder
-    destination for the page. <p> <img src="../images/org.eclipse.jdt.debug.ui/jpage_wizard.png"  alt="Create Java Scrapbook Page wizard"> 
-    </p></li>
-  <li> In the <strong>Enter or select the folder</strong> field, type or browse below 
-    to select the <em>JUnit</em> project root directory. </li>
-  <li> In the <strong>File name</strong> field, type <em>MyScrap</em>.&nbsp; </li>
-  <li>  
-    
-    Click <strong>Finish</strong> when you are done.&nbsp; A scrapbook page
-    resource is created for you with the <em>jpage</em> file extension.&nbsp; (The <em>jpage
-    </em>file extension will be added automatically if you do not enter it yourself.)&nbsp;
-    The scrapbook page opens automatically in an editor. 
-    <p> <img src="../images/org.eclipse.jdt.debug.ui/empty_jpage.png"  alt="Package Explorer and editor area of the active perspective"> 
-    </p>
- </li>
-  <li> In the editor, type <code>System.get</code> and then use content assist (Ctrl+Space) 
-    to complete the snippet as <code>System.getProperties()</code>. 
-    <p> <img src="../images/org.eclipse.jdt.debug.ui/scrap_assist.png"  alt="Content proposals popup"> </p>
-  </li>
-  <li> Select the entire line you just typed and select <strong>Display</strong> 
-    from the context menu.&nbsp; You can also select <strong>Display Result of
-    Evaluating Selected Text</strong> from the toolbar. 
-    <p> <img src="../images/org.eclipse.jdt.debug.ui/scrap_display.png"  alt="Snippet editor with System.getProperties() selected showing context menu"> 
-    </p>
-  </li>
-  <li> When the evaluation completes, the result of the evaluation is displayed
-    and highlighted 
-    in the scrapbook page. </li>
-  <li> You can inspect the result of an evaluation by selecting text and
-    choosing <strong>Inspect</strong> from the context menu (or selecting <strong>Inspect
-    Result of Evaluating Selected Text</strong> from the toolbar.) </li>
-  <li> When you are finished evaluating code snippets in the scrapbook page, you
-    can close the editor.&nbsp; Save the changes in the page if you want to keep
-    the snippets for future use. </li>
-</ol>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-10.htm">Debugger</a></p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-149.htm">Creating a Java scrapbook page</a><br>
-<a href="../tasks/tasks-151.htm">Displaying the result of evaluating an
-expression</a><br>
-<a href="../tasks/tasks-150.htm">Inspecting the result of evaluating an
-expression</a><br>
-<a href="../tasks/tasks-107.htm">Viewing compilation errors and warnings</a></p>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-129.htm">New Java Scrapbook Page wizard</a><br>
-<a href="../reference/ref-34.htm">Java scrapbook page</a><br>
-<a href="../reference/ref-56.htm">Expressions view</a></p>
-<p><a href="../notices.html"><img src="../cpy.png" border="0" alt="Legal notices" ></a>
-</p>
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-2.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-2.htm
deleted file mode 100644
index b5d9239..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-2.htm
+++ /dev/null

@@ -1,104 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Preparing Eclipse
-    </title>
-  </head>
-  <body>
-    <h1>
-      Preparing Eclipse
-    </h1>
-    <p>
-      In this section, you will verify that Eclipse is properly set up for Java development.
-    </p>
-    <p>
-      The following is assumed:
-    </p>
-    <ul>
-      <li>
-        You are starting with a new Eclipse installation with default settings.
-      </li>
-      <li>
-        You are familiar with the basic Eclipse workbench mechanisms, such as views and perspectives.
-      </li>
-    </ul>
-    <p>
-      If you're not familiar with the basic workbench mechanisms, please see the Getting Started chapter of the Workbench User Guide.
-    </p>
-    <h2>
-      Verifying JRE installation and classpath variables
-    </h2>
-    <ol>
-      <li>
-        If you still see the Eclipse Welcome page, click the arrow icon to begin using Eclipse.
-      </li>
-      <li>
-        Select the menu item <b> Window &gt; Preferences</b> to open the workbench preferences.&nbsp;
-      </li>
-      <li>
-        Select <b>Java &gt; Installed JREs</b> in the tree pane on the left to
-        display the <strong>Installed Java Runtime Environments</strong> preference page. Confirm
-        that a JRE has been detected. By default, the JRE used to run the workbench will be used to build and run 
-        Java programs. It should appear with a checkmark in the list of installed JREs. We recommend that you
-        use a Java SDK instead of a JRE. An SDK is designed for development and contains the source code for the
-        Java library, easing debugging. Additional SDKs can be added by searching the hard drive for installed
-        SDKs. To do so, simply click the <strong>Search</strong> button and specify a root folder for the search.
-		<p>
-		<img src="../images/qs-1.png"  alt="Installed JREs preference page">
-		</p>
-      </li>
-      <li>
-        Select <strong>General &gt; Workspace</strong> in the tree pane to display the <strong>Workspace</strong> preference page. Confirm that the <strong>Build automatically</strong> option is checked.
-		<p>
-		<img src="../images/qs-2.png"  alt="Workbench preference page">
-		</p>
-      </li>
-      <li>
-        Select <b>Java &gt; Build Path </b> in the tree pane to display the <strong>Build Path</strong> preference page. Confirm that <strong>Source and output folder </strong> is set to <strong>Project</strong>.
-		<p>
-		<img src="../images/qs-3.png"  alt="New project preference page">
-		</p>
-      </li>
-      <li>
-        Select <strong>Java &gt; Editor</strong> in the tree pane to display the <strong>Java Editor</strong> preference page. 
-        Confirm that  option <STRONG>Report problems as you type</STRONG>   is checked.
-		<p>
-		<img src="../images/qs-17a.png"  alt="Java Editor preference page">
-		</p>
-      </li>
-      <li>
-        Click on <strong>OK</strong> to save the preferences.
-      </li>
-    </ol>
- 
-<p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a><br>
-       <a href="../concepts/cclsspthv.htm">Classpath variables</a><br>
-       <a href="../concepts/cbuildcp.htm">Build classpath</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png"  alt="Related tasks">
-    </p>
-    <p>
-      <a href="../tasks/tasks-110.htm">Working with build paths</a><br>
-       <a href="../tasks/tasks-JREs.htm">Working with JREs</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-19.htm">JRE Installations Preferences</a><br>
-       <a href="../reference/ref-21.htm">Java Editor Preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-3.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-3.htm
deleted file mode 100644
index 7fb9e27..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-3.htm
+++ /dev/null

@@ -1,107 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Creating your first Java project
-    </title>
-  </head>
-  <body>
-    <h1>
-      Creating your first Java project
-    </h1>
-    <p>
-      In this section, you will create a new Java project. You will be using
-      JUnit as your example project. JUnit is an open source unit testing framework for Java.
-    </p>
-<H2>Getting the Sample Code (JUnit)</H2>
-
-
-<P>First you need to download the JUnit source code.</P>
-<OL>
-	<LI>Go to the <A href="http://www.eclipse.org/downloads/">http://www.eclipse.org/downloads/</A>
-	page</LI>
-	<LI>Select the Downloads link under Java Development Tools.</LI>
-	<LI>Select the link for the release that you are working with.</LI>
-	<LI>Scroll down to the <EM>Example Plug-ins</EM> section and download
-	the examples archive.</LI>
-	<LI>Extract the contents of the Zip file to a directory  from  now on  referenced as &lt;Downloads&gt; (e.g. c:\myDownloads).
-	</LI>
-	</OL>
-<H2>Creating the project</H2>
-
-<OL>
-
-	<LI>Inside Eclipse select the menu item <STRONG>File &gt; New &gt;
-	Project...</STRONG>. to open the <STRONG>New Project</STRONG> wizard
-	</LI>
-	<LI>Select <STRONG>Java Project</STRONG> then click <STRONG>Next</STRONG> 
-	to start the <STRONG>New Java Project</STRONG> wizard:
-	<P><img src="../images/qs-newjavaproject.png"  alt="New Java Project wizard"></P>
-	On this page, type &quot;JUnit&quot; in the <STRONG>Project name</STRONG>
-	field.  Make sure the <STRONG>JDK compliance</STRONG> is set to 1.4, and click <STRONG>Finish</STRONG>. 
-	(If you are interested in the new features in Eclipse supporting J2SE 5.0 development,
-	see the companion guide "Getting Started with Java 5.0 development in Eclipse").
-	</LI>
-	<LI>In the Package Explorer, make sure that the JUnit project is
-	selected. Select the menu item <STRONG>File &gt; Import...</STRONG>.</LI>
-	<LI>Select <STRONG>Archive file</STRONG>, then click <STRONG>Next</STRONG>.
-	</LI>
-	<LI>Click the <STRONG>Browse</STRONG> button next to the <STRONG>Archive
-	file</STRONG> field and browse to select
-	&lt;Downloads&gt;eclipse/plugins/org.eclipse.jdt.ui.examples.projects_3.0.0/archive/junit/junit381src.jar.<BR>
-	<STRONG>Note:</STRONG> This step assumes that you followed steps 1-3 in the <STRONG>Getting
-	the Sample Code</STRONG> section above.<BR>
-	</LI>
-	<LI>In the Import wizard, below the file tree click <STRONG>Select
-	All</STRONG>. You can expand and select elements within the <EM>junit</EM>
-	directory on the left pane to view the individual resources that you
-	are importing on the right pane. <EM>Note: Do not deselect any of the
-	resources in the</EM> junit directory at this time. You will need all
-	of these resources in the tutorial.
-	<P><img src="../images/qs-5.png"  alt="Import hierarchy list">
-</P>
-	</LI>
-	<LI>Make sure that the JUnit project appears in the destination <STRONG>Folder</STRONG>
-	field. Then click <STRONG>Finish</STRONG>. In the import progress
-	indicator, notice that the imported resources are compiled as they are
-	imported into the workbench. This is because the <STRONG>Build
-	automatically</STRONG> option is checked on the Workbench preferences
-	page. You will be prompted to overwrite the .classpath and .project
-	files in the JUnit project. This is because the .classpath resource was
-	created for you when you created the JUnit project. It is safe to
-	overwrite these files.</LI>
-	<LI>In the Package Explorer view, expand the JUnit project to view the
-	JUnit packages.
-	<P><img src="../images/qs-6.png"  alt="Package explorer"></P>
-	</LI>
-</OL>
-<p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a><br>
-      <a href="../concepts/concepts-6.htm">Java views</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-110.htm">Working with build paths</a><br>
-       <a href="../tasks/tasks-12.htm">Creating a new Java project</a><br>
-       <a href="../tasks/tasks-45.htm">Using the Package Explorer</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-121.htm">New Java Project Wizard</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-4.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-4.htm
deleted file mode 100644
index 85a648e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-4.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Browsing Java elements using the package explorer
-    </title>
-  </head>
-  <body>
-    <h1>
-      Browsing Java elements using the package explorer
-    </h1>
-    <p>
-      In this section, you will browse Java elements within the JUnit project.
-    </p>
-    <ol>
-      <li>
-        In the Package Explorer view, make sure the JUnit project is expanded so you can see its packages.
-      </li>
-      <li>
-        Expand the package <code>junit.framework</code> to see the Java files contained in the package.
-      </li>
-      <li>
-        Expand the Java file <code>TestCase.java. </code>Note that the Package
-        Explorer shows Java-specific sub-elements of the source code file.&nbsp;
-        The public type and its members (fields and
-        methods) appear in the tree.
-        <p>
-            <img src="../images/qs-7.png"  alt="Package explorer"> 
-        </p>
-      </li>
-    </ol>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-6.htm">Java views</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-45.htm">Using the Package Explorer</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-view-package-explorer.htm">Package Explorer View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-6.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-6.htm
deleted file mode 100644
index dbe5865..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-6.htm
+++ /dev/null

@@ -1,106 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<title> Viewing the type hierarchy</title>
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-</head>
-<body>
-<h1>Viewing the type hierarchy</h1>
-<p> In this section, you will learn about using the Hierarchy view by viewing
-classes and members in a variety of different ways. </p>
-<ol>
-  <li> In the Package Explorer view, find <em>junit.framework.TestCase.java</em>. 
-    From its context menu, select <strong>Open Type Hierarchy</strong>. You 
-    can also open type hierarchy view: 
-    <ul>
-      <li> from the menu bar by selecting <strong>Navigate &gt; Open Type 
-        Hierarchy</strong>.</li>
-      <li> from the keyboard by pressing F4 after selecting <em>TestCase.java</em>. 
-      </li>
-    </ul>
-	<p>
-    <img src="../images/qs-28.png"  alt="Context menu">
-	</p>
-  </li>
-  <li> The buttons in the view tool bar control which part of the hierarchy is
-    shown.&nbsp; Click the&nbsp;<strong>Show the Type Hierarchy&nbsp;</strong>button 
-    to see the class hierarchy, including the base classes and subclasses. The 
-    small arrow on the left side of the type icon of TestCase indicates that the 
-    hierarchy was opened on this type.
-	<p>
-    <img src="../images/qs-29.png"  alt="Type hierarchy"> 
-	</p>
-  </li>
-  <li> Click the <strong>Show the Supertype Hierarchy</strong> button to 
-    see a hierarchy showing the type's parent elements including implemented
-    interfaces. This view shows the results of going up the type hierarchy.
-	<p>
-    <img src="../images/qs-30.png"  alt="Supertype hierarchy"> 
-	</p>
-    In this &quot;reversed hierarchy&quot; view, you can see that TestCase implements 
-    the Test interface. </li>
-  <li> Click the&nbsp;<strong>Show the Subtype Hierarchy</strong> button in the 
-    view toolbar.
-	<p>
-    <img src="../images/qs-31.png"  alt="Subtype hierarchy"> 
-	</p>
-  </li>
-  <li> Click the <strong>Lock View and Show Members in Hierarchy</strong> 
-    button in the toolbar of the member pane, then select the runTest() method 
-    in the member pane. The view will now show all the types implementing runTest(). 
-	<p>
-    <img src="../images/qs-32.png"  alt="Subtype hierarchy showing method implementors"> 
-	</p>
-  </li>
-  <li> In the Hierarchy view, click the <strong>Show the Supertype Hierarchy</strong> 
-    button. Then on the member pane, select <code>countTestCases()</code> to display 
-    the places where this method is declared.
-	<p>
-    <img src="../images/qs-33.png"  alt="Supertype hierarchy showing method implementors"> 
-	</p>
-  </li>
-  <li> In the Hierarchy view select the <em>Test</em> element and select <strong>Focus 
-    On 'Test'</strong> from its context menu. <em>Test</em> is presented in the Hierarchy view. </li>
-  <li> Activate the Package Explorer view and select the package junit.framework. 
-    Use <strong>Open Type Hierarchy</strong> from its context menu. A hierarchy 
-    is opened containing all classes of the package. For completion of the tree, 
-    the hierarchy also shows some classes from other packages. These types are 
-    shown by a type icon with a white fill.
-	<p>
-    <img src="../images/qs-33a.png"  alt="Hierarchy on a package"> 
-	</p>
-  </li>
-  <li> Use <strong>Previous Type Hierarchies</strong> to go back to a previously 
-    opened element. Click on the arrow next to the button to see a list of elements or click 
-    on the button to edit the history list.
-	<p>
-    <img src="../images/qs-33b.png"  alt="History menu"> 
-	</p>
-  </li>
-  <li> From the menu bar, select&nbsp;<strong>Window &gt; Preferences</strong>. 
-    Go to&nbsp;<strong>Java</strong> and select&nbsp;<strong>Open a new Type Hierarchy 
-    Perspective</strong>. Then click&nbsp;<strong>OK</strong>. </li>
-  <li> In the Hierarchy view, select the Test element again, and activate&nbsp;<strong>Open 
-    Type Hierarchy</strong> from the Navigate menu bar. The resource containing 
-    the selected type is shown in a new perspective (the Hierarchy perspective), 
-    and its source is shown in the Java editor.&nbsp; By setting the preference 
-    option for viewing type hierarchy perspectives, you can have more than one 
-    type hierarchy in your workbench and switch between them as needed.  
-    Close the Hierarchy perspective before proceeding to the next step.</li>
-</ol>
-<img src="../images/ngrelc.png"  alt="Related concepts" border="0"> 
-<p> <a href="../concepts/concepts-7.htm">Java views</a> </p>
-<p> <img src="../images/ngrelt.png"  alt="Related tasks" border="0"> 
-</p>
-<p> <a href="../tasks/tasks-37.htm">Using the Hierarchy view</a> </p>
-<p> <img src="../images/ngrelr.png"  alt="Related reference" border="0"> 
-</p>
-<p> <a href="../reference/ref-type-hierarchy.htm">Type Hierarchy view</a><br>
-  <a href="../reference/ref-13.htm">Java Base preference page</a> </p>
-
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-7.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-7.htm
deleted file mode 100644
index f1c8f5b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-7.htm
+++ /dev/null

@@ -1,96 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
-<meta name="Author" content="MAe">
-<title> Identifying problems in your code </title>
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-</head>
-<body>
-<h1> Identifying problems in your code </h1>
-<p> In this section, you will review the different indicators for identifying 
-  problems in your code. </p>
-<p>Build problems are displayed in the  Problems view and annotated in the vertical
-ruler of your source code. </p>
-<ol>
-  <li> Open <em>junit.framework.TestCase.java</em> in the editor from the 
-    Package Explorer view. </li>
-  <li> Add a syntax error by deleting the semicolon at the end of the package
-    declaration in the source code. 
-    <p> <img src="../images/qs-34.png"  alt="Editor with missing semicolon"> 
-    </p>
-  </li>
-  <li> Click the <strong>Save</strong> button. The project is rebuilt
-    and the problem is indicated in several ways: 
-    <ul>
-      <li> In the  Problems view, the problems are listed, </li>
-      <li> In the Package Explorer view, the Type Hierarchy or the Outline view, 
-        problem ticks appear on the affected Java elements and their parent elements, 
-      </li>
-      <li> In the editor's vertical ruler, a problem marker is displayed near the affected line, 
-      </li>
-      <li> Squiggly lines appear under the word which might have caused the error, and</li>
-      <li> The editor tab is annotated with a problem marker. </li>
-    </ul>
-    <p><img src="../images/qs-35.png"  alt="Problem marker in Package Explorer, editor and Tasks view"> 
-    </p>
-  </li>
-  <li> You can hover over the problem marker in the vertical ruler to view a description 
-    of the problem. 
-    <p> <img src="../images/qs-36.png"  alt="Problem marker hover"> 
-    </p>
-  </li>
-  <li> Click the <strong>Close</strong> (&quot;X&quot;) button on the editor's tab to 
-    close the editor. </li>
-  <li> In the  Problems view, select a problem in the list. Open its context menu 
-    and select Go To. The file is opened in the editor at the location of the 
-    problem. 
-    <p> <img src="../images/qs-37.png"  alt="Problems view"> 
-    </p>
-  </li>
-  <li> Correct the problem in the editor by adding the semicolon. Click 
-    the <strong>Save</strong> button. The project is rebuilt and the problem indicators disappear. </li>
-  <li> In the Outline view, select the method <em>getName()</em>. The editor will 
-    scroll to this method. </li>
-  <li> On the first line of the method change the returned variable <code>fName</code> 
-    to <code>fTestName</code>. While you type, a problem highlight underline appears 
-    on fTestName, to indicate a problem. Hovering over the highlighted problem 
-    will display a description of the problem.</li>
-  <li> On the marker bar a light bulb marker appears. The light bulb signals that 
-    correction proposals are available for this problem. 
-    <p> <img src="../images/qs-37a.png"  alt="Light bulb and problem highlight line"> 
-    </p>
-  </li>
-  <li> Click to place the cursor onto the highlighted error, and choose <strong>Quick Fix</strong> 
-    from the Edit menu bar. You can also press Ctrl+1 or left click the light 
-    bulb. A selection dialog appears with possible corrections. 
-    <p> <img src="../images/qs-37b.png"  alt="Correction proposals"> 
-    </p>
-  </li>
-  <li> Select 'Change to fName' to fix the problem. The problem highlight 
-    line will disappear as the correction is applied. </li>
-  <li> Close the file without saving. </li>
-  <li> You can configure how problems are indicated on the <strong>Window 
-    &gt; Preferences &gt; General &gt; Editors &gt; Text Editors &gt; Annotations </strong>page. </li>
-</ol>
-<img src="../images/ngrelc.png"  alt="Related concepts" border="0"> 
-<p> <a href="../concepts/concepts-7.htm">Java editor</a><br>
-  <a href="../concepts/concepts-6.htm">Java views</a><br>
-  <a href="../concepts/concepts-4.htm">Java builder</a> </p>
-<p> <img src="../images/ngrelt.png"  alt="Related tasks" border="0"> 
-</p>
-<p> <a href="../tasks/tasks-54.htm">Using the Java editor</a><br>
-  <a href="../tasks/tasks-69.htm">Viewing documentation and information</a><br>
-  <a href="../tasks/tasks-175.htm">Using quick fix</a><a href="../tasks/tasks-106.htm"></a> 
-</p>
-<p> <img src="../images/ngrelr.png"  alt="Related reference" border="0"> 
-</p>
-<p> <a href="../reference/ref-21.htm">Editor preference page</a><br>
-  <a href="../reference/ref-java-editor-quickfix.htm">Quick Fix</a> </p>
-
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-8.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-8.htm
deleted file mode 100644
index 07fa01e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-8.htm
+++ /dev/null

@@ -1,74 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
-<title> Renaming Java elements </title>
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-</head>
-<body>
-<h1> Renaming Java elements </h1>
-<p> In this section, you will rename a Java element using refactoring.&nbsp;
-Refactoring actions change the structure of your code without changing its
-semantic behavior. </p>
-<ol>
-  <li> In the Package Explorer view, select&nbsp;<em>junit.framework.TestCase.java</em>. 
-  </li>
-  <li> From its context menu, select&nbsp;<strong>Refactor &gt; Rename</strong>. </li>
-  <li> In the&nbsp;<strong>New Name</strong> field on the Rename Compilation 
-    Unit page, type &quot;<em>TestCase2</em>&quot;. 
-    <p> <img src="../images/qs-38.png"  alt="Rename refactoring wizard"> 
-    </p>
-  </li>
-  <li> To preview the changes that will be made as a result of renaming the
-    class, press <strong>Preview &gt;</strong>.
-  </li>
-  <li> The workbench analyzes the proposed change and presents you with a preview 
-    of the changes that would take place if you rename this 
-    resource.&nbsp;<p>Since renaming a compilation unit will affect the import
-    statements in other compilation units, there are other compilation units
-    affected by the change.&nbsp; These are shown in a list of changes in the
-    preview pane. </p>
-    <p> <img src="../images/qs-39.png"  alt="Refactoring wizard preview page"> 
-    </p>
-  </li>
-  <li> On the Refactoring preview page, you can scroll through the proposed 
-    changes and select or deselect changes, if necessary.&nbsp; You will
-    typically accept all of the proposed changes. </li>
-  <li> Click&nbsp;<strong>OK</strong>  to accept all proposed changes. </li>
-</ol>
-<p>You have seen that a refactoring action can cause many changes in different
-compilation units.&nbsp; These changes can be undone as a group.</p>
-<ol>
-  <li> In the menu bar, select&nbsp;<strong>Edit &gt; Undo Rename TestCase.java 
-    to TestCase2.java</strong>. 
-    <p> <img src="../images/qs-40.png"  alt="Refactor menu"> 
-    </p>
-  </li>
-  <li> The refactoring changes are undone, and the workbench returns to its previous 
-    state. You can undo refactoring actions right up until you change and save 
-    a compilation unit, at which time the refactoring undo buffer is cleared. 
-  </li>
-</ol>
-<img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-<p> <a href="../concepts/concepts-9.htm">Refactoring support</a> </p>
-<p> <img src="../images/ngrelt.png" alt="Related tasks" border="0" > 
-</p>
-<p> <a href="../tasks/tasks-80.htm">Refactoring</a><br>
-  <a href="../tasks/tasks-92.htm">Renaming a compilation unit</a><br>
-  <a href="../tasks/tasks-82.htm">Refactoring without preview</a><br>
-  <a href="../tasks/tasks-83.htm">Refactoring with preview</a><br>
-  <a href="../tasks/tasks-84.htm">Previewing refactoring changes</a><br>
-  <a href="../tasks/tasks-100.htm">Undoing a refactoring operation</a><a href="../tasks/tasks-100.htm"></a> 
-</p>
-<p> <img src="../images/ngrelr.png" alt="Related reference" border="0" > 
-</p>
-<p> <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-  <a href="../reference/ref-117.htm">Refactoring wizard</a><br>
-  <a href="../reference/ref-13.htm">Java preferences</a> </p>
-
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-9.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-9.htm
deleted file mode 100644
index c397e94..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-9.htm
+++ /dev/null

@@ -1,112 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
-<title> Creating a Java class </title>
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-</head>
-
-<body>
-<h1> Creating a Java class </h1>
-<p> In this section, you will create a new Java class and add methods using 
-  code generation actions. </p>
-<ol>
-  <li> In the Package Explorer view, select the JUnit project. 
-  Click the&nbsp;<strong>New Java Package</strong> button in the toolbar, or select&nbsp;<strong>New &gt; Package</strong> from the project's 
-    context menu . </li>
-  <li> In the&nbsp;<strong>Name</strong> field, type&nbsp;<em>test</em> as the 
-    name for the new package. Then click&nbsp;<strong>Finish</strong>. </li>
-  <li> In the Package Explorer view, select the new&nbsp;<em>test</em> package 
-    and click the&nbsp;<strong>New Java Class</strong> button in the toolbar. 
-  </li>
-  <li> Make sure that&nbsp;<em>JUnit</em> appears in the&nbsp;<strong>Source Folder</strong> 
-    field and that&nbsp;<em>test</em> appears in the&nbsp;<strong>Package</strong> 
-    field. In the&nbsp;<strong>Name</strong> field, type&nbsp;<em>MyTestCase</em>. 
-    <p> <img src="../images/qs-41.png"  alt="Java Class wizard"> 
-    </p>
-  </li>
-  <li> Click the&nbsp;<strong>Browse</strong> button next to the&nbsp;<strong>Superclass</strong> 
-    field. </li>
-  <li> In the&nbsp;<strong>Choose a type</strong> field in the Superclass Selection 
-    dialog, type&nbsp;<em>Test</em> to narrow the list of available superclasses. 
-    <p> <img src="../images/qs-42.png"  alt="Superclass Selection dialog"> 
-    </p>
-  </li>
-  <li> Select the&nbsp;<em>TestCase</em> class and click&nbsp;<strong>OK</strong>. 
-  </li>
-  <li> Select the checkbox for&nbsp;<strong>Constructors from superclass</strong>. 
-  </li>
-  <li> Click&nbsp;<strong>Finish</strong> to create the new class. 
-    <p> <img src="../images/qs-43.png"  alt="Java Class wizard"> 
-    </p>
-  </li>
-  <li> The new file is opened in the editor. It contains the new class,
-    the constructor and comments.&nbsp; You can select options for the creation and
-    configuration of generated comments in the Java preferences (<strong>Window &gt; Preferences &gt; Java &gt; Code Style &gt; Code Templates</strong>).</li>
-  <li> In the Outline view select the new class&nbsp;<em>MyTestCase</em>. Open 
-    the context menu and select&nbsp;<strong>Source &gt; Override/Implement Methods...</strong>. 
-    <p> <img src="../images/qs-43a.png"  alt="Context menu of a type"> 
-    </p>
-  </li>
-  <li> In the Override Methods dialog, check <em>setUp()</em> and <em>tearDown()</em>
-    and click&nbsp;<strong>OK</strong>. Two methods are added to the class. 
-    <p> <img src="../images/qs-43b.png"  alt="Override Methods dialog"> 
-    </p>
-  </li>
-  <li> Change the body of <em>setUp()</em> to <code>container= new Vector();</code> </li>
-  <li> <em>container</em> and <em>Vector</em> are underlined with a problem 
-    highlight line as they cannot be resolved. A light bulb appears on the marker 
-    bar. Set the cursor inside <em>Vector</em> and press <kbd>Ctrl+1</kbd> (or use 
-    <strong>Edit &gt; Quick Fix</strong> from the menu bar). Choose <em>Import 'Vector' (java.util)</em>.This adds the missing import declaration. 
-    <p> <img src="../images/qs-43c.png"  alt="Correction proposals for Vector"><br>
-    </p>
-    Set the cursor inside <em>container</em> and press <kbd>Ctrl+1</kbd>. Choose <em>Create 
-    field 'container'</em> to add the new field. 
-    <p> <img src="../images/qs-43d.png"  alt="Correction proposals for container"> 
-    </p>
-  </li>
-  <li> In the Outline view, select the class <em>MyTestCase</em>. Open the 
-    context menu and select <strong>Source &gt; Generate Getters and Setters...</strong>. 
-    <p> <img src="../images/qs-43e.png"  alt="Generate Getter and Setter in context menu"> 
-    </p>
-  </li>
-  <li> The Generate Getter and Setter dialog suggests that you create the methods getContainer 
-    and setContainer. Select both and click <strong>OK</strong>. A getter 
-    and setter method for the field container are added. 
-    <p> <img src="../images/qs-43f.png"  alt="Generate Getter and Setter dialog"> 
-    </p>
-  </li>
-  <li> Save the file. </li>
-  <li> The formatting of generated code can be configured in&nbsp;<strong>Window 
-    &gt; Preferences &gt; Java &gt; Code Style &gt; Formatter</strong>. If you use a prefix 
-    or suffix for field names (e.g. fContainer), you can specify this in&nbsp;<strong>Window 
-    &gt; Preferences &gt; Java &gt; Code  Style</strong> so that generated
-    getters and setters will suggest method names without the prefix or suffix. 
-  </li>
-</ol>
-<img src="../images/ngrelc.png"  alt="Related concepts" border="0"> 
-<p> <a href="../concepts/concepts-6.htm">Java views</a><br>
-  <a href="../concepts/concepts-7.htm">Java editor</a> </p>
-<p> <img src="../images/ngrelt.png"  alt="Related tasks" border="0"> 
-</p>
-<p> <a href="../tasks/tasks-175.htm">Using quick fix</a><br>
-  <a href="../tasks/tasks-11.htm">Creating Java elements</a><br>
-  <a href="../tasks/tasks-57.htm">Generating getters and setters</a> </p>
-<p> <img src="../images/ngrelr.png"  alt="Related reference" border="0"> 
-</p>
-<p> <a href="../reference/ref-126.htm">New Java Class wizard</a><br>
-  <a href="../reference/ref-menu-source.htm">Source actions</a><br>
-  <a href="../reference/ref-java-editor-quickfix.htm">Quick Fix</a><br>
-  <a href="../reference/ref-dialog-override-method.htm">Override Methods dialog</a><br>
-  <a href="../reference/ref-dialog-gettersetter.htm">Generate Getter and Setter dialog</a><br>
-  <a href="../reference/ref-17.htm">Code formatter preference page</a><br>
-  <a href="../reference/ref-preferences-code-generation.htm">Code style preference page</a><br>
-  <a href="../reference/ref-preferences-code-templates.htm">Code templates preference page</a><br>
-</p>
-
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-AddMethod.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-AddMethod.htm
deleted file mode 100644
index 1a9b354..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-AddMethod.htm
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Adding new methods
-    </title>
-  </head>
-  <body>
-    <h1>
-      Adding new methods
-    </h1>
-    <ol>
-      <li>
-        Start adding a method by typing the following at the end of the <em>VectorTest.java</em> file (but before the closing 
-        brackets of the type) in the Java editor:<br>
-        <code>public void testSizeIsThree()</code><br>
-		As soon as you type the method name in the editor area, the new method appears at the bottom of the Outline view. 
-		<p>
-		<img src="../images/qs-13.png"  alt="New method in outline view">
-		</p>
-		In addition, error annotations (red boxes) appear in the overview ruler positioned on the right hand side 
-		of the editor. These error annotations indicate that the compilation unit is currently not correct. If you hover
-		over the second red box, a tool tip appears: <em>Unmatched bracket</em>; <em>Syntax error on token &quot;)&quot;, 
-		{ expected after this token</em>, which is correct since the method doesn't have a body yet. Note that error 
-		annotations in the editor's rulers are updated as you type. This behavior can be controlled via  the
-		<STRONG>Report problems as you type</STRONG> option located on the preference page <strong>Java &gt; 
-		Editor</strong>.
-		<p>
-		<img src="../images/qs-13a.png"  alt="Error annotations in overview ruler">
-		</p>
-		
-      </li>
-      <li>
-        Click the <strong>Save</strong> button. The compilation unit is compiled automatically and errors appear in the 
-        Package Explorer view, in the Problems view and on the vertical ruler (left hand side of the editor). In the Package 
-        Explorer view, the errors are propagated up to the project of the compilation unit containing the error.
-		<p>
-		<img src="../images/qs-14.png"  alt="Error propagation in package explorer">
-		</p>
-      </li>
-      <li>
-        Complete the new method by typing the following:<br>
-        <p><code>
-          {<br>
-          &nbsp; assertTrue(fFull.size() == 3);<br>
-        </code></p>
-        Note that the closing curly bracket has been auto inserted.
-      </li>
-      <li>
-        Save the file. Notice that the error indicators disappear since the
-        missing bracket has been added.
-      </li>
-    </ol>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-       <a href="../concepts/concepts-7.htm">Java editor</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-54.htm">Using the Java editor</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-       <a href="../reference/ref-21.htm">Java Editor Preferences</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-BasicTutorial.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-BasicTutorial.htm
deleted file mode 100644
index 1d3c755..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-BasicTutorial.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Basic tutorial
-    </title>
-  </head>
-  <body>
-    <h1>
-      Basic tutorial
-    </h1>
-    <p>
-      This tutorial provides a step by step walk-through of the Java development tools.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-Browsing.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-Browsing.htm
deleted file mode 100644
index 47c6ddc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-Browsing.htm
+++ /dev/null

@@ -1,83 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Using the Java browsing perspective
-    </title>
-  </head>
-  <body>
-    <h1>
-      Using the Java browsing perspective
-    </h1>
-    <p>
-      In this section you will use the Java browsing perspective to browse and
-      manipulate your code. <a href="qs-4.htm">Browsing Java elements with the 
-      Package Explorer</a> gives an overview of using the Package Explorer to browse
-      elements. In contrast to the Package Explorer, which organizes all Java elements
-      in a tree, consisting of projects, packages, compilation units, types, etc., the
-      browsing perspective uses distinct views to present the same information. Selecting 
-      an element in one view, will show its content in another view.
-    </p> 
-    <p>To open a browsing
-      perspective activate <strong>Window &gt; Open Perspective &gt; Java Browsing</strong> from 
-      within the Java perspective or use the context menu of the <strong>Open a Perspective
-      </strong> toolbar button.
-    </p>
-    <p>
-	  <img src="../images/qs-browsing1.png"  alt="Java browsing perspective">
-    </p>
-    <p>
-      The views of the perspective are connected to each other in the following ways:
-      <ul>
-        <li>
-          Selecting an element in the <strong>Projects</strong> views shows its packages
-          in the <strong>Packages</strong> view.
-        </li>
-        <li>
-          The <strong>Types</strong> view shows the types contained in the package selected
-          in the <strong>Packages</strong> view.
-        </li>
-        <li>
-          The <strong>Members</strong> view shows the members of a selected type. Functionally,
-          the <strong>Members</strong> view is comparable to the <strong>Outline</strong> view used in the normal Java
-          perspective.
-        </li>
-        <li>
-          Selecting an element in the <strong>Members</strong> view reveals the element in the editor. If there
-          isn't an editor open for the element, double-clicking on the element will open a corresponding editor.
-        </li>
-      </ul>
-    </p>
-    <p>
-      All four views are by default linked to the active editor. This means that the views will adjust 
-      their content and their selection according to the file presented in the active editor. The 
-      following steps illustrate this behavior:
-      <ol>
-        <li>
-          Select <em>junit.extensions</em> in the <strong>Packages</strong> view.
-        </li>
-        <li>
-          Open type <em>TestSetup</em> in the editor by double-clicking it in the <strong>Types view</strong>.
-        </li>
-        <li>
-          Now give back focus to the editor opened on file <em>TestCase.java</em> by clicking on the
-          editor tab. The <strong>Packages</strong>, <strong>Types</strong> and <strong>
-          Members</strong> view adjust their content and selections to reflect the active editor. The
-          <strong>Packages</strong> view's selection is set to <em>junit.framework</em> and the <strong>
-          Types</strong> view shows the content of the <em>junit.framework</em> packages. In addition,
-          the type <em>TestCase</em> is selected.
-        </li>
-      </ol> 
-    </p>
-    <p>
-      Functionally, the Java browsing perspective is fully comparable to the Java perspective.
-      The context menus for projects, packages, types, etc. and the global menu and tool bar are the same.
-      Therefore activating these functions is analogous to activating them in the Java perspective.
-    </p>
-    
-  </body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ContentAssist.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ContentAssist.htm
deleted file mode 100644
index 872f24b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ContentAssist.htm
+++ /dev/null

@@ -1,88 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Using content assist
-    </title>
-  </head>
-  <body>
-    <h1>
-      Using content assist
-    </h1>
-    <p>
-      In this section you will use <em>content assist</em> to finish writing a new
-      method. Open <em>junit.samples.VectorTest.java</em> file in the Java
-      editor if you do not already have it open and select the <code>testSizeIsThree()</code> method
-      in the Outline view. If the file doesn't contain such a method see <a href="qs-AddMethod.htm">Adding new methods</a>
-      for instructions on how to add this method.
-    </p>
-    <ol>
-      <li>
-        Add the following lines to the end of the method.  
-        When you type the <tt>.</tt> after <tt>v</tt>, Eclipse will show a list of possible completions.
-        Notice how the options are narrowed down as you continue to type.
-        <p>
-          <code>
-            Vector v = new Vector();<br>
-            for (int i=0; i&lt;3; i++)<br>
-            &nbsp;&nbsp;v.addElement(new Object());<br>
-            assert<br>
-          </code>
-        </p>  
-      </li>
-      <li>
-        With your cursor at the end of the word <code>assert</code>, press <kbd>Ctrl</kbd>+<kbd>Space</kbd> to activate content assist. The content assist window with a list of
-        proposals will appear. Scroll the list to see the available choices.
-		<p>
-		<img src="../images/qs-16.png"  alt="Content assist">
-		</p>
-      </li>
-      <li>
-        With the content assist window still active, type the letter 't'
-        in the source code after <code>assert</code> (with no space in between). The list is narrowed and only shows entries
-        starting with 'assert'. Single-click various items in the list to view any available Javadoc help for each item.
-		<p>
-		<img src="../images/qs-17.png"  alt="Content assist filtered">
-		</p>
-      </li>
-      <li>
-        Select <code>assertTrue(boolean)</code> from the list and press <kbd>Enter</kbd>. The code for the <code>assertTrue(boolean)</code> method is inserted.
-      </li>
-      <li>
-        Complete the line so that it reads as follows:<br>
-        <p><code>
-        assertTrue(v.size() == fFull.size());
-        </code></p>
-      </li>
-      <li>
-        Save the file.
-      </li>
-    </ol>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-       <a href="../concepts/concepts-7.htm">Java editor</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-54.htm">Using the Java editor</a><br>
-       <a href="../tasks/tasks-65.htm">Using content assist</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-       <a href="../reference/ref-143.htm">Java Content Assist</a><br>
-       <a href="../reference/ref-21.htm">Java Editor Preferences</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-DetectingExistingLayout.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-DetectingExistingLayout.htm
deleted file mode 100644
index f0de456..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-DetectingExistingLayout.htm
+++ /dev/null

@@ -1,91 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Detecting existing layout
-    </title>
-  </head>
-  <body>
-    <h1>
-      Detecting existing layout
-    </h1>
-    <h3>Layout on file system</h3>
-    <ul>
-	<li>The source files for a product are laid out in one directory "src".</li>
-	<li>The class files are in another directory "bin".</li>
-	<p><img src="../images/qs-DetectingExistingLayout1.png"  alt="Layout 1"></p>
-	</ul>
-    <h3>Steps for defining a corresponding project</h3>
-    <ol>
-	<li>
-		<p>Open a Java perspective, select the menu item <strong>File &gt; New &gt; Project...</strong>. to open the <strong>New Project</strong> wizard.</p>
-	</li>
-	<li>
-        <p>Select <strong>Java project</strong> in the list of wizards and click <strong>Next</strong>.</p>
-    </li>
-    <li>
-    	<p>On the next page, type &quot;Product&quot; in the <strong>Project name</strong> field.</p>
-    </li>
-    <li>
-    	<p>In <strong>Project layout</strong> group, change selection to <strong>Create separate source and output folders</strong>.</p>
-    	<p>In <strong>Contents</strong> group, change selection to <strong>Create project from existing source</strong>.</p>
-    	<p>Click <strong>Browse...</strong> and choose the <i><code>Product</code></i> directory on drive <i><code>D:</code></i>.</p>
-		<p><img src="../images/qs-DetectingExistingLayout2.png"  alt="Layout 2"></p>
-    </li>
-    <li>
-     	<p>Click <strong>Next</strong>.</p>
-     	<p>Ensure that the source and output folders are detected.</p>
-		<p><img src="../images/qs-DetectingExistingLayout3.png"  alt="Layout 3"></p>
-		<p>
-			<em>Warning: </em>If the preference <strong>Window &gt; Preferences &gt; Java &gt; Compiler &gt; Building &gt; Output Folder &gt; Scrub output folders when cleaning projects</strong>
-			is checked, clicking <strong>Finish</strong> will scrub the &quot;bin&quot; directory in the file system before
-			generating the class files.
-		</p>
-    </li>
-    <li>
-    	Click <strong>Finish</strong>.
-    </li>
-    <li>
-    	You now have a Java project with a &quot;src&quot; folder which contains the sources of the &quot;Product&quot; directory.
-		<p><img src="../images/qs-DetectingExistingLayout4.png"  alt="Layout 4"></p>
-    </li>
-	</ol>
-	<p>
-		<em>Note: </em>This solution creates a &quot;.project&quot; file and a &quot;.classpath&quot; file in the 
-		&quot;Product&quot; directory. If you do not wish to have these files in the &quot;Product&quot; directory,
-		you should use linked folders as shown in the 
-		<a href="qs-WorkingWithExistingLayout1.htm">Sibling products in a common source tree</a> section.
-	</p>
-
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a><br>
-      <a href="../concepts/concepts-6.htm">Java views</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="../tasks/tasks-110.htm">Working with build paths</a><br>
-       <a href="../tasks/tasks-12.htm">Creating a new Java project</a><br>
-       <a href="../tasks/tasks-14.htm">Creating a Java project with source folders</a><br>
-       <a href="../tasks/tasks-26.htm">Creating a new source folder</a><br>
-       <a href="../tasks/tasks-45.htm">Using the Package Explorer</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-121.htm">New Java Project Wizard</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-EditorTemplates.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-EditorTemplates.htm
deleted file mode 100644
index 6c281e0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-EditorTemplates.htm
+++ /dev/null

@@ -1,133 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Using code templates
-    </title>
-  </head>
-  <body>
-    <h1>
-      Using code templates
-    </h1>
-    <p>
-      In this section you will use content assist to fill in a template for a common loop structure. 
-      Open <em>junit.samples.VectorTest.java</em> file in the Java editor if you do not already 
-      have it open.
-    </p>
-    <ol>
-      <li>
-        Start adding a new method by typing the following:<br>
-        <p><code>
-        public void testValues() {<br>
-        &nbsp;&nbsp;&nbsp; Integer[] expected= new Integer[3];<br>
-        &nbsp;&nbsp;&nbsp; for<br>
-        </code></p>
-      </li>
-      <li>
-        With the cursor at the end of <code>for</code>, press <kbd>Ctrl</kbd>+<kbd>Space</kbd> to enable content assist.&nbsp;
-        You will see a list of common templates for &quot;for&quot; loops.&nbsp;
-        When you single-click a template, you'll see the code for the template in
-        its help message.&nbsp; Note that the local array name is guessed automatically.
-		<p>
-		<img src="../images/qs-17b.png"  alt="Content assist for for">
-		</p>
-      </li>
-      <li>
-        Choose the <code>for - iterate over array</code>  entry and press <kbd>Enter</kbd> to confirm the template.&nbsp;
-        The template will be inserted in your source code.
-		<p>
-		<img src="../images/qs-17c.png"  alt="Inserted for template">
-		</p>
-      </li>
-      <li>
-        Next we change the name of the index variable from <em>i</em> to <em>e</em>. To do so simply press <kbd>e</kbd>, as
-        the index variable is automatically selected. 
-        Observe that the name of the index variable changes at all places. When inserting a template all references to the same variable
-        are connected to each other. So changing one changes all the other values 
-        as well.
-		<p>
-		<img src="../images/qs-17c1.png"  alt="Inserted for template">
-		</p>
-      </li>
-      <li>
-        Pressing the <kbd>tab</kbd> key moves the cursor to the next variable of the code template. This is the array
-        <em>expected</em>.
-		<p>
-		<img src="../images/qs-17c2.png"  alt="Inserted for template">
-		</p>
-        Since we don't want to change the name (it was guessed right by the template) we press
-        tab again, which leaves the template since there aren't any variables left to edit.
-      </li>
-      <li>
-        Complete the <code>for</code> loop as follows:<br>
-        <p><code>
-        for (int e= 0; e &lt; expected.length; e++) {<br>
-        &nbsp;&nbsp;&nbsp; expected[e]= new Integer(e + 1);<br>
-        }<br>
-        Integer[] actual= to<br>
-        </code></p>
-      </li>
-      <li>
-        With the cursor at the end of <code>to</code>, press <kbd>Ctrl</kbd>+<kbd>Space</kbd> to enable content assist. Pick <code>toarray - convert collection to array</code>
-        and press <kbd>Enter</kbd> to confirm the selection (or double-click the
-        selection).
-		<p>
-        <img src="../images/qs-17d.png"  alt="Inserted for template">
-		</p>
-		The template is inserted in the editor and <code>type</code> is highlighted and selected.
-		<p>
-		<img src="../images/qs-17e.png"  alt="Inserted for template">
-		</p>
-      </li>
-      <li>
-        Overwrite the selection by typing <code>Integer</code>. The type of array constructor changes
-        when you change the selection.
-      </li>
-      <li>
-        Press <kbd>Tab</kbd> to move the selection to <code>collection</code> and
-        overwrite it by typing <code>fFull</code>.
-		<p>
-		<img src="../images/qs-17f.png"  alt="Inserted for template">
-		</p>
-      </li>
-      <li>
-        Add the following lines of code to complete the method:<br>
-        <p><code>
-        assertEquals(expected.length, actual.length);<br>
-        for (int i= 0; i &lt; actual.length; i++)<br>
-        &nbsp;&nbsp;&nbsp; assertEquals(expected[i], actual[i]);<br>
-        </code></p>
-      </li>
-      <li>
-        Save the file.
-      </li>
-    </ol>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-       <a href="../concepts/concepts-7.htm">Java editor</a><br>
-       <a href="../concepts/ctemplates.htm">Templates</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-54.htm">Using the Java editor</a><br>
-       <a href="../tasks/tasks-171.htm">Using templates</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-       <a href="../reference/ref-preferences-templates.htm">Templates Preferences</a><br>
-       <a href="../reference/ref-21.htm">Java Editor Preferences</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ExtractMethod.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ExtractMethod.htm
deleted file mode 100644
index fd5ca40..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ExtractMethod.htm
+++ /dev/null

@@ -1,87 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Extracting a new method
-    </title>
-  </head>
-  <body>
-    <h1>
-      Extracting a new method
-    </h1>
-    <p>
-      In this section, you will improve the code of the constructor of <em>junit.framework.TestSuite</em>. 
-      To make the intent of the code clearer, you will extract the code that collects test cases 
-      from base classes into a new method called <em>collectTestMethods</em>.
-    </p>
-    <ol>
-      <li>
-        In the <em>junit.framework.TestSuite.java</em> file, select the following range of
-        code inside the <em>TestSuite(Class)</em> constructor:<br>
-        <p><code>
-        Class superClass= theClass;<br>
-        Vector names= new Vector();<br>
-        while(Test.class.isAssignableFrom(superClass)) {<br>
-        &nbsp;&nbsp;&nbsp; Method[] methods= superClass.getDeclaredMethods();<br>
-        &nbsp;&nbsp;&nbsp; for (int i= 0; i &lt; methods.length; i++) {<br>
-        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; addTestMethod(methods[i],names, constructor);<br>
-        &nbsp;&nbsp;&nbsp; }<br>
-        &nbsp;&nbsp;&nbsp; superClass= superClass.getSuperclass();<br>
-        }</code></p>
-      </li>
-      <li>
-        From the selection's context menu in the editor, select <strong>Refactor &gt; Extract Method...</strong>.
-		<p>
-		<img src="../images/qs-20.png"  alt="Context menu extract method">
-		</p>
-      </li>
-      <li>
-        In the <strong>Method Name</strong> field, type <em>collectInheritedTests</em>.
-		<p>
-		<img src="../images/qs-21.png"  alt="Extract method wizard data input page">
-		</p>
-      </li>
-      <li>
-        To preview the changes, press <strong>Preview&gt;</strong>.The preview page displays the 
-        changes that will be made. Press <strong>OK</strong> to extract the method.
-		<p>
-		<img src="../images/qs-22.png"  alt="Extract method preview page">
-		</p>
-      </li>
-      <li>
-        Go to the extracted method by selecting it in the Outline view.
-		<p>
-		<img src="../images/qs-23.png"  alt="Extracted method">
-		</p>
-      </li>
-    </ol>
-    <p>
-      <img src="../images/ngrelc.png"  border="0" alt="Related concepts">
-    </p>
-    <p>
-       <a href="../concepts/concepts-7.htm">Java editor</a><br>
-       <a href="../concepts/concepts-9.htm">Refactoring support</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png"  alt="Related tasks" border="0">
-    </p>
-    <p>
-      <a href="../tasks/tasks-54.htm">Using the Java editor</a><br>
-       <a href="../tasks/tasks-80.htm">Refactoring</a><br>
-       <a href="../tasks/tasks-83.htm">Refactoring with preview</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-       <a href="../reference/ref-154.htm">Extract Method Errors</a><br>
-       <a href="../reference/ref-13.htm">Java Preferences</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-LocalHistory.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-LocalHistory.htm
deleted file mode 100644
index d64bf39..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-LocalHistory.htm
+++ /dev/null

@@ -1,89 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Using the local history
-    </title>
-  </head>
-  <body>
-    <h1>
-      Using the local history
-    </h1>
-    <p>
-      In this section, you will use the local history feature to switch to a previously saved version of an individual 
-      Java element.
-    </p>
-    <ol>
-      <li>
-        Open <em>junit.samples.VectorTest.java</em> file in the Java editor and select the method
-        <em>testCapacity()</em> in the Outline view.
-      </li>
-      <li>
-      	Change the content of the method so that the 'for' statements reads as:<br>
-      	<p><code>
-      	for (int i= 0; i &lt; 99; i++)
-      	</code></p>
-	    Save the file by pressing Ctrl+S.
-      </li>
-      <li>
-        In the Outline view, select the method <code>testCapacity()</code>, and from its context menu, select <strong>Replace
-        With &gt; Element from Local History</strong>.
-      </li>
-      <li>
-        In the <strong>Replace Java Element from Local History</strong> dialog, the Local History list 
-        shows the various saved states of the method. The Java Source Compare pane shows details of the 
-        differences between the selected history resource and the existing workbench resource.
-		<p>
-		<img src="../images/qs-15.png"  alt="Replace from local history">
-		</p>
-      </li>
-      <li>
-       In the top pane, select the previous version, and click the <strong> Replace 
-       button</strong>. In the Java editor, the method is replaced with the selected history version.
-      </li>
-      <li>
-        Save the file.
-      </li>
-      <li>
-        Beside replacing a method's version with a previous one you can also restore Java elements that were 
-        deleted. Again, select the method <em>testCapacity()</em> in the Outline view, and from its context
-        menu, select <strong>Delete</strong>. Confirm the resulting dialog with <strong>Yes</strong> and
-        save the file. 
-      </li>
-      <li>
-        Now select the type <em>VectorTest</em> in the Outline view, and from its context menu, select
-        <strong>Restore from Local History...</strong>. Select and check the method <em>testCapacity()</em>
-        in the Available Java Elements pane. As before, the Local History pane shows the versions saved 
-        in the local history.
-		<p>
-		<img src="../images/qs-15a.png"  alt="Restore from local history">
-		</p>
-      </li>
-      <li>
-        In the Local History pane, select the earlier working version and then click <strong>Restore</strong>.
-      </li>
-      <li>
-        Press <strong>Ctrl+S</strong> to save the file.
-      </li>
-    </ol>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-       <a href="../concepts/concepts-7.htm">Java editor</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="../tasks/tasks-54.htm">Using the Java editor</a><br>
-       <a href="../tasks/tasks-62.htm">Using the local history</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-Navigate.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-Navigate.htm
deleted file mode 100644
index a456258..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-Navigate.htm
+++ /dev/null

@@ -1,72 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Navigate to a Java element's declaration
-    </title>
-  </head>
-  <body>
-    <h1>
-      Navigate to a Java element's declaration
-    </h1>
-    
-	<ol>
-	  <li> Open the <em>junit.samples.money.MoneyTest.java</em> file in the Java editor. 
-	  </li>
-	  <li> On the first line of the MoneyTest class declaration, select the
-	    superclass TestCase and either 
-	    <ul>
-	      <li> from the menu bar select Navigate &gt; Open Declaration or </li>
-	      <li> press <kbd>F3</kbd>. </li>
-	    </ul>	    
-		<p>
-	    <img src="../images/qs-24.png"  alt="Menu open declaration">
-		</p>
-	    The TestCase class opens in the editor area and is also represented in 
-	    the Outline view. <br><em>Note: This command also works on methods and fields.</em>
-		<p>
-	    <img src="../images/qs-25.png"  alt="Opened declaration">
-		</p>
-	  </li>
-	  <li> With the <em>TestCase.java</em> editor open and the class declaration
-	    selected: 
-	    <ul>
-	      <li> from the menu bar select Navigate &gt; Open Type Hierarchy or </li>
-	      <li> press <kbd>F4</kbd>. </li>
-	    </ul>
-		<p>
-	    <img src="../images/qs-26.png"  alt="Menu open type hierarchy">
-		</p>
-	  </li>
-	  <li> 
-	    The Hierarchy view opens with the TestCase class displayed.
-		<p>
-	    <img src="../images/qs-27.png"  alt="Type hierarchy view">
-		</p>
-	    <em>Note: You can also open editors on types and methods in the Hierarchy view.</em> 
-	  </li>
-	</ol>
-	
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="../tasks/tasks-37.htm">Using the Hierarchy view</a><br>
-       <a href="../tasks/tasks-39.htm">Opening a type hierarchy on a Java element</a><br>
-       <a href="../tasks/tasks-40.htm">Opening a type hierarchy on the current text selection</a><br>
-       <a href="../tasks/tasks-73.htm">Opening an editor for a selected element</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-       <a href="../reference/ref-type-hierarchy.htm">Type Hierarchy View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OpenJavaEditor.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OpenJavaEditor.htm
deleted file mode 100644
index ebb1bc4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OpenJavaEditor.htm
+++ /dev/null

@@ -1,109 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Opening a Java editor
-    </title>
-  </head>
-  <body>
-    <h1>
-      Opening a Java editor
-    </h1>
-    <p>
-      In this section, you will learn how to open an editor for Java files.  You will also learn about some of the basic Java editor features.
-    </p>
-    <p>
-		<ol>
-		  <li> Expand the package <em>junit.samples</em> and select the file <em>VectorTest.java</em>.&nbsp;
-		    You can open <em>VectorTest.java</em> in the Java editor by double clicking on
-		    it. In general you can open a Java editor for Java files, types, methods and fields by simply double 
-		    clicking on them. For example, to open the editor directly on the method <em>testClone</em>
-		    defined in <em>VectorTest.java</em>, expand the file in the Package Explorer and double click on the method.</li>
-		  <li> Notice the syntax highlighting.&nbsp; Different kinds of elements in the
-		    Java source are rendered in unique colors.&nbsp; Examples of Java source
-		    elements that are rendered differently are: 
-		    <ul>
-		      <li> Regular comments </li>
-		      <li> Javadoc comments </li>
-		      <li> Keywords </li>
-		      <li> Strings. </li>
-		    </ul>
-			<p>
-		    <img src="../images/qs-8.png"  alt="Syntax highlighting">
-			</p>
-		  </li>
-		  <li> Look at the Outline view. It displays an outline of the Java file including 
-		    the package declaration, import declarations, fields, types and methods. The 
-		    Outline view uses icons to annotate Java elements.&nbsp; For example, icons indicate whether a Java element is 
-		    static (<img src="../images/org.eclipse.jdt.ui/ovr16/static_co.png" alt="S" >), 
-		    abstract (<img src="../images/org.eclipse.jdt.ui/ovr16/abstract_co.png" alt="A" >),
-		    or final (<img src="../images/org.eclipse.jdt.ui/ovr16/final_co.png" alt="F" >).&nbsp; Different icons show you whether a method overrides a method from a 
-		    base class (<img src="../images/org.eclipse.jdt.ui/ovr16/over_co.png"  alt="overridden">
-) or 
-		    when it implements a method from an interface (<img src="../images/org.eclipse.jdt.ui/ovr16/implm_co.png"  alt="implements">
-).
-			<p>	
-		    <img src="../images/qs-9.png"  alt="Outline view">
-			</p>
-		  </li>
-		  <li> Toggle the <strong>Hide Fields</strong>, <strong>Hide Static Members</strong>, 
-		    and <strong>Hide Non-Public Members</strong> buttons in the Outline view toolbar 
-		    to filter the view's display.
-			Before going to the next step make sure that <STRONG>Hide Non-Public
-	Members</STRONG>
-	button is not pressed.<p>
-			<img src="../images/qs-10.png"  alt="Outline view tool bar"> 
-			</p>
-		  </li>
-		  <li> You can edit source code by viewing the whole Java file, or you can narrow 
-		    the view to a single Java element. The toolbar includes a button, <strong>Show Source of Selected 
-		    Element Only</strong>, that will cause only the source code of the selected
-		    outline element to be displayed in the Java editor.&nbsp; In the example
-		    below, only the <em>setUp()</em> method is displayed.
-			<p>
-			<img src="../images/qs-11.png"  alt="Show selected element only tool bar button"> 
-			</p>
-		  </li>
-		  <li> Press the <strong>Show Source of Selected Element Only</strong> button 
-		    again to see the whole Java file again. In the Outline view, select different 
-		    elements and note that they are again displayed in a whole file view 
-		    in the editor. The Outline view selection now contains a range indicator 
-		    on the vertical ruler on the left border of the Java editor that indicates
-		    the range of the selected element.
-			<p>
-			<img src="../images/qs-12.png"  alt="Range indicator"> 
-			</p>
-		  </li>
-		</ol>
-	</p>	
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-6.htm">Java views</a><br>
-       <a href="../concepts/concepts-7.htm">Java editor</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-54.htm">Using the Java editor</a><br>
-       <a href="../tasks/tasks-2.htm">Showing and hiding elements</a><br>
-       <a href="../tasks/tasks-6.htm">Showing single elements or whole Java files</a><br>
-       <a href="../tasks/tasks-195.htm">Sorting elements in Java views</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-view-outline.htm">Java Outline View</a><br>
-       <a href="../reference/ref-21.htm">Java Editor Preferences</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OrganizeImports.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OrganizeImports.htm
deleted file mode 100644
index 7d08e23..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OrganizeImports.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Organizing import statements
-    </title>
-  </head>
-  <body>
-    <h1>
-      Organizing import statements
-    </h1>
-    <p>
-      In this section you will organize the import declarations in your
-      source code.&nbsp; Open <em>junit.samples.VectorTest.java</em> file in the Java
-      editor if you do not already have it open.
-    </p>
-    <ol>
-      <li>
-        Delete the import declarations by selecting them in the Outline view and selecting 
-        <strong>Delete</strong> from the context menu. Confirm the resulting dialog with
-        <strong>Yes</strong>.
-        You will see numerous compiler warnings in the vertical ruler since the
-        types used in the method are no longer imported.
-		<p>
-		<img src="../images/qs-18.png"  alt="Outline view context menu">
-		</p>
-      </li>
-      <li>
-        From the context menu in the editor, select <strong>Source &gt; Organize Imports</strong>. The required import statements are added to the beginning of your code below the package
-        declaration.
-		<p>
-		<img src="../images/qs-19.png"  alt="Organize imports">
-		</p>
-        You can also choose <strong>Organize Imports</strong> from the context menu of the
-        import declarations in the Outline view.<br>
-        Note: You can specify the order of the import declarations 
-        in preferences <strong>Window &gt; Preferences &gt; Java &gt; Code Style &gt; Organize Imports</strong>.
-      </li>
-      <li>
-        Save the file.
-      </li>
-    </ol>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-       <a href="../concepts/concepts-7.htm">Java editor</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-58.htm">Managing import statements</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-       <a href="../reference/ref-22.htm">Organize Imports Preferences</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OrganizingSources.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OrganizingSources.htm
deleted file mode 100644
index 9e3b8e7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OrganizingSources.htm
+++ /dev/null

@@ -1,105 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Organizing sources
-    </title>
-  </head>
-  <body>
-    <h1>
-      Organizing sources
-    </h1>
-
-    <h3>Layout on file system</h3>
-    <ul>
-    <li>
-		In this section, you will create a new Java project and organize your sources in separate folders. This will 
-		prepare you for handling more complex layouts.
-    </li>
-	<li>Let's assume you want to put your sources in one folder and your tests in another folder:</li>
-	<p><img src="../images/qs-OrganizeSources1.png"  alt="Layout 1"></p>
-	</ul>
-    <h3>Steps for defining a corresponding project</h3>
-    <ol>
-	<li>
-		<p>Open a Java perspective, select the menu item <strong>File &gt; New &gt; Project...</strong>. to open the <strong>New Project</strong> wizard.</p>
-	</li>
-	<li>
-        <p>Select <strong>Java project</strong> in the list of wizards and click <strong>Next</strong>.</p>
-    </li>
-    <li>
-    	<p>On the next page, type &quot;MyProject&quot; in the <strong>Project name</strong> field.</p>
-    </li>
-    <li>
-    	<p>In <strong>Project layout</strong> group, change selection to <strong>Create separate source and output folders</strong>
-    	and edit <strong>Configure default...</strong> to modify <strong>Source folder name</strong> from "src" to "sources".</p>
-		<p><img src="../images/qs-OrganizeSources2.png"  alt="Layout 2"></p>
-    </li>
-    <li>
-    	Click <strong>OK</strong> to return on New Java Project wizard and then click <strong>Next</strong>.
-		<p><img src="../images/qs-OrganizeSources3.png"  alt="Layout 3"></p>
-	</li>
-    <li>
-    	Click <strong>Finish</strong>
-    </li>
-    <li>
-    	<p>Edit project &quot;MyProject&quot;properties and select <strong>Java Builder Path</strong> page.</p>
-		<p>On <strong>Source</strong> tab, click <strong>Add Folder...</strong>.</p>
-    	<p><img src="../images/qs-OrganizeSources4.png"  alt="Layout 4"></p>
-    </li>
-	<li>
-		<p>On <strong>Source Folder Selection</strong> click <strong>Create New Folder...</strong>.</p>
-    	<p><img src="../images/qs-OrganizeSources5.png"  alt="Layout 5"></p>
-    </li>
-	<li>
-		<p>In <strong>New Folder</strong> dialog, type &quot;tests&quot; in the <strong>Folder name</strong> field.</p>
-    	<p><img src="../images/qs-OrganizeSources6.png"  alt="Layout 6"></p>
-    </li>
-	<li>
-		Click <strong>OK</strong>  to close the dialog.
-	</li>
-    <li>
-    	<p>Your project setup now looks as follows:</p>
-	    <p><img src="../images/qs-OrganizeSources7.png"  alt="Layout 7"></p>
-    </li>
-    <li>
-    	<p>Click <strong>OK</strong></p>
-    </li>
-    <li>
-    	You now have a Java project with a <i><code>sources</code></i> and a <i><code>tests</code></i> folders. You can start adding classes
-    	to these folders or you can copy them using drag and drop.
-	    <p><img src="../images/qs-OrganizeSources8.png"  alt="Layout 8"></p>
-    </li>
-	</ol>    
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a><br>
-      <a href="../concepts/concepts-6.htm">Java views</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="../tasks/tasks-110.htm">Working with build paths</a><br>
-       <a href="../tasks/tasks-12.htm">Creating a new Java project</a><br>
-       <a href="../tasks/tasks-14.htm">Creating a Java project with source folders</a><br>
-       <a href="../tasks/tasks-26.htm">Creating a new source folder</a><br>
-       <a href="../tasks/tasks-45.htm">Using the Package Explorer</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-121.htm">New Java Project Wizard</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ProjectConfiguration.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ProjectConfiguration.htm
deleted file mode 100644
index 47bf1b8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ProjectConfiguration.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Project configuration tutorial
-    </title>
-  </head>
-  <body>
-    <h1>
-    	Project configuration tutorial
-    </h1>
-    <p>
-    	In this section, you will create and configure a new Java project to use source folders and 
-    	to match some existing layout on the file system. Some typical layouts have been identified. 
-    	Choose the sub-section that matches your layout. 
-    </p>
-
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a><br>
-      <a href="../concepts/concepts-6.htm">Java views</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="../tasks/tasks-110.htm">Working with build paths</a><br>
-       <a href="../tasks/tasks-12.htm">Creating a new Java project</a><br>
-       <a href="../tasks/tasks-14.htm">Creating a Java project with source folders</a><br>
-       <a href="../tasks/tasks-26.htm">Creating a new source folder</a><br>
-       <a href="../tasks/tasks-45.htm">Using the Package Explorer</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-121.htm">New Java Project Wizard</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout1.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout1.htm
deleted file mode 100644
index 484ca88..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout1.htm
+++ /dev/null

@@ -1,93 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Sibling products in a common source tree
-    </title>
-  </head>
-  <body>
-    <h1>
-      Sibling products in a common source tree
-    </h1>
-    <h3>Layout on file system</h3>
-    <ul>
-	<li>The source files for products are laid out in one big directory that is version and configuration managed outside Eclipse.</li>
-	<li>The source directory contains two siblings directories <i><code>Product1</code></i> and <i><code>Product2</code></i>.</li>
-	<p><img src="../images/qs-WorkingWithExistingLayout10.png"  alt="Layout 10"></p>
-	</ul>
-    <h3>Steps for defining corresponding projects</h3>
-    <ol>
-	<li>
-		<p>Open a Java perspective, select the menu item <strong>File &gt; New &gt; Project...</strong>. to open the <strong>New Project</strong> wizard.</p>
-	</li>
-	<li>
-        <p>Select <strong>Java project</strong> in the list of wizards and click <strong>Next</strong>.</p>
-    </li>
-    <li>
-    	<p>On the next page, type &quot;Product1&quot; in the <strong>Project name</strong> field. Click <strong>Next</strong>.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout41.png"  alt="Layout 41"></p>
-	</li>
-	<li>
-		<p>On the next page, Select &quot;Product1&quot; source folder.</p>
-		<p>Click <strong>Link Additional Source to Project</strong> button <img src="../images/add_linked_source_to_buildpath.png"  alt="Link Additional Source to Project"> in view bar.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout42.png"  alt="Layout 42"></p>
-	</li>
-	<li>
-		<p>In <strong>Link Additional Source</strong> click <strong>Browse....</strong> and choose the <i><code>D:\Product1\JavaSourceFiles</code></i> directory.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout11.png"  alt="Layout 11"></p>
-	</li>
-	<li>
-		Click <strong>OK</strong> to close the dialog.
-	</li>
-	<li>
-		<p>Click <strong>OK</strong> in confirmation dialog to have &quot;/Product1/bin&quot; as default output folder.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout12.png"  alt="Layout 12"></p>
-	</li>
-	<li>
-		<p>Your project source setup now looks as follows:</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout13.png"  alt="Layout 13"></p>
-	</li>
-    <li>
-    	<p>Click <strong>Finish</strong>.</p>
-    </li>
-    <li>
-    	<p>Repeat these steps for  &quot;Product2&quot;.</p>
-    </li>
-    <li>
-    	<p>You now have two Java projects which respectively contain the sources of &quot;Product1&quot; and &quot;Product2&quot;.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout14.png"  alt="Layout 14"></p>
-    </li>
-	</ol>
-
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a><br>
-      <a href="../concepts/concepts-6.htm">Java views</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="../tasks/tasks-110.htm">Working with build paths</a><br>
-       <a href="../tasks/tasks-12.htm">Creating a new Java project</a><br>
-       <a href="../tasks/tasks-14.htm">Creating a Java project with source folders</a><br>
-       <a href="../tasks/tasks-26.htm">Creating a new source folder</a><br>
-       <a href="../tasks/tasks-45.htm">Using the Package Explorer</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-121.htm">New Java Project Wizard</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout2.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout2.htm
deleted file mode 100644
index 342e456..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout2.htm
+++ /dev/null

@@ -1,112 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Overlapping products in a common source tree
-    </title>
-  </head>
-  <body>
-    <h1>
-      Overlapping products in a common source tree
-    </h1>
-    <h3>Layout on file system</h3>
-    <ul>
-	<li>The Java source files for products are all held in a single main directory.</li>
-	<li>Products are separated into four siblings packages <i><code>Product1</code></i>, <i><code>Product2</code></i>, <i><code>Product3</code></i> and <i><code>Product4</code></i>.</li>
-	<p><img src="../images/qs-WorkingWithExistingLayout20.png"  alt="Layout 20"></p>
-	</ul>
-    <h3>Steps for defining corresponding &quot;Product1&quot; and &quot;Product2&quot; projects</h3>
-    <ol>
-	<li>
-		<p>Open a Java perspective, select the menu item <strong>File &gt; New &gt; Project...</strong>. to open the <strong>New Project</strong> wizard.</p>
-	</li>
-	<li>
-        <p>Select <strong>Java project</strong> in the list of wizards and click <strong>Next</strong>.</p>
-    </li>
-    <li>
-    	<p>On the next page, type &quot;Product1&quot; in the <strong>Project name</strong> field. Click <strong>Next</strong>.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout41.png"  alt="Layout 41"></p>
-	</li>
-	<li>
-		<p>On the next page, Select &quot;Product1&quot; source folder.</p>
-		<p>Click <strong>Link Additional Source to Project</strong> button <img src="../images/add_linked_source_to_buildpath.png"  alt="Link Additional Source to Project"> in view bar.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout42.png"  alt="Layout 42"></p>
-	</li>
-	<li>
-		<p>In <strong>Link Additional Source</strong> click <strong>Browse....</strong> and choose the <i><code>D:\AllJavaSourceFiles</code></i> directory.</p>
-		<p>Type &quot;src&quot; in <strong>Folder name</strong>.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout21.png"  alt="Layout 21"></p>
-	</li>
-	<li>
-		<p>Click <strong>OK</strong> to close the dialog.</p>
-	</li>
-	<li>
-		<p>Click <strong>OK</strong> in confirmation dialog to have &quot;Product1/bin&quot; as default output folder.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout12.png"  alt="Layout 12"></p>
-	</li>
-	<li>
-		<p>Expand the &quot;src&quot; source folder. Select all packages you want to exclude and exclude them using popup-menu.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout22.png"  alt="Layout 22"></p>
-	</li>
-	<li>
-		<p>Your project source setup now looks as follows:</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout23.png"  alt="Layout 23"></p>
-	</li>
-	<li>
-    	<p>Click <strong>Finish</strong>.</p>
-	</li>
-    <li>
-    	<p>Copy &quot;Product1&quot; project and paste it as &quot;Product2&quot;.</p>
-    	<p>Edit &quot;Product2&quot; project properties and go on <strong>Java Build Path</strong> page.</p>
-    	<p>Select <strong>Excluded</strong> and click <strong>Edit...</strong>.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout24.png"  alt="Layout 24"></p>
-    </li>
-    <li>
-    	<p>In <strong>Inclusion and Exclusion Patterns</strong>, select &quot;com/xyz/product2&quot; and click <strong>Edit...</strong>.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout25.png"  alt="Layout 25"></p>
-    </li>
-    <li>
-    	<p>Change &quot;com/xyz/product2&quot; to &quot;com/xyz/product1&quot; instead.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout26.png"  alt="Layout 26"></p>
-    </li>
-    <li>
-		<p>Click <strong>OK</strong> three times to valid and close all dialogs.</p>
-    </li>
-    <li>
-    	<p>You now have two Java projects which respectively contain the sources of &quot;product1&quot;, &quot;product2&quot;.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout27.png"  alt="Layout 27"></p>
-    </li>
-	</ol>
-		
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a><br>
-      <a href="../concepts/concepts-6.htm">Java views</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="../tasks/tasks-110.htm">Working with build paths</a><br>
-       <a href="../tasks/tasks-12.htm">Creating a new Java project</a><br>
-       <a href="../tasks/tasks-14.htm">Creating a Java project with source folders</a><br>
-       <a href="../tasks/tasks-26.htm">Creating a new source folder</a><br>
-       <a href="../tasks/tasks-45.htm">Using the Package Explorer</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-121.htm">New Java Project Wizard</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout3.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout3.htm
deleted file mode 100644
index 0516a69..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout3.htm
+++ /dev/null

@@ -1,111 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Product with nested tests
-    </title>
-  </head>
-  <body>
-    <h1>
-      Product with nested tests
-    </h1>
-    <h3>Layout on file system</h3>
-    <ul>
-	<li>The Java source files for a product are laid out in a package directory.</li>
-	<li>Source files of tests are laid out in a nested package directory.</li>
-	<p><img src="../images/qs-WorkingWithExistingLayout30.png"  alt="Layout 30"></p>
-	</ul>
-    <h3>Steps for defining a corresponding project</h3>
-    <ol>
-	<li>
-		<p>Open a Java perspective, select the menu item <strong>File &gt; New &gt; Project...</strong>. to open the <strong>New Project</strong> wizard.</p>
-	</li>
-	<li>
-        <p>Select <strong>Java project</strong> in the list of wizards and click <strong>Next</strong>.</p>
-    </li>
-    <li>
-    	<p>On the next page, type &quot;Product1&quot; in the <strong>Project name</strong> field. Click <strong>Next</strong>.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout41.png"  alt="Layout 41"></p>
-	</li>
-	<li>
-		<p>On the next page, Select &quot;Product1&quot; source folder.</p>
-		<p>Click <strong>Link Additional Source to Project</strong> button <img src="../images/add_linked_source_to_buildpath.png"  alt="Link Additional Source to Project"> in view bar.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout42.png"  alt="Layout 42"></p>
-	</li>
-	<li>
-		<p>In <strong>Link Additional Source</strong> click <strong>Browse....</strong> and choose the <i><code>D:\Product1\JavaSourceFiles</code></i> directory.</p>
-		<p>Type &quot;src&quot; in the <strong>Folder name</strong> field.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout31.png"  alt="Layout 31"></p>
-	</li>
-	<li>
-		<p>Click <strong>OK</strong> to close the dialog.</p>
-	</li>
-	<li>
-		<p>Click <strong>OK</strong> in confirmation dialog to have &quot;Product1/bin&quot; as default output folder.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout12.png"  alt="Layout 12"></p>
-	</li>
-	<li>
-		<p>Your project source setup now looks as follows:</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout32.png"  alt="Layout 32"></p>
-	</li>
-    <li>
-    	Click <strong>Finish</strong>.
-    </li>
-    <li>
-    	<p>Edit project &quot;Product1&quot;properties and select <strong>Java Builder Path</strong> page.</p>
-		<p>On <strong>Source</strong> tab, click <strong>Add Folder...</strong>.</p>
-    	<p><img src="../images/qs-WorkingWithExistingLayout33.png"  alt="Layout 33"></p>
-    </li>
-	<li>
-		<p>Expand &quot;Product1&quot;, then &quot;src&quot; and select &quot;tests&quot;.</p>
-    	<p><img src="../images/qs-WorkingWithExistingLayout34.png"  alt="Layout 34"></p>
-    </li>
-	<li>
-		<p>Click <strong>OK</strong>  to close the dialog. You get an information dialog saying that exclusion filters have been added. Click <strong>OK</strong>.</p>
-	</li>
-    <li>
-    	<p>Your project setup now looks as follows:</p>
-	    <p><img src="../images/qs-WorkingWithExistingLayout35.png"  alt="Layout 35"></p>
-    </li>
-    <li>
-    	<p>Click <strong>OK</strong>.</p>
-    </li>
-    <li>
-    	You now have a Java project with a &quot;src&quot; folder and a &quot;tests&quot; folder which contain respectively 
-    	the <i><code>D:\Product1\JavaSourceFiles</code></i> directory and the <i><code>D:\Product1\JavaSourceFiles\tests</code></i> directory.
-		<p><img src="../images/qs-WorkingWithExistingLayout36.png"  alt="Layout 36"></p>
-    </li>
-	</ol>
-
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a><br>
-      <a href="../concepts/concepts-6.htm">Java views</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="../tasks/tasks-110.htm">Working with build paths</a><br>
-       <a href="../tasks/tasks-12.htm">Creating a new Java project</a><br>
-       <a href="../tasks/tasks-14.htm">Creating a Java project with source folders</a><br>
-       <a href="../tasks/tasks-26.htm">Creating a new source folder</a><br>
-       <a href="../tasks/tasks-45.htm">Using the Package Explorer</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-121.htm">New Java Project Wizard</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout4.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout4.htm
deleted file mode 100644
index 992b9b9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout4.htm
+++ /dev/null

@@ -1,124 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Products sharing a common source framework
-    </title>
-  </head>
-  <body>
-    <h1>
-      Products sharing a common source framework
-    </h1>
-    <h3>Layout on file system</h3>
-    <ul>
-	<li>The Java source files for two products require a common framework.</li>
-	<li>Projects and common framework are in separate directories which have their own source and output folders.</li>
-	<p><img src="../images/qs-WorkingWithExistingLayout40.png"  alt="Layout 40"></p>
-	</ul>
-    <h3>Steps for defining corresponding projects</h3>
-	<ol>
-	<li>
-		<p>Open a Java perspective, select the menu item <strong>File &gt; New &gt; Project...</strong>. to open the <strong>New Project</strong> wizard.</p>
-	</li>
-	<li>
-        <p>Select <strong>Java project</strong> in the list of wizards and click <strong>Next</strong>.</p>
-    </li>
-    <li>
-    	<p>On the next page, type &quot;Product1&quot; in the <strong>Project name</strong> field. Click <strong>Next</strong>.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout41.png"  alt="Layout 41"></p>
-	</li>
-	<li>
-		<p>On the next page, Select &quot;Product1&quot; source folder.</p>
-		<p>Click <strong>Link Additional Source to Project</strong> button <img src="../images/add_linked_source_to_buildpath.png"  alt="Link Additional Source to Project"> in view bar.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout42.png"  alt="Layout 42"></p>
-	</li>
-	<li>
-		<p>In <strong>Link Additional Source</strong> click <strong>Browse....</strong> and choose the <i><code>D:\Product1\JavaSourceFiles</code></i> directory.</p>
-		<p>Type &quot;src&quot; in the <strong>Folder name</strong> field.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout31.png"  alt="Layout 31"></p>
-	</li>
-	<li>
-		<p>Click <strong>OK</strong> to close the dialog.</p>
-	</li>
-	<li>
-		<p>Click <strong>OK</strong> in confirmation dialog to have &quot;Product1/bin&quot; as default output folder.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout12.png"  alt="Layout 12"></p>
-	</li>
-	<li>
-		<p>Your project source setup now looks as follows:</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout43.png"  alt="Layout 43"></p>
-	</li>
-    <li>
-    	Click <strong>Finish</strong>.
-    </li>
-    <li>
-    	<p>Edit project &quot;Product1&quot;properties and select <strong>Java Builder Path</strong> page.</p>
-		<p>On <strong>Source</strong> tab, click <strong>Add Folder...</strong>.</p>
-    	<p><img src="../images/qs-WorkingWithExistingLayout33.png"  alt="Layout 33"></p>
-    </li>
-	<li>
-		<p>On <strong>Source Folder Selection</strong> click <strong>Create New Folder...</strong>.</p>
-    	<p><img src="../images/qs-WorkingWithExistingLayout44.png"  alt="Layout 44"></p>
-    </li>
-	<li>
-		<p>In <strong>New Folder</strong>, type &quot;src-common&quot; in the <strong>Folder name</strong> field.</p>
-		<p>Click <strong>Advanced&gt;&gt;</strong> and check <strong>Link to folder in the file system</strong>.</p>
-		<p>Then click <strong>Browse....</strong> and choose the <i><code>D:\Framework\JavaSourceFiles</code></i> directory.</p>
-    	<p><img src="../images/qs-WorkingWithExistingLayout45.png"  alt="Layout 45"></p>
-    </li>
-	<li>
-		<p>Click <strong>OK</strong> twice to close dialogs.</p>
-	</li>
-    <li>
-    	<p>Your project setup now looks as follows:</p>
-	    <p><img src="../images/qs-WorkingWithExistingLayout46.png"  alt="Layout 46"></p>
-    </li>
-    <li>
-    	Click <strong>OK</strong>.
-    </li>
-    <li>
-    	<p>Repeat these steps for &quot;Product2&quot;.</p>
-    </li>
-    <li>
-    	You now have two Java projects which respectively contain the sources of &quot;Product1&quot; and &quot;Product2&quot;
-    	and which are using the sources of &quot;Framework&quot;.
-		<p><img src="../images/qs-WorkingWithExistingLayout47.png"  alt="Layout 47"></p>
-    </li>
-	</ol>
-	<em>Note: </em>Files in &quot;src-common&quot; are shared. So editing &quot;Common.java&quot; in &quot;Product1&quot;
-	will modify &quot;Common.java&quot; in &quot;Product2&quot;. However they are compiled in the context of their
-	respective projects. Two &quot;Common.class&quot; files will be generated; one for each project. If the two projects have 
-	different compiler options, then different errors could be reported on each &quot;Common.java&quot; file.
-	
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a><br>
-      <a href="../concepts/concepts-6.htm">Java views</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="../tasks/tasks-110.htm">Working with build paths</a><br>
-       <a href="../tasks/tasks-12.htm">Creating a new Java project</a><br>
-       <a href="../tasks/tasks-14.htm">Creating a Java project with source folders</a><br>
-       <a href="../tasks/tasks-26.htm">Creating a new source folder</a><br>
-       <a href="../tasks/tasks-45.htm">Using the Package Explorer</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-121.htm">New Java Project Wizard</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout5.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout5.htm
deleted file mode 100644
index 684ce3c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout5.htm
+++ /dev/null

@@ -1,121 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Nesting resources in output directory
-    </title>
-  </head>
-  <body>
-    <h1>
-      Nesting resources in output directory
-    </h1>
-    <h3>Layout on file system</h3>
-    <ul>
-	<li>The Java source files for a product are laid out both in <i><code>sources</code></i> and <i><code>deliverables</code></i> directories.</li>
-	<li>All Java class files are laid out in <i><code>deliverables</code></i> directory.</li>
-	<li>Project needs to use some libraries located in <i><code>deliverables/libraries</code></i> directory:</li>
-	<p><img src="../images/qs-WorkingWithExistingLayout5.png"  alt="Layout 5"></p>
-	</ul>
-    <h3>Steps for defining a corresponding project</h3>
-	<ol>
-	<li>
-		<p>Open a Java perspective, select the menu item <strong>File &gt; New &gt; Project...</strong>. to open the <strong>New Project</strong> wizard.</p>
-	</li>
-	<li>
-        <p>Select <strong>Java project</strong> in the list of wizards and click <strong>Next</strong>.</p>
-    </li>
-    <li>
-    	<p>On the next page, type &quot;Product&quot; in the <strong>Project name</strong> field. Click <strong>Next</strong>.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout50.png"  alt="Layout 50"></p>
-	</li>
-	<li>
-		<p>On the next page, Type &quot;Product/deliverables&quot; in <strong>Default output folder</strong> field.</p>
-		<p>Select &quot;Product1&quot; source folder.</p>
-		<p>Click <strong>Link Additional Source to Project</strong> button <img src="../images/add_linked_source_to_buildpath.png"  alt="Link Additional Source to Project"> in view bar.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout51.png"  alt="Layout 51"></p>
-	</li>
-	<li>
-		<p>In <strong>Link Additional Source</strong> click <strong>Browse....</strong> and choose the <i><code>D:\Product\sources</code></i> directory.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout52.png"  alt="Layout 52"></p>
-	</li>
-	<li>
-		<p>Click <strong>OK</strong> to close the dialog.</p>
-	</li>
-	<li>
-		<p>Click <strong>OK</strong> in confirmation dialog to remove the project as source folder.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout53.png"  alt="Layout 53"></p>
-	</li>
-	<li>
-		<p>Repeat previous steps to create source folder "deliverables" linked to <i><code>D:\Product\deliverables</code></i> directory.</p>
-		<p>Click <strong>Finish</strong>.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout54.png"  alt="Layout 54"></p>
-	</li>
-    <li>
-    	<p>Edit project &quot;Product1&quot;properties and select <strong>Java Builder Path</strong> page.</p>
-		<p>Expand &quot;Product/deliverables&quot;, select <strong>Excluded</strong> and click <strong>Edit...</strong>.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout55.png"  alt="Layout 55"></p>
-	</li>
-	<li>
-		<p>Click <strong>Add...</strong> in <strong>Exclusion patterns</strong> part
-		 of the <strong>Inclusion and Exclusion Patterns</strong> dialog.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout56.png"  alt="Layout 56"></p>
-	</li>
-	<li>
-		<p>Type &quot;libraries/&quot; in <strong>Add Exclusion Pattern</strong> dialog and click <strong>OK</strong> to validate and close the dialog.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout57.png"  alt="Layout 57"></p>
-	</li>
-	<li>
-		<p>Click <strong>OK</strong> twice to close dialogs.</p>
-	</li>
-	<li>
-		<p>Your project source setup now looks as follows:</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout58.png"  alt="Layout 58"></p>
-	</li>
-    <li>
-    	<p>Select <strong>Libraries</strong> tab.</p>
-    	<p>Click on <strong>Add JARs...</strong>.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout59.png"  alt="Layout 59"></p>
-    </li>
-    <li>
-    	<p>Expand &quot;Product&quot; hierarchy to select jar files in &quot;libraries&quot; directory</p>
-    	<p>Click <strong>OK</strong>.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout5A.png"  alt="Layout 5A"></p>
-    </li>
-    <li>
-    	You now have a Java project with a &quot;sources&quot; folder and an output folder which contains nested library resources.
-		<p><img src="../images/qs-WorkingWithExistingLayout5B.png"  alt="Layout 5B"></p>
-    </li>
-	</ol>
-
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a><br>
-      <a href="../concepts/concepts-6.htm">Java views</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="../tasks/tasks-110.htm">Working with build paths</a><br>
-       <a href="../tasks/tasks-12.htm">Creating a new Java project</a><br>
-       <a href="../tasks/tasks-14.htm">Creating a Java project with source folders</a><br>
-       <a href="../tasks/tasks-26.htm">Creating a new source folder</a><br>
-       <a href="../tasks/tasks-45.htm">Using the Package Explorer</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-121.htm">New Java Project Wizard</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout6.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout6.htm
deleted file mode 100644
index 354fe69..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout6.htm
+++ /dev/null

@@ -1,140 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Project using a source framework with restricted access
-    </title>
-  </head>
-  <body>
-    <h1>
-      Project using a source framework with restricted access
-    </h1>
-    <h3>Layout on file system</h3>
-    <ul>
-	<li>The Java source files for a product requires a source framework.</li>
-	<li>&quot;Product&quot; and &quot;Framework&quot; are in separate directories which have their own source and output folders.</li>
-	<p><img src="../images/qs-WorkingWithExistingLayout60.png"  alt="Layout 60"></p>
-	</ul>
-    <h3>Steps for defining corresponding projects</h3>
-	<ol>
-	<li>
-		<p>Open a Java perspective, select the menu item <strong>File &gt; New &gt; Project...</strong>. to open the <strong>New Project</strong> wizard.</p>
-	</li>
-	<li>
-        <p>Select <strong>Java project</strong> in the list of wizards and click <strong>Next</strong>.</p>
-    </li>
-    <li>
-    	<p>On the next page, type &quot;Framework&quot; in the <strong>Project name</strong> field.</p>
-    </li>
-    <li>
-    	<p>In <strong>Contents</strong> group, change selection to <strong>Create project from existing source</strong>.</p>
-    	<p>Click <strong>Browse...</strong> and choose the <i><code>D:\Framework</code></i> directory.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout61.png"  alt="Layout 61"></p>
-    	<p>Click <strong>Next</strong>.</p>
-	</li>
-	<li>
-		<p>On the next page, verify that directory <i><code>JavaSourceFiles</code></i> has been automatically added as source folder.</p>
-		<p>Expand it to preview your project source folder contents:</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout62.png"  alt="Layout 62"></p>
-	</li>
-    <li>
-    	Click <strong>Finish</strong>.
-    </li>
-	<li>
-		<p>In Java perspective, type <strong>Ctrl+N</strong> to open <strong>New</strong> wizards dialog.</p>
-        <p>Select <strong>Java project</strong> in the list of wizards and click <strong>Next</strong>.</p>
-    </li>
-    <li>
-    	<p>On the next page, type &quot;Product&quot; in the <strong>Project name</strong> field.</p>
-	</li>
-    <li>
-    	<p>In <strong>Contents</strong> group, change selection to <strong>Create project from existing source</strong>.</p>
-    	<p>Click <strong>Browse...</strong> and choose the <i><code>D:\Product</code></i> directory.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout63.png"  alt="Layout 63"></p>
-    	<p>Click <strong>Next</strong>.</p>
-	</li>
-	<li>
-		<p>Let's add a dependency to source framework project...</p>
-	</li>
-	<li>
-		<p>On the next page, verify that directory <i><code>JavaSourceFiles</code></i> has been automatically added as source folder.</p>
-		<p>Select <strong>Projects</strong> tab.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout64.png"  alt="Layout 64"></p>
-    	<p>Click <strong>Add...</strong>.</p>
-	</li>
-	<li>
-		<p>In <strong>Required Project Selection</strong>, check &quot;Framework&quot;.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout65.png"  alt="Layout 65"></p>
-    	<p>Click <strong>OK</strong>.</p>
-	</li>
-	<li>
-		<p>Now, let's put access rules on source framework content to authorize, discourage or forbid access to &quot;Framework&quot; source folders, package and classes...</p>
-	</li>
-	<li>
-		<p>In <strong>Projects</strong> tab, select &quot;Access rules&quot; of &quot;Framework&quot; depending project.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout66.png"  alt="Layout 66"></p>
-    	<p>Click <strong>Edit...</strong>.</p>
-	</li>
-	<li>
-		<p>In <strong>Type Access Rules</strong>, click <strong>Add...</strong>.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout67.png"  alt="Layout 67"></p>
-	</li>
-	<li>
-		<p>In <strong>Edit Access Rule</strong>, select &quot;Forbidden&quot; for <strong>Resolution</strong>.</p>
-		<p>Type &quot;**/forbidden/**&quot; in <strong>Rule Pattern</strong> field.</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout68.png"  alt="Layout 68"></p>
-    	<p>Click <strong>OK</strong>.</p>
-	</li>
-	<li>
-		<p>Add another access rule:</p>
-		<p><strong>Resolution</strong>: &quot;Discouraged&quot; and <strong>Rule Pattern</strong>: &quot;**/internal/**&quot;.</p>
-	</li>
-	<li>
-		<p>Your access rules now look as follows:</p>
-		<p><img src="../images/qs-WorkingWithExistingLayout69.png"  alt="Layout 69"></p>
-    	<p>Click <strong>OK</strong>.</p>
-	</li>
-    <li>
-    	<p>Dependent project has now 2 access rules set.</p>
-    	<p><img src="../images/qs-WorkingWithExistingLayout6a.png"  alt="Layout 6a"></p>
-    	<p>Click <strong>Finish</strong>.</p>
-    </li>
-    <li>
-    	<p>You now have a Java project which contains the source of &quot;Product&quot; and which is using the source of &quot;Framework&quot;.</p>
-    	<p>Some packages of the project &quot;Framework&quot; are restricted and if you try to import them, compiler displays either warnings or errors depending on your restriction level:</p> 
-		<p><img src="../images/qs-WorkingWithExistingLayout6b.png"  alt="Layout 6b"></p>
-    </li>
-	</ol>
-	
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a><br>
-      <a href="../tasks/tasks-6.htm">Java views</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="../tasks/tasks-110.htm">Working with build paths</a><br>
-       <a href="../tasks/tasks-12.htm">Creating a new Java project</a><br>
-       <a href="../tasks/tasks-14.htm">Creating a Java project with source folders</a><br>
-       <a href="../tasks/tasks-26.htm">Creating a new source folder</a><br>
-       <a href="../tasks/tasks-45.htm">Using the Package Explorer</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-121.htm">New Java Project Wizard</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-junit.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-junit.htm
deleted file mode 100644
index 526e436..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-junit.htm
+++ /dev/null

@@ -1,169 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Writing and running JUnit tests
-    </title>
-  </head>
-  <body>
-    <h1>
-      Writing and running JUnit tests
-    </h1>
-    <p>
-      In this section, you will be using the <a href="http://www.junit.org" target="_blank"> JUnit</a> 
-    testing framework to write and run tests. To get started with JUnit you can
-    refer to the <a href="http://junit.sourceforge.net/doc/cookbook/cookbook.htm" target="_blank">JUnit
-    Cookbook</a>.
-    </p>
-    <h2>
-      Writing Tests
-    </h2>
-
-    <p>
-      Create a project &quot;JUnitTest&quot;.  Now you can write your
-      first test. You implement the test in a subclass of <strong>TestCase</strong>. You can
-      do so either using the standard Class wizard or the specialized <strong>Test Case 
-      </strong> wizard:
-    </p>
-    <ol>
-      <li>Open the New wizard (<strong>File  &gt; New  &gt; JUnit Test Case</strong>).</li>
-      <li>A dialog will open asking to add the junit library to the class path.  Select <strong>Yes</strong>.</li>
-      <li>Enter &quot;<i>TestFailure&quot;</i> as the name of your test class:
-       <p>
-        <img src="../images/qs-jun1.png"  alt="TestCase creation wizard page 1"><br>
-       </p>
-      </li>
-      <li>Click <strong>Finish</strong> to create the test class.
-      </li>
-    </ol>
-    <p>
-      Add a test method that fails to the class <i>TestFailure</i>. A quick
-      way to enter a test method is with the <i>test</i> template. To do so, place the cursor inside the class declaration. 
-      Type &quot;test&quot; followed by Ctrl+Space to activate code
-      assist and select the &quot;test&quot; template. Change the name of the
-      created method to <i>testFailure</i> and invoke the <i>fail() </i>method.
-    </p>
-    <p><code>
-      public void testFailure() throws Exception {<br>
-      &nbsp;&nbsp;&nbsp; fail();<br>
-      }
-    </code></p>
-     
-    <p>Now you are ready to run your first test.</p>
-
-    <h2>
-      Running Tests
-    </h2>
-    
-    <p>To run TestFailure, and activate the <b>Run</b> drop-down
-    menu in the toolbar and select <span class="control">Run as &gt; JUnit Test</span>.
-    You can inspect the test results in the <i>JUnit</i> view. This view shows
-    you the test run progress and status:</p>
-
-    <p><img src="../images/qs-jun3.png"  alt="Failed test"></p>
-
-    <p> The view is shown in the current
-    perspective whenever you start a test run. A convenient arrangement for the
-    JUnit view is to dock it as a fast view. The JUnit view has two tabs: one shows
-    you a list of failures and the other shows you the full test suite as
-    a tree. You can navigate from a failure to the corresponding source by
-    double clicking the corresponding line in the failure trace.</p>
-
-    <p>Dock the JUnit view as a fast view, remove the <i>
-    fail()</i> statement in the method <i> testFailure()</i> so that the test passes and rerun
-    the test again. You can rerun a test either by clicking the <b>Rerun</b> button in
-    the view's tool bar or you can re-run the program that was last launched by activating
-    the <b>Run</b> drop down. This time the test should succeed. Because the test was successful,
-     the JUnit view doesn't pop up, but the success indicator shows on 
-    the JUnit view icon and the status line shows the test result. As a reminder
-    to rerun your tests the view icon is decorated by a &quot;*&quot;
-    whenever you change the workspace contents after the run.</p>
-
-    <blockquote>
-      <p><img src="../images/qs-jun2.png"  border="0" alt="Successful test">
-      - A successful test run<br>
-      <img src="../images/qs-jun4.png"  border="0" alt="Successful test but workspace has changed"> - 
-      A successful test run, but the workspace contents have changed since the
-      last test run.</p>
-
-    </blockquote>
-    <p>In addition to running a test case as described above you can also:</p>
-    <ul>
-      <li>Run all tests inside a project, source folder, or package - &nbsp;<br>
-        Select a project, package or source folder and run all the included tests with <strong>Run as &gt; JUnit Test</strong>.
-        This command finds all tests inside a project, source folder or package
-        and executes them.</li>
-      <li>Run a single test method - <br>
-        Select a test method in the Outline or Package Explorer and with <strong>Run as &gt; JUnit Test</strong>
-        the selected test method will be run.</li>
-      <li>Rerun a single test - <br>
-        Select a test in the JUnit view and execute <b>Run </b>from the context
-        menu.</li>
-    </ul>
-
-    <h2>
-      Customizing a Test Configuration
-    </h2>
-    
-    <p>When you want to pass parameters or customize the
-    settings for a test run you open the Launch Configuration Dialog. Select <strong>Run...</strong>.in the <strong>Run</strong>
-    drop-down menu in the toolbar:</p>
-    <p><img src="../images/qs-jun5.png"  alt="JUnit Launch Configuration"></p>
-    <p>In this dialog you can specify the test to be run, its arguments, its run-time
-    class path, and the Java run-time environment.</p>
-
-    <h2>
-      Debugging a Test Failure
-    </h2>
-    
-    <p>In the case of a test failure you can follow these steps to debug it:</p>
-    <ol>
-      <li>Double click the failure entry from the Failures tab in the JUnit view to open the
-        corresponding file in the editor.</li>
-      <li>Set a breakpoint at the beginning of the test method.</li>
-      <li>Select the test case and execute&nbsp; <b>Debug As&gt;JUnit Test</b> from
-        the <b>Debug </b>drop down.</li>
-    </ol>
-    <p>A JUnit launch configuration has a &quot;keep alive&quot; option. If your
-    Java virtual machine supports &quot;hot code replacement&quot; you can fix the code and rerun the test
-    without restarting the full test run. To enable this option select the <strong>Keep
-    JUnit running after a test run when debugging</strong> checkbox in the JUnit
-    launch configuration.</p>
-
-    <h2>
-      Creating a Test Suite
-    </h2>
-    
-    <p>
-      The JUnit <b>TestSuite </b>wizard helps you with the creation of a test
-      suite. You can select the set of classes that should belong to a suite. 
-    </p>
-    
-    <ol>
-      <li>Open the New wizard</li>
-      <li>Select <strong>Java &gt; JUnit &gt; JUnit Test Suite</strong> and click <strong>Next</strong>.</li>
-      <li>Enter a name for your test suite class (the convention is to use
-        &quot;AllTests&quot; which appears by default).<br>
-        <p><img src="../images/qs-jun6.png"  alt="Test Suite wizard"></p>
-      </li>
-      <li>Select the classes that should be included in the suite. We currently
-        have a single test class only, but you can add to the suite later.</li>
-    </ol>
-    
-    <p>You can add or remove test classes from the test suite in two ways:</p>
-    <ul>
-      <li>Manually by editing the test suite file</li>
-	  <li>By re-running the wizard and selecting the new set of test classes.</li>
-    </ul>
-    <p>Note: the wizard puts 2 markers, <code>//$JUnit-BEGIN$</code> and
-    <code>//$JUnit-END$</code>, into the created Test suite class, which allows
-    the wizard to update existing test suite classes. Editing code between the markers is 
-    not recommended.</p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-with-j2se50.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-with-j2se50.htm
deleted file mode 100644
index 19ed578..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-with-j2se50.htm
+++ /dev/null

@@ -1,216 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-<title>Getting Started with Eclipse 3.1 and J2SE 5.0</title>
-</head>
-<body>
-<h1>Getting Started with Eclipse 3.1 and J2SE 5.0</h1>
-<p>
-Eclipse 3.1 includes full support for the new features of J2SE 5.0 (codenamed "Tiger").
-One of the most important consequences of this support is that you 
-may not notice it at all--everything you expect to work for J2SE 1.4, 
-including editing, compiling, debugging, quick fixes, refactorings, source
-actions, searching, etc., will
-work seamlessly with J2SE 5.0's new types and syntax.  In this document,
-we will introduce some of the more interesting capabilities Eclipse users
-will find when working with J2SE 5.0.
-</p>
-
-<h2>Prerequisites</h2>
-
-<p>
-In order to develop code compliant with J2SE 5.0, you will need a J2SE 5.0 Java Runtime Environment (JRE).
-If you start Eclipse for the first time using a J2SE 5.0 JRE, then it will use it by default.
-Otherwise, you will need to use the <strong>Installed JRE's</strong> dialog 
-(<strong>Windows &gt; Preferences &gt; Java &gt; Installed JRE's</strong>) to register it with Eclipse.
-</p>
-
-<p>
-This document introduces some of the 
-<a href="http://java.sun.com/developer/technicalArticles/releases/j2se15/" target="_blank">new language features</a> 
-in J2SE 5.0 very briefly, but it is not a proper tutorial for these features.
-</p>
-
-<h3>Compiler Compliance Level</h3>
-
-<p>
-To use the new J2SE 5.0 features, you must be working on a project that has a 5.0 compliance level enabled.
-New projects can easily be marked as 5.0-compliant on the first page of the <strong>New &gt; Project</strong> wizard:</p>
-<p><img src="../images/j2se50/new-project.png" alt="New Project Wizard"></p>
-To convert an existing J2SE 1.4 project to J2SE 5.0, you can simply:
-<ol>
-<li>Make sure you have a J2SE 5.0 JRE installed.</li>
-<li>Start using the 5.0 features in your code.</li>
-<li>When a compiler error is flagged, use Quick Fix to update the project's compliance level:
-<p><img src="../images/j2se50/quick-fix.png" alt="Quick fix to enable J2SE 5.0">
-</p>
-</li>
-</ol> 
-
-<p>
-For more fine-tuned control, 
-the compiler compliance level can be set globally for a workspace (<strong>Windows &gt; Preferences &gt; Java &gt; Compiler</strong>)
-or individually for each project (from the project's context menu, choose <strong>Properties &gt; Java Compiler</strong>).
-Projects with different compliance levels can co-exist in the workspace, and depend on each other.
-You can also fine-tune the kinds of compiler warnings and errors produced for each project 
-using <strong>Properties &gt; Java Compiler &gt; Errors/Warnings &gt; J2SE 5.0 Options</strong>
-</p>
-
-<h2>Generic Types</h2>
-
-<p>
-Generic types allow objects of the same class to safely operate on objects of different types.
-For example, they allow compile-time assurances that a 
-<code>List&lt;String&gt;</code> always contains <code>String</code>s, and a <code>List&lt;Integer&gt;</code> always contains <code>Integer</code>s.
-</p>
-
-<p>
-Anywhere that Eclipse handles a non-generic type, it can handle a generic type:
-<ul>
-<li> Generic types can be safely renamed.</li>
-<li> Type variables can be safely renamed.</li>
-<li> Generic methods can be safely extracted from / inlined into generic code.</li>
-<li> Code assist can automatically insert appropriate type parameters in parameterized types.</li>
-</ul>
-</p>
-
-In addition, a new refactoring has been added: <strong>Infer Generic Type Arguments</strong> can infer
-type parameters for every type reference in a class, a package, or an entire project:
-
-<p><img src="../images/j2se50/infer-generic.png" alt="Invoking Infer Generic Type Arguments"></p>
-
-Invoking the refactoring produces:
-
-<p><img src="../images/j2se50/inferred-generic.png" alt="Invoked Infer Generic Type Arguments">
-</p>
-
-
-<p>
-Eclipse 3.1 provides new options when searching for references to generic types.  Consider this example:
-</p>
-<p><img src="../images/j2se50/foo.png" alt="Example with four different parameterized instantiations of List"></p>
-
-Selecting the reference to <code>List&lt;Integer&gt;</code> and using 
-<strong>Search &gt; References &gt; Project</strong> 
-will highlight the List types on all four lines:
-
-<p><img src="../images/j2se50/no-filters.png" alt="Search with no filters"></p>
-
-Using the Search View menu, the results can be filtered:
-
-<p>
-<strong>Filter Incompatible</strong> leaves only references to types that are assignment-compatible with
-the selected type:</p>
-<p><img src="../images/j2se50/filter-incompatible.png" alt="Filter incompatible">
-</p>
-
-
-<p><strong>Filter Inexact</strong> leaves only type references with the exact same signature:</p>
-<p><img src="../images/j2se50/filter-inexact.png" alt="Filter inexact"></p>
-
-<h2>Annotations</h2>
-
-<p>
-Annotations attach metadata about how Java types and methods are used 
-and documented to the Java source and can then affect compilation or 
-be queried at run-time.  For example, <code>@Override</code> will trigger
-a compiler warning if the annotated method does not override a method in
-a superclass:
-</p>
-
-<p><img src="../images/j2se50/override.png" alt="Override annotation"></p>
-
-<p>
-Everything you can do with a Java type, you can do with an annotation:
-<ul>
-<li> Create new annotations using <strong>New &gt; Annotation</strong></li>
-<li> Refactor: rename, move, change signatures of members, etc.</li>
-<li> Search for occurrences</li>
-<li> Use code assist to fill in names and values</li>
-</ul>
-</p>
-
-<p>
-A very useful annotation with full support in Eclipse is <code>@SuppressWarnings</code>.
-For example, consider a private method that is currently unused, but you'd rather not delete:</p>
-<p><img src="../images/j2se50/unused-warning.png" alt="Warning: unused private method"></p>
-
-Invoking quick fix on the warning proposes adding a <code>@SuppressWarnings</code> annotation:
-<p><img src="../images/j2se50/suppress-proposed.png" alt="SuppressWarnings proposed"></p>
-
-Selecting the quick fix adds the annotation.  The Eclipse compiler honors the annotation by
-removing the warning on <code>foo</code>:
-<p><img src="../images/j2se50/suppress-applied.png" alt="SuppressWarnings inserted"></p>
-
-<h2>Enumerations</h2>
-
-<p>
-Enumerations are types that are instantiated at runtime by a known, finite set of objects:</p>
-<p><img src="../images/j2se50/enum.png" alt="enum type"></p>
-
-<p>
-Again, anything you can do to a Java class can be done to an enumeration:
-
-<ul>
-<li> Create new enumerations using <strong>New &gt; Enum</strong></li>
-<li> Refactor: rename, move, rename constants, etc.</li>
-<li> Search for occurrences</li>
-<li> Use code assist to fill in constants</li>
-</ul>
-</p>
-
-<h2>Autoboxing</h2>
-
-<p>
-Autoboxing and auto unboxing allow for elegant syntax when primitive types are assigned
-to or retrieved from Object references:
-</p>
-<p><img src="../images/j2se50/autobox.png" alt="autoboxing highlighted"></p>
-
-<p>
-Eclipse's source manipulation features handle autoboxing seamlessly, 
-giving the correct types to new local variables and correct code assists.
-For code understanding, it is also possible to flag instances of 
-autoboxing or autounboxing as compile warnings 
-(<strong>Window &gt; Preferences &gt; Java &gt; Compiler &gt; Errors/Warnings &gt; J2SE 5.0 Options &gt; Boxing and unboxing conversions</strong>), 
-or highlight them using syntax coloring
-(<strong>Window &gt; Preferences &gt; Java &gt; Editor &gt; Syntax Coloring &gt; Java &gt; Auto(un)boxed expressions</strong>):</p>
-<p><img src="../images/j2se50/autobox-coloring.png" alt="Enabling highlighting for autoboxing"></p>
-
-<h2>Enhanced for loop</h2>
-
-<p>
-For the common case of operating on each element of an array or collection in turn, 
-J2SE 5.0 allows a new, cleaner syntax.  
-Eclipse 3.1 provides a "foreach" code template that can automatically guess 
-the collection to be iterated:
-</p>
-<p><img src="../images/j2se50/foreach-proposal.png" alt="foreach template proposed"></p>
-
-Choosing the template produces:
-
-<p><img src="../images/j2se50/foreach-inserted.png" alt="foreach template inserted"></p>
-
-<p>
-Eclipse 3.1 also provides a "Convert to enhanced for loop" quick-assist to
-upgrade 1.4-style <code>for</code> loops where possible.
-</p>
-
-<h2>Other</h2>
-
-<p>
-All other features of J2SE 5.0 are handled flexibly by Eclipse's editing, searching, and code manipulation tools:
-
-<ul>
-<li> Static imports</li>
-<li> Varargs</li>
-<li> Covariant return types</li>
-</ul>
-
-Happy coding!
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/images/add_linked_source_to_buildpath.png b/bundles/org.eclipse.jdt.doc.user/images/add_linked_source_to_buildpath.png
deleted file mode 100644
index 5ef9813..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/add_linked_source_to_buildpath.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/c-quickfix.png b/bundles/org.eclipse.jdt.doc.user/images/c-quickfix.png
deleted file mode 100644
index 1eb9de7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/c-quickfix.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/classpathVar.png b/bundles/org.eclipse.jdt.doc.user/images/classpathVar.png
deleted file mode 100644
index 45de599..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/classpathVar.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/contentassist.png b/bundles/org.eclipse.jdt.doc.user/images/contentassist.png
deleted file mode 100644
index 4c317e6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/contentassist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/j2se50/autobox-coloring.png b/bundles/org.eclipse.jdt.doc.user/images/j2se50/autobox-coloring.png
deleted file mode 100644
index ab6f4db..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/j2se50/autobox-coloring.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/j2se50/autobox.png b/bundles/org.eclipse.jdt.doc.user/images/j2se50/autobox.png
deleted file mode 100644
index f68e438..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/j2se50/autobox.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/j2se50/enum.png b/bundles/org.eclipse.jdt.doc.user/images/j2se50/enum.png
deleted file mode 100644
index 075cb5b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/j2se50/enum.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/j2se50/filter-incompatible.png b/bundles/org.eclipse.jdt.doc.user/images/j2se50/filter-incompatible.png
deleted file mode 100644
index 1bf2fcc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/j2se50/filter-incompatible.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/j2se50/filter-inexact.png b/bundles/org.eclipse.jdt.doc.user/images/j2se50/filter-inexact.png
deleted file mode 100644
index 69a7b3c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/j2se50/filter-inexact.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/j2se50/foo.png b/bundles/org.eclipse.jdt.doc.user/images/j2se50/foo.png
deleted file mode 100644
index db65433..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/j2se50/foo.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/j2se50/foreach-inserted.png b/bundles/org.eclipse.jdt.doc.user/images/j2se50/foreach-inserted.png
deleted file mode 100644
index 342e905..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/j2se50/foreach-inserted.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/j2se50/foreach-proposal.png b/bundles/org.eclipse.jdt.doc.user/images/j2se50/foreach-proposal.png
deleted file mode 100644
index f9e2a17..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/j2se50/foreach-proposal.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/j2se50/infer-generic.png b/bundles/org.eclipse.jdt.doc.user/images/j2se50/infer-generic.png
deleted file mode 100644
index df1ce71..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/j2se50/infer-generic.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/j2se50/inferred-generic.png b/bundles/org.eclipse.jdt.doc.user/images/j2se50/inferred-generic.png
deleted file mode 100644
index bea5b35..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/j2se50/inferred-generic.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/j2se50/new-project.png b/bundles/org.eclipse.jdt.doc.user/images/j2se50/new-project.png
deleted file mode 100644
index 9f3633d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/j2se50/new-project.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/j2se50/no-filters.png b/bundles/org.eclipse.jdt.doc.user/images/j2se50/no-filters.png
deleted file mode 100644
index 6070748..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/j2se50/no-filters.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/j2se50/override.png b/bundles/org.eclipse.jdt.doc.user/images/j2se50/override.png
deleted file mode 100644
index 69fee99..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/j2se50/override.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/j2se50/quick-fix.png b/bundles/org.eclipse.jdt.doc.user/images/j2se50/quick-fix.png
deleted file mode 100644
index d1a3046..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/j2se50/quick-fix.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/j2se50/suppress-applied.png b/bundles/org.eclipse.jdt.doc.user/images/j2se50/suppress-applied.png
deleted file mode 100644
index 82092cc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/j2se50/suppress-applied.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/j2se50/suppress-proposed.png b/bundles/org.eclipse.jdt.doc.user/images/j2se50/suppress-proposed.png
deleted file mode 100644
index e56f747..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/j2se50/suppress-proposed.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/j2se50/unused-warning.png b/bundles/org.eclipse.jdt.doc.user/images/j2se50/unused-warning.png
deleted file mode 100644
index 6972414..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/j2se50/unused-warning.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/ngrelc.png b/bundles/org.eclipse.jdt.doc.user/images/ngrelc.png
deleted file mode 100644
index 161e3aa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/ngrelc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/ngrelr.png b/bundles/org.eclipse.jdt.doc.user/images/ngrelr.png
deleted file mode 100644
index 4726f8c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/ngrelr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/ngrelt.png b/bundles/org.eclipse.jdt.doc.user/images/ngrelt.png
deleted file mode 100644
index 74bee2b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/ngrelt.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/changevariablevalue_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/changevariablevalue_co.png
deleted file mode 100644
index 5944714..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/changevariablevalue_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/collapseall.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/collapseall.png
deleted file mode 100644
index e6a51f2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/collapseall.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/copy_edit_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/copy_edit_co.png
deleted file mode 100644
index 6710357..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/copy_edit_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/copyviewtoclipboard_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/copyviewtoclipboard_tsk.png
deleted file mode 100644
index ae69f07..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/copyviewtoclipboard_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/debuglast_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/debuglast_co.png
deleted file mode 100644
index 99cf37c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/debuglast_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_hide.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_hide.png
deleted file mode 100644
index b35b56d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_hide.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_right.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_right.png
deleted file mode 100644
index 10af6c0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_right.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_under.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_under.png
deleted file mode 100644
index 16200d4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_under.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/disabled_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/disabled_co.png
deleted file mode 100644
index a772650..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/disabled_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/disconnect_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/disconnect_co.png
deleted file mode 100644
index 9db8853..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/disconnect_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/edtsrclkup_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/edtsrclkup_co.png
deleted file mode 100644
index 2eae230..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/edtsrclkup_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/enabled_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/enabled_co.png
deleted file mode 100644
index ca175c0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/enabled_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/lock_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/lock_co.png
deleted file mode 100644
index e613f9a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/lock_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/memoryreset_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/memoryreset_tsk.png
deleted file mode 100644
index 5e807fb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/memoryreset_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/metharg_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/metharg_obj.png
deleted file mode 100644
index 5b829ff..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/metharg_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/monitorexpression_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/monitorexpression_tsk.png
deleted file mode 100644
index 66fd225..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/monitorexpression_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/printview_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/printview_tsk.png
deleted file mode 100644
index 0550c10..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/printview_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/rem_all_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/rem_all_co.png
deleted file mode 100644
index 7d5a844..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/rem_all_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/rem_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/rem_co.png
deleted file mode 100644
index 1d3ee9e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/rem_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/removememory_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/removememory_tsk.png
deleted file mode 100644
index 1d3ee9e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/removememory_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/resume_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/resume_co.png
deleted file mode 100644
index 7f78504..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/resume_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/runlast_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/runlast_co.png
deleted file mode 100644
index 7620144..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/runlast_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/runtoline_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/runtoline_co.png
deleted file mode 100644
index e4ef891..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/runtoline_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/skip_brkp.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/skip_brkp.png
deleted file mode 100644
index ac88344..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/skip_brkp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepbystep_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepbystep_co.png
deleted file mode 100644
index 4d308c1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepbystep_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepinto_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepinto_co.png
deleted file mode 100644
index 7ba98b1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepinto_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepover_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepover_co.png
deleted file mode 100644
index f1b8323..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepover_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepreturn_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepreturn_co.png
deleted file mode 100644
index c7a6f4a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepreturn_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/suspend_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/suspend_co.png
deleted file mode 100644
index 349f8ab..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/suspend_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/synced.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/synced.png
deleted file mode 100644
index d28c6b7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/synced.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_all_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_all_co.png
deleted file mode 100644
index e9a444b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_all_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_co.png
deleted file mode 100644
index d3a0590..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_rem_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_rem_co.png
deleted file mode 100644
index 191bf21..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_rem_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/tnames_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/tnames_co.png
deleted file mode 100644
index 2c6b2f5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/tnames_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/toggledetailpane_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/toggledetailpane_co.png
deleted file mode 100644
index 24eba96..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/toggledetailpane_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/var_cntnt_prvdr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/var_cntnt_prvdr.png
deleted file mode 100644
index d997a25..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/var_cntnt_prvdr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/debug_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/debug_exc.png
deleted file mode 100644
index 2e29e64..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/debug_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/environment_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/environment_co.png
deleted file mode 100644
index d4dfe0c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/environment_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/profile_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/profile_exc.png
deleted file mode 100644
index 1bf8948..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/profile_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/run_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/run_exc.png
deleted file mode 100644
index 9a55714..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/run_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/term_restart.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/term_restart.png
deleted file mode 100644
index 1b106fc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/term_restart.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/watch_exp.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/watch_exp.png
deleted file mode 100644
index 706bc23..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/watch_exp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/changevariablevalue_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/changevariablevalue_co.png
deleted file mode 100644
index 6d6a3f0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/changevariablevalue_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/collapseall.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/collapseall.png
deleted file mode 100644
index 2349877..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/collapseall.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/copy_edit_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/copy_edit_co.png
deleted file mode 100644
index bb5451c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/copy_edit_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/copyviewtoclipboard_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/copyviewtoclipboard_tsk.png
deleted file mode 100644
index 39f1090..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/copyviewtoclipboard_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/debuglast_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/debuglast_co.png
deleted file mode 100644
index 69221be..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/debuglast_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_hide.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_hide.png
deleted file mode 100644
index c6ff25e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_hide.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_right.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_right.png
deleted file mode 100644
index 8d23eb3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_right.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_under.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_under.png
deleted file mode 100644
index b22ac64..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_under.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/disabled_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/disabled_co.png
deleted file mode 100644
index 6fa89b3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/disabled_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/disconnect_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/disconnect_co.png
deleted file mode 100644
index 070671e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/disconnect_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/dissolve_group.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/dissolve_group.png
deleted file mode 100644
index 21a7c0d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/dissolve_group.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/drop_to_frame.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/drop_to_frame.png
deleted file mode 100644
index 96cf8c2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/drop_to_frame.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/edtsrclkup_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/edtsrclkup_co.png
deleted file mode 100644
index 3e92946..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/edtsrclkup_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/enabled_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/enabled_co.png
deleted file mode 100644
index e3e9baa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/enabled_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/expandall.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/expandall.png
deleted file mode 100644
index 12e979a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/expandall.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/hierarchicalLayout.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/hierarchicalLayout.png
deleted file mode 100644
index a9355ea..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/hierarchicalLayout.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/lock_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/lock_co.png
deleted file mode 100644
index 6a00020..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/lock_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/memoryreset_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/memoryreset_tsk.png
deleted file mode 100644
index a7b8b42..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/memoryreset_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/metharg_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/metharg_obj.png
deleted file mode 100644
index a037e58..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/metharg_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/monitorexpression_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/monitorexpression_tsk.png
deleted file mode 100644
index 6d48492..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/monitorexpression_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/new_con.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/new_con.png
deleted file mode 100644
index 469ec49..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/new_con.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/pin.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/pin.png
deleted file mode 100644
index fc0cf1b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/pin.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/printview_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/printview_tsk.png
deleted file mode 100644
index 495b869..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/printview_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/rem_all_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/rem_all_co.png
deleted file mode 100644
index 73053c4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/rem_all_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/rem_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/rem_co.png
deleted file mode 100644
index 91e4e01..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/rem_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/removememory_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/removememory_tsk.png
deleted file mode 100644
index 91e4e01..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/removememory_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/resume_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/resume_co.png
deleted file mode 100644
index 114193f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/resume_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/runlast_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/runlast_co.png
deleted file mode 100644
index 668fd32..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/runlast_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/runtoline_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/runtoline_co.png
deleted file mode 100644
index 560e289..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/runtoline_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/skip_brkp.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/skip_brkp.png
deleted file mode 100644
index 30c82c6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/skip_brkp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepbystep_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepbystep_co.png
deleted file mode 100644
index a24953f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepbystep_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepinto_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepinto_co.png
deleted file mode 100644
index b237fe8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepinto_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepover_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepover_co.png
deleted file mode 100644
index 407268c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepover_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepreturn_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepreturn_co.png
deleted file mode 100644
index 7fc74f9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepreturn_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/suspend_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/suspend_co.png
deleted file mode 100644
index 5254176..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/suspend_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/synced.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/synced.png
deleted file mode 100644
index 7d54854..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/synced.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_all_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_all_co.png
deleted file mode 100644
index d9aa1ee..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_all_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_co.png
deleted file mode 100644
index cddc772..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_rem_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_rem_co.png
deleted file mode 100644
index 833ebf3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_rem_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/tnames_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/tnames_co.png
deleted file mode 100644
index a1a64c1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/tnames_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/toggledetailpane_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/toggledetailpane_co.png
deleted file mode 100644
index e5f9f9f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/toggledetailpane_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/var_cntnt_prvdr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/var_cntnt_prvdr.png
deleted file mode 100644
index 918861d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/var_cntnt_prvdr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/debug_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/debug_exc.png
deleted file mode 100644
index 95d69dd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/debug_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/environment_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/environment_co.png
deleted file mode 100644
index 1e5240e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/environment_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/profile_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/profile_exc.png
deleted file mode 100644
index 983ba0a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/profile_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/run_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/run_exc.png
deleted file mode 100644
index 967cf0f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/run_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/term_restart.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/term_restart.png
deleted file mode 100644
index 6e3a83d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/term_restart.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/watch_exp.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/watch_exp.png
deleted file mode 100644
index 236d9ad..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/watch_exp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/breakpoint_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/breakpoint_view.png
deleted file mode 100644
index 379357a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/breakpoint_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/debug_persp.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/debug_persp.png
deleted file mode 100644
index 71b6ebd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/debug_persp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/debug_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/debug_view.png
deleted file mode 100644
index 71b6ebd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/debug_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/details_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/details_view.png
deleted file mode 100644
index 095263c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/details_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/memory_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/memory_view.png
deleted file mode 100644
index 8264f7d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/memory_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/register_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/register_view.png
deleted file mode 100644
index b164d3a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/register_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/variable_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/variable_view.png
deleted file mode 100644
index 9a44e10..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/variable_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/watchlist_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/watchlist_view.png
deleted file mode 100644
index 41ae47f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/watchlist_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/brkp_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/brkp_obj.png
deleted file mode 100644
index 5672584..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/brkp_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/brkpd_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/brkpd_obj.png
deleted file mode 100644
index 5c7b2fe..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/brkpd_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugt_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugt_obj.png
deleted file mode 100644
index 471c091..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugt_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugts_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugts_obj.png
deleted file mode 100644
index 6801070..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugts_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugtt_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugtt_obj.png
deleted file mode 100644
index 0ad64e7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugtt_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/expression_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/expression_obj.png
deleted file mode 100644
index aeb9294..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/expression_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/genericvariable_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/genericvariable_obj.png
deleted file mode 100644
index 02b6e29..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/genericvariable_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/inst_ptr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/inst_ptr.png
deleted file mode 100644
index 2fa71f8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/inst_ptr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/inst_ptr_top.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/inst_ptr_top.png
deleted file mode 100644
index ba437e5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/inst_ptr_top.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/ldebug_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/ldebug_obj.png
deleted file mode 100644
index 6e4d0d8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/ldebug_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/lrun_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/lrun_obj.png
deleted file mode 100644
index 5bd0e13..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/lrun_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/osprc_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/osprc_obj.png
deleted file mode 100644
index 38ac821..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/osprc_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/osprct_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/osprct_obj.png
deleted file mode 100644
index a3c460e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/osprct_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/readwrite_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/readwrite_obj.png
deleted file mode 100644
index 1eb5eb3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/readwrite_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/stckframe_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/stckframe_obj.png
deleted file mode 100644
index 6871a8e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/stckframe_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/stckframe_running_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/stckframe_running_obj.png
deleted file mode 100644
index 45089c1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/stckframe_running_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/terminatedlaunch_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/terminatedlaunch_obj.png
deleted file mode 100644
index 7299114..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/terminatedlaunch_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/thread_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/thread_obj.png
deleted file mode 100644
index 212a6c2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/thread_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/threads_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/threads_obj.png
deleted file mode 100644
index 9e69cf1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/threads_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/ovr16/error.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/ovr16/error.png
deleted file mode 100644
index d8f0680..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/ovr16/error.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/ovr16/stcksync_ov.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/ovr16/stcksync_ov.png
deleted file mode 100644
index dabc465..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/ovr16/stcksync_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/addsrcloc_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/addsrcloc_wiz.png
deleted file mode 100644
index d0b18e7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/addsrcloc_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/debug_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/debug_wiz.png
deleted file mode 100644
index 0fdecfb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/debug_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/edtsrclkup_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/edtsrclkup_wiz.png
deleted file mode 100644
index 8b1108f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/edtsrclkup_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/profile_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/profile_wiz.png
deleted file mode 100644
index f922f24..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/profile_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/run_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/run_wiz.png
deleted file mode 100644
index 1a9b33f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/run_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/at_breakpoint.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/at_breakpoint.png
deleted file mode 100644
index b31f4e9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/at_breakpoint.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/constant_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/constant_co.png
deleted file mode 100644
index cfbdd66..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/constant_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/deadlock_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/deadlock_view.png
deleted file mode 100644
index f7f2995..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/deadlock_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/exc_catch.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/exc_catch.png
deleted file mode 100644
index ed6fe17..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/exc_catch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/final_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/final_co.png
deleted file mode 100644
index bb8312d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/final_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/monitor_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/monitor_view.png
deleted file mode 100644
index 17446cc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/monitor_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/resume_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/resume_co.png
deleted file mode 100644
index 7f78504..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/resume_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/sethitcount_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/sethitcount_co.png
deleted file mode 100644
index dedb799..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/sethitcount_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/static_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/static_co.png
deleted file mode 100644
index a7489e6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/static_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/suspend_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/suspend_co.png
deleted file mode 100644
index 349f8ab..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/suspend_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/thread_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/thread_view.png
deleted file mode 100644
index 3c33fd6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/thread_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/debug_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/debug_exc.png
deleted file mode 100644
index 2e29e64..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/debug_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/disp_sbook.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/disp_sbook.png
deleted file mode 100644
index 0157f6e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/disp_sbook.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/insp_sbook.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/insp_sbook.png
deleted file mode 100644
index fa1fe6b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/insp_sbook.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_app.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_app.png
deleted file mode 100644
index c3b0a18..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_app.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_applet.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_applet.png
deleted file mode 100644
index d329a42..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_applet.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_attach.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_attach.png
deleted file mode 100644
index 002a532..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_attach.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/newsbook_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/newsbook_wiz.png
deleted file mode 100644
index fb3388a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/newsbook_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/run_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/run_exc.png
deleted file mode 100644
index 9a55714..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/run_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/run_sbook.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/run_sbook.png
deleted file mode 100644
index 2279f74..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/run_sbook.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/term_sbook.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/term_sbook.png
deleted file mode 100644
index d3a0590..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/term_sbook.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/watch_exp.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/watch_exp.png
deleted file mode 100644
index 706bc23..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/watch_exp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/constant_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/constant_co.png
deleted file mode 100644
index 8c72bed..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/constant_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/deadlock_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/deadlock_view.png
deleted file mode 100644
index 90973ab..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/deadlock_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/exc_catch.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/exc_catch.png
deleted file mode 100644
index 95070cf..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/exc_catch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/final_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/final_co.png
deleted file mode 100644
index bf224ab..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/final_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/monitor_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/monitor_view.png
deleted file mode 100644
index c11b767..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/monitor_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/resume_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/resume_co.png
deleted file mode 100644
index 114193f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/resume_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/sethitcount_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/sethitcount_co.png
deleted file mode 100644
index 2c8726a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/sethitcount_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/static_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/static_co.png
deleted file mode 100644
index 8adf87a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/static_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/suspend_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/suspend_co.png
deleted file mode 100644
index 5254176..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/suspend_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/thread_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/thread_view.png
deleted file mode 100644
index 4dcff67..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/thread_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/empty_jpage.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/empty_jpage.png
deleted file mode 100644
index 2eb3b5d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/empty_jpage.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/debug_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/debug_exc.png
deleted file mode 100644
index 95d69dd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/debug_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/disp_sbook.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/disp_sbook.png
deleted file mode 100644
index 694fe36..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/disp_sbook.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/insp_sbook.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/insp_sbook.png
deleted file mode 100644
index e936fba..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/insp_sbook.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_app.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_app.png
deleted file mode 100644
index e491d06..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_app.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_applet.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_applet.png
deleted file mode 100644
index dad7e1e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_applet.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_attach.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_attach.png
deleted file mode 100644
index b3cb48b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_attach.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/newsbook_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/newsbook_wiz.png
deleted file mode 100644
index eefe413..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/newsbook_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/run_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/run_exc.png
deleted file mode 100644
index 967cf0f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/run_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/run_sbook.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/run_sbook.png
deleted file mode 100644
index 9d7dbbe..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/run_sbook.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/term_sbook.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/term_sbook.png
deleted file mode 100644
index cfbf9d1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/term_sbook.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/watch_exp.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/watch_exp.png
deleted file mode 100644
index 236d9ad..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/watch_exp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/eview16/thread_and_monitor_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/eview16/thread_and_monitor_view.png
deleted file mode 100644
index 59c5e0a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/eview16/thread_and_monitor_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/eview16/variable_tab.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/eview16/variable_tab.png
deleted file mode 100644
index 9a44e10..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/eview16/variable_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/example_display.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/example_display.png
deleted file mode 100644
index cfe737a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/example_display.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/example_display_result.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/example_display_result.png
deleted file mode 100644
index 79790ae..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/example_display_result.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/example_inspect.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/example_inspect.png
deleted file mode 100644
index 2f7f734..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/example_inspect.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/example_inspect_result.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/example_inspect_result.png
deleted file mode 100644
index 36fb52e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/example_inspect_result.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/executable.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/executable.png
deleted file mode 100644
index da73610..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/executable.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/jpage_wizard.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/jpage_wizard.png
deleted file mode 100644
index f98b77a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/jpage_wizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/brkpi_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/brkpi_obj.png
deleted file mode 100644
index edb0b3f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/brkpi_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/class_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/class_obj.png
deleted file mode 100644
index b763245..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/class_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/classpath_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/classpath_obj.png
deleted file mode 100644
index 9557b04..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/classpath_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/contended_monitor_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/contended_monitor_obj.png
deleted file mode 100644
index 1f5638b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/contended_monitor_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/envvar_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/envvar_obj.png
deleted file mode 100644
index 9044217..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/envvar_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/insp_sbook.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/insp_sbook.png
deleted file mode 100644
index 1a9271c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/insp_sbook.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jar_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jar_obj.png
deleted file mode 100644
index af4d58f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jar_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexcept_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexcept_obj.png
deleted file mode 100644
index 2d07a1e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexcept_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexception_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexception_obj.png
deleted file mode 100644
index 7056a38..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexception_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexceptiond_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexceptiond_obj.png
deleted file mode 100644
index a2ab6e1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexceptiond_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jline_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jline_obj.png
deleted file mode 100644
index fe55c43..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jline_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jload_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jload_obj.png
deleted file mode 100644
index 8c6a3e1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jload_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jmeth_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jmeth_obj.png
deleted file mode 100644
index 5f1afe6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jmeth_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jrtexception_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jrtexception_obj.png
deleted file mode 100644
index 6d90522..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jrtexception_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jsbook_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jsbook_obj.png
deleted file mode 100644
index b89a649..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jsbook_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jsbook_run_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jsbook_run_obj.png
deleted file mode 100644
index de97cd7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jsbook_run_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jspbrkpt_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jspbrkpt_obj.png
deleted file mode 100644
index 6644b96..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jspbrkpt_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jwatch_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jwatch_obj.png
deleted file mode 100644
index 8307428..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jwatch_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/library_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/library_obj.png
deleted file mode 100644
index e21e089..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/library_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/localvariable_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/localvariable_obj.png
deleted file mode 100644
index 493ffc9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/localvariable_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/monitor_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/monitor_obj.png
deleted file mode 100644
index c11b767..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/monitor_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/owned_monitor_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/owned_monitor_obj.png
deleted file mode 100644
index cfb8a11..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/owned_monitor_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/package_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/package_obj.png
deleted file mode 100644
index 922c435..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/package_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/prj_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/prj_obj.png
deleted file mode 100644
index c4b05fb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/prj_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/read_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/read_obj.png
deleted file mode 100644
index 9869709..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/read_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/readwrite_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/readwrite_obj.png
deleted file mode 100644
index 52cbf7a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/readwrite_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/thread_and_monitor_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/thread_and_monitor_obj.png
deleted file mode 100644
index ed03ca0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/thread_and_monitor_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/thread_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/thread_obj.png
deleted file mode 100644
index 14ebb9e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/thread_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/write_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/write_obj.png
deleted file mode 100644
index 5a17ef5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/write_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/caught_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/caught_ovr.png
deleted file mode 100644
index 97faa0b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/caught_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/caught_ovr_disabled.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/caught_ovr_disabled.png
deleted file mode 100644
index 27f7dd9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/caught_ovr_disabled.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/conditional_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/conditional_ovr.png
deleted file mode 100644
index fbb326a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/conditional_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/conditional_ovr_disabled.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/conditional_ovr_disabled.png
deleted file mode 100644
index d9a1f0d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/conditional_ovr_disabled.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/contention_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/contention_ovr.png
deleted file mode 100644
index a9fb776..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/contention_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/contentionformonitor_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/contentionformonitor_ovr.png
deleted file mode 100644
index c5b975e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/contentionformonitor_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/deadlock_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/deadlock_ovr.png
deleted file mode 100644
index 3ad81a1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/deadlock_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/entry_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/entry_ovr.png
deleted file mode 100644
index d57e6f2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/entry_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/entry_ovr_disabled.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/entry_ovr_disabled.png
deleted file mode 100644
index 2f22f66..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/entry_ovr_disabled.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/error_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/error_co.png
deleted file mode 100644
index afb5bbd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/error_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/exit_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/exit_ovr.png
deleted file mode 100644
index d7f0d5a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/exit_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/exit_ovr_disabled.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/exit_ovr_disabled.png
deleted file mode 100644
index 08bb335..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/exit_ovr_disabled.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/installed_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/installed_ovr.png
deleted file mode 100644
index 1764c9a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/installed_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/installed_ovr_disabled.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/installed_ovr_disabled.png
deleted file mode 100644
index 1cdb362..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/installed_ovr_disabled.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/owned_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/owned_ovr.png
deleted file mode 100644
index d15e6e8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/owned_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/ownsmonitor_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/ownsmonitor_ovr.png
deleted file mode 100644
index a3bc4c6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/ownsmonitor_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/scoped_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/scoped_ovr.png
deleted file mode 100644
index 13de7f2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/scoped_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/scoped_ovr_disabled.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/scoped_ovr_disabled.png
deleted file mode 100644
index fb5815c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/scoped_ovr_disabled.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/sync_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/sync_ovr.png
deleted file mode 100644
index 9809abb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/sync_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/uncaught_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/uncaught_ovr.png
deleted file mode 100644
index cc7ad8d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/uncaught_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/uncaught_ovr_disabled.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/uncaught_ovr_disabled.png
deleted file mode 100644
index fbc3432..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/uncaught_ovr_disabled.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/warning_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/warning_co.png
deleted file mode 100644
index 20fe5b3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/warning_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/remove_all_terminated.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/remove_all_terminated.png
deleted file mode 100644
index 7ac4052..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/remove_all_terminated.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/run_as.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/run_as.png
deleted file mode 100644
index 3658ec2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/run_as.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/run_dialog.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/run_dialog.png
deleted file mode 100644
index 73b04c6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/run_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/run_drop_down.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/run_drop_down.png
deleted file mode 100644
index a8148c9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/run_drop_down.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/run_history.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/run_history.png
deleted file mode 100644
index 9d2711e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/run_history.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/scrap_assist.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/scrap_assist.png
deleted file mode 100644
index f0c5b00..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/scrap_assist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/scrap_display.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/scrap_display.png
deleted file mode 100644
index 00e1ad4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/scrap_display.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/scrapbook.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/scrapbook.png
deleted file mode 100644
index fba0890..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/scrapbook.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/select_main_type.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/select_main_type.png
deleted file mode 100644
index 7c42207..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/select_main_type.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/set_breakpoint.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/set_breakpoint.png
deleted file mode 100644
index da049e7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/set_breakpoint.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/test_runner_args.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/test_runner_args.png
deleted file mode 100644
index dd0a256..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/test_runner_args.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/test_runner_console.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/test_runner_console.png
deleted file mode 100644
index da70ab3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/test_runner_console.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/test_runner_debug_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/test_runner_debug_view.png
deleted file mode 100644
index ad82561..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/test_runner_debug_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/test_runner_output.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/test_runner_output.png
deleted file mode 100644
index 7770da7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/test_runner_output.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/var_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/var_view.png
deleted file mode 100644
index a7a1d6f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/var_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/java_app_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/java_app_wiz.png
deleted file mode 100644
index eada818..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/java_app_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/java_attach_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/java_attach_wiz.png
deleted file mode 100644
index aaa4aec..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/java_attach_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/library_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/library_wiz.png
deleted file mode 100644
index 2afd872..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/library_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/newsbook_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/newsbook_wiz.png
deleted file mode 100644
index 50e4f8e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/newsbook_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/cfilter.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/cfilter.png
deleted file mode 100644
index b80a728..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/cfilter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/compare.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/compare.png
deleted file mode 100644
index ab00daa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/compare.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/lock.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/lock.png
deleted file mode 100644
index e613f9a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/lock.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/relaunch.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/relaunch.png
deleted file mode 100644
index dbcc934..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/relaunch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/relaunchf.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/relaunchf.png
deleted file mode 100644
index 7f45578..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/relaunchf.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/select_next.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/select_next.png
deleted file mode 100644
index a010dbd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/select_next.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/select_prev.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/select_prev.png
deleted file mode 100644
index da0f8d2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/select_prev.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/stop.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/stop.png
deleted file mode 100644
index d3a0590..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/stop.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/th_automatic.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/th_automatic.png
deleted file mode 100644
index ecec4ab..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/th_automatic.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/th_horizontal.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/th_horizontal.png
deleted file mode 100644
index 10af6c0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/th_horizontal.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/th_vertical.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/th_vertical.png
deleted file mode 100644
index 16200d4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dlcl16/th_vertical.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dtool16/debugjunit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dtool16/debugjunit.png
deleted file mode 100644
index dea8415..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dtool16/debugjunit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dtool16/new_testcase.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dtool16/new_testcase.png
deleted file mode 100644
index a4d803c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dtool16/new_testcase.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dtool16/new_testsuite.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dtool16/new_testsuite.png
deleted file mode 100644
index b6c855d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dtool16/new_testsuite.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dtool16/runjunit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dtool16/runjunit.png
deleted file mode 100644
index 49b7fc6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/dtool16/runjunit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/cfilter.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/cfilter.png
deleted file mode 100644
index 3227064..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/cfilter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/compare.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/compare.png
deleted file mode 100644
index 6b7733d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/compare.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/lock.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/lock.png
deleted file mode 100644
index 6a00020..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/lock.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/relaunch.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/relaunch.png
deleted file mode 100644
index 668fd32..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/relaunch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/relaunchf.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/relaunchf.png
deleted file mode 100644
index 5039cb7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/relaunchf.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/select_next.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/select_next.png
deleted file mode 100644
index 9ec7da8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/select_next.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/select_prev.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/select_prev.png
deleted file mode 100644
index 684f65c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/select_prev.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/stop.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/stop.png
deleted file mode 100644
index cddc772..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/stop.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_automatic.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_automatic.png
deleted file mode 100644
index 7ebf21f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_automatic.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_horizontal.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_horizontal.png
deleted file mode 100644
index 8d23eb3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_horizontal.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_vertical.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_vertical.png
deleted file mode 100644
index b22ac64..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_vertical.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/debugjunit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/debugjunit.png
deleted file mode 100644
index 2dcb670..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/debugjunit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/new_testcase.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/new_testcase.png
deleted file mode 100644
index 4bd7cb7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/new_testcase.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/new_testsuite.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/new_testsuite.png
deleted file mode 100644
index 1b174b9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/new_testsuite.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/runjunit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/runjunit.png
deleted file mode 100644
index 325786f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/runjunit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junit.png
deleted file mode 100644
index 3387549..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/juniterr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/juniterr.png
deleted file mode 100644
index d480412..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/juniterr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/juniterrq.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/juniterrq.png
deleted file mode 100644
index a2c0f07..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/juniterrq.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junitsucc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junitsucc.png
deleted file mode 100644
index 8c02486..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junitsucc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junitsuccq.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junitsuccq.png
deleted file mode 100644
index 3ceb8a3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junitsuccq.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/stackframe.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/stackframe.png
deleted file mode 100644
index dc403bb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/stackframe.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/exc_catch.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/exc_catch.png
deleted file mode 100644
index c226cab..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/exc_catch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/faillist.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/faillist.png
deleted file mode 100644
index 574f0b9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/faillist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/failures.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/failures.png
deleted file mode 100644
index c2f1cbe..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/failures.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/julaunch.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/julaunch.png
deleted file mode 100644
index 4dad425..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/julaunch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/stkfrm_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/stkfrm_obj.png
deleted file mode 100644
index dc403bb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/stkfrm_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/test.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/test.png
deleted file mode 100644
index 8bba0b1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/test.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testerr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testerr.png
deleted file mode 100644
index 57396bd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testerr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testfail.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testfail.png
deleted file mode 100644
index 5742eb9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testfail.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testhier.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testhier.png
deleted file mode 100644
index fd9bd17..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testhier.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testok.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testok.png
deleted file mode 100644
index 9321db9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testok.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testrun.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testrun.png
deleted file mode 100644
index eb55546..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testrun.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuite.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuite.png
deleted file mode 100644
index f7dbbee..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuite.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiteerror.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiteerror.png
deleted file mode 100644
index 3d4a095..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiteerror.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuitefail.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuitefail.png
deleted file mode 100644
index 4e79f60..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuitefail.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiteok.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiteok.png
deleted file mode 100644
index 1d79ce1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiteok.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiterun.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiterun.png
deleted file mode 100644
index d5306b0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiterun.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/error_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/error_ovr.png
deleted file mode 100644
index 24e921d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/error_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/failed_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/failed_ovr.png
deleted file mode 100644
index 93baf01..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/failed_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/success_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/success_ovr.png
deleted file mode 100644
index cd59f45..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/success_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff1.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff1.png
deleted file mode 100644
index 0ddfd61..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff2.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff2.png
deleted file mode 100644
index 0d5cd8f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff3.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff3.png
deleted file mode 100644
index 118a572..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff4.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff4.png
deleted file mode 100644
index 5a37d3f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff5.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff5.png
deleted file mode 100644
index ed8b164..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff5.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff6.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff6.png
deleted file mode 100644
index 3a30fa7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff6.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff7.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff7.png
deleted file mode 100644
index c9c69e2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff7.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff8.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff8.png
deleted file mode 100644
index 0d0001c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff8.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff9.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff9.png
deleted file mode 100644
index 26b789e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff9.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss1.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss1.png
deleted file mode 100644
index fa0006b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss2.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss2.png
deleted file mode 100644
index cdfd34e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss3.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss3.png
deleted file mode 100644
index 89d59a5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss4.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss4.png
deleted file mode 100644
index 03b38c6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss5.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss5.png
deleted file mode 100644
index 9f689a5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss5.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss6.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss6.png
deleted file mode 100644
index e775d83..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss6.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss7.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss7.png
deleted file mode 100644
index 9f29839..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss7.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss8.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss8.png
deleted file mode 100644
index c5f006b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss8.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss9.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss9.png
deleted file mode 100644
index 86b3a81..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss9.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/wizban/newsuite_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/wizban/newsuite_wiz.png
deleted file mode 100644
index 0674cb9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/wizban/newsuite_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/wizban/newtest_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/wizban/newtest_wiz.png
deleted file mode 100644
index ce6ffb0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/wizban/newtest_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/add_as_source_folder.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/add_as_source_folder.png
deleted file mode 100644
index 7bff4de..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/add_as_source_folder.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/add_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/add_exc.png
deleted file mode 100644
index 77dea43..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/add_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/add_linked_source_to_buildpath.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/add_linked_source_to_buildpath.png
deleted file mode 100644
index 0c642a9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/add_linked_source_to_buildpath.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/add_to_buildpath.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/add_to_buildpath.png
deleted file mode 100644
index b20eced..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/add_to_buildpath.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/alphab_sort_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/alphab_sort_co.png
deleted file mode 100644
index a15803e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/alphab_sort_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/ch_callees.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/ch_callees.png
deleted file mode 100644
index 151f2ce..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/ch_callees.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/ch_callers.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/ch_callers.png
deleted file mode 100644
index 8050d7f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/ch_callers.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/ch_cancel.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/ch_cancel.png
deleted file mode 100644
index d3a0590..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/ch_cancel.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/class_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/class_obj.png
deleted file mode 100644
index 65d05bc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/class_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/clear_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/clear_co.png
deleted file mode 100644
index d17bc9e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/clear_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/collapseall.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/collapseall.png
deleted file mode 100644
index bdba4db..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/collapseall.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/configure_build_path.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/configure_build_path.png
deleted file mode 100644
index 3b28d65..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/configure_build_path.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/configure_buildpath_filters.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/configure_buildpath_filters.png
deleted file mode 100644
index baa6f50..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/configure_buildpath_filters.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/configure_output_folder.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/configure_output_folder.png
deleted file mode 100644
index 7b927d8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/configure_output_folder.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/default_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/default_co.png
deleted file mode 100644
index 9e0f577..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/default_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/definingtype_sort_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/definingtype_sort_co.png
deleted file mode 100644
index 5c8fdef..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/definingtype_sort_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/exc_catch.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/exc_catch.png
deleted file mode 100644
index b34551b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/exc_catch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/exclude_from_buildpath.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/exclude_from_buildpath.png
deleted file mode 100644
index c431944..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/exclude_from_buildpath.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/exclusion_filter_attrib.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/exclusion_filter_attrib.png
deleted file mode 100644
index 1b508f0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/exclusion_filter_attrib.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/fields_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/fields_co.png
deleted file mode 100644
index 6a1c567..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/fields_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/file_mode.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/file_mode.png
deleted file mode 100644
index 12d1d13..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/file_mode.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/filter_ps.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/filter_ps.png
deleted file mode 100644
index d697cb8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/filter_ps.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/flatLayout.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/flatLayout.png
deleted file mode 100644
index 6591eb0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/flatLayout.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/gointo_toplevel_type.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/gointo_toplevel_type.png
deleted file mode 100644
index cfd6700..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/gointo_toplevel_type.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/goto_input.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/goto_input.png
deleted file mode 100644
index 22f4633..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/goto_input.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/hide_externalized.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/hide_externalized.png
deleted file mode 100644
index eac98f5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/hide_externalized.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/hide_ignored.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/hide_ignored.png
deleted file mode 100644
index 800063a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/hide_ignored.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/hide_internalized.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/hide_internalized.png
deleted file mode 100644
index 136aa56..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/hide_internalized.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/hierarchicalLayout.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/hierarchicalLayout.png
deleted file mode 100644
index c2869a0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/hierarchicalLayout.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/hierarchy_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/hierarchy_co.png
deleted file mode 100644
index 4f25bbd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/hierarchy_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/history_list.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/history_list.png
deleted file mode 100644
index 7c7cc8c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/history_list.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/impl_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/impl_co.png
deleted file mode 100644
index 575c59e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/impl_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/include_on_buildpath.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/include_on_buildpath.png
deleted file mode 100644
index fa7e18f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/include_on_buildpath.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/inclusion_filter_attrib.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/inclusion_filter_attrib.png
deleted file mode 100644
index 51c661f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/inclusion_filter_attrib.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/inher_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/inher_co.png
deleted file mode 100644
index 8cb3225..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/inher_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/localtypes_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/localtypes_co.png
deleted file mode 100644
index 3518e5f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/localtypes_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/metharg_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/metharg_obj.png
deleted file mode 100644
index d7d5d65..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/metharg_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/newpackfolder_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/newpackfolder_wiz.png
deleted file mode 100644
index 4d4a881..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/newpackfolder_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/output_folder_attrib.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/output_folder_attrib.png
deleted file mode 100644
index 5268f24..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/output_folder_attrib.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/pack_empty_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/pack_empty_co.png
deleted file mode 100644
index 398a547..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/pack_empty_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/package_mode.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/package_mode.png
deleted file mode 100644
index 3ae5b59..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/package_mode.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/private_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/private_co.png
deleted file mode 100644
index 513643e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/private_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/prj_mode.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/prj_mode.png
deleted file mode 100644
index 291ae71..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/prj_mode.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/protected_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/protected_co.png
deleted file mode 100644
index 189d711..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/protected_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/public_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/public_co.png
deleted file mode 100644
index 19cf402..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/public_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/refresh_nav.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/refresh_nav.png
deleted file mode 100644
index 2bf2011..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/refresh_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/remove_as_source_folder.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/remove_as_source_folder.png
deleted file mode 100644
index c29b8a8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/remove_as_source_folder.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/remove_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/remove_exc.png
deleted file mode 100644
index 1d3ee9e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/remove_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/remove_from_buildpath.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/remove_from_buildpath.png
deleted file mode 100644
index f15c88e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/remove_from_buildpath.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/removea_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/removea_exc.png
deleted file mode 100644
index 7d5a844..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/removea_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/search_sortmatch.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/search_sortmatch.png
deleted file mode 100644
index aa76fbc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/search_sortmatch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/smartmode_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/smartmode_co.png
deleted file mode 100644
index 8f46d38..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/smartmode_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/static_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/static_co.png
deleted file mode 100644
index 458531e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/static_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/sub_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/sub_co.png
deleted file mode 100644
index c57c1b8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/sub_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/super_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/super_co.png
deleted file mode 100644
index 08bdf47..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/super_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/synced.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/synced.png
deleted file mode 100644
index d28c6b7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/synced.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/text_edit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/text_edit.png
deleted file mode 100644
index 3607a5c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/text_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/th_automatic.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/th_automatic.png
deleted file mode 100644
index ecec4ab..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/th_automatic.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/th_horizontal.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/th_horizontal.png
deleted file mode 100644
index 65ab5bc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/th_horizontal.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/th_showqualified.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/th_showqualified.png
deleted file mode 100644
index 65abe30..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/th_showqualified.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/th_single.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/th_single.png
deleted file mode 100644
index 7f6fb8b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/th_single.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/th_vertical.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/th_vertical.png
deleted file mode 100644
index 71ca263..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/th_vertical.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/type_mode.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/type_mode.png
deleted file mode 100644
index 9e9ef32..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/type_mode.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/view_menu.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/view_menu.png
deleted file mode 100644
index b68d27c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dlcl16/view_menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/comment_edit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/comment_edit.png
deleted file mode 100644
index 6761454..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/comment_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/exportapp_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/exportapp_wiz.png
deleted file mode 100644
index 14548d5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/exportapp_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/exportjar_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/exportjar_wiz.png
deleted file mode 100644
index dd2400a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/exportjar_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/importjar_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/importjar_wiz.png
deleted file mode 100644
index 3ca8d16..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/importjar_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/java_app.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/java_app.png
deleted file mode 100644
index 7634a6d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/java_app.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/java_attach.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/java_attach.png
deleted file mode 100644
index f1bf44d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/java_attach.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/javadoc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/javadoc.png
deleted file mode 100644
index 5b7d232..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/javadoc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/jdoc_hover_edit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/jdoc_hover_edit.png
deleted file mode 100644
index 91bef8f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/jdoc_hover_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/mark_occurrences.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/mark_occurrences.png
deleted file mode 100644
index a5009a8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/mark_occurrences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newannotation_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newannotation_wiz.png
deleted file mode 100644
index 0338913..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newannotation_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newclass_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newclass_wiz.png
deleted file mode 100644
index 0d0b8f8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newclass_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newenum_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newenum_wiz.png
deleted file mode 100644
index e50d986..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newenum_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newint_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newint_wiz.png
deleted file mode 100644
index bf4df85..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newint_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newjprj_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newjprj_wiz.png
deleted file mode 100644
index 05dd237..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newjprj_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newjworkingSet_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newjworkingSet_wiz.png
deleted file mode 100644
index 7634a6d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newjworkingSet_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newpack_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newpack_wiz.png
deleted file mode 100644
index 66076e4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newpack_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newpackfolder_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newpackfolder_wiz.png
deleted file mode 100644
index 4d4a881..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newpackfolder_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newsbook_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newsbook_wiz.png
deleted file mode 100644
index fb3388a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/newsbook_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/opentype.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/opentype.png
deleted file mode 100644
index 61dbfb6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/opentype.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/segment_edit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/segment_edit.png
deleted file mode 100644
index 52639ad..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/segment_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/shift_l_edit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/shift_l_edit.png
deleted file mode 100644
index cdaff43..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/shift_l_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/shift_r_edit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/shift_r_edit.png
deleted file mode 100644
index 112b9c9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/dtool16/shift_r_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_as_source_folder.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_as_source_folder.png
deleted file mode 100644
index da64778..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_as_source_folder.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_exc.png
deleted file mode 100644
index 6d48492..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_linked_source_to_buildpath.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_linked_source_to_buildpath.png
deleted file mode 100644
index 7b105a9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_linked_source_to_buildpath.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_to_buildpath.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_to_buildpath.png
deleted file mode 100644
index 38fe830..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_to_buildpath.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/alphab_sort_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/alphab_sort_co.png
deleted file mode 100644
index 6ead1de..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/alphab_sort_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_callees.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_callees.png
deleted file mode 100644
index 9688673..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_callees.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_callers.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_callers.png
deleted file mode 100644
index a07fa2f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_callers.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_cancel.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_cancel.png
deleted file mode 100644
index cddc772..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_cancel.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/class_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/class_obj.png
deleted file mode 100644
index 3158b41..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/class_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/clear_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/clear_co.png
deleted file mode 100644
index 890b626..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/clear_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/collapseall.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/collapseall.png
deleted file mode 100644
index 611a8c5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/collapseall.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_build_path.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_build_path.png
deleted file mode 100644
index 3c1123f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_build_path.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_buildpath_filters.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_buildpath_filters.png
deleted file mode 100644
index 166803d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_buildpath_filters.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_output_folder.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_output_folder.png
deleted file mode 100644
index 66a5db7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_output_folder.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/default_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/default_co.png
deleted file mode 100644
index ac1983f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/default_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/definingtype_sort_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/definingtype_sort_co.png
deleted file mode 100644
index 10a24b2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/definingtype_sort_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exc_catch.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exc_catch.png
deleted file mode 100644
index 912d98d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exc_catch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exclude_from_buildpath.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exclude_from_buildpath.png
deleted file mode 100644
index 6d45a38..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exclude_from_buildpath.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exclusion_filter_attrib.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exclusion_filter_attrib.png
deleted file mode 100644
index 8db750d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exclusion_filter_attrib.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/fields_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/fields_co.png
deleted file mode 100644
index e6f29ae..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/fields_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/file_mode.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/file_mode.png
deleted file mode 100644
index f94e413..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/file_mode.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/filter_ps.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/filter_ps.png
deleted file mode 100644
index ba649ab..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/filter_ps.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/flatLayout.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/flatLayout.png
deleted file mode 100644
index 728e0d0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/flatLayout.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/gointo_toplevel_type.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/gointo_toplevel_type.png
deleted file mode 100644
index c3eab69..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/gointo_toplevel_type.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/goto_input.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/goto_input.png
deleted file mode 100644
index 2a9d6fa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/goto_input.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/help.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/help.png
deleted file mode 100644
index 9a71283..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/help.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_externalized.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_externalized.png
deleted file mode 100644
index 2d262ba..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_externalized.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_ignored.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_ignored.png
deleted file mode 100644
index 04bfa11..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_ignored.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_internalized.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_internalized.png
deleted file mode 100644
index a7cf68c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_internalized.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hierarchicalLayout.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hierarchicalLayout.png
deleted file mode 100644
index a9355ea..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hierarchicalLayout.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hierarchy_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hierarchy_co.png
deleted file mode 100644
index 149fcf7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hierarchy_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/history_list.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/history_list.png
deleted file mode 100644
index dd65c94..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/history_list.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/impl_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/impl_co.png
deleted file mode 100644
index 39e2431..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/impl_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/include_on_buildpath.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/include_on_buildpath.png
deleted file mode 100644
index a1ad8df..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/include_on_buildpath.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/inclusion_filter_attrib.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/inclusion_filter_attrib.png
deleted file mode 100644
index b0afee8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/inclusion_filter_attrib.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/inher_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/inher_co.png
deleted file mode 100644
index 9dcf491..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/inher_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/localtypes_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/localtypes_co.png
deleted file mode 100644
index 62df84a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/localtypes_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/metharg_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/metharg_obj.png
deleted file mode 100644
index ccefd75..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/metharg_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/pack_empty_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/pack_empty_co.png
deleted file mode 100644
index d4b5f0f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/pack_empty_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/package_mode.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/package_mode.png
deleted file mode 100644
index d300af9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/package_mode.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/private_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/private_co.png
deleted file mode 100644
index 6b17504..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/private_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/prj_mode.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/prj_mode.png
deleted file mode 100644
index eed93c8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/prj_mode.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/protected_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/protected_co.png
deleted file mode 100644
index cd3c7f4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/protected_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/public_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/public_co.png
deleted file mode 100644
index 659619d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/public_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/refresh_nav.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/refresh_nav.png
deleted file mode 100644
index 5e996e1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/refresh_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_as_source_folder.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_as_source_folder.png
deleted file mode 100644
index e88e086..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_as_source_folder.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_exc.png
deleted file mode 100644
index 91e4e01..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_from_buildpath.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_from_buildpath.png
deleted file mode 100644
index 0ffe5c2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_from_buildpath.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/removea_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/removea_exc.png
deleted file mode 100644
index 73053c4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/removea_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/search_sortmatch.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/search_sortmatch.png
deleted file mode 100644
index cec4466..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/search_sortmatch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/smartmode_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/smartmode_co.png
deleted file mode 100644
index ea23610..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/smartmode_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/static_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/static_co.png
deleted file mode 100644
index 1f1134d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/static_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/sub_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/sub_co.png
deleted file mode 100644
index 2d17d53..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/sub_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/super_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/super_co.png
deleted file mode 100644
index 89b1bf9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/super_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/synced.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/synced.png
deleted file mode 100644
index 7d54854..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/synced.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_automatic.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_automatic.png
deleted file mode 100644
index 7ebf21f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_automatic.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_horizontal.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_horizontal.png
deleted file mode 100644
index 8d23eb3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_horizontal.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_showqualified.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_showqualified.png
deleted file mode 100644
index c9e0dde..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_showqualified.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_single.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_single.png
deleted file mode 100644
index c6ff25e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_single.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_vertical.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_vertical.png
deleted file mode 100644
index b22ac64..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_vertical.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/type_mode.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/type_mode.png
deleted file mode 100644
index a8058e9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/type_mode.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/view_menu.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/view_menu.png
deleted file mode 100644
index af96ccb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/view_menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/comment_edit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/comment_edit.png
deleted file mode 100644
index 0687fcc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/comment_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/exportapp_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/exportapp_wiz.png
deleted file mode 100644
index 905d88f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/exportapp_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/exportjar_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/exportjar_wiz.png
deleted file mode 100644
index 7a0c048..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/exportjar_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/importjar_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/importjar_wiz.png
deleted file mode 100644
index 701ff59..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/importjar_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/java_app.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/java_app.png
deleted file mode 100644
index ee268ce..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/java_app.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/java_attach.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/java_attach.png
deleted file mode 100644
index a085071..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/java_attach.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/javadoc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/javadoc.png
deleted file mode 100644
index 002e8f5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/javadoc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/jdoc_hover_edit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/jdoc_hover_edit.png
deleted file mode 100644
index 0b3cd9e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/jdoc_hover_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/mark_occurrences.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/mark_occurrences.png
deleted file mode 100644
index c7a5b09..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/mark_occurrences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newannotation_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newannotation_wiz.png
deleted file mode 100644
index e80bb18..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newannotation_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newclass_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newclass_wiz.png
deleted file mode 100644
index 5ef0b5c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newclass_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newenum_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newenum_wiz.png
deleted file mode 100644
index 3f37799..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newenum_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newint_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newint_wiz.png
deleted file mode 100644
index 5f394a8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newint_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newjprj_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newjprj_wiz.png
deleted file mode 100644
index 576da69..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newjprj_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newjworkingSet_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newjworkingSet_wiz.png
deleted file mode 100644
index ee268ce..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newjworkingSet_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newpack_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newpack_wiz.png
deleted file mode 100644
index db1ca46..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newpack_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newpackfolder_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newpackfolder_wiz.png
deleted file mode 100644
index 73097a0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newpackfolder_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newsbook_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newsbook_wiz.png
deleted file mode 100644
index 8887b6d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newsbook_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/opentype.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/opentype.png
deleted file mode 100644
index 4879264..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/opentype.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/segment_edit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/segment_edit.png
deleted file mode 100644
index 99d537e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/segment_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/shift_l_edit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/shift_l_edit.png
deleted file mode 100644
index 05131a5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/shift_l_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/shift_r_edit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/shift_r_edit.png
deleted file mode 100644
index fb31861..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/shift_r_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/browse_persp.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/browse_persp.png
deleted file mode 100644
index 5b7314a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/browse_persp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/call_hierarchy.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/call_hierarchy.png
deleted file mode 100644
index 74ab5c7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/call_hierarchy.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/class_hi.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/class_hi.png
deleted file mode 100644
index 94ca97e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/class_hi.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/classfilegeneration_tab.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/classfilegeneration_tab.png
deleted file mode 100644
index 8103f27..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/classfilegeneration_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/errorwarning_tab.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/errorwarning_tab.png
deleted file mode 100644
index 2413af5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/errorwarning_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/hierch_persp.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/hierch_persp.png
deleted file mode 100644
index 92fc00e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/hierch_persp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/javadoc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/javadoc.png
deleted file mode 100644
index d4cdfd1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/javadoc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/jdkcompliance_tab.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/jdkcompliance_tab.png
deleted file mode 100644
index 9dea8a5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/jdkcompliance_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/jperspective.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/jperspective.png
deleted file mode 100644
index 46005b6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/jperspective.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/members.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/members.png
deleted file mode 100644
index 1373ef3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/members.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/package.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/package.png
deleted file mode 100644
index 7ed990f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/package.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/packages.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/packages.png
deleted file mode 100644
index f716ab9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/packages.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/projects.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/projects.png
deleted file mode 100644
index bb37ddc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/projects.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/source.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/source.png
deleted file mode 100644
index 427cc76..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/source.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/types.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/types.png
deleted file mode 100644
index d35ffca..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/types.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/access_restriction_attrib.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/access_restriction_attrib.png
deleted file mode 100644
index a9fea6e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/access_restriction_attrib.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/add_correction.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/add_correction.png
deleted file mode 100644
index 6d48492..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/add_correction.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_alt_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_alt_obj.png
deleted file mode 100644
index 7ecac62..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_alt_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_default_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_default_obj.png
deleted file mode 100644
index 75e69db..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_default_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_obj.png
deleted file mode 100644
index fb9a252..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_private_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_private_obj.png
deleted file mode 100644
index 2cd51c2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_private_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_protected_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_protected_obj.png
deleted file mode 100644
index bc66583..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_protected_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/brkpi_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/brkpi_obj.png
deleted file mode 100644
index 4354230..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/brkpi_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/change.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/change.png
deleted file mode 100644
index 2a70312..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/change.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/class_default_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/class_default_obj.png
deleted file mode 100644
index 8d42ac8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/class_default_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/class_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/class_obj.png
deleted file mode 100644
index b763245..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/class_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classf_generate.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classf_generate.png
deleted file mode 100644
index 876397e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classf_generate.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classf_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classf_obj.png
deleted file mode 100644
index cec8fe3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classf_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classfo_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classfo_obj.png
deleted file mode 100644
index 1241905..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classfo_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/collapsed.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/collapsed.png
deleted file mode 100644
index 97a160d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/collapsed.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/compare_field.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/compare_field.png
deleted file mode 100644
index 0c659a2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/compare_field.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/compare_method.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/compare_method.png
deleted file mode 100644
index 77e7d27..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/compare_method.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/composite_change.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/composite_change.png
deleted file mode 100644
index 2bc7bd8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/composite_change.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_cast.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_cast.png
deleted file mode 100644
index 3ff8c21..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_cast.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_change.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_change.png
deleted file mode 100644
index e6c6c8f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_change.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_delete_import.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_delete_import.png
deleted file mode 100644
index fb0867e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_delete_import.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_move.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_move.png
deleted file mode 100644
index d5d818d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_move.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_rename.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_rename.png
deleted file mode 100644
index e6c6c8f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_rename.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cp_order_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cp_order_obj.png
deleted file mode 100644
index 9c2f84a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cp_order_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cu_change.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cu_change.png
deleted file mode 100644
index bee2c9e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cu_change.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cu_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cu_obj.png
deleted file mode 100644
index eaa4bfe..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cu_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_logical_package_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_logical_package_obj.png
deleted file mode 100644
index 589850d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_logical_package_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_pack_fldr_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_pack_fldr_obj.png
deleted file mode 100644
index 91b70da..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_pack_fldr_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_pack_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_pack_obj.png
deleted file mode 100644
index d4b5f0f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_pack_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_alt_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_alt_obj.png
deleted file mode 100644
index a88ce15..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_alt_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_default_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_default_obj.png
deleted file mode 100644
index 343f26e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_default_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_obj.png
deleted file mode 100644
index 711c806..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_private_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_private_obj.png
deleted file mode 100644
index e47390e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_private_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_protected_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_protected_obj.png
deleted file mode 100644
index bb0e404..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_protected_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/envvar_nonexist_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/envvar_nonexist_obj.png
deleted file mode 100644
index 602004e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/envvar_nonexist_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/envvar_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/envvar_obj.png
deleted file mode 100644
index 9044217..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/envvar_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/error_gray_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/error_gray_obj.png
deleted file mode 100644
index 4261edb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/error_gray_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/error_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/error_obj.png
deleted file mode 100644
index f29bb8b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/error_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/exclusion_filter_attrib.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/exclusion_filter_attrib.png
deleted file mode 100644
index 79481e2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/exclusion_filter_attrib.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/expanded.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/expanded.png
deleted file mode 100644
index f3fce8f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/expanded.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/externalize.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/externalize.png
deleted file mode 100644
index b9a2970..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/externalize.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/fatalerror_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/fatalerror_obj.png
deleted file mode 100644
index 0220931..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/fatalerror_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_default_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_default_obj.png
deleted file mode 100644
index f2336c6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_default_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_private_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_private_obj.png
deleted file mode 100644
index e88e002..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_private_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_protected_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_protected_obj.png
deleted file mode 100644
index b8ce728..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_protected_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_public_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_public_obj.png
deleted file mode 100644
index 6c163f5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_public_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/file_change.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/file_change.png
deleted file mode 100644
index c9b7ad8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/file_change.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/file_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/file_obj.png
deleted file mode 100644
index 24ed3ea..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/file_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/history_working_set_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/history_working_set_obj.png
deleted file mode 100644
index ff97fc3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/history_working_set_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/html_tag_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/html_tag_obj.png
deleted file mode 100644
index 07ec71f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/html_tag_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/ignore.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/ignore.png
deleted file mode 100644
index eca1cc4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/ignore.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/imp_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/imp_obj.png
deleted file mode 100644
index 96da039..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/imp_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/impc_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/impc_obj.png
deleted file mode 100644
index f6e2819..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/impc_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/implm_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/implm_co.png
deleted file mode 100644
index 377d7a3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/implm_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/inclusion_filter_attrib.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/inclusion_filter_attrib.png
deleted file mode 100644
index 1738ad3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/inclusion_filter_attrib.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/info_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/info_obj.png
deleted file mode 100644
index 42d44bb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/info_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_default_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_default_obj.png
deleted file mode 100644
index 8d42ac8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_default_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_private_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_private_obj.png
deleted file mode 100644
index f0f0dd0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_private_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_protected_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_protected_obj.png
deleted file mode 100644
index b07081f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_protected_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_public_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_public_obj.png
deleted file mode 100644
index b763245..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_public_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_default_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_default_obj.png
deleted file mode 100644
index 9a155f0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_default_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_private_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_private_obj.png
deleted file mode 100644
index 73a1c72..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_private_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_protected_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_protected_obj.png
deleted file mode 100644
index fc329ee..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_protected_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_public_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_public_obj.png
deleted file mode 100644
index 8142855..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_public_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/int_default_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/int_default_obj.png
deleted file mode 100644
index 9a155f0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/int_default_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/int_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/int_obj.png
deleted file mode 100644
index 8142855..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/int_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/internalize.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/internalize.png
deleted file mode 100644
index c0d4dc5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/internalize.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/intf_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/intf_obj.png
deleted file mode 100644
index babf844..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/intf_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_desc_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_desc_obj.png
deleted file mode 100644
index 424091d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_desc_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_l_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_l_obj.png
deleted file mode 100644
index aeee881..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_l_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_lsrc_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_lsrc_obj.png
deleted file mode 100644
index 1ba21b1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_lsrc_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_nonexist_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_nonexist_obj.png
deleted file mode 100644
index 789ba37..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_nonexist_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_obj.png
deleted file mode 100644
index af4d58f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_src_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_src_obj.png
deleted file mode 100644
index 938e372..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_src_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/java_model_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/java_model_obj.png
deleted file mode 100644
index 1c20f32..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/java_model_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/javadoc_location_attrib.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/javadoc_location_attrib.png
deleted file mode 100644
index f5285ef..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/javadoc_location_attrib.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jcu_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jcu_obj.png
deleted file mode 100644
index fa9ad47..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jcu_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jcu_resource_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jcu_resource_obj.png
deleted file mode 100644
index d3bbbb2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jcu_resource_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jdoc_tag_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jdoc_tag_obj.png
deleted file mode 100644
index d4cdfd1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jdoc_tag_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jexception_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jexception_obj.png
deleted file mode 100644
index c226cab..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jexception_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jexceptiond_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jexceptiond_obj.png
deleted file mode 100644
index a2ab6e1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jexceptiond_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jrtexception_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jrtexception_obj.png
deleted file mode 100644
index 6d90522..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jrtexception_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jsbook_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jsbook_obj.png
deleted file mode 100644
index a58e816..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jsbook_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jsearch_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jsearch_obj.png
deleted file mode 100644
index b6dcf74..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jsearch_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jworkingSet_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jworkingSet_obj.png
deleted file mode 100644
index 31303b7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jworkingSet_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/library_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/library_obj.png
deleted file mode 100644
index e21e089..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/library_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/localvariable_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/localvariable_obj.png
deleted file mode 100644
index 13a0f92..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/localvariable_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/logical_package_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/logical_package_obj.png
deleted file mode 100644
index e7911e2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/logical_package_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methdef_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methdef_obj.png
deleted file mode 100644
index cbd58a5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methdef_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpri_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpri_obj.png
deleted file mode 100644
index bf432c0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpri_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpro_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpro_obj.png
deleted file mode 100644
index c23f54c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpro_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpub_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpub_obj.png
deleted file mode 100644
index a032863..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpub_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/native_lib_path_attrib.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/native_lib_path_attrib.png
deleted file mode 100644
index 5dba2c2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/native_lib_path_attrib.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/never_translate.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/never_translate.png
deleted file mode 100644
index 204f5e7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/never_translate.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/nls_search_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/nls_search_obj.png
deleted file mode 100644
index d537e9a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/nls_search_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/no_breakpoint.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/no_breakpoint.png
deleted file mode 100644
index 6bd79e2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/no_breakpoint.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_match.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_match.png
deleted file mode 100644
index c08590a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_match.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_read.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_read.png
deleted file mode 100644
index b526346..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_read.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_write.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_write.png
deleted file mode 100644
index 06286dd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_write.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/output_folder_attrib.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/output_folder_attrib.png
deleted file mode 100644
index fabb060..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/output_folder_attrib.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/over_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/over_co.png
deleted file mode 100644
index 4187bc3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/over_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/package_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/package_obj.png
deleted file mode 100644
index 922c435..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/package_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/packagefolder_nonexist_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/packagefolder_nonexist_obj.png
deleted file mode 100644
index b38a023..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/packagefolder_nonexist_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/packagefolder_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/packagefolder_obj.png
deleted file mode 100644
index 64b97cc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/packagefolder_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/packd_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/packd_obj.png
deleted file mode 100644
index c9e0dde..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/packd_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/prjct_nonexist_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/prjct_nonexist_obj.png
deleted file mode 100644
index 8f199d8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/prjct_nonexist_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickassist_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickassist_obj.png
deleted file mode 100644
index 62cdf90..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickassist_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickfix_error_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickfix_error_obj.png
deleted file mode 100644
index de6d4bd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickfix_error_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickfix_warning_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickfix_warning_obj.png
deleted file mode 100644
index b21c3fb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickfix_warning_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/remove_correction.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/remove_correction.png
deleted file mode 100644
index 2310de3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/remove_correction.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/search_decl_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/search_decl_obj.png
deleted file mode 100644
index bde4c96..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/search_decl_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/search_ref_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/search_ref_obj.png
deleted file mode 100644
index fee2907..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/search_ref_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/searchm_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/searchm_obj.png
deleted file mode 100644
index 2dca488..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/searchm_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/skip.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/skip.png
deleted file mode 100644
index 0634268..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/skip.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/source_attach_attrib.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/source_attach_attrib.png
deleted file mode 100644
index 99d0b64..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/source_attach_attrib.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/template_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/template_obj.png
deleted file mode 100644
index d1b3efc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/template_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/text_edit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/text_edit.png
deleted file mode 100644
index 594806d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/text_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/translate.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/translate.png
deleted file mode 100644
index e3e9baa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/translate.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/type_separator.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/type_separator.png
deleted file mode 100644
index 321474a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/type_separator.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/typevariable_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/typevariable_obj.png
deleted file mode 100644
index 0977bdf..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/typevariable_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/unknown_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/unknown_obj.png
deleted file mode 100644
index 1065efa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/unknown_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/warning_gray_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/warning_gray_obj.png
deleted file mode 100644
index 9cc943c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/warning_gray_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/warning_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/warning_obj.png
deleted file mode 100644
index 5d9da44..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/warning_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/abstract_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/abstract_co.png
deleted file mode 100644
index ce61b92..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/abstract_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/callee_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/callee_co.png
deleted file mode 100644
index 0869f53..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/callee_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/caller_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/caller_co.png
deleted file mode 100644
index f2575ce..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/caller_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/constr_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/constr_ovr.png
deleted file mode 100644
index d400f98..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/constr_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/deprecated.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/deprecated.png
deleted file mode 100644
index b851b53..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/deprecated.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/error_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/error_co.png
deleted file mode 100644
index afb5bbd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/error_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/final_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/final_co.png
deleted file mode 100644
index dbedc29..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/final_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/focus_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/focus_ovr.png
deleted file mode 100644
index df5fd6a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/focus_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/implm_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/implm_co.png
deleted file mode 100644
index 09931ba..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/implm_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/java_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/java_ovr.png
deleted file mode 100644
index a08d70d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/java_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/maxlevel_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/maxlevel_co.png
deleted file mode 100644
index 270ce61..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/maxlevel_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/native_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/native_co.png
deleted file mode 100644
index bb34d4d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/native_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/over_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/over_co.png
deleted file mode 100644
index 53afd41..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/over_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/read.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/read.png
deleted file mode 100644
index 8f32a86a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/read.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/recursive_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/recursive_co.png
deleted file mode 100644
index d698835..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/recursive_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/run_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/run_co.png
deleted file mode 100644
index a7eb514..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/run_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/static_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/static_co.png
deleted file mode 100644
index d654189..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/static_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/sync_impl.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/sync_impl.png
deleted file mode 100644
index 97cb623..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/sync_impl.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/sync_over.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/sync_over.png
deleted file mode 100644
index 5b22c6e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/sync_over.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/synch_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/synch_co.png
deleted file mode 100644
index 9809abb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/synch_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/volatile_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/volatile_co.png
deleted file mode 100644
index 26434fc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/volatile_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/warning_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/warning_co.png
deleted file mode 100644
index 20fe5b3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/warning_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/write.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/write.png
deleted file mode 100644
index 7d8c2c9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/write.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/addlibrary_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/addlibrary_wiz.png
deleted file mode 100644
index fd9effb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/addlibrary_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/coderefact_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/coderefact_wiz.png
deleted file mode 100644
index b82f53a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/coderefact_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/compunitrefact_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/compunitrefact_wiz.png
deleted file mode 100644
index 952ca9a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/compunitrefact_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/export_javadoc_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/export_javadoc_wiz.png
deleted file mode 100644
index bbeb013..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/export_javadoc_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/exportapp_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/exportapp_wiz.png
deleted file mode 100644
index e43b616..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/exportapp_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/extstr_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/extstr_wiz.png
deleted file mode 100644
index 3614cfa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/extstr_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/fieldrefact_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/fieldrefact_wiz.png
deleted file mode 100644
index 98e7eba..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/fieldrefact_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/jar_pack_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/jar_pack_wiz.png
deleted file mode 100644
index b95cd1b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/jar_pack_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/java_app_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/java_app_wiz.png
deleted file mode 100644
index b90be86..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/java_app_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/java_attach_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/java_attach_wiz.png
deleted file mode 100644
index 1a66fcd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/java_attach_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/java_workingset_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/java_workingset_wiz.png
deleted file mode 100644
index e76f9ce..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/java_workingset_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/methrefact_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/methrefact_wiz.png
deleted file mode 100644
index 6006fe9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/methrefact_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newannotation_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newannotation_wiz.png
deleted file mode 100644
index 9f3242a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newannotation_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newclass_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newclass_wiz.png
deleted file mode 100644
index 5926d03..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newclass_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newenum_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newenum_wiz.png
deleted file mode 100644
index 4b1e436..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newenum_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newfield_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newfield_wiz.png
deleted file mode 100644
index 7e7aeb1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newfield_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newint_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newint_wiz.png
deleted file mode 100644
index 1ab6d57..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newint_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newjprj_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newjprj_wiz.png
deleted file mode 100644
index f9c8104..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newjprj_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newmeth_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newmeth_wiz.png
deleted file mode 100644
index 912d713..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newmeth_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newpack_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newpack_wiz.png
deleted file mode 100644
index 4ab38bb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newpack_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newsbook_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newsbook_wiz.png
deleted file mode 100644
index 4f4bac8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newsbook_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newsrcfldr_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newsrcfldr_wiz.png
deleted file mode 100644
index d635b59..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/newsrcfldr_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/packrefact_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/packrefact_wiz.png
deleted file mode 100644
index 1bf21a6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/packrefact_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/pullup_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/pullup_wiz.png
deleted file mode 100644
index bc3f7df..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/pullup_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/refactor_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/refactor_wiz.png
deleted file mode 100644
index 3e85f59..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/refactor_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/typerefact_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/typerefact_wiz.png
deleted file mode 100644
index 13337bc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/wizban/typerefact_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/collapseall.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/collapseall.png
deleted file mode 100644
index e6a51f2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/collapseall.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/expandall.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/expandall.png
deleted file mode 100644
index 76b77e8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/expandall.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/flatLayout.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/flatLayout.png
deleted file mode 100644
index db81cbd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/flatLayout.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/hierarchicalLayout.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/hierarchicalLayout.png
deleted file mode 100644
index 3d9a9cf..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/hierarchicalLayout.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_goto.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_goto.png
deleted file mode 100644
index 24c3762..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_goto.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_history.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_history.png
deleted file mode 100644
index d0405d4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_history.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_next.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_next.png
deleted file mode 100644
index ec7c956..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_next.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_prev.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_prev.png
deleted file mode 100644
index a7a3daa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_prev.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_rem.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_rem.png
deleted file mode 100644
index 1d3ee9e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_rem.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_remall.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_remall.png
deleted file mode 100644
index 7d5a844..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_remall.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_sortmatch.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_sortmatch.png
deleted file mode 100644
index 625e4da..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/search_sortmatch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/stop.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/stop.png
deleted file mode 100644
index d3a0590..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/stop.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/tsearch_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/tsearch_obj.png
deleted file mode 100644
index cc31082..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dlcl16/tsearch_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dtool16/group_by_file.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dtool16/group_by_file.png
deleted file mode 100644
index a805c69..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dtool16/group_by_file.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dtool16/group_by_folder.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dtool16/group_by_folder.png
deleted file mode 100644
index 97ce0fc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dtool16/group_by_folder.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dtool16/group_by_project.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dtool16/group_by_project.png
deleted file mode 100644
index 291ae71..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dtool16/group_by_project.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dtool16/search.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dtool16/search.png
deleted file mode 100644
index be877f4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/dtool16/search.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/collapseall.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/collapseall.png
deleted file mode 100644
index 2349877..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/collapseall.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/expandall.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/expandall.png
deleted file mode 100644
index 494c77c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/expandall.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/flatLayout.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/flatLayout.png
deleted file mode 100644
index 728e0d0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/flatLayout.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/hierarchicalLayout.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/hierarchicalLayout.png
deleted file mode 100644
index a9355ea..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/hierarchicalLayout.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_goto.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_goto.png
deleted file mode 100644
index d731f83..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_goto.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_history.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_history.png
deleted file mode 100644
index c2724d9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_history.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_next.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_next.png
deleted file mode 100644
index 9ec7da8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_next.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_prev.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_prev.png
deleted file mode 100644
index 684f65c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_prev.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_rem.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_rem.png
deleted file mode 100644
index 91e4e01..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_rem.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_remall.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_remall.png
deleted file mode 100644
index 73053c4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_remall.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_sortmatch.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_sortmatch.png
deleted file mode 100644
index a374bc5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/search_sortmatch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/stop.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/stop.png
deleted file mode 100644
index cddc772..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/stop.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/tsearch_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/tsearch_obj.png
deleted file mode 100644
index 7466003..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/elcl16/tsearch_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/etool16/group_by_file.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/etool16/group_by_file.png
deleted file mode 100644
index 82b68b4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/etool16/group_by_file.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/etool16/group_by_folder.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/etool16/group_by_folder.png
deleted file mode 100644
index 2f6bee8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/etool16/group_by_folder.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/etool16/group_by_project.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/etool16/group_by_project.png
deleted file mode 100644
index 90e8308..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/etool16/group_by_project.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/etool16/search.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/etool16/search.png
deleted file mode 100644
index 95e60a5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/etool16/search.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/eview16/searchres.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/eview16/searchres.png
deleted file mode 100644
index 95e60a5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/eview16/searchres.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/obj16/searchm_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/obj16/searchm_obj.png
deleted file mode 100644
index e466a46..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/obj16/searchm_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/obj16/tsearch_dpdn_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/obj16/tsearch_dpdn_obj.png
deleted file mode 100644
index c7134fe..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.search/obj16/tsearch_dpdn_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-1.png b/bundles/org.eclipse.jdt.doc.user/images/qs-1.png
deleted file mode 100644
index 12b10b6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-10.png b/bundles/org.eclipse.jdt.doc.user/images/qs-10.png
deleted file mode 100644
index 3ef8829..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-10.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-11.png b/bundles/org.eclipse.jdt.doc.user/images/qs-11.png
deleted file mode 100644
index 024c77b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-11.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-12.png b/bundles/org.eclipse.jdt.doc.user/images/qs-12.png
deleted file mode 100644
index bcfa01a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-12.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-13.png b/bundles/org.eclipse.jdt.doc.user/images/qs-13.png
deleted file mode 100644
index e21535f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-13.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-13a.png b/bundles/org.eclipse.jdt.doc.user/images/qs-13a.png
deleted file mode 100644
index f7873c0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-13a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-14.png b/bundles/org.eclipse.jdt.doc.user/images/qs-14.png
deleted file mode 100644
index 262356a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-14.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-15.png b/bundles/org.eclipse.jdt.doc.user/images/qs-15.png
deleted file mode 100644
index 0ff8b7a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-15.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-15a.png b/bundles/org.eclipse.jdt.doc.user/images/qs-15a.png
deleted file mode 100644
index 48061b7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-15a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-16.png b/bundles/org.eclipse.jdt.doc.user/images/qs-16.png
deleted file mode 100644
index c9c313b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-16.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-17.png b/bundles/org.eclipse.jdt.doc.user/images/qs-17.png
deleted file mode 100644
index b9eafd5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-17.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-17a.png b/bundles/org.eclipse.jdt.doc.user/images/qs-17a.png
deleted file mode 100644
index e40e798..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-17a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-17b.png b/bundles/org.eclipse.jdt.doc.user/images/qs-17b.png
deleted file mode 100644
index 5980517..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-17b.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-17c.png b/bundles/org.eclipse.jdt.doc.user/images/qs-17c.png
deleted file mode 100644
index cfe2618..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-17c.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-17c1.png b/bundles/org.eclipse.jdt.doc.user/images/qs-17c1.png
deleted file mode 100644
index 8735f9f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-17c1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-17c2.png b/bundles/org.eclipse.jdt.doc.user/images/qs-17c2.png
deleted file mode 100644
index b0a4864..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-17c2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-17d.png b/bundles/org.eclipse.jdt.doc.user/images/qs-17d.png
deleted file mode 100644
index 506c588..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-17d.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-17e.png b/bundles/org.eclipse.jdt.doc.user/images/qs-17e.png
deleted file mode 100644
index f944358..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-17e.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-17f.png b/bundles/org.eclipse.jdt.doc.user/images/qs-17f.png
deleted file mode 100644
index 17813e6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-17f.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-18.png b/bundles/org.eclipse.jdt.doc.user/images/qs-18.png
deleted file mode 100644
index ba72daa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-18.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-19.png b/bundles/org.eclipse.jdt.doc.user/images/qs-19.png
deleted file mode 100644
index 3e11250..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-19.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-2.png b/bundles/org.eclipse.jdt.doc.user/images/qs-2.png
deleted file mode 100644
index a613b83..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-20.png b/bundles/org.eclipse.jdt.doc.user/images/qs-20.png
deleted file mode 100644
index 44776c4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-20.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-21.png b/bundles/org.eclipse.jdt.doc.user/images/qs-21.png
deleted file mode 100644
index 28df8e2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-21.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-22.png b/bundles/org.eclipse.jdt.doc.user/images/qs-22.png
deleted file mode 100644
index aaa04fa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-22.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-23.png b/bundles/org.eclipse.jdt.doc.user/images/qs-23.png
deleted file mode 100644
index 332fc1a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-23.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-24.png b/bundles/org.eclipse.jdt.doc.user/images/qs-24.png
deleted file mode 100644
index 654ac5d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-24.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-25.png b/bundles/org.eclipse.jdt.doc.user/images/qs-25.png
deleted file mode 100644
index 25f85a8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-25.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-26.png b/bundles/org.eclipse.jdt.doc.user/images/qs-26.png
deleted file mode 100644
index a3a9a30..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-26.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-27.png b/bundles/org.eclipse.jdt.doc.user/images/qs-27.png
deleted file mode 100644
index 1c87db8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-27.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-28.png b/bundles/org.eclipse.jdt.doc.user/images/qs-28.png
deleted file mode 100644
index 31ee728..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-28.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-29.png b/bundles/org.eclipse.jdt.doc.user/images/qs-29.png
deleted file mode 100644
index 9924753..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-29.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-3.png b/bundles/org.eclipse.jdt.doc.user/images/qs-3.png
deleted file mode 100644
index 576ecd6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-30.png b/bundles/org.eclipse.jdt.doc.user/images/qs-30.png
deleted file mode 100644
index 869f4c0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-30.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-31.png b/bundles/org.eclipse.jdt.doc.user/images/qs-31.png
deleted file mode 100644
index 0fe2004..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-31.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-32.png b/bundles/org.eclipse.jdt.doc.user/images/qs-32.png
deleted file mode 100644
index 2022882..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-32.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-33.png b/bundles/org.eclipse.jdt.doc.user/images/qs-33.png
deleted file mode 100644
index 8d450fc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-33.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-33a.png b/bundles/org.eclipse.jdt.doc.user/images/qs-33a.png
deleted file mode 100644
index 4b5b326..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-33a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-33b.png b/bundles/org.eclipse.jdt.doc.user/images/qs-33b.png
deleted file mode 100644
index 8b8e70e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-33b.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-34.png b/bundles/org.eclipse.jdt.doc.user/images/qs-34.png
deleted file mode 100644
index fb3547c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-34.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-35.png b/bundles/org.eclipse.jdt.doc.user/images/qs-35.png
deleted file mode 100644
index 55f093f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-35.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-36.png b/bundles/org.eclipse.jdt.doc.user/images/qs-36.png
deleted file mode 100644
index 0fdb056..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-36.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-37.png b/bundles/org.eclipse.jdt.doc.user/images/qs-37.png
deleted file mode 100644
index fadf2d9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-37.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-37a.png b/bundles/org.eclipse.jdt.doc.user/images/qs-37a.png
deleted file mode 100644
index 0dafde5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-37a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-37b.png b/bundles/org.eclipse.jdt.doc.user/images/qs-37b.png
deleted file mode 100644
index 6f1de75..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-37b.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-38.png b/bundles/org.eclipse.jdt.doc.user/images/qs-38.png
deleted file mode 100644
index 7db3d9b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-38.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-39.png b/bundles/org.eclipse.jdt.doc.user/images/qs-39.png
deleted file mode 100644
index 99d2e0b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-39.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-40.png b/bundles/org.eclipse.jdt.doc.user/images/qs-40.png
deleted file mode 100644
index dae9777..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-40.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-41.png b/bundles/org.eclipse.jdt.doc.user/images/qs-41.png
deleted file mode 100644
index 0319a38..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-41.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-42.png b/bundles/org.eclipse.jdt.doc.user/images/qs-42.png
deleted file mode 100644
index a991142..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-42.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-43.png b/bundles/org.eclipse.jdt.doc.user/images/qs-43.png
deleted file mode 100644
index a3a3484..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-43.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-43a.png b/bundles/org.eclipse.jdt.doc.user/images/qs-43a.png
deleted file mode 100644
index 90aad51..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-43a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-43b.png b/bundles/org.eclipse.jdt.doc.user/images/qs-43b.png
deleted file mode 100644
index 689532c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-43b.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-43c.png b/bundles/org.eclipse.jdt.doc.user/images/qs-43c.png
deleted file mode 100644
index 3ef1176..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-43c.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-43d.png b/bundles/org.eclipse.jdt.doc.user/images/qs-43d.png
deleted file mode 100644
index b679bcd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-43d.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-43e.png b/bundles/org.eclipse.jdt.doc.user/images/qs-43e.png
deleted file mode 100644
index b484f0a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-43e.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-43f.png b/bundles/org.eclipse.jdt.doc.user/images/qs-43f.png
deleted file mode 100644
index 1db3069..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-43f.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-44.png b/bundles/org.eclipse.jdt.doc.user/images/qs-44.png
deleted file mode 100644
index 668c4a7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-44.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-46.png b/bundles/org.eclipse.jdt.doc.user/images/qs-46.png
deleted file mode 100644
index 195663b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-46.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-47.png b/bundles/org.eclipse.jdt.doc.user/images/qs-47.png
deleted file mode 100644
index ebf897e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-47.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-48.png b/bundles/org.eclipse.jdt.doc.user/images/qs-48.png
deleted file mode 100644
index 186942b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-48.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-49.png b/bundles/org.eclipse.jdt.doc.user/images/qs-49.png
deleted file mode 100644
index 12e0f61..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-49.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-5.png b/bundles/org.eclipse.jdt.doc.user/images/qs-5.png
deleted file mode 100644
index ee0945c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-5.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-50.png b/bundles/org.eclipse.jdt.doc.user/images/qs-50.png
deleted file mode 100644
index c1aca9c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-50.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-52.png b/bundles/org.eclipse.jdt.doc.user/images/qs-52.png
deleted file mode 100644
index db757e1c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-52.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-53.png b/bundles/org.eclipse.jdt.doc.user/images/qs-53.png
deleted file mode 100644
index f1d1f6d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-53.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-54.png b/bundles/org.eclipse.jdt.doc.user/images/qs-54.png
deleted file mode 100644
index 0a60ee5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-54.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-55.png b/bundles/org.eclipse.jdt.doc.user/images/qs-55.png
deleted file mode 100644
index 8ea97c3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-55.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-56.png b/bundles/org.eclipse.jdt.doc.user/images/qs-56.png
deleted file mode 100644
index f645d3d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-56.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-6.png b/bundles/org.eclipse.jdt.doc.user/images/qs-6.png
deleted file mode 100644
index 505b410..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-6.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-7.png b/bundles/org.eclipse.jdt.doc.user/images/qs-7.png
deleted file mode 100644
index fbf6f3a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-7.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-8.png b/bundles/org.eclipse.jdt.doc.user/images/qs-8.png
deleted file mode 100644
index 25f7fa4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-8.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-9.png b/bundles/org.eclipse.jdt.doc.user/images/qs-9.png
deleted file mode 100644
index bafba4b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-9.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-DetectingExistingLayout1.png b/bundles/org.eclipse.jdt.doc.user/images/qs-DetectingExistingLayout1.png
deleted file mode 100644
index faca518..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-DetectingExistingLayout1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-DetectingExistingLayout2.png b/bundles/org.eclipse.jdt.doc.user/images/qs-DetectingExistingLayout2.png
deleted file mode 100644
index d9e761a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-DetectingExistingLayout2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-DetectingExistingLayout3.png b/bundles/org.eclipse.jdt.doc.user/images/qs-DetectingExistingLayout3.png
deleted file mode 100644
index 02d22a4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-DetectingExistingLayout3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-DetectingExistingLayout4.png b/bundles/org.eclipse.jdt.doc.user/images/qs-DetectingExistingLayout4.png
deleted file mode 100644
index 7d486b6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-DetectingExistingLayout4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources1.png b/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources1.png
deleted file mode 100644
index 4825da5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources2.png b/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources2.png
deleted file mode 100644
index f4dedcb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources3.png b/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources3.png
deleted file mode 100644
index 3a763ea..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources4.png b/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources4.png
deleted file mode 100644
index 53cd119..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources5.png b/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources5.png
deleted file mode 100644
index 5ae288c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources5.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources6.png b/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources6.png
deleted file mode 100644
index 897a6f2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources6.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources7.png b/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources7.png
deleted file mode 100644
index f79df1a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources7.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources8.png b/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources8.png
deleted file mode 100644
index f93472b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-OrganizeSources8.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout10.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout10.png
deleted file mode 100644
index fe32429..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout10.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout11.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout11.png
deleted file mode 100644
index 97e57a7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout11.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout12.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout12.png
deleted file mode 100644
index ab662fc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout12.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout13.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout13.png
deleted file mode 100644
index 8ef3d55..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout13.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout14.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout14.png
deleted file mode 100644
index 46ba82a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout14.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout20.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout20.png
deleted file mode 100644
index 167d822..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout20.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout21.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout21.png
deleted file mode 100644
index 353955e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout21.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout22.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout22.png
deleted file mode 100644
index 6f7bce3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout22.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout23.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout23.png
deleted file mode 100644
index 504369c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout23.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout24.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout24.png
deleted file mode 100644
index c373d85..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout24.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout25.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout25.png
deleted file mode 100644
index 87f0ce6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout25.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout26.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout26.png
deleted file mode 100644
index 9f00f22..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout26.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout27.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout27.png
deleted file mode 100644
index ccfc137..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout27.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout30.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout30.png
deleted file mode 100644
index 1aaa4f0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout30.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout31.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout31.png
deleted file mode 100644
index 676101b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout31.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout32.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout32.png
deleted file mode 100644
index 533fec0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout32.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout33.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout33.png
deleted file mode 100644
index 4581f5c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout33.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout34.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout34.png
deleted file mode 100644
index 877e752..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout34.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout35.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout35.png
deleted file mode 100644
index 906f69e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout35.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout36.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout36.png
deleted file mode 100644
index a8f1959..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout36.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout40.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout40.png
deleted file mode 100644
index cb3c1c8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout40.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout41.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout41.png
deleted file mode 100644
index 0d250ae..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout41.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout42.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout42.png
deleted file mode 100644
index 333b0f9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout42.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout43.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout43.png
deleted file mode 100644
index 4c7b54a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout43.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout44.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout44.png
deleted file mode 100644
index c6ff6d9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout44.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout45.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout45.png
deleted file mode 100644
index 2a8b964..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout45.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout46.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout46.png
deleted file mode 100644
index a890c88..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout46.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout47.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout47.png
deleted file mode 100644
index 177cc7e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout47.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout5.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout5.png
deleted file mode 100644
index 82b1161..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout5.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout50.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout50.png
deleted file mode 100644
index 36462a0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout50.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout51.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout51.png
deleted file mode 100644
index 1d877e2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout51.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout52.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout52.png
deleted file mode 100644
index 4fd9713..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout52.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout53.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout53.png
deleted file mode 100644
index 4352c6f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout53.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout54.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout54.png
deleted file mode 100644
index 8c0be0a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout54.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout55.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout55.png
deleted file mode 100644
index c428ec1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout55.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout56.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout56.png
deleted file mode 100644
index c2768e6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout56.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout57.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout57.png
deleted file mode 100644
index ada9f4a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout57.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout58.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout58.png
deleted file mode 100644
index ed9b1ca..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout58.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout59.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout59.png
deleted file mode 100644
index 85edadc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout59.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout5A.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout5A.png
deleted file mode 100644
index 558b997..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout5A.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout5B.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout5B.png
deleted file mode 100644
index f302678..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout5B.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout60.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout60.png
deleted file mode 100644
index 31f7df9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout60.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout61.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout61.png
deleted file mode 100644
index 163c5c7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout61.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout62.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout62.png
deleted file mode 100644
index f8028f1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout62.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout63.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout63.png
deleted file mode 100644
index 1947dbd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout63.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout64.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout64.png
deleted file mode 100644
index 26a4ae1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout64.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout65.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout65.png
deleted file mode 100644
index fa441f4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout65.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout66.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout66.png
deleted file mode 100644
index 492c272..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout66.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout67.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout67.png
deleted file mode 100644
index e5ca325..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout67.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout68.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout68.png
deleted file mode 100644
index 576935c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout68.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout69.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout69.png
deleted file mode 100644
index 391184a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout69.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout6a.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout6a.png
deleted file mode 100644
index 2007a59..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout6a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout6b.png b/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout6b.png
deleted file mode 100644
index 3cbf3b0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-WorkingWithExistingLayout6b.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-browsing1.png b/bundles/org.eclipse.jdt.doc.user/images/qs-browsing1.png
deleted file mode 100644
index 2fbfab5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-browsing1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-jun1.png b/bundles/org.eclipse.jdt.doc.user/images/qs-jun1.png
deleted file mode 100644
index b7433a0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-jun1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-jun2.png b/bundles/org.eclipse.jdt.doc.user/images/qs-jun2.png
deleted file mode 100644
index 3311495..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-jun2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-jun3.png b/bundles/org.eclipse.jdt.doc.user/images/qs-jun3.png
deleted file mode 100644
index 6c58a9d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-jun3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-jun4.png b/bundles/org.eclipse.jdt.doc.user/images/qs-jun4.png
deleted file mode 100644
index 74ce13b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-jun4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-jun5.png b/bundles/org.eclipse.jdt.doc.user/images/qs-jun5.png
deleted file mode 100644
index ab8fb50..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-jun5.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-jun6.png b/bundles/org.eclipse.jdt.doc.user/images/qs-jun6.png
deleted file mode 100644
index e46f8e8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-jun6.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/qs-newjavaproject.png b/bundles/org.eclipse.jdt.doc.user/images/qs-newjavaproject.png
deleted file mode 100644
index 488c603..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/qs-newjavaproject.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/tasks-160a.png b/bundles/org.eclipse.jdt.doc.user/images/tasks-160a.png
deleted file mode 100644
index db7438f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/tasks-160a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/tasks-163a.png b/bundles/org.eclipse.jdt.doc.user/images/tasks-163a.png
deleted file mode 100644
index 8ea3f2a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/tasks-163a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/tasks-166a.png b/bundles/org.eclipse.jdt.doc.user/images/tasks-166a.png
deleted file mode 100644
index 7beef47..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/tasks-166a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/tasks-166b.png b/bundles/org.eclipse.jdt.doc.user/images/tasks-166b.png
deleted file mode 100644
index 5d08cf1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/tasks-166b.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/tasks-168a.png b/bundles/org.eclipse.jdt.doc.user/images/tasks-168a.png
deleted file mode 100644
index eba45a2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/tasks-168a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/tasks-170a.png b/bundles/org.eclipse.jdt.doc.user/images/tasks-170a.png
deleted file mode 100644
index b6297d3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/tasks-170a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/tasks-189a.png b/bundles/org.eclipse.jdt.doc.user/images/tasks-189a.png
deleted file mode 100644
index e96a247..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/tasks-189a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/tasks-190a.png b/bundles/org.eclipse.jdt.doc.user/images/tasks-190a.png
deleted file mode 100644
index 9035bf8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/tasks-190a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/tasks-199a.png b/bundles/org.eclipse.jdt.doc.user/images/tasks-199a.png
deleted file mode 100644
index e550901..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/tasks-199a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/tasks-208a.png b/bundles/org.eclipse.jdt.doc.user/images/tasks-208a.png
deleted file mode 100644
index 118dc9f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/tasks-208a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/tasks-208b.png b/bundles/org.eclipse.jdt.doc.user/images/tasks-208b.png
deleted file mode 100644
index 5eea188..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/tasks-208b.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/tasks-209a.png b/bundles/org.eclipse.jdt.doc.user/images/tasks-209a.png
deleted file mode 100644
index 64df6df..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/tasks-209a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/tasks-27.png b/bundles/org.eclipse.jdt.doc.user/images/tasks-27.png
deleted file mode 100644
index e7ab394..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/tasks-27.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/tasks-28.png b/bundles/org.eclipse.jdt.doc.user/images/tasks-28.png
deleted file mode 100644
index c30c411..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/tasks-28.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/tasks-29.png b/bundles/org.eclipse.jdt.doc.user/images/tasks-29.png
deleted file mode 100644
index 230a75e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/tasks-29.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/tasks-30.png b/bundles/org.eclipse.jdt.doc.user/images/tasks-30.png
deleted file mode 100644
index 551ad46..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/tasks-30.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/tasks-31.png b/bundles/org.eclipse.jdt.doc.user/images/tasks-31.png
deleted file mode 100644
index 8ed8ffb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/tasks-31.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/tasks-32.png b/bundles/org.eclipse.jdt.doc.user/images/tasks-32.png
deleted file mode 100644
index 204b778..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/tasks-32.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/tasks-46.png b/bundles/org.eclipse.jdt.doc.user/images/tasks-46.png
deleted file mode 100644
index 6c9f90f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/tasks-46.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/tasks-8.png b/bundles/org.eclipse.jdt.doc.user/images/tasks-8.png
deleted file mode 100644
index c8e7afe..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/tasks-8.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/tasks_200a.png b/bundles/org.eclipse.jdt.doc.user/images/tasks_200a.png
deleted file mode 100644
index 7914299..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/tasks_200a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/tasks_201a.png b/bundles/org.eclipse.jdt.doc.user/images/tasks_201a.png
deleted file mode 100644
index 8dfc914..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/tasks_201a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/tasks_205a.png b/bundles/org.eclipse.jdt.doc.user/images/tasks_205a.png
deleted file mode 100644
index c0c1889..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/tasks_205a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/notices.html b/bundles/org.eclipse.jdt.doc.user/notices.html
deleted file mode 100644
index 03ff544..0000000
--- a/bundles/org.eclipse.jdt.doc.user/notices.html
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <LINK REL="STYLESHEET" HREF="book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Legal Notices</title>
-</head>
-<body>
-
-<h3>
-<a NAME="Notices"></a>Notices</h3>
-<p>
-The material in this guide is Copyright (c) IBM Corporation and others 2000, 2005.
-</p>
-<p>
-<a href="about.html">Terms and conditions regarding the use of this guide.</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/plugin.properties b/bundles/org.eclipse.jdt.doc.user/plugin.properties
deleted file mode 100644
index c608241..0000000
--- a/bundles/org.eclipse.jdt.doc.user/plugin.properties
+++ /dev/null

@@ -1,12 +0,0 @@
-###############################################################################
-# Copyright (c) 2000, 2005 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-pluginName=Eclipse Java Development User Guide
-providerName=Eclipse.org

diff --git a/bundles/org.eclipse.jdt.doc.user/plugin.xml b/bundles/org.eclipse.jdt.doc.user/plugin.xml
deleted file mode 100644
index 733be6b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/plugin.xml
+++ /dev/null

@@ -1,60 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?eclipse version="3.0"?>
-
-<!-- ===================================================== -->
-<!-- Declare the documentation for the JDT User Guide  -->
-<!-- We will declare only one infoset (book)               -->
-<!-- ===================================================== -->
-
-<plugin>
-
-
-<!-- ============================================================================= -->
-<!-- Define primary TOC                                                            -->
-<!-- ============================================================================= -->
-
-   <extension point="org.eclipse.help.toc"> 
-       <toc file="toc.xml" primary="true" />
-       <index path="index"/>
-   </extension>
-
-
-<!-- ============================================================================= -->
-<!-- Define TOCs                                                                   -->
-<!-- ============================================================================= -->
-
-   <extension point="org.eclipse.help.toc">
-       <toc file="topics_GettingStarted.xml" />
-	   <toc file="topics_TipsTricks.xml" />
-       <toc file="topics_Concepts.xml" />
-       <toc file="topics_Tasks.xml" />
-       <toc file="topics_Reference.xml" />
-   </extension>
-
-
-<!-- ============================================================================= -->
-<!-- F1 context files                                                              -->
-<!-- ============================================================================= -->
-
-	<extension point="org.eclipse.help.contexts"> 
-		<contexts file="contexts_JDT.xml" plugin="org.eclipse.jdt.ui"/> 
-	</extension>
-
-	<extension point="org.eclipse.help.contexts">
-		<contexts file="contexts_Debugger.xml" plugin="org.eclipse.debug.ui"/> 
-		<contexts file="contexts_Debugger.xml" plugin="org.eclipse.ui.console"/> 
-	</extension>
-	
-	<extension point="org.eclipse.help.contexts">
-		<contexts file="contexts_JDT_Debugger.xml" plugin="org.eclipse.jdt.debug.ui"/> 
-	</extension>
-
-	<extension point="org.eclipse.help.contexts">
-		<contexts file="contexts_JDT_JUnit.xml" plugin="org.eclipse.jdt.junit"/> 
-	</extension>
-	
-	<extension point="org.eclipse.help.contexts">
-   		<contexts file="contexts_APT.xml" plugin="org.eclipse.jdt.apt.ui"/>
-	</extension>
-
-</plugin>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/brkAccess.htm b/bundles/org.eclipse.jdt.doc.user/reference/brkAccess.htm
deleted file mode 100644
index accf7a9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/brkAccess.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Access
-    </title>
-  </head>
-  <body>
-    <h1>
-      Access
-    </h1>
-    <p>
-      When this option is turned on, the watchpoint causes execution to suspend on access of a field.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-      </p>
-      <p>
-       <a href="../concepts/cbrkpnts.htm">Breakpoints</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-     </p>
-     <p>
-    	<a href="../tasks/tasks-144.htm">Adding breakpoints</a><br>
-    	<a href="../tasks/tasks-144a.htm">Removing breakpoints</a><br>
-    	<a href="../tasks/tasks-130.htm">Launching a Java program</a> <br>
-		<a href="../tasks/tasks-126.htm">Running and debugging</a> 
-	 </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/brkEntry.htm b/bundles/org.eclipse.jdt.doc.user/reference/brkEntry.htm
deleted file mode 100644
index d55d9e4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/brkEntry.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Entry
-    </title>
-  </head>
-  <body>
-    <h1>
-      Entry
-    </h1>
-    <p>
-      When this option is turned on, the breakpoint causes execution to suspend on entry of the method.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-      </p>
-      <p>
-      <a href="../tasks/tasks-145.htm">Setting method breakpoints</a>
-	</p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/brkExit.htm b/bundles/org.eclipse.jdt.doc.user/reference/brkExit.htm
deleted file mode 100644
index 8d30eb4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/brkExit.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Exit
-    </title>
-  </head>
-  <body>
-    <h1>
-      Exit
-    </h1>
-    <p>
-      When this option is turned on, the breakpoint causes execution to suspend on exit of the method.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-      </p>
-      <p>
-      <a href="../tasks/tasks-145.htm">Setting method breakpoints</a>
-	</p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/brkMod.htm b/bundles/org.eclipse.jdt.doc.user/reference/brkMod.htm
deleted file mode 100644
index 7307fb3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/brkMod.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Modification
-    </title>
-  </head>
-  <body>
-    <h1>
-      Modification
-    </h1>
-    <p>
-      When this option is turned on, the watchpoint causes execution to suspend on modification of a field.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-      </p>
-      <p>
-       <a href="../concepts/cbrkpnts.htm">Breakpoints</a>
-	</p>
-	<p>
-       <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-       </p>
-       <p>
-    	<a href="../tasks/tasks-144.htm">Adding breakpoints</a><br>
-    	<a href="../tasks/tasks-144a.htm">Removing breakpoints</a><br>
-	    <a href="../tasks/tasks-130.htm">Launching a Java program</a><br>
-     <a href="../tasks/tasks-126.htm">Running and debugging</a> 
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/brkProperties.htm b/bundles/org.eclipse.jdt.doc.user/reference/brkProperties.htm
deleted file mode 100644
index a3a73e3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/brkProperties.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Properties
-    </title>
-  </head>
-  <body>
-    <h1>
-      Properties
-    </h1>
-    <p>
-      This action realizes a breakpoint properties dialog for the currently selected breakpoint
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-     </p>
-     <p>
-      <a href="../tasks/tasks-144.htm">Adding breakpoints</a><br>
-       <a href="../tasks/tasks-146.htm">Applying hit counts</a><br>
-       <a href="../tasks/tasks-147.htm">Catching Java exceptions</a><br>
-       <a href="../tasks/tasks-144a.htm">Removing breakpoints</a><br>
-       <a href="../tasks/tasks-144b.htm">Enabling and disabling breakpoints</a><br>
-       <a href="../tasks/tasks-144c.htm">Managing conditional breakpoints</a><br>
-       <a href="../tasks/tasks-145.htm">Setting method breakpoints</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/brkSelectAll.htm b/bundles/org.eclipse.jdt.doc.user/reference/brkSelectAll.htm
deleted file mode 100644
index c138871..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/brkSelectAll.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Select all
-    </title>
-  </head>
-  <body>
-    <h1>
-      Select all
-    </h1>
-    <p>
-      This command selects all breakpoints in the <strong>Breakpoints view</strong>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/brkShowSupported.htm b/bundles/org.eclipse.jdt.doc.user/reference/brkShowSupported.htm
deleted file mode 100644
index dc7cf3d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/brkShowSupported.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Show supported breakpoints
-    </title>
-  </head>
-  <body>
-    <h1>
-      Show supported breakpoints
-    </h1>
-    
-<p> When this action is toggled on, the breakpoints view only displays breakpoints 
-  applicable to the selected debug target. </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/brkSuspendPolicy.htm b/bundles/org.eclipse.jdt.doc.user/reference/brkSuspendPolicy.htm
deleted file mode 100644
index 1417c01..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/brkSuspendPolicy.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Suspend policy
-    </title>
-  </head>
-  <body>
-    <h1>
-      Suspend policy
-    </h1>
-    
-<p> This action toggles the suspend policy of a breakpoint between suspending 
-  all of the threads in the VM and the thread in which the breakpoint occurred.<br>
-      <br>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-     </p>
-     <p>
-      <a href="../concepts/cbrkpnts.htm">Breakpoints</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-      </p>
-      <p>
-    	<a href="../tasks/tasks-144.htm">Adding breakpoints</a><br>
-    	<a href="../tasks/tasks-144a.htm">Removing breakpoints</a><br>
-    	<a href="../tasks/tasks-130.htm">Launching a Java program</a><br>
-      	<a href="../tasks/tasks-126.htm">Running and debugging</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-11.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-11.htm
deleted file mode 100644
index 67f980f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-11.htm
+++ /dev/null

@@ -1,134 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Debug preferences
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Debug preferences
-    </h1>
-    <p>
-      The following preferences can be set using the Debug Preferences page.
-    </p>
- 
-<table border="1" cellspacing="0" cellpadding="5" >
-  <caption> <br>
-  </caption>
-  <tbody> 
-  <tr> 
-    <th> 
-      <p> Option </p>
-    </th>
-    <th> 
-      <p> Description </p>
-    </th>
-    <th> 
-      <p> Default </p>
-    </th>
-  </tr>
-  <tr> 
-    <td align="left" valign="top"> 
-      <p> Build (if required) before launching </p>
-    </td>
-    <td align="left" valign="top"> 
-      <p> If the workspace requires building, an incremental build will be performed 
-        prior to launching an application. </p>
-    </td>
-    <td align="left" valign="top"> 
-      <p> On </p>
-    </td>
-  </tr>
-  <tr> 
-    <td align="left" valign="top"> 
-      <p> Remove terminated launches when a new launch is created </p>
-    </td>
-    <td align="left" valign="top"> 
-      <p> When an application is launched, all terminated applications in the 
-        Debug view are automatically cleared. </p>
-    </td>
-    <td align="left" valign="top"> 
-      <p> On</p>
-    </td>
-  </tr>
-  <tr> 
-    <td align="left" valign="top"> 
-      <p> Reuse editor when displaying source code </p>
-    </td>
-    <td align="left" valign="top"> 
-      <p> The debugger displays source code in an editor when stepping through 
-        an application. When this option is on, the debugger will reuse the editor 
-        that it opened to display source from different source files. This prevents 
-        the debugger from opening an excessive number of editors. When this option 
-        is off, the debugger will open a new editor for each source file that 
-        needs to be displayed. </p>
-    </td>
-    <td align="left" valign="top"> 
-      <p> On </p>
-    </td>
-  </tr>
-  <tr> 
-    <td align="left" valign="top">Activate the workbench when when a breakpoint 
-      is hit</td>
-    <td align="left" valign="top">This option brings attention to the debugger 
-      when a breakpoint is encountered, by activating the associated window. The 
-      visual result varies from platform to platform. For example, on Windows, 
-      the associated window's title bar will flash.</td>
-    <td align="left" valign="top">On</td>
-  </tr>
-  <tr> 
-    <td align="left" valign="top"> 
-      <p> Save dirty editors before launching </p>
-    </td>
-    <td align="left" valign="top"> 
-      <p> This option controls whether the user will be prompted to save any dirty 
-        editors before an application is launched. The allowable settings are: 
-      </p>
-      <ul>
-        <li> Never - when this option is selected, the user is never prompted 
-          to save dirty editors, and editors are not automatically saved. </li>
-        <li> Prompt - when this option is selected, the user is prompted to save 
-          dirty editors before launching an application. </li>
-        <li> Auto-save - when this option is selected, any dirty editors are automatically 
-          saved before launching (and the user is not prompted). </li>
-      </ul>
-    </td>
-    <td align="left" valign="top"> 
-      <p> Prompt </p>
-    </td>
-  </tr>
-  </tbody> 
-</table>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-10.htm">Debugger</a><br>
-       <a href="../concepts/clocdbug.htm">Local Debugging</a><br>
-       <a href="../concepts/cremdbug.htm">Remote Debugging</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related Tasks" border="0" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-9.htm">Changing Debugger Launch Options</a><br>
-       <a href="../tasks/tasks-133.htm">Preparing to Debug</a><br>
-       <a href="../tasks/tasks-126.htm">Running and Debugging</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="ref-131.htm">Java search tab</a><br>
-       <a href="ref-menu-search.htm">Search menu</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-115.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-115.htm
deleted file mode 100644
index ee22cbf..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-115.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Refactoring
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Refactoring
-    </h1>
-    <p>
-      The goal of refactoring support is to allow for improving your code without changing its behavior. When you refactor your code, your goal is to make a system-wide coding
-      change without affecting the semantic behavior of the system. The JDT automatically manages refactorings for you.
-    </p>
-    <p>
-      The workbench optionally allows you to preview all the impending results of a refactoring action before you finally choose to carry it out.
-    </p>
-    <p>
-      Refactoring commands are available from the context menus in many views and editors and the <a href="ref-menu-refactor.htm">Refactor menu</a> in the menu bar.
-    </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-9.htm">Refactoring support</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="ref-menu-refactor.htm">Refactoring actions</a><br>
-       <a href="ref-117.htm">Refactoring wizard</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-117.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-117.htm
deleted file mode 100644
index 3209574..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-117.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Refactoring Dialog
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Refactoring Dialog
-    </h1>
-    <p>
-      A dialog based user interface guides you through the steps necessary to execute a selected refactoring.
-      Depending on the complexity of the refactoring, either a wizard or a simple dialog is used to gather information that is required for the refactoring.
-    </p>
-    <p>
-      <ul>
-        <li><a href="ref-117a.htm">Wizard based user interface</a> (used for example, for <em>Pull Up</em>)</li>
-        <li><a href="ref-117b.htm">Dialog based user interface</a> (used for example, for <em>Rename</em>)</li>
-      </ul>
-    </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-9.htm">Refactoring support</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="ref-menu-refactor.htm">Refactoring actions</a><br>
-    </p>
-    <p>
-      <a href="ref-156.htm">Icons</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-117a.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-117a.htm
deleted file mode 100644
index 3663944..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-117a.htm
+++ /dev/null

@@ -1,118 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Wizard based refactoring user interface
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Wizard based refactoring user interface</h1>
-    <p>
-      A wizard based user interface guides you through the steps necessary to execute a refactoring.
-      A refactoring wizard consists of 1 - n parameter pages, a preview page and a problem page.</p><h2>
-      Parameter pages
-    </h2>
-    <p>
-      These pages gather information that is required for the refactoring. For example, the 
-      <em>Pull Up</em> refactoring uses two pages to gather the methods and fields to be pulled 
-      up and to gather the obsolete methods and fields in subclasses that can be deleted. The
-      user can navigate the parameter pages using the <strong>Next &gt;</strong> and <strong>
-      &lt; Back</strong> button.
-    </p>
-    <p>
-      After you have provided the required information, you can click&nbsp;<strong><strong>Finish</strong></strong> to carry out the refactoring without previewing
-      the results. If you want to preview the changes press <strong>Next &gt;</strong>.</p>
-    <h2>
-      Preview page
-    </h2>
-    <p>
-      The JDT allows you to preview the results of a refactoring action before you execute it.
-    </p>
-    <p>
-      The preview page consists of two parts:
-    </p>
-    <ul>
-      <li>
-        A tree at the top containing all Java elements affected by the refactoring. Each top-level node in the tree represents one compilation unit.
-      </li>
-      <li>
-        A compare viewer at the bottom. The left side of the compare viewer shows the original, the right side displays the refactored source.
-      </li>
-    </ul>
-    <h2>
-      Problem page
-    </h2>
-    <p>
-      The Refactoring Problem page indicates if there are suspected, potential, or definite problems with the refactoring action you are attempting.
-    </p>
-    <p>
-      Four types of problems are possible:
-    </p>
-    <dl>
-      <dt>
-        Information
-      </dt>
-      <dd>
-        A problem described as Information will not affect the refactoring in any way, nor will it negatively affect the code in the workbench. You can most likely ignore this type of
-        problem.
-      </dd>
-      <dt>
-        Warnings
-      </dt>
-      <dd>
-        Warnings attempt to predict compiler warnings. This type of problem most likely will not negatively affect the code in your workbench.
-      </dd>
-      <dt>
-        Errors
-      </dt>
-      <dd>
-        A problem described as an Error is very likely to cause compiler errors or change your workbench code semantically. You can choose to continue with the refactoring in spite of these
-        errors, although it is not recommended.
-      </dd>
-      <dt>
-        Stop problems
-      </dt>
-      <dd>
-        This type of problem prevents the refactoring from taking place. For example, if you select a comment and choose the Extract Method command from it, the
-        workbench will issue a stop problem on the refactoring attempt because you cannot extract a comment.
-	  </dd>
-    </dl>
-    <p>
-      If there aren't any stop problems then the refactoring can be carried out by pressing the <strong>
-      Finish</strong> button. To preview the results of the refactoring action, press the
-      <strong>Next &gt;</strong> button.
-    </p>
-
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-9.htm">Refactoring support</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="../tasks/tasks-84.htm">Previewing refactoring changes</a><br>
-       <a href="../tasks/tasks-100.htm">Undoing a refactoring operation</a><br>
-       <a href="../tasks/tasks-101.htm">Redoing a refactoring operation</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="ref-menu-refactor.htm">Refactoring actions</a><br>
-    </p>
-    <p>
-      <a href="ref-156.htm">Icons</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-117b.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-117b.htm
deleted file mode 100644
index d7d1d32..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-117b.htm
+++ /dev/null

@@ -1,122 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Dialog based refactoring user interface
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Dialog based refactoring user interface</h1>
-    <p>
-      A dialog based user interface guides you through the steps necessary to execute a selected 
-      refactoring. A dialog based refactoring user interface consists of a short first dialog 
-      gathering information that is required to execute the refactoring, a separate problem dialog 
-      that pops up if any errors are detected and a preview dialog to preview the results of a 
-      refactoring.</p>
-    <h2>
-      Input dialog
-    </h2>
-    <p>
-      This dialog gathers information that is required for the refactoring. For example, for a rename 
-      refactoring you will enter the new name for the Java element. You can either press <strong>OK
-      </strong> to execute the refactoring or <strong>Preview  &gt;</strong> to preview the result
-      of the refactoring.
-    </p>
-    <h2>
-      Preview dialog
-    </h2>
-    <p>
-      The JDT allows you to preview the results of a refactoring action before you execute it.
-    </p>
-    <p>
-      The preview dialog consists of two parts:
-    </p>
-    <ul>
-      <li>
-        A tree at the top containing all Java elements affected by the refactoring. Each top-level 
-        node in the tree represents one compilation unit.
-      </li>
-      <li>
-        A compare viewer at the bottom. The left side of the compare viewer shows the original, 
-        the right side displays the refactored source.
-      </li>
-    </ul>
-    <h2>
-      Problem dialog
-    </h2>
-    <p>
-      The problem dialog indicates if there are suspected, potential, or definite problems with the 
-      refactoring action you are attempting.
-    </p>
-    <p>
-      Four types of problems are possible:
-    </p>
-    <dl>
-      <dt>
-        Information
-      </dt>
-      <dd>
-        A problem described as Information will not affect the refactoring in any way, nor will it negatively affect the code in the workbench. You can most likely ignore this type of
-        problem.
-      </dd>
-      <dt>
-        Warnings
-      </dt>
-      <dd>
-        Warnings attempt to predict compiler warnings. This type of problem most likely will not negatively affect the code in your workbench.
-      </dd>
-      <dt>
-        Errors
-      </dt>
-      <dd>
-        A problem described as an Error is very likely to cause compiler errors or change your workbench code semantically. You can choose to continue with the refactoring in spite of these
-        errors, although it is not recommended.
-      </dd>
-      <dt>
-        Stop problems
-      </dt>
-      <dd>
-        This type of problem prevents the refactoring from taking place. For example, if you select a comment and choose the Extract Method command from it, the
-        workbench will issue a stop problem on the refactoring attempt because you cannot extract a comment.
-      </dd>
-    </dl>
-    <p>
-      If there aren't any stop problems then the refactoring can be carried out by pressing the <strong>
-      OK</strong> button. To preview the results of the refactoring action, press the
-      <strong>Continue</strong> button.
-    </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-9.htm">Refactoring support</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-82.htm">Refactoring without preview</a><br>
-       <a href="../tasks/tasks-83.htm">Refactoring with preview</a><br>
-       <a href="../tasks/tasks-84.htm">Previewing refactoring changes</a><br>
-       <a href="../tasks/tasks-100.htm">Undoing a refactoring operation</a><br>
-       <a href="../tasks/tasks-101.htm">Redoing a refactoring operation</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="ref-menu-refactor.htm">Refactoring actions</a><br>
-    </p>
-    <p>
-      <a href="ref-156.htm">Icons</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-12.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-12.htm
deleted file mode 100644
index d57c4d9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-12.htm
+++ /dev/null

@@ -1,131 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Console preferences
-    </title>
-  </head>
-  <body>
-    <h1>
-      Console preferences
-    </h1>
-    <p>
-      The following preferences can be set using the Console Preferences page. The console displays output from running applications, and allows keyboard input to be read by
-      running applications.
-    </p>
-    
-<table border="1" cellspacing="0" cellpadding= "5">
-  <thead> 
-  <tr> 
-    <th rowspan="1" colspan="1"> 
-      <p> Option </p>
-    </th>
-    <th rowspan="1" colspan="1"> 
-      <p> Description </p>
-    </th>
-    <th rowspan="1" colspan="1"> 
-      <p> Default </p>
-    </th>
-  </tr>
-  </thead> <tbody> 
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> Fixed width console </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> This preference controls whether the console has a fixed character width. 
-        When on, a maximum character width must also be specified. Some applications 
-        write long lines to the console which require horizontal scrolling to 
-        read. This can be avoided by setting the console to use a fixed width, 
-        automatically wrapping console output. </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> Off </p>
-    </td>
-  </tr>
-  <tr> 
-    <td colspan="1" valign="top" align="left">Limit console output</td>
-    <td colspan="1" valign="top" align="left">This preference limits the number 
-      of characters buffered in the console. When on, a maximum buffer size must 
-      also be specified. When console output surpasses the specified maximum, 
-      output is truncated from the beginning of the buffer.</td>
-    <td colspan="1" valign="top" align="left">On</td>
-  </tr>
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> Standard Out Text Color </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> This preference controls the color of text written to the standard output 
-        stream by an application. </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> Blue </p>
-    </td>
-  </tr>
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> Standard Error Text Color </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> This preference controls the color of text written to the standard error 
-        stream by an application. </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> Red </p>
-    </td>
-  </tr>
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> Standard In Text Color </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> This preference controls the color of text typed into the console to 
-        be read by an application. </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> Green </p>
-    </td>
-  </tr>
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> Show when program writes to standard out </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> Often, the Console view is hidden or inactive when you begin running 
-        or debugging a program that creates output. If this option is turned on, 
-        then when you run a program that produces output, the Console view is 
-        automatically opened (if necessary) and is made the active view. </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> On </p>
-    </td>
-  </tr>
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> Show when program writes to standard error </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> Often, the Console view is hidden or inactive when you begin running 
-        or debugging a program that creates error output. If this option is turned 
-        on, then when you run a program that produces error output, the Console 
-        view is automatically opened (if necessary) and is made the active view. 
-      </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> On </p>
-    </td>
-  </tr>
-  </tbody> 
-</table>
-    <p>
-      You can also click the <strong>Change</strong> button to set the font for the Console.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-121.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-121.htm
deleted file mode 100644
index cf55057..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-121.htm
+++ /dev/null

@@ -1,142 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>New Java Project Wizard</title>
-  </head>
-
-  <body>
-    <h1>New Java Project Wizard</h1>
-
-    <p>This wizard helps you create a new Java project in the workbench.</p>
-
-    <h2>Project name page</h2>
-
-    <table border="1" cellspacing="0" cellpadding="5" summary="Project name page">
-      <tr>
-        <th>Option</th>
-
-        <th>Description</th>
-
-        <th>Default</th>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Project name</td>
-
-        <td align="left" valign="top">Type a name for the new project.</td>
-
-        <td align="left" valign="top">&lt;blank&gt;</td>
-      </tr>
-
-         <tr>
-          <td valign="top">
-            Contents
-          </td>
-          <td valign="top">
-            <dl>
-              <dt>
-                <strong>Create new project in workspace:</strong>
-              </dt>
-              <dd>
-                When selected, the New Project Wizard will create a new project with the specified name in the workspace.
-              </dd>
-              <dt>
-                <strong>Create project from existing source:</strong>
-              </dt>
-              <dd>
-                 When selected, you can specify the location from which the New Java Project Wizard will retrieve
-                 an existing Java project.<br>Click on <strong>Browse...</strong> to browse for a location of an existing Java project.
-              </dd>
-            </dl>
-          </td>
-          <td valign="top">
-             workspace
-          </td>
-        </tr>
-      
-         <tr>
-          <td valign="top">
-            JDK Compliance
-          </td>
-          <td valign="top">
-            <dl>
-              <dt>
-                <strong>Use default compiler compliance:</strong>
-              </dt>
-              <dd>
-                When selected, the New Java Project Wizard creates a new Java project with the default compiler 
-                compliance. The default compiler compliance can be configured on the <a href="ref-preferences-compiler.htm">Compiler</a> preference page.
-              </dd>
-              <dt>
-                <strong>Use project specific compliance:</strong>
-              </dt>
-              <dd>
-                 When selected, you can explicitly specify the compiler compliance of the new Java project.
-              </dd>
-            </dl>
-          </td>
-          <td valign="top">
-            default compliance
-          </td>
-        </tr>
-      
-         <tr>
-          <td valign="top">
-            Project layout
-          </td>
-          <td valign="top">
-            <dl>
-              <dt>
-                <strong>Use project folder as root for sources and class files:</strong>
-              </dt>
-              <dd>
-                When selected, the project folder is used both as source folder and as output folder for class files.
-              </dd>
-              <dt>
-                <strong>Create separate source and output folders:</strong>
-              </dt>
-              <dd>
-                When selected, the New Java Project Wizard creates a source folder for Java source files and an output folder which holds the class files of the project.
-              </dd>
-            </dl>
-          </td>
-          <td valign="top">
-            Use project folder
-          </td>
-        </tr>
-      
-    </table>
-
-    <h2>Java settings page</h2>
-
-    <p>You can skip this page by pressing <span class="control">Finish</span> on the first page. Otherwise press <span class="control">Next</span> to configure the <a href="ref-123.htm">Java Build
-    Path</a>.<br>
-     If the project location on the first page has been set to an existing directory, you will be prompted if the New Java Project wizard should try to detect existing classpath
-    settings. To do this the project will be created early on the invocation of the <span class="control">Next</span> button, and the <span class="control">Back</span> will be
-    disabled on the Java Settings page.</p>
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-    <p>
-     <a href="../concepts/concepts-3.htm">Java projects</a><br>
-    </p>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-     <a href="../tasks/tasks-12.htm">Creating a new Java project</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-     <p>
-     <a href="../reference/ref-menu-file.htm">File actions</a>
-    </p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-123.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-123.htm
deleted file mode 100644
index f907f16..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-123.htm
+++ /dev/null

@@ -1,244 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>Java Build Path page</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-
-  <body>
-    <h1>Java Build Path page</h1>
-
-    <p>The options in this page indicate the build path settings for a Java project. You can reach this page through the project properties (Project &gt; Properties &gt; Java Build Path) from the context menu on a created project or the <a href="ref-menu-file.htm">File
-      menu</a> of the workbench.</p>
-
-    <p>The build class path is a list of paths visible to the compiler when building the project.</p>
-
-    <h2>Source tab</h2>
-
-    <p>Source folders are the root of packages containing .java files. The compiler will translate the contained files to .class files that will be written to the output folder. The output folder is defined per project except if a source folder specifies an own output folder.  Each source folder can define an exclusion filter to specify which resources inside the folder should not be visible to the compiler.<br>
-Resources existing in source folders are also copied to the output folder unless the setting in the <a href="ref-preferences-compiler.htm">Compiler preference
-    page</a> (Window &gt; Preferences &gt; Java &gt; Compiler &gt; Building) specifies that the resource is filtered.</p>
-
-<table border="1" cellspacing="0" cellpadding="5" summary="Source folder options" width="600">
-	<caption>Source folder options<br>
-	</caption>
-
-	<tbody>
-		<tr>
-			<th>Option</th>
-
-			<th>Description</th>
-		</tr>
-
-		<tr>
-			<td align="left" valign="top" width="20%">Add Folder</td>
-
-			<td align="left" valign="top">Creates a new folder to contain source</td>
-		</tr>
-
-		<tr>
-			<td align="left" valign="top">Edit</td>
-
-			<td align="left" valign="top">Allows to modify the currently selected
-			source folder or source folder attribute.</td>
-		</tr>
-
-		<tr>
-			<td>Remove</td>
-
-			<td>Removes the selected folders from the class path. This does not
-			delete the folders nor their contents.</td>
-		</tr>
-		<tr>
-			<td>Allow output folder per source folder</td>
-			<td>Shows/Hides the 'output folder' attribute of the source folders</td>
-		</tr>
-	</tbody>
-</table>
-<br>
-<table border="1" cellspacing="0" cellpadding="5" summary="Source folder options" width="600">
-	<caption>Source folder attributes<br>
-	</caption>
-
-	<tbody>
-		<tr>
-			<th>Attribute</th>
-
-			<th>Description</th>
-		</tr>
-
-		<tr>
-			<td align="left" valign="top" width="20%">Exclusion filter</td>
-
-			<td align="left" valign="top">Selects which resources are not visible to the compiler</td>
-		</tr>
-
-		<tr>
-			<td align="left" valign="top">Output folder</td>
-
-			<td align="left" valign="top">Only available when <b>Allow output
-			folder per source folder</b> is checked. Defines a source folder specific output location. If not set the project's default output folder is used.</td>
-		</tr>
-	</tbody>
-</table>
-
-    <h2>Projects tab</h2>
-
-    <p>In the <b>Required projects on the build path</b> list, you can add project dependencies by selecting other workbench
-    projects to add to the build path for this new project. The <b>Select All</b> and <b>Deselect All</b> buttons can be used to add or remove all other projects to or from the build path.</p>
-
-    <p>Adding a required project indirectly adds all its classpath entries marked as 'exported'. Setting a classpath entry as exported is done in the Order and Export tab.</p>
-
-    <p>The projects selected here are automatically added to the referenced projects list. The referenced project list is used to determine the build order. A project is always
-    build after all its referenced projects are built.</p>
-
-    <h2>Libraries tab</h2>
-
-    <p>On this page, you can add libraries to the build path. You can add:</p>
-
-    <ul>
-      <li>Workbench-managed (internal) JAR files</li>
-
-      <li>File system (external) JAR files</li>
-
-      <li>Folders containing CLASS files</li>
-	<li>Predefined libraries like the JRE System Library</li>
-</ul>
-
-    <p>JAR files can also be added indirectly as class path variables.</p>
-
-    <p>By default, the library list contains an entry representing the Java runtime library.  This entry points to the JRE
-    selected as the default JRE. The default JRE is configured in the <a href="ref-18.htm">Installed JREs preferences page</a> (Window &gt; Preferences &gt; Java &gt; Installed
-    JREs)</p>
-
-    <table border="1" cellspacing="0" cellpadding= "5" summary="libraries tab options" width="600">
-      <caption>
-        Libraries tab options<br>
-      </caption>
-
-      <tbody>
-        <tr>
-          <th width="20%">Option</th>
-
-          <th>Description</th>
-        </tr>
-
-        <tr>
-          <td align="left" valign="top">Add JARs</td>
-
-          <td align="left" valign="top">Allows you to navigate the workbench hierarchy and select JAR files to add to the build path.</td>
-        </tr>
-
-        <tr>
-          <td align="left" valign="top">Add External JARs</td>
-
-          <td align="left" valign="top">Allows you to navigate the file system (outside the workbench) and select JAR files to add to the build path.</td>
-        </tr>
-
-        <tr>
-          <td align="left" valign="top">Add Variable</td>
-
-          <td align="left" valign="top">Allows you to add classpath variables to the build path. Classpath variables are an indirection to JARs with the benefit of avoiding local
-          file system paths in a classpath. This is needed when projects are shared in a team.<br>
-           Variables can be created and edited in the <a href="ref-15.htm">Classpath Variable preference page</a> (Window &gt; Preferences &gt; Java &gt; Build Path &gt; Classpath Variables)</td>
-        </tr>
-
-        <tr>
-          <td>Add Library</td>
-
-          <td>Allows to add a predefined libraries like the JRE System Library. Such libraries can stand for an arbitrary number of entries (visible as children node of the library node)</td>
-        </tr>
-
-        <tr>
-          <td>Add Class Folder</td>
-
-          <td>Allows to navigate the workbench hierarchy and select a class folder for the build path. The selection dialog also allows you to create a new folder.</td>
-        </tr>
-
-        <tr>
-          <td align="left" valign="top">Edit</td>
-
-          <td align="left" valign="top">Allows you to modify the currently selected library entry or entry attribute</td>
-        </tr>
-
-        <tr>
-          <td align="left" valign="top">Remove</td>
-
-          <td align="left" valign="top">Removes the selected element from the build path. This does not delete the resource.</td>
-        </tr>
-      </tbody>
-    </table>
-
-    <p>&nbsp;Libraries have the following attributes (presented as library entry children nodes):</p>
-
-<table border="1" cellspacing="0" cellpadding="5" summary="Source folder options"
-	width="600">
-	<caption>Library entry attributes<br>
-	</caption>
-
-	<tbody>
-		<tr>
-			<th>Attribute</th>
-
-			<th>Description</th>
-		</tr>
-
-		<tr>
-			<td align="left" valign="top" width="20%">Javadoc location</td>
-
-			<td align="left" valign="top">Specifies where the library's Javadoc documentation can be found. If specified you can use <b>Shift+F2</b> on an element of this library to open its documentation.</td>
-		</tr>
-
-		<tr>
-			<td align="left" valign="top">Source attachment</td>
-
-			<td align="left" valign="top">Specifies where the library's source can be found.</td>
-		</tr>
-	</tbody>
-</table>
-
-
-
-
-<h2>Order and Export tab</h2>
-
-    <p>In the <b>Build class path order</b> list, you can click the <b>Up</b> and <b>Down</b> buttons to move the selected path entry up or down in the build path order for this new project.</p>
-
-    <p>Checked list entries are marked as exported. Exported entries are visible to projects that require the project. Use the <b>Select
-    All</b> and <b>Deselect All</b> to change the checked state of all entries. Source folders are always exported,
-    and can not be deselected.</p>
-
-    <h2>Default output folder</h2>
-
-    <p>At the bottom of this page, the <b>Default output folder</b> field allows you to enter a path to a folder path where the compilation output for this
-    project will reside. The default output is used for source folders that do not specify an own output folder. Use <b>Browse</b> to select an existing location from the current project.</p>
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-    <p>
-     <a href="../concepts/cbuildcp.htm">Build classpath</a><br>
-     <a href="../concepts/cclsspthv.htm">Classpath variables</a><br>
-    </p>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-    <p>
-     <a href="../tasks/tasks-110.htm">Working with build paths</a><br>
-     <a href="../tasks/tasks-116.htm">Attaching source to variables</a><br>
-     <a href="../tasks/tasks-115.htm">Attaching source to a JAR file</a>
-    </p>
-     <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-     <a href="../reference/ref-152.htm">Frequently asked questions on JDT</a><br>
-     <a href="../reference/ref-15.htm">Classpath Variables preferences</a><br>
-     <a href="../reference/ref-properties-compiler.htm">Java Compiler properties</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-123b.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-123b.htm
deleted file mode 100644
index 7e46c66..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-123b.htm
+++ /dev/null

@@ -1,296 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>Java Build Path page</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-
-  <body>
-    <h1>Java Build Path page</h1>
-
-    <p>The options in this page indicate the build path settings for a Java project.
-     You can reach this page through the <a href="ref-121.htm">New Java Project wizard</a>.</p>
-
-    <p>The build class path is a list of paths visible to the compiler when building the project.</p>
-
-    <h2>Source tab</h2>
-
-    <p>Source folders are the root of packages containing .java files. The compiler will translate the contained files to .class files that will be written to the output folder. 
-The output folder is defined per project except if a source folder specifies an own output folder. Each source folder can define an exclusion filter to specify which 
-resources inside the folder should not be visible to the compiler.<br>
-Resources existing in source folders are also copied to the output folder unless the setting in the <a href="ref-preferences-compiler.htm">Compiler preference
-    page</a> (Window &gt; Preferences &gt; Java &gt; Compiler &gt; Building) specifies that the resource is filtered.</p>
-
-    <p>The tree shows the project as it will look like when switching to the package explorer. Several operations can be executed 
-	on this tree to change the structure of the project.</p>
-
-<table border="1" cellspacing="0" cellpadding= "5" summary="Source folder options" width="700">
-
-	<tbody>
-		<tr>
-			<th>Icon</th>
-
-			<th>Option</th>
-
-			<th>Description</th>
-		</tr>
-
-		<tr>
-			<td align="center" valign="center" width="5%"><img src="../images/org.eclipse.jdt.ui/elcl16/add_to_buildpath.png" alt="Add to build path" border="0" ></td>
-
-			<td align="center" valign="center" width="20%">Add to build path</td>
-
-			<td align="left" valign="top">Allows to add a folder or package to the Java build path and change it to a source folder. A source folder is a top-level 
-				folder in the project hierarchy that is used as the root of packages. Entries on the build path like source folders are visible to the compiler 
-				and all contained resources like .java files are used to build the project. Source folders allow to structure the project, for example to separate 
-				test from the application in two source folders. Within a source folder, a more detailed structuring can be done by using packages.
-				</td>
-		</tr>
-		
-		<tr>
-			<td align="center" valign="center" width="05%"><img src="../images/org.eclipse.jdt.ui/elcl16/remove_from_buildpath.png" alt="Remove from buildpath" border="0" ></td>
-
-			<td align="center" valign="center" width="20%">Remove from buildpath</td>
-
-			<td align="left" valign="top">Allows to remove a source folder from the Java build path and change it into a normal folder. All contained resources 
-				in this folder (like .java files) are no longer visible to the compiler and will not be included when building the project.
-			</td>
-		</tr>
-
-		<tr>
-			<td align="center" valign="center" width="05%"><img src="../images/org.eclipse.jdt.ui/elcl16/exclusion_filter_attrib.png" alt="Exclude" border="0" ></td>
-
-			<td align="center" valign="center" width="20%">Exclude</td>
-
-			<td align="left" valign="top">Allows to add a resource to the exclusion filter of it's parent source folder. The consequence is that 
-				all children of this resource are no longer visible to the compiler. This operation can be useful if for example, some packages 
-				are not needed in the project and can therefore be hidden from the compiler.
-			</td>
-		</tr>
-
-		<tr>
-			<td align="center" valign="center" width="05%"><img src="../images/org.eclipse.jdt.ui/elcl16/inclusion_filter_attrib.png" alt="Include" border="0" ></td>
-
-			<td align="center" valign="center" width="20%">Include</td>
-
-			<td align="left" valign="top">This action is available on files or folders that have been excluded. In this situation, include allows to make this 
-				resources again visible to the compiler.
-			</td>
-
-		</tr>
-
-		<tr>
-			<td align="center" valign="center" width="05%"><img src="../images/org.eclipse.jdt.ui/obj16/text_edit.png" alt="Configure source folder properties" border="0" ></td>
-
-			<td align="center" valign="center" width="20%">Configure source folder properties</td>
-
-			<td align="left" valign="top">Editing can be used in two situations: <p>
-				<ol>
-				<li>Customize the inclusion and exclusion filters by defining string patterns. This can be useful if 
-				including or excluding every single resource would take too long and just some simple patterns can do the job. A very 
-				practical operator is the wildcard operator to define more sophisticated patterns (for example exclude all resources 
-				that start with &quot;Test*.java&quot;).</li>
-				<li>Change the output folder for a source folder. The consequence is that all generated 
-				.class files from the .java files in this source folder are will be generated in the separate output folder instead of the 
-				project's output folder.</li>
-				</ol>
-				Note that this advanced action is only available on single selected objects.
-				</p></td>
-		</tr>
-
-		<tr>
-			<td align="center" valign="center" width="05%"><img src="../images/org.eclipse.jdt.ui/elcl16/clear_co.png" alt="Undo all changes" border="0" ></td>
-
-			<td align="center" valign="center" width="20%">Undo all changes</td>
-
-			<td align="left" valign="top">All changes that have been applied to the project in this wizard will be withdrawn and the original 
-				state of the project is reconstructed.
-			</td>
-		</tr>
-
-		<tr>
-			<td align="center" valign="center" width="05%"><img src="../images/org.eclipse.jdt.ui/etool16/newpackfolder_wiz.png" alt="Link additional source to project" border="0" ></td>
-
-			<td align="center" valign="center" width="20%">Link additional source to project</td>
-
-			<td align="left" valign="top">When creating a project, there are might already exist some pieces of code or other resources somewhere in the 
-				file system that could also be used for this new project. To add this sources to the project, it is possible to create a linked source 
-				folder to the folder in the file system and make its content visible to the compiler. Note that only a link to the folder is created. This means that 
-				any modifications on resources in that folder will also have an impact on other projects also using this resources.
-			</td>
-		</tr>
-
-		<tr>
-			<td align="center" valign="center" width="05%">No icon</td>
-
-			<td align="center" valign="center" width="20%">Allow output folders for source folders</td>
-
-			<td align="left" valign="top">Shows/Hides the 'output folder' attribute of the source folders. If no output folders are shown, this 
-				means that the project's default output folder is used for the generated .class files.</td>
-		</tr>
-	</tbody>
-</table>
-
-<p>Note that a shorter description of all operations is visible in the area at the bottom of the project tree (labeled with 'Description'). Only the descriptions 
-which are valid for the current selection on the project are shown. For experienced users it is also possible to close the description area to view 
-the projects structure enlarged.</p>
-
-    <h2>Projects tab</h2>
-
-    <p>In the <b>Required projects on the build path</b> list, you can add project dependencies by selecting other workbench
-    projects to add to the build path for this new project. The <b>Select All</b> and <b>Deselect All</b> buttons can be used to add or remove all other projects to or from the build path.</p>
-
-    <p>Adding a required project indirectly adds all its classpath entries marked as 'exported'. Setting a classpath entry as exported is done in the Order and Export tab.</p>
-
-    <p>The projects selected here are automatically added to the referenced projects list. The referenced project list is used to determine the build order. A project is always
-    build after all its referenced projects are built.</p>
-
-    <h2>Libraries tab</h2>
-
-    <p>On this page, you can add libraries to the build path. You can add:</p>
-
-    <ul>
-      <li>Workbench-managed (internal) JAR files</li>
-
-      <li>File system (external) JAR files</li>
-
-      <li>Folders containing CLASS files</li>
-	<li>Predefined libraries like the JRE System Library</li>
-</ul>
-
-    <p>JAR files can also be added indirectly as class path variables.</p>
-
-    <p>By default, the library list contains an entry representing the Java runtime library.  This entry points to the JRE
-    selected as the default JRE. The default JRE is configured in the <a href="ref-18.htm">Installed JREs preferences page</a> (Window &gt; Preferences &gt; Java &gt; Installed
-    JREs)</p>
-
-    <table border="1" cellspacing="0" cellpadding="5" summary="libraries tab options" width="700">
-      <caption>
-        Libraries tab options<br>
-      </caption>
-
-      <tbody>
-        <tr>
-          <th width="20%">Option</th>
-
-          <th>Description</th>
-        </tr>
-
-        <tr>
-          <td align="left" valign="top">Add JARs</td>
-
-          <td align="left" valign="top">Allows you to navigate the workbench hierarchy and select JAR files to add to the build path.</td>
-        </tr>
-
-        <tr>
-          <td align="left" valign="top">Add External JARs</td>
-
-          <td align="left" valign="top">Allows you to navigate the file system (outside the workbench) and select JAR files to add to the build path.</td>
-        </tr>
-
-        <tr>
-          <td align="left" valign="top">Add Variable</td>
-
-          <td align="left" valign="top">Allows you to add classpath variables to the build path. Classpath variables are an indirection to JARs with the benefit of avoiding local
-          file system paths in a classpath. This is needed when projects are shared in a team.<br>
-           Variables can be created and edited in the <a href="ref-15.htm">Classpath Variable preference page</a> (Window &gt; Preferences &gt; Java &gt; Build Path &gt; Classpath Variables)</td>
-        </tr>
-
-        <tr>
-          <td>Add Library</td>
-
-          <td>Allows to add a predefined libraries like the JRE System Library. Such libraries can stand for an arbitrary number of entries (visible as children node of the library node)</td>
-        </tr>
-
-        <tr>
-          <td>Add Class Folder</td>
-
-          <td>Allows to navigate the workbench hierarchy and select a class folder for the build path. The selection dialog also allows you to create a new folder.</td>
-        </tr>
-
-        <tr>
-          <td align="left" valign="top">Edit</td>
-
-          <td align="left" valign="top">Allows you to modify the currently selected library entry or entry attribute</td>
-        </tr>
-
-        <tr>
-          <td align="left" valign="top">Remove</td>
-
-          <td align="left" valign="top">Removes the selected element from the build path. This does not delete the resource.</td>
-        </tr>
-      </tbody>
-    </table>
-
-    <p>&nbsp;Libraries have the following attributes (presented as library entry children nodes):</p>
-
-<table border="1" cellspacing="0" cellpadding="5" summary="Source folder options"
-	width="750">
-	<caption>Library entry attributes<br>
-	</caption>
-
-	<tbody>
-		<tr>
-			<th>Attribute</th>
-
-			<th>Description</th>
-		</tr>
-
-		<tr>
-			<td align="left" valign="top" width="20%">Javadoc location</td>
-
-			<td align="left" valign="top">Specifies where the library's Javadoc documentation can be found. If specified you can use <b>Shift+F2</b> on an element of this library to open its documentation.</td>
-		</tr>
-
-		<tr>
-			<td align="left" valign="top">Source attachment</td>
-
-			<td align="left" valign="top">Specifies where the library's source can be found.</td>
-		</tr>
-	</tbody>
-</table>
-
-
-
-
-<h2>Order and Export tab</h2>
-
-    <p>In the <b>Build class path order</b> list, you can click the <b>Up</b> and <b>Down</b> buttons to move the selected path entry up or down in the build path order for this new project.</p>
-
-    <p>Checked list entries are marked as exported. Exported entries are visible to projects that require the project. Use the <b>Select
-    All</b> and <b>Deselect All</b> to change the checked state of all entries. Source folders are always exported,
-    and can not be deselected.</p>
-
-    <h2>Default output folder</h2>
-
-    <p>At the bottom of this page, the <b>Default output folder</b> field allows you to enter a path to a folder path where the compilation output for this
-    project will reside. The default output is used for source folders that do not specify an own output folder. Use <b>Browse</b> to select an existing location from the current project.</p>
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-    <p>
-     <a href="../concepts/cbuildcp.htm">Build classpath</a><br>
-     <a href="../concepts/cclsspthv.htm">Classpath variables</a><br>
-    </p>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-     <a href="../tasks/tasks-110.htm">Working with build paths</a><br>
-     <a href="../tasks/tasks-116.htm">Attaching source to variables</a><br>
-     <a href="../tasks/tasks-115.htm">Attaching source to a JAR file</a>
-          <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-     <a href="../reference/ref-152.htm">Frequently asked questions on JDT</a><br>
-     <a href="../reference/ref-15.htm">Classpath Variables preferences</a><br>
-     <a href="../reference/ref-properties-compiler.htm">Java Compiler properties</a>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-124.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-124.htm
deleted file mode 100644
index 7496fb6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-124.htm
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>Source attachments</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-
-  <body>
-    <h1>Source attachments</h1>
-
-    <p>To browse the source of a type contained in library you can attach a source archive or source folder to this library. The editor will then show the source instead of a the decompiled code.
-    Having the source attachment set the debugger can offer source level stepping in this type.</p>
-
-    <p>The Source Attachment dialog can be reached in several ways:</p>
-
-    <ul>
-      <li>Select a JAR in the Package Explorer and choose <b>Properties &gt; Java Source Attachment</b> from the context
-	menu or the <a href="ref-menu-project.htm">Project menu</a></li>
-
-      <li>Open the Java Build Path page of a project (<b>Projects &gt;
-	Properties &gt; Java Build Path</b>). On the <b>Libraries</b> page  expand the library's  node and select the <b>Source
-	attachment</b> attribute and press <b>Edit</b></li>
-	<li><span class="control"></span>Open an editor on a class file. If the
-	source attachment has not already been configured for this JAR, the
-	editor contains a button <span class="control">Attach Source</span></li>
-</ul>
-
-    <p>Depending of how a JAR was contributed to the classpath, you can see different types of Source attachment dialogs:</p>
-
-    
-
-    <h2>JAR</h2>
-
-<p>In the <span class="control">Location path</span> field, enter the path of an archive or a folder containing the source. Use either the <b>Workspace</b>, <b>External
-File</b> or the <b>External Folder</b> button to browse for a location.</p>
-
-<h2>Variable</h2>
-
-<p>In the <span class="control">Location Variable Path</span> field
-enter a <i>variable path</i> that points to the source attachment's location.
-A variable path has as first segment a variable (which will resolve to a
-folder or file), the rest is an optional path extension (e.g.<em>MYVARIABLE/src.jar</em>
-). Use either the <span class="control">Variable</span> button to select
-an existing variable and the <span class="control">Extension</span>
-button to select the extension path. The <span class="control">Extension</span>
-button is only enabled when the variable can be extended (resolves to a
-folder)</p>
-
-<p><var>JRE_SRC</var> is a reserved variable that points to a JRE selected in the <a href="ref-19.htm">Installed JREs preference page</a> (<span
-    class="control">Window &gt; Preferences &gt; Java &gt; Installed JREs</span>). Go to this preference page to configure the source attachment for the JRE's library..</p>
-
-    
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-    <p>
-     <a href="../concepts/cbuildcp.htm">Build classpath</a></p>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-    <p>
-     <a href="../tasks/tasks-110.htm">Working with build paths</a><br>
-     <a href="../tasks/tasks-116.htm">Attaching source to variables</a><br>
-     <a href="../tasks/tasks-115.htm">Attaching source to a JAR file</a></p>
-     <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-     <a href="../reference/ref-19.htm">Installed JREs preferences</a><br>
-     <a href="../reference/ref-123.htm">Java Build Path properties</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-125.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-125.htm
deleted file mode 100644
index bbbed2d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-125.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>New Java Package Wizard</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-
-  <body>
-    <h1>New Java Package Wizard</h1>
-
-    <p>This wizard helps you create a folder corresponding to a new Java package. The corresponding folder of the default package always exists, and therefore doesn't have to be
-    created.</p>
-
-    <table border="1" cellspacing="0" cellpadding="5" summary="Java Package Options">
-      <caption>
-        Java Package Options<br>
-      </caption>
-
-      <tr>
-        <th>Option</th>
-
-        <th>Description</th>
-
-        <th>Default</th>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Source folder</td>
-
-        <td align="left" valign="top">Type or browse to select a container (project or folder) for the new package.</td>
-
-        <td align="left" valign="top">The source folder of the element that was selected when the wizard has been started.</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Name</td>
-
-        <td align="left" valign="top">Type a name for the new package</td>
-
-        <td align="left" valign="top">&lt;blank&gt;</td>
-      </tr>
-    </table>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-    <p>
-     <a href="../tasks/tasks-15.htm">Creating a new Java package</a></p>
-     <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-     <p><a href="../reference/ref-menu-file.htm">File actions</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-126.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-126.htm
deleted file mode 100644
index e2efc5d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-126.htm
+++ /dev/null

@@ -1,143 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>New Java Class Wizard</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-
-  <body>
-    <h1>New Java Class Wizard</h1>
-
-    <p>This wizard helps you to create a new Java class in in a Java project.</p>
-
-    <table border="1" cellspacing="0" cellpadding="5">
-      <caption>
-        Java Class Options<br>
-      </caption>
-
-      <tr>
-        <th>Option</th>
-
-        <th>Description</th>
-
-        <th>Default</th>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Source folder</td>
-
-        <td align="left" valign="top">Enter a source folder for the new class. Either type a valid source folder path or click <span class="control">Browse</span> to select a
-        source folder via a dialog.</td>
-
-        <td align="left" valign="top">The source folder of the element that was selected when the wizard has been started.</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Package</td>
-
-        <td align="left" valign="top">Enter a package to contain the new class. You can select either this option or the Enclosing Type option, below. Either type a valid package
-        name or click <span class="control">Browse</span> to select a package via a dialog.</td>
-
-        <td align="left" valign="top">The package of the element that was selected when the wizard has been started.</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Enclosing type</td>
-
-        <td align="left" valign="top">Select this option to choose a type in which to enclose the new class. You can select either this option or the Package option, above. Either
-        type a valid name in the field or click <span class="control">Browse</span> to select a type via a dialog.</td>
-
-        <td align="left" valign="top">The type or the primary type of the compilation unit that was selected when the wizard has been started or &lt;blank&gt;</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Name</td>
-
-        <td align="left" valign="top">Type a name for the new class.</td>
-
-        <td align="left" valign="top">&lt;blank&gt;</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Modifiers</td>
-
-        <td align="left" valign="top">
-          <p>Select one or more access modifiers for the new class.</p>
-
-          <ul>
-            <li>Either public, default, private, or protected (private and protected are only available if you specify an enclosing type)</li>
-
-            <li>abstract</li>
-
-            <li>final</li>
-
-            <li>static (only available if you specify an enclosing type)</li>
-          </ul>
-        </td>
-
-        <td align="left" valign="top">public</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Superclass</td>
-
-        <td align="left" valign="top">Type or click <span class="control">Browse</span> to select a superclass for this class.</td>
-
-        <td align="left" valign="top">The type (not the compilation unit!) that was selected when the wizard has been started or &lt;java.lang.Object&gt;</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Interfaces</td>
-
-        <td align="left" valign="top">Click <span class="control">Add</span> to choose interfaces that the new class implements.</td>
-
-        <td align="left" valign="top">&lt;blank&gt;</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Which method stubs would you like to create?</td>
-
-        <td align="left" valign="top">
-          <p>Choose the method stubs to create in this class:</p>
-
-          <ul>
-            <li>public static void main(String [] args): Adds a main method stub to the new class.</li>
-
-            <li>Constructors from superclass: Copies the constructors from the new class's superclass and adds these stubs to the new class.</li>
-
-            <li>Inherited abstract methods: Adds to the new class stubs of any abstract methods from superclasses or methods of interfaces that need to be implemented.</li>
-          </ul>
-        </td>
-
-        <td align="left" valign="top">Inherited abstract methods enabled</td>
-      </tr>
-      
-      <tr>
-        <td align="left" valign="top">Do you want to add comments?</td>
-
-        <td align="left" valign="top">When selected, the wizard adds comments to the new class where appropriate.</td>
-
-        <td align="left" valign="top">Do not add comments</td>
-      </tr>
-      
-    </table>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-    <p>
-     <a href="../tasks/tasks-17.htm">Creating a new Java class</a>
-     </p>
-          <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-	<p>
-     <a href="../reference/ref-menu-file.htm">File actions</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-126b.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-126b.htm
deleted file mode 100644
index ffb388e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-126b.htm
+++ /dev/null

@@ -1,111 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>New Java Enum Wizard</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-
-  <body>
-    <h1>New Java Enum Wizard</h1>
-
-    <p>This wizard helps you to create a new Java enum in in a Java project.</p>
-
-    <table border="1" cellspacing="0" cellpadding="5">
-      <caption>
-        Java Enum Options<br>
-      </caption>
-
-      <tr>
-        <th>Option</th>
-
-        <th>Description</th>
-
-        <th>Default</th>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Source folder</td>
-
-        <td align="left" valign="top">Enter a source folder for the new enum. Either type a valid source folder path or click <span class="control">Browse</span> to select a
-        source folder via a dialog.</td>
-
-        <td align="left" valign="top">The source folder of the element that was selected when the wizard has been started.</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Package</td>
-
-        <td align="left" valign="top">Enter a package to contain the new enum. You can select either this option or the Enclosing Type option, below. Either type a valid package
-        name or click <span class="control">Browse</span> to select a package via a dialog.</td>
-
-        <td align="left" valign="top">The package of the element that was selected when the wizard has been started.</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Enclosing type</td>
-
-        <td align="left" valign="top">Select this option to choose a type in which to enclose the new enum. You can select either this option or the Package option, above. Either
-        type a valid name in the field or click <span class="control">Browse</span> to select a type via a dialog.</td>
-
-        <td align="left" valign="top">The type or the primary type of the compilation unit that was selected when the wizard has been started or &lt;blank&gt;</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Name</td>
-
-        <td align="left" valign="top">Type a name for the new enum.</td>
-
-        <td align="left" valign="top">&lt;blank&gt;</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Modifiers</td>
-
-        <td align="left" valign="top">
-          <p>Select one or more access modifiers for the new enum.</p>
-
-          <ul>
-            <li>Either public, default, private, or protected (private and protected are only available if you specify an enclosing type)</li>
-          </ul>
-        </td>
-
-        <td align="left" valign="top">public</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Interfaces</td>
-
-        <td align="left" valign="top">Click <span class="control">Add</span> to choose interfaces that the new enum implements.</td>
-
-        <td align="left" valign="top">&lt;blank&gt;</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Do you want to add comments?</td>
-
-        <td align="left" valign="top">When selected, the wizard adds comments to the new enum where appropriate.</td>
-
-        <td align="left" valign="top">Do not add comments</td>
-      </tr>
-      
-    </table>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-    <p>
-     <a href="../tasks/tasks-17b.htm">Creating a new Java enum</a>
-     </p>
-          <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-     <p>
-     <a href="../reference/ref-menu-file.htm">File actions</a>
-     </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-127.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-127.htm
deleted file mode 100644
index 8a8f42d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-127.htm
+++ /dev/null

@@ -1,112 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>New Java Interface Wizard</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-
-  <body>
-    <h1>New Java Interface Wizard</h1>
-
-    <p>This wizard helps you to create a new Java interface in a Java project.</p>
-
-    <table border="1" cellspacing="0" cellpadding="5">
-      <caption>
-        Java Interface Options<br>
-      </caption>
-
-      <tr>
-        <th>Option</th>
-
-        <th>Description</th>
-
-        <th>Default</th>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Source folder</td>
-
-        <td align="left" valign="top">Enter a source folder for the new interface. Either type a valid source folder path or click <span class="control">Browse</span> to select a
-        source folder via a dialog.</td>
-
-        <td align="left" valign="top">The source folder of the element that was selected when the wizard has been started.</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Package</td>
-
-        <td align="left" valign="top">Enter a package to contain the new interface. You can select either this option or the Enclosing Type option, below. Either type a valid
-        package name or click <span class="control">Browse</span> to select a package via a dialog.</td>
-
-        <td align="left" valign="top">The package of the element that was selected when the wizard has been started.</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Enclosing type</td>
-
-        <td align="left" valign="top">Select this option to choose a type in which to enclose the new interface. You can select either this option or the Package option, above.
-        Either type a valid name in the field or click <span class="control">Browse</span> to select a type via a dialog.</td>
-
-        <td align="left" valign="top">The type or the primary type of the compilation unit that was selected when the wizard has been started or &lt;blank&gt;</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Name</td>
-
-        <td align="left" valign="top">Type a name for the new interface.</td>
-
-        <td align="left" valign="top">&lt;blank&gt;</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Modifiers</td>
-
-        <td align="left" valign="top">
-          <p>Select one or more access modifiers for the new interface.</p>
-
-          <ul>
-            <li>Either public, default, private, or protected (private and protected are only available if you specify an enclosing type)</li>
-
-            <li>static (only available if you specify an enclosing type)</li>
-          </ul>
-        </td>
-
-        <td align="left" valign="top">public</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Extended interfaces</td>
-
-        <td align="left" valign="top">Click Add to choose interfaces that the new interface extends.</td>
-
-        <td align="left" valign="top">&lt;blank&gt;</td>
-      </tr>
-      
-      <tr>
-        <td align="left" valign="top">Do you want to add comments?</td>
-
-        <td align="left" valign="top">When selected, the wizard adds comments to the new class where appropriate.</td>
-
-        <td align="left" valign="top">Do not add comments</td>
-      </tr>
-      
-    </table>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-    <p>
-     <a href="../tasks/tasks-21.htm">Creating a new Java interface</a>
-     </p>
-          <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-     <a href="../reference/ref-menu-file.htm">File actions</a>
-     </p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-127b.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-127b.htm
deleted file mode 100644
index 98703d8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-127b.htm
+++ /dev/null

@@ -1,102 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>New Java Annotation Wizard</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-
-  <body>
-    <h1>New Java Annotation Wizard</h1>
-
-    <p>This wizard helps you to create a new Java Annotation in a Java project.</p>
-
-    <table border="1" cellspacing="0" cellpadding="5">
-      <caption>
-        Java Annotation Options<br>
-      </caption>
-
-      <tr>
-        <th>Option</th>
-
-        <th>Description</th>
-
-        <th>Default</th>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Source folder</td>
-
-        <td align="left" valign="top">Enter a source folder for the new annotation. Either type a valid source folder path or click <span class="control">Browse</span> to select a
-        source folder via a dialog.</td>
-
-        <td align="left" valign="top">The source folder of the element that was selected when the wizard has been started.</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Package</td>
-
-        <td align="left" valign="top">Enter a package to contain the new annotation. You can select either this option or the Enclosing Type option, below. Either type a valid
-        package name or click <span class="control">Browse</span> to select a package via a dialog.</td>
-
-        <td align="left" valign="top">The package of the element that was selected when the wizard has been started.</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Enclosing type</td>
-
-        <td align="left" valign="top">Select this option to choose a type in which to enclose the new annotation. You can select either this option or the Package option, above.
-        Either type a valid name in the field or click <span class="control">Browse</span> to select a type via a dialog.</td>
-
-        <td align="left" valign="top">The type or the primary type of the compilation unit that was selected when the wizard has been started or &lt;blank&gt;</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Name</td>
-
-        <td align="left" valign="top">Type a name for the new annotation.</td>
-
-        <td align="left" valign="top">&lt;blank&gt;</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Modifiers</td>
-
-        <td align="left" valign="top">
-          <p>Select one or more access modifiers for the new annotation.</p>
-
-          <ul>
-            <li>Either public, default, private, or protected (private and protected are only available if you specify an enclosing type)</li>
-          </ul>
-        </td>
-
-        <td align="left" valign="top">public</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Do you want to add comments?</td>
-
-        <td align="left" valign="top">When selected, the wizard adds comments to the new class where appropriate.</td>
-
-        <td align="left" valign="top">Do not add comments</td>
-      </tr>
-      
-    </table>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-    <p>
-     <a href="../tasks/tasks-21b.htm">Creating a new Java annotation</a></p>
-          <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-     <p>
-     <a href="../reference/ref-menu-file.htm">File actions</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-128.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-128.htm
deleted file mode 100644
index bc12aa9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-128.htm
+++ /dev/null

@@ -1,78 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>New Source Folder Wizard</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-
-  <body>
-    <h1>New Source Folder Wizard</h1>
-
-    <p>This wizard helps you to create a new source folder to a Java project.</p>
-
-    <p>Note that a new source folder can not be nested in existing source folders or in an output folder. You can choose to add exclusion filters to the other nesting source folders or the
-    wizard will suggest to replace the nesting classpath entry with the new created entry. The wizard will also suggest to change the output location.</p>
-
-    <table border="1" cellspacing="0" cellpadding="5" summary="New Source Folder Options">
-      <caption>
-        New Source Folder Options</caption>
-
-      <tr>
-        <th>Option</th>
-
-        <th>Description</th>
-
-        <th>Default</th>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Project name</td>
-
-        <td align="left" valign="top">Enter a project to contain the new source folder. Either type a valid project name or click <span class="control">Browse</span> to select a
-        project via a dialog.</td>
-
-        <td align="left" valign="top">The project of the element that was selected when the wizard has been started.</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Folder name</td>
-
-        <td align="left" valign="top">Type a path for the new source folder. The path is relative to the selected project.</td>
-
-        <td align="left" valign="top">&lt;blank&gt;</td>
-      </tr>
-      
-      <tr>
-        <td align="left" valign="top">Update exclusion filter in other source folders to solve nesting</td>
-
-        <td align="left" valign="top">Select to modify existing source folder's exclusion filters to solve nesting problems. For example if there is an existing source folder <i>src</i> and a folder <i>src/inner</i> is created, the source folder <i>src</i> will be updated to have a exclusion filter <i>src/inner</i>.</td>
-
-        <td align="left" valign="top">Off</td>
-      </tr>
-    </table>
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-    <p>
-     <a href="../concepts/concepts-3.htm">Java projects</a>
-    </p>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-    <p>
-     <a href="../tasks/tasks-11.htm">Creating Java elements</a><br>
-     <a href="../tasks/tasks-26.htm">Creating a new source folder</a>
-     </p>
-          <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-     <a href="../reference/ref-menu-file.htm">File actions</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-129.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-129.htm
deleted file mode 100644
index 3cef6d6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-129.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>New Java Scrapbook Page Wizard</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-
-  <body>
-    <h1>New Java Scrapbook Page Wizard</h1>
-
-    <p>This wizard helps you to create a new Java scrapbook page in a project.</p>
-
-    <table border="1" cellspacing="0" cellpadding= "5" summary="Create Java Scrapbook Page Options">
-      <caption>
-        Create Java Scrapbook Page Options
-      </caption>
-
-      <tr>
-        <th>Option</th>
-
-        <th>Description</th>
-
-        <th>Default</th>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Enter or select the parent folder</td>
-
-        <td align="left" valign="top">Type or browse the hierarchy below to select a container (project or folder) for the scrapbook page.</td>
-
-        <td align="left" valign="top">The container of the selected element</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">File name</td>
-
-        <td align="left" valign="top">Type a name for the new file. The "<em>.jpage</em> " extension is appended automatically when not added already.</td>
-
-        <td align="left" valign="top">&lt;blank&gt;</td>
-      </tr>
-    </table>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ></p>
-    <p>
-     <a href="../reference/ref-34.htm">Java Scrapbook page</a>
-     <a href="../reference/ref-menu-file.htm">File actions</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-13.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-13.htm
deleted file mode 100644
index 5965d7b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-13.htm
+++ /dev/null

@@ -1,159 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Java
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Java
-    </h1>
-    <p>
-      On this page, indicate your preferences for the general Java settings.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5">
-      <caption>
-        Java Preferences
-      </caption>
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-          <th>
-            <p>
-              Default
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-
-         <tr>
-          <td valign="top">
-            Action on double click in the Package Explorer
-          </td>
-          <td valign="top">
-            <dl>
-              <dt>
-                <strong>Go into the selected element:</strong>
-              </dt>
-              <dd>
-                When you double click a container, a <strong>Go Into</strong> command is executed.
-                <br>
-                See <strong>Go Into</strong> from the <a href="ref-menu-navigate.htm">Navigate</a> menu.
-              </dd>
-              <dt>
-                <strong>Expand the selected element:</strong>
-              </dt>
-              <dd>
-                 When you double click a container, it is expanded and its children are revealed.
-              </dd>
-            </dl>
-          </td>
-          <td valign="top">
-            Expand the selected element
-          </td>
-        </tr>
-      
-        <tr>
-          <td valign="top">
-            When opening a Type Hierarchy
-          </td>
-          <td valign="top">
-            <dl>
-              <dt>
-                <strong>Open a new Type Hierarchy Perspective</strong>
-              </dt>
-              <dd>
-                  Opens a new Type Hierarchy perspective whenever a Type Hierarchy view is opened.
-              </dd>
-              <dt>
-                <strong>Show the Type Hierarchy View in the current perspective</strong>
-              </dt>
-              <dd>
-                  The Type Hierarchy view is displayed in the current perspective.
-              </dd>
-            </dl>
-             <em>Note: On the Workbench preferences page, you can choose whether new perspectives open in a new window, in the current window, or as a replacement for the current
-            perspective.</em>
-          </td>
-          <td valign="top">
-            Show the Type Hierarchy View in the current perspective
-          </td>
-        </tr>
-
-        <tr>
-          <td valign="top">
-            Refactoring Java Code
-          </td>
-          <td valign="top">
-             <dl>
-              <dt>
-                <strong>Save all modified resources automatically prior to refactoring</strong>
-              </dt>
-              <dd>
-                  If this option is turned on, all refactorings prompt whether any modified files should be saved before opening the refactoring wizard.
-              </dd>
-              </dl>
-          </td>
-          <td valign="top">
-            On
-          </td>
-        </tr>
-
-        <tr>
-          <td valign="top">
-            Search
-          </td>
-          <td valign="top">
-             <dl>
-              <dt>
-                <strong>Use reduced search menu</strong>
-              </dt>
-              <dd>
-                  If this option is turned on, the search context menus show only the most frequently used search actions.
-              </dd>
-              </dl>
-          </td>
-          <td valign="top">
-            On
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-6.htm">Java views</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-45.htm">Using the Package Explorer</a><br>
-      <a href="../tasks/tasks-37.htm">Using the Hierarchy view</a>
-      </p>
-           <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-view-package-explorer.htm">Package Explorer view</a><br>
-      <a href="../reference/ref-type-hierarchy.htm">Hierarchy view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-131.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-131.htm
deleted file mode 100644
index d5acd2c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-131.htm
+++ /dev/null

@@ -1,133 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>Java search tab</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-
-  <body>
-    <h1>Java search tab</h1>
-
-    <p>This tab in the Search dialog allows you to search for Java elements.</p>
-
-    <h2>Search string</h2>
-
-    <p>In this field, type the expression for which you wish to search, using the wildcard characters mentioned in the dialog as needed. This field is initialized based on the
-    current selection.</p>
-
-    <ul>
-      <li>Depending on what is searched for, the search string should describe the element:
-      <ul>
-        <li>Type: the type name (may be qualified or not).<br>
-        	<i>Examples:
-        	<ul>
-        		<li>org.eclipse.jdt.internal.core.JavaElement</li>
-        		<li>MyClass.Inner</li>
-        		<li>Foo</li>
-        	</ul></i>
-        </li>
-        <li>Method: the defining type name (may be qualified or not as for Type search, optional), the method selector and its parameters (optional).<br>
-        	<i>Examples:
-        	<ul>
-        		<li>org.eclipse.jdt.internal.core.JavaElement.getHandleFromMemento(MementoTokenizer, WorkingCopyOwner)</li>
-        		<li>equals(Object)</li>
-        		<li>foo</li>
-        	</ul></i>
-        </li>
-        <li>Package: the package name for a package (e.g. org.eclipse.jdt.internal.core)</li>
-        <li>Constructor: the defining type name (may be qualified or not as for Type search, optional) and the constructor parameters (optional).<br>
-        	<i>Examples:
-        	<ul>
-        		<li>org.eclipse.jdt.internal.core.JavaElement(JavaElement, String)</li>
-        		<li>Foo</li>
-        	</ul></i>
-             Note that the constructor name should not be entered as it is always the same as the type name.
-        </li>
-        <li>Field: the defining type name (qualified or not as for Type search, optional) and the field name.<br>
-        	<i>Examples:
-        	<ul>
-        		<li>org.eclipse.jdt.internal.core.JavaElement.name</li>
-        		<li>foo</li>
-        	</ul></i>
-        </li>
-      </ul>
-      </li>
-      <li>From the drop-down menu, you can choose to repeat (or modify) a recent search.<br>
-       Select the <span class="control">Case sensitive</span> field to force a case aware search. <span class="control">Case sensitive</span> is enabled when a custom search
-      string is entered.</li>
-    </ul>
-
-    <h2 class="Head">Search For</h2>
-
-    <p>Select to search for one of the following kinds of elements:</p>
-
-    <ul>
-      <li>Type</li>
-
-      <li>Method</li>
-
-      <li>Package</li>
-
-      <li>Constructor</li>
-
-      <li>Field</li>
-    </ul>
-
-    <h2 class="Head">Limit To</h2>
-
-    <p>Select to limit your search results to one of the following kinds of matches:</p>
-
-    <ul>
-      <li>Declarations</li>
-
-      <li>Implementors (available only when searching for types)</li>
-
-      <li>References</li>
-
-      <li>All Occurrences</li>
-
-      <li>Read Access (available only when searching for fields)</li>
-
-      <li>Write Access (available only when searching for fields)</li>
-    </ul>
-
-    <p>If you would like to search the JRE system libraries as well, select the <strong>Search the JRE system libraries</strong> checkbox.</p>
-
-    <h2 class="Item">Scope</h2>
-
-    <p>Select to limit your search results to one of the following scope</p>
-
-    <ul>
-      <li>Workspace</li>
-
-      <li>Selected Resources</li>
-
-      <li>Working Set</li>
-    </ul>
-
-    <p>Press <span class="control">Choose</span> to select or create a working set.</p>
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-    <p>
-     <a href="../concepts/concepts-8.htm">Java search</a></p>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-    <p>
-     <a href="../tasks/tasks-103.htm">Conducting a Java search using the search dialog</a><br>
-     <a href="../tasks/tasks-104.htm">Conducting a Java search using pop-up menus</a>
-     </p>
-          <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-     <a href="../reference/ref-menu-search.htm">Search</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-143.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-143.htm
deleted file mode 100644
index 81764a2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-143.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Content/Code Assist
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Content/Code Assist
-    </h1>
-    <p>
-      If activated from a valid line of code in an editor, this command opens a scrollable list of available code completions. Some tips for using code assist are listed in the following paragraph:
-    </p>
-    <ul>
-      <li>
-        If you select and then hover over a selected line in the content assist list, you can view Javadoc information for that line.
-      </li>
-      <li>
-        You can use the mouse or the keyboard (Up Arrow, Down Arrow, Page Up, Page Down, Home, End, Enter) to navigate and select lines in the list.
-      </li>
-      <li>
-        Clicking or pressing Enter on a selected line in the list inserts the selection into the editor.
-      </li>
-      <li>
-        You can access specialized content assist features inside Javadoc comments.
-      </li>
-    </ul>
-    <img src="../images/contentassist.png"  alt="An editor showing a content assist and Javadoc window at the caret position"> <p>
-     Configure the behavior of the content assist in the <a href="ref-21.htm">Java &gt; Editor &gt; Code Assist</a> preference page.<br>
-     </p>
-     <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/concepts-7.htm">Java editor</a><br>
-       <a href="../concepts/concepts-1.htm">Java Development Tools (JDT)</a>
-    </p>
-    <p>
-       <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-65.htm">Using content/code assist</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-menu-edit.htm">Edit menu</a><br>
-       <a href="../reference/ref-21.htm">Java editor preferences</a><br>
-       <a href="../reference/ref-preferences-templates.htm">Templates preferences</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-148.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-148.htm
deleted file mode 100644
index ec0353f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-148.htm
+++ /dev/null

@@ -1,101 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Open Type
-    </title>
-  </head>
-  <body>
-    <h1>
-      Open Type
-    </h1>
-    <p>
-      This command allows you to browse the workbench for a type to open in an editor or type hierarchy
-    </p>
-    <ul>
-      <li>
-        <strong>Select a type to open</strong>: In this field, type the first few characters of the type you want to open in an editor. You may use wildcards as needed
-        (&quot;<em>?</em>&quot; for any character, &quot;<em>*</em>&quot; for any string, and &quot;<em>TZ</em>&quot; for types containing &quot;<em>T</em>&quot; and &quot;<em>Z</em>&quot; as upper-case letters in camel-case notation, <code>e.g. java.util.TimeZone</code>).
-      </li>
-      <li>
-        <strong>Matching types</strong>: This list displays matches for the expression you type in the <strong>Select a type to open</strong> field.
-      </li>
-    </ul>
-    <p>
-      The behavior of the <strong>Open Type</strong> dialog can be further customized using the dialog menu:
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5">
-      <caption>
-        Open Type Preferences
-      </caption>
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-          <th>
-            <p>
-              Default
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-
-         <tr>
-          <td valign="top">
-            Fully Qualify Duplicates
-          </td>
-          <td valign="top">
-            When selected, duplicate matches are displayed using fully qualified names, packages, and container information (e.g. the package and containing JRE)
-          </td>
-          <td valign="top">
-            Do not fully qualify
-          </td>
-        </tr>
-      
-        <tr>
-          <td valign="top">
-            Show Container Info
-          </td>
-          <td valign="top">
-			When selected, the <strong>Open Type</strong> dialog shows an additional bar at the bottom of the dialog which displays the package and containing
-			JRE of the selected type
-          </td>
-          <td valign="top">
-            Do not show container info
-          </td>
-        </tr>
-
-      </tbody>
-    </table>
-    <p>
-     Additionally, the dialog menu allows to use working sets to further constrain the matching types.
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-76.htm">Opening an editor on a type</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-menu-navigate.htm">Navigate actions</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-149.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-149.htm
deleted file mode 100644
index 3fa3e80..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-149.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Run menu
-    </title>
-  </head>
-  <body>
-    <h1>
-      Run menu
-    </h1>
-    <p>
-      This menu allows you to manage the running of an application in the workbench. Some menu items are only active if the Debug view is the active view.<br>
-      <br>
-       <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-130.htm">Launching a Java program</a><br>
-       <a href="../tasks/tasks-126.htm">Running and debugging</a><br>
-       &nbsp;
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <a href="ref-4.htm">Run and debug actions</a> 
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-15.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-15.htm
deleted file mode 100644
index d1c2ba2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-15.htm
+++ /dev/null

@@ -1,122 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Classpath variables
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Classpath variables
-    </h1>
-    <h2 class="Head">
-      Configurable variables
-    </h2>
-    <p>
-      Classpath variables can be used in a Java Build Path to avoid a reference to the local file system. Using a variable entry, the classpath only contains a variable and the
-      build path can be shared in a team. The value of the variable has to be configured on this page.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <caption>
-        &nbsp;<br>
-      </caption>
-      <tr>
-        <th>
-          <p>
-            Command
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            <strong>New...</strong>
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Adds a new variable entry. In the resulting dialog, specify a name and path for the new variable. You can click the&nbsp;<strong>File</strong>
-            or&nbsp;<strong>Folder</strong> buttons to browse for a path.&nbsp;
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            <strong>Edit...</strong>
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Allows you to edit the selected variable entry. In the resulting dialog, edit the name and/or path for the variable. You can click the&nbsp;<strong>File</strong>
-            or&nbsp;<strong>Folder</strong> buttons to browse for a path.&nbsp;
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            <strong>Remove</strong>
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Removes the selected variable entry.&nbsp;
-          </p>
-        </td>
-      </tr>
-    </table>
-    <h2 class="Head">
-      Reserved class path variables
-    </h2>
-    <p>
-      Certain class path variables are set internally and can not be changed in the Classpath variables preferences:
-    </p>
-    <ul>
-      <li>
-        JRE_LIB: The archive with the runtime JAR file for the currently used JRE.
-      </li>
-      <li>
-        JRE_SRC: The source archive for the currently used JRE.
-      </li>
-      <li>
-        JRE_SRCROOT: The root path in the source archive for the currently used JRE.
-      </li>
-    </ul>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/cclsspthv.htm">Classpath variables</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-JREs.htm">Working with JREs</a><br>
-       <a href="../tasks/tasks-110.htm">Working with build paths</a><br>
-       <a href="../tasks/tasks-114.htm">Adding a variable classpath entry</a><br>
-       <a href="../tasks/tasks-116.htm">Attaching source to a classpath variable</a><br>
-       <a href="../tasks/tasks-117.htm">Defining a classpath variable</a><br>
-       <a href="../tasks/tasks-118.htm">Deleting a classpath variable</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <p>
-      <a href="ref-18.htm">Installed JREs</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-150.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-150.htm
deleted file mode 100644
index d7c2806..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-150.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Step commands
-    </title>
-  </head>
-  <body>
-    <h1>
-      Step commands
-    </h1>
-    <p>
-      Many of the commands in this menu allow you to step through code being debugged. <a href="ref-51.htm">See Debug View</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-152.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-152.htm
deleted file mode 100644
index b2bcfac..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-152.htm
+++ /dev/null

@@ -1,153 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Frequently asked questions on JDT
-    </title>
-  </head>
-  <body>
-    <h1>
-      Frequently asked questions on JDT
-    </h1>
-    <h3>
-      Can I use a Java compiler other than the built-in one (javac for example) with the workbench?
-    </h3>
-    <p>
-      No. The JDT provides a number of sophisticated features including fully automatic incremental recompilation, code snippet evaluation, code assist, type hierarchies, and hot
-      code replace. These features require special support found in the workbench Java compiler (an integral part of the JDT's incremental project builder), but not available
-      in standard Java compilers.
-    </p>
-    <h3>
-      Where do Java packages come from?
-    </h3>
-    <p>
-      A project contains only files and folders. The notion of a Java package is introduced by a Java project's class path (at the UI, the Package Explorer presents the
-      packages as defined by the classpath). <strong>Tip:</strong> If the package structure is not what you expect, check out your class path. The Java search infrastructure only
-      finds declarations for and references from Java elements on the class path.
-    </p>
-    <h3>
-      When do I use an internal vs. an external JAR library file?
-    </h3>
-    <p>
-      An internal resource resides in some project in the workbench and is therefore managed by the workbench; like other resources, these resources can be version managed by the
-      workbench. An external resource is not part of the workbench and can be used only by reference. For example, a JRE is often external and very large, and there is no need to
-      associate it with a VCM system.
-    </p>
-    <h3>
-      When should I use source folders within a Java project?
-    </h3>
-    <p>
-      Each Java project locates its Java source files via one or more source type entries on the project's class path. Use source folders to organize the packages of a large
-      project into useful grouping, or to keep source code separate from other files in the same project. Also, use source folders if you have files (documentation for example)
-      which need not be on the build path.
-    </p>
-    <h3>
-      What are source attachments, How do I define one?
-    </h3>
-    <p>
-      Libraries are stored as JAR files containing binary class files (and perhaps other resources). These binary class files provide signature information for packages, classes,
-      methods, and fields. This information is sufficient to compile or run against, but contains far less information that the original source code. In order to make it easier to
-      browse and debug binary libraries, there is a mechanism for associating a corresponding source JAR (or ZIP) file with a binary JAR file.
-    </p>
-    <h3>
-      Why are all my resources duplicated in the output folder (bin, for example)?
-    </h3>
-    <p>
-      If your Java project is using source folders, then in the course of compiling the source files in the project, the Java compiler copies non-Java resources to the output
-      folder as well so that they will be available on the class path of the running program. To avoid certain resources to be copied to the output location you can set a resource
-      filter in the Java compiler preferences: <strong>Window &gt; Preferences &gt; Java &gt; Compiler &gt; Building</strong>
-    </p>
-    <h3>
-      How do I prevent having my documentation files from being copied to the project's output folder?
-    </h3>
-    <p>
-      Use source folders and put any resources that you do not want to be copied to the output folder into a separate folder that is not included on the class path.You can also
-      set a resource filter in the Java compiler preferences:<strong> Window &gt; Preferences &gt; Java &gt; Compiler &gt; Building</strong> to for example *.doc.
-    </p>
-    <h3>
-      How do I create a default package?
-    </h3>
-    <p>
-      You don't have to. Files in the root folder of a source folder or project are considered to be in the default package. In effect, every source folder has the capability
-      of having a fragment of the default package.
-    </p>
-    <h3>
-      What is refactoring?
-    </h3>
-    <p>
-      Refactoring means behavior-preserving program transformations. The JDT supports a number of transformations described in Martin Fowler's book <em>Refactoring: Improving
-      the Design of Existing Code</em>, Addison Wesley 1999.
-    </p>
-    <h3>
-      When do I use code select/code resolve (F3)?
-    </h3>
-    <p>
-      To find out the Java element that corresponds to a source range with the help of the compiler.
-    </p>
-    <h3>
-      Is the Java program information (type hierarchy, declarations, references, for example) produced by the Java builder? Is it still updated when auto-build is off?
-    </h3>
-    <p>
-      The Java program information is independent from the Java builder. It is automatically updated when performing resource changes or Java operations. In particular, all the
-      functionality offered by the Java tooling (for example, type hierarchies, code assisting, search) will continue to perform accurately when auto-build is off; for example,
-      when doing heavy refactoring which require to turn off the builders, you can still use code assist, which will reflect the latest changes (not yet build). Other than the
-      launching (that is, running and debugging) of programs, the only functionality which requires the Java builder is the evaluation of code snippets.
-    </p>
-    <h3>
-      After reopening a workbench, the first build that happens after editing a Java source file seems to take a long time. Why is that?
-    </h3>
-    <p>
-      The Java incremental project builder saves its internal state to a file when the workbench is closed. On the first build after the project is reopened, the Java incremental
-      project builder will restore its internal state. When this file is large, the user experiences an unusually long build delay.
-    </p>
-    <h3>
-      I can't see a type hierarchy for my class. What can I do?
-    </h3>
-    <p>
-      Check that you have your build class path set up properly. Setting up the proper build class path is an important task when doing Java development. Without the correct build
-      path, you will not be able to compile your code. In addition, you will not be able to search or look at the type hierarchies for Java elements.
-    </p>
-    <h3>
-      How do I turn off &quot;auto compile&quot; and do it manually when I want?
-    </h3>
-    
-<p> Clear the <strong>Window &gt; Preferences &gt; General &gt; Workspace &gt; Build automatically</strong> checkbox. 
-When you want to build, press <kbd>Ctrl+B</kbd>, 
-  or select <strong>Project &gt; Build All</strong> from the menu bar. </p>
-<p><b>Hint</b>: when you turn &quot;auto compile&quot; off and build manually, 
-  you may also want to select the <strong>Window &gt; Preferences &gt; General &gt; Workspace &gt; Safe automatically before build</strong> checkbox. 
-</p>
-<h3>When I select a method or a field in the Outline view, only the source for 
-  that element is shown in the editor. What do I do to see the source of the whole 
-  file?</h3>
-<p>There is a toolbar button <b>Show Source of Selected Element Only</b> - all 
-  you have to do is un-press it.</p>
-<h3>Can I nest source folders?</h3>
-<p>Yes, you can use exclusion filters to create nested source folders.</p>
-<h3>Can I have separate output folders for each source folder?</h3>
-<p>Yes, select the <b>Allow output folders for source folders</b> checkbox in 
-  the <b>Java Build Path &gt; Source</b> property page of your Java project.</p>
-<h3>Can I have an output or source folder that is located outside of the workspace?</h3>
-<p>Yes, you can create a linked folder that points to the desired location and 
-  use that folder as the source or output folder in your Java project.</p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <p>
-      <a href="../reference/ref-123.htm">Java Build Path page</a><br>
-       <a href="../reference/ref-155.htm">JDT glossary</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-154.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-154.htm
deleted file mode 100644
index 22ced1f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-154.htm
+++ /dev/null

@@ -1,85 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Extract method errors
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Extract method errors
-    </h1>
-    <p>
-      When you attempt to extract a method, you may get one or more of the following common errors:
-    </p>
-    <ul>
-      <li>
-        <code>Selected block references a local type declared outside the selection</code> A local type declaration is not part of the selection but is referenced by one of the
-        statements selected for extraction. Either extend the selection that it includes the local type declaration or reduce the selection that no reference to the local type
-        declaration is selected.<br>
-      </li>
-      <li>
-        <code>A local type declared in the selected block is referenced outside the selection</code> The selection covers a local type declaration but the type is also referenced
-        outside the selected statements. Either extend the selection that is includes all references to the local type or reduce the selection that the local type declaration
-        isn't selected.<br>
-      </li>
-      <li>
-        <code>Ambiguous return value: selected block contains more than one assignment to local variable</code> More than one assignment to a local variable was found inside the
-        selected block. Either reduce the selection that only one assignment is selected or extend the selection that at least all reference except of one to the local variables
-        are covered by the selection too.<br>
-      </li>
-      <li>
-        <code>Ambiguous return value: expression access to local and return statement selected</code> The selected statement generates more than one return value. This is for
-        example the case if an expression is selected and an expression's argument is modified as well. To remedy this problem extend the selection to cover the read access of
-        the modified argument as well.<br>
-      </li>
-      <li>
-        <code>Selection contains a break statement but the corresponding break target isn't selected</code> To remedy the problem either extend the selection to include the
-        break / continue target or reduce the selection that the break / continue statement isn't covered by the selection.<br>
-      </li>
-      <li>
-        <code>Selection contains a continue statement but the corresponding continue target isn't selected</code> To remedy the problem either extend the selection to include
-        the break / continue target or reduce the selection that the break / continue statement isn't covered by the selection.<br>
-      </li>
-      <li>
-        <code>Selection starts inside a comment</code> Parts of a comment cannot be extracted. Either extend the selection that it covers the whole comment or reduce the selection
-        that the comment isn't covered at all.<br>
-      </li>
-      <li>
-        <code>Selection ends inside a comment</code> Parts of a comment can't be extracted. Either extend the selection that it covers the whole comment or reduce the
-        selection that the comment isn't covered at all.<br>
-      </li>
-      <li>
-        <code>Cannot extract selection that ends in the middle of a statement</code> Adjust selection so 
-        that it fully covers a set of statements or expressions. The users can extend the selection to 
-        a valid range using the <strong>Expand Selection to</strong> in the <a href="ref-menu-edit.htm">Edit menu.</a><br>
-        <a href="ref-menu-edit.htm"></a>
-      </li>
-    </ul>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a><br>
-      <a href="../concepts/concepts-9.htm">Refactoring support</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-87.htm">Extracting a method</a><br>
-      <a href="../tasks/tasks-176.htm">Using Structured Selection</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="ref-menu-source.htm">Source menu</a><br>
-      <a href="ref-menu-refactor.htm">Refactor Menu</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-155.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-155.htm
deleted file mode 100644
index 9c04415..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-155.htm
+++ /dev/null

@@ -1,153 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      JDT glossary
-    </title>
-  </head>
-  <body>
-    <h1>
-      JDT glossary
-    </h1>
-    <p>
-      <strong>CLASS file</strong>
-    </p>
-    <p>
-      A compiled Java source file.
-    </p>
-    <p>
-      <strong>compilation unit</strong>
-    </p>
-    <p>
-      A Java source file.
-    </p>
-    <p>
-      <strong>field</strong>
-    </p>
-    <p>
-      A field inside a type.
-    </p>
-    <p>
-      <strong>import container</strong>
-    </p>
-    <p>
-      Represents a collection of import declarations. These can be seen in the Outline view.
-    </p>
-    <p>
-      <strong>import declaration</strong>
-    </p>
-    <p>
-      A single package import declaration.
-    </p>
-    <p>
-      <strong>initializer</strong>
-    </p>
-    <p>
-      A static or instance initializer inside a type.
-    </p>
-    <p>
-      <strong>JAR file</strong>
-    </p>
-    <p>
-      JAR (Java archive) files are containers for compiled Java source files. They can be associated with an archive (such as, ZIP, JAR) as a source attachment. The children of
-      JAR files are packages. JAR files can be either compressed or uncompressed.
-    </p>
-    <p>
-      <strong>JAVA elements</strong>
-    </p>
-    <p>
-      Java elements are Java projects, packages, compilation units, class files, types, methods and fields.
-    </p>
-    <strong>JAVA file</strong><br>
-     <br>
-     
-    <p>
-      An editable file that is compiled into a byte code (CLASS) file.
-    </p>
-    <p>
-      <strong>Java projects</strong>
-    </p>
-    <p>
-      Projects which contain compilable Java source code and are the containers for source folders or packages.
-    </p>
-    <p>
-      <strong>JDT</strong>
-    </p>
-    <p>
-      Java development tools. Workbench components that allow you to write, edit, execute, and debug Java code.
-    </p>
-    <p>
-      <strong>JRE</strong>
-    </p>
-    <p>
-      Java runtime environment (for example, J9, JDK, and so on).
-    </p>
-    <p>
-      <strong>method</strong>
-    </p>
-    <p>
-      A method or constructor inside a type.
-    </p>
-    <p>
-      <strong>package declaration</strong>
-    </p>
-    <p>
-      The declaration of a package inside a compilation unit.
-    </p>
-    <p>
-      <strong>packages</strong>
-    </p>
-    <p>
-      A group of types that contain Java compilation units and CLASS files.
-    </p>
-    <p>
-      <strong>refactoring</strong>
-    </p>
-    <p>
-      A comprehensive code editing feature that helps you improve, stabilize, and maintain your Java code. It allows you to make a system-wide coding change without affecting the
-      semantic behavior of the system.
-    </p>
-    <p>
-      <strong>type</strong>
-    </p>
-    <p>
-      A type inside a compilation unit or CLASS file.
-    </p>
-    <p>
-      <strong>source folder</strong>
-    </p>
-    <p>
-      A folder that contains Java packages.
-    </p>
-    <p>
-      <strong>VCM</strong>
-    </p>
-    <p>
-      Version control management. This term refers to the various repository and versioning features in the workbench.
-    </p>
-    <p>
-      <strong>VM</strong>
-    </p>
-    <p>
-      Virtual machine.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <p>
-      <a href="../reference/ref-152.htm">Frequently asked questions on JDT</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-156.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-156.htm
deleted file mode 100644
index f67b292..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-156.htm
+++ /dev/null

@@ -1,1544 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      JDT icons
-    </title>
-  </head>
-  <body>
-    <h1>
-      JDT icons
-    </h1>
-    <h2>
-      Objects
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="40%">
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/jcu_obj.png"  alt="Compilation Unit (*.java file)"><br>
-          </td>
-          <td valign="top">
-            Compilation Unit (*.java file)<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/jcu_resource_obj.png"  alt="File ending with .java"><br>
-          </td>
-          <td valign="top">
-            Java file which is not on a build path<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/classf_obj.png"  alt="class file"><br>
-          </td>
-          <td valign="top" width="90%">
-            class file<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/file_obj.png"  alt="file without icon assigned to its type"><br>
-          </td>
-          <td valign="top">
-            file without icon assigned to its type<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/unknown_obj.png"  alt="unknown object"><br>
-          </td>
-          <td valign="top">
-            unknown object<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.debug.ui/obj16/jsbook_obj.png"  alt="Java scrapbook page (*.jpage file)"><br>
-          </td>
-          <td valign="top">
-            Java scrapbook page (*.jpage file)<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.debug.ui/obj16/jsbook_run_obj.png"  alt="Java scrapbook page (evaluation in progress)"><br>
-          </td>
-          <td valign="top">
-            Java scrapbook page (evaluation in progress)<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/jar_desc_obj.png"  alt="JAR description file"><br>
-          </td>
-          <td valign="top">
-            JAR description file<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/jworkingSet_obj.png"  alt="Java Working Set"><br>
-          </td>
-          <td valign="top">
-            Java Working Set<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/java_model_obj.png"  alt="Java Model"><br>
-          </td>
-          <td valign="top">
-            Java Model<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/library_obj.png"  alt="JRE system library container"><br>
-          </td>
-          <td valign="top">
-            JRE system library container<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/jar_lsrc_obj.png"  alt="JAR file with attached source"><br>
-          </td>
-          <td valign="top">
-            JAR file with attached source<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/jar_l_obj.png"  alt="JAR file without attached source"><br>
-          </td>
-          <td valign="top">
-            JAR file without attached source<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/packagefolder_obj.png"  alt="source folder"><br>
-          </td>
-          <td valign="top">
-            source folder<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/package_obj.png"  alt="package"><br>
-          </td>
-          <td valign="top">
-            package<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/empty_pack_obj.png"  alt="empty package"><br>
-          </td>
-          <td valign="top">
-            empty package<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/logical_package_obj.png"  alt="logical package"><br>
-          </td>
-          <td valign="top">
-            logical package<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/empty_logical_package_obj.png"  alt="empty logical package"><br>
-          </td>
-          <td valign="top">
-            empty logical package<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/empty_pack_fldr_obj.png"  alt="package only containing non Java resources"><br>
-          </td>
-          <td valign="top">
-            package only containing non Java resources<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/packd_obj.png"  alt="package declaration"><br>
-          </td>
-          <td valign="top">
-            package declaration<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/impc_obj.png"  alt="import container"><br>
-          </td>
-          <td valign="top">
-            import container<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/imp_obj.png"  alt="import"><br>
-          </td>
-          <td valign="top">
-            import<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/class_default_obj.png"  alt="default type (package visible)"><br>
-          </td>
-          <td valign="top">
-            default type (package visible)<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/class_obj.png"  alt="public type"><br>
-          </td>
-          <td valign="top">
-            public type<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/int_default_obj.png"  alt="default interface (package visible)"><br>
-          </td>
-          <td valign="top">
-            default interface (package visible)<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/int_obj.png"  alt="public interface"><br>
-          </td>
-          <td valign="top">
-            public interface<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/innerclass_default_obj.png"  alt="default inner type (package visible)"><br>
-          </td>
-          <td valign="top">
-            default inner type (package visible)<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/innerclass_private_obj.png"  alt="private inner type"><br>
-          </td>
-          <td valign="top">
-            private inner type<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/innerclass_protected_obj.png"  alt="protected inner type"><br>
-          </td>
-          <td valign="top">
-            protected inner type<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/innerclass_public_obj.png"  alt="public inner type"><br>
-          </td>
-          <td valign="top">
-            public inner type<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/innerinterface_default_obj.png"  alt="default inner interface (package visible)"><br>
-          </td>
-          <td valign="top">
-            default inner interface (package visible)<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/innerinterface_private_obj.png"  alt="private inner interface"><br>
-          </td>
-          <td valign="top">
-            private inner interface<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/innerinterface_protected_obj.png"  alt="protected inner interface"><br>
-          </td>
-          <td valign="top">
-            protected inner interface<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/innerinterface_public_obj.png"  alt="public inner interface"><br>
-          </td>
-          <td valign="top">
-            public inner interface<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            &nbsp;<br>
-          </td>
-          <td valign="top">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/field_default_obj.png"  alt="default field (package visible)"><br>
-          </td>
-          <td valign="top">
-            default field (package visible)<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/field_private_obj.png"  alt="private field"><br>
-          </td>
-          <td valign="top">
-            private field<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/field_protected_obj.png"  alt="protected field"><br>
-          </td>
-          <td valign="top">
-            protected field<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/field_public_obj.png"  alt="public field"><br>
-          </td>
-          <td valign="top">
-            public field<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/methdef_obj.png"  alt="default method (package visible)"><br>
-          </td>
-          <td valign="top">
-            default method (package visible)<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/methpri_obj.png"  alt="private method"><br>
-          </td>
-          <td valign="top">
-            private method<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/methpro_obj.png"  alt="protected method"><br>
-          </td>
-          <td valign="top">
-            protected method<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/methpub_obj.png"  alt="public method"><br>
-          </td>
-          <td valign="top">
-            public method<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-     
-    <h2>
-      Object adornments
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="40%">
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/java_ovr.png" alt="Java Overlay" ><br>
-          </td>
-          <td valign="top">
-            marks project as Java project<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/error_co.png" alt="Abstract Overlay" ><br>
-          </td>
-          <td valign="top">
-            this Java element causes an error<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/warning_co.png" alt="Warning Overlay" ><br>
-          </td>
-          <td valign="top">
-            this Java element causes warning<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/deprecated.png" alt="Deprecation Overlay" ><br>
-          </td>
-          <td valign="top">
-            this Java element is deprecated<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/constr_ovr.png" alt="Constructor Overlay" ><br>
-          </td>
-          <td valign="top" width="90%">
-            constructor<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/abstract_co.png" alt="Abstract Overlay" ><br>
-          </td>
-          <td valign="top" width="90%">
-            abstract member<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/final_co.png" alt="Final Overlay" ><br>
-          </td>
-          <td valign="top" width="90%">
-            final member<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/static_co.png" alt="Static overlay" ><br>
-          </td>
-          <td valign="top">
-            static member<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/synch_co.png" alt="Synchronized Overlay" ><br>
-          </td>
-          <td valign="top">
-            synchronized member<br>
-          </td>
-        </tr>
-        <!--
-          native_co.png and volatile_co.png, and read.png and write.png are currently unused.
-          sync_impl.png and sync_over.png are self-explanatory combinations of the above overlays.
-        -->
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/run_co.png" alt="Run Overlay" ><br>
-          </td>
-          <td valign="top">
-            type with public static void main(String[] args)<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/implm_co.png" alt="Implementor of interface overlay" ><br>
-          </td>
-          <td valign="top" width="90%">
-            implements method from interface<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/over_co.png" alt="Overrides Overlay" ><br>
-          </td>
-          <td valign="top" width="90%">
-            overrides method from super class<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/focus_ovr.png" alt="Focus Overlay" ><br>
-          </td>
-          <td valign="top">
-            type with focus in Type hierarchy<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/maxlevel_co.png" alt="Maximal Expansion Overlay" ><br>
-          </td>
-          <td valign="top">
-            maximal expansion level in Call Hierarchy<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/recursive_co.png" alt="Recursive Overlay" ><br>
-          </td>
-          <td valign="top">
-            recursive call in Call Hierarchy<br>
-          </td>
-        </tr>
-        <!-- callee_co.png and caller_co.png are currently unused -->
-      </tbody>
-    </table>
-    <br>
-     
-    <h2>
-      Build path
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="40%">
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/envvar_obj.png"  alt="class path variable"><br>
-          </td>
-          <td valign="top" width="90%">
-            class path variable<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/envvar_nonexist_obj.png"  alt="unresolved class path variable"><br>
-          </td>
-          <td valign="top" width="90%">
-            unresolved class path variable<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/jar_src_obj.png"  alt="JAR with attached source"><br>
-          </td>
-          <td valign="top" width="90%">
-            JAR with attached source<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/jar_obj.png"  alt="JAR without attached source"><br>
-          </td>
-          <td valign="top" width="90%">
-            JAR without attached source<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/library_obj.png"  alt="system library"><br>
-          </td>
-          <td valign="top">
-            system library<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/prjct_nonexist_obj.png"  alt="reference to unavailable project"><br>
-          </td>
-          <td valign="top" width="90%">
-            reference to unavailable project<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/packagefolder_nonexist_obj.png"  alt="reference to unavailable source folder"><br>
-          </td>
-          <td valign="top">
-            reference to unavailable source folder<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/jar_nonexist_obj.png"  alt="reference to unavailable JAR"><br>
-          </td>
-          <td valign="top" width="90%">
-            reference to unavailable JAR<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/cp_order_obj.png"  alt="build path ordering"><br>
-          </td>
-          <td valign="top" width="90%">
-            build path ordering<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/inclusion_filter_attrib.png"  alt="inclusion filter"><br>
-          </td>
-          <td valign="top" width="90%">
-            inclusion filter<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/exclusion_filter_attrib.png"  alt="exclusion filter"><br>
-          </td>
-          <td valign="top" width="90%">
-            exclusion filter<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/output_folder_attrib.png"  alt="output folder"><br>
-          </td>
-          <td valign="top" width="90%">
-            output folder<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/javadoc_location_attrib.png"  alt="Javadoc location"><br>
-          </td>
-          <td valign="top" width="90%">
-            Javadoc location<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/source_attach_attrib.png"  alt="source attachment"><br>
-          </td>
-          <td valign="top" width="90%">
-            source attachment<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-     
-    <h2>
-      Code assist
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="40%">
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/html_tag_obj.png"  alt="HTML tag"><br>
-          </td>
-          <td valign="top" width="90%">
-            HTML tag<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/jdoc_tag_obj.png"  alt="Javadoc tag"><br>
-          </td>
-          <td valign="top" width="90%">
-            Javadoc tag<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/localvariable_obj.png"  alt="local variable"><br>
-          </td>
-          <td valign="top" width="90%">
-            local variable<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/template_obj.png"  alt="template"><br>
-          </td>
-          <td valign="top" width="90%">
-            template<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-     
-    <h2>
-      Compare
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="40%">
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/compare_field.png"  alt="field"><br>
-          </td>
-          <td valign="top" width="90%">
-            field<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/compare_method.png"  alt="method"><br>
-          </td>
-          <td valign="top" width="90%">
-            method<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-     
-    <h2>
-      Debugger
-    </h2>
-    
-<table cellspacing="0" cellpadding="5" border="1" width="40%">
-  <tbody> 
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/ldebug_obj.png"  alt="debug launch"><br>
-    </td>
-    <td valign="top" width="90%"> debug launch<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/lrun_obj.png"  alt="run launch"><br>
-    </td>
-    <td valign="top" width="90%"> run launch<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/terminatedlaunch_obj.png"  alt="terminated run launch"><br>
-    </td>
-    <td valign="top" width="90%"> terminated run launch<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/osprc_obj.png"  alt="process"><br>
-    </td>
-    <td valign="top" width="90%"> process<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/osprct_obj.png"  alt="terminated process"><br>
-    </td>
-    <td valign="top" width="90%"> terminated process<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/debugt_obj.png"  alt="debug target"><br>
-    </td>
-    <td valign="top" width="90%"> debug target<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/debugts_obj.png"  alt="suspended debug target"><br>
-    </td>
-    <td valign="top" width="90%"> suspended debug target<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/debugtt_obj.png"  alt="terminated debug target"><br>
-    </td>
-    <td valign="top" width="90%"> terminated debug target<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center" rowspan="1" colspan="2"> <br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/thread_obj.png"  alt="thread"><br>
-    </td>
-    <td valign="top" width="90%"> thread<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/threads_obj.png"  alt="suspended thread"><br>
-    </td>
-    <td valign="top" width="90%"> suspended thread<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/stckframe_obj.png"  alt="stack frame"><br>
-    </td>
-    <td valign="top" width="90%"> stack frame<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/stckframe_running_obj.png"  alt="running stack frame"><br>
-    </td>
-    <td valign="top" width="90%"> running stack frame<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/warning_co.png"  alt="adornment that marks a stack frame that may be out of synch with the target VM as a result of an unsuccessful hot code replace"> 
-      <br>
-    </td>
-    <td valign="top" width="90%"> adornment that marks a stack frame that may 
-      be out of synch with the target VM as a result of an unsuccessful hot code 
-      replace<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/ovr16/error.png"  alt="adornment that marks a stack frame that is out of synch with the target VM as a result of an unsuccessful hot code replace"> 
-      <br>
-    </td>
-    <td valign="top" width="90%"> adornment that marks a stack frame that is out 
-      of synch with the target VM as a result of an unsuccessful hot code replace<br>
-    </td>
-  </tr>
-  <tr>
-    <td valign="middle" align="center"><img src="../images/org.eclipse.jdt.debug.ui/obj16/insp_sbook.png"  alt="adornment that marks a stack frame that may be out of synch with the target VM as a result of an unsuccessful hot code replace"></td>
-    <td valign="top" width="90%">inspected object or primitive value</td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/expression_obj.png"  alt="evaluated expression"><br>
-    </td>
-    <td valign="top" width="90%"> watch expression<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/obj16/localvariable_obj.png"  alt="local variable"><br>
-    </td>
-    <td valign="top" width="90%"> local variable<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center" rowspan="1" colspan="2"> <br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/obj16/monitor_obj.png"  alt="monitor"><br>
-    </td>
-    <td valign="top" width="90%"> monitor<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/contention_ovr.png"  alt="a monitor in contention"><br>
-    </td>
-    <td valign="top" width="90%"> a monitor in contention<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/contentionformonitor_ovr.png"  alt="in thread in contention for a monitor"><br>
-    </td>
-    <td valign="top" width="90%"> a thread in contention for a monitor<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/owned_ovr.png"  alt="a monitor that is owned by a thread"><br>
-    </td>
-    <td valign="top" width="90%"> a monitor that is owned by a thread<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/ownsmonitor_ovr.png"  alt="a thread that owns a monitor"><br>
-    </td>
-    <td valign="top" width="90%"> a thread that owns a monitor<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center" rowspan="1" colspan="2"> <br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/inst_ptr_top.png"  alt="current instruction pointer (top of stack)"><br>
-    </td>
-    <td valign="top" width="90%"> current instruction pointer (top of stack)<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/inst_ptr.png"  alt="current instruction pointer"><br>
-    </td>
-    <td valign="top" width="90%"> current instruction pointer<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center" rowspan="1" colspan="2"> <br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/brkp_obj.png"  alt="enabled line breakpoint"><br>
-    </td>
-    <td valign="top" width="90%"> enabled line breakpoint<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/brkpd_obj.png"  alt="disabled line breakpoint"><br>
-    </td>
-    <td valign="top" width="90%"> disabled line breakpoint<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/installed_ovr.png"  alt="adornment that marks a line breakpoints as installed"><br>
-    </td>
-    <td valign="top" width="90%"> adornment that marks a line breakpoints as installed<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/conditional_ovr.png"  alt="adornment that marks a breakpoint as conditional"><br>
-    </td>
-    <td valign="top" width="90%"> adornment that marks a breakpoint as conditional<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/entry_ovr.png"  alt="adornment that marks an entry method breakpoint"><br>
-    </td>
-    <td valign="top" width="90%"> adornment that marks an entry method breakpoint<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/exit_ovr.png"  alt="adornment that marks an exit method breakpoint"><br>
-    </td>
-    <td valign="top" width="90%"> adornment that marks an exit method breakpoint<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center" rowspan="1" colspan="2"> <br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/obj16/read_obj.png"  alt="field access watchpoint"><br>
-    </td>
-    <td valign="top" width="90%"> field access watchpoint<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/obj16/write_obj.png"  alt="field modification watchpoint"><br>
-    </td>
-    <td valign="top" width="90%"> field modification watchpoint<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/obj16/readwrite_obj.png"  alt="field access and modification watchpoint"><br>
-    </td>
-    <td valign="top" width="90%"> field access and modification watchpoint<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/installed_ovr.png"  alt="adornment that marks a watchpoint as installed"><br>
-    </td>
-    <td valign="top" width="90%"> adornment that marks a watchpoint as installed<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center" rowspan="1" colspan="2"> <br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/obj16/jexception_obj.png"  alt="exception breakpoint"><br>
-    </td>
-    <td valign="top" width="90%"> exception breakpoint<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/obj16/jrtexception_obj.png"  alt="runtime exception breakpoint"><br>
-    </td>
-    <td valign="top" width="90%"> runtime exception breakpoint<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/obj16/jexceptiond_obj.png"  alt="disabled exception breakpoint"><br>
-    </td>
-    <td valign="top" width="90%"> disabled exception breakpoint<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/caught_ovr.png"  alt="adornment that marks an exception breakpoint as caught"><br>
-    </td>
-    <td valign="top" width="90%"> adornment that marks an exception breakpoint 
-      as caught<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/uncaught_ovr.png"  alt="adornment that marks an exception breakpoint as uncaught"><br>
-    </td>
-    <td valign="top" width="90%"> adornment that marks an exception breakpoint 
-      as uncaught<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/scoped_ovr.png"  alt="adornment that marks an exception breakpoint as scoped"><br>
-    </td>
-    <td valign="top" width="90%"> adornment that marks an exception breakpoint 
-      as scoped<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/installed_ovr.png"  alt="adornment that marks an exception breakpoint as installed"><br>
-    </td>
-    <td valign="top" width="90%"> adornment that marks an exception breakpoint 
-      as installed<br>
-    </td>
-  </tr>
-  </tbody> 
-</table>
-    <br>
-     
-    <h2>
-      Editor
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="40%">
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/implm_co.png"  alt="implements"><br>
-          </td>
-          <td valign="top" width="90%">
-            implements<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/over_co.png"  alt="overrides"><br>
-          </td>
-          <td valign="top" width="90%">
-            overrides<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/quickassist_obj.png"  alt="quick assist available"><br>
-          </td>
-          <td valign="top" width="90%">
-            quick assist available<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/searchm_obj.png"  alt="search match"><br>
-          </td>
-          <td valign="top" width="90%">
-            search match<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/collapsed.png"  alt="collapsed"><br>
-          </td>
-          <td valign="top" width="90%">
-            collapsed<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/expanded.png"  alt="expanded"><br>
-          </td>
-          <td valign="top" width="90%">
-            expanded<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-    
-    <h2>
-      JUnit
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="40%">
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.junit/obj16/test.png"  alt="test"><br>
-          </td>
-          <td valign="top" width="90%">
-            test<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.junit/obj16/testrun.png"  alt="currently running test"><br>
-          </td>
-          <td valign="top" width="90%">
-            currently running test<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.junit/obj16/testok.png"  alt="successful test"><br>
-          </td>
-          <td valign="top" width="90%">
-            successful test<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.junit/obj16/testfail.png"  alt="failing test"><br>
-          </td>
-          <td valign="top" width="90%">
-            failing test<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.junit/obj16/testerr.png"  alt="test throwing an exception"><br>
-          </td>
-          <td valign="top" width="90%">
-            test throwing an exception<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.junit/obj16/tsuite.png"  alt="test suite"><br>
-          </td>
-          <td valign="top" width="90%">
-            test suite<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.junit/obj16/tsuiterun.png"  alt="currently running test suite"><br>
-          </td>
-          <td valign="top" width="90%">
-            currently running test suite<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.junit/obj16/tsuiteok.png"  alt="successfully completed test suite"><br>
-          </td>
-          <td valign="top" width="90%">
-            successfully completed test suite<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.junit/obj16/tsuitefail.png"  alt="test suite with failing test"><br>
-          </td>
-          <td valign="top" width="90%">
-            test suite with failing test<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.junit/obj16/tsuiteerror.png"  alt="test suite with exception throwing test"><br>
-          </td>
-          <td valign="top" width="90%">
-            test suite with exception throwing test<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-     
-    <h2>
-      NLS tools
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="40%">
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/skip.png"  alt="skipped NLS key"><br>
-          </td>
-          <td valign="top" width="90%">
-            skipped NLS key<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/translate.png"  alt="translated NLS key"><br>
-          </td>
-          <td valign="top" width="90%">
-            translated NLS key<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/never_translate.png"  alt="untranslated NLS key"><br>
-          </td>
-          <td valign="top" width="90%">
-            untranslated NLS key<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/nls_search_obj.png"  alt="search for unused NLS keys"><br>
-          </td>
-          <td valign="top" width="90%">
-            search for unused NLS keys<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-     
-    <h2>
-      Quick fix
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="40%">
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/quickfix_error_obj.png"  alt="quick fixable error"><br>
-          </td>
-          <td valign="top" width="90%">
-            quick fixable error<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/quickfix_warning_obj.png"  alt="quick fixable warning"><br>
-          </td>
-          <td valign="top" width="90%">
-            quick fixable warning<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/error_gray_obj.png"  alt="error that got fixed in source code"><br>
-          </td>
-          <td valign="top" width="90%">
-            error that got fixed in source but file still needs a recompile<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/warning_gray_obj.png"  alt="warning that got fix in source code"><br>
-          </td>
-          <td valign="top" width="90%">
-            warning that got fixed in source but file still needs a recompile<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/add_correction.png"  alt="add"><br>
-          </td>
-          <td valign="top" width="90%">
-            add<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/correction_change.png"  alt="change"><br>
-          </td>
-          <td valign="top" width="90%">
-            change<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/correction_cast.png"  alt="change cast"><br>
-          </td>
-          <td valign="top" width="90%">
-            change cast<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/correction_move.png"  alt="move to another package"><br>
-          </td>
-          <td valign="top" width="90%">
-            move to another package<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/remove_correction.png"  alt="remove"><br>
-          </td>
-          <td valign="top" width="90%">
-            remove<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/correction_delete_import.png"  alt="remove import"><br>
-          </td>
-          <td valign="top" width="90%">
-            remove import<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/correction_rename.png"  alt="rename"><br>
-          </td>
-          <td valign="top">
-            rename<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/jexception_obj.png"  alt="surround with try/catch"><br>
-          </td>
-          <td valign="top">
-            surround with try/catch<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-     
-    <h2>
-      Refactoring
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="40%">
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/change.png"  alt="general change"><br>
-          </td>
-          <td valign="top">
-            general change<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/composite_change.png"  alt="composite change"><br>
-          </td>
-          <td valign="top">
-            composite change<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/cu_change.png"  alt="compilation unit change"><br>
-          </td>
-          <td valign="top">
-            compilation unit change<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/text_edit.png"  alt="text change"><br>
-          </td>
-          <td valign="top">
-            text change<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/file_change.png"  alt="file change"><br>
-          </td>
-          <td valign="top" width="90%">
-            file change
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/fatalerror_obj.png"  alt="Stop error">
-          </td>
-          <td valign="top">
-            Stop error<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/error_obj.png"  alt="Error"><br>
-          </td>
-          <td valign="top">
-            Error<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/warning_obj.png"  alt="Warning"><br>
-          </td>
-          <td valign="top">
-            Warning<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/info_obj.png"  alt="Information"><br>
-          </td>
-          <td valign="top">
-            Information<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-     
-    <h2>
-      Search
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="40%">
-      <tbody>
-        <tr>
-          <td valign="middle" align="right">
-            <img src="../images/org.eclipse.jdt.ui/obj16/jsearch_obj.png"  alt="Java Search"><br>
-          </td>
-          <td valign="top">
-            Java Search<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/search_decl_obj.png"  alt="search for declarations"><br>
-          </td>
-          <td valign="top">
-            search for declarations<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/search_ref_obj.png"  alt="search for references"><br>
-          </td>
-          <td valign="top">
-            search for references<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/nls_search_obj.png"  alt="search for unused NLS keys"><br>
-          </td>
-          <td valign="top" width="90%">
-            search for unused NLS keys<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-     
-    <h2>
-      Search - Occurrences in File
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="40%">
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/occ_match.png"  alt="general match"><br>
-          </td>
-          <td valign="top" width="90%">
-            a general match<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/occ_read.png"  alt="read access to local or field"><br>
-          </td>
-          <td valign="top" width="90%">
-            read access to local or field<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/occ_write.png"  alt="write access to local or field"><br>
-          </td>
-          <td valign="top" width="90%">
-			write access to local or field          
-		  </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-    
-    <h2>
-      Type hierarchy view
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="40%">
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/classfo_obj.png"  alt="type from non selected package"><br>
-          </td>
-          <td valign="top">
-            type from non selected package<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/intf_obj.png"  alt="interface from non selected package"><br>
-          </td>
-          <td valign="top">
-            interface from non selected package<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-<!-- currently unused in org.eclipse.jdt.ui/obj16:
-brkpi_obj.png
-classf_generate.png
-externalize.png
-ignore.png
-internalize.png
-jsbook_obj.png - from debug
-no_breakpoint.png
--->
-
-<!-- calculated, cannot copy from plugin, must take a screenshot:
-error_gray_obj.png
-warning_gray_obj.png
--->
-
-<!-- unsure what to do:
-jworkingSet_obj.png
--->
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-17.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-17.htm
deleted file mode 100644
index 57d48ae..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-17.htm
+++ /dev/null

@@ -1,96 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Code Formatter
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Code Formatter
-    </h1>
-
-<p>This page lets you manage your code formatter profiles for the Java code formatter.</p>
-<table border="1" cellspacing="0" cellpadding="5" width="600">
-	<thead>
-		<tr>
-			<th>
-			<p>Action</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top" width="25%">
-			<p>New...</p>
-			</td>
-			<td valign="top">
-			<p>Shows the dialog to create a new formatter profile. The dialog requires you to enter a name for the new formatter profile. Additionally, you may select a built-in or user-defined existing formatter profile to base your new formatter profile on.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Show/Edit...</p>
-			</td>
-			<td valign="top">
-			<p>Shows a dialog which displays the settings stored in the selected code formatter profile. Only user-defined profiles can be edited.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Rename...</p>
-			</td>
-			<td valign="top">
-			<p>Renames the selected code formatter profile. This action is only available on user-defined profiles.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Remove</p>
-			</td>
-			<td valign="top">
-			<p>Removes the selected code formatter profile. This action is only available on user-defined profiles.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Import...</p>
-			</td>
-			<td valign="top">
-			<p>Imports code formatter profiles from the file system.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Export...</p>
-			</td>
-			<td valign="top">
-			<p>Exports the selected code formatter profile to the file system. This action is only available on user-defined profiles.</p>
-			</td>
-		</tr>
-	</tbody>
-</table>
-
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-66.htm">Formatting Java code</a><br>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-	</p>
-	<p>
-      <a href="../reference/ref-java-editor.htm">Java editor</a><br>
-       <a href="../reference/ref-21.htm">Java editor preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-18.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-18.htm
deleted file mode 100644
index 7e6bfd2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-18.htm
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Installed JREs
-    </title>
-  </head>
-  <body>
-    <h1>
-      Installed JREs
-    </h1>
-    <p>
-      Check the box for the JRE that you want to act as your default for running and debugging Java programs in the workbench.
-    </p>
-    <p>
-      This JRE defines the values for the three reserved classpath variables (JRE_LIB, JRE_SRC, JRE_SRCROOT).
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-19.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-19.htm
deleted file mode 100644
index 4ced7f6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-19.htm
+++ /dev/null

@@ -1,103 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      JRE installations
-    </title>
-  </head>
-  <body>
-    <h1>
-      JRE installations
-    </h1>
-    
-<table border="1" cellspacing="0" cellpadding="5" >
-  <caption> Classpath Variable Preferences </caption>
-  <thead> 
-  <tr> 
-    <th rowspan="1" colspan="1"> 
-      <p> Option </p>
-    </th>
-    <th rowspan="1" colspan="1"> 
-      <p> Description </p>
-    </th>
-  </tr>
-  </thead> <tbody> 
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> Add... </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> Adds a new JRE definition to the workbench. In the resulting dialog, 
-        specify the following: </p>
-      <ul>
-        <li> JRE type: (select a VM type from the drop-down list) </li>
-        <li> JRE name: Type a name for this JRE definition </li>
-        <li> JRE home directory: Type or browse to select the root directory for 
-          this JRE installation </li>
-        <li> Javadoc URL: Type or browse to select the URL location. The location 
-          is used by the Javadoc export wizard as a default value and by the 'Open 
-          External Javadoc' action. Debugger timeout: Type the default timeout 
-          for this JRE's debugger (in ms) </li>
-        <li> Either check the box to use the default library locations for this 
-          JRE or clear the checkbox and type or browse to select library locations 
-          for the following: 
-          <ul>
-            <li> JAR file (e.g., classes.zip) </li>
-            <li> Source file (e.g., source.zip) </li>
-          </ul>
-        </li>
-      </ul>
-      <p> You can click the <strong>Browse</strong> buttons to browse for paths. 
-      </p>
-    </td>
-  </tr>
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> Edit... </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> Allows you to edit the selected JRE. </p>
-    </td>
-  </tr>
-  <tr>
-    <td colspan="1" valign="top" align="left">Remove</td>
-    <td colspan="1" valign="top" align="left">Removes the selected JRE from the 
-      workbench.</td>
-  </tr>
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> Search... </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left"> 
-      <p> Automatically searches for JREs installed in the local file system and 
-        creates corresponding JRE definitions in the workspace.</p>
-    </td>
-  </tr>
-  </tbody> 
-</table>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/cclsspthv.htm">Classpath variables</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-JREs.htm">Working with JREs</a>
-    </p>
-         <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-124.htm">Source Attachment</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-2.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-2.htm
deleted file mode 100644
index cbe83ce..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-2.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      JDT actions
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      JDT actions
-    </h1>
-    <p>
-      JDT actions are available from
-    </p>
-    <ul>
-      <li>
-        Menu bar
-      </li>
-      <li>
-        Toolbar
-      </li>
-      <li>
-        Context menus in views
-      </li>
-    </ul>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/concepts-1.htm">Java Development Tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="ref-152.htm">Frequently Asked Questions on JDT</a><br>
-       <a href="ref-155.htm">JDT Glossary</a><br>
-       <a href="../reference/ref-menu-file.htm">File actions</a><br>
-       <a href="../reference/ref-menu-edit.htm">Edit actions</a><br>
-       <a href="../reference/ref-menu-source.htm">Source actions</a><br>
-       <a href="../reference/ref-menu-refactor.htm">Refactor actions</a><br>
-       <a href="../reference/ref-menu-navigate.htm">Navigate actions</a><br>
-       <a href="../reference/ref-menu-search.htm">Search actions</a><br>
-       <a href="../reference/ref-menu-project.htm">Project actions</a><br>
-       <a href="../reference/ref-149.htm">Run actions</a><br>
-       <a href="../reference/ref-3.htm">Java Toolbar actions</a><br>
-       <a href="../reference/ref-java-editor.htm">Java Editor actions</a><br>
-       <a href="../reference/ref-4.htm">Run and Debug actions</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-21.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-21.htm
deleted file mode 100644
index 9e22182..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-21.htm
+++ /dev/null

@@ -1,516 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <title>
-      Java editor
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Java editor
-    </h1>
-    <p>
-      The following Java editor preferences can be set on this page and its sub-pages.
-    </p>
-    <ul>
-      <li><a href="#appearance">Appearance and Navigation</a></li>
-      <li><a href="#codeassist">Code Assist</a></li>
-      <li><a href="#syntaxcoloring">Syntax Coloring</a></li>
-    </ul>
-    <p>
-      Note that some options that are generally applicable to text editors can be configured on the text editor preference page.
-    </p>
-    <h2 class="Head">
-      <a name="appearance">Appearance and Navigation</a>
-    </h2>
-    <p>
-      Java editor appearance and navigation options.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <caption>
-        Appearance and Navigation
-      </caption>
-      <thead>
-        <tr>
-          <th>Option</th>
-          <th>Description</th>
-          <th>Default</th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-          Smart caret positioning at line start and end
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, the <strong>Home</strong> and <strong>End</strong> commands jump to the first and last non whitespace character on a line.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              On
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-          Smart caret positioning in Java names (overrides platform behavior)
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, there are additional word boundaries inside <tt>|Camel|Case|</tt> Java names.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              On
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-          Report problems as you type
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, the editor marks errors and warnings as you type, even if you do not save the editor contents. The problems are updated after a short delay.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              On
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-          Highlight matching brackets
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, whenever the cursor is next to a parenthesis, bracket or curly braces, its opening or closing counter part is highlighted.
-            </p>
-            <p>
-              The color of the bracket highlight is specified with <strong>Appearance color options</strong>.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              On
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-          Light bulb for quick assists
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, a <img src="../images/org.eclipse.jdt.ui/obj16/quickassist_obj.png" alt="light bulb">  shows up in the vertical ruler whenever a <strong>quick assist</strong> is available. See the <a href="../concepts/cquickassists.htm">quick assist section</a> for a list of the available assists.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Off
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            Appearance color options
-          </td>
-          <td valign="top">
-            <p>
-              The colors of various Java editor appearance features are specified here.
-            </p>
-            <dl>
-              <dt>Matching brackets highlight</dt>
-              <dd>The color of brackets highlight.</dd>
-
-              <dt>Find scope</dt>
-              <dd>The color of find scope.</dd>
-              <dt>Completion proposal background</dt>
-              <dd>The background color of the completion proposal window</dd>
-            	
-              <dt>Completion proposal foreground</dt>
-              <dd>The foreground color of the completion proposal window</dd>
-            
-              <dt>Method parameter background</dt>
-              <dd>The background color of the parameter window</dd>
-            	
-              <dt>Method parameter foreground</dt>
-              <dd>The foreground color of the parameter window</dd>
-            
-              <dt>Completion overwrite background</dt>
-              <dd>The background color of the completion overwrite window</dd>
-           		
-           	  <dt>Completion overwrite foreground</dt>
-              <dd>The foreground color of the completion overwrite window</dd>
-            </dl>
-          </td>
-          <td valign="top">
-            <p>
-              default colors
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <h2 class="Head">
-      <a name="codeassist">Code assist</a>
-    </h2>
-    <p>
-      Configures <strong>Code Assist</strong> behavior.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <caption>
-        Code Assist
-      </caption>
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-          <th>
-            <p>
-              Default
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            Completion inserts/Completion overwrites
-          </td>
-          <td valign="top">
-            <p>
-              If <strong>Completion inserts</strong> is on, the completion text is inserted at the caret position,
-              so it never overwrites any existing text.
-              <br>
-              If <strong>Completion overwrites</strong> is on, the completion text replaces the characters
-              following the caret position until the end of the word.
-            </p>
-            <p>
-            Note that pressing <strong>Ctrl</strong> when applying a completion proposal toggles between
-            the two insertion modes.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Completion inserts
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            Insert single proposals automatically
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, code assist will choose and insert automatically single proposals.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              On
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            Insert common prefixes automatically
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, code assist will automatically insert the common prefix of all possible completions similar
-              to unix shell expansion. This can be used repeatedly, even while the code assist window is being
-              displayed.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Off
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            Automatically add import instead of qualified name
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, type proposals which are in other packages will invoke the addition of the corresponding import declaration. Otherwise, the type will be inserted fully
-              qualified.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              On
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            Fill argument names on completion
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, code assist will add the argument names when completing a method or generic type.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Off
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            Guess filled method arguments
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, code assist will try to guess method parameters from the context where a method proposal is inserted.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Off
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            Present proposals in alphabetical order
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, the proposals are sorted in alphabetical order.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Off
-            </p>
-          </td>
-        </tr>
-         <tr>
-          <td valign="top">
-            Hide proposals not visible in the invocation context
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, the Java element proposals are limited by the rules of visibility. For example, private field proposals of other classes would not be displayed.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              On
-            </p>
-          </td>
-        </tr>
-         <tr>
-          <td valign="top">
-            Hide forbidden references
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, references to Java elements forbidden by access rules are not displayed.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              On
-            </p>
-          </td>
-        </tr>
-         <tr>
-          <td valign="top">
-            Hide discouraged references
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, references to Java elements discouraged by access rules are not displayed.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Off
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            Enable auto activation
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, code assist can be invoked automatically.
-            </p>
-            <p>
-              The condition for automatic invocation is specified with the preferences <strong>Auto activation delay</strong>, <strong>Auto activation triggers for Java</strong>
-              and <strong>Auto activation triggers for Javadoc</strong>.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              On
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            Auto activation delay
-          </td>
-          <td valign="top">
-            <p>
-              If the time starting when an auto activation trigger character is encountered until a new character is typed exceeds the auto activation delay, code assist is
-              invoked.
-            </p>
-          </td>
-          <td valign="top">
-            200
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            Auto activation triggers for Java
-          </td>
-          <td valign="top">
-            <p>
-              If one of the trigger characters is typed inside Java source code (but not inside a Javadoc comment) and no other character is typed before the auto activation delay
-              times out, the code assist is invoked.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              '.'
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            Auto activation triggers for Javadoc
-          </td>
-          <td valign="top">
-            <p>
-              If one of the trigger characters is typed inside a Java doc and no other character is typed before the auto activation delay times out, the code assist is invoked.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              '@#'
-            </p>
-          </td>
-        </tr>
-        
-      </tbody>
-    </table>
-
-    <h2 class="Head">
-      <a name="syntaxcoloring">Syntax Coloring</a>
-    </h2>
-    <p>
-      <strong>Syntax Coloring</strong> specifies how Java source code is rendered. Note that general 
-      text editor settings such as the background color can be configured on the general 'Text Editors' preference pages. Fonts
-      may be configured on the general 'Colors and Fonts' preference page.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <caption>
-        Syntax Coloring
-      </caption>
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-          <th>
-            <p>
-              Default
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            Element
-          </td>
-          <td valign="top">
-            <p>
-              Each category (<strong>Java</strong>, <strong>Javadoc</strong> and <strong>Comments</strong>)
-              contains a list of language elements that may be rendered with its own color and style.
-            </p>
-            <p>
-            Note that some semantic highlighting options can be disabled by the user in order to
-            ensure editor performance on low-end systems.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              default colors and styles
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            Preview
-          </td>
-          <td valign="top">
-            <p>
-              Displays the preview of a Java source code respecting the current colors and styles.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              n/a
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-7.htm">Java Editor</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-54.htm">Using the Java editor</a>
-    </p>
-         <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-java-editor.htm">Java editor</a><br>
-      <a href="../reference/ref-17.htm">Code Formatter preferences</a><br>
-      <a href="../reference/ref-view-outline.htm">Java outline</a><br>
-      <a href="../reference/ref-143.htm">Java Content Assist</a><br>
-      <a href="../reference/ref-java-editor-quickfix.htm">Quick Fix</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-22.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-22.htm
deleted file mode 100644
index dc0493a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-22.htm
+++ /dev/null

@@ -1,251 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Organize Imports
-    </title>
-  </head>
-  <body>
-    <h1>
-      Organize Imports
-    </h1>
-    <p>
-      The following preferences define how the Organize Imports command generates the import statements in a compilation unit.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5">
-      <caption>
-        Organize Imports Preferences
-      </caption>
-      <thead>
-        <tr>
-          <th rowspan="1" colspan="1">
-            <p>
-              Option
-            </p>
-          </th>
-          <th rowspan="1" colspan="1">
-            <p>
-              Description
-            </p>
-          </th>
-          <th rowspan="1" colspan="1">
-            <p>
-              Default
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Import order list
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              This list of prefixes shows the sequential order for packages imported into a Java compilation unit. Each entry defines a block. Different blocks are separated by a
-              spacer line.
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              java<br>
-              javax<br>
-              org<br>
-              com
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              New...
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Adds a package name prefix to the import order list. In the resulting dialog, type a package name or package name prefix.
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              n/a
-            </p>
-          </td>
-        </tr>
-         <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              New Static...
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Adds a package name prefix to the import order list. In the resulting dialog, type a package name or package name prefix.
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              n/a
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Edit...
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Change the name of an existing package name prefix. In the resulting dialog, type a package name or package name prefix.
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              n/a
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Remove
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Removes a package name prefix from the import order list.
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              n/a
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Up
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Moves the selected package name prefix up in the import order list.
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              n/a
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Down
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Moves the selected package name prefix down in the import order list.
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              n/a
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Import...
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Load a list of package name prefixes from a file.
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              n/a
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Export...
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Save the list of package name prefixes to a file.
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              n/a
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Number of imports needed for .*
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              The number of fully-qualified import statements that are allowed from the same package before <em>&lt;package&gt;.*</em> is used.
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              99
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Do not create imports for types starting with a lower case letter
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              If enabled, types starting with a lowercase letter are not imported.
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              On
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-58.htm">Managing import statements</a><br>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-	</p>
-	<p>
-      <a href="../reference/ref-menu-source.htm">Source actions</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-24.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-24.htm
deleted file mode 100644
index b3ba1b5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-24.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Views and editors
-    </title>
-  </head>
-  <body>
-    <h1>
-      Views and editors
-    </h1>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-7.htm">Java editor</a><br>
-       <a href="../concepts/concepts-6.htm">Java views<br>
-      </a> <a href="../concepts/concepts-1.htm">Java Development Tools (JDT)</a> <a href="../concepts/concepts-6.htm"><br>
-      <br>
-      </a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-consoleAppearance.htm">Changing the appearance of the console view</a><br>
-       <a href="../tasks/tasks-38.htm">Changing the appearance of the Hierarchy view</a><br>
-       <a href="../tasks/tasks-73.htm">Opening an editor for a selected element</a><br>
-       <a href="../tasks/tasks-76.htm">Opening an editor on a type</a><br>
-       <a href="../tasks/tasks-65.htm">Using content/code assist</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <p>
-      <a href="../reference/ref-java-editor.htm">Java editor actions</a><br>
-       <a href="../reference/ref-35.htm">Breakpoints view</a><br>
-       <a href="../reference/ref-45.htm">Console view</a><br>
-       <a href="../reference/ref-51.htm">Debug view</a><br>
-       <a href="../reference/ref-52.htm">Display view</a><br>
-       <a href="../reference/ref-56.htm">Expressions view</a><br>
-       <a href="../reference/ref-view-outline.htm">Java outline</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer view</a><br>
-       <a href="../reference/ref-type-hierarchy.htm">Type Hierarchy view</a><br>
-       <a href="../reference/ref-74.htm">Variables view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-3.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-3.htm
deleted file mode 100644
index afd3e00..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-3.htm
+++ /dev/null

@@ -1,220 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Java toolbar actions
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Java toolbar actions
-    </h1>
-    <br>
-     <br>
-     
-    <table border="1" cellspacing="0" cellpadding="5">
-      <caption>
-        Java Actions<br>
-      </caption>
-      <tbody>
-        <tr>
-          <th>
-            <p>
-              Toolbar Button
-            </p>
-          </th>
-          <th>
-            <p>
-              Command
-            </p>
-          </th>
-          <th>
-            Description
-          </th>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <img src="../images/org.eclipse.jdt.ui/etool16/newjprj_wiz.png" alt="Create a Java Project"  align="center">
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Create a Java Project
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              This command helps you create a new Java project.
-            </p>
-            <br>
-             <a href="ref-121.htm">See New Java Project Wizard</a>
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <img src="../images/org.eclipse.jdt.ui/etool16/newpack_wiz.png" alt="Create a Java Package"  align="center">
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Create a Java Package
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              This command helps you create a new Java package.
-            </p>
-            <br>
-             <a href="ref-125.htm">See New Java Package Wizard</a>
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <img src="../images/org.eclipse.jdt.ui/etool16/newclass_wiz.png" alt="Create a Java Class"  align="center">
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Create a Java Class
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              This command helps you create a new Java class.
-            </p>
-            <br>
-             <a href="ref-126.htm">See New Java Class Wizard</a>
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <img src="../images/org.eclipse.jdt.ui/etool16/newenum_wiz.png" alt="Create a Java Enum"  align="center">
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Create a Java enum
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              This command helps you create a new Java enum.
-            </p>
-            <br>
-             <a href="ref-126b.htm">See New Java Enum Wizard</a>
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <img src="../images/org.eclipse.jdt.ui/etool16/newint_wiz.png" alt="Create a Java Interface"  align="center">
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Create a Java Interface
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              This command helps you create a new Java interface.
-            </p>
-            <br>
-             <a href="ref-127.htm">See New Java Interface Wizard</a>
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <img src="../images/org.eclipse.jdt.ui/etool16/newannotation_wiz.png" alt="Create a Java annotation"  align="center">
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Create a Java annotation
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              This command helps you create a new Java annotation.
-            </p>
-            <br>
-             <a href="ref-127b.htm">See New Java Annotation Wizard</a>
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <img src="../images/org.eclipse.jdt.ui/etool16/newsbook_wiz.png" alt="Create a Scrapbook Page"  align="center">
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Create a Scrapbook Page
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              This command helps you create a new Java scrapbook page for experimenting with Java expressions.
-            </p>
-            <br>
-             <a href="ref-129.htm">See New Java Scrapbook Page Wizard</a>
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <img src="../images/org.eclipse.jdt.ui/etool16/opentype.png" alt="Open Type"  align="center">
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Open Type
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              This command allows you to browse the workspace for a type to open in the defined default Java editor. You can optionally choose to display the type simultaneously
-              in the Hierarchy view.
-            </p>
-            <dl>
-              <dt>
-                <strong>Select a type to open</strong>:
-              </dt>
-              <dd>
-				In this field, type the first few characters of the type you want to open in an editor. You may use wildcards as needed
-        (&quot;<em>?</em>&quot; for any character, &quot;<em>*</em>&quot; for any string, and &quot;<em>TZ</em>&quot; for types containing &quot;<em>T</em>&quot; and &quot;<em>Z</em>&quot; as upper-case letters in camel-case notation, <code>e.g. java.util.TimeZone</code>).
-              </dd>
-              <dt>
-                <strong>Matching Types</strong>:
-              </dt>
-              <dd>
-                This list displays matches for the expression you type in the <strong>Select a type to open</strong> field.
-              </dd>
-            </dl>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <br>
-       <img  src="../images/ngrelc.png" alt="Related concepts" border="0">
-    </p>
-    <p>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelt.png" alt="Related tasks">
-    </p>
-    <a href="../tasks/tasks-11.htm">Creating Java elements</a> <br>
-     <a href="../tasks/tasks-76.htm">Opening an editor on a type</a> 
-    <p>
-       <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="ref-121.htm">New Java Project wizard</a><br>
-       <a href="ref-125.htm">New Java Package wizard</a><br>
-       <a href="ref-126.htm">New Java Class wizard</a><br>
-       <a href="ref-126b.htm">New Java Enum wizard</a><br>
-       <a href="ref-127.htm">New Java Interface wizard</a><br>
-       <a href="ref-127b.htm">New Java Annotation wizard</a><br>
-       <a href="ref-129.htm">New Java Scrapbook Page wizard</a><br>
-       <a href="../reference/ref-24.htm">Views and editors</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-34.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-34.htm
deleted file mode 100644
index d59d149..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-34.htm
+++ /dev/null

@@ -1,147 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Java scrapbook page
-    </title>
-  </head>
-  <body>
-    <h1>
-      Java scrapbook page
-    </h1>
-    <p>
-      The scrapbook allows Java expressions to be run, inspected, and displayed, under the control of the debugger.
-    </p>
-    <p>
-      <strong>Note:</strong> Content assist (such as code assist) is available on scrapbook pages.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5">
-      <caption>
-        Java Scrapbook page buttons
-      </caption>
-      <thead>
-        <tr>
-          <th rowspan="1" colspan="1">
-            <p>
-              Command
-            </p>
-          </th>
-          <th rowspan="1" colspan="1">
-            <p>
-              Name
-            </p>
-          </th>
-          <th rowspan="1" colspan="1">
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <img src="../images/org.eclipse.jdt.debug.ui/etool16/run_sbook.png" align="baseline"  alt="Run Snippet button">
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run Snippet
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Running an expression evaluates an expression but does not display a result.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <img src="../images/org.eclipse.jdt.debug.ui/etool16/disp_sbook.png" align="baseline"  alt="Display button">
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Display
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Displaying shows the result of evaluating an expression as a string in the scrapbook editor.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <img src="../images/org.eclipse.jdt.debug.ui/etool16/insp_sbook.png" align="baseline"  alt="Inspect button">
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Inspect
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Inspecting shows the result of evaluating an expression in the Expressions view.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <img src="../images/org.eclipse.jdt.debug.ui/etool16/term_sbook.png" align="baseline"  alt="Terminate button">
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Terminate
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              This command terminates the Java VM that is used to evaluate expressions.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <img src="../images/org.eclipse.jdt.ui/obj16/impc_obj.png" align="baseline"  alt="Set the import Declarations button">
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Set the Import Declarations
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              This commands sets the import declarations to be used for the context of evaluating the code
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-11.htm">Scrapbook</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-149.htm">Creating a Java scrapbook page</a><br>
-       <a href="../tasks/tasks-151.htm">Displaying the result of evaluating an expression</a><br>
-       <a href="../tasks/tasks-150.htm">Inspecting the result of evaluating an expression</a><br>
-       <a href="../tasks/tasks-152.htm">Executing an expression</a>
-    </p>
-    <p>
-       <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-129.htm">New Java Scrapbook Page wizard</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-35.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-35.htm
deleted file mode 100644
index e02ca7c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-35.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Breakpoints view
-    </title>
-  </head>
-  <body>
-    <h1>
-      Breakpoints view
-    </h1>
-    <p>
-      The Breakpoints view lists all the breakpoints you have set in the workbench projects. You can double-click a breakpoint to display its location in the editor. In this view,
-      you can also enable or disable breakpoints, delete them, or add new ones.
-    </p>
-    <p>
-      This view also lists Java exception breakpoints, which suspend execution at the point where the exception is thrown. You can add or remove exceptions.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/cbrkpnts.htm">Breakpoints</a><br>
-       <a href="../concepts/concepts-6.htm">Java views</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-144.htm">Adding breakpoints</a><br>
-       <a href="../tasks/tasks-146.htm">Applying hit counts</a><br>
-       <a href="../tasks/tasks-147.htm">Catching Java exceptions</a><br>
-       <a href="../tasks/tasks-144a.htm">Removing breakpoints</a><br>
-       <a href="../tasks/tasks-144b.htm">Enabling and disabling breakpoints</a><br>
-       <a href="../tasks/tasks-144c.htm">Managing conditional breakpoints</a><br>
-       <a href="../tasks/tasks-145.htm">Setting method breakpoints</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <p>
-      <a href="../reference/ref-24.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-36.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-36.htm
deleted file mode 100644
index c0f54dd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-36.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Remove selected breakpoint
-    </title>
-  </head>
-  <body>
-    <h1>
-      Remove selected breakpoint
-    </h1>
-    <p>
-      This command removes the selected breakpoint(s).
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-37.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-37.htm
deleted file mode 100644
index a6ace72..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-37.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Remove all breakpoints
-    </title>
-  </head>
-  <body>
-    <h1>
-      Remove all breakpoints
-    </h1>
-    <p>
-      This command removes all breakpoints in the workbench.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-38.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-38.htm
deleted file mode 100644
index 35c5195..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-38.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Go to file for breakpoint
-    </title>
-  </head>
-  <body>
-    <h1>
-      Go to file for breakpoint
-    </h1>
-    <p>
-      If the resource containing the selected breakpoint is not open and/or active, this command causes the file to be opened and made active, focusing on the line with which the
-      breakpoint is associated.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/cbrkpnts.htm">Breakpoints</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-      <p>
-    	<a href="../tasks/tasks-144.htm">Adding breakpoints</a><br>
-    	<a href="../tasks/tasks-144a.htm">Removing breakpoints</a><br>
-      	<a href="../tasks/tasks-130.htm">Launching a Java program</a><br>
-       <a href="../tasks/tasks-126.htm">Running and debugging</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-39.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-39.htm
deleted file mode 100644
index 726320f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-39.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Show qualified names
-    </title>
-  </head>
-  <body>
-    <h1>
-      Show qualified names
-    </h1>
-    <p>
-      This option can be toggled to show or hide qualified names.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-4.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-4.htm
deleted file mode 100644
index 537deed..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-4.htm
+++ /dev/null

@@ -1,390 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Run and debug actions
-    </title>
-  </head>
-  <body>
-    <h1>
-      Run and debug actions
-    </h1>
-    <table border="1" cellspacing="0" cellpadding="5">
-      <caption>
-        Run and Debug Actions
-      </caption>
-      <thead>
-        <tr>
-          <th rowspan="1" colspan="1">
-            <p>
-              Toolbar Button
-            </p>
-          </th>
-          <th rowspan="1" colspan="1">
-            <p>
-              Command
-            </p>
-          </th>
-          <th rowspan="1" colspan="1">
-            Description
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <img src="../images/org.eclipse.debug.ui/etool16/run_exc.png" align="baseline"  alt="Run button">
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              This command re-launches the most recently launched application.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <img src="../images/org.eclipse.debug.ui/etool16/debug_exc.png" align="baseline"  alt="Debug button">
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Debug
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              This command re-launches the most recently launched application under debugger control.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run Menu
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Debug Last Launched
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              This command allows you to quickly repeat the most recent launch in debug mode (if that mode is supported).
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run Menu
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run Last Launched
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              This command allows you to quickly repeat the most recent launch in run mode (if that mode is supported).
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run Menu
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run History
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Presents a sub menu of the recent history of launch configurations launched in run mode
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run Menu
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run As
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Presents a sub menu of registered run launch shortcuts. Launch shortcuts provide support for workbench or active editor selection sensitive launching.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run Menu
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run...
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              This command realizes the launch configuration dialog to manage run mode launch configurations.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run Menu
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Debug History
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Presents a sub menu of the recent history of launch configurations launched in debug mode.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run Menu
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Debug As
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Presents a sub menu of registered debug launch shortcuts. Launch shortcuts provide support for workbench or active editor selection sensitive launching.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run Menu
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Debug...
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              This command realizes the launch configuration dialog to manage debug mode launch configurations.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run Menu
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Various step commands
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              These commands allow you to step through code being debugged.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run Menu
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Inspect
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              When a thread suspends, this command uses the Expressions view to show the result of inspecting the selected expression or variable in the context of a stack frame
-              or variable in that thread.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run Menu
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Display
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              When a thread suspends, this command uses the Display view to show the result of evaluating the selected expression in the context of a stack frame or variable in
-              that thread. If the current active part is a Java Snippet Editor, the result is displayed there.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run Menu
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run Snippet
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Within the context of the Java snippet editor, this command allows you to evaluate an expression but does not display a result.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run Menu
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run to Line
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              When a thread is suspended, it is possible to resume execution until a specified line is executed. This is a convenient way to suspend execution at a line without
-              setting a breakpoint.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run Menu
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            
-      <p> Toggle Line Breakpoint </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              This command allows you to add or remove a Java line breakpoint at the current selected line in the active Java editor.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run Menu
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Add Java Exception Breakpoint
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              This command allows you to create an exception breakpoint. It is possible to suspend the execution of thread or VM when an exception is thrown by specifying an
-              exception breakpoint. Execution can be suspended at locations where the exception is uncaught, caught, or both.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run Menu
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            
-      <p> Toggle Method Breakpoint </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              This command allows you to add or remove a method breakpoint for the current binary method. The binary method can be selected in source of a Java class file editor,
-              or be selected in any other view (such as the Outline view).
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run Menu
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            
-      <p> Toggle Watchpoint </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              This command allows you to add or remove a field watchpoint for the current Java field. The field can be selected in the source of a Java editor, or be selected in
-              any other view (such as the Outline view).
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-10.htm">Debugger</a><br>
-       <a href="../concepts/clocdbug.htm">Local Debugging</a><br>
-       <a href="../concepts/cremdbug.htm">Remote Debugging</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-      <p>
-       <a href="../tasks/tasks-126.htm">Running and Debugging</a><br>
-       <a href="../tasks/tasks-141.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-       <a href="../tasks/tasks-144.htm">Line breakpoints</a><br>
-       <a href="../tasks/tasks-145.htm">Setting method breakpoints</a><br>
-       <a href="../tasks/tasks-147.htm">Catching exceptions</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related Reference" >
-    </p>
-    <p>
-      <a href="ref-51.htm">Debug View</a><br>
-       <a href="../reference/ref-11.htm">Debug Preferences</a><br>
-       <a href="../reference/ref-4.htm">Run and Debug actions</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-40.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-40.htm
deleted file mode 100644
index 3b321fb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-40.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Add Java exception breakpoint
-    </title>
-  </head>
-  <body>
-    <h1>
-      Add Java exception breakpoint
-    </h1>
-    <p>
-      This command allows you to add a Java exception breakpoint. In the resulting dialog:
-    </p>
-    <ul>
-      <li>
-        In the <strong>Choose an Exception</strong> field, type a string that is contained in the name of the exception you want to add. You can use wildcards as needed
-        (&quot;<em>*</em> &quot; for any string and &quot;<em>?</em> &quot; for any character).
-      </li>
-      <li>
-        In the exceptions list, select the exception you want to add.
-      </li>
-      <li>
-        Check or clear the <strong>Caught</strong> and <strong>Uncaught</strong> checkboxes as needed to indicate on which exception type you want to suspend the program.
-      </li>
-    </ul>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/cbrkpnts.htm">Breakpoints</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-    </p>
-    <a href="../tasks/tasks-147.htm">Catching Java exceptions</a><br>
-    	<a href="../tasks/tasks-144.htm">Adding breakpoints</a><br>
-    	<a href="../tasks/tasks-144a.htm">Removing breakpoints</a><br>
-	    <a href="../tasks/tasks-130.htm">Launching a Java program</a> <br>
-     <a href="../tasks/tasks-126.htm">Running and debugging</a> 
-    <p>
-      <br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-41.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-41.htm
deleted file mode 100644
index dc7d11d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-41.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Uncaught
-    </title>
-  </head>
-  <body>
-    <h1>
-      Uncaught
-    </h1>
-    <p>
-      When this option is turned on, execution stops when the exception is thrown and is not caught in the program.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ></p>
-      <p>
-       <a href="../concepts/cbrkpnts.htm">Breakpoints</a>
-    </p>
-    <p>
-       <img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-       <p>
-       <a href="../tasks/tasks-147.htm">Catching exceptions</a><br>
-    	<a href="../tasks/tasks-144.htm">Adding breakpoints</a><br>
-    	<a href="../tasks/tasks-144a.htm">Removing breakpoints</a><br>
-        <a href="../tasks/tasks-130.htm">Launching a Java program</a><br>
-        <a href="../tasks/tasks-126.htm">Running and debugging</a><br>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <p>
-      <a href="../reference/ref-40.htm">Add Java exception breakpoint</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-42.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-42.htm
deleted file mode 100644
index 86e588e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-42.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Caught
-    </title>
-  </head>
-  <body>
-    <h1>
-      Caught
-    </h1>
-    <p>
-      When this option is turned on, execution stops when the exception is thrown and is caught in the program.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ></p>
-      <p>
-       <a href="../concepts/cbrkpnts.htm">Breakpoints</a>
-    </p>
-	<p>
-     <img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-     <p>
-     <a href="../tasks/tasks-147.htm">Catching exceptions</a><br>
-    	<a href="../tasks/tasks-144.htm">Adding breakpoints</a><br>
-    	<a href="../tasks/tasks-144a.htm">Removing breakpoints</a><br>
-	    <a href="../tasks/tasks-130.htm">Launching a Java program</a> <br>
-     	<a href="../tasks/tasks-126.htm">Running and debugging</a> 
-    </p>
-    <p>
-       <img border="0" src="../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <p>
-      <a href="../reference/ref-40.htm">Add Java exception breakpoint</a>
-    </p>
-
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-43.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-43.htm
deleted file mode 100644
index 1f4a582..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-43.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Hit count
-    </title>
-  </head>
-  <body>
-    <h1>
-      Hit count
-    </h1>
-    <p>
-      This option sets the hit count for the selected breakpoint. The hit count keeps track of the number of times that the breakpoint is hit. When the breakpoint is hit for the
-      <em>n</em>th time, the thread that hit the breakpoint suspends. The breakpoint is disabled until either it is re-enabled or its hit count is changed.<br>
-      <br>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ></p>
-      <p>
-       <a href="../concepts/cbrkpnts.htm">Breakpoints</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-    </p>
-    <p>
-      	<a href="../tasks/tasks-144.htm">Adding breakpoints</a><br>
-    	<a href="../tasks/tasks-144a.htm">Removing breakpoints</a><br>
-	    <a href="../tasks/tasks-130.htm">Launching a Java program</a> <br>
-     <a href="../tasks/tasks-126.htm">Running and debugging</a> 
-    </p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-44.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-44.htm
deleted file mode 100644
index 3fde9e4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-44.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Enable
-    </title>
-  </head>
-  <body>
-    <h1>
-      Enable
-    </h1>
-    <p>
-      This command enables the selected breakpoints.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-44a.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-44a.htm
deleted file mode 100644
index e0f5600..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-44a.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Disable
-    </title>
-  </head>
-  <body>
-    <h1>
-      Disable
-    </h1>
-    <p>
-      This command disables the selected breakpoints. A disabled breakpoint does not cause the execution of a program to be suspended.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-45.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-45.htm
deleted file mode 100644
index aa6663e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-45.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Console view
-    </title>
-  </head>
-  <body>
-    <h1>
-      Console view
-    </h1>
-    
-<p> This view shows the output of a process and allows you to provide keyboard 
-  input to a process. The console shows three different kinds of text, each in 
-  a different color. </p>
-    <ul>
-      <li>
-        Standard output
-      </li>
-      <li>
-        Standard error
-      </li>
-      <li>
-        Standard input
-      </li>
-    </ul>
-    <p>
-      You can choose the different colors for these kinds of text on the preferences pages (<strong>Window</strong> &gt; <strong>Preferences</strong> &gt; <strong>Debug</strong>
-      &gt; <strong>Console</strong>).
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-6.htm">Java views</a><br>
-       <a href="../concepts/concepts-5.htm">Java perspectives</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-consoleAppearance.htm">Changing the appearance of the console view</a><br>
-       <a href="../tasks/tasks-136.htm">Stepping through the execution of a program</a>
-    </p>
-    <p>
-      <a href="../reference/ref-4.htm">Run menu</a> <a href="../reference/ref-35.htm">Breakpoints view</a> <a href="../reference/ref-24.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-45b.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-45b.htm
deleted file mode 100644
index 220d1f5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-45b.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Terminate
-    </title>
-  </head>
-  <body>
-    <h1>
-      Terminate
-    </h1>
-    <p>
-      This command terminates the process that is currently associated with the console
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-46.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-46.htm
deleted file mode 100644
index e01ded1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-46.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Clear
-    </title>
-  </head>
-  <body>
-    <h1>
-      Clear
-    </h1>
-    <p>
-      This command clears all content in the Console view.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-47.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-47.htm
deleted file mode 100644
index 7d9ec7f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-47.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Copy
-    </title>
-  </head>
-  <body>
-    <h1>
-      Copy
-    </h1>
-    <p>
-      This command copies all selected text from the Console view onto the clipboard.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-48.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-48.htm
deleted file mode 100644
index 607e815..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-48.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Select all
-    </title>
-  </head>
-  <body>
-    <h1>
-      Select all
-    </h1>
-    <p>
-      This command selects all text in the current pane of the Console view.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-49.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-49.htm
deleted file mode 100644
index d6a4cc9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-49.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Find/Replace
-    </title>
-  </head>
-  <body>
-    <h1>
-      Find/Replace
-    </h1>
-    <p>
-      This command allows you to search for an expression and replace it with another expression.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-50.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-50.htm
deleted file mode 100644
index f509417..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-50.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Go to line
-    </title>
-  </head>
-  <body>
-    <h1>
-      Go to line
-    </h1>
-    <p>
-      This command allows you to go to the specified line in the console. The line is specified in the resulting dialog.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-51.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-51.htm
deleted file mode 100644
index d094aa3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-51.htm
+++ /dev/null

@@ -1,271 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Debug view
-    </title>
-  </head>
-  <body>
-    <h1>
-      Debug view
-    </h1>
-    <p>
-      This view allows you to manage the debugging or running of a program in the workbench. It displays the stack frame for the suspended threads for each target you are
-      debugging. Each thread in your program appears as a node in the tree. It displays the process for each target you are running.
-    </p>
-    <p>
-      If the thread is suspended, its stack frames are shown as child elements.
-    </p>
-    
-<table border="1" cellspacing="0" cellpadding="5" width="697">
-  <caption> Debug View Commands </caption>
-  <thead> 
-  <tr> 
-    <th rowspan="1" colspan="1" width="78"> 
-      <p> Command </p>
-    </th>
-    <th rowspan="1" colspan="1" width="111"> 
-      <p> Name </p>
-    </th>
-    <th rowspan="1" colspan="1" width="494"> 
-      <p> Description </p>
-    </th>
-  </tr>
-  </thead> <tbody> 
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left" width="78"> <img src="../images/org.eclipse.debug.ui/elcl16/resume_co.png" align="baseline"  alt="Resume button"> 
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="111"> 
-      <p> Resume </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="494"> 
-      <p> This command resumes a suspended thread. </p>
-    </td>
-  </tr>
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left" width="78"> <img src="../images/org.eclipse.debug.ui/elcl16/suspend_co.png" align="baseline"  alt="Suspend button"> 
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="111"> 
-      <p> Suspend </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="494"> 
-      <p> This command suspends the selected thread of a target so that you can 
-        browse or modify code, inspect data, step, and so on. </p>
-    </td>
-  </tr>
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left" width="78"> <img src="../images/org.eclipse.debug.ui/elcl16/terminate_co.png" align="baseline"  alt="Terminate button"> 
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="111"> 
-      <p> Terminate </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="494"> 
-      <p> This command terminates the selected debug target. </p>
-    </td>
-  </tr>
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left" width="78"> 
-      <p> <img src="../images/org.eclipse.debug.ui/elcl16/terminate_rem_co.png" align="baseline"  alt="Terminate &amp; Remove command in context menu"><br>
-        Context menu only </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="111"> 
-      <p> Terminate &amp; Remove </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="494"> 
-      <p> This command terminates the selected debug target and removes it from 
-        the view. </p>
-    </td>
-  </tr>
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left" width="78"> 
-      <p> <img src="../images/org.eclipse.debug.ui/elcl16/terminate_all_co.png" align="baseline"  alt="Terminate All command in context menu"><br>
-        Context menu only </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="111"> 
-      <p> Terminate All </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="494"> 
-      <p> This command terminates all active launches in the view. </p>
-    </td>
-  </tr>
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left" width="78"> <img src="../images/org.eclipse.debug.ui/elcl16/disconnect_co.png" align="baseline"  alt="Disconnect button"> 
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="111"> 
-      <p> Disconnect </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="494"> 
-      <p> This command disconnects the debugger from the selected debug target 
-        when debugging remotely. </p>
-    </td>
-  </tr>
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left" width="78"> <img src="../images/org.eclipse.debug.ui/elcl16/rem_all_co.png" align="baseline"  alt="Remove All Terminated Launches button"> 
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="111"> 
-      <p> Remove All Terminated Launches </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="494"> 
-      <p> This command clears all terminated debug targets from the view display. 
-      </p>
-    </td>
-  </tr>
-  <tr> 
-    <td colspan="1" valign="top" align="left" width="78"><img src="../images/org.eclipse.debug.ui/elcl16/stepbystep_co.png" align="baseline"  alt="Step with Filters button"> 
-    </td>
-    <td colspan="1" valign="top" align="left" width="111">Use Step Filters</td>
-    <td colspan="1" valign="top" align="left" width="494">This command toggles 
-      step filters on/off. When on, all step functions apply step filters.</td>
-  </tr>
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left" width="78"> <img src="../images/org.eclipse.debug.ui/elcl16/stepinto_co.png" align="baseline"  alt="Step Into button"> 
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="111"> 
-      <p> Step Into </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="494"> 
-      <p> This command steps into the highlighted statement. </p>
-    </td>
-  </tr>
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left" width="78"> <img src="../images/org.eclipse.debug.ui/elcl16/stepover_co.png" align="baseline"  alt="Step Over button"> 
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="111"> 
-      <p> Step Over </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="494"> 
-      <p> This command steps over the highlighted statement. Execution will continue 
-        at the next line either in the same method or (if you are at the end of 
-        a method) it will continue in the method from which the current method 
-        was called. </p>
-      <p> The cursor jumps to the declaration of the method and selects this line. 
-      </p>
-    </td>
-  </tr>
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left" width="78"> <img src="../images/org.eclipse.debug.ui/elcl16/stepreturn_co.png" align="baseline"  alt="Run to Return button"> 
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="111"> 
-      <p> Run to Return </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="494"> 
-      <p> This command steps out of the current method. This option stops execution 
-        after exiting the current method. </p>
-    </td>
-  </tr>
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left" width="78"> <img src="../images/org.eclipse.jdt.debug.ui/obj16/package_obj.png" align="baseline"  alt="Show Qualified Names button"> 
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="111"> 
-      <p> Show Qualified Names </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="494"> 
-      <p> This option can be toggled to display or hide qualified names. </p>
-    </td>
-  </tr>
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left" width="78"> 
-      <p> <img src="../images/org.eclipse.debug.ui/elcl16/copy_edit_co.png" align="baseline"  alt="Copy Stack command in context menu"><br>
-        Context menu only </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="111"> 
-      <p> Copy Stack </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="494"> 
-      <p> This command copies the selected stack of suspended threads as well 
-        as the state of the running threads to the clipboard. </p>
-    </td>
-  </tr>
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left" width="78"> 
-      <p><img src="../images/org.eclipse.debug.ui/elcl16/drop_to_frame.png"  align="baseline" alt="Copy Stack command in context menu"> 
-      </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="111"> 
-      <p> Drop to Frame </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="494"> 
-      <p> This command lets you drop back and reenter a specified stack frame. 
-        This feature is similar to &quot;running backwards&quot; and restarting 
-        your program part-way through. </p>
-      <p> To drop back and reenter a specified stack frame, select the stack frame 
-        that you want to &quot;drop&quot; to, and select <strong>Drop to Frame</strong>. 
-      </p>
-      <p> Some caveats apply to this feature: </p>
-      <ul>
-        <li> You cannot drop past a native method on the stack. </li>
-        <li> Global data are unaffected and will retain their current values. 
-          For example, a static vector containing elements will not be cleared. 
-        </li>
-      </ul>
-      <em>Note: This command is only enabled if the underlying VM supports this 
-      feature.</em> </td>
-  </tr>
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left" width="78"> 
-      <p> <img src="../images/org.eclipse.debug.ui/elcl16/runlast_co.png" align="baseline"  alt="Relaunch command in context menu"><br>
-        Context menu only </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="111"> 
-      <p> Relaunch </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="494"> 
-      <p> This command re-launches the selected debug target. </p>
-    </td>
-  </tr>
-  <tr> 
-    <td rowspan="1" colspan="1" valign="top" align="left" width="78"> 
-      <p> Context menu only </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="111"> 
-      <p> Properties </p>
-    </td>
-    <td rowspan="1" colspan="1" valign="top" align="left" width="494"> 
-      <p> This command displays the properties of the selected launch. It also 
-        allows you to view the full command line for a selected process. </p>
-    </td>
-  </tr>
-  </tbody> 
-</table>
-    <p>&nbsp;
-      
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-10.htm">Debugger</a><br>
-       <a href="../concepts/concepts-6.htm">Java views</a><br>
-       <a href="../concepts/clocdbug.htm">Local debugging</a><br>
-       <a href="../concepts/cremdbug.htm">Remote debugging</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-       <a href="../tasks/tasks-141.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-       <a href="../tasks/tasks-142.htm">Disconnecting from a VM</a><br>
-       <a href="../tasks/tasks-130.htm">Launching a Java program</a><br>
-       <a href="../tasks/tasks-133.htm">Preparing to debug</a><br>
-       <a href="../tasks/tasks-135.htm">Resuming the execution of suspended threads</a><br>
-       <a href="../tasks/tasks-126.htm">Running and debugging</a><br>
-       <a href="../tasks/tasks-136.htm">Stepping through the execution of a program</a><br>
-       <a href="../tasks/tasks-134.htm">Suspending threads</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <p>
-      <a href="../reference/ref-11.htm">Debug preferences</a><br>
-       <a href="../reference/ref-4.htm">Run and debug actions</a><br>
-       <a href="../reference/ref-24.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-51a.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-51a.htm
deleted file mode 100644
index 81ba67c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-51a.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Open declared type
-    </title>
-  </head>
-  <body>
-    <h1>
-      Open declared type
-    </h1>
-    <p>
-      This command allows you open an editor on the declared type of the currently selected stack frame in the <strong>Debug view</strong>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-51b.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-51b.htm
deleted file mode 100644
index dd6490d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-51b.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Open receiving type
-    </title>
-  </head>
-  <body>
-    <h1>
-      Open receiving type
-    </h1>
-    <p>
-      This command allows you open an editor on the receiving type of the currently selected stack frame in the <strong>Debug view</strong>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-51c.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-51c.htm
deleted file mode 100644
index c057c35..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-51c.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Copy stack
-    </title>
-  </head>
-  <body>
-    <h1>
-      Copy stack
-    </h1>
-    <p>
-      This command allows you copy the labels of the currently selected element and its children in the <strong>Debug view</strong> to the system clipboard.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-51d.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-51d.htm
deleted file mode 100644
index 3a3fd97..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-51d.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Drop to frame
-    </title>
-  </head>
-  <body>
-    <h1>
-      Drop to frame
-    </h1>
-    <p>
-      This command allows you re-enter the currently stack frame in the <strong>Debug view</strong>.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-52.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-52.htm
deleted file mode 100644
index 747f714..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-52.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Display view
-    </title>
-  </head>
-  <body>
-    <h1>
-      Display view
-    </h1>
-    <p>
-      This view displays the result of evaluating an expression in the context of the current stack frame. You can evaluate and display a selection either from the editor or
-      directly from the Display view.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-6.htm">Java views</a><br>
-       <a href="../concepts/concepts-5.htm">Java perspectives</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-138.htm">Evaluating expressions</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <p>
-      <a href="../reference/ref-24.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-53.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-53.htm
deleted file mode 100644
index bf48f18..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-53.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Clear the display
-    </title>
-  </head>
-  <body>
-    <h1>
-      Clear the display
-    </h1>
-    <p>
-      This command clears the display view.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-54.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-54.htm
deleted file mode 100644
index 5568bad..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-54.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Display
-    </title>
-  </head>
-  <body>
-    <h1>
-      Display
-    </h1>
-    <p>
-      You can type an expression in the Display view and then use the <strong>Display</strong> command to display its value.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-55.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-55.htm
deleted file mode 100644
index 6567806..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-55.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Inspect
-    </title>
-  </head>
-  <body>
-    <h1>
-      Inspect
-    </h1>
-    <p>
-      You can type an expression in the Display view and then use the <strong>Inspect</strong> command to evaluate the expression and inspect the result in the Expressions view.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-56.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-56.htm
deleted file mode 100644
index 12fa3ea..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-56.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Expressions view
-    </title>
-  </head>
-  <body>
-    <h1>
-      Expressions view
-    </h1>
-    
-<p> Data can be inspected in the Expressions view. You can inspect data from a 
-  scrapbook page, a stack frame of a suspended thread, and other places. The Expressions 
-  view opens automatically when an item is added to the view. </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-6.htm">Java views</a><br>
-       <a href="../concepts/concepts-5.htm">Java perspectives</a><br>
-       <a href="../concepts/concepts-11.htm">Scrapbook</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-138.htm">Evaluating expressions</a><br>
-       <a href="../tasks/tasks-134.htm">Suspending threads</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <p>
-      <a href="../reference/ref-24.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-56a.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-56a.htm
deleted file mode 100644
index 9392c10..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-56a.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Select all
-    </title>
-  </head>
-  <body>
-    <h1>
-      Select all
-    </h1>
-    <p>
-      This command selects all expressions in the <strong>Expressions view</strong>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-56b.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-56b.htm
deleted file mode 100644
index 5bb2244..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-56b.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Copy variables
-    </title>
-  </head>
-  <body>
-    <h1>
-      Copy variables
-    </h1>
-    <p>
-      This command copies a text representation of all selected expressions and variables onto the clipboard.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-56c.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-56c.htm
deleted file mode 100644
index f9d121a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-56c.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Show detail pane
-    </title>
-  </head>
-  <body>
-    <h1>
-      Show detail pane
-    </h1>
-    <p>
-      This command toggles showing the detail pane for the <strong>Expressions view</strong>. The details pane shows the <em>toString</em> for selected objects. For primitive
-      variables, it shows the value.<br>
-       Code completion in the context of selected variable or the current stack frame is available as well. Evaluation can occur on expressions using <strong>Inspect</strong> and
-      <strong>Display</strong>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-138.htm">Evaluating expressions</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-56d.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-56d.htm
deleted file mode 100644
index 7c33515..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-56d.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Add/Remove watchpoint
-    </title>
-  </head>
-  <body>
-    <h1>
-      Add/Remove watchpoint
-    </h1>
-    <p>
-      This command allows you to add or remove a field watchpoint for the current selected variable in the <strong>Expressions</strong> view.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-56e.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-56e.htm
deleted file mode 100644
index 8ca5bd3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-56e.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Open declared type
-    </title>
-  </head>
-  <body>
-    <h1>
-      Open declared type
-    </h1>
-    <p>
-      This command allows you open an editor on the declared type of the currently selected variable in the <strong>Expressions view</strong>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-57.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-57.htm
deleted file mode 100644
index 80a4d5b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-57.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Show type names
-    </title>
-  </head>
-  <body>
-    <h1>
-      Show type names
-    </h1>
-    <p>
-      This option can be toggled to show or hide type names.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-58.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-58.htm
deleted file mode 100644
index 726320f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-58.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Show qualified names
-    </title>
-  </head>
-  <body>
-    <h1>
-      Show qualified names
-    </h1>
-    <p>
-      This option can be toggled to show or hide qualified names.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-59.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-59.htm
deleted file mode 100644
index 365ac6c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-59.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Remove selected expressions
-    </title>
-  </head>
-  <body>
-    <h1>
-      Remove selected expressions
-    </h1>
-    <p>
-      This command removes the selected expressions from the Expressions view.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-6.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-6.htm
deleted file mode 100644
index 0deb3dd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-6.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      JDT perspectives
-    </title>
-  </head>
-  <body>
-    <h1>
-      JDT perspectives
-    </h1>
-    <p>
-      Several predefined perspectives are included in the workbench by default.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-60.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-60.htm
deleted file mode 100644
index 5e0d6a3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-60.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Remove all expressions
-    </title>
-  </head>
-  <body>
-    <h1>
-      Remove all expressions
-    </h1>
-    <p>
-      This command removes all expressions from the <strong>Expressions</strong> view.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-62.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-62.htm
deleted file mode 100644
index e25eee5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-62.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Show static fields
-    </title>
-  </head>
-  <body>
-    <h1>
-      Show static fields
-    </h1>
-    <p>
-      This option can be toggled to show or hide static fields.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-63.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-63.htm
deleted file mode 100644
index c763ff7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-63.htm
+++ /dev/null

@@ -1,21 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Show constants
-    </title>
-  </head>
-  <body>
-    
-<h1> Show constants </h1>
-    
-<p> This option can be toggled to show or hide constants (static final fields). 
-</p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-64.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-64.htm
deleted file mode 100644
index 7897426..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-64.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Inspect
-    </title>
-  </head>
-  <body>
-    <h1>
-      Inspect
-    </h1>
-    <p>
-      This command causes the selected variables to be inspected.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-65.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-65.htm
deleted file mode 100644
index 44f3a99..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-65.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Change variable value
-    </title>
-  </head>
-  <body>
-    <h1>
-      Change variable value
-    </h1>
-    <p>
-      This command allows you to change the value of the selected variable.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-67.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-67.htm
deleted file mode 100644
index 2dd41df..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-67.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Terminate
-    </title>
-  </head>
-  <body>
-    <h1>
-      Terminate
-    </h1>
-    <p>
-      This command terminates the launch associated with the selected element.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-68.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-68.htm
deleted file mode 100644
index 268a1aa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-68.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Disconnect
-    </title>
-  </head>
-  <body>
-    <h1>
-      Disconnect
-    </h1>
-    <p>
-      This command disconnects the debugger from the selected remote debug launch.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-69.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-69.htm
deleted file mode 100644
index 2699b13..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-69.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Remove all terminated launches
-    </title>
-  </head>
-  <body>
-    <h1>
-      Remove all terminated launches
-    </h1>
-    <p>
-      This command clears all terminated launches from the view display.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-7.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-7.htm
deleted file mode 100644
index bf01b8d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-7.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Java
-    </title>
-  </head>
-  <body>
-    <h1>
-      Java
-    </h1>
-    <p>
-      Related Topics:
-    </p>
-    <ul>
-      <li>
-        <a href="ref-view-package-explorer.htm">See Packages View</a>
-      </li>
-      <li>
-        <a href="ref-type-hierarchy.htm">See Hierarchy View</a>
-      </li>
-      <li>
-        <a href="ref-45.htm">See Console View</a>
-      </li>
-      <li>
-        <a href="ref-view-outline.htm">See Java outline</a>
-      </li>
-    </ul>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-70.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-70.htm
deleted file mode 100644
index 1f8ac79..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-70.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Terminate and remove
-    </title>
-  </head>
-  <body>
-    <h1>
-      Terminate and remove
-    </h1>
-    <p>
-      This command terminates the launch associated with the selected element and removes it from the view.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-71.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-71.htm
deleted file mode 100644
index 284d8b3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-71.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Terminate all
-    </title>
-  </head>
-  <body>
-    <h1>
-      Terminate all
-    </h1>
-    <p>
-      This command terminates all active launches in the view.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-72.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-72.htm
deleted file mode 100644
index 43d0d83..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-72.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Relaunch
-    </title>
-  </head>
-  <body>
-    <h1>
-      Relaunch
-    </h1>
-    <p>
-      This command re-launches the selected launch.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-73.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-73.htm
deleted file mode 100644
index a58e244..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-73.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Properties
-    </title>
-  </head>
-  <body>
-    <h1>
-      Properties
-    </h1>
-    <p>
-      This command displays the various properties of the selected launch. For example, you can view the full command line that launched the selected process.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-74.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-74.htm
deleted file mode 100644
index 4cc551e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-74.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Variables view
-    </title>
-  </head>
-  <body>
-    <h1>
-      Variables view
-    </h1>
-    <p>
-      This view displays information about the variables in the currently-selected stack frame.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-6.htm">Java views</a><br>
-       <a href="../concepts/concepts-5.htm">Java perspectives</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-134.htm">Suspending threads</a><br>
-      <a href="../tasks/tasks-138.htm">Evaluating expressions</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <p>
-      <a href="../reference/ref-24.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-74a.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-74a.htm
deleted file mode 100644
index ccc486d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-74a.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Add/Remove watchpoint
-    </title>
-  </head>
-  <body>
-    <h1>
-      Add/Remove watchpoint
-    </h1>
-    <p>
-      This command allows you to add or remove a field watchpoint for the current selected variable in the <strong>Variables</strong> view.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-75.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-75.htm
deleted file mode 100644
index 80a4d5b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-75.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Show type names
-    </title>
-  </head>
-  <body>
-    <h1>
-      Show type names
-    </h1>
-    <p>
-      This option can be toggled to show or hide type names.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-76.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-76.htm
deleted file mode 100644
index 726320f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-76.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Show qualified names
-    </title>
-  </head>
-  <body>
-    <h1>
-      Show qualified names
-    </h1>
-    <p>
-      This option can be toggled to show or hide qualified names.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-78.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-78.htm
deleted file mode 100644
index e25eee5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-78.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Show static fields
-    </title>
-  </head>
-  <body>
-    <h1>
-      Show static fields
-    </h1>
-    <p>
-      This option can be toggled to show or hide static fields.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-8.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-8.htm
deleted file mode 100644
index 7de9923..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-8.htm
+++ /dev/null

@@ -1,27 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Java type hierarchy
-    </title>
-  </head>
-  <body>
-    <h1>
-      Java type hierarchy
-    </h1>
-    <p>
-      Related Topics:
-    </p>
-    <ul>
-      <li>
-        <a href="ref-type-hierarchy.htm">See Hierarchy View</a>
-      </li>
-    </ul>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-80.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-80.htm
deleted file mode 100644
index a3b1dbe..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-80.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Inspect
-    </title>
-  </head>
-  <body>
-    <h1>
-      Inspect
-    </h1>
-    <p>
-      This command causes the selected variable(s) to be inspected.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-81.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-81.htm
deleted file mode 100644
index 44f3a99..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-81.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Change variable value
-    </title>
-  </head>
-  <body>
-    <h1>
-      Change variable value
-    </h1>
-    <p>
-      This command allows you to change the value of the selected variable.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-9.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-9.htm
deleted file mode 100644
index 1f0c0a8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-9.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Debug
-    </title>
-  </head>
-  <body>
-    <h1>
-      Debug
-    </h1>
-    <p>
-      Related Topics:
-    </p>
-    <ul>
-      <li>
-        <a href="ref-51.htm">See Debug View</a>
-      </li>
-      <li>
-        <a href="ref-35.htm">See Breakpoints View</a>
-      </li>
-      <li>
-        <a href="ref-56.htm">See Expressions View</a>
-      </li>
-      <li>
-        <a href="ref-74.htm">See Variables View</a>
-      </li>
-      <li>
-        <a href="ref-52.htm">See Display View</a>
-      </li>
-      <li>
-        <a href="ref-view-outline.htm">See Java outline</a>
-      </li>
-      <li>
-        <a href="ref-45.htm">See Console View</a>
-      </li>
-    </ul>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-automaticProcessorOptions.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-automaticProcessorOptions.htm
deleted file mode 100644
index 9999dcc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-automaticProcessorOptions.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-	<meta name="copyright" content="Copyright (c) 2005 BEA Systems, Inc. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html" >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Automatic Processor Options
-    </title>
-  </head>
-  <body>
-    <h1>
-      Automatic Processor Options
-    </h1>
-    <p>Annotation processor options are configured in the 
-    <a href="ref-apt-config.htm">Annotation Processing preference dialog</a>.  Certain options 
-    are automatically provided to the processors; entering them in the Annotation Processing 
-    preference dialog will have no effect, since the automatically provided values will 
-    override any values set there.  The automatic options include the following:
-    <dl>
-    	<dt><strong>-classpath</strong></dt>
-    	<dd>
-    		The compiler classpath.  All entries are absolute paths, not workspace-relative.
-    	</dd>
-    	<dt><strong>-sourcepath</strong></dt>
-    	<dd>
-    		The compiler source path.  All entries are absolute paths, not workspace-relative.
-    	</dd>
-    	<dt><strong>-d</strong></dt>
-    	<dd>
-    		The absolute path of the compiler binary output directory, into which .class files are 
-    		built.
-    	</dd>
-    	<dt><strong>-s</strong></dt>
-    	<dd>
-    		The absolute path of the generated source directory, into which annotation processors 
-    		will generate files.
-    	</dd>
-    	<dt><strong>-source</strong></dt>
-    	<dd>
-    		The compiler -source option.  Typically a string such as &quot;5.0&quot;.
-    	</dd>
-    	<dt><strong>-target</strong></dt>
-    	<dd>
-    		The compiler -target option.  Typically a string such as &quot;5.0&quot;.
-    	</dd>
-    </dl>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-config.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-config.htm
deleted file mode 100644
index 1a16f11..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-config.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-	<meta name="copyright" content="Copyright (c) 2005 BEA Systems, Inc. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html" >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Annotation Processing Preferences
-    </title>
-  </head>
-  <body>
-    <h1>
-      Annotation Processing
-    </h1>
-    <p>Annotation processors can generate additional Java code or other files, and produce problem markers,
-    based on Java 5 (JSR-175) annotations.  The Annotation Processing preference pane permits configuration 
-    of preferences that apply to all processors in a project or workspace.  The <a href="ref-apt-factoryPath.htm">
-    Factory Path preference pane</a> specifies which processors are enabled and permits configuration of 
-    individual processors.
-    <h2>
-    	Generated source directory
-    </h2>
-    <p>Files will be generated on disk relative to the specified directory.  By default this directory
-    is named &quot;.apt_generated&quot;, which causes it to be filtered out of the Package Explorer view.  
-    Generated files have the &quot;derived&quot; bit set; in a clean, all derived files under the
-    generated source directory will be removed.  It is recommended to only
-    use this directory for files generated by processors; do not place any manually created files under
-    this directory, and do not use a pre-existing directory as the generated source directory.
-    <h2>
-    	Processor options
-    </h2>
-    <p>Options entered here will be available to the processors via the AnnotationProcessorEnvironment
-    interface.  Certain options are automatically provided to the processors; entering them in this dialog
-    will have no effect, since the automatically provided values will override any values set here.  
-    The automatic options are described <a href="ref-apt-automaticProcessorOptions.htm">here</a>. More
-    information about processor options is in the topic on <a href="ref-apt-processorOptionsInput.htm">the
-    Processor Options input dialog</a>.
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-factoryPath.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-factoryPath.htm
deleted file mode 100644
index 645619f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-factoryPath.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-	<meta name="copyright" content="Copyright (c) 2005 BEA Systems, Inc. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html" >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Factory Path Preferences
-    </title>
-  </head>
-  <body>
-    <h1>
-      Factory Path Preferences
-    </h1>
-    <p>Annotation processors can generate additional Java code or other files, and produce problem markers,
-    based on Java 5 (JSR-175) annotations.  The <a href="ref-apt-config.htm">Annotation Processing preference
-    pane</a> permits configuration of preferences that apply to all processors in a project or workspace.  
-    The Factory Path preference pane specifies which processors are enabled and permits configuration of 
-    individual processors.
-    <p>The pane displays a list of all the plugins and jar files that contain annotation processors that
-    may be applied to the project.  To add or remove jar files from the list, use the corresponding buttons.
-    Jar files may be specified by absolute path using the Add External Jars... button, or by path relative
-    to a classpath variable using the Add Variable... button.  All installed plugins that extend the
-    org.eclipse.jdt.apt.annotationProcessorFactory extension point are also displayed in the list.
-    <p>To enable a particular plugin or jar file, select the corresponding checkbox within the list.
-    Processors within plugins and jars that are not checked will not be executed.  If more than one processor
-    claims the same annotation, only first one on the list will be served that annotation.  To reorder the
-    list, use the Up and Down buttons.
-    <p>The Advanced... button leads to the <a href="ref-apt-factoryPathOptions.htm">Advanced Factory Path Options
-    dialog</a>, which is used to view the individual processor factories within a plugin or jar file
-    and to configure additional options.
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-factoryPathOptions.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-factoryPathOptions.htm
deleted file mode 100644
index 8d3f292..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-factoryPathOptions.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-	<meta name="copyright" content="Copyright (c) 2005 BEA Systems, Inc. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html" >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Advanced Factory Path Options Dialog
-    </title>
-  </head>
-  <body>
-    <h1>
-      Advanced Factory Path Options Dialog
-    </h1>
-    <p>The Advanced Factory Path Options dialog is reached from the <a href="ref-apt-factoryPath.htm">Factory Path</a>
-    preferences pane.  It is used to view the individual processor factories within a plugin or jar file
-    and to configure additional options.  Options on this dialog do not normally need to be changed from
-    the default.
-    <p>
-    <dl>
-    <dt><strong>Run this container's processors in batch mode</strong></dt>
-    <dd>
-    When this option is selected, the processors and processor factories in this jar will be run in  
-    a mode that enhances compatibility with the Sun(TM) command-line tool apt.  In this mode, 
-    processor classes are loaded at the beginning of a build, executed over the full set of Java types,
-    and then unloaded, as they would be when running apt at the command line.  Processors run in this
-    mode are only run during a full build, not during incremental builds.
-    This option is only configurable for jar files; for plugins it is always set to false.  
-    </dd>
-    </dl>
-    
-  </body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-processorOptionsInput.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-processorOptionsInput.htm
deleted file mode 100644
index 1f09966..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-processorOptionsInput.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-	<meta name="copyright" content="Copyright (c) 2005 BEA Systems, Inc. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html" >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Processor Option Input Dialog
-    </title>
-  </head>
-  <body>
-    <h1>
-      Processor Option Input Dialog
-    </h1>
-    <p>The Processor Option input dialog is reached from the <a href="ref-apt-config.htm">Annotation Processing
-    preferences pane</a>.  It allows processor options to be added or modified.  
-    <p>Options entered here will be presented to the processors through the AnnotationProcessorEnvironment
-    interface.  Each option will be presented in two forms: as a key/value pair, and as a combined
-    key corresponding to the command-line form of the option, namely &quot;-Akey=value&quot;.
-    For instance, an option with key &quot;foo&quot; and value &quot;bar&quot; would be presented
-    both that way and as key &quot;-Afoo=bar&quot;, value null.
-    <p>Option values representing paths may begin with a percent-delimited token such as <code>%FOO%/</code>.  
-    If the token is the name of a classpath variable, it will be replaced with the current
-    value of the variable at processor execution time.  The special value <code>ROOT</code> expands
-    to the absolute path of the workspace.  For example, <code>%ROOT%/foo/bar.xml</code> might 
-    expand to <code>d:/my_workspace/foo/bar.xml</code>, and <code>%JRE_LIB%/rt.jar</code> might 
-    expand to <code>c:/jdk1.5.0/lib/rt.jar</code>.  Similarly, the special value <code>PROJECT.DIR</code>
-    expands to the absolute path of the current project.
-    <p>Certain options are automatically provided to the processors; entering them in this dialog
-    will have no effect, since the automatically provided values will override any values set here.  
-    The automatic options are described <a href="ref-apt-automaticProcessorOptions.htm">here</a>.
-  </body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-gettersetter.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-gettersetter.htm
deleted file mode 100644
index 266521e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-gettersetter.htm
+++ /dev/null

@@ -1,95 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Create Getters and Setters
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Create Getters and Setters
-    </h1>
-    <p>
-      This dialog lets select the getter and setter methods to create.
-    </p>
-	<p>
-     Use <strong>Generate Getters and Setters</strong> from the <a href="ref-menu-source.htm">Source menu</a> or the context menu on a selected field or type, or a text selection in
-    a type to open the dialog.
-     The Generate Getters and Setters dialog shows getters and setters for all fields of the selected type. The methods are grouped by the type's fields. 
-	 </p>
-    <p>
-      The names of the getter and setter methods are derived from the field name. If you use a prefix or suffix for fields (e.g. fValue, _value, val_m), you can specify the
-      suffixes and prefixes in the <a href="ref-preferences-code-generation.htm">Code Style preference page</a> (Windows &gt; Preferences &gt; Java &gt; Code Style).
-    </p>
-    <p>
-      When pressing&nbsp;<strong>OK</strong>, all selected getters and setters are created.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <tr>
-        <th>
-          <p>
-            Option
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Select getters and setters to create
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            A tree containing getter and setter methods that can be created. Getters and setters are grouped by field their associated field.&nbsp;
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Select All
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Select all getter and setter methods
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Deselect All
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Deselect all getter and setter methods
-          </p>
-        </td>
-      </tr>
-    </table>
-	<p>
-    You can control whether Javadoc comments are added to the created methods
-    with the <strong>Generate method comments</strong> option at the bottom of the dialog.</p>
-    <p> 
-	  <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-	  </p>
-	  <p>
-      <a href="../tasks/tasks-57.htm">Generating getters and setters</a><br>
-      <a href="../reference/ref-menu-source.htm">Source actions</a>
-	</p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-java-element-filters.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-java-element-filters.htm
deleted file mode 100644
index bb8bdc5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-java-element-filters.htm
+++ /dev/null

@@ -1,97 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Java element filters dialog
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Java element filters dialog
-    </h1>
-    <p>
-      This dialog lets you define Java element filters for the Package Explorer view.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-          <th>
-            <p>
-              Default
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-             Name filter patterns
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, a comma separated list of patterns can be specified additionally.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Off
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Select the elements to exclude from the view
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              List of pre-defined filters which can be enabled.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              	.* files<br>
-			  	Empty parent packages<br>
-				Import declarations<br>
-				Inner class files<br>
-				Package declarations
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      The <strong>Filter description</strong> field displays the description for the currently selected filter.
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-      <p>
-      <a href="../tasks/tasks-47.htm">Filtering elements</a><br>
-       <a href="../tasks/tasks-2.htm">Showing and hiding elements</a>
-       </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-view-package-explorer.htm">Package Explorer view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-javadoc-location.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-javadoc-location.htm
deleted file mode 100644
index 4df02d5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-javadoc-location.htm
+++ /dev/null

@@ -1,110 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Javadoc location page
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Javadoc location page
-    </h1>
-    <p>
-      This dialog lets you define the location of the Javadoc documentation for a JAR or a Java project.
-    </p>
-	<p>
-     You can reach this dialog the following ways: 
-	</p>
-    <ul>
-      <li>
-        Select a JAR or Java project, open the context menu and select Properties &gt; Javadoc Location or use&nbsp;<strong>Properties</strong> from the <a href=
-        "ref-menu-file.htm">File menu</a>
-      </li>
-      <li>
-        In the Javadoc generation wizard, on the Standard doclet settings page, choose&nbsp;<strong>Configure</strong>
-      </li>
-    </ul>
-	<p>
-    Javadoc can be attached to JARs or Java projects. For projects it documents the elements of all source folders, 
-	for JARs, elements contained in the JAR are documented. The location is used by 
-	</p>
-    <ul>
-      <li>
-        <strong>Open External Javadoc</strong> in the <a href="ref-menu-navigate.htm">Navigate menu</a> to find the Javadoc location of an element
-      </li>
-      <li>
-        Context Help (F1) to point to a Javadoc location
-      </li>
-      <li>
-        <a href="ref-export-javadoc.htm">Javadoc Export Wizard</a> to link to other documentation or as default destination for a project's documentation
-      </li>
-    </ul>
-	<p>
-    Valid locations are URLs that point to a folder containing the API documentation's&nbsp;<em>index.html</em> and&nbsp;<em>package-list</em> file. Examples are: 
-	</p>
-    <blockquote>
-      file:///M:/JAVA/JDK1.2/DOCS/API/<br>
-       http://java.sun.com/j2se/1.4/docs/api/
-    </blockquote>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <tr>
-        <th>
-          <p>
-            Option
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-        <th>
-          <p>
-            Default
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Javadoc Location
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Specify the location of the generated Javadoc documentation. You can&nbsp;<strong>Browse</strong> in the local file system for a Javadoc location (will result in a
-            file:// URL)&nbsp;
-          </p>
-        </td>
-        <td valign="top">
-          &lt;empty&gt;
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Validate
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Validate the current location by trying to access the&nbsp;<em>index.html</em> and&nbsp;<em>package-list</em> file with the given URL. If the validation was
-            successful, you can directly open the documentation.&nbsp;
-          </p>
-        </td>
-        <td valign="top">
-          <p>&nbsp;
-            
-          </p>
-        </td>
-      </tr>
-    </table>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-override-method.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-override-method.htm
deleted file mode 100644
index d20bef7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-override-method.htm
+++ /dev/null

@@ -1,127 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Override methods
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Override methods
-    </h1>
-    <p>
-      This dialog lets you define methods to override.
-    </p>
-	<p>
-     Use <strong>Override/Implement Methods</strong> from the <a href="ref-menu-source.htm">Source menu</a> or the context menu on a selected type or on a text selection in a type. 
-	</p>
-    <p>
-      The dialog presents all methods that can be overridden from supertypes or implemented from interfaces. Abstract methods or unimplemented methods are selected by default.
-    </p>
-    <p>
-      The tree view groups methods by the type declaring the method. If more than one type in the hierarchy declare the same method, the method is only shown once, grouped to the
-      first type in the list of supertypes that implements or defines this method.
-    </p>
-    <p>
-      The flat view shows only methods, sorted alphabetically.
-    </p>
-    <p>
-      When pressing&nbsp;<strong>OK</strong>, method stubs for all selected methods are created.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <tr>
-        <th>
-          <p>
-            Option
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-        <th>
-          <p>
-            Default
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Select methods to override or implement
-          </p>
-        </td>
-        <td valign="top">
-          Select methods to override or implement
-        </td>
-        <td valign="top">
-          Abstract methods from superclasses and unimplemented methods from interfaces are selected
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Group methods by types
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Shows methods grouped by a list of the super types in which they are declared.&nbsp;
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            selected&nbsp;
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Select All
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Select all methods
-          </p>
-        </td>
-        <td valign="top">
-                <p>n/a</p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Deselect All
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Deselect all methods
-          </p>
-        </td>
-        <td valign="top">
-        <p>n/a</p>
-        </td>
-      </tr>
-    </table>
-    	<p>
-    You can control whether Javadoc comments are added to the created methods
-    with the <strong>Generate method comments</strong> option at the bottom of the dialog.</p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-menu-source.htm">Source actions</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-export-jar.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-export-jar.htm
deleted file mode 100644
index 76c09cd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-export-jar.htm
+++ /dev/null

@@ -1,273 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      JAR file exporter
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      JAR file exporter
-    </h1>
-    <p>
-      This wizard allows you to create a JAR file.
-    </p>
-    <h2>
-      JAR package specification
-    </h2>
-	<p>
-	  JAR Specification Options:
-	</p>
-    <table border="1" cellspacing="0" cellpadding="5">
-      <tbody>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Select the resources to export
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              In the list, check or clear the boxes to specify exactly the files that you want to export to the JAR file. This list is initialized by the workbench selection.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Export generated class files and resources
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              If you want to export generated CLASS files and resources, select this option.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Export Java source files and resources
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              If you want to export JAVA source files and resources, select this option.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Select the export destination
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Enter an external file system path and name for a JAR file (either new or existing). Either type a valid file path in the field or click Browse to select a file via
-              a dialog.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Options
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              You can select any of the following options:
-            </p>
-            <ul>
-              <li>
-                <strong>Compress the contents of the JAR file&nbsp;</strong>: to create a compressed JAR file
-              </li>
-              <li>
-                <strong>Overwrite existing files without warning</strong> : if an existing file might be overwritten, you are prompted for confirmation. This option is applied to
-                the JAR file, the JAR description, and the manifest file.
-              </li>
-            </ul>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <h2>
-      JAR packaging options
-    </h2>
-	<p>
-        JAR Options:
-	</p>
-    <table border="1" cellspacing="0" cellpadding="5">
-      <tbody>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Select options for handling problems
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Choose whether to export classes with certain problems:
-            </p>
-            <ul>
-              <li>
-                Export class files with compile errors
-              </li>
-              <li>
-                Export class files with compile warnings
-              </li>
-            </ul>
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Create source folder structure
-          </td>
-          <td>
-            Selected this option if you want the source folder structure to be rebuilt in the JAR. This option is only enabled when source files but no class files are
-            exported.&nbsp;
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Build projects if not build automatically
-          </td>
-          <td>
-            Select this option to force a rebuild before exporting. It is recommended to build be before exporting so the exported class files are up to date.
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Save the description of this JAR in the workspace
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              If you select this option, you can create a file in the workbench describing the JAR file you are creating. Either type and/or browse to select a path and name for
-              this new file.
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <h2>
-      JAR manifest specification
-    </h2>
-	<p>
-        JAR Manifest Specification Options (Available when class file are exported):
-	</p>
-    <table border="1" cellspacing="0" cellpadding="5">
-      <tbody>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Specify the manifest
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Choose the source of the manifest file for this JAR file:
-            </p>
-            <ul>
-              <li>
-                Generate the manifest file (you can also choose either to save or reuse and save the new manifest file)
-              </li>
-              <li>
-                Use existing manifest from workspace
-              </li>
-            </ul>
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Seal contents
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Choose which packages in the JAR file must be sealed:
-            </p>
-            <ul>
-              <li>
-                Seal the JAR: to seal the entire JAR file; click&nbsp;<strong>Details</strong> to exclude selectively
-              </li>
-              <li>
-                Seal some packages; click&nbsp;<strong>Details</strong> to choose selectively
-              </li>
-            </ul>
-             <em>Note: This option is only available if the manifest is generated.</em>
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Select the class of the application entry point&nbsp;
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Type or click&nbsp;<strong>Browse</strong> to select the main class for the JAR file, if desired.
-            </p>
-             <em>Note: This option is only available if the manifest is generated.</em>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-      <p>
-      <a href="../tasks/tasks-32.htm">Creating JAR Files</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference"></p>
-      <p>
-      <a href="../reference/ref-menu-file.htm">File actions</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-export-javadoc.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-export-javadoc.htm
deleted file mode 100644
index a716a66..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-export-javadoc.htm
+++ /dev/null

@@ -1,344 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Javadoc generation
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Javadoc generation
-    </h1>
-    <p>
-      This wizard allows you to generate Javadoc Generation.It is a user interface for the javadoc.exe tool available in the Java JDK. Visit <a href=
-      "http://java.sun.com/j2se/1.4/docs/tooldocs/javadoc/index.html" target="_blank">Sun's Javadoc Tool</a> page for a complete documentation of the Javadoc tool.
-	</p>
-    <h2>
-      First page
-    </h2>
-	<p>
-        Type Selection:
-	</p>
-    <table border="1" cellspacing="0" cellpadding="5">
-      <tr>
-        <th>
-          <p>
-            Option
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Select types for which Javadoc will be generated
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <p>
-            In the list, check or clear the boxes to specify exactly the types that you want to export to the JAR file. This list is initialized by the workbench selection. Only
-            one project can be selected at once as only one project's classpath can be used at a time when running the Javadoc tool.
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Create Javadoc for members with visibility
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <ul>
-            <li>
-              <strong>Private</strong>: All members will be documented
-            </li>
-            <li>
-              <strong>Package</strong>: Only members with default, protected or public visibility will be documented
-            </li>
-            <li>
-              <strong>Protected</strong>: Only members with protected or public visibility will be documented
-            </li>
-            <li>
-              <strong>Public</strong>: Only members with public visibility will be documented (default)
-            </li>
-          </ul>
-          <br>
-          <br>
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Use Standard Doclet
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Start the Javadoc command with the standard doclet (default)&nbsp;
-          </p>
-          <ul>
-            <li>
-              <strong>Destination</strong>: select the destination to which the standard doclet will write the generated documentation. The destination is a doclet specific
-              argument, and therefore not enabled when using a custom doclet.
-            </li>
-          </ul>
-          <br>
-          <br>
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Use Custom Doclet
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Use a custom doclet to generate documentation&nbsp;
-          </p>
-          <ul>
-            <li>
-              <strong>Doclet name</strong>: Qualified type name of the doclet
-            </li>
-            <li>
-              <strong>Doclet class path</strong>: Classpath needed by the doclet class
-            </li>
-          </ul>
-          <br>
-          <br>
-        </td>
-      </tr>
-    </table>
-	
-    <h2>
-      Standard doclet arguments
-    </h2>
-	<p>
-        Standard Doclet Arguments (available when&nbsp;<strong>Use standard doclet</strong> has been selected):
-	</p>
-    <table border="1" cellspacing="0" cellpadding="5">
-      <tr>
-        <th>
-          <p>
-            Option
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Document title
-          </p>
-        </td>
-        <td align="left" valign="top">
-          Specify a document title.
-        </td>
-      </tr>
-      <tr>
-        <td>
-          Generate use page
-        </td>
-        <td>
-          Selected this option if you want the documentation to contain a Use page.
-        </td>
-      </tr>
-      <tr>
-        <td>
-          Generate hierarchy tree
-        </td>
-        <td>
-          Selected this option if you want the documentation to contain a Tree page.
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Generate navigator bar
-          </p>
-        </td>
-        <td align="left" valign="top">
-          Selected this option if you want the documentation to contain a navigation bar (header and footer).
-        </td>
-      </tr>
-      <tr>
-        <td>
-          Generate index
-        </td>
-        <td>
-          Selected this option if you want the documentation to contain a Index page.
-        </td>
-      </tr>
-      <tr>
-        <td>
-          Generate index per letter
-        </td>
-        <td>
-          Create an index per letter. Enabled when <strong>Generate Index</strong> is selected.&nbsp;
-        </td>
-      </tr>
-      <tr>
-        <td>
-          @author
-        </td>
-        <td>
-          Selected this option if you want to the @author tag to be documented.
-        </td>
-      </tr>
-      <tr>
-        <td>
-          @version
-        </td>
-        <td>
-          Selected this option if you want to the @version tag to be documented.
-        </td>
-      </tr>
-      <tr>
-        <td>
-          @deprecated
-        </td>
-        <td>
-          Selected this option if you want to the @deprecated tag to be documented.
-        </td>
-      </tr>
-      <tr>
-        <td>
-          deprecated list
-        </td>
-        <td>
-          Selected this option if you want the documentation to contain a Deprecated page. Enabled when the&nbsp;<strong>@deprecated</strong> option is selected.
-        </td>
-      </tr>
-      <tr>
-        <td>
-          Select referenced classes to which Javadoc should create links
-        </td>
-        <td>
-          Specify to which other documentation Javadoc should create links when other types are referenced.&nbsp; 
-          <ul>
-            <li>
-              Select All: Create links to all other documentation locations
-            </li>
-            <li>
-              Clear All: Do not create links to other documentation locations
-            </li>
-            <li>
-              Configure: Configure the Javadoc location of a referenced JAR or project.
-            </li>
-          </ul>
-        </td>
-      </tr>
-      <tr>
-        <td>
-          Style sheet
-        </td>
-        <td>
-          Select the style sheet to use
-        </td>
-      </tr>
-    </table>
-     
-    <h2>
-      General arguments
-    </h2>
-	<p>
-        General Javadoc Options:
-	</p>
-    <table border="1" cellspacing="0" cellpadding="5">
-      <tr>
-        <th>
-          <p>
-            Option
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Overview
-          </p>
-        </td>
-        <td align="left" valign="top">
-          Specifies that Javadoc should retrieve the text for the overview documentation from the given file. It will be placed in overview-summary.html.
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Extra Javadoc options
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Add any number of extra options here: Custom doclet options,VM options or JRE 1.4 compatibility options.<br>
-             Note that arguments containing spaces must enclosed in quotes. For arguments specifying html code (e.g. -header) use the &amp;nbsp; or &amp;quot; to avoid spaces and
-            quotes.
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Save the settings of this Javadoc export as an Ant script
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Specify to store an Ant script that will perform the specified Javadoc export without the need to use the wizard. Existing Ant script can be modified with this wizard
-            (Use Open Javadoc wizard' from the context menu on the generated Ant script)
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td>
-          Open generated index file in browser
-        </td>
-        <td>
-          Opens the generated index.html file in the browser (Only available when using the standard doclet)
-        </td>
-      </tr>
-    </table>
-    <p>
-      Press&nbsp;<strong>Finish</strong> to start the Javadoc generation.
-       If the destination is different to the location configured the project's <a href="ref-dialog-javadoc-location.htm"> Javadoc Location page</a> , you will be asked if you
-      want to set the project's Javadoc location to the new destination folder. By doing this, all invocations of Open External Javadoc will use the now created
-      documentation.
-    </p>
-    <p>
-      A new process will be started and the generation performed in the background. Open the <a href="ref-45.htm">Console view</a> (Window &gt; Show View &gt; Console) to see the
-      progress and status of the generation.
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-      <p>
-      <a href="../tasks/tasks-196.htm">Creating Javadoc documentation</a>
-      </p>
-           <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-       <a href="../reference/ref-menu-file.htm">File actions</a><br>
-       <a href="../reference/ref-dialog-javadoc-location.htm">Javadoc Location properties</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor-quickfix.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor-quickfix.htm
deleted file mode 100644
index 1f39bf5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor-quickfix.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Quick fix
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Quick fix
-    </h1>
-    <p>
-      For certain problems underlined with a problem highlight line, the Java editor can offer corrections. This is shown by the light bulb shown in the editor marker bar.
-    </p>
-	<p>
-    <img src="../images/qs-37a.png"  alt="A Java editor indicating a quick-fixable problem with a lightbulb in the editor marker bar"> <br>
-	</p>
-     To see the correction proposals use the Quick Fix action 
-    <ul>
-      <li>
-        Set the cursor inside the highlight range, and select&nbsp;<strong>Quick Fix</strong> from the <a href="ref-menu-edit.htm">Edit menu</a> or the context menu.
-      </li>
-      <li>
-        Set the cursor inside the highlight range, and press Ctrl + 1
-      </li>
-      <li>
-        Click on the light bulb
-      </li>
-    </ul>
-<p>Quick fix is also available on a problem entry in the Problem view. The Quick Fix action will open a dialog to select the correction.
-<br>
-    <br>
-Note that the light bulb is only a hint. It is possible that even with the light bulb shown, it turns out that no corrections can be offered.<br>
-A overview of quick fixes available in the Java editor can be found <a
-	href="../concepts/cquickfix.htm">here</a>.<br><br>Quick Assists are proposals available even if there is no problem or warning. See the <a
-	href="../concepts/cquickassists.htm">Quick Assist</a> page for more information.</p>
-	<p>	  
-       <img src="../images/ngrelc.png" alt="Related concepts" border="0" ><br>
-<a href="../concepts/cquickfix.htm">Quick Fix</a><br>
-<a href="../concepts/cquickassists.htm">Quick Assist<br>
-<a href="../concepts/concepts-7.htm">Java editor</a>
-</a></p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-      <p>
-      <a href="../tasks/tasks-175.htm">Using quick fix</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference"></p>
-      <p>
-      <a href="../reference/ref-21.htm">Java editor preferences</a><br>
-       <a href="../reference/ref-menu-edit.htm">Edit menu</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor.htm
deleted file mode 100644
index 16e575c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor.htm
+++ /dev/null

@@ -1,189 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Java editor
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Java editor
-    </h1>
-    <h2 class="Head">
-      Toolbar actions
-    </h2>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Command
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-              Show Source of Selected Element Only
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              This option can be toggled to display a segmented view of the source of the selected Java element. This button applies to the currently-active editor and to all
-              editors opened in the future; other currently-open editors are not affected.
-            </p>
-            <p>
-              For example, if a method is selected in the Outline view, the <strong>Show Source Of Selected Element Only</strong> option causes only that method to be displayed in
-              the editor, as opposed to the entire class.
-            </p>
-            <dl>
-              <dt>
-                <strong>Off</strong>:
-              </dt>
-              <dd>
-                The entire compilation unit is displayed in the editor, with the selected Java element highlighted in the marker bar with a range indicator.
-              </dd>
-              <dt>
-                <strong>On</strong>:
-              </dt>
-              <dd>
-                Only the selected Java element is displayed in the editor, which is linked to the selection in the Outline or Hierarchy view.
-              </dd>
-            </dl>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Go to Next Problem
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              This command navigates to the next problem marker in the active editor.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Go to Previous Problem
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              This command navigates to the previous problem marker in the active editor.
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <h2 class="Head">
-      Key binding actions
-    </h2>
-    <p>
-      The following actions can only be reached through key bindings. The <strong>Key bindings</strong> field in <strong>Window &gt; Preferences &gt; General &gt;
-      Keys </strong> must be set to 'Emacs'.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Key binding
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-              <kbd>Alt</kbd>+<kbd>0</kbd> <kbd>Ctrl</kbd>+<kbd>K</kbd>, <kbd>Esc</kbd> <kbd>0</kbd> <kbd>Ctrl</kbd>+<kbd>K</kbd>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Deletes from the cursor position to the beginning of the line.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <kbd>Ctrl</kbd>+<kbd>K</kbd>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Deletes from the cursor position to the end of the line.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <kbd>Ctrl</kbd>+<kbd>Space</kbd>, <kbd>Ctrl</kbd>+<kbd>2</kbd>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Sets a mark at the current cursor position.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <kbd>Ctrl</kbd>+<kbd>X</kbd> <kbd>Ctrl</kbd>+<kbd>X</kbd>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Swaps the cursor and mark position if any.
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-      <p>
-      <a href="../concepts/concepts-7.htm">Java editor</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-      </p>
-      <p>
-      <a href="../tasks/tasks-54.htm">Using the Java editor</a><br>
-      <a href="../tasks/tasks-69.htm">Viewing documentation and information</a><br>
-       <a href="../tasks/tasks-6.htm">Showing single elements or whole Java files</a><br>
-       <a href="../tasks/tasks-73.htm">Opening an editor for a selected element</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference"></p>
-      <p>
-      <a href="../reference/ref-view-outline.htm">Java outline</a><br>
-      <a href="../reference/ref-21.htm">Java editor preferences</a><br>
-      <a href="../reference/ref-2.htm">JDT actions</a><br>
-      <a href="../reference/ref-24.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-edit.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-edit.htm
deleted file mode 100644
index 028f95f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-edit.htm
+++ /dev/null

@@ -1,323 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Edit actions
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Edit actions
-    </h1>
-	<p>
-        Edit menu commands shown when a Java Editor is visible:
-	</p>     
-    <table border="1" cellspacing="0" cellpadding="5">
-      <tbody>
-        <tr>
-          <th>
-            <p>
-              Name
-            </p>
-          </th>
-          <th>
-            <p>
-              Function
-            </p>
-          </th>
-          <td>
-            <strong>Keyboard Shortcut</strong>
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td align="left" valign="top">
-            <p>
-              Undo
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Revert the last change in the editor
-            </p>
-          </td>
-          <td>
-            Ctrl + Z
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Redo&nbsp;
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Revert an undone change
-            </p>
-          </td>
-          <td>
-            Ctrl + Y
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Cut
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Copies the currently selected text or element to the clipboard and removes the element. On elements, the remove is not performed before the clipboard is pasted.
-            </p>
-          </td>
-          <td>
-            Ctrl + X
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Copy
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Copies the currently selected text or elements to the clipboard
-            </p>
-          </td>
-          <td>
-            Ctrl + C
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Paste
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Paste the current content as text to the editor, or as a sibling or child element to the a currently selected element.&nbsp;
-            </p>
-          </td>
-          <td>
-            Ctrl + V
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Delete
-          </td>
-          <td>
-            Delete the current text or element selection.
-          </td>
-          <td>
-            Delete
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Select All
-          </td>
-          <td>
-            Select all the editor content..
-          </td>
-          <td>
-            Ctrl + A
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Find / Replace
-          </td>
-          <td>
-            Open the Find / Replace dialog. Editor only.
-          </td>
-          <td>
-            Ctrl + F
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Find Next
-          </td>
-          <td>
-            Finds the next occurrence of the currently selected text. Editor only.
-          </td>
-          <td>
-            Ctrl + K
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Find Previous
-          </td>
-          <td>
-            Finds the previous occurrence of the currently selected text. Editor only.
-          </td>
-          <td>
-            Ctrl + Shift + K
-          </td>
-        </tr>
-        
-        <tr>
-          <td>
-            Incremental Find Next
-          </td>
-          <td>
-            Starts the incremental find mode. After invocation, enter the search text as instructed in the status bar. Editor only.
-          </td>
-          <td>
-            Ctrl + J
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Incremental Find Previous
-          </td>
-          <td>
-            Starts the incremental find mode. After invocation, enter the search text as instructed in the status bar. Editor only.
-          </td>
-          <td>
-            Ctrl + Shift + J
-          </td>
-        </tr>
-        
-        <tr align="left" valign="top">
-          <td>
-            Add Bookmark
-          </td>
-          <td>
-            Add a bookmark to the current text selection or selected element.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Add Task
-          </td>
-          <td>
-            Add a user defined task to the current text selection or selected element.
-          </td>
-          <td>
-            Alt + Enter
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Expand Selection to
-          </td>
-          <td>
-            <ul>
-              <li>
-                Enclosing Element: Selects the enclosing expression, block, method in the code. This action is aware of the Java syntax. It may not function properly when the code
-                has syntax errors. (Arrow Up)
-              </li>
-              <li>
-                Next Element: Selects the current and next element. (Arrow Right)
-              </li>
-              <li>
-                Previous Element: Selects the current and the previous element (Arrow Left)
-              </li>
-              <li>
-                Restore Last Selection: After an invocation of&nbsp;<em>Expand Selection to</em> restore the previous selection. (Arrow Down)
-              </li>
-            </ul>
-          </td>
-          <td>
-            Alt + Shift + Arrow Keys
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Show Tooltip Description
-          </td>
-          <td>
-            Shows the value of a hover that would appear at the current cursor location. The dialog shown is scrollable and does not shorten descriptions.
-          </td>
-          <td>
-            F2
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Content Assist
-          </td>
-          <td>
-            Opens a context assist dialog at the current cursor position to bring up Java code assist proposals and templates. See the <a href=
-            "ref-preferences-templates.htm">Templates preference page</a> for available templates (Window &gt; Preferences &gt; Java &gt; Editor &gt; Templates) and go to the <a href=
-            "ref-21.htm">Java Editor preference page</a> (Window &gt; Preferences &gt; Java &gt; Editor &gt; Code Assist) for configuring the behavior of code assist.
-          </td>
-          <td>
-            Ctrl + Space
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Quick Fix
-          </td>
-          <td>
-            If the cursor is located at a location with problem indication this opens a context assist dialog at the current cursor to present possible corrections.&nbsp;
-          </td>
-          <td>
-            Ctrl + 1
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Parameter Hints
-          </td>
-          <td>
-            If the cursor is located at the parameter specification for method reference, this actions shows a hover with parameter types information.The parameter at the current
-            cursor location is shown in bold.
-          </td>
-          <td>
-            Ctrl + Shift + Space
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Encoding
-          </td>
-          <td>
-            Toggles the encoding of the currently shown text content.
-          </td>
-          <td>&nbsp;
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-       <img  src="../images/ngrelc.png" alt="Related concepts" border="0">
-      </p>
-      <p>
-      <a href="../concepts/concepts-7.htm">Java editor</a><br>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelt.png" alt="Related tasks">
-      </p>
-      <p>
-      <a href="../tasks/tasks-54.htm">Using the Java editor</a><br>
-       <a href="../tasks/tasks-175.htm">Using Quick Fix</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-      </p>
-      <p>
-      <a href="ref-java-editor.htm">Java editor</a><br>
-       <a href="ref-21.htm">Java editor preferences</a><br>
-       <a href="ref-view-outline.htm">Java outline</a><br>
-       <a href="ref-24.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-file.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-file.htm
deleted file mode 100644
index 123087a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-file.htm
+++ /dev/null

@@ -1,265 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      File actions
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      File actions
-    </h1>
-    <p>
-        File Menu Commands:
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5">
-      <caption>
-      </caption>
-      <tbody>
-        <tr>
-          <th>
-            <p>
-              Name
-            </p>
-          </th>
-          <th>
-            <p>
-              Function
-            </p>
-          </th>
-          <td>
-            <strong>Keyboard Shortcut</strong>
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td align="left" valign="top">
-            <p>
-              New
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Create a Java element or a new resource. Configure which elements are shown in the submenu in Window &gt; Customize Perspective. In a Java perspective, by default
-              action for creating a <a href="ref-121.htm">project</a>, <a href="ref-125.htm">package</a>, <a href="ref-126.htm">class</a>, <a href="ref-126b.htm">enum</a>, <a href="ref-127.htm">interface</a> , <a href="ref-127b.htm">annotation</a> , <a href="ref-128.htm">source
-              folder</a>, <a href="ref-129.htm">scrapbook</a>, file and folder are available.
-            </p>
-          </td>
-          <td>
-            Ctrl + N
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Close&nbsp;
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Close the current editor. If the editor contains unsaved data, a save request dialog will be shown.
-            </p>
-          </td>
-          <td>
-            Ctrl + F4
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Close All
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Close all editors. If editors contains unsaved data, a save request dialog will be shown.
-            </p>
-          </td>
-          <td>
-            Ctrl + Shift + F4
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Save
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Save the content of the current editor. Disabled if the editor does not contain unsaved changes.
-            </p>
-          </td>
-          <td>
-            Ctrl + S
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Save As
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Save the content of the current editor under a new name.
-            </p>
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Save All
-          </td>
-          <td>
-            Save the content of all editors with unsaved changes. Disabled if no editor contains unsaved changes.
-          </td>
-          <td>
-            Ctrl + Shift + S
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Revert
-          </td>
-          <td>
-            Revert the content of the current editor back to the content of the saved file. Disabled if the editor does not contain unsaved changes.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Move
-          </td>
-          <td>
-            Move a resource. Disabled on Java Elements. To move Java elements use Refactor &gt; Move (with updating all references to the file) or <a href=
-            "ref-menu-edit.htm">Edit</a> &gt; Cut / Paste (no updating of references).
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Rename
-          </td>
-          <td>
-            Renames a resource. Disabled on Java Elements. To rename Java elements use Refactor &gt; Rename (with updating all references to the file).
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Refresh
-          </td>
-          <td>
-            Refreshes the content of the selected element with the local file system.When launched from no specific selection, this command refreshes all projects.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Print
-          </td>
-          <td>
-            Prints the content of the current editor. Enabled when an editor has the focus.
-          </td>
-          <td>
-            Ctrl + P
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Import
-          </td>
-          <td>
-            Opens the import wizard dialog. JDT does not contribute any import wizards.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Export
-          </td>
-          <td>
-            Opens the export wizard dialog. JDT contributes the <a href="ref-export-jar.htm">JAR file export wizard</a> and the <a href=
-            "ref-export-javadoc.htm">Javadoc generation wizard</a>.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Properties
-          </td>
-          <td>
-            Opens the property pages of the select elements. Opened on Java projects the <a href="ref-123.htm">Java Build Path</a> page and the <a href=
-            "ref-dialog-javadoc-location.htm">Javadoc Location page</a> are available. For JAR archives, configure the JAR's <a href="ref-124.htm">Source Attachment</a> and <a
-            href="ref-dialog-javadoc-location.htm">Javadoc Location</a> here.
-          </td>
-          <td>
-            Alt + Enter
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Exit
-          </td>
-          <td>
-            Exit Eclipse
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img  src="../images/ngrelc.png" alt="Related concepts" border="0">
-      </p>
-      <p>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelt.png" alt="Related tasks">
-      </p>
-      <p>
-      <a href="../tasks/tasks-11.htm">Creating Java elements</a><br>
-       <a href="../tasks/tasks-32.htm">Creating JAR Files</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-      </p>
-      <p>
-      <a href="ref-121.htm">New Java Project wizard</a><br>
-	  <a href="ref-125.htm">New Java Package wizard</a><br> 
-	  <a href="ref-126.htm">New Java Class wizard</a><br>
-	  <a href="ref-126b.htm">New Java Enum wizard</a><br>
-	  <a href="ref-127.htm">New Java Interface wizard</a><br>
-	  <a href="ref-127b.htm">New Java Annotation wizard</a><br>
-	  <a href="ref-129.htm">New Java Scrapbook Page wizard</a><br>
-	  <a href="ref-export-jar.htm">JAR file exporter</a><br>
-	  <a href="ref-export-javadoc.htm">Javadoc generation</a><br>
-	  <a href="ref-dialog-javadoc-location.htm">Javadoc Location properties</a><br>
-	  <a href="ref-123.htm">Java Build Path properties</a><br>
-	  <a href="ref-124.htm">Source Attachment properties</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-navigate.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-navigate.htm
deleted file mode 100644
index 4026db2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-navigate.htm
+++ /dev/null

@@ -1,271 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Navigate actions
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Navigate actions
-    </h1>
-	<p>
-        Navigate menu commands:
-	</p>
-    <table border="1" cellspacing="0" cellpadding="5">
-      <tbody>
-        <tr>
-          <th>
-            <p>
-              Name
-            </p>
-          </th>
-          <th>
-            <p>
-              Function
-            </p>
-          </th>
-          <td>
-            <strong>Keyboard Shortcut</strong>
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td align="left" valign="top">
-            <p>
-              Go Into
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Sets the view input to the currently selected element. Supported by the <a href="ref-view-package-explorer.htm">Packages Explorer view</a>.
-            </p>
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Go To
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <ul>
-              <li>
-                Back: Sets the view input to the input back in history: Only enabled when a history exists (<strong>Go Into</strong> was used)
-              </li>
-              <li>
-                Forward: Sets the view input to the input forward in history: Only enabled when a history exists (<strong>Go Into</strong>,&nbsp; <strong>Go To &gt; Back</strong>
-                were used)
-              </li>
-              <li>
-                Up One Level: Sets the input of the current view to its input's parent element
-              </li>
-              <li>
-                Referring Tests: Browse for all JUnit tests that refer to the currently selected type
-              </li>
-              <li>
-                Type: Browse for a type and reveal it in the current view. Supported by the Package Explorer view
-              </li>
-              <li>
-                Package: Browse for a package and reveal it in the current view. Supported by the Package Explorer view
-              </li>
-              <li>
-                Resource: Browse for a resource and reveal it in the current view.
-              </li>
-            </ul>
-          </td>
-          <td>&nbsp;
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Open
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Tries to resolve the element referenced at the current code selection and opens the file declaring the reference.&nbsp;
-            </p>
-          </td>
-          <td>
-            F3
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Open Type Hierarchy
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Tries to resolve the element referenced at the current code selection and opens the element in the <a href="ref-type-hierarchy.htm">Type Hierarchy view</a>. Invoked
-              on elements, opens the type hierarchy of the element. Supported in the Java editor and views showing Java elements.
-            </p>
-          </td>
-          <td>
-            F4
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Open Super Implementation
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Open an editor for the super implementation of the currently selected method or method surrounding the current cursor position. No editor is opened if no method is
-              selected or the method has no super implementation.
-            </p>
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Open External Javadoc
-          </td>
-          <td>
-            Opens the Javadoc documentation of the currently selected element or text selection. The location of the Javadoc of a JAR or a project is specified in the <a href=
-            "ref-dialog-javadoc-location.htm">Javadoc Location property page</a> on projects or JARs. Note that this external Javadoc documentation may not be up to date with the
-            Javadoc specified in the current code. You can create Javadoc documentation for source files in a Java project using the <a href="ref-export-javadoc.htm">Javadoc
-            export wizard</a>.&nbsp;
-          </td>
-          <td>
-            Shift + F2
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Open Type
-          </td>
-          <td>
-            Brings up the Open Type dialog to open a type in the editor.The Open Type selection dialog shows all types existing in the workspace.
-          </td>
-          <td>
-            Ctrl + Shift + T
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Open Type In Hierarchy
-          </td>
-          <td>
-            Brings up the Open Type dialog to open a type in the editor and the <a href="ref-type-hierarchy.htm">Type Hierarchy view</a>. The Open Type selection dialog
-            shows all types that exist in the workspace.
-          </td>
-          <td>
-            Ctrl + Shift + H
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Show in &gt; Package Explorer
-          </td>
-          <td>
-            Reveals the currently selected element (or the element surrounding the current cursor position) in the <a href="ref-view-package-explorer.htm">Package Explorer
-            view</a>.
-          </td>
-          <td>&nbsp;
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Show Outline
-          </td>
-          <td>
-            Opens the lightweight outliner for the currently selected type.
-          </td>
-          <td>Ctrl + O
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Go to Next Problem
-          </td>
-          <td>
-            Selects the next problem. Supported in the Java editor.
-          </td>
-          <td>
-            Ctrl + .
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Go to Previous Problem
-          </td>
-          <td>
-            Selects the previous problem. Supported in the Java editor.
-          </td>
-          <td>
-            Ctrl + ,
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Go to Last Edit Location
-          </td>
-          <td>
-            Reveal the location where the last edit occurred.
-          </td>
-          <td>
-            Ctrl + Q
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Go to Line
-          </td>
-          <td>
-            Opens an a dialog which allows entering the line number to which the editor should jump to. Editor only.
-          </td>
-          <td>
-            Ctrl + L
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img  src="../images/ngrelc.png" alt="Related concepts" border="0">
-      </p>
-      <p>
-      <a href="../concepts/concepts-6.htm">Java views</a><br>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelt.png" alt="Related tasks">
-      </p>
-      <p>
-    <a href="../tasks/tasks-73.htm">Opening an editor for a selected element</a><br>
-     <a href="../tasks/tasks-74.htm">Showing an element in the Package Explorer</a><br>
-     <a href="../tasks/tasks-75.htm">Opening a type in the Package Explorer</a><br>
-     <a href="../tasks/tasks-76.htm">Opening an editor on a type</a><br>
-     <a href="../tasks/tasks-77.htm">Opening a package</a><br>
-     <a href="../tasks/tasks-39.htm">Opening a type hierarchy on a Java element</a><br>
-     <a href="../tasks/tasks-40.htm">Opening a type hierarchy on the current text selection</a><br>
-     <a href="../tasks/tasks-41.htm">Opening a type hierarchy in the workbench</a><br>
-     <a href="../tasks/tasks-42.htm">Opening a type hierarchy in its own perspective</a><br>
-    </p> 
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-      </p>
-      <p>
-      <a href="ref-view-package-explorer.htm">Package Explorer view</a><br>
-	  <a href="ref-type-hierarchy.htm">Type Hierarchy view</a><br>
-	  <a href="ref-dialog-javadoc-location.htm">Javadoc Location properties</a><br>
-	  <a href="ref-export-javadoc.htm">Javadoc export wizard</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-project.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-project.htm
deleted file mode 100644
index 4919e0b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-project.htm
+++ /dev/null

@@ -1,179 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Project actions
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Project actions
-    </h1>
-	<p>
-        Project menu commands:
-	</p>
-    <table border="1" cellspacing="0" cellpadding="5">
-      <tbody>
-        <tr>
-          <th>
-            <p>
-              Name
-            </p>
-          </th>
-          <th>
-            <p>
-              Function
-            </p>
-          </th>
-          <td>
-            <strong>Keyboard Shortcut</strong>
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td align="left" valign="top">
-            <p>
-              Open Project
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Shows a dialog that can be used to select a closed project and open it
-            </p>
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Close Project
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Closes the currently selected projects
-            </p>
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Build All
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Builds the all projects in the workspace. This is an incremental build, meaning that the builder analyzes the changes since the last time of build and minimizes the
-              number of changed files.
-            </p>
-          </td>
-          <td>
-            Ctrl + B&nbsp;
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Build Project
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Builds the currently selected project. This is an incremental build, meaning that the builder analyzes the changes since the last time of build and minimizes the
-              number of changed files.
-            </p>
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Build Working Set
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Builds the projects contained in the currently selected working set. This is an incremental build, meaning that the builder analyzes the changes since the last time of build and minimizes the
-              number of changed files.
-            </p>
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Clean...
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Shows a dialog where the projects to be cleaned can be selected.
-            </p>
-          </td>
-          <td>&nbsp;
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Build Automatically
-          </td>
-          <td>
-           	If selected, all modified files are automatically rebuilt if saved. This is an incremental build, meaning that the builder analyzes the changes since the last time of build and minimizes the
-              number of changed files.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Generate Javadoc...
-          </td>
-          <td>
-            Opens the Generate Javadoc wizard on the currently selected project.
-          </td>
-          <td>&nbsp;
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Properties
-          </td>
-          <td>
-            Opens the property pages on the currently selected project.
-          </td>
-          <td>&nbsp;
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-       <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-       </p>
-       <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a><br>
-       <a href="../concepts/concepts-4.htm">Java builder</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-      </p>
-      <p>
-      <a href="../tasks/tasks-106.htm">Building a Java program</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-refactor.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-refactor.htm
deleted file mode 100644
index 75b8e77..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-refactor.htm
+++ /dev/null

@@ -1,323 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Refactor actions
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Refactor actions
-    </h1>
-	<p>
-        Refactor menu commands:
-	</p>
-    <table border="1" cellspacing="0" cellpadding="5">
-      <tbody>
-        <tr>
-          <th>
-            <p>
-              Name
-            </p>
-          </th>
-          <th>
-            <p>
-              Function
-            </p>
-          </th>
-          <td>
-            <strong>Keyboard Shortcut</strong>
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Rename
-            </p>
-          </td>
-          <td align="left" valign="top">
-            
-      <p> Starts the Rename refactoring dialog:&nbsp; Renames the selected element 
-        and (if enabled) corrects all references to the elements (also in other 
-        files). Is available on methods, method parameters, fields, local variables, 
-        types, type parameters, enum constants, compilation units, packages, source folders, projects and on a 
-        text selection resolving to one of these element types.&nbsp; </p>
-          </td>
-          <td>
-            Alt + Shift + R
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Move
-            </p>
-          </td>
-          
-    <td align="left" valign="top"> 
-      <p> Starts the Move refactoring dialog: Moves the selected elements and 
-        (if enabled) corrects all references to the elements (also in other files). 
-        Can be applied to one instance method (which can be moved to a component), 
-        one or more static methods, static fields, types, compilation units, packages, 
-        source folders and projects and on a text selection resolving to one of 
-        these element types.&nbsp; </p>
-          </td>
-          <td>
-            Alt + Shift + V
-          </td>
-        </tr>
-   <tr>
-    <td>Change Method Signature </td>
-    <td> 
-      <p>Starts the Change Method Signature refactoring dialog. Changes parameter 
-        names, parameter types, parameter order and updates all references to 
-        the corresponding method. Additionally, parameters can be removed or added 
-        and method return type as well as its visibility can be changed. This 
-        refactoring can be applied to methods or on text selection resolving to 
-        a method.&nbsp; </p>
-      </td>
-   <td>&nbsp;</td>
-  </tr>
-   <tr>
-     
-    <td>Convert Anonymous Class to Nested</td>
-     
-    <td> 
-      <p>Start the Convert Anonymous Class to Nested Class refactoring dialog. 
-        Helps you convert an anonymous inner class to a member class. This refactoring 
-        can be applied to anonymous inner classes.</p>
-      </td>
-     <td>&nbsp;</td>
-   </tr>
-   <tr>
-     
-    <td>Convert Member Type to Top Level</td>
-     
-    <td> 
-      <p>Starts the Convert Member Type to Top Level refactoring dialog. 
-        Creates a new Java compilation unit for the selected member type, updating 
-        all references as needed. For non-static member types, a field is added 
-        to allow access to the former enclosing instance, if necessary. 
-        This refactoring can 
-        be applied to member types or text resolving to a member type.</p>
-     </td>
-     <td>&nbsp;</td>
-   </tr>
-   <tr>
-     
-    <td>Push Down</td>
-     
-    <td> 
-      <p>Starts the Push Down refactoring dialog. Moves a set of methods and fields 
-        from a class to its subclasses. This refactoring can be applied to one 
-        or more methods and fields declared in the same type or on a text selection 
-        inside a field or method.&nbsp; </p>
-     </td>
-     <td>&nbsp;</td>
-   </tr>
-
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Pull Up
-            </p>
-          </td>
-          
-    <td align="left" valign="top"> 
-      <p> Starts the Pull Up refactoring wizard. Moves a field or method to a 
-        superclass of its declaring class or (in the case of methods) declares 
-        the method as abstract in the superclass. This refactoring can be applied 
-        on one or more methods, fields and member types declared in the same type 
-        or on a text selection inside a field, method or member type.&nbsp; </p>
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-   <tr>
-     
-    <td>Extract Interface</td>
-     
-    <td> 
-      <p>Starts the Extract Interface refactoring dialog. Creates a new interface 
-        with a set of methods and makes the selected class implement the interface, 
-        optionally changing references to the class to the new interface wherever 
-        possible. This refactoring can be applied to types.</p>
-     </td>
-     <td>&nbsp;</td>
-   </tr>
-   <tr>
-         
-    <td>Generalize Declared Type</td>
-     
-    <td> 
-      <p>Starts the Generalize Declared Type refactoring dialog.  Allows the user to choose
-      a supertype of the reference's current type.  If the reference can be safely changed to the
-      new type, it is. This refactoring can be applied to type references and declarations 
-        of fields, local variables, and parameters with reference types.</p>
-     </td>
-     <td>&nbsp;</td>
-   </tr>
-   <tr>
-     
-    <td>Use Supertype Where Possible</td>
-     
-    <td> 
-      <p>Starts the Use Supertype Where Possible refactoring dialog. Replaces occurrences 
-        of a type with one of its supertypes after identifying all places where 
-        this replacement is possible.This refactoring is available on types.</p>
-     </td>
-     <td>&nbsp;</td>
-   </tr>
-      <tr>
-     
-    <td>Infer Generic Type Arguments</td>
-     
-    <td> 
-      <p>Starts the Infer Generic Type Arguments refactoring dialog. Replaces raw type occurrences 
-        of generic types by parameterized types after identifying all places where 
-        this replacement is possible.This refactoring is available on projects, packages and types.</p>
-     </td>
-     <td>&nbsp;</td>
-   </tr>
-	        <tr align="left" valign="top">
-          
-    <td> Inline</td>
-          
-    <td> Starts the Inline refactoring dialog. Inlines local variables, methods 
-      or constants. This refactoring is available on methods, static final fields 
-      and text selections that resolve to methods, static final fields or local 
-      variables.</td>
-          <td>
-            Alt + Shift + I
-          </td>
-        </tr>
-	
-        <tr align="left" valign="top">
-          <td>
-            Extract Method
-          </td>
-          
-    <td> Starts the Extract Method refactoring dialog. Creates a new method containing 
-      the statements or expression currently selected and replaces the selection 
-      with a reference to the new method. You can use&nbsp;<em>Expand Selection 
-      to</em> from the <a href="ref-menu-edit.htm">Edit</a> menu to get a valid 
-      selection range.<br>
-             This feature is useful for cleaning up lengthy, cluttered, or overly-complicated methods.&nbsp;
-          </td>
-          <td>
-            Alt + Shift + M
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          
-    <td> Extract Local Variable </td>
-    <td> 
-      <p>Starts the Extract Variable refactoring dialog. Creates a new variable 
-        assigned to the expression currently selected and replaces the selection 
-        with a reference to the new variable. This refactoring is available on 
-        text selections that resolve to local variables. You can use&nbsp;<em>Expand 
-        Selection to</em> from the <a href="ref-menu-edit.htm">Edit</a> menu to 
-        get a valid selection range. </p>
-      </td>
-          <td>
-            Alt + Shift + L
-          </td>
-        </tr>
-   <tr>
-     
-    <td>Extract Constant</td>
-     
-    <td> 
-      <p>Starts the Extract Constant refactoring dialog. Creates a static final 
-        field from the selected expression and substitutes a field reference, 
-        and optionally rewrites other places where the same expression occurs. 
-        This refactoring is available on static final fields and text selections 
-        that resolve to static final fields.</p>
-     </td>
-     <td>&nbsp;</td>
-   </tr>
-   <tr>     
-   
-    <td>Introduce Factory</td>
-     
-    <td> 
-      <p>Starts the Introduce Factory refactoring dialog.  
-      This will create a new factory method, which will call a selected
-	  constructor and return the created object.  All references to the constructor will be
-     replaced by calls to the new factory method.
-        This refactoring is available on constructor declarations.</p>
-     </td>
-     <td>&nbsp;</td>
-   </tr>
-   <tr>     
-   
-    <td>Introduce Parameter</td>
-     
-    <td> 
-      <p>Starts the Introduce Parameter refactoring dialog. Replaces an expression
-      with a reference to a new method parameter, and updates all callers of the
-      method to pass the expression as the value of that parameter. 
-        This refactoring is available on text selections that resolve to expressions.</p>
-     </td>
-     <td>&nbsp;</td>
-   </tr>
-   <tr>
-     
-    <td>Convert Local Variable to Field</td>
-     
-    <td> 
-      <p>Start the Convert Local Variable to Field refactoring dialog. Turn a 
-        local variable into a field. If the variable is initialized on creation, 
-        then the operation moves the initialization to the new field's declaration 
-        or to the class's constructors. This refactoring is available on text 
-        selections that resolve to local variables.</p>
-     </td>
-     <td>&nbsp;</td>
-   </tr>
-        <tr>
-          
-    <td> Encapsulate Field </td>
-          
-    <td> Starts the Self Encapsulate Field refactoring dialog. Replaces all references 
-      to a field with getting and setting methods. Is applicable to a selected 
-      field or a text selection resolving to a field. </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      Refactoring commands are also available from the context menus in many views and the Java editor.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-      </p>
-      <p>
-       <a href="../concepts/concepts-9.htm">Refactoring support</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-      </p>
-      <p>
-      <a href="../tasks/tasks-80.htm">Refactoring</a><br>
-      <a href="../tasks/tasks-176.htm">Using Structured Selection</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-      </p>
-      <p>
-       <a href="ref-117.htm">Refactoring dialogs</a><br>
-       <a href="ref-154.htm">Extract Method Errors</a><br>
-       <a href="ref-13.htm">Java preferences</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-search.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-search.htm
deleted file mode 100644
index 3808fc5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-search.htm
+++ /dev/null

@@ -1,300 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Search actions
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Search actions
-    </h1>
-	<p>
-        Search menu commands:
-	</p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <tr>
-        <th>
-          <p>
-            Name
-          </p>
-        </th>
-        <th>
-          <p>
-            Function
-          </p>
-        </th>
-        <td>
-          <strong>Keyboard Shortcut</strong>
-        </td>
-      </tr>
-      <tr align="left" valign="top">
-        <td align="left" valign="top">
-          <p>
-            Search...
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Opens the search dialog
-          </p>
-        </td>
-        <td>
-          Ctrl + H
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            File...
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Opens the search dialog on the File search page
-          </p>
-        </td>
-        <td>&nbsp;
-          
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Help...
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Opens the search dialog on the Help search page
-          </p>
-        </td>
-        <td>&nbsp;
-          
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Java...
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Opens the search dialog on the Java search page
-          </p>
-        </td>
-        <td>&nbsp;
-          
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            References
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Finds all references to the selected Java element
-          </p>
-        </td>
-        <td>&nbsp;
-        </td>
-      </tr>
-      <tr>
-        <td>
-          Declarations
-        </td>
-        <td>
-          Finds all declarations of the selected Java element
-        </td>
-        <td>&nbsp;          
-        </td>
-      </tr>
-      <tr align="left" valign="top">
-        <td>
-          Implementors
-        </td>
-        <td>
-          Finds all implementors of the selected interface.
-        </td>
-        <td>&nbsp;
-        </td>
-      </tr>
-      <tr align="left" valign="top">
-        <td>
-          Read Access
-        </td>
-        <td>
-          Finds all read accesses to the selected field
-        </td>
-        <td>&nbsp;   
-        </td>
-      </tr>
-      <tr align="left" valign="top">
-        <td>
-          Write Access
-        </td>
-        <td>
-          Finds all write accesses to the selected field
-        </td>
-        <td>&nbsp;
-        </td>
-      </tr>
-
-      <tr>
-        <td valign="top">
-          <p>Occurrences in File</p>
-        </td>
-
-        <td valign="top">
-          <p>Finds all occurrences of the selected Java element in its file</p>
-        </td>
-        <td>
-        	Ctrl + Shift + U
-        </td>
-
-      </tr>
-
-    </table>
-	
-	<p>
-        Search Scopes Submenu:
-	</p>
-    <table border="1" cellspacing="0" cellpadding="5">
-      <tr>
-        <th>
-          <p>
-            Scope
-          </p>
-        </th>
-        <td>
-          <strong>Availability</strong>
-        </td>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Workspace
-          </p>
-        </td>
-        <td>
-          all elements
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Searches in the full workspace
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Project
-          </p>
-        </td>
-        <td>
-          all elements
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Searches in the project enclosing the selected element
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Hierarchy
-          </p>
-        </td>
-        <td>
-          types and members
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Searches in the type's hierarchy
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Workings Set
-          </p>
-        </td>
-        <td>
-          all elements
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Searches in a working set
-          </p>
-        </td>
-      </tr>
-    </table>
-    <p>
-      Scopes can be saved and names in the working set dialog. Existing instances of working sets 
-	  are also available in the Search Scope submenu
-    </p>
-    <p>
-      A Java search can also be conducted via the context menu of selected resources and elements in the following views:
-    </p>
-    <ul>
-      <li>
-        Package Explorer
-      </li>
-      <li>
-        Outline view
-      </li>
-      <li>
-        Search result view
-      </li>
-      <li>
-        Hierarchy view
-      </li>
-      <li>
-        Browsing views
-      </li>
-    </ul>
-    <p>
-      The search context menu is also available in the Java editor. The search is only performed if the currently selected text can be resolved to a Java element.
-    </p>
-    <p>
-      The type of the selected Java element defines which search context menus are available. The Java editor does not constrain the list of available Java searches based on the
-      selection.
-    </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-      </p>
-      <p>
-      <a href="../concepts/concepts-8.htm">Java search</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-      </p>
-      <p>
-      <a href="../tasks/tasks-103.htm">Conducting a Java search using the search dialog</a><br>
-       <a href="../tasks/tasks-104.htm">Conducting a Java search using pop-up menus</a>
-    </p>
-    <p>
-       <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-       </p>
-       <p>
-     <a href="../reference/ref-131.htm">Java Search tab</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-source.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-source.htm
deleted file mode 100644
index 4c041de..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-source.htm
+++ /dev/null

@@ -1,331 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Source actions
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Source actions
-    </h1>
-	<p>
-        Source menu commands:
-	</p>
-    <table border="1" cellspacing="0" cellpadding="5">
-      <tbody>
-        <tr>
-          <th>
-            <p>
-              Name
-            </p>
-          </th>
-          <th>
-            <p>
-              Function
-            </p>
-          </th>
-          <td>
-            <strong>Keyboard Shortcut</strong>
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td align="left" valign="top">
-            <p>
-              Toggle Comment
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Comments or uncomments all lines containing the current selection.
-            </p>
-          </td>
-          <td>
-            Ctrl + Shift + C
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td align="left" valign="top">
-            <p>
-              Add Block Comment
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Adds a block comment around all lines containing the current selection.
-            </p>
-          </td>
-          <td>
-            Ctrl + Shift + /
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Remove Block Comment
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Removes a block comment from all lines containing the current selection.
-            </p>
-          </td>
-          <td>
-            Ctrl + Shift + \
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Shift Right
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Increments the level of indentation of the currently select lines. Only activated when the selection covers multiple lines or a single whole line.
-            </p>
-          </td>
-          <td>
-           &nbsp;
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Shift Left
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Decrements the level of indentation of the currently select lines. Only activated when the selection covers multiple lines or a single whole line.
-            </p>
-          </td>
-          <td>
-         &nbsp;
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Format
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Uses the code formatter to format the current text selection. The formatting options are configured on the <a href="ref-17.htm">Code Formatter preference page</a>
-              (Window &gt; Preferences &gt; Java &gt; Code Style &gt; Formatter)
-            </p>
-          </td>
-          <td>
-            Ctrl + Shift + F
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Format Element
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Uses the code formatter to format the Java element comprising the current text selection. The Format Element action works on method and type level. The formatting options are configured on the <a href="ref-17.htm">Code Formatter preference page</a>
-              (Window &gt; Preferences &gt; Java &gt; Code Style &gt; Formatter)
-            </p>
-          </td>
-          <td>
-            &nbsp;
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Correct Indentation
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Corrects the indentation of the line denoted by the current text selection.
-            </p>
-          </td>
-          <td>
-          	Ctrl + I
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Sort Members
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Sorts the members of a type according to the sorting order specified in 
-              (Window &gt; Preferences &gt; Java &gt; Appearance &gt; Members Sort Order)
-            </p>
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Organize Imports
-          </td>
-          <td>
-            Organizes the import declarations in the compilation unit currently open or selected. Unnecessary import declarations are removed, and required import declarations are
-            ordered as specified in the <a href="ref-22.htm">Organize Imports preference page</a> (Window &gt; Preferences &gt; Java &gt; Organize Imports). Organize imports can be
-            executed on incomplete source and will prompt you when a referenced type name can not be mapped uniquely to a type in the current project.<br>
-             You can also organize multiple compilation units by invoking the action on a package or selecting a set of compilation units.
-          </td>
-          <td>
-            Ctrl + Shift + O
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Add Import
-          </td>
-          <td>
-            Creates an import declaration for a type reference currently selected. If the type reference if qualified, the qualification will be removed if possible. If the
-            referenced type name can not be mapped uniquely to a type of the current project you will be prompted to specify the correct type. Add Import tries to follow the
-            import order as specified in the <a href="ref-22.htm">Organize Import preference page</a>
-          </td>
-          <td>
-            Ctrl + Shift + M
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Override/Implement Methods
-          </td>
-          <td>
-            Opens the <a href="ref-dialog-override-method.htm">Override Method dialog</a> that allows you to override or implement a method in the current type. Available on types
-            or on a text selection inside a type.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Generate Getter and Setter
-          </td>
-          <td>
-            Opens the <a href="ref-dialog-gettersetter.htm">Generate Getters and Setters dialog</a> that allows you to create Getters and Setters for fields in the current type.
-            Available on fields and types or on a text selection inside a type.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Generate Delegate Methods
-          </td>
-          <td>
-            Opens the Generate Delegate Methods dialog that allows you to create method delegates for fields 
-            in the current type. Available on fields.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-          <tr>
-          <td>
-            Generate Constructor using Fields
-          </td>
-          <td>
-            Adds constructors which initialize fields for the currently selected types. Available on types, fields or on a text selection inside a type.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Add Constructor from Superclass
-          </td>
-          <td>
-            Adds constructors as defined in the super class for the currently selected types. Available on types or on a text selection inside a type.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Generate Element Comment
-          </td>
-          <td>
-          	Adds a comment to the selected element. See the	<a href="../reference/ref-preferences-code-templates.htm">Code templates preference page</a> 
-          	to specify the format of the generated comments. Available on types, fields, constructors, and methods.
-          </td>
-          <td>
-          Alt + Shift + J
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Surround with try/catch
-          </td>
-          <td>
-            For the selected statements all exception that have to be caught are evaluated. A try catch block is created around these expressions. You can use&nbsp;<em>Expand
-            Selection to</em> from the <a href="ref-menu-edit.htm">Edit</a> menu to get a valid selection range.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Externalize Strings
-          </td>
-          <td>
-            Opens the Externalize strings wizard. This wizards allows you to replace all strings in the code by statements accessing a property file.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Find Strings to Externalize
-          </td>
-          <td>
-            Shows a dialog presenting a summary of number of strings not externalized. Available on projects, source folders and packages.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-       <img  src="../images/ngrelc.png" alt="Related concepts" border="0"></p>
-       <p>
-    <a href="../concepts/concepts-7.htm">Java editor</a><br>
-     <a href="../concepts/cnls.htm">String externalization</a><br>
-     <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a></p>
-    <p>
-       <img border="0"  src="../images/ngrelt.png" alt="Related tasks"></p>
-       <p>
-      <a href="../tasks/tasks-54.htm">Using the Java editor</a><br>
-      <a href="../tasks/tasks-206.htm">Externalizing Strings</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference"></p>
-      <p>
-      <a href="ref-java-editor.htm">Java editor</a><br>
-       <a href="ref-21.htm">Java editor preferences</a><br>
-       <a href="ref-view-outline.htm">Java outline</a><br>
-       <a href="ref-24.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-appearance.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-appearance.htm
deleted file mode 100644
index 756e07d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-appearance.htm
+++ /dev/null

@@ -1,160 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>Appearance</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Appearance
-    </h1>
-    <p>
-      On this preference page, the appearance of Java elements in views can be configured. The options are:
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-          <th>
-            <p>
-              Default
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-               Show method return types
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, methods displayed in views show the return type.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Off
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Show method type parameters
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, methods displayed in views show the their type parameters.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              On
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Show members in Package Explorer
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, Java elements below the level of Java files and Class files are displayed as well.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              On
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Fold empty packages in hierarchical layout
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, empty packages which do not contain resources or other child elements are folded.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              On
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Compress package name segments
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, package names, except for the final segment, are compressed according to the compression pattern.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Off
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Stack views vertically in the Java Browsing perspective
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, views in Java Browsing perspective will be stacked vertically, rather than horizontally.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Off
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-      <p>
-      <a href="../concepts/concepts-6.htm">Java views</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-      <p>
-      <a href="../tasks/tasks-2.htm">Showing and hiding elements</a><br>
-       <a href="../tasks/tasks-194.htm">Showing full or compressed package names</a><br>
-    </p>
-    <p>
-     <img border="0"  src="../images/ngrelr.png" alt="Related reference"></p>
-     <p>
-     <a href="../reference/ref-view-package-explorer.htm">Package Explorer view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-code-generation.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-code-generation.htm
deleted file mode 100644
index ac89dcd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-code-generation.htm
+++ /dev/null

@@ -1,134 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Code style
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Code style
-    </h1>
-<p>The Code style preference page allows to configure naming conventions, style rules and comment settings.
-These preferences are used when new code has to be generated.
-</p>
-
-<h2 class="Head">Naming Conventions</h2>
-<p>The list defines the naming conventions for fields (static and non-static), parameters and local variables. For each variable type it is possible to configure a list of prefix or suffix or both.<br>
-Naming conventions are used by all actions and 'Quick Fix' proposals that create fields, parameters and local variables, in particular the <a href="../reference/ref-menu-source.htm">Source actions</a>.</p>
-<table border="1" cellspacing="0" cellpadding="5" width="600">
-	<thead>
-		<tr>
-			<th>
-			<p>Action</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Edit...</p>
-			</td>
-			<td valign="top">
-			<p>Opens a dialog to edit the list of prefix and suffixes for the currently selected variable type</p>
-			</td>
-		</tr>
-	</tbody>
-</table>
-
-<h2 class="Head">Code Conventions</h2>
-<p>The following settings specify how newly generated code should look like. The names of getter methods can be specified as well as the format of field accesses, method comments, annotations and exception variables.</p>
-<table border="1" cellspacing="0" cellpadding="5" width="600">
-	<thead>
-		<tr>
-			<th>
-			<p>Action</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-			<th>
-			<p>Default</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Qualify field accesses with 'this'</p>
-			</td>
-			<td valign="top">
-			<p>If selected, field accesses are always prefixed with 'this', regardless whether the name of the field is unique in the scope of the field access or not.</p>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Use 'is' prefix for getters returning boolean</p>
-			</td>
-			<td valign="top">
-			<p>If selected, the names of getter methods of boolean type are prefixed with 'is' rather than 'get'.</p>
-			</td>
-			<td valign="top">
-			<p>On</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Add comments for new methods and types</p>
-			</td>
-			<td valign="top">
-			<p>If selected, newly generated methods and types are automatically generated with comments where appropriate. See the
-			<a href="../reference/ref-preferences-code-templates.htm">Code templates preference page</a> to specify the format of the generated comments.</p>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Add '@Override' annotation for overriding methods</p>
-			</td>
-			<td valign="top">
-			<p>If selected, methods which override an already implemented method are annotated with an '@Override' annotation. See the
-			<a href="../reference/ref-preferences-compiler.htm">Compiler preference page</a> for settings related to annotations.</p>
-			</td>
-			<td valign="top">
-			<p>On</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Exception variable name in catch blocks</p>
-			</td>
-			<td valign="top">
-			<p>Specify the name of the exception variable declared in catch blocks.</p>
-			</td>
-			<td valign="top">
-			<p>e</p>
-			</td>
-		</tr>
-	</tbody>
-</table>
-
-<p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference"></p>
-      <p>
-      <a href="../reference/ref-menu-source.htm">Source actions</a><br>
-	  <a href="../reference/ref-java-editor.htm">Java editor</a><br>
-	  <a href="../reference/ref-21.htm">Java editor preferences</a><br>
-	  <a href="../reference/ref-preferences-compiler.htm">Java compiler preferences</a><br>
-	  <a href="../reference/ref-preferences-code-templates.htm">Code templates preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-code-templates.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-code-templates.htm
deleted file mode 100644
index f8c76af..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-code-templates.htm
+++ /dev/null

@@ -1,164 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Code templates
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Code templates
-    </h1>
-<p>This page lets you configure the format of newly generated code and comments.</p>
-
-<h2>Code and Comments</h2>
-<p>The code and comment page contains code templates that are used by actions that generate code. Templates contain variables that are substituted when the template is applied. Some variables are available in all templates, some are specific to templates.</p><table
-	border="1" cellspacing="0" cellpadding="5" width="600">
-	<thead>
-		<tr>
-			<th>
-			<p>Action</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Edit...</p>
-			</td>
-			<td valign="top">
-			<p>Opens a dialog to edit the currently selected code template.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Import...</p>
-			</td>
-			<td valign="top">
-			<p>Imports code templates from the file system.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Export...</p>
-			</td>
-			<td valign="top">
-			<p>Exports all selected code templates to the file system.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Export All...</p>
-			</td>
-			<td valign="top">
-			<p>Exports all code templates to the file system.</p>
-			</td>
-		</tr>
-	</tbody>
-</table>
-
-
-<h3>Comment templates</h3>
-<p>Comment templates can   contain the variable <b>${tags}</b> that will be substituted by the standard Javadoc tags (@param, @return..) for the commented element.
-The 'Overriding method' comment can additionally contain the template <b>${see_to_overridden}</b></p><ul>
-	<li>Getter comment: Template that specifies the comment for a getter method</li>
-	<li>Setter comment: Template that specifies the comment for a setter method</li>
-	<li>Constructor comment: Template that specifies the comment for new constructors</li>
-	<li>File comment: Template that specifies the header comment for newly created files. Note that this template can be referenced in the 'New Java File' template</li>
-	<li>Type  comment: Template that specifies the comment for new types. Note that this template can be referenced in the 'New Java File' template</li>
-	<li>Field  comment: Template that specifies the comment for new fields. Note that this template can be referenced in the 'New Java File' template</li>
-	<li>Method comment: Template that specifies the comment for new methods that do not override an method in a base class</li>
-	<li>Overriding method comment: Template that specifies the comment for new methods that override an method in a base class. By default the comment is defined as a non-Javadoc comment (Javadoc will replace this comment with the comment of the overridden method). You can change this to a real Javadoc comment if you want</li>
-</ul>
-
-<h3>New Java files template</h3>
-<p>The 'New Java files' template is used by the New Type wizards when a new Java file is created. The template can specify where comments are added. Note that the template can contain the variable <b>${typecomment}</b> that will be substituted by the evaluation of the type comment template.</p>
-
-<h3>Catch block body template</h3>
-<p>The 'Catch block body' template is used when a catch block body is
-created. It can use the variables <b>${exception_type}</b> and <b>${exception_var}</b>.</p>
-
-<h3>Method body template</h3>
-<p>The 'Method body'  templates are used when new method with a body is created that still needs some code to complete its functionality. It contains the variable
-<b>${body_statement}</b> that resolves to a return statement or/and a super-call. </p>
-
-<h3>Constructor body template</h3>
-<p>The 'Constructor body' templates are used when new method or constructor with body is
-created. It contains the variable <b>${body_statement}</b> that resolves  a super call.<b></b></p>
-
-<h3>Getter body template</h3>
-<p>The 'Getter body' templates are used when new getter method is created
-. It contains the variable <b>${body_statement}</b> that resolves to the appropriate return statement.<b></b></p>
-
-<h3>Setter body template</h3>
-<p>The 'Setter body' templates are used when new setter method is created
-. It contains the variable <b>${body_statement}</b> that resolves to the appropriate assignment statement.<b></b></p>
-
-<p>
-&nbsp;
-</p>
-<h2>Code Template dialog</h2>
-
-<p>The following fields and buttons appear in the dialog:</p>
-<table border="1" cellspacing="0" cellpadding="5" width="100%">
-	<thead>
-		<tr>
-			<th>
-			<p>Action</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top">
-			<p>Description</p>
-			</td>
-			<td valign="top">
-			<p>A description of the template</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Pattern</p>
-			</td>
-			<td valign="top">
-			<p>The template pattern.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Insert Variables...</p>
-			</td>
-			<td valign="top">
-			<p>Displays a list of pre-defined template specific variables.</p>
-			</td>
-		</tr>
-	</tbody>
-</table><p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0"
-	></p>
-	<p>
-<a href="../tasks/tasks-57.htm">Generating getters and setters</a>
-</p>
-
-<p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference"></p>
-      <p>
-      <a href="../reference/ref-menu-source.htm">Source actions</a><br>
-	  <a href="../reference/ref-java-editor.htm">Java editor</a><br>
-	  <a href="../reference/ref-21.htm">Java editor preferences</a><br>
-	  <a href="../reference/ref-preferences-templates.htm">Templates preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-compiler.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-compiler.htm
deleted file mode 100644
index f3c3924..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-compiler.htm
+++ /dev/null

@@ -1,1295 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Java Compiler
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Java Compiler
-    </h1>
-    <p>This preference page lets you configure the various settings related to compiling, building and checking Java source code.</p>
-    <p>
-      The Java compiler preferences are separated in the following sections:
-    </p>
-    <ul>
-      <li>
-        General
-      </li>
-      <li>
-        Building
-      </li>
-      <li>
-        Errors/Warnings
-      </li>
-    </ul>
-	
-    <h2 class="Head">
-      General
-    </h2>
-               <p><h3>JDK Compliance</h3></p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <tr>
-        <th>
-          <p>
-            Option
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-        <th>
-          <p>
-            Default
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Compiler compliance level
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Specifies the compiler compliance level.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            1.4
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Use default compliance settings
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            If enabled, the default compliance settings for the compiler compliance level are applied.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            On
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Generated class files compatibility
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Specifies the generated class file compatibility.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            1.2
-          </p>
-        </td>
-      </tr>
-        <tr>
-        <td valign="top">
-          <p>
-            Source compatibility
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Specifies the compatibility of the accepted source code.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            1.3
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Disallow identifiers called 'assert'
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever 'assert' is used as an identifier (reserved keyword in J2SE 1.4).
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-            <tr>
-        <td valign="top">
-          <p>
-            Disallow identifiers called 'enum'
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever 'enum' is used as an identifier (reserved keyword in J2SE 5.0).
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-          </table>
-          <p><h3>Classfile generation</h3></p>
-           <table border="1" cellspacing="0" cellpadding="5" width="100%">   
-      <tr>
-        <td valign="top">
-          <p>
-            Add variable attributes to generated class files
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            If enabled, variable attributes are added to the class file. This will enable local variable names to be displayed in the debugger (in places where variables are
-            definitely assigned) The resulting .class file is then bigger.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            On
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Add line number attributes to generated class files
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            If enabled, line number information is added to the class file. This will enable source code highlighting in the debugger.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            On
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Add source file name to generated class file
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            If enabled, the source file name is added to the class file. This will enable the debugger to present the corresponding source code.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            On
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Preserve unused local variables
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            If enabled, unused local variables (i.e. never read) are not stripped from the class file. If stripped this potentially alters debugging.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            On
-          </p>
-        </td>
-      </tr>
-       <tr>
-        <td valign="top">
-          <p>
-            Inline finally blocks
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            If enabled, finally blocks are inlined in the generated class files. This positively affects performance, but may result in larger class files.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Off
-          </p>
-        </td>
-      </tr>
-    </table>
-	
-    <h2 class="Head">
-      Building
-    </h2>
-                    <p><h3>General</h3></p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <tr>
-        <th>
-          <p>
-            Option
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-        <th>
-          <p>
-            Default
-          </p>
-        </th>
-      </tr>
-            <tr>
-        <td valign="top">
-          <p>
-            Maximum number of reported problems per compilation unit
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Specifies how many problems should be reported for a compilation unit.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            100
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Enable using exclusion patterns in source folders
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When disabled, no entry on a project classpath can be associated with
-			an exclusion pattern.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            On
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Enable using multiple output locations for source folders
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-             When disabled, no entry on a project classpath can be associated with
-	         a specific output location, preventing thus usage of multiple output locations.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            On
-          </p>
-        </td>
-      </tr>
-      </table>
-      <p><h3>Build path problems</h3></p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-          <tr>
-        <td valign="top">
-          <p>
-            Abort building on build path errors
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Allow to toggle the builder to abort if the classpath is invalid.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            On
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Incomplete build path
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Indicate the severity of the problem reported when an entry on the classpath does not exist,
-            is not legitimate or is not visible (e.g. a reference project is closed).
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Error
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Circular dependencies
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Indicate the severity of the problem reported when a project is involved in a cycle.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Error
-          </p>
-        </td>
-      </tr>
-       <tr>
-        <td valign="top">
-          <p>
-            Incompatible required binaries
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Indicated the severity of the problem reported when a project requires incompatible binaries.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Ignore
-          </p>
-        </td>
-      </tr>
-       </table>
-     <p><h3>Output folder</h3></p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <tr>
-        <td valign="top">
-          <p>
-            Duplicated resources
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Indicate the severity of the problem reported when more than one occurrence of a resource
-            is to be copied into the output location.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Scrub output folders when cleaning projects
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Indicate whether the Java Builder is allowed to clean the output folders
-	 	    when performing full build operations.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            On
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Filtered resources
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            A comma separated list of file patterns which are not copied to the output folder.&nbsp;
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            ''
-          </p>
-        </td>
-      </tr>
-    </table>
-    <h2 class="Head">
-      Errors/Warnings
-    </h2>
-     <p><h3>Code style</h3></p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <tr>
-        <th>
-          <p>
-            Option
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-        <th>
-          <p>
-            Default
-          </p>
-        </th>
-      </tr>
-            <tr>
-        <td valign="top">
-          <p>
-            Non-static access to a static member
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever a static field or method is accessed with an expression receiver.
-            A reference to a static member should be qualified with a type name.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-                  <tr>
-        <td valign="top">
-          <p>
-            Indirect access to a static member
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever a static field or method is indirectly accessed. A static field of an interface should
-            be qualified with the declaring type name.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-            <tr>
-        <td valign="top">
-          <p>
-            Unqualified access to instance field
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever it encounters a field access which is not qualified (eg. misses a 'this').
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Ignore
-          </p>
-        </td>
-      </tr>
-            <tr>
-        <td valign="top">
-          <p>
-            Undocumented empty block
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever it encounters an empty block statement with no explaining comment.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Ignore
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Access to a non-accessible member of an enclosing type
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever it emulates access to a non-accessible member of an enclosing type. Such accesses can have
-            performance implications.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Ignore
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Methods with a constructor name
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Naming a method with a constructor name is generally considered poor style programming. When enabling this option, the compiler will signal such scenario either as an
-            error or a warning.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-            <tr>
-        <td valign="top">
-          <p>
-            Usage of non-externalized strings
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning for non externalized String literal (i.e. non tagged with //$NON-NLS-&lt;n&gt;$).&nbsp;
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Ignore
-          </p>
-        </td>
-      </tr>
-          </table>
-     <p><h3>Potential programming problems</h3></p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <tr>
-        <td valign="top">
-          <p>
-            Serializable class without serialVersionUID
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever a type implementing 'java.io.Serializable' does not contain a serialVersionUID field.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Assignment has no effect (eg. 'x = x')
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever an assignment has no effect (eg. 'x = x').
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-            <tr>
-        <td valign="top">
-          <p>
-            Possible accidential boolean assigment (eg. 'if (a = b)')
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever if encounters a possible accidential boolean assignment (eg. 'if (a = b)').
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-                  <tr>
-        <td valign="top">
-          <p>
-            'finally' does not complete normally
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever a 'finally' statement does not complete normally (eg. contains a return statement).
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-            <tr>
-        <td valign="top">
-          <p>
-            Empty statement
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever it encounters an empty statement (eg. a superfluos semicolon).
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Ignore
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Using a char array in string concatenation
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever a char[] expression is used in String concatenations, 
-          </p>
-            <code>"hello" + new char[]{'w','o','r','l','d'}</code>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-                  <tr>
-        <td valign="top">
-          <p>
-            Hidden catch blocks
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Locally to a try statement, some catch blocks may hide others , eg.
-          </p>
-          <code>try { throw new java.io.CharConversionException();</code><br>
-           <code>} catch (java.io.CharConversionException e) {</code><br>
-           <code>} catch (java.io.IOException e) {}.</code><br>
-          <br>
-           
-          <p>
-            When enabling this option, the compiler will issue an error or a warning for hidden catch blocks corresponding to checked exceptions.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-      
-          </table>
-     <p><h3>Name shadowing and conflicts</h3></p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-              <tr>
-        <td valign="top">
-          <p>
-            Field declaration hides another field or variable
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabling this option, the compiler will issue an error or a warning if a field declaration hides another inherited field.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Ignore
-          </p>
-        </td>
-      </tr>
-                    <tr>
-        <td valign="top">
-          <p>
-            Local variable declaration hides another field or variable
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabling this option, the compiler will issue an error or a warning if a local variable declaration hides another field or variable.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Ignore
-          </p>
-        </td>
-      </tr>
-                    <tr>
-        <td valign="top">
-          <p>
-            Include constructor or setter method parameters
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabling this option, the compiler additionally will issue an error or a warning if a constructor or setter method parameter hides another field or variable.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Off
-          </p>
-        </td>
-      </tr>
-          <tr>
-        <td valign="top">
-          <p>
-            Type parameter hides another type
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabling this option, the compiler will issue an error or a warning if eg. a type parameter of an inner class hides an outer type.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Methods overridden but not package visible
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            A package default method is not visible in a different package, and thus cannot be overridden. When enabling this option, the compiler will signal such scenario either
-            as an error or a warning.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-
-      <tr>
-        <td valign="top">
-          <p>
-            Conflict of interface method with protected 'Object' method
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever an interface defines a method incompatible with a 
-            non-inherited Object method. Until this conflict is resolved, such an interface cannot be implemented, eg.
-          </p>
-          <code>interface I {</code><br>
-          <code>&nbsp;&nbsp;&nbsp;int clone();</code><br>
-          <code>}</code><br>
-          <br>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-          </table>
-     <p><h3>Name shadowing and conflicts</h3></p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-    
-      <tr>
-        <td valign="top">
-          <p>
-            Deprecated API
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will signal use of deprecated API either as an error or a warning.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Signal use of deprecated API inside deprecated code
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will signal use of deprecated API inside deprecated code.
-            The severity of the problem is controlled with option "Deprecated API".
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Off
-          </p>
-        </td>
-      </tr>
-            <tr>
-        <td valign="top">
-          <p>
-            Signal overriding or implementing deprecated method
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will signal overriding or implementing a deprecated method
-            The severity of the problem is controlled with option "Deprecated API".
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Off
-          </p>
-        </td>
-      </tr>
-                  <tr>
-        <td valign="top">
-          <p>
-            Forbidden reference (access rules)
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will signal a forbidden reference specified in the access rules.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Error
-          </p>
-        </td>
-      </tr>
-                  <tr>
-        <td valign="top">
-          <p>
-            Discouraged reference (access rules)
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will signal a discouraged reference specified in the access rules.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>          
-      </table>
-     <p><h3>Unnecessary code</h3></p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-                      <tr>
-        <td valign="top">
-          <p>
-            Local variable is never read
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning 
-            whenever a local variable is declared but never used within the its scope.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-                            <tr>
-        <td valign="top">
-          <p>
-           Parameter is never read
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning 
-            whenever a parameter is declared but never used within the its scope.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Ignore
-          </p>
-        </td>
-      </tr>     
-                                  <tr>
-        <td valign="top">
-          <p>
-           Check overriding and implementing methods
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler additionally will issue an error or a warning 
-            whenever a parameter is declared but never used within the its scope in overriding or implementing methods.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Off
-          </p>
-        </td>
-      </tr>     
-          <tr>
-        <td valign="top">
-          <p>
-            Unused imports
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning for unused import reference.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Unused local or private members
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever a local or private member is declared but never used within the same unit.            
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-            <tr>
-        <td valign="top">
-          <p>
-            Unnecessary else statement
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever it encounters an unnecessary else statement (eg. if (condition) return; else doSomething();).
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Ignore
-          </p>
-        </td>
-      </tr>
-            <tr>
-        <td valign="top">
-          <p>
-            Unnecessary cast or 'instanceof' operation
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever it encounters an unnecessary cast or 'instanceof' operation (eg. if (object instanceof Object) return;).
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Ignore
-          </p>
-        </td>
-      </tr>
-                  <tr>
-        <td valign="top">
-          <p>
-            Unnecessary declaration of thrown checked exception
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever it encounters an unnecessary declaration of a thrown exception.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Ignore
-          </p>
-        </td>
-      </tr>
-                                        <tr>
-        <td valign="top">
-          <p>
-           Check overriding and implementing methods
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler additionally will issue an error or a warning 
-            whenever it encounters an unnecessary declaration of a thrown exception in an overriding or implementing method.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Off
-          </p>
-        </td>
-      </tr>     
-    </table>
-     <p><h3>J2SE 5.0 options</h3></p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-                      <tr>
-        <td valign="top">
-          <p>
-           Unchecked generic type operation
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever it encounters an unchecked generic type operation.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-       <tr>
-        <td valign="top">
-          <p>
-           Generic type parameter declared with a final type bound
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever it encounters a type bound involving a final type.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-       <tr>
-        <td valign="top">
-          <p>
-           Inexact type match for vararg arguments
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever it encounters an 
-            inexact type match for vararg arguments.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-             <tr>
-        <td valign="top">
-          <p>
-          Boxing and unboxing conversions
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever it encounters a boxing or
-            unboxing conversion. Autoboxing may affects performance negatively.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Ignore
-          </p>
-        </td>
-      </tr>
-                 <tr>
-        <td valign="top">
-          <p>
-          Missing '@Override' annotation
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever it encounters a method overriding another
-            implemented method, and the '@Override' annotation is missing.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Ignore
-          </p>
-        </td>
-      </tr>
-                   <tr>
-        <td valign="top">
-          <p>
-          Missing '@Deprecated' annotation
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever it encounters a deprecated
-            type without additional '@Deprecated' annotation.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Ignore
-          </p>
-        </td>
-      </tr>
-                  <tr>
-        <td valign="top">
-          <p>
-          Annotation is used as super interface
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever it encounters a type implementing 
-            an annotation. Although possible, this is considered bad practice.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-                        <tr>
-        <td valign="top">
-          <p>
-          Not all enum constants covered on 'switch'
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever it encounters a switch statement which 
-            does not contain case statements for every enum constant of the referenced enum.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Ignore
-          </p>
-        </td>
-      </tr>
-                              <tr>
-        <td valign="top">
-          <p>
-          Unhandled warning tokens in '@SuppressWarnings'
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever it encounters an unhandled
-            warning token in a '@SuppressWarnings' annotation.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-                              <tr>
-        <td valign="top">
-          <p>
-          Enable '@SuppressWarnings' annotations
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will process '@SuppressWarnings' annotations.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            On
-          </p>
-        </td>
-      </tr>
-    </table>
-
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-      <p>
-      <a href="../concepts/concepts-4.htm">Java builder</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-      <p>
-      <a href="../tasks/tasks-106.htm">Building a Java program</a><br>
-       <a href="../tasks/tasks-110.htm">Working with build paths</a><br>
-       <a href="../tasks/tasks-JREs.htm">Working with JREs</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference"></p>
-      <p>
-      <a href="../reference/ref-15.htm">Classpath Variables preferences</a><br>
-	  <a href="../reference/ref-123.htm">Java Build Path properties</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-junit.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-junit.htm
deleted file mode 100644
index ddfcd61..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-junit.htm
+++ /dev/null

@@ -1,93 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      JUnit
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      JUnit
-    </h1>
-    <p>This page lets you configure the stack trace filter patterns for JUnit. The patterns are used in the <i>JUnit</i> view to control which entries are visible in stack traces.</p>
-    
-<table
-	border="1" cellspacing="0" cellpadding="5" width="600">
-	<thead>
-		<tr>
-			<th>
-			<p>Action</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Add Filter...</p>
-			</td>
-			<td valign="top">
-			<p>Allows to add a custom filter pattern. This action inserts an empty pattern which can be edited.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Add Class...</p>
-			</td>
-			<td valign="top">
-			<p>Allows to add classes to be filtered. This action opens the <strong>Open Type</strong> dialog to choose a type to be filtered in the stack traces.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Add Packages...</p>
-			</td>
-			<td valign="top">
-			<p>Allows to add packages to be filtered. This action opens a package selection dialog to choose the packages to be filtered in the stack traces.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Remove</p>
-			</td>
-			<td valign="top">
-			<p>Removes the currently selected stack trace filter pattern.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Enable All</p>
-			</td>
-			<td valign="top">
-			<p>Enables all stack trace filter patterns.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Disable All</p>
-			</td>
-			<td valign="top">
-			<p>Disables all stack trace filter patterns.</p>
-			</td>
-		</tr>
-	</tbody>
-</table>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-      <p>
-      <a href="../gettingStarted/qs-junit.htm">Using JUnit</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-148.htm">Open type</a>
-    </p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-task-tags.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-task-tags.htm
deleted file mode 100644
index 14d3d9f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-task-tags.htm
+++ /dev/null

@@ -1,104 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Task Tags
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Task Tags
-    </h1>
-    <p>
-      On this preference page, the task tags can be configured.
-      When the tag list is not empty, the compiler will issue a task marker whenever it encounters
-      one of the corresponding tag inside any comment in Java source code.
-      Generated task messages will include the tag and range until the next line separator or comment ending.
-    </p>
-    <p>
-        See the <a href="../reference/ref-preferences-compiler.htm">Compiler preference page</a> for information on how to enable task tags in your source code.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <caption>
-      </caption>
-      <tr>
-        <th>
-          <p>
-            Action
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            New...
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Adds a new task tag. In the resulting dialog, specify a name and priority for the new task tag.
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Remove
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Removes the selected task tag.
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Edit...
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Allows you to edit the selected task tag. In the resulting dialog, edit the name and/or priority for the task tag.
-          </p>
-        </td>
-      </tr>
-            <tr>
-        <td valign="top">
-          <p>
-            Default
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Sets the currently selected task tag as the default task tag. The default task tag is the one that is used in the 
-            code templates as specified on the <a href="../reference/ref-preferences-code-templates.htm">Code Templates preference page</a>.
-            The default task tag is displayed in bold font.
-          </p>
-        </td>
-      </tr>
-    </table>
-    <p>
-    Case sensitivity of the task tags can be specified at the bottom of the preference page using the option
-    <strong>Case sensitive task tag names</strong>.
-	</p>
-        <p>
-     <img border="0"  src="../images/ngrelr.png" alt="Related reference"></p>
-     <p>
-     <a href="../reference/ref-preferences-compiler.htm">Java compiler preferences</a><br>
-     <a href="../reference/ref-preferences-code-templates.htm">Code template preferences</a>
-    </p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-templates.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-templates.htm
deleted file mode 100644
index c1f973f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-preferences-templates.htm
+++ /dev/null

@@ -1,645 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Templates
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Templates
-    </h1>
-    <p>
-      The Templates preference page allows to create new and edit existing templates. A template is a convenience for the programmer to quickly insert often reoccurring source
-      code patterns.
-    </p>
-    <p>
-      The following buttons allow manipulation and configuration of templates:
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Action
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-              New...
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Opens a dialog to create a new template.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Edit...
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Opens a dialog to edit the currently selected template.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Remove
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Removes all selected templates.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Import...
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Imports templates from the file system.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Export...
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Exports all selected templates to the file system.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Export All...
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Exports all templates to the file system.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Enable All
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Enables all templates.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Disable All
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Disables all templates.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Use code formatter
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, the template is formatted according to the code formatting rules specified in the <a href="ref-17.htm">Code Formatter preferences</a>, prior to insertion.
-              Otherwise, the template is inserted as is, but correctly indented.
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <h2>
-      Template dialog
-    </h2>
-    <p>
-      Creating a new template and editing an existing template uses the same dialog, which is described here.
-    </p>
-    <p>
-      The following fields and buttons appear in the dialog:
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-              Name
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              The name of the template.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Context
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              The context determines where the template can be used and the set of available pre-defined template variables.
-            </p>
-            <dl>
-              <dt>
-                Java
-              </dt>
-              <dd>
-                The Java context
-              </dd>
-              <dt>
-                Javadoc
-              </dt>
-              <dd>
-                The Javadoc context
-              </dd>
-            </dl>
-          </td>
-        </tr>
-                <tr>
-          <td valign="top">
-            <p>
-              Automatically insert
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              If selected, code assist will automatically insert the template if it is the only proposal available at the caret position.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Description
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              A description of the template, which is displayed to the user when choosing the template.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Pattern
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              The template pattern.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Insert Variables...
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Displays a list of pre-defined context specific variables.
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <h2>
-      Template variables
-    </h2>
-    <p>
-      Both Java and Javadoc context define the following variables:
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Variable
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-              <strong>${cursor}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Specifies the cursor position when the template edit mode is left. This is useful when the cursor should jump to another place than to the end of the template on
-              leaving template edit mode.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <strong>${date}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to the current date.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <strong>${dollar}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to the dollar symbol '$'.
-            </p>
-            <p>
-              Alternatively, two dollars can be used: '$$'.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <strong>${enclosing_method}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to the name of the enclosing name.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <strong>${enclosing_method_arguments}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to a comma separated list of argument names of the enclosing method. This variable can be useful when generating log statements for many methods.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <strong>${enclosing_package}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to the name of the enclosing package.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <strong>${enclosing_project}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to the name of the enclosing project.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <strong>${enclosing_type}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to the name of the enclosing type.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <strong>${file}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to the name of the file.
-            </p>
-          </td>
-        </tr>
-                <tr>
-          <td valign="top">
-            <p>
-              <strong>${line_selection}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to content of all currently selected lines.
-            </p>
-          </td>
-        </tr>
-                <tr>
-          <td valign="top">
-            <p>
-              <strong>${primary_type_name}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to the name primary type of the current compilation unit.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <strong>${return_type}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to the return type of the enclosing method.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <strong>${time}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to the current time.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <strong>${user}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to the user name.
-            </p>
-          </td>
-        </tr>
-                <tr>
-          <td valign="top">
-            <p>
-              <strong>${word_selection}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to the content of the current text selection.
-            </p>
-          </td>
-        </tr>
-                <tr>
-          <td valign="top">
-            <p>
-              <strong>${year}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to the current year.
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      The Java context additionally defines the following variables:
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Variable
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-              <strong>${array}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to a proposal for a declared array name.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <strong>${array_element}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to a proposal for an element name of a declared array.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <strong>${array_type}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to a proposal for the element type of a declared array.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <strong>${collection}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to a proposal for a declared collection implementing <code>java.util.Collection</code>.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <strong>${index}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to a proposal for an undeclared array index iterator.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <strong>${iterator}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to a proposal for an undeclared collection iterator.
-            </p>
-          </td>
-        </tr>
-                <tr>
-          <td valign="top">
-            <p>
-              <strong>${iterable}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to a proposal for a declared iterable name.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <strong>${iterable_element}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to a proposal for an element name of a declared iterable.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <strong>${iterable_type}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to a proposal for the element type of a declared iterable.
-            </p>
-          </td>
-        </tr>
-                <tr>
-          <td valign="top">
-            <p>
-              <strong>${todo}</strong>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Evaluates to a proposal for the currently specified default task tag.
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-      <p>
-      <a href="../concepts/ctemplates.htm">Templates</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-      <p>
-      <a href="../tasks/tasks-171.htm">Using templates</a><br>
-       <a href="../tasks/tasks-203.htm">Writing your own templates</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference"></p>
-      <p>
-      <a href="../reference/ref-143.htm">Java content assist</a><br>
-      <a href="../reference/ref-preferences-task-tags.htm">Task tag preferences</a><br>
-      <a href="../reference/ref-preferences-code-templates.htm">Code templates preferences</a><br>
-      <a href="../reference/ref-preferences-code-generation.htm">Code style preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-properties-compiler.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-properties-compiler.htm
deleted file mode 100644
index 477992e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-properties-compiler.htm
+++ /dev/null

@@ -1,75 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>Java Compiler page</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-
-  <body>
-    <h1>Java Compiler page</h1>
-
-    <p>The options in this page indicate the compiler settings for a Java project.<br>
-     You can reach this page through the</p>
-
-    <ul>
-      <li>Java Compiler property page (File &gt; Properties &gt; Java Compiler) from the context menu on a created project or the <a href="ref-menu-file.htm">File
-      menu</a></li>
-    </ul>
-
-	<p> A project can either reuse workspace default settings or use its own custom settings.</p>
-
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-              Enable project specific settings
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Once selected, compiler settings can be configured for this project. 
-              All <a href="../reference/ref-preferences-compiler.htm">Java compiler preferences</a> can be customized.
-              At any time, it is possible to revert to workspace defaults, by using the button <strong>Restore Defaults</strong>.  
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-    <p>
-     <a href="../concepts/cbuildcp.htm">Build classpath</a><br>
-    </p>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-    <p>
-     <a href="../reference/ref-preferences-compiler.htm">Java compiler preferences</a><br>
-     <a href="../reference/ref-123.htm">Java Build Path properties</a><br>
-     <a href="../reference/ref-152.htm">Frequently asked questions on JDT</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-properties-task-tags.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-properties-task-tags.htm
deleted file mode 100644
index 60a145b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-properties-task-tags.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>Java Task Tags page</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-
-  <body>
-    <h1>Java Task Tags page</h1>
-
-    <p>The options in this page indicate the task tags for a Java project.<br>
-     You can reach this page through the</p>
-
-    <ul>
-      <li>Java task tags property page (File &gt; Properties &gt; Java Compiler &gt; Task Tags) from the context menu on a created project or the <a href="ref-menu-file.htm">File
-      menu</a></li>
-    </ul>
-
-	<p> A project can either reuse workspace default settings or use its own custom settings.</p>
-
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-              Enable project specific settings
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Once selected, task tags can be configured for this project as in the <a href="../reference/ref-preferences-task-tags.htm">Task tags preference page</a>.
-              At any time, it is possible to revert to workspace defaults, by using the button <strong>Restore Defaults</strong>.  
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-
-<p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-      </p>
-    <p>
-     <a href="../reference/ref-preferences-task-tags.htm">Task tag preferences</a>
-    </p>
-
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-showdetailpane.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-showdetailpane.htm
deleted file mode 100644
index 5955980..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-showdetailpane.htm
+++ /dev/null

@@ -1,30 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Show detail pane
-    </title>
-  </head>
-  <body>
-    <h1>
-      Show detail pane
-    </h1>
-    <p>
-      This command toggles showing the detail pane for the <strong>Variables view</strong>. The details pane shows the <em>toString</em> for selected objects. For primitive
-      variables, it shows the value.<br>
-       Code completion in the context of selected variable or the current stack frame is available as well. Evaluation can occur on expressions using <strong>Inspect</strong> and
-      <strong>Display</strong>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-      <p>
-      <a href="../tasks/tasks-138.htm">Evaluating expressions</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-type-hierarchy.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-type-hierarchy.htm
deleted file mode 100644
index 2da2216..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-type-hierarchy.htm
+++ /dev/null

@@ -1,244 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Type Hierarchy view
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Type Hierarchy view
-    </h1>
-    <p>
-      This view shows the hierarchy of a type. The Type Hierarchy view consists of two panes:
-    </p>
-    <ul>
-      <li>
-        Type Hierarchy tree pane
-      </li>
-      <li>
-        Member list pane (optional)
-      </li>
-    </ul>
-    <h2 class="Head">
-      Type Hierarchy tree pane toolbar buttons
-    </h2>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Command
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-              Previous Hierarchy Inputs
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              This menu displays a history of previously displayed type hierarchies.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Show the Type Hierarchy
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              This command displays the type in its full context (i.e., superclasses and subclasses) in the Hierarchy view. To see for which type the hierarchy is shown, hover
-              over the view title (e.g., &quot;Types&quot;).
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Show the Supertype Hierarchy
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              This command displays the supertypes and the hierarchy of all implemented interfaces of the type in the Hierarchy view. The tree starts at the selected type and
-              displays the result of traversing up the hierarchy.
-            </p>
-             <em>Note: The selected type is always at the top level, in the upper-left corner.</em>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Show the Subtype Hierarchy
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              This command displays the subtypes of the selected class and/or all implementors of the interface in the Hierarchy view. The tree starts at the selected type and
-              displays the result of traversing down the hierarchy
-            </p>
-             <em>Note: The selected type is always at the top level, in the upper-left corner.</em>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Vertical View Orientation
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Arranges the two panes vertically.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Horizontal View Orientation
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Arranges the two panes horizontally.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Hierarchy View Only
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Hides the member list pane.
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <h2 class="Head">
-      Member list pane toolbar buttons
-    </h2>
-    <p>
-      The member list pane displays the members of the currently selected type in the type hierarchy tree pane.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Command
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-              Lock View and Show Members in Hierarchy
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Shows the members implementing the selected method Only types implementing the method are shown.
-            </p>
-            <p>
-              When the view is locked, the member list pane no longer tracks the selection in the hierarchy pane above.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Show All Inherited Members
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Shows or hides all methods and fields inherited by base classes. When this option is set, the name of the type that defines the method is appended to the method
-              name.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Sort Members by the Defining Type
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Sorts the members according to the type in which they are defined.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Hide Fields
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Shows or hides the fields.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Hide Static Members
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Shows or hides the static fields and methods.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Hide Non-Public Members
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Shows or hides the static fields and methods.
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference"></p>
-      <p>
-      <a href="../reference/ref-24.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-view-outline.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-view-outline.htm
deleted file mode 100644
index 912ee79..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-view-outline.htm
+++ /dev/null

@@ -1,140 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Java outline
-    </title>
-  </head>
-  <body>
-    <h1>
-      Java outline
-    </h1>
-    <p>
-      This view displays an outline of the structure of the currently-active Java file in the editor area.
-    </p>
-    <h2 class="Head">
-      Toolbar buttons
-    </h2>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Command
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-              Go into Top Level Type
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Makes the top level type of the compilation unit the new input for this view.
-              Package declaration and import statements are no longer shown.
-            </p>
-         </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Sort
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              This option can be toggled to either sort the outline elements in alphabetical order or sequential order, as defined inside the compilation unit.
-            </p>
-             <em>Note: Static members are always listed first.</em>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Hide Fields
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Shows or hides the fields.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-             Hide Static Fields and Methods
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Shows or hides the static fields and methods.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Hide Non-Public Members
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Shows or hides the static fields and methods.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Hide Local Types
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Shows or hides the local types.
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-      <p>
-      <a href="../concepts/concepts-7.htm">Java editor</a><br>
-      <a href="../concepts/concepts-6.htm">Java views</a>
-    </p>
-    <p>
-       <img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-       <p>
-       <a href="../tasks/tasks-57.htm">Generating getters and setters</a><br>
-       <a href="../tasks/tasks-64.htm">Restoring a deleted workbench element</a><br>
-       <a href="../tasks/tasks-145.htm">Setting method breakpoints</a><br>
-       <a href="../tasks/tasks-191.htm">Showing and hiding members in Java views</a><br>
-       <a href="../tasks/tasks-192.htm">Showing and hiding override indicators</a><br>
-       <a href="../tasks/tasks-193.htm">Showing and hiding method return types in Java views</a><br>
-       <a href="../tasks/tasks-195.htm">Sorting elements in Java views</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ></p>
-      <p>
-      <a href="../reference/ref-dialog-override-method.htm">Override methods</a><br>
-       <a href="../reference/ref-24.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-view-package-explorer.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-view-package-explorer.htm
deleted file mode 100644
index 3d0efe3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-view-package-explorer.htm
+++ /dev/null

@@ -1,212 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Package Explorer view
-    </title>
-  </head>
-  <body>
-    <h1>
-      Package Explorer view
-    </h1>
-    <p>
-      The Package Explorer view, shown by default in the Java perspective, shows the Java element hierarchy of the Java projects in your workbench. It provides you with a
-      Java-specific view of the resources shown in the Navigator. The element hierarchy is derived from the project's build paths.
-    </p>
-    <p>
-      For each project, its source folders and referenced libraries are shown in the tree. You can open and browse the contents of both internal and external JAR files. Opening a
-      Java element inside a JAR opens the CLASS file editor, and if there is a source attachment for the JAR file, its corresponding source is shown.
-    </p>
-    <h1>
-      Toolbar buttons
-    </h1>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Command
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-              Back
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Navigates to the most recently-displayed state of the view with a different element at the top level.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Forward
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Navigates to the state of the view with a different element at the top level that was displayed immediately after the current state.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Up
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Navigates to the parent container of the package that is currently displayed at the top level in the view.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Collapse All
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Collapses all tree nodes.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Link with Editor
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-            Links the package explorer's selection to the active editor.</p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Select Working Set...
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Opens the <strong>Select Working Set</strong> dialog to allow selecting a working set.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Deselect Working Set
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Deselects the current working set.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Edit Active Working Set
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Opens the <strong>Edit Working Set</strong> wizard..
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Hide Non-Public Members
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Shows or hides the static fields and methods.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Hide Static Members
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Shows or hides the static fields and methods.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Hide Fields
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Shows or hides fields.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Filters...
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Opens the <strong>Java Element Filters</strong> dialog.
-            </p>
-            <p>
-              <a href="ref-dialog-java-element-filters.htm">See Java Element Filters dialog</a>
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ></p>
-      <p>
-       <a href="../concepts/concepts-6.htm">Java views</a><br>
-       <a href="../concepts/concepts-5.htm">Java perspectives</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-      <p>
-      <a href="../tasks/tasks-45.htm">Using the Package Explorer</a><br>
-      <a href="../tasks/tasks-2.htm">Showing and hiding elements</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ></p>
-      <p>
-      <a href="../reference/ref-dialog-java-element-filters.htm">Java Element Filters dialog</a><br>
-       <a href="../reference/ref-24.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-externalize-strings.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-externalize-strings.htm
deleted file mode 100644
index ec3ac43..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-externalize-strings.htm
+++ /dev/null

@@ -1,297 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Externalize Strings Wizard
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Externalize Strings Wizard
-    </h1>
-    <p>
-      The Externalize Strings wizard allows you to refactor a compilation unit such that strings used in the compilation unit can be translated to different languages. The wizard
-      consists of the following pages:
-    </p>
-    <ul>
-      <li>
-        String selection page
-      </li>
-      <li>
-        Translation settings page
-      </li>
-      <li>
-        Error page
-      </li>
-      <li>
-        Preview page
-      </li>
-    </ul>
-    <h2 class="Head">
-      String selection page
-    </h2>
-    <p>
-      This page specifies which strings are translated and which not.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Field
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-              Use Eclipse's string externalization mechanism
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              If unchecked the standard externalization mechanism is used, otherwise the new
-              <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-core-home/documents/3.1/message_bundles.html">Eclipse string externalization mechanism</a> is used.
-              <br><em>Note:</em> This field is only present if the project build path contains the <code>org.eclipse.osgi.util.NLS</code> class.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Enter common prefix for generated keys
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Specifies an optional prefix for every generated key. For example, the fully qualified name of the compilation unit could be used.
-            </p>
-          </td>
-        </tr>
-        
-        <tr>
-          <td valign="top">
-            <p>
-              Strings to externalize
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Displays the list of non-externalized strings with proposed keys and values.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Translate
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Marks the selected strings to be translated.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Never Translate
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Marks the selected strings as not to be translated.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Skip
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Marks the selected strings as to be skipped.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Edit Key...
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Opens a dialog for entering a new key.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Context
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Displays the occurrence of the string in the context of the compilation unit.
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <h2 class="Head">
-      Translation settings page
-    </h2>
-    <p>
-      This page specifies translation specific settings.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-              Package
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Specifies the destination package for the property file.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Property file name
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Specifies the property file name.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Create resource bundle accessor class in &quot;<var>package</var>&quot;
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, the wizard creates a class to access the language specific resource bundle.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Class name
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              The name of the class to access the resource bundle.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Use default substitution pattern
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, the wizard will use default substitution patterns.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Substitution pattern
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Specifies the source pattern to replace the string to externalize.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Add import declaration
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Specifies additional import declarations. This might be required depending on referenced types by the substitution pattern.
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <h2 class="Head">
-      Error page
-    </h2>
-    <p>
-      Displays a list of errors and warnings if any.
-    </p>
-    <h2 class="Head">
-      Preview page
-    </h2>
-    <p>
-      Displays a preview of the actions which will be performed on 'Finish'.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ></p>
-      <p>
-      <a href="../concepts/cnls.htm">String externalization</a><br>
-      <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-core-home/documents/3.1/message_bundles.html">Eclipse string externalization mechanism</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-      <p>
-      <a href="../tasks/tasks-206.htm">Externalizing Strings</a><br>
-      <a href="../tasks/tasks-180.htm">Using the Externalize Strings wizard</a>
-      <a href="../tasks/tasks-110.htm"></a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference"></p>
-      <p>
-      <a href="../reference/ref-menu-source.htm">Source actions</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-100.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-100.htm
deleted file mode 100644
index 8c4b92f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-100.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Undoing a refactoring operation
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Undoing a refactoring operation
-    </h1>
-    <p>
-      The most recent refactoring can be undone as long as you have not modified any Java elements in the workbench.
-      After performing a refactoring operation, you can build the
-      project, run and debug it, and execute any test cases, and still undo the refactoring action.
-    </p>
-    <p>
-      To undo the most recent refactoring, select <strong>Edit</strong> &gt; <strong>Undo</strong> from the menu bar.
-    </p>
-    <p>
-      <strong>Note</strong>: If the workbench contains unsaved files that affect undoing the refactoring, an error dialog appears.
-      The dialog contains a list of files that must be
-      reverted to their saved editions before the refactoring can be completed.
-    </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-9.htm">Refactoring support</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-82.htm">Refactoring without preview</a><br>
-       <a href="tasks-83.htm">Refactoring with preview</a><br>
-       <a href="tasks-84.htm">Previewing refactoring changes</a><br>
-       <a href="tasks-101.htm">Redoing a refactoring operation</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-       <a href="../reference/ref-117.htm">Refactoring dialog</a><br>
-       <a href="../reference/ref-13.htm">Java preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-101.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-101.htm
deleted file mode 100644
index 394500a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-101.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Redoing a refactoring operation
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Redoing a refactoring operation
-    </h1>
-    <p>
-      To redo a previously undone refactoring operation, select <strong>Edit</strong> &gt; <strong>Redo</strong> from the menu bar.
-    </p>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/concepts-9.htm">Refactoring support</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-82.htm">Refactoring without preview</a><br>
-       <a href="tasks-83.htm">Refactoring with preview</a><br>
-       <a href="tasks-84.htm">Previewing refactoring changes</a><br>
-       <a href="tasks-100.htm">Undoing a refactoring operation</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a><br>
-       <a href="../reference/ref-view-outline.htm">Java outline</a><br>
-       <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-       <a href="../reference/ref-117.htm">Refactoring dialogs</a><br>
-       <a href="../reference/ref-13.htm">Java preferences</a>
-    </p>
-   
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-102.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-102.htm
deleted file mode 100644
index 65ea911..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-102.htm
+++ /dev/null

@@ -1,19 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Searching
-    </title>
-  </head>
-  <body>
-    <h1>
-      Searching
-    </h1>
-   
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-103.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-103.htm
deleted file mode 100644
index d211dfb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-103.htm
+++ /dev/null

@@ -1,89 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <meta name="Author" content="Adam Kiezun">
-    <title>
-      Conducting a Java search using the Search dialog
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Conducting a Java search using the Search dialog
-    </h1>
-    <p>
-      Java search allows you to quickly find references to and declarations of Java elements.
-    </p>
-    <ul>
-      <li>
-        Open the Search dialog by either: 
-        <ul>
-          <li>
-            Clicking the <strong>Search</strong> button in the toolbar or
-          </li>
-          <li>
-            Pressing <strong>Ctrl+H</strong> or
-          </li>
-          <li>
-            Selecting <strong>Search &gt; Search...</strong> from the menu bar.
-          </li>
-        </ul>
-      </li>
-      <li>
-        Select the <strong>Java Search</strong> tab.
-      </li>
-      <li>
-        In the <strong>Search string</strong> field, type the string for which you want to search, using wildcards as needed.
-      </li>
-      <li>
-        You can also choose a previous search expression from the drop-down list. Selecting a previous search expression restores all values associated with that previous search
-        in the dialog.
-      </li>
-      <li>
-        Select the Java element type in the <strong>Search For</strong> area.
-      </li>
-      <li>
-        Narrow your search in the <strong>Limit To</strong> area, or select <strong>All occurrences</strong> to search for references
-        and declarations to a Java element.
-      </li>
-      <li>
-        Optionally, select the <strong>Search the JRE system libraries</strong> checkbox to include the JRE in your search.
-      </li>
-      <li>
-        Optionally, use the <strong>Scope</strong> area to narrow the scope of your search.
-      </li>
-      <li>
-        Click <strong>Search</strong>, and the search is carried out. The results are displayed in the Search view in the workbench window.
-      </li>
-      <li>
-        Optionally, use the Search view's view menu to switch between flat and hierarchical result presentation, or to configure filters.
-      </li>
-    </ul>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/concepts-8.htm">Java search</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="tasks-104.htm">Conducting a Java search using pop-up menus</a>
-    </p>
-    <p>
-      <br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-131.htm">Java search tab</a><br>
-       <a href="../reference/ref-menu-search.htm">Search menu</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-104.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-104.htm
deleted file mode 100644
index 5317b8b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-104.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Conducting a Java search using pop-up menus
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Conducting a Java search using pop-up menus
-    </h1>
-    <p>
-      Open the context menu on any Java element visible in a view.
-    </p>
-    <ul>
-      <li>
-        Search, Outline, and Hierarchy views: The selected Java element in these views can be searched for declarations and references.
-      </li>
-      <li>
-        Package Explorer: Packages, Java compilation units, types and their members can be searched for declarations and references.
-        If a compilation unit or CLASS file contains
-        more than one type, a dialog prompts you to choose one.
-      </li>
-    </ul>
-    The search pop-up menu is also available in the Java editor. If the selection in the Java editor can be resolved to a Java element,
-	then you can search for declarations and references. 
-    <p>
-      To conduct a search from a pop-up menu, follow these steps:
-    </p>
-    <ol>
-      <li>
-        Select a Java element (for example a Java compilation unit in the Package Explorer or a method in the Outline view) or some text in a Java editor.
-      </li>
-      <li>
-        From the selection's pop-up menu, navigate to the available Java searches. After you select a search to perform, the search progress is shown in a dialog. Note: in the
-        editor searches are available under the&nbsp;<strong><strong>Search</strong></strong> submenu.
-      </li>
-      <li>
-        You may stop the search process by clicking&nbsp;<strong><strong>Cancel</strong></strong> in the progress dialog.
-      </li>
-    </ol>
-    <p>
-      The type of the selected Java element defines which search pop-up menus are available. The Java editor does not constrain the list of available Java searches based on the
-      selection.
-    </p>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/concepts-8.htm">Java search</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-79.htm">Searching Java code</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-131.htm">Java search tab</a><br>
-       <a href="../reference/ref-menu-search.htm">Search menu</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-105.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-105.htm
deleted file mode 100644
index 8b293f0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-105.htm
+++ /dev/null

@@ -1,19 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Building
-    </title>
-  </head>
-  <body>
-    <h1>
-      Building
-    </h1>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-106.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-106.htm
deleted file mode 100644
index 24b9752..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-106.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Building a Java program
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Building a Java program
-    </h1>
-    <p>
-      A build command compiles workbench resources. A build command can be triggered in different ways:
-    </p>
-    <ul>
-      <li>
-        Building automatically: If auto build is turned on
-        (<strong>Project &gt; Build Automatically</strong>, or <strong>Window &gt; Preferences &gt; General &gt; Workspace &gt; Build automatically</strong>), then an
-        incremental build occurs every time you save a modified workbench resource.
-      </li>
-      <li>
-        Building manually: You can perform a manual build using a keyboard shortcut, a project's pop-up menu or the <strong>Project</strong> menu in the menu bar.
-      </li>
-    </ul>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/cbuildcp.htm">Build classpath</a><br>
-       <a href="../concepts/concepts-4.htm">Java builder</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="tasks-108.htm">Building automatically</a><br>
-       <a href="tasks-109.htm">Building manually</a><br>
-      <a href="tasks-113.htm">Adding a JAR file to the build path</a><br>
-       <a href="tasks-112.htm">Adding a class folder to the build path</a><br>
-       <a href="tasks-111.htm">Viewing and editing a project's build path</a><br>
-       <a href="tasks-110.htm">Working with build paths</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-123.htm">Java Build Path</a><br>
-       <a href="../reference/ref-preferences-compiler.htm">Java Compiler preferences</a>
-       <a href="../reference/ref-menu-project.htm">Project menu</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-107.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-107.htm
deleted file mode 100644
index 103534a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-107.htm
+++ /dev/null

@@ -1,72 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Viewing compilation errors and warnings
-    </title>
-  </head>
-  <body>
-    <h1>
-      Viewing compilation errors and warnings
-    </h1>
-    <p>
-      The workbench supports different ways to examine errors and warnings:
-    </p>
-    <ul>
-      <li>
-        Error ticks in Java views (e.g. Package Explorer)
-      </li>
-      <li>
-        Marker annotations in the editor
-      </li>
-      <li>
-        Problems in the Problems view
-      </li>
-      <li>
-        Tasks in the Tasks view
-      </li>
-    </ul>
-    <p>
-      If an expression you select to evaluate has a compilation error, it will be reported in the Scrapbook editor.
-    </p>
-    <p>
-      For example, if you type and select the (invalid) expression <em>System.println(&quot;hi&quot;)</em> in the editor and click <strong><strong>Run</strong></strong> in the
-      toolbar, the error message:
-    </p>
-    <p>
-      <em>The method println(java.lang.String) is undefined for the type java.lang.System</em>
-    </p>
-    <p>
-      is displayed in the editor at the point of the error.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-4.htm">Java builder</a><br>
-       <a href="../concepts/concepts-7.htm">Java editor</a><br>
-       <a href="../concepts/concepts-11.htm">Scrapbook</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-108.htm">Building automatically</a><br>
-       <a href="../tasks/tasks-109.htm">Building manually</a><br>
-       <a href="../tasks/tasks-126.htm">Running and debugging</a><br>
-       <a href="../tasks/tasks-executionArgs.htm">Setting execution arguments</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <p>
-      <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-108.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-108.htm
deleted file mode 100644
index af1bdf7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-108.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Building automatically
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Building automatically
-    </h1>
-    <p>
-      To enable automatic building:
-    </p>
-    <blockquote>
-      Enable <strong>Project &gt; Build Automatically</strong> or<br>
-      select the <strong>Window &gt; Preferences &gt; General &gt; Workspace &gt; Build automatically</strong> checkbox.
-    </blockquote>
-    To disable automatic building: 
-    <blockquote>
-      Disable <strong>Project &gt; Build Automatically</strong> or<br>
-      clear the <strong>Window &gt; Preferences &gt; General &gt; Workspace &gt; Build automatically</strong> checkbox.
-    </blockquote>
-    <p>
-       <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-4.htm">Java builder</a><br>
-       <a href="../concepts/cbuildcp.htm">Build class path</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-		<a href="tasks-106.htm">Building a Java program</a><br>
-		<a href="tasks-109.htm">Building manually</a><br>
-		<a href="tasks-107.htm">Viewing compilation errors and warnings</a><br>
-		<a href="tasks-110.htm">Working with build paths</a><br>
-      <a href="tasks-113.htm">Adding a JAR file to the build path</a><br>
-       <a href="tasks-112.htm">Adding a class folder to the build path</a><br>
-       <a href="tasks-111.htm">Viewing and editing a project's build path</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-123.htm">Java Build path</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-109.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-109.htm
deleted file mode 100644
index 81ded44..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-109.htm
+++ /dev/null

@@ -1,112 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Building manually
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Building manually
-    </h1>
-    <h2>
-      Incremental build
-    </h2>
-    <p>
-      The <strong>Build</strong> command performs an incremental build that compiles all
-      resources modified since the last build. To trigger an incremental build, either:
-    </p>
-    <ul>
-      <li>
-        press <strong>Ctrl+B</strong> or
-      </li>
-      <li>
-        from the menu bar, select <strong>Project &gt; Build All</strong>
-      </li>
-    </ul>
-    <h2>
-      Incremental project build
-    </h2>
-    <p>
-      You can also incrementally build single projects. Select the project that you want to build and:
-    </p>
-    <ul>
-      <li>
-        Select <strong>Project &gt; Build Project</strong> from the menu bar or
-      </li>
-      <li>
-        Select <strong>Build Project</strong> from the project's pop-up menu
-      </li>
-    </ul>
-    <h2>
-      Clean and rebuild from scratch (full build)
-    </h2>
-    <p>
-      To clean and rebuild all workbench resources that have an associated builder (e.g. Java projects),
-      select <strong>Project</strong> &gt; <strong>Clean...</strong> from the menu bar.
-      Then select <strong>Clean all projects</strong> and press <strong>OK</strong>.
-    </p>
-    <h2>
-      Clean and rebuild selected projects
-    </h2>
-    <p>
-      To clean and rebuild all resources contained in one or multiple projects:
-    </p>
-    <ul>
-      <li>
-        Select the projects
-      </li>
-      <li>
-        Select <strong>Project</strong> &gt; <strong>Clean...</strong> from the menu bar
-      </li>
-      <li>
-        Press <strong>OK</strong>
-      </li>
-    </ul>
-    <p>
-      or
-    </p>
-    <ul>
-      <li>
-        Select <strong>Project</strong> &gt; <strong>Clean...</strong> from the menu bar
-      </li>
-      <li>
-        Select <strong>Clean projects selected below</strong>
-      </li>
-      <li>
-        Select the projects to clean and press <strong>OK</strong>
-      </li>
-    </ul>
-          
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-4.htm">Java builder</a><br>
-       <a href="../concepts/cbuildcp.htm">Build classpath</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="tasks-106.htm">Building a Java program</a><br>
-       <a href="tasks-108.htm">Building automatically</a><br>
-       <a href="tasks-110.htm">Working with build paths</a><a href="tasks-110.htm"></a><br>
-      <a href="tasks-113.htm">Adding a JAR file to the build path</a><br>
-       <a href="tasks-112.htm">Adding a class folder to the build path</a><br>
-       <a href="tasks-111.htm">Viewing and editing a project's build path</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-123.htm">Java Build path</a><br>
-       <a href="../reference/ref-menu-project.htm">Project menu</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-109a.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-109a.htm
deleted file mode 100644
index 6e2dd3d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-109a.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Building circular projects
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Building circular projects
-    </h1>
-    <p>
-      To enable building circular projects:
-    </p>
-    <blockquote>
-      Select the <strong>Window &gt; Preferences &gt; Java &gt; Compiler &gt; Building</strong> page.<br>
-      Then set the option <strong>Circular dependencies</strong> to <strong>Warning</strong>.
-    </blockquote>
-    To disable building circular projects:
-    <blockquote>
-      Select the <strong>Window &gt; Preferences &gt; Java &gt; Compiler &gt; Building</strong> page.<br>
-      Then set the option <strong>Circular dependencies</strong> to <strong>Error</strong>.
-    </blockquote>
-    <p>
-      To enable building a single project involved in a cycle:
-    </p>
-    <blockquote>
-      Select the project, and from its pop-up menu, select <strong>Properties</strong>.<br>
-      In the Properties dialog, select the <strong>Java Compiler &gt; Building</strong> page.<br>
-      Then set the option <strong>Circular dependencies</strong> to <strong>Warning</strong>.
-    </blockquote>
-    To disable building a single project involved in a cycle:
-    <blockquote>
-      Select the project, and from its pop-up menu, select <strong>Properties</strong>.<br>
-      In the Properties dialog, select the <strong>Java Compiler &gt; Building</strong> page.<br>
-      Then set the option <strong>Circular dependencies</strong> to <strong>Error</strong>.
-    </blockquote>
-    <p>
-       <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-4.htm">Java builder</a><br>
-       <a href="../concepts/cbuildcp.htm">Build class path</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-		<a href="tasks-106.htm">Building a Java program</a><br>
-		<a href="tasks-109.htm">Building manually</a><br>
-		<a href="tasks-107.htm">Viewing compilation errors and warnings</a><br>
-		<a href="tasks-110.htm">Working with build paths</a><br>
-      <a href="tasks-113.htm">Adding a JAR file to the build path</a><br>
-       <a href="tasks-112.htm">Adding a class folder to the build path</a><br>
-       <a href="tasks-111.htm">Viewing and editing a project's build path</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-123.htm">Java Build path</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-109b.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-109b.htm
deleted file mode 100644
index 6d55034..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-109b.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Building without cleaning the output location
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Building without cleaning the output location
-    </h1>
-    <p>
-      To build projects without cleaning the output location:
-    </p>
-    <blockquote>
-      Select the <strong>Window &gt; Preferences &gt; Java &gt; Compiler &gt; Building</strong> page.<br>
-      Then set the <strong>Scrub output folders on full build</strong> checkbox.
-    </blockquote>
-    To build projects after cleaning the output location:
-    <blockquote>
-      Select the <strong>Window &gt; Preferences &gt; Java &gt; Compiler &gt; Building</strong> page.<br>
-      Then clear the <strong>Scrub output folders on full build</strong> checkbox.
-    </blockquote>
-    <p>
-      To build a single project without cleaning the output location:
-    </p>
-    <blockquote>
-      Select the project, and from its pop-up menu, select <strong>Properties</strong>.<br>
-      In the Properties dialog, select the <strong>Java Compiler &gt; Building</strong> page.<br>
-      Then set the <strong>Scrub output folders on full build</strong> checkbox.
-    </blockquote>
-      To build a single project after cleaning the output location:
-    <blockquote>
-      Select the project, and from its pop-up menu, select <strong>Properties</strong>.<br>
-      In the Properties dialog, select the <strong>Java Compiler &gt; Building</strong> page.<br>
-      Then clear the <strong>Scrub output folders on full build</strong> checkbox.
-    </blockquote>
-    <p>
-       <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-4.htm">Java builder</a><br>
-       <a href="../concepts/cbuildcp.htm">Build class path</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-		<a href="tasks-106.htm">Building a Java program</a><br>
-		<a href="tasks-109.htm">Building manually</a><br>
-		<a href="tasks-107.htm">Viewing compilation errors and warnings</a><br>
-		<a href="tasks-110.htm">Working with build paths</a><br>
-      <a href="tasks-113.htm">Adding a JAR file to the build path</a><br>
-       <a href="tasks-112.htm">Adding a class folder to the build path</a><br>
-       <a href="tasks-111.htm">Viewing and editing a project's build path</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-123.htm">Java Build path</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-11.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-11.htm
deleted file mode 100644
index 5a31269..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-11.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Creating Java elements
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Creating Java elements
-    </h1>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a><br>
-       <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="tasks-12.htm">Organizing Java projects</a><br>
-       <a href="tasks-13.htm">Creating a Java project as its own source container</a><br>
-       <a href="tasks-14.htm">Creating a Java project with source folders</a><br>
-       <a href="tasks-26.htm">Creating a new source folder</a><br>
-       <a href="tasks-15.htm">Creating a new Java package</a><br>
-       <a href="tasks-17.htm">Creating a new Java class</a><br>
-       <a href="tasks-17b.htm">Creating a new Java enum</a><br>
-       <a href="tasks-21.htm">Creating a new Java interface</a><br>
-       <a href="tasks-21b.htm">Creating a new Java annotation</a><br>
-       <a href="tasks-149.htm">Creating a Java scrapbook page</a><br>
-       <a href="tasks-114.htm">Adding a variable class path entry</a><br>
-       <a href="tasks-85.htm">Copying and moving Java elements</a><br>
-       <a href="tasks-117.htm">Defining a class path variable</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>	  
-       <a href="../reference/ref-121.htm">New Java Project wizard</a><br>
-       <a href="../reference/ref-128.htm">New Source Folder wizard</a><br>
-       <a href="../reference/ref-125.htm">New Java Package wizard</a><br>
-       <a href="../reference/ref-126.htm">New Java Class wizard</a><br>
-       <a href="../reference/ref-126b.htm">New Java Enum wizard</a><br>
-       <a href="../reference/ref-127.htm">New Java Interface wizard</a><br>
-       <a href="../reference/ref-127b.htm">New Java Annotation wizard</a><br>
-       <a href="../reference/ref-129.htm">New Scrapbook Page wizard</a><br>
-       <a href="../reference/ref-3.htm">Java Toolbar actions</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-110.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-110.htm
deleted file mode 100644
index 2f18626..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-110.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Working with build paths
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Working with build paths
-    </h1>
-    <p>
-      Setting up the proper Java build path is an important task when doing Java development.
-      Without the correct Java build path, you cannot compile your code. In addition, you
-      cannot search or look at the type hierarchies for Java elements.
-    </p>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/concepts-4.htm">Java builder</a><br>
-       <a href="../concepts/cbuildcp.htm">Build classpath</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="tasks-111.htm">Viewing and editing a project's build path</a><br>
-      <a href="tasks-113.htm">Adding a JAR file to the build path</a><br>
-       <a href="tasks-112.htm">Adding a class folder to the build path</a><br>
-       <a href="tasks-31.htm">Adding source code as individual files</a><br>
-       <a href="tasks-120.htm">Assigning the default JRE for the workbench</a><br>
-       <a href="tasks-106.htm">Building a Java program</a><br>
-       <a href="tasks-108.htm">Building automatically</a><br>
-       <a href="tasks-109.htm">Building manually</a><br>
-       <a href="tasks-124.htm">Choosing a JRE for launching a project</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-123.htm">Java Build path</a><br>
-       <a href="../reference/ref-19.htm">Installed JREs preference page</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-111.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-111.htm
deleted file mode 100644
index c4628bc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-111.htm
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Viewing and editing a project's Java build path
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Viewing and editing a project's Java build path
-    </h1>
-    <p>
-      A project's Java build path can either be defined when creating the project with the <strong>New Wizard</strong> or later in the project's property dialog. The Java
-      build path settings dialog is the same in both cases. To view and edit a project's Java build path, follow these steps:
-    </p>
-    <ol>
-      <li>
-        Select the project you want to view or edit
-      </li>
-      <li>
-        From the project's pop-up menu, select <strong>Properties</strong>
-      </li>
-      <li>
-        Select the <strong>Java Build Path</strong> page
-      </li>
-      <li>
-        Define the source entries for the build path on the <strong>Source</strong> page: 
-        <ul>
-          <li>
-             Click the <strong>Add Folder</strong> button to add source folders to the Java build path.<br>
-             The <strong>Remove</strong> button removes the selected folder(s) from the build path.<br>
-             <strong>Edit</strong> lets you modify the selected entry.
-          </li>
-        </ul>
-      </li>
-      <li>
-        On the <strong>Projects</strong> page, identify the other projects that are required for building this project. The list shows all the existing Java projects from the
-        workbench. <strong>Note</strong>: Each selected project is automatically added to the list of referenced projects.
-      </li>
-      <li>
-        On the <strong>Libraries</strong> page, define the libraries required by your project. Libraries come in different forms. There are buttons for adding a library in each
-        form. By default, each Java project has a 'JRE System Library' entry on the build path. This entry stands for the workbench's default JRE.
-      </li>
-      <li>
-        On the <strong>Order and Export</strong> page, define the Java build path order. The recommended ordering is to have source entries before the library entries and the
-        required projects.
-      </li>
-    </ol>
-    <p>
-       <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-4.htm">Java builder</a><br>
-       <a href="../concepts/cbuildcp.htm">Build classpath</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-113.htm">Adding a JAR file to the build path</a><br>
-       <a href="tasks-112.htm">Adding a class folder to the build path</a><br>
-       <a href="tasks-114.htm">Adding a variable class path entry</a><br>
-       <a href="tasks-106.htm">Building a Java program</a><br>
-       <a href="tasks-110.htm">Working with build paths</a><br>
-       <a href="tasks-JREs.htm">Working with JREs</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-123.htm">Java Build path</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-112.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-112.htm
deleted file mode 100644
index 606698b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-112.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Adding a class folder to the build path
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Adding a class folder to the build path
-    </h1>
-    <p>
-      A class folder is an ordinary folder containing a collection of class files inside the workbench. Use this format for a library when a library is not packaged as a JAR file. A
-      the class folder is the root of the package folders so that all class files are by placed according to their package declaration.
-    </p>
-      To add a class folder to the project's build class path, follow these steps: 
-    <ol>
-      <li>
-        Select the project, and from its context menu, select <strong>Properties</strong>.
-      </li>
-      <li>
-        In the Properties dialog, select the <strong>Java Build Path</strong> page.
-      </li>
-      <li>
-        Click the <strong>Libraries</strong> tab.
-      </li>
-      <li>
-        Click the <strong>Add Class Folder</strong> button.
-      </li>
-      <li>
-        In the dialog that appears, select a folder to add press the <strong>OK</strong> button.
-      If you want to add a not yet existing folder use first  <strong>Create
-	New Folder.</strong> After the folder is created select the new folder and press the <strong>OK</strong> button</li>
-    </ol>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" ><a href="../concepts/concepts-4.htm"></a>
-    </p>
-    <p>
-      <a href="../concepts/concepts-4.htm">Java builder</a><br>
-       <a href="../concepts/cbuildcp.htm">Build classpath</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-113.htm">Adding a JAR file to the build path</a><br>
-       <a href="tasks-106.htm">Building a Java program</a><br>
-       <a href="tasks-108.htm">Building automatically</a><br>
-       <a href="tasks-109.htm">Building manually</a><br>
-       <a href="tasks-111.htm">Viewing and editing a project's build path</a><br>
-       <a href="tasks-110.htm">Working with build paths</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><a href="../reference/ref-123.htm"></a>
-    </p>
-    <p>
-      <a href="../reference/ref-123.htm">Java Build Path</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-113.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-113.htm
deleted file mode 100644
index 13e7220..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-113.htm
+++ /dev/null

@@ -1,80 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Adding a JAR file to the build path
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Adding a JAR file to the build path
-    </h1>
-    <p>
-      You can add a JAR file stored either in the workbench or anywhere in your file system to the build class path.
-    </p>
-    <p>
-       To add a JAR to your build class path follow these steps:
-    </p>
-    <ol>
-      <li>
-        Select the project, and from its pop-up menu, select <strong>Properties</strong>.
-        In the Properties dialog, select the <strong>Java Build Path</strong> page.<br>
-         Click the <strong>Libraries</strong> tab.<br>
-         You can now either add a JAR file which is contained in your workspace or which is somewhere else:
-   
-        <ul>
-          <li>
-            to add a JAR file which is inside your workspace click the <strong>Add JARs</strong> button
-          </li>
-          <li>
-            to add an external JAR file click the <strong>Add External JARs</strong> button
-          </li>
-        </ul>
-      </li>
-      <li>
-        In the dialog that appears, select the JAR file that you want to add.
-      Note that you can add multiple JARs at once.</li>
-    </ol>
-    <p>
-       Alternatively, to add an external JAR to your build class path follow these steps:
-    </p>
-    <ol>
-      <li>
-        Select the project, and from its pop-up menu, select <strong>Build Path &gt; Add external archives</strong>.
-      </li>
-      <li>
-        In the dialog that appears, select the JAR file that you want to add.
-      Note that you can add multiple JARs at once.</li>
-    </ol>
-    
-    
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/concepts-4.htm">Java builder</a><br>
-       <a href="../concepts/cbuildcp.htm">Build classpath</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-112.htm">Adding a class folder to the build path</a><br>
-       <a href="tasks-106.htm">Building a Java program</a><br>
-       <a href="tasks-108.htm">Building automatically</a><br>
-       <a href="tasks-109.htm">Building manually</a><br>
-       <a href="tasks-33.htm">Creating a new JAR file</a><br>
-       <a href="tasks-111.htm">Viewing and editing a project's build path</a><br>
-       <a href="tasks-110.htm">Working with build paths</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-123.htm">Java Build path</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-114.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-114.htm
deleted file mode 100644
index 268fcad..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-114.htm
+++ /dev/null

@@ -1,75 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Adding a classpath variable to the build path
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Adding a classpath variable to the build path
-    </h1>
-    <p>
-      To add a classpath variable to the Java build path of a project, follow these steps:
-    </p>
-    <ol>
-      <li>
-        Select the project to which you want to add the classpath&nbsp;variable
-      </li>
-      <li>
-        From the project's pop-up menu, select <strong>Properties</strong><br>
-      </li>
-      <li>
-        In the Properties page, select the <strong>Java Build Path</strong> page.
-      </li>
-      <li>
-        On the <strong>Libraries</strong> tab, click <strong>Add Variable</strong> for adding a variable that refers to a JAR file.<br>
-         The <strong>New Variable Classpath Entry</strong> dialog appears which shows all available classpath variables.
-         <p><img src="../images/classpathVar.png"  alt="Classpath variable dialog"></p>
-      </li>
-      <li>
-        Select a classpath variable then press <strong>OK</strong>.
-      <ul>
-		<li>
-        If the variable resolves to a folder, you can specify a path extension that points to a JAR.
-        To do this press the <strong>Extend...</strong> button. </li>
-		<li>Press <strong>Edit...</strong> to create a new classpath variable or edit an existing one.
-      </li>
-	</ul>
-	</li>
-</ol>
-    <p>
-      <strong>Hint</strong>: You can add multiple variable entries at once to the Java build path:
-      Select more than one variable in the <strong>New Variable Classpath
-      Entry</strong> dialog, or multiple JAR files in the <strong>Variable Extension</strong> dialog.<br>
-    </p>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/cclsspthv.htm">Classpath variables</a><br>
-       <a href="../concepts/cbuildcp.htm">Build classpath</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-116.htm">Attaching source to a class path variable</a><br>
-       <a href="tasks-11.htm">Creating Java elements</a><br>
-       <a href="tasks-117.htm">Defining a class path variable</a><br>
-       <a href="tasks-118.htm">Deleting a class path variable</a><br>
-       <a href="tasks-111.htm">Viewing and editing a project's build path</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-15.htm">Classpath Variables preference page</a><br>
-       <a href="../reference/ref-123.htm">Build path properties page</a><br>
-       &nbsp;
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-115.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-115.htm
deleted file mode 100644
index 2d80431..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-115.htm
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Attaching source to a JAR file
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Attaching source to a JAR file
-    </h1>
-    <p>
-      You can attach source to a JAR file to enable source-level stepping and browsing of classes contained in a binary JAR file.
-      Unless its source code is attached to a JAR file
-      in the workbench, you will not be able to view the source for the JAR file.
-    </p>
-    <p>
-      To attach source to a JAR file:
-    </p>
-    <ol>
-      <li>
-        Select the project, and from its pop-up menu, select <strong>Properties</strong>.<br>
-         In the Properties dialog, select the Java Build Path page.
-      </li>
-      <li>
-        On the <strong>Libraries</strong> tab, select the JAR file to which you want to attach source.<br>
-         Expand the node by clicking on the plus and select the node <em>Source Attachment</em>.
-         Click the <strong>Edit </strong> button to bring up the source attachment dialog.
-      </li>
-      <li>
-        Fill in the <strong>Location path</strong> field depending on the location, choose between the workspace, an external file or external folder.
-      </li>
-      <li>
-        Click <strong>OK</strong>.
-      </li>
-    </ol>
-    <p>
-      or
-    </p>
-    <ol>
-      <li>
-        Select the JAR file in the Package Explorer, and from its pop-up menu, select <strong>Properties</strong>.<br>
-         In the Properties dialog, select the <strong>Java Source Attachment</strong> page.
-      </li>
-      <li>
-        Fill in the <strong>Location path</strong> field depending on the location, choose between the workspace, an external file or external folder.
-      </li>
-      <li>
-        Click <strong>OK</strong> .
-      </li>
-    </ol>
-    
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-116.htm">Attaching source to variables</a><br>
-       <a href="tasks-33.htm">Creating a new JAR file</a><br>
-       <a href="tasks-136.htm">Stepping through the execution of a program</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-123.htm">Java Build Path</a><br>
-       <a href="../reference/ref-124.htm">Source Attachment dialog</a><br>
-       &nbsp;
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-115a.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-115a.htm
deleted file mode 100644
index f1b5b6d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-115a.htm
+++ /dev/null

@@ -1,78 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Attaching source to a class folder
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Attaching source to a class folder
-    </h1>
-    <p>
-      You can attach source to a class folder to enable source-level stepping and browsing of classes contained in a class folder.
-      Unless its source code is attached to a class folder in the workbench, you will not be able to view the source for the class folder.
-    </p>
-    <p>
-      To attach source to a class folder:
-    </p>
-    <ol>
-      <li>
-        Select the project, and from its pop-up menu, select <strong>Properties</strong>.<br>
-         In the Properties dialog, select the Java Build Path page.
-      </li>
-      <li>
-        On the <strong>Libraries</strong> tab, select the class folder to which you want to attach source.<br>
-         Expand the node by clicking on the plus and select the node <em>Source Attachment</em>.
-         Click the <strong>Edit </strong> button to bring up the source attachment dialog.
-      </li>
-      <li>
-        Fill in the <strong>Location path</strong> field depending on the location, choose between the workspace, an external file or external folder.
-      </li>
-      <li>
-        Click <strong>OK</strong>.
-      </li>
-    </ol>
-    <p>
-      or
-    </p>
-    <ol>
-      <li>
-        Select the class folder in the Package Explorer, and from its pop-up menu, select <strong>Properties</strong>.<br>
-         In the Properties dialog, select the <strong>Java Source Attachment</strong> page.
-      </li>
-      <li>
-        Fill in the <strong>Location path</strong> field depending on the location, choose between the workspace, an external file or external folder.
-      </li>
-      <li>
-        Click <strong>OK</strong> .
-      </li>
-    </ol>
-    
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-116.htm">Attaching source to variables</a><br>
-       <a href="tasks-33.htm">Creating a new JAR file</a><br>
-       <a href="tasks-136.htm">Stepping through the execution of a program</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-123.htm">Java Build Path</a><br>
-       <a href="../reference/ref-124.htm">Source Attachment dialog</a><br>
-       &nbsp;
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-116.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-116.htm
deleted file mode 100644
index a4b5850..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-116.htm
+++ /dev/null

@@ -1,78 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Attaching source to a class path variable
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Attaching source to a class path variable
-    </h1>
-    <p>
-      When attaching source for a class path variable entry, both the path to the&nbsp;<strong>Archive</strong> and the <strong>Root Path</strong> must be defined by
-      variables. Follow these steps to make a source attachment for a variable:
-    </p>
-    <ol>
-      <li>
-        Select the project, and from its pop-up menu, select <strong>Properties</strong>.<br>
-         In the Properties dialog, select the Java Build Path page.
-      </li>
-      <li>
-        On the <strong>Libraries</strong> tab, select the class path variable to which you want to attach source.<br>
-         Expand the node by clicking on the plus and select the node <em>Source Attachment</em>. Click the <strong>Edit </strong> button to bring up the source attachment dialog.
-      </li>
-      <li>
-        In <strong>Location variable path</strong> field, use a variable to define the location of the archive. Use
-        the <strong>Variable</strong> button to select an existing variable and the <strong>Extension</strong> button to append an
-        optional path extension.</li>
-      <li>
-        Click <strong>OK</strong>.
-      </li>
-    </ol>
-    <p>
-      or
-    </p>
-    <ol>
-      <li>
-        Select the JAR file in the Package Explorer, and from its pop-up menu, select <strong>Properties</strong>.<br>
-         In the Properties dialog, select the <strong>Java Source Attachment</strong> page.
-      </li>
-      <li>
-        In <strong>Location variable path</strong> field, use a variable to define the location of the archive. Use
-        the <strong>Variable</strong> button to select an existing variable and the <strong>Extension</strong> button to append an
-        optional path extension.</li>
-      <li>
-        Click <strong>OK</strong> .
-      </li>
-    </ol>
-    
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/cclsspthv.htm">Classpath variables</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-114.htm">Adding a variable class path entry</a><br>
-       <a href="tasks-117.htm">Defining a class path variable</a><br>
-       <a href="tasks-118.htm">Deleting a class path variable</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-15.htm">Classpath Variables preference page</a><br>
-       <a href="../reference/ref-124.htm">Source Attachment dialog</a><br>
-       &nbsp;
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-117.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-117.htm
deleted file mode 100644
index 0587eb9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-117.htm
+++ /dev/null

@@ -1,74 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Defining a classpath variable
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Defining a classpath variable
-    </h1>
-    <p>
-       Classpath variables are stored global to the workbench; in other words, all projects in the workbench can share the classpath variables.
-    </p>
-    <p>
-      To add or change a class path variable, follow these steps:
-    </p>
-    <ol>
-      <li>
-        From the menu bar, select <strong>Window</strong> &gt; <strong>Preferences</strong>.<br>
-        Select the <strong>Java &gt; Build Path &gt; Classpath Variables</strong> page.
-      </li>
-      <li>
-        This page allows you to add, edit, or remove class path variables. 
-        <ul>
-          <li>
-            To add a new class path variable, click the <strong>New...</strong> button. The New Variable Entry page opens.
-          </li>
-          <li>
-            To edit an existing class path variable, select the variable in the <strong>Defined class path variables</strong> list and click
-            the <strong>Edit...</strong> button. The Edit Variable Entry page opens. <em>Note: The reserved class path variables, JRE_LIB, JRE_SRC, and
-            JRE_SRCROOT cannot be edited in this page. To change them, change the default workbench JRE on the Installed JREs page (<strong>Window</strong> &gt;
-            <strong>Preferences</strong> &gt; <strong>Java</strong> &gt; <strong>Installed JREs</strong>).</em>
-          </li>
-        </ul>
-        Type a name for the variable in the <strong>Name</strong> field.
-      </li>
-      <li>
-        Type a path to be referenced by the variable in the <strong>Path</strong> field. You can also click the <strong>File</strong>
-        or <strong>Folder</strong> buttons to browse the file system.
-      </li>
-      <li>
-        Click <strong>OK</strong> when you are done. The new or modified variable appears in the <strong>Defined class path variables</strong> list on the Preferences page.
-      </li>
-    </ol>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/cclsspthv.htm">Classpath variables</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-114.htm">Adding a variable class path entry</a><br>
-       <a href="tasks-116.htm">Attaching source to a class path variable</a><br>
-       <a href="tasks-11.htm">Creating Java elements</a><br>
-       <a href="tasks-118.htm">Deleting a class path variable</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-15.htm">Classpath Variables preference page</a><br>
-       &nbsp;
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-118.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-118.htm
deleted file mode 100644
index b5a33ec..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-118.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Deleting a classpath variable
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Deleting a classpath variable
-    </h1>
-     To delete an existing class path variable: 
-    <ol>
-      <li>
-        From the menu bar, select <strong>Window</strong> &gt; <strong>Preferences</strong>.
-      </li>
-      <li>
-        Select the <strong>Java &gt; Build Path &gt; Classpath Variables</strong> page.
-      </li>
-      <li>
-        Select the variable(s) you want to delete in the <strong>Defined class path variables</strong> list and click the <strong>Remove</strong>
-        button. The variable(s) are removed from the classpath variables list on the preferences page.
-      </li>
-    </ol>
-    <p>
-      <strong>Note</strong>: The reserved class path variables, JRE_LIB, JRE_SRC, and JRE_SRCROOT cannot be deleted.&nbsp;
-    </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/cclsspthv.htm">Classpath variables</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-114.htm">Adding a variable class path entry</a><br>
-       <a href="tasks-116.htm">Attaching source to a class path variable</a><br>
-       <a href="tasks-11.htm">Creating Java elements</a><br>
-       <a href="tasks-117.htm">Defining a class path variable</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-15.htm">Classpath Variables preference page</a><br>
-       &nbsp;
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-12.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-12.htm
deleted file mode 100644
index b21bccb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-12.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Creating a new Java project
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Creating a new Java project
-    </h1>
-	<p>
-    You can organize Java projects in two different ways. 
-    </p>
-	<ul>
-      <li>
-        Use the project as the container of packages. In this organization, all Java packages are created directly inside the project. This is the selected organization by
-        default. The generated CLASS files are stored along with the JAVA source files.
-      </li>
-      <li>
-        Use source folders as the container for packages. In this project organization, packages are not created directly inside the project but in source folders. You create
-        source folders as children of the project and create your packages inside these source folders.
-      </li>
-    </ul>
-	<p>
-    The default organization for new projects can be changed on the preference pages (<strong>Window &gt; Preferences &gt; Java &gt; Build Path</strong>). 
-    </p>
-	<p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-13.htm">Creating a Java project as its own source container</a><br>
-       <a href="tasks-14.htm">Creating a Java project with source folders</a><br>
-       <a href="tasks-17.htm">Creating a new Java class</a><br>
-       <a href="tasks-21.htm">Creating a new Java interface</a><br>
-       <a href="tasks-26.htm">Creating a new source folder</a><br>
-       <a href="tasks-11.htm">Creating Java elements</a><br>
-       <a href="tasks-110.htm">Working with build paths</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>
-       <a href="../reference/ref-121.htm">New Java Project wizard</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-120.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-120.htm
deleted file mode 100644
index 6c26dab..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-120.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Assigning the default JRE for the workbench
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Assigning the default JRE for the workbench
-    </h1>
-    <p>
-      The default JRE is used for compiling and launching Java programs in all projects unless you specifically override the default JRE.
-      The default JRE is the installed JRE to which JRE_LIB, JRE_SRC and JRE_SRCROOT are bound.
-      A project is not compiled against the default JRE if the JRE_LIB variable has been removed from its build path.
-      A program is not launched with the default JRE if a custom runtime JRE has been set for its project.
-    </p>
-    <p>
-      Here is how you can change the default JRE:
-    </p>
-    <ol>
-      <li>
-        From the workbench's menu bar, select <strong>Window</strong> &gt; <strong>Preferences</strong>.
-      </li>
-      <li>
-        Expand the <strong>Java</strong> category in the left pane and select <strong>Installed JREs</strong>.
-      </li>
-      <li>
-        Check the box on the line for the JRE that you want to assign as the default JRE in your workbench.
-        If the JRE you want to assign as the default does not appear in the list, you must <a href="tasks-121.htm">add it</a>.
-      </li>
-      <li>
-        Click <strong>OK</strong>.
-      </li>
-    </ol>
-    <strong>Note</strong>: The JRE_LIB, JRE_SRC and JRE_SRCROOT system variables are automatically updated when you change the default JRE. This may cause a build to occur if you
-    have auto build enabled
-    (<strong>Project &gt; Build Automatically</strong> or 
-      <strong>Window &gt; Preferences &gt; General &gt; Workspace &gt; Build automatically</strong>). 
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-121.htm">Adding a new JRE definition</a><br>
-       <a href="tasks-124.htm">Choosing a JRE for launching a project</a><br>
-       <a href="tasks-110.htm">Working with build paths</a><br>
-       <a href="tasks-JREs.htm">Working with JREs</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-19.htm">Installed JREs preference page</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-121.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-121.htm
deleted file mode 100644
index b0607ab..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-121.htm
+++ /dev/null

@@ -1,70 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Adding a new JRE definition
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Adding a new JRE definition
-    </h1>
-    <p>
-      You can add any number of JRE definitions.
-    </p>
-    <ol>
-      <li>
-        From the menu bar, select <strong>Window</strong> &gt; <strong>Preferences.</strong>
-      </li>
-      <li>
-        In the left pane, expand the <strong>Java</strong> category and select <strong>Installed JREs</strong>.
-      </li>
-      <li>
-        Click the&nbsp;<strong>Add...</strong> button. The Create JRE dialog opens.
-      </li>
-      <li>
-        In the <strong>JRE type</strong> field, select the type of JRE you want to add from the drop-down list.
-      </li>
-      <li>
-        In the&nbsp;<strong>JRE name</strong> field, type a name for the new JRE definition. All JREs of the same type must have a unique name.
-      </li>
-      <li>
-        In the&nbsp;<strong>JRE home directory</strong> field, type or click&nbsp;<strong>Browse</strong> to select the path to the root
-        directory of the JRE installation (usually the directory containing the&nbsp;<em>bin</em> and&nbsp;<em>lib</em> directories for the JRE). This location is checked
-        automatically to make sure it is a valid path.
-      </li>
-      <li>
-        In the&nbsp;<strong>Javadoc URL</strong> field, type or click&nbsp;<strong>Browse</strong> to select the URL location. The location is
-        used by the Javadoc export wizard as a default value and by the 'Open External Javadoc' action.
-      </li>
-      <li>
-        If you want to use the default libraries and source files for this JRE, select the <strong>Use default system libraries</strong> checkbox. Otherwise,
-        clear it and customize as desired. Source can be attached for the referenced JARs as well.
-      </li>
-      <li>
-        Click&nbsp;<strong>OK</strong> when you are done.
-      </li>
-    </ol>
-    <p>
-     <img src="../images/ngrelc.png" alt="Related concepts" border="0" > <br>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-      <a href="tasks-JREs.htm">Working with JREs</a><br>
-       <a href="tasks-120.htm">Assigning the default JRE for the workbench</a><br>
-       <a href="tasks-123.htm">Editing a JRE definition</a><br>
-       <a href="tasks-122.htm">Overriding the default system libraries for a JRE definition</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-19.htm">Installed JREs preference page</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-122.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-122.htm
deleted file mode 100644
index 33f9e1b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-122.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Overriding the default system libraries for a JRE definition
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Overriding the default system libraries for a JRE definition
-    </h1>
-    <p>
-      <br>
-       You can override the system libraries and the corresponding source attachments when adding a JRE.
-    </p>
-    <ol>
-      <li>
-        Begin adding a new JRE definition.
-      </li>
-      <li>
-        In the Create JRE dialog, clear the <strong><strong>Use default system libraries</strong></strong> checkbox.<br>
-         If the system was able to determine the set of system libraries, these libraries will already be displayed.
-      </li>
-      <li>
-        Order and/or remove the system libraries that were determined. Add external JARs to the list of system libraries.
-      </li>
-      <li>
-        Associate source with the system libraries using the&nbsp;<strong><strong>Attach source</strong></strong> button.
-      </li>
-      <li>
-        When you are finished with this dialog, click <strong>OK</strong> to create the new JRE definition.
-        The new JRE definition will use the customized
-        system libraries (and attached source).
-      </li>
-    </ol>
-    <p>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" ><br> 
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-      <a href="tasks-JREs.htm">Working with JREs</a><br>
-       <a href="tasks-121.htm">Adding a new JRE definition</a><br>
-       <a href="tasks-123.htm">Editing a JRE definition</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-19.htm">Installed JREs preference page</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-123.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-123.htm
deleted file mode 100644
index ff73b7e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-123.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Editing a JRE definition
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Editing a JRE definition
-    </h1>
-    <p>
-      <br>
-       You can modify all settings for a JRE definition except its JRE type.
-    </p>
-    <ol>
-      <li>
-        From the menu bar, select <strong>Window</strong> &gt; <strong>Preferences</strong>.
-      </li>
-      <li>
-        In the left pane, expend the <strong>Java</strong> category, and select <strong>Installed JREs</strong>.
-      </li>
-      <li>
-        Select the JRE definition that you want to edit and click <strong>Edit...</strong>. The Edit JRE page opens.
-      </li>
-      <li>
-        In the <strong>JRE name</strong> field, edit the name for the JRE definition. All JREs of the same type must have a unique name.
-      </li>
-      <li>
-        In the <strong>JRE home directory</strong> field, edit or click <strong>Browse...</strong> to select the path to the root
-        directory of the JRE installation (usually the directory containing the <em>bin</em> and <em>lib</em> directories for the JRE). This location is checked
-        automatically to make sure it is a valid path.
-      </li>
-      <li>
-        In the <strong>Javadoc URL</strong> field, edit or click <strong>Browse...</strong> to select the URL location. The location is
-        used by the Javadoc export wizard as a default value and by the 'Open External Javadoc' action.
-      </li>
-      <li>
-        If you want to use the default libraries and source files for this JRE, select the <strong>Use default system libraries</strong> checkbox.
-        Otherwise, clear it and customize as desired. Source can be attached for the referenced jars as well.
-      </li>
-      <li>
-        Click <strong>OK</strong> when you are done.
-      </li>
-    </ol>
-    <p>
-     <img src="../images/ngrelc.png" alt="Related concepts" border="0" > <br>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-      <a href="tasks-121.htm">Adding a new JRE definition</a><br>
-       <a href="tasks-deleteJRE.htm">Deleting a JRE definition</a><br>
-       <a href="tasks-122.htm">Overriding the default system libraries for a JRE definition</a><br>
-       <a href="tasks-JREs.htm">Working with JREs</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-19.htm">Installed JREs preference page</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-124.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-124.htm
deleted file mode 100644
index 4fe9346..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-124.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Choosing a JRE for a launch configuration
-    </title>
-  </head>
-  <body>
-    <h1>
-      Choosing a JRE for a launch configuration
-    </h1>
-    <p>
-      Instead of using the default JRE for running and debugging all Java Application launch configurations, you can specifically assign a JRE for launching an individual
-      configuration.
-    </p>
-    <ol>
-      <li>
-        With a Java Application configuration selected in the Launch Configuration Dialog, select the JRE tab.
-      </li>
-      <li>
-        In the list of available JREs, select the JRE you want to use to launch this configuration and click <strong>Apply</strong>,
-        <strong>Run</strong>, or <strong>Debug</strong>.
-      </li>
-    </ol>
-    <p>
-      <strong>Note</strong>: Changing the JRE used for running does not affect the way Java source is compiled. You can adjust the build path to compile against custom
-      libraries.&nbsp;
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="tasks-120.htm">Assigning the default JRE for the workbench</a><br>
-       <a href="../tasks/tasks-126.htm">Running and debugging</a><br>
-       <a href="../tasks/tasks-110.htm">Working with build paths</a><br>
-       <a href="../tasks/tasks-JREs.htm">Working with JREs</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-126.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-126.htm
deleted file mode 100644
index 98ab9c9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-126.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Running and debugging
-    </title>
-  </head>
-  <body>
-    <h1>
-      Running and debugging
-    </h1>
-    <p>
-      You may launch your Java programs from the workbench.&nbsp; The programs may be launched in either run or debug mode.
-    </p>
-    <ul>
-      <li>
-        In run mode, the program executes, but the execution may not be suspended or examined.
-      </li>
-      <li>
-        In debug mode, execution may be suspended and resumed, variables may be inspected, and expressions may be evaluated.
-      </li>
-    </ul>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/concepts-10.htm">Debugger</a><br>
-       <a href="../concepts/cremdbug.htm">Remote debugging</a><br>
-       <a href="../concepts/clocdbug.htm">Local debugging</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-       <a href="tasks-124.htm">Choosing a JRE for launching a project</a><br>
-       <a href="../tasks/tasks-149.htm">Creating a Java scrapbook page</a><br>
-       <a href="../tasks/tasks-142.htm">Disconnecting from a VM</a><br>
-       <a href="../tasks/tasks-130.htm">Launching a Java program</a><br>
-       <a href="../concepts/clocdbug.htm">Local debugging</a><br>
-       <a href="../tasks/tasks-133.htm">Preparing to debug</a><br>
-       <a href="../tasks/tasks-131.htm">Re-launching a program</a><br>
-       <a href="../concepts/cremdbug.htm">Remote debugging</a><br>
-       <a href="../tasks/tasks-135.htm">Resuming the execution of suspended threads</a><br>
-       <a href="../tasks/tasks-executionArgs.htm">Setting execution arguments</a><br>
-       <a href="../tasks/tasks-136.htm">Stepping through the execution of a program</a><br>
-       <a href="../tasks/tasks-134.htm">Suspending threads</a><br>
-       <a href="../tasks/tasks-107.htm">Viewing compilation errors and warnings</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/ref-4.htm">Run and debug actions</a><br>
-       <a href="../reference/ref-51.htm">Debug view</a><br>
-       <a href="../reference/ref-11.htm">Debug preferences</a><br>
-       <a href="../reference/ref-12.htm">Console preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-13.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-13.htm
deleted file mode 100644
index 33300d2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-13.htm
+++ /dev/null

@@ -1,82 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Creating a Java project as its own source container
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Creating a Java project as its own source container
-    </h1>
-    For simple projects, the project itself acts as the source container. 
-    <ol>
-      <li>
-        From the main workbench window, click <strong>File</strong> &gt; <strong>New</strong> &gt; <strong>Project</strong>. The New Project wizard opens.
-      </li>
-      <li>
-        Select <strong>Java Project</strong>, then click <strong>Next</strong>. The New Java Project wizard opens.
-      </li>
-      <li>
-        In the <strong>Project name</strong> field, type a name for your new Java project.
-      </li>
-      <li>
-        Select a location for the project and configure the JDK Compliance.
-      </li>
-      <li>
-        In the <strong>Project layout</strong> section, make sure
-        <strong>Use project folder as root for source and class files</strong> is selected.
-      </li>
-      <li>
-        Click <strong>Next</strong>. The Java Settings Page opens.
-      </li>
-      <li>
-        On the <strong>Source</strong> tab, check that the project is the only source folder and the default output folder.
-      </li>
-      <li>
-        Optionally, on the <strong>Projects</strong> tab, select the required projects to be on the build path for this project. Use these options only if your project depends on
-        other projects.
-      </li>
-      <li>
-        Optionally, on the <strong>Libraries</strong> tab, select JAR files and CLASS folders to add to the build path for this new project and attach source to the JAR
-        files. Use these options only if your project requires additional libraries.
-      </li>
-      <li>
-        On the <strong>Order and Export</strong> tab, use the&nbsp;<strong><strong>Up</strong></strong> and&nbsp;<strong><strong>Down</strong></strong> buttons to move the
-        selected JAR file or CLASS folders  up or down in the build path order for this new project.
-      </li>
-      <li>
-        Click&nbsp;<strong><strong>Finish</strong></strong> when you are done.
-      </li>
-    </ol>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-11.htm">Creating Java elements</a><br>
-       <a href="tasks-12.htm">Creating a new Java project</a><br>
-       <a href="tasks-14.htm">Creating a Java project with source folders</a><br>
-       <a href="tasks-15.htm">Creating a new Java package</a><br>
-       <a href="tasks-17.htm">Creating a new Java class</a><br>
-       <a href="tasks-25.htm">Creating a new interface in a compilation unit</a><br>
-       <a href="tasks-110.htm">Working with build paths</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>
-       <a href="../reference/ref-121.htm">New Java Project wizard</a><a href="../reference/ref-121.htm"></a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-130.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-130.htm
deleted file mode 100644
index b4745d6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-130.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Launching a Java program
-    </title>
-  </head>
-  <body>
-    <h1>
-      Launching a Java program
-    </h1>
-    
-<p>The simplest way to launch a Java program is to run it using a<strong> Java 
-  Application </strong> launch configuration.&nbsp;This launch configuration type 
-  uses information derived from the workbench preferences and your program's Java 
-  project to launch the program. </p>
-    
-<ol>
-  <li> In the Package Explorer, select the Java compilation unit or class file 
-    you want to launch. </li>
-  <li>From the pop-up menu, select <strong>Run &gt; Java Application</strong>. 
-    Alternatively, select <strong>Run &gt; Run As &gt; Java Application </strong>in 
-    the workbench menu bar, or Select <strong>Run As &gt; Java Application </strong>in 
-    the drop-down menu on the <strong>Run</strong> tool bar button.</li>
-  <li> Your program is now launched, and text output is shown in the Console. 
-  </li>
-</ol>
-    
-<p>You can also launch a Java program by selecting a project instead of the compilation 
-  unit or class file.&nbsp; You will be prompted to select a class from those 
-  classes that define a <em>main</em> method.&nbsp; (If only one class with a 
-  main method is found in the project, that class is launched as if you selected 
-  it.)</p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/concepts-6.htm">Java views</a><br>
-       <a href="../concepts/concepts-7.htm">Java editor</a><br>
-       <a href="../concepts/concepts-10.htm">Debugger</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-141.htm">Connecting to a remote VM with the Java Remote Application launcher</a><br>
-       <a href="../tasks/tasks-131.htm">Re-launching a program</a><br>
-       <a href="../tasks/tasks-126.htm">Running and debugging</a><br>
-       <a href="../tasks/tasks-executionArgs.htm">Setting execution arguments</a><br>
-       <a href="../tasks/tasks-136.htm">Stepping through the execution of a program</a><br>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/ref-51.htm">Debug view</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-130a.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-130a.htm
deleted file mode 100644
index 9ea901d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-130a.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Launching a Java applet
-    </title>
-  </head>
-  <body>
-    <h1>
-      Launching a Java applet
-    </h1>
-    <p>If your Java program is structured as an applet, you can use the <strong> Java
-    Applet </strong>launch configuration.&nbsp; This launch configuration uses information
-    derived from the workbench preferences and your program's Java project to launch the program.
-    </p>
-    
-<ol>
-  <li> In the Package Explorer, select the Java compilation unit or class file 
-    you want to launch. </li>
-  <li>From the pop-up menu, select <strong>Run &gt; Java Applet</strong>. Alternatively, 
-    select <strong>Run &gt; Run As &gt; Java Applet </strong>in the workbench 
-    menu bar, or select <strong>Run As &gt; Java Applet </strong>in the drop-down 
-    menu on the <strong>Run</strong> tool bar button.&nbsp; </li>
-  <li> Your program is now launched. </li>
-</ol>
-    <p>You can also launch a Java applet by selecting a project instead of the
-    compilation unit or class file.&nbsp; You will be prompted to select a class
-    from those classes that extend Applet.&nbsp; (If only one applet class is
-        found in the project, that class is launched as if you selected it.)</p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-       <a href="../concepts/concepts-10.htm">Debugger</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-       <a href="../tasks/tasks-131.htm">Re-launching a program</a><br>
-       <a href="../tasks/tasks-126.htm">Running and debugging</a><br>
-       <a href="../tasks/tasks-136.htm">Stepping through the execution of a program</a><br>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/ref-51.htm">Debug view</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-131.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-131.htm
deleted file mode 100644
index f115b0c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-131.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Re-launching a program
-    </title>
-  </head>
-  <body>
-    <h1>
-      Re-launching a program
-    </h1>
-    <p>
-      The workbench keeps a history of each launched and debugged program. To
-      relaunch a program, do one of the following:
-    </p>
-    <ul>
-      <li>
-        Select a previous launch from <strong>Run</strong> or <strong>Debug</strong> button pull-down menus.
-      </li>
-      <li>
-        From the menu bar, select <strong>Run</strong> &gt; <strong>Run History</strong> or <strong>Run</strong> &gt; <strong>Debug History</strong> and select a previous launch
-        from these sub-menus.
-      </li>
-      <li>
-        In the Debug view, select a process that you want to relaunch, and select <strong>Relaunch</strong> from the process's pop-up menu.
-      </li>
-    </ul>
-    <p>
-      To relaunch the most recent launch, do one of the following:
-    </p>
-    <ul>
-      <li>
-        Click the <strong>Run</strong> or <strong>Debug</strong>  buttons
-        (without using the button pull-down menu).
-      </li>
-      
-  <li> Select <strong>Run</strong> &gt; <strong>Run Last Launched</strong> (<kbd>Ctrl+F11</kbd>), 
-    or <strong>Run</strong> &gt; <strong>Debug Last Launched</strong> (<kbd>F11</kbd>)
-    from the workbench menu bar. 
-  </li>
-    </ul>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-130.htm">Launching a Java program</a><br>
-       <a href="../tasks/tasks-126.htm">Running and debugging</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/ref-51.htm">Debug view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-133.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-133.htm
deleted file mode 100644
index 6bace59..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-133.htm
+++ /dev/null

@@ -1,48 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Preparing to debug
-    </title>
-  </head>
-  <body>
-    <h1>
-      Preparing to debug
-    </h1>
-    <p>
-      You can make your programs easier to debug by following these guidelines:
-    </p>
-    <ul>
-      <li>
-        Where possible, do not put multiple statements on a single line, because some debugger features operate on a line basis. For example, you cannot step over or set line
-        breakpoints on more than one statement on the same line.
-      </li>
-      <li>
-        Attach source code to JAR files if you have the source code.
-      </li>
-    </ul>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/concepts-10.htm">Debugger</a><br>
-       <a href="../concepts/cremdbug.htm">Remote debugging</a><br>
-       <a href="../concepts/clocdbug.htm">Local debugging</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-       <a href="../tasks/tasks-126.htm">Running and debugging</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/ref-11.htm">Debug preferences</a><br>
-       <a href="../reference/ref-51.htm">Debug view</a><br>
-       <a href="../reference/ref-4.htm">Run and debug actions</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-134.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-134.htm
deleted file mode 100644
index 613e397..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-134.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Suspending threads
-    </title>
-  </head>
-  <body>
-    <h1>
-      Suspending threads
-    </h1>
-    <p>
-      To suspend an executing thread:
-    </p>
-    <ol>
-      <li>
-        Select the thread in the Debug view.
-      </li>
-      <li>
-        Click the <strong><strong>Suspend</strong></strong> button in the Debug view toolbar. The thread suspends its execution. The current call stack for the thread is
-        displayed, and the current line of execution is highlighted in the editor in the Debug perspective.
-      </li>
-    </ol>
-    <p>
-      When a thread suspends, the top stack frame of the thread is automatically
-      selected.&nbsp; The Variables view shows the stack frame's variables and
-      their values.&nbsp; Complex variables can be further examined by expanding
-      them to show the values of their members.
-    </p>
-    <p>
-      When a thread is suspended and the cursor is hovered over a variable in the Java editor, the value of that variable is displayed.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/concepts-10.htm">Debugger</a><br>
-       <a href="../concepts/concepts-7.htm">Java editor</a><br>
-       <a href="../concepts/concepts-5.htm">Java perspectives</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-147.htm">Catching Java exceptions</a><br>
-       <a href="../tasks/tasks-138.htm">Evaluating expressions</a><br>
-       <a href="../tasks/tasks-135.htm">Resuming the execution of suspended threads</a><br>
-       <a href="../tasks/tasks-136.htm">Stepping through the execution of a program</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/ref-51.htm">Debug view</a><br>
-       <a href="../reference/ref-74.htm">Variables view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-135.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-135.htm
deleted file mode 100644
index ce7ae6c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-135.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Resuming the execution of suspended threads
-    </title>
-  </head>
-  <body>
-    <h1>
-      Resuming the execution of suspended threads
-    </h1>
-    <p>
-      To resume the execution of a suspended threads:
-    </p>
-    <ol>
-      <li>
-        Select the thread or its stack frame in the Debug view.
-      </li>
-      <li>
-        Click the <strong>Resume</strong> button in the Debug view toolbar (or press the <kbd>F8</kbd> key). The thread resumes its execution, and stack
-        frames are no longer displayed for the thread.&nbsp; The Variables view is cleared.
-      </li>
-    </ol>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/concepts-10.htm">Debugger</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-138.htm">Evaluating expressions</a><br>
-       <a href="../tasks/tasks-136.htm">Stepping through the execution of a program</a><br>
-       <a href="../tasks/tasks-134.htm">Suspending threads</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/ref-51.htm">Debug view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-136.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-136.htm
deleted file mode 100644
index cfdd845..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-136.htm
+++ /dev/null

@@ -1,123 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Stepping through the execution of a Java program
-    </title>
-  </head>
-  <body>
-    <h1>
-      Stepping through the execution of a Java program
-    </h1>
-    <p>
-      When a thread is suspended, the step controls can be used to step through the execution of the program line-by-line.
-      If a breakpoint is encountered while performing a step operation,&nbsp;
-      the execution will suspend at the breakpoint and the step operation is
-      ended.
-    </p>
-    <h2>
-      Step over
-    </h2>
-    <ol>
-      <li>
-        Select a stack frame in the Debug view. The current line of execution in that stack frame is highlighted in the editor in the Debug perspective.
-      </li>
-      <li>
-        Click the <strong>Step Over</strong> button in the Debug view toolbar, or press the <kbd>F6</kbd> key. The currently-selected line is executed and
-        suspends on the next executable line.
-      </li>
-    </ol>
-    <h2>
-      Step into
-    </h2>
-    <ol>
-      <li>
-        Select a stack frame in the Debug view. The current line of execution in the selected frame is highlighted in the editor in the Debug perspective.
-      </li>
-      <li>
-        Click the <strong>Step Into</strong> button in the Debug view toolbar, or press the <kbd>F5</kbd> key. The next expression on the currently-selected
-        line to be executed is invoked, and execution suspends at the next executable line in the method that is invoked.
-      </li>
-    </ol>
-    
-<h2> Step into Selection</h2>
-<ol>
-  <li> Select a stack frame in the Debug view. The current line of execution in 
-    the selected frame is highlighted in the editor in the Debug perspective. 
-  </li>
-  <li>In the Java editor, within the current line of execution, place the cursor 
-    on the name of a method that you would like to step into.</li>
-  <li> Click the <strong>Step into Selection </strong>action in the Run menu or 
-    Java editor context menu, or press the <kbd>Ctrl-F5</kbd> key. Execution resumes 
-    until the selected method is invoked. </li>
-</ol>
-    <h2>
-      Step with filters
-    </h2>
-    
-<ol>
-  <li>Toggle the <strong>Use Step Filters</strong> button in the Debug view toolbar, 
-    or use <kbd>Shift+F5</kbd>. When the action is toggled on, each of the step 
-    actions (over, into, return) will apply the set of step filters which are 
-    defined in the user preferences (see <strong>Window &gt; Preferences &gt; 
-    Java &gt; Debug &gt; Step Filtering</strong>). When a step action is invoked, 
-    stepping will continue until an unfiltered location is reached or a breakpoint 
-    is encountered.</li>
-</ol>
-    <h2>
-      Run to return
-    </h2>
-    <ol>
-      <li>
-        Select a stack frame in the Debug view. The current line of execution in the selected frame is highlighted in the editor in the Debug perspective.
-      </li>
-      <li>
-        Click the <strong>Run to Return</strong> button in the Debug view toolbar or press the <kbd>F7</kbd> key. Execution resumes until the next return
-        statement in the current method is executed, and execution suspends on the next executable line.
-      </li>
-    </ol>
-    <h2>
-      Run to line
-    </h2>
-    <p>
-      When a thread is suspended, it is possible to resume execution until a specified line is executed. This is a convenient way to suspend execution at a line without setting a
-      breakpoint.
-    </p>
-    <ol>
-      <li>
-        Place your cursor on the line at which you want the program to run.
-      </li>
-      <li>
-        Select <strong>Run to Line</strong> from the pop-up menu or use
-        <kbd>Ctrl+R</kbd>. Program execution is resumed and suspends just before the specified line is to be executed.
-      </li>
-    </ol>
-    <p>It is possible that the line will never be hit and that the program will not suspend.&nbsp;</p>
-    <p> Breakpoints and exceptions can cause the thread to suspend before reaching the specified
-        line.</p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/cbrkpnts.htm">Breakpoints</a><br>
-       <a href="../concepts/concepts-5.htm">Java perspectives</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-144.htm">Adding breakpoints</a><br>
-       <a href="../tasks/tasks-130.htm">Launching a Java program</a><br>
-       <a href="../tasks/tasks-135.htm">Resuming the execution of suspended threads</a><br>
-       <a href="../tasks/tasks-126.htm">Running and debugging</a><br>
-       <a href="../tasks/tasks-executionArgs.htm">Setting execution arguments</a><br>
-       <a href="../tasks/tasks-134.htm">Suspending threads</a><br>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/ref-51.htm">Debug view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-137.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-137.htm
deleted file mode 100644
index c26e95a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-137.htm
+++ /dev/null

@@ -1,27 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Inspecting values
-    </title>
-  </head>
-  <body>
-    <h1>
-      Inspecting values
-    </h1>
-    <p>
-      When stack frame is selected, you can see the visible variables in that
-      stack frame in the Variables view.
-    </p>
-    <p>
-      The Variables view shows the value of primitive types.&nbsp; Complex
-      variables can be examined by expanding them to show their members.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-138.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-138.htm
deleted file mode 100644
index 449de22..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-138.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Evaluating expressions
-    </title>
-  </head>
-  <body>
-    <h1>
-      Evaluating expressions
-    </h1>
-    
-<p>When the VM suspends a thread (due to hitting a breakpoint or stepping through 
-  code), you can evaluate expressions in the context of a stack frame. </p>
-    
-<ol>
-  <li> Select the stack frame in which an evaluation is to be performed. For the 
-    detail panes of the <strong>Variables</strong> and <strong>Expressions</strong> 
-    views, the evaluation context will be a selected variable. If no variable 
-    is selected, the selected stack frame will be the context. </li>
-  <li> Expressions can be entered and evaluated in the following areas: 
-    <ul>
-      <li> <strong>Display</strong> view </li>
-      <li> Detail pane of the <strong>Expressions</strong> view </li>
-      <li> Detail pane of the <strong>Variables</strong> view </li>
-      <li> Java editor when it is displaying source and it is not read-only </li>
-    </ul>
-  </li>
-  <li> Select the expression to be evaluated and select <strong>Display</strong>, 
-    <strong>Inspect</strong> or <strong>Execute</strong> from the context pop-up 
-    menu. The result of a <strong>Display</strong> or <strong>Inspect </strong>evaluation 
-    is shown in a popup window. Note that <strong>Execute</strong> does not display 
-    a result - the expression is just executed.</li>
-  <li>The result popup window can be dismissed by clicking outside of the popup 
-    window or by pressing <strong>Esc</strong>. The result can be persisted to 
-    the Display view (if <strong>Display</strong> was chosen) or Expressions view 
-    (if <strong>Inspect</strong> was chosen) by pressing the key sequence shown 
-    at the bottom of the popup window. For example, to move the result of an <strong>Inspect 
-    </strong>evaluation to the Expressions view press <strong>CTRL-Shift-I</strong>. 
-    Note that when the <strong>Display</strong> action is used from the Display 
-    view the result is written to the Display view rather than a popup</li>
-</ol>
-    <p><strong>Note:</strong> Evaluations cannot be performed in threads that have been manually suspended.</p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/concepts-10.htm">Debugger</a><br>
-       <a href="../concepts/concepts-7.htm">Java editor</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-134.htm">Suspending threads</a><br>
-       <a href="../tasks/tasks-135.htm">Resuming the execution of suspended threads</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/ref-52.htm">Display view</a><br>
-       <a href="../reference/ref-56.htm">Expressions view</a><br>
-       <a href="../reference/ref-56c.htm">Expressions view Show Detail Pane</a><br>
-       <a href="../reference/ref-74.htm">Variables view</a><br>
-       <a href="../reference/ref-showdetailpane.htm">Variables view Show Detail Pane</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-14.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-14.htm
deleted file mode 100644
index 77d047a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-14.htm
+++ /dev/null

@@ -1,100 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Creating a Java project with source folders
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Creating a Java project with source folders
-    </h1>
-    For larger projects, create a project with source folders. 
-    <blockquote>
-      <em>Note: When using source folders, non-Java resources are copied to the output folder by the Java builder.
-      If you have non-Java resources (documentation, for example) that should not be copied into the output folder, 
-      you can create an ordinary folder and store the resources there. You can also use the preferences page
-      <strong>Window &gt; Preferences &gt; Java &gt; Compiler &gt; Building</strong>
-	  to specify a list of resources that will not be automatically copied to the output folder.</em>
-    </blockquote>
-    <ol>
-      <li>
-        From the main workbench window, click <strong>File</strong> &gt; <strong>New</strong> &gt; <strong>Project</strong>. The New Project wizard opens.
-      </li>
-      <li>
-        Select <strong>Java Project</strong>, then click <strong>Next</strong>. The New Java Project wizard opens.
-      </li>
-      <li>
-        In the <strong>Project name</strong> field, type a name for your new Java project.
-      </li>
-      <li>
-        Select a location for the project and configure the JDK Compliance.
-      </li>
-      <li>
-        In the <strong>Project layout</strong> section, make sure
-        <strong>Create separate source and output folders</strong> is selected.
-      </li>
-      <li>
-        Click <strong>Next</strong>. The Java Settings Page opens.
-      </li>
-      <li>
-        On the <strong>Source</strong> tab, check that the project contains a source folder. You can create additional source folders at any time
-        later.
-      </li>
-      <li>
-        Optionally, replace the default name in the&nbsp;<strong><strong>Default output folder</strong></strong> field to use a different name for the output folder.
-      </li>
-      <li>
-        On the <strong>Projects</strong> tab, select the required projects to be on the build path for this project.
-      </li>
-      <li>
-        On the <strong>Libraries</strong> tab, select JAR files and CLASS file containers to add to the build path for this new project and attach source to the JAR files.
-      </li>
-      <li>
-        On the <strong>Order and Export</strong> tab, use the <strong>Up</strong> and <strong>Down</strong> buttons to move the
-        selected JAR file or CLASS file container up or down in the build path order for this new project.
-      </li>
-      <li>
-        Click&nbsp;<strong>Finish</strong> when you are done.
-      </li>
-    </ol>
-    <blockquote>
-      <em>Note: When you are using CVS as your repository, it is recommended that you create a .cvsignore file inside the project. In this file, add a line with the name of the
-      output folder (&quot;bin&quot; for example). Adding the output folder in the .cvsignore file ensures that the CVS versioning support ignores the output folder in versioning
-      operations.</em>
-    </blockquote>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a><br>
-       <a href="../concepts/concepts-4.htm">Java builder</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-11.htm">Creating Java elements</a><br>
-       <a href="tasks-12.htm">Creating a new Java project</a><br>
-       <a href="tasks-26.htm">Creating a new source folder</a><br>
-       <a href="tasks-13.htm">Creating a Java project as its own source container</a><br>
-       <a href="tasks-15.htm">Creating a new Java package</a><br>
-       <a href="tasks-17.htm">Creating a new Java class</a><br>
-       <a href="tasks-149.htm">Creating a Java scrapbook page</a><br>
-       <a href="tasks-110.htm">Working with build paths</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>
-       <a href="../reference/ref-121.htm">New Java Project wizard</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-141.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-141.htm
deleted file mode 100644
index 341336c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-141.htm
+++ /dev/null

@@ -1,81 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Using the remote Java application launch configuration
-    </title>
-  </head>
-  <body>
-    <h1>
-      Using the remote Java application launch configuration
-    </h1>
-    <p>The <strong>Remote Java Application </strong> launch configuration should
-    be used when debugging an application that is running on a remote VM.&nbsp;
-    Since the application is started on the remote system, the launch
-    configuration does not specify the usual information about the JRE, program
-    arguments, or VM arguments.&nbsp; Instead, information about connecting to
-    the application is supplied.
-    </p>
-    <p>To create a <strong>Remote Java Application</strong>  launch
-    configuration, do the following:
-    </p>
-    <ol>
-      <li>
-        Select <strong>Run &gt;Debug...</strong>.from the workbench menu bar (or
-        <strong>Debug... </strong>from the drop-down menu on the <strong>Debug</strong> 
-        tool bar button) to show the launch configuration dialog.
-      </li>
-      <li>
-        Select the <strong>Remote Java Application</strong>  in the list of
-        configuration types on the left.
-      </li>
-      <li>
-        Click the <strong>New</strong> button. A new remote launch configuration is created and three tabs are shown: <strong>Connect</strong>,
-        <strong>Source</strong>, and <strong>Common</strong>.
-      </li>
-      <li>
-        In the <strong>Project</strong> field of the <strong>Connect</strong> tab, type or browse to select the project to use as a reference for
-        the launch (for source lookup). A project does not need to be specified.
-      </li>
-      <li>
-        In the <strong>Host</strong> field of the <strong>Connect</strong> tab, type the IP address or domain name of the host where the Java
-        program is running.<br>
-         If the program is running on the same machine as the workbench, type <em>localhost</em>.
-      </li>
-      <li>
-        In the <strong>Port</strong> field of the <strong>Connect</strong> tab, type the port where the remote VM is accepting connections.
-        Generally, this port is specified when the remote VM is launched.
-      </li>
-      <li>
-        The <strong>Allow termination of remote VM</strong> flag is a toggle that determines whether the <strong>Terminate</strong> command is
-        enabled in the debugger. Select this option if you want to be able to terminate the VM to which you are connecting.
-      </li>
-      <li>
-        Click <strong>Debug</strong>. The launch attempts to connect to a VM at the specified address and port, and the result is displayed in the Debug view. If
-        the launcher is unable to connect to a VM at the specified address, an error message appears.
-      </li>
-    </ol>
-    <p>Specific instructions for setting up the remote VM should be obtained
-    from your VM provider.&nbsp;</p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/concepts-10.htm">Debugger</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-130.htm">Launching a Java program</a><br>
-       <a href="../tasks/tasks-142.htm">Disconnecting from a VM</a><br>
-       <a href="../tasks/tasks-executionArgs.htm">Setting execution arguments</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/ref-51.htm">Debug view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-142.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-142.htm
deleted file mode 100644
index 018cbef..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-142.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Disconnecting from a VM
-    </title>
-  </head>
-  <body>
-    <h1>
-      Disconnecting from a VM
-    </h1>
-    <p>
-      To disconnect from a VM that was connected to with a Remote Java Application launch configuration:
-    </p>
-    <ol>
-      <li>
-        In the Debug view, select the launch.
-      </li>
-      <li>
-        Click the <strong>Disconnect</strong> button in the view's toolbar. Communication with the VM is terminated, and all threads in the remote VM are
-        resumed. Although the remote VM continues to execute, the debug session is now terminated.
-      </li>
-    </ol>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/concepts-10.htm">Debugger</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-141.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-       <a href="../tasks/tasks-126.htm">Running and debugging</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/ref-51.htm">Debug view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-144.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-144.htm
deleted file mode 100644
index 34d6964..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-144.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Adding breakpoints
-    </title>
-  </head>
-  <body>
-    <h1>
-      Adding breakpoints
-    </h1>
-    <p>
-      Line breakpoints are set on an executable line of a program.
-    </p>
-    <ol>
-      <li>
-        In the editor area, open the file where you want to add the breakpoint.
-      </li>
-      
-  <li> Directly to the left of the line where you want to add the breakpoint, 
-    open the marker bar (vertical ruler) pop-up menu and select <strong>Toggle 
-    Breakpoint.</strong>&nbsp;&nbsp; You can also double-click on the marker bar 
-    next to the source code line.&nbsp; A new breakpoint marker appears on the 
-    marker bar, directly to the left of the line where you added the breakpoint. 
-    Also, the new breakpoint appears in the Breakpoints view list. </li>
-    </ol>
-    <p>
-      While the breakpoint is enabled, thread execution suspends before that line of code is executed. The debugger selects the thread that has suspended and displays the stack
-      frames on that thread's stack. The line where the breakpoint was set is highlighted in the editor in the Debug perspective.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-    <a href="../concepts/concepts-10.htm">Debugger</a><br>
-     <a href="../concepts/concepts-5.htm">Java perspectives</a><br>
-     <a href="../concepts/concepts-7.htm">Java editor</a><br>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-146.htm">Applying hit counts</a><br>
-       <a href="../tasks/tasks-147.htm">Catching Java exceptions</a><br>
-       <a href="../tasks/tasks-144a.htm">Removing breakpoints</a><br>
-       <a href="../tasks/tasks-144b.htm">Enabling and disabling breakpoints</a><br>
-       <a href="../tasks/tasks-144c.htm">Managing conditional breakpoints</a><br>
-       <a href="../tasks/tasks-145.htm">Setting method breakpoints</a><br>
-       <a href="../tasks/tasks-136.htm">Stepping through the execution of a program</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/ref-35.htm">Breakpoints view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-144a.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-144a.htm
deleted file mode 100644
index 46f0e66..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-144a.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Removing breakpoints
-    </title>
-  </head>
-  <body>
-    <h1>
-      Removing breakpoints
-    </h1>
-    <p>
-      Breakpoints can be easily removed when you no longer need them.
-    </p>
-    <ol>
-      <li>
-        In the editor area, open the file where you want to remove the breakpoint.
-      </li>
-      
-  <li> Directly to the left of the line where you want to remove the breakpoint, 
-    open the marker bar pop-up menu and select <strong>Toggle Breakpoint</strong>. 
-    The breakpoint is removed from the workbench.&nbsp; You can also double-click 
-    directly on the breakpoint icon to remove it. </li>
-    </ol>
-    Breakpoints can also be removed in the <strong>Breakpoints view</strong>. Select the breakpoint(s) to be removed and from the context menu select <strong>Remove</strong>.<br>
-     All breakpoints can be removed from the workbench using the <strong>Remove All</strong> action in the context menu of the <strong>Breakpoints view</strong>.
-    <p>If you find yourself frequently adding and removing a breakpoint in the
-    same place, consider disabling the breakpoint when you don't need it (using <strong>Disable
-    Breakpoint </strong>in the breakpoint context menu or the <strong>Breakpoints view</strong>)
-    and enabling it when needed again.&nbsp;&nbsp;</p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-    <a href="../concepts/concepts-10.htm">Debugger</a><br>
-     <a href="../concepts/concepts-5.htm">Java perspectives</a><br>
-     <a href="../concepts/concepts-7.htm">Java editor</a><br>
-    </p>
-	<p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-144.htm">Adding breakpoints</a><br>
-       <a href="../tasks/tasks-144b.htm">Enabling and disabling breakpoints</a><br>
-       <a href="../tasks/tasks-146.htm">Applying hit counts</a><br>
-       <a href="../tasks/tasks-147.htm">Catching Java exceptions</a><br>
-       <a href="../tasks/tasks-144c.htm">Managing conditional breakpoints</a><br>
-       <a href="../tasks/tasks-145.htm">Setting method breakpoints</a><br>
-       <a href="../tasks/tasks-136.htm">Stepping through the execution of a program</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/ref-35.htm">Breakpoints view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-144b.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-144b.htm
deleted file mode 100644
index 1f9c195..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-144b.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Enabling and disabling breakpoints
-    </title>
-  </head>
-  <body>
-    <h1>
-      Enabling and disabling breakpoints
-    </h1>
-    <p>
-      Breakpoints can be enabled and disabled as needed.&nbsp; When a breakpoint is enabled, thread execution suspends before that line of code is executed.&nbsp;
-      When a breakpoint is disabled, thread execution is not suspended by the
-      presence of the breakpoint.
-    </p>
-    
-<p> To disable a breakpoint in the <strong>Breakpoints view</strong>: </p>
-<ol>
-  <li> Open the breakpoint's context menu and select <strong>Disable</strong>, 
-    or deselect the breakpoint's checkbox.</li>
-  <li> The breakpoint image will change to a white circle and its checkbox will 
-    be empty.</li>
-</ol>
-<p>To disable a breakpoint in the marker bar of an editor: </p>
-<ol>
-  <li> Open the breakpoint's context menu and select <strong>Disable Breakpoint</strong>.</li>
-  <li> The breakpoint image will change to a white circle.</li>
-</ol>
-<p>To enable the breakpoint in the <strong>Breakpoints view</strong>:</p>
-<ol>
-  <li> Open the breakpoint's context menu and select <strong>Enable</strong>, 
-    or select the breakpoint's checkbox. </li>
-  <li> The breakpoint image will change back to a blue circle, and its checkbox 
-    will be checked.</li>
-</ol>
-<p>To enable a breakpoint in the marker bar of an editor: </p>
-<ol>
-  <li> Open the breakpoint's context menu and select <strong>Enable Breakpoint</strong>.</li>
-  <li> The breakpoint image will change to a white circle.</li>
-</ol>
-<p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-    <a href="../concepts/concepts-10.htm">Debugger</a><br>
-     <a href="../concepts/concepts-5.htm">Java perspectives</a><br>
-     <a href="../concepts/concepts-7.htm">Java editor</a><br>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-146.htm">Applying hit counts</a><br>
-       <a href="../tasks/tasks-147.htm">Catching Java exceptions</a><br>
-       <a href="../tasks/tasks-144a.htm">Removing breakpoints</a><br>
-       <a href="../tasks/tasks-145.htm">Setting method breakpoints</a><br>
-       <a href="../tasks/tasks-144c.htm">Managing conditional breakpoints</a><br>
-       <a href="../tasks/tasks-136.htm">Stepping through the execution of a program</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/ref-35.htm">Breakpoints view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-144c.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-144c.htm
deleted file mode 100644
index 2cd987d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-144c.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title> Managing conditional breakpoints </title>
-</head>
-<body>
-<h1> Managing conditional breakpoints </h1>
-<p> 
-      An enabling condition can be applied to line breakpoints, so that the
-      breakpoint suspends execution of a thread in one of these cases: </p>
-<ul>
-  <li>when the enabling condition is true</li>
-  <li>when the enabling condition changes</li>
-</ul>
-<p> To set a condition on a breakpoint: </p>
-<ol>
-      <li>
-        Find the breakpoint to which an enabling condition is to be applied (in
-        the Breakpoints view or in the editor marker bar).
-      </li>
-      <li>
-        From the breakpoint's pop-up menu, select <strong>Breakpoint
-        Properties...</strong>.&nbsp; The Breakpoint properties dialog will open.
-      </li>
-  <li> In the properties dialog, check the <strong>Enable Condition</strong> checkbox.&nbsp; </li>
-  <li> In the <strong>Condition</strong> field enter the expression for 
-    the breakpoint condition. </li>
-  <li> Do one of the following:
-    <ul>
-      <li>If you want the breakpoint to stop every time the condition evaluates
-        to <em>true</em>, select the <strong>condition is 'true' </strong>option.&nbsp;
-        The expression provided must be a boolean expression.</li>
-      <li>If you want the breakpoint to stop only when the result of the
-        condition changes, select the <strong>value of condition changes </strong>option.</li>
-    </ul>
- </li>
-  <li> Click <strong>OK</strong> to close the dialog and commit the changes. While 
-    the breakpoint is enabled, thread execution suspends before that line of code 
-    is executed if the breakpoint condition evaluates to <em>true</em>.&nbsp; 
-  </li>
-</ol>
-<p>
-    A conditional breakpoint has a question mark overlay on the breakpoint icon.</p>
-<p> <img border="0" src="../images/ngrelc.png" alt="Related concepts" > 
-  <br>
-  <a href="../concepts/concepts-10.htm">Debugger</a><br>
-  <a href="../concepts/concepts-5.htm">Java perspectives</a><br>
-  <a href="../concepts/concepts-7.htm">Java editor</a><br>
-</p>
-<p> <img border="0" src="../images/ngrelt.png" alt="Related tasks" > 
-  <br>
-  <a href="../tasks/tasks-144.htm">Adding breakpoints</a><br>
-  <a href="../tasks/tasks-146.htm">Applying hit counts</a><br>
-  <a href="../tasks/tasks-147.htm">Catching Java exceptions</a><br>
-  <a href="../tasks/tasks-144a.htm">Removing breakpoints</a><br>
-  <a href="../tasks/tasks-145.htm">Setting method breakpoints</a><br>
-  <a href="../tasks/tasks-136.htm">Stepping through the execution of a program</a> 
-</p>  
-<p> <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-  <a href="../reference/ref-35.htm">Breakpoints view</a> 
-</p>
-    
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-145.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-145.htm
deleted file mode 100644
index fdfbeff..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-145.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Setting method breakpoints
-    </title>
-  </head>
-  <body>
-    <h1>
-      Setting method breakpoints
-    </h1>
-    <p>
-      Method breakpoints are used when working with types that have no source
-    code (binary types).
-    </p>
-    <ol>
-      <li>
-        Open the class in the Outline view, and select the method where you want to add a method breakpoint.
-      </li>
-      
-  <li> From the method's pop-up menu, select <strong>Toggle Method Breakpoint</strong>. 
-  </li>
-      <li>
-        A breakpoint appears in the Breakpoints view. If source exists for the class, then a breakpoint also appears in the marker bar in the file's editor for the method that
-        was selected.
-      </li>
-      <li>
-        While the breakpoint is enabled, thread execution suspends when the method is entered, before any line in the method is executed.&nbsp;
-      </li>
-    </ol>
-    <p>Method breakpoints can also be setup to break on method exit.&nbsp; In the Breakpoints view, select the breakpoint and toggle the
-    <strong>Exit</strong>&nbsp; item in its context menu.</p>
-    <p>Method breakpoints can be removed, enabled, and disabled just like line
-    breakpoints.</p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/cbrkpnts.htm">Breakpoints</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-144.htm">Adding breakpoints</a><br>
-       <a href="../tasks/tasks-144a.htm">Removing breakpoints</a><br>
-       <a href="../tasks/tasks-144b.htm">Enabling and disabling breakpoints</a><br>
-       <a href="../tasks/tasks-146.htm">Applying hit counts</a><br>
-       <a href="../tasks/tasks-147.htm">Catching Java exceptions</a><br>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/ref-35.htm">Breakpoints view</a><br>
-       <a href="../reference/ref-view-outline.htm">Java outline</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-146.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-146.htm
deleted file mode 100644
index 029ad87..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-146.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Applying hit counts
-    </title>
-  </head>
-  <body>
-    <h1>
-      Applying hit counts
-    </h1>
-    <p>
-      A hit count can be applied to line breakpoints, exception breakpoints, watchpoints and method breakpoints. When a hit count is applied to a breakpoint, the breakpoint
-      suspends execution of a thread the <em>n</em>th time it is hit, but never again, until it is re-enabled or the hit count is changed or disabled.
-    </p>
-    <p>
-      To set a hit count on a breakpoint:
-    </p>
-    <ol>
-      <li>
-        Select the breakpoint to which a hit count is to be added.
-      </li>
-      <li>
-        From the breakpoint's pop-up menu, select <strong><strong>Hit Count</strong></strong>.
-      </li>
-      <li>
-        In the <strong><strong>Enter the new hit count for the breakpoint</strong></strong> field, type the number of times you want to hit the breakpoint before suspending
-        execution.<br>
-        <br>
-         <strong>Note:</strong> When the breakpoint is hit for the <em>n</em>th time, the thread that hit the breakpoint suspends. The breakpoint is disabled until either it is
-        re-enabled or its hit count is changed.
-      </li>
-    </ol>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/cbrkpnts.htm">Breakpoints</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-144.htm">Adding breakpoints</a><br>
-       <a href="../tasks/tasks-144a.htm">Removing breakpoints</a><br>
-       <a href="../tasks/tasks-144b.htm">Enabling and disabling breakpoints</a><br>
-       <a href="../tasks/tasks-145.htm">Setting method breakpoints</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/ref-35.htm">Breakpoints view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-147.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-147.htm
deleted file mode 100644
index 092ab0e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-147.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Catching Java exceptions
-    </title>
-  </head>
-  <body>
-    <h1>
-      Catching Java exceptions
-    </h1>
-    <p>
-      It is possible to suspend the execution of thread when an exception is thrown by specifying an
-      exception breakpoint. Execution can be suspended at locations where the exception is
-      uncaught, caught, or both.
-    </p>
-    <ol>
-      <li>
-        Choose <strong>Add Java Exception Breakpoint</strong>  from the
-        Breakpoints view or the workbench Run menu.&nbsp;&nbsp;
-      </li>
-      <li>
-        A dialog listing all of the available exceptions is shown.
-      </li>
-      <li>
-        Either type the name of the exception you want to catch or select it from the list.
-      </li>
-      <li>
-        At the bottom of the page, use the checkboxes to specify how you want execution to suspend at locations where the exception is thrown. 
-        <ul>
-          <li>
-            Select <strong>Caught</strong> if you want execution to suspend at locations where the exception is thrown but caught.
-          </li>
-          <li>
-            Select <strong>Uncaught</strong> if you want execution to suspend at locations where the exception is uncaught.
-          </li>
-        </ul>
-      </li>
-    </ol>
-    <p>
-      <strong>Note:</strong> Exception breakpoints can be enabled and disabled and have hit counts
-    just like regular breakpoints.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a><br>
-       <a href="../concepts/cbrkpnts.htm">Breakpoints</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-134.htm">Suspending threads</a><br>
-       <a href="../tasks/tasks-144.htm">Adding breakpoints</a><br>
-       <a href="../tasks/tasks-144a.htm">Removing breakpoints</a><br>
-       <a href="../tasks/tasks-144b.htm">Enabling and disabling breakpoints</a><br>
-       <a href="../tasks/tasks-145.htm">Setting method breakpoints</a><br>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/ref-35.htm">Breakpoints view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-149.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-149.htm
deleted file mode 100644
index 3f9089e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-149.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Creating a Java scrapbook page
-    </title>
-  </head>
-  <body>
-    <h1>
-      Creating a Java scrapbook page
-    </h1>
-    <p>
-      The scrapbook allows Java expressions, to be run, inspected, and displayed under the control of the debugger. Breakpoints and exceptions
-      behave as they do in a regular debug
-      session.
-    </p>
-    <p>
-      Code is edited on a scrapbook page.&nbsp; A VM is launched for each scrapbook page in which expressions are being evaluated. The first time an expression is evaluated in a scrapbook page after it is opened, a VM is
-      launched. The VM for a page will remain active until the page is closed, terminated explicitly (in the debugger or via the <strong>Stop the Evaluation</strong> button in the
-      editor toolbar), or when a <em>System.exit()</em> is evaluated.
-    </p>
-    <p>
-      There are several ways to open the New Java Scrapbook Page
-      wizard.&nbsp;&nbsp;
-    </p>
-        
-<ul>
-  <li> Create a file with a <strong>.jpage</strong> extension</li>
-  <li> From the menu bar, select <strong>File</strong> &gt; <strong>New</strong> 
-    &gt; <strong>Other</strong>. Then select <strong>Java</strong> &gt; <strong>Java 
-    Run/Debug</strong> &gt; <strong>Scrapbook Page</strong>. Then click <strong>Next</strong>. 
-  </li>
-</ul>
-    Once you've opened the New Java Scrapbook Page wizard:.
-    <ol>
-      <li>
-        In the <strong><strong>Enter or select the folder</strong> field</strong>, type or click <strong>Browse</strong> to select the container for the new page.
-      </li>
-      <li>
-        In the <strong><strong>File name</strong></strong> field, type a name for the new page. The <em>.jpage</em> extension will be added automatically if you do not type it
-        yourself.
-      </li>
-      <li>
-        Click <strong><strong>Finish</strong></strong> when you are done. The new scrapbook page opens in an editor.
-      </li>
-    </ol>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/concepts-11.htm">Scrapbook</a><br>
-       <a href="../concepts/concepts-3.htm">Java projects</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-26.htm">Creating a new source folder</a><br>
-       <a href="../tasks/tasks-11.htm">Creating Java elements</a><br>
-       <a href="tasks-126.htm">Running and debugging</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/ref-34.htm">Java scrapbook page</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-15.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-15.htm
deleted file mode 100644
index 64a441c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-15.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Creating a new Java package
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Creating a new Java package
-    </h1>
-    <p>
-      To create new Java packages in the Package Explorer:
-    </p>
-    <ol>
-      <li>
-        Optionally, select the project or source folder where you want the package to reside.
-      </li>
-      <li>
-        Click the <strong>New Java Package</strong> button in the workbench toolbar. The New Java Package wizard opens.
-      </li>
-      <li>
-        Edit the&nbsp;<strong><strong>Source Folder</strong></strong> field to indicate in which container you want the new package to reside. You can either type a path or
-        click&nbsp;<strong><strong>Browse</strong></strong> to find the container. If a folder was selected when you chose to create the new package, that folder appears in
-        the&nbsp;<strong><strong>Source Folder</strong></strong> field as the container for the new package.
-      </li>
-      <li>
-        In the&nbsp;<strong><strong>Name</strong></strong> field, type a name for the new package.
-      </li>
-      <li>
-        Click&nbsp;<strong><strong>Finish</strong></strong> when you are done.
-      </li>
-    </ol>
-    <p>
-      <strong>Note:</strong> the default (unnamed) package always exists and does not need to be created.
-    </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-11.htm">Creating Java elements</a><br>
-       <a href="tasks-51.htm">Moving folders, packages, and files</a><br>
-       <a href="tasks-12.htm">Organizing Java projects</a><br>
-       <a href="tasks-77.htm">Opening a package</a><br>
-       <a href="tasks-90.htm">Renaming a package</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>
-       <a href="../reference/ref-125.htm">New Java Package wizard</a><br>
-       <a href="../reference/ref-128.htm">New Source Folder wizard</a><br>
-       <a href="../reference/ref-3.htm">Java Toolbar actions</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-150.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-150.htm
deleted file mode 100644
index 72f06b9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-150.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Inspecting the result of evaluating an expression
-    </title>
-  </head>
-  <body>
-    <h1>
-      Inspecting the result of evaluating an expression
-    </h1>
-    <p>
-      Inspecting shows the result of evaluating an expression in the Expressions view.
-    </p>
-    <ol>
-      <li>
-        In the scrapbook page, either type an expression or highlight an existing expression to be inspected. For example: <code>System.getProperties();</code>
-      </li>
-      <li>
-        Click the <strong>Inspect</strong> button in the toolbar (or select <strong>Inspect</strong> from the selection's pop-up
-        menu).
-      </li>
-      
-  <li> The result of the inspection appears in a pop-up.&nbsp; </li>
-      <li>
- The result can be inspected like a variable in the debugger (for
-        example, children of the result can be expanded).
-      </li>
-    </ol>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/concepts-11.htm">Scrapbook</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-149.htm">Creating a Java scrapbook page</a><br>
-       <a href="../tasks/tasks-151.htm">Displaying the result of evaluating an expression</a><br>
-       <a href="../tasks/tasks-152.htm">Executing an expression</a><br>
-       <a href="../tasks/tasks-156.htm">Viewing runtime exceptions</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/ref-56.htm">Expressions view</a><br>
-       <a href="../reference/ref-34.htm">Java scrapbook page</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-151.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-151.htm
deleted file mode 100644
index bd1e5ce..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-151.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Displaying the result of evaluating an expression
-    </title>
-  </head>
-  <body>
-    <h1>
-      Displaying the result of evaluating an expression
-    </h1>
-    <p>
-      Displaying shows the result of evaluating an expression in the scrapbook editor.
-    </p>
-    <ol>
-      <li>
-        In the scrapbook page, either type an expression or highlight an existing expression to be displayed. For example: <code>System.getProperties();</code>
-      </li>
-      <li>
-        Click the <strong>Display</strong> button in the toolbar (or select <strong>Display</strong> from the selection's pop-up menu.)
-      </li>
-      <li>
-        The result of the evaluation appears highlighted in the scrapbook editor. The result displayed is either 
-        <ul>
-          <li>
-            the value obtained by sending <code>toString()</code> to the result of the evaluation, or
-          </li>
-          <li>
-            when evaluating a primitive data type (e.g., an <em>int</em> ), the result is the simple value of the result.
-          </li>
-        </ul>
-      </li>
-    </ol>
-    <p>
-      For example:
-    </p>
-    <ul>
-      <li>
-        Type and highlight <code>new java.util.Date()</code> in the editor, and click <strong>Display</strong>. A result such as <code>(java.util.Date) Tue Jun 12
-        14:03:17 CDT 2001</code> appears in the editor.
-      </li>
-      <li>
-        As another example, type and highlight <code>3 + 4</code> in the editor, and press <strong>Display</strong>. The result <code>(int) 7</code> is displayed in the
-        editor.
-      </li>
-    </ul>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/concepts-11.htm">Scrapbook</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-152.htm">Executing an expression</a><br>
-       <a href="../tasks/tasks-150.htm">Inspecting the result of evaluating an expression</a><br>
-       <a href="../tasks/tasks-156.htm">Viewing runtime exceptions</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/ref-34.htm">Java scrapbook page</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-152.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-152.htm
deleted file mode 100644
index 2e99007..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-152.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Executing an expression
-    </title>
-  </head>
-  <body>
-    <h1>
-      Executing an expression
-    </h1>
-    <p>
-      Executing an expression evaluates an expression but does not display a result.
-    </p>
-    <p>
-      If you select the expression to execute and click the <strong>Execute</strong> button in the toolbar, no result is
-      displayed, but the code is executed.&nbsp;&nbsp;
-    </p>
-    <p>
-      For example, if you type and highlight <code>System.out.println(&quot;Hello World&quot;)</code>, and click the <strong>Execute</strong> button, <em>Hello World</em>
-      appears in the Console view, but no result is displayed in the scrapbook editor or the Expressions view.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/concepts-6.htm">Java views</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-151.htm">Displaying the result of evaluating an expression</a><br>
-       <a href="../tasks/tasks-150.htm">Inspecting the result of evaluating an expression</a><br>
-       <a href="../tasks/tasks-156.htm">Viewing runtime exceptions</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/ref-56.htm">Expressions view</a><br>
-       <a href="../reference/ref-45.htm">Console view</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-153.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-153.htm
deleted file mode 100644
index 6cbdb9b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-153.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Using code assist
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Using code assist
-    </h1>
-    <p>
-      The scrapbook editor supports code assist similarly to the regular Java
-      editor.
-    </p>
-    <p>
-      For example, type&nbsp;<em>TestCase&nbsp;</em>in the scrapbook editor and press <kbd>Ctrl+Space</kbd>. Code assist prompts you with possible completions.
-    </p>
-    <img src="../images/tasks-46.png"  alt="A Java editor with a content assist window at the caret position"> 
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-143.htm">Java Content Assist</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-154.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-154.htm
deleted file mode 100644
index 669ad3d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-154.htm
+++ /dev/null

@@ -1,27 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Scrapbook error reporting
-    </title>
-  </head>
-  <body>
-    <h1>
-      Scrapbook error reporting
-    </h1>
-    <p>
-      Java scrapbook errors are reported in the scrapbook page editor.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="tasks-155.htm">Viewing compilation errors</a><br>
-      <a href="tasks-156.htm">Viewing runtime exceptions</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-155.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-155.htm
deleted file mode 100644
index 638289b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-155.htm
+++ /dev/null

@@ -1,29 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Viewing compilation errors
-    </title>
-  </head>
-  <body>
-    <h1>
-      Viewing compilation errors
-    </h1>
-    <p>
-      If you try to evaluate an expression containing a compilation error, it
-      will be reported in the scrapbook editor.
-    </p>
-    <p>
-      For example, type and select the (invalid) expression <code>System.println(&quot;hi&quot;)</code> in the editor and click <strong>Execute</strong> in the toolbar.
-    </p>
-    <p>
-      The error message <em>The method println(java.lang.String) is undefined for the type java.lang.System</em> appears in the editor at the point of the error.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-156.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-156.htm
deleted file mode 100644
index 0722595..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-156.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Viewing runtime exceptions
-    </title>
-  </head>
-  <body>
-    <h1>
-      Viewing runtime exceptions
-    </h1>
-    <p>
-      If an expression you evaluate causes a runtime exception, the exception will be reported in the editor. For example:
-    </p>
-    <p>
-      Type and select the expression <code>Object x = null; x.toString()</code> in the editor and click <strong>Display</strong> in the toolbar.
-    </p>
-    <p>
-      The error message:
-    </p>
-    <p>
-      <em>An exception occurred during evaluation: java.lang.NullPointerException</em>
-    </p>
-    <p>
-      will be displayed in the editor.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/concepts-7.htm">Java editor</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-151.htm">Displaying the result of evaluating an expression</a><br>
-       <a href="../tasks/tasks-150.htm">Inspecting the result of evaluating an expression</a><br>
-       <a href="../tasks/tasks-152.htm">Executing an expression</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-157.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-157.htm
deleted file mode 100644
index aba24cc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-157.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Changing method signature
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    
-<h1> Changing method signature</h1>
-    In addition to renaming a method, you can change other parts of the method's 
-signature. 
-<ul>
-  <li>Select the method in a Java view (e.g. Outline, Package Explorer, Members). 
-  </li>
-  <li> Do one of the following to open the Change Method Signature refactoring dialog: 
-    <ul>
-      <li> From the menu bar, select <strong>Refactor &gt; Change Method Signature</strong> 
-        or </li>
-      <li> From the method's pop-up menu, select <strong>Refactor &gt; </strong><strong>Change 
-        Method Signature</strong></li>
-    </ul>
-  </li>
-</ul>
-    <p>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > <br>
-     <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a> 
-    </p>
-	<p>
- <img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-       <a href="tasks-96.htm">Renaming a method</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-       <a href="../reference/ref-117.htm">Refactoring dialogs</a><br>
-       <a href="../reference/ref-13.htm">Java preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-158.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-158.htm
deleted file mode 100644
index 7d60445..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-158.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Parameters page
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Parameters page
-    </h1>
-    <h1>
-      <img src="../images/tasks-32.png"  alt="Parameters Page for the Reordering method parameters Refactoring Command">
-    </h1>
-    
-<p> Parameters Page for the Change Method Signature Refactoring Command </p>
-<ul>
-  <li>Use the Access Modifier drop-down to control the method's visibility</li>
-  <li>Change the method's return type or name by editing the provided text fields</li>
-  <li>Select one or more parameters and use the <strong>Up</strong> and <strong>Down</strong> 
-    buttons to reorder the parameters (you can see a signature preview below the 
-    parameter list) </li>
-  <li>Use the <b>Add</b> button to add a parameter; you can then edit its type, 
-    name and default value in the table</li>
-  <li>Switch to the <b>Exceptions</b> tab to add or remove thrown exceptions</li>
-  <li> Press <strong>Preview</strong> to see the preview or <strong>OK</strong> 
-    to perform the refactoring without seeing the preview </li>
-</ul>
-    
-<p> This refactoring changes the signature of the selected method and all methods 
-  that override it.<br>
-  Also, all references will be updated to use the signature. </p>
-    <p>
-      Related Topics:
-    </p>
-    <ul>
-      <li>
-        <a href="tasks-82.htm">See Refactoring without Preview</a>
-      </li>
-      <li>
-        <a href="tasks-83.htm">See Refactoring with Preview</a>
-      </li>
-    </ul>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-159.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-159.htm
deleted file mode 100644
index 2c76d72..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-159.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Extracting a local variable
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Extracting a local variable
-    </h1>
-    To extract a local variable from an expression: 
-    <ul>
-      <li>
-        In a Java editor, select the expression that you want to extract to a local variable
-      </li>
-      <li>
-        Do one of the following: 
-        <ul>
-          
-      <li> From the editor's pop-up menu, select <strong>Refactor &gt; Extract 
-        Local Variable</strong> or </li>
-          
-      <li> From the menu bar, select <strong>Refactor &gt; Extract Local Variable</strong> 
-      </li>
-        </ul>
-      </li>
-    </ul>
-    <img src="../images/ngrelr.png" alt="Related reference" border="0" > <br>
-      <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-       <a href="../reference/ref-117.htm">Refactoring dialogs</a><br>
-       <a href="../reference/ref-13.htm">Java preferences</a><br>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-160.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-160.htm
deleted file mode 100644
index 37367d5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-160.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Parameters page
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Parameters page
-    </h1>
-    <h1>
-      <img src="../images/tasks-160a.png"  alt="Parameters Page for the Extracting a local variable Refactoring Command">
-    </h1>
-    <p>
-      Parameters Page for the Extracting Local Variable Refactoring Command
-    </p>
-    <ul>
-      <li>
-        In the Variable name field, enter a name for the extracted variable
-      </li>
-      <li>
-        Optionally, clear the <strong>Replace all occurrences of the selected expression with references to the local variable</strong> checkbox if you want to replace only the
-        expression you selected when invoking the refactoring.
-      </li>
-      <li>
-        Optionally, select <strong>Define the local variable as 'final'</strong>
-      </li>
-      
-  <li> Press <strong>Preview</strong> to see the preview of the changes or <strong>OK</strong> 
-    to perform the refactoring without preview </li>
-    </ul>
-    <p>
-      Related Topics:
-    </p>
-    <ul>
-      <li>
-        <a href="tasks-82.htm">See Refactoring without Preview</a>
-      </li>
-      <li>
-        <a href="tasks-83.htm">See Refactoring with Preview</a>
-      </li>
-    </ul>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-161.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-161.htm
deleted file mode 100644
index 28df4cb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-161.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Inlining a local variable
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Inlining a local variable
-    </h1>
-    To inline a local variable: 
-    <ul>
-      <li>
-        In a Java editor, select the variable that you want to inline (you can select a reference to the variable)
-      </li>
-      <li>
-        Do one of the following: 
-        <ul>
-          
-      <li> From the menu bar, select <strong>Refactor &gt; Inline</strong> or 
-      </li>
-          
-      <li> From the editor's pop-up menu, select <strong>Refactor &gt; Inline</strong> 
-      </li>
-        </ul>
-      </li>
-    </ul>
-    <img src="../images/ngrelr.png" alt="Related reference" border="0" > <br>
-     <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a> <br>
-     <a href="../reference/ref-117.htm">Refactoring dialogs</a> <br>
-     <a href="../reference/ref-13.htm">Java preferences</a> 
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-162.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-162.htm
deleted file mode 100644
index 2f44e4d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-162.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Self encapsulating a field
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Self encapsulating a field
-    </h1>
-    <p>
-      To self-encapsulate a field:
-    </p>
-    <ul>
-      <li>
-        Select the field in one of the Java views (e.g. Outline, Package Explorer or Members view)
-      </li>
-      <li>
-        Do one of the following 
-        <ul>
-          
-      <li> From the menu bar, select <strong>Refactor &gt; Self Encapsulate</strong> 
-        or </li>
-      <li> From the field's pop-up menu, select <strong>Refactor &gt; Self Encapsulate</strong></li>
-        </ul>
-      </li>
-    </ul>
-    You can also invoke this refactoring from the Java editor: 
-    <ul>
-      <li>
-        In the Java editor, select the field (or a reference to it)
-      </li>
-      <li>
-        Do one of the following 
-        <ul>
-          
-      <li> From the menu bar, select <strong>Refactor &gt; Self Encapsulate</strong> 
-        or </li>
-      <li> From the editor's pop-up menu, select <strong>Refactor &gt; Self Encapsulate</strong></li>
-        </ul>
-      </li>
-    </ul>
-	<p>
-    <img src="../images/ngrelr.png" alt="Related reference" border="0" > <br>
-     <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a> <br>
-     <a href="../reference/ref-117.htm">Refactoring dialogs</a> <br>
-     <a href="../reference/ref-13.htm">Java preferences</a> 
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-163.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-163.htm
deleted file mode 100644
index 1b7ec21..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-163.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Parameters page
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Parameters page
-    </h1>
-    <h1>
-      <img src="../images/tasks-163a.png"  alt="Parameters Page for the Self Encapsulate Field Refactoring Command">
-    </h1>
-    <p>
-      Parameters Page for the Self Encapsulate Field Refactoring Command
-    </p>
-    <ul>
-      <li>
-        In the <strong>Getter name</strong> field, enter the name for the getter.
-      </li>
-      <li>
-        In the <strong>Setter name</strong> field, enter the name for the setter.
-      </li>
-      <li>
-        Use the <strong>Insert new method after</strong> combo-box to indicate the location for the getter and/or setter methods.
-      </li>
-      <li>
-        Select one radio button from the <strong>Access modifier</strong> group to specify the new method's visibility.
-      </li>
-      <li>
-        In the class in which the field is declared, read and write accesses can be direct or you can use getter and setter. 
-        <ul>
-          <li>
-            Select the <strong>use getter and setter</strong> radio button if you want the refactoring to convert all these accesses to use getter and setter.
-          </li>
-          <li>
-            Select the <strong>keep field reference</strong> radio button if you do not want the refactoring to modify the current field accesses in the class in which the field is
-            declared.
-          </li>
-        </ul>
-      </li>
-      
-  <li> Press <strong>Preview</strong> to perform refactoring with preview or press 
-    <strong>OK</strong> to perform refactoring without preview. </li>
-    </ul>
-    <p>
-      Related Topics:
-    </p>
-    <ul>
-      <li>
-        <a href="tasks-82.htm">See Refactoring without Preview</a>
-      </li>
-      <li>
-        <a href="tasks-83.htm">See Refactoring with Preview</a>
-      </li>
-    </ul>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-164.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-164.htm
deleted file mode 100644
index c10f1e0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-164.htm
+++ /dev/null

@@ -1,70 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Replacing a local variable with a query
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Replacing a local variable with a query
-    </h1>
-    <p>
-      To replace a local variable with a query:
-    </p>
-    <ul>
-      <li>
-        In the Java editor, select the expression with which the local variable is initialized
-      </li>
-      <li>
-        Invoke the Extract Method refactoring by either: 
-        <ul>
-          
-      <li> Selecting <strong>Refactor &gt; Extract Method</strong> from the editor's 
-        pop-up menu or </li>
-          
-      <li> Selecting <strong>Refactor &gt; Extract Method</strong> from the menu 
-        bar </li>
-        </ul>
-      </li>
-      <li>
-        Perform the Extract Method refactoring
-      </li>
-      <li>
-        Select the local variable (or a reference to it)
-      </li>
-      <li>
-        Invoke the Inline Local Variable by either: 
-        <ul>
-          
-      <li> Selecting <strong>Refactor &gt; Inline</strong> from the editor's pop-up 
-        menu or </li>
-          
-      <li> Selecting <strong>Refactor &gt; Inline</strong> from the menu bar </li>
-        </ul>
-      </li>
-      <li>
-        Perform the Inline Local Variable refactoring
-      </li>
-    </ul>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > <br>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-      <a href="tasks-87.htm">Extracting a method</a><br>
-      <a href="tasks-161.htm">Inlining a local variable</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-       <a href="../reference/ref-117.htm">Refactoring dialogs</a><br>
-       <a href="../reference/ref-13.htm">Java preferences</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-165.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-165.htm
deleted file mode 100644
index bee75a5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-165.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Pulling members up to superclass
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Pulling members up to superclass
-    </h1>
-    To pull up class members (fields and methods) to the class's superclass: 
-    <ul>
-      <li>
-        In a Java view (e.g. Outline, Package Explorer, Members), select the members that you want to pull up.
-      </li>
-      <li>
-        Do on of the following: 
-        <ul>
-          
-      <li> From the menu bar, select <strong>Refactor &gt; Pull Up</strong> or 
-      </li>
-          
-      <li> From the pop-up menu, select <strong>Refactor &gt; Pull Up</strong> 
-      </li>
-        </ul>
-      </li>
-    </ul>
-    <strong>Note:</strong> the selected members must all have the same declaring type for this refactoring to be enabled. 
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-       <a href="../reference/ref-117.htm">Refactoring dialogs</a><br>
-       <a href="../reference/ref-13.htm">Java preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-166.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-166.htm
deleted file mode 100644
index 0c0df07..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-166.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Parameters page
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    
-<h1> Parameters page </h1>
-<h1>&nbsp; </h1>
-    <h1>
-      <img src="../images/tasks-166a.png"  alt="Pulling members up to superclass Refactoring Command">
-    </h1>
-    
-<p> Parameters Page for the Pulling members up to superclass Refactoring Command 
-</p>
-<ul>
-  <li>Select the destination class</li>
-  <li>In the list, select the members that you want to pull up or declare abstract</li>
-  <li>Press the Edit button to specify the action that you want to perform for 
-    the selected members (you can also edit the table cells in-place.)</li>
-  <li> Press <strong>Next</strong> to see the next page or press <strong>Finish</strong> 
-    to perform the refactoring</li>
-</ul>
-<p><img src="../images/tasks-166b.png"  alt="Pull up refactoring dialog"></p>
-<ul>
-  <li>In the left pane, select the methods that you want to be deleted after pull 
-    up (so that the superclass implementation can be used instead). <br>
-    <strong>Note:</strong> the methods originally selected when invoking the refactoring 
-    are pre-selected in the left pane </li>
-  <li> Press <strong>Next</strong> to see the preview or press <strong>Finish</strong> 
-    to perform the refactoring</li>
-</ul>
-    <p>
-      Related Topics:
-    </p>
-    <ul>
-      <li>
-        <a href="tasks-82.htm">See Refactoring without Preview</a>
-      </li>
-      <li>
-        <a href="tasks-83.htm">See Refactoring with Preview</a>
-      </li>
-    </ul>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-167.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-167.htm
deleted file mode 100644
index 6bc16a8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-167.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Moving static members between types
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Moving static members between types
-    </h1>
-    <p>
-       To move static members (fields and methods) between types:
-    </p>
-    <ul>
-      <li>
-        In a Java view, select the static members that you want to move
-      </li>
-      <li>
-        Do one of the following: 
-        <ul>
-          
-      <li> From the menu bar, select <strong>Refactor &gt; Move</strong> or </li>
-          
-      <li> From the pop-up menu select, <strong>Refactor &gt; Move</strong> </li>
-        </ul>
-      </li>
-    </ul>
-    <img src="../images/ngrelr.png" alt="Related reference" border="0" > <br>
-     <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a> <br>
-     <a href="../reference/ref-117.htm">Refactoring dialogs</a> <br>
-     <a href="../reference/ref-13.htm">Java preferences</a><a href="../reference/ref-13.htm"></a> 
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-168.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-168.htm
deleted file mode 100644
index b1efff4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-168.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Parameters page
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Parameters page
-    </h1>
-    <h1>
-      <img src="../images/tasks-168a.png"  alt="Parameters Page for the Moving static members between types Refactoring Command">
-    </h1>
-    <p>
-      Parameters Page for the Moving static members between types Refactoring Command
-    </p>
-    <ul>
-      <li>
-        Use the text field to enter the destination type name or press the <strong>Browse</strong> button to see a list of types.
-      </li>
-      
-  <li> Press <strong>Preview</strong> to see a preview or press <strong>OK</strong> 
-    to perform the refactoring without preview. </li>
-    </ul>
-    <p>
-      Related Topics:
-    </p>
-    <ul>
-      <li>
-        <a href="tasks-82.htm">See Refactoring without Preview</a>
-      </li>
-      <li>
-        <a href="tasks-83.htm">See Refactoring with Preview</a>
-      </li>
-    </ul>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-169.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-169.htm
deleted file mode 100644
index 7a33e5b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-169.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Renaming a field
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Renaming a field
-    </h1>
-    You can rename a field by modifying its declaration in the compilation unit in which it is declared. However, if you also want to update all references to it, do one of the
-    following: 
-    <ol>
-      <li>
-        In a Java view presenting fields (for example in the Outline view) select a field.
-      </li>
-      <li>
-        From the view's pop-up menu, select <strong>Refactor</strong> &gt; <strong>Rename</strong> or select <strong>Refactor &gt; Rename</strong> from the global menu bar.
-      </li>
-    </ol>
-    or 
-    <ol>
-      <li>
-        In a Java editor, select a reference to the field (or the field's declaration).
-      </li>
-      <li>
-        From the editor's pop-up menu, select <strong>Refactor &gt; Rename</strong> or select <strong>Refactor &gt; Rename</strong> from the global menu bar.
-      </li>
-    </ol>
-    <p>
-      <br>
-       <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-       <a href="../reference/ref-117.htm">Refactoring dialogs</a><br>
-       <a href="../reference/ref-13.htm">Java preferences</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-17.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-17.htm
deleted file mode 100644
index 4c3305b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-17.htm
+++ /dev/null

@@ -1,102 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Creating a new Java class
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Creating a new Java class
-    </h1>
-    <p>
-      Use the New Java Class wizard to create a new Java class. There are a number of ways to open this wizard:
-    </p>
-    <ol>
-      <li>
-        Select the container where you want the new class to reside.
-      </li>
-      <li>
-        Click the <strong>New Java Class</strong> button in the workbench toolbar.
-      </li>
-    </ol>
-    <p>
-      or
-    </p>
-    <ol>
-      <li>
-        Select the container where you want the new class to reside.
-      </li>
-      <li>
-        From the container's pop-up menu, select <strong>New</strong> &gt; <strong>Class</strong>.
-      </li>
-    </ol>
-    <p>
-      or
-    </p>
-    <ol>
-      <li>
-        Select the container where you want the new class to reside.
-      </li>
-      <li>
-        From the drop-down menu on the <strong>New</strong> button in the workbench toolbar, select <strong>Class</strong>.
-      </li>
-    </ol>
-    <p>
-      or
-    </p>
-    <ol>
-      <li>
-        Click the <strong>New</strong> button in the workbench toolbar to open the <strong>New</strong> wizard.
-      </li>
-      <li>
-        Select <strong>Class</strong> or <strong>Java &gt; Class</strong> and click <strong>Next</strong>.
-      </li>
-    </ol>
-    <p>
-      or
-    </p>
-    <ol>
-      <li>
-        Select the container where you want the new class to reside.
-      </li>
-      <li>
-        Then, select from the menu bar <strong>File</strong> &gt; <strong>New</strong> &gt; <strong>Class</strong>.
-      </li>
-    </ol>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-11.htm">Creating Java elements</a><br>
-       <a href="tasks-12.htm">Creating a new Java project</a><br>
-       <a href="tasks-18.htm">Creating a top-level class</a><br>
-       <a href="tasks-19.htm">Creating a nested class</a><br>
-       <a href="tasks-20.htm">Creating a class in an existing compilation unit</a><br>
-       <a href="tasks-executionArgs.htm">Setting execution arguments</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>
-       <a href="../reference/ref-121.htm">New Java Project wizard</a><br>
-       <a href="../reference/ref-128.htm">New Source Folder wizard</a><br>
-       <a href="../reference/ref-125.htm">New Java Package wizard</a><br>
-       <a href="../reference/ref-126.htm">New Java Class wizard</a><br>
-       <a href="../reference/ref-3.htm">Java Toolbar actions</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-170.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-170.htm
deleted file mode 100644
index aa303a1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-170.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Parameters page
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Parameters page
-    </h1>
-    <img src="../images/tasks-170a.png"  alt="Parameters Page for the Rename Field Refactoring Command"> 
-    <p>
-      Parameters Page for the Rename Field Refactoring Command
-    </p>
-    <ul>
-      <li>
-        In the <strong>Enter new name</strong> text field, type a new name for the field that you're renaming.
-      </li>
-      <li>
-        If you do not want to update references to the renamed field, deselect the&nbsp;<strong>Update references to the renamed element</strong> checkbox.
-      </li>
-      <li>
-        If you want to update textual references in strings and comments which are referring to the renamed field, select the&nbsp;<strong>Update textual matches in comments and strings</strong> checkbox.
-      </li>
-      <li>
-        If the refactoring finds accessor (getter/setter) methods to the field you're renaming, it offers you to rename them as well (and update all references to them): 
-        <ul>
-          <li>
-            If you want to rename the getter, select the <strong>Rename Getter</strong> checkbox
-          </li>
-          <li>
-            If you want to rename the setter, select the <strong>Rename Setter</strong> checkbox
-          </li>
-        </ul>
-      </li>
-      
-  <li> Click <strong>OK</strong> to perform a quick refactoring, or click&nbsp;<strong>Preview</strong> 
-    to perform a controlled refactoring. </li>
-    </ul>
-    
-<strong>Note:</strong> The refactoring detects getters / setters using preferences 
-set on <strong>Window &gt; Preferences &gt; Java &gt; Code Style</strong> 
-preference page. <br>
-<strong>Note:</strong> References in Javadoc comments, regular comments and string 
-literals are updated based on textual matching. It is recommended that you perform 
-a controlled refactoring and review the suggested changes if you select one of 
-these options. 
-<p>
-      Related Topics:
-    </p>
-    <ul>
-      <li>
-        <a href="tasks-82.htm">See Refactoring without Preview</a>
-      </li>
-      <li>
-        <a href="tasks-83.htm">See Refactoring with Preview</a>
-      </li>
-    </ul>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-171.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-171.htm
deleted file mode 100644
index fece18f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-171.htm
+++ /dev/null

@@ -1,105 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Using templates
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Using templates
-    </h1>
-    <p>
-      To use templates:
-    </p>
-    <ol>
-      <li>
-        In the Java editor, position the caret in a place where you want to insert a template.
-      </li>
-      <li>
-        Invoke content assist by pressing <kbd>Ctrl</kbd>+<kbd>Space</kbd>.
-      </li>
-      <li>
-        Templates appear in the presented list. Note that the list is filtered as you type, so typing a few first characters of a template name will reveal it.
-      </li>
-      <li>
-        Note that a preview is presented for each selected template.
-      </li>
-    </ol>
-    <p>
-      <strong>Notes:</strong>
-    </p>
-    <p>
-      Templates can have variables, which are place-holders for the dynamic part of a template pattern, e.g. subject to change with every application of the particular template.
-    </p>
-    <p>
-      When a template is inserted in the Java editor and the template pattern contained a template variable, the editor enters the template edit mode.
-    </p>
-    <p>
-      A box is drawn around all variables. The first variable is selected and can be modified by typing in the editor.
-      If the same variable existed multiple times in the template pattern, all
-      instances of the same variable are highlighted in blue and updated instantaneously to save typing.
-    </p>
-    <p>
-      Pressing <kbd>Tab</kbd> navigates to the next unique template variable, <kbd>Shift-Tab</kbd> navigates to the previous unique template variable.
-    </p>
-    <p>
-      The template edit mode is left by either pressing <kbd>Tab</kbd> on the last template variable or pressing <kbd>Esc</kbd> or <kbd>Enter</kbd>.
-    </p>
-    <p>
-      Example:
-    </p>
-    <ul>
-      <li>
-        Create a method <code>void m(int[] intarray){}</code> and position the caret inside the method.
-      </li>
-      <li>
-        Type <code>for</code> and press <kbd>Ctrl+Space</kbd> to open Code Assist
-      </li>
-      <li>
-        Select the first entry from the list (i.e.<strong>for - iterate over array</strong>). Note the template preview window.
-      </li>
-      <li>
-        Note also that the name of the array (i.e. <code>intarray</code>) is automatically detected.
-      </li>
-      <li>
-        The local variable <code>i</code> is now selected and you are in the template edit mode.
-		Typing another name instantaneously updates all occurrences of it.
-      </li>
-      <li>
-        Press <kbd>Tab</kbd>. You can now modify the suggested name for the array (pressing <kbd>Shift-Tab</kbd> will let you modify the name of the local variable again).
-      </li>
-      <li>
-        To leave the template edit mode
-        <ul>
-          <li>
-            press <kbd>Tab</kbd> or <kbd>Enter</kbd>, which will move the caret so that you can enter the body of the newly created loop or
-          </li>
-          <li>
-            press <kbd>Esc</kbd>, which will not move the caret and preserves the current selection in the editor.
-          </li>
-        </ul>
-      </li>
-    </ul>
-    <p>
-      <img  src="../images/ngrelc.png" alt="Related concepts" border="0"><br>
-      <a href="../concepts/concepts-7.htm">Java editor</a><br>
-      <a href="../concepts/ctemplates.htm">Templates</a><br>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelt.png" alt="Related tasks"><br>
-      <a href="tasks-54.htm">Using the Java editor</a><br>
-       <a href="tasks-203.htm">Writing your own templates</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference"><br>
-      <a href="../reference/ref-preferences-templates.htm">Templates preference page</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-172.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-172.htm
deleted file mode 100644
index 28e0755..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-172.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Converting line delimiters
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Converting line delimiters
-    </h1>
-    <p>
-      The Java editor can handle Java files with heterogeneous line delimiters.
-      However other external editors or tools may not be able to handle them correctly.
-    </p>
-    <p>
-    If you want to change line delimiters used by your Java files:
-    </p>
-    <ol>
-      <li>
-        Open a Java file in the Java editor
-      </li>
-      <li>
-        Select <strong>File &gt; Convert Line Delimiters To</strong> from the menu bar
-      </li>
-      <li>
-        Select the delimiters to which you want to convert the file to (one of <em>Windows:</em> CRLF, <em>Unix:</em> LF, <em>MacOS 9:</em> CR)
-      </li>
-    </ol>
-    <p>
-      <strong>Notes:</strong>
-    </p>
-    <ul>
-      <li>
-        You can also apply these conversions to multiple files, whole folders or project that are selected in the Package Explorer or in the Navigator.
-      </li>
-      <li>
-        To change the line delimiters used for new files,
-        <ul>
-          <li>
-            set the workspace default (<strong>Window &gt; Preferences &gt; General &gt; Editors &gt; New text file line delimiter</strong>), or
-          </li>
-          <li>
-            set the project-specific default (<strong>Context menu &gt; Properties &gt; Info &gt; New text file line delimiter</strong>)
-          </li>
-        </ul>
-      </li>
-    </ul>
-    
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" ><br>
-    <a href="../concepts/concepts-7.htm">Java editor</a> 
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-      <a href="tasks-54.htm">Using the Java editor</a><a href="tasks-54.htm"></a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-menu-source.htm">Source menu</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-173.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-173.htm
deleted file mode 100644
index 934061c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-173.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Finding and replacing
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Finding and replacing
-    </h1>
-    <p>
-      <img border="0"  src="../images/ngrelt.png" alt="Related tasks"><br>
-      <a href="tasks-54.htm">Using the Java editor</a><br>
-       <a href="tasks-181.htm">Using the Find/Replace dialog</a><br>
-       <a href="tasks-182.htm">Using Incremental Find</a><br>
-       <a href="tasks-187.htm">Finding Next or Previous Match</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-174.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-174.htm
deleted file mode 100644
index 1f35135..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-174.htm
+++ /dev/null

@@ -1,61 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Changing the encoding used to show the source
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Changing the encoding used to show the source
-    </h1>
-    To change the encoding used by the Java editor to display source files: 
-    <ul>
-      <li>
-        With the Java editor open and the file saved, select <strong>Edit &gt; Set Encoding...</strong> from the menu bar
-      </li>
-      <li>
-        Select <strong>Other</strong> and then select an encoding from the menu or type in the encoding's name.
-      </li>
-    </ul>
-    <p>
-      <strong>Notes:</strong>
-    </p>
-    <ul>
-      <li>
-        This setting affects only the way the source is presented--it does not change the file's contents.
-      </li>
-      <li>
-        To change the default encoding used for interpreting text files,
-        <ul>
-          <li>
-            set the workspace default (<strong>Window &gt; Preferences &gt; General &gt; Workspace &gt; Text file encoding</strong>), or
-          </li>
-          <li>
-            set the project- or folder-specific default (<strong>Context menu &gt; Properties &gt; Info &gt; Text file encoding</strong>)
-          </li>
-        </ul>
-        This will change the encoding of all contained files that don't have an explicit encoding set.
-      </li>
-    </ul>
-    
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" ><br>
-       <a href="../concepts/concepts-7.htm">Java editor</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-       <a href="tasks-54.htm">Using the Java editor</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-menu-edit.htm">Edit menu</a><a href="../reference/ref-menu-source.htm"></a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-175.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-175.htm
deleted file mode 100644
index ebccd4a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-175.htm
+++ /dev/null

@@ -1,100 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Using Quick Fix
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Using Quick Fix
-    </h1>
-    To use the Quick Fix feature: 
-<ul>
-      
-  <li> You need to have the <strong>Window &gt; Preferences &gt; Java &gt; Editor 
-    &gt; Report problems as you type</strong> checkbox selected. 
-  </li>
-      <li>
-        In the Java editor, if you see an error or a warning underlined with a squiggly line, position the caret inside the underlined range and do one of the following 
-        <ul>
-          <li>
-            Press <kbd>Ctrl+1</kbd> or
-          </li>
-          <li>
-            From the menu bar, select <strong>Edit &gt; Quick Fix</strong>
-          </li>
-        </ul>
-      </li>
-      <li>
-        A list of suggested corrections is presented, with a preview displayed when an entry is selected.
-      </li>
-      <li>
-        Select an entry form the list and press <kbd>Enter</kbd>.
-      </li>
-    </ul>
-      Light bulb icons appear on the left-hand side vertical ruler to indicate Quick Fix'able problems. You can then click on 
-      one of the the light bulb icons to invoke Quick Fix. 
-    <p>
-      <strong>Note:</strong> Occasionally, invoking Quick Fix will not suggest any corrections. A message saying '<strong>No suggestions available</strong>' will be
-      displayed in such cases.
-    </p>
-    
-    <h1>
-      Using Quick Assist
-    </h1>
-    <p>
-      The Java editor also offers some common code changes even when there's no error or warning in your code.
-      For example, set the caret into the <code>if</code> of the following if-else statement, press <kbd>Ctrl+1</kbd>, and select "Change 'if-else' statements to blocks":
-    </p>
-<pre>
-    String test(int arg) {
-        if (arg > 1000)
-            return "big";
-        else
-            return "small";
-    }
-</pre>
-    <p>
-      Braces are added around the return statements:
-    </p>
-<pre>
-    String test(int arg) {
-        if (arg > 1000) {
-            return "big";
-        } else {
-            return "small";
-        }
-    }
-</pre>
-    <p>
-      Check out the 
-       <a href="../concepts/cquickfix.htm">Available Quick Fix proposals</a>
-       and the 
-       <a href="../concepts/cquickassists.htm">Available Quick Assist proposals</a>, or
-         just press <kbd>Ctrl+1</kbd> to see what quick fixes or quick assists Eclipse offers in your current context.
-    </p>
-    
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" ><br>
-       <a href="../concepts/concepts-7.htm">Java editor</a><br>
-       <a href="../concepts/cquickfix.htm">Available Quick Fix proposals</a><br>
-       <a href="../concepts/cquickassists.htm">Available Quick Assist proposals</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-       <a href="tasks-54.htm">Using the Java editor</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-java-editor-quickfix.htm">Quick Fix</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-176.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-176.htm
deleted file mode 100644
index c962926..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-176.htm
+++ /dev/null

@@ -1,61 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Using Structured Selection
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Using Structured Selection
-    </h1>
-    <p>
-      Structured Selection lets you quickly select Java code in a syntax-aware way.
-    </p>
-    <p>
-      To use Structured Selection:
-    </p>
-    <ul>
-      <li>
-        In a Java editor, (optionally) select some text and press <kbd>Alt+Shift+Arrow Up</kbd> or select <strong>Edit &gt; Expand Selection To &gt; Enclosing
-        Element</strong> from the menu bar.
-      </li>
-      <li>
-        The current text selection is expanded to the inner-most syntax element (more precisely, <u>A</u>bstract <u>S</u>yntax <u>T</u>ree node) that encloses the selection.
-      </li>
-    </ul>
-    When a statement or a list of statements is selected, you can press <kbd>Alt+Shift+Arrow Right</kbd> or select <strong>Edit &gt; Expand Selection To &gt; Next
-    Element</strong>, which will expand the selection with the statement (if any exists) that is immediately <em>after</em> the selected statements. 
-    <p>
-      When a statement or a list of statements is selected, you can press <kbd>Alt+Shift+Arrow Left</kbd> or select <strong>Edit &gt; Expand Selection To &gt; Previous
-      Element</strong>, which will expand the selection with the statement (if any exists) that is immediately <em>before</em> the selected statements.<br>
-    </p>
-    <p>
-      Pressing <kbd>Alt+Shift+Arrow Down</kbd> or selecting <strong>Edit &gt; Expand Selection To &gt; Restore Last Selection</strong> from the menu bar lets you restore
-      the previous structured selection.
-    </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" ><br>
-       <a href="../concepts/concepts-7.htm">Java editor</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-       <a href="tasks-54.htm">Using the Java editor</a><br>
-       <a href="tasks-179.htm">Using Surround with Try/Catch</a><br>
-       <a href="tasks-87.htm">Extracting a method</a><br>
-       <a href="tasks-159.htm">Extracting a local variable</a><br>
-       <a href="tasks-161.htm">Inlining a local variable</a><br>
-       <a href="tasks-164.htm">Replacing a local variable with a query</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-menu-edit.htm">Edit menu</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-177.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-177.htm
deleted file mode 100644
index 25e9855..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-177.htm
+++ /dev/null

@@ -1,83 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Commenting and uncommenting lines of code
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Commenting and uncommenting lines of code
-    </h1>
-    To toggle line comments (<code>// comment</code>) in the Java editor: 
-    <ul>
-      <li>
-        Select the lines you wish to comment or uncomment, or set the caret into a line
-      </li>
-      <li>
-        Do one of the following: 
-        <ul>
-          <li>
-            Press <kbd>Ctrl+/</kbd> or
-          </li>
-          <li>
-            Select <strong>Source &gt; Toggle Comment</strong> from the menu bar
-          </li>
-        </ul>
-      </li>
-    </ul>
-    To insert a block comment (<code>/*comment*/</code>) in the Java editor:
-    <ul>
-      <li>
-        Select the text range you wish to comment
-      </li>
-      <li>
-        Do one of the following 
-        <ul>
-          <li>
-            Press <kbd>Ctrl+Shift+/</kbd> or
-          </li>
-          <li>
-            Select <strong>Source &gt; Add Block Comment</strong> from the menu bar
-          </li>
-        </ul>
-      </li>
-    </ul>
-    To remove a block comment (<code>/*comment*/</code>) in the Java editor: 
-    <ul>
-      <li>
-        Select the text range you wish to uncomment or set the caret into a block comment
-      </li>
-      <li>
-        Do one of the following 
-        <ul>
-          <li>
-            Press <kbd>Ctrl+Shift+\</kbd> or
-          </li>
-          <li>
-            Select <strong>Source &gt; Remove Block Comment</strong> from the menu bar
-          </li>
-        </ul>
-      </li>
-    </ul>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >    <br>
-     <a href="../concepts/concepts-7.htm">Java editor</a> 
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-       <a href="tasks-54.htm">Using the Java editor</a><a href="tasks-54.htm"></a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-menu-source.htm">Source menu</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-178.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-178.htm
deleted file mode 100644
index 0c61ea7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-178.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Shifting lines of code left and right
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Shifting lines of code left and right
-    </h1>
-    To shift lines of code to the right (i.e. indent): 
-    <ul>
-      <li>
-        Select the lines you wish to shift right
-      </li>
-      <li>
-        Do one of the following: 
-        <ul>
-          <li>
-            Press <kbd>Tab</kbd> or
-          </li>
-          <li>
-            Select <strong>Source &gt; Shift Right</strong> from the menu bar
-          </li>
-        </ul>
-      </li>
-    </ul>
-    To shift lines of code to the left (i.e. outdent): 
-    <ul>
-      <li>
-        Select the lines you wish to shift left
-      </li>
-      <li>
-        Do one of the following: 
-        <ul>
-          <li>
-            Press <kbd>Shift+Tab</kbd> or
-          </li>
-          <li>
-            Select <strong>Source &gt; Shift Left</strong> from the menu bar
-          </li>
-        </ul>
-      </li>
-    </ul>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" ><br>
-     <a href="../concepts/concepts-7.htm">Java editor</a> 
-    </p> 
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-       <a href="tasks-54.htm">Using the Java editor</a><a href="tasks-54.htm"></a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-menu-source.htm">Source menu</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-179.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-179.htm
deleted file mode 100644
index c72d86e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-179.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Using Surround with Try/Catch
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Using Surround with Try/Catch
-    </h1>
-    To surround a statement or a set of statements with a try/catch block: 
-    <ul>
-      <li>
-        In the Java editor, select the statement or a set of statements that you want to surround with a try/catch block.
-      </li>
-      <li>
-        Do one of the following: 
-        <ul>
-          <li>
-            From the menu bar, select <strong>Source &gt; Surround with try/catch Block</strong> or
-          </li>
-          <li>
-            From the editors pop-up menu, select <strong>Source &gt; Surround with try/catch Block</strong>
-          </li>
-        </ul>
-      </li>
-      <li>
-        'catch' blocks for all uncaught exceptions (if there are any) are created. If there are no uncaught exceptions, a dialog appears informing you about this fact and
-        asking if you want to create a 'catch' block for java.lang.RuntimeException.
-      </li>
-    </ul>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" ><br>
-     <a href="../concepts/concepts-7.htm">Java editor</a>
-	 </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-       <a href="tasks-54.htm">Using the Java editor</a><br>
-      <a href="tasks-176.htm">Using Structured Selection</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-menu-source.htm">Source menu</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-17b.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-17b.htm
deleted file mode 100644
index ab8a3fa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-17b.htm
+++ /dev/null

@@ -1,95 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Creating a new Java enum
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Creating a new Java enum
-    </h1>
-    <p>
-      Use the New Java Enum wizard to create a new Java enum. There are a number of ways to open this wizard:
-    </p>
-    <ol>
-      <li>
-        Select the container where you want the new enum to reside.
-      </li>
-      <li>
-        Click the <strong>New Java Enum</strong> button in the workbench toolbar.
-      </li>
-    </ol>
-    <p>
-      or
-    </p>
-    <ol>
-      <li>
-        Select the container where you want the new enum to reside.
-      </li>
-      <li>
-        From the container's pop-up menu, select <strong>New</strong> &gt; <strong>Enum</strong>.
-      </li>
-    </ol>
-    <p>
-      or
-    </p>
-    <ol start="1" type="1">
-      <li>
-        Select the container where you want the new enum to reside.
-      </li>
-      <li>
-        From the drop-down menu on the <strong>New</strong> button in the workbench toolbar, select <strong>Enum</strong>.
-      </li>
-    </ol>
-    <p>
-      or
-    </p>
-    <ol>
-      <li>
-        Click the <strong>New</strong> button in the workbench toolbar to open the <strong>New</strong> wizard.
-      </li>
-      <li>
-        Select <strong>Java &gt; Enum</strong> and click <strong>Next</strong>.
-      </li>
-    </ol>
-    <p>
-      or
-    </p>
-    <ol>
-      <li>
-        Select the container where you want the new enum to reside.
-      </li>
-      <li>
-        Then, select from the menu bar <strong>File</strong> &gt; <strong>New</strong> &gt; <strong>Enum</strong>.
-      </li>
-    </ol>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="tasks-94.htm">Renaming a type</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>
-       <a href="../reference/ref-126b.htm">New Java Enum wizard</a><br>
-       <a href="../reference/ref-3.htm">Java Toolbar actions</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-18.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-18.htm
deleted file mode 100644
index 2211b6e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-18.htm
+++ /dev/null

@@ -1,105 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Creating a top-level class
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Creating a top-level class
-    </h1>
-    <p>
-      You can create classes that are not enclosed in other types.
-    </p>
-    <ol>
-      <li>
-        Open the New Class wizard.
-      </li>
-      <li>
-        Edit the&nbsp;<strong>Source Folder</strong> field as needed to indicate in which folder you want the new class to reside. You can either type a path or
-        click the&nbsp;<strong>Browse</strong> button to find the folder. If a folder is found for the current selection, that folder appears in
-        the&nbsp;<strong>Source Folder</strong> field as the container for the new class.
-      </li>
-      <li>
-        In the&nbsp;<strong>Package</strong> field, type or click&nbsp;<strong>Browse</strong> to select the package where you want the new class
-        to reside. Leave this field empty to indicate that you want the new class to be created in the default package.
-      </li>
-      <li>
-        Leave the&nbsp;<strong>Enclosing type</strong> box deselected.
-      </li>
-      <li>
-        In the&nbsp;<strong>Name</strong> field, type a name for the new class.
-        (Optionally, in a 5.0 project, add type parameters enclosed in <strong>&lt;</strong> and <strong>&gt;</strong>).
-      </li>
-      <li>
-        Select the <strong>public</strong> or <strong>default</strong> access modifier using the&nbsp;<strong>Modifiers</strong> radio buttons.<br>
-         <strong>Note:</strong> The private and protected options are available only when creating a class enclosed in a type.
-      </li>
-      <li>
-        Optionally, select the <strong>abstract</strong> or <strong>final</strong> modifier for the new class using the appropriate checkboxes:<br>
-         <strong>Note:</strong> The static option is available only when creating a class enclosed in a type.
-      </li>
-      <li>
-        In the&nbsp;<strong>Superclass</strong> field, type or click&nbsp;<strong>Browse</strong> to select a superclass for the new class.
-        (Optionally, in a 5.0 project, add type arguments enclosed in <strong>&lt;</strong> and <strong>&gt;</strong>).
-      </li>
-      <li>
-        Click the&nbsp;<strong>Add</strong> button to add interfaces for the new class to implement.
-        (Optionally, in a 5.0 project, add type arguments enclosed in <strong>&lt;</strong> and <strong>&gt;</strong>).
-      </li>
-      <li>
-        If you want to create some method stubs in the new class: 
-        <ul>
-          <li>
-            Select the&nbsp;<strong>public static void main(String[] args)</strong> box if you want the wizard to add the main method to the new class, thus
-            making it a starting point of an application.
-          </li>
-          <li>
-            Select the&nbsp;<strong>Constructors from superclass</strong> checkbox if you want the wizard to create, in the new class, a set of constructors, one
-            for each of the constructors declared in the superclass. Each of them will have the same number of parameters (of the same types) as the respective constructor from
-            the superclass.
-          </li>
-          <li>
-            Select the&nbsp;<strong>Inherited abstract methods</strong> checkbox if you want the wizard to generate method stubs for each of the abstract methods
-            that the new class will inherit from its superclass and implemented interfaces.
-          </li>
-        </ul>
-      </li>
-      <li>
-        Click&nbsp;<strong>Finish</strong> when you are done.
-      </li>
-    </ol>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-	</p>
-	<p>
-       <a href="../concepts/concepts-3.htm">Java projects</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-	</p>
-	<p>
-       <a href="tasks-17.htm">Creating a new Java class</a><br>
-       <a href="tasks-19.htm">Creating a nested class</a><br>
-       <a href="tasks-20.htm">Creating a class in an existing compilation unit</a><a href="tasks-20.htm"></a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>
-       <a href="../reference/ref-121.htm">New Java Project wizard</a><br>
-       <a href="../reference/ref-128.htm">New Source Folder wizard</a><br>
-       <a href="../reference/ref-125.htm">New Java Package wizard</a><br>
-       <a href="../reference/ref-126.htm">New Java Class wizard</a><br>
-       <a href="../reference/ref-3.htm">Java Toolbar actions</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-180.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-180.htm
deleted file mode 100644
index 10c085c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-180.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>Using the Externalize Strings Wizard</title>
-  </head>
-  <body>
-    <h1>
-      Using the Externalize Strings Wizard
-    </h1>
-    <p>
-      To open the Externalize Strings wizard, do one of the following: 
-    </p>
-    <ul>
-      <li>
-        Find strings to externalize (using the <strong>Find Strings To Externalize</strong> function), select an entry in the resulting dialog and press the
-        <strong>Externalize</strong> button or
-      </li>
-      
-  <li> Select the compilation unit in which you want to externalize strings and 
-    selecting <strong>Source &gt; Externalize Strings</strong> from the menu bar. 
-  </li>
-    </ul>
-    
-<p> <strong>Note:</strong> Externalizing strings is undoable (with the same restrictions 
-  as for refactorings). Use <strong>Refactor &gt; Undo</strong> from the menu 
-  bar to undo externalizing strings. </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" ><br>
-       <a href="../concepts/cnls.htm">String Externalization</a><br>
-       <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-core-home/documents/3.1/message_bundles.html">Eclipse string externalization mechanism</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-       <a href="tasks-206.htm">Externalizing Strings</a><br>
-       <a href="tasks-100.htm">Undoing a refactoring operation</a><br>
-       <a href="tasks-101.htm">Redoing a refactoring operation</a><br>
-      <a href="tasks-189.htm">Key/value page</a><br>
-       <a href="tasks-190.htm">Property file page</a><a href="tasks-190.htm"></a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-wizard-externalize-strings.htm">Externalize Strings wizard</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-181.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-181.htm
deleted file mode 100644
index dddd966..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-181.htm
+++ /dev/null

@@ -1,95 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>Using the Find/Replace dialog</title>
-  </head>
-
-  <body>
-    <h1>Using the Find/Replace dialog</h1>
-
-    <p>To open the Find / Replace dialog:</p>
-
-    <ol>
-      <li>Optionally, select some text in a text (or Java) editor</li>
-
-      <li>Press <kbd>Ctrl</kbd>+<kbd>F</kbd> or</li>
-
-      <li>From the menu bar, select <span class="control">Edit &gt; Find / Replace</span></li>
-    </ol>
-
-    <p>To use the Find / Replace dialog:</p>
-
-    <ol>
-      <li>In the <span class="control">Find</span> field, enter the text you want to replace</li>
-
-      <li>Optionally, in the <span class="control">Replace With</span> field, enter the next text</li>
-
-      <li>Use the radio buttons in the <span class="control">Direction</span> group to select the direction of finding occurrences (relative to the current caret position)</li>
-
-      <li>
-        In the <span class="control">Scope</span> radio button group: 
-
-        <ul>
-          <li>Select the <span class="control">Selected Lines</span> button if you want to limit find / replace to the lines you selected when opening the dialog</li>
-
-          <li>Select the <span class="control">All</span> button otherwise</li>
-        </ul>
-      </li>
-
-      <li>
-        In the <span class="control">Options</span> group: 
-
-        <ul>
-          <li>Select the <span class="control">Case Sensitive</span> checkbox if you want finding to be case sensitive.</li>
-
-          <li>Select the <span class="control">Whole Word</span> checkbox if you want to find / replace only those occurrences in which the text you entered in the <span class=
-          "control">Find</span> field is a whole word</li>
-
-          <li>Select the <span class="control">Wrap Search</span> checkbox if you want the dialog to continue from the top of the file once the bottom is reached (if you find /
-          replace in Selected Lines only, then this option applies to those lines only)</li>
-
-          <li>Select the <span class="control">Incremental</span> checkbox if you want to perform incremental find (e.g. the dialog will find matching occurrences while you are
-          typing in the Find field)</li>
-
-          <li>Select the <span class="control">Regular Expressions</span> checkbox if you want to perform regex search.
-          When Regular Expressions are enabled, you can use content assist (<kbd>Ctrl+Space</kbd>) in the Find and Replace fields to get support for regex syntax.</li>
-        </ul>
-      </li>
-
-      <li>
-        Press: 
-
-        <ul>
-          <li><span class="control">Find</span> if you want to find the next matching occurrence</li>
-
-          <li><span class="control">Replace</span>, if you want to replace the currently selected occurrence with the new text</li>
-
-          <li><span class="control">Replace / Find</span>, if you want to replace the currently selected occurrence with the new text and find the next matching occurrence</li>
-
-          <li><span class="control">Replace All</span>, if you want to replace all matching occurrences with the new text</li>
-        </ul>
-      </li>
-
-      <li>Press <span class="control">Close</span>.</li>
-    </ol>
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ><br>
-     <a href="../concepts/concepts-7.htm">Java editor</a><br>
-    </p>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-54.htm">Using the Java editor</a><br>
-     <a href="tasks-173.htm">Finding and replacing</a><a href="tasks-173.htm"></a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-menu-edit.htm">Edit menu</a><a href="../reference/ref-menu-edit.htm"></a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-182.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-182.htm
deleted file mode 100644
index 8cceaf9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-182.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>Using Incremental Find</title>
-  </head>
-
-  <body>
-    <h1>Using Incremental Find</h1>
-
-    <p>To use Incremental Find:</p>
-
-    <ol>
-      <li>In the text (or Java) editor, press <kbd>Ctrl</kbd>+<kbd>J</kbd> or select <span class="control">Edit &gt; Incremental Find Next</span> from the menu bar.</li>
-
-      <li>The workbench status line displays "Incremental Find:". The editor is now in the Incremental Find mode.</li>
-
-      <li>As you type, the editor finds the next occurrence of the text and updates the selection after each character typed.</li>
-
-      <li>Navigate to the next or previous match by pressing <kbd>Arrow Down</kbd> or <kbd>Arrow Up</kbd>.</li>
-
-      <li>Undo the last action within the Incremental Find mode by pressing <kbd>Backspace</kbd>.</li>
-
-      <li>You can leave the Incremental Find mode by pressing <kbd>Esc</kbd>.</li>
-    </ol>
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ><br>
-     <a href="../concepts/concepts-7.htm">Java editor</a></p>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-54.htm">Using the Java editor</a><br>
-     <a href="tasks-173.htm">Finding and Replacing</a><br>
-     <a href="tasks-187.htm">Finding Next or Previous Match</a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-menu-edit.htm">Edit menu</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-183.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-183.htm
deleted file mode 100644
index 3f5c544..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-183.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>Showing and hiding empty packages</title>
-  </head>
-
-  <body>
-    <h1>Showing and hiding empty packages</h1>
-
-    <p>To show empty packages:</p>
-
-    <ol>
-      <li>Select the <span class="control">Filters</span> command from the Package Explorer's drop-down menu.</li>
-
-      <li>In the exclude list clear the checkbox for <span class="control">Empty packages</span>.</li>
-    </ol>
-
-    <p>To hide empty packages:</p>
-
-    <ol>
-      <li>Select the <span class="control">Filters</span> command from the Package Explorer's drop-down menu.</li>
-
-      <li>In the exclude list select the checkbox for <span class="control">Empty packages</span>.</li>
-    </ol>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-2.htm">Showing and hiding elements</a><br>
-     <a href="tasks-47.htm">Filtering elements</a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-dialog-java-element-filters.htm">Java Element Filters</a><br>
-     <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-184.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-184.htm
deleted file mode 100644
index 4f061b8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-184.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>Showing and hiding empty parent packages</title>
-  </head>
-
-  <body>
-    <h1>Showing and hiding empty parent packages</h1>
-
-    <p>To show empty parent packages:</p>
-
-    <ol>
-      <li>Select the <span class="control">Filters</span> command from the Package Explorer's drop-down menu.</li>
-
-      <li>In the exclude list clear the checkbox for <span class="control">Empty parent packages</span>.</li>
-    </ol>
-
-    <p>To hide empty parent packages:</p>
-
-    <ol>
-      <li>Select the <span class="control">Filters</span> command from the Package Explorer's drop-down menu.</li>
-
-      <li>In the exclude list select the checkbox for <span class="control">Empty parent packages</span>.</li>
-    </ol>
-
-    <p class="Note">Note: As an example, the parent packages created for package org.eclipse.ui, would be:</p>
-
-    <p>(default package)<br>
-     org<br>
-     org.eclipse</p>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-2.htm">Showing and hiding elements</a><br>
-     <a href="tasks-47.htm">Filtering elements</a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-dialog-java-element-filters.htm">Java Element Filters</a><br>
-     <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-185.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-185.htm
deleted file mode 100644
index b9417af..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-185.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>Showing and hiding Java files</title>
-  </head>
-
-  <body>
-    <h1>Showing and hiding Java files</h1>
-
-    <p>To show Java files:</p>
-
-    <ol>
-      <li>Select the <span class="control">Filters</span> command from the Package Explorer's drop-down menu.</li>
-
-      <li>In the exclude list clear the checkbox for <span class="control">Java files</span>.</li>
-    </ol>
-
-    <p>To hide Java files:</p>
-
-    <ol>
-      <li>Select the <span class="control">Filters</span> command from the Package Explorer's drop-down menu.</li>
-
-      <li>In the exclude list select the checkbox for <span class="control">Java files</span>.</li>
-    </ol>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-2.htm">Showing and hiding elements</a><br>
-     <a href="tasks-47.htm">Filtering elements</a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-dialog-java-element-filters.htm">Java Element Filters</a><br>
-     <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-186.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-186.htm
deleted file mode 100644
index c969cc2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-186.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>Showing and hiding non-Java elements</title>
-  </head>
-
-  <body>
-    <h1>Showing and hiding non-Java elements</h1>
-
-    <p>To show non-Java elements:</p>
-
-    <ol>
-      <li>Select the <span class="control">Filters</span> command from the Package Explorer's drop-down menu.</li>
-
-      <li>In the exclude list clear the checkbox for <span class="control">Non-Java elements</span>.</li>
-    </ol>
-
-    <p>To hide non-Java elements:</p>
-
-    <ol>
-      <li>Select the <span class="control">Filters</span> command from the Package Explorer's drop-down menu.</li>
-
-      <li>In the exclude list select the checkbox for <span class="control">Non-Java elements</span>.</li>
-    </ol>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-2.htm">Showing and hiding elements</a><br>
-     <a href="tasks-47.htm">Filtering elements</a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-dialog-java-element-filters.htm">Java Element Filters</a><br>
-     <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-187.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-187.htm
deleted file mode 100644
index 523cbfb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-187.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>Finding next or previous match</title>
-  </head>
-
-  <body>
-    <h1>Finding next or previous match</h1>
-
-    <p>To find the next match:</p>
-
-    <ol>
-      <li>In the text (or Java) editor, press <kbd>Ctrl</kbd>+<kbd>K</kbd> or select <span class="control">Edit &gt; Find Next</span> from the menu bar.</li>
-
-      <li>The next occurrence of the text selected in the editor will be found.</li>
-    </ol>
-
-    <p>To find the previous match:</p>
-
-    <ol>
-      <li>In the text (or Java) editor, press <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> or select <span class="control">Edit &gt; Find Previous</span> from the menu bar.</li>
-
-      <li>The next occurrence of the text selected in the editor will be found.</li>
-    </ol>
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ><br>
-     <a href="../concepts/concepts-7.htm">Java editor</a></p>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-54.htm">Using the Java editor</a><br>
-     <a href="tasks-173.htm">Finding and Replacing</a><br>
-     <a href="tasks-182.htm">Using Incremental Find</a><a href="tasks-182.htm"></a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-menu-edit.htm">Edit menu</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-188.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-188.htm
deleted file mode 100644
index a68be57..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-188.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>Finding strings to externalize</title>
-  </head>
-
-  <body>
-    <h1>Finding strings to externalize</h1>
-
-    <p>To find strings to externalize:</p>
-
-    
-<ul>
-  <li>In a Java view (e.g. Package Explorer), select a set of packages, source 
-    folders or projects.</li>
-  <li>From the menu bar, select <span class="control">Source &gt; Find Strings 
-    to Externalize</span></li>
-  <li>A dialog comes up with a list of all compilation units that have some non-externalized 
-    strings</li>
-  <li>In the dialog, you can double click on a listed compilation unit or press 
-    the <b>Externalize</b> button to open the Externalize Strings wizard</li>
-</ul>
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ><br>
-     <a href="../concepts/cnls.htm">String Externalization</a></p>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-206.htm">Externalizing Strings</a><br>
-     <a href="tasks-202.htm">Finding unused and incorrectly used keys in property files</a><br>
-     <a href="tasks-180.htm">Using the Externalize Strings wizard</a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-wizard-externalize-strings.htm">Externalize Strings wizard</a><br>
-     <a href="../reference/ref-menu-source.htm">Source menu</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-189.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-189.htm
deleted file mode 100644
index 257b033..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-189.htm
+++ /dev/null

@@ -1,76 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>Key/value page</title>
-  </head>
-
-  <body>
-    <h1>Key/value page</h1>
-
-    
-<h1><img src="../images/tasks-189a.png"  alt="Externalize Strings Key/value page"></h1>
-
-    <p>Externalize Strings Key/value page</p>
-
-    
-<ul>
-  <li>In the <span class="control">Enter common prefix for generated keys</span> 
-    text field, you can specify an optional prefix that will be used for all keys.</li>
-  <li> Select one or more entries in the table and: 
-    <ul>
-      <li>Press the <span class="control">Translate</span> button to mark them 
-        as entries to externalize or</li>
-      <li>Press the <span class="control">Never Translate</span> button to mark 
-        them as entries to be not externalized</li>
-      <li>Press the <span class="control">Skip</span> button to mark them as entries 
-        excluded from externalization</li>
-    </ul>
-  </li>
-  <li>Icons on the left side of the entries are updated and so are the counter 
-    below the table</li>
-  <li>To edit a key, single-click on a row in the <span class="control">Key</span> 
-    column. You can edit the key in-place. You can also press the <b>Edit Key</b> 
-    button and edit the key in the dialog that appears then.</li>
-  <li>Press <span class="control">Next</span> to proceed to the Property File 
-    page or press <span class="control">Finish</span> to externalize strings without 
-    checking the settings from the Property File page (if you are not familiar 
-    with the externalize strings functionality, it is recommended that you press 
-    <span class="control">Next</span> to proceed to the Property File page).</li>
-</ul>
-Note: You can double-click on the icons that are displayed on the left side of 
-the table entries to alternate the state between <span class="control">Translate</span>, 
-<span
-    class="control">Never Translate</span> and <span class="control">Skip</span> 
-<p>Note (explanation of the table entry states):</p>
-
-    <ul>
-      <li>Strings from entries marked as <span class="control">'Translate'</span> will be externalized and marked as such in the Java file by adding non-nls tags.</li>
-
-      <li>Strings from entries marked as <span class="control">'Never Translate'</span> will not be externalized but an non-nls tag will be added to them to inform the wizard that
-      they need not be translated.</li>
-
-      <li>Strings from entries marked as <span class="control">'Skip'</span> will not be externalized and no tags will be added to them.</li>
-    </ul>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-206.htm">Externalizing Strings</a><br>
-     <a href="tasks-180.htm">Using the Externalize Strings wizard</a><br>
-     <a href="tasks-190.htm">Property file page</a><br>
-     <a href="tasks-100.htm">Undoing a refactoring operation</a><br>
-     <a href="tasks-101.htm">Redoing a refactoring operation</a><br>
-     <a href="tasks-82.htm">Refactoring with preview</a><br>
-     <a href="tasks-83.htm">Refactoring without preview</a><br>
-    </p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-wizard-externalize-strings.htm">Externalize Strings wizard</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-19.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-19.htm
deleted file mode 100644
index f87f06a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-19.htm
+++ /dev/null

@@ -1,98 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Creating a nested class
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Creating a nested class
-    </h1>
-    <p>
-      You can create classes that are enclosed in other types (that is, nested classes).
-    </p>
-    <ol>
-      <li>
-        Open the New Java Class wizard.
-      </li>
-      <li>
-        Edit the&nbsp;<strong>Source Folder</strong> field to indicate in which folder you want the new class to reside. You can either type a path or
-        click&nbsp;<strong>Browse</strong> to find the folder. If a folder is found for the current selection, that folder appears in
-        the&nbsp;<strong>Source Folder</strong> field as the container for the new class.
-      </li>
-      <li>
-        Select the&nbsp;<strong>Enclosing Type</strong> checkbox and type the name of the enclosing type in the <strong>Enclosing Type</strong> field. You can
-        also click&nbsp;<strong>Browse</strong> to select the enclosing type for the new class.
-      </li>
-      <li>
-        In the&nbsp;<strong>Name</strong> field, type a name for the new class.
-        (Optionally, in a 5.0 project, add type parameters enclosed in <strong>&lt;</strong> and <strong>&gt;</strong>).
-      </li>
-      <li>
-        Select the desired modifiers by using the&nbsp;<strong>Modifiers</strong> radio buttons and checkboxes.
-      </li>
-      <li>
-        In the&nbsp;<strong>Superclass</strong> field, type or click&nbsp;<strong>Browse</strong> to select a superclass for the new class.
-        (Optionally, in a 5.0 project, add type arguments enclosed in <strong>&lt;</strong> and <strong>&gt;</strong>).
-      </li>
-      <li>
-        Click the&nbsp;<strong>Add</strong> button to add interfaces for the new class to implement.
-        (Optionally, in a 5.0 project, add type arguments enclosed in <strong>&lt;</strong> and <strong>&gt;</strong>).
-      </li>
-      <li>
-        If you want to create some method stubs in the new class:
-      </li>
-      <li>
-        <ul>
-          <li>
-            Select the&nbsp;<strong>public static void main(String[] args)</strong> checkbox if you want the wizard to add the main method to the new class, thus
-            making it a starting point of an application.
-          </li>
-          <li>
-            Select the&nbsp;<strong>Constructors from superclass</strong> checkbox if you want the wizard to create, in the new class, a set of constructors, one
-            for each of the constructors declared in the superclass. Each of them will have the same number of parameters (of the same types) as the respective constructor from
-            the superclass.
-          </li>
-          <li>
-            Select the&nbsp;<strong>Inherited abstract methods</strong> checkbox if you want the wizard to generate method stubs for each of the abstract methods
-            that the new class will inherit from its superclass and implemented interfaces.
-          </li>
-        </ul>
-      </li>
-      <li>
-        Click&nbsp;<strong>Finish</strong> when you are done.
-      </li>
-    </ol>
-    <p>
-      <strong>Note:</strong> The new class is created in the same compilation unit as its enclosing type.
-    </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-	</p>
-	<p>
-       <a href="../concepts/concepts-3.htm">Java projects</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-	</p>
-	<p>	  
-       <a href="tasks-17.htm">Creating a new Java class</a><br>
-       <a href="tasks-18.htm">Creating a top-level class</a><br>
-       <a href="tasks-20.htm">Creating a class in an existing compilation unit</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>	  
-       <a href="../reference/ref-126.htm">New Java Class wizard</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-190.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-190.htm
deleted file mode 100644
index d8bc0a2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-190.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>Property File page</title>
-  </head>
-
-  <body>
-    <h1>Property File page</h1>
-    <img src="../images/tasks-190a.png"  alt="Externalize Strings Property File page"> 
-
-    <p>Externalize Strings Property File page</p>
-
-    <ol>
-      <li>In the <span class="control">Package</span> field, enter the name for the package in which you want the wizard to locate the property file (you can use the <span class=
-      "control">Browse</span> button to display the list of all packages)</li>
-
-      <li>In the Property file name field, enter the name of the property file (new or existing) in which the externalized strings will be put (you can use the <span class=
-      "control">Browse</span> button to display the list of all .properties files located in the package selected in the Package field.)</li>
-
-      <li>Select the <span class="control">Create resource bundle accessor class</span> checkbox if you want to create a class that will be used to access the externalized strings
-      (Note: the class will be reused if it exists already).</li>
-
-      <li>In the <span class="control">Class name</span> field, if you have the above-mentioned checkbox selected, you can specify the name of the accessor class</li>
-
-      <li>Press <span class="control">Next</span> to see a preview of the modifications or press <span class="control">Finish</span> to externalize strings without previewing
-      changes.</li>
-    </ol>
-
-    <p class="Note">Note: The default behavior of the wizard (i.e. creating a class with a name specified in the <span class="control">Class name field</span> and using <span
-    class="control">getString</span> as the name of the method used to retrieve strings from the property file) can be overridden. You may want to do so if you already have an
-    accessor class in another package or your accessor class uses another method with another name to get strings from the property file.</p>
-
-    <ol>
-      <li>Clear the <span class="control">Use default substitution pattern</span> checkbox</li>
-
-      <li>In the <span class="control">Substitution pattern</span> field enter the new pattern that will be used to retrieve strings from the property file. For each externalized
-      string, the first occurrence of <span class="control">${key}</span> will be substituted with the key.</li>
-
-      <li>Use the <span class="control">Add import declaration</span> field if you want the wizard to add an additional import to the compilation unit (you can use the <span
-      class="control">Browse</span> button to help you find a class that you want to import.)</li>
-    </ol>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-206.htm">Externalizing Strings</a><br>
-     <a href="tasks-180.htm">Using the Externalize Strings wizard</a><br>
-     <a href="tasks-189.htm">Key/value page</a><br>
-     <a href="tasks-100.htm">Undoing a refactoring operation</a><br>
-     <a href="tasks-101.htm">Redoing a refactoring operation</a><br>
-     <a href="tasks-82.htm">Refactoring with preview</a><br>
-     <a href="tasks-83.htm">Refactoring without preview</a><a href="tasks-83.htm"></a><br>
-    </p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-wizard-externalize-strings.htm">Externalize Strings wizard</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-191.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-191.htm
deleted file mode 100644
index e9df6b5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-191.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>Showing and hiding members</title>
-  </head>
-
-  <body>
-    <h1>Showing and hiding members</h1>
-
-    <p>Several Java views (e.g. Outline, Package Explorer, Members) offer filtering of members (fields, types and methods). The filters are available as toolbar
-    buttons or as view menu items, depending on the view. There are
-    3 member filters:</p>
-
-    <ul>
-      <li><span class="control">Hide Fields</span>: when activated, this filter causes all fields to be removed from the view.</li>
-
-      <li><span class="control">Hide Static Members</span>: when activated, this filter causes all static members to be removed from the view.</li>
-
-      <li><span class="control">Hide Non-Public Members</span>: when activated, this filter causes all non-public members to be removed from the view.</li>
-    </ul>
-    Additionally, the Package Explorer can display or hide all elements inside compilation units. 
-
-    <p>To show members in the Package Explorer:</p>
-
-    <ul>
-      <li>Select the <span class="control"> Show members in Package Explorer</span> checkbox
-        in the <span class="control">Window &gt; Preferences &gt; Java &gt; Appearance
-        </span>page.</li>
-    </ul>
-    To hide members in the Package Explorer: 
-
-    <ul>
-      <li>Clear the <span class="control"> Show members in Package Explorer</span> checkbox
-        in the <span class="control">Window &gt; Preferences &gt; Java &gt; Appearance
-        </span> page</li>
-    </ul>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-2.htm">Showing and hiding elements</a><br>
-     <a href="tasks-47.htm">Filtering elements</a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-preferences-appearance.htm">Appearance preference page</a><br>
-     <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-192.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-192.htm
deleted file mode 100644
index 7aec359..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-192.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>Showing and hiding override indicators</title>
-  </head>
-
-  <body>
-    <h1>Showing and hiding override indicators</h1>
-
-    <p>Outline and Hierarchy views can show special icons (override indicators) to indicate members that override or implement other members from supertypes.</p>
-
-    <p>To show the override indicators:</p>
-
-    <ul>
-      <li>Select the <span class="control"> Show override indicators in outline and hierarchy</span> checkbox
-        in the <span class="control">Window &gt; Preferences &gt; Java &gt; Appearance
-        </span>page&nbsp;</li>
-    </ul>
-    To hide the override indicators: 
-
-    <ul>
-      <li>Clear the <span class="control"> Show override indicators in outline and hierarchy</span> checkbox
-        in the <span class="control">Window &gt; Preferences &gt; Java &gt; Appearance
-        </span> page&nbsp;</li>
-    </ul>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-2.htm">Showing and hiding elements</a><br>
-     <a href="tasks-47.htm">Filtering elements</a><br>
-     <a href="tasks-47.htm"></a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-preferences-appearance.htm">Appearance preference page</a><br>
-     <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-193.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-193.htm
deleted file mode 100644
index daa3743..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-193.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>Showing and hiding method return types</title>
-  </head>
-
-  <body>
-    <h1>Showing and hiding method return types</h1>
-
-    <p>Several Java views (e.g. Outline, Members) present methods and can also show their return types.</p>
-
-    <p>To show method return types in Java views:</p>
-
-    <ul>
-      <li>Open the <span class="control">Window &gt; Preferences &gt; Java &gt; Appearance</span>
-        page and select the <span class="control">Show method return types</span> checkbox</li>
-    </ul>
-
-    <p>To hide method return types in Java views:</p>
-
-    <ul>
-      <li>Clear the <span class="control"> Show method return types</span> checkbox
-        in the <span class="control">Window &gt; Preferences &gt; Java &gt; Appearance
-        </span> page</li>
-    </ul>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-2.htm">Showing and hiding elements</a><br>
-     <a href="tasks-47.htm">Filtering elements</a><br>
-     <a href="tasks-47.htm"></a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-preferences-appearance.htm">Appearance preference page</a><br>
-     <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-194.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-194.htm
deleted file mode 100644
index 77e8b97..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-194.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>Showing full or compressed package names</title>
-  </head>
-
-  <body>
-    <h1>Showing full or compressed package names</h1>
-
-    <p>Package Explorer and Packages views can show full or compressed package names.</p>
-
-    <p>To show full package names:</p>
-
-    <ul>
-      <li>Clear the <span class="control"> Compress all package name segments, except the final segment</span> checkbox
-        on the <span class="control">Window &gt; Preference &gt; Java &gt; Appearance
-        </span> page</li>
-    </ul>
-    To show compressed package names: 
-
-    <ul>
-      <li>
-        <p>Check the <span class="control"> Compress all package name segments, except the final segment</span> 
-        checkbox on the <span class="control">Window &gt; Preference &gt; Java &gt; Appearance
-        </span> page</p>
-
-        <p>Compression patterns control how many characters of each package name
-        segment are displayed. The last segment of a package name is
-        always displayed.</p>
-        <p>A compression pattern of &quot;.&quot; indicates that only the
-        separating periods are shown to represent a segment. A digit (n)
-        in a compression pattern represents the first n characters of a package name segment.
-        Examples are the best way to understand compression patterns. The
-        package <span class="control">org.eclipse.jdt </span>would be displayed
-        as follows using the example compression patterns:</p>
-        <p> <span class="control">.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>..jdt</p>
-        <p><span class="control">0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>jdt</p>
-        <p><span class="control">2~&nbsp;&nbsp;&nbsp;&nbsp; </span>or~.ec~.jdt</p>
-        <p> <span class="control">3~&nbsp;&nbsp;&nbsp;&nbsp; </span>org.ecl~.jdt</p>
-      </li>
-    </ul>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-preferences-appearance.htm">Java Appearance preference page</a><br>
-     <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-195.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-195.htm
deleted file mode 100644
index 1110187..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-195.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>Sorting elements in Java views</title>
-  </head>
-
-  <body>
-    <h1>Sorting elements in Java views</h1>
-
-    <p>Members and Outline views can present members sorted
-    or in the order of declaration in the compilation unit.</p>
-
-    <p>To sort members:</p>
-
-    <ul>
-      <li>Toggle on the <span class="control">Sort</span> toolbar button in the Java view</li>
-      <li>The sorting order can be configured on the on the Window &gt; Preferences... &gt; Java &gt; Appearance &gt; Members Sort Order page </li>
-      <li>After the above sorting is performed, members in each group are sorted alphabetically</li>
-    </ul>
-    
-    To present members in the order of declaration in the compilation unit. 
-
-    <ul>
-      <li>Toggle off the <span class="control">Sort</span> toolbar button in the Java view</li>
-    </ul>
-    <img src="../images/ngrelr.png" alt="Related reference" border="0" > <br>
-     <a href="../reference/ref-3.htm">Java Toolbar actions</a><a href="../reference/ref-3.htm"></a> 
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-196.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-196.htm
deleted file mode 100644
index 8e432d3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-196.htm
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>Creating Javadoc documentation</title>
-  </head>
-
-  <body>
-    <h1>Creating Javadoc documentation</h1>
-    
-    <p>Select the set (containing one or more elements) of packages, source folders or projects for which you want to generate Javadoc documentation.</p>
-
-    <p>Open the Export wizard by doing one of the following:</p>
-
-    <ul>
-      <li>Selecting <span class="control">Export</span> from the selection's pop-up menu or</li>
-
-      <li>Selecting <span class="control">File &gt; Export</span> from the menu bar.</li>
-    </ul>
-
-    <p>In the resulting dialog, select <span class="control">Javadoc</span> from the list and press <span class="control">Next</span>.</p>
-    <img src="../images/ngrelt.png" alt="Related tasks" border="0" > <br>
-     <a href="tasks-199.htm">Selecting types for Javadoc generation</a> 
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-export-javadoc.htm">Javadoc Generation wizard</a><br>
-     <a href="../reference/ref-dialog-javadoc-location.htm">Javadoc Location property page</a></p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-199.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-199.htm
deleted file mode 100644
index ccf39b3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-199.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>Selecting types for Javadoc generation</title>
-  </head>
-
-  <body>
-    <h1>Selecting types for Javadoc generation</h1>
-
-    <p><img src="../images/tasks-199a.png"  alt="Javadoc wizard page"></p>
-
-    <ul>
-      <li>The JDT uses the Javadoc command (typically available in JRE distributions) to generate Javadoc documentation from source files.
-          To set the location of the Javadoc command, enter the absolute path (e.g. C:\Java\14\jdk1.4\bin\javadoc.exe).</li>
-          
-      <li>In the tree control, select the elements for which you want to generate Javadoc.</li>
-
-      <li>Select the visibility using the radio buttons listed under <span class="control">Create Javadoc for members with visibility</span></li>
-
-      <li>Leave the <span class="control">Use Standard Doclet</span> radio button selected</li>
-
-      <li>Specify the location for the generated Javadoc using the <span class="control">Destination</span> field.</li>
-
-      <li>Press <span class="control">Finish</span> to create generate Javadoc for the elements you selected or press <span class="control">Next</span> to specify more
-      options.</li>
-    </ul>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-196.htm">Creating Javadoc documentation</a><br>
-     <a href="tasks-200.htm">Configuring Javadoc arguments for standard doclet</a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-export-javadoc.htm">Javadoc Generation wizard</a><br>
-     <a href="../reference/ref-dialog-javadoc-location.htm">Javadoc Location property page</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-2.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-2.htm
deleted file mode 100644
index 23c153e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-2.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Microsoft FrontPage 4.0">
-    <title>
-      Showing and hiding elements
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Showing and hiding elements
-    </h1>
-    <p>
-      You can use filters to control which files are displayed in the Package Explorer.
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-3.htm">Showing and hiding system files</a><br>
-       <a href="tasks-4.htm">Showing and hiding CLASS files generated for inner types</a><br>
-       <a href="tasks-5.htm">Showing and hiding libraries</a><br>
-       <a href="tasks-6.htm">Showing single elements or whole Java files</a><br>
-       <a href="tasks-183.htm">Showing and hiding empty packages</a><br>
-       <a href="tasks-184.htm">Showing and hiding empty parent packages</a><br>
-       <a href="tasks-185.htm">Showing and hiding Java files</a><br>
-       <a href="tasks-186.htm">Showing and hiding non-Java elements</a><br>
-       <a href="tasks-213.htm">Showing and hiding non-Java projects in Java views</a><br>
-       <a href="tasks-191.htm">Showing and hiding members in Java views</a><br>
-       <a href="tasks-192.htm">Showing and hiding override indicators</a><br>
-       <a href="tasks-193.htm">Showing and hiding method return types in Java views</a><br>
-       <a href="tasks-212.htm">Showing and hiding import declarations in Java views</a><br>
-       <a href="tasks-214.htm">Showing and hiding package declarations in Java views</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>
-       <a href="../reference/ref-dialog-java-element-filters.htm">Java Element Filters</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-20.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-20.htm
deleted file mode 100644
index effe734..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-20.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Creating a new class in an existing compilation unit
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Creating a new class in an existing compilation unit
-    </h1>
-    <p>
-      An alternative way to create a new class is to add it to an existing compilation unit.
-    </p>
-	<ol>
-    <li>
-      In the Package Explorer, double-click a compilation unit to open it in an editor.
-    </li>
-    <li>
-      Type the code for the class at the desired position in the compilation unit.
-    </li>
-	</ol>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-	</p>
-	<p>
-       <a href="../concepts/concepts-3.htm">Java projects</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-	</p>
-	<p>	  
-       <a href="tasks-17.htm">Creating a new Java class</a><br>
-       <a href="tasks-18.htm">Creating a top-level class</a><br>
-       <a href="tasks-19.htm">Creating a nested class</a><br>
-       <a href="tasks-94.htm">Renaming a class, field, or interface</a><br>
-       <a href="tasks-92.htm">Renaming a compilation unit</a><br>
-       <a href="tasks-executionArgs.htm">Setting execution arguments</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>	  
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-200.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-200.htm
deleted file mode 100644
index 46866f6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-200.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>Configuring Javadoc arguments for standard doclet</title>
-  </head>
-
-  <body>
-    <h1>Configuring Javadoc arguments for standard doclet</h1>
-
-    <p><img src="../images/tasks_200a.png"  alt="Javadoc generation wizard showing the page for specifying arguments for the standard doclet"></p>
-
-    <ul>
-      <li>Use the checkboxes listed under <span class="control">Basic Options</span> to specify Javadoc options.</li>
-
-      <li>You can change the tags that will be documented by using the checkboxes in the <span class="control">Document these tags</span> group.</li>
-
-      <li>If you want references to classes from a library to be linked to the library's Javadoc, select the library in the list and press <span class="control">Configure</span>
-      to specify the location of the library's Javadoc.</li>
-
-      <li>Press <span class="control">Finish</span> to generate Javadoc or press <span class="control">Next</span> to specify additional Javadoc generation options.</li>
-    </ul>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-196.htm">Creating Javadoc documentation</a><br>
-     <a href="tasks-199.htm">Selecting types for Javadoc generation</a><br>
-     <a href="tasks-201.htm">Configuring Javadoc arguments</a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-export-javadoc.htm">Javadoc Generation wizard</a><br>
-     <a href="../reference/ref-dialog-javadoc-location.htm">Javadoc Location property page</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-201.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-201.htm
deleted file mode 100644
index 7a4850b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-201.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>Configuring Javadoc arguments</title>
-  </head>
-
-  <body>
-    <h1>Configuring Javadoc arguments</h1>
-
-    <p><img src="../images/tasks_201a.png"  alt="Javadoc generation wizard"></p>
-
-    <ul>
-      <li>You can specify more specific options for the Javadoc command by entering them in the text area.</li>
-
-      <li>Select the <span class="control">JRE source compatibility level</span>.</li>
-      
-      <li>Select the <span class="control">Save the settings of this Javadoc export as an Ant script</span> checkbox.</li>
-
-      <li>Specify the location for the <span class="control">Ant Script</span>.</li>
-
-      <li>Select the <span class="control">Open generated index file in browser</span> checkbox.</li>
-
-      <li>Press <span class="control">Finish</span> to generate Javadoc.</li>
-    </ul>
-
-    <p class="Note">Note: The output produced by the Javadoc command (including errors and warning) is shown in the Console view.</p>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-
-    <p><a href="tasks-196.htm">Creating Javadoc documentation</a><br>
-     <a href="tasks-199.htm">Selecting types for Javadoc generation</a><br>
-     <a href="tasks-200.htm">Configuring Javadoc arguments for standard doclet</a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-export-javadoc.htm">Javadoc Generation wizard</a><br>
-     <a href="../reference/ref-dialog-javadoc-location.htm">Javadoc Location property page</a><br>
-     &nbsp;</p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-202.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-202.htm
deleted file mode 100644
index df07c1d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-202.htm
+++ /dev/null

@@ -1,66 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>Finding unused and incorrectly used keys in property files</title>
-  </head>
-
-  <body>
-    <h1>Finding unused and incorrectly used keys in property files</h1>
-
-    <p>Finding unused and incorrectly used keys in a property file:</p>
-
-    <ul>
-      <li>
-        Open the Search dialog by: 
-
-        <ul>
-          <li>pressing <kbd>Ctrl</kbd>+<kbd>H</kbd> or</li>
-
-          <li>selecting <span class="control">Search &gt; Search</span> from the menu bar</li>
-        </ul>
-      </li>
-
-      <li>See if a tab called <span class="control">NLS Keys</span> is visible. If it is, then select it.</li>
-
-      <li>If it is not visible, press the <span class="control">Customize</span> button and select the <span class="control">NLS Keys</span> checkbox, press <span class=
-      "control">OK</span> to close the dialog and switch to the <span class="control">NLS Key</span> tab.</li>
-
-      <li>In the <span class="control">Resource bundle accessor class</span> field, enter the name of the class that you use to retrieve strings from the property file. You can
-      use the <span class="control">Browse</span> button to select the class from a list.</li>
-
-      <li>In the <span class="control">Property file name</span> field, enter the name of the property file. You can use the <span class="control">Browse</span> button to select
-      the file.</li>
-
-      <li>Select the scope of the search by using the controls in the <span class="control">Scope</span> group.</li>
-
-      <li>Press <span class="control">Search</span></li>
-    </ul>
-
-    <p>After the search is finished, the Search Result view displays a list of unused keys in the property file and all incorrect references to non-existing keys.</p>
-
-    <p class="Note">Note: This feature assumes that the resource bundle accessor class used a method called <em>getString</em> with a single <em>String</em> parameter to retrieve
-    strings from the property file.</p>
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ><br>
-     <a href="../concepts/cnls.htm">String Externalization</a><br>
-    </p>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-206.htm">Externalizing Strings</a><br>
-     <a href="tasks-188.htm">Finding strings to externalize</a><br>
-     <a href="tasks-180.htm">Using the Externalize Strings wizard</a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-wizard-externalize-strings.htm">Externalize Strings wizard</a><br>
-     <a href="../reference/ref-menu-source.htm">Source menu</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-203.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-203.htm
deleted file mode 100644
index b80658b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-203.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>Writing your own templates</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-
-  <body>
-    <h1>Writing your own templates</h1>
-
-    <p>You can define your own templates.</p>
-
-    <ul>
-      <li>Go to <span class="control">Window &gt; Preferences &gt; Java &gt; Editor &gt; Templates</span> and press the <span class="control">New</span> button.</li>
-
-      <li>In the <span class="control">Name</span> field, enter the name for the template. This name need not be unique. It is used for selecting templates from the Code Assist
-      list.</li>
-
-      <li>
-        Specify the context for the template using the <span class="control">Context</span> combo-box: 
-
-        <ul>
-          <li>Select <span class="control">Java</span> if the template is to be used in normal Java code</li>
-
-          <li>Select <span class="control">javadoc</span> if the template is to be used in Javadoc comments</li>
-        </ul>
-      </li>
-
-      <li>Uncheck the <span class="control">Automatically insert</span> checkbox, if the template should not be inserted automatically if it is the only proposal available at the caret position.</li>
-
-      <li>In the <span class="control">Description</span> field, enter a brief description of the template.</li>
-
-      <li>
-        Use the <span class="control">Pattern</span> text field to enter the template pattern<br>
-         The pattern may contain pre-defined and custom template variables.<br>
-         Template variables are place-holders for the dynamic part of the template pattern, i.e. they are different in every application of the particular template. Before a
-        template is inserted, the variables in its pattern are evaluated and the place-holders are replaced with the evaluated values. Variables are of the form
-        <code>${variable_name}</code>. 
-
-        <ul>
-          <li>To insert a pre-defined template variable, use the <span class="control">Insert Variable</span> button or press <kbd>Ctrl+Space</kbd> and select the variable from
-          the presented list.</li>
-
-          <li>You can insert your own template variables, which will evaluate to the name of the variable itself. You must, however, make sure that the name does not conflict with
-          the pre-defined template variable names in the specific context.</li>
-
-          <li>If the dollar symbol <code>$</code> should be displayed, it must be escaped by using two dollar symbols or by using the variable <code>${dollar}</code>.<br>
-          </li>
-        </ul>
-      </li>
-    </ul>
-
-    <p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-     <a href="../concepts/ctemplates.htm">Templates</a></p>
-
-    <p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-     <a href="tasks-54.htm">Using the Java editor</a><br>
-     <a href="tasks-171.htm">Using templates</a></p>
-
-    <p><img border="0"  src="../images/ngrelr.png" alt="Related reference"><br>
-     <a href="../reference/ref-preferences-templates.htm">Template preference page</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-204.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-204.htm
deleted file mode 100644
index 4d3a48a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-204.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>Renaming a local variable</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-
-  <body>
-    <h1>Renaming a local variable</h1>
-
-    <p>To rename a local variable (or a method parameter):</p>
-
-    <ul>
-      <li>Select the variable (or a reference to it) in the Java editor</li>
-
-      <li>
-        Do one of the following: 
-
-        <ul>
-          <li>From the menu bar, select <span class="control">Refactor &gt; Rename</span> or</li>
-
-          <li>From the editor's pop-up menu, select <span class="control">Refactor &gt; Rename</span></li>
-        </ul>
-      </li>
-    </ul>
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ><br>
-     <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a></p>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-205.htm">Parameters page</a><br>
-     <a href="tasks-159.htm">Extracting a local variable</a><br>
-     <a href="tasks-161.htm">Inlining a local variable</a><br>
-     <a href="tasks-98.htm">Renaming method parameters</a><br>
-     <a href="tasks-157.htm">Changing method signature</a><br>
-     <a href="tasks-164.htm">Replacing a local variable with a query</a><br>
-    </p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-     <a href="../reference/ref-117.htm">Refactoring dialogs</a><br>
-     <a href="../reference/ref-13.htm">Java preferences</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-205.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-205.htm
deleted file mode 100644
index 37fbfe4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-205.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>Parameters page</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-
-  <body>
-    <h1>Parameters page</h1>
-    <img src="../images/tasks_205a.png"  alt="Parameters Page for the Rename Local Variable Refactoring Command"> 
-
-    <p>Parameters Page for the Rename Local Variable Refactoring Command</p>
-
-    <ul>
-      <li>In the <span class="control"><span class="control">Enter new name</span></span> field, type a new name for the local variable.</li>
-
-      <li>If you do not want to update references to the renamed local variable, deselect the <span class="control"><span class="control">Update references to the renamed
-      element</span></span> checkbox.</li>
-
-      
-  <li>Click <span class="control"><span class="control">OK</span></span> to perform 
-    a quick refactoring, or click&nbsp;<span class="control"><span class=
-      "control">Preview</span></span> to perform a controlled refactoring.</li>
-    </ul>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-204.htm">Renaming a local variable</a><br>
-     <a href="tasks-82.htm">See Refactoring without Preview</a><br>
-     <a href="tasks-83.htm">See Refactoring with Preview</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-206.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-206.htm
deleted file mode 100644
index 09ba281..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-206.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>Externalizing Strings</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-
-  <body>
-    <h1>Externalizing Strings</h1>
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ><br>
-     <a href="../concepts/concepts-7.htm">Java editor</a><br>
-     <a href="../concepts/cnls.htm">String Externalization</a></p>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-188.htm">Finding strings to externalize</a><br>
-     <a href="tasks-202.htm">Finding unused and incorrectly used keys in property files</a><br>
-     <a href="tasks-180.htm">Using the Externalize Strings wizard</a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-wizard-externalize-strings.htm">Externalize Strings wizard</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-207.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-207.htm
deleted file mode 100644
index 7f9889b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-207.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Inlining a constant
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    
-<h1> Inlining a constant</h1>
-    To inline a constant: 
-<ul>
-      
-  <li> In a Java editor or in one of the Java views, select the constant that 
-    you want to inline (you can select a reference to the constant) </li>
-      <li>
-        Do one of the following: 
-        <ul>
-          
-      <li> From the menu bar, select <strong>Refactor &gt; Inline</strong> or 
-      </li>
-          
-      <li> From the editor's pop-up menu, select <strong>Refactor &gt; Inline</strong> 
-      </li>
-        </ul>
-      </li>
-    </ul>
-    <img src="../images/ngrelr.png" alt="Related reference" border="0" > <br>
-     <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a> <br>
-     <a href="../reference/ref-117.htm">Refactoring dialogs</a> <br>
-     <a href="../reference/ref-13.htm">Java preferences</a> 
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-208.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-208.htm
deleted file mode 100644
index 783f33e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-208.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Inlining a method
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    
-<h1> Inlining a method</h1>
-    To inline a method: 
-<ul>
-      
-  <li> In a Java editor or in one of the Java views, select the method that you 
-    want to inline (you can also select an invocation site of the method) </li>
-      <li>
-        Do one of the following: 
-        <ul>
-          
-      <li> From the menu bar, select <strong>Refactor &gt; Inline</strong> or 
-          </li>
-          
-      <li> From the editor's pop-up menu, select <strong>Refactor &gt; Inline</strong> 
-          </li>
-        </ul>
-      </li>
-    </ul>
-    <img src="../images/ngrelr.png" alt="Related reference" border="0" > <br>
-     <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a> <br>
-     <a href="../reference/ref-117.htm">Refactoring dialogs</a> <br>
-     <a href="../reference/ref-13.htm">Java preferences</a> 
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-209.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-209.htm
deleted file mode 100644
index 62121b9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-209.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Extracting a constant
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    
-<h1> Extracting a constant</h1>
-    To extract a constant from an expression: 
-<ul>
-  <li> In a Java editor, select the expression that you want to extract to a constant</li>
-  <li> Do one of the following: 
-    <ul>
-      <li> From the editor's pop-up menu, select <strong>Refactor &gt; Extract 
-        Constant</strong> or </li>
-      <li> From the menu bar, select <strong>Refactor &gt; Extract Constant</strong></li>
-    </ul>
-  </li>
-</ul>
-    <img src="../images/ngrelr.png" alt="Related reference" border="0" > <br>
-      <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-       <a href="../reference/ref-117.htm">Refactoring dialogs</a><br>
-       <a href="../reference/ref-13.htm">Java preferences</a><br>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-21.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-21.htm
deleted file mode 100644
index a1e0d74..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-21.htm
+++ /dev/null

@@ -1,98 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Creating a new Java interface
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Creating a new Java interface
-    </h1>
-    <p>
-      Use the New Java Interface wizard to create a new Java interface. There are a number of ways to open this wizard:
-    </p>
-    <ol>
-      <li>
-        Select the container where you want the new class to reside.
-      </li>
-      <li>
-        From the drop-down menu on the <strong>New Java Class</strong> button in the workbench toolbar, select <strong>Interface</strong>.
-      </li>
-    </ol>
-    <p>
-      or
-    </p>
-    <ol>
-      <li>
-        Select the container where you want the new class to reside.
-      </li>
-      <li>
-        From the container's pop-up menu, select <strong>New</strong> &gt; <strong>Interface</strong>.
-      </li>
-    </ol>
-    <p>
-      or
-    </p>
-    <ol>
-      <li>
-        Select the container where you want the new class to reside.
-      </li>
-      <li>
-        From the drop-down menu on the <strong>New</strong> button in the workbench toolbar, select <strong>Interface</strong>.
-      </li>
-    </ol>
-    <p>
-      or
-    </p>
-    <ol>
-      <li>
-        Click the <strong>New</strong> button in the workbench toolbar to open the <strong>New</strong> wizard.
-      </li>
-      <li>
-        Select <strong>Interface</strong> or <strong>Java &gt; Interface</strong> and click <strong>Next</strong>.
-      </li>
-    </ol>
-    <p>
-      or
-    </p>
-    <ol>
-      <li>
-        Select the container where you want the new interface to reside.
-      </li>
-      <li>
-        Then, select from the menu bar <strong>File</strong> &gt; <strong>New</strong> &gt; <strong>Interface</strong>.
-      </li>
-    </ol>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-23.htm">Creating a top-level interface</a><br>
-       <a href="tasks-24.htm">Creating a nested interface</a><br>
-       <a href="tasks-25.htm">Creating a new interface in an existing compilation unit</a><br>
-       <a href="tasks-94.htm">Renaming a type</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>
-       <a href="../reference/ref-127.htm">New Java Interface wizard</a><br>
-       <a href="../reference/ref-3.htm">Java Toolbar actions</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-210.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-210.htm
deleted file mode 100644
index a5d5be2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-210.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Moving an instance method to a component
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    
-<h1> Moving an instance method to a component</h1>
-    
-<p> To move an instance method to a component: </p>
-    <ul>
-      
-  <li> In a Java view or in the Java editor, select the method that you want to 
-    move </li>
-      <li>
-        Do one of the following: 
-        <ul>
-          <li>
-            From the menu bar, select <strong>Refactor &gt; Move</strong> or
-          </li>
-          <li>
-            From the pop-up menu select, <strong>Refactor &gt; Move</strong>
-          </li>
-        </ul>
-      </li>
-    </ul>
-    <img src="../images/ngrelr.png" alt="Related reference" border="0" > <br>
-     <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a> <br>
-     <a href="../reference/ref-117.htm">Refactoring dialogs</a> <br>
-     <a href="../reference/ref-13.htm">Java preferences</a><a href="../reference/ref-13.htm"></a> 
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-211.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-211.htm
deleted file mode 100644
index fa0c90a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-211.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Converting a local variable to a field
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-<h1> Converting a local variable to a field</h1>
-To convert a local variable to a field: 
-<ul>
-  <li> In a Java editor or in one of the Java views, select the local variable</li>
-  <li> Do one of the following: 
-    <ul>
-      <li> From the menu bar, select <strong>Refactor &gt; Convert Local Variable 
-        to Field</strong> or </li>
-      <li> From the editor's pop-up menu, select <strong>Refactor &gt; Convert 
-        Local Variable to Field</strong></li>
-    </ul>
-  </li>
-</ul>
-    <img src="../images/ngrelr.png" alt="Related reference" border="0" > <br>
-     <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a> <br>
-     <a href="../reference/ref-117.htm">Refactoring dialogs</a> <br>
-     <a href="../reference/ref-13.htm">Java preferences</a> 
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-212.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-212.htm
deleted file mode 100644
index 766892e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-212.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>Showing and hiding import declarations</title>
-  </head>
-
-  <body>
-    <h1>Showing and hiding import declarations</h1>
-
-    <p>To show import declarations:</p>
-
-    <ol>
-      <li>Select the <span class="control">Filters</span> command from the Package Explorer's drop-down menu.</li>
-
-      <li>In the exclude list clear the checkbox for <span class="control">Import declarations</span>.</li>
-    </ol>
-
-    <p>To hide non-Java elements:</p>
-
-    <ol>
-      <li>Select the <span class="control">Filters</span> command from the Package Explorer's drop-down menu.</li>
-
-      <li>In the exclude list select the checkbox for <span class="control">Import declarations</span>.</li>
-    </ol>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-2.htm">Showing and hiding elements</a><br>
-     <a href="tasks-47.htm">Filtering elements</a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-dialog-java-element-filters.htm">Java Element Filters</a><br>
-     <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-213.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-213.htm
deleted file mode 100644
index 8d391e8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-213.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>Showing and hiding non-Java projects</title>
-  </head>
-
-  <body>
-    <h1>Showing and hiding non-Java projects</h1>
-
-    <p>To show non-Java projects:</p>
-
-    <ol>
-      <li>Select the <span class="control">Filters</span> command from the Package Explorer's drop-down menu.</li>
-
-      <li>In the exclude list clear the checkbox for <span class="control">Non-Java projects</span>.</li>
-    </ol>
-
-    <p>To hide non-Java elements:</p>
-
-    <ol>
-      <li>Select the <span class="control">Filters</span> command from the Package Explorer's drop-down menu.</li>
-
-      <li>In the exclude list select the checkbox for <span class="control">Non-Java projects</span>.</li>
-    </ol>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-2.htm">Showing and hiding elements</a><br>
-     <a href="tasks-47.htm">Filtering elements</a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-dialog-java-element-filters.htm">Java Element Filters</a><br>
-     <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-214.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-214.htm
deleted file mode 100644
index 3321ac7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-214.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>Showing and hiding package declarations</title>
-  </head>
-
-  <body>
-    <h1>Showing and hiding package declarations</h1>
-
-    <p>To show package declarations:</p>
-
-    <ol>
-      <li>Select the <span class="control">Filters</span> command from the Package Explorer's drop-down menu.</li>
-
-      <li>In the exclude list clear the checkbox for <span class="control">Package declarations</span>.</li>
-    </ol>
-
-    <p>To hide package declarations:</p>
-
-    <ol>
-      <li>Select the <span class="control">Filters</span> command from the Package Explorer's drop-down menu.</li>
-
-      <li>In the exclude list select the checkbox for <span class="control">Package declarations</span>.</li>
-    </ol>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-2.htm">Showing and hiding elements</a><br>
-     <a href="tasks-47.htm">Filtering elements</a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-dialog-java-element-filters.htm">Java Element Filters</a><br>
-     <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-216.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-216.htm
deleted file mode 100644
index 511686e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-216.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Converting an anonymous inner class to a nested class
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-<h1> Converting an anonymous inner class to a nested class</h1>
-To convert an anonymous inner class to a nested class: 
-<ul>
-  <li> In a Java editor, position the care inside the anonymous class</li>
-  <li> Do one of the following: 
-    <ul>
-      <li> From the menu bar, select <strong>Refactor &gt; Convert Anonymous Class 
-        to Nested</strong> or </li>
-      <li> From the editor's pop-up menu, select <strong>Refactor &gt; Convert 
-        Anonymous Class to Nested</strong></li>
-    </ul>
-  </li>
-</ul>
-    <img src="../images/ngrelr.png" alt="Related reference" border="0" > <br>
-     <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a> <br>
-     <a href="../reference/ref-117.htm">Refactoring dialogs</a> <br>
-     <a href="../reference/ref-13.htm">Java preferences</a> 
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-217.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-217.htm
deleted file mode 100644
index 59a70b9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-217.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Converting a nested type to a top level type
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-<h1> Converting a nested type to a top level type</h1>
-To convert a nested type to a top level type: 
-<ul>
-  <li> In a Java editor or a Java view, select the member type</li>
-  <li> Do one of the following: 
-    <ul>
-      <li> From the menu bar, select <strong>Refactor &gt; Convert Nested Type 
-        to Top Level</strong> or </li>
-      <li> From the editor's pop-up menu, select <strong>Refactor &gt; Convert 
-        Nested Type to Top Level</strong> </li>
-    </ul>
-  </li>
-</ul>
-    <img src="../images/ngrelr.png" alt="Related reference" border="0" > <br>
-     <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a> <br>
-     <a href="../reference/ref-117.htm">Refactoring dialogs</a> <br>
-     <a href="../reference/ref-13.htm">Java preferences</a> 
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-218.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-218.htm
deleted file mode 100644
index 64a83f6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-218.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Extracting an interface from a type
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-<h1> Extracting an interface from a type</h1>
-To extract an interface from a type: 
-<ul>
-  <li> In a Java editor or a Java view, select the type from which you want to 
-    extract an interface</li>
-  <li> Do one of the following: 
-    <ul>
-      <li> From the menu bar, select <strong>Refactor &gt; Extract Interface</strong> 
-        or </li>
-      <li> From the editor's pop-up menu, select <strong>Refactor &gt; Extract 
-        Interface</strong> </li>
-    </ul>
-  </li>
-</ul>
-    <img src="../images/ngrelr.png" alt="Related reference" border="0" > <br>
-     <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a> <br>
-     <a href="../reference/ref-117.htm">Refactoring dialogs</a> <br>
-     <a href="../reference/ref-13.htm">Java preferences</a> 
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-219.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-219.htm
deleted file mode 100644
index 4959d8d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-219.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Replacing references to a type with references to one of its supertypes
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-<h1> Replacing references to a type with references to one of its supertypes</h1>
-To replace references to a type with references to one of its supertypes: 
-<ul>
-  <li> In a Java editor or a Java view, select the type</li>
-  <li> Do one of the following: 
-    <ul>
-      <li> From the menu bar, select <strong>Refactor &gt; Use Supertype Where 
-        Possible</strong> or </li>
-      <li> From the editor's pop-up menu, select <strong>Refactor &gt; Use Supertype 
-        Where Possible</strong> </li>
-    </ul>
-  </li>
-</ul>
-    <img src="../images/ngrelr.png" alt="Related reference" border="0" > <br>
-     <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a> <br>
-     <a href="../reference/ref-117.htm">Refactoring dialogs</a> <br>
-     <a href="../reference/ref-13.htm">Java preferences</a> 
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-21b.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-21b.htm
deleted file mode 100644
index baaf049..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-21b.htm
+++ /dev/null

@@ -1,95 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Creating a new Java annotation
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Creating a new Java annotation
-    </h1>
-    <p>
-      Use the New Java Annotation wizard to create a new Java annotation. There are a number of ways to open this wizard:
-    </p>
-    <ol>
-      <li>
-        Select the container where you want the new class to reside.
-      </li>
-      <li>
-        From the drop-down menu on the <strong>New Java Class</strong> button in the workbench toolbar, select <strong>Annotation</strong>.
-      </li>
-    </ol>
-    <p>
-      or
-    </p>
-    <ol>
-      <li>
-        Select the container where you want the new class to reside.
-      </li>
-      <li>
-        From the container's pop-up menu, select <strong>New</strong> &gt; <strong>Annotation</strong>.
-      </li>
-    </ol>
-    <p>
-      or
-    </p>
-    <ol>
-      <li>
-        Select the container where you want the new class to reside.
-      </li>
-      <li>
-        From the drop-down menu on the <strong>New</strong> button in the workbench toolbar, select <strong>Annotation</strong>.
-      </li>
-    </ol>
-    <p>
-      or
-    </p>
-    <ol>
-      <li>
-        Click the <strong>New</strong> button in the workbench toolbar to open the <strong>New</strong> wizard.
-      </li>
-      <li>
-        Select <strong>Java &gt; Annotation</strong> and click <strong>Next</strong>.
-      </li>
-    </ol>
-    <p>
-      or
-    </p>
-    <ol>
-      <li>
-        Select the container where you want the new annotation to reside.
-      </li>
-      <li>
-        Then, select from the menu bar <strong>File</strong> &gt; <strong>New</strong> &gt; <strong>Annotation</strong>.
-      </li>
-    </ol>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="tasks-94.htm">Renaming a type</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>
-       <a href="../reference/ref-127b.htm">New Java Annotation wizard</a><br>
-       <a href="../reference/ref-3.htm">Java Toolbar actions</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-220.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-220.htm
deleted file mode 100644
index d6ca707..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-220.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Pushing members down to subclasses
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    
-<h1> Pushing members down to subclasses</h1>
-    To push down class members (fields and methods) to the class's subclasses: 
-<ul>
-      
-  <li> In a Java view (e.g. Outline, Package Explorer, Members), select the members 
-    that you want to push down. </li>
-      <li>
-        Do on of the following: 
-        <ul>
-          
-      <li> From the menu bar, select <strong>Refactor &gt; Push Down</strong> 
-        or </li>
-      <li> From the pop-up menu, select <strong>Refactor &gt; Push Down</strong></li>
-        </ul>
-      </li>
-    </ul>
-    <strong>Note:</strong> the selected members must all have the same declaring type for this refactoring to be enabled. 
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-       <a href="../reference/ref-117.htm">Refactoring dialogs</a><br>
-       <a href="../reference/ref-13.htm">Java preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-221.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-221.htm
deleted file mode 100644
index c30abb8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-221.htm
+++ /dev/null

@@ -1,97 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Creating a new source folder with exclusion filter
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Creating a new source folder with exclusion filter
-    </h1>
-    In a project that uses source folders, you can create a new folder to contain Java source code with exclusion patterns. Exclusion
-    patterns are useful if you have nested source folders. There are two ways to do it:
-    <ol>
-    	<li>You don't already have an existing Java project in which you want to create a source folder with exclusion pattern.</li>
-    	<li>You already have an existing Java project.</li>
-    </ol>
-    <h2>Starting from scratch</h2>
-    <ol>
-	  <li>First follow the steps of the task &quot;Creating a new source folder&quot;.</li>
-      <li>Once a first source folder is created, if you want to create another source folder that is nested inside the first one, you
-      need to use the exclusion pattern.
-      </li>
-      <li>
-        Open the <a href="../reference/ref-123.htm">Java Build Path</a> page <strong>(Project &gt; Properties &gt; Java Build Path)</strong> and click the <strong>Source</strong> tab.
-      </li>
-      <li>
-        Click <strong>Add Folder</strong>, select an existing source folder, and click <strong>Create New Folder</strong> to create a folder that is nested inside the first one.
-      </li>
-      <li>You will get a dialog saying that exclusion filter has been added to the first source folder.
-      <blockquote>NOTE: The trailing '/' at the end of the exclusion pattern <b>is required</b> to exclude the children of this folder.
-      The exclusion pattern follows the ant exclusion pattern syntax.
-      </blockquote>
-      </li>
-      <li>
-        Click&nbsp;<strong>OK</strong> and <strong>Finish</strong> when you are done.
-      </li>
-    </ol>
-    <h2>From an existing Java Project</h2>
-    <ol>
-      <li>Before you start, make sure that your project properties are enabled to handle exclusion filters in source folders.
-      </li>
-      <li>
-        In the Package Explorer, select the project where you want the new source folder to reside.
-      </li>
-      <li>
-        From the project's pop-up menu, select <strong>New</strong> &gt; <strong>Source Folder</strong>. The New Source Folder wizard opens.
-      </li>
-      <li>
-        In the&nbsp;<strong>Project Name</strong> field, the name of the selected project appears. If you need to edit this field, you can either type a path or
-        click&nbsp;<strong>Browse</strong> to choose a project that uses source folders.
-      </li>
-      <li>
-        In the&nbsp;<strong>Folder Name</strong> field, type a name for the new source folder. If you choose a path that is nested
-        inside an existing source folder, you will see an error saying that you have nested source folders.
-      </li>
-      <li>
-        Check&nbsp;<strong>Update exclusion filters in other source folders to solve nesting</strong>.
-      </li>
-      <li>
-        Click&nbsp;<strong>Finish</strong> when you are done.
-      </li>
-    </ol>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-	 </p>
-	 <p>	  
-       <a href="../concepts/concepts-3.htm">Java projects</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-	 </p>
-	 <p>
-       <a href="tasks-11.htm">Creating Java elements</a><br>
-       <a href="tasks-12.htm">Creating a new Java project</a><br>
-       <a href="tasks-15.htm">Creating a new Java package</a><br>
-       <a href="tasks-13.htm">Creating a Java project as its own source container</a><br>
-       <a href="tasks-14.htm">Creating a Java project with source folders</a><br>
-       <a href="tasks-26.htm">Creating a new source folder</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	 </p>
-	 <p>	  
-       <a href="../reference/ref-128.htm">New Source Folder wizard</a><br>
-       <a href="../reference/ref-3.htm">Java Toolbar actions</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-222.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-222.htm
deleted file mode 100644
index 8098cff..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-222.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Creating a new source folder with specific output folder
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Creating a new source folder with specific output folder
-    </h1>
-	Any source folder can use either the default project output folder or its specific output folder.
-    <ol>
-	  <li>First follow the steps of the task &quot;Creating a new source folder&quot;.</li>
-      <li>Once a first source folder is created, you might want to change its default output folder.
-      </li>
-	  <li>Click on <strong>Allow output folders for source folders</strong>. This adds a new entry to the source folder tree.
-	  </li>
-	  <li>Expand the source folder tree.
-	  </li>
-	  <li>Double-click on the <strong>Output folder entry</strong>.
-	  </li>
-	  <li>A dialog asks you if you want to use the project's default output folder or a specific output folder. Choose the second
-	  option and click <strong>Browse...</strong>.
-	  </li>
-	  <li>Select the folder you want and click <strong>OK</strong> and then <strong>Finish</strong>.
-	  </li>
-    </ol>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-	 </p>
-	 <p>	  
-       <a href="../concepts/concepts-3.htm">Java projects</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-	 </p>
-	 <p>
-       <a href="tasks-11.htm">Creating Java elements</a><br>
-       <a href="tasks-12.htm">Creating a new Java project</a><br>
-       <a href="tasks-15.htm">Creating a new Java package</a><br>
-       <a href="tasks-13.htm">Creating a Java project as its own source container</a><br>
-       <a href="tasks-14.htm">Creating a Java project with source folders</a><br>
-       <a href="tasks-26.htm">Creating a new source folder</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	 </p>
-	 <p>	  
-       <a href="../reference/ref-123.htm">Java Build Path</a><br>
-       <a href="../reference/ref-128.htm">New Source Folder wizard</a><br>
-       <a href="../reference/ref-3.htm">Java Toolbar actions</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-223.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-223.htm
deleted file mode 100644
index 65cc636..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-223.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Replacing a single reference to a type with a reference to one of its supertypes
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-<h1> Replacing a single reference to a type with a reference to one of its supertypes</h1>
-To replace a single reference to a type with a reference to one of its supertypes: 
-<ul>
-  <li> In the Java editor, select the type reference, or the declaration of a field, parameter, or local variable</li>
-  <li> Do one of the following: 
-    <ul>
-      <li> From the menu bar, select <strong>Refactor &gt; Generalize Declared Type</strong> or </li>
-      <li> From the editor's pop-up menu, select <strong>Refactor &gt; Generalize Declared Type</strong> </li>
-    </ul>
-  </li>
-</ul>
-<p>You will be prompted for the type to which you would like to update the reference.  If the
-   reference can be safely changed to the new type, the refactoring proceeds.</p>
-
-    <img src="../images/ngrelr.png" alt="Related reference" border="0" > <br>
-     <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a> <br>
-     <a href="../reference/ref-117.htm">Refactoring dialogs</a> <br>
-     <a href="../reference/ref-13.htm">Java preferences</a> 
-    
-  </body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-224.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-224.htm
deleted file mode 100644
index adbbf05..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-224.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Replacing an expression with a method parameter
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-<h1> Replacing an expression with a method parameter </h1>
-To replace an expression with a method parameter: 
-<ul>
-  <li> In the Java editor, select the expression</li>
-  <li> Do one of the following: 
-    <ul>
-      <li> From the menu bar, select <strong>Refactor &gt; Introduce Parameter</strong> or </li>
-      <li> From the editor's pop-up menu, select <strong>Refactor &gt; Introduce Parameter</strong> </li>
-    </ul>
-  </li>
-</ul>
-  <p>
-  The highlighted expression will be replaced with a reference to a new method parameter.
-  Callers of the method will be updated to pass the expression as the value of the new parameter.
-  </p>
-  <p>
-  <strong>Note:</strong> this refactoring may result in non-compiling code if the highlighted
-  expression explicitly or implicitly references <code>this</code>.
-  </p>
-    <img src="../images/ngrelr.png" alt="Related reference" border="0" > <br>
-     <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a> <br>
-     <a href="../reference/ref-117.htm">Refactoring dialogs</a> <br>
-     <a href="../reference/ref-13.htm">Java preferences</a> 
-    
-  </body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-225.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-225.htm
deleted file mode 100644
index 8c458fe..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-225.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Replacing constructor calls with factory method invocations
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-<h1> Replacing constructor calls with factory method invocations </h1>
-To replace calls to a constructor with calls to an equivalent factory method: 
-<ul>
-  <li> In a Java editor or Java view, select the constructor declaration</li>
-  <li> Do one of the following: 
-    <ul>
-      <li> From the menu bar, select <strong>Refactor &gt; Introduce Factory</strong> or </li>
-      <li> From the pop-up menu, select <strong>Refactor &gt; Introduce Factory</strong> </li>
-    </ul>
-  </li>
-</ul>
-  <p>
-  You will be asked what to name the new factory method, on what class it should be placed,
-  and whether to make the constructor private when the refactoring is complete.  When the
-  refactoring executes, it will create the new factory method, which will call the selected
-  constructor and return the created object.  All references to the constructor will be
-  replaced by calls to the new factory method.
-  </p>
-    <img src="../images/ngrelr.png" alt="Related reference" border="0" > <br>
-     <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a> <br>
-     <a href="../reference/ref-117.htm">Refactoring dialogs</a> <br>
-     <a href="../reference/ref-13.htm">Java preferences</a> 
-    
-  </body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-226.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-226.htm
deleted file mode 100644
index 502abda..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-226.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Inferring type parameters for generic type references
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-<h1> Inferring type parameters for generic type references </h1>
-Eclipse can attempt to infer type parameters for all generic type references in a 
-class, package, or project.  This is especially useful when migrating from Java 1.4 code
-to Java 5.0 code, allowing you to automatically make use of the generic classes in 
-Java's collections API.
-<ul>
-  <li> Open a class in the Java editor, or in a Java view, select a class, package, or project. </li>
-  <li> Do one of the following: 
-    <ul>
-      <li> From the menu bar, select <strong>Refactor &gt; Infer Generic Type Arguments</strong> or </li>
-      <li> From the pop-up menu, select <strong>Refactor &gt; Infer Generic Type Arguments</strong> </li>
-    </ul>
-  </li>
-</ul>
-  <p>
-  You will be given a dialog with two configurable options:
-  <ul>
-  <li><strong>Assume clone() returns an instance of the receiver type</strong>
-  Well-behaved classes generally respect this rule, but if you know that your
-  code violates it, uncheck the box.</li>
-  <li><strong>Leave unconstrained type arguments raw (rather than inferring &lt;?&gt;).</strong>
-  If there are no constraints on the elements of e.g. <code>ArrayList a</code>, unchecking this
-  box will cause Eclipse to still provide a wildcard parameter, replacing the reference with 
-  <code>ArrayList&lt;?&gt; a</code>.</li>
-  </ul>
-  
-  Press <strong>OK</strong> or <strong>Preview</strong> to continue with the operation.
-  </p>
-  <p><strong>Note</strong>: It may in some cases be impossible to assign
-  consistent type parameters in a selection, or require deeper analysis
-  than Eclipse can perform.
-  </p>
-    <img src="../images/ngrelr.png" alt="Related reference" border="0" > <br>
-     <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a> <br>
-     <a href="../reference/ref-117.htm">Refactoring dialogs</a> <br>
-     <a href="../reference/ref-13.htm">Java preferences</a> 
-    
-  </body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-23.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-23.htm
deleted file mode 100644
index e68ae7a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-23.htm
+++ /dev/null

@@ -1,77 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Creating a top-level interface
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Creating a top-level interface
-    </h1>
-    <p>
-      You can create interfaces that are not enclosed in other types.
-    </p>
-    <ol>
-      <li>
-        Open the New Java Interface wizard.
-      </li>
-      <li>
-        Edit the&nbsp;<strong>Source Folder</strong> field as needed to indicate in which folder you want the new interface to reside. You can either type a path
-        or click the&nbsp;<strong>Browse</strong> button to find the folder. If a folder is found for the current selection, that folder appears in
-        the&nbsp;<strong>Source Folder</strong> field as the container for the new interface.
-      </li>
-      <li>
-        In the&nbsp;<strong>Package</strong> field, type a name or click&nbsp;<strong>Browse</strong> to select the package where you want the
-        new interface to reside. If you want the new interface to be created in the default package, leave this field empty.
-      </li>
-      <li>
-        Clear the&nbsp;<strong>Enclosing type</strong> checkbox.
-      </li>
-      <li>
-        In the&nbsp;<strong>Name</strong> field, type a name for the new interface.
-        (Optionally, in a 5.0 project, add type parameters enclosed in <strong>&lt;</strong> and <strong>&gt;</strong>).
-      </li>
-      <li>
-        Select the <strong>public</strong> or <strong>default</strong> access modifier using the&nbsp;<strong>Modifiers</strong> radio buttons.
-      </li>
-      <li>
-        Click the&nbsp;<strong>Add</strong> button to add interfaces for the new interface to extend.
-        (Optionally, in a 5.0 project, add type arguments enclosed in <strong>&lt;</strong> and <strong>&gt;</strong>).
-      </li>
-      <li>
-        Click&nbsp;<strong>Finish</strong>.
-      </li>
-    </ol>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-21.htm">Creating a new Java interface</a><br>
-       <a href="tasks-24.htm">Creating a nested interface</a><br>
-       <a href="tasks-25.htm">Creating a new interface in a compilation unit</a><br>
-       <a href="tasks-94.htm">Renaming a type</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-   </p>
-    <p>	  
-       <a href="../reference/ref-127.htm">New Java Interface wizard</a><br>
-       <a href="../reference/ref-3.htm">Java Toolbar actions</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-230.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-230.htm
deleted file mode 100644
index 8fe5305..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-230.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) Red Hat Incorporated 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Using the Formatter Application
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Using the Formatter Application
-    </h1>
-    <p>
- 	The JDT has a commandline Eclipse Application that allows users to format Java source code either with 
- 	the Eclipse default code formatter options or with custom options.
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-66.htm">Formatting Java Code</a><br>
-      <a href="tasks-231.htm">Running the Formatter Application</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-17.htm">CodeFormatter</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-231.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-231.htm
deleted file mode 100644
index 79a97d0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-231.htm
+++ /dev/null

@@ -1,78 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) Red Hat Incorporated 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Running the Formatter Application
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Running the Formatter Application
-    </h1>
-    <p>
-    Running the Formatter Application is as simple as running the org.eclipse.jdt.core.JavaCodeFormatter application from the commandline:
-    <pre>
-    eclipse -vm &lt;path to virtual machine&gt; -application org.eclipse.jdt.core.JavaCodeFormatter [ OPTIONS ] &lt;files&gt;
-    </pre>
-    <table border="1" cellspacing="0" cellpadding="5" width="600">
-      <tr>
-        <td width="25%">&lt;files&gt;</td> 
-        <td>Java source files and/or directories to format. Only files ending with .java will be formatted in the given directory.</td>
-      </tr>
-    </table>
-    </p>
-    <p>
-    <table border="1" cellspacing="0" cellpadding="5" width="600">
-    	<thead>
-		<tr>
-			<th><p>OPTIONS</p></th>
-			<th><p>Description</p></th>
-		</tr>
-	    </thead>
-	    <tbody>
-		<tr>
-			<td valign="top" width="25%"><p>-config &lt;file&gt;</p></td>
-			<td valign="top"><p>Use the formatting style from the specified properties file. 
-			                    Refer to <a href="tasks-232.htm">Generating a config file for the Formatter Application</a>
-			                    for details.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%"><p>-help</p></td>
-			<td valign="top"><p>Display the help message.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%"><p>-quiet</p></td>
-			<td valign="top"><p>Only print error messages.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%"><p>-verbose</p></td>
-			<td valign="top"><p>Be verbose about the formatting job.</p>
-			</td>
-		</tr>
-		</tbody>
-	</table>
-    </p>
-    
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-66.htm">Formatting Java Code</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-17.htm">CodeFormatter</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-232.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-232.htm
deleted file mode 100644
index 61d23a8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-232.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) Red Hat Incorporated 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Generating a config file for the Formatter Application
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Generating a config file for the Formatter Application
-    </h1>
-    <p>
-    Generating a config file for the Formatter Application involves modifying the code formatter settings
-    for a Java Project and copying org.eclipse.jdt.core.prefs out of the .settings directory for that project.
-    </p>
-    <ol>
-      <li>
-        Select a java project, open the pop-up menu and choose <strong>Properties</strong>.
-      </li>
-
-      <li>
-        Select the <strong>Code Style &gt; Formatter</strong> page and check <strong>Enable project specific sttings</strong>.
-      </li>
-      <li>
-        Select or edit a profile as explained above.
-      </li>
-
-      <li>
-        Click <strong>OK</strong> when you are done.
-      </li>
-      
-      <li>
-        Use either a file manager or the command line to copy <b><code>workspace/YourJavaProject/.settings/org.eclipse.jdt.core.prefs</code></b>
-        to a new location.
-      </li>
-      
-    </ol>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-68.htm">Setting code formatting preferences</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-17.htm">Code Formatter</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-233.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-233.htm
deleted file mode 100644
index cf66ca0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-233.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) Red Hat Incorporated 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Code Clean Up
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Code Clean Up
-    </h1>
-    <p>
-    The 'Clean Up' action can be executed on a single Java file, a Java package, a Java project or on multiple projects
-    by selecting the Java elements and executing source -> Clean Up...
-    </p>
-    <p>
-    The 'Clean Up' action allows to enforce a code style standard on multiple files or on a whole project. It also
-    allows to apply quick fixes in batch to remove warnings, potential programming problems, unnecessary or unused code.
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-234.htm">The Clean Up Wizard</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-234.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-234.htm
deleted file mode 100644
index 304468f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-234.htm
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) Red Hat Incorporated 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      The Clean Up Wizard
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      The Clean Up Wizard
-    </h1>
-    <p>
-    The Clean Up wizard allows to select the cleanups to apply to the selected compilation units.
-    </p>
-    <p>
-    Each tab shows on the left side the cleanups and there options and on the right side
-    a preview. The preview reflects the resulting changes in the code when the cleanups are executed.
-    </p>
-    <p>
-    The selected options are saved when the wizard is closed and restored the next time the wizard is opened.
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-233.htm">Code Clean Up</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-24.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-24.htm
deleted file mode 100644
index 219c9e6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-24.htm
+++ /dev/null

@@ -1,83 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Creating a nested interface
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Creating a nested interface
-    </h1>
-    <p>
-      You can create interfaces that are enclosed in other types (that is, nested interfaces).
-    </p>
-    <ol>
-      <li>
-        Open the New Java Interface wizard.
-      </li>
-      <li>
-        Edit the&nbsp;<strong>Source Folder</strong> field to indicate in which folder you want the new interface to reside. You can either type a path or click
-        the&nbsp;<strong>Browse</strong> button to find the folder. If a folder is found for the current selection, that folder appears in the
-        <strong>Source&nbsp;</strong>Folder field as the container for the new interface.
-      </li>
-      <li>
-        Select the&nbsp;<strong>Enclosing type</strong> checkbox.
-      </li>
-      <li>
-        In the&nbsp;<strong>Enclosing type</strong> field, type the name of the enclosing type or click the&nbsp;<strong>Browse</strong> button
-        to select the enclosing type for the new interface.
-      </li>
-      <li>
-        In the&nbsp;<strong>Name</strong> field, type a name for the new interface.
-        (Optionally, in a 5.0 project, add type parameters enclosed in <strong>&lt;</strong> and <strong>&gt;</strong>).
-      </li>
-      <li>
-        Select the <strong>public</strong> or <strong>default</strong> access modifier by using the&nbsp;<strong>Modifiers</strong> radio buttons.
-      </li>
-      <li>
-        Select the&nbsp;<strong>static</strong> checkbox if you want the new interface to be static.
-      </li>
-      <li>
-        Click the&nbsp;<strong>Add</strong> button to add interfaces for the new interface to extend.
-        (Optionally, in a 5.0 project, add type arguments enclosed in <strong>&lt;</strong> and <strong>&gt;</strong>).
-      </li>
-      <li>
-        Click&nbsp;<strong>Finish</strong> when you are done.
-      </li>
-    </ol>
-    <p>
-      <strong>Note</strong>: The new interface is created in the same compilation unit as its enclosing type.
-    </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-21.htm">Creating a new Java interface</a><br>
-       <a href="tasks-23.htm">Creating a top-level interface</a><br>
-       <a href="tasks-25.htm">Creating a new interface in a compilation unit</a><br>
-       <a href="tasks-94.htm">Renaming a type</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-   </p>
-    <p>	  
-       <a href="../reference/ref-127.htm">New Java Interface wizard</a><br>
-       <a href="../reference/ref-3.htm">Java Toolbar actions</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a><a href="../reference/ref-view-package-explorer.htm"></a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-25.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-25.htm
deleted file mode 100644
index b0b75e5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-25.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Creating a new interface in an existing compilation unit
-    </title>
-  </head>
-  <body>
-    <h1>
-      Creating a new interface in an existing compilation unit
-    </h1>
-    <p>
-      An alternative way to create a new interface is to add it to an existing compilation unit.
-    </p>
-	<ol>
-    <li>
-      In the Package Explorer, double-click a compilation unit.
-    </li>
-    <li>
-      Type the code for the interface at the desired position in the compilation unit.
-    </li>
-	</ol>
-    <p>
-      <img  src="../images/ngrelc.png" alt="Related concepts" border="0">
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelt.png" alt="Related tasks">
-    </p>
-    <p>
-      <a href="tasks-11.htm">Creating Java elements</a><br>
-       <a href="tasks-21.htm">Creating a new Java interface</a><br>
-       <a href="tasks-24.htm">Creating a nested interface</a><br>
-       <a href="tasks-23.htm">Creating a top-level interface</a><br>
-       <a href="tasks-92.htm">Renaming a compilation unit</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-26.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-26.htm
deleted file mode 100644
index 225a1df..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-26.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Creating a new source folder
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Creating a new source folder
-    </h1>You can create a new folder to contain Java source code using the New Source Folder wizard.<ol>
-      <li>
-        In the Package Explorer, select the project where you want the new source folder to reside.
-      </li>
-      <li>
-        From the project's pop-up menu, select <strong>New</strong> &gt; <strong>Source Folder</strong>. The New Source Folder wizard opens.
-      </li>
-      <li>
-        In the&nbsp;<strong>Project Name</strong> field, the name of the selected project appears. If you need to edit this field, you can either type a path or
-        click&nbsp;<strong>Browse</strong> to choose a project that uses source folders.
-      </li>
-      <li>
-        In the&nbsp;<strong>Folder Name</strong> field, type a name for the new source folder.
-      </li>
-	<li>If the new folder nests with an existing source folder you can check <strong>Update
-	exclusion filters in other source folders to solve nesting</strong>. Otherwise you have to use the 
-	<a href="../reference/ref-123.htm">Java Build Path</a> page <strong>(Project
-	&gt; Properties &gt; Java Build Path)</strong> to fix the nesting conflict by removing other source folders.</li>
-	<li>
-        Click&nbsp;<strong>Finish</strong> when you are done.
-      </li>
-    </ol>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-	 </p>
-	 <p>	  
-       <a href="../concepts/concepts-3.htm">Java projects</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-	 </p>
-	 <p>
-       <a href="tasks-11.htm">Creating Java elements</a><br>
-       <a href="tasks-12.htm">Creating a new Java project</a><br>
-       <a href="tasks-15.htm">Creating a new Java package</a><br>
-       <a href="tasks-13.htm">Creating a Java project as its own source container</a><br>
-       <a href="tasks-14.htm">Creating a Java project with source folders</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	 </p>
-	 <p>	  
-       <a href="../reference/ref-123.htm">Java Build Path</a><br>
-       <a href="../reference/ref-128.htm">New Source Folder wizard</a><br>
-       <a href="../reference/ref-3.htm">Java Toolbar actions</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-27.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-27.htm
deleted file mode 100644
index e85d1f6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-27.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Creating a new Java Scrapbook Page
-    </title>
-  </head>
-  <body>
-    <h1>
-      Creating a new Java Scrapbook Page
-    </h1>
-    <p>
-      You can create a new Java scrapbook page using any one of several different approaches. <a href="tasks-149.htm">See Creating a Scrapbook Page</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-3.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-3.htm
deleted file mode 100644
index c6811a3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-3.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Microsoft FrontPage 4.0">
-    <title>
-      Showing and hiding system files
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Showing and hiding system files
-    </h1>
-    To show system files: 
-    <ol>
-    <li>
-      Select the <strong>Filters</strong> command from the Package Explorer view drop-down menu.
-    </li>
-    <li>
-      In the exclude list clear the checkbox for <span class="control">.* files</span>.
-    </li>
-    </ol>
-    <p>
-      To hide system files:
-    </p>
-    <ol>
-    <li>
-      Select the <strong>Filters</strong> command from the Package Explorer view drop-down menu.
-    </li>
-    <li>
-      In the exclude list select the checkbox for <span class="control">.* files</span>.
-      This hides files that have only a file extension but no file name, such as <em>.classpath</em>.
-    </li>
-	</ol>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>	
-       <a href="tasks-2.htm">Showing and hiding elements</a><br>
-       <a href="tasks-47.htm">Filtering elements</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>	  
-       <a href="../reference/ref-dialog-java-element-filters.htm">Java Element Filters</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-30.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-30.htm
deleted file mode 100644
index 1fd100d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-30.htm
+++ /dev/null

@@ -1,66 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Adding a JAR file as a library
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Adding a JAR file as a library
-    </h1>
-    <p>
-      To add a JAR file as a library, you can either drag and drop the JAR file into the workbench from the file system or you can use the Import wizard to import the file.
-    </p>
-    <ol>
-      <li>
-        From the workbench menu bar, select <strong>File</strong> &gt; <strong>Import</strong>. The Import wizard opens
-      </li>
-      <li>
-        Select <strong>File System</strong>, then click <strong>Next</strong>.
-      </li>
-      <li>
-        In the <strong>From directory</strong> field, type or browse to select the directory where the JAR file resides.
-      </li>
-      <li>
-        In the import selection panes, expand the hierarchy and use the buttons to select the JAR file you want to import.
-      </li>
-      <li>
-        In the <strong>Into folder</strong> field, type or browse to select a workbench container for the JAR file.
-      </li>
-      <li>
-        Click <strong>Finish</strong> when you are done.
-      </li>
-      <li>
-        You now must add the JAR file to the build class path of any projects that need this library.
-      </li>
-    </ol>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/concepts-4.htm">Java builder</a><br>
-       <a href="../concepts/cbuildcp.htm">Build classpath</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-113.htm">Adding a JAR file to the build path</a><br>
-       <a href="tasks-115.htm">Attaching source to a JAR file</a><br>
-       <a href="tasks-110.htm">Working with build paths</a><br>
-       <a href="tasks-31.htm">Adding source code as individual files</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-   </p>
-    <p>	  
-       <a href="../reference/ref-123.htm">Java Build Path</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-31.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-31.htm
deleted file mode 100644
index b9579c4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-31.htm
+++ /dev/null

@@ -1,138 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Adding source code as individual files
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Adding source code as individual files
-    </h1>
-    <h2>
-      From a ZIP or JAR file
-    </h2>
-    <ol>
-      <li>
-        In the Navigator or Package Explorer, you can optionally select the source folder into which you wish to import the source. <em>Note: It is important to choose a source
-        container; otherwise, the imported files will not be on the build path.</em>
-      </li>
-      <li>
-        From the workbench menu bar, select <strong>File</strong> &gt; <strong>Import</strong>.
-      </li>
-      <li>
-        In the Import wizard, select <strong>Zip file</strong>, then click&nbsp;<strong>Next</strong>.
-      </li>
-      <li>
-        In the&nbsp;<strong>Zip file</strong> field, type or browse to select the file from which you would like to add the resources. In the import selection
-        panes, use the following methods to select exactly the resources you want to add: 
-        <ul>
-          <li>
-            Expand the hierarchies in the left pane and check or clear the boxes representing the containers in the selected directory. Then in the right pane, select or clear
-            boxes for individual files.
-          </li>
-          <li>
-            Click <strong>Select Types</strong> to select specific file types to add.
-          </li>
-          <li>
-            Click <strong>Select All</strong> to select all files in the directory, then go through and deselect the ones that you don't want to add.
-          </li>
-          <li>
-            Click <strong>Deselect All</strong> to deselect all files in the directory, then go through and choose individual files to add.
-          </li>
-        </ul>
-      </li>
-      <li>
-        In the <strong>Select the destination for imported resources</strong> field, type or browse to select a workbench container for the added resources (if it was not
-        already selected when you activated the&nbsp;<strong>Import</strong> command).
-      </li>
-      <li>
-        In the <strong>Options</strong> area, you can choose whether or not to overwrite existing resources without warning.
-      </li>
-      <li>
-        Click <strong>Finish</strong> when you are done.
-      </li>
-    </ol>
-    <h2>
-      From a directory
-    </h2>
-    <ol>
-      <li>
-        In the Navigator or Package Explorer, select the source folder into which you wish to import the source. <em>Note: It is important to choose a source container; otherwise,
-        the imported files will not be on the build path.</em>
-      </li>
-      <li>
-        From the workbench menu bar, select <strong>File</strong> &gt; <strong>Import</strong>.
-      </li>
-      <li>
-        In the import wizard, select <strong>File System</strong>, then click&nbsp;<strong>Next</strong>.
-      </li>
-      <li>
-        In the <strong>Directory</strong> field, type or browse to select the directories from which you would like to add the resources.
-      </li>
-      <li>
-        In the import selection panes, use the following methods to select exactly the resources you want to add: 
-        <ul>
-          <li>
-            Expand the hierarchies in the left pane and check or clear the boxes representing the containers in the selected directory. Then in the right pane, select or clear
-            boxes for individual files.
-          </li>
-          <li>
-            Click&nbsp;<strong>Select Types</strong> to select specific file types to add.
-          </li>
-          <li>
-            Click&nbsp;<strong>Select All</strong> to select all files in the directory, then go through and deselect the ones that you don't want to add.
-          </li>
-          <li>
-            Click&nbsp;<strong>Deselect All</strong> to deselect all files in the directory, then go through and choose individual files to add.
-          </li>
-        </ul>
-      </li>
-      <li>
-        In the <strong>Select the destination for imported resources</strong> field, type or browse to select a workbench container for the added resources (if
-        it was not already selected when you activated the&nbsp;<strong>Import</strong> command).
-      </li>
-      <li>
-        In the <strong>Options</strong> area, you can choose whether you want to:
-      </li>
-	  <ul>
-      <li>
-        overwrite existing resources without warning
-      </li>
-      <li>
-        create a complete file structure for the imported files
-      </li>
-	  </ul>
-      <li>
-        Click&nbsp;<strong>Finish</strong> when you are done.
-      </li>
-    </ol>
-	<p>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-	</p>
-	<p>
-     <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a> <br>
-     <a href="../concepts/cbuildcp.htm">Build classpath</a> </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-	</p>
-	<p>
-       <a href="tasks-30.htm">Adding a JAR file as a library</a><br>
-       <a href="tasks-110.htm">Working with build paths</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>
-       <a href="../reference/ref-123.htm">Java Build Path</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-32.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-32.htm
deleted file mode 100644
index 17a0e47..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-32.htm
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-	   Creating JAR files
-    </title>
-  </head>
-  <body>
-    <h1>
-      Creating JAR files
-    </h1>
-    <p>
-      You can create and regenerate JAR files in the workbench.
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-33.htm">Creating a new JAR file</a><br>
-       <a href="tasks-36.htm">Regenerating a JAR file</a><a href="tasks-36.htm"></a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>
-       <a href="../reference/ref-export-jar.htm">JAR file exporter</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-33.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-33.htm
deleted file mode 100644
index a0c5b65..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-33.htm
+++ /dev/null

@@ -1,90 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Creating a new JAR file
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Creating a new JAR file
-    </h1>
-    <p>
-      To create a new JAR file in the workbench:
-    </p>
-    <ol>
-      <li>
-        In the Package Explorer, you can optionally pre-select one or more Java elements to export. (These will be automatically selected in the <strong>JAR Package
-        Specification</strong> wizard page, described in Step 4.)
-      </li>
-      <li>
-        Either from the context menu or from the menu bar's <strong>File</strong> menu, select <strong>Export</strong>.
-      </li>
-      <li>
-        Select <strong>JAR file</strong>, then click&nbsp;<strong>Next</strong>.
-      </li>
-      <li>
-        In the <strong>JAR Package Specification</strong> page, select the resources that you want to export in the <strong>Select the resources to
-        export&nbsp;</strong>field.
-      </li>
-      <li>
-        Select the appropriate checkbox to specify whether you want to <strong>Export generated class files and resources</strong> or <strong>Export Java source files and
-        resources</strong>. <strong>Note</strong>: Selected resources are exported in both cases.
-      </li>
-      <li>
-        In the&nbsp;<strong>Select the export destination</strong> field, either type or click&nbsp;<strong>Browse</strong> to select a location
-        for the JAR file.
-      </li>
-      <li>
-        Select or clear the&nbsp;<strong>Compress the contents of the JAR file</strong> checkbox.
-      </li>
-      <li>
-        Select or clear the&nbsp;<strong>Overwrite existing files without warning</strong> checkbox. If you clear this checkbox,&nbsp;then you will be prompted
-        to confirm the replacement of each file that will be overwritten.
-      </li>
-      <li>
-        <strong>Note</strong>: The overwrite option is applied when writing the JAR file, the JAR description, and the manifest file.
-      </li>
-      <li>
-        You have two options:
-        <ul>
-          <li>
-            Click&nbsp;<strong>Finish</strong> to create the JAR file immediately.
-          </li>
-          <li>
-            Click&nbsp;<strong>Next</strong> to use the JAR Packaging Options page to set advanced options, create a JAR description, or change the default
-            manifest.
-          </li>
-        </ul>
-      </li>
-    </ol>
-	<p>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-	</p>
-	<p>
-     <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a></p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-	</p>
-	<p>	  
-       <a href="tasks-113.htm">Adding a JAR file to the build path</a><br>
-       <a href="tasks-115.htm">Attaching source to a JAR file</a><br>
-       <a href="tasks-35.htm">Defining the JAR file's manifest</a><br>
-       <a href="tasks-34.htm">Setting advanced options</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>	  
-       <a href="../reference/ref-export-jar.htm">JAR file exporter</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-34.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-34.htm
deleted file mode 100644
index b1a8720..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-34.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Setting advanced options
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Setting advanced options
-    </h1>
-    <ol>
-      <li>
-        Follow the procedure for creating a JAR file, but click <strong>Next</strong> in the last step to go to the JAR Packaging Options page.
-      </li>
-      <li>
-        If you want to save the JAR file description, select the <strong>Save the description of this JAR in the workspace</strong> checkbox.
-      </li>
-      <li>
-        The compiler is able to generate CLASS files even when source contains errors. You have the option to exclude CLASS (but not source) files with compile errors. These files
-        will be reported at the end, if reporting is enabled.
-      </li>
-      <li>
-        You can choose to exclude CLASS (but not source) files that have compile warnings. These files will be reported at the end.<br>
-         <strong>Note</strong>: This option does not automatically exclude class files with compile errors.
-      </li>
-      <li>
-        You can choose to include the source folder path by selecting the <strong>Create source folder structure</strong> checkbox.
-      </li>
-      <li>
-        Select the <strong>Build projects if not built automatically</strong> checkbox if you want the export to perform a build before creating the JAR file.
-      </li>
-      <li>
-        Click <strong>Finish</strong> to create the JAR file immediately or <strong>Next</strong> if you want to change the default manifest.
-      </li>
-    </ol>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-	</p>
-	<p>
-       <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-	</p>
-	<p>
-       <a href="tasks-33.htm">Creating a new JAR file</a><br>
-       <a href="tasks-35.htm">Defining the JAR file's manifest</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>	  
-       <a href="../reference/ref-export-jar.htm">JAR file exporter</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-35.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-35.htm
deleted file mode 100644
index c934ded..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-35.htm
+++ /dev/null

@@ -1,97 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Defining the JAR file's manifest
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Defining the JAR file's manifest
-    </h1>
-    <p>
-      You can either define the important parts of the JAR file manifest directly in the wizard or choose to use a manifest file that already exists in your workbench.
-    </p>
-    <h2>
-      Creating a new manifest
-    </h2>
-    <ol>
-      <li>
-        Follow the procedure for creating a JAR file, but click&nbsp;<strong>Next</strong> in the last step to go to the JAR Packaging Options page.
-      </li>
-      <li>
-        Set any advanced options that you want to set, and then click&nbsp;<strong>Next</strong> again to go to the JAR Manifest Specification page.
-      </li>
-      <li>
-        If it is not already selected, click the&nbsp;<strong>Generate the manifest file</strong> button.
-      </li>
-      <li>
-        You can now choose to save the manifest in the workbench. This will save the manifest for later use. Click&nbsp;<strong>Save the manifest in the workspace</strong>, then
-        click&nbsp;<strong>Browse</strong> next to the&nbsp;<strong>Manifest file</strong> field to specify a path and file name for the
-        manifest.
-      </li>
-      <li>
-        If you decided to save the manifest file in the previous step and you chose to save the JAR description on the previous wizard page, then you can choose to reuse it in the
-        JAR description (by selecting the <strong>Reuse and save the manifest in the workspace</strong> checkbox). This means that the saved file will be used when the JAR file is
-        recreated from the JAR description.This option is useful if you want to modify or replace the manifest file before recreating the JAR file from the description.
-      </li>
-      <li>
-        You can choose to seal the JAR and optionally exclude some packages from being sealed or specify a list with sealed packages. By default, nothing is sealed.
-      </li>
-      <li>
-        Click the&nbsp;<strong>Browse</strong> button next to the&nbsp;<strong>Main class</strong> field to specify the entry point for your
-        applications.<br>
-         <strong>Note</strong>: If your class is not in the list, then you forgot to select it at the beginning.
-      </li>
-      <li>
-        Click&nbsp;<strong>Finish</strong>. This will create the JAR, and optionally a JAR description and a manifest file.
-      </li>
-    </ol>
-    <h2>
-      Using an existing manifest
-    </h2>
-    You can use an existing manifest file that already exists in your workbench. 
-    <ol>
-      <li>
-        Follow the procedure for creating a JAR file, but click&nbsp;<strong>Next</strong> in the last step to go to the JAR Packaging Options page.
-      </li>
-      <li>
-        Set any advanced options that you want to set, and the click&nbsp;<strong>Next</strong> again to go to the JAR Manifest Specification page.
-      </li>
-      <li>
-        Click the&nbsp;<strong>Use existing manifest from workspace</strong> radio button.
-      </li>
-      <li>
-        Click the&nbsp;<strong>Browse</strong> button to choose a manifest file from the workbench.
-      </li>
-      <li>
-        Click&nbsp;<strong>Finish</strong>. This will create the JAR and optionally a JAR description.
-      </li>
-    </ol>
-	<p>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-	</p>
-	<p>
-     <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a></p> 
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-	</p>
-	<p> 
-       <a href="tasks-33.htm">Creating a new JAR file</a><br>
-       <a href="tasks-34.htm">Setting advanced options</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>
-       <a href="../reference/ref-export-jar.htm">JAR file exporter</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-36.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-36.htm
deleted file mode 100644
index 11a9f8e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-36.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Regenerating a JAR file
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Regenerating a JAR file
-    </h1>
-    <p>
-      You can use a JAR file description to regenerate a previously created JAR file.
-    </p>
-    <ol>
-      <li>
-        Select one or more JAR file descriptions in your workbench.
-      </li>
-      <li>
-        From the selection's pop-up menu, select&nbsp;<strong>Create JAR</strong>. The JAR file(s) are regenerated.
-      </li>
-    </ol>
-	<p>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>	
-     <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a> 
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="tasks-33.htm">Creating a new JAR file</a><br>
-       <a href="tasks-35.htm">Defining the JAR file's manifest</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-       <a href="../reference/ref-export-jar.htm">JAR file exporter</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-37.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-37.htm
deleted file mode 100644
index c5c53d7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-37.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Using the Hierarchy view
-    </title>
-  </head>
-  <body>
-    <h1>
-      Using the Hierarchy view
-    </h1>
-    <p>
-       <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="tasks-38.htm">Changing the appearance of the Hierarchy view</a><br>
-       <a href="tasks-39.htm">Opening a type hierarchy on a Java element</a><br>
-       <a href="tasks-40.htm">Opening a type hierarchy on the current text selection</a><br>
-       <a href="tasks-42.htm">Opening a type hierarchy in its own perspective</a><br>
-       <a href="tasks-44.htm">Finding overridden methods</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>	  
-       <a href="../reference/ref-24.htm">Views and editors</a><br>
-       <a href="../reference/ref-type-hierarchy.htm">Type Hierarchy view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-38.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-38.htm
deleted file mode 100644
index b74b584..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-38.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Changing the appearance of the Hierarchy view
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Changing the appearance of the Hierarchy view
-    </h1>
-    <p>
-      The Hierarchy view offers three different ways to look at a type hierarchy (use the toolbar buttons to alternate between them):
-    </p>
-    <ul>
-      <li>
-        <strong>Show the Type Hierarchy</strong> displays the type hierarchy of a type. This view shows all super- and subtypes of the selected type. Type
-        <em>java.lang.Object</em> is shown in the top-left corner. Interfaces are not shown.
-      </li>
-      <li>
-        <strong>Show the Supertype Hierarchy</strong> displays the supertype hierarchy of a type. This view shows all supertypes and the hierarchy of all
-        implemented interfaces. The selected type is always shown in the top-left corner.
-      </li>
-      <li>
-        <strong>Show the Subtype Hierarchy</strong> displays the subtype hierarchy of a type. This view shows all subtypes of the selected type and all
-        implementors of the selected interface (if the view is opened on an interface). The selected type is always shown in the top-left corner.
-      </li>
-    </ul>
-	<p>	
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-	</p>
-	<p>
-     <a href="../concepts/concepts-6.htm">Java views</a></p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-	</p>
-	<p>	  
-       <a href="tasks-37.htm">Using the Hierarchy view</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>	  
-       <a href="../reference/ref-24.htm">Views and editors</a><br>
-       <a href="../reference/ref-type-hierarchy.htm">Type Hierarchy view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-39.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-39.htm
deleted file mode 100644
index 58b5053..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-39.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Opening a type hierarchy on a Java element
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Opening a type hierarchy on a Java element
-    </h1>
-	<p>
-    There are several ways to open a type hierarchy. Select a Java element in a Java view and: 
-	</p>
-    <ul>
-      <li>
-        Press <strong>F4</strong> or
-      </li>
-      <li>
-        Choose <strong>Open Type Hierarchy</strong> from the view's pop-up menu or
-      </li>
-      <li>
-        Drag and drop the element to the Hierarchy view or
-      </li>
-      <li>
-        Press <strong>Ctrl+Shift+H</strong> and select a type from the list in the resulting dialog (you cannot select a package, source folder, or project with this method) or
-      </li>
-      <li>
-        Select <strong>Navigate &gt; Open Type in Hierarchy</strong> from the menu bar or
-      </li>
-      <li>
-        Select <strong>Focus On...</strong> from the pop-up menu of the type hierarchy viewer.
-      </li>
-    </ul>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-	</p>
-	<p>
-       <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-	</p>
-	<p>	  
-       <a href="tasks-7.htm">Changing new type hierarchy defaults</a><br>
-       <a href="tasks-11.htm">Creating Java elements</a><br>
-       <a href="tasks-37.htm">Using the Hierarchy view</a><br>
-       <a href="tasks-39.htm">Opening a type hierarchy on a Java element</a><br>
-       <a href="tasks-40.htm">Opening a type hierarchy on the current text selection</a><br>
-       <a href="tasks-41.htm">Opening a type hierarchy in the workbench</a><br>
-       <a href="tasks-42.htm">Opening a type hierarchy in its own perspective</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>	  
-       <a href="../reference/ref-24.htm">Views and editors</a><br>
-       <a href="../reference/ref-type-hierarchy.htm">Type Hierarchy view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-4.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-4.htm
deleted file mode 100644
index 8639190..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-4.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Microsoft FrontPage 4.0">
-    <title>
-      Showing and hiding CLASS files generated for inner types
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Showing and hiding CLASS files generated for inner types
-    </h1>
-    <p>
-      To show CLASS files for inner types:
-    </p>
-    <ol>
-	<li>
-      Select the <strong>Filters</strong> command from the Package Explorer drop-down menu.
-    </li>
-    <li>
-      Ensure that the <strong>Inner class files</strong> filter is not selected.
-    </li>
-	</ol>
-    <p>
-      To hide CLASS files for inner types:
-    </p>
-    <ol>
-	<li>
-      Select the <strong>Filters</strong> command from the Package Explorer drop-down menu.
-    </li>
-    <li>
-      Ensure that the <strong>Inner class files</strong> filter is selected.
-    </li>
-	</ol>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-2.htm">Showing and hiding elements</a><br>
-      <a href="tasks-47.htm">Filtering elements</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-dialog-java-element-filters.htm">Java Element Filters</a><br>
-      <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-40.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-40.htm
deleted file mode 100644
index a84d308..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-40.htm
+++ /dev/null

@@ -1,61 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Opening a type hierarchy on the current text selection
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Opening a type hierarchy on the current text selection
-    </h1>
-    <p>
-      To open a type hierarchy on a text selection, select the name of a Java element in the editor, and do one of the following:
-    </p>
-    <ul>
-      <li>
-        Press <strong>F4</strong>
-      </li>
-      <li>
-        select&nbsp;<strong>Open Type Hierarchy</strong> from the editor's pop-up menu
-      </li>
-      <li>
-        select <strong>Navigate &gt; Open Type Hierarchy</strong> from the menu bar
-      </li>
-    </ul>
-    <strong>Note:</strong> If the selected Java element (or editor selection) is not a type or a compilation unit, the hierarchy opens on the type enclosing the current
-    selection. 
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-	</p>
-	<p>
-       <a href="../concepts/concepts-7.htm">Java editor</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-	</p>
-	<p>	  
-       <a href="tasks-37.htm">Using the Hierarchy view</a><br>
-       <a href="tasks-7.htm">Changing new type hierarchy defaults</a><br>
-       <a href="tasks-38.htm">Changing the appearance of the Hierarchy view</a><br>
-       <a href="tasks-39.htm">Opening a type hierarchy on a Java element</a><br>
-       <a href="tasks-41.htm">Opening a type hierarchy in the workbench</a><br>
-       <a href="tasks-42.htm">Opening a type hierarchy in its own perspective</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>	  
-       <a href="../reference/ref-24.htm">Views and editors</a><br>
-       <a href="../reference/ref-type-hierarchy.htm">Type Hierarchy view</a><br>
-       <a href="../reference/ref-menu-edit.htm">Edit menu</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-41.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-41.htm
deleted file mode 100644
index f01a808..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-41.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Opening a type hierarchy in the workbench
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Opening a type hierarchy in the workbench
-    </h1>
-    <p>
-      You can open a type hierarchy from a button in the workbench toolbar.
-    </p>
-    <ol>
-      <li>
-        In the workbench toolbar, click the&nbsp;<strong>Open Type</strong> button.
-      </li>
-      <li>
-        Select a type in the dialog.
-      </li>
-      <li>
-        Select the&nbsp;<strong>Open in Type Hierarchy</strong> checkbox.
-      </li>
-      <li>
-        Click&nbsp;<strong>OK</strong>.
-      </li>
-    </ol>
-	<p>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>	
-     <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a> 
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>	  
-       <a href="tasks-7.htm">Changing new type hierarchy defaults</a><br>
-       <a href="tasks-39.htm">Opening a type hierarchy on a Java element</a><br>
-       <a href="tasks-40.htm">Opening a type hierarchy on the current text selection</a><br>
-       <a href="tasks-42.htm">Opening a type hierarchy in its own perspective</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>	  
-       <a href="../reference/ref-24.htm">Views and editors</a><br>
-       <a href="../reference/ref-type-hierarchy.htm">Type Hierarchy view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-42.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-42.htm
deleted file mode 100644
index 391fd74..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-42.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Opening a type hierarchy in its own perspective
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Opening a type hierarchy in its own perspective
-    </h1>
-    <p>
-      The default behavior for opening the Hierarchy view is to replace the Hierarchy view that is already open in the perspective. If there are no open Hierarchy views, one is
-      opened automatically.
-    </p>
-    <p>
-      Sometimes, it is useful to look at or work with several type hierarchies in different perspectives. This can be achieved by changing a workbench preference.
-    </p>
-    <ol>
-      <li>
-        From the menu bar, select <strong>Window</strong> &gt; <strong>Preferences</strong> and select the <strong>Java</strong> category. The general Java Preferences page opens.
-      </li>
-      <li>
-        In the <strong>When Opening a Type Hierarchy</strong> category, select the radio button <strong>Open a new Type Hierarchy Perspective</strong>.
-      </li>
-    </ol>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-5.htm">Java perspectives</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-37.htm">Using the Hierarchy view</a><br>
-       <a href="tasks-7.htm">Changing new type hierarchy defaults</a><br>
-       <a href="tasks-39.htm">Opening a type hierarchy on a Java element</a><br>
-       <a href="tasks-40.htm">Opening a type hierarchy on the current text selection</a><br>
-       <a href="tasks-41.htm">Opening a type hierarchy in the workbench</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>	  
-       <a href="../reference/ref-24.htm">Views and editors</a><br>
-       <a href="../reference/ref-type-hierarchy.htm">Type Hierarchy view</a><br>
-       <a href="../reference/ref-13.htm">Java Base preference page</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-44.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-44.htm
deleted file mode 100644
index 58e97e8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-44.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Finding overridden methods
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Finding overridden methods
-    </h1>
-    <p>
-      You can discover which methods override a selected method.
-    </p>
-    <ol>
-      <li>
-        Open the type hierarchy for the selected method's declaring type. Toggle on the <strong>Show the Subtype Hierarchy</strong> toolbar button.
-      </li>
-      <li>
-        In the list pane of the Hierarchy view, make sure that the&nbsp;<strong><strong>Lock View and Show Members in Hierarchy</strong></strong> button is toggled on. This option
-        locks the current class in the method pane and shows only those classes in the upper view that implement the currently selected method of the locked class. 
-        <p>
-        <img src="../images/tasks-8.png"  alt="Hierarchy view in Filtered Subtypes mode">
-        </p>
-        The methods of interest are shown in the upper pane. You can select any method and open it in an editor.
-      </li>
-    </ol>
-     <em>Note: The selection might not show all members if a filter (such as <strong>Hide Fields</strong> or <strong>Hide Static Members</strong>) is active.<br>
-    </em> 
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" ><br>
-    </p>
-	<p>
-	   <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a> 
-    </p>
-	<p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>	  
-       <a href="tasks-37.htm">Using the Hierarchy view</a><br>
-       <a href="tasks-47.htm">Filtering elements</a><br>
-       <a href="tasks-73.htm">Opening an editor for a selected element</a><br>
-       <a href="tasks-39.htm">Opening a type hierarchy on a Java element</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>	  
-       <a href="../reference/ref-dialog-override-method.htm">Override methods</a><br>
-       <a href="../reference/ref-type-hierarchy.htm">Type Hierarchy view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-45.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-45.htm
deleted file mode 100644
index 1bffd12..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-45.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Using the Package Explorer view
-    </title>
-  </head>
-  <body>
-    <h1>
-      Using the Package Explorer view
-    </h1>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>	  
-       <a href="tasks-47.htm">Filtering elements</a><br>
-       <a href="tasks-2.htm">Showing and hiding elements</a><br>
-       <a href="tasks-51.htm">Moving folders, packages and files</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>	  
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-47.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-47.htm
deleted file mode 100644
index cd84c05..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-47.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Filtering elements
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Filtering elements
-    </h1>
-    <p>
-      To filter elements:
-    </p>
-    <ol>
-      <li>
-        On the Package Explorer toolbar, click the <strong>Menu</strong> button and choose <strong>Filters</strong>.
-      </li>
-      <li>
-        Select or clear the filters that you want to apply to the view (read <strong>Filter description</strong> to learn about the selected filter's functionality).
-      </li>
-      <li>
-        Optionally, you can select patterns for filtering the view:
-        <ul>
-          <li>
-            Select the <strong>Name filter patterns</strong> checkbox at the top of the dialog.
-          </li>
-          <li>
-            In the text field below, specify the desired patterns (names matching one of the patterns will be hidden).
-          </li>
-        </ul>
-      </li>
-    </ol>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-	<p>
-    <a href="../concepts/concepts-3.htm">Java projects</a> 
-    </p>
-	<p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>	  
-       <a href="tasks-45.htm">Using the Package Explorer</a><br>
-       <a href="tasks-3.htm">Showing and hiding system files</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>	  
-       <a href="../reference/ref-dialog-java-element-filters.htm">Java Element Filters</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-5.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-5.htm
deleted file mode 100644
index 992e5bd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-5.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Microsoft FrontPage 4.0">
-    <title>
-      Showing and hiding libraries
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Showing and hiding libraries
-    </h1>
-	<p>
-    To show libraries: 
-	</p>
-    <ol>
-      <li>
-        Select the <strong>Filters</strong> command from the Package Explorer's drop-down menu.
-      </li>
-      <li>
-      	In the exclude list clear the checkbox for <span class="control">Referenced libraries</span>.
-      </li>
-    </ol>
-	<p>
-    To hide libraries: 
-    </p>
-	<ol>
-      <li>
-        Select the <strong>Filters</strong> command from the Package Explorer's drop-down menu.
-      </li>
-      <li>
-      	In the exclude list select the checkbox for <span class="control">Referenced libraries</span>.
-      </li>
-    </ol>
-	<p>
-    <img src="../images/ngrelt.png" alt="Related tasks" border="0" > 
-    </p>
-	<p>
-      <a href="tasks-2.htm">Showing and hiding elements</a><br>
-       <a href="tasks-47.htm">Filtering elements</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>
-       <a href="../reference/ref-dialog-java-element-filters.htm">Java Element Filters</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-51.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-51.htm
deleted file mode 100644
index 0d1e1b7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-51.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Moving folders, packages, and files
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Moving folders, packages, and files
-    </h1>
-    <ol>
-      <li>
-        In the Package Explorer, select the folder, package or file you want to move.
-      </li>
-      <li>
-        Drag-and-drop the selected resources onto the desired location.
-      </li>
-    </ol>
-    <p>
-      <strong>Note</strong>: You can use drag-and-drop to move resources between different workbench windows. Select a resource you want to move, and drag-and-drop it onto the
-      desired destination. If you want to copy rather than move, hold the <strong>Ctrl</strong> key down while dragging.
-    </p>
-    
-<p> You can also use drag-and-drop to copy resources between the workbench and 
-  the desktop (both ways), but you cannot move files from the desktop to the workbench 
-  using drag-and-drop. </p>
-    <p>
-       <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a><br>
-       <a href="../concepts/concepts-9.htm">Refactoring support</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-45.htm">Using the Package Explorer</a><br>
-       <a href="tasks-15.htm">Creating a new Java package</a><br>
-       <a href="tasks-85.htm">Copying and moving Java elements</a><br>
-       <a href="tasks-77.htm">Opening a package</a><br>
-       <a href="tasks-90.htm">Renaming a package</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a><br>
-       <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-54.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-54.htm
deleted file mode 100644
index 607ee0e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-54.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Using the Java editor
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Using the Java editor
-    </h1>
-    <p>
-      <strong>Note:</strong> Keyboard shortcuts used in the section (Java editor-related tasks) are the default key bindings.<br>
-       You can change between the <strong>Standard</strong> and the <strong>Emacs</strong> key binding sets by using the
-       <strong>Active configuration</strong> combo box on 
-       <strong>Window &gt; Preferences &gt; General &gt; Keys</strong>.
-    </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-7.htm">Java editor</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-57.htm">Generating getters and setters</a><br>
-       <a href="tasks-58.htm">Managing import statements</a><br>
-       <a href="tasks-62.htm">Using the local history</a><br>
-       <a href="tasks-66.htm">Formatting Java code</a><br>
-       <a href="tasks-69.htm">Viewing documentation and information</a><br>
-       <a href="tasks-171.htm">Using templates</a><br>
-       <a href="tasks-203.htm">Writing your own templates</a><br>
-       <a href="tasks-172.htm">Converting line delimiters</a><br>
-       <a href="tasks-173.htm">Finding and replacing</a><br>
-       <a href="tasks-174.htm">Changing the encoding used to show the source</a><br>
-       <a href="tasks-175.htm">Using quick fix</a><br>
-       <a href="tasks-176.htm">Using Structured Selection</a><br>
-       <a href="tasks-177.htm">Commenting and uncommenting lines of code</a><br>
-       <a href="tasks-178.htm">Shifting lines of code left and right</a><br>
-       <a href="tasks-179.htm">Using Surround with try/catch</a><br>
-       <a href="tasks-6.htm">Showing single elements or whole Java files</a><br>
-       <a href="tasks-73.htm">Opening an editor for a selected element</a><br>
-       <a href="tasks-65.htm">Using content/code assist</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>
-       <a href="../reference/ref-java-editor.htm">Java Editor</a><br>
-       <a href="../reference/ref-view-outline.htm">Java outline</a><br>
-       <a href="../reference/ref-java-editor.htm">Java editor actions</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-57.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-57.htm
deleted file mode 100644
index 6651605..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-57.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Generating getters and setters
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Generating getters and setters
-    </h1>
-    <p>
-      The Java editor allows you to generate accessors (&quot;getters and setters&quot;) for the fields of a type inside a compilation unit.
-    </p>
-    <ol>
-      <li>
-        In the editor, select the field for which you want to generate accessors (or a type in which you want to create these methods).
-      </li>
-      <li>
-        Select <strong>Generate Getter and Setter</strong> from the <strong>Source</strong> pop-up menu.
-      </li>
-      <li>
-        A dialog will open to let you select which methods you want to create.
-      </li>
-      <li>
-        Select the methods and press OK.
-      </li>
-    </ol>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-	</p>
-	<p>
-       <a href="../concepts/concepts-7.htm">Java editor</a><br>
-       <a href="../concepts/concepts-3.htm">Java projects</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-	</p>
-	<p>
-       <a href="tasks-54.htm">Using the Java editor</a><br>
-       <a href="tasks-20.htm">Creating a class in an existing compilation unit</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>
-       <a href="../reference/ref-dialog-gettersetter.htm">Generate Getter and Setter</a><br>
-       <a href="../reference/ref-view-outline.htm">Java outline</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-58.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-58.htm
deleted file mode 100644
index 3777a6d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-58.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Managing import statements
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Managing import statements
-    </h1>
-    <p>
-      The default Java editor includes several features that help you manage import statements.
-    </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-7.htm">Java editor</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-54.htm">Using the Java editor</a><br>
-       <a href="tasks-59.htm">Adding required import statements</a><br>
-       <a href="tasks-60.htm">Organizing existing import statements</a><br>
-       <a href="tasks-61.htm">Setting the order of import statements</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-menu-source.htm">Source menu</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-59.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-59.htm
deleted file mode 100644
index 2bfc7c4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-59.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Adding required import statements
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Adding required import statements
-    </h1>
-    <p>
-      The Java editor can help you adding required import statements for a selected type inside a compilation unit.
-    </p>
-    <ol>
-      <li>
-        Select a reference to a type in your Java code, and do one of the following: 
-        <ul>
-          <li>
-            Select <strong>Source &gt; Add Import</strong> from the pop-up menu in the editor
-          </li>
-          <li>
-            Select <strong>Source &gt; Add Import</strong> from the menu bar.
-          </li>
-          <li>
-            Press <strong>Ctrl + Shift + M</strong>
-          </li>
-        </ul>
-      </li>
-      <li>
-        Either the editor can identify the type or you are prompted to choose the desired type from a list of possible types.
-      </li>
-      <li>
-        The import statement is generated and inserted as specified by the import order preference.
-      </li>
-    </ol>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/concepts-7.htm">Java editor</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-54.htm">Using the Java editor</a><br>
-       <a href="tasks-58.htm">Managing import statements</a><br>
-       <a href="tasks-60.htm">Organizing existing import statements</a><br>
-       <a href="tasks-61.htm">Setting the order of import statements</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-menu-source.htm">Source menu</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-6.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-6.htm
deleted file mode 100644
index 93223db..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-6.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Showing single element or whole Java file
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Showing single element or whole Java file
-    </h1>
-    <ul>
-      <li>
-        To display the selected Java file in a single element view, click the&nbsp;<strong>Show Source of Selected Element Only</strong> button in the workbench
-        toolbar, so that it is pressed.
-      </li>
-      <li>
-        To display the selected Java file in a whole (non-segmented) view, click the&nbsp;<strong>Show Source of Selected Element Only</strong> button in the
-        workbench toolbar, so that it is not pressed.
-      </li>
-    </ul>
-    <p>
-      <strong>Note:</strong> this toolbar button is enabled only when a Java editor is open.
-    </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-7.htm">Java editor</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-54.htm">Using the Java editor</a><a href="tasks-54.htm"></a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-java-editor.htm">Java editor</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-60.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-60.htm
deleted file mode 100644
index e9e0006..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-60.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Organizing existing import statements
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Organizing existing import statements
-    </h1>
-    <p>
-      The Java editor can help you improve the existing import statements inside a compilation unit.
-    </p>
-    <ol>
-      <li>
-        Do one of the following while editing your Java code: 
-        <ul>
-          <li>
-            Select <strong>Source &gt; Organize Imports </strong> from the pop-up menu in the editor
-          </li>
-          <li>
-            Select <strong>Source &gt; Organize Imports</strong> from the menu bar
-          </li>
-          <li>
-            Press <strong>Ctrl</strong>+<strong>Shift</strong>+<strong>O</strong>
-          </li>
-        </ul>
-      </li>
-      <li>
-        The Java editor generates a complete list of import statements, as specified by the import order preference, and new import statements replace the old ones.
-      </li>
-    </ol>
-    <p>
-      Note: <strong>Source &gt; Organize Imports </strong> also works on whole packages or projects - just select them in the Package Explorer.
-    </p>
-    
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-7.htm">Java editor</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-59.htm">Adding required import statements</a><br>
-       <a href="tasks-58.htm">Managing import statements</a><br>
-       <a href="tasks-61.htm">Setting the order of import statements</a><br>
-       <a href="tasks-74.htm">Showing a type's compilation unit in the Package Explorer view</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-menu-source.htm">Source menu</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-61.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-61.htm
deleted file mode 100644
index 6523992..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-61.htm
+++ /dev/null

@@ -1,102 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Setting the order of import statements
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Setting the order of import statements
-    </h1>
-    <ol>
-      <li>
-        From the menu bar, select <strong>Window</strong> &gt; <strong>Preferences</strong>.
-      </li>
-      <li>
-        In the left pane, expand the <strong>Java &gt; Code Style</strong> category and select <strong>Organize Imports</strong>.
-      </li>
-      <li>
-        The Organize Imports page defines the sorting order of import statements.
-        In the Imports list, manage the list of package prefixes as follows: 
-        <ul>
-          <li>
-            <strong>New</strong> to add a new prefix
-          </li>
-          <li>
-            <strong>New Static</strong> to add a new prefix for static imports (J2SE 5.0 only)
-          </li>
-          <li>
-            <strong>Edit</strong> to change the name of an existing prefix
-          </li>
-          <li>
-            Use <strong>Up</strong> and <strong>Down</strong> buttons to rearrange the sequence
-            of the list by moving the selected prefix up or down
-          </li>
-          <li>
-            <strong>Remove</strong> to remove the selected prefix from the list
-          </li>
-          <li>
-            Use <strong>Import...</strong> and <strong>Export...</strong> to load a list of prefixes from a file
-            or to store it to a file
-          </li>
-        </ul>
-      </li>
-      <li>
-        In the <strong>Number of imports needed before .*</strong> field,
-        type the number of import statements that are allowed to refer to the
-        same package before <em>&lt;package prefix&gt;.*</em> is used.
-        This number is called the import threshold.
-      </li>
-      <li>
-        Click <strong>OK</strong> when you are done.
-      </li>
-    </ol>
-    <p>
-      <strong>Note:</strong> The order of import statements can also be configured per project:
-    </p>
-    <ol>
-      <li>
-        Select a java project, open the pop-up menu and choose <strong>Properties</strong>.
-      </li>
-      <li>
-        Select the <strong>Code Style &gt; Organize Imports</strong> page and check <strong>Enable project specific sttings</strong>.
-      </li>
-      <li>
-        Manage the list as explained above.
-      </li>
-      <li>
-        Click <strong>OK</strong> when you are done.
-      </li>
-    </ol>
-
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-7.htm">Java editor</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-59.htm">Adding required import statements</a><br>
-       <a href="tasks-58.htm">Managing import statements</a><br>
-       <a href="tasks-60.htm">Organizing existing import statements</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-       <a href="../reference/ref-22.htm">Organize Import preference page</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-62.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-62.htm
deleted file mode 100644
index e7bd22b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-62.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Using the local history
-    </title>
-  </head>
-  <body>
-    <h1>
-      Using the local history
-    </h1>
-    <p>
-      The JDT extends the workbench concept of a local history in three ways:
-    </p>
-    <ul>
-      <li>
-        A file can be replaced with an edition from the local history not just in the Navigator but also in the Package Explorer view.
-      </li>
-      <li>
-        The JDT allows you to compare and/or replace individual Java elements (types and their members) with editions from the local history.
-      </li>
-      <li>
-        The JDT allows you to restore Java elements (and files) deleted from the workbench that have been kept in the local history.
-      </li>
-    </ul>
-    <p>
-      Note: Files and Java elements such as types and their members change in time. A 'snapshot' of what they look like a point in time (as saved in the local
-      history) is called an edition.
-    </p>
-    <p>
-      <img  src="../images/ngrelc.png" alt="Related concepts" border="0">
-    </p>
-    <p>
-      	<a href="../concepts/concepts-1.htm">Java development tools (JDT)</a><br>
-       	<a href="../concepts/concepts-6.htm">Java views</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelt.png" alt="Related tasks">
-    </p>
-    <p>
-      <a href="tasks-54.htm">Using the Java editor</a><br>
-      <a href="tasks-63.htm">Replacing a Java element with a local history edition</a><br>
-      <a href="tasks-63a.htm">Comparing a Java element with a local history edition</a><br>
-      <a href="tasks-64.htm">Restoring a deleted workbench element</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a>
-     </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-63.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-63.htm
deleted file mode 100644
index 9a799b0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-63.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Replacing a Java element with a local history edition
-    </title>
-  </head>
-  <body>
-    <h1>
-      Replacing a Java element with a local history edition
-    </h1>
-    <ol>
-      <li>
-        Make sure that a Java view is visible.
-      </li>
-      <li>
-        Open a Java editor for the Java file in which you want to replace a Java element with an edition from the local history.
-      </li>
-      <li>
-        Activate the editor by clicking its tab in the editor area. The Outline view also displays the Java file. <em>Note: The Package Explorer can be configured to show or not show
-        Java elements in files. Use <strong>Window &gt; Preferences &gt; Java &gt; Appearance &gt; Show Members in Package Explorer</strong> to set your preference.</em>
-      </li>
-      <li>
-        Select the element that you want to replace in the Outline or the Package Explorer.
-      </li>
-      <li>
-        From the element's pop-up menu, select <strong>Replace With &gt; Element from Local History</strong>.
-      </li>
-      <li>
-        In the upper pane of the resulting dialog, all available editions of the selected element in the local history are displayed.
-      </li>
-      <li>
-        Select an edition in the upper pane to view the differences between the selected edition and the edition in the workbench.
-      </li>
-      <li>
-        When you have identified the edition with which you want to replace the existing Java element, click <strong>Replace</strong>.
-      </li>
-      <li>
-        The local history edition replaces the current one in the editor. <em>Note: The changed compilation unit has not yet been saved at this point.</em>
-      </li>
-    </ol>
-    <p>
-      <img  src="../images/ngrelc.png" alt="Related concepts" border="0">
-    </p>
-    <p>
-      <a href="../concepts/concepts-6.htm">Java views</a><br>
-       <a href="../concepts/concepts-7.htm">Java editor</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelt.png" alt="Related tasks">
-    </p>
-    <p>
-      <a href="tasks-62.htm">Using the local history</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-view-outline.htm">Java outline</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-63a.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-63a.htm
deleted file mode 100644
index 49e360f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-63a.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Comparing a Java element with a local history edition
-    </title>
-  </head>
-  <body>
-    <h1>
-      Comparing a Java element with a local history edition
-    </h1>
-    <ol>
-      <li>
-        Make sure that a Java view is visible.
-      </li>
-      <li>
-        Open a Java editor for the Java file in which you want to compare a Java element with an edition from the local history.
-      </li>
-      <li>
-        Activate the editor by clicking its tab in the editor area. The Outline view also displays the Java file.
-        <em>Note: The Package Explorer can be configured to show or not show
-        Java elements in files. Use <strong>Window &gt; Preferences &gt; Java &gt; Appearance &gt; Show Members in Package Explorer</strong>
-        to set your preference.</em>
-      </li>
-      <li>
-        Select the element that you want to compare in the Outline or the Package Explorer.
-      </li>
-      <li>
-        From the element's pop-up menu, select <strong>Compare With &gt; Element from Local History</strong>.
-      </li>
-      <li>
-        In the upper pane of the resulting dialog, all available editions of the selected element in the local history are displayed.
-      </li>
-      <li>
-        Select an edition in the upper pane to view the differences between the selected edition and the edition in the workbench.
-      </li>
-      <li>
-        If you are done with the comparison, click OK to close the dialog.
-      </li>
-    </ol>
-    <p>
-      <img  src="../images/ngrelc.png" alt="Related concepts" border="0">
-    </p>
-    <p>
-      <a href="../concepts/concepts-6.htm">Java views</a><br>
-       <a href="../concepts/concepts-7.htm">Java editor</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelt.png" alt="Related tasks">
-    </p>
-    <p>
-      <a href="tasks-62.htm">Using the local history</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-view-outline.htm">Java outline</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-64.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-64.htm
deleted file mode 100644
index 4a5bd49..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-64.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Restoring a deleted workbench element
-    </title>
-  </head>
-  <body>
-    <h1>
-      Restoring a deleted workbench element
-    </h1>
-    <ol>
-      <li>
-        Ensure that a Java view that show Java elements inside files (such as the Outline view) is visible.
-      </li>
-      <li>
-        Open the compilation unit to which you want to add a previously removed Java element from the local history.
-      </li>
-      <li>
-        Activate the editor by clicking its tab in the editor area, and the Java view shows the content of the Java file.
-      </li>
-      <li>
-        In the Java view, select the element to whose container type you want to restore the deleted element.
-      </li>
-      <li>
-        From the type's pop-up menu in the Java view, select <strong>Restore from Local History</strong>.
-      </li>
-      <li>
-        In the upper left pane of the resulting dialog, all available editions of the selected element in the local history are displayed.
-      </li>
-      <li>
-        In the left pane check all elements that you want to replace.
-      </li>
-      <li>
-      	For every checked element select an edition in the right hand pane and view its content in the bottom pane.
-      </li>
-      <li>
-        When you have identified the edition that you want to restore, press <strong>Restore</strong>.
-        The local history editions are loaded into the editor.
-      </li>
-    </ol>
-    <p>
-      <img  src="../images/ngrelc.png" alt="Related concepts" border="0">
-    </p>
-    <p>
-      <a href="../concepts/concepts-7.htm">Java editor</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelt.png" alt="Related tasks">
-    </p>
-    <p>
-      <a href="tasks-62.htm">Using the local history</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-view-outline.htm">Java outline</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-65.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-65.htm
deleted file mode 100644
index 873039f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-65.htm
+++ /dev/null

@@ -1,77 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Using content/code assist
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Using content/code assist
-    </h1>
-    <p>
-      You can use content assist (also called code assist) when writing Java code or Javadoc comments.
-    </p>
-    <ol>
-      <li>
-        Place your cursor in a valid position on a line of code in an editor and either 
-        <ul>
-          <li>
-            Press <strong>Ctrl</strong>+<strong>Space</strong>
-          </li>
-          <li>
-            Select <strong>Edit</strong> &gt; <strong>Content Assist</strong> from the menu bar
-          </li>
-        </ul>
-        If the Java editor finds valid candidates for this position, a list of possible completions is shown in a floating window. You can type further to narrow the list. You can
-        also hover over the selected list items to view its Javadoc information, if it is available.
-      </li>
-      <li>
-        Use the arrow keys or the mouse pointer to navigate through the possible completions.
-      </li>
-      <li>
-        Select an item in the list to complete the fragment by doing one of the following: 
-        <ul>
-          <li>
-            Selecting it and pressing <strong>Enter</strong>
-          </li>
-          <li>
-            Double-clicking it
-          </li>
-          <li>
-            <em>Note: When a list item is selected, you can view any available Javadoc information for this item in hover help. Note that you must click an item to select it in
-            the list before you can view Javadoc hover help for it.</em>
-          </li>
-        </ul>
-      </li>
-    </ol>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-7.htm">Java editor</a><br>
-       <a href="../concepts/concepts-11.htm">Scrapbook</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-54.htm">Using the Java editor</a><br>
-       <a href="tasks-66.htm">Formatting Java code</a><br>
-       <a href="tasks-54.htm">Using the Java editor</a><br>
-       <a href="tasks-71.htm">Viewing Javadoc information</a><br>
-       <a href="../reference/ref-24.htm">Views and editors</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-143.htm">Java Content Assist</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-66.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-66.htm
deleted file mode 100644
index 2015313..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-66.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Formatting Java code
-    </title>
-  </head>
-  <body>
-    <h1>
-      Formatting Java code
-    </h1>
-    <p>
-      The Java editor supports the formatting of Java code according to your personal preferences.
-    </p>
-    <p>
-      <img  src="../images/ngrelc.png" alt="Related concepts" border="0">
-    </p>
-    <p>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a><br>
-       <a href="../concepts/concepts-7.htm">Java editor</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelt.png" alt="Related tasks">
-    </p>
-    <p>
-      <a href="tasks-54.htm">Using the Java editor</a><br>
-       <a href="tasks-68.htm">Setting code formatting preferences</a><br>
-       <a href="tasks-67.htm">Formatting files or portions of code</a><br>
-       <a href="tasks-65.htm">Using content/code assist</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-17.htm">Code Formatter preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-67.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-67.htm
deleted file mode 100644
index 9b4626b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-67.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Formatting files or portions of code
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Formatting files or portions of code
-    </h1>
-    <p>
-      To format Java code:
-    </p>
-    <ol>
-      <li>
-        Use the Code Formatting Preferences page (<strong>Window</strong> &gt; <strong>Preferences</strong> &gt; <strong>Java</strong> &gt; <strong>Code Style</strong> &gt; <strong>Formatter</strong>) to
-        specify your preferences for code formatting.
-      </li>
-      <li>
-        Open a Java file and select the code you want to format. If nothing is selected, then all of the editor content is formatted.
-      </li>
-      <li>
-        Format the code by either 
-        <ul>
-          <li>
-            Selecting <strong>Source</strong> &gt; <strong>Format</strong> from the editor's pop-up menu or
-          </li>
-          <li>
-            Pressing <strong>Ctrl+Shift+F</strong> or
-          </li>
-          <li>
-            Selecting <strong>Source</strong> &gt; <strong>Format</strong> from the menu bar.
-          </li>
-        </ul>
-      </li>
-    </ol>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a><br>
-      <a href="../concepts/concepts-7.htm">Java editor</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-54.htm">Using the Java editor</a><br>
-      <a href="tasks-66.htm">Formatting Java code</a><br>
-      <a href="tasks-68.htm">Setting code formatting preferences</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-menu-source.htm">Source menu</a><br>
-      <a href="../reference/ref-17.htm">Code Formatter preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-68.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-68.htm
deleted file mode 100644
index 0fb6793..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-68.htm
+++ /dev/null

@@ -1,78 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Setting code formatting preferences
-    </title>
-  </head>
-  <body>
-    <h1>
-      Setting code formatting preferences
-    </h1>
-    <ol>
-      <li>
-        From the workbench menu bar, select <strong>Window</strong> &gt; <strong>Preferences.</strong> The Workbench Preferences page opens.
-      </li>
-      <li>
-        In the left pane, expand the <strong>Java</strong> category and select <strong>Code Formatter</strong>. The Code Formatter Preferences page opens.
-      </li>
-      <li>
-        Select a profile and click the <strong>Show</strong> or <strong>Edit</strong> button to configure it, or press <strong>New</strong> to create a new profile.
-      </li>
-      <li>
-        In the dialog, select the code formatting conventions that you want the formatter to follow.
-      </li>
-      <li>
-        Note that at the right side of the page, you can observe an example effect of each individual code formatting option and see a preview of what your formatted code will look
-        like.
-      </li>
-      <li>
-        Click <strong>OK</strong> when you are done.
-      </li>
-    </ol>
-    <p>
-      <strong>Note:</strong> Code formatter settings can also be configured per project:
-    </p>
-    <ol>
-      <li>
-        Select a java project, open the pop-up menu and choose <strong>Properties</strong>.
-      </li>
-      <li>
-        Select the <strong>Code Style &gt; Formatter</strong> page and check <strong>Enable project specific sttings</strong>.
-      </li>
-      <li>
-        Select or edit a profile as explained above.
-      </li>
-      <li>
-        Click <strong>OK</strong> when you are done.
-      </li>
-    </ol>
-    
-    <p>
-      <img  src="../images/ngrelc.png" alt="Related concepts" border="0">
-    </p>
-    <p>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelt.png" alt="Related tasks">
-    </p>
-    <p>
-      <a href="tasks-66.htm">Formatting Java code</a><br>
-      <a href="tasks-67.htm">Formatting files or portions of code</a><br>
-      <a href="tasks-230.htm">Using the Formatter Application</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-17.htm">Code Formatter preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-69.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-69.htm
deleted file mode 100644
index c7d74ab..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-69.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Viewing documentation and information
-    </title>
-  </head>
-  <body>
-    <h1>
-      Viewing documentation and information
-    </h1>
-    <p>
-      You can view different kinds of documentation information while working in the workbench.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-    </p>
-    <p>
-      <a href="tasks-54.htm">Using the Java editor</a><br>
-       <a href="../tasks/tasks-71.htm">Viewing Javadoc information</a><br>
-       <a href="../tasks/tasks-70.htm">Viewing marker help</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-7.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-7.htm
deleted file mode 100644
index d4dd7bb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-7.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Changing new type hierarchy defaults
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Changing new type hierarchy defaults
-    </h1>
-    <p>
-      New type hierarchies can open in a Hierarchy view or in a Java Hierarchy perspective. You can indicate which is the default method for opening new type hierarchies on the
-      preferences pages.
-    </p>
-	<ol>
-    <li>
-      Select <strong>Window</strong> &gt; <strong>Preferences</strong>, and select the <strong>Java</strong> category. The general Java Preferences page opens.
-    </li>
-    <li>
-      Use the radio buttons that appear under <strong>When opening a Type Hierarchy</strong> to indicate your preference.
-    </li>
-	</ol>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-39.htm">Opening a type hierarchy on a Java element</a><br>
-       <a href="tasks-40.htm">Opening a type hierarchy on the current text selection</a><br>
-       <a href="tasks-41.htm">Opening a type hierarchy in the workbench</a><br>
-       <a href="tasks-42.htm">Opening a type hierarchy in its own perspective</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-13.htm">Java Base preference page</a><br>
-      <a href="../reference/ref-13.htm"></a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-70.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-70.htm
deleted file mode 100644
index 328122c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-70.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Viewing marker help
-    </title>
-  </head>
-  <body>
-    <h1>
-      Viewing marker help
-    </h1>
-    <p>
-      You can use hover help to view various kinds of information in the marker bar in the editor area. For example:
-    </p>
-    <ul>
-      <li>
-        Information about problems
-      </li>
-      <li>
-        Information about breakpoints
-      </li>
-    </ul>
-    <p>
-      Hover your mouse pointer over the marker in the marker bar to view any available hover help.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-    </p>
-    <p>
-      <a href="tasks-54.htm">Using the Java editor</a><br>
-       <a href="../tasks/tasks-69.htm">Viewing documentation and information</a><br>
-       <a href="../tasks/tasks-71.htm">Viewing Javadoc information</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-71.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-71.htm
deleted file mode 100644
index d452b1d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-71.htm
+++ /dev/null

@@ -1,100 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Viewing Javadoc information
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Viewing Javadoc information
-    </h1>
-    <p>
-    The JDT provides easy access to Javadoc information for the code edited in the Java editor.
-    </p>
-    <ol>
-      <li>
-        Open the Java editor on a Java file.
-      </li>
-      <li>
-        Place the mouse pointer over the element whose Javadoc information you want to view (a method name, for example).
-      </li>
-      <li>
-        If Javadoc information is available, a pop-up window opens, displaying the Javadoc information. HTML Javadoc can be viewed as any other resource in the workbench, through
-        an embedded or external editor or viewer. Import the Javadoc into the workbench and double-click it in the Package Explorer.
-      </li>
-    </ol>
-    <p>
-      You can also view Javadoc information by:
-    </p>
-    <ol>
-      <li>
-        Opening the Java editor on a Java file.
-      </li>
-      <li>
-        Placing the mouse pointer over the element whose Javadoc information you want to view (a method name, for example).
-      </li>
-      <li>
-        Pressing <kbd>F2</kbd> or selecting <strong>Edit &gt; Show Tooltip Description</strong> from the menu bar.
-      </li>
-    </ol>
-    <p>
-      To view Javadoc in the Javadoc view:
-    </p>
-    <ol>
-      <li>
-        Open the Java editor on a Java file.
-      </li>
-      <li>
-        Place the caret over the element whose Javadoc information you want to view (a method name, for example).
-      </li>
-      <li>
-        Open the Javadoc View (press <kbd>Alt+Shift+Q, J</kbd> or select <strong>Window > Show View > Javadoc</strong>).
-      </li>
-    </ol>
-    <p>
-      To view Javadoc in an external browser:
-    </p>
-    <ol>
-      <li>
-        Open the Java editor on a Java file.
-      </li>
-      <li>
-        Place the caret over the element whose Javadoc information you want to view (a method name, for example).
-      </li>
-      <li>
-        Press <kbd>Shift+F2</kbd> or select <strong>Navigate &gt; Open External Javadoc</strong> from the menu bar.
-      </li>
-    </ol>
-    
-    <p>
-       <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-7.htm">Java editor</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-54.htm">Using the Java editor</a><br>
-       <a href="tasks-65.htm">Using content/code assist</a><br>
-       <a href="tasks-69.htm">Viewing documentation and information</a><br>
-       <a href="tasks-70.htm">Viewing marker help</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a><br>
-       <a href="../reference/ref-dialog-javadoc-location.htm">Javadoc Location</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-72.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-72.htm
deleted file mode 100644
index 4b1bd13..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-72.htm
+++ /dev/null

@@ -1,19 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Navigating the JDT Workbench
-    </title>
-  </head>
-  <body>
-    <h1>
-      Navigating the JDT Workbench
-    </h1>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-73.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-73.htm
deleted file mode 100644
index 8450f32..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-73.htm
+++ /dev/null

@@ -1,80 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Opening an editor for a selected element
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Opening an editor for a selected element
-    </h1>
-    <p>
-      You can select the name of a type, method, or field in the Java source editor or in the scrapbook and open an editor on the definition of the element.
-    </p>
-    <ol>
-      <li>
-        In the Java editor, select the name of a type, method, or field. You can also just click into the name once.
-      </li>
-      <li>
-        Do one of the following: 
-        <ul>
-          <li>
-            From the menu bar, select <strong>Navigate</strong> &gt; <strong>Open Declaration</strong>
-          </li>
-          <li>
-            From the editor's pop-up menu, select <strong>Open Declaration</strong>
-          </li>
-          <li>
-            Press <strong>F3</strong>
-          </li>
-        </ul>
-      </li>
-    </ol>
-    <p>
-      or
-    </p>
-    <ol>
-      <li>
-        Hold down the <strong>Ctrl</strong> key.
-      </li>
-      <li>
-        In the Java editor, move the mouse over the name of a type, method, or field until the name becomes underlined.
-      </li>
-      <li>
-        Click the hyperlink once.
-      </li>
-    </ol>
-    
-    <p>
-      If there are multiple definitions of the same name, a dialog is shown, and you can select one definition that you want to open. 
-      An editor opens containing the selected element.
-    </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-7.htm">Java editor</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-54.htm">Using the Java editor</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-menu-navigate.htm">Navigate menu</a><br>
-       <a href="../reference/ref-24.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-74.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-74.htm
deleted file mode 100644
index 15a3b5a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-74.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Showing an element in the Package Explorer view
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Showing an element in the Package Explorer view
-    </h1>
-    <p>
-      You can reveal an element's location in the Package Explorer view
-    </p>
-    
-    <ul>
-      <li>
-        <ol>
-          <li>
-            Select a Java element or activate a Java editor.
-          </li>
-          <li>
-            From the menu bar, select <strong>Navigate</strong> &gt; <strong>Show In</strong> &gt; <strong>Package Explorer</strong>.
-            If the Package Explorer is not already open, then it opens in the
-            current perspective. The workbench navigates to the selected element (or the edited compilation unit).
-          </li>
-        </ol>
-      </li><br>
-      <li>
-        From the Java editor's pop-up menu, select 
-        <strong>Show in Package Explorer</strong>. The currently edited compilation unit will be revealed.
-      </li>
-    </ul>
-    <p>
-      <strong>Note:</strong> The element might not be revealed if Package Explorer filters are active or the <strong>Window &gt; Preferences &gt; Java &gt; Appearance &gt; Show Members in Package
-      Explorer</strong> preference is cleared.
-    </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-6.htm">Java views</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-executionArgs.htm">Setting execution arguments</a><br>
-       <a href="tasks-92.htm">Renaming a compilation unit</a><br>
-       <a href="tasks-75.htm">Opening a type in the Package Explorer</a><br>
-       <a href="tasks-60.htm">Organizing existing import statements</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-13.htm">Java Base preference page</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-75.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-75.htm
deleted file mode 100644
index 0d3fb4b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-75.htm
+++ /dev/null

@@ -1,66 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Opening a type in the Package Explorer view
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Opening a type in the Package Explorer view
-    </h1>
-    <p>
-      You can open the Package Explorer on any type that is included on a project's class path.
-    </p>
-    <ol>
-		<li>
-			From the menu bar, select <strong>Navigate &gt; Go To &gt; Type.</strong> The Go to Type dialog opens.
-		</li>
-		<li>
-			In the <strong>Choose a type</strong> field, begin typing an expression to narrow the list of available types, using wildcards as needed. As you
-      		type, the list is filtered to display only types that match the current expression.
-      	</li>
-		<li>
-			In the <strong>Matching types</strong> list, select a type. Hint: you can press the <Strong>Down</strong> key to move to the first type.
-		</li>
-		<li>
-			Click <strong>OK</strong> when you are done. The selected type is displayed in the Package Explorer.
-    	</li>
-    </ol>
-	
-	<p>
-	  <strong>Note:</strong> The Goto Type dialog maintains a history of recently opened types.
-	  These are shown when the dialog is opened and stay above a separator line when you start to type a filter expression.
-	</p>
-	
-	<p>
-		<strong>Note:</strong> Revealing may not be possible if Package Explorer filters are applied.
-	</p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-74.htm">Showing a type's compilation unit in the Package Explorer</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-menu-navigate.htm">Navigate actions</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-76.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-76.htm
deleted file mode 100644
index c4efea6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-76.htm
+++ /dev/null

@@ -1,70 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Opening an editor on a type
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Opening an editor on a type
-    </h1>
-    <p>
-      You can open an editor on any type in the workbench.
-    </p>
-    <ol>
-		<li>
-			Press <strong>Ctrl+Shift+T</strong> or, select <strong>Navigate</strong> &gt; <strong>Open Type</strong> from the menu bar. The Open Type dialog opens.
-		</li>
-		<li>
-			In the <strong>Choose a type</strong> field, begin typing an expression to narrow the list of available types, using wildcards as needed. As you
-			type, the list is filtered to display only types that match the current expression.
-		</li>
-		<li>
-			In the <strong>Matching types</strong> list, select a type. Hint: you can press the <Strong>Down</strong> key to move to the first type.
-		</li>
-		<li>
-			Click <strong>OK</strong> when you are done. An editor opens on the selected type.
-		</li>
-	</ol>
-	
-	<p>
-	  <strong>Note:</strong> The Open Type dialog maintains a history of recently opened types.
-	  These are shown when the dialog is opened and stay above a separator line when you start to type a filter expression.
-	</p>
-	
-    <p>
-      <strong>Note:</strong> If you open a type from a CLASS or JAR file, you will see a special editor showing only method signatures unless you have attached source to it.
-    </p>
-    
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-7.htm">Java editor</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-115.htm">Attaching source to a JAR file</a><br>
-       <a href="tasks-73.htm">Opening an editor for a selected element</a><br>
-       <a href="tasks-54.htm">Using the Java editor</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-148.htm">Open Type dialog</a>
-      <a href="../reference/ref-menu-navigate.htm">Navigate actions</a><br>
-      <a href="../reference/ref-24.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-77.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-77.htm
deleted file mode 100644
index 700a517..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-77.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Opening a package
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Opening a package
-    </h1>
-    <p>
-      To reveal a package in the tree of the Package Explorer:
-    </p>
-    <ol>
-		<li>
-			Select <strong>Navigate</strong> &gt; <strong>Go To</strong> &gt; <strong>Package</strong> from the menu bar. The Go to Package dialog opens.
-		</li>
-		<li>
-			Type a package name in the <strong>Choose a package</strong> field to narrow the list of available packages, using wildcards as needed. As you type,
-			the list is filtered to display only packages that match the current expression.
-		</li>
-		<li>
-			Select a package from the list, then click <strong>OK</strong>. The selected package is displayed in the Package Explorer.
-		</li>
-	</ol>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-6.htm">Java views</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-74.htm">Showing a type's compilation unit in the Package Explorer</a><br>
-       <a href="tasks-90.htm">Renaming a package</a><br>
-       <a href="tasks-51.htm">Moving folders, packages, and files</a><br>
-       <a href="tasks-15.htm">Creating a new Java package</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><a href="../reference/ref-menu-navigate.htm"></a>
-    </p>
-    <p>
-      <a href="../reference/ref-menu-navigate.htm">Navigate actions</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-78.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-78.htm
deleted file mode 100644
index 631220a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-78.htm
+++ /dev/null

@@ -1,23 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Viewing source in a JAR file
-    </title>
-  </head>
-  <body>
-    <h1>
-      Viewing source in a JAR file
-    </h1>
-    <p>
-      Unless its source code is attached to a JAR file in the workbench, you will not be able to view the source for the JAR file.
-    </p>
-    <a href="tasks-115.htm">See Attaching Source to a JAR File</a> 
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-79.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-79.htm
deleted file mode 100644
index 4b00bcb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-79.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Searching Java code
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Searching Java code
-    </h1>
-    <p>
-      A Java search can be conducted using the Search dialog as well as using the pop-up menu of selected resources and elements.
-    </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-8.htm">Java search</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-104.htm">Conducting a Java search using pop-up menus</a><br>
-       <a href="tasks-103.htm">Conducting a Java search using the Search button</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><a href="../reference/ref-menu-search.htm"></a>
-    </p>
-    <p>
-      <a href="../reference/ref-menu-search.htm">Search menu</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-80.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-80.htm
deleted file mode 100644
index 98af879..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-80.htm
+++ /dev/null

@@ -1,75 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Refactoring
-    </title>
-  </head>
-  <body>
-    <h1>
-      Refactoring
-    </h1>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-9.htm">Refactoring support</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-82.htm">Refactoring without preview</a><br>
-       <a href="../tasks/tasks-83.htm">Refactoring with preview</a><br>
-       <a href="../tasks/tasks-84.htm">Previewing refactoring changes</a><br>
-       <a href="../tasks/tasks-100.htm">Undoing a refactoring operation</a><br>
-       <a href="../tasks/tasks-101.htm">Redoing a refactoring operation</a>
-    </p>
-    
-<p> <a href="tasks-85.htm">Copying and moving Java elements</a><br>
-  <a href="tasks-87.htm">Extracting a method</a><br>
-  <a href="tasks-159.htm">Extracting a local variable</a><br>
-  <a href="tasks-209.htm">Extracting a constant</a><br>
-  <a href="tasks-90.htm">Renaming a package</a><br>
-  <a href="tasks-92.htm">Renaming a compilation unit</a><br>
-  <a href="tasks-94.htm">Renaming a type</a><br>
-  <a href="tasks-96.htm">Renaming a method</a><br>
-  <a href="tasks-169.htm">Renaming a field</a><br>
-  <a href="tasks-204.htm">Renaming a local variable</a><br>
-  <a href="tasks-98.htm">Renaming method parameters</a><br>
-  <a href="tasks-159.htm">Changing method signature</a><br>
-  <a href="tasks-161.htm">Inlining a local variable</a><br>
-  <a href="tasks-208.htm">Inlining a method</a><br>
-  <a href="tasks-207.htm">Inlining a constant</a><br>
-  <a href="tasks-162.htm">Self encapsulating a field</a><br>
-  <a href="tasks-164.htm">Replacing a local variable with a query</a><br>
-  <a href="tasks-165.htm">Pulling members up to superclass</a><br>
-  <a href="tasks-220.htm">Pushing members down to subclasses</a><br>
-  <a href="tasks-167.htm">Moving static members between types</a><br>
-  <a href="tasks-210.htm">Moving an instance method to a component</a><br>
-  <a href="tasks-211.htm">Converting a local variable to a field</a><br>
-  <a href="tasks-216.htm">Converting an anonymous inner class to a nested class</a><br>
-  <a href="tasks-217.htm">Converting a nested type to a top level type</a><br>
-  <a href="tasks-218.htm">Extracting an interface from a type</a><br>
-  <a href="tasks-219.htm">Replacing references to a type with references to one of its supertypes</a><br>
-  <a href="tasks-223.htm">Replacing a single reference to a type with a reference to one of its supertypes</a><br>
-  <a href="tasks-224.htm">Replacing an expression with a method parameter</a><br>
-  <a href="tasks-225.htm">Replacing constructor calls with factory method invocations</a><br>
-  <a href="tasks-226.htm">Inferring type parameters for generic type references</a><br>
- </p>
-<p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <p>
-      <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-       <a href="../reference/ref-117.htm">Refactoring dialogs</a><br>
-       <a href="../reference/ref-13.htm">Java preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-81.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-81.htm
deleted file mode 100644
index 0e3a4da..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-81.htm
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Refactoring steps
-    </title>
-  </head>
-  <body>
-    <h1>
-      Refactoring steps
-    </h1>
-    <p>
-      The goal of refactoring support is to improve your code without changing its behavior.
-    </p>
-    <p>
-      You can execute a refactoring in one of two different ways.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-82.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-82.htm
deleted file mode 100644
index 705a5f9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-82.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Refactoring without preview
-    </title>
-  </head>
-  <body>
-    <h1>
-      Refactoring without preview
-    </h1>
-    
-<ol>
-  <li> Activate a refactoring command. For example, rename a type by selecting 
-    it in the Outline view and choosing <strong>Refactor</strong> &gt; <strong>Rename</strong> 
-    from its pop-up menu. </li>
-  <li> The Refactoring Parameters page prompts you for information necessary for 
-    the action. For example, the Rename Type Refactoring dialog asks you for a 
-    new name for the selected type. </li>
-  <li> Provide the necessary data on the parameters page, and click <strong>OK</strong>. 
-  </li>
-  <li> If no problems are anticipated, 
-    then the refactoring is carried out.<br>
-    Otherwise, the problems page comes to the front to display the 
-    errors. </li>
-  <li> If a fatal problem was anticipated, then only the <strong>Back</strong> 
-    and <strong>Cancel</strong> buttons are enabled, and you are prevented from 
-    carrying out the refactoring. If the problems are related to data provided 
-    on the parameters page, click <strong>Back</strong> and attempt to remedy 
-    the problem. Otherwise, click <strong>Cancel</strong> to close the dialog. 
-  </li>
-  <li> If other kinds of problems were anticipated, you can click <strong>Continue</strong> 
-    to acknowledge the problems. The refactoring is carried out, and the dialog 
-    closes. </li>
-</ol>
-    <p>
-      <img  src="../images/ngrelc.png" alt="Related concepts" border="0">
-    </p>
-    <p>
-      <a href="../concepts/concepts-9.htm">Refactoring support</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelt.png" alt="Related tasks">
-    </p>
-    <p>
-      <a href="tasks-83.htm">Refactoring with preview</a><br>
-       <a href="tasks-100.htm">Undoing a refactoring operation</a><br>
-       <a href="tasks-101.htm">Redoing a refactoring operation</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-       <a href="../reference/ref-117.htm">Refactoring dialogs</a><br>
-       <a href="../reference/ref-13.htm">Java preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-83.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-83.htm
deleted file mode 100644
index f50234f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-83.htm
+++ /dev/null

@@ -1,73 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Refactoring with preview
-    </title>
-  </head>
-  <body>
-    <h1>
-      Refactoring with preview
-    </h1>
-    <ol>
-      <li>
-        Activate a refactoring command. For example, rename a type by selecting it in the Outline view and choosing
-        <strong>Refactor</strong> &gt; <strong>Rename</strong> from its pop-up menu.
-      </li>
-      <li>
-        The Refactoring Parameters page prompts you for information necessary for the action. For example, the Rename Type Refactoring dialog
-        asks you for the new name for the selected type.
-      </li>
-      
-  <li> Provide the necessary data on the parameters page, and then click <strong>Preview</strong>. 
-  </li>
-      <li>
-        If problems are anticipated, then the problems page comes to the front to display them. 
-        <ul>
-          
-      <li> If a fatal problem was anticipated, then only the <strong>Back</strong> 
-        and <strong>Cancel</strong> buttons are enabled, and you are prevented 
-        from carrying out the refactoring. If the problems are related to data 
-        provided on the parameters page, click <strong>Back</strong> and attempt 
-        to remedy the problem. Otherwise, click <strong>Cancel</strong> to close 
-        the dialog. </li>
-      <li> If other kinds of problems were anticipated, you can click <strong>Continue</strong> 
-        to acknowledge the problems and move on to the preview page. </li>
-        </ul>
-        The Refactoring Preview page opens.
-      </li>
-      
-  <li> Click <strong>OK</strong> to execute the refactoring and close the dialog. 
-  </li>
-    </ol>
-    <p>
-      <img  src="../images/ngrelc.png" alt="Related concepts" border="0">
-    </p>
-    <p>
-      <a href="../concepts/concepts-9.htm">Refactoring support</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelt.png" alt="Related tasks">
-    </p>
-    <p>
-      <a href="tasks-82.htm">Refactoring without preview</a><br>
-       <a href="tasks-84.htm">Previewing refactoring changes</a><br>
-       <a href="tasks-100.htm">Undoing a refactoring operation</a><br>
-       <a href="tasks-101.htm">Redoing a refactoring operation</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-       <a href="../reference/ref-117.htm">Refactoring dialogs</a><br>
-       <a href="../reference/ref-13.htm">Java preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-84.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-84.htm
deleted file mode 100644
index cad2455..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-84.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Previewing refactoring changes
-    </title>
-  </head>
-  <body>
-    <h1>
-      Previewing refactoring changes
-    </h1>
-    <p>
-      The Preview page shows the proposed effects of a refactoring action. You can use this page as follows.
-    </p>
-    <ul>
-      <li>
-        Select a node in the tree to examine a particular change.
-      </li>
-      <li>
-        To examine a change inside a compilation unit, expand a compilation unit node in the tree and select one of its children.
-      </li>
-      <li>
-        When selecting nodes, the compare viewer is adjusted only to show a preview for the selected node.
-      </li>
-      <li>
-        Clear the checkbox for a node to exclude it from the refactoring.
-      </li>
-    </ul>
-    <p>
-      <strong>Note</strong>: Excluding a node can result
-      in compile errors when performing the refactoring without further warning.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-9.htm">Refactoring support</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-83.htm">Refactoring with preview</a><br>
-       <a href="../tasks/tasks-100.htm">Undoing a refactoring operation</a><br>
-       <a href="../tasks/tasks-101.htm">Redoing a refactoring operation</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <p>
-      <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-       <a href="../reference/ref-117.htm">Refactoring dialogs</a><br>
-       <a href="../reference/ref-13.htm">Java preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-85.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-85.htm
deleted file mode 100644
index 04ea4bf..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-85.htm
+++ /dev/null

@@ -1,108 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Copying and moving Java elements
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Copying and moving Java elements
-    </h1>
-    <p>
-      To move Java elements:
-    </p>
-    <ol>
-		<li>
-			From a Java view, select the Java elements you want to move.
-		</li>
-		<li>
-			From the menu bar, select <strong>Refactor &gt; Move</strong> or, from the view's pop-up menu, select <strong>Refactor &gt;&nbsp;Move</strong>.
-		</li>
-		<li>
-			In the resulting dialog, select the new location for the element and press <strong>OK</strong>.<br>
-			<strong>Note:</strong> Moving static members (such as methods and types), classes or compilation units 
-			allows you to choose to also update references to these elements.
-			Additional options may be available; for more on these options, see the 
-			documentation for the corresponding "Rename" refactoring.
-		</li>
-	</ol>
-    <p>
-      You can also move Java elements by dragging them and dropping in the desired new location.
-    </p>
-    <p>
-      <strong>Note</strong>: Dragging and dropping compilation units and types allows you to update references to these elements. In the dialog that appears on dropping, press
-      <strong>Yes</strong> if you want to update references, press <strong>Preview</strong> if you want to see the preview of the reference updates, press <strong>No</strong> if
-      you want to move the elements without updating references or press <strong>Cancel</strong> if you want to cancel the move operation.
-			Additional options may be available; for more on these options, see the 
-			documentation for the corresponding "Rename" refactoring.
-    </p>
-    <p>
-    </p>
-    <p>
-      To copy Java elements you need to copy them to the clipboard and paste them in the desired new location:
-    </p>
-    <ol>
-		<li>
-			From a Java view, select the Java elements you want to copy to the clipboard and do one of the following:
-		    <ul>
-			      <li>
-			        Press <strong>Ctrl+C</strong>
-			      </li>
-			      <li>
-			        From the menu bar, select <strong>Edit &gt; Copy</strong>
-			      </li>
-			      <li>
-			        From the view's pop-up menu, select <strong>Copy</strong>
-			      </li>
-		    </ul>
-		</li>
-		<li>
-			Now, to paste the elements, select the desired destination and do one of the following:
-		    <ul>
-		      <li>
-		        Press <strong>Ctrl+V</strong>
-		      </li>
-		      <li>
-		        From the menu bar, select <strong>Edit &gt; Paste</strong>
-		      </li>
-		      <li>
-		        From the view's pop-up menu, select <strong>Copy</strong>
-		      </li>
-		    </ul>
-		</li>
-	</ol>
-    <p>
-      You can also copy Java elements by dragging them and dropping in the desired new location. You will need to have <strong>Ctrl</strong> pressed while dragging to copy the
-      elements.
-    </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-11.htm">Creating Java elements</a><br>
-       <a href="tasks-51.htm">Moving folders, packages, and files</a><br>
-       <a href="tasks-85.htm">Copying and moving Java elements</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><a href="../reference/ref-menu-edit.htm"></a>
-    </p>
-    <p>
-      <a href="../reference/ref-menu-edit.htm">Edit menu</a><br>
-       <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-86.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-86.htm
deleted file mode 100644
index 72894ee..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-86.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Moving a compilation unit
-    </title>
-  </head>
-  <body>
-    <h1>
-      Moving a compilation unit
-    </h1>
-    <p>
-      You can move a compilation unit to a different package. Imports and references are automatically updated.
-    </p>
-    <p>
-      To move a selected compilation unit and update all references to it:
-    </p>
-    <ol>
-      <li>
-        In the Package Explorer, select a compilation unit.
-      </li>
-      <li>
-        From the compilation unit's pop-up menu, select <strong>Move to Another Package</strong>. The Move Compilation Unit to Another Package page opens.
-      </li>
-      <li>
-        In the <strong>Choose package to move the compilation unit to</strong> field, type or click <strong>Browse</strong> to select the name of the package
-        where you want the compilation unit to move.
-      </li>
-      <li>
-        Click <strong>Next</strong> to perform a refactoring without preview, or click <strong>Finish</strong> to perform a refactoring with
-        preview.
-      </li>
-    </ol>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-9.htm">Refactoring support</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-    </p>
-    <p>
-      <a href="tasks-82.htm">Refactoring without preview</a><br>
-       <a href="tasks-83.htm">Refactoring with preview</a><br>
-       <a href="../tasks/tasks-92.htm">Renaming a compilation unit</a><br>
-       <a href="../tasks/tasks-51.htm">Moving folders, packages, and files</a><br>
-       <a href="../tasks/tasks-85.htm">Copying and moving Java elements</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <p>
-      <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a><br>
-       <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-87.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-87.htm
deleted file mode 100644
index d1d4e1a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-87.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Extracting a method
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Extracting a method
-    </h1>
-    <p>
-      To extract a method:
-    </p>
-    <ol>
-      <li>
-        In an editor, select a set of statements or an expression from a method body.
-      </li>
-      <li>
-        Do one of the following: 
-        <ul>
-          <li>
-            From the pop-up menu in the editor, select <strong>Refactor</strong> &gt; <strong>Extract Method</strong>.
-          </li>
-          <li>
-            From the menu bar, select <strong>Refactor</strong> &gt; <strong>Extract Method</strong>.
-          </li>
-        </ul>
-      </li>
-    </ol>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="tasks-96.htm">Renaming a method</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><a href="../reference/ref-154.htm"></a>
-    </p>
-    <p>
-      <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-       <a href="../reference/ref-117.htm">Refactoring dialogs</a><br>
-       <a href="../reference/ref-13.htm">Java preferences</a><br>
-       <a href="../reference/ref-154.htm">Extract method errors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-88.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-88.htm
deleted file mode 100644
index 5668e5e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-88.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Parameters page
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Parameters page
-    </h1>
-    <img src="../images/tasks-27.png"  alt="Parameters page of the Extract Method refactoring dialog"> 
-    <p>
-      Extract Method Parameters Page
-    </p>
-    
-<ul>
-  <li> In the <strong>Method name</strong> field, type a name for the new method 
-    that will be extracted. </li>
-  <li> In the <strong>Access Modifier</strong> list, specify the method's visibility 
-    (public, default, protected, or private). </li>
-  <li> You can <strong>Add thrown runtime exceptions to method signature</strong> 
-    by selecting the corresponding checkbox. </li>
-  <li> You can <strong>Generate method comment</strong> 
-    by selecting the corresponding checkbox. </li>  
-  <li>You can rearrange and rename the parameters for the new method.</li>
-  <li> Click <strong>OK</strong> to perform a quick refactoring, or click <strong>Preview</strong> 
-    to perform a controlled refactoring. </li>
-</ul>
-    <p>
-      Related Topics:
-    </p>
-    <ul>
-      <li>
-        <a href="tasks-82.htm">See Refactoring without Preview</a>
-      </li>
-      <li>
-        <a href="tasks-83.htm">See Refactoring with Preview</a>
-      </li>
-    </ul>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-89.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-89.htm
deleted file mode 100644
index 00c6f81..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-89.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Problems page
-    </title>
-  </head>
-  <body>
-    <h1>
-      Problems page
-    </h1>
-    <p>
-      The most common mistakes when extracting a method are:
-    </p>
-    <ul>
-      <li>
-        The selection does not cover statements or an expression from a method body.
-      </li>
-      <li>
-        The selection does not cover a whole set of statements or an expression.
-      </li>
-    </ul>
-    <p>
-      You can use the <strong>Edit</strong> &gt; <strong>Expand Selection To</strong> actions to expand an selection to a valid expression or set of statements.
-    </p>
-    <p>
-      On the problems pages, you can press F1 to link to a detailed description of errors.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-9.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-9.htm
deleted file mode 100644
index 42ec011..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-9.htm
+++ /dev/null

@@ -1,77 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Changing the active perspective when launching
-    </title>
-  </head>
-  <body>
-    <h1>
-      Changing the active perspective when launching
-    </h1>
-    You can control which perspective becomes active when a program is launched 
-and when it suspends. The setting is configurable for each launch configuration 
-type, for each of the launch modes it supports. 
-<p>To activate a particular perspective when a program is launched, do the following:</p>
-    
-<ol>
-  <li>Open the debugger launch options preferences page (<strong>Window</strong> 
-    &gt; <strong>Preferences</strong> &gt; <strong>Run/Debug</strong> &gt; <strong>Launching</strong>).</li>
-  <li>Select the <strong>Always</strong> option for the <strong>Open the associated 
-    perspective when launching</strong> preference. This will cause the perspective 
-    associated with a program to become active whenever it is launched.</li>
-</ol>
-<p>To activate a particular perspective when a program is suspends, do the following:</p>
-<ol>
-  <li>Open the debugger preferences page (<strong>Window</strong> &gt; <strong>Preferences</strong> 
-    &gt; <strong>Run/Debug</strong>).</li>
-  <li> Select the <strong>Always</strong> option for the <strong>Open the associated 
-    perspective when a breakpoint is hit</strong> preference.&nbsp; This will 
-    cause the perspective associated with a program to become active whenever 
-    a program suspends.</li>
-</ol>
-<p>To associate a particular perspective with a program, do the following:</p>
-<ol>
-  <li>Open the run dialog (<strong>Run &gt; Run...</strong>).</li>
-  <li>Select the type of launch configuration (program) that you would like to 
-    associate a perspective with (for example, <strong>Java Application</strong>). 
-    The <strong>Perspectives</strong> tab will be displayed.</li>
-  <li> For each launch mode, select the desired perspective using the combo box.&nbsp;This 
-    will cause the perspective you choose to become active based on your preference 
-    settings (i.e. when a program is launched and/or when it suspends).</li>
-  <li>Press the <strong>Apply</strong> button to save the settings.</li>
-</ol>
-<p>If the specified perspective is not open at the time it needs to be activated, 
-  that perspective is created.&nbsp;</p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-10.htm">Debugger</a><br>
-       <a href="../concepts/cremdbug.htm">Remote debugging</a><br>
-       <a href="../concepts/clocdbug.htm">Local debugging</a><br>
-       <a href="../concepts/concepts-5.htm">Java perspectives</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-      <br>
-       <a href="../tasks/tasks-126.htm">Running and debugging</a><br>
-       <a href="../tasks/tasks-executionArgs.htm">Setting execution arguments</a><br>
-       <a href="../tasks/tasks-130.htm">Launching a Java program</a><br>    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <p>
-      <a href="../reference/ref-45.htm">Console view</a><br>
-       <a href="../reference/ref-11.htm">Debug preferences</a><br>
-       <a href="../reference/ref-51.htm">Debug view</a><br>
-       <a href="../reference/ref-4.htm">Run and debug actions</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-90.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-90.htm
deleted file mode 100644
index 4c15f04..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-90.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Renaming a package
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Renaming a package
-    </h1>
-    <p>
-      To rename a package:
-    </p>
-    <ol>
-      <li>
-        In the Package Explorer or the Packages view select the package that you want to rename.
-      </li>
-      <li>
-        From the view's pop-up menu, select <strong>Refactor</strong> &gt; <strong>Rename</strong>.
-      </li>
-    </ol>
-    <p>
-      This updates all import statements of any affected compilation units and all fully qualified references to types declared in the renamed package.
-    </p>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a><br>
-       <a href="../concepts/concepts-9.htm">Refactoring support</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-77.htm">Opening a package</a><br>
-       <a href="tasks-51.htm">Moving folders, packages, and files</a><br>
-       <a href="tasks-15.htm">Creating a new Java package</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a><br>
-       <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-       <a href="../reference/ref-117.htm">Refactoring dialog</a><br>
-       <a href="../reference/ref-13.htm">Java preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-91.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-91.htm
deleted file mode 100644
index 711a44b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-91.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Parameters page
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Parameters page
-    </h1>
-    <img src="../images/tasks-28.png"  alt="Parameters page of the Rename Package refactoring dialog"> 
-    <p>
-      Rename Package Parameters Page
-    </p>
-    <ul>
-      <li>
-        In the <strong>Enter new name</strong> field, type a new name for the package.
-      </li>
-      <li>
-        If you do not want to update references to the renamed package, deselect the <strong>Update references</strong> checkbox.
-      </li>
-      <li>
-        If you want to update references to the renamed package and strings in code, select the <strong>Update textual matches in comments and strings</strong> checkbox.
-      </li>
-      <li>
-        If you want to update references in non-Java files (like XML configuration files), select the <strong>Update fully-qualified name in non-Java files</strong> checkbox.
-      </li>
-      
-  <li> Click <strong>OK</strong> to perform a quick refactoring, or click <strong>Preview</strong> 
-    to perform a controlled refactoring. </li>
-    </ul>
-    <p>
-    	<strong>Note:</strong> References in Javadoc comments, regular comments and string literals are updated based on textual matching. It is recommended that you
-    	perform a controlled refactoring and review the suggested changes if you select one of these options.
-    </p> 
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-    	<a href="tasks-82.htm">See Refactoring without Preview</a><br>
-    	<a href="tasks-83.htm">See Refactoring with Preview</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-92.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-92.htm
deleted file mode 100644
index 254b2c8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-92.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Renaming a compilation unit
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Renaming a compilation unit
-    </h1>
-    <p>
-      To rename a compilation unit:
-    </p>
-    <ol>
-      <li>
-        In the Package Explorer, select the compilation unit you want to rename.
-      </li>
-      <li>
-        From the view's pop-up menu, select <strong>Refactor</strong> &gt; <strong>Rename</strong>.
-      </li>
-    </ol>
-    <p>
-      Renaming a compilation unit also renames (and updates all references to) the top-level type that has the same name as the compilation unit. For example, renaming a
-      compilation unit <em>A.java</em> in which a class <em>A</em> is declared also renames class <em>A</em> and updates all references to it.
-    </p>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/concepts-9.htm">Refactoring support</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-85.htm">Copying and moving Java elements</a><br>
-       <a href="tasks-107.htm">Viewing compilation errors and warnings</a><br>
-       <a href="tasks-20.htm">Creating a class in an existing compilation unit</a><br>
-       <a href="tasks-25.htm">Creating a new interface in a compilation unit</a><br>
-       <a href="tasks-74.htm">Showing a type's compilation unit in the Packages view</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a><br>
-       <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-       <a href="../reference/ref-117.htm">Refactoring dialogs</a><br>
-       <a href="../reference/ref-13.htm">Java preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-93.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-93.htm
deleted file mode 100644
index 322e454..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-93.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Parameters page
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Parameters page
-    </h1>
-    <img src="../images/tasks-29.png"  alt="Parameters page of the Rename Compilation Unit refactoring dialog"> 
-    <p>
-      Rename Compilation Unit Parameters Page
-    </p>
-    <ul>
-      <li>
-        In the <strong>Enter new name</strong> field, type a new name for the compilation unit.
-      </li>
-      <li>
-        If you do not want to update references to the renamed compilation unit, deselect the <strong>Update references</strong> checkbox.
-      </li>
-      <li>
-        If you want to update references to the renamed compilation unit and strings in code, select the <strong>Update textual matches in comments and strings</strong> checkbox.
-      </li>
-      <li>
-        If you want to update references in non-Java files (like XML configuration files), select the <strong>Update fully-qualified name in non-Java files</strong> checkbox.
-      </li>
-
-  <li> Click <strong>OK</strong> to perform a quick refactoring, or click <strong>Preview</strong> 
-    to perform a controlled refactoring. </li>
-    </ul>
-    <p>
-    	<strong>Note:</strong> References in Javadoc comments, regular comments and string literals are updated based on textual matching. It is recommended
-    	that you perform a controlled refactoring and review the suggested changes if you select one of these options.
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-    	<a href="tasks-82.htm">See Refactoring without Preview</a><br>
-    	<a href="tasks-83.htm">See Refactoring with Preview</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-94.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-94.htm
deleted file mode 100644
index 1efbaba..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-94.htm
+++ /dev/null

@@ -1,70 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <meta name="Author" content="Adam Kiezun">
-    <title>
-      Renaming a type
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Renaming a type
-    </h1>
-    <p>
-      You can rename a type by modifying its declaration in the compilation unit in which it is declared. However, if you also want to update all references to
-      it, do one of the following:
-    </p>
-    <ol>
-      <li>
-        In a Java view presenting types (e.g. the Outline view, the Type Hierarchy views, etc.) select a type.
-      </li>
-      <li>
-        From the type's pop-up menu, select <strong>Refactor</strong> &gt; <strong>Rename</strong> or use the
-        <strong>Refactor</strong> &gt; <strong>Rename</strong> action from the global menu bar.
-      </li>
-    </ol>
-    or 
-    <ol>
-      <li>
-        In a Java editor, select a reference to the type.
-      </li>
-      <li>
-        From the editor's pop-up menu, select <strong>Refactor</strong> &gt; <strong>Rename</strong> or use the
-        <strong>Refactor</strong> &gt; <strong>Rename</strong> action from the global menu bar.
-      </li>
-    </ol>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/concepts-3.htm">Java projects</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-17.htm">Creating a new Java class</a><br>
-      <a href="tasks-17b.htm">Creating a new Java enum</a><br>
-       <a href="tasks-21b.htm">Creating a new Java annotation</a><br>
-       <a href="tasks-24.htm">Creating a nested interface</a><br>
-       <a href="tasks-23.htm">Creating a top-level interface</a><br>
-       <a href="tasks-18.htm">Creating a top-level class</a><br>
-       <a href="tasks-19.htm">Creating a nested class</a><br>
-       <a href="tasks-20.htm">Creating a class in an existing compilation unit</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a><br>
-       <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-       <a href="../reference/ref-117.htm">Refactoring dialogs</a><br>
-       <a href="../reference/ref-13.htm">Java preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-95.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-95.htm
deleted file mode 100644
index 4627707..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-95.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Parameters page
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Parameters page
-    </h1>
-    <img src="../images/tasks-30.png"  alt="Parameters page of the Rename Type refactoring dialog"> 
-    <p>
-      Rename Type Wizard Page
-    </p>
-    <ul>
-      <li>
-        In the <strong>Enter new name</strong> field, type a new name for the type.
-      </li>
-      <li>
-        If you do not want to update references to the renamed type, deselect the <strong>Update references to the renamed element</strong> checkbox.
-      </li>
-      <li>
-        If you want to update textual references in strings and comments which are referring to the renamed type, select the <strong>Update textual matches in comments and strings</strong> checkbox.
-      </li>
-      <li>
-        If you want to update fully qualified names in non-Java files, select the <strong>Update fully qualified name in non-Java files</strong> checkbox.
-      </li>
-      
-  <li> Click <strong>OK</strong> to perform a quick refactoring, or click <strong>Preview</strong> 
-    to perform a controlled refactoring. </li>
-    </ul>
-    <p>
-    	<strong>Note:</strong> References in comments and strings are updated based on textual matching. It is recommended that you
-    	perform a controlled refactoring and review the suggested changes if you select one of these options.
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-    	<a href="tasks-82.htm">Refactoring without Preview</a><br>
-    	<a href="tasks-83.htm">Refactoring with Preview</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-96.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-96.htm
deleted file mode 100644
index a9410d8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-96.htm
+++ /dev/null

@@ -1,75 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Renaming a method
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Renaming a method
-    </h1>
-    <p>
-      You can rename a method by modifying its declaration in the compilation unit in which it is declared. However, if you also want to update
-      all references to it, you must either:
-    </p>
-    <ol>
-      <li>
-        In a Java view presenting methods (for example the Outline view) select the method to be renamed.
-      </li>
-      <li>
-        From the view's pop-up menu, select <strong>Refactor</strong> &gt; <strong>Rename</strong> or select <strong>Refactor</strong> &gt; <strong>Rename</strong> from the global menu bar.
-      </li>
-    </ol>
-    <p>
-      or
-    </p>
-    <ol>
-      <li>
-        In a Java editor, select a reference to or the declaration of the method to be renamed.
-      </li>
-      <li>
-        From the editor's pop-up menu, select <strong>Refactor</strong> &gt; <strong>Rename</strong> or select <strong>Refactor</strong> &gt; <strong>Rename</strong> from the global menu bar.
-      </li>
-    </ol>
-    <p>
-    	<strong>Note 1:</strong> Renaming a method declared in an interface also renames (and updates all references to) all methods that are implementations of that method.
-    </p>
-    <p>
-    	<strong>Note 2:</strong> When renaming a non-static method declared as public, package visible, or protected, all methods overriding it are also renamed and all references
-    	to them are updated.
-	</p>
-	<p>
-		<strong>Note 3:</strong> Renaming a static method or a private method updates references only to that method.
-	</p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-87.htm">Extracting a method</a><br>
-       <a href="tasks-98.htm">Renaming method parameters</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-dialog-override-method.htm">Override methods</a><br>
-       <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-       <a href="../reference/ref-117.htm">Refactoring dialogs</a><br>
-       <a href="../reference/ref-13.htm">Java preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-97.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-97.htm
deleted file mode 100644
index 495c118..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-97.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Parameters page
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Parameters page
-    </h1>
-    <img src="../images/tasks-31.png"  alt="Parameters page of the Rename Method refactoring dialog"> 
-    <p>
-      Parameters Page for the Rename Method Refactoring Command
-    </p>
-    <ul>
-      <li>
-        In the <strong>Enter new name</strong>  field, type a new name for the method.
-      </li>
-      <li>
-        If you do not want to update references to the renamed method, deselect the <strong>Update references to the renamed element</strong> checkbox.
-      </li>
-      
-  <li> Click <strong>OK</strong> to perform a quick refactoring, or click <strong>Preview</strong> 
-    to perform a controlled refactoring. </li>
-    </ul>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-    	<a href="tasks-82.htm">See Refactoring without Preview</a><br>
-    	<a href="tasks-83.htm">See Refactoring with Preview</a><br>
-    	<a href="tasks-74.htm">See Showing a Type's Compilation Unit in the Packages View</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-98.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-98.htm
deleted file mode 100644
index 764be5f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-98.htm
+++ /dev/null

@@ -1,70 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Renaming method parameters
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Renaming method parameters
-    </h1>
-    <p>
-      You can rename the parameters of a method by renaming the parameter's declaration as well as all references to the parameters inside the method body.
-    </p>
-    <p>
-      Use the <strong>Change Method Signature</strong> command to rename one or more parameters of a method as well as all references to these parameters.
-    </p>
-    <ul>
-      <li>
-        Select the method in a Java view (the Outline view, for example)
-      </li>
-      <li>
-        From the method's pop-up menu, select <strong>Refactor</strong> &gt; <strong>Change Method Signature</strong> or, from the menu bar, select
-        <strong>Refactor</strong> &gt; <strong>Change Method Signature</strong>.<br>
-        <strong>Note:</strong> these menu entries will no be active if the method has no parameters.
-      </li>
-      <li>
-        Select a parameter, press the <strong>Edit</strong> button, enter a new name for the parameter and press <strong>OK</strong>
-      </li>
-    </ul>
-    <p>
-    To rename a single parameter, it is often easier to: 
-    </p>
-    <ul>
-      <li>
-        Select the parameter in the Java editor.
-      </li>
-      <li>
-        From the editor's pop-up menu, select <strong>Refactor</strong> &gt; <strong>Rename</strong> to open the Rename refactoring dialog.
-      </li>
-    </ul>
-    <p>
-    	<img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-157.htm">Changing method signature</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-       <a href="../reference/ref-117.htm">Refactoring dialogs</a><br>
-       <a href="../reference/ref-13.htm">Java preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-99.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-99.htm
deleted file mode 100644
index 8a05d2b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-99.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Parameters page
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Parameters page
-    </h1>
-    <img src="../images/tasks-32.png"  alt="Parameters page of the Change Method Signature refactoring wizard"> 
-    <p>
-      Parameters Page for the Change Method Signature Refactoring Command
-    </p>
-    <ul>
-      <li>
-        Click in the <strong>Name</strong> column on the row containing the parameter you want to change or select the row and press
-        <strong>Edit</strong> and type a new name for the parameter.
-      </li>
-    </ul>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-    	<a href="tasks-82.htm">See Refactoring without Preview</a><br>
-    	<a href="tasks-83.htm">See Refactoring with Preview</a><br>
-    	<a href="tasks-74.htm">See Showing a Type's Compilation Unit in the Packages View</a>
-    </p>    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-JREs.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-JREs.htm
deleted file mode 100644
index 6944cda..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-JREs.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Working with JREs
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Working with JREs
-    </h1>
-    <p>
-      You can install as many different Java Runtime Environments (JREs) as you like. A JRE definition consists of:
-    </p>
-    <ul>
-      <li>
-        The type of the JRE (e.g. Standard VM or Standard 1.x.x VM)
-      </li>
-      <li>
-        A name
-      </li>
-      <li>
-        The location where the JRE is installed
-      </li>
-      <li>
-        The location (URL) of the Javadoc
-      </li>
-      <li>
-        The system libraries containing the Java system classes (like java.lang.Object). Optionally, the system libraries can be associated with the source file containing the
-        source for the classes in the JRE's CLASS files
-      </li>
-    </ul>
-    <p>
-      You can switch the default JRE for the workbench. The default JRE is the JRE to which the pre-defined classpath variables JRE_LIB, JRE_SRC and JRE_SRCROOT are bound.
-    </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a><br>
-       <a href="../concepts/cclsspthv.htm">Classpath variable</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-121.htm">Adding a new JRE definition</a><br>
-       <a href="tasks-120.htm">Assigning the default JRE for the workbench</a><br>
-       <a href="tasks-124.htm">Choosing a JRE for launching a project</a><br>
-       <a href="tasks-deleteJRE.htm">Deleting a JRE definition</a><br>
-       <a href="tasks-123.htm">Editing a JRE definition</a><br>
-       <a href="tasks-122.htm">Overriding the default system libraries for a JRE definition</a><br>
-       <a href="tasks-111.htm">Viewing and editing a project's build path</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-19.htm">Installed JREs preference page</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-consoleAppearance.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-consoleAppearance.htm
deleted file mode 100644
index 3b6e899..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-consoleAppearance.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Changing the appearance of the console view
-    </title>
-  </head>
-  <body>
-    <h1>
-      Changing the appearance of the console view
-    </h1>
-    <p>
-      To set the types of output (and their colors) in the Console view:
-    </p>
-    <ol>
-      <li>
-        From the menu bar, select <strong>Window</strong> &gt; <strong>Preferences
-        &gt; Debug &gt; Console</strong> to view the Console Preferences page.
-      </li>
-      <li>
-        Checking the <strong><strong>Show when program writes to standard out</strong></strong> 
-        checkbox will make the Console view visible each
-        time new output is written to the console from the program's standard output stream. If there is no Console view in the current perspective, one will be created.
-      </li>
-      <li>
-        Checking the <strong><strong>Show when program writes to standard err</strong></strong> 
-        checkbox will make the Console view visible each
-        time new output is written to the console from the program's standard error stream. If there is no Console view in the current perspective, one will be created.
-      </li>
-      <li>
-        Click any of the color buttons to change the color for the corresponding
-        text stream.&nbsp;&nbsp;
-      </li>
-    </ol>
-    <p>To set the fonts used in the Console view:</p>
-    <ol>
-      <li>
-        From the menu bar, select <strong>Window</strong> &gt; <strong>Preferences
-        &gt; General &gt; Appearance &gt; Colors and Fonts </strong>to view the Fonts Preferences page.
-      </li>
-      <li>
-        Select <strong>Debug Console Text Font </strong>from the list of fonts
-        and use the <strong>Change... </strong>button to change the font.&nbsp;
-        (The <strong>Detail Pane Text Font</strong> can be used to change the
-        font of the debugger's detail pane).
-      </li>
-    </ol>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-10.htm">Debugger</a><br>
-       <a href="../concepts/concepts-6.htm">Java views</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <p>
-      <a href="../reference/ref-45.htm">Console view</a><br>
-       <a href="../reference/ref-24.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-debug-launch.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-debug-launch.htm
deleted file mode 100644
index e9804a3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-debug-launch.htm
+++ /dev/null

@@ -1,66 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Launching a Java program in debug mode
-    </title>
-  </head>
-  <body>
-    <h1>
-      Launching a Java program in debug mode
-    </h1>
-    <p>
-      Launching a program in debug mode allows you to suspend and resume the
-      program, inspect variables, and evaluate expressions using the debugger.
-    </p>
-    <p>
-      To launch a Java program in debug mode,
-    </p>
-    <ol>
-      <li>
-        In the Package Explorer, select the Java compilation unit or class file you want to launch.
-      </li>
-      <li>
-        Select <strong>Run &gt; Debug As &gt; Java Application</strong>.&nbsp;<br>
-        or Select
-        <strong>Debug As &gt; Java Application </strong>in the drop-down menu on the <strong>Debug</strong> tool bar button.&nbsp;
-      </li>
-      <li>
-        Your program is now launched and the launched process appears in the Debug view.&nbsp;
-      </li>
-    </ol>
-    <p>If you want your program to stop in the <em>main</em>  method so that you
-    can step through its complete execution, create a <strong> Java Application</strong>
-    launch configuration and check the <strong>Stop in main </strong>checkbox on
-    the <strong>Main </strong>tab.&nbsp;</p>
-    <p>You can also debug a Java program by selecting a project instead of the
-    compilation unit or class file.&nbsp; You will be prompted to select a class
-    from those classes that define a <em>main</em> method.&nbsp; (If only one class with a main method is
-        found in the project, that class is launched as if you selected it.)</p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/concepts-6.htm">Java views</a><br>
-       <a href="../concepts/concepts-7.htm">Java editor</a><br>
-       <a href="../concepts/concepts-10.htm">Debugger</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-141.htm">Connecting to a remote VM with the Java Remote Application launcher</a><br>
-       <a href="../tasks/tasks-131.htm">Re-launching a program</a><br>
-       <a href="../tasks/tasks-126.htm">Running and debugging</a><br>
-       <a href="../tasks/tasks-executionArgs.htm">Setting execution arguments</a><br>
-       <a href="../tasks/tasks-136.htm">Stepping through the execution of a program</a><br>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/ref-51.htm">Debug view</a><br>
-       <a href="../reference/ref-view-package-explorer.htm">Package Explorer</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-deleteJRE.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-deleteJRE.htm
deleted file mode 100644
index ff77800..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-deleteJRE.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Deleting a JRE definition
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Deleting a JRE definition
-    </h1>
-    <p>
-      <br>
-       You can delete Java runtime environment definitions that are available for executing Java programs in the workbench.
-    </p>
-    <ol>
-      <li>
-        Select&nbsp; <strong>Window</strong> &gt; <strong>Preferences</strong> from the main menu bar.
-      </li>
-      <li>
-        From the left pane, expand the <strong>Java</strong> category and select <strong>Installed JREs</strong>.
-      </li>
-      <li>
-        Select the definition you want to delete and click&nbsp;<strong><strong>Remove</strong></strong>.
-      </li>
-      <li>
-        Check the box for the definition that you want to use as the default JRE for the workbench.
-      </li>
-    </ol>
-	<p>
-     <img src="../images/ngrelc.png" alt="Related concepts" border="0" > <br>
-      <a href="../concepts/concepts-1.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-      <a href="tasks-JREs.htm">Working with JREs</a><br>
-       <a href="tasks-121.htm">Adding a new JRE definition</a><br>
-       <a href="tasks-123.htm">Editing a JRE definition</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-       <a href="../reference/ref-19.htm">Installed JREs preference page</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-executionArgs.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-executionArgs.htm
deleted file mode 100644
index 9053144..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-executionArgs.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Setting execution arguments
-    </title>
-  </head>
-  <body>
-    <h1>
-      Setting execution arguments
-    </h1>
-    <p>
-      If you want to specify execution arguments for your program, you must
-      define a launch configuration that specifies the arguments.
-    </p>
-    <ol>
-      <li>
-        Select <strong>Run &gt;Run...</strong>
-        (or&nbsp;<strong>Run &gt;Debug...)</strong> from the workbench <strong>Run</strong>
-        menu to open the list of launch configurations.&nbsp;&nbsp; Launch
-        configurations for Java programs are shown underneath <strong>Java
-        Application </strong>in this list.&nbsp;
-      </li>
-      <li>
-        Create a new launch
-        configuration by pushing the <strong>New</strong> button after selecting
-        <strong>Java Application</strong>.
-      </li>
-      <li>
-        On the <strong>Arguments</strong> tab for the configuration, you can
-        specify the following fields as necessary: 
-        <ul>
-          <li>
-            <strong>Program Arguments</strong>: Application-specific values that your code is expecting (a user name or a URL for locating help files, for
-            example).
-          </li>
-          <li>
-            <strong>VM Arguments</strong>: Values meant to change the behavior of the Java virtual machine (VM). For example, you may need to tell the VM whether
-            to use a just-in-time (JIT) compiler, or you may need to specify the maximum heap size the VM should use. Refer to your VM's documentation for more information
-            about the available VM arguments.
-          </li>
-          <li>
-            <strong>Working Directory</strong>: The working directory used for the launched process. To change from using the default working directory, uncheck
-            <strong>Use default working directory</strong> and specify the workspace or local directory to use for the working directory of the launched process.
-          </li>
-        </ul>
-      </li>
-      <li>
-        Click <strong>Apply</strong> or&nbsp; <strong>Close</strong> when you are done. Every time you launch this configuration, these execution
-        arguments will be used.
-      </li>
-    </ol>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-java-local-configuration.htm">Creating a Java Application launch
-      configuration</a><br>
-      <a href="../tasks/tasks-130.htm">Launching a Java program</a><br>
-      <br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-java-local-configuration.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-java-local-configuration.htm
deleted file mode 100644
index ae4fbd6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-java-local-configuration.htm
+++ /dev/null

@@ -1,102 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Creating a Java application launch configuration
-    </title>
-  </head>
-  <body>
-    <h1>
-      Creating a Java application launch configuration
-    </h1>
-    <p>
-      When you choose <strong>Run &gt;Run As &gt;Java Application </strong>to
-      launch your class, you are running your class using a generic <strong>Java
-      Application</strong> launch configuration that derives most of the launch
-      parameters from your Java project and your workbench preferences.&nbsp; In
-      some cases, you will want to override the derived parameters or specify
-      additional arguments.
-    </p>
-    <p>
-      You do this by creating your own <strong>Java Application</strong> launch
-      configuration.&nbsp;
-    </p>
-    <ol>
-      <li>
-        Select <strong>Run &gt;Run... </strong>or <strong>Run &gt;Debug...</strong>
-        from the workbench menu bar.&nbsp; This opens a dialog that lets you
-        create, modify, and delete launch configurations of different types.
-      </li>
-      <li>
-        Select <strong>Java Application</strong> in the left hand list of launch configuration types, and press <strong>New</strong>. This will create a new launch configuration
-        for a Java application.&nbsp;The tabs on the right hand side allow you
-        control specific aspects of the launch.
-      </li>
-    </ol>
-    <blockquote>
-      
-  <ul>
-    <li>The <strong>Main</strong> tab defines the class to be launched. Enter 
-      the name of the project containing the class to launch in the project field, 
-      and the fully qualified name of the main class in the the Main class field.&nbsp;Check 
-      the <strong>Stop in main</strong> checkbox if you want the program to stop 
-      in the main method whenever the program is launched in debug mode.<br>
-      Note:&nbsp; You do not have to specify a project, but doing so allows a 
-      default classpath, source lookup path, and JRE to be chosen.</li>
-    <li>The <strong>Arguments</strong> tab defines the arguments to be passed 
-      to the application and to the virtual machine (if any). You can also specify 
-      the working directory to be used by the launched application.</li>
-    <li>The <strong>JRE</strong> tab defines the JRE used to run or debug the 
-      application. You can select a JRE from the already defined JREs, or define 
-      a new JRE.</li>
-    <li>The <strong>Classpath</strong> tab defines the location of class files 
-      used when running or debugging an application. By default, the user and 
-      bootstrap class locations are derived from the associated project's build 
-      path. You may override these settings here.</li>
-    <li>The <strong>Source</strong> tab defines the location of source files used 
-      to display source when debugging a Java application. By default, these settings 
-      are derived from the associated project's build path. You may override these 
-      settings here.</li>
-    <li>The <strong>Environment</strong> tab defines the environment variable 
-      values to use when running or debugging a Java application. By default, 
-      the environment is inherited from the Eclipse runtime. You may override 
-      or append to the inherited environment. </li>
-    <li>The <strong>Common</strong> tab defines general information about the 
-      launch configuration.&nbsp; You may choose to store the launch configuration 
-      in a specific file and specify which perspectives become active when the 
-      launch configuration is launched.</li>
-  </ul>
-    </blockquote>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concepts-10.htm">Debugger</a><br>
-       <a href="../concepts/clocdbug.htm">Local debugging</a>
-    </p>
-    <p>
-      <br>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-    </p>
-    <p>
-      <a href="tasks-124.htm">Choosing a JRE for launching a project</a><br>
-      <a href="tasks-130.htm">Launching a Java program</a><br>
-      <a href="tasks-executionArgs.htm">Setting execution arguments<br>
-      </a><a href="../tasks/tasks-9.htm">Changing debugger launch options</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <p>
-      <a href="../reference/ref-11.htm">Debug preferences</a><br>
-       <a href="../reference/ref-51.htm">Debug view</a><br>
-       <a href="../reference/ref-4.htm">Run and debug actions</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/3.1_tag.png b/bundles/org.eclipse.jdt.doc.user/tips/images/3.1_tag.png
deleted file mode 100644
index 408c40a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/3.1_tag.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/DeclarationView.png b/bundles/org.eclipse.jdt.doc.user/tips/images/DeclarationView.png
deleted file mode 100644
index 6fc42f6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/DeclarationView.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/JavadocView.png b/bundles/org.eclipse.jdt.doc.user/tips/images/JavadocView.png
deleted file mode 100644
index 07e5a0a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/JavadocView.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/advanced-highlighting.png b/bundles/org.eclipse.jdt.doc.user/tips/images/advanced-highlighting.png
deleted file mode 100644
index 5c43ecb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/advanced-highlighting.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/annotation-navigation.png b/bundles/org.eclipse.jdt.doc.user/tips/images/annotation-navigation.png
deleted file mode 100644
index a365c10..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/annotation-navigation.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/assign-to-casted-quickfix.png b/bundles/org.eclipse.jdt.doc.user/tips/images/assign-to-casted-quickfix.png
deleted file mode 100644
index 14dda85..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/assign-to-casted-quickfix.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/build-path-actions.png b/bundles/org.eclipse.jdt.doc.user/tips/images/build-path-actions.png
deleted file mode 100644
index f9f75f1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/build-path-actions.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/call_hierarchy.png b/bundles/org.eclipse.jdt.doc.user/tips/images/call_hierarchy.png
deleted file mode 100644
index 9b66daa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/call_hierarchy.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-add-constructor.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-add-constructor.png
deleted file mode 100644
index 122c7a0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-add-constructor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-anonym.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-anonym.png
deleted file mode 100644
index b3310b9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-anonym.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-argument-proposal-inserted.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-argument-proposal-inserted.png
deleted file mode 100644
index fefdf9b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-argument-proposal-inserted.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-argument-proposal.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-argument-proposal.png
deleted file mode 100644
index 6f18eb3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-argument-proposal.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-fieldname.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-fieldname.png
deleted file mode 100644
index 9583feb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-fieldname.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-javadoc2.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-javadoc2.png
deleted file mode 100644
index ab87f47..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-javadoc2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-newmethod.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-newmethod.png
deleted file mode 100644
index fa9e113..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-newmethod.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-type-arg-guessing.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-type-arg-guessing.png
deleted file mode 100644
index ca1e2d9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-type-arg-guessing.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-type-arg-guessing2.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-type-arg-guessing2.png
deleted file mode 100644
index fb345bb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-type-arg-guessing2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist.png
deleted file mode 100644
index 2f29073..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-templates.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-templates.png
deleted file mode 100644
index e29f793..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-templates.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/codeassist-getter.png b/bundles/org.eclipse.jdt.doc.user/tips/images/codeassist-getter.png
deleted file mode 100644
index e030fa3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/codeassist-getter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/compare-java.png b/bundles/org.eclipse.jdt.doc.user/tips/images/compare-java.png
deleted file mode 100644
index d31ca1b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/compare-java.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/compare-properties.png b/bundles/org.eclipse.jdt.doc.user/tips/images/compare-properties.png
deleted file mode 100644
index 7044e42..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/compare-properties.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/compiler-projectspecific.png b/bundles/org.eclipse.jdt.doc.user/tips/images/compiler-projectspecific.png
deleted file mode 100644
index 1b76af5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/compiler-projectspecific.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/compress-packages1.png b/bundles/org.eclipse.jdt.doc.user/tips/images/compress-packages1.png
deleted file mode 100644
index 5c27c51..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/compress-packages1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/compress-packages2.png b/bundles/org.eclipse.jdt.doc.user/tips/images/compress-packages2.png
deleted file mode 100644
index 32ec61a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/compress-packages2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/create-getter-setter.png b/bundles/org.eclipse.jdt.doc.user/tips/images/create-getter-setter.png
deleted file mode 100644
index 4d355bc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/create-getter-setter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/debug-drop-down.png b/bundles/org.eclipse.jdt.doc.user/tips/images/debug-drop-down.png
deleted file mode 100644
index 10984d1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/debug-drop-down.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/delegate-method.png b/bundles/org.eclipse.jdt.doc.user/tips/images/delegate-method.png
deleted file mode 100644
index ebd6bf7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/delegate-method.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/editor-code-hover.png b/bundles/org.eclipse.jdt.doc.user/tips/images/editor-code-hover.png
deleted file mode 100644
index 9a6ada3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/editor-code-hover.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/editor-hover-window.png b/bundles/org.eclipse.jdt.doc.user/tips/images/editor-hover-window.png
deleted file mode 100644
index 621e432..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/editor-hover-window.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/editor-link-style-open.png b/bundles/org.eclipse.jdt.doc.user/tips/images/editor-link-style-open.png
deleted file mode 100644
index 5f490af..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/editor-link-style-open.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/ff4.png b/bundles/org.eclipse.jdt.doc.user/tips/images/ff4.png
deleted file mode 100644
index 1be032d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/ff4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/folding-preferences.png b/bundles/org.eclipse.jdt.doc.user/tips/images/folding-preferences.png
deleted file mode 100644
index 3b6762a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/folding-preferences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/hierarchy-lockview.png b/bundles/org.eclipse.jdt.doc.user/tips/images/hierarchy-lockview.png
deleted file mode 100644
index 1c90bec..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/hierarchy-lockview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/hovergenericsignature.png b/bundles/org.eclipse.jdt.doc.user/tips/images/hovergenericsignature.png
deleted file mode 100644
index 94a6de2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/hovergenericsignature.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/inplace_outline.png b/bundles/org.eclipse.jdt.doc.user/tips/images/inplace_outline.png
deleted file mode 100644
index d02a5dc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/inplace_outline.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-location.png b/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-location.png
deleted file mode 100644
index 0ec480c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-location.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-prefs.png b/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-prefs.png
deleted file mode 100644
index 9232cda..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-prefs.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-quickfix.png b/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-quickfix.png
deleted file mode 100644
index 7d47ae4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-quickfix.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/juniterr.png b/bundles/org.eclipse.jdt.doc.user/tips/images/juniterr.png
deleted file mode 100644
index cc5588c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/juniterr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/junitsucc.png b/bundles/org.eclipse.jdt.doc.user/tips/images/junitsucc.png
deleted file mode 100644
index 81514e5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/junitsucc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/localhistory-replace.png b/bundles/org.eclipse.jdt.doc.user/tips/images/localhistory-replace.png
deleted file mode 100644
index 58f280f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/localhistory-replace.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/localhistory-restore.png b/bundles/org.eclipse.jdt.doc.user/tips/images/localhistory-restore.png
deleted file mode 100644
index 0d10ba6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/localhistory-restore.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/mark-occurrences-toolbar.png b/bundles/org.eclipse.jdt.doc.user/tips/images/mark-occurrences-toolbar.png
deleted file mode 100644
index 6cef6c7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/mark-occurrences-toolbar.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/mark-occurrences.png b/bundles/org.eclipse.jdt.doc.user/tips/images/mark-occurrences.png
deleted file mode 100644
index 6b72139..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/mark-occurrences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/mark-return-occurrences.png b/bundles/org.eclipse.jdt.doc.user/tips/images/mark-return-occurrences.png
deleted file mode 100644
index 637e297..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/mark-return-occurrences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/matching-brackets.png b/bundles/org.eclipse.jdt.doc.user/tips/images/matching-brackets.png
deleted file mode 100644
index c38d043..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/matching-brackets.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/name-conventions.png b/bundles/org.eclipse.jdt.doc.user/tips/images/name-conventions.png
deleted file mode 100644
index eab1452..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/name-conventions.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/new-class.png b/bundles/org.eclipse.jdt.doc.user/tips/images/new-class.png
deleted file mode 100644
index 9b894ec..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/new-class.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/new-scrapbook-button.png b/bundles/org.eclipse.jdt.doc.user/tips/images/new-scrapbook-button.png
deleted file mode 100644
index 0515fad..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/new-scrapbook-button.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/open-type-camel-case.png b/bundles/org.eclipse.jdt.doc.user/tips/images/open-type-camel-case.png
deleted file mode 100644
index adc6ddd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/open-type-camel-case.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/args_tab.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/args_tab.png
deleted file mode 100644
index 58120f9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/args_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/assign_value.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/assign_value.png
deleted file mode 100644
index 8b65710..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/assign_value.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/breakpoint_condition.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/breakpoint_condition.png
deleted file mode 100644
index a54b399..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/breakpoint_condition.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/breakpoint_menu.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/breakpoint_menu.png
deleted file mode 100644
index aaef043..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/breakpoint_menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/code_assist.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/code_assist.png
deleted file mode 100644
index f0f097c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/code_assist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/context_menu_launch.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/context_menu_launch.png
deleted file mode 100644
index eb44ec5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/context_menu_launch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/deadlock.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/deadlock.png
deleted file mode 100644
index ae82340..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/deadlock.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/def_vm_args.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/def_vm_args.png
deleted file mode 100644
index 96ebf8e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/def_vm_args.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/detail_formatter.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/detail_formatter.png
deleted file mode 100644
index 1a8173f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/detail_formatter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/env_tab.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/env_tab.png
deleted file mode 100644
index b1af79a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/env_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/inspect_popup.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/inspect_popup.png
deleted file mode 100644
index 0434641..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/inspect_popup.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/logical_structure_toggle.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/logical_structure_toggle.png
deleted file mode 100644
index 6327bcc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/logical_structure_toggle.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/pin_console.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/pin_console.png
deleted file mode 100644
index 2e7c3ba..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/pin_console.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/process_properties.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/process_properties.png
deleted file mode 100644
index cf9a51e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/process_properties.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/scrapbook.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/scrapbook.png
deleted file mode 100644
index fba0890..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/scrapbook.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/stack_trace.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/stack_trace.png
deleted file mode 100644
index 78935cf..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/stack_trace.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/step_into_selection.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/step_into_selection.png
deleted file mode 100644
index de8973a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/step_into_selection.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/stop_in_main.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/stop_in_main.png
deleted file mode 100644
index 6c40676..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/stop_in_main.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/variable_hover.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/variable_hover.png
deleted file mode 100644
index 885b256..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/variable_hover.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/watchpoint_properties.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/watchpoint_properties.png
deleted file mode 100644
index e0351b0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/watchpoint_properties.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/word_wrap.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/word_wrap.png
deleted file mode 100644
index d69f984..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/word_wrap.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/override-method.png b/bundles/org.eclipse.jdt.doc.user/tips/images/override-method.png
deleted file mode 100644
index 4f101c7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/override-method.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/package-explorer.png b/bundles/org.eclipse.jdt.doc.user/tips/images/package-explorer.png
deleted file mode 100644
index 9480c0f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/package-explorer.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/packages-compound.png b/bundles/org.eclipse.jdt.doc.user/tips/images/packages-compound.png
deleted file mode 100644
index 1ed0bd4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/packages-compound.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/packages-flat.png b/bundles/org.eclipse.jdt.doc.user/tips/images/packages-flat.png
deleted file mode 100644
index dbb64ab..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/packages-flat.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/packages-hierarchical.png b/bundles/org.eclipse.jdt.doc.user/tips/images/packages-hierarchical.png
deleted file mode 100644
index 81e45a3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/packages-hierarchical.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/parameter-hints.png b/bundles/org.eclipse.jdt.doc.user/tips/images/parameter-hints.png
deleted file mode 100644
index bea48a2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/parameter-hints.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/problems-in-javadoc.png b/bundles/org.eclipse.jdt.doc.user/tips/images/problems-in-javadoc.png
deleted file mode 100644
index 430634d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/problems-in-javadoc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/project-specific-jre.png b/bundles/org.eclipse.jdt.doc.user/tips/images/project-specific-jre.png
deleted file mode 100644
index 567dc4c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/project-specific-jre.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/project-specific-settings.png b/bundles/org.eclipse.jdt.doc.user/tips/images/project-specific-settings.png
deleted file mode 100644
index ab79a0b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/project-specific-settings.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-assign-statement.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-assign-statement.png
deleted file mode 100644
index c3d03aa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-assign-statement.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-assign-statement2.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-assign-statement2.png
deleted file mode 100644
index 901319d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-assign-statement2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-catch-to-throws.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-catch-to-throws.png
deleted file mode 100644
index a444406..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-catch-to-throws.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-create-field.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-create-field.png
deleted file mode 100644
index b21c702..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-create-field.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-remove-surrounding.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-remove-surrounding.png
deleted file mode 100644
index 8ecf462..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-remove-surrounding.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-shortcuts.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-shortcuts.png
deleted file mode 100644
index a9ee030..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-shortcuts.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-create-method.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-create-method.png
deleted file mode 100644
index 20c5725..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-create-method.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-localrename.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-localrename.png
deleted file mode 100644
index 0431faa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-localrename.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-uncaught-exception.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-uncaught-exception.png
deleted file mode 100644
index 00224ca..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-uncaught-exception.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-unimplemented-methods.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-unimplemented-methods.png
deleted file mode 100644
index a76e6f6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-unimplemented-methods.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-outline-inherited.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-outline-inherited.png
deleted file mode 100644
index 7138206..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-outline-inherited.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-refactoring-menu.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-refactoring-menu.png
deleted file mode 100644
index 0478e4e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-refactoring-menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast1.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast1.png
deleted file mode 100644
index 38c9ae9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast2.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast2.png
deleted file mode 100644
index 8d27bdf..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast3.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast3.png
deleted file mode 100644
index 6189f67..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-change-signature.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-change-signature.png
deleted file mode 100644
index e8076d7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-change-signature.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/search-returntype.png b/bundles/org.eclipse.jdt.doc.user/tips/images/search-returntype.png
deleted file mode 100644
index 93fff1a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/search-returntype.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/search.png b/bundles/org.eclipse.jdt.doc.user/tips/images/search.png
deleted file mode 100644
index e5b6be5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/search.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/smart-javadoc.png b/bundles/org.eclipse.jdt.doc.user/tips/images/smart-javadoc.png
deleted file mode 100644
index e50933a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/smart-javadoc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/sort-by-def.png b/bundles/org.eclipse.jdt.doc.user/tips/images/sort-by-def.png
deleted file mode 100644
index 574424b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/sort-by-def.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/spelling-correction-proposal.png b/bundles/org.eclipse.jdt.doc.user/tips/images/spelling-correction-proposal.png
deleted file mode 100644
index 737c4ca..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/spelling-correction-proposal.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/ss4.png b/bundles/org.eclipse.jdt.doc.user/tips/images/ss4.png
deleted file mode 100644
index 078da49..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/ss4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/suppresswarningsR31.png b/bundles/org.eclipse.jdt.doc.user/tips/images/suppresswarningsR31.png
deleted file mode 100644
index 3392312..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/suppresswarningsR31.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/surroundwith.png b/bundles/org.eclipse.jdt.doc.user/tips/images/surroundwith.png
deleted file mode 100644
index 7bd18c2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/surroundwith.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/template-for-iter.png b/bundles/org.eclipse.jdt.doc.user/tips/images/template-for-iter.png
deleted file mode 100644
index 9b8215a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/template-for-iter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/templates-create-method.png b/bundles/org.eclipse.jdt.doc.user/tips/images/templates-create-method.png
deleted file mode 100644
index 1fc6146..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/templates-create-method.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/todo-example.png b/bundles/org.eclipse.jdt.doc.user/tips/images/todo-example.png
deleted file mode 100644
index e7ca3b4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/todo-example.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/type-access-rules.png b/bundles/org.eclipse.jdt.doc.user/tips/images/type-access-rules.png
deleted file mode 100644
index 6fb0620..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/type-access-rules.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/type-filter.png b/bundles/org.eclipse.jdt.doc.user/tips/images/type-filter.png
deleted file mode 100644
index 0a2c9ea..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/type-filter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/type-hierarchy-structured-view.png b/bundles/org.eclipse.jdt.doc.user/tips/images/type-hierarchy-structured-view.png
deleted file mode 100644
index 5989fb6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/type-hierarchy-structured-view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/typing-preferences.png b/bundles/org.eclipse.jdt.doc.user/tips/images/typing-preferences.png
deleted file mode 100644
index 4980b1c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/typing-preferences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-i.png b/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-i.png
deleted file mode 100644
index d11788b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-i.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-opt.png b/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-opt.png
deleted file mode 100644
index a8bc066..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-opt.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-x.png b/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-x.png
deleted file mode 100644
index cab1804..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-x.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-x2.png b/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-x2.png
deleted file mode 100644
index 5a7054b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-x2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-y.png b/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-y.png
deleted file mode 100644
index 3f854ff..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-y.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-y2.png b/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-y2.png
deleted file mode 100644
index a7bff68..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-y2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-privates.png b/bundles/org.eclipse.jdt.doc.user/tips/images/warn-privates.png
deleted file mode 100644
index 3f2026b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-privates.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/jdt_tips.html b/bundles/org.eclipse.jdt.doc.user/tips/jdt_tips.html
deleted file mode 100644
index f54bc72..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/jdt_tips.html
+++ /dev/null

@@ -1,1674 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
-	type="text/css">
-<title>Tips and Tricks</title>
-
-</head>
-<body>
-
-<h2>Tips and Tricks</h2>
-<table border="0" cellpadding="8">
-	<tbody>
-		<tr>
-			<td width="16%" align="center"><a href="#editing_section">Editing</a></td>
-			<td width="16%" align="center"><a href="#searching_section">Searching</a></td>
-			<td width="16%" align="center"><a href="#navigation_section">Navigation</a></td>
-			<td width="16%" align="center"><a href="#views_section">Views</a></td>
-			<td width="16%" align="center"><a href="#debugging_section">Debugging</a></td>
-			<td width="16%" align="center"><a href="#misc_section">Miscellaneous</a></td>
-		</tr>
-	</tbody>
-</table>
-<h3><a name="editing_section"></a>Editing source</h3>
-
-<table border="1" cellpadding="10" cellspacing="0" width="600" bgcolor="white">
-	<tbody>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Content assist</b></td>
-			<td valign="top" align="left" width="80%">Content assist provides you
-			with a list of suggested completions for partially entered strings.
-			In the Java editor press <b>Ctrl+Space</b> or invoke <b>Edit &gt;
-			Content Assist</b>.
-			<p><img src="images/code-assist.png" border="0" alt="Content assist selection dialog">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Content assist in
-			Javadoc comments</b></td>
-			<td valign="top" align="left" width="80%">Content assist is also
-			available in Javadoc comments.
-			<p><img src="images/code-assist-javadoc2.png" border="0" alt="Content assist for Javadoc comments">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Suppress types in code
-			assist</b></td>
-			<td valign="top" align="left" width="80%">
-			<p>To exclude certain types from appearing in content assist, use the type
-			filter feature configured on the <b>Window &gt; Preferences &gt; Java &gt; Appearance &gt; Type Filters</b>
-			preference page. Types matching one of these filter patterns
-			will not appear in the Open Type dialog and will not be available to
-			code assist, quick fix and organize imports. These filter patterns
-			do not affect the Package Explorer and Type Hierarchy views.</p>
-			<img border="0" src="images/type-filter.png" alt="Type filter preference page"></td>
-
-		</tr>
-		<tr>
-
-			<td width="20%" valign="top" align="left"><b>Content assist for
-			variable, method parameter and field name completions</b></td>
-
-			<td valign="top" align="left" width="80%">
-			<p>You can use content assist to speed up the creation of fields, method
-			parameters and local variables. With the cursor positioned after the
-			type name of the declaration, invoke <b>Edit &gt; Content Assist</b>
-			or press <b>Ctrl+Space</b>.</p>
-			<p><img src="images/code-assist-fieldname.png" alt="Suggestions for field names">
-</p>
-			<p>If you use a name prefix or suffix for fields, local variables or
-			method parameters, be sure to specify this in the Code Style
-			preference page <b>(Window &gt; Preferences &gt; Java &gt; Code
-			Style)</b>.</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Parameter Hints</b></td>
-			<td valign="top" align="left" width="80%">With the cursor in a method
-			argument, you can see a list of parameter hints. In the Java Editor
-			press <b>Ctrl+Shift+Space</b> or invoke <b>Edit &gt; Parameter Hints</b>.
-			<p><img src="images/parameter-hints.png" border="0" alt="Parameter hint hover">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Content assist on
-			anonymous classes</b></td>
-			<td valign="top" align="left" width="80%">Content assist also
-			provides help when creating an anonymous class. With the cursor
-			positioned after the opening bracket of a class instance creation,
-			invoke <b>Edit &gt; Content Assist</b> or press <b>Ctrl+Space</b>.
-			<p><img src="images/code-assist-anonym.png" border="0" alt="Content assist for an anonymous class">
-</p>
-			This will create the body of the anonymous inner class including all
-			methods that need to be implemented.</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Toggle between
-			inserting and replacing code assist</b></td>
-
-			<td valign="top" align="left" width="80%">When code assist is invoked
-			on an existing identifier, code assist can either replace the
-			identifier with the chosen completion or do an insert. The
-			default behavior (overwrite or insert) is defined in <b>Window &gt;
-			Preferences &gt; Java &gt; Editor &gt; Code Assist</b>.<br>
-			You can temporarily toggle the behavior while inside the content
-			assist selection dialog by pressing and holding the <b>Ctrl</b> key while
-			selecting the completion.</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Incremental content
-			assist</b></td>
-			
-			<td>Per default, content assist will now <b>Insert common prefixes automatically</b>, similar to 
-			Unix shell expansion. To change that behavior uncheck the setting on the <b>Window &gt; Preferences &gt; Java
-			&gt; Editor &gt; Code Assist</b> preference page.</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Create Getter and
-			Setters dialog</b></td>
-			<td valign="top" align="left" width="80%">To create getter and setter
-			methods for a field, select the field's declaration and invoke <b>Source
-			&gt; Generate Getter and Setter</b>.
-			<p><img src="images/create-getter-setter.png" border="0" alt="Generate Getter and Setter dialog">
-</p>
-			If you use a name prefix or suffix be sure to specify this in the
-			Code Style preference page <b>(Window &gt; Preferences &gt; Java &gt;
-			Code Style)</b>. </td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use content assist to
-			create Getter and Setters</b></td>
-			<td valign="top" align="left" width="80%">Another way to create
-			getters and setters is using content assist. Set the cursor in the
-			type body between members and press <b>Ctrl+Space</b> to get the proposals
-			that create a getter or setter method stub. <br>
-			<img border="0" src="images/codeassist-getter.png" alt="Code assist for creating a setter"></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Delete Getters and
-			Setters together with a field</b></td>
-
-			<td valign="top" align="left" width="80%">When you delete a field
-			from within a view,
-			Eclipse can propose deleting its Getter and Setter methods. If you
-			use a name prefix or suffix for fields, be sure to specify this
-			in the Code Style preference page <b>(Window &gt; Preferences &gt;
-			Java &gt; Code Style)</b>.</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Create delegate methods</b></td>
-			<td valign="top" align="left" width="80%">To create a delegate method
-			for a field select the field's declaration and invoke <b>Source &gt;
-			<b>Generate Delegate Methods</b></b>. This adds the selected methods
-			to the type that contains a forward call to delegated methods. This
-			is an example of a delegate method: <br>
-			<img src="images/delegate-method.png" border="0" alt="Delegate method example">
- <TT></TT></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use Drag &amp; Drop for
-			refactoring</b></td>
-			<td valign="top" align="left" width="80%">You can move Java
-			compilation units between packages by Drag &amp; Drop - all missing
-			imports will be added and references updated.</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use Drag &amp; Drop to
-			move and copy Java code elements</b></td>
-			<td valign="top" align="left" width="80%">You can move and copy Java
-			elements such as methods and fields by Drag &amp; Drop. This will not
-			trigger refactoring - only the code will be copied or moved.</td>
-		</tr>
-
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use Templates to create
-			a method</b></td>
-			<td valign="top" align="left" width="80%">You can define a new
-			template <b>(Window &gt; Preferences &gt; Java &gt; Editor &gt; Templates)</b>
-			that contains a method stub. Templates are shown together with the <b>Content
-			Assist (Ctrl+Space)</b> proposals.<br>
-			There are also existing templates, such as 'private_method',
-			'public_method', 'protected_method' and more.<br>
-			Use the <b>Tab</b> key to navigate between the values to enter
-			(return type, name and arguments).
-			<p><img src="images/templates-create-method.png" border="0" alt="Content assist with new method template proposals">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use Quick Fix to create
-			a new method</b></td>
-			<td valign="top" align="left" width="80%">Start with the method
-			invocation and use <b>Quick Fix (Ctrl+1)</b> to create the method.
-			<p><img src="images/quick-fix-create-method.png" border="0" alt="'Create method' quick fix">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use Quick Fix to change
-			a method signature</b></td>
-			<td valign="top" align="left" width="80%">Add an argument to a method
-			invocation at a call site. Then use <b>Quick Fix (Ctrl+1)</b> to add the
-			required parameter in the method declaration.
-			<p><img src="images/quickfix-change-signature.png" border="0" alt="'Change signature' quick fix">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use Content Assist to
-			create a constructor stub</b></td>
-			<td valign="top" align="left" width="80%">At the location where you
-			want to add the new constructor, use code assist after typing the
-			first letters of the constructor name.<br>
-			<img border="0" src="images/code-assist-add-constructor.png" alt="Create constructor on code assist"></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Create new fields from
-			parameters</b></td>
-			<td valign="top" align="left" width="80%">Do you need to create new
-			fields to store the arguments passed in the constructor? Use <b>Quick
-			Assist (Ctrl+1)</b> on a parameter to create the assignment and the
-			field declaration and let Eclipse propose a name according to your Code
-			Style preferences.<br>
-			<img border="0" src="images/quick-assist-create-field.png" alt="'Assign parameter to new field' quick assist"></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use Content Assist to
-			override a method</b></td>
-			<td valign="top" align="left" width="80%">Invoke <b>Content Assist
-			(Ctrl+Space)</b> in the type body at the location where the method
-			should be added. Content assist will offer all methods that can be
-			overridden. A method body for the chosen method will be created.
-			<p><img src="images/code-assist-newmethod.png" border="0" alt="'Override method' content assist">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use Quick Fix to add
-			unimplemented methods</b></td>
-			<td valign="top" align="left" width="80%">To implement a new
-			interface, add the 'implements' declaration first to the type.
-			Even without saving or building, the Java editor will underline the
-			type to signal that methods are missing and will show the Quick Fix
-			light bulb. Click on the light bulb or press <b>Ctrl+1 (Edit &gt;
-			Quick Fix)</b> to choose between adding the unimplemented methods or
-			making your class abstract.
-			<p><img src="images/quick-fix-unimplemented-methods.png" border="0" alt="Quick Fix offering 'Add unimplemented methods' proposal">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Override a method
-			from a base class</b></td>
-			<td valign="top" align="left" width="80%">To create a method that
-			overrides a method from a base class: <br>
-			Select the type where the methods should be added and invoke <b>Source &gt;
-			Override / Implement Methods</b>. This opens a dialog that lets you
-			choose which methods to override.
-			<p><img src="images/override-method.png" border="0" alt="'Override / Implement method' dialog">
-</p>
-			</td>
-		</tr>
-
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Rename in File</b></td><td valign="top" align="left" width="80%">To quickly do a rename that
-			doesn't require full analysis of dependencies in other files, use the
-			'rename in file' Quick Assist. In the Java Editor, position the
-			cursor in an identifier of a variable, method or type and press <b>Ctrl+1
-			(Edit &gt; Quick Fix)</b><br>
-			The editor is switched to the linked edit mode (like templates) and
-			changing the identifier simultaneously changes all other references
-			to that variable, method or type.
-			<p><img src="images/quick-fix-localrename.png" border="0" alt="Changing multiple identifiers using 'Local Rename' quick fix">
-</p>
-			</td>
-			
-		</tr>
-		
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use Quick Fix to handle
-			exceptions</b></td>
-			<td width="80%" valign="top">Dealing with thrown exceptions is 
-			easy. Unhandled exceptions are detected while typing and marked with
-			a red line in the editor.
-			<ul>
-				<li>Click on the light bulb or press <b>Ctrl+1</b> to surround the
-				call with a try catch block. If you want to include more statements
-				in the try block, select the statements and use <b>Source &gt;
-				Surround With try/catch Block</b>. You can also select individual
-				statements by using <b>Edit &gt; Expand Selection to </b> and
-				selecting <b>Enclosing</b>, <b>Next</b> or <b>Previous</b>.</li>
-				<li>If the call is already surrounded with a try block, Quick Fix
-				will suggest adding the catch block to the existing block.</li>
-				<li>If you don't want to handle the exception, let Quick Fix add a
-				new thrown exception to the enclosing method declaration</li>
-
-			</ul>
-			<p><img src="images/quick-fix-uncaught-exception.png" border="0" alt="'Uncaught exception' quick fix proposals">
-</p>
-			At any time you can convert a catch block to a thrown exception. Use
-			<b>Ctrl+1 (Edit &gt; Quick Fix)</b> on a catch block.<br>
-			<p><img src="images/quick-assist-catch-to-throws.png" border="0" alt="'Replace catch clause with throws' quick assist">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Less typing for
-			assignments</b></td>
-			<td width="80%" valign="top">Instead of typing an assignment, start
-			with the expression that will be assigned.
-			<p><img src="images/quick-assist-assign-statement.png" border="0" alt="'Assign statement to local variable' quick assist">
-</p>
-			Now use <b>Ctrl+1 (Edit &gt; Quick Fix)</b> and choose '<b>Assign
-			statement to new local variable</b>' and Quick Assist will guess a
-			variable name for you. <br>
-			<img src="images/quick-assist-assign-statement2.png" alt="Quick Assist Assignment" border="0"></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Less work with cast
-			expressions</b></td>
-			<td width="80%" valign="top">Don't spend too much time with typing casts. Ignore them first and use quick assist to add them after
-			finishing the statement. <br>
-			For example on assignments:<br>
-			<img border="0" src="images/quickfix-addcast1.png" alt="Add cast in assignment"> <br>
-			Or in for method arguments:<br>
-			<img border="0" src="images/quickfix-addcast2.png" alt="Add cast for method arguments"> <br>
-			Or for method call targets<br>
-			<img border="0" src="images/quickfix-addcast3.png" alt="Add cast in method call targets"></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Assign a casted
-			expression</b><br>
-			<img border="0" src="images/3.1_tag.png" alt="New in 3.1">
-			</td>
-			<td width="80%" valign="top">After an 'instanceof' check, it is very common to cast the expression and assign it to a new local variable. Invoke <b>Quick
-			Assist (Ctrl+1)</b> on the 'instanceof' keyword to save yourself some typing:<br>
-			<img border="0" src="images/assign-to-casted-quickfix.png"
-				alt="'Introduce new local with casted type' quick fix">
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>More quick assists</b><br>
-			<img border="0" src="images/3.1_tag.png" alt="New in 3.1"></td>
-			<td width="80%" valign="top">Check out the <a
-				href="../concepts/cquickassists.htm">quick assist</a> page for a complete list of available code transformations. Amongst them are<ul>
-				<li>Invert if statements</li>
-				<li>Convert 'switch' into 'if-else'</li>
-				<li>Replace 'if-else' with conditional<br>...and many more</li>
-				
-			</ul>A list of quick fixes can be found <a
-				href="../concepts/cquickfix.htm">here</a>.
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Shortcuts for Quick Fixes and Assists<br>
-			<img border="0" src="images/3.1_tag.png" alt="New in 3.1"></b></td>
-			<td valign="top" align="left" width="80%">Some of the popular quick assists like <b>Rename
-			In File</b> and <b>Assign To Local</b> can be invoked
-			directly with <b>Ctrl+2&nbsp;R</b> and <b>Ctrl+2&nbsp;L</b>. Check
-			the keys preference page for more quick fixes that support direct
-			invocation.
-			<p><img src="images/quick-assist-shortcuts.png" alt="Keys preference page with quick assist shortcuts"></p>
-			</td>
-		</tr><tr>
-			<td width="20%" valign="top" align="left"><b>Surround lines</b></td>
-			<td width="80%" valign="top">To surround statements with an if /
-			while / for statement or a block, select the lines to surround and
-			press <b>Ctrl+1 (Edit &gt; Quick Fix)</b>. This lists all templates
-			that contain the variable ${line_selection}.
-			<p><img src="images/surroundwith.png" border="0" alt="'Surround with templates' quick assist">
-</p>
-			Templates can be configured on <b>Window &gt; Preferences &gt; Java
-			&gt; Editor &gt; Templates</b>. Edit the corresponding templates or
-			define your own templates to customize the resulting code.<br>
-			</td>
-		</tr>
-
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Create your own
-			templates</b></td>
-			<td width="80%" valign="top">
-			<p>To create your own templates, go to the <b>Window &gt; Preferences &gt; Java &gt; Editor
-			&gt; Templates</b> preference page and press the <b>New</b> button to
-			create a template. For example, a template to iterate backwards in an
-			array would look like this:</p>
-			<img border="0" src="images/template-for-iter.png" 
-				alt="Template showing backward iteration"></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Code assist can insert
-			argument names automatically</b></td>
-
-			<td width="80%" valign="top">
-			<p>You can have code assist insert argument names automatically on
-			method completion. This behavior can be customized on the <b>Window &gt; Preferences &gt; Java
-			&gt; Editor &gt; Code Assist</b> preference page (see the <b>Fill
-			argument names on completion</b> checkbox.) For example, when
-			you select the second entry here, </p>
-			<p><img src="images/code-assist-argument-proposal.png" alt="code assist window">
-</p>
-			<p>code assist will automatically insert argument names:</p>
-			<p><img src="images/code-assist-argument-proposal-inserted.png" alt="code assist inserted argument names">
-</p>
-			<p>you can then use the <b>Tab</b> key to navigate between the
-			inserted names.</p>
-			<p>Code assist can also guess argument names - based on their
-			declared types. This can be configured by the <b>Guess filled
-			argument names</b> checkbox on the <b>Window &gt; Preferences &gt; Java &gt; Editor &gt; Code
-			Assist</b> preference page.</p>
-			</td>
-
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Automatically insert
-			type arguments</b><br>
-			<img border="0" src="images/3.1_tag.png" alt="New in 3.1">
-			</td>
-			<td width="80%" valign="top">Enabling <b>Fill argument names on completion</b> on the <b>Window
-			&gt; Preferences &gt; Java &gt; Editor &gt; Code Assist</b> preference page is also useful when working with parameterized types in J2SE 5.0.<br>
-			<img border="0" src="images/code-assist-type-arg-guessing.png"
-				alt="Code assist on a parameterized type">
-			<br>results in<br>
-			<img border="0" src="images/code-assist-type-arg-guessing2.png"
-				alt="Code assist guessed and inserted type argument">
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Remove surrounding
-			statement</b></td>
-			<td width="80%" valign="top">To remove a surrounding statement or
-			block, position the cursor at the opening bracket and press <b>Ctrl+1
-			(Edit &gt; Quick Fix)</b>.
-			<p><img src="images/quick-assist-remove-surrounding.png" border="0" alt="'Remove surrounding statement' quick assist">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>How was that word spelled again?</b></td>
-			<td>You can enable spell-checking support in the Java editor on the
-			<b>General &gt; Editors &gt; Text Editors &gt; Spelling</b> preference page. Spelling errors
-			are displayed in the Java editor and corresponding Quick Fixes are available:
-			<p><img alt="An example of a spelling correction proposal." title="Spelling Correction Proposal" src="images/spelling-correction-proposal.png" align="middle"></p>
-			<p>You can make the
-			dictionary also available to the content assist. However, there is currently no dictionary included in Eclipse. The required format
-			is just a list of words separated by new lines and the Quick Fixes allow you to
-			add new words to the dictionary on-the-fly. Contributions of dictionaries would be welcome.</p>
-				</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Structured selections</b></td>
-			<td width="80%" valign="top">You can quickly select Java code
-			syntactically using the Structured Selection feature.<br>
-			Highlight the text and press <b>Alt+Shift+Arrow Up</b> or select <b>Edit
-			&gt; Expands Selection To &gt; Enclosing Element</b> from the menu
-			bar - the selection will be expanded to the smallest Java-syntax
-			element that contains the selection. You can then further expand the
-			selection by invoking the action again.</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Find the matching
-			bracket</b></td>
-			<td width="80%" valign="top">To find a matching bracket select an
-			opening or closing bracket and press <b>Ctrl+Shift+P (Navigate &gt;
-			Go To &gt; Matching Bracket)</b>. You can also <b>double click</b>
-			before an opening or after a closing bracket - this selects the text
-			between the two brackets.
-			<p><img src="images/matching-brackets.png" border="0" alt="Using 'double click' to select text between two brackets">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Smart Javadoc</b></td>
-			<td width="80%" valign="top">Type '/**' and press <b>Enter</b>. This
-			automatically adds a Javadoc comment stub containing the standard
-			@param, @return and @exception tags.
-			<p><img src="images/smart-javadoc.png" border="0" alt="Result of 'Smart Javadoc'">
-</p>
-			The templates for the new comment can be configured in <b>Window
-			&gt; Preferences &gt; Java &gt; Code Style &gt; Code Templates</b></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use the local history
-			to revert back to a previous edition of a method</b></td>
-			<td valign="top" align="left" width="80%">Whenever you edit a file,
-			its previous contents are kept in the local history. Java tooling
-			makes the local history available for Java elements, so you can
-			revert back to a previous edition of a single method instead of the
-			full file.
-			<p>Select an element and use <b>Replace With &gt; Local History</b>
-			to revert back to a previous edition of the element.</p>
-			<p><img src="images/localhistory-replace.png" border="0" alt="Replace form local history dialog">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use the local history
-			to restore removed methods</b></td>
-			<td valign="top" align="left" width="80%">Whenever you edit a file,
-			its previous contents are kept in the local history. Java tooling
-			makes the local history available for Java elements, so you can
-			restore deleted methods selectively.
-			<p>Select a container and use <b>Restore from Local History</b> to
-			restore any removed members.</p>
-			<p><img src="images/localhistory-restore.png" border="0" alt="Restore from local history dialog">
-</p>
-			</td>
-		</tr>
-
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Customizable code
-			generation</b></td>
-			<td width="80%" valign="top" align="left">The <b>Window &gt; Preferences &gt; Java &gt; Code Style
-			&gt; Code Templates</b> preference page allows you to customize
-			generated code and comments in a similar way to normal templates.
-			These code templates are used whenever code is generated.<br>
-			<img
-				src="images/code-templates.png" border="0"
-				alt="Code templates preference page"><br>
-			<br>
-			Since 3.1, it is possible to project specific Code templates, that will also be shared in the team if your project is shared. Open the <b>Properties</b> on project to enable project specific settings.
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Create comments in your
-			code</b></td>
-			<td width="80%" valign="top" align="left">Comments can be added explicitly with <b>Source &gt; Generate Element Comment (Ctrl+Shift+J)</b> or automatically by various wizards, refactorings or quick fixes.<br>Configure the comment   templates on the <b>Window
-			&gt; Preferences &gt; Java &gt; Code Style &gt; Code Templates</b> preference page.<br>Enable or disable the automatic generation of comments either directly on the wizard (e.g. using <b>'Generate
-			Comment'</b> checkbox on the new Java type wizards) or by the <b>'Automatically
-			add new comments for new methods and types'</b> checkbox of the <b>Window
-			&gt; Preferences &gt; Java &gt; Code Style</b> page.<br>All these settings can also be configured on a per project basis. Open the <b>Properties</b> on project to enable project specific settings.</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Sort members</b></td>
-			<td width="80%" valign="top" align="left">You can <b>Sort Members</b>
-			of a Java compilation unit according to a category order defined in
-			the <b>Window
-			&gt; Preferences &gt; Java &gt; Appearance &gt; Members Sort Order</b> preference
-			page.<br>
-			You'll find the action under <b>Source &gt; Sort Members</b></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Wrap Strings</b></td>
-			<td width="80%" valign="top" align="left">
-			<p>You can have String literals wrapped when you edit them. For
-			example, if you have code like this:</p>
-			<pre>String message= &quot;This is a very long message.&quot;;</pre>
-
-			<p>position your caret after the word &quot;very&quot; and press <b>Enter</b>.
-			The code will be automatically changed to:</p>
-			<pre>String message= &quot;This is a very&quot; + 
-           &quot; long message.&quot;;</pre>
-			<p>This behavior can be customized in the <b>Window
-			&gt; Preferences &gt; Java &gt; Editor &gt;
-			Typing</b> preference page.</p>
-			</td>
-		</tr>
-
-		<tr>
-			<td valign="top" align="left"><b>Smart Typing and how to control it</b></td>
-			<td>
-			The Java editor's Smart Typing features ease your daily work. You can configure
-			them on the     <b>Java&nbsp;&gt;&nbsp;Editor &gt; Typing</b> preference page.
-			<p>
-			<img src="images/typing-preferences.png" border="0" alt="Java editor typing preference page" title="Typing Preference Page" align="middle">
-</p>
-			<p>
-			When you enable <b>Automatically insert Semicolons at correct
-			position</b>, typing a semicolon  automatically positions the cursor at the end of the statement before inserting the semicolon. This safes you some additional cursor navigation.<br>
-			You can
-			undo this automatic positioning by pressing backspace right afterwards.
-			</p>
-			</td>
-		</tr>
-		
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Fix your code
-			indentation with one key stroke</b></td>
-			<td width="80%" valign="top" align="left">A useful feature is <b>Source
-			&gt; Correct Indentation</b> or <b>Ctrl+I</b>. Select the code where the indents are
-			incorrect and invoke the action.</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Quick menus for source and
-			refactoring actions</b></td>
-			<td align="left" valign="top">
-			<p>The refactoring and source actions can be accessed via a quick
-			menu. Select the element to be manipulated in the Java editor or in a
-			Java view and press <b>Alt+Shift+S</b> for the quick source menu or
-			<b>Alt+Shift+T</b> for the quick refactoring menu.</p>
-			<img border="0" src="images/quick-refactoring-menu.png" alt="Quick refactoring menu"></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Find unused code</b></td>
-			<td width="80%" valign="top" align="left">The Java compiler detects
-			unreachable code, unused variables, parameters, imports and unused
-			private types, methods and fields. 
-			The setting is on the <b>Window
-			&gt; Preferences &gt; Java &gt; Compiler &gt; <b>Error/Warnings</b></b> preference page (or set for an individual
-			project using <b>Project &gt; Properties &gt; Java Compiler &gt;
-			Error/Warnings</b>).<p><img src="images/warn-privates.png" border="0" alt="Compiler preference page">
-</p>
-			These settings are also detected as you type and a quick fix is
-			offered to remove the unneeded code.</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Javadoc comment handling</b></td>
-			<td>The Eclipse Java compiler can process Javadoc comments. Search
-			reports references in doc comments, and refactoring updates these
-			references as well. This feature is controlled from the <b>Window &gt;
-			Preferences &gt; Java &gt;
-			Compiler &gt; Javadoc</b> preference page (or set for an individual
-			project using <b>Project &gt; Properties &gt; Java Compiler &gt;
-			Javadoc</b>).
-			<p><img src="images/javadoc-prefs.png" alt="Javadoc preference page">
-</p>When turned on, malformed Javadoc comments are marked in the Java editor and can be fixed using <b>Edit
-			&gt; Quick Fix (Ctrl+1)</b>: 
-			<p>
-			<img src="images/javadoc-quickfix.png" alt="Problems detected in Javadoc" title="Problems detected in Javadoc">
-</p></td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Suppress warnings</b><br><img src="images/3.1_tag.png" border="0" alt="New in 3.1"></td>
-			<td>In J2SE 5.0 you can suppress all optional compiler warnings using the 'SuppressWarnings' annotation.<br>
-			In this example 'addAll()' is marked as an unused method. <b>Quick Fix (Ctrl+1)</b> is used to add a SuppressWarnings annotation so that the warning will  not be shown for this method.<br>
-			<img src="images/suppresswarningsR31.png" border="0"
-				alt="Quick fix to add SuppressWarning annotation">
-			</td>
-		</tr>
-
-	</tbody>
-</table>
-<h3><a name="searching_section"></a>Searching</h3>
-
-<table border="1" cellpadding="10" cellspacing="0" width="600"
-	bgcolor="white">
-	<tbody>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Locate variables and
-			their read/write access</b></td>
-			<td valign="top" align="left" width="80%">You can locate variables
-			and see their read/write status by selecting an identifier
-			(variable, method or type reference or declaration) and invoking <b>Search
-			&gt; Occurrences in File</b>. This marks all references of this
-			identifier in the same file. The results are also shown in the search
-			view, along with icons showing the variable's read or write access.<br>
-			<p><img src="images/search.png"  border="0" alt="Read and write accesses to a field">
-</p>
-			<p>Alternatively, use the  <b><a href="#mark_occurrences">Mark
-			Occurrences</a></b> feature to dynamically highlight occurrences.
-			You can search over several files by using the general search
-			features (<b>Search &gt; References</b>).
-			</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Search for methods with
-			a specific return type</b></td>
-			<td valign="top" align="left" width="80%">
-			<p>To search for methods with a specific return type, use &quot;*
-			&lt;return type&gt;&quot; as follows:</p>
-
-			<ul>
-				<li>Open the search dialog and click on the <b>Java Search</b> tab.</li>
-				<li>Type '*' and the return type, separated by a space, in the <b>Search
-				string</b>.</li>
-				<li>Select the <b>Case sensitive</b> checkbox.</li>
-				<li>Select <b>Method</b> and <b>Declarations</b> and then click <b>Search.</b></li>
-			</ul>
-			<p><img src="images/search-returntype.png"  border="0" alt="Search for method with given return type">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Remove Javadoc results from Java search</b></td>
-			<td width="80%" valign="top" align="left">By default <b>Java Search</b> finds references inside
-			Java code and Javadoc. If you don't want to find references inside Javadoc, you can filter these matches by enabling 'Filter Javadoc' in the view menu (triangle symbol) of the search view </td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Trace method call chains
-			with the Call Hierarchy</b></td>
-			<td valign="top" align="left" width="80%">
-			<p>Have you ever found yourself searching for references to methods
-			again and again? Use the new Call Hierarchy to follow long or complex
-			call chains without losing the original context: Just select a method
-			and invoke <b>Navigate &gt; Open Call Hierarchy</b> (Ctrl+Alt+H).</p>
-			<p><img src="images/call_hierarchy.png"  border="0" alt="Call Hierarchy View">
-</p>
-			</td>
-		</tr>
-		
-	</tbody>
-</table>
-<h3><a name="navigation_section"></a>Code navigation and reading</h3>
-
-<table border="1" cellpadding="10" cellspacing="0" width="600"
-	bgcolor="white">
-	<tbody>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Open on a selection in
-			the Java editor</b></td>
-			<td valign="top" align="left" width="80%">There are two ways that you
-			can open an element from its reference in the Java editor.
-			<ul>
-				<li>Select the reference in the code and press <b>F3 (Navigate &gt;
-				Open Declaration)</b></li>
-				<li>Hold <b>Ctrl </b>and move the mouse pointer over the reference</li>
-			</ul>
-			<img src="images/editor-link-style-open.png"  border="0" alt="Hyperlink style navigation">
-<br>
-			The hyperlink style navigation can be configured in <b>Preferences
-			&gt; General &gt; Editors &gt; Text Editors &gt; Support hyperlink style navigation</b>.</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>In-place outlines</b></td>
-			<td valign="top" align="left" width="80%">Press <b>Ctrl+F3</b> in the
-			Java editor to pop up an in-place outline of the element at the
-			current cursor position. Or press <b>Ctrl+O (Navigate &gt; Quick
-			Outline)</b> to pop up an in-place outline of the current source
-			file.
-			<p><img src="images/inplace_outline.png"  border="0" alt="Inplace outline">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>In-place outlines show inherited members</b></td>
-			<td valign="top" align="left" width="80%">Press <b>Ctrl+O</b> or <b>Ctrl+F3</b>
-			 again to add inherited members to an open In-place outline. Inherited members have a gray label.
-			 Filter and sort the outline with the menu in the upper right corner.
-			<p><img src="images/quick-outline-inherited.png"  border="0" alt="Quick outline view"></p>
-            </td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>In-place hierarchy</b></td>
-			<td valign="top" align="left" width="80%">Find out which are the
-			possible receivers of a virtual call using the 'quick hierarchy'.
-			Place the cursor inside the method call and press
-			<b>Ctrl+T (Navigate&nbsp;&gt;&nbsp;Quick Hierarchy)</b>.
-			The view shows all types that implement the method with a full icon.
-			<p><img border="0" src="images/type-hierarchy-structured-view.png"
-				 alt="Quick hierarchy view">
-			</p>
-			<p>Press <b>Ctrl+T</b> again to switch to the Supertype hierarchy.</p></td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Advanced highlighting</b></td>
-			<td align="left" valign="top">
-				The Java editor can highlight source code according to its
-				semantics (for example: static fields, local variables, static method
-				invocations). Have a look at the various options on the <b>Window &gt; Preferences &gt; Java
-				&gt; Editor &gt; Syntax Coloring</b> preference page.<p><img src="images/advanced-highlighting.png"  alt="An example of advanced highlighting." title="Advanced Highlighting" align="middle">
-</p>
-				
-			</td>
-
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Initially folded regions</b></td>
-			<td>You can specify which regions are folded by default when an editor is opened. Have a look ate the <b>Window &gt; Preferences &gt; Java &gt; Editor &gt; Folding</b>
-			preference page to customize this.<p><img src="images/folding-preferences.png"  alt="Folding preference page" title="Folding Preference Page" align="middle">
-</p>
-				</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Mark occurrences</b></td>
-			<td valign="top" align="left" width="80%">
-			<a name="mark_occurrences"></a>When working in the
-			editor, turn on <b>Mark Occurrences</b> in the toolbar (<img src="../images/org.eclipse.jdt.ui/etool16/mark_occurrences.png"  alt="Picture of Mark Occurrences Toolbar Button" title="Picture of Mark Occurrences Toolbar Button">
-) or
-			press <b>Alt+Shift+O</b>. You'll see within a file, where a
-			variable, method or type is referenced.<br>
-			<img border="0" src="images/mark-occurrences.png" alt="Editor with occurrences of 'info' marked"><br>
-			Selecting a return type shows you the method's exit points. Select an
-			exception to see where it is thrown.<br>
-			<img border="0" src="images/mark-return-occurrences.png" alt="Editor with method exits marked"><br>
-			Select a super class or interface to see the methods override or implement a method from the selected super type.<br>
-			Fine tune 'mark occurrences' on <b>Window &gt; Preferences &gt; Java &gt; Editor
-			&gt; Mark Occurrences.</b>.</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Go to next / previous
-			method</b></td>
-			<td valign="top" align="left" width="80%">To quickly navigate to the
-			next or previous method or field, use<br>
-			<b>Ctrl+Shift+Arrow Up (Navigate &gt; Go To &gt; Previous Member</b>)
-			or <b>Ctrl+Shift+Arrow Down (Navigate &gt; Go To &gt; Next Member)</b></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Control your navigation between annotations</b></td>
-			<td>
-			Use the Next / Previous Annotation toolbar buttons or <b>Navigate
-			&gt; Next Annotation</b> (<b>Ctrl+.</b>) and <b>Navigate &gt; Previous
-			Annotation</b> (<b>Ctrl+,</b>) to navigate between annotations
-			in a Java source file.
-			With the button drop-down menus,  you can configure on which annotations you want to stop:
-			<p><img src="images/annotation-navigation.png"  alt="Next/Previous annotation drop-down." title="Next/Previous Annotation Drop-Down" align="middle">
-</p>
-			
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Reminders in your Java
-			code</b></td>
-			<td valign="top" align="left" width="80%">When you tag a comment in
-			Java source code with "TODO" the Java compiler automatically creates
-			a corresponding task as a reminder. Opening the task navigates you
-			back to the "TODO" in the code. Use the <b>Window
-			&gt; Preferences &gt; Java Compiler &gt; Task Tags </b>preference
-			page to configure any other special tags (like "FIXME") that you'd
-			like to track in the task list.<p><img src="images/todo-example.png"  border="0" alt="Task tags in editor and task view">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Tricks in the Open Type dialog</b><br>
-			<img border="0" src="images/3.1_tag.png" alt="New in 3.1">
-			</td>
-			<td valign="top" align="left" width="80%">
-			<ul>
-				<li>To find types quickly, only type the capital letters of the type name: IOOBE finds IndexOutOfBoundsException</li>
-				<li>To see all types ending with a given suffix, e.g. all Tests, use '*Test&lt;' to not see all types containing 'Test' somewhere else in the type
-			name.</li>
-			</ul>
-			<img border="0" src="images/open-type-camel-case.png"
-				 alt="Open type dialog with camel case matching"></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b> Make hovers sticky</b></td>
-			<td valign="top" align="left" width="80%">You can open the text from
-			a hover in a scrollable window by pressing <b>F2 (Edit &gt; Show
-			Tooltip Description)</b>. You can select and copy content from this
-			window.
-			<p><img src="images/editor-hover-window.png"  border="0" alt="Window containing content of the hover">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Hovers in the Java
-			editor</b></td>
-			<td valign="top" align="left" width="80%">You can see different hovers in the
-			Java editor by using the
-			modifier keys (Shift, Ctrl, Alt). <br> 
-			When you move the mouse over an identifier in the Java editor, by
-			default a hover with the Javadoc extracted from the corresponding
-			source of this element is shown. Holding down the Ctrl key shows you
-			the source code.
-			<p><img src="images/editor-code-hover.png"  border="0" alt="Hover showing code of the element in the hover">
-</p>
-			You can change this behavior and define the hovers for other modifier
-			keys in <b>Window &gt; Preferences &gt; Java &gt; Editor &gt; Hovers</b>.</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Generic method inferred signature</b><br>
-			<img border="0" src="images/3.1_tag.png" alt="New in 3.1"></td>
-			<td valign="top" align="left" width="80%">You can use hover to show the generic method inferred signature.
-			<p><img src="images/hovergenericsignature.png" border="0" alt="Hover showing generic method inferred signature">
-			</p></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Open and configure
-			external Javadoc documentation</b></td>
-			<td valign="top" align="left" width="80%">If you want to open the
-			Javadoc documentation for a type, method or field with <b>Shift+F2
-			(Navigate &gt; Open External Javadoc)</b>, you first have to specify
-			the documentation locations to the elements parent library (JAR,
-			class folder) or project (source folder).<br>
-			For libraries open the build path page (<b>Project &gt; Properties
-			&gt; Java Build Path</b>), go to the <b>Libraries</b>, expand the
-			node of the library where you can edit the 'Javadoc location' node.
-			The documentation can be local on your file system in a folder or
-			archive or on a web server.
-			<p><img src="images/javadoc-location.png"  border="0" alt="Configuring Javadoc location in the Java build path dialog">
-</p>
-			For types, methods or fields in source folders, go to the (<b>Project
-			&gt; Properties &gt; Javadoc Location</b>).</td>
-		</tr>
-	</tbody>
-</table>
-<h3><a name="views_section"></a>Java views</h3>
-
-<table border="1" cellpadding="10" cellspacing="0" width="600"
-	bgcolor="white">
-	<tbody>
-		<tr>
-			<td valign="top" align="left">
-			<b>Organizing workspace with many projects</b><br>
-			<img border="0" src="images/3.1_tag.png" alt="New in 3.1">
-			</td>
-			<td>Use <b>Show &gt; Working Sets</b> in the Package Explorer's view menu to enable 
-a new mode that shows working sets as top level elements. This mode makes it 
-much easier to manage workspaces containing lots of projects.
-			<p><img alt="Package Explorer in Working Set mode"
-				src="images/package-explorer.png"></p>
-			<p>Use <b>Select Working Sets</b> from the Package Explorer's view
-			menu to configure which working sets get shown. The dialog lets you
-			create new Java working sets, define which working sets are shown and
-			in what order. Working sets can also be rearranged directly in the
-			Package Explorer using drag and drop and copy/paste.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Declaration view</b></td>
-			<td>The    Declaration view (<b>Window &gt; Show View &gt;
-			Other &gt; Java &gt; Declaration</b>)  shows the source of the
-			element selected in the Java editor or in a Java view.
-			<p><img src="images/DeclarationView.png"  title="Declaration view" alt="Declaration view">
-</p>
-			</td>
-		</tr>
-
-		<tr>
-			<td valign="top" align="left"><b>Javadoc view</b></td>
-			<td>There is a Javadoc view (<b>Window &gt; Show View &gt; Other
-			&gt; Java &gt; Javadoc</b>) which shows the Javadoc of the element
-			selected in the Java editor or in a Java view. The Javadoc view uses
-			the SWT Browser widget to display HTML on platforms which support it.
-			<p><img src="images/JavadocView.png"  title="Javadoc view" alt="Javadoc view">
-</p>
-			</td>
-		</tr><tr>
-			<td width="20%" valign="top" align="left"><b>Type Hierarchy view and method
-			 implementations / definitions</b></td>
-			<td valign="top" align="left" width="80%">To find out 
-			which types in a hierarchy override a method, use the 'Show Members in
-			Hierarchy' feature.
-			<ul>
-				<li>Select the method to look at and press <b>F4 (Navigate &gt; Open
-				Type Hierarchy)</b>. This opens the type hierarchy view on the
-				method's declaring type.</li>
-				<li>With the method selected in the Hierarchy view, press the 'Lock
-				View and Show Members in Hierarchy' tool bar button.</li>
-				<li>The hierarchy view now shows only types that implement or define
-				the 'locked' method. You can for example see that 'isEmpty()' is
-				defined in 'List' and implemented in 'ArrayList' and 'Vector' but
-				not in 'AbstractList'.</li>
-			</ul>
-			<p><img src="images/hierarchy-lockview.png" border="0" alt="Lock view and show members in Hierarchy">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Type hierarchy view
-			supports grouping by defining type</b></td>
-			<td valign="top" align="left" width="80%">The type hierarchy method
-			view lets you sort the selected type's methods by its defining types.
-			For example, for AbstractList you can see that it contains methods
-			that were defined in Object, Collection and List:
-			<p><img src="images/sort-by-def.png"  border="0" alt="Sort members by the defining type in the type hierarchy">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Tricks in the type
-			hierarchy</b></td>
-			<td valign="top" align="left" width="80%">
-			<ul>
-				<li>Focus the type hierarchy on a new type by pressing <b>F4
-				(Navigate &gt; Open Type Hierarchy)</b> on an element or a selected
-				name.</li>
-				<li>You can open the Hierarchy view not only on types but also on
-				packages, source folders, JAR archives and Java projects.</li>
-				<li>You can Drag &amp; Drop an element onto the Hierarchy view to
-				focus it on that element.</li>
-				<li>You can change the orientation (from the default vertical to
-				horizontal) of the Hierarchy view from the view's toolbar menu.</li>
-			</ul>
-			</td>
-		</tr>
-		
-		
-		<tr>
-			<td valign="top" align="left"><b>Structural compare of Java source</b>
-			</td>
-
-			<td valign="top" align="left">A structural comparison of Java source
-			ignores the textual order of Java elements like methods and fields
-			and shows more clearly which elements were changed, added, or removed. <br>
-			For initiating a structural comparison of Java files you have two
-			options:
-			<ul>
-				<li>Select two Java compilation units and choose <b>Compare With</b>
-				&gt; <b>Each Other</b> from the view's context menu. If the files
-				have differences, they are opened into a Compare Editor. The top
-				pane shows the differing Java elements; double clicking on one of
-				them shows the source of the element in the bottom pane.</li>
-				<li>In any context where a file comparison is involved (e.g. a CVS
-				Synchronization) a double click on a Java file not only shows the
-				content of the file in a text compare viewer, but it also performs a
-				structural compare and opens a new pane showing the results.</li>
-			</ul>
-			<p><img src="images/compare-java.png" alt="Structural compare of Java source">
-</p>
-			You can even ignore comments and formatting changes when performing
-			the structural compare: turn on the <strong>Ignore Whitespace</strong>
-			option via the Compare Editor's toolbar button, or the CVS
-			Synchronization View's drop down menu.</td>
-		</tr><tr>
-			<td valign="top" align="left"><b>Structural compare of property
-			files</b></td>
-
-			<td valign="top" align="left">A structural comparison of Java
-			property files (extension: .properties) ignores the textual order of
-			properties and shows which properties were changed, added, or
-			removed. <br>
-			For initiating a structural comparison of property files you have two
-			options:
-			<ul>
-				<li>Select two files in the Package Explorer or Navigator and choose
-				<b>Compare With</b> &gt; <b>Each Other</b> from the view's context
-				menu.</li>
-				<li>In any context where a file comparison is involved (e.g. a CVS
-				Synchronization) a double click on a property file not only shows
-				the content of the file in a text compare viewer, but it also
-				performs a structural compare and opens a new pane showing the
-				results.</li>
-			</ul>
-			<p><img src="images/compare-properties.png" alt="Structural compare of property files">
-</p>
-			</td>
-		</tr><tr>
-			<td width="20%" valign="top" align="left"><b>Hierarchical vs. flat
-			layout of packages</b></td>
-			<td valign="top" align="left" width="80%">An option on the Java
-			Packages view (and Package Explorer view) allows you to change the
-			way packages are displayed. <b>Hierarchical</b> displays packages in
-			a tree, with sub-packages below packages; <b>Flat</b> displays them
-			in the standard arrangement, as a flat list with all packages and
-			sub-packages as siblings.<br>
-			<table border="0">
-				<tbody>
-					<tr align="left" valign="top">
-						<td><img src="images/packages-flat.png" border="0" alt="Flat packages layout">
-</td>
-						<td><img src="images/packages-hierarchical.png" border="0" alt="Hierarchical package layout">
-</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-		</tr><tr>
-			<td width="20%" valign="top" align="left"><b>Logical packages</b></td>
-			<td valign="top" align="left" width="80%">The Java Packages view
-			(Java Browsing perspective) coalesces packages of the same name
-			across source folders within a project. This shows the Packages view
-			containing a logical package.
-			<p><img src="images/packages-compound.png"  border="0" alt="Java browsing perspective containing a logical package" align="bottom">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Compress package names</b></td>
-			<td valign="top" align="left" width="80%">If your package names are
-			very long you can configure a compressed name that appears in the viewers.
-			Configuration of the compression pattern is done in <b> &gt; Window &gt; Preferences
-			&gt; Java &gt; Appearance</b>
-			<p><img src="images/compress-packages1.png"  border="0" alt="Compression pattern configuration in the Java appearance preference page">
-</p>
-			Using this example, packages are rendered the following way:<p><img src="images/compress-packages2.png"  border="0" alt="Compressed package names">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Manipulating the Java
-			build path directly in the package explorer</b><br>
-			<img border="0" src="images/3.1_tag.png" alt="New in 3.1">
-			</td>
-			<td valign="top" align="left" width="80%">Instead of manipulating the Java Build path on <b>Project
-			&gt; Properties &gt; Java Build Path</b>, use the actions in the package explorer's context menu.<br>You can for example add new source folders, archives and libraries to the build path or in- and exclude file and folders from a source folder.<br>
-			<img border="0" src="images/build-path-actions.png" 
-				alt="Build path context menu">
-			</td>
-		</tr>
-	</tbody>
-</table>
-<h3><a name="misc_section"></a>Miscellaneous</h3>
-
-<table border="1" cellpadding="10" cellspacing="0" width="600"
-	bgcolor="white">
-	<tbody>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Project specific
-			preferences<br>
-			<img border="0" src="images/3.1_tag.png" alt="New in 3.1">
-			</b><br></td>
-			<td valign="top" align="left" width="80%">All code style and compiler options  can now be defined  per project.<br>
-			Open the project property pages with <b>Project &gt; Properties</b> on a project or use the link on the workspace preferences (e.g. <b>Window
-			&gt; Preferences &gt; Java &gt; Code Style</b>) to open a project property page and enable project specific settings.<br>
-			<img border="0" src="images/project-specific-settings.png"
-				alt="Project property page with 'Enable project specific settings' checkbox">
-			<br>The project specific settings are stored in a configuration file inside the project (in the '.settings' folder). When you share a project in a team, team members will also get these project specific settings.</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Access Rules</b><br>
-			<img border="0" src="images/3.1_tag.png" alt="New in 3.1">
-			</td>
-			<td valign="top" align="left" width="80%">Access rules give you the possibility to enforce API rules  for  types from referenced libraries. On the Java build path page (<b>Project
-			&gt; Properties &gt; Java Build Path</b>)  edit the 'Access Rules' node available on  referenced projects, archives, class folders and libraries.<br>
-			Packages or types in these references can be classified as:<ul>
-				<li>Accessible</li>
-				<li>Discouraged</li>
-				<li>Forbidden</li>
-			</ul>According to the settings on <b>Window &gt; Preferences &gt; Java &gt; Compiler &gt; Errors/Warnings</b>, the compiler will mark discouraged and forbidden references with warning or errors.<br><img
-				border="0" src="images/type-access-rules.png" alt="Access rules configuration dialog"></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>JUnit</b></td>
-			<td valign="top" align="left" width="80%">Select a JUnit test method
-			in a view and choose <b>Run &gt; JUnit Test</b> from the context menu or <b>Run
-			&gt; Run As &gt; JUnit Test</b> from the main menu. This
-			creates a launch configuration to run the selected test.</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Hide JUnit view until
-			errors or failures occur</b></td>
-
-			<td valign="top" align="left" width="80%">You can make the JUnit view
-			open only when there are errors or failures. That way, you can have
-			the view set as a fast view and never look at it when there are no
-			failing tests. While there are no problems in your tests you will see
-			this icon <img src="../images/org.eclipse.jdt.junit/prgss/ss4.png"  alt="Successfully running"> (the
-			number of small green squares will grow, indicating progress)
-			while running them and this icon <img src="../images/org.eclipse.jdt.junit/eview16/junitsucc.png"  alt="Successfully finished">
- after they are finished. If, however,
-			errors or failures occur, the icon will change to <img src="../images/org.eclipse.jdt.junit/prgss/ff4.png"  alt="Failure or error occurred">
- (or <img src="../images/org.eclipse.jdt.junit/eview16/juniterr.png"  alt="Finished with failure or error">
- if
-			tests are finished) and the JUnit view will appear. This behavior can
-			be configured via the <b>Window &gt;
-			Preferences &gt; Java &gt; JUnit </b>preference page.</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Content assist in dialog fields</b>
-			</td>
-			<td>Content Assist (Ctrl+Space) is now also available in input fields
-			of various Java dialogs. Look for small light bulb icon beside the
-			field when it has focus.
-			<p><img src="images/new-class.png"  alt="New Class Dialog">
-</p>
-			<p>Content Assist is e.g. implemented in the New Java Class, New Java
-			Interface, and New JUnit Test wizards, as well as in the refactoring
-			dialogs for Change Method Signature and moving static members.</p>
-			<p>The Extract Local Variable, Convert Local Variable to Field, and
-			Introduce Parameter refactorings offer content assist proposals for
-			the new element name.</p>
-			</td>
-		</tr>
-		
-
-
-		
-
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Define prefixes or
-			suffixes for fields, parameters and local variables</b></td>
-			<td valign="top" align="left" width="80%">In addition to configuring
-			the prefix or suffix for fields, you can also specify the prefix or
-			suffix for static fields, parameters, and local variables. These
-			settings on the <b>Window &gt;
-			Preferences &gt; Java &gt; Code Style</b> preference page are used
-			in content assist, quick fix, and refactoring whenever a variable
-			name is computed.
-			<p><img src="images/name-conventions.png"  border="0" alt="Name conventions in the code style preference page">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Organize Imports works
-			on more than single files</b></td>
-			<td valign="top" align="left" width="80%">You can invoke Organize
-			Imports on sets of compilation units, packages, source folders or
-			Java projects.</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Format more than one
-			file</b></td>
-			<td valign="top" align="left" width="80%">Select all
-			Java files to format and choose Source &gt; Format to format them
-			all. The format action is also available on packages, source folders
-			or Java projects.</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use project specific
-			compiler settings</b></td>
-			<td valign="top" align="left" width="80%">Each project can 
-			use the global compiler settings or you can define project specific
-			settings. Select the project and open the Java compiler page in the
-			project properties <b>(Project &gt; Properties &gt; Java Compiler)</b><p><img src="images/compiler-projectspecific.png"  border="0" alt="Project specific Java compiler settings">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use a specific JRE for
-			a project</b></td>
-			<td valign="top" align="left" width="80%">When creating new projects the JRE that 
-			is added by default is the one selected in <b>Window &gt; Preferences &gt; Java
-			&gt; Installed JRE's.</b> To set a project specific JRE, open the
-			project's Java Build path property page <b>(Project &gt; Properties
-			&gt; Java Build Path)</b>, then the<b> Libraries</b> page, select
-			'JRE System Library' and press <b>Edit</b>. In the 'Edit Library'
-			dialog you can select either the default JRE or a project specific
-			JRE to add to new projects.
-			<p><img src="images/project-specific-jre.png"  alt="Edit JRE system library" border="0">
-</p>
-			</td>
-		</tr>
-		
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Propagating deprecation
-			tag</b></td>
-			<td width="80%" valign="top" align="left">
-			The Java compiler can be configured to diagnose deprecation using 
-			options on the <b>Window &gt; Preferences &gt; Java &gt; Compiler &gt; Advanced</b> page.
-			<p><img src="images/warn-deprecation-opt.png"  border="0" alt="Compiler preference page">
-</p>
-			Using this configuration, the result is:
-			<p><img src="images/warn-deprecation-i.png"  border="0" alt="I.java"></p>
-			<p><img src="images/warn-deprecation-x.png"  border="0" alt="X.java"></p>
-			<p><img src="images/warn-deprecation-y.png"  border="0" alt="Y.java"></p>
-			If you're unable to fix a usage of a deprecated construct, we recommend that you
-			tag the enclosing method, field or type as deprecated.
-			This way, you acknowledge that you did override a deprecated construct,
-			 and the deprecation flag is propagated to further dependents.
-			<p><img src="images/warn-deprecation-x2.png"  border="0" alt="X.java"></p>
-			<p><img src="images/warn-deprecation-y2.png"  border="0" alt="Y.java"></p></td>
-		</tr>
-		
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Recovering from abnormal
-			inconsistencies</b></td>
-			<td width="80%" valign="top" align="left">
-			In the rare event of a dysfunction, JDT could reveal some inconsistencies
-			such as:
-			<ul>
-				<li>missing results in a <b>Java Search</b> or <b>Open Type</b></li>
-				<li>invalid items in package explorer</li>
-			</ul>
-			<br>
-			To make it consistent again, the following actions need to be performed
-			in this exact order:
-			<ol>
-			<li>Close all projects using navigator <b>Close Project</b> menu action</li>
-			<li>Exit and restart Eclipse</li>
-			<li>Open all projects using navigator <b>Open Project</b> menu action</li>
-			<li>Manually trigger a clean build of entire workspace (<b>Project &gt;
-			 Clean...</b>)</li>
-			</ol>
-			</td>
-		</tr>
-	</tbody>
-</table>
-
-<h3><a name="debugging_section"></a>Debugging</h3>
-
-<table border="1" cellpadding="10" cellspacing="0" width="600"
-	bgcolor="white">
-	<tbody>
-		<tr>
-			<td width="20%" valign="top" align="left">
-      <p><b>Launching from the Context Menu</b></p>
-    </td>
-			<td width="80%" valign="top" align="left">
-			<p>You can run and debug Java applications from the context menu.
-			You can launch a source file, package, method, type, etc. by
-			choosing <b>Run As</b> (or <b>Debug As</b>)<b> &gt; Java Application</b>
-			from the context menu in a view or editor. Alternatively, you can
-			use the Java application launch shortcut key binding (Alt-Shift-D, J). The
-			top level <b>Run As</b> (or <b>Debug As</b>) actions are also
-			sensitive to the current selection or active editor.</p>
-			<p><img src="images/org.eclipse.jdt.debug.ui/context_menu_launch.png"  alt="Context menu with launch option">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Evaluations in the
-			debugger</b></td>
-			<td width="80%" valign="top" align="left">
-			<p>Snippet evaluation is available from a number of places in the
-			debugger. Choosing <b>Display</b> or <b>Inspect</b> from the context
-			menu of the editor or <b>Variables view</b> will show the result in a
-			pop-up whose result can be sent to the <b>Display</b> or <b>Expressions
-			views</b>.</p>
-			<p><img src="images/org.eclipse.jdt.debug.ui/inspect_popup.png"  alt="Result of an inspect in a pop-up">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left">
-      <p><b>View Management in Non-Debug perspectives</b></p>
-    </td>
-			<td width="80%" valign="top" align="left">
-			
-      <p>The Debug view automatically manages debug related views based on the view selection 
-        (displaying Java views for Java stack frames and C views for C stack frames, 
-        for example). By default, this automatic view management only occurs in 
-        the Debug perspective, but you can enable it for other perspectives via 
-        the <b>View Management</b> preference page available from the <b>Debug 
-        view</b> toolbar pulldown.</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left">
-      <p><b>Environment Variables</b></p>
-    </td>
-			<td width="80%" valign="top" align="left">
-			
-      <p>You can now specify the environment used to launch Java applications 
-        via the <b>Environment</b> tab.</p>
-			<p><img src="images/org.eclipse.jdt.debug.ui/env_tab.png"  alt="Environment tab in the launch configuration dialog">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left">
-      <p><b>String Substitutions</b></p>
-    </td>
-			<td width="80%" valign="top" align="left">
-			
-      <p>Variables are now supported for many parameters of Java Application launch 
-        configurations. Most fields that support variables have a <b>Variables...</b> 
-        button next to them, such as the program and VM arguments fields. The <b>Main Type</b> field
-        supports variables as 
-        well; the <i>${java_type_name}</i> variable allows you to create a configuration 
-        that will run the selected type.</p>
-		<p><img src="images/org.eclipse.jdt.debug.ui/args_tab.png"  alt="Arguments tab in the launch configuration dialog">
-		</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left">
-      <p><b>Logical Structures</b></p>
-    </td>
-			<td width="80%" valign="top" align="left">
-			
-      <p>The <b>Logical Structures</b> toggle on the <b>Variables view</b> toolbar 
-        presents alternate structures for common types. JDT provides logical views 
-        for Maps, Collections, and SWT Composites. You can define
-        logical structures for other types from the <b>Logical Structures</b>
-        preference page.</p>
-			<p><img src="images/org.eclipse.jdt.debug.ui/logical_structure_toggle.png"  alt="Vector displayed as a logical structure in the variable view">
-</p>
-			</td>
-			
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left">
-      <p><b>Default VM Arguments</b></p>
-    </td>
-			<td width="80%" valign="top" align="left">
-			<p>If you specify the same arguments to a certain VM frequently,
-			you can configure <b>Default VM Arguments</b> in the <b>Installed JREs</b>
-			preference page. This is more convenient than specifying them for
-			each launch configuration.</p>
-			<p><img src="images/org.eclipse.jdt.debug.ui/def_vm_args.png"  alt="JRE preference page with default argument specified">
-</p>
-			</td>
-			
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Stop in Main</b></td>
-			<td width="80%" valign="top" align="left">
-			<p>You can use <b>Stop in main </b>in a Java Application launch
-			configuration to cause your program to stop at the first executable
-			line of the main method when you run it under debug mode.</p>
-
-			<p><img src="images/org.eclipse.jdt.debug.ui/stop_in_main.png"  alt="Main tab with Stop in Main option selected">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Conditional breakpoints</b></td>
-			<td valign="top" align="left">You can use conditional breakpoints in
-			<b> Breakpoint Properties... </b>to control when a breakpoint
-			actually halts execution. You can specify whether you want the
-			breakpoint to suspend execution only when the condition is true, or
-			when the condition value changes.
-			<p><img src="images/org.eclipse.jdt.debug.ui/breakpoint_condition.png"  alt="Breakpoint condition editor in breakpoint properties dialog"></p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Disabling breakpoints</b></td>
-			<td valign="top" align="left">
-			<p>If you find yourself frequently adding and removing a breakpoint
-			in the same place, consider disabling the breakpoint when you don't
-			need it and enabling it when needed again. This can be done using <b>Disable
-			Breakpoint </b>in the breakpoint context menu or by unchecking the
-			breakpoint in the <b>Breakpoints view</b>.</p>
-			<p>You can also temporarily disable all breakpoints using the <b>Skip
-			All Breakpoints</b> action in the <b>Breakpoints view</b> toolbar.
-			This will tell the debugger to skip all breakpoints while maintaining
-			their current enabled state.</p>
-			<p><img src="images/org.eclipse.jdt.debug.ui/breakpoint_menu.png"  alt="Disable Breakpoint action in the ruler context menu">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Changing variable values</b></td>
-			<td valign="top" align="left">
-			
-      <p>When a thread is suspended in the debugger, you can change the values 
-        of Java primitives and Strings in the <b>Variables</b> view. From the 
-        variable's context menu, choose <b>Change Variable Value</b>. You can 
-        also change the value by typing a new value into the Details pane and 
-        using the <strong>Assign Value </strong>action in the context menu (CTRL-S 
-        key binding).</p>
-
-			<p><img src="images/org.eclipse.jdt.debug.ui/assign_value.png"  alt="Change variable value from detail pane">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Variable values in hover help</b></td>
-			<td valign="top" align="left">When a thread is suspended and the
-			cursor is placed over a variable in the Java editor, the value of
-			that variable is displayed as hover help.
-			<p><img src="images/org.eclipse.jdt.debug.ui/variable_hover.png"  alt="Variable value hover in the editor">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Drop to Frame</b></td>
-			<td valign="top" align="left">
-			<p>When stepping through your code, you might occasionally step too
-			far, or step over a line you meant to step into. Rather than
-			restarting your debug session, you can use the <b>Drop to Frame</b>
-			action to quickly go back to the beginning of a method. Select the
-			stack frame corresponding to the Java method you wish to restart, and
-			select <b>Drop to Frame</b> from <b>Debug view</b> toolbar or the
-			stack frame's context menu. The current instruction pointer will be
-			reset to the first executable statement in the method. This works for
-			non-top stack frames as well.</p>
-			<p>Note that Drop to frame is only available when debugging with a
-			1.4 or higher VM, or the J9 VM. There are some situations where a JVM
-			may be unable to pop the desired frames from the stack. For example,
-			it is generally impossible to drop to the bottom frame of the stack
-			or to any frame below a native method.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Hot code replace</b></td>
-			
-    <td valign="top" align="left">The debugger supports Hot Code Replace when 
-      debugging with a 1.4 or higher VM, or the J9 VM. This lets you make changes 
-      to code you are currently debugging. Note that some changes such as new 
-      or deleted methods, class variables or inner classes cannot be hot swapped, 
-      depending on the support provided by a particular VM.</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Stepping into selections</b></td>
-			<td valign="top" align="left">
-			<p>The Java debugger allows you to step into a single method within a
-			series of chained or nested method calls. Simply highlight the method
-			you wish to step into and select <b>Step into Selection</b> from the
-			Java editor context menu.</p>
-			<p>This feature works in places other than the currently executing
-			line. Try debugging to a breakpoint and stepping into a method a few
-			lines below the currently instruction pointer.</p>
-
-			<p><img src="images/org.eclipse.jdt.debug.ui/step_into_selection.png"
-				alt="Stepping into selection"></p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Controlling<br>
-			your console</b></td>
-
-			
-    <td valign="top" align="left">Output displayed in the console can be locked 
-      to a specific process via the <strong>Pin Console</strong> action in the 
-      Console view toolbar. There's also a <strong>Scroll Lock </strong>action 
-      that stops the console from automatically scrolling as new output is appended. 
-      <p><img src="images/org.eclipse.jdt.debug.ui/pin_console.png"  alt="Console view with process drop-down">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Creating watch items</b></td>
-			
-    <td valign="top" align="left">A watch item is an expression in the <b>Expressions</b> 
-      view whose value is updated as you debug. You can create watch items from 
-      the Java editor by selecting an expression or variable and choosing <b>Watch</b> 
-      from its context menu or the top-level <b>Run</b> menu.</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Watch points</b></td>
-			<td valign="top" align="left">
-			
-      <p>A watch point is a breakpoint that suspends execution whenever a specified 
-        variable is accessed or modified. To set a watchpoint, select a variable 
-        in the Outline view and choose <b>Toggle Watchpoint</b> from its context 
-        menu. To configure a watchpoint, select the watchpoint in the <b>Breakpoints</b> 
-        view and choose <b>Properties...</b> from its context menu. The most important 
-        properties for this type of breakpoint are the <b>Access</b> and <b>Modification</b> 
-        checkboxes which control when the breakpoint can suspend execution.</p>
-			<p><img src="images/org.eclipse.jdt.debug.ui/watchpoint_properties.png"  alt="Breakpoint properties dialog">
-</p>
-			</td>
-		</tr>
-		<tr>
-
-			<td valign="top" align="left"><b>Threads and Monitors</b></td>
-			<td valign="top" align="left">
-			<p>The Java debugger optionally displays monitor information
-			in the <b>Debug</b> view. Use the <b>Show Monitors</b> action in the
-			Debug view drop down menu to show which	threads are holding locks and
-			which are waiting to acquire locks. Threads involved in a deadlock
-			are rendered in red.</p>
-			<p><img src="images/org.eclipse.jdt.debug.ui/deadlock.png"
-				alt="Debug view showing deadlock cycles"></p>
-
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Step filters</b></td>
-			
-    <td valign="top" align="left">Step filters prevent the debugger from suspending 
-      in specified classes and packages when stepping into code. Step filters 
-      are established in <b> Window &gt; Preferences &gt; Java &gt; Debug &gt; 
-      Step Filtering</b>. When the <b>Use Step Filters</b> toggle (on the debug 
-      toolbar and menu) is on, step filters are applied to all step actions. In 
-      the Debug view, the selected stack frame's package or declaring type can 
-      be quickly added to the list of filters by selecting <b>Filter Type</b> 
-      or <b>Filter Package</b> from the stack frame's context menu.</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Using the scrapbook</b></td>
-			<td valign="top" align="left">
-			
-      <p>If you want to experiment with API or test out a new algorithm, it's 
-        frequently easier to use a Java scrapbook page than create a new class. 
-        A scrapbook page is a container for random snippets of code that you can 
-        execute at any time without a context. To create a scrapbook page, create 
-        a new file with a <strong>.jpage</strong> extension (or use the <strong>New</strong> 
-        wizard - <strong>Java &gt; Java Run/Debug &gt; Scrapbook Page</strong>). 
-        Enter whatever code you wish to execute, then select it. There are three 
-        ways to execute your code:</p>
-
-			<ul>
-				<li>Execute the selected code and place the returned result in the
-				Expressions view</li>
-				<li>Execute the selected code and place the String result right in
-				the scrapbook page
-				<p><img src="images/org.eclipse.jdt.debug.ui/scrapbook.png"  alt="Scrapbook page displaying result">
-</p>
-				</li>
-				<li>Execute the selected code (and ignore any returned result)</li>
-			</ul>
-			<p>These actions are in the workbench toolbar and also in the
-			scrapbook page's context menu.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Editing<br>
-			launch<br>
-			configurations</b></td>
-			<td valign="top" align="left">Holding down the <b>Ctrl</b> key and
-			making a selection from the <b>Run</b> or <b>Debug</b> drop-down menu
-			opens the associated launch configuration for editing. The launch
-			configuration can also be opened from the context menu associated
-			with any item in the Debug view.</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Favorite launch configurations</b></td>
-			<td valign="top" align="left">
-			
-      <p>Launch configurations appear in the Run/Debug drop-down menus in most 
-        recently launched order. However it is possible to force a launch configuration 
-        to always appear at the top of the drop-downs by making the configuration 
-        a 'favorite'. Use the <strong>Organize Favorites...</strong> action from 
-        the appropriate drop down menu to configure your favorite launch configurations.</p>
-
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Detail formatters</b></td>
-			<td valign="top" align="left">
-			<p>In the <b>Variables</b> &amp; <b>Expressions</b> views, the detail
-			pane shows an expanded representation of the currently selected
-			variable. By default, this expanded representation is the result of
-			calling <b>toString()</b> on the selected object, but you can create
-			a custom detail formatter that will be used instead by choosing <b>New
-			Detail Formatter</b> from the variable's context menu. This detail
-			formatter will be used for all objects of the same type. You can view
-			and edit all detail formatters in the <b>Window &gt; Preferences &gt; Java &gt; Debug &gt; Detail
-			Formatters</b> preference page.</p>
-			<p><img src="images/org.eclipse.jdt.debug.ui/detail_formatter.png"  alt="Detail formatter dialog">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Running code with compile errors</b></td>
-			<td valign="top" align="left">
-			<p>You can run and debug code that did not compile cleanly. The only
-			difference between running code with and without compile errors is
-			that if a line of code with a compile error is executed, one of two
-			things will happen:</p>
-			<ul>
-				<li>If the 'Suspend execution on compilation errors' preference on
-				the <b>Window &gt; Preferences &gt; Java &gt; Debug</b> preference page is set and you are
-				debugging, the debug session will suspend as if a breakpoint had
-				been hit. Note that if your VM supports Hot Code Replace, you could
-				then fix the compilation error and resume debugging</li>
-				<li>Otherwise, execution will terminate with a 'unresolved
-				compilation' error</li>
-			</ul>
-			<p>It is important to emphasize that as long as your execution path
-			avoids lines of code with compile errors, you can run and debug just
-			as you normally do.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Word wrap in Variables view</b></td>
-			<td valign="top" align="left">The details area of the debugger's <b>Variables</b>
-			and <b>Expressions</b> views supports word wrap, available from the
-			view drop-down menu.
-			<p><img src="images/org.eclipse.jdt.debug.ui/word_wrap.png"  alt="Word wrap action in Variables view drop-down menu">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Code assist in the debugger</b></td>
-			<td valign="top" align="left">
-			<p>Code assist is available in many contexts beyond writing code in
-			the Java editor:</p>
-			<ul>
-				<li>When entering a <b>breakpoint condition</b></li>
-				<li>In the <b>Details</b> pane of the <b>Variables</b> &amp; <b>Expressions</b> view</li>
-				<li>When entering a <b>Detail Formatter</b> code snippet</li>
-				<li>When entering a <b>Logical Structure</b> code snippet</li>
-				<li>When entering code in a <b>Scrapbook</b> page</li>
-				<li>In the <b>Display</b> view</li>
-			</ul>
-			<p><img src="images/org.eclipse.jdt.debug.ui/code_assist.png"  alt="Display view code assist pop-up">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Command line details</b></td>
-
-			<td valign="top" align="left">You can always see the exact command
-			line used to launch a program in run or debug mode by selecting <b>Properties</b>
-			from the context menu of a process or debug target, even if the
-			launch has terminated.
-			<p><img src="images/org.eclipse.jdt.debug.ui/process_properties.png"  alt="Command line details"></p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Stack trace<br>
-			hyperlinks</b></td>
-			<td valign="top" align="left">
-			
-      <p>Java stack traces in the console appear with hyperlinks. When you place 
-        the mouse over a line in a stack trace the pointer changes to the hand.
-        Pressing the mouse button opens the 
-        associated Java source file and positions the cursor at the corresponding 
-        line. Pressing the mouse button on the exception name at the top of the 
-        stack trace will create an exception breakpoint.</p>
-			<p><img src="images/org.eclipse.jdt.debug.ui/stack_trace.png"  alt="Stack traces in Console view with hyperlinks">
-</p>
-			</td>
-		</tr>
-	</tbody>
-</table>
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/toc.xml b/bundles/org.eclipse.jdt.doc.user/toc.xml
deleted file mode 100644
index c815bc7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/toc.xml
+++ /dev/null

@@ -1,27 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define the top level topics                                                   -->
-<!-- ============================================================================= -->
-
-<toc label="Java Development User Guide">
-	<topic label="Getting Started">
-		<link toc="topics_GettingStarted.xml" />
-	</topic>
-	<anchor id="jdt_getstart" />
-	<topic label="Concepts">
-		<link toc="topics_Concepts.xml" />
-	</topic>
-	<anchor id="jdt_concepts" />
-	<topic label="Tasks">
-		<link toc="topics_Tasks.xml" />
-	</topic>
-	<topic label="Reference">
-		<link toc="topics_Reference.xml" />
-	</topic>
-	<anchor id="jdt_reference" />
-	
-	<topic label="Tips and tricks" href="tips/jdt_tips.html"/>
-	<topic label="What's new" href="whatsNew/jdt_whatsnew.html"/>
-	<topic label="Legal" href="notices.html"/>
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.user/topics_Concepts.xml b/bundles/org.eclipse.jdt.doc.user/topics_Concepts.xml
deleted file mode 100644
index 9c4c1cb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/topics_Concepts.xml
+++ /dev/null

@@ -1,49 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ========================== -->
-<!-- Define topics for the Concepts -->
-<!-- ========================== -->
-<toc label="Concepts" href="concepts/concepts-1.htm" >
-   <!-- <topic label="Overview" href="concepts/concepts-1.htm"/> -->
-   <topic label="Java projects" href="concepts/concepts-3.htm"/>
-   <anchor id="c_javaprojects" />
-   <topic label="Java builder" href="concepts/concepts-4.htm"/>
-   <anchor id="c_javabuilder" />
-   <topic label="Java perspectives" href="concepts/concepts-5.htm"/>
-   <anchor id="c_javaperspective" />
-   <topic label="Java views" href="concepts/concepts-6.htm"/>
-   <anchor id="c_javaviews" />
-   <topic label="Java editor" href="concepts/concepts-7.htm"/>
-   <anchor id="c_javaeditor" />
-   <topic label="Quick Fix" href="concepts/cquickfix.htm"/>
-   <anchor id="c_quickfix" />   
-   <topic label="Quick Assist" href="concepts/cquickassists.htm"/>
-   <anchor id="c_quickassist" />   
-   <topic label="Templates" href="concepts/ctemplates.htm" />
-   <anchor id="ctemplates" />
-   <topic label="Java search" href="concepts/concepts-8.htm"/>
-   <anchor id="c_javasearch" />
-   <topic label="Refactoring support" href="concepts/concepts-9.htm"/>
-   <anchor id="c_refactoring" />
-   <topic label="Build classpath" href="concepts/cbuildcp.htm" />
-   <anchor id="c_buildclasspath" />
-   <topic label="Exclusion and inclusion filters" href="concepts/filters.htm" />
-   <anchor id="c_filters" />
-   <topic label="Access rules" href="concepts/rules.htm" />
-   <anchor id="c_restrict" />
-   <topic label="Classpath variables" href="concepts/cclsspthv.htm" />
-   <anchor id="c_classpathvariables" />
-   <topic label="Debugger" href="concepts/concepts-10.htm"/>
-   <anchor id="c_debugger" />
-   <topic label="Scrapbook" href="concepts/concepts-11.htm"/>
-   <anchor id="c_scrapbook" />
-   <topic label="Local debugging" href="concepts/clocdbug.htm" />
-   <anchor id="c_localdebug" />
-   <topic label="Remote debugging" href="concepts/cremdbug.htm" />
-   <anchor id="c_remotedebug" />
-   <topic label="Breakpoints" href="concepts/cbrkpnts.htm" />
-   <anchor id="c_breakpoints" />
-   <topic label="String externalization" href="concepts/cnls.htm" />
-   <anchor id="c_nls" />
-  
-</toc>

diff --git a/bundles/org.eclipse.jdt.doc.user/topics_GettingStarted.xml b/bundles/org.eclipse.jdt.doc.user/topics_GettingStarted.xml
deleted file mode 100644
index 93564f1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/topics_GettingStarted.xml
+++ /dev/null

@@ -1,55 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ========================== -->
-<!-- Define topics for the GettingStarted -->
-<!-- ========================== -->
-<toc label="GettingStarted" extradir="gettingStarted/intro">
-   <topic label="Basic tutorial" href="gettingStarted/qs-BasicTutorial.htm"> 
-	   <topic label="Preparing the workbench" href="gettingStarted/qs-2.htm"/>
-	   <topic label="Creating your first Java project" href="gettingStarted/qs-3.htm"/>
-	   <topic label="Browsing Java elements using the package explorer" href="gettingStarted/qs-4.htm"/>
-	   <topic label="Editing Java elements"> 
-		   <topic label="Opening a Java editor" href="gettingStarted/qs-OpenJavaEditor.htm"/>
-		   <topic label="Adding new methods" href="gettingStarted/qs-AddMethod.htm"/>
-		   <topic label="Using content assist" href="gettingStarted/qs-ContentAssist.htm"/>
-		   <topic label="Identifying problems in your code" href="gettingStarted/qs-7.htm"/>
-		   <topic label="Using code templates" href="gettingStarted/qs-EditorTemplates.htm"/>
-		   <topic label="Organizing import statements" href="gettingStarted/qs-OrganizeImports.htm"/>
-		   <topic label="Using the local history" href="gettingStarted/qs-LocalHistory.htm"/>
-		   <topic label="Extracting a new method" href="gettingStarted/qs-ExtractMethod.htm"/>
-	   </topic>
-	   
-	   <topic label="Creating a Java class" href="gettingStarted/qs-9.htm"/>
-	   <topic label="Renaming Java elements" href="gettingStarted/qs-8.htm"/>
-	   <topic label="Moving and copying Java elements" href="gettingStarted/qs-10.htm"/>
-	   
-	   <topic label="Navigate to a Java element's declaration" href="gettingStarted/qs-Navigate.htm"/>
-	   <topic label="Viewing the type Hierarchy" href="gettingStarted/qs-6.htm"/>
-	   
-	   <topic label="Searching the workbench" href="gettingStarted/qs-11.htm"/>
-	   
-	   <topic label="Running your programs" href="gettingStarted/qs-12.htm"/>
-	   <topic label="Debugging your programs" href="gettingStarted/qs-13.htm"/>
-	   <topic label="Evaluating expressions" href="gettingStarted/qs-14.htm"/>
-	   <topic label="Evaluating snippets" href="gettingStarted/qs-15.htm"/>
-	   
-	   <topic label="Using the Java browsing perspective" href="gettingStarted/qs-Browsing.htm"/>
-	   
-	   <topic label="Writing and running JUnit tests" href="gettingStarted/qs-junit.htm"/>
-   </topic>
-   
-   <topic label="Project configuration tutorial" href="gettingStarted/qs-ProjectConfiguration.htm">
-	   <topic label="Detecting existing layout" href="gettingStarted/qs-DetectingExistingLayout.htm"/>
-	   <topic label="Organizing sources" href="gettingStarted/qs-OrganizingSources.htm"/>
-	   <topic label="Sibling products in a common source tree" href="gettingStarted/qs-WorkingWithExistingLayout1.htm"/>
-	   <topic label="Overlapping products in a common source tree" href="gettingStarted/qs-WorkingWithExistingLayout2.htm"/>
-	   <topic label="Product with nested tests" href="gettingStarted/qs-WorkingWithExistingLayout3.htm"/>
-	   <topic label="Products sharing a common source framework" href="gettingStarted/qs-WorkingWithExistingLayout4.htm"/>
-	   <topic label="Product nesting resources in output directory" href="gettingStarted/qs-WorkingWithExistingLayout5.htm"/>
-	   <topic label="Project using a source framework with restricted access" href="gettingStarted/qs-WorkingWithExistingLayout6.htm"/>
-   </topic>
-
-   <topic label="Eclipse and J2SE 5.0" href="gettingStarted/qs-with-j2se50.htm">
-   </topic>
-   <anchor id="javagetstart" />
-</toc>

diff --git a/bundles/org.eclipse.jdt.doc.user/topics_Reference.xml b/bundles/org.eclipse.jdt.doc.user/topics_Reference.xml
deleted file mode 100644
index b2d2fbd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/topics_Reference.xml
+++ /dev/null

@@ -1,230 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ========================== -->
-<!-- Define topics for the Reference -->
-<!-- ========================== -->
-<toc label="Reference">
-
-	<topic label="Java Development Toolkit (JDT) Basics">
-		<topic label="JDT Actions" href="reference/ref-2.htm">
-			<topic label="File Actions" href="reference/ref-menu-file.htm" />
-			<topic label="Edit Actions" href="reference/ref-menu-edit.htm" />
-			<topic label="Source Actions" href="reference/ref-menu-source.htm" />
-			<topic label="Refactor Actions" href="reference/ref-menu-refactor.htm" />
-			<topic label="Navigate Actions" href="reference/ref-menu-navigate.htm" />
-			<topic label="Search Actions" href="reference/ref-menu-search.htm" />
-			<topic label="Project Actions" href="reference/ref-menu-project.htm" />
-			<topic label="Run Actions" href="reference/ref-149.htm"/>
-			<topic label="Java Toolbar Actions" href="reference/ref-3.htm"/>
-			<topic label="Java editor" href="reference/ref-java-editor.htm" />
-			<topic label="Run and Debug Actions" href="reference/ref-4.htm" />
-		</topic>
-		<!--<topic label="JDT Perspectives" href="reference/ref-6.htm">
-			<topic label="Java" href="reference/ref-7.htm" />
-			<topic label="Java Type Hierarchy" href="reference/ref-8.htm" />
-			<topic label="Debug" href="reference/ref-9.htm" />
-		</topic> -->
-	</topic>
-	<anchor id="r_jdtbasics" />
-	
-
-	<topic label="Views and editors" href="reference/ref-24.htm">
-		<topic label="Java Editor" href="reference/ref-java-editor.htm">
-			<topic label="Java Content Assist" href="reference/ref-143.htm" />
-			<topic label="Quick fix" href="reference/ref-java-editor-quickfix.htm" />
-		</topic>
-		<anchor id="r_javaeditor" />
-		<topic label="Java Scrapbook Page" href="reference/ref-34.htm" />
-		<anchor id="r_scrapbook" />
-		<topic label="Breakpoints View" href="reference/ref-35.htm">
-			<topic label="Go to File for Breakpoint" href="reference/ref-38.htm" />
-			<topic label="Add Java Exception Breakpoint" href="reference/ref-40.htm" />
-			<topic label="Suspend Policy" href="reference/brkSuspendPolicy.htm" />
-			<topic label="Hit Count" href="reference/ref-43.htm" />
-			<topic label="Uncaught" href="reference/ref-41.htm" />
-			<topic label="Caught" href="reference/ref-42.htm" />
-			<topic label="Modification" href="reference/brkMod.htm" />
-			<topic label="Access" href="reference/brkAccess.htm" />
-			<topic label="Exit" href="reference/brkExit.htm" />
-			<topic label="Entry" href="reference/brkEntry.htm" />
-			<topic label="Select All" href="reference/brkSelectAll.htm" />
-			<topic label="Enable" href="reference/ref-44.htm" />
-			<topic label="Disable" href="reference/ref-44a.htm" />
-			<topic label="Remove Selected Breakpoints" href="reference/ref-36.htm" />
-			<topic label="Remove All Breakpoints" href="reference/ref-37.htm" />
-		    <topic label="Show Qualified Names in Breakpoints View" href="reference/ref-39.htm" /> 
-		    <topic label="Show Supported Breakpoints" href="reference/brkShowSupported.htm" /> 
-		    <topic label="Breakpoint Properties" href="reference/brkProperties.htm" /> 
-		</topic>
-		<anchor id="r_breakpointsview" />
-		<topic label="Console View" href="reference/ref-45.htm">
-			<topic label="Copy" href="reference/ref-47.htm"/>
-			<topic label="Select All" href="reference/ref-48.htm"/>
-			<topic label="Find/Replace" href="reference/ref-49.htm"/>
-			<topic label="Go To Line" href="reference/ref-50.htm"/>
-			<topic label="Clear the Console" href="reference/ref-46.htm"/>
-			<topic label="Terminate" href="reference/ref-45b.htm"/>
-		</topic>
-		<anchor id="r_consoleview" />
-		<topic label="Debug View" href="reference/ref-51.htm">
-		</topic>
-		<anchor id="r_debugview" />
-		<topic label="Display View" href="reference/ref-52.htm">
-			<topic label="Evaluating Expressions" href="tasks/tasks-138.htm"/>
-			<topic label="Inspect" href="reference/ref-55.htm"/>
-			<topic label="Display" href="reference/ref-54.htm"/>
-		   	<topic label="Clear" href="reference/ref-53.htm"/>
-		</topic>
-		<anchor id="r_displayview" />
-		<topic label="Expressions View" href="reference/ref-56.htm">
-			<topic label="Select All in the Expressions View" href="reference/ref-56a.htm"/>
-			<topic label="Copy Variables in the Expressions View" href="reference/ref-56b.htm"/>
-			<topic label="Remove Selected Expressions" href="reference/ref-59.htm" />
-		    <topic label="Remove All Expressions" href="reference/ref-60.htm" />
-		    <topic label="Change Variable Values in the Expressions View" href="reference/ref-65.htm" /> 
-		    <topic label="Show Constants in the Expressions View" href="reference/ref-63.htm" />
-		    <topic label="Show Static Fields in the Expressions View" href="reference/ref-62.htm" />
-		    <topic label="Show Qualified Names in the Expressions View" href="reference/ref-58.htm" />
-			<topic label="Show Type Names in the Expressions View" href="reference/ref-57.htm" /> 
-		    <topic label="Show Detail Pane for the Expressions View" href="reference/ref-56c.htm" /> 
-		    <topic label="Add/Remove Watchpoint" href="reference/ref-56d.htm" /> 
-		    <topic label="Inspect" href="reference/ref-64.htm" /> 
-		    <topic label="Open Declared Type" href="reference/ref-56e.htm" /> 
-			<topic label="Show Type Names" href="reference/ref-57.htm"/>
-		</topic>
-		<anchor id="r_expressionsview" />
-		
-		<topic label="Variables View" href="reference/ref-74.htm">	
-			<topic label="Inspecting Values" href="tasks/tasks-137.htm"/>
-	      	<topic label="Show Qualified Names in Variables View" href="reference/ref-76.htm" />
-    	  	<topic label="Show Type Names in Variables View" href="reference/ref-75.htm" />
-      		<topic label="Show Detail Pane in Variables View" href="reference/ref-showdetailpane.htm" />
-      		<topic label="Add/Remove Watchpoint" href="reference/ref-74a.htm" />
-	      	<topic label="Show Static Fields in Variables View" href="reference/ref-62.htm" />
-    	  	<topic label="Show Constants in Variables View" href="reference/ref-63.htm" />
-      		<topic label="Change Variable Values in the Variables View" href="reference/ref-81.htm" /> 
-	      	<topic label="Inspect in the Variables View" href="reference/ref-80.htm" /> 
-		</topic>
-		<anchor id="r_variablesview" />
-		
-		<topic label="Type Hierarchy view" href="reference/ref-type-hierarchy.htm" />
-
-		<topic label="Package Explorer view" href="reference/ref-view-package-explorer.htm">
-            <topic label="Java Element Filters dialog" href="reference/ref-dialog-java-element-filters.htm" />
-        </topic>
-
-		<topic label="Java Outline view" href="reference/ref-view-outline.htm" />
-	</topic>
-	
-	<topic label="Menus">
-		<topic label="File Menu" href="reference/ref-menu-file.htm" />
-		<topic label="Edit Menu" href="reference/ref-menu-edit.htm" />
-		<topic label="Source Menu" href="reference/ref-menu-source.htm" />
-		<topic label="Refactor Menu" href="reference/ref-menu-refactor.htm" />
-		<topic label="Navigate Menu" href="reference/ref-menu-navigate.htm" />
-		<topic label="Search Menu" href="reference/ref-menu-search.htm" />
-		<topic label="Project Menu" href="reference/ref-menu-project.htm" />
-		<topic label="Run Menu" href="reference/ref-149.htm">
-			<topic label="Step Commands" href="reference/ref-150.htm">
-			</topic>
-			<topic label="Run and Debug Actions" href="reference/ref-4.htm">
-			</topic>
-		</topic>
-	</topic>
-	<anchor id="r_menus" />
-	
-	<topic label="Toolbar">
-		<topic label="Java Toolbar Actions" href="reference/ref-3.htm"/>
-		<topic label="Java Editor Toolbar Actions" href="reference/ref-java-editor.htm" />
-		<topic label="Run and Debug Actions" href="reference/ref-4.htm" />
-	</topic>
-	
-	<topic label="Preferences" >
-		<topic label="Java" href="reference/ref-13.htm" >
-			<topic label="Appearance" href="reference/ref-preferences-appearance.htm" />
-			<topic label="Classpath Variables" href="reference/ref-15.htm" />
-			<topic label="Code Style" href="reference/ref-preferences-code-generation.htm">
-				<topic label="Code Templates" href="reference/ref-preferences-code-templates.htm" />
-				<topic label="Formatter" href="reference/ref-17.htm" />
-				<topic label="Organize Imports" href="reference/ref-22.htm" />
-			</topic>
-			<topic label="Compiler" href="reference/ref-preferences-compiler.htm">
-				<topic label="Task Tags" href="reference/ref-preferences-task-tags.htm" />
-			</topic>
-			<topic label="Java Editor" href="reference/ref-21.htm" >
-	  			<topic label="Templates" href="reference/ref-preferences-templates.htm" />
-			</topic>
-			<topic label="Installed JREs" href="reference/ref-19.htm" />
-			<topic label="JUnit" href="reference/ref-preferences-junit.htm" />
-		</topic>
-		<topic label="Debug" href="reference/ref-11.htm">
-			<topic label="Console Preferences" href="reference/ref-12.htm"/>
-		</topic>
-	</topic>
-	<anchor id="r_jdtprefs" />	
-
-    <topic label="Dialogs">
-        <topic label="Java Element Filters" href="reference/ref-dialog-java-element-filters.htm" />
-        <topic label="Open Type dialog" href="reference/ref-148.htm" />
-		<topic label="Create Getter and Setter" href="reference/ref-dialog-gettersetter.htm" />
-    	<topic label="Override Methods" href="reference/ref-dialog-override-method.htm" />
-    </topic>
-
-    <topic label="Property Pages">
-        <topic label="Javadoc Location" href="reference/ref-dialog-javadoc-location.htm" />
- 		<topic label="Java Build Path" href="reference/ref-123.htm" />
- 		<topic label="Java Compiler" href="reference/ref-properties-compiler.htm" />
- 		<topic label="Java Task Tags" href="reference/ref-properties-task-tags.htm" />
-		<topic label="Source Attachment" href="reference/ref-124.htm" />
-    </topic>    
-
-    <topic label="Wizards">
-        <topic label="Externalize Strings wizard" href="reference/ref-wizard-externalize-strings.htm" />
-		<topic label="JAR file exporter" href="reference/ref-export-jar.htm" />
-		<topic label="Javadoc generation" href="reference/ref-export-javadoc.htm" />
-    </topic>
-
-	<topic label="New Wizards" >
-		<topic label="New Java Project Wizard" href="reference/ref-121.htm">
-			<topic label="Java Build Path Page" href="reference/ref-123b.htm" />
-			<topic label="Attaching Source to JAR Files and Variables" href="reference/ref-124.htm" />
-		</topic>
-		<anchor id="r_newwizards" />
-		
-		<anchor id="r_newjavapkgwizard" />
-		<topic label="New Java Package Wizard" href="reference/ref-125.htm" />
-		<anchor id="r_newjavaclasswizard" />
-		<topic label="New Java Class Wizard" href="reference/ref-126.htm" />
-		<anchor id="r_newjavaenumwizard" />
-		<topic label="New Java Enum Wizard" href="reference/ref-126b.htm" />
-		<anchor id="r_newjavainterfacewizard" />
-		<topic label="New Java Interface Wizard" href="reference/ref-127.htm" />
-		<anchor id="r_newjavaannotationwizard" />
-		<topic label="New Java Annotation Wizard" href="reference/ref-127b.htm" />
-		<anchor id="r_newsourcefolderwizard" />
-		<topic label="New Source Folder Wizard" href="reference/ref-128.htm" />
-		<anchor id="r_newjavascrapbookpgwizard" />
-		<topic label="New Java Scrapbook Page Wizard" href="reference/ref-129.htm" />
-	</topic>
-
-	<topic label="Search" >
-		<topic label="Java Search Tab" href="reference/ref-131.htm" />
-		<topic label="Java Search Actions" href="reference/ref-menu-search.htm" />
-	</topic>
-	<anchor id="r_search" />
-	<topic label="Refactoring" href="reference/ref-115.htm">
-		<topic label="Refactor Actions" href="reference/ref-menu-refactor.htm" />
-		<topic label="Refactor Wizard" href="reference/ref-117.htm" />
-		<topic label="Extract Method Errors" href="reference/ref-154.htm" />
-		<topic label="Java Preferences" href="reference/ref-13.htm" />		
-		<anchor id="r_refactoringerrors" />
-
-	</topic>
-
-	<topic label="Frequently-Asked Questions: JDT" href="reference/ref-152.htm" />
-	<anchor id="r_faqjdt" />
-
-	<topic label="Icons" href="reference/ref-156.htm" />
-	<topic label="Glossary" href="reference/ref-155.htm" />
-
-</toc>

diff --git a/bundles/org.eclipse.jdt.doc.user/topics_Tasks.xml b/bundles/org.eclipse.jdt.doc.user/topics_Tasks.xml
deleted file mode 100644
index 93c4e15..0000000
--- a/bundles/org.eclipse.jdt.doc.user/topics_Tasks.xml
+++ /dev/null

@@ -1,318 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ========================== -->
-<!-- Define topics for the Tasks -->
-<!-- ========================== -->
-<toc label="Tasks">
-
-	<topic label="Changing the appearance of the Java tools">
-		<topic label="Showing and hiding elements" href="tasks/tasks-2.htm">
-			<topic label="Showing and hiding system files" href="tasks/tasks-3.htm"></topic>
-			<topic label="Showing and hiding CLASS files generated for inner types" href="tasks/tasks-4.htm"></topic>
-			<topic label="Showing and hiding libraries" href="tasks/tasks-5.htm"></topic>
-			<topic label="Showing and hiding empty packages " href="tasks/tasks-183.htm"></topic>
-			<topic label="Showing and hiding empty parent packages " href="tasks/tasks-184.htm"></topic>
-			<topic label="Showing and hiding Java files " href="tasks/tasks-185.htm"></topic>
-			<topic label="Showing and hiding non-Java elements" href="tasks/tasks-186.htm"></topic>
-			<topic label="Showing and hiding non-Java projects" href="tasks/tasks-213.htm"></topic>
-			<topic label="Showing and hiding members" href="tasks/tasks-191.htm"></topic>
-			<topic label="Showing and hiding override indicators" href="tasks/tasks-192.htm"></topic>
-			<topic label="Showing and hiding method return types" href="tasks/tasks-193.htm"></topic>
-			<topic label="Showing and hiding import declarations" href="tasks/tasks-212.htm"></topic>
-			<topic label="Showing and hiding package declarations" href="tasks/tasks-214.htm"></topic>
-		</topic>
-		<topic label="Showing full or compressed package names" href="tasks/tasks-194.htm"></topic>
-		<topic label="Sorting elements in Java views" href="tasks/tasks-195.htm"></topic>		
-		<topic label="Customizing the debugger and console" >
-			<topic label="Changing the active perspective when launching" href="tasks/tasks-9.htm"></topic>
-			<topic label="Changing the appearance of the console view" href="tasks/tasks-consoleAppearance.htm"></topic>
-		</topic>
-	</topic>
-	<anchor id="t_appearancejava" />
-
-	<topic label="Creating Java elements" href="tasks/tasks-11.htm">
-		<topic label="Creating a new Java project" href="tasks/tasks-12.htm">
-			<topic label="Creating a Java project as its own source container" href="tasks/tasks-13.htm"></topic>
-			<topic label="Creating a Java project with source folders" href="tasks/tasks-14.htm"></topic>
-		</topic>
-		<topic label="Creating a new source folder" href="tasks/tasks-26.htm">
-			<topic label="Creating a new source folder with exclusion filter" href="tasks/tasks-221.htm"></topic>
-			<topic label="Creating a new source folder with specific output folder" href="tasks/tasks-222.htm"></topic>
-		</topic>
-		<topic label="Creating a new Java package" href="tasks/tasks-15.htm"></topic>
-		<topic label="Creating a new Java class" href="tasks/tasks-17.htm">
-			<topic label="Creating a top-level class" href="tasks/tasks-18.htm"></topic>
-			<topic label="Creating a nested class" href="tasks/tasks-19.htm"></topic>
-			<topic label="Creating a new class in an existing compilation unit" href="tasks/tasks-20.htm"></topic>
-		</topic>
-		<topic label="Creating a new Java enum" href="tasks/tasks-17b.htm"></topic>
-		<topic label="Creating a new Java interface" href="tasks/tasks-21.htm">
-			<topic label="Creating a top-level interface" href="tasks/tasks-23.htm"></topic>
-			<topic label="Creating a nested interface" href="tasks/tasks-24.htm"></topic>
-			<topic label="Creating a new interface in an existing compilation unit" href="tasks/tasks-25.htm"></topic>
-		</topic>
-		<topic label="Creating a new Java annotation" href="tasks/tasks-21b.htm"></topic>
-		<topic label="Creating a new Java scrapbook page" href="tasks/tasks-27.htm"></topic>
-	</topic>
-	<anchor id="t_createjavaelements" />
-
-	<topic label="Creating JAR Files" href="tasks/tasks-32.htm">
-		<topic label="Creating a new JAR file" href="tasks/tasks-33.htm"></topic>
-		<topic label="Setting advanced options" href="tasks/tasks-34.htm"></topic>
-		<topic label="Defining the JAR file&apos;s manifest" href="tasks/tasks-35.htm"></topic>
-		<topic label="Regenerating a JAR File" href="tasks/tasks-36.htm"></topic>
-	</topic>
-	<anchor id="t_createjar" />
-
-	<topic label="Creating Javadoc documentation" href="tasks/tasks-196.htm">
-		<topic label="Selecting types for Javadoc generation" href="tasks/tasks-199.htm"></topic>	
-		<topic label="Configuring Javadoc arguments for standard doclet" href="tasks/tasks-200.htm"></topic>	
-		<topic label="Configuring Javadoc arguments" href="tasks/tasks-201.htm"></topic>	
-	</topic>
-	<anchor id="t_createjavadoc" />
-	
-	<topic label="Using the Hierarchy view" href="tasks/tasks-37.htm">
-		<topic label="Changing the appearance of the Hierarchy view" href="tasks/tasks-38.htm"></topic>
-		<topic label="Opening a type hierarchy on a Java element" href="tasks/tasks-39.htm"></topic>
-		<topic label="Opening a type hierarchy on the current text selection" href="tasks/tasks-40.htm"></topic>
-		<!--<topic label="Opening a type hierarchy in the workbench" href="tasks/tasks-41.htm"></topic>-->
-		<topic label="Opening a type hierarchy in its own perspective" href="tasks/tasks-42.htm"></topic>
-		<topic label="Finding overridden methods" href="tasks/tasks-44.htm"></topic>
-	</topic>
-	<anchor id="t_hierarchyview" />
-
-	<topic label="Using the Package Explorer" href="tasks/tasks-45.htm">
-		<topic label="Filtering elements" href="tasks/tasks-47.htm"></topic>
-		<topic label="Moving folders, packages and files" href="tasks/tasks-51.htm"></topic>
-	</topic>
-	<anchor id="t_packagesview" />
-
-	<topic label="Using the Java editor" href= "tasks/tasks-54.htm">
-		<topic label="Generating getters and setters" href="tasks/tasks-57.htm"></topic>
-		<topic label="Showing single elements or whole Java files" href="tasks/tasks-6.htm"></topic>
-		<topic label="Managing import statements" href="tasks/tasks-58.htm">
-			<topic label="Adding required import statements" href="tasks/tasks-59.htm"></topic>
-			<topic label="Organizing existing import statements" href="tasks/tasks-60.htm"></topic>
-			<topic label="Setting the order of import statements" href="tasks/tasks-61.htm"></topic>
-		</topic>
-		<topic label="Using the local history" href="tasks/tasks-62.htm">
-			<topic label="Comparing a Java element with a local history edition" href="tasks/tasks-63a.htm"></topic>
-			<topic label="Replacing a Java element with a local history edition" href="tasks/tasks-63.htm"></topic>
-			<topic label="Restoring a deleted workbench element" href="tasks/tasks-64.htm"></topic>
-		</topic>
-		<topic label="Using content assist" href="tasks/tasks-65.htm"></topic>
-		<topic label="Formatting Java code" href="tasks/tasks-66.htm">
-			<topic label="Formatting files or portions of code" href="tasks/tasks-67.htm"></topic>
-			<topic label="Setting code formatting preferences" href="tasks/tasks-68.htm"></topic>
-		</topic>
-		<topic label="Viewing documentation and information" href="tasks/tasks-69.htm">
-			<topic label="Viewing marker help" href="tasks/tasks-70.htm"></topic>
-			<topic label="Viewing Javadoc information" href="tasks/tasks-71.htm"></topic>
-		</topic>
-		<topic label="Using templates" href="tasks/tasks-171.htm"></topic>
-		<topic label="Writing your own templates" href="tasks/tasks-203.htm"></topic>
-		<topic label="Converting line delimiters" href="tasks/tasks-172.htm"></topic>
-		<topic label="Finding and replacing" href="tasks/tasks-173.htm">
-			<topic label="Using the Find/Replace dialog" href="tasks/tasks-181.htm"></topic>
-			<topic label="Using Incremental Find" href="tasks/tasks-182.htm"></topic>
-			<topic label="Finding Next or Previous Match" href="tasks/tasks-187.htm"></topic>
-		</topic>
-		<topic label="Changing the encoding used to show the source" href="tasks/tasks-174.htm"></topic>
-		<topic label="Using Quick Fix" href="tasks/tasks-175.htm"></topic>
-		<topic label="Using structured selection" href="tasks/tasks-176.htm"></topic>
-		<topic label="Commenting and uncommenting lines of code" href="tasks/tasks-177.htm"></topic>
-		<topic label="Shifting lines of code left and right" href="tasks/tasks-178.htm"></topic>
-		<topic label="Using Surround with try/catch" href="tasks/tasks-179.htm"></topic>
-	</topic>
-	<anchor id="t_usingjavaed" />
-
-	<topic label="Externalizing Strings" href="tasks/tasks-206.htm">
-		<topic label="Finding strings to externalize" href="tasks/tasks-188.htm"></topic>
-		<topic label="Finding unused and incorrectly used keys in property files" href="tasks/tasks-202.htm"></topic>
-		<topic label="Using the Externalize Strings wizard" href="tasks/tasks-180.htm">
-			<topic label="Key/value page" href="tasks/tasks-189.htm"></topic>
-			<topic label="Property file page" href="tasks/tasks-190.htm"></topic>
-		</topic>
-	</topic>
-	<anchor id="t_externalizingstrings" />
-	
-	<topic label="Navigating the JDT workbench" >
-		<topic label="Opening an editor for a selected element" href="tasks/tasks-73.htm"></topic>
-		<topic label="Showing an element in the Package Explorer view" href="tasks/tasks-74.htm"></topic>
-		<topic label="Opening a type in the Package Explorer view" href="tasks/tasks-75.htm"></topic>
-		<topic label="Opening an editor on a type" href="tasks/tasks-76.htm"></topic>
-		<topic label="Opening a package" href="tasks/tasks-77.htm"></topic>
-		<!--<topic label="Viewing Source in a JAR File" href="tasks/tasks-78.htm"></topic>-->
-		<!--< topic label="Searching Java code" href="tasks/tasks-79.htm"></topic> -->
-	</topic>
-	<anchor id="t_navigatingjdt" />
-
-	<topic label="Refactoring" href="tasks/tasks-80.htm">
-		<topic label="Refactoring steps" >
-			<topic label="Refactoring without preview" href="tasks/tasks-82.htm"></topic>
-			<topic label="Refactoring with preview" href="tasks/tasks-83.htm"></topic>
-			<topic label="Previewing refactoring changes" href="tasks/tasks-84.htm"></topic>
-		</topic>
-		<topic label="Copying and moving Java elements" href="tasks/tasks-85.htm"></topic>
-		<topic label="Extracting a method" href="tasks/tasks-87.htm">
-			<topic label="Parameters page" href="tasks/tasks-88.htm"></topic>
-			<topic label="Problems page" href="tasks/tasks-89.htm"></topic>
-		</topic>
-		<topic label="Renaming a package" href="tasks/tasks-90.htm">
-			<topic label="Parameters page" href="tasks/tasks-91.htm"></topic>
-		</topic>
-		<topic label="Renaming a compilation unit" href="tasks/tasks-92.htm">
-			<topic label="Parameters page" href="tasks/tasks-93.htm"></topic>
-		</topic>
-		<topic label="Renaming a type" href="tasks/tasks-94.htm">
-			<topic label="Parameters page" href="tasks/tasks-95.htm"></topic>
-		</topic>
-		<topic label="Renaming a method" href="tasks/tasks-96.htm">
-			<topic label="Parameters page" href="tasks/tasks-97.htm"></topic>
-		</topic>
-		<topic label="Renaming a field" href="tasks/tasks-169.htm">
-			<topic label="Parameters page" href="tasks/tasks-170.htm"></topic>
-		</topic>
-		<topic label="Renaming a local variable" href="tasks/tasks-204.htm">
-			<topic label="Parameters page" href="tasks/tasks-205.htm"></topic>
-		</topic>
-		<topic label="Renaming method parameters" href="tasks/tasks-98.htm">
-			<topic label="Parameters page" href="tasks/tasks-99.htm"></topic>
-		</topic>
-		<topic label="Changing method signature" href="tasks/tasks-157.htm">
-			<topic label="Parameters page" href="tasks/tasks-158.htm"></topic>
-		</topic>
-		<topic label="Extracting a local variable" href="tasks/tasks-159.htm">
-			<topic label="Parameters page" href="tasks/tasks-160.htm"></topic>
-		</topic>
-		<topic label="Extracting a constant" href="tasks/tasks-209.htm">
-		</topic>
-		<topic label="Inlining a local variable" href="tasks/tasks-161.htm">
-		</topic>
-		<topic label="Inlining a method" href="tasks/tasks-208.htm">
-		</topic>
-		<topic label="Inlining a constant" href="tasks/tasks-207.htm">
-		</topic>
-		<topic label="Self encapsulating a field" href="tasks/tasks-162.htm">
-			<topic label="Parameters page" href="tasks/tasks-163.htm"></topic>
-		</topic>
-		<topic label="Replacing a local variable with a query" href="tasks/tasks-164.htm">
-		</topic>
-		<topic label="Pulling members up to superclass" href="tasks/tasks-165.htm">
-			<topic label="Parameters page" href="tasks/tasks-166.htm"></topic>
-		</topic>
-		<topic label="Pushing members down to subclasses" href="tasks/tasks-220.htm">
-		</topic>
-		<topic label="Moving static members between types" href="tasks/tasks-167.htm">
-			<topic label="Parameters page" href="tasks/tasks-168.htm"></topic>
-		</topic>
-		<topic label="Moving an instance method to a component" href="tasks/tasks-210.htm">
-		</topic>
-		<topic label="Converting a local variable to a field" href="tasks/tasks-211.htm">
-		</topic>
-		<topic label="Converting an anonynous inner class to a nested class" href="tasks/tasks-216.htm">
-		</topic>
-		<topic label="Converting a nested type to a top level type" href="tasks/tasks-217.htm">
-		</topic>
-		<topic label="Extracting an interface from a type" href="tasks/tasks-218.htm">
-		</topic>
-		<topic label="Replacing references to a type with references to one of its supertypes" href="tasks/tasks-219.htm">
-		</topic>
-		<topic label="Replacing a single reference to a type with a reference to one of its supertypes" href="tasks/tasks-223.htm">
-		</topic>
-		<topic label="Replacing an expression with a method parameter" href="tasks/tasks-224.htm">
-		</topic>
-		<topic label="Replacing constructor calls with factory method invocations" href="tasks/tasks-225.htm">
-		</topic>
-		<topic label="Inferring type parameters for generic type references" href="tasks/tasks-226.htm">
-		</topic>
-		
-		<topic label="Undoing a refactoring operation"  href="tasks/tasks-100.htm"></topic>
-		<topic label="Redoing a refactoring operation" href="tasks/tasks-101.htm"></topic>
-	</topic>
-	<anchor id="t_refactoringjdt" />
-
-	<topic label="Searching" >
-		<topic label="Conducting a Java search using the search dialog" href="tasks/tasks-103.htm"></topic>
-		<topic label="Conducting a Java search using pop-up menus" href="tasks/tasks-104.htm"></topic>
-	</topic>
-	<anchor id="t_searchingjdt" />
-
-	<topic label="Building" >
-		<topic label="Building a Java program" href="tasks/tasks-106.htm">
-			<topic label="Viewing compilation errors and warnings" href="tasks/tasks-107.htm"></topic>
-			<topic label="Building automatically" href="tasks/tasks-108.htm"></topic>
-			<topic label="Building manually" href="tasks/tasks-109.htm"></topic>
-			<topic label="Building circular projects" href="tasks/tasks-109a.htm"></topic>
-			<topic label="Building without cleaning output location" href="tasks/tasks-109b.htm"></topic>
-		</topic>
-		<topic label="Working with build paths" href="tasks/tasks-110.htm">
-			<topic label="Viewing and editing a project&apos;s build path" href="tasks/tasks-111.htm"></topic>
-			<topic label="Adding a library folder to the build path" href="tasks/tasks-112.htm"></topic>
-			<topic label="Adding a JAR file to the build path" href="tasks/tasks-113.htm"></topic>
-			<topic label="Adding a classpath variable to the build path" href="tasks/tasks-114.htm"></topic>
-			<topic label="Attaching source to a JAR file" href="tasks/tasks-115.htm"></topic>
-			<topic label="Attaching source to a library folder" href="tasks/tasks-115a.htm"></topic>
-			<topic label="Attaching source to a classpath variable" href="tasks/tasks-116.htm"></topic>
-			<topic label="Defining a class path variable" href="tasks/tasks-117.htm"></topic>
-			<topic label="Deleting a class path variable" href="tasks/tasks-118.htm"></topic>
-		</topic>
-		<topic label="Working with JREs" href="tasks/tasks-JREs.htm">
-			<topic label="Assigning the default JRE for the workbench" href="tasks/tasks-120.htm"></topic>
-			<topic label="Adding a new JRE definition" href="tasks/tasks-121.htm"></topic>
-			<topic label="Overriding the default system libraries for a JRE definition" href="tasks/tasks-122.htm"></topic>
-			<topic label="Editing a JRE definition" href="tasks/tasks-123.htm"></topic>
-			<topic label="Choosing a JRE for launching a project" href="tasks/tasks-124.htm"></topic>
-			<topic label="Deleting a JRE definition" href="tasks/tasks-deleteJRE.htm">	</topic>
-		</topic>
-	</topic>
-	<anchor id="t_buildingjdt" />
-
-	<topic label="Running and debugging" href="tasks/tasks-126.htm">
-		<topic label="Launching a Java program" href="tasks/tasks-130.htm"></topic>
-		<topic label="Launching a Java applet" href="tasks/tasks-130a.htm"></topic>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"></topic>
-		<topic label="Setting execution arguments" href="tasks/tasks-executionArgs.htm"></topic>
-		<topic label="Relaunching a program" href="tasks/tasks-131.htm"></topic>
-		<topic label="Local debugging" href="concepts/clocdbug.htm">
-			<topic label="Preparing to debug" href="tasks/tasks-133.htm"></topic>
-			<topic label="Launching a Java program in debug mode" href="tasks/tasks-debug-launch.htm"></topic>
-			<topic label="Suspending threads" href="tasks/tasks-134.htm"></topic>
-			<topic label="Resuming the execution of suspended threads" href="tasks/tasks-135.htm"></topic>
-			<topic label="Stepping through the execution of a program" href="tasks/tasks-136.htm"></topic>
-			<topic label="Inspecting Values" href="tasks/tasks-137.htm"></topic>
-			<topic label="Evaluating expressions" href="tasks/tasks-138.htm"></topic>
-		</topic>
-		<topic label="Remote debugging" href="concepts/cremdbug.htm">
-			<topic label="Using the remote Java application launch configuration" href="tasks/tasks-141.htm"></topic>
-			<topic label="Disconnecting from a VM" href="tasks/tasks-142.htm"></topic>
-		</topic>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm">
-			<topic label="Adding breakpoints" href="tasks/tasks-144.htm"></topic>
-			<topic label="Removing breakpoints" href="tasks/tasks-144a.htm"></topic>
-			<topic label="Enabling and disabling breakpoints" href="tasks/tasks-144b.htm"></topic>
-			<topic label="Setting method breakpoints" href="tasks/tasks-145.htm"></topic>
-			<topic label="Applying hit counts" href="tasks/tasks-146.htm"></topic>
-			<topic label="Managing conditional breakpoints" href="tasks/tasks-144c.htm"></topic>
-			<topic label="Catching Java exceptions" href="tasks/tasks-147.htm"></topic>
-		</topic>
-	</topic>
-	<anchor id="t_runningdebuggingjdt" />
-	<topic label="Using the scrapbook" href="concepts/concepts-11.htm">
-		<topic label="Creating a Java scrapbook page" href="tasks/tasks-149.htm"></topic>
-		<topic label="Inspecting the result of evaluating an expression" href="tasks/tasks-150.htm"></topic>
-		<topic label="Displaying the result of evaluating an expression" href="tasks/tasks-151.htm"></topic>
-		<topic label="Running an expression" href="tasks/tasks-152.htm"></topic>
-		<topic label="Using code assist" href="tasks/tasks-153.htm"></topic>
-		<topic label="Scrapbook error reporting" href="tasks/tasks-154.htm">
-			<topic label="Viewing compilation errors" href="tasks/tasks-155.htm"></topic>
-			<topic label="Viewing runtime exceptions" href="tasks/tasks-156.htm"></topic>
-		</topic>
-	</topic>
-	<anchor id="t_scrapbook" />
-	<topic label="Using the Formatter Application" href="tasks/tasks-230.htm">
-			<topic label="Running the Formatter Application" href="tasks/tasks-231.htm"></topic>
-			<topic label="Generating a config file for the Formatter Application" href="tasks/tasks-232.htm"></topic>
-	</topic>
-	
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/EnumConstantQuickFix.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/EnumConstantQuickFix.png
deleted file mode 100644
index b3ab217..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/EnumConstantQuickFix.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/FirstContact.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/FirstContact.png
deleted file mode 100644
index 41e5252..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/FirstContact.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/NewEnumAnnWizards.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/NewEnumAnnWizards.png
deleted file mode 100644
index 07cb259..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/NewEnumAnnWizards.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/SerialVersionID.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/SerialVersionID.png
deleted file mode 100644
index b9a378e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/SerialVersionID.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/UnusedLocalWarning.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/UnusedLocalWarning.png
deleted file mode 100644
index 8f7df9f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/UnusedLocalWarning.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/UnusedLocalWarningSuppressed.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/UnusedLocalWarningSuppressed.png
deleted file mode 100644
index f1a8e7d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/UnusedLocalWarningSuppressed.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/access-restrictionR31.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/access-restrictionR31.png
deleted file mode 100644
index dbd6e5b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/access-restrictionR31.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/accessrulesR31.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/accessrulesR31.png
deleted file mode 100644
index 82f4d38..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/accessrulesR31.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/add_typeparam.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/add_typeparam.png
deleted file mode 100644
index 3e09f31..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/add_typeparam.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/advan-qas1.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/advan-qas1.png
deleted file mode 100644
index e7afc9b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/advan-qas1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/assignmenthasnoeffectR31.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/assignmenthasnoeffectR31.png
deleted file mode 100644
index 52cdecc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/assignmenthasnoeffectR31.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/augment-after.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/augment-after.png
deleted file mode 100644
index fa3ea97..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/augment-after.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/augment-before.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/augment-before.png
deleted file mode 100644
index 2ea2b2d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/augment-before.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/autoboxing_proposals.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/autoboxing_proposals.png
deleted file mode 100644
index bcb9f01..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/autoboxing_proposals.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/book.css b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/book.css
deleted file mode 100644
index 84d8880..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/book.css
+++ /dev/null

@@ -1 +0,0 @@
-@import "../PRODUCT_PLUGIN/book.css";

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/buildpath-menu.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/buildpath-menu.png
deleted file mode 100644
index c44102e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/buildpath-menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/change-compliance-quickfix.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/change-compliance-quickfix.png
deleted file mode 100644
index 12a11f8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/change-compliance-quickfix.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/completeannotationattributeR31.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/completeannotationattributeR31.png
deleted file mode 100644
index 9feb04a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/completeannotationattributeR31.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/completiononemptyword.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/completiononemptyword.png
deleted file mode 100644
index 8e822c7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/completiononemptyword.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/cpy.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/cpy.png
deleted file mode 100644
index a0f8775..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/cpy.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/ctrl-click.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/ctrl-click.png
deleted file mode 100644
index 905301a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/ctrl-click.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/deprecated_member_highlighting.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/deprecated_member_highlighting.png
deleted file mode 100644
index 1ea5038..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/deprecated_member_highlighting.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/enhanced-for-2.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/enhanced-for-2.png
deleted file mode 100644
index 1f0a66c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/enhanced-for-2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/enhanced-for.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/enhanced-for.png
deleted file mode 100644
index 56a65b2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/enhanced-for.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/enumidentifierR31.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/enumidentifierR31.png
deleted file mode 100644
index cd870f9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/enumidentifierR31.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/externalize_strings_wizard.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/externalize_strings_wizard.png
deleted file mode 100644
index fcc7cae..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/externalize_strings_wizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/folding.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/folding.png
deleted file mode 100644
index f0b86ea..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/folding.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/formatter.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/formatter.png
deleted file mode 100644
index 4dce5e2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/formatter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/header_folding.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/header_folding.png
deleted file mode 100644
index 5b6358b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/header_folding.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/implementsannotationR31.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/implementsannotationR31.png
deleted file mode 100644
index 9657019..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/implementsannotationR31.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/import-static-groups.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/import-static-groups.png
deleted file mode 100644
index 5583717..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/import-static-groups.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/inferdialog.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/inferdialog.png
deleted file mode 100644
index 4abc57b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/inferdialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/interface_refactoring.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/interface_refactoring.png
deleted file mode 100644
index 5a6376b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/interface_refactoring.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/javadoc-quickfix.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/javadoc-quickfix.png
deleted file mode 100644
index d41b355..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/javadoc-quickfix.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/javasearchfilter.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/javasearchfilter.png
deleted file mode 100644
index 9f61298..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/javasearchfilter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/line-wrap.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/line-wrap.png
deleted file mode 100644
index 3a12d89..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/line-wrap.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/mark-implement-occurrences.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/mark-implement-occurrences.png
deleted file mode 100644
index bb8a6d4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/mark-implement-occurrences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/missingdeprecatedannotationR31.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/missingdeprecatedannotationR31.png
deleted file mode 100644
index bb737e8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/missingdeprecatedannotationR31.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/missingenumconstantR31.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/missingenumconstantR31.png
deleted file mode 100644
index d6624c9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/missingenumconstantR31.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/missingoverrideannotationR31.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/missingoverrideannotationR31.png
deleted file mode 100644
index 384e3e6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/missingoverrideannotationR31.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/mixed-indents.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/mixed-indents.png
deleted file mode 100644
index 2785b1b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/mixed-indents.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/move-refactoring.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/move-refactoring.png
deleted file mode 100644
index 4566795..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/move-refactoring.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/navigatorlocaltypeR31.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/navigatorlocaltypeR31.png
deleted file mode 100644
index 990dd9b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/navigatorlocaltypeR31.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/new-type-wizard.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/new-type-wizard.png
deleted file mode 100644
index b28640c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/new-type-wizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/new_for_loop.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/new_for_loop.png
deleted file mode 100644
index edb3916..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/new_for_loop.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/nls-hover.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/nls-hover.png
deleted file mode 100644
index d69e772..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/nls-hover.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/open-type.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/open-type.png
deleted file mode 100644
index 5cb97dd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/open-type.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/deadlock.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/deadlock.png
deleted file mode 100644
index ae82340..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/deadlock.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/edit_jre.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/edit_jre.png
deleted file mode 100644
index f90d40d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/edit_jre.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/edit_value.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/edit_value.png
deleted file mode 100644
index 19aabca..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/edit_value.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/logical_structures.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/logical_structures.png
deleted file mode 100644
index bac89e2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/logical_structures.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/stack_trace_console.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/stack_trace_console.png
deleted file mode 100644
index 4dfe2dd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/stack_trace_console.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/tostring_inline.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/tostring_inline.png
deleted file mode 100644
index 1ab70e9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/org.eclipse.jdt.debug.ui/tostring_inline.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/override_method.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/override_method.png
deleted file mode 100644
index 17bbf1a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/override_method.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/package-explorer.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/package-explorer.png
deleted file mode 100644
index 9480c0f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/package-explorer.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/packageinfosupportR31.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/packageinfosupportR31.png
deleted file mode 100644
index c156859..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/packageinfosupportR31.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/perprojectlink.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/perprojectlink.png
deleted file mode 100644
index 934960f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/perprojectlink.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/project-settings.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/project-settings.png
deleted file mode 100644
index 2748b65..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/project-settings.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/properties-file-compare.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/properties-file-compare.png
deleted file mode 100644
index 0ac7c0c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/properties-file-compare.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/property-key-navigation.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/property-key-navigation.png
deleted file mode 100644
index 2b86248..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/property-key-navigation.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist-shortcuts.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist-shortcuts.png
deleted file mode 100644
index 7423fac..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist-shortcuts.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist1.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist1.png
deleted file mode 100644
index a51428e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist1b.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist1b.png
deleted file mode 100644
index 58738c0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist1b.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist2.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist2.png
deleted file mode 100644
index 96e9489..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist3.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist3.png
deleted file mode 100644
index 3c2fb6c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist4.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist4.png
deleted file mode 100644
index c38c53c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist5.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist5.png
deleted file mode 100644
index 3222e16..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/quick-assist5.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/rename-type-parameter.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/rename-type-parameter.png
deleted file mode 100644
index 0328636..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/rename-type-parameter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/rerunfailed.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/rerunfailed.png
deleted file mode 100644
index 111ddeb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/rerunfailed.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/selectinjavadoc.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/selectinjavadoc.png
deleted file mode 100644
index 7b81dff..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/selectinjavadoc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/sourcefolderwizard.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/sourcefolderwizard.png
deleted file mode 100644
index 56c306c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/sourcefolderwizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/staticimportcodeassistR31.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/staticimportcodeassistR31.png
deleted file mode 100644
index 8ab19ba..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/staticimportcodeassistR31.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/supertype.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/supertype.png
deleted file mode 100644
index b00d700..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/supertype.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/suppresswarningsR31.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/suppresswarningsR31.png
deleted file mode 100644
index 0441de1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/suppresswarningsR31.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/suppresswarningsTokenR31.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/suppresswarningsTokenR31.png
deleted file mode 100644
index cf6252a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/suppresswarningsTokenR31.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/syntax_coloring.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/syntax_coloring.png
deleted file mode 100644
index 85c26e5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/syntax_coloring.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/type-argument-completion.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/type-argument-completion.png
deleted file mode 100644
index eb66f83..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/type-argument-completion.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/typeparameterhidingtypeR31.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/typeparameterhidingtypeR31.png
deleted file mode 100644
index 640b8b2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/typeparameterhidingtypeR31.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/unboxingwarningR31.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/unboxingwarningR31.png
deleted file mode 100644
index 9bf40f1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/unboxingwarningR31.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/undo.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/undo.png
deleted file mode 100644
index b974724..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/undo.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/varargsneedcastR31.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/varargsneedcastR31.png
deleted file mode 100644
index 10e43b5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/varargsneedcastR31.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/visibility-adjustment.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/visibility-adjustment.png
deleted file mode 100644
index 5576f53..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/visibility-adjustment.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html b/bundles/org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html
deleted file mode 100644
index 1f94c10..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html
+++ /dev/null

@@ -1,1600 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
-	type="text/css">
-<title>What's New in 3.1</title>
-</head>
-<body>
-<h2>What's New in 3.1</h2>
-<p><em></em>This document contains descriptions of some of the more interesting
-or significant changes made to the Java development tools for the 3.1
-release of Eclipse since 3.0. It is broken into several sections:</p>
-<ul>
-	<li><a href="#50">J2SE 5.0</a></li>
-	<li><a href="#Debug">Java Debugger</a></li>
-	<li><a href="#JavaCompiler">Java Compiler</a></li>
-	<li><a href="#JavaText">Java Editor</a></li>
-	<li><a href="#JavaUI">General Java Tools</a></li>
-</ul>
-<!-- *************************************************** -->
-<h2><a name="50">J2SE 5.0<br>
-</a></h2>
-<table cellpadding="10" cellspacing="0" width="600">
-	<colgroup>
-		<col width="20%" valign="top" align="right">
-		<col width="80%" valign="top" align="left">
-	</colgroup>
-	<tbody>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>J2SE 5.0</b></p>
-			</td>
-			<td width="70%" valign="top">
-			<p>Eclipse 3.1 includes full support for the new features of J2SE 5.0
-			(aka &quot;Tiger&quot;). One of the most important consequences of
-			this support is that you may not notice it at all -- everything that
-			you expect to work with J2SE 1.4, including editing, code assist,
-			compiling, debugging, quick fixes, refactorings, source actions,
-			searching, etc. will work seamlessly with J2SE 5.0's new types and
-			syntax.</p>
-			In order to develop code compliant with J2SE 5.0, you will need a 5.0
-			Java Runtime Environment (JRE). If you start Eclipse for the first
-			time using a 5.0 JRE, then it will use it by default. Otherwise, you
-			will need to use the Installed JREs dialog to register one with
-			Eclipse. You can reach this dialog either via the preference <b>Java &gt; Installed JREs</b> or by following the <b>Configure
-			default...</b> link on the New Java Project wizard.
-			<p><img src="images/FirstContact.png" alt="New Java Project wizard"
-				title="New Java Project Wizard"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>Quick Fix to<br>
-			update JRE and compiler compliance to 5.0</b></p>
-			</td>
-			<td valign="top" width="70%">A new quick fix helps you change the compliance settings when you
-			try to enter 5.0 constructs in a 1.4 project. Note that a 1.5 JRE is
-			required, which can be added in the 'Installed JRE's' preference
-			page.
-			<p><img alt="Change compliance quick fix"
-				src="images/change-compliance-quickfix.png"></p>
-
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b> New Type wizards support generics</b></p>
-			</td>
-			<td valign="top" width="70%">The New Type wizards support J2SE 5.0
-			generic types in various fields:
-			<ul>
-				<li>The <i>Name</i> field can include type parameter declarations.</li>
-				<li>The <i>Superclass</i> and the implemented <i>Interfaces</i> can
-				include generic type arguments.</li>
-			</ul>
-			<p><img src="images/new-type-wizard.png"
-				alt="Picture of New Type wizard" title="New Type wizard"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b> Creating Enumerations and Annotations</b></p>
-			</td>
-			<td width="70%" valign="top">Enumerations and Annotations can be
-			created with the new Enum or Annotation wizard:
-			<p><img src="images/NewEnumAnnWizards.png" alt="Enum wizard"></p>
-
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>Guessing for type arguments</b></p>
-			</td>
-			<td valign="top" width="70%">Code Assist inserts the correct type
-			arguments when completing a type in the Java editor. Type arguments
-			that cannot be disambiguated will be selected, and the <b>Tab</b> key
-			will move from one argument to the next.
-			<p>In this example <code>String</code> is inserted as the first type
-			argument, while <code>Number</code> is proposed for the second:</p>
-			<p><img src="images/type-argument-completion.png"
-				alt="Screenshot: a 'HashMap' is returned from a method declaring 'Map&lt;String, ? extends Number&gt;' as return type. String is inserted as the first type argument, while 'Number' is proposed for the second"
-				title="'String' is inserted as the first type argument, while 'Number' is proposed for the second">
-			</p>
-			<p>To try out this feature, you need to enable <b>Fill argument names</b>
-			on the <b>Java &gt; Editor &gt; Code Assist</b> preference page.</p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Type parameter declaration hiding another type
-			diagnosis</b></p>
-			</td>
-			<td width="70%" valign="top">The Java compiler can optionally flag a
-			type parameter declaration hiding another type.
-			<p><img
-				alt="picture of Java editor with type parameter hiding another type warning"
-				title="Java editor with type parameter hiding another type warning"
-				src="images/typeparameterhidingtypeR31.png"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Rename refactoring</b></p>
-			</td>
-			<td width="70%" valign="top">The Rename refactoring has been extended
-			to handle renaming of type parameters.<p><img src="images/rename-type-parameter.png"
-				alt="Screenshot showing the renaming of a type parameter in a generic class"
-				title="Rename Refactoring"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>Infer Generic Type Arguments<br>refactoring
-			</b></p>
-			</td>
-			<td valign="top" width="70%">With J2SE 5.0, your code can use
-			generics to enhance readability and static type safety. <b>Refactor
-			&gt; Infer Generic Type Arguments</b> is a new refactoring that helps
-			clients of generic class libraries, like the Java Collections Framework, to migrate their code.
-			<p><img alt="Augment Raw Container Clients - Before"
-				src="images/augment-before.png"></p>
-			<p>The refactoring infers type parameters for generic types, and will remove any unnecessary casts. It works on
-			single compilation units as well as on whole packages and Java
-			projects.</p>
-			<p><img alt="Augment Raw Container Clients - After"
-				src="images/augment-after.png"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>Quick fixes for Generics</b></p>
-			</td>
-			<td valign="top" width="70%">For unresolved Java types, you now also
-			get a proposal to create a new type parameter:
-			<p><img alt="Add type parameter quick fix"
-				src="images/add_typeparam.png"></p>
-			Support for Javadoc tags for type parameters has been added. In
-			J2SE 5.0, you document type parameters using the existing @param tag but
-			with the name enclosed in angle brackets.
-			<p><img alt="Javadoc quick fix for type parameter"
-				src="images/javadoc-quickfix.png"></p>
-
-
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>New search result filters for reference search
-			for parameterized types</b>
-</p>
-			</td>
-			<td valign="top" width="70%"><p>When searching for references to a
-			parameterized type such as <code>List&lt;Integer&gt;</code>, the
-			search result will contain references to all occurrences of List as
-			well. The search result view now offers two additional filters to
-			hide matches:</p>
-			<ul>
-				<li>Filter incompatible matches: this filter hides all results that
-				are not assignment compatible with the search pattern. For example
-				when searching for <code>List&lt;Integer&gt;</code> filtering
-				incompatible matches will hide <code>List&lt;String&gt;</code>, but
-				not <code>List&lt;? extends Number&gt;</code>.</li>
-				<li>Filter inexact matches: this filter hides all results that don't
-				exactly match the pattern. For the example above the filter will
-				also hide <code>List&lt;? extends Number&gt;</code>.</li>
-			</ul>
-			<p><img alt="Add type parameter quick fix"
-				src="images/javasearchfilter.png"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Completion on annotations</b></p>
-			</td>
-			<td width="70%" valign="top">Code completion inside a single
-			member annotation or annotation attribute value is supported.
-			<p><img
-				alt="picture of Java editor completing on an annotation attribute"
-				title="Java editor completing on an annotation attribute"
-				src="images/completeannotationattributeR31.png"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Usage of annotation type as super interface
-			diagnosis</b></p>
-			</td>
-			<td width="70%" valign="top">In J2SE 5.0, the Java language allows a
-			class to implement an annotation type. However this should be
-			discouraged. The Java compiler optionally flags such usage.
-			<p><img
-				alt="picture of Java editor with usage of annotation type as super interface warning"
-				title="Java editor with usage of annotation type as super interface warning"
-				src="images/implementsannotationR31.png" align="bottom"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Support for @SuppressWarnings
-			annotation</b></p>
-			</td>
-			<td width="70%" valign="top">The J2SE 5.0 @SuppressWarnings
-			annotation is supported. Recognized warning token names are:
-			"all", &quot;boxing&quot;, &quot;dep-ann&quot;, "deprecation", &quot;incomplete-switch&quot;, &quot;hiding&quot;, &quot;finally&quot;, &quot;static-access&quot;, &quot;nls&quot;, "serial", &quot;synthetic-access&quot;, &quot;unqualified-field-access&quot;, "unchecked", &quot;unused&quot; and &quot;warningToken&quot;. In the
-			example below, the first field is tagged with the
-			@SuppressWarnings("deprecation") annotation and no deprecation
-			warning is reported. The second field is not tagged and a deprecation
-			warning is reported.
-			<p><img alt="picture of Java editor showing @SuppressWarnings usage"
-				title="Java editor showing @SuppressWarnings usage"
-				src="images/suppresswarningsR31.png"></p>
-			<p>Note that a compiler option controls whether @SuppressWarnings
-			annotations are active or not. See the preference <b>Java &gt; Compiler &gt; Errors/Warnings &gt; J2SE
-			5.0 options &gt; Enable '@SuppressWarnings' annotations</b></p>
-			<p>By default, unhandled warning tokens are signaled by a warning.
-			This warning can also be suppressed using the
-			@SuppressWarnings("warningToken") annotation.</p>
-			<p><img alt="picture of Java editor showing warningToken usage"
-				title="Java editor showing warningToken usag"
-				src="images/suppresswarningsTokenR31.png"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Quick fix<br>
-			support for<br>
-			@SuppressWarnings</b></p>
-			</td>
-			<td width="70%" valign="top">Warnings that can be suppressed using a @SuppressWarning annotation offer a quick fix to do so. Applying quick fix to the unused local warning below <p><img alt="Suppress Warning quick fix"
-				title="Java editor showing @SuppressWarnings usage"
-				src="images/UnusedLocalWarning.png"></p>
-			<p>results in:</p>
-			<p><img alt="Suppressed unused warning problem"
-				title="Java editor showing warningToken usag"
-				src="images/UnusedLocalWarningSuppressed.png"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Missing @Override annotation diagnosis</b></p>
-			</td>
-			<td width="70%" valign="top">The Java compiler can optionally flag a
-			method overriding a superclass method, but missing a proper @Override
-			annotation.
-			Missing @Override annotations can be added using Quick Fix.<p><img
-				alt="picture of Java editor with method missing @Override warning"
-				title="Java editor with method missing @Override warning"
-				src="images/missingoverrideannotationR31.png"></p>
-			See the preference <b>Java &gt;
-			Compiler &gt; Errors/Warnings &gt; J2SE 5.0 options &gt; Missing
-			'@Override annotation</b></td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Missing @Deprecated annotation diagnosis</b></p>
-			</td>
-			<td width="70%" valign="top">The Java compiler recognizes the
-			@Deprecated annotations, and treats them equivalent to the doc comment
-			/** @deprecated */. It can optionally flag deprecated constructs
-			missing a proper @Deprecated annotation (to encourage using
-			annotations instead of doc comment tag).
-			<p><img
-				alt="picture of Java editor with missing @Deprecated annotation warning"
-				title="Java editor with missing @Deprecated annotation warning"
-				src="images/missingdeprecatedannotationR31.png"></p>
-			See preference under <b>Java &gt;
-			Compiler &gt; Errors/Warnings &gt; J2SE 5.0 options &gt; Missing
-			'@Deprecated' annotation</b></td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Incomplete enum switch statement diagnosis</b></p>
-			</td>
-			<td width="70%" valign="top">The Java compiler can optionally flag
-			incomplete enum switch statements.
-			<p><img
-				alt="picture of Java editor with incomplete enum switch statement warning"
-				title="Java editor with incomplete enum switch statement warning"
-				src="images/missingenumconstantR31.png"></p>
-			See preference under <b>Java &gt;
-			Compiler &gt; Errors/Warnings &gt; J2SE 5.0 options &gt; Not all enum
-			constants covered on 'switch'</b></td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Compiler diagnosis for 'enum' identifier</b></p>
-			</td>
-			<td width="70%" valign="top">The Java compiler can find and flag
-			where 'enum' is used as an identifier. While 'enum' is a legal
-			identifier up to source level 1.4, but a reserved keyword in 5.0
-			source. Enabling this warning helps to anticipate source migration
-			issues. See the preference <b>Java
-			&gt; Compiler &gt; JDK Compliance &gt; Disallow identifier called
-			'enum'</b>.
-			<p><img src="images/enumidentifierR31.png"
-				alt="Compiler optional diagnosis for 'enum' identifier"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Quick Fix to<br>
-			create enum constants</b></p>
-			</td>
-			<td width="70%" valign="top">Quick Fix <b></b>supports creation of enumeration constants. In the example below the constant BLUE is missing from the enumeration Colors<p><img src="images/EnumConstantQuickFix.png"
-				alt="Compiler optional diagnosis for 'enum' identifier"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>Autoboxing parameter<br>
-			proposals</b></p>
-			</td>
-			<td valign="top" width="70%">Proposed parameters include
-			auto(un-)boxing proposals:
-			<p><img src="images/autoboxing_proposals.png"
-				alt="Screenshot showing autoboxing proposals"
-				title="Autoboxing Proposals"></p><p>Note: The <b>Java &gt; Editor
-			&gt; Code Assist &gt; Fill argument names on completion</b>
-			preference has to be enabled.</p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>Boxing/<br>
-			unboxing diagnosis</b></p>
-			</td>
-			<td valign="top" width="70%">The J2SE 5.0 autoboxing capability is
-			powerful but it can lead to unexpected behavior especially when
-			passing arguments. The compiler introduces an optional diagnosis that
-			indicates when autoboxing or autounboxing is performed. In the
-			following example, one might think that <code>foo(Integer)</code>
-			would be called, but since autounboxing is performed, <code>foo(int)</code>
-			is called.
-			<p><img alt="picture of Java editor with unboxing warning"
-				title="Java editor with unboxing warning"
-				src="images/unboxingwarningR31.png"></p>
-			See preference under <b>Java &gt;
-			Compiler &gt; Errors/Warnings &gt; J2SE 5.0 options &gt; Boxing and
-			unboxing conversions</b>.</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Support for J2SE 5.0 in Java editor</b></p>
-			</td>
-			<td valign="top" width="70%">The Java editor provides syntax coloring for
-			the new J2SE 5.0 language features. Go to the <b>Java &gt; Editor
-			&gt; Syntax Coloring</b> preference page to change the colors or to
-			enable semantic coloring of <span style="color:#ff8040;">type variables</span>, <span style="color:#008040;">annotation elements</span> and
-			<span style="color:#ff0000;">auto(un-)boxed expressions</span>:
-			<p><img src="images/syntax_coloring.png"
-				alt="Screenshot showing syntax coloring of enum, annotations, annotation elements, type variables, and autoboxed expressions"
-				title="Syntax coloring of enum, annotations, annotation elements, type variables, and autoboxed expressions"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>New for loop template</b></p>
-			</td>
-			<td valign="top" width="70%">The <strong>foreach</strong>
-			template inserts a new 'for' loop into the code, proposing local <code>Iterable</code>
-			instances you may want to iterate over:
-			<p><img src="images/new_for_loop.png"
-				alt="Screenshot showing an inserted for-loop template"
-				title="New for loop syntax"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Convert to enhanced for loop</b></p>
-			</td>
-			<td width="70%" valign="top">A new Quick Assist (<b>Ctrl+1</b>)
-			offers to convert old-style for loops over arrays and collections to
-			J2SE 5.0 enhanced for loops:
-			<p><IMG SRC="images/enhanced-for.png" ALT="Picture convert to enhanced for loop example"></p>
-			<p>The Quick Fix simplifies the loop to:</p>
-			<p><IMG SRC="images/enhanced-for-2.png" ALT="Picture demonstrating the result of enhanced for loop quick assist" align="middle"></p>
-
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Varargs argument<br>
-			needing a cast</b></p>
-			</td>
-			<td width="70%" valign="top">The Java compiler can optionally flag
-			suspicious varargs method invocations. A null last argument is not
-			wrapped as a 1-element array as one might expect; adding an explicit
-			cast makes the intention of the code clear.
-			<p><img src="images/varargsneedcastR31.png"
-				alt="Compiler diagnoses required cast for varargs argument"></p>
-			<p>The preference setting can be found at <b>Java &gt; Compiler &gt; Errors/Warnings &gt; J2SE
-			5.0 Options &gt; Inexact type match for vararg arguments</b>.</p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Completion uses static imports</b></p>
-			</td>
-			<td width="70%" valign="top">Code completion in the Java editor is
-			able to process static imports when inferring context-sensitive
-			completions.
-			<p><img src="images/staticimportcodeassistR31.png"
-				alt="picture of Java editor completing and finding method from static import Math.*"
-				title="Java editor completing and finding method from static import Math.*"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>Static import <br>
-			groups</b></p>
-			</td>
-			<td width="70%">To organize your static imports, create groups for
-			the static imports and place them where you prefer. You can define an
-			'others' group to collect up all imports not matched by any other
-			group:
-			<p><img alt="Static imports group"
-				src="images/import-static-groups.png"></p>
-			<p>The 'others' group feature is also available for non-static
-			imports.</p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Support for<br>
-			package-info.java</b></p>
-			</td>
-			<td width="70%" valign="top">Support has been added for the special
-			source file package-info.java, which allows annotating and documenting
-			packages. All JDT tools (code assist, code select, search, outline,
-			type hierarchies, etc.) can be used in this special compilation unit.
-			<p>Doc comments inside the package-info.java are processed, and the
-			syntax and references in standard comment tags are verified.</p>
-			<p><img
-				alt="picture of Package Explorer and Java editor on package-info.java"
-				title="Package Explorer and Java editor on package-info.java"
-				src="images/packageinfosupportR31.png"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Code formatter for J2SE 5.0 constructs</b></p>
-			</td>
-			<td width="70%" valign="top">The code formatter supports all the new
-			J2SE 5.0 language constructs. Control over how the formatter handles
-			them are found on the <b>Java &gt; Code Style &gt; Code Formatter</b>
-			preference page:
-			<p><IMG SRC="images/formatter.png" ALT="Picture of white space formatter preference page"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Debugging 5.0 source code</b></p>
-			</td>
-			<td width="70%" valign="top">You can run and debug 5.0 source code
-			with a 1.5 JRE. Java debug evaluations support J2SE 5.0 constructs such as
-			generics and enhanced for loops.</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Class file naming change for local inner types</b></p>
-			</td>
-			<td width="70%" valign="top">In 5.0 compliance mode, the Java
-			compiler generates class files that follow the naming convention
-			specified in JLS 13.1 (3rd edition) for local inner types. As a
-			consequence, in the below example, instead of generating a file named <code>X$1$A.class</code>,
-			it will simply be <code>X$1A.class</code>.
-			<p><img alt="picture of Navigator with local inner type class file"
-				title="Navigator with local inner type class file"
-				src="images/navigatorlocaltypeR31.png"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-	</tbody>
-</table>
-<!-- *************************************************** -->
-<h2><a name="Debug">Java Debugger</a></h2>
-<table cellpadding="10" cellspacing="0" width="600">
-	<colgroup>
-		<col width="20%" valign="top" align="right">
-		<col width="80%" valign="top" align="left">
-	</colgroup>
-	<tbody>
-
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Watchpoints and<br>
-			method entry<br>
-			breakpoints</b></p>
-			</td>
-			<td width="70%" valign="top">Double clicking in the Java editor ruler
-			creates watchpoints on fields and method entry breakpoints on method
-			declarations.</td>
-		</tr>
-
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Locks and deadlocks</b></p>
-			</td>
-			<td width="70%" valign="top">
-			<p>The locks owned by a thread as well as the lock a thread is
-			waiting for can both be displayed inline in the Debug view by
-			toggling the <b>Show Monitors</b> menu item in the Debug view
-			drop-down menu. Threads and locks involved in a deadlock are
-			highlighted in red.</p>
-			<p><img src="images/org.eclipse.jdt.debug.ui/deadlock.png"
-				title="Threads and Monitors"
-				alt="A deadlock displayed in the Debug view"></p>
-			</td>
-		</tr>
-
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Navigating stack traces</b></p>
-			</td>
-			<td width="70%" valign="top">
-			<p>Copy and paste a stack trace into the Java Stack Trace Console and
-			use hyperlinks to navigate the trace. The Java Stack Trace Console
-			can be opened from the <b>Open Console</b> drop-down menu in the
-			Console view. Pasted stack traces can be formatted via the standard <b>Format</b>
-			key binding.</p>
-			<p><img src="images/org.eclipse.jdt.debug.ui/stack_trace_console.png"
-				title="Java Stack Trace Console" alt="Java Stack Trace Console"></p>
-			</td>	
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>'toString()' inline</b></p>
-			</td>
-			<td width="70%" valign="top">
-			<p>The toString()-computed value of a variable can be displayed
-			inline in the Variables view tree, as well as in the details area.
-			The <b>Java Detail Formatters...</b> command in the view drop-down menu is
-			used for configuring how this feature works.</p>
-			<p><img src="images/org.eclipse.jdt.debug.ui/tostring_inline.png" title="Inline toString()"
-				alt="Inline toString() example"></p>
-			</td>
-		</tr>
-
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>User-defined logical structures</b></p>
-			</td>
-			<td width="70%" valign="top">
-			<p>The Java debugger now lets you control what gets shown in the
-			variables view for different types of objects. For example,
-			collections can be displayed as a simple array of values, instead of
-			the gory details on how that particular collection object is
-			implemented.</p>
-			<p>This is done from the <b>Java &gt; Debug&gt; Logical Structures</b>
-			preference page, where you associate with a specific class or
-			interface either a single expression (for example, <code>this.toArray()</code>)
-			or a series of named expressions. When the object is to be shown in
-			the variables view, the expressions are evaluated to produce the
-			values to display.</p>
-			<p><img src="images/org.eclipse.jdt.debug.ui/logical_structures.png"
-				title="Java logical structure dialog"
-				alt="Dialog to edit Java logical structure"></p>
-			</td>
-		</tr>
-
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Enhanced variable value modification</b></p>
-			</td>
-			<td width="70%" valign="top">
-			<p>The Java debugger now lets you change the value of variables by
-			entering an expression into either the <b>Change Value</b> dialog or
-			into the details area of the variables view and pressing <b>Save</b>.</p>
-
-			<p><img src="images/org.eclipse.jdt.debug.ui/edit_value.png"
-				title="Change object value dialog"
-				alt="Dialog to edit an expression to replace the current value of a variable"></p>
-			</td>
-		</tr>
-
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Find variable</b></p>
-			</td>
-			<td width="70%" valign="top">
-			<p>The Find Variable action in the Variables view allows you to type
-			in the name of a variable you are looking for. As you type, the
-			Variables view selects the next visible variable matching the entered
-			text. As well, the Find variable dialog shows variables matching the
-			text entered so far.</p>
-			</td>
-		</tr>
-
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Javadoc attachments</b></p>
-			</td>
-			<td width="70%" valign="top">
-			<p>You can now associate a different Javadoc location with each JAR
-			in a JRE's libraries.</p>
-			<p><img src="images/org.eclipse.jdt.debug.ui/edit_jre.png"
-				title="Edit JRE Dialog" alt="Dialog showing a javadoc location per JRE library"></p>
-			</td>
-		</tr>
-
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-
-	</tbody>
-</table>
-
-<!-- *************************************************** -->
-<h2><a name="JavaCompiler">Java Compiler</a></h2>
-<table cellpadding="10" cellspacing="0" width="600">
-	<colgroup>
-		<col width="20%" valign="top" align="right">
-		<col width="80%" valign="top" align="left">
-	</colgroup>
-	<tbody>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="30%">
-			<p align="right"><b>New Javadoc<br>
-			compiler settings</b></p>
-			</td>
-			<td valign="top" width="70%">When Javadoc checking is enabled, you
-			can configure it to
-			<ul>
-				<li>warn when <code>@see</code> and <code>@link</code> tags
-				reference deprecated elements</li>
-				<li>warn when <code>@see</code> and <code>@link</code> tags
-				reference elements that are not visible</li>
-			</ul>
-			<p>The settings are on the <b>Java &gt; Compiler &gt; Javadoc</b>
-			preference page.</p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>Assignment with no effect diagnosis for postfix
-			expression</b></p>
-			</td>
-			<td valign="top" width="70%">The optional diagnosis for <strong>assignment
-			with no effect</strong> detects the case where a postfix expression is
-			assigned to the same variable, e.g. i = i++;
-			<p><img alt="picture of post fix expression assignment"
-				title="Post fix expression assignment"
-				src="images/assignmenthasnoeffectR31.png"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Serial Version UID</b></p>
-			</td>
-			<td width="70%" valign="top"><p>There is a new optional compiler diagnosis for
-			serializable classes missing a declaration of a <code>serialVersionUID</code>
-			field.</p><p> The preference setting can be found at <b>Java &gt; Compiler &gt;
-			Errors/Warnings &gt; Potential programming problems</b></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="30%">
-			<p align="right"><b>Early detection of references to internal classes</b></p>
-			</td>
-			<td valign="top" width="70%">You can annotate library (and
-			project) entries on the Java build path (<b>Properties &gt; Java
-			Build Path &gt; Libraries</b>) to identify any internal packages that
-			you want to avoid referencing directly from your code. For example,
-			it's generally a bad idea to depend on any of the vendor-specific
-			packages, like <code>com.ibm.*</code> or <code>com.sun.*</code>, commonly found in the J2SE
-			libraries. Access restrictions are expressed with a combination of
-			inclusion and exclusion rules on build path entries. The pattern
-			syntax follows Ant fileset notation, and matches against the path to
-			the class file. For example, using the pattern <code>com/ibm/**</code> as an
-			exclusion rule would restrict access to all classes in the <code>com.ibm</code>
-			package and its subpackages; using the pattern
-			<code>org/eclipse/**/internal/**</code> as an exclusion rule would catch all
-			classes to internal Eclipse packages. When you provide inclusion
-			rules, everything matched by these rules is ok, and everything else
-			is considered out of bounds.
-			<p>The <b>Java &gt; Compiler &gt; Errors/Warnings &gt; Deprecated
-			and restricted API</b> preference setting lets you control whether errant
-			references are flagged as errors or warnings (they are errors by
-			default for forbidden reference and warnings for discouraged references).</p>
-			<p><img alt="picture of Java Build Path properties dialog"
-				title="Java Build Path properties dialog"
-				src="images/access-restrictionR31.png"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Access rules on libraries and projects</b></p>
-			</td>
-			<td width="70%" valign="top">Access rules can be defined on
-			referenced libraries and projects to explicitly
-			allow/disallow/discourage access to specific types.
-			<p><img alt="picture of Build path wizard with access rules"
-				title="Build path wizard with access rules"
-				src="images/accessrulesR31.png"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-	</tbody>
-</table>
-<!-- *************************************************** -->
-<h2><a name="JavaText">Java Editor</a></h2>
-<table cellpadding="10" cellspacing="0" width="600">
-	<colgroup>
-		<col width="20%" valign="top" align="right">
-		<col width="80%" valign="top" align="left">
-	</colgroup>
-	<tbody>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b> Improved folding icons and captions </b></p>
-			</td>
-			<td valign="top" width="70%">When folding a Java element, the
-			remaining line in the Java editor is the one containing the element's
-			name. The first comment line is displayed for folded Javadoc
-			comments. The new lightweight folding icons shown in the Java editor
-			now differ from the override and implements indicators:
-			<p><img src="images/folding.png" 
-				alt="Picture of new folding artwork" title="Folding Artwork"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>Header comment folding</b></p>
-			</td>
-			<td valign="top" width="70%">Header comments and copyright statements
-			in Java source files can be folded:
-			<p><img src="images/header_folding.png"
-				alt="Screenshot showing a a folded header comment"
-				title="Header comments are now folded per default" width="464"
-				height="93"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>Mark occurrences of inherited methods</b></p>
-			</td>
-			<td style="width: 70%; vertical-align: top">The Java editor can
-			highlight all method declarations that implement or override methods
-			inherited from the selected supertype. See the <b>Java &gt; Editor
-			&gt; Mark Occurrences &gt; Method implementing an interface</b> preference setting.
-			<p><img alt="Picture of mark Implement occurrences"
-				title="Mark Implement Occurrences"
-				src="images/mark-implement-occurrences.png" width="385" height="249"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>New Occurrences Quick Menu</b></p>
-			</td>
-			<td width="70%" valign="top">A context menu with occurrences searches can be opened in the
-			Java editor by pressing <span style="font-weight: bold">Ctrl+Shift+U</span>.
-			<p><strong>Note:</strong> Those who prefer the old behavior can
-			reassign the above key sequence to the "Search All Occurrences in
-			File" command.</p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Highlighting of deprecated class members in the
-			Java editor</b></p>
-			</td>
-			<td width="70%" valign="top">Deprecated class members are marked
-			by advanced highlighting:<br>
-
-			<p><img src="images/deprecated_member_highlighting.png"
-				alt="Highlighting of deprecated members"
-				title="Highlighting of deprecated members"></p>
-			This is configurable on the <b>Java &gt; Editor &gt; Syntax Coloring</b>
-			preference page.
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>References in Javadoc</b></p>
-			</td>
-			<td width="70%" valign="top">Eclipse now recognizes references 
-			to Java elements inside doc comments (i.e., @see, @link,
-			@linkplain, @throws, @exception, @param or @value tags).  This enables
-			hover help and linking to the referenced Java element.
-			<p><img alt="picture of Java editor with hover in Javadoc"
-				title="Java editor with hover in Javadoc"
-				src="images/selectinjavadoc.png"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Improved completion on empty word</b></p>
-			</td>
-			<td width="70%" valign="top">Java code completion on an empty word no
-			longer automatically proposes all types visible at the completion
-			location. You have to type the first character of the type to get a
-			completion proposal.
-			<p><img alt="picture of Java editor showing completion on empty word"
-				title="Java editor showing completion on empty word"
-				src="images/completiononemptyword.png"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>Tool tip description for Javadoc</b></p>
-			</td>
-			<td valign="top" width="70%">
-			<p>The Javadoc which is shown via <b>Edit &gt; Show Tooltip Description (F2)</b>
-			shows up in the SWT Browser widget.</p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Move Lines adjusts indentation</b></p>
-			</td>
-			<td width="70%" valign="top">The <b>Move Lines</b> (<b>Alt+Up/Down</b>)
-			and <b>Copy Lines</b> (<b>Ctrl+Alt+Up/Down</b>) commands
-			automatically adjust the indentation of the selected lines as you
-			move them inside the Java editor.</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>Improved Java properties file editor</b></p>
-			</td>
-			<td width="70%">The editors for Java property files have been greatly improved. They offer syntax
-			highlighting, improved double-clicking behavior, and a separate font
-			preference. The syntax highlighting colors are adjusted from the <b>Java
-			&gt; Properties File Editor</b> preference page. Spell checking is
-			also available, and Quick Fix (Ctrl+1) can be used to fix spelling
-			problems.
-			<p><img alt="Picture of Java Properties File editor"
-				title="Java Properties File Editor"
-				src="images/properties-file-compare.png" width="466" height="473"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>Working with externalized strings</b></p>
-			</td>
-			<td width="70%">When you linger over a key for an externalized string
-			in the Java editor, the associated externalized value is shown in a
-			hover:
-			<p><img alt="Picture of Externalize String hover"
-				title="Externalize String Hover" src="images/nls-hover.png"></p>
-			<p><b>Ctrl+Click</b> on it to navigate directly to the entry in the
-			corresponding Java properties file:</p>
-			<p><img alt="Picture of Ctrl+Click in Java editor"
-				title="Ctrl+Click in Java Editor" src="images/ctrl-click.png"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>Navigate from property key in Properties File
-			editor to its references</b></p>
-			</td>
-			<td width="70%" valign="top">Use <b>Navigate &gt; Open</b> (<b>F3</b>)
-			or <b>Ctrl+click</b> to navigate from a property key in the
-			Properties File editor back to places in the code where the key is
-			referenced.
-			<p><img alt="Picture showing property key hyperlinking"
-				title="Property Key Hyperlinking"
-				src="images/property-key-navigation.png"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>Externalize Strings wizard supports new message
-			bundles</b></p>
-			</td>
-			<td valign="top" width="70%">The Externalize Strings wizard supports Eclipse's
-			string externalization mechanism which is new with this release:
-			<p><img src="images/externalize_strings_wizard.png"
-				alt="Picture of Externalize Strings wizard"
-				title="Externalize Strings wizard" width="413" height="553"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>New API to create code proposals like in the Java
-			editor</b></p>
-			</td>
-			<td width="70%" valign="top">Implementing an editor for a Java-like
-			language? Create your own code assist proposals similar to the
-			ones proposed in the Java editor. Instantiate <code>CompletionProposalCollector</code>
-			to get the same proposals as the Java editor, or subclass it to mix
-			in your own proposals. Use <code>CompletionProposalLabelProvider</code>
-			to get the images and labels right, and sort the proposals using <code>CompletionProposalComparator</code>.
-			<p>Package: <code>org.eclipse.jdt.ui.text.java</code> in the <code>org.eclipse.jdt.ui</code>
-			plug-in.</p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-	</tbody>
-</table>
-<!-- *************************************************** -->
-<h2><a name="JavaUI">General Java Tools</a></h2>
-<table cellpadding="10" cellspacing="0" width="600">
-	<colgroup>
-		<col width="20%" valign="top" align="right">
-		<col width="80%" valign="top" align="left">
-	</colgroup>
-	<tbody>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>New Open Type dialog</b></p>
-			</td>
-			<td valign="top" width="70%">The Java Open Type dialog has been
-			improved in a number of ways:
-			<ul>
-				<li>There is now only a single list to select from.</li>
-				<li>A history of recently opened types shows up first in the dialog;
-				workspace types matching the pattern appear below the separator
-				line.</li>
-				<li>CamelCase pattern matching takes you to a type with fewer
-				keystrokes. For example TZ matches TimeZone or IOOBE matches
-				IndexOutOfBoundsException.</li>
-				<li>The content of the dialog can further be constrained to a working set. The working set can be selected from the dialog's drop down menu.</li>
-			</ul>
-			<p><img src="images/open-type.png" title="" alt="Open type dialog"></p>
-			<p>There are major architectural changes under the hood as well. The
-			types shown in the dialog are now found with a Java search engine
-			query. This nets a saving of 4-6MB on a normal Eclipse development
-			workspace over the memory-hungry approach used previously.</p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>Organizing workspace with many projects</b></p>
-			</td>
-			<td width="70%" valign="top">Use <b>Show &gt; Working Sets</b> in the
-			Package Explorer's view menu to enable a new mode that shows working
-			sets as top level elements. This mode makes it much easier to manage
-			workspaces containing lots of projects.
-			<p><img alt="Package Explorer in Working Set mode"
-				src="images/package-explorer.png"></p>
-			<p>Use <b>Select Working Sets</b> from the Package Explorer's view
-			menu to configure which working sets get shown. The dialog lets you
-			create new Java working sets, define which working sets are shown and
-			in what order. Working sets can also be rearranged directly in the
-			Package Explorer using drag and drop and copy/paste.</p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>Improved source folder page for new Java project
-			wizard</b></p>
-			</td>
-			<td valign="top" width="70%">An improved source folder configuration
-			page in the Java project creation wizard assists you in creating
-			projects from existing source. You can define source folder entries,
-			include/exclude folders directly on the tree, and test the results of
-			your action right away.
-			<p><img alt="New source folder page"
-				src="images/sourcefolderwizard.png"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Sharing Java project settings</b></p>
-			</td>
-			<td width="70%" valign="top">Each Java project can carry custom
-			settings for compiler options and code style. These settings are
-			stored in the project itself, and automatically applied when the
-			project is loaded (or updated) from the repository.
-			<p>Modifying the settings of a Java project via the UI automatically
-			writes the settings to a file in the .settings directory. (The
-			contents of the setting file are auto-generated, and not intended to
-			be edited directly).</p>
-			<p><img src="images/project-settings.png"
-				alt="Shareable compiler settings"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>Navigate to project-specific settings</b></p>
-			</td>
-			<td width="70%">The preference pages for settings that are also
-			configurable on a per-project basis offer a link to the project
-			specific preference page.
-			<p><img alt="Screenshot showing the per project settings link"
-				title="Per project settings link" src="images/perprojectlink.png"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p align="right"><b>Javadoc locations stored in the .classpath file</b></p>
-			</td>
-			<td valign="top">The Javadoc locations that are attached to JAR files
-			and class folders are stored in the .classpath file so they can
-			be shared with the team. When 3.1 starts up, a background job will
-			migrate all the previously internally stored locations to the
-			.classpath file.
-			<p>The Javadoc locations are used by 'Open External Javadoc' (CTRL +
-			F2) and by the Javadoc wizard.</p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>Shortcuts for quick assists and quick fixes<br>
-			</b></p>
-			</td>
-			<td width="70%">Some of the popular quick assists like <strong>Rename
-			In File</strong> and <strong>Assign To Local</strong> can be invoked
-			directly with <b>Ctrl+2&nbsp;R</b> and <b>Ctrl+2&nbsp;L</b>. Check
-			the keys preference page for more quick fixes that support direct
-			invocation.
-			<p><img src="images/quick-assist-shortcuts.png" alt="Keys preference page with quick assist shortcuts"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>New Quick Fixes</b></p>
-			</td>
-			<td width="70%" valign="top">New Quick Fixes have been added for several Java compiler options, for example:
-			<ul>
-				<li>Missing serial version ID: <img src="images/SerialVersionID.png"
-					alt="Screenshot showing serial version quick fixes"
-					title="Serial Version Quick Fixes"></li>
-			</ul>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>New Quick Assists</b></p>
-			</td>
-			<td width="70%" valign="top">Several Quick Assists (Ctrl+1) have been
-			added to the Java Editor:
-			<ul>
-				<li>Invert boolean expressions:<br>
-				<IMG SRC="images/advan-qas1.png" ALT="Picture of invert conditions quick assist">
-		 		</li>
-				<li>Invert a conditional expression:<br>
-				<img alt="Invert condition quick assist"
-					src="images/quick-assist1.png"><br>
-				results in:<br>
-				<img alt="Inverted result" src="images/quick-assist1b.png">
-				</li>
-				<li>Convert conditional expression (<code>?</code> operator) to <code>if-else</code>
-				statement, or vice versa</li>
-				<li>Introduce a new local variable after an instanceof check:<br>
-				<img alt="Assign cast to local before invocation"
-					src="images/quick-assist2.png"><br>
-				results in:<br>
-				<img alt="Result after quick assist invocation"
-					src="images/quick-assist3.png">
-				</li>
-
-				<li>Break out single substring literal:<br>
-				<img alt="Pick out string quick assist"
-					src="images/quick-assist4.png"><br>
-				results in:<br>
-				<img alt="Result of 'Pick out string' quick assist"
-					src="images/quick-assist5.png"></li>
-			</ul>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>Refactoring Undo/Redo available from Edit menu</b></p>
-			</td>
-			<td valign="top" width="70%">
-			<p>Refactoring Undo/Redo is now available from the Edit menu, and the
-			separate Refactor Undo/Redo actions have been removed from the global
-			menu bar. Additionally, refactoring Undo/Redo operations are now
-			integrated with Java editor Undo/Redo, resulting in a more
-			transparent undo story in the editor. For example, a refactoring
-			triggered from within the editor is now undoable in the editor by
-			simply pressing <b>Ctrl+Z</b>.</p>
-			<p><img src="images/undo.png" alt="Undo action in editor context menu"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Member visibility adjustment</b></p>
-			</td>
-			<td width="70%" valign="top">The refactoring commands Move method, Move Member Type to New File, Move Static member,  Pull Up and Push Down automatically change the visibility of referenced
-			fields, methods and types wherever necessary.
-			<p><img src="images/visibility-adjustment.png"
-				alt="Screenshot showing the move member type to new file refactoring"
-				title="Move Member Type to New File Refactoring"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Move method refactoring</b></p>
-			</td>
-			<td width="70%" valign="top">The <b>Refactor &gt; Move</b> command
-			has been extended to better support moving instance
-			methods. New features include:
-			<ul>
-				<li>The option to create a delegate method for compatibility</li>
-				<li>Unreferenced fields can now also be method targets</li>
-			</ul>
-			<p><img src="images/move-refactoring.png"
-				alt="Screenshot showing the move refactoring on an instance method"
-				title="Move Refactoring"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Use Supertype Where Possible refactoring</b></p>
-			</td>
-			<td width="70%" valign="top">The Use Supertype Where Possible
-			refactoring has been extended with a preference that specifies
-			whether type occurrences in <code>instanceof</code> expressions
-			should be updated:
-			<p><img src="images/supertype.png"
-				alt="Screenshot showing the use supertype where possible wizard"
-				title="Use Supertype Where Possible"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>Build path menu in the Package Explorer<br>
-			</b></p>
-			</td>
-			<td valign="top" width="70%">The context menu of the Java Package
-			Explorer has a new 'Build Path' menu entry, offering
-			context-sensitive actions to modify the build path of a Java project.
-			You can add/remove new source folders, archives and libraries, and
-			include/exclude folders and files from a source folder:
-			<p><img alt="Build path menu" src="images/buildpath-menu.png"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>New Eclipse default built-in formatter profile</b></p>
-			</td>
-			<td valign="top" width="70%">Although Eclipse's default 3.0 code
-			formatter profile is named Java Conventions, formatting a file using
-			this profile uses tabs for indentation instead of spaces. A new
-			profile named Eclipse has been added which reflects what the
-			default formatter options have been all along, which uses tabs for
-			indentation. To use true Java Convention settings, simply switch the
-			formatter profile to Java Conventions using <b>Java &gt; Code Style
-			&gt; Formatter</b> preference page.</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="30%">
-			<p align="right"><b>Changing multiple line-wrap settings at once</b></p>
-			</td>
-			<td valign="top" width="70%">The Java code formatter page lets you
-			change multiple line-wrap settings at once by multi-selecting in the
-			tree and then changing settings:
-			<p><img alt="Code Formatter line wrap page"
-				src="images/line-wrap.png"></p>
-			<p>Code formatter settings are on the <b>Java &gt; Code Style &gt; Formatter </b>preference page.</p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td width="30%" valign="top" align="left">
-			<p align="right"><b>Mixed indentation settings</b></p>
-			</td>
-			<td valign="top" width="70%">The Java formatter preferences
-			allows the tab size to be configured independently from the
-			indentation size (see the <b>Indentation</b> tab in your formatter
-			profile):
-			<p><img src="images/mixed-indents.png" alt="Java formatter preference page. Set the indentation preferences on the 'Indentation' tab of the formatter profile."
-				title="The 'Indentation' tab of the formatter profile allows you to separately configure tabulator and indentation settings">
-			</p>
-			<p>For example, set <b>Tab&nbsp;size</b> to <b>8</b> and <b>Indentation&nbsp;size</b>
-			to <b>4</b> to indent your source with four spaces. If you set the <b>Tab&nbsp;policy</b>
-			to <b>Mixed</b>, every two indentation units will be replaced by a
-			tab character.</p>
-			<p>Formatter&nbsp;profiles can be configured on the <b>Java &gt; Code
-			Style &gt; Formatter</b> preference page.</p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="30%">
-			<p align="right"><b>Rerun failed tests first</b></p>
-			</td>
-			<td width="70%" valign="top">There's a new action in the JUnit view
-			that allows you to rerun failing tests before any of the ones that
-			were passing.
-			<p><img alt="Rerun last failed tests" src="images/rerunfailed.png"></p>
-			</td>
-		</tr>
-		<tr>
-			<td colspan="2">
-			<hr>
-			</td>
-		</tr>
-	</tbody>
-</table>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/.classpath b/bundles/org.eclipse.pde.doc.user/.classpath
deleted file mode 100644
index 73fb5bf..0000000
--- a/bundles/org.eclipse.pde.doc.user/.classpath
+++ /dev/null

@@ -1,5 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<classpath>
-    <classpathentry kind="src" path=""/>
-    <classpathentry kind="output" path="bin"/>
-</classpath>

diff --git a/bundles/org.eclipse.pde.doc.user/.project b/bundles/org.eclipse.pde.doc.user/.project
deleted file mode 100644
index 7d8c4b1..0000000
--- a/bundles/org.eclipse.pde.doc.user/.project
+++ /dev/null

@@ -1,22 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>

-<projectDescription>

-	<name>org.eclipse.pde.doc.user</name>

-	<comment></comment>

-	<projects>

-	</projects>

-	<buildSpec>

-		<buildCommand>

-			<name>org.eclipse.pde.ManifestBuilder</name>

-			<arguments>

-			</arguments>

-		</buildCommand>

-		<buildCommand>

-			<name>org.eclipse.pde.SchemaBuilder</name>

-			<arguments>

-			</arguments>

-		</buildCommand>

-	</buildSpec>

-	<natures>

-		<nature>org.eclipse.pde.PluginNature</nature>

-	</natures>

-</projectDescription>


diff --git a/bundles/org.eclipse.pde.doc.user/META-INF/MANIFEST.MF b/bundles/org.eclipse.pde.doc.user/META-INF/MANIFEST.MF
deleted file mode 100644
index 5213b9d..0000000
--- a/bundles/org.eclipse.pde.doc.user/META-INF/MANIFEST.MF
+++ /dev/null

@@ -1,8 +0,0 @@
-Manifest-Version: 1.0
-Bundle-ManifestVersion: 2
-Bundle-Name: %pluginName
-Bundle-SymbolicName: org.eclipse.pde.doc.user; singleton:=true
-Bundle-Version: 3.2.0.qualifier
-Bundle-Vendor: %providerName
-Bundle-Localization: plugin
-Require-Bundle: org.eclipse.help

diff --git a/bundles/org.eclipse.pde.doc.user/aaa-how-to-add-things.txt b/bundles/org.eclipse.pde.doc.user/aaa-how-to-add-things.txt
deleted file mode 100644
index 168e854..0000000
--- a/bundles/org.eclipse.pde.doc.user/aaa-how-to-add-things.txt
+++ /dev/null

@@ -1,18 +0,0 @@
-Last revised March 31, 2004
-(This file is for information only; it is not included in the release.)
-
-To add new plug-ins you need to make changes in several places in
-this doc plug-in:
-
-pdeOptions.txt
-- the plug-in's source folder(s) must be included on the -sourcepath
-- the package names must be included in the (alphabetical) package list at the end of the file
-
-pdeOptions (the Unix version of pdeOptions.txt)
-- same changes as pdeOptions.txt but with ":" path separators
-
-buildDoc.xml
-- add a line in convertSchemaToHtml target to handle a new plug-ins extension point schemas
-
-reference/extension-points/index.html
-- add a line for each extension point

diff --git a/bundles/org.eclipse.pde.doc.user/about.html b/bundles/org.eclipse.pde.doc.user/about.html
deleted file mode 100644
index e336131..0000000
--- a/bundles/org.eclipse.pde.doc.user/about.html
+++ /dev/null

@@ -1,23 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<title>About</title>
-<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
-</head>
-<body lang="EN-US">
-<h2>About This Content</h2>
- 
-<p>February 24, 2005</p>	
-<h3>License</h3>
-
-<p>The Eclipse Foundation makes available all content in this plug-in (&quot;Content&quot;).  Unless otherwise indicated below, the Content is provided to you under the terms and conditions of the
-Eclipse Public License Version 1.0 (&quot;EPL&quot;).  A copy of the EPL is available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
-For purposes of the EPL, &quot;Program&quot; will mean the Content.</p>
-
-<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is being redistributed by another party (&quot;Redistributor&quot;) and different terms and conditions may
-apply to your use of any object code in the Content.  Check the Redistributor's license that was provided with the Content.  If no such license exists, contact the Redistributor.  Unless otherwise
-indicated below, the terms and conditions of the EPL still apply to any source code in the Content.</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/about.ini b/bundles/org.eclipse.pde.doc.user/about.ini
deleted file mode 100644
index 69aeec6..0000000
--- a/bundles/org.eclipse.pde.doc.user/about.ini
+++ /dev/null

@@ -1,23 +0,0 @@
-# about.ini

-# contains information about a feature

-# java.io.Properties file (ISO 8859-1 with "\" escapes)

-# "%key" are externalized strings defined in about.properties

-# This file does not need to be translated.

-

-# Property "aboutText" contains blurb for "About" dialog (translated)

-aboutText=%blurb

-

-# Property "windowImage" contains path to window icon (16x16)

-# needed for primary features only

-

-# Property "featureImage" contains path to feature image (32x32)

-featureImage=eclipse32.png

-

-# Property "aboutImage" contains path to product image (500x330 or 115x164)

-# needed for primary features only

-

-# Property "appName" contains name of the application (translated)

-# needed for primary features only

-

-# Property "welcomePage" contains path to welcome page (special XML-based format)

-# optional


diff --git a/bundles/org.eclipse.pde.doc.user/about.mappings b/bundles/org.eclipse.pde.doc.user/about.mappings
deleted file mode 100644
index 720ca87..0000000
--- a/bundles/org.eclipse.pde.doc.user/about.mappings
+++ /dev/null

@@ -1,6 +0,0 @@
-# about.mappings

-# contains fill-ins for about.properties

-# java.io.Properties file (ISO 8859-1 with "\" escapes)

-# This file does not need to be translated.

-

-0=@build@
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/about.properties b/bundles/org.eclipse.pde.doc.user/about.properties
deleted file mode 100644
index cf37f52..0000000
--- a/bundles/org.eclipse.pde.doc.user/about.properties
+++ /dev/null

@@ -1,24 +0,0 @@
-###############################################################################
-# Copyright (c) 2000, 2005 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-# about.properties
-# contains externalized strings for about.ini
-# java.io.Properties file (ISO 8859-1 with "\" escapes)
-# fill-ins are supplied by about.mappings
-# This file should be translated.
-
-blurb=Eclipse Plug-in Development Environment User Guide\n\
-\n\
-Version: {featureVersion}\n\
-Build id: {0}\n\
-\n\
-(c) Copyright IBM Corp. and others 2000, 2003.  All rights reserved.\n\
-Visit http://www.eclipse.org/pde
-

diff --git a/bundles/org.eclipse.pde.doc.user/book.css b/bundles/org.eclipse.pde.doc.user/book.css
deleted file mode 100644
index a4eedda..0000000
--- a/bundles/org.eclipse.pde.doc.user/book.css
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/build.properties b/bundles/org.eclipse.pde.doc.user/build.properties
deleted file mode 100644
index a98c323..0000000
--- a/bundles/org.eclipse.pde.doc.user/build.properties
+++ /dev/null

@@ -1,12 +0,0 @@
-###############################################################################

-# Copyright (c) 2000, 2005 IBM Corporation and others.

-# All rights reserved. This program and the accompanying materials

-# are made available under the terms of the Eclipse Public License v1.0

-# which accompanies this distribution, and is available at

-# http://www.eclipse.org/legal/epl-v10.html

-#

-# Contributors:

-#     IBM Corporation - initial API and implementation

-###############################################################################

-# use provided build.xml

-custom=true


diff --git a/bundles/org.eclipse.pde.doc.user/build.xml b/bundles/org.eclipse.pde.doc.user/build.xml
deleted file mode 100644
index c6d9bd4..0000000
--- a/bundles/org.eclipse.pde.doc.user/build.xml
+++ /dev/null

@@ -1,73 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>

-<project name="org.eclipse.pde.doc.user" default="build.jars" basedir=".">

-

-	<target name="init">

-		<property name="plugin" value="org.eclipse.pde.doc.user"/>

-		<property name="version.suffix" value="3.1.0"/>

-		<property name="full.name" value="${plugin}_${version.suffix}"/>

-		<property name="temp.folder" value="${basedir}/temp.folder"/>

-		<property name="plugin.destination" value="${basedir}"/>

-		<property name="build.result.folder" value="${basedir}"/>

-	</target>

-

-	<target name="build.update.jar" depends="init">

-		<delete dir="${temp.folder}"/>

-		<mkdir dir="${temp.folder}"/>

-		<antcall target="build.jars"/>

-		<antcall target="gather.bin.parts">

-			<param name="destination.temp.folder" value="${temp.folder}/"/>

-		</antcall>

-		<zip zipfile="${plugin.destination}/${full.name}.jar" basedir="${temp.folder}/${full.name}" filesonly="false"/>

-		<delete dir="${temp.folder}"/>

-	</target>

-

-	<target name="gather.bin.parts" depends="init" if="destination.temp.folder">

-		<ant antfile="buildDoc.xml" />

-		<mkdir dir="${destination.temp.folder}/${full.name}"/>

-		<copy todir="${destination.temp.folder}/${full.name}">

-			<fileset dir="${basedir}" includes="META-INF/,*.properties,*.xml,*.zip,*.html,*.htm,*.png,*.css,index/**,guide/**,tips/**,reference/**,whatsNew/**,images/**" excludes="build.properties,build.xml,buildDoc.xml"/>

-		</copy>

-		<eclipse.versionReplacer path="${destination.temp.folder}/${full.name}" version="${version.suffix}"/>

-	</target>

-

-	<target name="build.jars" depends="init">

-	</target>

-

-	<target name="gather.sources" depends="init" if="destination.temp.folder">

-	</target>

-

-	<target name="build.sources" depends="init">

-	</target>

-

-	<target name="gather.logs" depends="init" if="destination.temp.folder">

-	</target>

-

-	<target name="clean" depends="init">

-		<delete file="${plugin.destination}/${full.name}.jar"/>

-		<delete file="${plugin.destination}/${full.name}.zip"/>

-		<delete dir="${temp.folder}"/>

-	</target>

-

-	<target name="refresh" depends="init" if="eclipse.running">

-		<eclipse.refreshLocal resource="${plugin}" depth="infinite"/>

-	</target>

-

-	<target name="zip.plugin" depends="init">

-		<delete dir="${temp.folder}"/>

-		<mkdir dir="${temp.folder}"/>

-		<antcall target="build.jars"/>

-		<antcall target="build.sources"/>

-		<antcall target="gather.bin.parts">

-			<param name="destination.temp.folder" value="${temp.folder}/"/>

-		</antcall>

-		<antcall target="gather.sources">

-			<param name="destination.temp.folder" value="${temp.folder}/"/>

-		</antcall>

-		<delete>

-			<fileset dir="${temp.folder}" includes="**/*.bin.log"/>

-		</delete>

-		<zip zipfile="${plugin.destination}/${full.name}.zip" basedir="${temp.folder}" filesonly="true"/>

-		<delete dir="${temp.folder}"/>

-	</target>

-

-</project>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/buildDoc.xml b/bundles/org.eclipse.pde.doc.user/buildDoc.xml
deleted file mode 100644
index b62c2cf..0000000
--- a/bundles/org.eclipse.pde.doc.user/buildDoc.xml
+++ /dev/null

@@ -1,85 +0,0 @@
-<project name="PDE Doc ISV Build" default="all"  basedir="." >
-
-	<target name="init">
-		<available file="${basedir}/index" property="index.present"/>
-	</target>
-
-	<target name="all" depends="init" unless="index.present">
-		<antcall target="convertSchemaToHtml" />
-		<antcall target="generateJavadoc" />
-		<antcall target="build.index" />
-		<!--antcall target="createDocZip" /-->
-	</target>
-
-	<target name="build.index" description="Builds search index for the plug-in: org.eclipse.pde.doc.user." if="eclipse.running">
-		<help.buildHelpIndex manifest="${basedir}/plugin.xml" destination="${basedir}"/>
-	</target>
-
-	<target name="convertSchemaToHtml" if="eclipse.running">
-		<property name="dest" value="reference/extension-points" />
-		<record name="${basedir}/pdeconvert.txt" action="start"/>
-
-		<pde.convertSchemaToHTML manifest="../org.eclipse.pde.core/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.pde.build/plugin.xml" destination="${dest}" />
-    	<pde.convertSchemaToHTML manifest="../org.eclipse.pde.ui/plugin.xml" destination="${dest}" />
-
-		<record name="${basedir}/pdeconvert.txt" action="stop"/>
-	</target>
-
-	<target name="getJavadocPath">
-		<available file="${java.home}/../bin/javadoc.exe" property="javadoc" value="${java.home}/../bin/javadoc.exe"/>
-		<available file="${java.home}/../bin/javadoc" property="javadoc" value="${java.home}/../bin/javadoc" />
-	</target>
-
-
-	<target name="generateJavadoc" depends="getJavadocPath" if="javadoc">
-
-		<!--HACK to ensure the jdt doc is built before PDE - call to this script should be moved to build.jars target-->
-		<available file="../org.eclipse.jdt.doc.isv/index" property="jdt.index.present"/>
-		<antcall target="buildJdtDoc" />
-
-		<condition property="optionsFile" value="pdeOptions">
-			<os family="unix" />
-		</condition>
-		<condition property="optionsFile" value="pdeOptions.txt">
-			<os family="windows" />
-		</condition>
-
-		<replace file="${basedir}/${optionsFile}" token="@rt@" value="${bootclasspath}" />
-
-
-		<!--scrub isv plugin directories of any preexisting api doc content-->
-		<delete dir="reference/api"/>
-		<mkdir dir="reference/api"/>
-
-		<exec dir="." executable="${javadoc}" output="doc.bin.log">
-			<arg line="@${basedir}/${optionsFile} -J-Xmx1000M" />
-		</exec>
-	</target>
-
-	<target name="buildJdtDoc" unless="jdt.index.present">
-		<ant antfile="buildDoc.xml" dir="../org.eclipse.jdt.doc.isv" />
-	</target>
-
-	<target name="createDocZip">
-		<zip zipfile="${basedir}/doc.zip"
-		basedir="${basedir}"
-		includes="schema.css, book.css,  notices.html, about.html, guide/**, tips/**, reference/**, whatsNew/**, images/**"
-	/>
-	</target>
-
-</project>
-
-
-
-
-
-
-
-
-
-
-
-
-
-

diff --git a/bundles/org.eclipse.pde.doc.user/contexts_PDE.xml b/bundles/org.eclipse.pde.doc.user/contexts_PDE.xml
deleted file mode 100644
index 09de0f5..0000000
--- a/bundles/org.eclipse.pde.doc.user/contexts_PDE.xml
+++ /dev/null

@@ -1,568 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-
-<!-- Actions -->
-	<context id="open_manifest">
-		<description>This action opens the manifest files contained in the selected plug-in project(s).</description>
-	</context>
-	<context id="organize_manifest">
-		<description>This action organizes and cleans up the manifest files contained in the selected plug-in project(s).</description>
-	</context>
-	<context id="update_classpath">
-		<description>PDE computes the classpath of this project by looking for dependencies in the workspace and enabled external plug-ins and fragments.</description>
-		<topic label="Dynamic classpaths FAQ" href="guide/dynamic-classpaths.htm"/>
-		<topic label="Concepts" href="guide/pde_configuring.htm"/>
-	</context>
-	<context id="open_dependencies">
-		<description>This command opens the Dependencies view to show all the plug-ins needed to run the selected plug-in.</description>
-		<topic label="Dependencies page" href="guide/pde_manifest_dependencies.htm"/>
-		<topic label="Concepts" href="guide/pde_configuring.htm"/>
-	</context>	
-	<context id="find_references">
-		<description>This command searches for all the plug-ins that directly depend on the selected plug-in and all the fragments which target it.</description>
-		<topic label="Dependencies page" href="guide/pde_manifest_dependencies.htm"/>
-		<topic label="Fragments" href="guide/pde_fragment.htm"/>
-	</context>
-	<context id="create_plugin_jars">
-		<description>This command builds an Ant script which can then be used to build an executable version of the plug-in.</description>
-		<topic label="Generating Ant Scripts" href="guide/pde_feature_generating_ant.htm"/>
-		<topic label="Build configuration" href="guide/pde_feature_generating_build.htm"/>
-		<topic label="Deploying a plug-in" href="guide/pde_deploy.htm"/>
-	</context>
-	<context id="create_fragment_jars">
-		<description>This command builds an Ant script which can then be used to build an executable version of the fragment.</description>
-		<topic label="Generating Ant Scripts" href="guide/pde_feature_generating_ant.htm"/>
-		<topic label="Build configuration" href="guide/pde_feature_generating_build.htm"/>
-		<topic label="Deploying a plug-in" href="guide/pde_deploy.htm"/>
-	</context>
-	<context id="create_feature_jars">
-		<description>This command builds an Ant script which can then be used to build a feature.</description>
-		<topic label="Features" href="guide/pde_features.htm"/>
-		<topic label="Generating Ant Scripts" href="guide/pde_feature_generating_ant.htm"/>
-		<topic label="Build configuration" href="guide/pde_feature_generating_build.htm"/>
-	</context>	
-	<context id="migrate_action">
-		<description>This command migrates pre-3.0 plug-ins and fragments to comply with Eclipse 3.0 guidelines.</description>
-		<topic label="FAQ" href="../org.eclipse.platform.doc.isv/porting/faq.html" />
-		<topic label="Incompatibilities" href="../org.eclipse.platform.doc.isv/porting/incompatibilities.html" />
-	</context>	
-	<context id="build_site">
-		<description>This command builds all the features and plug-ins contained in this site.</description>
-		<topic label="Update Sites" href="guide/pde_sites.htm"/>
-		<topic label="Building plug-ins and features using update site editor" href="guide/pde_site_building.htm"/>
-	</context>	
-	<context id="preview_schema">
-		<description>This command transforms and renders the schema into HTML format.</description>
-		<topic label="Creating an extension point schema" href="guide/pde_schema.htm"/>
-		<topic label="Extension point schema editor" href="guide/pde_schema_editor.htm"/>
-	</context>			
-    <context id="history_action">
-        <description>Choose this previously shown plug-in dependency, to open it again.</description>
- 
-    </context>
-    <context id="history_list_action">
-        <description>Choose to open a dialog with all previously shown plug-in dependencies.</description>
-    </context>
-    
-<!-- Dialogs -->
- 	<context id="fragment_add_target">
- 		<description>This wizard allows you to select the target plug-in for your fragment.</description>
-		<topic label="Fragments" href="guide/pde_fragment.htm"/>
-		<topic label="Fragment example" href="guide/pde_fragment_example.htm"/>
-	</context>
-	<context id="schema_type_restriction">
-		<description>This wizard allows you to define the possible values for the selected attribute.</description>
-		<topic label="Extension point schema" href="guide/pde_schema.htm"/>
-		<topic label="Extension point schema editor" href="guide/pde_schema_editor.htm"/>
-		<topic label="Using extension point schema" href="guide/pde_schema_using.htm"/>
-	</context>
-	<context id="search_page">
-		<description>On this page, you can search for references to and declarations of plug-ins, fragments and extension points.
-The search can be extended beyond workspace resources to include external plug-ins. </description>
-	</context>
-	<context id="launcher_basic">
-		<description>This page allows you to set the basic program arguments to run the configuration.</description>
-		<topic label="Running a plug-in" href="guide/pde_running.htm"/>
-	</context>
-	<context id="launcher_advanced">
-		<description>This page allows you to run your configuration with only a subset of the plug-ins.</description>
-		<topic label="Choosing plug-ins to run" href="guide/pde_running_plugins.htm"/>
-	</context>
-	<context id="launcher_tracing">
-		<description>This page allows you to use tracing flags that will cause tracing information to be printed to the standard output (or the console view) when you run the configuration.</description>
-		<topic label="Running with tracing" href="guide/pde_running_tracing.htm"/>
-	</context>
-	<context id="launcher_configuration">
-		<description>This page allows you to specify the plug-ins that are to be automatically installed, and optionally started, by the runtime.</description>
-		<topic label="Running a plug-in" href="guide/pde_running.htm"/>
-		<topic label="Choosing plug-ins to run" href="guide/pde_running_plugins.htm"/>
-	</context>
-    <context id="history_list_dialog">
-        <description>A dialog for re-opening previously viewed plug-in dependencies.</description>
-    </context>
-    	
-<!-- Editors -->
-
-	<context id="manifest_source_page">
-		<description>This page allows you to edit the file content directly.</description>
-		<topic label="Source page" href="guide/pde_manifest_source.htm"/>
-	</context>
-	<context id="manifest_plugin_overview">
-		<description>The Overview page shows you the plug-in at a glance.</description>
-		<topic label="Plug-in manifest editor" href="guide/pde_manifest.htm"/>
-		<topic label="Overview page" href="guide/pde_manifest_overview.htm" />
-		<topic label="Creating a plug-in project" href="guide/pde_creating.htm"/>
-	</context>
-	<context id="manifest_plugin_dependencies">
-		<description>The Dependencies page shows the dependencies that your plug-in has on other plug-ins.</description>
-		<topic label="Dependencies page" href="guide/pde_manifest_dependencies.htm"/>
-		<topic label="Creating a plug-in project" href="guide/pde_creating.htm"/>
-	</context>
-	<context id="manifest_plugin_runtime">
-		<description>The Runtime page shows information about the plug-in's runtime libraries and OSGi plug-in activation settings.</description>
-		<topic label="Runtime page" href="guide/pde_manifest_runtime.htm" />
-	</context>
-	<context id="manifest_plugin_extensions">
-		<description>The Extensions page shows all the extensions used by your plug-in.</description>
-		<topic label="Extensions page" href="guide/pde_manifest_extensions.htm" />
-	</context>
-	<context id="manifest_plugin_ext_points">
-		<description>The Extension points page shows all the extension points declared by the plug-in.</description>
-		<topic label="Extension points page" href="guide/pde_manifest_extensionpoints.htm" />
-		<topic label="Extension point schema" href="guide/pde_schema.htm"/>
-		<topic label="Extension point schema editor" href="guide/pde_schema_editor.htm"/>
-		<topic label="Using extension point schema" href="guide/pde_schema_using.htm"/>
-	</context>
-	<context id="manifest_fragment_overview">
-		<description>The Overview page shows you the fragment at a glance.</description>
-		<topic label="Plug-in manifest editor" href="guide/pde_manifest.htm"/>
-		<topic label="Overview page" href="guide/pde_manifest_overview.htm" />
-		<topic label="Fragments" href="guide/pde_fragment.htm"/>
-		<topic label="Fragment example" href="guide/pde_fragment_example.htm"/>
-	</context>
-	<context id="manifest_fragment_dependencies">
-		<description>The Dependencies page shows the dependencies that your fragment has on other plug-ins.</description>
-		<topic label="Dependencies page" href="guide/pde_manifest_dependencies.htm"/>
-		<topic label="Dynamic classpaths FAQ" href="guide/dynamic-classpaths.htm"/>
-		<topic label="Fragment example" href="guide/pde_fragment_example.htm"/>
-	</context>
-	<context id="manifest_fragment_runtime">
-		<description>The Runtime page shows information about the fragment's runtime libraries.</description>
-		<topic label="Runtime page" href="guide/pde_manifest_runtime.htm" />
-	</context>
-	<context id="manifest_fragment_extensions">
-		<description>The Extensions page shows all the extensions used by your fragment.</description>
-		<topic label="Extensions page" href="guide/pde_manifest_extensions.htm" />
-	</context>
-	<context id="manifest_fragment_ext_points">
-		<description>The Extension points page shows all the extension points declared by the fragment.</description>
-		<topic label="Extension points page" href="guide/pde_manifest_extensionpoints.htm" />
-		<topic label="Extension point schema" href="guide/pde_schema.htm"/>
-		<topic label="Extension point schema editor" href="guide/pde_schema_editor.htm"/>
-		<topic label="Using extension point schema" href="guide/pde_schema_using.htm"/>
-	</context>
-	<context id="build_page">
-		<description>This editor is used to edit the build configuration for a plug-in, fragment or a feature.</description>
-		<topic label="Build configuration" href="guide/pde_feature_generating_build.htm"/>
-		<topic label="Build Properties Editor" href="guide/pde_build_editor.htm"/>
-	</context>
-	<context id="schema_editor_main">
-		<description>This editor creates a schema for an extension point, to which all extensions extending this point must conform.</description>
-		<topic label="Extension point schema" href="guide/pde_schema.htm"/>
-		<topic label="Extension point schema editor" href="guide/pde_schema_editor.htm"/>
-		<topic label="Using extension point schema" href="guide/pde_schema_using.htm"/>
-	</context>
-	<context id="schema_editor_doc">
-		<description>Documentation for the use of this extension point is entered on this page.</description>
-		<topic label="Extension point schema" href="guide/pde_schema.htm"/>
-		<topic label="Extension point schema editor" href="guide/pde_schema_editor.htm"/>
-		<topic label="Using extension point schema" href="guide/pde_schema_using.htm"/>
-	</context>
-	<context id="manifest_feature_overview">
-		<description>This page shows general information about the feature.</description>
-		<topic label="Feature manifest editor" href="guide/pde_feature_manifest.htm"/>
-		<topic label="Features" href="guide/pde_features.htm"/>
-		<topic label="Synchronizing versions" href="guide/pde_feature_synchronizing.htm"/>
-		<topic label="Deploying a Feature" href="guide/pde_feature_generating.htm"/>
-	</context>
-	<context id="manifest_feature_info">
-		<description>This page is used to edit the required description, license and copyright information.</description>
-		<topic label="Feature manifest editor" href="guide/pde_feature_manifest.htm"/>
-	</context>
-	<context id="manifest_feature_content">
-		<description>This page shows the list of plug-ins and fragments that are included in the feature.</description>
-		<topic label="Feature manifest editor" href="guide/pde_feature_manifest.htm"/>
-		<topic label="Synchronizing versions" href="guide/pde_feature_synchronizing.htm"/>
-	</context>
-	<context id="manifest_feature_advanced">
-		<description>This page lists all features included in this feature</description>
-		<topic label="Feature manifest editor" href="guide/pde_feature_manifest.htm"/>
-	</context>
-	<context id="manifest_feature_dependencies">
-		<description>This page lists all plug-ins and features that need to be installed before installing this feature. </description>
-	</context>
-	<context id="manifest_feature_installation">
-		<description>This page details installation options</description>
-	</context>	
-	<context id="feature_synchronize_versions">
-		<description>The versions of the plug-ins and fragments should be synchronized with that of the packaged feature.</description>
-		<topic label="Synchronizing versions" href="guide/pde_feature_synchronizing.htm"/>
-	</context>
-	
-	// Site Editor
-	<context id="manifest_site_overview" >
-		<description>This page shows the general information about the update site.</description>
-		<topic label="Setting up an update site project" href="guide/pde_site_setup.htm"/>
-		<topic label="Building plug-ins and features using update site editor" href="guide/pde_site_building.htm"/>
-	</context>
-	<context id="manifest_site_build">
-		<description>This page allows you to configure how this site will be built from features and plug-ins in the workspace.</description>
-		<topic label="Setting up an update site project" href="guide/pde_site_setup.htm"/>
-		<topic label="Building plug-ins and features using update site editor" href="guide/pde_site_building.htm"/>
-	</context>
-	<context id="manifest_site_features">
-		<description>This page lists all the features visible to the user when connecting to this site.</description>
-		<topic label="Setting up an update site project" href="guide/pde_site_setup.htm"/>
-		<topic label="Building plug-ins and features using update site editor" href="guide/pde_site_building.htm"/>
-	</context>
-	<context id="manifest_site_archives">
-		<description>This page lists all the archive mappings in this site.</description>
-		<topic label="Setting up an update site project" href="guide/pde_site_setup.htm"/>
-		<topic label="Building plug-ins and features using update site editor" href="guide/pde_site_building.htm"/>
-	</context>
-	<context id="new_category_def_dialog">
-		<description>This dialog defines a new or edits an existing feature category definition.</description>
-	</context>
-		
-<!-- Children of the PDEFormPage -->
-
-	<context id="branding_page">
-		<description>Information on this page controls branding of the product.</description>
-	</context>
-	<context id="configuration_page">
-		<description>Select plug-ins or features belonging to the product.  Optionally specify custom config.ini file, or program arguments.</description>
-	</context>
-	<context id="overview_page">
-		<description>Specify product and application IDs</description>
-	</context>
-
-
-<!-- end Children of the PDEFormPage -->
-
-
-<!-- Preference pages -->
-   <context id="main_preference_page" >
-      <description>This page allows you to set Plug-in Development Environment general settings.</description>
-   </context>
-   
-   <context id="build_options_preference_page" >
-      <description>This page allows you to set the default values for some of the variables used when running a plug-in Ant build script.</description>
-   </context>
-     
-   <context id="compilers_preference_page" >
-      <description>This page allows you to specify the behavior of the various manifest compilers.</description>
-	  <topic label="Source page" href="guide/pde_manifest_source.htm"/>
-   </context>
-   
-   <context id="editor_preference_page" >
-      <description>This page allows you to configure behavior and presentation of PDE multi-page editors.</description>
-	<topic label="Plug-in manifest editor" href="guide/pde_manifest.htm"/>
-	<topic label="Feature manifest editor" href="guide/pde_feature_manifest.htm"/>
-	<topic label="Extension point schema editor" href="guide/pde_schema_editor.htm"/>
-   </context>
-   
-   <context id="source_preference_page" >
-      <description>This page allows you to configure source code locations.
-When attaching source archives to Java libraries, PDE first looks in plug-ins. If not found, the search is extended to source locations. 
-Source locations can be provided by plug-ins that are used to carry source code (in SDKs). They can also be defined by users. 
-Unchecked source locations will be ignored by PDE.</description>
-   </context>
-   
-    <context id="target_environment_preference_page" >
-      <description>This page allows you to set the target environment for the plug-ins you develop.</description>
- 		<topic label="Running a plug-in" href="guide/pde_running.htm"/>
-		<topic label="Deploying a plug-in" href="guide/pde_deploy.htm"/>
-		<topic label="Deploying a feature" href="guide/pde_feature_generating.htm"/>
-   </context>
-   
-   <context id="target_platform_preference_page" >
-      <description>This page allows you to configure the target platform that will be used to develop and test against. 
-In cases where a plug-in with the same id exists both in the workspace and in the target platform, the workspace copy will take precedence.</description>
-	<topic label="Concepts" href="guide/pde_configuring.htm"/>
-	<topic label="Dynamic classpaths FAQ" href="guide/dynamic-classpaths.htm"/>
-   </context>
-
-<!-- Property pages -->	
-    <context id="selfhosting_property_page" >
-      <description>This page allows you to exclude certain class folders from the runtime workbench.</description>
- 	  <topic label="Running a plug-in" href="guide/pde_running.htm"/>
-	  <topic label="Choosing plug-ins to run" href="guide/pde_running_plugins.htm"/>
-   </context>
-
-   <context id="compilers_property_page" >
-      <description>This page allows you to specify the behavior of the various manifest compilers.</description>
-	  <topic label="Source page" href="guide/pde_manifest_source.htm"/>
-   </context>
-   
-<!-- Views -->	
-	<context  id="plugins_view">
-		<description>The Plug-in View show the plug-ins and fragments that will be passed to the runtime workbench when running or debugging.
-If simple self-hosting is used, the view allows you to browse external plug-ins that are not part of the workspace.</description>
-	    <topic label="Concepts" href="guide/pde_configuring.htm"/>
-	 </context>
-	 <context id="dependencies_view">
-	 	<description>The Dependencies view shows all the plug-ins required to run the selected plug-in.</description>
-		<topic label="Dependencies page" href="guide/pde_manifest_dependencies.htm"/>
-		<topic label="Running a plug-in" href="guide/pde_running.htm"/>
-	</context>
-	<context id="registry_view">
-		<description>The Plug-in Registry view shows a read-only view of the plug-in registry of the running platform.</description>
-	</context>
-	<context id="log_view">
-		<description>The log view captures warnings and internal errors thrown by the internal platform or your code.</description>
-		<topic label="Preparing the workbench" href="guide/pde_setup.htm"/>
-	</context>
-		
-		
-<!-- Wizard pages -->
-	<context id="new_project_structure_page">
-		<description>This wizard helps you create a new plug-in project.
-If the plug-in is to contain resources only, create a simple project.
-Otherwise, create a Java project.</description>
-		<topic label="Creating a plug-in project" href="guide/pde_creating.htm"/>
-	</context>
-	<context id="new_project_required_data">
-		<description>Data entered on this page is used to customize the generated manifest file and top level plug-in Java class.</description>
-		<topic label="Creating a plug-in project" href="guide/pde_creating.htm"/>
-	</context>
-	<context id="new_project_code_gen_page">
-		<description>For a quick start, use the code generation wizards to create a plug-in project containing a working extension.
-You can customize a plug-in to contain any combination of the available extension templates by choosing the 'Custom Plug-in Wizard' option.</description>
-		<topic label="Creating a plug-in project" href="guide/pde_creating.htm"/>
-	</context>
-	
-	<context id="new_fragment_structure_page">
-		<description>This wizard helps you create a new fragment project.
-If the fragment is to contain resources only, create a simple project.
-Otherwise, create a Java project.</description>
-		<topic label="Fragments" href="guide/pde_fragment.htm"/>
-		<topic label="Fragment example" href="guide/pde_fragment_example.htm"/>
-	</context>
-	<context id="new_fragment_required_data">
-		<description>This page specifies the fragment's target plug-in and other data required to generate the fragment's manifest file.</description>
-		<topic label="Fragments" href="guide/pde_fragment.htm"/>
-		<topic label="Fragment example" href="guide/pde_fragment_example.htm"/>
-	</context>	
-	
-	<context id="new_library_plugin_jar_page">
-		<description>This wizard helps you create a new plug-in project from existing JAR archives.
-Use this page to specify archives to be included in the plug-in.
-The buttons allow adding JAR archives from the workspace or the file system.</description>
-		<topic label="Creating a plug-in project" href="guide/pde_creating.htm"/>
-	</context>
-
-	<context id="new_library_plugin_structure_page">
-		<description>This wizard helps you create a new plug-in project from existing JAR archives.
-Data entered on this page is used to customize the generated manifest file.</description>
-		<topic label="Creating a plug-in project" href="guide/pde_creating.htm"/>
-	</context>
-
-	<context id="new_feature_main">
-		<description>This wizard creates a new feature project that can be used to package plug-ins.</description>	
-		<topic label="Features" href="guide/pde_features.htm"/>
-		<topic label="Setting up a feature project" href="guide/pde_feature_setup.htm"/>
-	</context>
-	<context id="new_feature_data">
-		<description>This page specifies basic data about the feature.</description>	
-		<topic label="Features" href="guide/pde_features.htm"/>
-		<topic label="Setting up a feature project" href="guide/pde_feature_setup.htm"/>
-	</context>
-	<context id="new_feature_referenced_plugins">
-		<description>The plug-ins and fragments selected on this page will be packaged in the feature.</description>
-		<topic label="Features" href="guide/pde_features.htm"/>
-		<topic label="Setting up a feature project" href="guide/pde_feature_setup.htm"/>
-	</context>
-	
-	<context id="new_patch_main">
-		<description>This wizard creates a patch to an existing feature.</description>	
-		<topic label="Features" href="guide/pde_features.htm"/>
-		<topic label="Setting up a feature project" href="guide/pde_feature_setup.htm"/>
-	</context>
-	<context id="new_patch_data">
-		<description>This page specifies basic data about the patch and the feature it targets.</description>	
-		<topic label="Features" href="guide/pde_features.htm"/>
-		<topic label="Setting up a feature project" href="guide/pde_feature_setup.htm"/>
-	</context>
-	<context id="new_patch_referenced_plugins">
-		<description>The plug-ins and fragments selected on this page will be packaged in the patch.</description>
-		<topic label="Features" href="guide/pde_features.htm"/>
-		<topic label="Setting up a feature project" href="guide/pde_feature_setup.htm"/>
-	</context>
-	
-	<context id="new_site_main">
-		<description>This wizard creates an update site project where you can publish features for the Update Manager to find.</description>
-		<topic label="Update Sites" href="guide/pde_sites.htm"/>
-		<topic label="Setting up an update site project" href="guide/pde_site_setup.htm"/>
-	</context>
-	
-	<context id="new_schema">
-		<description>All extensions that extend the specified extension point will be validated against this schema.</description>
-		<topic label="Extension point schema" href="guide/pde_schema.htm"/>
-		<topic label="Extension point schema editor" href="guide/pde_schema_editor.htm"/>
-		<topic label="Using extension point schema" href="guide/pde_schema_using.htm"/>
-	</context>
-	
-	<context id="converted_projects">
-		<description>Select Java projects to which you want to add PDE capabilities.
-If the selected project does not contain a manifest file, PDE will generate a generic one.</description>
-		<topic label="Converting existing projects" href="guide/pde_convert.htm"/>
-	</context>	
-
-	<context id="migrate_3_0">
-		<description>All pre-3.0 plug-ins must be migrated using this wizard to update their list of dependencies and add the 3.0 processing instruction.</description>
-		<topic label="FAQ" href="../org.eclipse.platform.doc.isv/porting/faq.html" />
-		<topic label="Incompatibilities" href="../org.eclipse.platform.doc.isv/porting/incompatibilities.html" />
-	</context>	
-	
-	<context id="plugin_import_first_page">
-		<description>This wizard allows you to import plug-ins into the workspace.  Source code, if found, will be attached to JARs.
-Importing plug-ins as binary projects with links is the fastest.  It will not import these plug-ins physically into the workspace.
-It will instead create links to those plug-ins on disk.  Note that deleting these binary linked projects will not delete the files that they map to on disk. 
-		</description>
-	</context>
-	<context id="plugin_import_second_page">
-		<description>This list shows the plug-ins and fragments found in the location specified on the previous page.</description>
-	</context>
-	<context id="plugin_import_express_page">
-		<description>For each one of the selected plug-ins, the wizard will import all its pre-requisites that do not already exist as shared projects in the workspace.</description>
-	</context>
-	
-	<context id="feature_import_first_page">
-		<description>This page defines the location from which the features will be imported into the workspace. This wizard
-should only be used in conjunction with feature-based self-hosting.</description>	
-	</context>
-	<context id="feature_import_second_page">
-		<description>This list shows the features found in the location specified on the previous page.</description>
-	</context>
-	
-	<context id="template_selection">
-		<description>Customize the plug-in by choosing one or more template extensions.</description>
-	</context>		
-	<context id="template_editor">
-		<description>This template creates a sample XML editor with basic editing capabilities, syntax highlighting, etc.</description>
-	</context>
-	<context id="template_hello_world">
-		<description>This template creates a sample action set that adds a menu to the menu bar and a button to the toolbar.</description>
-	</context>
-	<context id="template_help">
-		<description>This template creates a sample Help Table of Contents.</description>
-	</context>
-	<context id="template_intro">
-		<description>This template creates a sample intro for product.</description>
-	</context>
-	<context id="template_multipage_editor">
-		<description>This template creates a multi-page editor that works on files with the chosen extension.</description>
-	</context>
-	<context id="template_new_wizard">
-		<description>This template creates a wizard that can create a new file in the workspace</description>
-	</context>
-	<context id="template_popup_menu">
-		<description>This template adds a popup menu to the specified target object.
- The menu will appear in all views where an object of the specified type is selected.</description>
-	</context>
-	<context id="template_preference_page">
-		<description>This template creates a page that is contributed to the Preferences.</description>
-	</context>
-	<context id="template_property_page">
-		<description>This template adds a property page to a resource that matches the specified filter, and will appear in the Properties dialog for that resource.</description>
- 	</context>
- 	<context id="template_view">
- 		<description>This template creates a workbench view and is contributed to the Workbench by creating a category.</description>
- 	</context>
- 	<context id="template_universal_welcome">
- 		<description>This template creates a contribution to the Universal Welcome in the section of your choice. For this to work, your product must use Universal Welcome.</description>
- 	</context>
- 	<context id="template_builder">
- 		<description>This template creates an incremental project builder and a project nature.  A popup action on the project configures or unconfigures the nature.</description>
- 	</context>
- 	<context id="manifest_add_dependencies">
- 		<description>This wizard allows you to add plug-ins as dependencies to your plug-in.
- Use the filter to accelerate your search for the plug-ins.</description>
-		<topic label="Dependencies page" href="guide/pde_manifest_dependencies.htm"/>
-		<topic label="Creating a plug-in project" href="guide/pde_creating.htm"/>
-	</context>
-	<context id="add_extensions_main">
-		<description>This wizard allows you to add an extension to one of the available extension points.
- You can also create a working template extension from the list of available templates.</description>
- 	</context>
- 	<context id="add_extensions_schema_based">
- 		<description>This wizard allows you to extend one of the available extension points.  To be able to extend an extension point, your plug-in has to import the plug-in where the point is declared.</description>
-		<topic label="Dependencies page" href="guide/pde_manifest_dependencies.htm"/>
-		<topic label="Extension point schema" href="guide/pde_schema.htm"/>
- 	</context>
- 	<context id="java_attribute_wizard_page">
- 		<description>This wizard allows you to create a new Java class or select an existing one.</description>
- 	</context>
-	<context id="feature_portability_wizard">
-		<description>This wizard allows you to add constraints to ensure that your feature is not installed or shown in a context that does not match these constraints.</description>
-		<topic label="Feature manifest editor" href="guide/pde_feature_manifest.htm"/>
-	</context>		
-	
-	<context id="plugin_export_wizard" >
-		<description>This wizard builds and exports the selected plug-ins and/or fragments into the specified location.</description>
-		<topic label="Deploying a plug-in" href="guide/pde_deploy.htm"/>
-	</context>
-	<context id="feature_export_wizard">
-		<description>This wizard builds and exports the selected features and the associated plug-ins into the specified location.</description>
-		<topic label="Deploying a feature" href="guide/pde_feature_generating.htm"/>
-	</context>
-	
-	<context id="plugins_container_page">
-		<description>This page shows you the actual classpath entries that are managed by this dynamic classpath container. In case one of the library entries does not have source associated, you can add source by selecting 'Attach Source...' button.</description>
-		<topic label="Dynamic classpaths FAQ" href="guide/dynamic-classpaths.htm"/>
-	</context>		
- 	
- 	<!-- new help contents, need to be completed -->
- 	<context id="advanced_plugin_export_page">
-		<description>This page allows signing the JARs for added security.
-If present, the JNLP option allows generation of manifests for Java Web Start deployment.</description>
-	</context>
-	<context id="cross_platform_export_page">
-		<description>When exporting for multiple platforms, select the desired target platforms on this page.  A directory will be created for each selection.</description>
-	</context>
-	<context id="library_plugin_jars">
-		<description>Add JAR archives to include in the new plug-in.  JAR files can be imported from existing workspace projects, or external directories. </description>
-	</context>
-	<context id="plugin_working_set">
-		<description>Create a new working set by selecting plug-ins or fragments that will belong to it.</description>
-	</context>
-	<context id="product_definitions_wizard_page">
-		<description>This wizard creates a new product extension.  A product must be assoicated with an application.</description>
-	</context>
-	<context id="project_names_page">
-		<description>Specify project name.</description>
-	</context>
-	<context id="required_plugins_container_page">
-		<description>The Plug-in Dependencies container is a read-only container managed by PDE.  This page shows the classpath entries that the container resolves to for this particular plug-in project.</description>
-		<topic label="Dynamic classpaths FAQ" href="guide/dynamic-classpaths.htm"/>
-		<topic label="Access Restrictions" href="guide/restrictions.htm"/>
-	</context>
-	<context id="review_page">
-		<description>Review details of the selected sample.</description>
-	</context>
-	<context id="selection_page">
-		<description>Select the samples to create.</description>
-	</context>
- 	
- 	
-<!-- Wizards -->
-
-
-<!-- Editor Outline -->
-	<context id="outline_sort_action">
-		<description>This action sorts elements in the Outline View.</description>
-	</context>		
-
-</contexts>
-

diff --git a/bundles/org.eclipse.pde.doc.user/cpy.png b/bundles/org.eclipse.pde.doc.user/cpy.png
deleted file mode 100644
index a0f8775..0000000
--- a/bundles/org.eclipse.pde.doc.user/cpy.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/eclipse32.png b/bundles/org.eclipse.pde.doc.user/eclipse32.png
deleted file mode 100644
index 4983d64..0000000
--- a/bundles/org.eclipse.pde.doc.user/eclipse32.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/book.css b/bundles/org.eclipse.pde.doc.user/guide/book.css
deleted file mode 100644
index 3fcb62a..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/book.css
+++ /dev/null

@@ -1,106 +0,0 @@
-P.Code {

-	display: block;

-	text-align: left;

-	text-indent: 0.00pt;

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 15pt;

-	font-size: 10.000000pt;

-	font-weight: normal;

-	font-style: normal;

-	color: #4444CC;

-	text-decoration: none;

-	vertical-align: baseline;

-	text-transform: none;

-	font-family: "Courier New";

-}

-H6.CaptionFigColumn {

-	display: block;

-	text-align: left;

-	text-indent: 0.000000pt;

-	margin-top: 3.000000pt;

-	margin-bottom: 11.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 0.000000pt;

-	font-size: 9.000000pt;

-	font-weight: normal;

-	font-style: Italic;

-	color: #000000;

-	text-decoration: none;

-	vertical-align: baseline;

-	text-transform: none;

-	font-family: "Arial";

-}

-P.Note {

-	display: block;

-	text-align: left;

-	text-indent: 0pt;

-	margin-top: 19.500000pt;

-	margin-bottom: 19.500000pt;

-	margin-right: 0.000000pt;

-	margin-left: 30pt;

-	font-size: 11.000000pt;

-	font-weight: normal;

-	font-style: Italic;

-	color: #000000;

-	text-decoration: none;

-	vertical-align: baseline;

-	text-transform: none;

-	font-family: "Arial";

-}

-EM.UILabel {

-	font-weight: Bold;

-	font-style: normal;

-	text-decoration: none;

-	vertical-align: baseline;

-	text-transform: none;

-}

-EM.CodeName {

-	font-weight: Bold;

-	font-style: normal;

-	text-decoration: none;

-	vertical-align: baseline;

-	text-transform: none;

-	font-family:"Courier New";

-}

-

-

-

-

-/* following font face declarations need to be removed for DBCS */

-

-body, h1, h2, h3, h4, h5, h6, p, table, td, caption, th, ul, ol, dl, li, dd, dt {font-family: Arial, Helvetica, sans-serif; color: #000000}

-pre				{ font-family: Courier, monospace}

-

-/* end font face declarations */

-

-/* following font size declarations should be OK for DBCS */

-body, h1, h2, h3, h4, h5, h6, p, table, td, caption, th, ul, ol, dl, li, dd, dt {font-size: 10pt; }

-pre				{ font-size: 10pt}

-

-/* end font size declarations */

-

-body	     { background: #FFFFFF}

-h1           { font-size: 18pt; margin-top: 5px; margin-bottom: 1px }	

-h2           { font-size: 14pt; margin-top: 25px; margin-bottom: 3px }

-h3           { font-size: 11pt; margin-top: 20px; margin-bottom: 3px }

-h4           { font-size: 10pt; margin-top: 20px; margin-bottom: 3px; font-style: italic }

-p            { margin-top: 10px; margin-bottom: 10px }

-pre	     { margin-left: 6px; font-size: 9pt }

-a:link	     { color: #0000FF }

-a:hover	     { color: #000080 }

-a:visited    { text-decoration: underline }

-ul	     { margin-top: 0px; margin-bottom: 10px }

-li	     { margin-top: 0px; margin-bottom: 0px } 

-li p	     { margin-top: 0px; margin-bottom: 0px } 

-ol	     { margin-top: 0px; margin-bottom: 10px }

-dl	     { margin-top: 0px; margin-bottom: 10px }

-dt	     { margin-top: 0px; margin-bottom: 0v; font-weight: bold }

-dd	     { margin-top: 0px; margin-bottom: 0px }

-strong	     { font-weight: bold}

-em	     { font-style: italic}

-var	     { font-style: italic}

-div.revision { border-left-style: solid; border-left-width: thin; 

-				   border-left-color: #7B68EE; padding-left:5 }

-th	     { font-weight: bold }


diff --git a/bundles/org.eclipse.pde.doc.user/guide/dynamic-classpaths.htm b/bundles/org.eclipse.pde.doc.user/guide/dynamic-classpaths.htm
deleted file mode 100644
index 69733e2..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/dynamic-classpaths.htm
+++ /dev/null

@@ -1,108 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>PDE Dynamic Classpaths FAQ</title>
-</head>
-<body>
-<h2>PDE Dynamic Classpaths FAQ</h2>
-<p>Dynamic Classpaths is the way PDE computes the build path for plug-in 
-projects in Eclipse 3.0. </p>
-<p><b>Q: What is classpath stability?<br>
-A:</b> Classpath stability is a measure of classpath change with respect to the 
-self-hosting choice made by a developer. Ideally, classpaths should not change 
-regardless of the complement of source projects in the workspace. Binary project 
-self-hosting offers good classpath stability, where all classpaths contain only 
-project references. External plug-in self-hosting provides less stable 
-classpaths. They are still stable with respect to the local install location of 
-the external libraries, but the list of plug-ins as source projects must remain 
-constant for all the members of a team in order to share them via a repository.</p>
-<p>Since 2.0, added plug-in version to the plug-in location on the file system 
-further reduced the classpath stability when external plug-ins were used.</p>
-<p><b>Q: If binary projects offer better classpath stability, why not use them 
-all the time?<br>
-A: </b>Self-hosting using imported binary projects is a good choice as long the 
-number of imported plug-ins is reasonably small (a few dozen). For large 
-products with hundreds of plug-ins, a wholesale import is not an option. 
-Typically, their developers self-host with a few source projects, a few dozen 
-directly related binary projects, and everything else as external plug-ins. From 
-the purely theoretical point of view, it seems strange to waste time and 
-resources to import dozens and dozens of external plug-ins to be able to compile 
-a few source projects.</p>
-<p><b>Q: I think that (binary projects/external plug-ins) self-hosting method is 
-better. What is wrong with my team using it if we do it together?<br>
-A:</b> Static classpaths (either using binary projects or external plug-ins) 
-cast in stone your self-hosting method of choice and force everybody else to use 
-it as well.</p>
-<p><b>Q: What are dynamic classpaths?</b><br>
-<b>A:</b> <b>Dynamic classpaths </b>is a PDE feature whereby a portion of the 
-plug-in project classpath that is related to plug-in dependencies is computed 
-dynamically using JDT classpath container technology. The resolution of the dynamic classpaths is performed 'just in 
-time' and is always up to date with the conditions in your workspace. 
-Furthermore, the dynamic nature of the classpath resolution allows PDE to adapt 
-to changes and always have the correct classpath regardless of your method of 
-self-hosting.</p>
-<p><b>Q: What is the classpath stability of dynamic classpaths?<br>
-A:</b> Ultimate. Since all the entries for the required plug-ins are replaced 
-with one classpath container entry, your classpath is always the same.</p>
-<p><b>Q: How can dynamic classpaths help me?</b><br>
-<b>A: </b>With dynamic classpaths, there is no need to make upfront decisions 
-with respect to the self-hosting style. If binary projects are present, dynamic 
-classpaths will resolve to project references. If not, they will resolve to 
-external plug-in JARs. As binary projects are added or removed, dynamic classpaths will track the changes and adapt. You will not need to update your 
-classpath ever again. In addition, other teams that want to take one or more of 
-your projects from CVS and get them to compile don't have to use your personal 
-self-hosting style to do so.</p>
-<p><b>Q: Since PDE Core is resolving the dynamic classpaths, does it mean that I 
-will be dependent on PDE to do the right thing?<br>
-A: </b>In a word, yes. Being dynamic, your classpath will always be computed on 
-the fly, not hard-coded in the .classpath file (that was the whole idea, 
-right?). But consider this: PDE has a sophisticated algorithm for computing the 
-classpath that strives to get you as close as possible to the run-time 
-conditions. What the JDT compiler 'sees' at development time should be as close 
-as possible to what class loaders will see at run time. PDE Core is more capable 
-of keeping your classpath up to date than yourself most of the time. If you need 
-to manually tweak the classpath in order to compile, something is most likely 
-wrong with your setup and there is a strong chance your plug-in will not run 
-correctly (SWT team being an exception).</p>
-<p><b>Q: My team uses binary projects for self-hosting exclusively. Will I lose 
-anything by switching to dynamic classpaths?<br>
-A:</b> No. Dynamic classpaths do not dictate your personal choice of self-hosting 
-arrangements. It simply resolves your plug-in dependencies in the given context. 
-If you continue to import external plug-ins as binary projects, dynamic 
-classpaths will resolve to project references as before.</p>
-<p><b>Q: What do I need to activate dynamic classpaths?<br>
-A: </b>Update the classpaths 
-of all your 2.1 plug-ins just once. You will notice that classpaths are now shorter and all 
-the dependent plug-in references are now replaced with one container entry. You 
-can continue to work. Make sure to check the source projects into the 
-repository, including the changed .classpath files.</p>
-<p><b>Q: I have extra classpath entries so that I can compile my Ant tasks/servlets/JSPs.<br>
-A:</b> As part of the classpath computation, PDE takes 'jars.extra.classpath' 
-property from build.properties file into account. If you are set up correctly 
-for building, PDE will generate the correct classpath.</p>
-<p><b>Q: How do I manipulate the dynamically computed classpath entries?<br>
-A:</b> In the unlikely event you need to manipulate your dynamic classpath 
-entries, you can do so from Properties&gt;Java Build Path&gt;Libraries tab. Expand the 
-'Plug-in Dependencies' node and manipulate the entries there.</p>
-<p><b>Q: Some of the computed entries for libraries don't have source 
-attachments. Can I add them manually?<br>
-A:</b> PDE computes source attachments for most of the libraries. There are some 
-odd cases where automatic source attachments may fail due to source zips not 
-following naming conventions. You can attach sources manually for these entries 
-in the build path properties dialog.</p>
-<p><b>Q: Will my manual source attachments be wiped out the next time PDE 
-computes the classpath dynamically?<br>
-A: </b>No. PDE keeps track of these manual cases and reapplies them after 
-dynamic computation as long as the library paths didn't change.</p>
-<p><b>Q: I am an SWT developer. Can I use dynamic classpaths?<br>
-A: </b>Sadly, no. SWT team has a unique self-hosting setup whereby classpaths for 
-various environments are saved in the repository and renamed into .classpath in 
-the project depending on the platform they are working on. They will have to 
-continue to use their self-hosting methods.</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/feature_based_product.htm b/bundles/org.eclipse.pde.doc.user/guide/feature_based_product.htm
deleted file mode 100644
index 0a1a6ec..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/feature_based_product.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Feature-Based Product</title>
-</head>
-
-<body>
-<h2>Feature-Based Product</h2>
-<p>To be able to take advantage of the Update Manager functionality and be able 
-  to publish upgrades and patches to your product, your product has to be feature-based.</p>
-<p>Creating a feature-based product using the product editor is almost the same 
-  as a plugin-based product, with the only difference being the settings on the 
-  Configuration page.</p>
-<p><img src="images/product-configuration-features.PNG" width="735" height="512"></p>
-<p>Using the <strong>New Feature...</strong> button on the <strong>Configuration</strong> 
-  page of the product editor, create a feature named <em>com.example.feature</em> 
-  that contains plug-in <em>com.example.xyz, </em>as described in the <a href="pde_feature_setup.htm">Feature 
-  section</a> of the guide.</p>
-<p>On the <a href="pde_feature_manifest.htm">Overview page of the feature editor</a>, 
-  the feature must declare the <em>com.example.xyz</em> plug-in as its <strong>branding</strong> 
-  plug-in.</p>
-<p>Add the <em>org.eclipse.rcp</em> feature to the list of features to be included 
-  in your product.</p>
-<p>That is it!</p>
-<p>Proceed to the Exporting a Product section as you normally would with a plugin-based 
-  configuration. </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/accessible.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/accessible.PNG
deleted file mode 100644
index 9eb6cfb..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/accessible.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/actionSet-1.png b/bundles/org.eclipse.pde.doc.user/guide/images/actionSet-1.png
deleted file mode 100644
index 136478b..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/actionSet-1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/binary-import1.png b/bundles/org.eclipse.pde.doc.user/guide/images/binary-import1.png
deleted file mode 100644
index 16db266..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/binary-import1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/binary-import2.png b/bundles/org.eclipse.pde.doc.user/guide/images/binary-import2.png
deleted file mode 100644
index c48fbd3..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/binary-import2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/binary-projects.png b/bundles/org.eclipse.pde.doc.user/guide/images/binary-projects.png
deleted file mode 100644
index 79846bf..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/binary-projects.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/build-editor.png b/bundles/org.eclipse.pde.doc.user/guide/images/build-editor.png
deleted file mode 100644
index 3c9f1e2..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/build-editor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/build-source.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/build-source.PNG
deleted file mode 100644
index 971cc41..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/build-source.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/classpath-update.png b/bundles/org.eclipse.pde.doc.user/guide/images/classpath-update.png
deleted file mode 100644
index 80a99cb..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/classpath-update.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/compiler_discouraged.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/compiler_discouraged.PNG
deleted file mode 100644
index 1cd34fa..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/compiler_discouraged.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/content_assist_discouraged.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/content_assist_discouraged.PNG
deleted file mode 100644
index fc5082b..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/content_assist_discouraged.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/convert-java.png b/bundles/org.eclipse.pde.doc.user/guide/images/convert-java.png
deleted file mode 100644
index b741fd3..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/convert-java.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/convert.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/convert.PNG
deleted file mode 100644
index dc0bc2b..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/convert.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/default-codegen.png b/bundles/org.eclipse.pde.doc.user/guide/images/default-codegen.png
deleted file mode 100644
index a824fc6..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/default-codegen.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/discourage_pref.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/discourage_pref.PNG
deleted file mode 100644
index 350bd07..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/discourage_pref.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/discouraged.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/discouraged.PNG
deleted file mode 100644
index 4136127..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/discouraged.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/errorLog.png b/bundles/org.eclipse.pde.doc.user/guide/images/errorLog.png
deleted file mode 100644
index 725b4a9..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/errorLog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/feature-advanced.png b/bundles/org.eclipse.pde.doc.user/guide/images/feature-advanced.png
deleted file mode 100644
index ce7cbae..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/feature-advanced.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/feature-content.png b/bundles/org.eclipse.pde.doc.user/guide/images/feature-content.png
deleted file mode 100644
index e11fa7f..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/feature-content.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/feature-dependencies.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/feature-dependencies.PNG
deleted file mode 100644
index fecee5f..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/feature-dependencies.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/feature-export.png b/bundles/org.eclipse.pde.doc.user/guide/images/feature-export.png
deleted file mode 100644
index 5e07a35..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/feature-export.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/feature-jar.png b/bundles/org.eclipse.pde.doc.user/guide/images/feature-jar.png
deleted file mode 100644
index df06cdc..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/feature-jar.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/feature-overview-info.png b/bundles/org.eclipse.pde.doc.user/guide/images/feature-overview-info.png
deleted file mode 100644
index 731bf66..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/feature-overview-info.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/feature-overview.png b/bundles/org.eclipse.pde.doc.user/guide/images/feature-overview.png
deleted file mode 100644
index 1290ff6..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/feature-overview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/feature-synchronizing.png b/bundles/org.eclipse.pde.doc.user/guide/images/feature-synchronizing.png
deleted file mode 100644
index 7c9e01e..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/feature-synchronizing.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/forbidden_pref.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/forbidden_pref.PNG
deleted file mode 100644
index ef01063..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/forbidden_pref.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/fragment-content.png b/bundles/org.eclipse.pde.doc.user/guide/images/fragment-content.png
deleted file mode 100644
index 53b14c3..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/fragment-content.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/fragment-overview.png b/bundles/org.eclipse.pde.doc.user/guide/images/fragment-overview.png
deleted file mode 100644
index 34f386c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/fragment-overview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/friends.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/friends.PNG
deleted file mode 100644
index 091007a..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/friends.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/hello-world-page.png b/bundles/org.eclipse.pde.doc.user/guide/images/hello-world-page.png
deleted file mode 100644
index 60a836c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/hello-world-page.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/included-features.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/included-features.PNG
deleted file mode 100644
index aefe55c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/included-features.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/initial-structure.png b/bundles/org.eclipse.pde.doc.user/guide/images/initial-structure.png
deleted file mode 100644
index 03a0a02..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/initial-structure.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/install-site-features.png b/bundles/org.eclipse.pde.doc.user/guide/images/install-site-features.png
deleted file mode 100644
index 4dab017..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/install-site-features.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/install-update-sites.png b/bundles/org.eclipse.pde.doc.user/guide/images/install-update-sites.png
deleted file mode 100644
index a6ee141..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/install-update-sites.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/java-interface.png b/bundles/org.eclipse.pde.doc.user/guide/images/java-interface.png
deleted file mode 100644
index 82cabb1..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/java-interface.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/jnlp.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/jnlp.PNG
deleted file mode 100644
index b6441d2..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/jnlp.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/launch-dialog.png b/bundles/org.eclipse.pde.doc.user/guide/images/launch-dialog.png
deleted file mode 100644
index 231abb3..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/launch-dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/launch-plugins.png b/bundles/org.eclipse.pde.doc.user/guide/images/launch-plugins.png
deleted file mode 100644
index c0a6cfe..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/launch-plugins.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/launch-tracing.png b/bundles/org.eclipse.pde.doc.user/guide/images/launch-tracing.png
deleted file mode 100644
index e27f23d..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/launch-tracing.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/manifest-source.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/manifest-source.PNG
deleted file mode 100644
index 1f7ae6b..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/manifest-source.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/manifest-validate.png b/bundles/org.eclipse.pde.doc.user/guide/images/manifest-validate.png
deleted file mode 100644
index b62f857..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/manifest-validate.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/ngrelc.png b/bundles/org.eclipse.pde.doc.user/guide/images/ngrelc.png
deleted file mode 100644
index 161e3aa..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/ngrelc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/ngrelt.png b/bundles/org.eclipse.pde.doc.user/guide/images/ngrelt.png
deleted file mode 100644
index 74bee2b..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/ngrelt.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/pdeperspective.png b/bundles/org.eclipse.pde.doc.user/guide/images/pdeperspective.png
deleted file mode 100644
index 78059ea..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/pdeperspective.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/plugin-dependencies.png b/bundles/org.eclipse.pde.doc.user/guide/images/plugin-dependencies.png
deleted file mode 100644
index ae1320a..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/plugin-dependencies.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/plugin-expoint.png b/bundles/org.eclipse.pde.doc.user/guide/images/plugin-expoint.png
deleted file mode 100644
index 6599d7a..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/plugin-expoint.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/plugin-export.png b/bundles/org.eclipse.pde.doc.user/guide/images/plugin-export.png
deleted file mode 100644
index bb44767..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/plugin-export.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/plugin-overview.png b/bundles/org.eclipse.pde.doc.user/guide/images/plugin-overview.png
deleted file mode 100644
index 0fedbb5..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/plugin-overview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/plugin-runtime.png b/bundles/org.eclipse.pde.doc.user/guide/images/plugin-runtime.png
deleted file mode 100644
index 3d8e163..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/plugin-runtime.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/plugin-source.png b/bundles/org.eclipse.pde.doc.user/guide/images/plugin-source.png
deleted file mode 100644
index caf4186..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/plugin-source.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/preferences.png b/bundles/org.eclipse.pde.doc.user/guide/images/preferences.png
deleted file mode 100644
index cc40fc2..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/preferences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/product-branding.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/product-branding.PNG
deleted file mode 100644
index 538a8ac..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/product-branding.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/product-configuration-features.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/product-configuration-features.PNG
deleted file mode 100644
index 36e2b0c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/product-configuration-features.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/product-configuration-plugins.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/product-configuration-plugins.PNG
deleted file mode 100644
index 912fbf8..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/product-configuration-plugins.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/product-export.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/product-export.PNG
deleted file mode 100644
index d9ebd77..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/product-export.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/product-overview.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/product-overview.PNG
deleted file mode 100644
index 7c140b2..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/product-overview.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/product_config_wizard.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/product_config_wizard.PNG
deleted file mode 100644
index e360fb2..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/product_config_wizard.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/project-codegen.png b/bundles/org.eclipse.pde.doc.user/guide/images/project-codegen.png
deleted file mode 100644
index a4e56b7..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/project-codegen.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/project-structure.png b/bundles/org.eclipse.pde.doc.user/guide/images/project-structure.png
deleted file mode 100644
index 73db591..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/project-structure.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/properties.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/properties.PNG
deleted file mode 100644
index d335759..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/properties.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/rcp_content.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/rcp_content.PNG
deleted file mode 100644
index 57c26b7..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/rcp_content.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/rcp_mail.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/rcp_mail.PNG
deleted file mode 100644
index a5facc4..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/rcp_mail.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/rcp_mail_app.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/rcp_mail_app.PNG
deleted file mode 100644
index bf30815..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/rcp_mail_app.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/registry.png b/bundles/org.eclipse.pde.doc.user/guide/images/registry.png
deleted file mode 100644
index a4db2d5..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/registry.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/restriction-dialog.png b/bundles/org.eclipse.pde.doc.user/guide/images/restriction-dialog.png
deleted file mode 100644
index b025f6f..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/restriction-dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/schema-1.png b/bundles/org.eclipse.pde.doc.user/guide/images/schema-1.png
deleted file mode 100644
index 90a0e35..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/schema-1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/schema-2.png b/bundles/org.eclipse.pde.doc.user/guide/images/schema-2.png
deleted file mode 100644
index 79145c6..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/schema-2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/schema-outline.png b/bundles/org.eclipse.pde.doc.user/guide/images/schema-outline.png
deleted file mode 100644
index fdd534c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/schema-outline.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/schema-usage.png b/bundles/org.eclipse.pde.doc.user/guide/images/schema-usage.png
deleted file mode 100644
index 5dd1b2c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/schema-usage.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/site-description.png b/bundles/org.eclipse.pde.doc.user/guide/images/site-description.png
deleted file mode 100644
index 75c6063..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/site-description.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/site-features.png b/bundles/org.eclipse.pde.doc.user/guide/images/site-features.png
deleted file mode 100644
index bb4841e..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/site-features.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/site-new.png b/bundles/org.eclipse.pde.doc.user/guide/images/site-new.png
deleted file mode 100644
index cb5ac59..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/site-new.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/source-locations.png b/bundles/org.eclipse.pde.doc.user/guide/images/source-locations.png
deleted file mode 100644
index 4a8deef..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/source-locations.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/xyz-tracing.png b/bundles/org.eclipse.pde.doc.user/guide/images/xyz-tracing.png
deleted file mode 100644
index bb6add9..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/xyz-tracing.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/intro/pde_overview.htm b/bundles/org.eclipse.pde.doc.user/guide/intro/pde_overview.htm
deleted file mode 100644
index aed0e6c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/intro/pde_overview.htm
+++ /dev/null

@@ -1,82 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Using the Plug-in Development Environment</title>
-<script language="JavaScript" src="../../../org.eclipse.help/livehelp.js"> </script>
-<script type="text/javaScript">
-	function openRelatedLink(rel) {
-		var href = '/org.eclipse.pde.doc.user/'+rel;
-		if (self.name=="ContentViewFrame") {
-			showTopicInContents(href);
-			window.location = '../../'+rel;
-		}
-		else {
-			window.location = 'http://org.eclipse.ui.intro/showHelpTopic?id='+href;
-		}
-	}
-</script></head>
-
-<BODY BGCOLOR="#ffffff">
-
-<h1>Plug-in Development Environment Overview</h1>
-<p>The Plug-in Development Environment (PDE) is a tool that is designed to 
-assist developers in the creation, development, testing, debugging, and 
-deployment of Eclipse plug-ins.&nbsp; The mandate of PDE also encompasses&nbsp; 
-tooling for the development of fragments, features, and update sites.</p>
-<p>PDE is part of the Eclipse SDK and not a separately launched
-tool.&nbsp; In line with the general Eclipse platform philosophy, PDE provides a 
-wide variety of platform contributions (e.g. views, editors, wizards, launchers, 
-etc.) that blend transparently with the rest of the Eclipse workbench, and 
-assist the developer in every stage of plug-in development while working inside 
-the Eclipse workbench.</p>
-<h2>Concepts</h2>
-<ul>
-	<li><b>Host vs. runtime</b><br>
-	When you start up the workbench, you will use it to work on your projects 
-	that define the plug-ins you are building.&nbsp;The workbench&nbsp;instance that you 
-	are running as you develop your plug-in using the PDE and other tools is the
-	<b>host</b> instance. The features available in this instance will come exclusively from 
-	the plug-ins that are installed with your application. Once you are happy 
-	with your plug-in and want to test it, you can launch another workbench 
-	instance, the <b>runtime</b> instance. This instance will contain the same plug-ins as the host instance, 
-	but will also have the plug-ins you were working on in the host instance. 
-	PDE launcher will take care of&nbsp;merging your plug-ins with the host plug-ins 
-	and creating the run-time instance.</li>
-	<li><b>External vs. workspace plug-ins</b><br>
-	When developing Eclipse plug-ins, the set of plug-ins that you will be used 
-	to run the runtime workbench come from two distinct places: the workspace of 
-	the host instance and the target platform.&nbsp; Although, to PDE, all plug-ins 
-	are the same no matter where they come from, there are a few differences 
-	that quickly become evident to users:<br>
-&nbsp;<ul>
-		<li><b>Workspace plug-ins</b> are those plug-ins under development in 
-		your host workbench.&nbsp; They are under your control and can be added, 
-		deleted and modified by the user. </li>
-		<li><b>External plug-ins</b> are plug-ins that arrived with the basic 
-		platform installation and are simply referenced from their original 
-		location without modification. You can reference them, browse them, view 
-		their source and debug them, but they are read-only.&nbsp; </li>
-	</ul>
-	</li>
-</ul>
-<p>The Plug-ins view, which is part of the PDE perspective, will show the 
-combined list of workspace and external plug-ins. In it, you will be able to 
-browse the directory structure of external plug-ins, open files, etc.</p>
-<p>
-<img border="0" src="../images/ngrelc.png" width="159" height="27" alt="Related concepts"><br>
-<a href="javaScript:openRelatedLink('guide/pde_setup.htm')">Preparing the workbench</a><br>
-<a href="javaScript:openRelatedLink('guide/pde_configuring.htm')">PDE concepts</a></p>
-<p>
-<img border="0" src="../images/ngrelt.png" width="159" height="27" alt="Related tasks"><br>
-<a href="javaScript:openRelatedLink('guide/pde_creating.htm')">Creating new plug-in project</a><br>
-<a href="javaScript:openRelatedLink('guide/pde_manifest.htm')">Editing the manifest</a><br>
-<a href="javaScript:openRelatedLink('guide/pde_running.htm')">Running</a><br>
-<a href="javaScript:openRelatedLink('guide/pde_deploy.htm')">Deploying</a><br>
-<a href="javaScript:openRelatedLink('guide/pde_features.htm')">Working with features</a><br>
-<a href="javaScript:openRelatedLink('guide/pde_sites.htm')">Working with update sites</a></p>
-<p></p>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/parsers.htm b/bundles/org.eclipse.pde.doc.user/guide/parsers.htm
deleted file mode 100644
index 5bcede3..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/parsers.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<!-- default platform documentation stylesheets -->
-<style>@import url("book.css");</style>
-<!-- default schema documentation stylesheets -->
-<style>@import url("schema.css");</style>
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-</HEAD>
-<BODY>
-<H1><CENTER>Sample Parsers</CENTER></H1>
-<p></p>
-<h6 class=CaptionFigColumn id=header>Identifier: </h6>com.example.xyz.parsers<p></p>
-<h6 class=CaptionFigColumn id=header>Since: </h6>3.0
-<p></p>
-
-<p>
-<h6 class=CaptionFigColumn id=header>Description: </h6>This extension point is used to plug in additional parsers. The parsers actually do not work - we have just used them as an example of extension point schema.</p>
-<p><h6 class=CaptionFigColumn id=header>Configuration Markup:</h6></p>
-<p class=code id=dtd>&lt;!ELEMENT <a name="e.extension">extension</a> EMPTY&gt;</p>
-<p class=code id=dtd>&lt;!ATTLIST extension</p>
-<p class=code id=dtdAttlist>point&nbsp;CDATA #REQUIRED</p><p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED</p><p class=code id=dtdAttlist>name&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
-<p></p>
-<ul class=ConfigMarkup id=attlistDesc>
-</ul>
-<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.parser">parser</a> (<a href="#e.parser">parser</a>+)&gt;</p>
-<p class=code id=dtd>&lt;!ATTLIST parser</p>
-<p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED</p><p class=code id=dtdAttlist>name&nbsp;&nbsp;CDATA #REQUIRED</p><p class=code id=dtdAttlist>class&nbsp;CDATA #REQUIRED</p><p class=code id=dtdAttlist>mode&nbsp;&nbsp;(manual|always|never) &gt;</p>
-<p></p>
-<ul class=ConfigMarkup id=attlistDesc>
-<li><b>id</b> - a unique name that will be used to reference this parser.</li>
-<li><b>name</b> - a translatable name that will be used for presenting this parser in the UI</li>
-<li><b>class</b> - a fully qualified name of the Java class that implements <samp>com.example.xyz.IParser</samp> interface</li>
-<li><b>mode</b> - an optional flag that indicates how often this parser instance will run (default is <samp>always</samp>).</li>
-</ul>
-<br><h6 class=CaptionFigColumn id=header>Examples: </h6>The following is an example of the extension point usage:
-   <p></p>
-   <pre>
-      <p class=code id=tag>&lt;extension point=</p><p class=code id=cstring>&quot;com.example.xyz.parsers&quot;</p><p class=code id=tag>&gt;</p>
-         <p class=code id=tag>&lt;parser
-            id=</p><p class=code id=cstring>&quot;com.example.xyz.parser1&quot;</p><p class=code id=tag>
-            name=</p>s<p class=code id=cstring>&quot;Sample Parser 1&quot;</p><p class=code id=tag>
-            class=</p><p class=code id=cstring>&quot;com.example.xyz.SampleParser1&quot;</p><p class=code id=tag>&gt;</p>
-         <p class=code id=tag>&lt;/parser&gt;</p>
-      <p class=code id=tag>&lt;/extension&gt;</p>
-   </pre>
-   <p></p>
-<p></p>
-
-<h6 class=CaptionFigColumn id=header>API Information: </h6>Plug-ins that want to extend this extension point must implement com.example.xyz.IParser interface.
-<p></p>
-
-<h6 class=CaptionFigColumn id=header>Supplied Implementation: </h6>XYZ Plug-in provides default implementation of the parser.
-<p></p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde.htm b/bundles/org.eclipse.pde.doc.user/guide/pde.htm
deleted file mode 100644
index 06b36af..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Using the Plug-in Development Environment</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h1>Introduction to PDE</h1>

-<p>The Plug-in Development Environment (PDE) is a tool that is designed to 

-assist developers in the creation, development, testing, debugging, and 

-deployment of Eclipse plug-ins.&nbsp; The mandate of PDE also encompasses&nbsp; 

-tooling for the development of fragments, features, and update sites.</p>

-<p>PDE is part of the Eclipse SDK and not a separately launched

-tool.&nbsp; In line with the general Eclipse platform philosophy, PDE provides a 

-wide variety of platform contributions (e.g. views, editors, wizards, launchers, 

-etc.) that blend transparently with the rest of the Eclipse workbench, and 

-assist the developer in every stage of plug-in development while working inside 

-the Eclipse workbench.</p>

-<p>As a pre-requisite to working with PDE, you need

-to understand the concepts presented in the Platform ISV Guide and the JDT User 

-Guide.</p>

-

-

-

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_build_editor.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_build_editor.htm
deleted file mode 100644
index 6d9dcd7..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_build_editor.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>
-<HEAD>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Build Configuration page</title>
-</head>
-
-<BODY BGCOLOR="#ffffff">
-
-<h2>Build configuration page</h2>
-<p>The <b>Build Configuration</b> page contains all the information needed to 
-build, package and export the plug-in.&nbsp; It appears as a page in the plug-in 
-manifest editor, but note that changes made to it will be written by PDE to the
-<b>build.properties</b> file of the plug-in.&nbsp; This file solely guides the 
-build process.</p>
-<p align="center"> <img src="images/build-editor.png" alt="Build Editor" border="0" >.</p>
-<p align="left">&nbsp;</p>
-<p align="left">The <b>Runtime Information</b> section lists all the libraries 
-  that you want to build.&nbsp; For each library, you must list the source folder(s) 
-  that will be compiled into the library.</p>
-<p align="left">If your plug-in declares more than one library, order them 
-correctly using the Up and Down button, so that they get compiled in the correct 
-order.</p>
-<p align="left">The <b>Binary Build</b> section is where you select all the 
-files and folders that will make it into the packaged plug-in.&nbsp; In this 
-example, you will see that we only want to the plugin.xml file, icons folder and 
-the xyz.jar to end up in the packaged plug-in.</p>
-<p align="left">The <b>Source Build </b>section has a specialized purpose and is not commonly used or needed by the general population.&nbsp; It is 
-needed only when you are shipping source in separate plug-ins and features than 
-the binary plug-ins.&nbsp; See the
-<a href="../reference/extension-points/org_eclipse_pde_core_source.html">
-org.eclipse.pde.core.source</a> extension point for details.</p>
-<p align="left">If the libraries you want to build include libraries that are 
-NOT listed on the Runtime page, and you need extra libraries on the build 
-path for them to compile, you can add these required JARs in the <b>Extra 
-Classpath Entries</b> section.</p>
-
-</body>
-
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_configuring.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_configuring.htm
deleted file mode 100644
index 045d664..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_configuring.htm
+++ /dev/null

@@ -1,66 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Configuring PDE</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h2><font size="5">Concepts</font></h2>

-<h2>Host vs. runtime</h2>

-<p>One of the most important concepts in PDE to understand is that of <b>host</b>

-and <b>runtime</b>   workbench instances.  </p>

-<p>When you start up the workbench, you

-will use it to work on your projects that define the plug-ins you are

-building.&nbsp; The workbench&nbsp;instance that you are running as you develop

-your

-plug-in using the PDE and other tools is the <b>host</b> instance. The features available in this instance will

-come exclusively from the plug-ins that are installed with your application.</p>

-<p> Once you are

-happy with your plug-in and want to test it, you can launch another workbench instance,

-the <b>runtime</b> instance. This instance will contain the same

-plug-ins as the <b>host</b> instance, but will also have the plug-ins you were

-working on in the <b>host</b> instance. PDE launcher will take care of&nbsp;merging your

-plug-ins with the host plug-ins and creating the run-time instance.</p>

-

-<h2><b>Target Platform</b></h2>

-<p>Target Platform refers to the Eclipse product against which the plug-ins you 

-are developing will be compiled and tested.&nbsp; The Target Platform must 

-therefore be the same platform in which you plan to deploy your plug-ins.</p>

-<p>The location of the target platform is set on the <b>Plug-in Development &gt; 

-Target Platform</b> preference page.&nbsp; By default, the target platform is 

-the same as the platform you are using for development, but this is not 

-required.&nbsp; You can set the target platform to whatever Eclipse-based 

-product you want.&nbsp; For example, if you want to take advantage of the latest 

-and greatest Eclipse 3.0 features to develop for plug-ins that will be deployed 

-in a product based on a 2.x Eclipse, you can use Eclipse 3.0 as your development 

-platform and a 2.x-based product as your target platform.</p>

-<p>&nbsp;</p>

-<p align="center">

-<img border="0" src="images/preferences.png" alt="PDE preferences - &quot;Target Platform&quot; page" ></p>

-<p align="left">&nbsp;</p>

-<p align="left">All the plug-ins found in the target platform location specified 

-by the user are listed on the preference page.&nbsp; However, only the plug-ins 

-that are explicitly checked constitute the target platform; the rest are ignored 

-by PDE.&nbsp; By default, all plug-ins are checked.</p>

-<h2>External vs. workspace plug-ins</h2>

-<p>When developing Eclipse plug-ins, the set of plug-ins that you will be used 

-to run the runtime workbench come from two distinct places: the workspace of the 

-host instance and the target platform.&nbsp; Although, to PDE, all plug-ins are 

-the same no matter where they come from, there are a few differences that 

-quickly become evident to users.</p>

-<ul>

-  <li><b>Workspace plug-ins</b> are those plug-ins under development in your host 

-    workbench.&nbsp; They are under your control and can be added, deleted and 

-    modified by the user.</li>

-  <li><b>External plug-ins</b> are plug-ins that arrived with the basic platform 

-    installation and are simply referenced from their original location without 

-    modification. You can reference them, browse them, view their source and debug 

-    them, but they are read-only.&nbsp;</li>

-</ul>

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_convert.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_convert.htm
deleted file mode 100644
index 566f859..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_convert.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Converting projects into PDE projects</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h1>Converting existing projects into PDE projects</h1>

-<p>A PDE project is a project that &quot;knows&quot; it hosts a plug-in and is 

-eligible for plug-in-specific operations. </p>

-<p>PDE is fully capable of working on plug-ins in the workspace represented as

-ordinary projects. However, it cannot offer incremental file checking,

-capability-based filtering and other similar features if a project does not

-possess full PDE capabilities.</p>

-<p>It is

-possible to convert a regular project into a PDE project at any point. For

-example, you may have some Java classes that you want to package into a library

-and share with others as a plug-in. Alternatively, you may want to get full

-support for manifest syntax checking and reporting that only PDE projects have.</p>

-<p>To convert projects into PDE projects, select a project in the Navigator view.

-  Select <b>PDE Tools &gt; Convert Projects to Plug-in Projects...</b> from the

-  context menu.</p>

-<p align="center">

-<img border="0" src="images/convert-java.png" alt="&quot;Convert Existing Projects&quot; wizard" ></p>

-<p>The wizard will list all projects that do not have PDE capability.

-Candidate projects do not need to have manifest files. If they are missing, PDE

-will create generic ones you can use as a starting point. Files that already

-exist will be left intact. Select one or more projects, click <b>Finish</b>.</p>

-

-

-

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_creating.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_creating.htm
deleted file mode 100644
index b611e7e..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_creating.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Creating a PDE plug-in</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h1>Creating a plug-in project</h1>

-<p>In the workspace, a plug-in is represented by a single project that encapsulates 

-  all the code and resources of the plug-in.</p>

-<p>To create a plug-in project, bring up the New Plug-in Project creation wizard 

-via&nbsp; <b>File &gt; New &gt; Plug-in Project</b>.</p>

-<p align="center">

-<img border="0" src="images/project-structure.png" alt="Plug-in Project Structure" ></p>

-<p>It is a convention that plug-in project names are the same as plug-in IDs, 

-but they can be different. </p>

-<p>The plug-in project can be created in one of two flavors: a Java project or a 

-simple project.&nbsp; Most plug-ins are meant to contain executable Java code 

-and must therefore be housed in a Java project.&nbsp; On the other hand, if, for 

-example, you are creating a documentation plug-in, then a simple project will 

-suffice.</p>

-<p>A plug-in with an OSGi bundle manifest is the recommended plug-in format. In 

-  addition to faster startup and classloading, it allows the plug-in to take advantage 

-  to many new runtime capabilities.</p>

-<p>Click <strong>Next</strong>.</p>

-<p align="center"> <img border="0" src="images/default-codegen.png" alt="plug-in content page" ></p>

-<p>&nbsp;</p>

-<p>&nbsp;</p>

-<p>On the Plug-in Content page, you set the data with which the plugin.xml file 

-  will be initialized, including the plug-id, version and name.</p>

-<p>The recommended deployed form of a plug-in is to be shipped as a single JAR 

-  with all the classes and resources at the root of the JAR. For this format, 

-  you may keep the <strong>Classpath</strong> field empty, or enter '.' (without 

-  quotes). </p>

-<p>The Plug-in class is a top-level Java class that represents the entire plug-in.&nbsp; 

-  It will be used at runtime to control the plug-in's life cycle, i.e. its implementation 

-  will determine what happens when the plug-in starts up or shuts down.&nbsp; 

-</p>

-<p>Click <strong>Next</strong>.</p>

-<p align="center">

-<img border="0" src="images/project-codegen.png" alt="Plug-in code generators" ></p>

-<p>&nbsp;</p>

-<p>The next page shows the various templates that PDE provides which generate 

-useful content such as views, editors, property pages etc. </p>

-<p>In this example, we will create a plug-in with the &quot;Hello, World&quot; 

-  template. You can read about the wizard in the area to the right of the wizard 

-  list.&nbsp; </p>

-<p>Click <b>Next</b>.</p>

-<p align="center">

-<img border="0" src="images/hello-world-page.png" alt="&quot;Sample Action Set&quot; template page" ></p>

-<p align="left">&nbsp;</p>

-<p align="left">The next page will let you customize the sample extension that 

-we are creating.</p>

-<p align="left">When you press <b>Finish</b>, the wizard will create the new project, 

-  all the specified folders and files, and the initial Java build path. The build 

-  path is important for correct compilation of Java classes that are generated. 

-  The wizard will also open the plug-in manifest editor.&nbsp;&nbsp;</p>

-<p align="left"> After the wizard is

-finished, the initial project structure should look like this:</p>

-<p align="center">

-<img border="0" src="images/initial-structure.png" alt="Initial plug-in project structure" ></p>

-

-

-

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_deploy.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_deploy.htm
deleted file mode 100644
index 13cbf1d..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_deploy.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Exporting a plug-in</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h1>Exporting a plug-in</h1>

-<p>During the design phase, plug-ins and fragments in your workspace are used 

-  as-is so that you can quickly test and debug. Once you reach the stage where 

-  you are satisfied with your code, you need to publish it in a form suitable 

-  for deployment in an Eclipse product.</p>

-<p>The easiest way to do so is through the <b>Export Plug-ins and Fragments</b> 

-  Wizard.&nbsp; It shields you from ant scripts and does not pollute your workspace 

-  with resources generated during the build operations:</p>

-<p>Select <b>File &gt; Export... &gt; Deployable plug-ins and fragments</b></p>

-<p>Select the plug-ins and fragments you want to export.&nbsp; </p>

-<p>The export destination can be an archive or a directory.</p>

-<p align="center"><img border="0" src="images/plugin-export.png" alt="Export plug-ins and fragments wizard" ></p>

-<p align="left">The recommended format for a deployable plug-in in 3.1 to be packaged 

-  as a JAR archive. Refer to the <a href="plugins_as_jars.htm">Exporting your 

-  plug-in as a JAR</a> document for details if you have a pre-3.1 plug-in that 

-  you need to JAR. </p>

-<p>You also have the option to save the settings of this export operation.&nbsp; 

-This way you would be able to redo this export operation without having to go 

-through the wizard all over again.</p>

-<p>Alternatively, plug-in JARs could be built manually.&nbsp; Refer to the

-<a href="pde_feature_generating_ant.htm">Creating Ant Scripts from PDE</a> 

-section.</p>

-

-

-</body>

-

-</html>


diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_feature_generating.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_feature_generating.htm
deleted file mode 100644
index f1082bc..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_feature_generating.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Exporting a feature</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h2>Exporting a Feature</h2>

-

-<p>First you have to set up the build configuration.&nbsp;&nbsp; The build 

-configuration includes information about the files and directories that should 

-be included in the feature for each individual plug-in and fragment.&nbsp; There 

-may be some design-time files and directories that should not be shipped.&nbsp; 

-See <a href="pde_feature_generating_build.htm">Build Configuration</a> for 

-details.</p>

-

-Then you can use PDE's Export Deployable Features wizard to build and export the 

-feature.&nbsp; This way you are shielded from Ant scripts and your workspace is 

-never polluted with build by-products. 

-<p>Select <b>File &gt; Export... &gt; Deployable Features</b>.</p>

-<p>Select the feature(s) you want to export. </p>

-<p>A feature can be exported to an archive or a directory.</p>

-<p>To publish a feature to an update site, the feature and its includes plug-ins 

-  must be packaged as individual JAR archives.</p>

-<p align="center"> <img border="0" src="images/feature-export.png" alt="Export Features wizard" ></p>

-<p align="left">Press <strong>Next</strong>.</p>

-<p align="center"><img src="images/jnlp.PNG" alt="JNLP manifest generation"></p>

-<p>You have the option to sign the JARs for added security. You also have the 

-  option to generate JNLP manifests for <a href="../../org.eclipse.platform.doc.isv/guide/java_web_start.htm">Java 

-  Web Start deployment</a>.</p>

-<p>The wizard will build all the features selected and their included plug-ins 

-  and fragments.&nbsp; Features go into a features/ subdirectory and plug-ins 

-  go into a plugins/ subdirectory.</p>

-<p>&nbsp;</p>

-<p>The alternative would be to build features manually:</p>

-<ol>

-  <li>Right-click on the feature.xml file for your feature project and choose '<b>Create 

-  Ant Build File</b>'.&nbsp; This will generate a build.xml file.</li>

-  <li>Select the build.xml file and choose '<b>Run Ant...</b>'&nbsp; </li>

-  <li>In the Ant build script wizard, select the target(s) you want to run.&nbsp; 

-  See <a href="pde_feature_generating_ant.htm">Generating Ant Scripts</a> for 

-  details.</li>

-</ol>

-

-

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_feature_generating_ant.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_feature_generating_ant.htm
deleted file mode 100644
index 769bc6f..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_feature_generating_ant.htm
+++ /dev/null

@@ -1,115 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Generating ANT scripts</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h3>Generating Ant scripts</h3>

-

-<p> <b> Ant</b> is a simple open-source scripting engine that is capable of running

-scripts written in XML format. Ant is ideal for executing tasks usually found in

-automated builds.&nbsp;</p>

-

-<p>The variables set in the plug-in, fragment or feature <b>build.properties

-</b> will be used to generate scripts for

-Ant.&nbsp; PDE generates Ant scripts for creating

-individual plug-in and fragment build files and one overall script for building

-the feature JAR. This &quot;main&quot; script is also responsible for running individual

-script files in the right order (defined by the plug-in dependency chain). Each

-build file has the same name (<b>build.xml</b>) and is created as a sibling of the manifest

-files in the corresponding projects.</p>

-

-<p>Since Ant scripts use the replacement variables in <b>build.properties</b>, you can typically use them &quot;as is&quot;, without

-modifying the generated scripts. If you do modify them, you must not recreate the

-scripts every time you want to rebuild the component. </p>

-

-<p>To create scripts, you can simply select <b>Create Ant Build File</b> while a 

-suitable manifest file (plugin.xml, fragment.xml or feature.xml) is selected in 

-the Navigator or Package Explorer views. The command will generate

-the build script. After selecting <b>Run Ant...</b> from the pop-up menu while 

-the newly generated script file is selected, the following wizard will open:</p>

-

-<p align="center">

-<img border="0" src="images/feature-jar.png" alt="Ant execution wizard showing available targets"></p>

-

-<p align="left">The standard Ant wizard allows customization in two ways: by

-providing the execution arguments and by selecting one or more build targets.</p>

-

-<h4>Properties</h4>

-<p align="left">Ant arguments are typically used to provide property values that

-override default values and control the build process. Arguments are set using

-&quot;-Dproperty=value&quot;. The following properties are recognized:</p>

-

-<ul>

-  <li>

-    <p align="left"><b>bootclasspath</b> - if set, it replaces the default boot

-    classpath. Used when compiling cross-platform plug-ins (e.g. building a UI

-    plug-in for Windows using Linux)</p></li>

-  <li><b>build.result.folder</b> - where

-    the temporary files for the update JAR creation should be placed.

-    These files are usually the plug-in library JARs.</li>

-  <li><b>plugin.destination</b> - where

-    plug-in and fragment update JARs should be put. These JARs represent

-    entire plug-ins and fragments in a format suitable for publishing on an

-    Install/Update server and referencing by a feature. The typical layout of an

-    Update site is to have all the plug-in and fragment JARs in one place and

-    all the features in another. This argument is useful for placing plug-ins and

-    fragment directly into the desired directory (or the staging place on the

-    local machine before pushing the features onto the remote server).</li>

-  <li><b>feature.destination</b> - where

-    feature update JARs should be put.</li>

-</ul>

-<p>To adapt the behavior of the compiler, the following properties are recognized:</p>

-<ul>

-	<li><b>javacFailOnError</b> - stop the build when an error occurs when set to true. Default is false.</li>

-	<li><b>javacDebugInfo</b> - compile source with debug information when set to true. Default is true.</li>

-	<li><b>javacVerbose</b> - produce verbose output when set to true. Default is true.</li>

-	<li><b>javacSource</b> - value of the -source command-line switch.</li>

-	<li><b>javacTarget</b> - generate class files for specific VM version.</li>

-	<li><b>compilerArg</b> - additional command line arguments for the compiler.</li>

-</ul>

-

-<h4>Targets</h4>

-

-<p>When executing feature build scripts, the

-following targets are used to call individual targets of plug-ins or fragments.

-In order to specify what target to execute, the property <b>target</b> should be

-set (e.g. -Dtarget=refresh). One of the <b>all.*</b> targets serves as an iterator, whereas

-the actual target to execute is specified via the property <b>target</b>.</p>

-<ul>

-  <li><b>all.plugins</b> - for all listed plug-ins</li>

-  <li><b>all.fragments</b> - for all listed fragments</li>

-  <li><b>all.children</b> - for all listed plug-ins and fragments</li>

-  <li><b>build.jars</b> - build JARs for all feature children;</li>

-  <li><b>build.sources</b> - build source for all feature children;</li>

-  <li><b>build.update.jar</b> - generate a feature JAR in the format used by the install/update mechanism.

-	The above mentioned property <b>feature.destination</b> can be used to define

-	where to put the JAR;</li>

-  <li><b>zip.distribution</b> - creates a zip

-file with the feature and its plug-ins and fragments in an SDK-like structure

-but does not include source code;</li>

-  <li><b>zip.sources</b> - creates a zip file with the feature and its plug-ins and fragments in an SDK-like structure which only includes the source;</li>

-  <li><b>clean</b> - delete everything produced by running any of the target;</li>

-  <li><b>refresh</b> - performs a &quot;Refresh&quot; action in the current project, thus making the

-newly generated resources visible in the Navigator or Package Explorer.</li>

-  <li><b>zip.plugin</b> - creates a zip file with the binary and source contents of a plug-in with the following structure:

-  <blockquote>

-  id_version/<br>

-  &nbsp;&nbsp;&nbsp; contents

-</blockquote>where 'id' is the plug-in unique identifier

-and 'version' is the plug-in version. This zip file can be directly unzipped

-into the Eclipse installation directory as a form of a quick manual deployment.</li>

-</ul>

-

-

-

-

-

-</body>

-

-</html>


diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_feature_generating_antcommandline.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_feature_generating_antcommandline.htm
deleted file mode 100644
index 4d5f64b..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_feature_generating_antcommandline.htm
+++ /dev/null

@@ -1,97 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html>

-<head>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Command line Ant script generation</title>

-</head>

-<body>

-

-<h3>Generating Ant scripts from the command line</h3>

-

-<p>Ant scripts are typically generated using the Plug-in Development Environment (PDE), but it is also possible to generate

-them by hand or from other scripts.&nbsp;<br>

-Indeed PDE exposes Ant tasks to generate the various build scripts. Build script generation facilities

-reside in the following tasks.&nbsp; Arguments are also listed for each task.

-</p>

-

-<ul>

-  <li><b>eclipse.fetch</b>: generates an Ant script that fetches content from a CVS repository.

-  The eclipse fetch is driven by a file whose format is described below (see <a href="#directoryFileFormat">Directory file format</a>).

-   <p><i>elements</i> : the entry that will be fetched. The format expected is of the form type@id as specified in the directory file format;</p>

-   <p><i>buildDirectory</i> :  the directory into which fetch scripts will be generated and into which features and plug-in projects will be checked out;</p>

-   <p><i>directory</i> : the path to a directory file;</p>

-   <p><i>children</i> : optional, specifies whether the script generation for contained plug-ins and fragments should be invoked. Default is set to true;</p>

-   <p><i>cvspassfile</i> : optional, the name of a CVS password file;</p>

-   <p><i>fetchTag</i> : optional, overrides the tag provided in directory file by the given value;</p>

-   <p><i>configInfo</i> : optional, an ampersand separated list of configuration indicating the targeted configuration. The default is set to be platform independent;</p>

-   <p><i>recursiveGeneration</i> :  optional, specify whether or not fetch scripts should be generated for nested features. The default is set to true.</p>

-  </li>

-  <li><b>eclipse.buildScript</b>: generates a build.xml file for the given elements.

-  	<p><i>elements</i> : the entry to be fetched from the repository. Entry is expected to be of the form type@id as specified in the directory file format;</p>

-  	<p><i>buildDirectory</i> :  the directory where the features and plug-ins to build are located;</p>

-  	<p><i>children</i> : optional, specifies whether the script generation for contained plug-ins and fragments should be invoked. Default is set to true;</p>

-  	<p><i>recursiveGeneration</i> : optional, specified whether the script generation for contained features should be invoked. Default is set to true;</p>

-  	<p><i>devEntries</i> : optional, a comma separated list of directories to be given to the compile classpath;</p>

-  	<p><i>buildingOSGi</i> : optional, indicates if the target is 3.x. or 2.1;</p>

-  	<p><i>baseLocation</i> : optional, indicates a folder which contains installed features and folders;</p>

-  	<p><i>configInfo</i> : optional, an ampersand separated list of configuration indicates the targeted configuration. The default is set to be platform independent;</p>

-  	<p><i>pluginPath</i> : optional, a comma separated list of URLs pointing to installed plug-ins. If specified, this list must include the whole list of plug-ins to be compiled;</p>

-  	<p><i>archivesFormat</i> : optional, an ampersand separated list of configs and the expected output format for each of those. The format is separated by a dash (-) from the configuration. The values supported are: folder,  tar, zip, antZip,

-  	respectively meaning don't archive, use tar to create the archive, use the version of info zip available on the platform, use ant zip . The default value is antZip.</p>

-	<p><i>product</i> : optional, '/' separated path to the location of an RCP product being built. The first segment of the path must refer to the plug-in id of a plug-in containing the .product file.</p>

-  	<p><i>signJars</i> : optional, indicates if the scripts generated must sign jars for features and plug-ins. The default value is false. The parameters to the sign task are controlled by the following ant properties:

-  	sign.alias, sign.keystore and sign.storepass respectively being passed to the alias, keystore and storepass parameters from the ant <a href="http://ant.apache.org/manual/CoreTasks/signjar.html">signJar task</a>. The default value is false.</p>

-    <p><i>generateJnlp</i> : optional, indicates if a jnlp file should be generated for all the features being built.</p>

-    <p><i>outputUpdateJars</i> : optional, generates plug-ins and features in the update site format when set. The default value is false. Note that the site.xml is not generated nor updated.</p>

-    <p><i>forceContextQualifier</i> : optional, uses the given value to replace the .qualifier being by plug-ins and features.</p>

-  </li>

-</ul>

-

-<h4>Examples</h4>

-<pre>

-&lt;eclipse.fetch elements=&quot;bundle@org.eclipse.osgi&quot;

-		buildDirectory=&quot;c:\toBuild&quot;

-		directory=&quot;directory.txt&quot;

-		configInfo=&quot;win32,win32,x86 &amp; linux, motif, x86&quot;

-		/&gt;

-		

-&lt;eclipse.buildScript elements=&quot;bundle@org.eclipse.osgi&quot; 

-		buildDirectory=&quot;c:\toBuild&quot;

-		archivesFormat=&quot;macosx, carbon, ppc - tar&quot;/&gt;

-</pre>

-

-<h3><a name="directoryFileFormat">Directory file format</a></h3>

-

-Directory files are used to indicate where the plug-ins and features are located, as well as indicating which version

-should be fetched. It is a Java property file whose line format is &quot;type@id=version, repositoryLocation, password,path&quot;.

-<ul>

-<li><i>type</i>: a string describing the type of the element. It must be one of the following: plugin, fragment, feature, bundle;</li> 

-<li><i>id</i>: the name of the CVS module where the element is located. Note that the feature/plugin/fragment.xml must be in the root of this module;</li> 

-<li><i>version</i>: an existing version tag in the repository;</li> 

-<li><i>repositoryLocation</i>: a CVS repository location;</li> 

-<li><i>password</i>: optional, a password to connect to this repository;</li> 

-<li><i>path</i>: optional, the cvs module name and path to the element manifest.</li>

-</ul>

-<h4>Example of a directory file</h4>

-<tt>

-plugin@org.eclipse.pde.build=v20040622,:pserver:anonymous@dev.eclipse.org:/home/eclipse,<br>

-feature@org.eclipse.pde.builder=v20040622,:pserver:anonymous@dev.eclipse.org:/home/eclipse,,org.eclipse.pde.build/feature<br>

-plugin@org.eclipse.osgi=v20040617a,:pserver:anonymous@dev.eclipse.org:/home/eclipse,

-</tt>

-  

-<h3>Using the targets</h3>

-<p>The tasks previously described only work if Eclipse is running. In the particular scenario of executing Ant scripts using 

-Eclipse tasks,the scripts must be run using the Eclipse Ant Runner application. The command line for this particular

-case is the following:

-</p>

-<pre>  java -cp startup.jar org.eclipse.core.launcher.Main -application org.eclipse.ant.core.antRunner -buildfile build.xml

- </pre>

-<p>Note that the parameters appearing after the application are the parameters that are passed to Ant.

-</p>

-

-

-</body>

-

-</html>


diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_feature_generating_build.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_feature_generating_build.htm
deleted file mode 100644
index 822ff0d..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_feature_generating_build.htm
+++ /dev/null

@@ -1,104 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Feature build configuration</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h3>Build configuration</h3>

-<p>The build mechanism is driven by a build configuration.&nbsp; The

-build configuration for an individual plug-in, fragment, or feature is found

-in a <b> build.properties</b> file for the corresponding element.</p>

-

-<p>PDE project creation wizards generate the <b> build.properties</b> file when

-plug-in projects are created. The file contains information on how to compile source folders into

-JARs. This information can be indirectly updated in the Runtime page of the

-manifest editor. It can also be directly modified using the appropriate editor.</p>

-

-<p>PDE provides a simple editor for the <b> build.properties</b> that has form and source views.

-The file itself follows the Java properties format. You need to provide a number of

-keys and their corresponding values. Multiple values are separated using a comma

-as the delimiter. </p>

-

-<h4>Common properties</h4>

-<ul>

-  <li><b>bin.includes</b> - lists files that will included in the binary version of the plug-in being built;</li>

-  <li><b>bin.excludes</b> - lists files to exclude from the binary build;</li>

-  <br>

-  <li><b>qualifier</b> - when the element version number ends with <b>.qualifier</b> this indicates by which value ".qualifier" must be replaced. The value of the property can either be <b>context</b>, <b>&lt;value&gt;</b> or <b>none</b>. 

-  Context will generate a date according to the system date, or use the CVS tags when the built is automated. Value is an actual value. None will remove &quot;.qualifier&quot;. If the property is omitted, context is used.</li> 

-  <br>

-  <li><b>custom=true</b> - indicates that the build script is hand-crafted as opposed to automatically generated. Therefore no other value is consulted.</li>  

-</ul>

-

-<h4>Plug-in specific properties</h4>

-<ul>

-  <li><b>source.&lt;library&gt;</b> - lists source folders that will be compiled (e.g. <b>source.xyz.jar=src/, src-ant/</b>). 

-  If the library is specified in your plugin.xml or manifest.mf, the value should match it;</li>

-  <li><b>output.&lt;library&gt;</b> - lists the output folder receiving the result of the compilation;</li>

-  <li><b>exclude.&lt;library&gt;</b> - lists the files that should not be copied into the library by the compiler;</li>

-  <li> <b>extra.&lt;library&gt;</b> - extra classpaths used to perform automated build. Classpath can either be relative paths, or

-	platform urls referring to plug-ins and fragments of your development environment (e.g. <b>../someplugin/xyz.jar</b>, <b>platform:/plugins/org.apache.ant/ant.jar</b>).

-	Platform urls are recommended over relative paths;</li>

-  <li><b>manifest.&lt;library&gt;</b> - indicate the file that will be used as a manifest for the library. The file must be located in one of the source folder

-  being used as input of the jar.</li>

-  <br>	

-  <li><b>src.includes</b> - lists files to include in the source build;</li>

-  <li> <b>src.excludes</b> - lists files to exclude from the source build;</li>

-  <br>  

-  <li> <b>jars.extra.classpath</b> - <b>(deprecated)</b> same effect than extra.&lt;library&gt; except that the entries are applied to all libraries;</li>

-  <li> <b>jars.compile.order</b> - defines the order in which jars should be compiled (in case there are multiple libraries).</li>

-</ul>

-

-<p> The values

-defined for these keys ending with "includes" or "excludes" are expressed as Ant "patterns". Standard formats give the expected results.&nbsp; For example, &quot;*<b>.jar</b>&quot; 

-indicates all jar files in the top level directory. The patterns are not deep by default.&nbsp; If you want to

-describe all Java files for example, you should use the pattern "<b>**/*.java</b>".&nbsp;&nbsp;

-The pattern "<b>**</b>" matches any number of directory levels.&nbsp;

-Similarly, to describe whole sub-trees, use "<b>xyz/</b>".

- </p>

-<h4>Feature specific properties</h4>

-<ul>

-  <li><b>root</b> - list the files and folders that must be included in the root of the product. The different values supported are:

-  	<ul>

-  		<li>&lt;folderName&gt; - a relative path to a folder to be copied;</li>

-  		<li>file:&lt;fileName&gt; - a relative path to a file to be copied;</li>

-  		<li>absolute:&lt;folderName&gt; - an absolute path to a folder to be copied;</li>

-  		<li>absolute:file:&lt;fileName&gt; - an absolute path to a file to be copied;</li>

-  	</ul></li>

-  <li><b>root.&lt;config&gt;</b> - list the files and folders that must be included in the root of 

-the product when it is built for the specified configuration. config is composed of the three (3) segments of a configuration separated with a dot;</li>

-<br>

-	<li><b>root.permissions.&lt;permissionValue&gt;</b> - list the files and folders to chmod to the given value. Reference to folders must ends with a '/';</li>

-	<li><b>root.permissions.&lt;config&gt;.&lt;permissionValue&gt;</b> - list the files and folders to chmod to the given value for a specific configuration. Reference to folders must ends with '/';</li>

-	<br>

-	<li><b>root.link</b> - list by pairs (separated by a comma) the files and folders that need to be symbolicly linked. The first entry indicate the source (target in the unix terminology) and the second entry the link name;</li>

-	<li><b>root.link.&lt;config&gt;</b> - a comma separated list of pairs of files and folders that need to be symbolicly linked for a specific configuration. The first entry indicate the source (target in the unix terminology) and the second entry the link name;</li>

-	<br>

-	<li><b>generate.feature@&lt;featureId&gt;</b> - indicates that the source feature <b>featureId</b> will be the source feature for the feature indicated as value of this property. 

-	The values listed after the first comma indicates elements to be fetched from the repository;</li>

-	<li><b>generate.plugin@&lt;pluginId&gt;</b> - indicates that the source plug-in <b>pluginId</b> will be the source plug-in for the indicated as value of this property.</li>

-</ul>

-

-The following example has been extracted from the build.properties of the org.eclipse.platform feature. 

-<pre>bin.includes=epl-v10.html,eclipse_update_120.jpg,feature.xml,feature.properties,license.html

-

-root=rootfiles,file:../../plugins/org.eclipse.platform/startup.jar,configuration/

-root.permissions.755=eclipse

-

-root.linux.motif.x86=../../plugins/platform-launcher/bin/linux/motif,linux.motif

-root.linux.motif.x86.link=libXm.so.2.1,libXm.so.2,libXm.so.2.1,libXm.so

-root.linux.motif.x86.permissions.755=*.so*

-</pre>

-

-<p  >&nbsp;

- </p>

-

-

-</body>

-

-</html>


diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_feature_manifest.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_feature_manifest.htm
deleted file mode 100644
index 1c9c91e..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_feature_manifest.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Feature manifest editor</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h2>Feature manifest editor</h2>

-<p>The feature manifest editor uses the same concepts seen in the other PDE editors. 

-</p>

-<p align="center">

-<img border="0" src="images/feature-overview.png" alt="Feature manifest editor - Overview page" ></p>

-<p align="left">Information that is entered during the feature project setup can 

-  be changed on the Overview page. In addition, you can provide anr <b> update 

-  site</b> URL to be used by the Update Manager when searching for new updates.&nbsp; 

-</p>

-<p align="left">Branding information for primary features is stored in a 

-branding plug-in. If not explicitly set, Eclipse will assume that the branding 

-plug-in has the same identifier as the feature.</p>

-<p align="left">By default, your feature is treated as universally portable. You 

-  can add constraints by providing supported operating/windowing systems, languages 

-  and/or system architectures. This information will be used to ensure that your 

-  feature is not installed or shown in the context that does not match these constraints.</p>

-<p align="center"> <img border="0" src="images/feature-overview-info.png" alt="Feature manifest editor - Information page" ></p>

-<p align="left">Features are required to provide description, license and copyright 

-  information. This information can be edited on the Information page. Each of 

-  these three categories can be represented as either text or a URL that points 

-  to a valid HTML page. Although URL can be absolute, HTML pages are typically 

-  provided with the feature and URLs are relative to the project root.</p>

-<p align="left">The <strong>Sites To Visit</strong> tab lists URLs that are used 

-  to point users to other interesting features and/or sites.</p>

-<p align="center"> <img border="0" src="images/feature-content.png" alt="Feature manifest editor - Content page" ></p>

-<p align="left">The plug-ins and fragments to be packaged in this feature are 

-  listed on the <strong>Plug-ins</strong> page. If a plug-in and/or fragment contains 

-  platform-specific code, then environment conditions should be specified and 

-  associated with that plug-in or fragment.</p>

-<p align="center"><img src="images/included-features.PNG" alt="Included Features"></p>

-<p align="left">A feature may include other features, thus creating a feature 

-  hierarchy. When the feature is built, all included features are recursively 

-  built and packaged.</p>

-<p align="center"><img src="images/feature-dependencies.PNG" alt="Feature dependencies"></p>

-<p align="left">This section lists all features and plug-ins that must be present 

-  in the product before the Update Manager installs this feature. If any of these 

-  pre-requisites is missing, the feature will not be installed. The requirement 

-  can be based solely on plug-in IDs, or further constrained using expected versions 

-  and match rules.</p>

-<p align="center"> <img border="0" src="images/feature-advanced.png" alt="Feature Installations page" ></p>

-<p align="left">In addition to plug-ins, opaque data entries can be specified 

-  to carry custom feature information. These entries usually come together with 

-  custom install handlers. Install handlers can be used to perform non-standard 

-  install tasks and manipulate data entries once they are downloaded by the Update 

-  Manager. You can read more about this and other feature issues in Platform Install 

-  and Update guide.</p>

-

-

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_feature_setup.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_feature_setup.htm
deleted file mode 100644
index 1a5f22e..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_feature_setup.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Setting up a feature project</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h2>Setting up a feature project</h2>

-<p>Similar to plug-ins and fragments, PDE treats platform features as projects.

-PDE attaches a special &quot;feature&quot; capability to these projects to be

-able to run nature-specific builders. The project must have a feature manifest.</p>

-<p>PDE provides a wizard for setting up a feature project. Typically, you use

-this wizard to set up a feature once you are done developing plug-ins and

-fragments. However, you can create the feature at any stage of development and

-add new plug-ins later.</p>

-<h3>Example: Setting up a feature for plug-ins and fragments</h3>

-<p>Assuming that you have followed the previous examples, you should have &quot;XYZ

-Plug-in&quot; and &quot;German Fragment&quot; in your workspace already.&nbsp; We will

-create a sample feature and package these artifacts to be ready for delivery.</p>

-<ol>

-  <li>Bring up the feature wizard (<b>New-&gt;Project-&gt;Plug-in

-    Development-&gt;Feature

-    Project</b>)</li>

-  <li>Set the name of the project to &quot;com.example.feature&quot; and press <b>Next</b>.</li>

-  <li>Set the feature name to &quot;Sample Feature&quot;&nbsp; and the feature version to &quot;1.2.2&quot;. Set the provider to

-    &quot;Example&quot;.</li>

-  <li>In the following page, check the plug-in (XYZ Plug-in) and the fragment

-    (German Fragment).&nbsp;</li>

-  <li>Press <b>Finish</b>.</li>

-</ol>

-<p>You should now have the &quot;com.example.feature&quot; project in your workspace.&nbsp;

-The project should have <br>

-&quot;feature.xml&quot; file and feature manifest editor will open for editing.</p>

-

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_feature_synchronizing.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_feature_synchronizing.htm
deleted file mode 100644
index a461303..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_feature_synchronizing.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Synchronizing versions</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h2>Synchronizing versions</h2>

-<h3>Automatic synchronization at build time (Recommended)</h3>

-If the plug-in version changes frequently and/or developers do not have access 

-to the feature, the versions of plug-ins, fragments and included features can 

-be set to the special value <b>0.0.0</b> that will be replaced when exporting 

-the feature. This is especially convenient when plug-in version are automatically 

-upgraded using the qualifier tag. 

-<h3>UI driven synchronization</h3>

-<p>The versions of plug-ins and fragments should be synchronized with the

-version of the packaged feature so that you can manage plug-in, fragment, and

-feature versions consistently.&nbsp; Developers typically ignore individual

-manifest versions until it is time to deploy their features.&nbsp; The Update

-Manager uses feature versions to determine whether a plug-in is older or newer

-than one already installed.&nbsp; Plug-ins and fragments need to follow the same

-version number conventions so there is no confusion about which plug-in version belongs

-to which feature version.</p>

-<p>The most convenient way to synchronize versions is to pick the version of the

-feature and force it into all the plug-ins and fragments that the feature references. This operation updates manifest files, so you are required to close all the manifest editors

-before proceeding.</p>

-<h4>Example: Synchronizing versions in the feature editor</h4>

-<p>We will take our ongoing example and force the feature version (1.2.2) into

-&quot;XYZ Plug-in&quot; and &quot;German Fragment.&quot;</p>

-<ol>

-  <li>Open the component manifest editor.</li>

-  <li>Select <b>Synchronize versions...</b> from the popup menu. A wizard will open.</li>

-  <li>Select the first radio button (&quot;Force feature version...&quot;). Press

-    <b>Finish</b>.</li>

-  <li>Switch to the Content page verify that the versions are now

-    1.2.2.</li>

-  <li>Double-click on &quot;XYZ Plug-in&quot; and &quot;German Fragment&quot; 

-    objects and verify versions in their corresponding manifest editors.</li>

-</ol>

-<p align="center">

-<img border="0" src="images/feature-synchronizing.png" alt="Feature version synchronization wizard" ></p>

-

-<h3>&nbsp;</h3>

-</body>

-

-</html>


diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_features.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_features.htm
deleted file mode 100644
index e8fa3f7..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_features.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Features</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h2>Features</h2>

-<p>The platform is designed to accept updates and additions to the initial

-installation. The platform <b> Update Manager</b> handles this task by connecting to sites where updates are posted.

-(See the Workbench User Guide and <a href="../../org.eclipse.platform.doc.isv/reference/misc/eclipse-install.html">Platform

-Installation and Update</a> for more information about features and the

-Update Manager.)</p>

-<p>You need to package your work in a form

-that will be accepted by the Update Manager.&nbsp;&nbsp;When you deliver an update to the platform, you are contributing a

-<b>feature</b>.</p>

-<p>Features have a manifest that provides basic information

-about the feature and its content.&nbsp; Content may include plug-ins, fragments and

-any other files that are important for the feature. The delivery format for a

-feature is a JAR.&nbsp;</p>

-<p>In PDE, your typical development process looks like this:</p>

-<ol>

-  <li>Projects for plug-ins and fragments are created.</li>

-  <li>Code for plug-ins and fragments is created, tested and debugged.</li>

-  <li>When you want to make your code available to others, you create&nbsp; a

-    new feature project.</li>

-  <li>Individual build properties for each plug-in and fragment are tailored to

-    control what files are included and excluded from the packaging.</li>

-  <li>Versions are synchronized with previous versions of the feature, so that

-    the Update Manager will know that a feature is a newer version of an

-    already installed feature.</li>

-  <li>The feature JAR is built.</li>

-  <li>The feature is published on the update server

-    and made available for download.</li>

-</ol>

-

-

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_fragment.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_fragment.htm
deleted file mode 100644
index 0ce6df4..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_fragment.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Fragments</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h1>Fragments</h1>

-<p>A plug-in <b> fragment</b> is used to provide additional plug-in 

-functionality to an existing plug-in after it has been installed. Fragments are 

-ideal for shipping features like language or maintenance packs that typically 

-trail the initial products for a few months.&nbsp;Another frequent use of fragments 

-is to deliver OS or windowing system-specific features. </p>

-<p>When a fragment is detected by the platform and its parent plug-in is found, 

-the fragment's libraries, extensions and extension points are &quot;merged&quot; with 

-those of the parent plug-in.&nbsp; </p>

-<p>While this merging mechanism is good from a runtime point of view,

-developers need to view

-fragments as separate entities while working on them. Fragment development is

-often done by different teams, on a different schedule, sometimes even on

-different operating systems from the original plug-in.</p>

-<p>PDE provides full support for fragment development. Fragments can be viewed as

-&quot;limited plug-ins&quot;.&nbsp; They have all of the capability of regular

-plug-ins but have no concept of life-cycle. Fragments have no top-level class

-with &quot;startup&quot; and &quot;shutdown&quot; methods.</p>

-

-

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_fragment_example.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_fragment_example.htm
deleted file mode 100644
index cd350c3..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_fragment_example.htm
+++ /dev/null

@@ -1,76 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>German fragment example</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h2>Example: Writing a German fragment for XYZ Plug-in</h2>

-<p>The PDE wizards and editors that manipulate plug-ins and fragments are nearly the

-same.&nbsp; However, you must be aware of some important differences.</p>

-<p>We start by creating a new fragment project.&nbsp;&nbsp;</p>

-<p>On the first page of the New Fragment Project wizard, type the project name 

-  &quot;com.example.german&quot;.&nbsp; Accept the default values and press <b>Next</b>. 

-</p>

-<p>The <strong>Fragment Content</strong> page has three additional fields from 

-  the plug-in creation wizard: host plug-in id, parent plug-in version, and version 

-  match rule.</p>

-<p>Since we are writing a fragment for a specific plug-in, we can use the <b>Browse</b> 

-  button to select &quot;com.example.xyz&quot; in the plug-in selection dialog. 

-  Using the dialog, we could have also chosen any external plug-in.</p>

-<p align="center">

-<img border="0" src="images/fragment-content.png" alt="Fragment example - sample fragment content page" ></p>

-<p align="left">Once the project is created, it opens the fragment manifest editor.</p>

-<p align="center">

-<img border="0" src="images/fragment-overview.png" alt="Fragment example - manifest overview"></p>

-<p align="left"> As opposed to a plug-in, a fragment does no have a plug-in class 

-  since they follow the life cycle of their host plug-in.</p>

-<p align="left">We will add a similar action set as in the plug-in example, but

-this time in German.</p>

-<ol>

-  <li>Go to the Extensions page in the fragment manifest editor.

-    Press <b>Add</b> to launch the Extension wizard.</li>

- <li> Select &quot;org.eclipse.ui.actionSets&quot; from the list of extension

-    points. Press <b>Finish</b>.</li>

-  <li>Select the new action set. Select <b>New-&gt;actionSet</b> from the popup

-    menu.</li>

-  <li>In the Extension Element Details section, change the <b>label</b> property to

-    &quot;Deutsche Aktionsmenge.&quot;</li>

-  <li>In the All Extensions section, right-click on the new action set and select <b>New-&gt;menu</b>

-    from the popup.</li>

-  <li>Change the <b>label</b> property of the menu to &quot;Beispiel Menu&quot;

-    and the <b>id</b> property to &quot;beispielMenu.&quot;</li>

-  <li>Select the menu element again and choose <b>New-&gt;separator</b> from

-    the popup menu. Change its name to &quot;beispielGruppe&quot;

-    and save it.</li>

-  <li>Create a new &quot;action&quot; element (similar to step 6). Set the <b> label</b>

-    property to &quot;Beispiel Aktion.&quot; Set the <b> menubarPath</b> to &quot;beispielMenu/beispielGruppe.&quot;</li>

-  <li>Click on the <b>class</b> property hyperlink to generate a new class for your action.  

-  Use "com.example.german/src" as your source folder and leave the package name blank (uses the default package).  

-  Change the class name to &quot;DeutscheBeispielAktion&quot;. Press <b>Finish</b>.</li>

-  <li>When the Java editor with the new class opens, find the &quot;run&quot; method and

-    add the following:

-	<p style="color:#4444CC; position:relative; left:40px;"><code>System.out.println(&quot;Hallo, PDE welt!&quot;);

-	</code></p>

-  </li>

-  <li>Save and close the Java editor and fragment manifest editor.</li>

-  </ol>

-<p align="left">When you run the fragment using the &quot;Run&quot; tool bar

-button, the run-time platform instance should have the &quot;Deutsche Aktionsmenge&quot;

-action set available.&nbsp; (Use <b>Window-&gt;Customize Perspective...-&gt;Other</b> to

-get to the list of action sets). When you activate the action set, the &quot;Beispiel

-Menu&quot; menu should

-appear on the tool bar. When you select its menu item, you should see

-&quot;Hallo, PDE welt!&quot; in the Console. The runtime platform didn't

-see the German fragment directly. Instead, its plug-in registry resolved

-fragment references in such a way that the fragment's action set appeared to the

-platform as though it came directly from the XYZ Plug-in.</p>

-

-

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_manifest.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_manifest.htm
deleted file mode 100644
index 4d1eba2..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_manifest.htm
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Plug-in manifest editor</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h1>Plug-in manifest editor</h1>

-<p>When the plug-in project is created, the manifest file is open in the plug-in 

-manifest editor.</p>

-<p>This multi-page editor is the central place to manage your plug-in and can 

-  be used to edit all the plug-in's file (manifest.mf , plugin.xml and build.properties).</p>

-<p>When you use the editor's forms, PDE transparently handles the task of 

-writing the changes to the right files.</p>

-<p>The best way to learn about the plug-in manifest editor is to visit each

-page.</p>

-

-

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_manifest_dependencies.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_manifest_dependencies.htm
deleted file mode 100644
index e7ed927..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_manifest_dependencies.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Dependencies page</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h2>Dependencies page</h2>

-<p>The <strong>Dependencies</strong> page shows the dependencies that your plug-in 

-  has on other plug-ins.&nbsp; You must list on this page all the plug-ins that 

-  contribute code required on your plug-in project's classpath to compile.&nbsp;&nbsp; 

-  When you modify the list of dependencies and save the file, PDE will automatically 

-  update your classpath.</p>

-<p align="center">

-<img border="0" src="images/plugin-dependencies.png" alt="Dependencies editor page" ></p>

-<p align="left">&nbsp;

-</p>

-<p align="left"> Note that the order of the plug-ins in the list is important 

-  because it dictates the classloading order at runtime, so use the <strong>Up</strong> 

-  and <strong>Down</strong> buttons to organize the list as appropriate.</p>

-<p align="left">A plug-in listed in the <strong>Required Plug-ins</strong> section 

-  can be marked as re-exported in its Properties dialog.&nbsp; Re-exporting a 

-  dependency means that clients of your plug-in will get that dependency for free.&nbsp; 

-  It is important that you do not abuse this functionality and use it only when 

-  it makes sense to do so.</p>

-<p align="left">If your plug-in requires a specific version of a plug-in to function 

-  properly, then you can specify the version required along with the version match 

-  rule.&nbsp; You can read more about valid values in the Platform ISV guide.</p>

-<p align="left">The Eclipse runtime gives the flexibility to declare a dependency 

-  on a package without explicitly identifying its originating plug-in. These packages 

-  are listed in the <strong>Imported Packages</strong> section.</p>

-<p align="left">The <b>Dependency Analysis</b> contain several useful features 

-such as finding cycles in the dependency graph.&nbsp; Such cycles are forbidden 

-by the runtime, making the analysis useful for performing a sanity check on your plug-in's 

-dependency graph before testing it.</p>

-<p align="left">For a selected plug-in in the list, <b>Compute Dependency Extent</b> 

-will give you a list of all the Java types and all the extension points that 

-your plug-in needs from that dependency.&nbsp; So, in essence, it tells you why 

-you need that plug-in.</p>

-<p align="left">Since the JARs from all the plug-ins in the list of dependencies 

-will be on your plug-in's classpath at runtime, it is very important to not have 

-any dependencies that you do not need, as they would slow down classloading.&nbsp; 

-To find such extraneous entries and remove them, use the <b>Find Unused 

-Dependencies</b> feature available on this page.</p>

-<p align="left">&nbsp;</p>

-

-

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_manifest_extensionpoints.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_manifest_extensionpoints.htm
deleted file mode 100644
index 5a6ddf3..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_manifest_extensionpoints.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Extension points page</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h2>Extension points page</h2>

-<p>Extension points define new function points for the platform that other 

-plug-ins can plug into.</p>

-<p>The Extension Points page is the place to add, remove and edit extension 

-point declared by your plug-in.</p>

-

-<p align="center"><img src="images/plugin-expoint.png" alt="Extension Points page"></p>

-

-<p>An extension point has three attributes:</p>

-<ul>

-  <li>id - a required attribute whose value is a simple name</li>

-  <li>name - a required attribute whose value is a translatable string</li>

-  <li>schema - an optional attribute whose value is a relative path to the 

-  schema corresponding to this extension point.</li>

-</ul>

-<p>Although schema is an optional attribute, you are strongly encouraged to 

-provide a schema, so that PDE could use it to make it easy for developers to use 

-your extension point.</p>

-<p>PDE provides a <a href="pde_schema_editor.htm">schema editor</a> to help you 

-create a schema for your extension point.</p>

-<p>.</p>

-

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_manifest_extensions.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_manifest_extensions.htm
deleted file mode 100644
index c42e179..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_manifest_extensions.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Extensions page</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h2>Extensions page</h2>

-<p>Extensions are the

-central mechanism for contributing behavior to the platform. Unless your plug-in is a

-simple Java API library made available to other plug-ins, new behavior is contributed as an extension.</p>

-<p>The Extensions page is where you can add, remove and modify the extensions 

-your plug-in contributes to the platform.</p>

-<p align="center">

-<img src="images/actionSet-1.png" alt="Extensions editor page" border="0" ></p>

-<p>&nbsp;</p>

-<p>Each extension point comes with an xml schema specifying its grammar.&nbsp; 

-Your extension's syntax must therefore follow that grammar in order to be 

-processed correctly.&nbsp; When you create a new extension, PDE extracts the 

-grammar for the corresponding extension point and populates the context menu of 

-each element selected in the Extensions viewer with a list of valid child 

-elements that you can create.</p>

-<p>Also, for each selected element in the body of an extension, PDE populates 

-the Extension Element Details section with all the valid attributes for that 

-element.&nbsp; Required attributes are denoted with an asterisk.&nbsp; </p>

-<p>When you hover your mouse over an attribute name, a tooltip box appears 

-describing the purpose of that attribute.</p>

-<p>When an attribute expects the name of a Java class as a value, e.g. the <i>

-class</i> attribute above, clicking on the name of the attribute will open the 

-Java file specified if it exists.&nbsp; If the file does not exist, then 

-clicking on the <i>class</i> link will bring up the JDT New Class wizard to 

-create a new Java class on the fly.&nbsp; PDE will prime the wizard with the 

-correct superclass and/or interface when the schema for the extension point 

-specifies this information for the given attribute.</p>

-

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_manifest_overview.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_manifest_overview.htm
deleted file mode 100644
index 626a5ce..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_manifest_overview.htm
+++ /dev/null

@@ -1,29 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Overview page</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h2>Overview page</h2>

-<p>The Overview page is designed to be a quick reference on how to develop, test 

-and deploy a plug-in.&nbsp; It is also a navigational center where you can 

-follow the hyperlinks to navigate a particular page or execute a particular 

-command.</p>

-<p align="center">

-<img src="images/plugin-overview.png" alt="Overview editor page" border="0" ></p>

-<p align="left">The <strong>Plug-in Content</strong> section explains the structure 

-  and content of each section of the plug-in manifest.</p>

-<p align="left">The <strong>Testing</strong> section provides shortcuts to quickly 

-  launch a runtime workbench to test and debug the plug-in.</p>

-<p align="left">The <strong>Exporting</strong> section lists the steps required 

-  to successfully build and package the plug-in.</p>

-

-

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_manifest_runtime.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_manifest_runtime.htm
deleted file mode 100644
index bf957a1..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_manifest_runtime.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Runtime page</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h2>Runtime page</h2>

-<p align="left">The <strong>Runtime</strong> page shows all the packages that 

-  your plug-in makes visible to other plug-ins. </p>

-<p align="left">Press the <strong>Add...</strong> button in the <strong>Exported 

-  Packages</strong> section to add the <em>com.example.xyz</em> and <em>com.example.xyz.actions</em> 

-  packages to the list.</p>

-<p align="center"> <img src="images/plugin-runtime.png" alt="Runtime editor page" border="0" ></p>

-<p>The <strong>Package Visibility</strong> section allows you to control on a 

-  per-package basis the visibility of your plug-in code to downstream plug-ins. 

-  Refer to the <a href="restrictions.htm">Access Restrictions</a> document for 

-  full details.</p>

-<p>The <strong>Classpath</strong> section is the place to declare the names of 

-  the libraries that constitute the plug-in classpath. Since JAR'd plug-ins are 

-  the recommended format for 3.1, it is recommended to leave this section blank.</p>

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_manifest_source.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_manifest_source.htm
deleted file mode 100644
index f83fde4..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_manifest_source.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Source pages</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h2>Source pages</h2>

-<p align="left">The plug-in editor manages all three plug-in files at the same 

-  time. </p>

-<p align="left">The manifest.mf file is where all the plug-in data and dependencies 

-  is stored.</p>

-<p align="center"><img src="images/manifest-source.PNG" alt="manifest.mf source page"></p>

-<p align="left">The plugin.xml file contains the extensions and extension points 

-  declared the plug-in.</p>

-<p align="center"> <img border="0" src="images/plugin-source.png" alt="plugin.xml source page" ></p>

-<p align="left">The build.properties file contains all the information necessary 

-  to build the plug-in.</p>

-<p align="center"><img src="images/build-source.PNG" alt="Build source page"> 

-</p>

-<p align="left">PDE validates the manifest.mf and plugin.xml for semantic errors 

-  and flags violations. The list problems that PDE flags are listed on the <b> 

-  Plug-ins</b> tab of the <b>Plug-in Development &gt; Compilers</b> preference 

-  page:</p>

-<p align="center"> <img border="0" src="images/manifest-validate.png" align="center" alt="Plug-in Development compiler preferences" ></p>

-<p align="left">You can set the level of each to one of <i>Error</i>, <i>Warning</i> or 

-<i>Ignore</i>.</p>

-<p align="left">Note that for PDE to be able to detect some of these problems 

-(e.g. required attributes not defined, undefined extension attributes, etc.), 

-extension points you are using must have a valid schema associated with them.&nbsp; 

-See <a href="pde_schema.htm">Extension Point Schema</a> for more details.</p>

-

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_running.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_running.htm
deleted file mode 100644
index 533bf9f..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_running.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Running a plug-in</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h1>Running a plug-in</h1>

-<p>As you develop your plug-in in the workspace, the incremental Java compiler 

-  will compile your Java source code and place the <b> *.class</b> files into 

-  the <b>bin</b> directory of your PDE project. When you are ready to test your 

-  plug-in, you can launch a separate Eclipse application instance to test your 

-  new plug-in.</p>

-<p>The easiest way to launch an Eclipse applicaiton is via the link in the Testing 

-  section of the plug-in manifest editor's Overview page. <b> </b>This will immediately 

-  create a second Eclipse instance that will appear within seconds.</p>

-<p>To gain full control over the way the run-time workbench is launched, select <b>Run 

-&gt; Run...</b> from the main menu bar. This will bring up the Launch Configuration 

-Dialog.</p>

-<p align="center"> <img border="0" src="images/launch-dialog.png" alt="Eclipse Application - Main tab" ></p>

-<p align="left"><b>Workspace data</b> field defines the workspace that will be 

-  used by your application. The location of this runtime workspace must be different 

-  from the workspace of your host instance.</p>

-<p align="left">The default program to run is the<i> org.eclipse.sdk.ide </i>product.&nbsp; 

-  Launching it will result in a second workbench instance coming up whose constituent 

-  plug-ins are the workspace plug-ins and the plug-ins selected on the Target 

-  Platform preference page.&nbsp; </p>

-<p align="left">You can test your runtime workbench using the <b>JRE</b> of your 

-  choice and does not have to be the same one against which your plug-ins compile 

-  in the workspace.&nbsp; You can also specify any VM arguments that are appropriate 

-  for your testing.</p>

-<h2>Example:&nbsp; Running the Sample</h2>

-<p>Press <b>Run</b>.&nbsp; Another platform instance should open. You will see a 

-top menu item called &quot;Sample Menu&quot; with a single &quot;Sample Action&quot; item. Selecting it should 

-pop up a dialog containing the phrase &quot;Hello,  world&quot;.</p>

-

-

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_running_debugging.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_running_debugging.htm
deleted file mode 100644
index ceb37db..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_running_debugging.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Running under debug</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h2>Running under debug</h2>

-<p>The same Runtime Workbench launcher can be used for debugging. There is no

-special PDE support for debugging beyond the standard Java debugging support.&nbsp;</p>

-<p>Press the <b>Debug</b> tool bar button instead of <b>Run</b> in

-order to debug your plug-in. You can place breakpoints in

-your Java code and step through the source once you reach them.&nbsp;</p>

-<p> PDE ensures that

-there is no difference between workspace and external plug-ins when

-debugging.&nbsp; You can jump from class to class without knowing whether you are looking at the

-read-only source attached to external libraries or editable source in your

-workspace. For more information about debugging, see the JDT User Guide.</p>

-<p>If your target platform is not the same as the host and the target platform

-is a product that does not contain source code, you will not be able to step

-through source when the control moves into the platform classes. Some

-platform-based products may elect to ship without source and offer source as

-part of the product SDK. In that case, source code will be installed separately

-(usually later). Source code is delivered via plug-ins that contain ZIP files

-and plug into the PDE extension point for registering source code locations.

-When associating run-time libraries and source attachments, PDE will scan the

-available source code locations trying to find the matching source ZIP.</p>

-<p>Alternatively, you can download source code onto your disk drive and register

-the location manually using PDE preference page:</p>

-<p align="center">

-<img border="0" src="images/source-locations.png" alt="PDE Preferences - Source Code Locations" ></p>

-<p align="left">You will notice that some locations already exist if the host

-instance is the SDK itself and contains source plug-ins. You can add new

-locations by selecting <b>Add...</b> and choosing a valid local directory.</p>

-

-

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_running_plugins.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_running_plugins.htm
deleted file mode 100644
index 4f10b47..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_running_plugins.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Running with tracing</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h2>Choosing plug-ins to run</h2>

-<p>By default, the Eclipse application is launched with all the workspace plug-ins 

-  and all the plug-ins selected on the <strong>Plug-in Development &gt; Target 

-  Platform</strong> preference page.</p>

-<p>It is possible however to hand-select a subset of plug-ins to launch with on 

-  the <strong>Plug-ins</strong> tab of the launch configuration.</p>

-<p align="center">

-<img border="0" src="images/launch-plugins.png" alt="Run-time workbench launcher - plug-ins and fragments" ></p>

-<p> This gives you great flexibility, but with flexibility comes the danger of 

-  ending up with an invalid configuration. Use this feature carefully and press 

-  the <strong>Validate Plug-in Set </strong>often to ensure that all inter-plug-in 

-  dependencies in your subset are satisfied.</p>

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_running_tracing.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_running_tracing.htm
deleted file mode 100644
index 91d63cd..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_running_tracing.htm
+++ /dev/null

@@ -1,61 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Running with tracing</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h2>Running with tracing</h2>

-<p>The platform provides a mechanism for tracking the activity of your plug-in at runtime

-without full debugging. It allows you to use tracing flags that will cause

-tracing information to be printed on the standard output (or Console view). These flags are defined in files named

-&quot;<b>.options</b>&quot; and have the following syntax:</p>

-<font color='#4444CC'><pre>   &lt;plug-in Id&gt;/debug = true/false  (master switch)

-   &lt;plug-in Id&gt;/&lt;tracing flag&gt; = &lt;value&gt;

-</pre></font>

-<p>The first entry represents master switch for tracing your plug-in. If you

-call the method <b>isDebugging</b> in your plug-in class, it will

-return true if the value of this tracing variable is true. Other tracing flags

-are defined by you and their value can be obtained by using</p>

-<font color='#4444CC'><pre>   Platform.getDebugOption(optionName);

-</pre></font>

-<p>Most of the platform plug-ins define tracing flags, particularly the platform 

-  core. For a new plug-in developer, the most interesting set of tracing flags 

-  are those related to class loading, because they can allow tracing of plug-in 

-  loading problems. </p>

-<p align="center">

-<img border="0" src="images/launch-tracing.png" alt="Run-time workbench launcher - tracing" ></p>

-<h2>Example:&nbsp; Adding tracing support to your plug-in</h2>

-<p align="left">If you add tracing support to the plug-in under development, 

-your plug-ins will appear in the list of plug-ins that support tracing.</p>

-<p>In order to allow other developers to control your plug-in's tracing flags,

-you need to make these options known.&nbsp; This is typically done by placing a <b>.options</b> 

-file in your plug-in.&nbsp; The file lists all the supported flags as well as 

-their default values. </p>

-<p>We will now define a template <b> .options</b> file with a

-few tracing flags for our new plug-in.</p>

-<p>Select the <b>com.example.xyz</b> project created earlier and create a new file

-.<b>options</b>. When

-the default text editor opens, add the following entries:</p>

-<font color='#4444CC'><pre>   com.example.xyz/debug = true

-   com.example.xyz/debug/flag = true

-   com.example.xyz/debug/filter = *

-</pre></font>

-<p>When this file is saved, select <b>Run &gt; Run...</b> to open the launch dialog. 

-  Our plug-in should now show up in the list. When selected, it should show the 

-  newly defined flags with their default values.</p>

-<p align="center">

-<img border="0" src="images/xyz-tracing.png" alt="Run-time workbench launcher - tracing example" ></p>

-<p>Creating the <b>.options</b> file only defines the availability flags,

-allowing other plug-in developers to define the values of the tracing

-properties.&nbsp; You will still need to check the values of your tracing

-properties in your plug-in code using <b>Platform.getDebugOption()</b><b>.</b></p>

-

-

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_schema.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_schema.htm
deleted file mode 100644
index 54af151..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_schema.htm
+++ /dev/null

@@ -1,89 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Extension point schema</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h1>Extension point schema</h1>

-<p>Extensions are the key mechanism that a plug-in uses to add new features to the platform. Extensions cannot be arbitrarily

-created.&nbsp; They are declared using a clear specification defined by an

-extension point.</p>

-<p>Each extension must conform to the

-specification of the extension point that it is extending&nbsp; Each extension

-point defines attributes and expected values that must be declared by an

-extension.&nbsp; This information is maintained in the platform plug-in

-registry.&nbsp; Extension point providers query these values from the registry,

-so it's important to ensure that your plug-in has provided the expected

-information.</p>

-<p>In the most rudimentary form, an extension point declaration is very simple.&nbsp;

-It defines the id and name of the extension point.&nbsp; Any other information

-expected by the extension point is specific to that extension point and is

-documented elsewhere.&nbsp; (See the <a href="../../org.eclipse.platform.doc.isv/reference/extension-points/index.html">Platform

-Extension Point Reference</a> for the platform extension point definitions.)</p>

-<p>Reference documentation is useful, but it does not enable any programmatic

-help for validating the specification of an extension. For this reason, PDE introduces

-an extension point schema that describes extension points in a format fit for

-automated processing.</p>

-<p>Extension point schema is a valid XML schema as defined by W3C specification.

-However, the full XML schema specification is very complex and mostly unnecessary for this particular use. For this reason, PDE uses only a

-subset of XML schema features.&nbsp; Each extension point schema is a valid

-XML schema, but PDE does not use all the available features.</p>

-<h2>The benefits of extension point schemas</h2>

-<p>There are many benefits to describing your extension point using the PDE

-extension point XML schema:</p>

-<ol>

-  <li>Extension point grammar allows elements, attributes, and types to be

-    expressed formally. This

-    information can be used by tools to validate extensions or offer assistance

-    during creation of the extension.</li>

-  <li> XML schema provides for documentation

-    annotation that is similar to Javadoc in Java source. This mechanism ties

-    short text for valid elements and attributes to the declaration of

-    these elements and attributes. It is much easier to keep the documentation

-    in sync because removal of an attribute will also remove documentation for

-    the attribute.&nbsp; There is no need to update the reference document.</li>

-  <li>Reference documentation can be generated.&nbsp; PDE provides a tool that tracks changes in extension point

-    schemas and updates reference documentation on the fly.</li>

-  <li>You can provide additional metadata about the extension point that can be

-    used by tools that process the schema.&nbsp; PDE uses this

-    mechanism to add additional information about elements and attributes. For

-    example, if an attribute is marked as &quot;Java,&quot; PDE can provide assistance

-    while setting the value of this attribute by interacting with Java platform

-    features.</li>

-</ol>

-<h2>Limitations of PDE XML Schema support</h2>

-<p>PDE uses a small subset of XML schema.&nbsp; Using the full XML schema

-features set would be

-an overkill in this particular case. The subset allows

-almost 1-&gt;1 mapping from DTDs to schemas, but without DTD limitations. The

-following are the main limitations of the PDE extension point schema:</p>

-<ol>

-  <li>Only global element declarations are allowed.</li>

-  <li>Only local attribute declarations are allowed.&nbsp; Global attributes cannot be

-    declared.</li>

-  <li>The following compositors are supported:  <b>all</b>, <b>sequence</b>, <b>choice</b>

-    

-    and <b>group</b>.</li>

-  <li>There is no global type support.&nbsp; Types must be declared and immediately used.</li>

-  <li>Attributes can only have <b>string</b> and <b>boolean</b> types.</li>

-  <li>If an attribute is<b> </b> of type <b>string</b>, only

-    the <b>enumeration</b> restriction is

-    supported.</li>

-</ol>

-<p>If you write an XML schema using these restrictions, you will

-notice that the resulting file looks strikingly similar to an equivalent DTD

-that defines the same grammar. The advantage of schema is in annotations (both

-documentation and metadata). An additional advantage is that the XML schema is itself

-written in XML, which makes its processing and reading much easier.</p>

-<p>The list above is for reference only. You are most likely to

-define an XML schema using the PDE schema editor that will take care of generating the correct file.</p>

-

-

-</body>

-

-</html>


diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_schema_editor.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_schema_editor.htm
deleted file mode 100644
index 810453a..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_schema_editor.htm
+++ /dev/null

@@ -1,237 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Extension point schema editor</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h2>Extension point schema editor</h2>

-<p>You can open the extension point schema editor in two ways: as a by-product of

-creating a new extension point or by opening an existing extension point

-schema.&nbsp; By

-convention, new schemas have the same name as the extension point id with a <b>.exsd</b> file extension. They are placed in

-<b>schema</b> directory in your plug-in directory tree.&nbsp;&nbsp;</p>

-<p>When a new extension point is created in the PDE, the initial schema file will also be

-created and the schema editor will be opened for editing. You can define the schema

-right away, or close it and do it later. Making a complete

-extension point schema allows PDE to offer automated assistance to the users

-of your extension point.</p>

-<p>The PDE schema editor is based on the same concepts as the plug-in manifest

-editor.&nbsp; It has two form pages and one source page.&nbsp; Since XML schema is verbose and

-can be hard

-to read in its source form, you should use the form pages for most of the

-editing.&nbsp; The source page is useful for reading the resulting source code.</p>

-<h3>Example: Creating schema for the &quot;Sample Parsers&quot; extension point</h3>

-<p>We previously created the &quot;Sample Parsers&quot; extension point and the

-initial schema. We can now open the schema by going into the <b>schema</b>

-folder of our project and double-clicking on the <b>parsers.exsd</b> file.&nbsp;

-This will open the schema editor.</p>

-<p>We want to do the following:</p>

-<ol>

-  <li>Define the valid XML elements and attributes for the extension point.</li>

-  <li>Define the grammar (content model).</li>

-  <li>Provide documentation snippets that will be merged into a reference

-    document.</li>

-</ol>

-<p>Every extension point schema starts with a declaration of the

-&quot;extension&quot;

-element.&nbsp; We will add a new XML element called &quot;parser.&quot;</p>

-<ol>

-  <li>Press the button <b>New Element</b> in the <b>Extension Points Elements</b>

-    section.</li>

-  <li>Move to the Properties view and change its name from &quot;New_Element&quot;

-    to &quot;parser&quot;</li>

-  <li>While the new element is still selected, press the <b>New Attribute</b>

-    button. This will create &quot;new_attribute&quot; as its child. Change its <b>

-    name</b> to &quot;id&quot; and <b>use</b> to &quot;required&quot; in the property sheet.</li>

-  <li>While still in the property sheet, press the button &quot;Clone this

-    attribute&quot; available on the local tool bar. This will create a copy of

-    the attribute.&nbsp; This is useful because it allows us to quickly define all the

-    attributes without leaving the property sheet.</li>

-  <li>Change the name of the new attribute into &quot;name.&quot;</li>

-  <li>Clone the attribute again. This time, change the name to &quot;class.&quot;&nbsp; This attribute will be used to represent a fully

-    qualified name of the Java class that must implement a specific Java

-    interface. We need to specify this so that PDE can later take advantage of

-    it. Change <b>kind</b> from &quot;string&quot; to &quot;java.&quot;&nbsp;

-    Set the <b>basedOn</b> property

-    to <b>com.example.xyz.IParser</b>.&nbsp; (This interface does not exist yet, but we will

-    make it later.)</li>

-</ol>

-<p>So far, the schema editor should look like this:</p>

-<p align="center">

-<img border="0" src="images/schema-1.png" alt="Extension point schema editor - Definition page" ></p>

-<p align="left">We will now add an additional attribute that takes values from

-a discrete list of choices.&nbsp; This means we need to create an enumeration restriction of

-the base <b>string</b>  type.&nbsp; In addition, we will set a default value for the

-attribute.</p>

-<ol>

-  <li>

-    While the &quot;parser&quot; element is selected, press&nbsp;

-    the <b>New Attribute</b>

-    button. Change its name in the property sheet to &quot;mode.&quot;</li>

-  <li>

-    Click in the value cell of the &quot;restriction&quot; property

-    to bring the restriction dialog up.&nbsp;</li>

-  <li>

-    Change the restriction type from &quot;none&quot; to

-    &quot;enumeration.&quot;</li>

-  <li>

-    Add the following three choices: &quot;never,&quot; &quot;always,&quot;

-    and &quot;manual.&quot;&nbsp; (These are our three hypothetical modes for

-    the parser extension.)</li>

-</ol>

-<p align="left">The restriction dialog should look like

-this:</p>

-<p align="center">

-<img border="0" src="images/restriction-dialog.png" alt="Type restriction dialog" ></p>

-<p align="left">When the dialog is closed, change the &quot;use&quot; attribute to

-&quot;default&quot; and &quot;value&quot; attribute to &quot;always.&quot;&nbsp;

-This establishes the default value.&nbsp; Note that the status line shows an error message as you are typing the value,

-since it restricts valid values to the three enumeration choices. Once you

-finish typing, the error message should go away because &quot;always&quot; is a

-valid value.</p>

-<p align="left">Now that we have defined all of the elements and attributes, we need to

-define grammar. Our goal is to define that the &quot;extension&quot; element can have any

-number of &quot;parser&quot; elements as children.&nbsp;</p>

-<ol>

-  <li>

-    Select the &quot;extension&quot; element. Its initial content model shows

-    an empty sequence compositor.</li>

-  <li>

-    Select the sequence compositor and select <b>New-&gt;Reference-&gt;parser</b>

-    from the popup menu. This will add the parser reference to

-    the sequence compositor.</li>

-  <li>

-    The default cardinality of references is [1,1] which means

-    that there can be exactly one &quot;parser&quot; element. That is not quite what we

-    wanted. We select the &quot;parser&quot; reference and change the <b>maxOccurs</b> to &quot;unbounded.&quot;</li>

-</ol>

-<p align="left">After defining the grammar, the DTD approximation

-below the grammar section shows what the grammar for the selected element would

-look like in DTD.&nbsp; This information is provided to help

-developers who are still more comfortable with DTDs than XML schemas.</p>

-<p align="center">

-<img border="0" src="images/schema-2.png" alt="Extension point schema editor - element grammar" ></p>

-<p align="left">Now that we have defined valid elements, attributes and grammar,

-we need to provide some information about the extension point. There are two

-types of schema

-documentation snippets:</p>

-<ul>

-  <li>

-    Documentation about elements and attributes</li>

-  <li>

-    Documentation about the extension point usage, API, etc.</li>

-</ul>

-<p align="left">The first snippet type is provided in the Definition page of

-the schema manifest. As you select elements and attributes, you can add short

-text about them in the &quot;Description&quot; section. The expected format is raw HTML (as

-with Javadoc) and the text will be copied as-is into the final reference

-document.</p>

-<ol>

-  <li>

-    Select the &quot;id&quot; attribute of the

-    &quot;parser&quot; element and type the

-    following in the Description editor:<br>

-    a unique name that will be used to

-    reference this parser.</li>

-  <li>

-    Select the &quot;name&quot; attribute and

-    add the following text:<b><br>

-    </b>

-    a translatable name that will be used for presenting this parser in the UI.</li>

-  <li>

-    Select the &quot;class&quot; attribute and

-    add the following text (note the HTML tags):<b><br>

-    </b>

-    a fully qualified name of the Java class that implements &lt;samp&gt;com.example.xyz.IParser&lt;/samp&gt;

-    interface.</li>

-  <li>

-    Select the &quot;mode&quot; attribute and

-    add the following:<b><br>

-    </b>

-    an optional flag that indicates how often this parser instance will run

-    (default is &lt;samp&gt;always&lt;/samp&gt;).</li>

-</ol>

-<p align="left">We now have to provide a short text description of the extension point

-itself. In order to do that, we switch to the Documentation page:</p>

-<ol>

-  <li>

-    You should now be on the &quot;Overview&quot; tab.

-    In the text editor and add the following text:<br>

-    <p style="color:#4444CC; position:relative; left:25px">

-    This extension point is used to plug in

-    additional parsers. 

-    The parsers actually do not work - we have just used

-    them as an example of extension point schema.<br>

-    </p>

-    Press <b>Apply</b>.</li>

-  <li>

-    Click on the  &quot;Examples&quot; tab and add the following text:<br>

-<p style="color:#4444CC; position:relative; left:25px">

-The following is an example of the extension point usage:

-<font color="#4444CC"><pre>

-   &lt;p&gt;

-   &lt;pre&gt;

-      &lt;extension point=&quot;com.example.xyz.parsers&quot;&gt;

-         &lt;parser

-            id=&quot;com.example.xyz.parser1&quot;

-            name=&quot;Sample Parser 1&quot;

-            class=&quot;com.example.xyz.SampleParser1&quot;&gt;

-         &lt;/parser&gt;

-      &lt;/extension&gt;

-   &lt;/pre&gt;

-   &lt;/p&gt;

-</pre>

-</font>

-</p>

-    <p>Press <b>Apply</b>.</p>

-  </li>

-  <li>Select the &quot;API Information&quot; tab and add the following text:<br>

-  <p style="color:#4444CC; position:relative; left:25px">

-    Plug-ins that want to extend this extension point must implement &lt;samp&gt;com.example.xyz.IParser&lt;/samp&gt;

-    interface.<br>

-  </p>

-    Press <b>Apply</b>.</li>

-  <li>Select the &quot;Supplied Implementation&quot; tab and add the following text:<b><br>

-    </b>

-    <p style="color:#4444CC; position:relative; left:25px">

-    XYZ Plug-in provides default implementation of the parser.

-    </p>

-    Press <b>Apply</b>.<i>

-    <br>

-    </i></li>

-</ol>

-<blockquote><i>Note: Special consideration has to be taken when providing examples.

-Normally, PDE would treat the provided text as raw HTML and would not respect new

-line and white space greater than one character (i.e. ignorable white space). This

-is to be expected when regular text is concerned, but is extremely annoying when

-providing examples, where tabbing and vertical alignment is significant if the

-example is to look good. PDE has a compromise for this situation: if it detects

-the HTML tag &lt;pre&gt;, it will take the content as-is (preserving all characters

-without modification) until closing tag &lt;/pre&gt; is seen. This is why we can

-provide an example like the above and be confident that it will look good in the final

-reference document.</i></blockquote>

-<p>You may have already noticed that as you type documentation, more and more

-elements in the editor Outline view acquire a &quot;pen&quot; image overlay. This little

-indicator tells you that the element in question has some text associated with

-it - a quick way to check if the documentation is missing somewhere in the

-document.</p>

-<p align="center">

-<img border="0" src="images/schema-outline.png" alt="Extension point schema editor outline"></p>

-<p>Once we have finished with the documentation, we can take a look at the

-reference documentation. You can do it in two ways. All the time during your 

-work, you can preview the reference document by selecting Preview Reference 

-Document item from the pop-up menu. Alternatively, you can set up PDE 

-preferences (Preferences&gt;Plug-in Development&gt;Compilers, under Schema tab) to 

-automatically create reference documentation on each schema file change. 

-Regardless of the method to create it, the resulting document for

-this example would look like <a href="parsers.htm">this</a>.</p>

-

-

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_schema_using.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_schema_using.htm
deleted file mode 100644
index c45b122..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_schema_using.htm
+++ /dev/null

@@ -1,83 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Using extension point schema</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h2>Using extension point schema</h2>

-<p>Extension points defined by the plug-ins in your workspace are readily available

-to your own plug-in and other plug-ins. If an extension point schema has been

-defined for it, PDE can provide assistance when creating new extensions.

-This assistance includes:</p>

-<ul>

-  <li>Providing choices for the <b>New</b> pop-up menu so that only valid child elements

-    are added</li>

-  <li>Providing attribute information for the property sheet so that only valid

-    attributes are set</li>

-  <li>Providing correct attribute property editors that match the attribute types (boolean,

-    string, and enumeration).</li>

-  <li>Providing additional support for special attribute types (&quot;java&quot;

-    and &quot;resource&quot;).</li>

-  <li>Using the status line to show the first sentence of the documentation

-    snippet for attributes when selected in the property sheet.</li>

-</ul>

-<h3>Example: Using the &quot;Sample Parsers&quot; extension point</h3>

-<p>Before trying to use the extension point we defined before, we still need to

-define the expected interface. Select the <b>com.example.xyz</b> project in the Navigator

-and press the <img src="images/java-interface.png" alt="Create a Java Interface" > tool bar button to create a new Java interface.

-Be sure to set the package name to <b>com.example.xyz</b> and interface name to

-<b>IParser</b> before pressing <b>Finish</b>.&nbsp; Edit the interface to look like this:</p>

-<font color='#4444CC'><pre>   package com.example.xyz;

-

-   public interface IParser {

-      /**

-       * Run the parser using the provided mode

-       */

-      public void parse(int mode);

-   }

-</pre></font>

-<p>We now have the extension point, an XML schema for it, and the required

-interface. Be sure to save all of your open editors.&nbsp; Everything is now

-ready for our own plug-in or other plug-ins to

-contribute to the extension point.</p>

-<ol>

-  <li>Open the manifest editor for the <b>com.example.xyz</b> plug-in.</li>

-  <li>Switch to the Extensions page and press <b>New-&gt; Extension</b>.</li>

-  <li>You should have &quot;com.example.xyz.parsers&quot; available as a choice. Select

-    it and press <b>Finish</b>.</li>

-  <li>Select the newly added &quot;com.example.xyz.parsers&quot; element and popup the <b>New-&gt;parser

-    </b>menu. (We specified that our extension point can accommodate any

-    number of&nbsp; &quot;parser&quot; elements.)</li>

-  <li>Select the new parser element. The Extension Element Details section should show four

-    attributes: <b>id</b>, <b>name</b>, <b> class</b> and <b>mode</b>. Note how the status line shows the

-    short information about attributes as you select them. This information

-    comes directly from the extension point schema.</li>

-  <li>Change the <b> name</b> to &quot;Default Parser&quot;. Change the <b>mode</b> to

-    &quot;manual.&quot;&nbsp;</li>

-  <li>Click on the <b>class</b> hyperlink in the Extension Element Details section. Here you will see that PDE is seamlessly integrated with 

-  JDT's "New Java Class" wizard and utilizes schema attributes to automatically implement your IParser interface.

-  Create your class with "com.example.xyz/src" as your source folder, "com.example.xyz" as the package, and <b>DefaultParser</b> as the class name.

-  Press <b>Finish</b>.

-  </li>

-  <li>You should now be in the Java editor for the <b> DefaultParser</b> class. Notice

-    how it has implemented the right interface (<b>IParser</b>) and already has the stub

-    implementation of the &quot;parse&quot; method.<br>

-    Note that if you close the editor and click on the <b>class</b> hyperlink again,

-    the editor will reopen the <b>DefaultParser</b> class.  The "New Java Class" wizard will only appear 

-    when the class specified in the class attribute text field cannot be found; otherwise, the link will

-    open the class in an editor.</li>

-</ol>

-<p>As you can see, when you provide a complete XML schema for your extension

-point, it will help all your potential users by letting PDE to assist them and

-prevent them from making errors.</p>

-<p align="center"><font SIZE="2" COLOR="#3f7f5f">

-<img border="0" src="images/schema-usage.png" alt="Restriction choices appearing as choices in the property sheet cell editor" ></font></p>

-

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_setup.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_setup.htm
deleted file mode 100644
index f87c8a0..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_setup.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"><HTML>

-<HEAD>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-<title>Setting up PDE</title>

-</head>

-

-<BODY BGCOLOR="#ffffff">

-

-<h1>Preparing the workbench</h1>

-<p>While you can access the PDE platform contributions from any perspective, the 

-PDE perspective is arguably the best.&nbsp; </p>

-<p>From the default Resource perspective, open the PDE perspective via 

-<b>Window &gt; Open Perspective &gt; Other...

-</b> and

-choose <b>Plug-in Development</b> from the offered list.</p>

-<p align="center"> <img src="images/pdeperspective.png" alt="PDE perspective"></p>

-<p>&nbsp;</p>

-<p>In addition to the main views and toolbar actions that are useful for Java 

-development, the PDE perspective adds shortcuts to very frequently used wizards 

-such as the New Plug-in Project creation wizard, etc.  It also adds 

-views that are very important to a plug-in developer including the <b>Error Log</b> 

-view.</p>

-<h2>Error Log</h2>

-<p>The <b>Error Log</b> view captures all internal warnings and errors thrown by the platform 

-and by your code.&nbsp;

-These errors are written to a <b>.log</b> file that is located in the <b>

-.metadata</b> subdirectory of your workspace, and the Error Log view shows the 

-content of this file with a variety of convenient options such as filtering, 

-sorting, etc.</p>

-<p>By default, once the Error Log view is in your workspace, it will be brought 

-to the front upon the logging of new events.&nbsp; This feature can be turned 

-on/off in the drop down menu of the view.</p>

-<p>Other features of the log view include the ability to import any arbitrary 

-log file into the view, and to export the log contents into a file.</p>

-<p align="center"> <img border="0" src="images/errorLog.png" alt="Error Log view" ></p>

-

-

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_site_building.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_site_building.htm
deleted file mode 100644
index 5bf238d..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_site_building.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>
-<HEAD>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Building using update site editor</title>
-</head>
-
-<BODY BGCOLOR="#ffffff">
-
-<h2>Building plug-ins, fragments and features using update site editor</h2>
-<p align="left">
-Building an update site is a relatively simple task and most of the work is done 
-on the <b>Features</b> page of the update site editor.</p>
-<p align="center">
-<img border="0" src="images/site-features.png" ></p>
-<p align="center">&nbsp;
-</p>
-<p align="left">
-Features added to the <b>Managing the Site</b> section will be built recursively
-when you press <b>Build All</b>.&nbsp; This means that the features and all the
-plug-ins and fragments they include will be built in one batch operation.&nbsp; 
-The feature JARs end up in the <b>features/</b> folder of your site project and
-the plug-in JARs are placed in the <b>plugins/</b> folder of your site project.</p>
-<p align="left">
-If you would like to build one feature, select a feature and press the <b>Build</b> 
-button..</p>
-<p align="left">
-If you are dealing with features that include other features, only the root 
-feature needs to be listed, since its child features will automatically be 
-built.</p>
-<p align="left">Features that have environment constraints need to specify environments
-  in the<b>  Feature Environments</b> section. Select a feature and fill in the
-  values, or press <b>Synchronize...</b> button and let the environment be copied
-  from feature manifest to the site.</p>
-<p align="left">
-For easy browsing of your features on your update site, you can create 
-categories and organize your published features in these categories.&nbsp; A 
-feature may appear in &gt;= 0 categories.</p>
-<p align="left">
-To preview on what your web site would look like, save the site.xml file and
-  open 
-the index.html file at the root of your site project in a browser.</p>
-
-
-</body>
-
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_site_editor.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_site_editor.htm
deleted file mode 100644
index 968280f..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_site_editor.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>
-<HEAD>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Update site editor</title>
-</head>
-
-<BODY BGCOLOR="#ffffff">
-
-<h2>Update site editor</h2>
-<p>The update site editor uses the same concepts seen in the other PDE editors. 
-However, it is different from these editors in that it has an additional page 
-that controls how plug-ins, fragments and features in other projects within the 
-workspace are build and placed in the update site project's folders. </p>
-<p>Update site editor opens on site.xml file that is created by the update site 
-creation wizard. This file represents the site map and defines what will be made 
-available to Eclipse update manager when connecting to the update site.</p>
-<p>The editor has three pages that deal strictly with the file content:
-(Description, Features and Archives) and a Source page that shows you raw XML code of the
-site map.</p>
-<p align="center">
-<img border="0" src="images/site-description.png" alt="Feature manifest editor - Overview page" ></p>
-<p align="center">
-&nbsp;</p>
-
-
-</body>
-
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_site_previewing.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_site_previewing.htm
deleted file mode 100644
index f06c168..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_site_previewing.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>
-<HEAD>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Previewing update site</title>
-</head>
-
-<BODY BGCOLOR="#ffffff">
-
-<h2>Previewing an update site</h2>
-<p>After you have built your feature using the update site editor and all the 
-archives are in the right places, you can preview it in-place using the Update 
-Manager. </p>
-<h3>Example: building and previewing the sample update site</h3>
-<p>1. Open the New Install Wizard via <b>Help &gt; Software Updates &gt; Find and 
-Install...</b></p>
-<p>2. Select <b>Search for new features to install.</b></p>
-<p>3. On the<b> Update sites to visit</b> page, use the <b>New Local Site...</b> 
-button to locate the update site you have created.&nbsp; Select the new site
-and click
-<b>Finish</b>.</p>
-<p align="center">
-<img border="0" src="images/install-update-sites.png" ></p>
-<p align="left">&nbsp;</p>
-<p align="left">4.&nbsp; Drill down, and verify that the feature you created
-  has been 
-located by the Update Manager.&nbsp; </p>
-<p align="center">
-<img border="0" src="images/install-site-features.png" ></p>
-<p align="left">5.&nbsp; Select the feature, and click <b>Next</b>. Verify the
-  license information. Proceeding beyond that point in the Install Wizard will
-  go through
-  the steps
-  of the actual installation, which is not the focus here.&nbsp; </p>
-
-
-</body>
-
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_site_setup.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_site_setup.htm
deleted file mode 100644
index 4abab22..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_site_setup.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>
-<HEAD>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Setting up an update site project</title>
-</head>
-
-<BODY BGCOLOR="#ffffff">
-
-<h2>Setting up an update site project</h2>
-<p>An update site project is represented in the workspace with a project that 
-has a site.xml file at its root.</p>
-<p>PDE provides a wizard for setting up an update site project. Typically, you use
-this wizard to set up an update site once you are done developing plug-ins,
-fragments and features. However, you can create the site project at any stage of development.</p>
-<p>By default, an update site project is created local to your workspace. Since you 
-may want to host multiple versions of your plug-ins and features in this site, 
-you may want to keep the update site outside the workspace location. In that 
-case, change the location of the update site project during creation. If the 
-location you specified already contains the files the wizard is about to create, 
-it will keep them instead. This will allow you to create this project in more 
-than one workspace and point at the same shared location.</p>
-<h3>Example: Setting up an update site project</h3>
-<p>Assuming that you have followed the previous examples, you should have &quot;XYZ
-Plug-in&quot; and &quot;German Fragment&quot; in your workspace already, as well 
-as &quot;Sample Feature&quot; feature project.&nbsp; We will
-create an update site that can serve &quot;Sample Feature&quot; to the update manager.</p>
-<ol>
-  <li>Bring up the update site wizard via <b>New &gt; Project &gt; Plug-in
-    Development &gt; Update Site
-    Project</b>.</li>
-  <li>Set the name of the project to &quot;Update Site&quot;. </li>
-  <li>Set the update location to a non-default location.</li>
-  <li>Select the <b>Generate a web page</b> listing option.&nbsp; This will help 
-  advertise your features and plug-ins to the world.&nbsp; Click <b>Finish</b>.</li>
-</ol>
-<p align="center">
-<img border="0" src="images/site-new.png" ></p>
-<p>&nbsp;</p>
-
-</body>
-
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/pde_sites.htm b/bundles/org.eclipse.pde.doc.user/guide/pde_sites.htm
deleted file mode 100644
index 984b135..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/pde_sites.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>
-<HEAD>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working with update sites</title>
-</head>
-
-<BODY BGCOLOR="#ffffff">
-
-<h2>Working with update sites</h2>
-<p>Eclipse is capable of installing or updating features placed on the remote 
-servers. The features and plug-ins must be packaged in JARs and have a manifest 
-(site.xml) file that links them together. These files collectively form an Eclipse <b>
-update site</b>.</p>
-<p>PDE provides support for building update sites directly in the workspace. 
-Normally, update sites are placed on remote HTTP servers, but sites in the local 
-file systems are also valid and can be viewed in update manager. PDE uses this 
-property to provide for building and previewing update sites directly in the 
-workspace.</p>
-
-
-</body>
-
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/plugins_as_jars.htm b/bundles/org.eclipse.pde.doc.user/guide/plugins_as_jars.htm
deleted file mode 100644
index 539e7ba..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/plugins_as_jars.htm
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Plug-ins As JARs</title>
-</head>
-
-<body>
-<h2>Shipping Your Plug-in As A Single JAR</h2>
-<p>Eclipse 3.0 and previous was shipped such that each plug-in was a directory 
-  that contained code in a JAR, along with multiple other files. In order to improve 
-  the number of files that we ship along with the size of the Eclipse distributions, 
-  we have added support in Eclipse to be able to ship each plug-in as a single 
-  JAR file containing its code and other resources. </p>
-<p><strong>Converting A Plug-in to be Shipped as a JAR</strong></p>
-<ol>
-  <li>Change the classpath:</li>
-  <ul>
-    <li> If you have a <code>manifest.mf </code>then simply delete the <code>Bundle-Classpath</code> 
-      header.</li>
-    <li>Otherwise if you have a <code>plugin.xml</code> then change the library 
-      entry to be a dot like this: <br>
-      <code>&nbsp;&nbsp;&nbsp;&lt;runtime&gt;<br>
-      &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;library name=&quot;.&quot;&gt;<br>
-      &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;export name=&quot;*&quot;/&gt;<br>
-      &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/library&gt;<br>
-      &nbsp;&nbsp;&nbsp;&lt;/runtime&gt;</code></li>
-  </ul>
-  <li>Change the <code>build.properties</code>:</li>
-  <ul>
-    <li>Change all occurences of the old jar name to simply a dot. <code>(.)</code></li>
-    <li> There should be one on the <code>bin.includes</code> line. For instance, 
-      if your <code>bin.includes</code> line used to have <code>core.jar</code>, 
-      that will be replaced with a <code>.</code>.For instance: <code>bin.includes=about.html,.,META-INF/MANIFEST.MF</code></li>
-    <li> Change <code>source.foo.jar= </code> to <code>source..= </code>(that 
-      is source dot dot)</li>
-    <li> Change <code>output.foo.jar= </code> to <code>output..= </code> (that 
-      is output dot dot)</li>
-    <li>There may be others like <code>jars.compile.order</code>, etc</li>
-    <li> If you newly generated a <code>manifest.mf</code>, then add <code>META-INF/</code> 
-      to the <code>bin.includes</code>.</li>
-  </ul>
-  <li>Change the feature</li>
-  <ul>
-    <li>find all features that list your plug-in and add following to the related 
-      <code>&lt;plugin&gt;</code> tag:<br>
-      <code>&nbsp;&nbsp;&nbsp;&nbsp;unpack=&quot;false&quot;</code></li>
-  </ul>
-  <li>Change <code>about.html</code> linked content.</li>
-  <ul>
-    <li>If you have a basic <code>about.html</code> with no linked files, then 
-      you don't need to do anything.</li>
-    <li>If you have content in your plug-in which is linked from your <code>about.html</code> 
-      file, then that content must be placed in a directory named <code>&quot;about_files&quot;</code> 
-      at the root of the plug-in.</li>
-    <li>Make sure to change the links in the <code>about.html</code> to point 
-      to the new location of the files!</li>
-  </ul>
-</ol>
-      
-<p> If you have a custom build script (<code>build.xml</code>):</p>
-      <ul>
-        <li>You need to ensure that your script will still work against plug-ins 
-          that are JAR'd as well as plug-ins which aren't JAR'd.</li>
-      </ul>
-      <p>If you have other scripts (e.g. javadoc generation scripts):</p>
-      
-<ul>
-  <li>If the script assumes the layout of plug-ins and needs to add code JAR files 
-    to the classpath, then it must be modified to put the whole JAR'd plug-in 
-    on the classpath rather than the individual JARs.</li>
-</ul>
-
-      </body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/product_configuration.htm b/bundles/org.eclipse.pde.doc.user/guide/product_configuration.htm
deleted file mode 100644
index 31be2f4..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/product_configuration.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Product Configuration</title>
-</head>
-
-<body>
-<h2>Product Configuration</h2>
-<p>The RCP product export story is based on a .product file. This file contains 
-  all the data necessary to build a plugin-based or a feature-based product. Note 
-  that this file is a development-time artefact used by PDE only. It is NOT read 
-  or interpreted by the runtime and must/should not be included in the product 
-  being built.</p>
-<p>To create a product configuration, select <strong>File &gt; New... &gt; File 
-  &gt; Product Configuration</strong>.</p>
-<p align="center"><img src="images/product_config_wizard.PNG" width="435" height="499"> 
-</p>
-<p align="left">The only restriction is that the file extension be <em>.product</em>. 
-  Otherwise, the product configuration could be place in any folder, in any project 
-  in the workspace.</p>
-<p align="left">To initialize the configuration, you have three options:</p>
-<ol>
-  <li>Create a configuration file with basic settings: This option should be chosen 
-    when the user does not even know what a product is or if the user has not 
-    yet declared a product extension in his plug-in.</li>
-  <li>Use an existing product to initialize the file: This option should be chosen 
-    if you already have a plugin declaring a product extension. With this option, 
-    PDE will pre-populate the product configuration with as much data as possible 
-    given your product declaration.</li>
-  <li>Use a launch configuration: This optionn should be chosen if you have been 
-    testing your plug-in with an Eclipse application launch configuration that 
-    is filled with custom settings, and you want all those settings to get carried 
-    over to the product configuration.</li>
-</ol>
-<p>In our RCP mail example, we already have a product defined: <em>com.example.xyz.product</em>. 
-  So the second option is best. Select it and press <strong>Finish</strong>.</p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/product_editor.htm b/bundles/org.eclipse.pde.doc.user/guide/product_editor.htm
deleted file mode 100644
index f6f9dcc..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/product_editor.htm
+++ /dev/null

@@ -1,61 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Product Editor</title>
-</head>
-
-<body>
-<h2>Product Editor </h2>
-<p>The product editor is the one-stop shop where you can define all aspects of 
-  your product from basic definition to branding.</p>
-<p>Because we just created a product configuration based on the RCP template, 
-  most of the product information has already been filled out by PDE based on 
-  the plugin.xml of the <em>com.example.xyz</em> plug-in.</p>
-<p align="center"><img src="images/product-overview.PNG" alt="Product Overview Page"></p>
-<p align="left">The Product Definition section is where the product ID and name 
-  are specified, as well as the application that will run when the product is 
-  launched.</p>
-<p align="left">In this example, we will create a plugin-based product.</p>
-<p align="left">The <strong>Testing</strong> and <strong>Exporting</strong> sections 
-  should look familiar to the user as they are very similar to sections on the 
-  <strong>Overview</strong> page of the plug-in editor.</p>
-<p align="left">A very noticeable difference however is the first step in the 
-  Testing section: <em>Synchronize this configuration with the product's defining 
-  plug-in</em>. What does this mean?</p>
-<p align="left">Remember that the product configuration is for PDE use only and 
-  is not interpreted nor read by the runtime. Some of the data that enter in this 
-  file (e.g. product ID, application, window images, about image, etc.) must be 
-  copied to the plugin.xml file of your branding plug-in for these changes to 
-  take <strong>real</strong> effect at runtime. That's what the synchronize action 
-  does. It makes sure your plugin.xml contains up-to-date data and in sync with 
-  the product configuration.</p>
-<p align="center"><img src="images/product-configuration-plugins.PNG" alt="Product Configuration"></p>
-<p align="left">The Configuration page is where you list all the plug-ins and 
-  fragments that constitute the product.</p>
-<p align="left">A configuration file is a property file containing system properties 
-  read by the runtime upon startup. It is recommended to let PDE generate a default 
-  config.ini file for you.</p>
-<p align="left">You can also specify the program arguments and VM argumens with 
-  which your product is to be launched.</p>
-<p align="left">For a list of program and VM properties, refer to the <a href="../../org.eclipse.platform.doc.isv/reference/misc/runtime-options.html">Runtime 
-  options</a> document.</p>
-<p align="center"><img src="images/product-branding.PNG" alt="Product Branding"></p>
-<p align="left">The <strong>Branding</strong> page is where the product is given 
-  its identity: launcher name, custom images, custom launcher icons, splash screen 
-  and About dialog.</p>
-<p align="left">Name the executable that will launch your product <em>rcpmail</em>.</p>
-<p align="left">Customizing the launcher icons varies per platform. In this example, 
-  we will leave the default Eclipse icon as-is.</p>
-<p align="left">The splash screen must be named 'spash.bmp' and is assumed to 
-  be at the root of the product's defining plug-in if its location is not specified. 
-  In our example, the RCP mail plug-in project does have a splash.bmp at the right 
-  location, so the field can remain empty.</p>
-<p align="left">More customization can be done to the window images and the About 
-  dialog. All that data is already filled out by PDE using the plugin.xml of the 
-  <em>com.example.xyz</em> plug-in.</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/product_export.htm b/bundles/org.eclipse.pde.doc.user/guide/product_export.htm
deleted file mode 100644
index fa225ff..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/product_export.htm
+++ /dev/null

@@ -1,29 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Exporting a Product</title>
-</head>
-
-<body>
-<h2>Exporting a Product</h2>
-<p>From the Exporting section of the product editor, click on the <em>Eclipse 
-  product export wizard </em>to bring up the wizard.</p>
-<p align="center"><img src="images/product-export.PNG" alt="Product Export Wizard"></p>
-<p align="left">The root directory refers the name of the top-level directory 
-  of your product. You can name it anything you like and can be more than one 
-  segment. </p>
-<p align="left">The synchronization option also appears in the wizard and is checked 
-  by default to make sure that your plugin.xml does not contain stale data and 
-  is updated with the latest content from the product configuration.</p>
-<p align="left">A product can be exported to an archive or a directory. Select 
-  the <strong>directory</strong> option. Enter the name of a directory and Press 
-  <strong>Finish</strong>.</p>
-<p align="left">When the operation completes, go to that directory and launch 
-  your new customized product.</p>
-<p align="left">Simple as that!</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/rcp_project.htm b/bundles/org.eclipse.pde.doc.user/guide/rcp_project.htm
deleted file mode 100644
index 682d722..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/rcp_project.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>RCP Mail</title>
-</head>
-
-<body>
-<h2>Create an RCP Template </h2>
-<p>The first step in creating a fully-branded RCP product is to create a plug-in 
-  project with an RCP template</p>
-<p>Select <strong>File &gt; New... &gt; Project &gt; Plug-in Project</strong>. 
-  Click <strong>Next</strong>.</p>
-<p align="center"><img src="images/project-structure.png" alt="RCP project"></p>
-<p>Enter <em>com.example.xyz</em> for the name of the project. Click <strong>Next</strong>.</p>
-<p align="center"><img src="images/rcp_content.PNG" alt="RCP content page"></p>
-<p align="left">Choose <strong>Yes</strong> in the Rich Client Application section. 
-  Click <strong>Next</strong>.</p>
-<p align="center"><img src="images/rcp_mail.PNG" alt="RCP mail template"></p>
-<p align="left">Press <strong>Finish</strong>.</p>
-<p align="left">A new plug-in project will be created and the manifest editor 
-  will open.</p>
-<p align="center"><img src="images/plugin-overview.png" alt="RCP Overview page"></p>
-<p align="left">Click on the <em>Launch an Eclipse application</em> link in the 
-  <strong>Testing</strong> section. A splash screen will appear and go away. The 
-  fully-branded RCP mail application subsequently appears.</p>
-<p align="center"><img src="images/rcp_mail_app.PNG" alt="RCP mail application"></p>
-<p align="left">&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/restrictions.htm b/bundles/org.eclipse.pde.doc.user/guide/restrictions.htm
deleted file mode 100644
index 19b453d..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/restrictions.htm
+++ /dev/null

@@ -1,130 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<HTML>
-<HEAD>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Access Restrictions</title>
-</HEAD>
-
-<BODY>
-<p align="center"><font size="5"><b>Access Restrictions</b></font></p>
-<p align="left">The Eclipse 3.1 runtime gives the plug-in developer the <em><strong>option</strong></em> 
-  to control on a per-package basis the visibility of the plug-in code to downstream 
-  plug-ins. </p>
-<p align="left">A package may be classified as one of the following:</p>
-<ol>
-  <li>Accessible</li>
-  <li>Forbidden</li>
-  <li>Internal</li>
-  <li>Internal with friends</li>
-</ol>
-<p align="left">PDE translates these runtime visibility rules into compiler access 
-  restriction rules at compile time. As a result, a violation of a visibility 
-  rule is flagged by the compiler as a warning or an error, depending on the severity 
-  of that violation. </p>
-<p align="left">With the availability of this support at compile time, one is 
-  never get caught by surprise by classloading errors at runtime, and is always 
-  aware when referencing internal types.</p>
-<p align="left">&nbsp;</p>
-<p align="left"><b><font size="4">Accessible Packages</font></b></p>
-<p align="left">Accessible packages are visible to downstream plug-ins unconditionally.&nbsp;&nbsp; 
-  While API packages must clearly fall in this category, it is completely up to 
-  the developer to decide what other packages exported by the plug-in ought to 
-  be given this level of visibility.</p>
-<p align="left">In order to declare a package as accessible, you must list it in 
-the <b>Exported Packages</b> section on the <b>Runtime</b> of the plug-in 
-manifest editor and leave the default visibility setting as-is.</p>
-<p align="center"><img src="images/accessible.PNG" alt="Accessible Packages"></p>
-<p align="center">&nbsp;</p>
-<p align="left"><b><font size="4">Forbidden Packages</font></b></p>
-<p align="left">You can hide a package from downstream plug-ins at all times by 
-  <b>excluding</b> it from the list in the <b> Exported Packages</b> section on 
-  the <b>Runtime</b> page of the plug-in manifest editor.</p>
-<p align="left">References to types from a forbidden package result in classloading 
-  errors at runtime.</p>
-<p align="left">&nbsp;To avoid such unpleasant situations:</p>
-<ol>
-  <li>The compiler will flag references to forbidden packages with an <font color="#000000">ERROR</font><font color="#FF0000">.</font></li>
-  <li>Types from forbidden packages are <font color="#000000"> NOT</font> available 
-    as proposals in the content assist.</li>
-</ol>
-<p align="left"><u>Notes:</u></p>
-<ol>
-  <li> All plug-ins in the Eclipse SDK enumerate all their packages in the Exported 
-    Packages section.&nbsp; Therefore, none of the packages in the SDK have forbidden 
-    access.</li>
-  <li> The severity level for forbidden references is set on the <b>Java &gt; 
-    Compiler &gt; Errors/Warnings &gt; Deprecated and restricted API</b> preference 
-    page.
-    <p> It is strongly recommended that the severity of a forbidden reference 
-      is kept at ERROR.</p>
-  </li>
-</ol>
-<p align="center">&nbsp;&nbsp;&nbsp; <img src="images/forbidden_pref.PNG" alt="Forbidden preferences" border="0"></p>
-<p align="left"><font size="4"><b>Internal Packages</b></font></p>
-<p align="left">Internal packages are packages that are not intended for use by 
-  downstream plug-ins. <em><strong>These packages are visible to downstream plug-ins 
-  by</strong> <strong>default</strong></em>. </p>
-<p align="left">Internal packages are hidden from downstream plug-ins only when 
-  Eclipse is launched in <em><strong>strict</strong></em> mode (i.e. when you 
-  launch with the <em>-Dosgi.resolverMode=strict</em> VM argument).</p>
-<p align="left">Internal packages must be listed in the <b>Exported Packages</b> 
-  section on the <b>Runtime</b> page of the plug-in manifest editor with the <i> 
-  <b>hidden</b></i> option selected.</p>
-<p align="center"> <img src="images/discouraged.PNG" alt="discouraged access"></p>
-<p align="left">Two measures are taken to discourage downstream plug-ins from 
-  referencing internal packages:</p>
-<ul>
-  <li>The compiler flags references to such packages with a <font color="#000000">WARNING</font>.</li>
-</ul>
-<p align="center"><img src="images/compiler_discouraged.PNG" alt="discouraged access"></p>
-<ul>
-  <li>Types from discouraged packages are available as proposals in the content 
-    assist but with a <font color="#000000">LOWER PRIORITY</font>.</li>
-</ul>
-<p align="center"><img src="images/content_assist_discouraged.PNG" alt="discouraged content assist"></p>
-<p align="left">The severity level for discouraged references can be set on the
-<b>Java &gt; Compiler &gt; Errors/Warnings &gt; Deprecated and restricted API</b> 
-preference page.</p>
-<p align="center"> <img src="images/discourage_pref.PNG" alt="Discouraged preferences" border="0"></p>
-<p align="left">&nbsp;</p>
-<p align="left"><b><font size="4">Internal packages with friends</font></b></p>
-<p align="left">It is important for a plug-in to be able to grant full access 
-  to its internal packages to designated &quot;friend&quot; plug-ins. For instance, 
-  the PDE code is split across multiple plug-ins, and the <em>org.eclipse.pde.ui</em> 
-  plug-in should have full access to <em>org.eclipse.pde.core</em>'s internal 
-  packages.</p>
-<p align="left">In the example below, the friends (the <em>org.eclipse.pde</em> 
-  and <em>org.eclipse.pde.ui</em> plug-ins) have full access to the <em>org.eclipse.pde.internal.core.bundle</em> 
-  package from the <em>org.eclipse.pde.core </em>plug-in.</p>
-<p align="center"><img src="images/friends.PNG" alt="Friends"></p>
-<p align="left">The friends are free to reference any type from the <em>org.eclipse.pde.internal.core.bundle</em> 
-  package with the compiler's blessing. </p>
-<p align="left">If, on the other hand, any other plug-in references a type from 
-  the <em>org.eclipse.pde.internal.core.bundle</em> package, the compiler flags 
-  the reference as a discouraged reference as described in the previous section.</p>
-<p align="left">&nbsp;</p>
-<p align="left"><strong><font size="4">How to enable access restrictions</font></strong></p>
-<p align="left">To take advantage of the PDE access restriction support, the only 
-  requirement is that the plug-ins in question contain an OSGi bundle manifest.mf. 
-  PDE, which manages the plug-in classpath, then takes care of the rest.</p>
-<p align="left">If the plug-in does not contain a manifest.mf file, that file 
-  can be created as follows:</p>
-<ol>
-  <li>Open the plugin.xml in the plug-in manifest editor.</li>
-  <li>In the <strong>Plug-in Content</strong> section of the <strong>Overview</strong> 
-    page, click on the '<strong>create an OSGi bundle manifest</strong>' link.</li>
-</ol>
-<div align="center">
-  <p><img src="images/convert.PNG" alt="convert to manifest.mf"></p>
-  <p align="left">&nbsp;</p>
-  <p align="left"><strong><font size="4">Inspecting access rules</font></strong></p>
-  <p align="left">You can inspect the access restriction rules imposed on each 
-    classpath entry by PDE on the <strong>Java Build Path</strong> property page 
-    of your plug-in project. </p>
-  <p align="center"><img src="images/properties.PNG" alt="Java Build Path Properties"></p>
-</div>
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/schema.css b/bundles/org.eclipse.pde.doc.user/guide/schema.css
deleted file mode 100644
index 4efbf26..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/schema.css
+++ /dev/null

@@ -1,66 +0,0 @@
-H6.CaptionFigColumn#header {

-	font-size:16px; 

-	display:inline

-}

-

-P.Note#copyright {

-	font-size: smaller; 

-	font-style: normal;

-	color: #336699; 

-	display:inline;

-	margin-top: 3.000000pt;

-	margin-bottom: 11.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 0.000000pt;

-}

-

-P.Code#dtd {

-	color: #800000; 

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 10.000000pt;

-}

-

-P.Code#dtdAttlist {

-	color: #800000; 

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 20.000000pt;

-}

-

-P.Code#tag {

-	color: #000080; 

-	display:inline;

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 0.000000pt;

-}

-

-P.Code#cstring {

-	color: #008000; 

-	display:inline;

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 0.000000pt;	

-}

-

-.ConfigMarkup#elementDesc {

-	color: black;

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 10.000000pt;

-}

-

-.ConfigMarkup#attlistDesc {

-	color: black;

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 32.000000pt;

-}

-


diff --git a/bundles/org.eclipse.pde.doc.user/notices.html b/bundles/org.eclipse.pde.doc.user/notices.html
deleted file mode 100644
index 03ff544..0000000
--- a/bundles/org.eclipse.pde.doc.user/notices.html
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <LINK REL="STYLESHEET" HREF="book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Legal Notices</title>
-</head>
-<body>
-
-<h3>
-<a NAME="Notices"></a>Notices</h3>
-<p>
-The material in this guide is Copyright (c) IBM Corporation and others 2000, 2005.
-</p>
-<p>
-<a href="about.html">Terms and conditions regarding the use of this guide.</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/pdeOptions b/bundles/org.eclipse.pde.doc.user/pdeOptions
deleted file mode 100644
index d5448a5..0000000
--- a/bundles/org.eclipse.pde.doc.user/pdeOptions
+++ /dev/null

@@ -1,24 +0,0 @@
--quiet
--charset "iso-8859-1"
--sourcepath "../org.eclipse.pde.core/src:../org.eclipse.pde.ui/src:../org.eclipse.pde.build/src"
--d reference/api
--classpath  @rt@:../org.eclipse.core.boot/@dot:../org.eclipse.debug.core/@dot:../org.eclipse.compare/@dot:../org.eclipse.help/@dot:../org.eclipse.help.ui/@dot:../org.eclipse.core.resources/@dot:../org.eclipse.core.runtime/@dot:../org.eclipse.swt.motif.linux.x86/@dot:../org.eclipse.ui/@dot:../org.eclipse.jdt.core/@dot:../org.eclipse.jdt.ui/@dot:../org.eclipse.jdt.launching/@dot:../org.eclipse.jdt.debug/jdi.jar:../org.eclipse.debug.ui/@dot:../org.eclipse.search/@dot:../org.eclipse.jface/@dot:../org.eclipse.jface.text/@dot:../org.eclipse.text/@dot:../org.eclipse.ui.editors/@dot:../org.eclipse.ui.views/@dot:../org.eclipse.ui.workbench/@dot:../org.eclipse.ui.workbench.texteditor/@dot:../org.eclipse.core.variables/@dot:../org.eclipse.ui.ide/@dot:../org.eclipse.jdt.junit/@dot:../org.eclipse.pde.core/@dot:../org.eclipse.pde.ui/@dot:../org.eclipse.osgi/@dot:../org.eclipse.osgi.services/@dot:../org.eclipse.osgi.util/@dot:../org.eclipse.core.jobs/@dot:../org.eclipse.equinox.registry/@dot:../org.eclipse.equinox.common/@dot:../org.eclipse.equinox.preferences/@dot:../org.eclipse.equinox.supplement/@dot:../org.eclipse.core.runtime.content/@dot:../org.eclipse.core.runtime.jobs/@dot:../org.eclipse.core.runtime.preferences/@dot:../org.eclipse.core.contenttype/@dot
--breakiterator
--use
--splitIndex
--windowtitle "Eclipse PDE API Specification"
--doctitle "Eclipse PDE API Specification"
--header "<b>Eclipse PDE</b><br>Release 3.2"
--bottom "Copyright (c) IBM Corp. and others 2000, 2006.  All Rights Reserved."
--link http://java.sun.com/j2se/1.4/docs/api
--linkoffline ./../../../org.eclipse.platform.doc.isv/reference/api ../org.eclipse.platform.doc.isv/reference/api
--linkoffline ./../../../org.eclipse.jdt.doc.isv/reference/api ../org.eclipse.jdt.doc.isv/reference/api
--link http://bundles.osgi.org/javadoc/r4
-
-org.eclipse.pde.build
-org.eclipse.pde.core
-org.eclipse.pde.core.build
-org.eclipse.pde.core.plugin
-org.eclipse.pde.ui
-org.eclipse.pde.ui.launcher
-org.eclipse.pde.ui.templates

diff --git a/bundles/org.eclipse.pde.doc.user/pdeOptions.txt b/bundles/org.eclipse.pde.doc.user/pdeOptions.txt
deleted file mode 100644
index e7031a3..0000000
--- a/bundles/org.eclipse.pde.doc.user/pdeOptions.txt
+++ /dev/null

@@ -1,23 +0,0 @@
--quiet
--charset "iso-8859-1"
--sourcepath "../org.eclipse.pde.core/src;../org.eclipse.pde.ui/src;../org.eclipse.pde.build/src"
--d reference/api
--classpath @rt@;../org.eclipse.core.boot/@dot;../org.eclipse.debug.core/@dot;../org.eclipse.compare/@dot;../org.eclipse.help/@dot;../org.eclipse.help.ui/@dot;../org.eclipse.core.resources/@dot;../org.eclipse.core.runtime/@dot;../org.eclipse.swt.win32.win32.x86/@dot;../org.eclipse.ui/@dot;../org.eclipse.jdt.core/@dot;../org.eclipse.jdt.ui/@dot;../org.eclipse.jdt.launching/@dot;../org.eclipse.jdt.debug/jdi.jar;../org.eclipse.debug.ui/@dot;../org.eclipse.search/@dot;../org.eclipse.jface/@dot;../org.eclipse.jface.text/@dot;../org.eclipse.text/@dot;../org.eclipse.ui.editors/@dot;../org.eclipse.ui.views/@dot;../org.eclipse.ui.workbench/@dot;../org.eclipse.ui.workbench.texteditor/@dot;../org.eclipse.core.variables/@dot;../org.eclipse.ui.ide/@dot;../org.eclipse.jdt.junit/@dot;../org.eclipse.pde.core/@dot;../org.eclipse.pde.ui/@dot;../org.eclipse.osgi/@dot;../org.eclipse.osgi.services/@dot;../org.eclipse.osgi.util/@dot;../org.eclipse.core.jobs/@dot;../org.eclipse.equinox.registry/@dot;../org.eclipse.equinox.common/@dot;../org.eclipse.equinox.preferences/@dot;../org.eclipse.equinox.supplement/@dot-breakiterator;../org.eclipse.core.runtime.content/@dot;../org.eclipse.core.runtime.jobs/@dot;../org.eclipse.core.runtime.preferences/@dot;../org.eclipse.core.contenttype/@dot
--use
--splitIndex
--windowtitle "Eclipse PDE API Specification"
--doctitle "Eclipse PDE API Specification"
--header "<b>Eclipse PDE</b><br>Release 3.2"
--bottom "Copyright (c) IBM Corp. and others 2000, 2006.  All Rights Reserved."
--link http://java.sun.com/j2se/1.4/docs/api
--linkoffline ./../../../org.eclipse.platform.doc.isv/reference/api ../org.eclipse.platform.doc.isv/reference/api
--linkoffline ./../../../org.eclipse.jdt.doc.isv/reference/api ../org.eclipse.jdt.doc.isv/reference/api
--link http://bundles.osgi.org/javadoc/r4
-
-org.eclipse.pde.build
-org.eclipse.pde.core
-org.eclipse.pde.core.build
-org.eclipse.pde.core.plugin
-org.eclipse.pde.ui
-org.eclipse.pde.ui.launcher
-org.eclipse.pde.ui.templates

diff --git a/bundles/org.eclipse.pde.doc.user/plugin.properties b/bundles/org.eclipse.pde.doc.user/plugin.properties
deleted file mode 100644
index 965fe94..0000000
--- a/bundles/org.eclipse.pde.doc.user/plugin.properties
+++ /dev/null

@@ -1,12 +0,0 @@
-###############################################################################

-# Copyright (c) 2000, 2005 IBM Corporation and others.

-# All rights reserved. This program and the accompanying materials

-# are made available under the terms of the Eclipse Public License v1.0

-# which accompanies this distribution, and is available at

-# http://www.eclipse.org/legal/epl-v10.html

-#

-# Contributors:

-#     IBM Corporation - initial API and implementation

-###############################################################################

-pluginName=Eclipse Plug-in Development User Guide

-providerName=Eclipse.org


diff --git a/bundles/org.eclipse.pde.doc.user/plugin.xml b/bundles/org.eclipse.pde.doc.user/plugin.xml
deleted file mode 100644
index 559465d..0000000
--- a/bundles/org.eclipse.pde.doc.user/plugin.xml
+++ /dev/null

@@ -1,46 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>

-<?eclipse version="3.0"?>

-<plugin>

-

-   

-<!-- ============================================================================= -->

-<!-- Define primary TOC                                                            -->

-<!-- ============================================================================= -->

-   <extension

-         point="org.eclipse.help.toc">

-      <toc

-            file="toc.xml"

-            primary="true"

-            extradir="guide/intro">

-      </toc>

-      <index path="index"/>

-   </extension>

-<!-- ============================================================================= -->

-<!-- Define TOCs                                                                   -->

-<!-- ============================================================================= -->

-   <extension point="org.eclipse.help.toc"> 

-       <toc file="topics_Reference.xml" />   

-   </extension>  

-<!-- ============================================================================= -->

-<!-- Define help context                                                           -->

-<!-- ============================================================================= -->

-

-   <extension

-         point="org.eclipse.help.contexts">

-      <contexts

-            file="contexts_PDE.xml">

-      </contexts>

-   </extension>

-   

-<!-- ============================================================================= -->

-<!-- Define javadoc locations                                                      -->

-<!-- ============================================================================= -->

-   <extension

-         point="org.eclipse.pde.core.javadoc">

-      <javadoc path="reference/api">

-         <plugin id="org.eclipse.pde.core"/>

-         <plugin id="org.eclipse.pde.ui"/>

-      </javadoc>

-   </extension>

-   

-</plugin>


diff --git a/bundles/org.eclipse.pde.doc.user/reference/extension-points/index.html b/bundles/org.eclipse.pde.doc.user/reference/extension-points/index.html
deleted file mode 100644
index c59a06a..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/extension-points/index.html
+++ /dev/null

@@ -1,23 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>PDE Extension Points</title>
-<link rel="stylesheet" type="text/css" HREF="../../book.css">
-</head>
-<body>
-<h1> PDE Extension Points </h1>
-<p>The following extension points can be used to extend the capabilities of the 
-  PDE infrastructure: </p>
-<ul>
-  <li><a href="org_eclipse_pde_build_fetchFactories.html">org_eclipse_pde_build_fetchFactories</a></li>
-  <li><a href="org_eclipse_pde_core_javadoc.html">org.eclipse.pde.core.javadoc</a></li>
-  <li><a href="org_eclipse_pde_core_source.html">org.eclipse.pde.core.source</a></li>
-  <li><a href="org_eclipse_pde_ui_newExtension.html">org.eclipse.pde.ui.newExtension</a></li>
-  <li><a href="org_eclipse_pde_ui_pluginContent.html">org.eclipse.pde.ui.pluginContent</a></li>
-  <li><a href="org_eclipse_pde_ui_templates.html">org.eclipse.pde.ui.templates</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/misc/index.html b/bundles/org.eclipse.pde.doc.user/reference/misc/index.html
deleted file mode 100644
index 8f4bc88..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/misc/index.html
+++ /dev/null

@@ -1,20 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta name="Author" content="IBM">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>PDE - Other Reference Information</title>
-</head>
-<body>
-<h1> Other Reference Information</h1>
-<p>The following specifications, white papers, and design notes describe various 
-  aspects of the PDE. </p>
-<ul>
-  <li><a href="overview-pde.html">Map of PDE Plug-ins</a> 
-  </li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/misc/overview-pde.html b/bundles/org.eclipse.pde.doc.user/reference/misc/overview-pde.html
deleted file mode 100644
index 3bf0948..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/misc/overview-pde.html
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta name="Author" content="IBM">
-<title>PDE Overview</title>
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-</head>
-<body>
-<h1>Map of PDE Plug-ins</h1>
-<p>The PDE provides a comprehensive plug-in development 
-  environment. </p>
-<p>PDE itself is divided up into a number of separate 
-  plug-ins. The following table shows which API packages are found in which plug-ins 
-  (the most commonly referenced API packages are highlighted). This table is useful 
-  for determining which plug-ins a given plug-in should include as prerequisites. 
-</p>
-<table border="1" width="80%" align="center">
-  <tbody> 
-  <tr> 
-    <td><b>API Package</b></td>
-    <td><b>Plug-in id</b></td>
-  </tr>
-  <tr> 
-    <td><tt>org.eclipse.pde.core[.*]</tt></td>
-    <td><tt>org.eclipse.pde.core</tt></td>
-  </tr>
-  <tr> 
-    <td><tt>org.eclipse.pde.ui[.*]</tt></td>
-    <td><tt>org.eclipse.pde.ui</tt></td>
-  </tr>
-  </tbody> 
-</table>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/schema.css b/bundles/org.eclipse.pde.doc.user/schema.css
deleted file mode 100644
index 4efbf26..0000000
--- a/bundles/org.eclipse.pde.doc.user/schema.css
+++ /dev/null

@@ -1,66 +0,0 @@
-H6.CaptionFigColumn#header {

-	font-size:16px; 

-	display:inline

-}

-

-P.Note#copyright {

-	font-size: smaller; 

-	font-style: normal;

-	color: #336699; 

-	display:inline;

-	margin-top: 3.000000pt;

-	margin-bottom: 11.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 0.000000pt;

-}

-

-P.Code#dtd {

-	color: #800000; 

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 10.000000pt;

-}

-

-P.Code#dtdAttlist {

-	color: #800000; 

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 20.000000pt;

-}

-

-P.Code#tag {

-	color: #000080; 

-	display:inline;

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 0.000000pt;

-}

-

-P.Code#cstring {

-	color: #008000; 

-	display:inline;

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 0.000000pt;	

-}

-

-.ConfigMarkup#elementDesc {

-	color: black;

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 10.000000pt;

-}

-

-.ConfigMarkup#attlistDesc {

-	color: black;

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 32.000000pt;

-}

-


diff --git a/bundles/org.eclipse.pde.doc.user/tips/images/package-prefix.png b/bundles/org.eclipse.pde.doc.user/tips/images/package-prefix.png
deleted file mode 100644
index e6e9949..0000000
--- a/bundles/org.eclipse.pde.doc.user/tips/images/package-prefix.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/tips/pde_tips.htm b/bundles/org.eclipse.pde.doc.user/tips/pde_tips.htm
deleted file mode 100644
index 85ea0ed..0000000
--- a/bundles/org.eclipse.pde.doc.user/tips/pde_tips.htm
+++ /dev/null

@@ -1,134 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Language" content="en-us">
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>PDE Tips and Tricks</title>
-</head>
-
-<body>
-
-<h2>Tips and Tricks</h2>
-
-<p>&nbsp;</p>
-<table border="1" cellpadding="10" cellspacing="0" width="600" style="border-collapse: collapse" bordercolor="#111111" height="1033">
-  <tr>
-    <td valign="top" align="left" width="20%" height="345"><b>Feature-based 
-    self-hosting</b></td>
-    <td valign="top" align="left" width="80%" height="345">The current method of self-hosting in Eclipse
-      is plug-in-based. PDE launches a second run-time workbench instance by
-      passing an array of plug-ins that it should load. A regular Eclipse
-      product is feature-based: during startup, it checks all the features that
-      should be active, computes plug-ins that belong to those features, and
-      passes the result for loading.
-      <p>This difference in behavior makes it complicated to self-host in
-      scenarios where a full startup that involves features is required. PDE now
-      supports this scenario if care is taken with the setup:</p>
-      <ol>
-        <li>The workspace needs to be &lt;work-area&gt;/plugins.</li>
-        <li>Features must be imported into the workspace using the new 'Feature
-          Import' wizard (they will be created in &lt;work-area&gt;/features).</li>
-        <li>All plug-ins must be in the workspace (either in source or imported
-          as binary projects WITHOUT linking).</li>
-        <li>When launching, Run-time Workbench launcher must be configured to
-          use features (in Plug-ins and Fragments tab).</li>
-      </ol>
-      <p>If all these conditions are met, the runtime Eclipse instance will be
-      launched in a way that is the closest possible approximation of a normal
-      Eclipse startup. This facilitates testing About dialogs and other aspects
-      that may depend on the set of installed features.</p></td>
-  </tr>
-  <tr>
-    <td valign="top" align="left" width="20%"><b>To clean or not to clean</b></td>
-    <td valign="top" align="left" width="80%">When you create a new runtime 
-    workbench launch configuration, PDE presets the Program Arguments on the 
-    launch configuration to include a -clean argument.&nbsp;
-    <p>This -clean argument clears all runtime-cached data in your runtime 
-    workbench from one invocation to the next to ensure that all the changes 
-    made in your host workbench, e.g. new Java packages were added to a plug-in 
-    project, etc., are picked up when you launch a runtime workbench.</p>
-    <p>This clearing of the cache may hinder performance if your target platform 
-    contains a large number of plug-ins.&nbsp; </p>
-    <p>Therefore, if you're in a situation where your target platform has a 
-    large number of plug-ins and you're at a stage where you are not actively 
-    adding/removing packages from your plug-in projects, you could remove the 
-    -clean argument from the launch configuration to improve startup time.</p></td>
-  </tr>
-  <tr>
-    <td valign="top" align="left" width="20%"><b>Importing with linking</b></td>
-    <td valign="top" align="left" width="80%">Importing external plug-ins and 
-    fragments can be time consuming and may result in large workspaces, 
-    depending on the content of the plug-ins being imported.&nbsp; Therefore, 
-    the 'Import External Plug-ins and Fragments' wizard gives you the option to 
-    import with linking.&nbsp; This means that the import operation will not 
-    copy the resources being imported into your workspace.&nbsp; It will simply 
-    create links to the files being imported.&nbsp; You will be able to browse 
-    these linked resources, as if they had been copied into your workspace.&nbsp; 
-    However, they are physically not there on your file system, so you will not 
-    be able to modify them.&nbsp; Beware of operations that depend on files 
-    being physically in your workspace, as they will not work on linked 
-    resources.</td>
-  </tr>
-  <tr>
-    <td valign="top" align="left" width="20%" height="112"><b>Templates</b></td>
-    <td valign="top" align="left" width="80%" height="112">For a quick start, PDE provides 
-    several template plug-ins that will generate a plug-in with one or more 
-    fully-working extensions.&nbsp; In addition, if at any point, you would like 
-    to add a new extension from the template list (without having to generate a 
-    plug-in), you could access these extension templates directly from the 
-    manifest editor.&nbsp; From the 'Extensions' page of the editor, click 
-    'Add...'.&nbsp; In the wizard that comes up, select Extension Templates in 
-    the left pane and choose the template of choice in the right pane.</td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left" height="280"><b>Plug-in dependency extent</b></td>
-    <td width="80%" valign="top" align="left" height="280">If you have ever looked at the 
-    list of plug-ins that your plug-in depends on and wondered why your plug-in 
-    needs a particular plug-in X, now you can easily find out why.&nbsp; 
-    <p>The <b>Compute Dependency Extent </b>operation
-      found on the context menu in several contexts (including manifest file
-      Dependencies page and Dependencies view) performs a combined Java and
-      plug-in search to find all Java types and extension points provided by 
-    plug-in X which are referenced
-      by your plug-in. The results will be displayed in the Search view.&nbsp; When a type is selected in the Search results view, the <b>References
-      in <i>MyPlugIn</i></b> action in the context menu searches for the places
-      in the plug-in where the selected type is referenced.&nbsp;</p>
-    <p>If the 
-    search returns 0 results, you should definitely remove plug-in X from your 
-    list of dependencies, as it is not being used at all, and it would just slow 
-    class loading.</p>
-    <p>The <b>Compute Dependency Extent</b> is also useful to check if you are 
-    using internal (non-API) classes from plug-in X, which might not be 
-    desirable.</p></td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left" height="112"><b>Finding unused dependencies</b></td>
-    <td width="80%" valign="top" align="left" height="112">Minimizing a plug-in's number of 
-    dependencies is certain to improve performance.&nbsp; As your plug-in 
-    evolves, its list of dependencies might become stale, as it might be still 
-    containing references to plug-ins that it no longer needs.&nbsp; A quick way 
-    to check that all dependencies listed by your plug-in are actually used by 
-    the plug-in is to run the 'Find Unused Dependencies' utility, which is 
-    available through the context menu of the 'Dependencies' page of PDE's 
-    manifest editor.</td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left" height="80"><b>Extending the Java 
-    search scope</b></td>
-    <td width="80%" valign="top" align="left" height="80">Java Search is limited to projects 
-    in your workspace and external jars that these projects reference.&nbsp; If 
-    you would like to add more libraries from external plug-ins into the search: 
-    open the Plug-ins View, select a plug-in and choose <b>Add to Java Search</b> 
-    from the context menu. This is handy for remaining
-      aware of other plug-ins that depend on ones you're working on.</td>
-  </tr>
-  </table>
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/toc.xml b/bundles/org.eclipse.pde.doc.user/toc.xml
deleted file mode 100644
index 73b4ee5..0000000
--- a/bundles/org.eclipse.pde.doc.user/toc.xml
+++ /dev/null

@@ -1,74 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>

-<?NLS TYPE="org.eclipse.help.toc"?>

-<!-- ============================================================================= -->

-<!-- Define topics for the main guide                                              -->

-<!-- ============================================================================= -->

-<toc label="Plug-in Development Environment Guide">

-	<topic label="Getting Started">

-		<topic label="Introduction to PDE" href="guide/pde.htm"/>

-		<topic label="Preparing the workbench" href="guide/pde_setup.htm"/>

-		<topic label="Concepts" href="guide/pde_configuring.htm"/>

-		<topic label="Basic Plug-in Tutorial">

-			<topic label="Creating a plug-in project" href="guide/pde_creating.htm"/>

-			<topic label="Plug-in manifest editor" href="guide/pde_manifest.htm">

-				<topic label="Overview page" href="guide/pde_manifest_overview.htm" />

-				<topic label="Dependencies page" href="guide/pde_manifest_dependencies.htm"/>

-				<topic label="Runtime page" href="guide/pde_manifest_runtime.htm" />

-				<topic label="Extensions page" href="guide/pde_manifest_extensions.htm" />

-				<topic label="Extension points page" href="guide/pde_manifest_extensionpoints.htm" />

-				<topic label="Build configuration page" href="guide/pde_build_editor.htm" />

-				<topic label="Source pages" href="guide/pde_manifest_source.htm" />

-			</topic>

-			<topic label="Running a plug-in" href="guide/pde_running.htm">

-				<topic label="Choosing plug-ins to run" href="guide/pde_running_plugins.htm"/>

-				<topic label="Running with tracing" href="guide/pde_running_tracing.htm"/>

-			</topic>

-			<topic label="Exporting a plug-in" href="guide/pde_deploy.htm"/>

-		</topic>

-		<topic label="Fragments" href="guide/pde_fragment.htm">

-			<topic label="Fragment example" href="guide/pde_fragment_example.htm"/>

-		</topic>

-		<topic label="Features" href="guide/pde_features.htm">

-			<topic label="Setting up a feature project" href="guide/pde_feature_setup.htm"/>

-			<topic label="Feature manifest editor" href="guide/pde_feature_manifest.htm"/>

-			<topic label="Synchronizing versions" href="guide/pde_feature_synchronizing.htm"/>

-			<topic label="Exporting a feature" href="guide/pde_feature_generating.htm"/>

-			<topic label="Advanced topics in building features">

-				<topic label="Build configuration" href="guide/pde_feature_generating_build.htm"/>

-				<topic label="Generating Ant scripts from PDE" href="guide/pde_feature_generating_ant.htm"/>

-				<topic label="Generating Ant scripts from scripts" href="guide/pde_feature_generating_antcommandline.htm"/>

-			</topic>

-		</topic>

-		<topic label="Update Sites" href="guide/pde_sites.htm">

-		   <topic label="Setting up an update site project" href="guide/pde_site_setup.htm"/>

-		   <topic label="Building plug-ins and features using update site editor" href="guide/pde_site_building.htm"/>

-		   <topic label="Previewing update sites" href="guide/pde_site_previewing.htm"/>

-		</topic>   

-		<topic label="Eclipse Products">

-			<topic label="RCP template" href="guide/rcp_project.htm"/>

-			<topic label="Product Configuration" href="guide/product_configuration.htm"/>

-			<topic label="Product Editor" href="guide/product_editor.htm">

-				<topic label="Feature-Based Configuration" href="guide/feature_based_product.htm"/>

-			</topic>

-			<topic label="Exporting a Product" href="guide/product_export.htm"/>

-		</topic>

-	</topic>

-	<topic label="Tasks">

-		<topic label="Creating an extension point schema" href="guide/pde_schema.htm">

-			<topic label="Extension point schema editor" href="guide/pde_schema_editor.htm"/>

-			<topic label="Using extension point schema" href="guide/pde_schema_using.htm"/>

-		</topic>

-		<topic label="Converting existing projects" href="guide/pde_convert.htm"/>

-	</topic>

-

-	<topic label="Reference">

-		<link toc="topics_Reference.xml" />

-		<topic label="Access Restrictions" href="guide/restrictions.htm"/>

-		<topic label="Plug-ins as JARs" href="guide/plugins_as_jars.htm"/>

-		<topic label="Dynamic classpaths FAQ" href="guide/dynamic-classpaths.htm"/>	

-	</topic>

-	

-	<topic label="Tips and tricks" href="tips/pde_tips.htm"/>

-	<topic label="What's new" href="whatsNew/pde_whatsnew.htm"/>

-	<topic label="Legal" href="notices.html"/>

-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/topics_Reference.xml b/bundles/org.eclipse.pde.doc.user/topics_Reference.xml
deleted file mode 100644
index 89f6a60..0000000
--- a/bundles/org.eclipse.pde.doc.user/topics_Reference.xml
+++ /dev/null

@@ -1,13 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define topics for the references                                              -->
-<!-- ============================================================================= -->
-<toc label="Reference">
-	<topic label="API Reference" href="reference/api/overview-summary.html">
-	</topic>
-	<topic label="Extension Points Reference" href="reference/extension-points/index.html">
-	</topic>
-	<topic label="Other Reference Information" href="reference/misc/index.html">
-	</topic>
-</toc>

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/book.css b/bundles/org.eclipse.pde.doc.user/whatsNew/images/book.css
deleted file mode 100644
index a4eedda..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/book.css
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/bundlizer.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/bundlizer.png
deleted file mode 100644
index bfe0fd6..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/bundlizer.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/compilers.PNG b/bundles/org.eclipse.pde.doc.user/whatsNew/images/compilers.PNG
deleted file mode 100644
index 678ab08..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/compilers.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/cpy.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/cpy.png
deleted file mode 100644
index a0f8775..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/cpy.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/cross.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/cross.png
deleted file mode 100644
index 678ad66..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/cross.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/export.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/export.png
deleted file mode 100644
index d35f190..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/export.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/overview.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/overview.png
deleted file mode 100644
index cdb991e..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/overview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/plugins.PNG b/bundles/org.eclipse.pde.doc.user/whatsNew/images/plugins.PNG
deleted file mode 100644
index bcbc4d5..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/plugins.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/pluginwizard.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/pluginwizard.png
deleted file mode 100644
index 0bd1a55..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/pluginwizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/product-editor.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/product-editor.png
deleted file mode 100644
index 03c1f43..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/product-editor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/project_pref.PNG b/bundles/org.eclipse.pde.doc.user/whatsNew/images/project_pref.PNG
deleted file mode 100644
index be67a82..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/project_pref.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/restricted.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/restricted.png
deleted file mode 100644
index 9e1808b..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/restricted.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/rich_client.PNG b/bundles/org.eclipse.pde.doc.user/whatsNew/images/rich_client.PNG
deleted file mode 100644
index 5311427..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/rich_client.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/runtime.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/runtime.png
deleted file mode 100644
index 241cb66..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/runtime.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/signed.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/signed.png
deleted file mode 100644
index d7beea3..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/signed.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/templates.PNG b/bundles/org.eclipse.pde.doc.user/whatsNew/images/templates.PNG
deleted file mode 100644
index 7e969db..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/templates.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/validate.PNG b/bundles/org.eclipse.pde.doc.user/whatsNew/images/validate.PNG
deleted file mode 100644
index 314da17..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/validate.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/validation.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/validation.png
deleted file mode 100644
index a82a231..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/validation.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/pde_whatsnew.htm b/bundles/org.eclipse.pde.doc.user/whatsNew/pde_whatsnew.htm
deleted file mode 100644
index e9a1a79..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/pde_whatsnew.htm
+++ /dev/null

@@ -1,241 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>PDE What's New for 3.1</title>
-</head>
-
-<body>
-
-<h2>What's New in 3.1</h2>
-<p>This document contains descriptions of some of the more interesting or significant 
-  changes made to PDE for the 3.1 release of Eclipse since 3.0. </p>
-
-<h2><a name="PDE">PDE</a></h2>
-<table summary="PDE New in 3.1" cellpadding="10" cellspacing="0" width="600">
-  <tr> 
-    <td colspan="2" align="left" valign="top"><hr></td>
-  </tr>
-  <tr> 
-    <td height="855" align="left" valign="top"> <p align="right"><b>Bundle manifests 
-        for plug-ins</b></p></td>
-    <td valign="top">In Eclipse 3.1, it is strongly recommended that plug-ins 
-      contain an OSGi bundle manifest.mf. In addition to faster startup and classloading, 
-      this format will allow you to take advantage of many of the new runtime 
-      capabilities such as fine control over what packages you want to expose 
-      to clients. 
-      <p>The option to create a manifest.mf in the New Plug-in Project creation 
-        wizard is now on by default.</p>
-      <p><img src="images/pluginwizard.png" alt="New Plug-in Wizard" border="0"></p>
-      <p>You can create a bundle manifest.mf for an existing plug-in on the Overview 
-        page of the plug-in manifest editor.</p>
-      <p><img src="images/overview.png" alt="Plug-in Content" border="0"></p>
-	</td></tr>
-  <tr> 
-    <td colspan="2" align="left" valign="top"><hr></td>
-  </tr>
-  <tr> 
-    <td valign="top" align="left"> <p align="right"><b>PDE enforces code accessibility</b></p></td>
-    <td valign="top">The plug-in's manifest.mf file allows you to control on a 
-      per-package basis the visibility of your plug-in's code to downstream plug-ins. 
-      <p>PDE manages each plug-in's Java classpath and checks these visibility 
-        rules at compile time. This means no one will never be caught by surprise 
-        by classloading errors at runtime, and will always be aware when they 
-        are referencing internal (discouraged) types.</p>
-      <p><img src="images/restricted.png" alt="discouraged access" width="466" height="115" border="0"></p>
-      <p>For full details, refer to the <a href="../guide/restrictions.htm">Access 
-        Restrictions</a> document.</p></td>
-  </tr>
-  <colgroup>
-  <col width="20%" valign="top" align="right">
-  <col width="80%" valign="top" align="left">
-  </colgroup>
-  <tbody>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td valign="top"> <div align="right"><strong>Creating a rich client application</strong></div></td>
-      <td valign="top"> <div align="left"> 
-          <p>The New Plug-in Project wizard gives you the option to create a rich 
-            client application.</p>
-          <p><img src="images/rich_client.PNG" alt="Rich Client"></p>
-        </div></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td valign="top"><div align="right"><strong>RCP templates</strong></div></td>
-      <td valign="top"><p>The New Plug-in Project wizard provides ready-to-run 
-          RCP templates. The templates range from a minimal Hello RCP template 
-          to a rich, fully-branded RCP mail template.</p>
-        <p><img src="images/templates.PNG" alt="RCP templates"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td valign="top" align="left"> <p align="right"><b>Build an Eclipse product 
-          with a single click</b></p></td>
-      <td valign="top">You can now create and manage an Eclipse product in a *.product 
-        file, which can be created via <b>File &gt; New &gt; Other... &gt; Product 
-        Configuration</b>. 
-        <p>The product configuration editor manages all aspects of a product from 
-          basic definition to branding. You can create plug-in-based and feature-based 
-          products. The overview page provides hot links to test and export the 
-          product.</p>
-        <p><img src="images/product-editor.png" alt="product editor" border="0"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2" align="left" valign="top"><hr></td>
-    </tr>
-    <tr> 
-      <td valign="top" align="left"> <p align="right"><b>Eclipse product export 
-          wizard</b></p></td>
-      <td valign="top"><p>You can export an Eclipse product as an archive or a 
-          directory structure in the Eclipse Product Export wizard.</p>
-        <p>The wizard is invoked via <b>File &gt; Export &gt; Eclipse Product 
-          </b>or from the <b>Overview</b> page of the Product Configuration editor. 
-        </p>
-        <p><img src="images/export.png" alt="Export Wizard" border="0"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td valign="top" align="left"> <p align="right"><b>Cross-platform product 
-          export</b></p></td>
-      <td valign="top">If you have the RCP delta pack installed, you can now build 
-        and export your product for multiple platforms at the same time via the 
-        Eclipse Product export wizard (<b>File &gt; Export &gt; Eclipse Product</b>). 
-        <p> <img src="images/cross.png" alt="Cross Platform" border="0"></p></td></tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td valign="top" align="left"> <p align="right"><b>Create a plug-in from 
-          existing JAR</b></p></td>
-      <td valign="top">PDE now provides a wizard that creates a plug-in from existing 
-        JAR archives. This wizard is ideal if you would like to package third-party 
-        non-Eclipse JARs as an Eclipse plug-in. 
-        <p>The wizard can be invoked via <b>File &gt; New &gt; Project &gt; Plug-in 
-          from existing JAR archives.</b></p>
-        <p><img src="images/bundlizer.png" alt="Bundlizer" border="0"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td valign="top" align="left"> <p align="right"><b>Manifest editor supports 
-          more OSGi bundle manifest headers</b></p></td>
-      <td valign="top">The PDE plug-in editor now exposes many interesting features 
-        of the runtime that are available only if your plug-in has a manifest.mf 
-        file. The Runtime page of the editor, for example, is the place where 
-        you can control access to your plug-in's code on a fine-grained level. 
-        <p><img src="images/runtime.png" alt="Bundle Editor" border="0"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td valign="top" align="left"> <p align="right"><b>Manifest.mf validation</b></p></td>
-      <td valign="top">PDE now flags syntactic and semantic errors in the plug-in's 
-        manifest.mf file. 
-        <p><img src="images/validation.png" alt="manifest.mf validation" border="0"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td valign="top" align="left"> <p align="right"><b>Improved plugin.xml validation</b></p></td>
-      <td valign="top"><p>Attributes and elements defined in extension point schemas 
-          can now be marked as translatable. Also, obsolete attributes and elements 
-          can be marked as deprecated, in the same spirit as @deprecated tag in 
-          obsolete Java APIs.</p>
-        <p>PDE uses this metadata to flag the usage of deprecated and non-externalized 
-          attributes and elements in the plug-in's manifest files.</p>
-        <p><img src="images/compilers.PNG" alt="Manifest Compiler"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td valign="top" align="left"> <p align="right"><b>Sharing plug-in manifest 
-          compiler settings</b></p></td>
-      <td valign="top">You can now set the PDE plug-in manifest compiler settings 
-        on a per-project basis and share these settings among team members. 
-        <p><img src="images/project_pref.PNG" alt="Project preferences"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td valign="top" align="left"> <p align="right"><b>Improved plug-in dependencies 
-          view</b></p></td>
-      <td valign="top"><p>The PDE Plug-in Dependencies view now shows both tabular 
-          and tree visualizations of dependencies, as well as caller/callee relationships 
-          and cyclic dependencies. This view can be opened from the context menu 
-          of plug-in project via <b>PDE Tools &gt; Open Dependencies</b>.</p>
-        <p><img src="images/plugins.PNG" alt="Plug-in Dependencies"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td valign="top" align="left"><div align="right"><strong>Validate plug-in 
-          set before launching</strong></div></td>
-      <td valign="top"><p>Prior to launching your Eclipse application, you can 
-          now validate the selected subset of plug-ins to find lurking launch 
-          startup problems such as unsatisfied plug-in dependencies, missing applications, 
-          etc.</p>
-        <p><img src="images/validate.PNG" alt="Validate Plug-ins"> </p></td>
-    </tr>
-    <tr> 
-      <td colspan="2" align="left" valign="top"><hr></td>
-    </tr>
-    <tr> 
-      <td width="19%" valign="top" align="left"> <p align="right"><b>No need to 
-          -clean</b></p></td>
-      <td width="81%" valign="top">When self-hosting with PDE, you no longer need 
-        to launch a runtime Eclipse application with the <code>-clean</code> program 
-        argument. Leaving this argument off significantly improves startup time.</td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="19%" valign="top" align="left"> <p align="right"><b>Improved 
-          feature and update site support</b></p></td>
-      <td width="81%" valign="top">The PDE feature and update site manifest editors 
-        have been redesigned to provide a simpler and better workflow.&nbsp; Improvements 
-        include the ability to build and package features without having to import 
-        them into your workspace.</td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="19%" valign="top" align="left"> <p align="right"><b>JNLP manifests 
-          and JAR signing</b></p></td>
-      <td width="81%" valign="top">The feature export wizard now provides you 
-        with the option to create JNLP manifests and digitally sign your plug-in 
-        and feature archives for Java Web Start deployment. 
-        <p><img src="images/signed.png" alt="JNLP and signed" border="0"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <!-- ****************** END OF N&N TABLE ****************** -->
-  </tbody>
-</table>
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/workbench.png b/bundles/org.eclipse.pde.doc.user/workbench.png
deleted file mode 100644
index c3f7d3f..0000000
--- a/bundles/org.eclipse.pde.doc.user/workbench.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/.classpath b/bundles/org.eclipse.platform.doc.isv/.classpath
deleted file mode 100644
index 065ac06..0000000
--- a/bundles/org.eclipse.platform.doc.isv/.classpath
+++ /dev/null

@@ -1,7 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<classpath>
-	<classpathentry kind="src" path="src"/>
-	<classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
-	<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
-	<classpathentry kind="output" path="bin"/>
-</classpath>

diff --git a/bundles/org.eclipse.platform.doc.isv/.cvsignore b/bundles/org.eclipse.platform.doc.isv/.cvsignore
deleted file mode 100644
index 4a2cb51..0000000
--- a/bundles/org.eclipse.platform.doc.isv/.cvsignore
+++ /dev/null

@@ -1,2 +0,0 @@
-bin
-platformOptions.tmp.txt

diff --git a/bundles/org.eclipse.platform.doc.isv/.project b/bundles/org.eclipse.platform.doc.isv/.project
deleted file mode 100644
index 423fcba..0000000
--- a/bundles/org.eclipse.platform.doc.isv/.project
+++ /dev/null

@@ -1,28 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
-	<name>org.eclipse.platform.doc.isv</name>
-	<comment></comment>
-	<projects>
-	</projects>
-	<buildSpec>
-		<buildCommand>
-			<name>org.eclipse.jdt.core.javabuilder</name>
-			<arguments>
-			</arguments>
-		</buildCommand>
-		<buildCommand>
-			<name>org.eclipse.pde.ManifestBuilder</name>
-			<arguments>
-			</arguments>
-		</buildCommand>
-		<buildCommand>
-			<name>org.eclipse.pde.SchemaBuilder</name>
-			<arguments>
-			</arguments>
-		</buildCommand>
-	</buildSpec>
-	<natures>
-		<nature>org.eclipse.jdt.core.javanature</nature>
-		<nature>org.eclipse.pde.PluginNature</nature>
-	</natures>
-</projectDescription>

diff --git a/bundles/org.eclipse.platform.doc.isv/.settings/org.eclipse.pde.prefs b/bundles/org.eclipse.platform.doc.isv/.settings/org.eclipse.pde.prefs
deleted file mode 100644
index c0d0c86..0000000
--- a/bundles/org.eclipse.platform.doc.isv/.settings/org.eclipse.pde.prefs
+++ /dev/null

@@ -1,12 +0,0 @@
-#Tue May 03 09:52:47 EDT 2005
-compilers.p.deprecated=1
-compilers.p.no-required-att=0
-compilers.p.not-externalized-att=1
-compilers.p.unknown-attribute=0
-compilers.p.unknown-class=0
-compilers.p.unknown-element=1
-compilers.p.unknown-resource=1
-compilers.p.unresolved-ex-points=0
-compilers.p.unresolved-import=0
-compilers.use-project=true
-eclipse.preferences.version=1

diff --git a/bundles/org.eclipse.platform.doc.isv/META-INF/MANIFEST.MF b/bundles/org.eclipse.platform.doc.isv/META-INF/MANIFEST.MF
deleted file mode 100644
index 2f7ae39..0000000
--- a/bundles/org.eclipse.platform.doc.isv/META-INF/MANIFEST.MF
+++ /dev/null

@@ -1,12 +0,0 @@
-Manifest-Version: 1.0
-Bundle-ManifestVersion: 2
-Bundle-Name: %pluginName
-Bundle-SymbolicName: org.eclipse.platform.doc.isv; singleton:=true
-Bundle-Version: 3.2.0.qualifier
-Bundle-ClassPath: activeHelpSample.jar
-Bundle-Vendor: %providerName
-Bundle-Localization: plugin
-Export-Package: org.eclipse.platform.doc.isv.activeHelp
-Require-Bundle: org.eclipse.help;bundle-version="[3.2.0,4.0.0)",
- org.eclipse.ui;bundle-version="[3.2.0,4.0.0)"
-Eclipse-LazyStart: true

diff --git a/bundles/org.eclipse.platform.doc.isv/aaa-how-to-add-things.txt b/bundles/org.eclipse.platform.doc.isv/aaa-how-to-add-things.txt
deleted file mode 100644
index 54d2db7..0000000
--- a/bundles/org.eclipse.platform.doc.isv/aaa-how-to-add-things.txt
+++ /dev/null

@@ -1,41 +0,0 @@
-Last revised January 30, 2006
-(This file is for information only; it is not included in the release.)
-
-ADDING NEW PLUGINS:
---------------------------
-
-To add new plug-ins you need to make changes in several places in
-this doc plug-in:
-
-1) platformOptions.txt
-- the plug-in's source folder(s) must be included on the -sourcepath
-- code of required plug-ins must be added on the -classpath (the JAR(s)for non-JARed plug-ins and <plugin>/@dot for JARed plug-ins
-- the API package names must be included in the (alphabetical) package list at the end of the file
-
-2) buildDoc.xml
- - If a plug-in contributes extension points, it should be added to the list of
-   plug-ins in the <convertSchemaToHTML> task in the buildDoc.xml of the
-   corresponding documentation plug-in.
-
-3) plugin.xml
- -If your plugin has javadoc API, add a line to plugin.xml under the 
- org.eclipse.pde.core.javadoc extension to associate your plugin's javadoc with
- the reference section for this doc plugin.
- 
-ADDING NEW API PACKAGES:
----------------------------------
-
-1) topics_Reference.xml
-- add a line for each API package
-
-2) overview-platform.html
-- add the API packages to the corresponding section
-
-ADDING NEW EXTENSION POINTS:
---------------------------------------
-
-1) reference/extension-points/index.html
-- add a line for each extension point
-
-2) topics_Reference.xml
-- add a line for each extension point

diff --git a/bundles/org.eclipse.platform.doc.isv/about.html b/bundles/org.eclipse.platform.doc.isv/about.html
deleted file mode 100644
index 6a04c10..0000000
--- a/bundles/org.eclipse.platform.doc.isv/about.html
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
-<title>About</title>
-
-</head>
-<body lang="EN-US">
-<h2>About This Content</h2>
- 
-<p>February 24, 2005</p>	
-<h3>License</h3>
-
-<p>The Eclipse Foundation makes available all content in this plug-in (&quot;Content&quot;).  Unless otherwise indicated below, the Content is provided to you under the terms and conditions of the
-Eclipse Public License Version 1.0 (&quot;EPL&quot;).  A copy of the EPL is available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
-For purposes of the EPL, &quot;Program&quot; will mean the Content.</p>
-
-<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is being redistributed by another party (&quot;Redistributor&quot;) and different terms and conditions may
-apply to your use of any object code in the Content.  Check the Redistributor's license that was provided with the Content.  If no such license exists, contact the Redistributor.  Unless otherwise
-indicated below, the terms and conditions of the EPL still apply to any source code in the Content.</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/book.css b/bundles/org.eclipse.platform.doc.isv/book.css
deleted file mode 100644
index a4eedda..0000000
--- a/bundles/org.eclipse.platform.doc.isv/book.css
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/build.properties b/bundles/org.eclipse.platform.doc.isv/build.properties
deleted file mode 100644
index a037299..0000000
--- a/bundles/org.eclipse.platform.doc.isv/build.properties
+++ /dev/null

@@ -1,35 +0,0 @@
-###############################################################################
-# Copyright (c) 2000, 2005 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-jars.compile.order = activeHelpSample.jar
-customBuildCallbacks=customBuildCallbacks.xml
-source.activeHelpSample.jar = src/
-output.activeHelpSample.jar = bin/
-bin.includes = activeHelpSample.jar,\
-               META-INF/,\
-               about.html,\
-               book.css,\
-               guide/,\
-               notices.html,\
-               plugin.properties,\
-               plugin.xml,\
-               porting/,\
-               questions/,\
-               reference/,\
-               samples/,\
-               schema.css,\
-               toc.xml,\
-               topics_Guide.xml,\
-               topics_Porting.xml,\
-               topics_Questions.xml,\
-               topics_Reference.xml,\
-               topics_Samples.xml,\
-               workbench.png,\
-               index/

diff --git a/bundles/org.eclipse.platform.doc.isv/buildDoc.xml b/bundles/org.eclipse.platform.doc.isv/buildDoc.xml
deleted file mode 100644
index ce33d6c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/buildDoc.xml
+++ /dev/null

@@ -1,124 +0,0 @@
-<project name="Platform Doc Isv Build" default="all"  basedir="." >
-
-	<target name="init">
-		<available file="${basedir}/index" property="index.present"/>
-	</target>
-
-	<target name="all" depends="init" unless="index.present">
-		<antcall target="convertSchemaToHtml" />
-		<antcall target="examplesDocCopy" />
-		<antcall target="generateJavadoc" />
-		<antcall target="build.index" />
-		<!--antcall target="createDocZip" /-->
-	</target>
-
-
-	<target name="build.index" description="Builds search index for the plug-in: org.eclipse.jdt.doc.isv" if="eclipse.running">
-		<help.buildHelpIndex manifest="${basedir}/plugin.xml" destination="${basedir}"/>
-	</target>
-
-	<target name="convertSchemaToHtml" if="eclipse.running">
-		<property name="dest" value="reference/extension-points" />
-
-		<record name="${basedir}/platformconvert.txt" action="start"/>
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ant.core/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ant.ui/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.compare/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.core.expressions/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.core.filebuffers/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.core.filesystem/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.core.resources/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.core.runtime/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.core.variables/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.debug.core/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.debug.ui/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.help/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.help.base/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ltk.core.refactoring/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ltk.ui.refactoring/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.search/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.team.core/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.team.ui/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ui/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ui.cheatsheets/plugin.xml" destination="${dest}" />
-		<!--copy extra files linked to by generated extension point doc-->
-		<copy file="../org.eclipse.ui.cheatsheets/schema/cheatSheetContentFileSpec.html" todir="${dest}"/>
-		<copy file="../org.eclipse.ui.cheatsheets/schema/contentFile.xsd" todir="${dest}"/>
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ui.console/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ui.editors/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ui.externaltools/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ui.ide/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ui.intro/plugin.xml" destination="${dest}" />
-		<!--copy extra HTML file linked to by generated extension point doc-->
-		<copy file="../org.eclipse.ui.intro/schema/introContentFileSpec.html" todir="${dest}"/>
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ui.navigator/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ui.views.properties.tabbed/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ui.workbench.texteditor/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.update.core/plugin.xml" destination="${dest}" />
-		<record name="${basedir}/platformconvert.txt" action="stop"/>
-	</target>
-
-	<target name="examplesDocCopy" >
-		<copy todir="samples">
-			<fileset dir="..">
-				<include name="org.eclipse.compare.examples/doc-html/"/>
-				<include name="org.eclipse.compare.examples.xml/doc-html/"/>
-				<include name="org.eclipse.help.examples.ex1/doc-html/"/>
-				<include name="org.eclipse.swt.examples/doc-html/"/>
-				<include name="org.eclipse.swt.examples.browser/doc-html/"/>
-				<include name="org.eclipse.swt.examples.controls/doc-html/"/>
-				<include name="org.eclipse.swt.examples.launcher/doc-html/"/>
-				<include name="org.eclipse.swt.examples.layouts/doc-html/"/>
-				<include name="org.eclipse.swt.examples.ole.win32/doc-html/"/>
-				<include name="org.eclipse.swt.examples.paint/doc-html/"/>
-				<include name="org.eclipse.ui.examples.fieldassist/doc-html/"/>
-				<include name="org.eclipse.ui.examples.javaeditor/doc-html/"/>
-				<include name="org.eclipse.ui.examples.multipageeditor/doc-html/"/>
-				<include name="org.eclipse.ui.examples.propertysheet/doc-html/"/>
-				<include name="org.eclipse.ui.examples.readmetool/doc-html/"/>
-				<include name="org.eclipse.ui.examples.undo/doc-html/"/>
-				<include name="org.eclipse.team.examples.filesystem/doc-html/"/>
-			</fileset>
-		</copy>
-	</target>
-
-	<target name="getJavadocPath">
-		<available file="${java.home}/../bin/javadoc.exe" property="javadoc" value="${java.home}/../bin/javadoc.exe"/>
-		<available file="${java.home}/../bin/javadoc" property="javadoc" value="${java.home}/../bin/javadoc" />
-	</target>
-
-	<target name="generateJavadoc" depends="getJavadocPath" if="javadoc">
-
-		<property name="optionsFile" value="platformOptions.tmp.txt" />
-		<copy file="platformOptions.txt" tofile="${optionsFile}" overwrite="true" />
-		
-		<condition property="argsListDelimiter" value=":">
-			<os family="unix" />
-		</condition>
-		<condition property="argsListDelimiter" value=";">
-			<os family="windows" />
-		</condition>
-		
-		<replaceregexp file="${basedir}/${optionsFile}" flags="g" match="(\r\n?|\n);" replace="${argsListDelimiter}" />
-		<replace file="${basedir}/${optionsFile}" token="@rt@" value="${bootclasspath}" />
-
-		<!--scrub isv plugin directories of any preexisting api doc content-->
-		<delete dir="reference/api"/>
-		<mkdir dir="reference/api"/>
-
-		<exec dir="." executable="${javadoc}" output="doc.bin.log">
-			<arg line="@${basedir}/${optionsFile} -J-Xmx1000M" />
-		</exec>
-		
-		<!--workaround for bug 101048-->
-		<replace dir="reference/api" token="=&quot;/../misc/api-usage-rules.html" value="=&quot;./../misc/api-usage-rules.html">
-			<include name="*htm*" />
-		</replace>
-
-	</target>
-
-	<target name="createDocZip">
-		<zip zipfile="${basedir}/doc.zip" basedir="${basedir}" includes="book.css, notices.html, about.html, no_help_exists.htm, concepts/**, gettingStarted/**, images/**, reference/**, porting/**, tasks/**,samples/**,guide/**,questions/**" />
-	</target>
-</project>
-

diff --git a/bundles/org.eclipse.platform.doc.isv/customBuildCallbacks.xml b/bundles/org.eclipse.platform.doc.isv/customBuildCallbacks.xml
deleted file mode 100644
index 408a8ee..0000000
--- a/bundles/org.eclipse.platform.doc.isv/customBuildCallbacks.xml
+++ /dev/null

@@ -1,141 +0,0 @@
-<!-- ===================================================================== -->
-<!-- Custom targets called from a project's generated build.xml            -->
-<!-- Set customBuildCallbacks=<path/to/this/file> in your build.properties.-->
-<!-- ===================================================================== -->
-<project name="Build specific targets and properties" default="noDefault">
-
-	<!-- ===================================================================== -->
-	<!-- Default target                                                        -->
-	<!-- ===================================================================== -->
-	<target name="noDefault">
-		<echo message="This file must be called with explicit targets" />
-	</target>
-	
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the target build.jars                              -->
-	<!-- Available parameters :                                                -->
-	<!--   build.result.folder - folder to contain the build results           -->
-	<!-- ===================================================================== -->
-	<target name="pre.build.jars">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target build.jars                               -->
-	<!-- Available parameters :                                                -->
-	<!--   build.result.folder - folder to contain the build results           -->
-	<!-- ===================================================================== -->
-	<target name="post.build.jars">
-		<ant antfile="buildDoc.xml" />
-	</target>
-	
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the target build.sources                           -->
-	<!-- Available parameters :                                                -->
-	<!--   build.result.folder - folder to contain the build results           -->
-	<!-- ===================================================================== -->
-	<target name="pre.build.sources">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target build.sources                            -->
-	<!-- Available parameters :                                                -->
-	<!--   build.result.folder - folder to contain the build results           -->
-	<!-- ===================================================================== -->
-	<target name="post.build.sources">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the compilation target <name>                      -->
-	<!-- Substitute "name" with the name of the compilation target, eg @dot    -->
-	<!-- Available parameters :                                                -->
-	<!--   source.foldern : n = 1 ... N, the source folders                    -->
-	<!--   target.folder  : where the results of the compilation go            -->
-	<!--   <name>.classpath : name = name of the compilation target. A         -->
-	<!--                      reference to the classpath structure.            -->
-	<!-- ===================================================================== -->
-	<target name="pre.activeHelpSample.jar">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after compilation but before jaring					   -->
-	<!-- Substitute "name" with the name of the compilation target, eg @dot    -->
-	<!-- Available parameters :                                                -->
-	<!--   source.foldern : n = 1 ... N, the source folders                    -->
-	<!--   target.folder  : where the results of the compilation go            -->
-	<!--   <name>.classpath : name = name of the compilation target. A         -->
-	<!--                      reference to the classpath structure.            -->
-	<!-- ===================================================================== -->
-	<target name="post.compile.activeHelpSample.jar">
-	</target>
-	
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the compilation target <name>                       -->
-	<!-- Substitute "name" with the name of the compilation target, eg @dot    -->
-	<!-- Available parameters :                                                -->
-	<!--   jar.location - the location of the compilation results              -->
-	<!--   <name>.classpath : name = name of the compilation target. A         -->
-	<!--                      reference to the classpath structure.            -->
-	<!-- ===================================================================== -->
-	<target name="post.activeHelpSample.jar">
-	</target>
-	
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target gather.bin.parts                         -->
-	<!-- Available parameters :                                                -->
-	<!--   base.dir - root of the project                                      -->
-	<!--   build.result.folder - folder containing the build results           -->
-	<!--   target.folder - destination folder                                  -->
-	<!-- ===================================================================== -->
-	<target name="post.gather.bin.parts">
-	</target>
-	
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the target gather.sources                          -->
-	<!-- Available parameters :                                                -->
-	<!--   destination.temp.folder - destination folder                        -->
-	<!-- ===================================================================== -->
-	<target name="pre.gather.sources">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target gather.sources                           -->
-	<!-- Available parameters :                                                -->
-	<!--   destination.temp.folder - destination folder                        -->
-	<!-- ===================================================================== -->
-	<target name="post.gather.sources">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the target gather.logs                             -->
-	<!-- Available parameters :                                                -->
-	<!--   destination.temp.folder - destination folder                        -->
-	<!-- ===================================================================== -->
-	<target name="pre.gather.logs">        
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target gather.logs                              -->
-	<!-- Available parameters :                                                -->
-	<!--   destination.temp.folder - destination folder                        -->
-	<!-- ===================================================================== -->
-	<target name="post.gather.logs">       
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the target clean                                   -->
-	<!-- Available parameters :                                                -->
-	<!--   destination.temp.folder - destination folder                        -->
-	<!-- ===================================================================== -->
-	<target name="pre.clean">              
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target clean                                    -->
-	<!-- Available parameters :                                                -->
-	<!--   plugin.destination - final destination of the build                 -->
-	<!--   build.result.folder - results of the compilation                    -->
-	<!--   temp.folder - temporary folder                                      -->
-	<!-- ===================================================================== -->
-	<target name="post.clean">             
-	</target>
-</project>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/adding_interfaces.htm b/bundles/org.eclipse.platform.doc.isv/guide/adding_interfaces.htm
deleted file mode 100644
index 832260a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/adding_interfaces.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Adding new interfaces</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2> Adding new interfaces</H2>
-New types of objects can be passed into a part's constructor by registering them 
-with the the <span style="font-style: italic;">org.eclipse.core.component.types</span> 
-extension point. At this point, we should introduce the term <span
- style="font-style: italic;">component</span>. A component is any sort of object 
-that is created from an extension point by injecting arguments into its constructor. 
-New-style parts are one sort of component, but there are other types of components 
-as well.<br>
-<br>
-The following example shows a sample types extension. This example specifies that 
-the INameable interface should be available from a part's site.<br>
-<br>
-<div style="margin-left: 40px;"><code>&lt;extension</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; point="org.eclipse.core.component.types"&gt;</code><br>
-  <code>&nbsp;&nbsp; &lt;component<br>
-  </code><code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; initializer="org.eclipse.ui.part.SiteInitializer"</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; interface="org.eclipse.ui.part.services.INameable"<br>
-  </code><code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; implementation="org.eclipse.ui.internal.part.services.NullNameableService"</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; singleton="true"</code><br>
-  <code>&nbsp;&nbsp; /&gt;</code><br>
-  <code>&lt;/extension&gt;</code><br>
-</div>
-<p>The <span style="font-style: italic;">initializer</span> attribute indicates 
-  where the interface will be used. For example, the string "org.eclipse.ui.part.SiteInitializer" 
-  means that the interface is used on a part's site. We could have also used "org.eclipse.ui.part.PartInitializer" 
-  if the interface was intended for parts themselves to implement. <br>
-  <br>
-  The <span style="font-style: italic;">interface</span> attribute is the name 
-  of the interface. This must exactly match the type that the component will receive 
-  in its constructor. If we create an extension that supplies Strings and a component 
-  asks for an Object, it will not use our extension even though it would have 
-  been a compatible type. <br>
-  <br>
-  The <span style="font-style: italic;">implementation</span> attribute identifies 
-  the default implementation of the interface. It either points to a component 
-  class that implements the interface or a ComponentFactory that can create them, 
-  for additional information, see the ComponentFactory section . This implementation 
-  is used to satisfy a dependency whenever a component requests this interface 
-  and it can't be found in its parent context. All interfaces must supply a default 
-  implementation. This means that a correctly written component will always work 
-  in a given scope, regardless of how many dependencies are supplied by its parent 
-  context. The implementation cannot override or extend the interface attribute 
-  by implementing additional interfaces. Other components can depend on this component 
-  through its registered interface, but cannot depend on the implementation class 
-  directly. <br>
-  <br>
-  The <span style="font-style: italic;">singleton</span> attribute indicates whether 
-  the default implementation is a singleton. If true, then a single instance will 
-  be created and shared between every other component that needs it. If false, 
-  then a new instance will be created for each container that needs it. For example, 
-  in the case of parts, singleton=:"false" would mean that one instance will be 
-  created for every part.<br>
-</p>
-<h2>&nbsp; </h2>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ant.htm b/bundles/org.eclipse.platform.doc.isv/guide/ant.htm
deleted file mode 100644
index 0e6a7ac..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ant.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Platform Ant support
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>Platform Ant support</h1>
-<p>Ant is a Java-based build tool that uses XML-based configuration files to
-describe build tasks.&nbsp; The Eclipse platform allows you to run Ant buildfiles
-from your plug-in and contribute new Ant <a href="../reference/extension-points/org_eclipse_ant_core_antTasks.html">tasks</a>, 
-<a href="../reference/extension-points/org_eclipse_ant_core_antTypes.html">types</a> and
-<a href="../reference/extension-points/org_eclipse_ant_core_antProperties.html">properties</a>
-using extension points.&nbsp; The rest of this discussion assumes that you have a basic
-understanding of Ant.</p>
-
-</BODY></HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ant_contributing_task.htm b/bundles/org.eclipse.platform.doc.isv/guide/ant_contributing_task.htm
deleted file mode 100644
index 9acc5c8..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ant_contributing_task.htm
+++ /dev/null

@@ -1,105 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Contributing tasks and types
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Contributing tasks and types</h2>
-<p>When your plug-in contributes Ant tasks and types, the tasks and types have access to all
-of the classes inside the contributing plug-in. For example, the <b>eclipse.refreshLocal</b> task 
-contributed by <b>org.eclipse.core.resources</b> plug-in is 
-a wrapper for the
-<a href="../reference/api/org/eclipse/core/resources/IResource.html#refreshLocal(int, org.eclipse.core.runtime.IProgressMonitor)">
-<b>
-IResource.refreshLocal()</b></a> method.</p>
-
-
-<p>Tasks and types contributed by plug-ins must not be placed in any of the 
-plug-in libraries. They have to be in a separate JAR. This means that the
-plug-in classes do not have access to the tasks and types provided by the 
-plug-in.&nbsp; (See 
-<a href="#jar">Why a separate JAR for tasks and types</a>?
-for more information.)</p>
-
-
-<p> The <b><a href="../reference/extension-points/org_eclipse_ant_core_antTasks.html">org.eclipse.ant.core.antTasks</a></b> extension point provides an example of how to specify
-a new task 
-in the <b>plugin.xml</b> file.</p>
-
-
-<A NAME="monitor"></A><h3>
-Progress Monitors</h3>
-<P >
-The Eclipse Ant support provides access to an <a href="../reference/api/org/eclipse/core/runtime/IProgressMonitor.html">
-<b>
-IProgressMonitor</b></a> if one is passed when invoking the AntRunner. One of the advantages of having access to a progress
-monitor is that a long-running task can check to see if the user has requested its cancellation. The progress
-monitor object is obtained from the Ant project's references.&nbsp; Note that a monitor is only made available if
-the method <a href="../reference/api/org/eclipse/ant/core/AntRunner.html#run(org.eclipse.core.runtime.IProgressMonitor)">
-<b>
-AntRunner.run(IProgressMonitor)</b></a> was called with a valid progress monitor. The following code snippet
-shows how to obtain a progress monitor from the task's project:
-</P>
-<pre>import org.apache.tools.ant.BuildException;
-import org.apache.tools.ant.Task;
-import org.eclipse.ant.core.AntCorePlugin;
-import org.eclipse.core.runtime.IProgressMonitor;
-
-public class CoolTask extends Task {
-
-public void execute() throws BuildException {
-<b>	IProgressMonitor monitor = 
-		(IProgressMonitor) getProject().getReferences().get(AntCorePlugin.ECLIPSE_PROGRESS_MONITOR);
-</b>	if (monitor == null) {
-		...
-	} else {
-		...
-	}
-}
-}
-</pre>
-
-
-<h3 >
-Important rules when contributing tasks and types</h3>
-
-
-<p>
-The following should work as a checklist for plug-in developers:</p>
-<ul>
-  <li>The JAR containing the tasks must not be a plug-in library (declared in 
-  &lt;library&gt;&lt;/library&gt;).</li>
-  <li>The task or type can reference any class available for the plug-in but 
-  plug-in classes must not access the tasks or types.</li>
-  <li>Native libraries should be loaded by the plug-in library classes and not tasks or types.</li>
-</ul>
-
-
-<A NAME="jar"></A>
-<h3>Why a separate JAR for tasks and types?</h3>
-<p>
-There are basically two requirements for running Ant in Eclipse that do not fit
-the plug-in model very well:</p>
-<ul>
-  <li>Change the Ant classpath at runtime</li>
-  <li>Change the Ant version at runtime</li>
-</ul>
-<p>
-During runtime plug-in classloaders cannot have their classpaths expanded and
-plug-ins cannot change their dependencies. At the same time having separate
-JARs for the tasks and types is a good isolation from the plug-in classloading
-mechanism. Having these extra JARs declared by a plug-in permits adding the
-contributing plug-in to the Ant classpath as well.
-</p>
-</BODY></HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ant_developing.htm b/bundles/org.eclipse.platform.doc.isv/guide/ant_developing.htm
deleted file mode 100644
index 7fb077e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ant_developing.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Developing tasks and types
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Developing Ant tasks and types within Eclipse</h2>
-<p>The following guidelines should be followed when developing and debugging Ant 
-  tasks and types within Eclipse. These requirements stem from the fact that Ant 
-  tasks and types must be loaded by the Ant classloader, rather than a plug-in 
-  classloader, when Ant is run in the same VM as Eclipse. To avoid having the 
-  Ant tasks and types loaded by a plug-in classloader, the tasks and types need 
-  to be stored in a location that is not visible to any plug-in classloader. Also 
-  see <a href="ant_contributing_task.htm">Contributing tasks and types</a>.</p>
-<ul>
-  <li> Contributed Ant tasks or types should be defined in their own source folder 
-    within a plug-in (i.e. separate from the source folders containing regular 
-    plug-in classes)</li>
-  <li>Each source folder containing the Ant tasks and types should have its own 
-    output location that does not overlap with the output location of the regular 
-    plug-in classes.</li>
-  <li>When testing/debugging the new Ant tasks or types, the project contributing
-    the Ant tasks or types must be configured to <b>exclude</b> the output folders 
-    containing the Ant tasks and types. Use the <b>Properties</b> dialog for the project to
-    correctly configure the <b>Plug-in Development > Runtime Classpath</b> by removing the Ant output 
-    directories from the plug-ins classpath.</li>
-</ul>
-
-</BODY></HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ant_eclipse_tasks.htm b/bundles/org.eclipse.platform.doc.isv/guide/ant_eclipse_tasks.htm
deleted file mode 100644
index 4c4f8cc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ant_eclipse_tasks.htm
+++ /dev/null

@@ -1,83 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Ant tasks provided by the platform
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Ant tasks provided by the platform</h2>
-<p>The platform provides some useful Ant tasks and properties that 
-interact with the workspace. They can be used with buildfiles that are set to build within the same JRE as the workspace.</p>
-
-
-<A NAME="monitor"></A><h3>
-eclipse.refreshLocal</h3>
-<p>
-This task is a wrapper to the <a href="../reference/api/org/eclipse/core/resources/IResource.html#refreshLocal(int, org.eclipse.core.runtime.IProgressMonitor)">
-<b>
-IResource.refreshLocal()</b></a> method. Example:</p>
-<pre>&lt;eclipse.refreshLocal resource=&quot;MyProject/MyFolder&quot; depth=&quot;infinite&quot;/&gt;</pre>
-<ul>
-  <li> <b>resource</b> is a resource path relative to the workspace&nbsp;</li>
-  <li> 
-<b>depth</b> can be one of the following: <b>zero</b>, <b> one</b> or <b>infinite</b></li>
-</ul>
-<h3 >
-eclipse.incrementalBuild</h3>
-
-<p>
-When the <b>project</b> attribute is supplied, this task is a wrapper to<b>
-<a href="../reference/api/org/eclipse/core/resources/IProject.html#build(int, org.eclipse.core.runtime.IProgressMonitor)">
-IProject.build()</a></b>.  Otherwise, this task is a wrapper to the method:<b>
-<a href="../reference/api/org/eclipse/core/resources/IWorkspace.html#build(int, org.eclipse.core.runtime.IProgressMonitor)">
-IWorkspace.build()</a></b>.  In both cases, the kind of build is always 
-<b><a href="../reference/api/org/eclipse/core/resources/IncrementalProjectBuilder.html#INCREMENTAL_BUILD">
-IncrementalProjectBuilder#INCREMENTAL_BUILD</a></b>
-</p>
-<p>
-Examples:
-</p>
-<pre>&lt;eclipse.incrementalBuild/&gt;</pre>
-
-<pre>
-&lt;eclipse.incrementalBuild project=&quot;MyProject&quot;/&gt;
-</pre>
-
-<ul>
-  <li> <b>project</b> the name of the project to be built</li>
-</ul>
-
-<h3>eclipse.convertPath</h3>
-
-<p>
-Converts a file system path to a resource path or vice-versa. The resulting value is
-assigned to the given property. The <b>property</b> attribute must be specified, as well as
-either the <b>fileSystemPath</b> or <b>resourcePath</b> attribute.  When 
-a file system path is supplied, this task is a wrapper to
-<b>
-<a href="../reference/api/org/eclipse/core/resources/IWorkspaceRoot.html#getContainerForLocation(org.eclipse.core.runtime.IPath)">
-IWorkspaceRoot.getContainerForLocation(IPath)</a></b>.  When a resource path
-is supplied, this task is a wrapper to
-<b>
-<a href="../reference/api/org/eclipse/core/resources/IResource.html#getLocation()">IResource.getLocation()</a></b>.
-</p>
-<p>
-Examples:</p>
-
-<pre>&lt;eclipse.convertPath fileSystemPath=&quot;${basedir}&quot; property=&quot;myPath&quot;/&gt;</pre>
-
-<pre>&lt;eclipse.convertPath resourcePath=&quot;MyProject/MyFile&quot; property=&quot;myPath&quot;/&gt;</pre>
-
-<br>
-
-</BODY></HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ant_expanding_classpath.htm b/bundles/org.eclipse.platform.doc.isv/guide/ant_expanding_classpath.htm
deleted file mode 100644
index 2a4c3c9..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ant_expanding_classpath.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Expanding the Ant classpath
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Expanding the Ant classpath</h2>
-<p>Plug-ins can contribute 
-<a href="../reference/extension-points/org_eclipse_ant_core_extraClasspathEntries.html">extra JARs</a> 
-to the Ant classpath. The plug-in contributing the JARs is also added to the Ant classpath. As a consequence,
-classes inside the extra JARs have access to all classes available for the plug-in.&nbsp;
-These extra JARs cannot be plug-in libraries; they must be separate JARs. The consequences are that 
-plug-in classes do not have access to the classes provided by these extra JARs. The
-<a href="../reference/extension-points/org_eclipse_ant_core_extraClasspathEntries.html">
-<b>org.eclipse.ant.core.extraClasspathEntries</b></a> extension point provides an example of how to specify the extra JARs 
-in the plugin.xml file.</p>
-
-&nbsp;
-
-</BODY></HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ant_running_buildfiles_programmatically.htm b/bundles/org.eclipse.platform.doc.isv/guide/ant_running_buildfiles_programmatically.htm
deleted file mode 100644
index c555eb1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ant_running_buildfiles_programmatically.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Running Ant buildfiles programmatically
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Running Ant buildfiles programmatically</h2>
-<p>
-The Ant support built into Eclipse allows plug-ins to programmatically run Ant buildfiles.
-This is done via the <a href="../reference/api/org/eclipse/ant/core/AntRunner.html"><b>AntRunner</b></a> 
-class included in the <b> org.eclipse.ant.core</b> plug-in.
-</p>
-
-<p>The following code snippet shows an example of how to use the <a href="../reference/api/org/eclipse/ant/core/AntRunner.html"><b>AntRunner</b></a> from within code of another plug-in:</p>
-
-<pre>import org.eclipse.ant.core.AntRunner;
-import org.eclipse.core.runtime.IProgressMonitor;
-
-...
-
-public void runBuild() {
-	IProgressMonitor monitor = ...
-	AntRunner runner = new AntRunner();
-	runner.setBuildFileLocation(&quot;c:/buildfiles/build.xml&quot;);
-	runner.setArguments(&quot;-Dmessage=Building -verbose&quot;);
-	runner.run(monitor);
-}</pre>
-
-<p>If a progress monitor is used, it is made available for the running tasks.
-See <a href="./ant_contributing_task.htm#monitor">Progress Monitors</a> for more details.
-</p><p>Note that only one Ant build can occur at any given time if the builds do not occur in separate VMs. See <a href="../reference/api/org/eclipse/ant/core/AntRunner.html#isBuildRunning()">
-AntRunner.isBuildRunning()</a>;
-</p>
-
-<h3>
-Special care for native libraries if build occurs within the same JRE as the workspace</h3>
-<P >
-Every time an Ant buildfile runs in Eclipse a new classloader is created. Since a library can only be
-loaded by one classloader in Java, tasks making use of native libraries could run into problems during
-multiple buildfile runs. If the previous classloader has not been garbage collected at the time the new
-classloader tries to load the native library, an exception is thrown indicating the problem and the
-build fails. One way of avoiding this problem is having the library load be handled by
-a class inside a plug-in library. The task can make use of that class for accessing native
-methods. This way, the library is loaded by the plug-in classloader and it does not run into the
-load library conflict.
-</P>
-
-
-<P >
-&nbsp;</P>
-
-
-</BODY></HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/arch.htm b/bundles/org.eclipse.platform.doc.isv/guide/arch.htm
deleted file mode 100644
index 3d2f432..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/arch.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Platform architecture 
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>Platform architecture </h1>
-
-<p>The Eclipse platform is structured around the concept of <b>plug-ins</b>.  Plug-ins are
-structured bundles of code and/or data that contribute function to the system.  Function can be
-contributed in the form of code libraries (Java classes with public API), platform <b>extensions</b>,
-or even documentation.  Plug-ins can define <b>extension points</b>, well-defined places 
-where other plug-ins can add functionality.</p>
-
-<p>Each subsystem in the platform is itself structured as a set of plug-ins that implement
-some key function.  Some plug-ins add visible features to the platform using the extension model.
-Others supply class libraries that can be used to implement system extensions.</p>
-
-<p>The Eclipse SDK includes the basic platform plus two major tools that are
-useful for plug-in development.&nbsp; The Java development tools (JDT)
-implement a full featured Java development environment.&nbsp; The Plug-in
-Developer Environment (PDE) adds specialized tools that streamline the
-development of plug-ins and extensions.</p>
-
-<p>These tools not only serve a useful purpose, but also provide a great example of
-how new tools can be added to the platform by building plug-ins that extend the
-system.</p>
-
-<p><img border="0" src="images/sdk-arch.jpg"  alt="line drawing of the architecture of the sdk"></p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/arch_struct.htm b/bundles/org.eclipse.platform.doc.isv/guide/arch_struct.htm
deleted file mode 100644
index f176b49..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/arch_struct.htm
+++ /dev/null

@@ -1,125 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Platform SDK roadmap</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Platform SDK roadmap</H2>
-
-<H3>Runtime core</H3>
-
-<P >
-The platform runtime core implements the runtime engine that starts the platform base and dynamically discovers and runs plug-ins. A
-<b> plug-in</b> is a structured component that describes itself to the system using
-an OSGi manifest (<b>MANIFEST.MF</b>) file and a plug-in manifest
-(<b>plugin.xml</b>) file. The platform maintains a registry of installed plug-ins and the function they provide.</P>
-
-<P >
-A general goal of the runtime is that the end user should not pay a memory or performance penalty for plug-ins that are installed, but not used. A plug-in can be installed and added to the registry, but the plug-in will not be activated unless
-a function provided by the plug-in has been requested according to the user's activity.</P>
-<P>The platform runtime is implemented using the OSGi services model. While implementation details of the runtime may not be 
-important to many application developers, those already familiar with OSGi will recognize that an Eclipse plug-in is, in effect,
-an OSGi bundle.</P>
-<P >
-The best way to get a feel for the runtime system is to build a plug-in. See
-<a HREF="firstplugin.htm" CLASS="XRef"> Plug it in: Hello World meets the workbench</a> to get started
-building a plug-in.  To understand the nuts and bolts of the runtime system, see 
-<a HREF="runtime.htm">Runtime overview</a>.</P>
-
-<H3>
-Resource management</H3>
-<P >
-The resource management plug-in defines a common resource model for managing the
-artifacts of tool plug-ins. Plug-ins can create and modify <b>projects</b>, <b>folders</b>, and 
-<b>files</b> for organizing and storing development artifacts on disk.</p>
-<P >
-<a HREF="resInt.htm" CLASS="XRef">Resources overview</a> provides an overview of the resource management system.</P>
-
-
-<H3>
-Workbench UI</H3>
-<P >
-The workbench UI plug-in implements the workbench UI and defines a number of extension points that allow 
-other plug-ins to contribute menu and toolbar actions, drag and drop operations, dialogs, wizards, 
-and custom views and editors.</P>
-<P >
-<a HREF="workbench.htm" CLASS="XRef">Plugging into the workbench</a> introduces the workbench
-UI extension points and API.</P>
-<P >
-Additional UI plug-ins define frameworks that are generally useful for user
-interface development.&nbsp; These frameworks were used to develop the workbench
-itself.&nbsp; Using the frameworks not only eases the development of a plug-in's
-user interface, but ensures that plug-ins have a common look and feel and a consistent 
-level of workbench integration.
-</P>
-
-<P >
-The Standard Widget Toolkit (SWT) is a low-level, operating system independent toolkit that supports platform integration and portable API.
-It is described in
-<a HREF="swt.htm" CLASS="XRef">Standard Widget Toolkit</a>.</P>
-<P >
-The JFace UI framework provides higher-level application constructs for supporting dialogs, wizards, actions, user preferences, and widget management.&nbsp;
-The functionality in JFace is described in
-<a HREF="dialogs.htm" CLASS="XRef"> Dialogs and wizards</a> and
-<a HREF="jface.htm" CLASS="XRef">JFace: UI framework for plug-ins</a>.</P>
-
-<H3>Team support</H3>
-<p>
-The Team plug-ins allow other plug-ins to define and register implementations
-for team programming, repository access, and versioning.&nbsp; The Eclipse SDK
-includes a CVS plug-in that uses the team support to provide CVS client support
-in the SDK.&nbsp;&nbsp;</p>
-
-<p>Team support is described in <a href="team.htm">Team support</a>.</p>
-
-<H3>Debug support</H3>
-<p>
-The Debug plug-ins allow other plug-ins to implement language specific program
-launchers and debuggers.&nbsp;</p>
-
-<p>Debug support is described in <a href="debug.htm">Program debug and launching
-support</a>.</p>
-
-<h3 >
-Help System</h3>
-<P >The Help plug-in implements a platform optimized help web server and
-document integration facility.&nbsp; It defines extension points that plug-ins
-can use to contribute help or other plug-in documentation as browsable
-books.&nbsp; The documentation web server includes special facilities to allow
-plug-ins to reference files by using logical, plug-in based URLs instead of file
-system URLs.</P>
-
-<P >Additional features are provided for integrating help topics in product
-level documentation configurations.</P>
-<P >The help facility is described in <a href="help.htm">Plugging in help</a>.</P>
-
-<H3>
-Java Development Tools (JDT)</H3>
-<P >
-The Java development tools (JDT) plug-ins extend the platform workbench by
-providing specialized features for editing, viewing, compiling, debugging, and
-running Java code.</P>
-<P >The JDT is installed as a set of plug-ins that are included in the SDK.&nbsp;
-The Java Development User Guide describes how to use the Java tools.&nbsp; The JDT Plug-in
-Developer Guide describes the structure and API of the JDT.</P>
-
-<H3>
-Plug-in Development Environment (PDE)</H3>
-<P >The Plug-in Development Environment (PDE) supplies tools that automate the
-creation, manipulation, debugging, and deploying of plug-ins.&nbsp; </P>
-<P >The PDE is installed as a set of plug-ins that are included in the
-SDK.&nbsp; The PDE Guide describes how to use the environment.</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/compare.htm b/bundles/org.eclipse.platform.doc.isv/guide/compare.htm
deleted file mode 100644
index 5f03e7f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/compare.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Compare support</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Compare support</H1>
-
-
-<p>
-If your plug-in defines and manipulates its own resource types, you may have
-special requirements for comparing resources.&nbsp; Resources are often compared
-when working with local history or with files from a repository.&nbsp; The <b>compare</b>
-plug-in supports merging of multiple content streams and the implementation of advanced compare views.
-Services provided by this plug-in include:</p>
-
-
-<ul>
-  <li>Interfaces for merging multiple text streams into a single output stream</li>
-  <li>Two and three-way compare and merge components for hierarchical structures
-    inferred from text</li>
-  <li>Differencing engines for hierarchical structures and character ranges in
-    text</li>
-</ul>
-<p>These services are used in the platform to assist with user tasks such as
-integrating patch files and comparing/merging the workspace with local history.</p>
-<h2>Compare viewers</h2>
-<p>
-All compare viewers are standard <a href="jface_viewers.htm"> JFace viewers</a> that expect an input object implementing the
-<b><a href="../reference/api/org/eclipse/compare/structuremergeviewer/ICompareInput.html">ICompareInput</a></b>
-interface.</p>
-<p>
-Compare viewers are said to be
-<a href="compare_contentviewer.htm">content-oriented</a>  if they compare flat
-inputs such as text or images and
-<a href="compare_structureviewer.htm">structure-oriented</a>  if they compare
-hierarchically structured input elements.</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/compare_beyond.htm b/bundles/org.eclipse.platform.doc.isv/guide/compare_beyond.htm
deleted file mode 100644
index fa0434d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/compare_beyond.htm
+++ /dev/null

@@ -1,136 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Advanced compare techniques</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Advanced compare techniques</H2>
-
-<p>
-This section provides additional information about advanced API in the compare
-plug-in.</p>
-
-<h3>Writing compare operations</h3>
-
-<p>A compare operation must be implemented as a subclass of
-<a href="../reference/api/org/eclipse/compare/CompareEditorInput.html"><b>CompareEditorInput</b></a>.&nbsp;
-A
-<a href="../reference/api/org/eclipse/compare/CompareEditorInput.html"><b>CompareEditorInput</b></a>
-runs a (potentially lengthy) compare operation
-under progress monitor control, creates a UI for drilling-down into the
-compare results, tracks the dirty state of the result in case of merge,
-and saves any changes that occurred during a merge.</p>
-
-<p>
-
-<a href="../reference/api/org/eclipse/compare/CompareUI.html"><b>CompareUI</b></a>
-defines the entry point to initiate a configurable
-compare operation on arbitrary resources. The result of the compare is
-opened into a compare editor where the details can be browsed and edited
-in dynamically selected structure and content viewers.</p>
-<p>
-
-<a href="../reference/api/org/eclipse/compare/NavigationAction.html"><b>NavigationAction</b></a>
-is used to navigate (step) through the individual
-differences of a 
-<a href="../reference/api/org/eclipse/compare/CompareEditorInput.html"><b>CompareEditorInput</b></a>.</p>
-<p>
-
-<a href="../reference/api/org/eclipse/compare/CompareConfiguration.html"><b>CompareConfiguration</b></a>
-configures various UI aspects
-of compare/merge viewers like title labels and images, or whether a side
-of a merge viewer is editable. It is passed to the
-<a href="../reference/api/org/eclipse/compare/CompareEditorInput.html"><b>CompareEditorInput</b></a>
-on creation.</p>
-<p>
-
-When implementing a hierarchical compare operation as a subclass of
-<a href="../reference/api/org/eclipse/compare/CompareEditorInput.html"><b>CompareEditorInput</b></a>,
-clients must provide a tree of objects where each
-node implements the interface
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/IStructureComparator.html"><b>IStructureComparator</b></a>.
-This interface is used by the hierarchical differencing engine
-(<a href="../reference/api/org/eclipse/compare/structuremergeviewer/Differencer.html"><b>Differencer</b></a>) to walk the tree.
-<br>
-In addition every leaf of the tree must implement the
-<a href="../reference/api/org/eclipse/compare/IStreamContentAccessor.html"><b>IStreamContentAccessor</b></a>
-interface in order to give the differencing engine access to its stream content.</p>
-<p>
-
-<a href="../reference/api/org/eclipse/compare/BufferedContent.html"><b>BufferedContent</b></a>
-provides a default implementation
-for the
-<a href="../reference/api/org/eclipse/compare/IStreamContentAccessor.html"><b>IStreamContentAccessor</b></a>
-and
-<a href="../reference/api/org/eclipse/compare/IContentChangeNotifier.html"><b>IContentChangeNotifier</b></a>
-interfaces.
-Its subclass
-<a href="../reference/api/org/eclipse/compare/ResourceNode.html"><b>ResourceNode</b></a>
-adds an implementation for the
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/IStructureComparator.html"><b>IStructureComparator</b></a>
-and
-<a href="../reference/api/org/eclipse/compare/ITypedElement.html"><b>ITypedElement</b></a>
-interfaces
-based on platform workbench resources
-(<a href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a>). 
-It can be used without modification as the input to the differencing engine.</p>
-
-
-<h3>Compare functionality outside of compare editors</h3>
-
-
-<p>If you want to use compare functionality outside of the standard compare editor 
-(for example, in a dialog or wizard) the compare plug-in provides additional helper
-classes.</p>
-
-<p>
-
-<a href="../reference/api/org/eclipse/compare/CompareViewerPane.html"><b>CompareViewerPane</b></a>
-is a convenience class which provides
-a label and local toolbar for a compare viewer (or any other subclass of a <a href="jface_viewers.htm"> JFace
-viewer</a>).&nbsp; Its abstract subclass
-<a href="../reference/api/org/eclipse/compare/CompareViewerSwitchingPane.html"><b>CompareViewerSwitchingPane</b></a>
-supports <b>dynamic viewer switching</b>, that is the viewer installed in the pane is dynamically 
-determined by the pane's input object.</p><p>
-<a href="../reference/api/org/eclipse/compare/EditionSelectionDialog.html"><b>EditionSelectionDialog</b></a>
-is a simple selection dialog where
-one input element can be compared against a list of historic variants (<b>editions</b>)
-of the same input element. The dialog is used to implement functions
-like <i>&quot;</i><b>Replace with Local History"</b> on workbench resources.</p>
-<p>
-
-In addition it is possible to specify a subsection of the input element
-(e.g. a method in a Java source file) by means of a <b>path</b>. In this
-case the dialog compares only the subsection (as specified by the path)
-with the corresponding subsection in the list of editions. This functionality
-can be used to implement <i>&quot;</i><b>Replace with Element from Local History"</b> for 
-Java Elements.</p>
-<p>
-
-The
-<a href="../reference/api/org/eclipse/compare/EditionSelectionDialog.html"><b>EditionSelectionDialog</b></a>
-requires that the editions implement the
-<a href="../reference/api/org/eclipse/compare/IStreamContentAccessor.html"><b>IStreamContentAccessor</b></a>
-and
-<a href="../reference/api/org/eclipse/compare/IModificationDate.html"><b>IModificationDate</b></a>
-interfaces.
-The
-<a href="../reference/api/org/eclipse/compare/HistoryItem.html"><b>HistoryItem</b></a>
-is a convenience class that implements these interfaces for
-<a href="../reference/api/org/eclipse/core/resources/IFileState.html"><b>IFileState</b></a> objects.
-</p>
-
-&nbsp;
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/compare_contentviewer.htm b/bundles/org.eclipse.platform.doc.isv/guide/compare_contentviewer.htm
deleted file mode 100644
index 57c01b1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/compare_contentviewer.htm
+++ /dev/null

@@ -1,176 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Implementing a Content Viewer</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Implementing a content viewer</H2>
-
-
-<p>
-The compare plug-in allows you to supply specialized viewers for viewing and
-merging content differences between unstructured elements.</p>
-
-
-<h3>
-Simple content viewers</h3>
-
-
-<p>
-A <b>content viewer</b> is used in places where only a single input is available and therefore
-no compare is necessary.&nbsp; A typical example for this is the &quot;<b>Restore from Local
-History</b>&quot; function.&nbsp; The <a href="../reference/extension-points/org_eclipse_compare_contentViewers.html"><b>org.eclipse.compare.contentViewers</b></a>
-extension point allows you to define a specialized content viewer that does not
-compare its inputs. </p>
-<pre>&lt;extension
-	point="org.eclipse.compare.contentViewers"&gt;
-	&lt;viewer
-		extensions="java,java2"
-		class="org.eclipse.jdt.internal.ui.compare.JavaTextViewerCreator"
-		id="org.eclipse.jdt.internal.ui.compare.JavaTextViewerCreator"&gt;
-	&lt;/viewer&gt;
-	&lt;contentTypeBinding
-		contentTypeId="org.eclipse.jdt.core.javaSource"
-		contentViewerId="org.eclipse.jdt.internal.ui.compare.JavaTextViewerCreator"&gt;
-	&lt;/contentTypeBinding&gt;
-&lt;/extension&gt;
-</pre>
-<p>Specialized viewers contributed by your plug-in are designated in the
-<b>viewer</b> element.  You must specify the <b>id </b>of the viewer and the <b>class</b> that
-creates it.  You may also specify any file <b>extensions</b> for which the content viewer should be used.&nbsp;&nbsp;</p>
-<p>You may also use the <b>contentTypeBinding</b> element to associate a <a href="runtime_content.htm">content type</a> 
-with a content viewer.  
-</p>
-<h3>Content merge viewers</h3>
-<p>	A <b> content merge viewer </b> performs a two-way or three-way compare of its inputs
-and presents the result side-by-side or in any other suitable way.&nbsp; The viewer lets the user 
-merge between the inputs.  Content merge viewers are common for text or images.</p>
-<p>If the standard merge viewers are not appropriate for your plug-in's
-function, you may choose to implement your own content merge viewer.&nbsp; Your
-content merge viewer should be registered with the platform using the
-<a href="../reference/extension-points/org_eclipse_compare_contentMergeViewers.html"><b>org.eclipse.compare.contentMergeViewers</b></a>
-extension point.&nbsp; The following markup shows
-the definition of specialized content merge viewers for viewing Java files and
-properties files in the Java IDE:
-</p>
-<pre>&lt;extension
-	point="org.eclipse.compare.contentMergeViewers"&gt;
-	&lt;viewer
-		extensions="java,java2"
-		class="org.eclipse.jdt.internal.ui.compare.JavaContentViewerCreator"
-		id="org.eclipse.jdt.internal.ui.compare.JavaContentViewerCreator"&gt;
-	&lt;/viewer&gt;
-	&lt;contentTypeBinding
-		contentTypeId="org.eclipse.jdt.core.javaProperties"
-		contentMergeViewerId="org.eclipse.compare.TextMergeViewerCreator"&gt;
-	&lt;/contentTypeBinding&gt;
-	&lt;contentTypeBinding
-		contentTypeId="org.eclipse.jdt.core.javaSource"
-		contentMergeViewerId="org.eclipse.jdt.internal.ui.compare.JavaContentViewerCreator"&gt;
-	&lt;/contentTypeBinding&gt;
-&lt;/extension&gt;
-</pre>
-<p>
-Similar to content viewers, specialized merge viewers contributed by your plug-in are designated in the
-<b>viewer</b> element.  You must specify the <b>id </b>of the viewer and the <b>class</b> that
-creates it.  You may also specify any file <b>extensions</b> for which the content merge viewer should be used.
-</p>
-<p>Also similar to content viewers, you can use <b>contentTypeBinding</b> to associate a <a href="runtime_content.htm">content type</a> 
-with a merge viewer.  The JDT plug-in binds content merge viewers to two different content types:  Java source and Java properties files.
-</p>
-
-
-<p> <a href="../reference/api/org/eclipse/compare/contentmergeviewer/ContentMergeViewer.html"><b>ContentMergeViewer</b></a>
-is an abstract compare and merge viewer
-with two side-by-side content areas and an optional content area for a
-common ancestor (for three-way compare).&nbsp; Because the implementation makes
-no assumptions about the content type, the subclass is responsible for dealing
-with the specific content type.&nbsp;&nbsp;</p>
-
-
-<p> <b>ImageMergeViewer</b> in <b> org.eclipse.compare.internal</b> shows how to
-implement a simple merge viewer for images using a <a href="../reference/api/org/eclipse/compare/contentmergeviewer/ContentMergeViewer.html"><b>ContentMergeViewer</b></a>.&nbsp;
-A <a href="../reference/api/org/eclipse/compare/contentmergeviewer/ContentMergeViewer.html"><b>ContentMergeViewer</b></a> 
-accesses its model by means of a content
-provider which must implement the
-<a href="../reference/api/org/eclipse/compare/contentmergeviewer/IMergeViewerContentProvider.html"><b>IMergeViewerContentProvider</b></a> interface.</p>
-
-
-<h4> Text merging</h4>
-
-
-<p> If your viewer uses text, additional classes that&nbsp; compare
-and merge text content can be used.</p>
-<p>
-<a href="../reference/api/org/eclipse/compare/contentmergeviewer/TextMergeViewer.html"><b>TextMergeViewer</b></a>
-is the concrete subclass of
-<a href="../reference/api/org/eclipse/compare/contentmergeviewer/ContentMergeViewer.html"><b>ContentMergeViewer</b></a>
- used for comparing and merging text content.&nbsp; A text merge viewer uses the
-<a href="../reference/api/org/eclipse/compare/rangedifferencer/RangeDifferencer.html"><b>RangeDifferencer</b></a>
-to perform a textual, line-by-line comparison of two (or three) input documents.</p>
-<p>
-For text lines that differ, the
-<a href="../reference/api/org/eclipse/compare/contentmergeviewer/TextMergeViewer.html"><b>TextMergeViewer</b></a>
-uses an
-<a href="../reference/api/org/eclipse/compare/contentmergeviewer/ITokenComparator.html"><b>ITokenComparator</b></a>
-to find the longest sequences of matching and non-matching tokens.
-The 
-<a href="../reference/api/org/eclipse/compare/contentmergeviewer/TextMergeViewer.html"><b>TextMergeViewer</b></a>'s
-default token compare works on characters separated by white space. If a
-different strategy is needed (for example, Java tokens in a Java-aware
-merge viewer), clients can create their own token comparators by implementing
-the
-<a href="../reference/api/org/eclipse/compare/contentmergeviewer/ITokenComparator.html"><b>ITokenComparator</b></a>
-interface.</p>
-<p>
- <a href="../reference/api/org/eclipse/compare/contentmergeviewer/TextMergeViewer.html"><b>TextMergeViewer</b></a>
- works on whole documents and on sub ranges of documents. For partial documents,
-the viewer's input must be an
-<a href="../reference/api/org/eclipse/compare/contentmergeviewer/IDocumentRange.html"><b>IDocumentRange</b></a>
-instead of an
-<a href="../reference/api/org/eclipse/jface/text/IDocument.html"><b>IDocument</b></a>.</p>
-<h4>Range differencing</h4>
-<p> 
-<a href="../reference/api/org/eclipse/compare/rangedifferencer/RangeDifferencer.html"><b>RangeDifferencer</b></a>
- finds the longest sequences of matching and
-non-matching comparable entities in text content. Its implementation is based on
-an objectified version of the algorithm described in:
-<i>A File Comparison Program,</i> by Webb Miller and Eugene W. Myers,
-Software Practice and Experience, Vol. 15, Nov. 1985.&nbsp; Clients must supply
-an input to the differencer that implements the
-<a href="../reference/api/org/eclipse/compare/rangedifferencer/IRangeComparator.html"><b>IRangeComparator</b></a>
-interface.
-<a href="../reference/api/org/eclipse/compare/rangedifferencer/IRangeComparator.html"><b>IRangeComparator</b></a>
-breaks the input data into a sequence
-of entities and provides a method for comparing
-one entity with the entity in another
-<a href="../reference/api/org/eclipse/compare/rangedifferencer/IRangeComparator.html"><b>IRangeComparator</b></a>.
-</p><p>
-For example, to compare two text documents and find the longest common
-sequences of matching and non-matching lines,
-the implementation of
-<a href="../reference/api/org/eclipse/compare/rangedifferencer/IRangeComparator.html"><b>IRangeComparator</b> </a>
-must break the document into lines and provide a method for testing
-whether two lines are considered equal.
-See <b>org.eclipse.compare.internal.DocLineComparator</b> for an example of how this can be done.</p>
-<p>The differencer returns the differences among these sequences as an
-array of
-<a href="../reference/api/org/eclipse/compare/rangedifferencer/RangeDifference.html"><b>RangeDifference</b></a>
-objects.
-Every single
-<a href="../reference/api/org/eclipse/compare/rangedifferencer/RangeDifference.html"><b>RangeDifference</b></a>
-describes the kind of difference
-(no change, change, addition, deletion) and the corresponding ranges
-of the underlying comparable entities in the two or three inputs.
-</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/compare_streammerger.htm b/bundles/org.eclipse.platform.doc.isv/guide/compare_streammerger.htm
deleted file mode 100644
index c228218..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/compare_streammerger.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Merging multiple streams</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Merging multiple streams</H2>
-<p>
-The search plug-in allows you to customize views that assist the user in merging different 
-content streams.  In some cases, however, the ability to merge streams without the assist of a user
-is desirable.  The extension point
-<a href="../reference/extension-points/org_eclipse_compare_streamMergers.html"><b>org.eclipse.compare.streamMergers</b></a>
-allows you to contribute a class that merges three different input streams into a single output stream.  Stream mergers
-can be associated with file extensions or bound to a particular content type.  The search plug-in defines a stream
-merger for merging three streams of plain text:</p>
-<pre>&lt;extension
-	point="org.eclipse.compare.streamMergers"&gt;
-	&lt;streamMerger
-		extensions="txt"
-		class="org.eclipse.compare.internal.merge.TextStreamMerger"
-		id="org.eclipse.compare.internal.merge.TextStreamMerger"&gt;
-	&lt;/streamMerger>
-	&lt;contentTypeBinding
-		contentTypeId="org.eclipse.core.runtime.text"
-		streamMergerId="org.eclipse.compare.internal.merge.TextStreamMerger"&gt;
-	&lt;/contentTypeBinding&gt;
-&lt;/extension&gt;
-</pre>
-<p>The stream merger itself is described in the <b>streamMerger</b> element.  You must specify the <b>id </b>of the 
-merger and the <b>class</b> that implements it.  You may also specify any file <b>extensions</b> for which the 
-the stream merger should be used.</p>
-<p>You may also use the <b>contentTypeBinding</b> element to associate a <a href="runtime_content.htm">content type</a> 
-with a stream merger.
-</p>
-<p>
-Stream mergers must implement 
-<a href="../reference/api/org/eclipse/compare/IStreamMerger.html"><b>IStreamMerger</b></a>.
-This simple interface merges the contents from three different input streams into a single output stream.
-The not-so-simple implementation depends upon your plug-in and its content types.
-</p>
-
-<p>
-New <a href="../reference/api/org/eclipse/compare/IStreamMerger.html"><b>IStreamMerger</b></a>s
-can be created for registered types with the createStreamMerger methods of <a href="../reference/api/org/eclipse/compare/CompareUI.html"><b>CompareUI</b></a>.
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/compare_structureviewer.htm b/bundles/org.eclipse.platform.doc.isv/guide/compare_structureviewer.htm
deleted file mode 100644
index ab0559e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/compare_structureviewer.htm
+++ /dev/null

@@ -1,167 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Implementing a structure viewer</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Implementing a structure viewer</H2>
-<p>
-A structure merge viewer performs a two-way or three-way compare of its inputs, presents the result
-in a hierarchical view, and lets the user merge between the inputs.&nbsp;
-Structure merge viewers are common for workspace resources or the members of
-an archive file.</p>
-<h3>Tree-like structure viewers</h3>
-<p>Because the implementation of many structure compare viewers is based
-on a tree, the compare plug-in provides a generic tree-based
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/StructureDiffViewer.html"><b>StructureDiffViewer</b></a>.
-Your plug-in is responsible for supplying a <b>structure creator</b>  that breaks a single input object into a hierarchical structure.
-The <a href="../reference/api/org/eclipse/compare/structuremergeviewer/StructureDiffViewer.html"><b>StructureDiffViewer</b></a>
-performs the compare on the resulting structure and displays the result as a tree.</p>
-<p>You designate a structure creator for your plug-in using the <a href="../reference/extension-points/org_eclipse_compare_structureCreators.html"><b>org.eclipse.compare.structureCreators</b></a>
-extension.  Much like content viewers, a structure creator can be specified for a set of file <b>extensions</b>, or
-a <b>contentTypeBinding</b> can be used to associate a <a href="runtime_content.htm">content type</a> with a particular
-structure creator.  We won't review the markup here since it's so similar to content viewers.
-The JDT plug-in defines several contributions for 
-<a href="../reference/extension-points/org_eclipse_compare_structureCreators.html"><b>org.eclipse.compare.structureCreators</b></a>.</p>
-
-<h3>Other hierarchical structure viewers</h3>
-<p>In some cases, the tree-based <a href="../reference/api/org/eclipse/compare/structuremergeviewer/StructureDiffViewer.html"><b>StructureDiffViewer</b></a>
-may not be appropriate for your plug-in.&nbsp; The <a href="../reference/extension-points/org_eclipse_compare_structureMergeViewers.html"><b>org.eclipse.compare.structureMergeViewers</b></a>
-extension point allows you to define your own implementation for a structure
-merge viewer.  A structure merge viewer can be specified for file <b>extensions</b>, or
-a <b>contentTypeBinding</b> can be used to associate a <a href="runtime_content.htm">content type</a> with a particular
-structure merge viewer.  See the JDT plug-in for examples of
-<a href="../reference/extension-points/org_eclipse_compare_structureMergeViewers.html"><b>org.eclipse.compare.structureMergeViewers</b></a>
-contributions.</p>
-
-<p>The search plug-in provides several utility classes to help you implement a search
-viewer.</p>
-
-
-<h4>
-Differencer&nbsp;</h4>
-
-
-<p>
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/Differencer.html"><b>Differencer</b></a>
-is a differencing engine for hierarchically
-structured data. It takes two or three inputs and performs a two-way or
-three-way compare on them.</p>
-
-
-<p>
-
-If the input elements to the differencing engine implement the
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/IStructureComparator.html"><b>IStructureComparator</b></a>
-interface, the engine recursively applies itself to the children of
-the input element. Leaf elements must implement the
-<a href="../reference/api/org/eclipse/compare/IStreamContentAccessor.html"><b>IStreamContentAccessor</b></a>
-interface so that the differencer can perform a byte wise comparison on their contents.</p><p>There
-are several good examples of differencers included in the platform
-implementation:</p>
-<ul>
-  <li>
-<a href="../reference/api/org/eclipse/compare/ResourceNode.html"><b>ResourceNode</b></a>
- implements both interfaces
-(and more) for platform workspace resources
-(<a href="../reference/api/org/eclipse/core/resources/IResource.html"><b>org.eclipse.core.resources.IResource</b></a>).</li>
-  <li>
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/DocumentRangeNode.html"><b>DocumentRangeNode</b></a>
-    is used to compare hierarchical structures
-that are superimposed on a document.&nbsp; Nodes and leaves correspond to ranges in a document
-(<a href="../reference/api/org/eclipse/compare/contentmergeviewer/IDocumentRange.html"><b>IDocumentRange</b></a>).&nbsp;
-    Typically, <a href="../reference/api/org/eclipse/compare/structuremergeviewer/DocumentRangeNode.html"><b>DocumentRangeNode</b></a>s
-are created while parsing a document and they represent
-the semantic entities of the document (e.g. a Java class, method or field).
-The two subclasses <b>JavaNode</b> (in <b>org.eclipse.jdt.internal.ui.compare</b>)
-and <b>PropertyNode</b> (in <b>org.eclipse.jdt.internal.ui.compare</b>) are good examples for this.</li>
-</ul>
-<p>
-
-By default the differencing engine returns the result of the compare operation
-as a tree of
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/DiffNode.html"><b>DiffNode</b></a>
-objects.&nbsp; A
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/DiffNode.html"><b>DiffNode</b></a>
-describes the changes among two or three inputs.&nbsp; The type of result nodes
-can be changed by overriding
-a single method of the engine.</p>
-<h4>Difference Viewers</h4>
-<p>
-
-A tree of
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/DiffNode.html"><b>DiffNode</b></a>s
-can be displayed in a 
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/DiffTreeViewer.html"><b>DiffTreeViewer</b></a>.
-The
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/DiffTreeViewer.html"><b>DiffTreeViewer</b></a>
-requires that inner nodes of the tree implement
-the
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/IDiffContainer.html"><b>IDiffContainer</b></a>
-interface and leaves implement the
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/IDiffElement.html"><b>IDiffElement</b></a>
-interface.</p>
-<p>
-
-The typical steps to compare hierarchically structured data and to display
-the differences are as follows:
-<ol>
-<li>
-Map the input data into a tree of objects implementing both the
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/IStructureComparator.html"><b>IStructureComparator</b></a>
-and
-<a href="../reference/api/org/eclipse/compare/IStreamContentAccessor.html"><b>IStreamContentAccessor</b></a>
- interfaces</li>
-
-<li>
-Perform the compare operation by means of the
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/Differencer.html"><b>Differencer</b></a></li>
-
-<li>
-Feed the differencing result into the
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/DiffTreeViewer.html"><b>DiffTreeViewer</b></a></li>
-
-</ol></p>
-<p>
-The
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/StructureDiffViewer.html"><b>StructureDiffViewer</b></a>
-is a specialized
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/DiffTreeViewer.html"><b>DiffTreeViewer</b></a>
-that automates the three steps from above. It takes a single input object
-of type
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/ICompareInput.html"><b>ICompareInput</b></a>
-from which it retrieves the two or three
-input elements to compare.&nbsp; It uses an
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/IStructureCreator.html"><b>IStructureCreator</b></a>
-to extract a tree containing <a href="../reference/api/org/eclipse/compare/structuremergeviewer/IStructureComparator.html"><b>IStructureComparator</b></a>
-and
-<a href="../reference/api/org/eclipse/compare/IStreamContentAccessor.html"><b>IStreamContentAccessor</b></a>
- objects from them.&nbsp; These trees are then compared with the differencing engine and
-the result is displayed in the tree viewer.
-</p>
-<p>
-The
-<a href="../reference/api/org/eclipse/compare/ZipFileStructureCreator.html"><b>ZipFileStructureCreator</b></a>
-is an implementation of the
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/IStructureCreator.html"><b>IStructureCreator</b></a>
-interface and makes the contents of a zip archive available as a
-hierarchical structure of
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/IStructureComparator.html"><b>IStructureComparator</b></a>s
-which can be easily compared
-by the differencing engine
-(<a href="../reference/api/org/eclipse/compare/structuremergeviewer/Differencer.html"><b>Differencer</b></a>).
-It is a good example for how to make structured files available to the hierarchical 
-compare functionality of the compare plug-in.</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/component_framework.htm b/bundles/org.eclipse.platform.doc.isv/guide/component_framework.htm
deleted file mode 100644
index 9966d87..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/component_framework.htm
+++ /dev/null

@@ -1,73 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Component Framework</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>Component Framework</H1>
-<P CLASS="Para"> By providing simple API for views and editors, also known as 
-  parts, the Component Framework permits existing parts to be nested and composed. 
-  The Component Framework API allows clients to instantiate parts inside arbitrary 
-  SWT composites, improves robustness and leak proofing by having a part communicate 
-  with local interfaces on its site rather than reaching to global objects, allows 
-  clients to extend the set of interfaces available from a site and provides a 
-  framework for clients to create their own reusable components using the same 
-  API available to views and editors. The Component Framework also allows for 
-  constructing and destructing a part with atomic operations and allows existing 
-  parts to use new site interfaces.</P>
-<P CLASS="Para"><img alt="Image of NameViewNew view" src="images/NameViewNew.PNG"><br>
-</P>
-<P CLASS="Para">This simple example provides a view that sets its name, title, 
-  tooltip, and image and demonstrates how to write an editor or view using the 
-  component framework. It shows the source using the component API. New parts 
-  can take arguments in their constructor and do not need to implement any particular 
-  interface or need to inherit from any particular base class.<br>
-  <br>
-</P>
-<div style="margin-left: 40px;"><code>/**<br>
-  &nbsp;* Sample view that sets its name, tooltip, image, and content description. 
-  The view<br>
-  &nbsp;* uses a custom image supplied by its plug-in.<br>
-  &nbsp;* <br>
-  &nbsp;* @since 3.1<br>
-  &nbsp;*/<br>
-  public class NameViewNew {<br>
-  &nbsp;&nbsp;&nbsp; /**<br>
-  &nbsp;&nbsp;&nbsp;&nbsp; * Component constructor. Do not invoke directly.<br>
-  &nbsp;&nbsp;&nbsp;&nbsp; */<br>
-  &nbsp;&nbsp;&nbsp; public NameViewNew(Composite parent, INameable name, IPluginImages 
-  images) {<br>
-  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; name.setName("Name View (New)");<br>
-  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; name.setContentDescription("content description");<br>
-  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; name.setTooltip("This is a tooltip");<br>
-  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; name.setImage(images.getImage("icons/sample.gif"));<br>
-  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; <br>
-  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; // Create some bogus view contents<br>
-  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Label content = new Label(parent, SWT.NONE);<br>
-  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; content.setText("View contents go here");<br>
-  &nbsp;&nbsp;&nbsp; }<br>
-  }</code><br>
-</div>
-<p>Notice that the arguments given to the view's constructor are already aware 
-  of their context. For example, the IPluginImages interface does not need to 
-  be told which plug-in the view belongs to. Similarly, the interfaces are resistant 
-  to leaks. In this example, the view's image is allocated and deallocated automatically 
-  by the INameable implementation, so the view itself doesn't need to implement 
-  a dispose method.<br>
-  <br>
-  It is interesting to note that the API for views and editors is exactly the 
-  same. In other words, if we had chosen to register the NameViewNew class with 
-  the org.eclipse.ui.editors extension point, it could also be used as an editor 
-  without further modification.<br>
-</p>
-<h2>&nbsp; </h2>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/component_implementation.htm b/bundles/org.eclipse.platform.doc.isv/guide/component_implementation.htm
deleted file mode 100644
index a518e05..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/component_implementation.htm
+++ /dev/null

@@ -1,133 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Component implementation</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Component implementation</H1>
-Components registered with the types extension point are much like part components. 
-They can take a set of dependencies in their constructor and must implement the 
-interface they were registered for. This example shows the implementation of the 
-NullNameableService.<br>
-<br>
-<div style="margin-left: 40px;"><code>/**</code><br>
-  <code>&nbsp;* Default implementation of the Nameable service. All methods are 
-  no-ops.</code><br>
-  <code>&nbsp;* </code><br>
-  <code>&nbsp;* @since 3.1</code><br>
-  <code>&nbsp;*/</code><br>
-  <code>public class NullNameableService implements INameable {</code><br>
-  <br>
-  <code>&nbsp;&nbsp;&nbsp; /**</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp; * Component constructor. Do not invoke directly.</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp; */</code><br>
-  <code>&nbsp;&nbsp;&nbsp; public NullNameableService() {</code><code>}</code><br>
-  <br>
-  <code>&nbsp;&nbsp;&nbsp; public void setName(String newName) {}</code><br>
-  <code>&nbsp;&nbsp;&nbsp; public void setContentDescription(String contentDescription) 
-  {</code><code>}</code><br>
-  <code>&nbsp;&nbsp;&nbsp; public void setImage(ImageDescriptor theImage) {</code><code>}</code><br>
-  <code>&nbsp;&nbsp;&nbsp; public void setTooltip(String toolTip) {</code><code>}</code><br>
-  <code>}</code><br>
-</div>
-<br>
-This may be a simple example as the class doesn't do anything, however it demonstrates 
-a common pattern. The INameable service is used to tell the parent about some 
-state in the child. With this type of interface, the default implementation typically 
-doesn't do anything. This makes sense: if the parent doesn't care about the state 
-of its child, it can be ignored. By convention, we use the "Null" prefix to indicate 
-that this is a component that doesn't do anything. This type of object is usually 
-registered as a singleton since it would be wasteful to create multiple instances 
-of such a trivial object. Clients should ensure that any new interfaces that report 
-state are capable of being multiplexed.<br>
-<br>
-If the purpose of the interface is to allocate resources or generate output, the 
-default implementation will typically do something more useful. The following 
-example shows the implementation of the DefaultMessageDialogs class. Since this 
-class is intended for generating interactive output, it has a useful default implementation 
-and would not support multiplexing. Since this class needs access to a part's 
-Composite, it cannot be a singleton. By convention, we use the class prefix "Default" 
-to indicate that this is a default component with some useful behavior.<br>
-<br>
-<span style="font-weight: bold;"> </span> 
-<div style="margin-left: 40px;"><code>/**</code><br>
-  <code>&nbsp;* Default implementation of the IMessageDialogs interface. Takes 
-  the part's </code><br>
-  <code>&nbsp;* control as context and allows the part to open dialogs in a child 
-  shell.</code><br>
-  <code>&nbsp;* </code><br>
-  <code>&nbsp;* @since 3.1</code><br>
-  <code>&nbsp;*/</code><br>
-  <code>public class DefaultMessageDialogs implements IMessageDialogs {</code><br>
-  <br>
-  <code>&nbsp;&nbsp;&nbsp; private Composite control;</code><br>
-  <code>&nbsp;&nbsp;&nbsp; </code><br>
-  <code>&nbsp;&nbsp;&nbsp; /**</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp; * Component constructor. Do not invoke directly.</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp; */</code><br>
-  <code>&nbsp;&nbsp;&nbsp; public DefaultMessageDialogs(Composite control) {</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; this.control = control;</code><br>
-  <code>&nbsp;&nbsp;&nbsp; }</code><br>
-  <code>&nbsp;&nbsp;&nbsp; </code><br>
-  <code>&nbsp;&nbsp;&nbsp; public void open(IStatus message) {</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if (message.getSeverity() == 
-  IStatus.ERROR) {</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ErrorDialog.openError(control.getShell(), 
-  null, null, message);</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; } else {</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; open(message.getSeverity(), 
-  message.getMessage());</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }</code><br>
-  <code>&nbsp;&nbsp;&nbsp; }</code><br>
-  <br>
-  <code>&nbsp;&nbsp;&nbsp; public void openError(String message, Throwable cause) 
-  {</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; open(new Status(IStatus.ERROR, 
-  </code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  WorkbenchPlugin.getDefault().getBundle().getSymbolicName(),</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  IStatus.OK,</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  message,</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  cause));</code><br>
-  <code>&nbsp;&nbsp;&nbsp; }</code><br>
-  <code>&nbsp;&nbsp;&nbsp; </code><br>
-  <code>&nbsp;&nbsp;&nbsp; public void open(int severity, String message) {</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if (severity == IStatus.ERROR) 
-  {</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MessageDialog.openError(control.getShell(), 
-  null, message);</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; } else if (severity == IStatus.WARNING) 
-  {</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MessageDialog.openWarning(control.getShell(), 
-  null, message);</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; } else {</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MessageDialog.openInformation(control.getShell(), 
-  null, message);</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }&nbsp;&nbsp;&nbsp; </code><br>
-  <code>&nbsp;&nbsp;&nbsp; }</code><br>
-  <code>}</code><br>
-  </div>
-<p>Here is the associated extension point markup for DefaultMessageDialog.</p>
-<div style="margin-left: 40px;"><code>&lt;extension</code><code> point="org.eclipse.core.component.types"&gt;</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;component</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  initializer="org.eclipse.ui.part.SiteInitializer"</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; interface="org.eclipse.ui.part.services.IMessageDialogs"</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; implementation="org.eclipse.ui.internal.part.services.DefaultMessageDialogs"</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; singleton="false"</code><code>/&gt;</code><br>
-  <code>&lt;/extension&gt;</code><br>
-</div>
-<h2>&nbsp; </h2>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug.htm
deleted file mode 100644
index bdaf5f0..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Program debug and launch support</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Program debug and launch support</H1>
-<p>The resources plug-in in the Eclipse platform allows you to manage a set of
-source files for a program and compile them using an incremental project
-builder.&nbsp; Plug-ins can define new builders that handle special resource
-types, such as source files for a particular programming language.&nbsp; Once an
-executable program is built with your plug-in's builder, how can you make sure
-that it gets invoked correctly?</p>
-<p>The <b><a href="../reference/api/org/eclipse/debug/core/package-summary.html"> org.eclipse.debug.core</a>
-</b> plug-in provides the API that allows a program to define a configuration
-for launching a program.&nbsp; The program can be launched in different modes.  For
-example, it could be launched for regular execution, for debugging, for profiling,
-or any other mode defined by your plug-in.&nbsp; The
-Eclipse Java development tooling (JDT) uses the platform debug support to launch
-Java VM's and the Java debugger.&nbsp;&nbsp;</p>
-<p>The <b><a href="../reference/api/org/eclipse/debug/ui/package-summary.html"> org.eclipse.debug.ui</a></b> plug-in includes support for user configuration of
-launch parameters and utility classes that ease the implementation of powerful debuggers.</p>
-<p>There are some shared concepts in launching and debugging programs that are
-implemented in the platform debug support.&nbsp; However, the best way to
-understand how to use the platform debug support is to study a robust concrete
-implementation of launching and debugging, such as the JDT launching and debug
-tools.&nbsp; We'll review the major concepts of the platform debug support in the context
-of the JDT concrete implementation.</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_breakpoints.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_breakpoints.htm
deleted file mode 100644
index 337202b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_breakpoints.htm
+++ /dev/null

@@ -1,82 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Breakpoints</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Breakpoints </h3>
-<p>Breakpoints allow users to suspend the execution of a program at a particular
-location. Breakpoints are typically shown in the UI along with the source
-code. When a breakpoint is encountered during execution of a program, the program suspends
-and triggers a <b>SUSPEND</b> debug event with <b>BREAKPOINT</b> as the
-reason.</p>
-<p>If your plug-in needs to show breakpoints in its UI, you can add an 
-<a href="../reference/api/org/eclipse/debug/core/IBreakpointListener.html"><b>IBreakpointListener</b></a>
-to the <a href="../reference/api/org/eclipse/debug/core/IBreakpointManager.html"><b>IBreakpointManager</b></a>.
-The <a href="../reference/api/org/eclipse/debug/core/IBreakpointManager.html"><b>IBreakpointManager</b></a> is the
-central authority over all breakpoints.  Breakpoints are added and removed using the breakpoint manager, which in
-turn informs any listeners about breakpoint activity.  The operation of breakpoints can be enabled or disabled
-using the breakpoint manager.  The breakpoint manager can be obtained from the 
-<a href="../reference/api/org/eclipse/debug/core/DebugPlugin.html"><b>DebugPlugin</b></a>:</p>
-<pre>
-IBreakpointManager mgr = DebugPlugin.getDefault().getBreakpointManager();
-</pre>
-<p>Plug-ins that define their own debug models and launch configurations often
-need to define their own breakpoint types. You can implement breakpoints
-for your particular debug model by defining a class that implements 
-<a href="../reference/api/org/eclipse/debug/core/model/IBreakpoint.html"><b>IBreakpoint</b></a>.</p>
-<p>Breakpoints are implemented using <a href="resAdv_markers.htm">resource markers</a>.
-Recall that resource markers allow you to associate meta information about a 
-resource in the form of named attributes. By implementing a breakpoint 
-using markers, the debug model can make use of all the existing marker function 
-such as persistence, searching, adding, deleting, and displaying in editors.</p>
-<p>Why is it important to know about markers when using breakpoints?&nbsp; When
-you create a breakpoint type, you must also specify an associated marker
-type. Every extension of <a href="../reference/extension-points/org_eclipse_debug_core_breakpoints.html"><b>org.eclipse.debug.core.breakpoints</b></a>
-should be accompanied by an extension of <a href="../reference/extension-points/org_eclipse_core_resources_markers.html"><b>org.eclipse.core.resources.markers</b></a>.&nbsp;
-This is best demonstrated by looking at the extensions defined by the Java
-tooling for Java breakpoints.</p>
-<pre>&lt;extension id=&quot;javaBreakpointMarker&quot; point=&quot;org.eclipse.core.resources.markers&quot;&gt;
-	&lt;super type=&quot;<b>org.eclipse.debug.core.breakpointMarker</b>&quot;/&gt;
-&lt;/extension&gt;
-
-&lt;extension id=&quot;<b>javaExceptionBreakpointMarker</b>&quot; point=&quot;org.eclipse.core.resources.markers&quot;&gt;
-	&lt;super type=&quot;org.eclipse.jdt.debug.javaBreakpointMarker&quot;/&gt;
-	&lt;persistent value=&quot;true&quot;/&gt;
-	&lt;attribute name=&quot;org.eclipse.jdt.debug.core.caught&quot;/&gt;
-	&lt;attribute name=&quot;org.eclipse.jdt.debug.core.uncaught&quot;/&gt;
-	&lt;attribute name=&quot;org.eclipse.jdt.debug.core.checked&quot;/&gt;
-&lt;/extension&gt;</pre>
-<pre>&lt;extension point=&quot;org.eclipse.debug.core.breakpoints&quot;&gt;
-	&lt;breakpoint
-		id=&quot;javaExceptionBreakpoint&quot;
-		markerType=&quot;<b>org.eclipse.jdt.debug.javaExceptionBreakpointMarker</b>&quot;
-		class=&quot;org.eclipse.jdt.internal.debug.core.breakpoints.JavaExceptionBreakpoint&quot;&gt;
-	&lt;/breakpoint&gt;
-&lt;/extension&gt;</pre>
-<p>The debug plug-in defines a special type of marker, <b>org.eclipse.debug.core.breakpointMarker</b>.
-When you define a breakpoint marker for your debugger, you should declare it using this marker as a super 
-type. This allows the debug model to find all possible breakpoints within 
-a source file by searching for subtypes of its marker. In the example 
-above, the <b>javaExceptionBreakpointMarker</b> has a super type, <b>javaBreakpointMarker</b>, 
-whose super type is the <b>breakpointMarker</b>. The <b>javaExceptionBreakpoint</b> 
-(defined in the breakpoint extension) designates the <b>javaExceptionBreakpointMarker</b> 
-as its marker.</p>
-<p>What does all of this mean? When the debug code obtains
-a source code file, it can search for all markers whose super type is 
-<b>org.eclipse.debug.core.breakpointMarker</b>. Having found all of the markers, it can then 
-use the extension registry to map the markers to their associated breakpoint classes.
-In this way, the platform debug code can generically find all breakpoint types that have been set on a
-particular source file. </p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_debug.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_debug.htm
deleted file mode 100644
index e7e30a6..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_debug.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Debugging a program</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Debugging a program</h2>
-<p>When you define a <a href="debug_launch.htm">launch configuration</a> for
-running a program, you can specify which modes (run, debug, profile, etc.) are supported
-by your program.  If you support debug mode, then you need to implement a debug
-model and UI that allow users to interact with your programs while they are under debug.
-The core platform debug plug-in provides support for:</p>
-<ul>
-  <li> a generic debug model</li>
-  <li>debug events and listeners</li>
-  <li>breakpoint management</li>
-  <li>expression management</li>
-</ul>
-<p>The debug UI plug-in provides a framework for showing your debug model in the UI.  It also includes
-utility classes for implementing common UI tasks.</p>
-<p>Since it's difficult to discuss generic debugging in any meaningful detail,
-we'll review the platform debug model and UI classes from the perspective of the
-Java debugger.</p>
-<p><a href="http://www.eclipse.org/articles/Article-Debugger/how-to.html">How to Write an Eclipse Debugger</a> 
-provides a start to finish example for building a debugger using a simple push down automata (PDA)
-assembly language as an example.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_expressions.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_expressions.htm
deleted file mode 100644
index 4ddd69d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_expressions.htm
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Expressions</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Expressions</h3>
-<p>An <b>expression</b> is a snippet of code that can be evaluated to produce a
-value. The context for an expression depends on the particular debug
-model. Some expressions may need to be evaluated at a specific location in
-the program so that its variables can be referenced.
-<a href="../reference/api/org/eclipse/debug/core/model/IExpression.html"><b>IExpression</b></a>
-defines a general interface for debug expressions.</p>
-<p>An expression manager (<a href="../reference/api/org/eclipse/debug/core/IExpressionManager.html"><b>IExpressionManager</b></a>)
-keeps track of all of the expressions in the workspace. It will also fire
-events to interested listeners as expressions are added, removed, or changed.</p>
-<p>Expressions can be used to implement &quot;inspectors,&quot; or &quot;scrapbooks&quot; that let users evaluate
-code snippets. The Java tooling uses expressions to implement the
-expression generated when the user inspects the source code.</p>
-<p>A <b>watch expression</b> is an expression that is repeatedly evaluated as the program executes.
-<a href="../reference/api/org/eclipse/debug/core/model/IWatchExpression.html"><b>IWatchExpression</b></a>
-defines a specialized kind of <a href="../reference/api/org/eclipse/debug/core/model/IExpression.html"><b>IExpression</b></a>
-that updates the value of the expression when supplied with a new debug context.  Watch expressions are used to implement
-&quot;watch lists,&quot; which show changes in the value of an expression as the program executes.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_launch.htm
deleted file mode 100644
index a98ae1c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Launching a program</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Launching a program</h2>
-<p>The platform debug plug-ins allow your plug-in to extend the platform so that your
-partiticular type of program can be launched from the workbench, obtaining input from the user if
-necessary.  A unique type of program that can be launched in the platform is called a
-<b>launch configuration type</b>. The class 
-<a href="../reference/api/org/eclipse/debug/core/ILaunchConfiguration.html"><b>ILaunchConfiguration</b></a>
-is used to describe a type of configuration.  A launch
-configuration keeps a set of named attributes that can be used to store data
-specific for a particular kind of launcher.</p>
-<p>For each launch configuration type, there are different <b>modes</b> in which the 
-configuration can be launched.  The platform defines modes for running, debugging, 
-or profiling a program defined by a particular configuration.  Plug-ins are free to implement 
-any or all of these launch modes for their 
-particular launch configuration, or define new launch modes for any launch
-configuration.</p>
-<p>Plug-ins that contribute additional types of launchers do so by providing an 
-<a href="../reference/api/org/eclipse/debug/core/model/ILaunchConfigurationDelegate.html"><b>ILaunchConfigurationDelegate</b></a>
-(or <a href="../reference/api/org/eclipse/debug/core/model/ILaunchConfigurationDelegate2.html"><b>ILaunchConfigurationDelegate2</b></a>)
-that knows how to launch a program given the expected type and mode for launch configuration.&nbsp; Once the program
-is launched, an <a href="../reference/api/org/eclipse/debug/core/ILaunch.html"><b>ILaunch</b>
-</a>object is used to represent the launched session.&nbsp; This object can be
-queried for information such as running processes, debug session information,
-and source code location.&nbsp; A launch knows the configuration that was used to create
-it.&nbsp; </p>
-<p><img alt="" border="0" src="images/launch.jpg" > </p>
-<p>Users interact with a launch
-configuration dialog to set up the parameters for different types of
-launches. These configurations can be
-stored in a file to be shared with other users or stored locally in the workspace.</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_adding.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_adding.htm
deleted file mode 100644
index 3de178d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_adding.htm
+++ /dev/null

@@ -1,95 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Adding launchers to the platform</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Adding launchers to the platform</h3>
-<p>Your plug-in can add launch configuration types to the platform using the <a href="../reference/extension-points/org_eclipse_debug_core_launchConfigurationTypes.html"><b>org.eclipse.debug.core.launchConfigurationTypes</b></a>
-extension point.&nbsp; This extension point allows you to declare a
-configuration type using a unique id.&nbsp; You must provide a corresponding
-implementation of <a href="../reference/api/org/eclipse/debug/core/model/ILaunchConfigurationDelegate.html"><b>ILaunchConfigurationDelegate</b></a>.
-The delegate is responsible for launching its launch configuration in a specified mode.  
-Optionally, you can implement <a href="../reference/api/org/eclipse/debug/core/model/ILaunchConfigurationDelegate2.html"><b>ILaunchConfigurationDelegate2</b></a>,
-which enhances the delegate interface to allow your delegate to abort a launch, build relevant projects in the workspace
-before a launch, and control the creation of the launch object that is used in a launch.
-</p>
-<p>
-In addition to defining the delegate, you can specify which launch modes are supported
-by your delegate, and a name that should be used when showing launchers
-of this type to the user.</p>
-<p>The following markup shows how the Java tools declare a Java launch
-configuration for launching local Java programs:</p>
-<pre>&lt;extension point = &quot;org.eclipse.debug.core.launchConfigurationTypes&quot;&gt;
-   &lt;launchConfigurationType
-   	   id=&quot;org.eclipse.jdt.launching.localJavaApplication&quot;
-	   <b>name=&quot;%localJavaApplication&quot;
-	   delegate=&quot;org.eclipse.jdt.internal.launching.JavaLocalApplicationLaunchConfigurationDelegate&quot;
-	   modes= &quot;run, debug&quot;</b>
-	   sourceLocatorId=&quot;org.eclipse.jdt.launching.sourceLocator.JavaSourceLookupDirector&quot;
-       sourcePathComputerId=&quot;org.eclipse.jdt.launching.sourceLookup.javaSourcePathComputer&quot;&gt;
-   &lt;/launchConfigurationType&gt;
-&lt;/extension&gt;</pre>
-<p>This extension defines a launch configuration delegate that can be used to run or debug programs that
-are launched using the local Java launch configuration.</p>
-<h4>Defining new launch modes</h4>
-<p>We mentioned previously that the platform defines launch modes for running, debugging, or profiling
-a program.  These modes are defined using the <a href="../reference/extension-points/org_eclipse_debug_core_launchModes.html"><b>org.eclipse.debug.core.launchModes</b></a>
-extension point. This extension point allows you to declare a launch mode by defining its string mode
-name and the label that should be shown to the user to describe the mode.  The following markup shows 
-the definition of the platform's three standard launch modes:</p>
-<pre>
-&lt;extension point="org.eclipse.debug.core.launchModes"&gt;
-	&lt;launchMode
-		label="%run"
-		mode="run"&gt;
-	&lt;/launchMode&gt;
-	&lt;launchMode
-		label="%debug"
-		mode="debug"&gt;
-	&lt;/launchMode&gt;
-	&lt;launchMode
-		label="%profile"
-		mode="profile"&gt;
-	&lt;/launchMode&gt;
-&lt;/extension&gt;
-</pre>
-<p>Note that the mode is not associated with any particular launch configuration type.  As shown earlier, that association
-occurs when a launch delegate is specified for a configuration type.  </p>
-<h4>Defining launch delegates</h4>
-<p>Since launch modes can be specified independently of launch configuration types, it's possible that new modes
-are defined that are not implemented by the original delegate for a launch configuration.  In this case, a plug-in
-may define a launch delegate that implements a particular mode for a particular launch configuration type.
-This can be done using the <a href="../reference/extension-points/org_eclipse_debug_core_launchDelegates.html"><b>org.eclipse.debug.core.launchDelegates</b></a>
-extension point. This extension point allows you to define a launch delegate that implements the specified modes
-for a given configuration type.  The following markup shows how you could define a delegate for profiling
-a local Java application:</p>
-<pre>
-&lt;extension point="org.eclipse.debug.core.launchDelegates"&gt;
-  &lt;launchDelegate
-   id=&quot;com.example.MyJavaProfileDelegate&quot;
-   delegate=&quot;com.example.MyJavaProfileDelegate&quot;
-   type=&quot;org.eclipse.jdt.launching.localJavaApplication&quot;
-   modes=&quot;profile&quot;&gt;
-  &lt;/launchDelegate&gt;
- &lt;/extension&gt;
-</pre>
-<p>The specification of the delegate is similar to the way it is done when defining a launch configuration
-type, except that in this case the type of launch configuration is specified along with the supported
-modes.  As seen previously, the delegate must implement <a href="../reference/api/org/eclipse/debug/core/model/ILaunchConfigurationDelegate.html"><b>ILaunchConfigurationDelegate</b></a>,
-and can optionally implement <a href="../reference/api/org/eclipse/debug/core/model/ILaunchConfigurationDelegate2.html"><b>ILaunchConfigurationDelegate2</b></a> for
-more control over the launch sequence.</p>
-<h4>Other references</h4>
-<p><a href="http://www.eclipse.org/articles/Article-Launch-Framework/launch.html">We Have Lift-off: The Launching Framework in Eclipse</a> 
-provides a start to finish example for defining your own launch type.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_comparators.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_comparators.htm
deleted file mode 100644
index 8ec329c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_comparators.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Comparing launch configurations</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h4>Comparing launch configurations</h4>
-<p>We've seen how a plug-in can use named attributes and values to store important data with a
-launch configuration. Since the interpretation of a plug-in's attributes are not known by the platform, 
-an extension point is provided that allows you to supply a comparator for a specific attribute.
-This comparator is used to determine whether attributes of the specified name are
-equal. In many cases, the simple string compare provided by
-java.lang.Object.equals(Object) is suitable for comparing attributes. This
-technique will be used if no comparator has been provided. However, some attribute values
-may require special handling, such as stripping white space values from text
-before comparing for equality. </p>
-<p>Comparators are contributed using the <a href="../reference/extension-points/org_eclipse_debug_core_launchConfigurationComparators.html"><b>org.eclipse.debug.core.launchConfigurationComparators</b></a>
-extension point.&nbsp; </p>
-<p>The Java tools supply launch configuration comparators for comparing program
-source paths and class paths.</p>
-<pre>&lt;extension point = &quot;org.eclipse.debug.core.launchConfigurationComparators&quot;&gt;
-	&lt;launchConfigurationComparator
-		id = &quot;org.eclipse.jdt.launching.classpathComparator&quot;
-		class = &quot;org.eclipse.jdt.internal.launching.RuntimeClasspathEntryListComparator&quot;
-		attribute = &quot;org.eclipse.jdt.launching.CLASSPATH&quot;/&gt;
-	&lt;launchConfigurationComparator
-		id = &quot;org.eclipse.jdt.launching.sourcepathComparator&quot;
-		class = &quot;org.eclipse.jdt.internal.launching.RuntimeClasspathEntryListComparator&quot;
-		attribute = &quot;org.eclipse.jdt.launching.SOURCE_PATH&quot;/&gt;		
-&lt;/extension&gt;</pre>
-<p>Comparators must implement the interface <b>java.util.Comparator</b>.</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_java.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_java.htm
deleted file mode 100644
index 26b3eac..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_java.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Launching Java applications</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h4>Launching Java applications</h4>
-<p>
-In <a href="debug_launch_processfactories.htm">Process factories</a>, we saw how a system process is used to invoke
-a program and how wrapping it with an <a href="../reference/api/org/eclipse/debug/core/model/IProcess.html"><b>IProcess</b></a>
-allows clients to access launch-related information about the process.  These techniques are general and can be used to launch
-any external program from the platform.
-</p>
-<p>Additional classes provided in the <b>org.eclipse.jdt.debug</b> plug-in provide support for launching a specific JRE with a specified
-classpath, arguments, VM arguments, and a main type.  See the following references for more specific information about launching
-a Java application:</p>
-<ul>
-<li><a href="http://www.eclipse.org/articles/Article-Java-launch/launching-java.html">Launching Java Applications Programmatically</a> </li>
-<li><a href="http://www.eclipse.org/articles/Article-Launch-Framework/launch.html">We Have Lift-off: The Launching Framework in Eclipse</a></li>
-</ul>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_processfactories.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_processfactories.htm
deleted file mode 100644
index 06e3cbc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_processfactories.htm
+++ /dev/null

@@ -1,70 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Process factories</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h4>Process factories</h4>
-<p>When a launch configuration launches its program, it is responsible for invoking the executable
-program in the requested mode.  The implementation for a launch will depend on the specifics of
-each launch configuration, but most plug-ins will build a command line and call a runtime exec to start
-the program.  The <a href="../reference/api/org/eclipse/debug/core/DebugPlugin.html"><b>DebugPlugin</b></a>
-class implements a convenience method for invoking a runtime exec and handling the possible exceptions.
-Clients can specify the command line and working directory for the exec.
-</p>
-<pre>
-Process p = DebugPlugin.exec(cmdLine, workingDirectory);
-</pre>
-<p>Once the <b>java.lang.Process</b> for the executing program has been created, it needs to be managed by the
-debug plug-in.  For starters, the process needs to be associated with the
-<a href="../reference/api/org/eclipse/debug/core/ILaunch.html"><b>ILaunch</b></a>
-that represents the launched program.  The debug plug-in defines a wrapper for a system process,
-<a href="../reference/api/org/eclipse/debug/core/model/IProcess.html"><b>IProcess</b></a>,
-that allows clients to access the associated <a href="../reference/api/org/eclipse/debug/core/ILaunch.html"><b>ILaunch</b></a>
-and assign their own named attributes to the process.  In addition, 
-<a href="../reference/api/org/eclipse/debug/core/model/IProcess.html"><b>IProcess</b></a>,
-defines a label for the process and associates an <a href="../reference/api/org/eclipse/debug/core/model/IStreamsProxy.html"><b>IStreamsProxy</b></a>
-with the process that gives clients access to the input, output, and error streams of the system process.  This process wrapper
-can also be created using a utility method in
-<a href="../reference/api/org/eclipse/debug/core/DebugPlugin.html"><b>DebugPlugin</b></a>.
-</p>
-<pre>
-IProcess process= DebugPlugin.newProcess(launch, p, "My Process);
-</pre>
-<p>
-A map of named attributes can also be supplied.
-</p>
-<p>
-Many plug-ins can simply rely on the utility methods in <a href="../reference/api/org/eclipse/debug/core/DebugPlugin.html"><b>DebugPlugin</b></a>
-for launching the system process and wrapping it in an <a href="../reference/api/org/eclipse/debug/core/model/IProcess.html"><b>IProcess</b></a>.
-For those plug-ins that need more control in the creation of the wrapper, a <b>process factory</b> can be associated with a launch
-configuration.  The process factory is used to create an <a href="../reference/api/org/eclipse/debug/core/model/IProcess.html"><b>IProcess</b></a> 
-that meets the special needs of the plug-in.   The process factory is referenced by id, and should be stored in the
-<b>DebugPlugin.ATTR_PROCESS_FACTORY_ID</b> attribute of the launch configuration.</p>
-<p>The association between the process factory id and the class that implements it is made using the
-<a href="../reference/extension-points/org_eclipse_debug_core_processFactories.html"><b>org.eclipse.debug.core.processFactories</b></a>
-extension point.</p>
-<p>The following example shows how the Ant plug-in sets up a process factory for its launches:</p>
-<pre>
-&lt;extension point=&quot;org.eclipse.debug.core.processFactories&quot;&gt;
-	&lt;processFactory
-		class=&quot;org.eclipse.ant.internal.ui.launchConfigurations.RemoteAntProcessFactory&quot;
-		id=&quot;org.eclipse.ant.ui.remoteAntProcessFactory&quot;&gt;
-	&lt;/processFactory&gt;
-&lt;/extension&gt;
-</pre>
-<p>
-It is the responsibility of the registering plug-in to store the process factory id in the proper launch configuration attribute.
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_sourcelocators.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_sourcelocators.htm
deleted file mode 100644
index b0a0b8e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_sourcelocators.htm
+++ /dev/null

@@ -1,103 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Obtaining a program's source code</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h4>Obtaining a program's source code</h4>
-<p>For certain kinds of launch modes, it may be important to obtain the source code that corresponds
-with the current execution point in the code.  This is typically important when debugging or profiling
-a program.  Several different extension points are provided by the debug plug-in that allow plug-ins to
-register classes that can assist with locating source code.</p>
-<h5>Source locators</h5>
-<p>
-<a href="../reference/api/org/eclipse/debug/core/model/ISourceLocator.html"><b>ISourceLocator</b></a>
-and <a href="../reference/api/org/eclipse/debug/core/model/IPersistableSourceLocator.html"><b>IPersistableSourceLocator</b></a>
-define interfaces for mapping from an executing program back to the source
-code. </p>
-<p>Source locators are typically implemented to work with a corresponding launch
-configuration and launch configuration delegate.  A source locator id may be specified when a launch configuration
-type is defined, or it may be associated programmatically with a launch configuration using the 
-<b>ILaunchConfiguration.ATTR_SOURCE_LOCATOR_ID</b> attribute.  In either case, at some point the id
-of a source locator for a configuration must be resolved to the class that actually implements 
-<a href="../reference/api/org/eclipse/debug/core/model/IPersistableSourceLocator.html"><b>IPersistableSourceLocator</b></a>.
-The association between a source locator id and its class is established using the 
-<a href="../reference/extension-points/org_eclipse_debug_core_sourceLocators.html"><b>org.eclipse.debug.core.sourceLocators</b></a>
-extension point.</p>
-<p>The following markup is from the Java tooling:</p>
-<pre>&lt;extension point = &quot;org.eclipse.debug.core.sourceLocators&quot;&gt;
-	&lt;sourceLocator
-		id = &quot;org.eclipse.jdt.debug.ui.javaSourceLocator&quot;
-	   	class=&quot;org.eclipse.jdt.debug.ui.JavaUISourceLocator&quot;
-	   	name=&quot;%javaSourceLocator&quot;/&gt;
-&lt;/extension&gt;</pre>
-<p>Since launch configurations can be persisted, source locator ids may will be stored
-with the launch configuration.  When it's time to instantiate a source locator, the
-debug plug-in looks up the source locator id attribute and instantiates the class associated with
-that id.</p>
-<p>The implementation for source lookup necessarily depends on the type of program being launched.  However, the platform
-defines an abstract implementation for a source locator that looks up source files on a given path that includes
-directories, zip files, jar files, and the like.  To take advantage of this implementation, your plug-in can extend
-<a href="../reference/api/org/eclipse/debug/core/sourcelookup/AbstractSourceLookupDirector.html"><b>AbstractSourceLookupDirector</b></a>.
-All that is needed from the specific implementation is the ability to provide an appropriate
-<a href="../reference/api/org/eclipse/debug/core/sourcelookup/ISourceLookupParticipant.html"><b>ISourceLookupParticipant</b></a>, which can
-map a stack frame to a file name. See the extenders of <a href="../reference/api/org/eclipse/debug/core/sourcelookup/AbstractSourceLookupDirector.html"><b>AbstractSourceLookupDirector</b></a>.
-for examples.</p>
-<h5>Source path computers</h5>
-<p>The <a href="../reference/api/org/eclipse/debug/core/sourcelookup/AbstractSourceLookupDirector.html"><b>AbstractSourceLookupDirector</b></a>
-searches for source files according to a particular source code lookup path.  This path is expressed as an array of
-<a href="../reference/api/org/eclipse/debug/core/sourcelookup/ISourceContainer.html"><b>ISourceContainer</b></a>.  The source containers
-that should be searched for source are typically computed according to the particulars of the source configuration that is being
-launched.  <a href="../reference/api/org/eclipse/debug/core/sourcelookup/ISourcePathComputer.html"><b>ISourcePathComputer</b></a>
-defines the interface for an object that computes the appropriate source path for a launch configuration.  A source path computer,
-much like a source locator, is specified by id, and can be specified in the extension definition for a launch configuration type, or 
-associated programmatically by setting the <b>ISourceLocator.ATTR_SOURCE_PATH_COMPUTER_ID</b> attribute for the launch configuration.
-The id for a source path computer is associated with its implementing class in the
-<a href="../reference/extension-points/org_eclipse_debug_core_sourcePathComputers.html"><b>org.eclipse.debug.core.sourcePathComputers</b></a>
-extension point.  The following markup shows the definition used by JDT for its Java source path computer:
-</p>
-<pre>
-&lt;extension point=&quot;org.eclipse.debug.core.sourcePathComputers&quot;&gt;
-	&lt;sourcePathComputer
-		id=&quot;org.eclipse.jdt.launching.sourceLookup.javaSourcePathComputer&quot;
-		class=&quot;org.eclipse.jdt.launching.sourcelookup.containers.JavaSourcePathComputer&quot;&gt;
- 	&lt;/sourcePathComputer&gt;
- 	...
-</pre>
-<p>
-The source path computer is responsible for computing an array of <a href="../reference/api/org/eclipse/debug/core/sourcelookup/ISourceContainer.html"><b>ISourceContainer</b></a>
-that represents the source lookup path.  For example, the Java source path computer considers the classpath when building the
-path. 
-</p>
-<h5>Source container types</h5>
-<p>The containers specified as part of a source lookup path must implement <a href="../reference/api/org/eclipse/debug/core/sourcelookup/ISourceContainer.html"><b>ISourceContainer</b></a>,
-which can search the container represented for a named source element.  Different kinds of source containers may be needed to represent the
-different kinds of places source code is stored.  For example, the JDT defines source containers that represent source in a Java project,
-source on the classpath, and source in a package fragment.  The source containers used for a launch configuration may be stored by id in
-the launch configuration.  Since launch configurations can be persisted, there must be a way to associate the the id of a source container
-with its implementation class.  This is done using the 
-<a href="../reference/extension-points/org_eclipse_debug_core_sourceContainerTypes.html"><b>org.eclipse.debug.core.sourceContainerTypes</b></a>
-extension point. The following example comes from the JDT:
-</p>
-<pre>
-&lt;extension point=&quot;org.eclipse.debug.core.sourceContainerTypes&quot;&gt;
-	&lt;sourceContainerType
-		id=&quot;org.eclipse.jdt.launching.sourceContainer.javaProject&quot;
-		name=&quot;%javaProjectSourceContainerType.name&quot;
-		description=&quot;%javaProjectSourceContainerType.description&quot;
-		class=&quot;org.eclipse.jdt.internal.launching.JavaProjectSourceContainerTypeDelegate&quot;&gt;
-	&lt;/sourceContainerType&gt; 
-	...
-</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_status.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_status.htm
deleted file mode 100644
index 8938b91..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_status.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Handling errors from a launched program</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Handling errors from a launched program</h3>
-<p>If you have defined your own type of launch configuration, it's likely that
-you will want to handle errors or other status information that arises during the
-running of the program. For example, you may want to prompt or alert the
-user when certain types of errors occur during a launch, or provide information
-messages for certain status changes in the program. Since it's good
-practice to separate UI handling from core function, you do not want to have
-direct references from your launch delegate to status handling classes.</p>
-<p>This problem is addressed by the 
-<a href="../reference/extension-points/org_eclipse_debug_core_statusHandlers.html"><b>org.eclipse.debug.core.statusHandlers</b></a>
-extension point. It allows you to associate a status handler with a
-specific status code. Using this extension point, you can define all of
-the possible status and error codes in your launch delegate and core classes,
-while registering unique handlers for the different status codes from another
-plug-in.</p>
-<p>The extension point does not designate any association between a status
-handler and a launch configuration. It is up to the implementation of the
-launch delegate to detect errors, find the appropriate status handler, and
-invoke it. The extension merely provides a registry so that the status
-handlers can be found for particular status codes. 
-<a href="../reference/api/org/eclipse/debug/core/DebugPlugin.html"><b>DebugPlugin</b></a>
-provides a utility method for obtaining a specific status handler.</p>
-<pre>
-IStatusHandler handler = DebugPlugin.getDefault().getStatusHandler(status);</pre>
-<p>Status handlers should implement <a href="../reference/api/org/eclipse/debug/core/IStatusHandler.html"><b>IStatusHandler</b></a>.
-The status handling class is specified in the extension definition, along with
-its associated status code and the plug-in that is expected to generate the
-status codes.</p>
-<p>The following markup shows how the Java tools declare status handlers:</p>
-<pre>&lt;extension point = &quot;org.eclipse.debug.core.statusHandlers&quot;&gt;
-	&lt;statusHandler
-		id=&quot;org.eclipse.jdt.debug.ui.statusHandler.vmConnectTimeout&quot;
-		class=&quot;org.eclipse.jdt.internal.debug.ui.launcher.VMConnectTimeoutStatusHandler&quot;
-		plugin =&quot;org.eclipse.jdt.launching&quot;
-		code=&quot;117&quot;&gt;
-	&lt;/statusHandler&gt;	
-	...
-&lt;/extension&gt;</pre>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_ui.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_ui.htm
deleted file mode 100644
index dc439a6..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_ui.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Launch configuration dialog</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Launch configuration dialog</h3>
-<p>Launch configurations can most easily be visualized by looking at their
-corresponding UI. Users interact with a launch configuration dialog to
-create instances of the different types of launch configurations that have been
-contributed by plug-ins. Each type of launch configuration defines a group
-of tabs that collect and display information about the configuration. The
-tab group for running a local Java application is shown below.</p>
-<p><img src="images/lcd.png" alt="Launch configuration dialog with contributed tab groups" border="0"></p>
-<p>The tabs are contributed using the <a href="../reference/extension-points/org_eclipse_debug_ui_launchConfigurationTabGroups.html"><b>org.eclipse.debug.ui.launchConfigurationTabGroups</b></a>
-extension point. In this extension, the id of a configuration type (defined using
-<a href="../reference/extension-points/org_eclipse_debug_core_launchConfigurationTypes.html"><b>org.eclipse.debug.core.launchConfigurationTypes</b></a>)
-is associated with the class that implements <a href="../reference/api/org/eclipse/debug/ui/ILaunchConfigurationTabGroup.html"><b>ILaunchConfigurationTabGroup</b></a>.</p>
-<p>It's possible that a some tab groups are only appropriate when launching the configuration in a particular mode.  If this is the case, then
-one or more <b>mode</b> elements can be specified along with the class.  For each mode, the tab group can be given a unique description. 
-If no mode is specified, then the tab group will be shown on all modes that
-do not have a mode-specific tab group contribution.  The Java application tab group is defined for run and debug modes:</p>
-<pre>
-   &lt;extension
-         point="org.eclipse.debug.ui.launchConfigurationTabGroups"&gt;
-      &lt;launchConfigurationTabGroup
-            type="org.eclipse.jdt.launching.localJavaApplication"
-            helpContextId="org.eclipse.jdt.debug.ui.launchConfigHelpContext.local_java_application"
-            class="org.eclipse.jdt.internal.debug.ui.launcher.LocalJavaApplicationTabGroup"
-            id="org.eclipse.jdt.debug.ui.launchConfigurationTabGroup.localJavaApplication"
-            bannerImage="icons/full/wizban/java_app_wiz.png"&gt;
-            &lt;launchMode 
-                  mode="debug"
-                  perspective="org.eclipse.debug.ui.DebugPerspective"
-                  description="%localJavaApplicationTabGroupDescription.debug"&gt;
-            &lt;/launchMode&gt;
-            &lt;launchMode
-                  mode="run"
-                  description="%localJavaApplicationTabGroupDescription.run"&gt;
-            &lt;/launchMode&gt;
-      &lt;/launchConfigurationTabGroup&gt;
-      ...
-</pre>
-<p>Note that a perspective may also be specified with a mode.  This will cause the platform to switch to the specified perspective when
-the program is launched in that mode.</p>
-<p>Your tab group class is responsible for creating the necessary tabs and
-displaying and saving the relevant data from the launch configuration
-attributes. A tab that is common to all configurations, <a href="../reference/api/org/eclipse/debug/ui/CommonTab.html"><b>CommonTab</b></a>,
-is already implemented and can be created by any configuration. This tab
-manages the saving of the launch configuration as well as collecting common
-preferences.</p>
-<p><img src="images/common_tab.png" alt="Launch configuration tabs" border="0"></p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_uiimages.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_uiimages.htm
deleted file mode 100644
index eb3fd6f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_uiimages.htm
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Launch configuration type images</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Launch configuration type images</h3>
-<p>The image that is shown for a launch configuration type in the launch dialog
-is contributed using the <a href="../reference/extension-points/org_eclipse_debug_ui_launchConfigurationTypeImages.html"><b>org.eclipse.debug.ui.launchConfigurationTypeImages</b></a>
-extension point.&nbsp; This extension associates an image file with the id of a
-configuration type.</p>
-<p><img src="images/launchImage.png" alt="Launch configuration images" border="0"></p>
-<p>The markup for the Java application image is as follows:</p>
-<pre>
-&lt;extension
-	point="org.eclipse.debug.ui.launchConfigurationTypeImages"&gt;
- 		&lt;launchConfigurationTypeImage
-			icon="icons/full/etool16/java_app.png"
-			configTypeID="org.eclipse.jdt.launching.localJavaApplication"
-			id="org.eclipse.jdt.debug.ui.launchConfigurationTypeImage.localJavaApplication"&gt;
-		&lt;/launchConfigurationTypeImage&gt;
-		...
-</pre>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_uishortcuts.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_uishortcuts.htm
deleted file mode 100644
index ecd65af..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_uishortcuts.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Launch shortcuts</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Launch shortcuts</h3>
-<p>Once a launch configuration has been defined using the dialog, it can be
-shown directly in the appropriate menu, rather than having to open the launch configuration
-dialog again.  When a launch configuration is shown directly in a menu, we refer to it as a
-<b>launch shortcut</b>.  The <a href="../reference/extension-points/org_eclipse_debug_ui_launchShortcuts.html"><b>org.eclipse.debug.ui.launchShortcuts</b></a>
-extension point is used to register these shortcuts.  In the extension
-definition, you can specify in which modes the shortcuts are shown. For each shortcut, you must specify
-an implementation of <a href="../reference/api/org/eclipse/debug/ui/ILaunchShortcut.html"><b>ILaunchShortcut</b></a>.
-This class is used to launch a program given a particular selection in a view or
-editor.</p>
-<p>
-You may also specify when the shortcut should be shown.  The <b>contexttualLaunch</b> element allows you to describe
-applicable modes and enabling conditions for the shortcut.  This is best demonstrated by example.  The following
-markup registers shortcuts for launching a Java application:</p>
-<pre>
-  &lt;extension
-         point="org.eclipse.debug.ui.launchShortcuts"&gt;
-      &lt;shortcut
-            label="%JavaApplicationShortcut.label"
-            icon="icons/full/etool16/java_app.png"
-            helpContextId="org.eclipse.jdt.debug.ui.shortcut_local_java_application"
-            modes="run, debug"
-            class="org.eclipse.jdt.internal.debug.ui.launcher.JavaApplicationLaunchShortcut"
-            id="org.eclipse.jdt.debug.ui.localJavaShortcut"&gt;
-         &lt;contextualLaunch&gt;
-           &lt;enablement&gt;
-             &lt;with variable="selection"&gt;
-               &lt;count value="1"/&gt;
-               &lt;iterate&gt;
-                 &lt;or&gt;
-                   &lt;test property="org.eclipse.debug.ui.matchesPattern" value="*.java"/&gt;
-                   &lt;test property="org.eclipse.debug.ui.matchesPattern" value="*.class"/&gt;
-                   &lt;instanceof value="org.eclipse.jdt.core.IJavaElement"/&gt;
-                 &lt;/or&gt;
-                 &lt;test property="org.eclipse.jdt.debug.ui.hasMainType"/&gt;
-               &lt;/iterate&gt;
-             &lt;/with&gt;
-           &lt;/enablement&gt;
-  		 &lt;/contextualLaunch&gt;
-         ...
-      &lt;/shortcut&gt;
-      ...
-</pre>
-<p>See <a href="workbench_actionfilters.htm">Boolean expressions and action filters</a> for an explanation of the XML syntax for 
-enabling conditions.  The complete syntax is described in the documentation for 
-<a href="../reference/extension-points/org_eclipse_debug_ui_launchShortcuts.html"><b>org.eclipse.debug.ui.launchShortcuts</b></a>.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_model.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_model.htm
deleted file mode 100644
index 29ac4cb..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_model.htm
+++ /dev/null

@@ -1,95 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Platform debug model</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Platform debug model</h3>
-<p>The platform debug model defines generic debug interfaces that are intended 
-  to be implemented and extended in concrete, language-specific implementations.</p>
-<h4>Artifacts</h4>
-<p>The model includes classes that represent different artifacts in a program
-under debug.&nbsp; All of the artifacts implement <a href="../reference/api/org/eclipse/debug/core/model/IDebugElement.html"><b>IDebugElement</b></a>
-in addition to their own interfaces.&nbsp; The model includes definitions for
-the following artifacts:</p>
-<ul>
-  <li>Debug targets (<a href="../reference/api/org/eclipse/debug/core/model/IDebugTarget.html"><b>IDebugTarget</b></a>)
-    - a debuggable execution context, such as a process or virtual machine</li>
-  <li>Expressions (<a href="../reference/api/org/eclipse/debug/core/model/IExpression.html"><b>IExpression</b></a>)
-    - a snippet of code that can be evaluated to produce a value</li>
-  <li>Memory blocks (<a href="../reference/api/org/eclipse/debug/core/model/IMemoryBlock.html"><b>IMemoryBlock</b></a>)
-    - a contiguous segment of memory in an execution context</li>
-  <li>Registers (<a href="../reference/api/org/eclipse/debug/core/model/IRegister.html"><b>IRegister</b></a>)
-    - a named variable in a register group</li>
-  <li>Register groups (<a href="../reference/api/org/eclipse/debug/core/model/IRegisterGroup.html"><b>IRegisterGroup</b></a>)
-    - a group of registers assigned to a stack frame</li>
-  <li>Stack frames (<a href="../reference/api/org/eclipse/debug/core/model/IStackFrame.html"><b>IStackFrame</b></a>)
-    - an execution context in a suspended thread containing local variables and
-    arguments</li>
-  <li>Threads (<a href="../reference/api/org/eclipse/debug/core/model/IThread.html"><b>IThread</b></a>)
-    - a sequential flow of execution in a debug target containing stack frames</li>
-  <li>Values (<a href="../reference/api/org/eclipse/debug/core/model/IValue.html"><b>IValue</b></a>)
-    - the value of a variable</li>
-  <li>Variables (<a href="../reference/api/org/eclipse/debug/core/model/IVariable.html"><b>IVariable</b></a>)
-    - a visible data structure in a stack frame or value</li>
-  <li>Watch expressions (<a href="../reference/api/org/eclipse/debug/core/model/IWatchExpression.html"><b>IWatchExpression</b></a>)
-    - an expression that updates its value when provided with a particular context</li>
-</ul>
-<p>Plug-ins that implement language-specific debuggers typically extend these
-interfaces to include language-specific behavior.&nbsp; All debug elements can
-return the id of the plug-in that originated them.&nbsp; This is important for
-registering other classes that are associated with a debug model, such as UI
-classes.</p>
-<h4>Actions</h4>
-<p>The model also includes interfaces that define a set of debug actions that
-are common behaviors among debug artifacts.&nbsp; These interfaces are
-implemented by debug elements where appropriate.&nbsp; They include the
-following actions:</p>
-<ul>
-  <li>Disconnect (<a href="../reference/api/org/eclipse/debug/core/model/IDisconnect.html"><b>IDisconnect</b></a>) 
-    - the ability to end a debug session with a target program and allow the target 
-    to continue running</li>
-  <li>Step (<a href="../reference/api/org/eclipse/debug/core/model/IStep.html"><b>IStep</b></a>) 
-    - the ability to step into, over, and return from the current execution point</li>
-  <li>Step filters (<a href="../reference/api/org/eclipse/debug/core/model/IStepFilters.html"><b>IStepFilters</b></a>) 
-    - the ability to enable or disable filtering of step operations so that a debug target can apply filters to
-    steps when appropriate</li>
-  <li>Suspend and resume (<a href="../reference/api/org/eclipse/debug/core/model/ISuspendResume.html"><b>ISuspendResume</b></a>) 
-    - the ability to suspend and resume execution</li>
-  <li>Terminate (<a href="../reference/api/org/eclipse/debug/core/model/ITerminate.html"><b>ITerminate</b></a>) 
-    - the ability to terminate an execution context</li>
-  <li>Modify a value (<a href="../reference/api/org/eclipse/debug/core/model/IValueModification.html"><b>IValueModification</b></a>) 
-    - the ability to modify the value of a variable</li>
-</ul>
-<p>If you look at the definitions for the platform debug elements, you will see
-that different elements implement different debug actions.&nbsp; Standard
-interfaces for the elements and their behaviors allow the platform to provide
-abstract implementations of utility classes and UI support that can be extended
-for concrete implementations of debuggers.</p>
-<h4>Events</h4>
-<p>Debug events (<a href="../reference/api/org/eclipse/debug/core/DebugEvent.html"><b>DebugEvent</b></a>)
-are used to describe events that occur as a program is being debugged.&nbsp;
-Debug events include the debug element that is associated with the event.&nbsp;
-Each kind of debug element has a specific set of events that it supports as
-documented in <a href="../reference/api/org/eclipse/debug/core/DebugEvent.html"><b>DebugEvent</b></a>.
-Debugger implementations can add application specific debug events using a designation of
-<b>DebugEvent.MODEL_SPECIFIC</b> as the kind of event.  A client data field can be used in this case
-to add model-specific information about the event.</p>
-<p>Debugger UI classes typically listen to specific events for elements in order
-display information about changes that occur in the elements.&nbsp; Debug events
-arrive in groups called <b>debug event sets</b>.&nbsp; Events that occur at the
-same point of execution in a program arrive in the same set.&nbsp; Clients
-should implement an <a href="../reference/api/org/eclipse/debug/core/IDebugEventSetListener.html"><b>IDebugEventSetListener</b></a>
-and register the listener with the <a href="../reference/api/org/eclipse/debug/core/package-summary.html"><b>org.eclipse.debug.core</b></a>
-plug-in in order to receive debug events.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_presentation.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_presentation.htm
deleted file mode 100644
index bcd7433..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_presentation.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Debug model presentation</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Debug model presentation</h3>
-<p>Since there is a generic, uniform model for debug elements in the platform,
-it's possible to provide a starting point for implementing a debugger UI.
-The heart of the debugger UI support is the <b>debug model
-presentation</b> (<a href="../reference/api/org/eclipse/debug/ui/IDebugModelPresentation.html"><b>IDebugModelPresentation</b></a>).
-The debug model presentation is responsible for providing labels, images, and
-editors associated with specific debug elements.</p>
-<p>Plug-ins that define their own debug model typically provide a debug model
-presentation for displaying debug elements in the model. This is
-accomplished using the 
-<a href="../reference/extension-points/org_eclipse_debug_ui_debugModelPresentations.html"><b>org.eclipse.debug.ui.debugModelPresentations</b></a>
-extension point. This extension point allows an implementation of <a href="../reference/api/org/eclipse/debug/ui/IDebugModelPresentation.html"><b>IDebugModelPresentation</b></a>
-to be associated with the identifier of a particular debug model.</p>
-<p>Recall that <a href="debug_model.htm">debug model elements</a> know the id of
-their originating debug model. This means that given any debug element,
-the debug platform can obtain the id of the debug model and then query the
-extension registry for any corresponding debug model presentations.</p>
-<p>The markup for adding a debug model presentation looks like this:</p>
-<pre>&lt;extension point = &quot;org.eclipse.debug.ui.debugModelPresentations&quot;&gt; 
-         &lt;debugModelPresentation
-             class = &quot;org.eclipse.jdt.internal.debug.ui.JDIModelPresentation&quot;
-             id = &quot;org.eclipse.jdt.debug&quot;
-             detailsViewerConfiguration = &quot;org.eclipse.jdt.internal.debug.ui.display.DetailsViewerConfiguration&quot;&gt;
-          &lt;/debugModelPresentation&gt; 
-&lt;/extension&gt;</pre>
-<p>An optional <b>detailsViewerConfiguration</b> can be specified in addition to
-the debug model presentation. The details viewer must extend the JFace 
-<a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html"><b>SourceViewerConfiguration</b></a>
-class. The meaning of &quot;details&quot; is interpreted by the debug
-model. The details are computed by the debug model presentation and passed
-to the details viewer. For example, the Java debugger uses the details
-viewer to show code assist in the variables view when expressions are evaluated.</p>
-<p>Implementors of <a href="../reference/api/org/eclipse/debug/ui/IDebugModelPresentation.html"><b>IDebugModelPresentation</b></a> may
-also implement <a href="../reference/api/org/eclipse/debug/ui/IDebugEditorPresentation.html"><b>IDebugEditorPresentation</b></a> when
-more control is needed over the editor that is displaying source code for a stack frame.  Implementors may control the
-editor's position or the annotations in the source.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_ui.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_ui.htm
deleted file mode 100644
index eec417c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_ui.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Debug UI utility classes</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Debug UI utility classes</h3>
-<p>In addition to defining a general framework for showing a debug UI, the debug UI plug-in 
-includes classes that implement useful utility methods for implementing a debugger UI.</p>
-<p><a href="../reference/api/org/eclipse/debug/ui/DebugUITools.html"><b>DebugUITools</b></a>
-groups many of these utilities and includes methods for the following:</p>
-<ul>
-  <li>Saving and/or building the workspace before launching a particular launch configuration</li>
-  <li>Storage and retrieval of images on behalf of debug UI clients</li>
-  <li>Lookup of the debug model presentation associated with a given debug model</li>
-  <li>Retrieval of the debug plug-in preference store</li>
-  <li>Information about the current program under debug, such as the current context, process, or console</li>
-  <li>Opening the launch configuration dialog with various defaults</li>
-  <li>Enabling or disabling the use of step filters</li>
-</ul>
-<p><a href="../reference/api/org/eclipse/debug/ui/IDebugView.html"><b>IDebugView</b></a>
-provides common function for debug views. It provides access to an
-underlying viewer and its debug model presentation. Typically, clients
-should extend <a href="../reference/api/org/eclipse/debug/ui/AbstractDebugView.html"><b>AbstractDebugView</b></a>
-rather than implement the interface from scratch. <a href="../reference/api/org/eclipse/debug/ui/AbstractDebugView.html"><b>AbstractDebugView</b></a>
-provides many useful functions:</p>
-<ul>
-  <li>Storage of actions in an action registry</li>
-  <li>Generic handling of the underlying viewer's context menu</li>
-  <li>General implementations of delete key and double click function </li>
-  <li>Mechanism for displaying an error message in the view</li>
-</ul>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs.htm
deleted file mode 100644
index a192742..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Dialogs and wizards
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>Dialogs and wizards</h1>
-<p>
-We've seen how to extend the workbench UI by adding views, editors, and 
-actions to the workbench.  We've contributed a preference page for controlling
-the behavior of our plug-in.  Now we can tie it all together by launching our 
-own dialogs in response to these actions.</p>
-<p>
-The JFace UI framework provides several standard dialogs and a framework for
-building your own dialogs and wizards.  We'll look at the different kinds of dialogs and wizards and how to build
-them.</p>
-<p>
-We'll also cover some simple workbench extensions for contributing wizards.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_applications.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs_applications.htm
deleted file mode 100644
index e0cbd7e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_applications.htm
+++ /dev/null

@@ -1,105 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-<TITLE>
-Application dialogs
-</TITLE>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-<h2>
-Application dialogs</h2>
-<P >
-When a standard dialog is too simple for your plug-in, you can build your own dialog using the
-<a href="../reference/api/org/eclipse/jface/dialogs/Dialog.html"><b> Dialog</b></a> class. Earlier, we saw how the readme tool contributed an &quot;Open Readme Browser&quot;
-action in an action set.&nbsp; This action set is shown in the workbench tool bar
-and <b>Window-&gt;Readme File Editor</b> menu.&nbsp;&nbsp;</P>
-
-<P >
-Now we are ready to look at the implementation of this action in the readme
-tool's <b>WindowActionDelegate</b>.</P>
-
-<pre>
-   public void run(IAction action) {
-      SectionsDialog dialog = new SectionsDialog(window.getShell(),
-         ReadmeModelFactory.getInstance().getSections(selection));
-      dialog.open();
-   }
-</pre>
-
-<P >
-The window action delegate for the action set uses the current selection in the resource navigator view (the
-<b> .readme</b> file) to get a list of sections in the readme file. This list and the
-workbench window's shell are passed to the
-<b>SectionsDialog</b>.&nbsp;</P>
-
-<P >
-When the user selects the action, the <b>SectionsDialog</b>
-is opened.</P>
-
-<img src="images/readmedialog.png" alt="" border="0" >
-
-
-<P >
- The <b> SectionsDialog</b> is implemented in the readme tool plug-in by subclassing the
-<b><a href="../reference/api/org/eclipse/jface/dialogs/Dialog.html"> Dialog</a>
-</b> class in the <b><a href="../reference/api/org/eclipse/jface/dialogs/package-summary.html"> org.eclipse.jface.dialogs</a>
-package.</b></P>
-<P >
-The <a href="../reference/api/org/eclipse/jface/dialogs/Dialog.html"><b> Dialog</b></a> class provides basic support for building a dialog shell window, creating the common dialog buttons, and launching the dialog. The subclasses are responsible for handling the content of the dialog itself:</P>
-<ul>
-  <li><b>createDialogArea</b> creates the SWT controls that represent the dialog contents. This is similar to creating the controls for a view or
-    editor.
-<P>
-The <b> SectionsDialog</b> creates an SWT list to display the list of sections. It uses a JFace viewer to populate the list. (We'll look at JFace viewers in
-<a HREF="jface_viewers.htm" CLASS="XRef"> Viewers</a>.) Note that our dialog does not have to create any of the buttons for the dialog since this is done by our
-superclass.</P>
-<pre>
-   protected Control createDialogArea(Composite parent) {
-      Composite composite = (Composite)super.createDialogArea(parent);
-      List list = new List(composite, SWT.BORDER);
-      ...
-      ListViewer viewer = new ListViewer(list);
-      ...
-      return composite;
-   }
-</pre>
-<br>
-  </li>
-  <li><b>configureShell</b> is overridden to set an appropriate title for the shell window.
-<pre>
-   protected void configureShell(Shell newShell) {
-      super.configureShell(newShell);
-      newShell.setText(MessageUtil.getString(&quot;Readme Sections&quot;));
-      ...
-   }
-</pre>
-<br>
-  </li>
-  <li>
-<b>
-okButtonPressed</b> is overridden to perform whatever action is necessary when the user presses the OK button. (You can also override
-<b> cancelButtonPressed</b> or <b> buttonPressed(int)</b> depending on the design of your dialog.)&nbsp;&nbsp;
-  </li>
-</ul>
-<b>SectionsDialog</b> does not implement an <b> okButtonPressed</b> method. It inherits the &quot;do-nothing&quot; implementation from
-<a href="../reference/api/org/eclipse/jface/dialogs/Dialog.html"><b>Dialog</b></a>. This is not typical. Your dialog usually performs some processing in response to one of the dialog buttons being pressed.
-<P >
-Dialogs can be as simple or as complicated as necessary. When you implement a dialog, most of your dialog code is concerned with creating the SWT controls that represent its content area and handling any events necessary while the dialog is up. Once a button is pressed by the user, the dialog can query the state of the various controls (or viewers) that make up the dialog to determine what to do.</P>
-
-
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_settings.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs_settings.htm
deleted file mode 100644
index 65589e7..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_settings.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-<TITLE>Dialog settings</TITLE>
-
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-
-<h2>
-Dialog settings</h2>
-<p>
-The <a href="../reference/api/org/eclipse/jface/dialogs/package-summary.html"> <b> org.eclipse.jface.dialogs</b></a> 
-package provides a utility class,
-<a href="../reference/api/org/eclipse/jface/dialogs/DialogSettings.html"><b>DialogSettings</b></a>, 
-for storing and retrieving keyed values. You can use this class to save and retrieve primitive data types 
-and string values that you associate with key names. The settings are loaded and saved using an XML file.</p>
-<p><a href="../reference/api/org/eclipse/ui/plugin/AbstractUIPlugin.html"><b>AbstractUIPlugin</b></a> provides support for plug-in wide dialog settings stored in an XML file in your plug-in's directory. If a dialog settings file is not found in your plug-in directory, an empty
-<a href="../reference/api/org/eclipse/jface/dialogs/DialogSettings.html"> <b> DialogSettings</b></a> will be created for you. When the plug-in is shut down, any settings that were added to it will be saved in an XML file and retrieved the next time the plug-in is started up.</p>
-<p>
-You can access your dialog settings anywhere in your plug-in code. The following snippet shows how you could obtain the dialog settings for the readme tool.</p>
-<pre>
-   IDialogSettings settings = ReadmePlugin.getDefault().getDialogSettings();
-</pre>
-<p>
-Values are stored and retrieved using get and put methods. The get methods are named after the type of primitive that is being accessed. You can store and retrieve
-boolean, long, double, float, int, array, and string values. The following snippet shows how we could use dialog settings to initialize control values in a dialog.</p>
-<pre>
-   protected Control createDialogArea(Composite parent) {
-      IDialogSettings settings = ReadmePlugin.getDefault().getDialogSettings();
-      checkbox = new Button(parent,SWT.CHECK);
-      checkbox.setText(&quot;Generate sample section titles&quot;);
-      // initialize the checkbox according to the dialog settings
-<b>      checkbox.setSelection(settings.getBoolean(&quot;GenSections&quot;));
-</b>   }
-</pre>
-<p>
-The value of the setting can be stored later when the ok button is pressed.</p>
-<pre>
-   protected void okPressed() {
-      IDialogSettings settings = ReadmePlugin.getDefault().getDialogSettings();
-      // store the value of the generate sections checkbox
-<b>      settings.put(&quot;GenSections&quot;, checkbox.getSelection());
-</b>      super.okPressed();
-   }
-</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_standard.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs_standard.htm
deleted file mode 100644
index fcf471c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_standard.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-<TITLE>
-Standard dialogs
-</TITLE>
-
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h2>
-Standard dialogs</h2>
-<P >
-The package <a href="../reference/api/org/eclipse/jface/dialogs/package-summary.html"> <b> org.eclipse.jface.dialogs</b></a> defines the basic support for dialogs. This package provides standard dialogs for displaying user messages and obtaining simple input from the user.</P>
-<ul>
-  <li>
-<a href="../reference/api/org/eclipse/jface/dialogs/MessageDialog.html">
-<b>
-MessageDialog</b></a> displays a message to the user. You can set the dialog title, image, button text, and message in the constructor for this dialog.</li>
-  <li><a href="../reference/api/org/eclipse/jface/dialogs/ErrorDialog.html"><b>ErrorDialog</b></a> displays information about an error. You can set the dialog title and message for the dialog. You can also supply an IStatus object which the dialog will use to obtain an error message.</li>
-  <li>
-<a href="../reference/api/org/eclipse/jface/dialogs/InputDialog.html"><b>
-InputDialog</b></a> allows the user to enter text. You can set the dialog title, default text value, and supply an object that will validate the text input.</li>
-  <li>
-<a href="../reference/api/org/eclipse/jface/dialogs/ProgressMonitorDialog.html"><b>
-ProgressMonitorDialog</b></a> shows progress to the user during the running of
-a long operation.</li>
-</ul>
-<P >
-The standard dialogs are designed so that you can completely specify the dialog in its constructor. We saw a
-<b><a href="../reference/api/org/eclipse/jface/dialogs/MessageDialog.html"> MessageDialog</a>
-</b> in action in the readme tool's view action:</P>
-<pre>
-   MessageDialog.openInformation(
-      view.getSite().getShell(),&quot;Readme Editor&quot;,&quot;View Action executed&quot;);</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards.htm
deleted file mode 100644
index dcc5315..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards.htm
+++ /dev/null

@@ -1,100 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Wizards
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Wizards</H2>
-<P >
-Wizards are used to guide the user through a sequenced set of tasks. Your plug-in can contribute wizards at predefined extension points in the workbench. It can also create and launch its own wizards.</P>
-<P >
-When you contribute to a workbench wizard extension point, the actions that launch the wizard are already set up by the workbench. You need only supply the wizard that will be used.&nbsp;</P>
-
-<P >
-If you need to launch other wizards that are not already defined in workbench
-wizard extension points, you must launch them yourself.&nbsp; You can launch your own wizards by adding an action to a view, editor, popup,
-or an action set.&nbsp;</P>
-
-<P >
-A wizard is composed of several different underlying parts.&nbsp;</P>
-
-<img alt="" border="0" src="images/wiz_arch.jpg" >
-
-
-<p>
-&nbsp;</p>
-
-
-<h3>
-Wizard dialog</h3>
-<P >
-The wizard dialog (<b><a href="../reference/api/org/eclipse/jface/wizard/WizardDialog.html">WizardDialog</a></b>)
-is the top level dialog in a wizard. It defines the standard wizard buttons and manages a set of pages that are provided to it.</P>
-<P >
-When you contribute to a workbench wizard extension, you do not have to create a wizard dialog. One is created on your behalf by the workbench, and your wizard is set into it.</P>
-
-
-<P >
-The wizard dialog performs the enabling and disabling of the <b>Next</b>, <b>Back</b>, and <b> Finish</b> 
-buttons based on information it obtains from the wizard and the current wizard
-page.</P>
-
-
-<h3>
-Wizard</h3>
-<P >
-The wizard (<a href="../reference/api/org/eclipse/jface/wizard/IWizard.html"><b>IWizard</b></a>)
-controls the overall appearance and behavior of the wizard, such as title bar text, image, and the availability of a help button.
-Wizards often use a corresponding <a href="../reference/api/org/eclipse/jface/dialogs/DialogSettings.html"><b>DialogSettings</b></a>
-to obtain (and store) the default values for the settings of controls on the wizard pages.</P>
-<P >
-The <b><a href="../reference/api/org/eclipse/jface/wizard/Wizard.html"> Wizard</a></b> class
-implements many of the details for standard wizard behavior.&nbsp; You typically
-extend this class to implement behavior specific to your wizard. The primary responsibilities of your wizard
-will include:</P>
-<ul>
-  <li>
-    
-Creating and adding your pages to your wizard</li>
-  <li>
-    
-Implementing the behavior that should occur when the user presses the <b> Finish</b> button.
-  </li>
-</ul>
-
-
-<h3>
-Wizard page</h3>
-<P >
-The wizard page (<a href="../reference/api/org/eclipse/jface/wizard/IWizardPage.html"><b>IWizardPage</b></a>) defines the controls that are used to show the content of the wizard page. It responds to events in its content areas and determines when the page is completed.</P>
-<P >
-Your wizard page typically extends the <a href="../reference/api/org/eclipse/jface/wizard/WizardPage.html"><b> WizardPage</b></a> class.&nbsp;
-The primary responsibilities of your wizard page will include:</P>
-<ul>
-  <li>
-    
-creating the SWT controls that represent the page</li>
-  <li>
-    
-determing when the user has supplied enough information to complete the page (that is, when the user can move to the next page.)
-  </li>
-</ul>
-
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_exportWizards.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_exportWizards.htm
deleted file mode 100644
index 9619e6c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_exportWizards.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-org.eclipse.ui.exportWizards
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-<H3>
-org.eclipse.ui.exportWizards</H3>
-<P >
-You can add a wizard to the <b> File &gt; Export</b> menu option in the workbench using the
-<a href="../reference/extension-points/org_eclipse_ui_exportWizards.html"><b> org.eclipse.ui.exportWizards</b></a> extension point. The process for defining the extension and implementing the wizard is similar to&nbsp;
-<b><a href="../reference/extension-points/org_eclipse_ui_newWizards.html">org.eclipse.ui.newWizards</a></b>.&nbsp;
-The primary difference in the markup is that export wizards do not define or
-assign categories for the wizards themselves.&nbsp; The wizards appear
-uncategorized in a wizard dialog. </P>
-<P >
-<img src="images/exportwizard.png" alt="" border="0"> </P>
-<P >
-The wizard supplied in the class parameter of the markup must implement <a href="../reference/api/org/eclipse/ui/IExportWizard.html"><b>IExportWizard</b></a>.
-Its pages are typically extended from
-<a href="../reference/api/org/eclipse/ui/dialogs/WizardExportPage.html"><b> WizardExportPage</b></a>.</P>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_extensions.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_extensions.htm
deleted file mode 100644
index 2a7ad83..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_extensions.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Workbench wizard extension points</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-
-<h2>
-Workbench wizard extension points</h2>
-<P >
-The workbench defines extension points for wizards that create new resources, import resources, or export resources.&nbsp;</P>
-<P >
- When you make selections in the new, import, or export menu, the workbench uses
-various wizard
-selection dialogs to display all the wizards that have been contributed for that particular extension point.&nbsp;
-The import wizard dialog is shown below.</P>
-<P >
-<img src="images/importwizard.png" alt="Import wizard dialog with selection list" border="0"></P>
-<P >
-Your wizard takes control once it is selected in the list and the <b> Next</b> button is pressed. This is when your first page becomes visible.&nbsp;</P>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_importWizards.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_importWizards.htm
deleted file mode 100644
index 6caa846..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_importWizards.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>org.eclipse.ui.importWizards</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-
-<H3>
-org.eclipse.ui.importWizards</H3>
-<P >
-You can add a wizard to the <b> File &gt; Import</b> menu option in the workbench using the
-<a href="../reference/extension-points/org_eclipse_ui_importWizards.html"> <b> org.eclipse.ui.importWizards</b></a> extension point. The process for defining the extension and implementing the wizard is similar to
-<b><a href="../reference/extension-points/org_eclipse_ui_newWizards.html">org.eclipse.ui.newWizards</a></b>.&nbsp;
-The primary difference in the markup is that import wizards do not define or
-assign categories for the wizards themselves.&nbsp; The wizards appear
-uncategorized in a wizard dialog. </P>
-<P >
-<img src="images/importwizard.png" alt="" border="0"> </P>
-<P >
-The wizard supplied in the class parameter of the markup must implement <a href="../reference/api/org/eclipse/ui/IImportWizard.html"><b>IImportWizard</b></a>.
-Its pages are typically extended from
-<a href="../reference/api/org/eclipse/ui/dialogs/WizardImportPage.html"> <b> WizardImportPage</b></a>.</P>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_multipage.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_multipage.htm
deleted file mode 100644
index e72c07c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_multipage.htm
+++ /dev/null

@@ -1,111 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Multi-page wizards
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-<h2>
-Multi-page wizards</h2>
-<P >
-If your wizard implements a complex task, you may want to use more than one page to obtain information from the user.</P>
-<P >
-In general, the implementation pattern is the same as for a single page wizard.</P>
-<ul>
-  <li>
-    
-Create a <a href="../reference/api/org/eclipse/jface/wizard/WizardPage.html"> <b> WizardPage</b></a> subclass for each page in your wizard. Each wizard page should use
-<b>setPageComplete(true)</b> when it has enough information.</li>
-  <li>
-    
-Create a <a href="../reference/api/org/eclipse/jface/wizard/Wizard.html"> <b> Wizard</b></a> subclass which adds each page to the wizard.</li>
-  <li>
-    
-Implement a <b> performFinish</b> method to perform the finish logic.</li>
-</ul>
-<P >
-When you design a wizard, it's good practice to put all the required information on the first page if possible. This way, the user does not have to traverse the entire set of pages in order to finish the task.&nbsp;
-Optional information can go on subsequent pages. </P>
-<P >
-When a page requires input from the user before it can be considered complete, use
-<b>setPageComplete(false)</b> to signify that it is not complete. As the page receives events from its controls, it rechecks to see if the page is complete. Once the required input is provided,
-<b>setPageComplete(true)</b> signals completion.</P>
-<P >
-The <a href="../reference/api/org/eclipse/jface/wizard/Wizard.html"> <b> Wizard</b></a> class handles the
-logic required to enable and disable the <b> Finish</b>  button according to the
-completion state of the pages.&nbsp; The
-<b> Finish</b> button is only enabled for a wizard when each of its pages have set its completion state to true.</P>
-
-<h3>
-Validation and page control</h3>
-<P >
-The classes <a href="../reference/api/org/eclipse/ui/dialogs/WizardNewFileCreationPage.html"> <b> WizardNewFileCreationPage</b></a> and
-<b> CreateReadme1</b> show a common pattern for implementing page validation.</P>
-<P >
-<a href="../reference/api/org/eclipse/ui/dialogs/WizardNewFileCreationPage.html">
-<b>
-WizardNewFileCreationPage</b></a> defines a common event handler for all SWT events which validates the page. This means the page will be validated whenever an event is received from a widget to which the page added a listener.</P>
-<pre>
-   public void handleEvent(Event event) {
-      setPageComplete(validatePage());
-   }
-</pre>
-<P >
-Once the <b>ReadmeCreationPage</b> creates its controls, it sets the state of the page using
-<b>validatePage</b>.</P>
-<pre>
-   public void createControl(Composite parent) {
-      super.createControl(parent);
-      // create controls, add listeners, and layout the page
-      ...
-      // sample section generation checkboxes
-      sectionCheckbox = new Button(group,SWT.CHECK);
-      sectionCheckbox.setText(MessageUtil.getString(&quot;Generate_sample_section_titles&quot;));
-      sectionCheckbox.setSelection(true);
-      sectionCheckbox.<b>addListener</b>(SWT.Selection,this);
-
-      subsectionCheckbox = new Button(group,SWT.CHECK);
-      subsectionCheckbox.setText(MessageUtil.getString(&quot;Generate_sample_subsection_titles&quot;));
-      subsectionCheckbox.setSelection(true);
-      subsectionCheckbox.<b>addListener</b>(SWT.Selection,this);
-      ...
-      <b>setPageComplete(validatePage());</b>
-   }
-</pre>
-<P >
-Using this pattern, a wizard page can put all of its page validation code in one method,
-<b>validatePage()</b>. This method determines the initial state of the page and recalculates the state any time it receives an event from a widget on its page.</P>
-<P >
-Since we added a listener to the section checkbox, we will recompute the valid state of the page whenever that checkbox receives a selection event.
-Note that the page's
-<b> handleEvent</b> method must call super to ensure that the
-inherited page validation behavior occurs in addition to any specific event handling for this
-page.</P>
-<pre>
-   public void handleEvent(Event e) {
-      Widget source = e.widget;
-      if (source == sectionCheckbox) {
-         if (!sectionCheckbox.getSelection())
-            subsectionCheckbox.setSelection(false);
-         subsectionCheckbox.setEnabled(sectionCheckbox.getSelection());
-      }
-      super.handleEvent(e);
-   }
-</pre>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_newWizards.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_newWizards.htm
deleted file mode 100644
index 66c3cf6..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_newWizards.htm
+++ /dev/null

@@ -1,203 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-org.eclipse.ui.newWizards
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-<H3>
-org.eclipse.ui.newWizards</H3>
-<P >
-You can add a wizard to the <b> File &gt; New &gt; </b>menu options in the workbench using the
-<a href="../reference/extension-points/org_eclipse_ui_newWizards.html"><b> org.eclipse.ui.newWizards</b></a> extension point. The readme
-tool example uses this extension point definition to add the Readme File wizard:</P>
-<pre>
-&lt;extension
-      point = &quot;org.eclipse.ui.newWizards&quot;&gt;
-	&lt;category
-	   id = &quot;org.eclipse.ui.examples.readmetool.new&quot;
-	   parentCategory=&quot;org.eclipse.ui.Examples&quot;
-	   name=&quot;%NewWizard.category&quot;&gt;
-	&lt;/category&gt;
- 	&lt;wizard
-	   id = &quot;org.eclipse.ui.examples.readmetool.wizards.new.file&quot;
-      	   name = &quot;%NewWizard.name&quot;
-	   class=&quot;org.eclipse.ui.examples.readmetool.ReadmeCreationWizard&quot;
-	   category=&quot;org.eclipse.ui.Examples/org.eclipse.ui.examples.readmetool.new&quot;
-	   icon=&quot;icons/obj16/newreadme_wiz.png&quot;&gt;
-    	   &lt;description&gt;%NewWizard.desc&lt;/description&gt;
-	   &lt;selection class=&quot;org.eclipse.core.resources.IResource&quot;/&gt;
-	&lt;/wizard&gt;
-&lt;/extension&gt;
-</pre>
-<P >The <b>category</b> describes the grouping for the wizard.&nbsp; An optional
-<b>parentCategory</b>  establishes the new category as a child of an existing
-category.</p>
-<P > Top level categories will appear in the <b> File &gt; New </b>menu.&nbsp;
-In this example, the <b>parentCategory</b> is set to an &quot;Examples&quot;
-category.&nbsp; Where did the parent category come from?&nbsp; The <b>org.eclipse.ui</b>
-plug-in defines a standard examples category in its markup:</p>
-<pre>&lt;extension
-        point=&quot;org.eclipse.ui.newWizards&quot;&gt;
-    &lt;category
-          name=&quot;%NewWizards.Category.Examples&quot;
-          id=&quot;org.eclipse.ui.Examples&quot;&gt;
-    &lt;/category&gt;
-    ...</pre>
-<P >This category appears in the <b> File &gt; New </b> menu.</P>
-<P >
-<img src="images/newwizardmenu.png" alt="New menu with Examples category" border="0"></P>
-<P >
-&nbsp;</P>
-<P >
-The readme tool's category <b>name</b> 
- defines the label that is used for the next layer of grouping underneath the
-parent category.&nbsp; These categories are shown as the second level in the tree
-shown in the <b>New Example</b> wizard.&nbsp; The wizard's <b>name</b> and <b>icon</b> are shown
-underneath when you expand the category.&nbsp; The <b>description</b> 
-of the selected wizard is shown at the top of the wizard when you select it.</P>
-<P >
-<img src="images/newwizardlist.png" alt="New example wizard with readme entries" border="0"></P>
-<P >
-This information about the wizard appears solely because of the markup in the <b>plugin.xml
-</b>file.&nbsp; None of the plug-in code runs
-until the user chooses the <b>Next</b> button.&nbsp; Once this happens, the
-workbench will instantiate the wizard <b>class</b>
-specified in the markup and pass it an expected selection <b>class</b>.</P>
-<P >
-The class identified in this extension (<b>ReadmeCreationWizard</b>) must
-implement the
-<a href="../reference/api/org/eclipse/ui/INewWizard.html"> <b> INewWizard</b></a> interface.&nbsp;
-Most wizards do so by extending the platform
-<a href="../reference/api/org/eclipse/jface/wizard/Wizard.html"> <b> Wizard</b></a> class
-although this is an implementation mechanism and not required by the extension
-point.</P>
-<P >
-The wizard itself does little but create the pages inside of it. Let's look at the implementation of the page first, and then come back to the wizard.</P>
-
-<H4>
-Pages</H4>
-<P >
-The workbench provides base wizard page classes that support the type of processing performed for each wizard extension point. You can use these pages, or extend them to add additional processing.</P>
-<P >
-The goal of the <b> ReadmeCreationWizard</b> is to create a new file, add the required content to the file, and as an option, open an editor on the file. Our page needs to define the controls that let the user specify what content goes in the file and whether an editor should be launched.</P>
-<P >
-We create the wizard page, <b>ReadmeCreationPage</b>, by extending
-<a href="../reference/api/org/eclipse/ui/dialogs/WizardNewFileCreationPage.html"><b>WizardNewFileCreationPage</b></a>. The controls for a wizard page are defined in a fashion
-similar to the definition of the controls for a view or an editor. The page implements a
-<b> createControl</b> method, creating the necessary SWT widgets as children of the supplied
-<a href="../reference/api/org/eclipse/swt/widgets/Composite.html"><b>Composite</b></a>. Since the superclass already adds widgets that support new file processing, we need only extend the
-<b> createControl</b> method in our wizard page to add the additional checkboxes that control generation of sections and opening of the editor.</P>
-<pre>
-   public void createControl(Composite parent) {
-      // inherit default container and name specification widgets
-      super.createControl(parent);
-      Composite composite = (Composite)getControl();
-      ...
-      // sample section generation group
-      Group group = new Group(composite,SWT.NONE);
-      group.setLayout(new GridLayout());
-      group.setText(MessageUtil.getString(&quot;Automatic_sample_section_generation&quot;));
-      group.setLayoutData(new GridData(GridData.GRAB_HORIZONTAL |
-         GridData.HORIZONTAL_ALIGN_FILL));
-      ...
-      // sample section generation checkboxes
-      sectionCheckbox = new Button(group,SWT.CHECK);
-      sectionCheckbox.setText(MessageUtil.getString(&quot;Generate_sample_section_titles&quot;));
-      sectionCheckbox.setSelection(true);
-      sectionCheckbox.addListener(SWT.Selection,this);
-
-      subsectionCheckbox = new Button(group,SWT.CHECK);
-      subsectionCheckbox.setText(MessageUtil.getString(&quot;Generate_sample_subsection_titles&quot;));
-      subsectionCheckbox.setSelection(true);
-      subsectionCheckbox.addListener(SWT.Selection,this);
-      ...
-      // open file for editing checkbox
-      openFileCheckbox = new Button(composite,SWT.CHECK);
-      openFileCheckbox.setText(MessageUtil.getString(&quot;Open_file_for_editing_when_done&quot;));
-      openFileCheckbox.setSelection(true);
-      ...
-   }
-</pre>
-<P >
-You should be able to follow this code if you understand the concepts in
-<a HREF="swt.htm" CLASS="XRef">Standard Widget Toolkit</a>.</P>
-<P >
-The basic patterns for implementing a page include:</P>
-<ul>
-  <li>
-    
-Add listeners to any controls that affect dynamic behavior of the page. For example, if selecting an item in a list or checking a box affects the state of other controls of the page, add a listener so you can change the state of the page.</li>
-  <li>
-    
-Populate the controls with data based on the current selection when the wizard was launched. Some of the data may depend on the values in other controls. Some of the controls may use dialog settings to initialize their
-values.&nbsp;&nbsp;</li>
-  <li>
-    
-Use <b>setPageComplete(true)</b> when enough information is provided by the user to exit the page (and move to the next page or finish the wizard.)</li>
-</ul>
-<P >
-The <b>ReadmeCreationPage</b> class inherits a lot of this behavior from the
-<a href="../reference/api/org/eclipse/ui/dialogs/WizardNewFileCreationPage.html"><b>WizardNewFileCreationPage</b></a>.&nbsp;
-Browse the implementation of these classes for further information.</P>
-<P >
-Now that we understand what a page does, let's look again at the wizard.</P>
-
-
-<H4>
-Wizard</H4>
-<P >
-The wizard is responsible for creating the pages and providing the &quot;finish&quot; logic.</P>
-<P >
-The basic patterns for implementing a wizard include:</P>
-<ul>
-  <li>
-Implement the <b>init</b> method to set up local variables for context information such as the workbench and the current selection.<br>
-<pre>
-   public void init(IWorkbench workbench,IStructuredSelection selection) {
-      this.workbench = workbench;
-      this.selection = selection;
-      setWindowTitle(MessageUtil.getString(&quot;New_Readme_File&quot;));
-      setDefaultPageImageDescriptor(ReadmeImages.README_WIZARD_BANNER);
-   }
-</pre></li>
-
-  <li>
-Implement <b> addPages</b> by creating instances of the pages.<br>
-<pre>
-   public void addPages() {
-      mainPage = new ReadmeCreationPage(workbench, selection);
-      addPage(mainPage);
-   }
-</pre></li>
-
-  <li>
-Implement <b> performFinish</b> to finish the task.<br>
-
-  Multi-page wizards typically handle the finish logic in the wizard itself, since each page will contribute information that determines how the task is implemented. Single page wizards can implement the logic in the wizard or ask the page to finish the job.
-The approach you take largely depends on where your important state is kept.&nbsp;
-In the case of the readme wizard, we are going to ask our page to handle the finish processing.&nbsp;
-<pre>
-   public boolean performFinish() {
-      return mainPage.finish();
-   }
-</pre></li>
-</ul>
-<P >
-The completed wizard looks like this:</P>
-<P >
-<img src="images/readmewizard.png" alt="Readme file creation wizard page" border="0"></P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_wizarddialogs.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_wizarddialogs.htm
deleted file mode 100644
index cda1df0..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_wizarddialogs.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Wizard dialogs
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-<h2>
-Wizard dialogs</h2>
-<P >
-The previous example supplied a wizard for a specified extension point. Another, perhaps more common,
-case is that you want to launch your own plug-in's wizard from some action that you have defined. (In
-<a HREF="workbench_menus.htm" CLASS="XRef"> Workbench menu contributions</a>, we discuss the ways you can contribute actions to the workbench.) </P>
-<P >Wizards are displayed in the UI by placing them in a containing
-dialog.&nbsp; This detail is handled for you when you contribute to a wizard
-extension.&nbsp; When you are launching your own wizard, you must display it
-yourself by wrapping it in a <a href="../reference/api/org/eclipse/jface/wizard/WizardDialog.html"><b>WizardDialog</b></a>.</P>
-<P >
-For example, the <b> ReadmeCreationWizard</b> could be launched independently by creating a wizard dialog and associating it with the
-<b>ReadmeCreationWizard</b>. The following code snippet shows how this could be done from some action delegate. (The method assumes that we know the workbench and the selection.)</P>
-<pre>
-   public void run(IAction action) {
-      // Create the wizard
-      ReadmeCreationWizard wizard = new ReadmeCreationWizard();
-      wizard.init(getWorkbench(), selection);
-
-      // Create the wizard dialog
-      WizardDialog dialog = new WizardDialog
-         (getWorkbench().getActiveWorkbenchWindow().getShell(),wizard);
-      // Open the wizard dialog
-      dialog.open();
-   }</pre>
-   <p>If you need to embed a wizard anywhere else in your plug-in's user
-   interface, the interface <a href="../reference/api/org/eclipse/jface/wizard/IWizardContainer.html"><b>IWizardContainer</b></a>
-   defines the necessary protocol for hosting a wizard.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors.htm
deleted file mode 100644
index de54c10..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Editors
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>Editors</h1>
-<P >
-We have seen how plug-ins can contribute an editor to the workbench, but we
-haven't yet looked at the implementation of an editor.</P>
-<P >There is no &quot;typical&quot; implementation pattern for an editor, because editors usually provide application-specific semantics.&nbsp;
-A tool that edits and manages a particular content type will
-provide customized behavior for manipulating the data represented by the resource.</P>
-<P >Editors can come in all shapes and sizes.&nbsp; If a plug-in's editor is text-based, then the editor can either use the existing default text editor, or create a customized text editor
-by using the facilities provided in the platform.&nbsp; The latter approach is used by the
-Java example editor.</P>
-    <p >
-<img src="images/javaeditor.png" alt="Java text editor" border="0" > </p>
-    <p >
-If a plug-in's editor is not text based, then a custom editor must be implemented by the plug-in. There are several approaches for building
-custom editors, all of which depend on the look and behavior of the editor.</p>
-<ul>
-  <li>
-    
-Form-based editors can layout controls in a fashion similar to a dialog or wizard.&nbsp;
-    The Plug-in Development Environment (PDE) uses this approach in building its
-    manifest editors.&nbsp;&nbsp;</li>
-  <li>
-    
-Graphics intensive editors can be written using SWT level code.&nbsp; For
-example, an editor could create its own SWT window for displaying the
-information, or it could use a custom SWT control that is optimized for the
-application.</li>
-  <li>
-    
-List-oriented editors can use JFace list, tree, and table viewers to manipulate
-their data.</li>
-</ul>
-<P >
-Once the implementation model for the editor has been determined, implementing the editor is much like programming a stand-alone JFace or SWT application.&nbsp;
-Platform extensions are used to add actions, preferences, and wizards needed to
-support the editor.&nbsp; But the internals of the editor are largely dependent
-on your application design principles and internal model.
-</P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors_actions.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors_actions.htm
deleted file mode 100644
index d481256..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors_actions.htm
+++ /dev/null

@@ -1,162 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Registering editor actions
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>Registering editor actions</H2>
-<p>The text editor framework provides many utility classes that aid in presenting
-and updating text and source code.&nbsp; Now we will turn our attention to the workbench in
-which the editor is but one part.&nbsp; How does the editor interact with other
-workbench features such as context menus, menu bars, and tool bars?</p>
-
-<h3>Editor menu bar actions</h3>
-
-<p>To understand how editors register themselves with the workbench and provide
-actions for the workbench menu bar, see the section discussing <a href="workbench_basicext_editors.htm">org.eclipse.ui.editors</a>.&nbsp;
-We won't rehash that information here.&nbsp;&nbsp;We'll just take a quick look
-at the markup where the Java example editor registers its editor.</p>
-
-<pre>&lt;extension
-      point=&quot;org.eclipse.ui.editors&quot;&gt;
-   &lt;editor
-         name=&quot;%javaEditorName&quot;
-         icon=&quot;icons/obj16/java.png&quot;
-         extensions=&quot;jav&quot;
-         <b>contributorClass=&quot;org.eclipse.ui.examples.javaeditor.JavaActionContributor&quot;</b>
-         class=&quot;org.eclipse.ui.examples.javaeditor.JavaEditor&quot;
-         id=&quot;org.eclipse.ui.JavaEditor&quot;&gt;
-   &lt;/editor&gt;
-&lt;/extension&gt;</pre>
-
-<p>Workbench menu bar actions are contributed by the <b>JavaActionContributor</b>.&nbsp; 
-  It implements actions that are placed in the workbench <b>Edit</b> menu and 
-  the workbench tool bar.</p>
-
-<pre>public JavaActionContributor() {
-	super();
-	fContentAssistProposal= <b>new RetargetTextEditorAction</b>(JavaEditorMessages.getResourceBundle(), &quot;ContentAssistProposal.&quot;); //$NON-NLS-1$
-	...
-	fContentAssistTip= new RetargetTextEditorAction(JavaEditorMessages.getResourceBundle(), &quot;ContentAssistTip.&quot;); //$NON-NLS-1$
-	...
-	fTogglePresentation= new PresentationAction();
-}</pre>
-<p>The first two actions are defined as retargetable text editor actions. The 
-  principle is similar to the <a href="wrkAdv_retarget.htm">retargetable actions</a> 
-  provided by the workbench. Retargetable text editor actions represent menu entries 
-  which the action contributor dynamically binds to corresponding actions provided 
-  by the active editor. When the active editor changes, the action to which a 
-  retargetable text editor action is bound changes as well. The following snippet 
-  shows that the editor action contributor finds the corresponding action by asking 
-  the editor for an action of a given id:</p>
-<pre>protected final IAction getAction(ITextEditor editor, String actionId) {<br>	return (editor == null ? null : editor.getAction(actionId));<br>}
-
-public void setActiveEditor(IEditorPart part) {<br>	super.setActiveEditor(part);<br>	ITextEditor editor= null;<br>	if (part instanceof ITextEditor)<br>		editor= (ITextEditor) part;<br>	fContentAssistProposal.setAction(getAction(editor, &quot;ContentAssistProposal&quot;));<br>	fContentAssistTip.setAction(getAction(editor, &quot;ContentAssistTip&quot;));<br>	fTogglePresentation.setEditor(editor);<br>	fTogglePresentation.update();<br>}</pre>
-<p>The id must be the same under which the action is registered with the editor 
-  as given here for the <b>JavaTextEditor</b>. (See also next section.):<br>
-</p>
-<pre>protected void createActions() {
-	super.createActions();
-		
-	IAction a= new TextOperationAction(JavaEditorMessages.getResourceBundle(), &quot;ContentAssistProposal.&quot;, this, ISourceViewer.CONTENTASSIST_PROPOSALS); //$NON-NLS-1$
-	<b>a.setActionDefinitionId(ITextEditorActionDefinitionIds.CONTENT_ASSIST_PROPOSALS);</b>
-	setAction(&quot;ContentAssistProposal&quot;, a); 
-		
-	a= new TextOperationAction(JavaEditorMessages.getResourceBundle(), &quot;ContentAssistTip.&quot;, this, ISourceViewer.CONTENTASSIST_CONTEXT_INFORMATION);  //$NON-NLS-1$
-	a.setActionDefinitionId(ITextEditorActionDefinitionIds.CONTENT_ASSIST_CONTEXT_INFORMATION);
-	setAction(&quot;ContentAssistTip&quot;, a); 
-}</pre>
-
-<p>The third action in the contributor is a concrete action added to the workbench 
-  tool bar.&nbsp; It toggles the state of the editor between showing the highlighted 
-  range (as dictated by the Java example's content outliner) and showing the entire 
-  file.&nbsp; This action only appears in the tool bar.</p>
-
-<h3>Editor context menus</h3>
-
-The editor context menus are created and managed in the <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html"><b>AbstractTextEditor</b></a>
- and <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a><b>
- </b>framework.
-<p>The method <b>createActions</b> is used to register actions with the editor.&nbsp; 
-  This includes actions appropriate for the editor context menus or any actions 
-  contributed in extension definitions.&nbsp; In the Java example editor, only 
-  the actions that get bound to the retargetable actions are created.&nbsp; However, 
-  the Java example editor also inherits the actions created by <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a> 
-  and its superclasses.&nbsp; These actions can be used in the editor context 
-  menus.</p>
-<p>The <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a>
-method <b>editorContextMenuAboutToShow</b> is used in the framework to allow
-editors to add actions to the context menu for the editing area.&nbsp; You can
-use a menu path to decide exactly where your action should appear.&nbsp; Valid
-menu paths inside the editor context menu are defined in the implementation of
-this method in <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html"><b>AbstractTextEditor</b></a>.</p>
-<p>There are several ways to add an action to this menu.&nbsp; The first way is 
-  by adding an action using only the id under which it is registered with the 
-  editor.&nbsp; For example, the <b>JavaTextEditor</b> adds its actions for content 
-  assistance to the menu when this method is called.&nbsp; Actions will not appear 
-  in the menu when no action is registered under the used id.</p>
-<pre>public void editorContextMenuAboutToShow(MenuManager menu) {
-	super.editorContextMenuAboutToShow(menu);
-	addAction(menu, &quot;ContentAssistProposal&quot;); 
-	addAction(menu, &quot;ContentAssistTip&quot;); 
-}</pre>
-<p>The superclass <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a> 
-  adds actions a second way - by specifying a menu group in the context menu 
-  for placing the action.&nbsp; In this case the actions (<b>Shift Left</b>, <b>Shift 
-  Right</b>) do appear in the context menu in the group defined by <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html"><b>AbstractTextEditor</b></a>.</p>
-<pre>protected void editorContextMenuAboutToShow(IMenuManager menu) {
-	super.editorContextMenuAboutToShow(menu);
-	addAction(menu, ITextEditorActionConstants.GROUP_EDIT, ITextEditorActionConstants.SHIFT_RIGHT);
-	addAction(menu, ITextEditorActionConstants.GROUP_EDIT, ITextEditorActionConstants.SHIFT_LEFT);
-}</pre>
-<p><img src="images/javaeditorcontextmenu.png" alt="Editor context menu" border="0"> </p>
-<p>The method <b>rulerContextMenuAboutToShow</b>  is used in the same way before
-the ruler's context menu is shown.&nbsp; The implementation of this method in <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html"><b>AbstractTextEditor</b></a>
-defines the groups in which items can be added to the menu. </p>
-<h3>Menu ids </h3>
-<p>The editor context and ruler context menus can be assigned ids so that other
-plug-ins can contribute to these menus in their extensions.&nbsp; The scheme for
-establishing menu ids is more flexible since the original version of the
-platform.&nbsp; However, the framework can run in a compatibility mode in order
-to remain compatible with plug-ins developed for the original version.&nbsp; You
-can use <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html"><b>AbstractTextEditor</b></a><b>.setCompatibilityMode()</b>
-to control this behavior.&nbsp; The default setting is true. </p>
-
-<h4>1.0 compatible menu ids </h4>
-<p>When the compatibility mode is true, the ids of the editor and ruler context 
-  menus can be set using <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html"><b>AbstractTextEditor</b></a> 
-  protocol.&nbsp; The methods <b>setEditorContextMenuId</b> and <b>setRulerContextMenuId</b> 
-  can be used for this purpose.&nbsp; Resetting the ids can be useful if you want 
-  to prevent inheriting menus that were contributed to superclass menus.&nbsp; 
-  For example, the <b>JavaTextEditor</b> in the example resets its context menu 
-  ids to be Java specific in order to prevent inheriting any generic text contributions 
-  from other plug-ins. </p>
-<pre>protected void initializeEditor() {
-	super.initializeEditor();
-	JavaEditorEnvironment.connect(this);
-	setSourceViewerConfiguration(new JavaSourceViewerConfiguration());
-	<b>setEditorContextMenuId(&quot;#JavaEditorContext&quot;); 
-	setRulerContextMenuId(&quot;#JavaRulerContext&quot;); </b>
-}</pre>
-<p>If no id is set anywhere in the 
-  concrete hierarchy, the default ids defined by <b><a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html">AbstractTextEditor</a></b> 
-  will be used. </p>
-<h4>1.0 non-compatible menu ids </h4>
-<p>The editor context menu id is always <code>&lt;editor id&gt;.EditorContext</code>, 
-  where <code>&lt;editor id&gt;</code> is the id of the editor . The id of an 
-  editor is defined in the xml declaration of the editor. The ruler context menu 
-  id is always <code>&lt;editor id&gt;.RulerContext</code>.</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors_annotations.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors_annotations.htm
deleted file mode 100644
index 5e71cd3..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors_annotations.htm
+++ /dev/null

@@ -1,212 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Source viewers and annotations
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>Source viewers and annotations</H2>
-<p>The editor and its corresponding text viewer are largely responsible for the
-implementation of the document's presentation and the configuration of any needed
-helper classes.&nbsp; (See <a href="jface_viewers.htm">Viewers</a> if you are not familiar with the
-concept of a viewer.)&nbsp;&nbsp;</p>
-<p>A <b><a href="../reference/api/org/eclipse/jface/text/TextViewer.html">TextViewer</a></b>
-handles all of the low level details of mapping the document model and its
-partitions into the colored and formatted text that a user sees.&nbsp; For source code style editors, a <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewer.html">SourceViewer</a></b>
-is provided.&nbsp; A source viewer introduces the notion of source code
-annotations.&nbsp; These annotations can be shown in a vertical ruler on the left side of
-the text, an overview ruler on the right side of the text,&nbsp;or as colored
-squigglies underneath text.</p>
-<p><b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewer.html">SourceViewer</a></b>
-and its helper classes are used
-throughout the <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html"><b>AbstractTextEditor</b></a>
-hierarchy.&nbsp; The package <b><a href="../reference/api/org/eclipse/jface/text/source/package-summary.html">org.eclipse.jface.text.source</a></b>
-defines this viewer and the other classes supporting annotation presentation.</p>
-<h3>Annotations and rulers</h3>
-<p>Annotations, like partitions, are largely dependent on the kind of document being edited.
-The <a href="../reference/api/org/eclipse/jface/text/source/IAnnotationModel.html"><b>IAnnotationModel</b></a>
-for a document is what holds the annotations, enumerates them on request, and listens for text
-changes in order to keep the annotations up to date with the text.  Annotation models are registered
-in the <b><a href="../reference/extension-points/org_eclipse_core_filebuffers_annotationModelCreation.html">org.eclipse.core.filebuffers.annotationModelCreation</a></b> 
-extension.  This extension point allows plug-ins to register a class that will create an annotation model
-appropriate for a given file extension.  The Java Editor example does not use this extension point, so it
-inherits the annotation model defined by the platform.</p>
-<pre>&lt;extension
-	point="org.eclipse.core.filebuffers.annotationModelCreation"&gt;
-	&lt;factory
-		extensions="*"
-		<b>class="org.eclipse.ui.texteditor.ResourceMarkerAnnotationModelFactory"</b>&gt;
-	&lt;/factory&gt;
-&lt;/extension&gt;
-</pre>
-<p>
-The supplied factory class will create a
-<b><a href="../reference/api/org/eclipse/ui/texteditor/ResourceMarkerAnnotationModel.html">ResourceMarkerAnnotationModel</a></b>
-for files with any extension.  This class displays annotations that represent a marker on a resource in the
-workspace.&nbsp; (See <a href="resAdv_markers.htm">Resource markers</a> for more
-information on markers.)&nbsp; It assigns an image and description to each marker and monitors its resource for changes in the markers.</p>
-<p>To see how an annotation model is displayed in a text editor, we'll examine
-the platform text editor and its use of rulers and annotations.&nbsp; The
-specifics of how different annotations are shown in the rulers and text can be
-controlled by the user in the <b>General &gt; Editors &gt; Text Editors &gt; Annotations</b>
-preferences.</p>
-<h4>Vertical ruler</h4>
-<p>A vertical ruler to the left of the editing area is used by platform text
-editors to show text ranges and line-based annotations adjacent to their text line.</p>
-
-<p><img src="images/javaeditorverticalruler.png" alt="Vertical ruler" border="0"></p>
-
-<p>These annotations are described in the supplied <b><a href="../reference/api/org/eclipse/ui/texteditor/ResourceMarkerAnnotationModel.html">ResourceMarkerAnnotationModel</a></b>.&nbsp; 
-  This model is set into the <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewer.html">SourceViewer</a></b> 
-  when the source viewer is initialized by the editor.&nbsp; The following snippet 
-  from <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html"><b>AbstractTextEditor</b></a> 
-  <b> </b>shows how the document and the annotation model are associated with 
-  the viewer.</p>
-
-<pre>private void initializeSourceViewer(IEditorInput input) {
-		
-	IAnnotationModel model= getDocumentProvider().getAnnotationModel(input);
-	IDocument document= getDocumentProvider().getDocument(input);
-		
-	if (document != null) {
-		<b>fSourceViewer.setDocument(document, model)</b>;
-		...</pre>
-<p>Once the source viewer is configured with the proper document and annotation
-model, it has enough information to present the document and ensure the correct
-annotations are shown in the vertical ruler to the left.&nbsp; The model is
-associated with the ruler when the document is set.&nbsp; The following snippet
-shows what happens when a document is set into the source viewer.&nbsp; It has
-been simplified from the actual code in <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewer.html">SourceViewer</a></b>
-for clarity:</p>
-
-<pre>public void setDocument(IDocument document, IAnnotationModel annotationModel) {
-	...
-	// create visual annotation model from the supplied model and store 
-	// in fVisualAnnotationModel
-	...
-	if (fVerticalRuler != null)
-		<b>fVerticalRuler.setModel(fVisualAnnotationModel)</b>;
-</pre>
-
-<p>In this way, the ruler is associated with the appropriate annotation
-model.&nbsp;&nbsp;</p>
-
-<p>Let's look at the ruler itself.&nbsp; It is created by the text editor and 
-  then connected with the editor's viewer.&nbsp; Since the Java editor example 
-  does not define any special behavior for rulers, it inherits the ruler as defined 
-  in <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a>.</p>
-
-<pre>protected IVerticalRuler createVerticalRuler() {
-	CompositeRuler ruler= new CompositeRuler();
-	ruler.addDecorator(0, new AnnotationRulerColumn(VERTICAL_RULER_WIDTH));
-	if (isLineNumberRulerVisible())
-		ruler.addDecorator(1, createLineNumberRulerColumn());
-	return ruler;
-}</pre>
-<p>The text editor uses a CompositeRuler. This ruler does not have a visual presentation 
-  of its own.&nbsp; The presentation is provided by a list of decorators that 
-  show columns (<b><a href="../reference/api/org/eclipse/jface/text/source/IVerticalRulerColumn.html">IVerticalRulerColumn</a></b>) 
-  in the ruler.&nbsp; In this example, a ruler column that shows annotations (<b><a href="../reference/api/org/eclipse/jface/text/source/AnnotationRulerColumn.html">AnnotationRulerColumn</a></b>) 
-  is always added, and a line number ruler column is added based on user preferences. 
-  The annotation ruler column handles the particulars of displaying the annotation 
-  images in the proper locations.</p>
-<p>Despite all the classes involved in showing a ruler, note that the example
-editor needed only to subclass framework classes to get ruler
-behavior.&nbsp;&nbsp; <b>JavaDocumentProvider</b>&nbsp;inherits an appropriate
-marker annotation model from <b><a href="../reference/api/org/eclipse/ui/editors/text/FileDocumentProvider.html">FileDocumentProvider</a></b>.&nbsp;
-The JavaTextEditor inherits the ruler presentation from <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a>.</p>
-<h4>Overview ruler</h4>
-<p>An overview ruler on the right hand side of the editing area is used to show 
-  annotations concerning the entire document.&nbsp; These annotations are shown 
-  relative to their position in the document and do not move as the user scrolls 
-  the document.&nbsp;&nbsp;There usually is a corresponding annotation on the 
-  vertical ruler when that portion of the document is visible.&nbsp;&nbsp;</p>
-<p>The vertical ruler below shows that there are two tasks in the document and
-one bookmark.&nbsp; Since the bookmarked text is visible, its annotation is also
-shown on the left.</p>
-<p><img src="images/javaeditoroverviewruler.png" alt="Vertical overview ruler in Java Editor" border="0" ></p>
-<p>The user can navigate to the location of the annotation in the code by
-clicking on the annotation itself.</p>
-<p>The types of annotations shown in the overview ruler are determined by adding 
-  annotation types to the ruler.&nbsp; In the following snippet from <a href="../reference/api/org/eclipse/ui/texteditor/SourceViewerDecorationSupport.html"><b>SourceViewerDecorationSupport</b></a>, 
-  annotation types are dynamically added to the ruler. (See next section for more 
-  information about <a href="../reference/api/org/eclipse/jface/text/IDocumentPartitioner.html"><b>SourceViewerDecorationSupport</b></a>.)</p>
-
-<pre>private void showAnnotationOverview(Object annotationType) {<br>	if (fOverviewRuler != null) {
-		Color c= getAnnotationTypeColor(annotationType);<br>		fOverviewRuler.setAnnotationTypeColor(annotationType, c);
-		int l= getAnnotationTypeLayer(annotationType);<br>		fOverviewRuler.setAnnotationTypeLayer(annotationType, l);<br>		fOverviewRuler.addAnnotationType(annotationType);<br>		fOverviewRuler.update();<br>	}
-}</pre>
-<p>The overview ruler is also supplied with an <b><a href="../reference/api/org/eclipse/jface/text/source/IAnnotationAccess.html">IAnnotationAccess</a></b>
-that is used to provide information about a particular annotation, such as its
-type and how it is to be displayed.&nbsp; The <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a>
-uses a <a href="../reference/api/org/eclipse/ui/texteditor/DefaultMarkerAnnotationAccess.html"><b>DefaultMarkerAnnotationAccess</b></a>
-which interprets annotations according to their marker types and consults the
-user preferences to see which marker types should be shown in the overview
-ruler. </p>
-
-<pre>protected IAnnotationAccess createAnnotationAccess() {
-	return new DefaultMarkerAnnotationAccess(fAnnotationPreferences);
-}</pre>
-<p>Consult the implementation of <a href="../reference/api/org/eclipse/ui/texteditor/DefaultMarkerAnnotationAccess.html"><b>DefaultMarkerAnnotationAccess</b></a>
-and <a href="../reference/api/org/eclipse/ui/texteditor/MarkerAnnotation.html"><b>MarkerAnnotation</b></a>
-for more detail about presenting markers in the overview ruler. </p>
-<h4>Text annotations </h4>
-<p>In addition to showing annotations in the rulers, a source viewer can show
-annotations as colored squiggly marks in the text.&nbsp;&nbsp;</p>
-<p><img src="images/javaeditorsquiggly.png" alt="Squiggly mark in Java Editor" border="0"></p>
-<p>We'll look again at the creation of the source viewer in <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a>.</p>
-
-<pre>protected ISourceViewer createSourceViewer(Composite parent, IVerticalRuler ruler, int styles) {
-		
-	... 
-	ISourceViewer sourceViewer= new SourceViewer(parent, ruler, fOverviewRuler, isOverviewRulerVisible(), styles);
-	<b>fSourceViewerDecorationSupport= new SourceViewerDecorationSupport(sourceViewer, fOverviewRuler, fAnnotationAccess, sharedColors);
-	configureSourceViewerDecorationSupport();</b>
-		
-	return sourceViewer;
-}</pre>
-<p>The class <a href="../reference/api/org/eclipse/ui/texteditor/SourceViewerDecorationSupport.html"><b>SourceViewerDecorationSupport</b></a>
-handles many of the decorations shown in a source viewer, including text
-annotations, colored margins, colored cursor lines, and the like.&nbsp; It is
-configured with the user preferences so that it can respond to dynamic updates
-of user preference changes.&nbsp; Most editors need not be concerned with the
-details of how these decorations are painted.&nbsp; (See <a href="../reference/api/org/eclipse/ui/texteditor/SourceViewerDecorationSupport.html"><b>SourceViewerDecorationSupport</b></a>
-and related classes such as <a href="../reference/api/org/eclipse/jface/text/source/AnnotationPainter.html"><b>AnnotationPainter</b></a>
-if you must!).&nbsp; The important thing to know is what decorations are
-available so that the <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewer.html">SourceViewer</a></b>
-and its supporting <a href="../reference/api/org/eclipse/ui/texteditor/SourceViewerDecorationSupport.html"><b>SourceViewerDecorationSupport</b></a>
-are configured correctly.</p>
-<h4>Configuring a SourceViewerDecorationSupport</h4>
-<p>Let's look at the configuration used by <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a>
-for the decoration support.</p>
-
-<pre>protected void configureSourceViewerDecorationSupport() {
-
-	<b>Iterator e= fAnnotationPreferences.getAnnotationPreferences().iterator();
-	while (e.hasNext())
-		fSourceViewerDecorationSupport.setAnnotationPreference((AnnotationPreference) e.next());</b>
-	fSourceViewerDecorationSupport.setAnnotationPainterPreferenceKeys(DefaultMarkerAnnotationAccess.UNKNOWN, UNKNOWN_INDICATION_COLOR, UNKNOWN_INDICATION, UNKNOWN_INDICATION_IN_OVERVIEW_RULER, 0);
-		
-	fSourceViewerDecorationSupport.setCursorLinePainterPreferenceKeys(CURRENT_LINE, CURRENT_LINE_COLOR);
-	fSourceViewerDecorationSupport.setMarginPainterPreferenceKeys(PRINT_MARGIN, PRINT_MARGIN_COLOR, PRINT_MARGIN_COLUMN);
-	fSourceViewerDecorationSupport.setSymbolicFontName(getFontPropertyPreferenceKey());
-}</pre>
-<p>Note that the annotation preferences are used to define annotation types for 
-  all of the annotations shown in the user preferences.&nbsp; This includes annotations 
-  contributed by any plug-in and is not limited to the workbench-supplied annotations.&nbsp; 
-  If you do not wish to show all available annotations in your editor, you should 
-  override this method and set up the <a href="../reference/api/org/eclipse/ui/texteditor/SourceViewerDecorationSupport.html"><b>SourceViewerDecorationSupport</b></a><b> 
-  </b>with only those types you want to show.</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors_contentassist.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors_contentassist.htm
deleted file mode 100644
index c799631..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors_contentassist.htm
+++ /dev/null

@@ -1,127 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Content assist
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>Content assist</H2>
-<p>Content assist allows you to provide context sensitive content completion upon 
-  user request.&nbsp; This functionality is implemented by the platform text framework 
-  in <b><a href="../reference/api/org/eclipse/jface/text/contentassist/package-summary.html">org.eclipse.jface.text.contentassist</a></b>.&nbsp; 
-  Popup windows (infopops) are used to propose possible text choices to complete 
-  a phrase.&nbsp; The user can select these choices for insertion in the text.&nbsp; 
-  Content assist also supports contextual infopops for providing the user with 
-  information that is related to the current position in the document.&nbsp;</p>
-<p>Implementing content assist is
-optional.&nbsp; By default, <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a>
-</b>does not install a content assistant since it does not know the
-document model used for a particular editor, and has no generic behavior for
-content assist.&nbsp;</p>
-<p>In order to implement content assist, your editor's source
-viewer configuration must be <a href="editors_sourceviewers.htm">configured</a>
-to define a content assistant.&nbsp; This is done in the Java editor example
-inside the <b>JavaSourceViewerConfiguration</b>.</p>
-
-<pre>public IContentAssistant getContentAssistant(ISourceViewer sourceViewer) {
-
-	ContentAssistant assistant= new ContentAssistant();
-<b>	assistant.setContentAssistProcessor(new JavaCompletionProcessor(), IDocument.DEFAULT_CONTENT_TYPE);
-	assistant.setContentAssistProcessor(new JavaDocCompletionProcessor(), JavaPartitionScanner.JAVA_DOC);
-</b>
-	...
-	return assistant;
-}</pre>
-<p>Content assist behavior is defined in the interface <a href="../reference/api/org/eclipse/jface/text/contentassist/IContentAssistant.html"><b>IContentAssistant</b></a>.&nbsp;
-Setting up a content assistant is somewhat similar to setting up syntax
-highlighting.&nbsp; The assistant should be configured with different phrase completion strategies for different
-document content types.&nbsp; The completion strategies are implemented
-using&nbsp; <a href="../reference/api/org/eclipse/jface/text/contentassist/IContentAssistantProcessor.html"><b>IContentAssistProcessor</b></a>.&nbsp;
-A processor proposes completions and computes context information for an offset
-within particular content type.</p>
-<h3>Content assist processors</h3>
-<p>Not all content types need to have content assistance.&nbsp; In the Java example 
-  editor, content assist processors are provided for the default content type 
-  and javadoc, but not for multi-line comments.&nbsp; Let's look at each of these 
-  processors.</p>
-<p>The <b>JavaCompletionProcessor</b> is quite simple.&nbsp; It can only propose
-keywords as completion candidates.&nbsp; The keywords are defined in a field,
-<code>fgProposals</code>, and these keywords are always proposed as the
-candidates:</p>
-
-<pre>public ICompletionProposal[] computeCompletionProposals(ITextViewer viewer, int documentOffset) {
-	ICompletionProposal[] result= new ICompletionProposal[fgProposals.length];
-	for (int i= 0; i &lt; fgProposals.length; i++) {
-		IContextInformation info= new ContextInformation(fgProposals[i], MessageFormat.format(JavaEditorMessages.getString(&quot;CompletionProcessor.Proposal.ContextInfo.pattern&quot;), new Object[] { fgProposals[i] })); //$NON-NLS-1$
-		result[i]= new CompletionProposal(fgProposals[i], documentOffset, 0, fgProposals[i].length(), null, fgProposals[i], info, MessageFormat.format(JavaEditorMessages.getString(&quot;CompletionProcessor.Proposal.hoverinfo.pattern&quot;), new Object[] { fgProposals[i]})); //$NON-NLS-1$
-	}
-	return result;
-}</pre>
-<p><img src="images/javacontentassist.png" alt="Keyword content assist" border="0"></p>
-
-<p>Completion can be triggered by user request or can be automatically triggered
-when the &quot;(&quot; or &quot;.&quot; character is typed:</p>
-
-<pre>public char[] getCompletionProposalAutoActivationCharacters() {
-	return new char[] { '.', '(' };
-}</pre>
-<p>In addition to proposing completions, the <b>JavaCompletionProcessor</b> 
-defines context information that can be requested by the user.&nbsp; Context
-information includes a description of the pieces of information available in a
-given context and the detailed information message.&nbsp;&nbsp;</p>
-<p>In the Java editor example, the information is not really contextual.&nbsp; 
-  An array containing five similar context information objects is computed for the 
-  current offset when the user requests context info.&nbsp;All of these context 
-  information objects define a context that contains the five characters in front 
-  of the offset and the five after the offset. If any one of these five proposals is 
-  selected, the detailed information will appear near the cursor and will stay 
-  as long as the cursor is within the context of the five characters around the offset. 
-</p>
-
-<pre>public IContextInformation[] computeContextInformation(ITextViewer viewer, int documentOffset) {
-	IContextInformation[] result= new IContextInformation[5];
-	for (int i= 0; i &lt; result.length; i++)
-		result[i]= new ContextInformation(
-			MessageFormat.format(JavaEditorMessages.getString(&quot;CompletionProcessor.ContextInfo.display.pattern&quot;), new Object[] { new Integer(i), new Integer(documentOffset) }),
-			MessageFormat.format(JavaEditorMessages.getString(&quot;CompletionProcessor.ContextInfo.value.pattern&quot;), new Object[] { new Integer(i), new Integer(documentOffset - 5), new Integer(documentOffset + 5)}));
-	return result;
-}</pre>
-<p><img src="images/javacontextassist.png" alt="Java context assist" border="0"></p>
-<p>&nbsp;</p>
-<p>This context information is shown automatically when the &quot;#&quot; character 
-  is typed:</p>
-<pre>public char[] getContextInformationAutoActivationCharacters() {
-	return new char[] { '#' };
-}</pre>
-<h3>Content assist configuration</h3>
-<p>The appearance and behavior of content assist can be configured using <a href="../reference/api/org/eclipse/jface/text/contentassist/IContentAssistant.html"><b>IContentAssistant</b></a>.&nbsp;
-For example, you can configure the auto activation time out, and the orientation
-and color of information popups.</p>
-
-<pre>public IContentAssistant getContentAssistant(ISourceViewer sourceViewer) {
-
-	ContentAssistant assistant= new ContentAssistant();
-	...
-	assistant.enableAutoActivation(true);
-	assistant.setAutoActivationDelay(500);
-	assistant.setProposalPopupOrientation(IContentAssistant.PROPOSAL_OVERLAY);
-	assistant.setContextInformationPopupOrientation(IContentAssistant.CONTEXT_INFO_ABOVE);
-	assistant.setContextInformationPopupBackground(JavaEditorEnvironment.getJavaColorProvider().getColor(new RGB(150, 150, 0)));
-
-	return assistant;
-}</pre>
-<p>&nbsp;</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors_documents.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors_documents.htm
deleted file mode 100644
index f810eb5..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors_documents.htm
+++ /dev/null

@@ -1,150 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Documents and partitions
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>Documents and partitions</H2>
-<p>The platform text framework defines a document model for text and provides 
-  a viewer that displays text using this model.&nbsp;We will start by looking 
-  at the Java editor example and how it uses this model.&nbsp; We will not focus 
-  on the basic mechanics of registering an editor extension, since we've already 
-  seen this in the section discussing <a href="workbench_basicext_editors.htm"><b>org.eclipse.ui.editors</b></a>.&nbsp; 
-  Instead, we'll look at the specifics of how the editor class is implemented 
-  in the example.</p>
-<h3>Document providers and documents</h3>
-<p>In the workbench, an editor is typically opened when the user selects a domain 
-  element (such as a file or an element stored inside an archive file) and opens 
-  it.&nbsp; When the editor is created, it is associated with an editor input 
-  (<a href="../reference/api/org/eclipse/ui/IEditorInput.html"><b>IEditorInput</b></a>), 
-  which describes the object being edited.</p>
-<p>The Java editor example opens when the user opens a file with the &quot;*.jav&quot; 
-  extension.&nbsp; In this case, the input to the editor is an <a href="../reference/api/org/eclipse/ui/IFileEditorInput.html"><b>IFileEditorInput</b></a>.&nbsp; 
-  The platform text framework assumes little about the editor input itself.&nbsp; 
-  It works with a presentation model, called an <a href="../reference/api/org/eclipse/jface/text/IDocument.html"><b>IDocument</b></a>, 
-  for the input, so that it can effectively display and manipulate text.</p>
-<p>This means that there must be a way to map from an expected domain model (the 
-  editor input) to the presentation model.&nbsp; This mapping is defined in an 
-  <a href="../reference/api/org/eclipse/ui/texteditor/IDocumentProvider.html"><b>IDocumentProvider</b></a>.&nbsp; 
-  Given an editor input, the document provider returns an appropriate <a href="../reference/api/org/eclipse/jface/text/IDocument.html"><b>IDocument</b></a>.</p>
-<p>The Java editor example inherits the <b>TextFileDocumentProvider</b> defined by 
-  the plug-in <b>org.eclipse.ui.editors</b>. The extension
-  <b><a href="../reference/extension-points/org_eclipse_ui_editors_documentProviders.html">org.eclipse.ui.editors.documentProviders</a></b> 
-  is used to define mappings between editor input types (or file extensions)
-  and document providers. The editors plug-in defines its document provider as follows:</p>
-<pre>
-   &lt;extension
-         point="org.eclipse.ui.editors.documentProviders"&gt;
-      &lt;provider
-            class="org.eclipse.ui.editors.text.TextFileDocumentProvider"
-            inputTypes="org.eclipse.ui.IStorageEditorInput"
-            id="org.eclipse.ui.editors.text.StorageDocumentProvider"&gt;
-      &lt;/provider&gt;
-   &lt;/extension&gt;
-</pre>
-<p>This extension point allows plug-ins to register document providers and associate them
-  with either a file extension or an editor input class.  Since the Java editor example does
-  not define its own document provider extension, it inherits the generic document provider
-  specified for all input types that are <a href="../reference/api/org/eclipse/ui/IStorageEditorInput.html"><b>IStorageEditorInput</b></a>.
-  When the user opens a file for editing, the platform manages the details of creating the
-  proper document provider instance.  If a specific document provider is registered for the file extension, that one
-  will be used.  If there is no specific document provider for the file extension, then the editor input type
-  will be used to find the appropriate provider.</p>
-<p>By using the generic platform document provider, the Java editor example can take advantage of all of the
-features of the document provider, such as file buffering and other optimizations.</p>
-<h4>Document setup</h4>
-<p>Since the Java editor uses the platform text document provider, how can it supply any specialized behavior
-for handling Java files?</p>
-<p>
-The extension <b><a href="../reference/extension-points/org_eclipse_core_filebuffers_documentSetup.html">org.eclipse.core.filebuffers.documentSetup</a></b> 
-is used to define mappings between file extensions and an <a href="../reference/api/org/eclipse/core/filebuffers/IDocumentSetupParticipant.html"><b>IDocumentSetupParticipant</b></a>.
-The setup participant will set up the document with any special features once it has been provided to the editor.</p>
-<pre>&lt;extension
-	id="ExampleJavaDocumentSetupParticipant"
-	name="%documentSetupParticipantName"
-	point="org.eclipse.core.filebuffers.documentSetup"&gt;
-	&lt;participant
-		extensions="jav"
-		<b>class="org.eclipse.ui.examples.javaeditor.JavaDocumentSetupParticipant"</b>&gt;
-	&lt;/participant&gt;
-&lt;/extension&gt;
-</pre>
-<p>This extension definition is what gives the example a chance to setup the document for Java specific
-tasks.  So what does <b>JavaDocumentSetupParticipant</b> do?  We'll look at a simplified version of the
-<b>setup</b> method.</p>
-<pre> 	public void setup(IDocument document) {
-		...
-		IDocumentPartitioner partitioner= new FastPartitioner(JavaEditorExamplePlugin.getDefault().getJavaPartitionScanner(), JavaPartitionScanner.JAVA_PARTITION_TYPES);
-		partitioner.connect(document);
-		...
-	}
-</pre>
-<p>The setup code configures an object called a <b>partitioner</b>.</p>
-<h4>Partitions</h4>
-<p>The partitioner (<a href="../reference/api/org/eclipse/jface/text/IDocumentPartitioner.html"><b>IDocumentPartitioner</b></a>)
-is responsible for dividing the document into non-overlapping 
-  regions called partitions.&nbsp; Partitions (represented by <a href="../reference/api/org/eclipse/jface/text/ITypedRegion.html"><b>ITypedRegion</b></a>) 
-  are useful for treating different sections of the document differently with 
-  respect to features like syntax highlighting or formatting.</p>
-<p> In the case of the Java editor
-example, the document is divided into partitions that represent the javadoc
-comments, multi line comments, and everything else.&nbsp; Each region is assigned a
-content type and its position in the document.&nbsp; Positions are updated as the user edits text.</p>
-<h4>Rule based document partitioning</h4>
-<p>It is up to each editor to determine the appropriate implementation for a
-document partitioner.&nbsp; Support is provided in <b><a href="../reference/api/org/eclipse/jface/text/rules/package-summary.html">org.eclipse.jface.text.rules</a></b>
- for rule-based document scanning.&nbsp; Using a rule-based scanner allows an editor to use
-the <a href="../reference/api/org/eclipse/jface/text/rules/FastPartitioner.html"><b>FastPartitioner</b></a>
-provided by the framework.</p>
-<pre>IDocumentPartitioner partitioner= new FastPartitioner(JavaEditorExamplePlugin.getDefault().getJavaPartitionScanner(), JavaPartitionScanner.JAVA_PARTITION_TYPES);
-</pre>
-<p><a href="../reference/api/org/eclipse/jface/text/rules/RuleBasedPartitionScanner.html"><b>RuleBasedPartitionScanner</b></a>
-is the superclass for rule based scanners.&nbsp; Subclasses are responsible
-for enumerating and implementing the rules that should be used to distinguish
-tokens such as line delimiters, white space, and generic
-    patterns when scanning a document.&nbsp; The example's <b>JavaPartitionScanner</b>
-defines rules for distinguishing single line comments, character constants, javadoc, multi
-line comments, and&nbsp;words.&nbsp; This is done in the scanner's constructor:</p>
-<pre>public JavaPartitionScanner() {
-	super();
-	IToken javaDoc= new Token(JAVA_DOC);
-	IToken comment= new Token(JAVA_MULTILINE_COMMENT);
-
-	List rules= new ArrayList();
-	// Add rule for single line comments.
-	rules.add(new EndOfLineRule(&quot;//&quot;, Token.UNDEFINED)); 
-
-	// Add rule for strings and character constants.
-	rules.add(new SingleLineRule(&quot;\&quot;&quot;, &quot;\&quot;&quot;, Token.UNDEFINED, '\\')); 
-	rules.add(new SingleLineRule(&quot;'&quot;, &quot;'&quot;, Token.UNDEFINED, '\\')); 
-
-	// Add special case word rule.
-	rules.add(new WordPredicateRule(comment));
-
-	// Add rules for multi-line comments and javadoc.
-	rules.add(new MultiLineRule(&quot;/**&quot;, &quot;*/&quot;, javaDoc, (char) 0, true)); 
-	rules.add(new MultiLineRule(&quot;/*&quot;, &quot;*/&quot;, comment, (char) 0, true)); 
-
-	IPredicateRule[] result= new IPredicateRule[rules.size()];
-	rules.toArray(result);
-	setPredicateRules(result);
-}</pre>
-<p>See the classes in <b><a href="../reference/api/org/eclipse/jface/text/rules/package-summary.html">org.eclipse.jface.text.rules</a></b>
- for more details about defining rules and the types of rules availables.&nbsp;
-We'll look at the scanners again when we look at <a href="editors_highlighting.htm">syntax
-coloring</a>.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors_highlighting.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors_highlighting.htm
deleted file mode 100644
index 6d5db59..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors_highlighting.htm
+++ /dev/null

@@ -1,130 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Syntax coloring
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>Syntax coloring</H2>
-<p>Syntax coloring is provided in the platform text framework using a model of damage, repair, and reconciling.&nbsp;
-For
-    each change applied to a document, a presentation reconciler determines
-    which region of the visual presentation should be invalidated and how to
-    repair it.&nbsp; Different strategies can be used for different content
-types in the document.</p>
-<p>Implementing syntax coloring (and doing so with a presentation reconciler) is
-optional.&nbsp; By default, <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a>
-</b>does not install a presentation reconciler since it does not know the
-document model used for a particular editor, and has no generic behavior for
-syntax highlighting.&nbsp;&nbsp;</p>
-<p>In order to use the reconciling classes to implement syntax highlighting, your editor's source
-viewer configuration must be <a href="editors_sourceviewers.htm">configured</a>
-to define a presentation reconciler.&nbsp; Once again, we start with <b>JavaSourceViewerConfiguration</b>
- to see how a presentation reconciler is defined for our editor.</p>
-
-<pre>public IPresentationReconciler getPresentationReconciler(ISourceViewer sourceViewer) {
-
-	PresentationReconciler reconciler= new PresentationReconciler();
-	...
-	return reconciler;
-}</pre>
-<p>To understand what a presentation reconciler does, we must first look at the
-concepts of damage, repair, and reconciling.</p>
-<h3>Damage, repair, and reconciling</h3>
-<p>As the user modifies text in an editor, parts of the editor must be
-redisplayed to show the changes.&nbsp; Computing the text that must be
-redisplayed is known as computing <b>damage</b>.&nbsp; When syntax coloring is
-involved, the amount of damage caused by an editing operation becomes more
-extensive, since the presence or absence of a single character could change the
-coloring of the text around it.&nbsp;&nbsp;</p>
-<p>Damagers (<b><a href="../reference/api/org/eclipse/jface/text/presentation/IPresentationDamager.html">IPresentationDamager</a></b>)
-  determine the region of a document's presentation which must be rebuilt because 
-  of a document change. A presentation damager is assumed to be specific to a 
-  particular document content type (or region). It must be able to return a damage 
-  region that is valid input for a presentation repairer (<b><a href="../reference/api/org/eclipse/jface/text/presentation/IPresentationRepairer.html">IPresentationRepairer</a></b>).&nbsp; 
-  A repairer must be able to derive all of the information 
-  it needs from a damage region in order to successfully describe the <b>repairs</b> 
-  that are needed for a particular content type.</p>
-<p><b>Reconciling</b> describes the overall process of
-maintaining the presentation of a document as changes are made in the
-editor.&nbsp; A presentation reconciler (<b><a href="../reference/api/org/eclipse/jface/text/presentation/IPresentationRepairer.html">IPresentationReconciler</a></b>)
-monitors changes to the text through its associated viewer.&nbsp; It uses the
-document's regions to determine the content types affected by the change and
-notifies a damager that is appropriate for the affected content type.&nbsp; Once
-the damage is computed, it is passed to the appropriate repairer which will
-construct repair descriptions that are applied to the viewer to put it back in
-sync with the underlying content.&nbsp;</p>
-<p>The classes in <b><a href="../reference/api/org/eclipse/jface/text/reconciler/package-summary.html">org.eclipse.jface.text.reconciler</a></b>
- define additional support classes for synchronizing a document model with
-external manipulation of the document.</p>
-<p>Presentation reconcilers should be provided with a repairer and
-damager pair for each content type to be found in the document.&nbsp; It is up to each editor to determine the appropriate implementation for a
-presentation reconciler.&nbsp; However, the platform provides support in <b><a href="../reference/api/org/eclipse/jface/text/rules/package-summary.html">org.eclipse.jface.text.rules</a></b>
- for using rule-based document scanners to compute and repair damage.&nbsp;
-Default damagers and repairers are defined in this package.&nbsp; They can be
-used along with the standard reconcilers in <b><a href="../reference/api/org/eclipse/jface/text/presentation/package-summary.html">org.eclipse.jface.text.presentation</a></b>
-to implement syntax coloring by defining scanning rules for the document.</p>
-<h4>Rule based reconciling</h4>
-<p>Now we have enough background to look in detail at the creation of the
-example presentation
-reconciler.&nbsp; Recall that the Java editor example implements a <b>JavaPartitionScanner</b>
- which partitions the document into content types representing javadoc, multi
-line comments, and everything else.&nbsp;</p>
-<p>For each of these content types, a damager/repairer pair must be
-specified.&nbsp; This is done below using the <b><a href="../reference/api/org/eclipse/jface/text/presentation/PresentationReconciler.html">PresentationReconciler</a></b>
-and the <b><a href="../reference/api/org/eclipse/jface/text/rules/DefaultDamagerRepairer.html">DefaultDamagerRepairer</a></b>.</p>
-<pre>
-	JavaColorProvider provider= JavaEditorEnvironment.getJavaColorProvider();
-	PresentationReconciler reconciler= new PresentationReconciler();
-		
-	DefaultDamagerRepairer dr= new DefaultDamagerRepairer(JavaEditorEnvironment.getJavaCodeScanner());
-	reconciler.setDamager(dr, IDocument.DEFAULT_CONTENT_TYPE);
-	reconciler.setRepairer(dr, IDocument.DEFAULT_CONTENT_TYPE);
-
-	dr= new DefaultDamagerRepairer(new SingleTokenScanner(new TextAttribute(provider.getColor(JavaColorProvider.JAVADOC_DEFAULT))));
-	reconciler.setDamager(dr, JavaPartitionScanner.JAVA_DOC);
-	reconciler.setRepairer(dr, JavaPartitionScanner.JAVA_DOC);
-
-	dr= new DefaultDamagerRepairer(new SingleTokenScanner(new TextAttribute(provider.getColor(JavaColorProvider.MULTI_LINE_COMMENT))));
-	reconciler.setDamager(dr, JavaPartitionScanner.JAVA_MULTILINE_COMMENT);
-	reconciler.setRepairer(dr, JavaPartitionScanner.JAVA_MULTILINE_COMMENT);
-
-	return reconciler;
-</pre>
-<p> Note that the example provide scanners for each content type.&nbsp;&nbsp;</p>
-<p>The default content type is set up with a <b>JavaCodeScanner</b> so that
-keywords can be detected and colored.&nbsp; The <b>JavaCodeScanner</b> builds
-rules for detecting different kinds of tokens, such as single line comments,
-white space, and words.&nbsp; It describes the colors that should be used for
-words of different token types.&nbsp;&nbsp;&nbsp;</p>
-<p>The other content types are set up with a <b>SingleTokenScanner</b> and given
-a color to be used for tokens in these content types.</p>
-<p>All of the details for damaging and repairing the proper parts of the
-documents according to the scanning rules are handled by <b><a href="../reference/api/org/eclipse/jface/text/rules/DefaultDamagerRepairer.html">DefaultDamagerRepairer</a></b>.&nbsp;
-These details typically don't need to be understood by plug-in code.&nbsp; Your
-plug-in should focus on building a set of rules that are appropriate for
-partitioning and scanning its editor content.</p>
-<h4>Dynamically installing a reconciler</h4>
-<p>The Java editor example provides a subclass of <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a>
-</b> for installing the presentation reconciler as seen earlier.&nbsp; A
-presentation reconciler can also be installed dynamically on a text viewer using
-<b><a href="../reference/api/org/eclipse/jface/text/presentation/IPresentationRepairer.html">IPresentationReconciler</a></b>
-protocol.&nbsp; There is no
-particular runtime benefit to doing it either way, but putting all of the
-pluggable behavior overrides in a subclass of <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a>
-</b>provides the advantage of consolidating all of the behavioral overrides in one place.&nbsp;
-The dynamic protocol may be useful when different presentation reconcilers are
-attached to a viewer throughout the life of an editor.</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors_hover.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors_hover.htm
deleted file mode 100644
index 845ed4f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors_hover.htm
+++ /dev/null

@@ -1,118 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Text and ruler hover
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>Text and ruler hover</H2>
-<p>Hover support is provided in the platform text framework, allowing you to implement 
-  informational hovers (or infopops) over the text and the rulers shown in your 
-  editor.</p>
-<p>Hover support is optional.&nbsp; By default, <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a>
-</b>does not install hover behavior since there is no useful general information
-to show.&nbsp; In order to provide text or ruler hover, your editor's source
-viewer configuration must be <a href="editors_sourceviewers.htm">configured</a>
-to define a pluggable hover object.</p>
-<p>Let's look again at <b>JavaSourceViewerConfiguration</b>
- to see which methods define the hover behavior:</p>
-
-<pre>public ITextHover getTextHover(ISourceViewer sourceViewer, String contentType) {
-	return new JavaTextHover();
-}
-public IAnnotationHover getAnnotationHover(ISourceViewer sourceViewer) {
-	return new JavaAnnotationHover();
-}
-</pre>
-<p>Hover helper classes can also be installed dynamically using <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewer.html">SourceViewer</a></b>
- protocol (<b>setTextHover</b> and <b>setAnnotationHover</b>).&nbsp; There is no
-particular runtime benefit to doing it either way, but putting all of the
-pluggable behavior overrides in a subclass of <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a>
-</b>provides the advantage of consolidating all of the definitions in one place.</p>
-<p>Let's look at the specifics of providing both kinds of hover.</p>
-<h3>Text hover</h3>
-<p>Text hover allows you to provide informational text about text shown in the 
-  editor.&nbsp; This is done using the <b><a href="../reference/api/org/eclipse/jface/text/ITextHover.html">ITextHover</a></b> 
-  interface.&nbsp; A text hover is responsible for computing the region that should 
-  be used as the source of hover information, given an offset into the document.&nbsp; 
-  It is also responsible for providing the informational text about a specific 
-  region.&nbsp; <b>JavaTextHover</b> is pretty simple.&nbsp; It checks to see 
-  if the supplied offset for hover is contained inside the text selection.&nbsp;&nbsp;&nbsp; 
-  If so, it supplies the selection range as hover region.&nbsp;</p>
-
-<pre>public class JavaTextHover implements ITextHover {
-
-	...
-	
-	public IRegion getHoverRegion(ITextViewer textViewer, int offset) {
-		Point selection= textViewer.getSelectedRange();
-		if (selection.x &lt;= offset &amp;&amp; offset &lt; selection.x + selection.y)
-			return new Region(selection.x, selection.y);
-		return new Region(offset, 0);
-	}
-}</pre>
-<p>Given its own computed hover region, it obtains the selected text from its
-document and returns that as the hover info.</p>
-
-<pre>public class JavaTextHover implements ITextHover {
-
-	public String getHoverInfo(ITextViewer textViewer, IRegion hoverRegion) {
-		if (hoverRegion != null) {
-			try {
-				if (hoverRegion.getLength() &gt; -1)
-					return textViewer.getDocument().get(hoverRegion.getOffset(), hoverRegion.getLength());
-			} catch (BadLocationException x) {
-			}
-		}
-		return JavaEditorMessages.getString(&quot;JavaTextHover.emptySelection&quot;); 
-	}
-	...
-}</pre>
-<p>Sure enough, we can see that if we hover over a selection in the editor, the
-hover text shows the selection.</p>
-<p><img src="images/javatexthover.png" alt="Hover information on selected region" border="0"></p>
-<p>More complicated contextual information can be used to compute useful hover
-information.&nbsp; Examples of this can be found in the <b>JavaTextHover</b>
-implemented with the JDT editor.</p>
-<h3>Ruler hover</h3>
-<p>Hover on the vertical ruler is useful for showing show line-oriented information.&nbsp;
-The hover class is configured as described above.&nbsp; <b><a href="../reference/api/org/eclipse/jface/text/source/IAnnotationHover.html">IAnnotationHover</a></b>
-is the interface for ruler hover objects.&nbsp; Although the name implies that
-the hover is designed for annotations in the ruler, it is really up to an
-individual editor to detemine what is appropriate.&nbsp; A ruler hover is responsible for returning the info string associated with a
-particular line number, regardless of the presence of markers on that line.&nbsp;&nbsp;&nbsp;</p>
-<p>The Java example editor's <b>JavaAnnotationHover</b>  implements hover for
-all lines.&nbsp; It uses the line number to
-obtain all of the text on the hover line and returning it as the info string.</p>
-
-<pre>public String getHoverInfo(ISourceViewer sourceViewer, int lineNumber) {
-	IDocument document= sourceViewer.getDocument();
-
-	try {
-		IRegion info= document.getLineInformation(lineNumber);
-		return document.get(info.getOffset(), info.getLength());
-	} catch (BadLocationException x) {
-	}
-	return null;
-}</pre>
-<p><img src="images/javarulerhover.png" alt="Hover information on ruler" border="0"></p>
-<p>Since the hover has access to the document and the
-source viewer, it has all the context needed to make more complicated contextual
-decisions about the info that should be shown.&nbsp; For example, the annotation
-model could be retrieved from the source viewer in order to provide hover info
-for any annotations shown in the vertical ruler.&nbsp; The <b>JavaAnnotationHover</b>
-provided by the JDT editor provides this capability.
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors_jface.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors_jface.htm
deleted file mode 100644
index c98e8f3..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors_jface.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Text editors and platform text
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2 CLASS="Heading2">Text editors and platform text</H2>
-<p>The platform text facility is used to implement the default text editor for
-the workbench.&nbsp; The interface for text editing is defined in <a href="../reference/api/org/eclipse/ui/texteditor/ITextEditor.html"><b>ITextEditor</b></a>
- as a text specific extension of <a href="../reference/api/org/eclipse/ui/IEditorPart.html"><b>IEditorPart</b></a>.&nbsp;&nbsp;</p>
-<p>The implementation of <a href="../reference/api/org/eclipse/ui/texteditor/ITextEditor.html"><b>ITextEditor</b></a>
-in the platform is structured in layers.&nbsp; <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html"><b>AbstractTextEditor</b></a>
-is the core class of the framework for extending the editor to support source code style
-editing of text.&nbsp; This framework is defined in <a href="../reference/api/org/eclipse/ui/texteditor/package-summary.html"><b>org.eclipse.ui.texteditor</b></a>.</p>
-<p>The concrete implementation class <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a>
-defines the behavior for the standard platform text editor.&nbsp; It is
-defined in the package <b><a href="../reference/api/org/eclipse/ui/editors/text/package-summary.html">org.eclipse.ui.editors.text</a></b>.</p>
-<p>The text editor framework provides a model-independent editor that
-supports the following features:</p>
-<ul>
-  <li>presentation and user modification of text</li>
-  <li>standard text editing operations such as cut/copy/paste, find/replace</li>
-  <li>support for context and pulldown menus</li>
-  <li>visual presentation of text annotations in rulers or as squigglies in the
-    text</li>
-  <li>automatic update of annotations as the user edits text</li>
-  <li>presentation of additional information such as line numbers</li>
-  <li>syntax highlighting</li>
-  <li>content assist</li>
-  <li>text outlining pages that show the hierarchical structure of the text</li>
-  <li>context sensitive behavior</li>
-  <li>hover support over rulers and text</li>
-  <li>key binding contexts</li>
-  <li>preference handling</li>
-</ul>
-<p>We will explore how these features can be implemented in an editor by
-studying the <b>org.eclipse.ui.examples.javaeditor</b>
- example.&nbsp; This example shows how complex features like text coloring, hover help, and
-automatic indenting can be implemented.&nbsp; </p>
-<p>In discussing these features we will be moving between the abstract
-framework, the platform editor <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a>,
-and the example's subclass, <b>JavaEditor</b>.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors_sourceviewers.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors_sourceviewers.htm
deleted file mode 100644
index 2b95ea9..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors_sourceviewers.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Configuring a source viewer
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>Configuring a source viewer</H2>
-<p>So far we've looked at <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewer.html">SourceViewer</a></b>
- in the context of managing source code annotations.</p>
-<p>The <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewer.html">SourceViewer</a></b> 
-  is also the central hub for configuring your editor with pluggable behavior 
-  such as text hovering and syntax highlighting.&nbsp; &nbsp;For these features, the editor 
-  supplies a <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a> 
-  </b>that is used to configure the <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewer.html">SourceViewer</a></b> 
-  when it is created.&nbsp; The Java example editor need only to supply a <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a> 
-  </b>appropriate for its needs.&nbsp; The following snippet shows how the <b>JavaTextEditor</b> 
-  creates its configuration:</p>
-<pre>
-protected void initializeEditor() {
-	super.initializeEditor();
-	<b>setSourceViewerConfiguration(new JavaSourceViewerConfiguration());</b>
-	...
-</pre>
-<p>What does the <b>JavaSourceViewerConfiguration</b> do?&nbsp; Much of its
-behavior is inherited from <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a></b>,
-which defines default strategies for pluggable editor behaviors such as auto
-indenting, undo behavior, double-click behavior, text hover, syntax
-highlighting, and formatting.&nbsp; Public methods in <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a>
-</b>provide the helper objects that implement these behaviors.
- </p>
-<p>If the default behavior defined in <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a></b>
-does not suit your editor, you should override <b>initializeEditor() </b>as
-shown above and set your own source viewer configuration into the editor.&nbsp;
-Your configuration can override methods in <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a></b>
-to supply customized helper objects that implement behavior for your
-editor.&nbsp; The following snippet shows two of the ways the <b>JavaSourceViewerConfiguration</b>
-supplies customized helper objects for the Java editor example:
- </p>
-
-<pre>public IAnnotationHover getAnnotationHover(ISourceViewer sourceViewer) {
-	return new JavaAnnotationHover();
-}
-	
-public IAutoIndentStrategy getAutoIndentStrategy(ISourceViewer sourceViewer, String contentType) {
-	return (IDocument.DEFAULT_CONTENT_TYPE.equals(contentType) ? new JavaAutoIndentStrategy() : new DefaultAutoIndentStrategy());
-}</pre>
-<p>In the first method, a customized helper class is provided for implementing 
-  annotation hovering.&nbsp; In the second method, the default content type of 
-  the document is queried to determine whether a customized auto-indent strategy 
-  or the default strategy should be used. </p>
-<p>See the API reference for <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a></b>
-for all the ways you can configure a source viewer by overriding methods.
- </p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors_utilities.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors_utilities.htm
deleted file mode 100644
index 718d975..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors_utilities.htm
+++ /dev/null

@@ -1,92 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Other text editor responsibilities
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>Other text editor responsibilities</H2>
-<p>The Java example editor inherits a lot of useful default behavior from <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html"><b>AbstractTextEditor</b></a>.&nbsp;
-The text editing framework handles several other responsibilities that you can
-customize by overriding methods in <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html"><b>AbstractTextEditor</b></a>.&nbsp;
-Browse the implementation of this class and its subclasses to see how behavior
-is customized in the framework.</p>
-<p>The following are some of the useful framework features that can be
-configured.</p>
-<h3>Preference handling</h3>
-<p>Text editors typically contribute user preferences that control the
-presentation and behavior of the editor.&nbsp; In the text framework, each text
-editor instance has an associated preference store that is used for accessing
-user preferences.&nbsp; This preference store can be set up by your editor, or
-you can inherit from preference stores already used in the framework.</p>
-<p>In the case of the Java example editor, it inherits the preference store
-initialized by <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a>.&nbsp;
-This is the preference store defined by the workbench editors
-plug-in.&nbsp;&nbsp;</p>
-
-<pre>protected void initializeEditor() {
-	...
-	setPreferenceStore(EditorsPlugin.getDefault().getPreferenceStore());
-}</pre>
-
-The editors plug-in preferences can be manipulated in the <b>General &gt;
-Editors</b> and <b>General &gt; Editors &gt; Text Editors</b> preference pages.
-<p>If you do not want to use the standard workbench text preferences for your 
-  editor, you can set a different preference store.&nbsp; This is typically done 
-  by overriding <b>initializeEditor</b> and setting your own preference store.&nbsp; 
-  If you do use your own preference store, you will also need to override the 
-  method <b>handlePreferenceStoreChanged()</b> which is triggered whenever a preference 
-  is updated.</p>
-<h3>Key bindings</h3>
-<p><a href="wrkAdv_keyBindings_contexts.htm">Key binding contexts</a> are useful
-for establishing a lookup order for key bindings. Having contextual key bindings
-reduces the chances of different plug-ins contributing conflicting key
-sequences.  By default, the workbench operates in a generic context for working with 
-windows or dialogs.  When a text editor becomes active, it is responsible
-for resetting the context to the text editing context, so that editor specific key
-bindings will be active.</p>
-
-<p>In the platform text framework, each text editor instance has an associated array of
-key binding scopes. It is responsible for setting the correct scopes when it becomes 
-  active. <a href="../reference/api/org/eclipse/ui/texteditor/AbstractDecoratedTextEditor.html"><b>AbstractDecoratedTextEditor</b></a> 
-  defines this scope and takes care of making it active. The scope is assigned 
-  in a method that is called from the constructor:</p>
-
-<pre>protected void initializeKeyBindingScopes() {
-	setKeyBindingScopes(new String[] { &quot;org.eclipse.ui.textEditorScope&quot; });  
-}</pre>
-
-<p>The argument to the method is an array of ids that have been defined for contexts.
-If you want your editor to define its own key binding context, then you can
-override this method in your editor class, or set the scope dynamically using <b>setKeybindingScopes</b>.</p>
-<p>The context itself must be defined with the corresponding id in the <b><a href="../reference/extension-points/org_eclipse_ui_contexts.html">org.eclipse.ui.contexts</a></b>
-extension point. The following is the definition for the text editing context.</p>
-<pre>
-&lt;extension
-	point=&quot;org.eclipse.ui.contexts&quot;&gt;
-	&lt;context
-		name=&quot;%context.editingText.name&quot;
-		description=&quot;%context.editingText.description&quot;
-		id=&quot;org.eclipse.ui.textEditorScope&quot;
-		parentId=&quot;org.eclipse.ui.contexts.window&quot;&gt;
-	&lt;/context&gt;
-	...
-</pre>
-<p>(Note:&nbsp; We use the terms <b>scope</b> and <b>context</b> interchangeably in this
-discussion.  The method names in the text classes still refer to key binding contexts
-as scopes.  These method names reflect the original implementation of contexts as scopes 
-and use outdated terminology.)</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors_workbench.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors_workbench.htm
deleted file mode 100644
index 19c12aa..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors_workbench.htm
+++ /dev/null

@@ -1,81 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Workbench editors
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Workbench editors</H2>
-<P >
-Although the implementation of a workbench editor will be specific to your plug-in and the 
-content that you want to edit, the workbench provides a general structure for building an 
-editor.  The following concepts apply to all workbench editors.</P>
-
-<h3 >
-Editor parts and their inputs</h3>
-
-<P >
-An editor must implement <a href="../reference/api/org/eclipse/ui/IEditorPart.html"><b>IEditorPart</b></a>
-and is often built by extending the <a href="../reference/api/org/eclipse/ui/part/EditorPart.html"><b>EditorPart</b></a>
-class.&nbsp; An editor implements its user interface in the <b>createPartControl</b>
-method.&nbsp; This method is used to assemble the SWT widgets or JFace viewers
-that present the editor contents.&nbsp;</P>
-
-<P >
-An <b> editor input</b> is a description of something to be edited. You can think of
-an editor input as a file name, though it is more general.
-<a href="../reference/api/org/eclipse/ui/IEditorInput.html"> <b> IEditorInput</b></a> defines the protocol for an editor input, including the name of the input and the image that should be used to represent it in
-the labels at the top of the editor.</P>
-
-<P >
-<img src="images/editorInputLabel.png" alt="Editor input label" border="0"></P>
-<P >
-Two generic editor inputs are provided in the platform. <a href="../reference/api/org/eclipse/ui/IFileEditorInput.html"><b> IFileEditorInput</b></a> represents an input
-that is a file in the file system.&nbsp;
-<a href="../reference/api/org/eclipse/ui/IStorageEditorInput.html"><b>IStorageEditorInput</b></a> represents an input
-that is a stream of bytes. These bytes may come from sources other than the file system.</P>
-
-
-<h3 >
-Resetting the editor input</h3>
-
-
-<P >If your editor can support the replacement of the
-editor's input object on the fly, you should implement&nbsp; <a href="../reference/api/org/eclipse/ui/IReusableEditor.html"><b>IReusableEditor</b></a>.
-Implementing this interface allows the workbench to &quot;recycle&quot; your
-editor.&nbsp; Workbench user preferences allow the user to dictate that editors
-should be reused after a certain number of them are open.</P>
-
-
-<h3 >
-Navigating the editor input&nbsp;</h3>
-
-
-<p>If you want to implement a navigation history in your editor, you should
-implement <a href="../reference/api/org/eclipse/ui/INavigationLocationProvider.html"><b>INavigationLocationProvider</b></a>.&nbsp;
-This provides a mechanism for the workbench to request a current navigation
-location (<a href="../reference/api/org/eclipse/ui/INavigationLocation.html"><b>INavigationLocation</b></a>)
-as needed to keep a navigation history.&nbsp; The workbench handles the
-mechanics of the navigation user interface.&nbsp; Your <a href="../reference/api/org/eclipse/ui/INavigationLocation.html"><b>INavigationLocation</b></a>
-will be notified when it needs to restore the editor to the location that it represents.</p>
-
-
-<P >The rest of your editor's implementation depends on the content that you are
-trying to present.&nbsp; We'll look next at the most common type of editor - the
-text editor.</P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors_workbench_outliner.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors_workbench_outliner.htm
deleted file mode 100644
index 567e589..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors_workbench_outliner.htm
+++ /dev/null

@@ -1,140 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Content outliners</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-<h2>
-Content outliners</h2>
-<P >
-Editors often have corresponding <b>content outliners</b> that provide a
-structured view of the editor contents and assist the user in navigating through
-the contents of the editor.</P>
-<P >
-The workbench provides a standard <b>Outline</b> view for this purpose.&nbsp;
-The workbench user controls when this view is visible using the <b>Window &gt; Show
-View</b> menu.</P>
-<P >Since the generic
-<a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b> TextEditor</b></a> 
-doesn't know anything about the structure of its text, it cannot provide
-behavior for an interesting outline view.&nbsp; Therefore, the default <b>Outline</b> view,
-shown below, doesn't
-do much.</P>
-<P ><img src="images/genericoutliner.png" alt="Default content outliner" border="0"></P>
-<P >&nbsp;</P>
-<P >Editors in the text framework can supply their own content outliner page to the
-outline view.&nbsp; The outliner for an editor is specified when the workbench requests an
-adapter of type <b><a href="../reference/api/org/eclipse/ui/views/contentoutline/IContentOutlinePage.html">IContentOutlinePage</a></b>.</P>
-<pre>
-public Object getAdapter(Class required) {
-	if (IContentOutlinePage.class.equals(required)) {
-		if (fOutlinePage == null) {
-			fOutlinePage= new <b>JavaContentOutlinePage</b>(getDocumentProvider(), this);
-			if (getEditorInput() != null)
-				fOutlinePage.setInput(getEditorInput());
-		}
-		return fOutlinePage;
-	}
-	return super.getAdapter(required);
-}
-</pre>
-
-
-<P >A content outliner page must implement <b><a href="../reference/api/org/eclipse/ui/views/contentoutline/IContentOutlinePage.html">IContentOutlinePage</a></b>.&nbsp;
-This interface combines the ability to notify selection change listeners (<a href="../reference/api/org/eclipse/jface/viewers/ISelectionProvider.html"><b>ISelectionProvider</b></a>)
-with the behavior of being a page in a view (<a href="../reference/api/org/eclipse/ui/part/IPage.html"><b>IPage</b></a>).&nbsp;
-Content outliners are typically implemented using JFace viewers.&nbsp; The
-default implementation of a content outliner (<b><a href="../reference/api/org/eclipse/ui/views/contentoutline/ContentOutlinePage.html">ContentOutlinePage</a></b>)
-uses a JFace tree viewer to display a hierarchical representation of the
-outline.&nbsp; This representation is suitable for many structured outliners, including
-<b>JavaContentOutlinePage</b>.</P>
-
-
-<P >Let's take a look at the implementation of the page. When the outline page 
-  is created by the editor in the snippet above, its input element is set to the 
-  editor's input element.&nbsp; This input can often be passed directly to the 
-  outline page's viewer, as is done below.</P>
-
-
-<pre>
-public void createControl(Composite parent) {
-
-	super.createControl(parent);
-
-	TreeViewer viewer= getTreeViewer();
-	viewer.setContentProvider(new ContentProvider());
-	viewer.setLabelProvider(new LabelProvider());
-	viewer.addSelectionChangedListener(this);
-
-	if (fInput != null)
-		viewer.setInput(fInput);
-}
-</pre>
-
-
-<P >The tree viewer creation is inherited from <b><a href="../reference/api/org/eclipse/ui/views/contentoutline/ContentOutlinePage.html">ContentOutlinePage</a></b>.&nbsp; 
-  The standard label provider is used.  The content provider is provided inside
-   <b>JavaContentOutlinePage</b> and is responsible for parsing the editor input into
-   individual segments whenever it changes.</P>
-
-
-<pre>
-		public void inputChanged(Viewer viewer, Object oldInput, Object newInput) {
-			...
-			if (newInput != null) {
-				IDocument document= fDocumentProvider.getDocument(newInput);
-				if (document != null) {
-					document.addPositionCategory(SEGMENTS);
-					document.addPositionUpdater(fPositionUpdater);
-					parse(document);
-				}
-			}
-		}
-</pre>
-
-
-<P >The text is parsed into ranges, called segments, within the document.&nbsp;
-These segments are displayed by name in the outline view.</P>
-
-
-<P ><img src="images/javacontentoutline.png" alt="Java example outliner" border="0"></P>
-
-
-<P >When the selection changes, the selected segment is 
-  retrieved.&nbsp; Its offsets are used to set the highlight range in the editor.</P>
-
-
-<pre>
-public void selectionChanged(SelectionChangedEvent event) {
-
-	super.selectionChanged(event);
-
-	ISelection selection= event.getSelection();
-	if (selection.isEmpty())
-		fTextEditor.resetHighlightRange();
-	else {
-		Segment segment= (Segment) ((IStructuredSelection) selection).getFirstElement();
-		int start= segment.position.getOffset();
-		int length= segment.position.getLength();
-		try {
-			fTextEditor.setHighlightRange(start, length, true);
-		} catch (IllegalArgumentException x) {
-			fTextEditor.resetHighlightRange();
-		}
-	}
-}
-</pre>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin.htm b/bundles/org.eclipse.platform.doc.isv/guide/firstplugin.htm
deleted file mode 100644
index f85dd32..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Simple plug-in example</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Plug it in: Hello World meets the workbench</H1>
-<P >
-The Eclipse platform is structured as a core runtime engine and a set of additional features that are installed as platform
-<b>plug-ins</b>. Plug-ins contribute functionality to the platform by contributing to pre-defined
-<b> extension points</b>. The workbench UI is contributed by one such plug-in. When you start up the workbench, you are not starting up a single Java program. You are activating a platform runtime which can dynamically discover registered plug-ins and start them as needed.</P>
-<P >
-When you want to provide code that extends the platform, you do this by defining
-system extensions in your plug-in. The platform has a well-defined set of extension
-points - places where you can hook into the platform and contribute system behavior. From the platform's perspective, your plug-in is no different
-than basic plug-ins like the resource management system or the workbench itself.</P>
-<P >
-So how does your code become a plug-in?&nbsp;</P>
-<ul>
-  <li>Decide how your plug-in will be integrated with the platform.</li>
-  <li>Identify the extension points that you need to contribute in order to
-    integrate your plug-in.</li>
-  <li>Implement these extensions according to the specification for the
-    extension points.</li>
-  <li>Provide a manifest file (manifest.mf) that describes the packaging and
-  prerequisites for your code, and a plug-in manifest (plugin.xml) that
-  describes the extensions you are defining.</li>
-</ul>
-<P >
-The process for creating a plug-in is best demonstrated by implementing an old classic, 
-&quot;Hello World,&quot; as a plug-in.  The intention of this example is to give you a flavor
-of how plug-in development is different from Java application development.  We'll gloss over a 
-lot of details in order to get the plug-in built and running.  Then we'll look at extension
-points in more detail, see where they are defined, and learn how plug-ins describe their implementation of an extension.</P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_btb.htm b/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_btb.htm
deleted file mode 100644
index 56aecb1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_btb.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Beyond the basics
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Beyond the basics</H2>
-<P >
-Hopefully you've gotten a flavor of how you can contribute code in the form of an extension, and package
-that functionality into a plug-in.  From here, you can start diving into more detail:</P>
-<ul>
-  <li><a href="workbench_basicext.htm">Basic workbench extension points</a></li>
-  <li><a href="workbench_menus.htm">Workbench menu contributions</a></li>
-  <li><a href="wrkAdv.htm">Advanced workbench concepts</a></li>
-  <li><a href="dialogs_wizards_extensions.htm">Workbench wizard extension points</a></li>
-</ul>
-<P >
-A complete list of extension points can be found in the <a href="../reference/extension-points/index.html">Platform
-Extension Point Reference</a>.</P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_create.htm b/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_create.htm
deleted file mode 100644
index 595bf9f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_create.htm
+++ /dev/null

@@ -1,73 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Creating the plug-in project
-</TITLE>
-
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Creating the plug-in project</H2>
-
-<P >You can use any Java IDE you wish to build Eclipse plug-ins, but of course the
-  Eclipse SDK provides tooling specific for plug-in development.  We'll walk 
-  through the steps for building our plug-in with the Eclipse SDK, since this is the 
-  typical case. If you are not already familiar with the Eclipse workbench and the Java IDE, 
-  consult the Java Development User Guide or PDE Guide for further explanations of the steps 
-  we are taking. For now we are focusing on the code, not the tool; 
-  however, there are some IDE logistics for getting started.</P>
-<h3>Creating your plug-in project</h3>
-<p>You will need to create a project that contains your work.  We'll take advantage of some of the
-code-generation facilities of the Plug-in Development Environment (PDE) to give us a template to
-start from.  This will set up the project for writing Java code and generate the default plug-in 
-manifest files (explained in a moment) and a class to hold our view.
-</p>
-<ol>
-  <li>Open the <b>New Project...</b> wizard (<strong>File &gt; New &gt; Project...</strong>) 
-    and choose <b>Plug-in Project </b>from the <b>Plug-in Development</b> category
-     and click <strong>Next</strong>.</li>
-  <li>On the <strong>Plug-in Project </strong> page, use <b>com.example.helloworld</b> 
-    as the name for your project and check the box for <strong>Create a Java project</strong> 
-    (this should be the default).  Leave the other settings on the page with their default
-    settings and then click <strong>Next</strong> to accept the default plug-in project structure.</li>
-  <li>On the <strong>Plug-in Content</strong> page, look at the default settings.  The wizard sets <strong>com.example.helloworld</strong> 
-    as the id of the plug-in.&nbsp; The wizard will also generate a plug-in class for your plug-in and allow you to supply additional information about
-    contributing to the UI.  These defaults are acceptable, so click <strong>Next</strong>.  </li>
-  <li>On the <strong>Templates</strong> page, check the box for <strong>Create a plug-in using one of the templates</strong>.  Then
-    select the <strong>Plug-in with a view</strong> template.  Click <strong>Next</strong>.  </li>
-  <li>We want to create a minimal plug-in, so at this point we need to change the default settings to keep things as
-    simple as possible.  On the <strong>Main View Settings</strong> page, change the suggested defaults as follows:
-    <img border="0" src="images/firstpluginpde.png" alt="Plug-in view settings" >
-    <ul>
-    <li>Change the <strong>Java Package Name</strong> from <strong>com.example.helloworld.views</strong> to <strong>com.example.helloworld</strong>
-    (we don't need a separate package for our view).</li>
-    <li>Change the <strong>View Class Name</strong> to <strong>HelloWorldView</strong>.</li>
-    <li>Change the <strong>View Name</strong> to <strong>Hello View</strong>.</li>
-    <li>Leave the default <strong>View Category Id</strong> as <strong>com.example.helloworld</strong>.</li>
-    <li>Change the <strong>View Category Name</strong> to <strong>Hello Category</strong>.</li>
-    <li>Leave the default viewer type as <strong>Table viewer</strong> (we will change this in the code to make it even simpler).</li>
-    <li>Uncheck the box for <strong>Add the view to the resource perspective</strong>.</li>
-    <li>Click <strong>Next</strong> to proceed to the next page.</li>
-    </ul></li>
-  <li>On the <strong>View Features</strong> page, uncheck all of the boxes so that no extra
-    features are generated for the plug-in.  Click <strong>Finish</strong> to create the project and the plug-in skeleton.  </li>
-  <li>When asked if you would like to switch to the Plug-in Development perspective, 
-    answer <strong>Yes</strong>.</li>
-  <li>Navigate to your new project and examine its contents.</li>
-</ol>
-<p>The skeleton project structure includes several folders, files, and a Java package.  The important files at this stage are the
-<strong>plugin.xml</strong> and <strong>MANIFEST.MF</strong> (manifest) files and the Java source code for your plug-in.  
-We'll start by looking at the implementation for a view and then
-examine the manifest files.</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_manifest.htm b/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_manifest.htm
deleted file mode 100644
index ae26e28..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_manifest.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-The Hello World manifests
-</TITLE>
-
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>The Hello World manifests</H2>
-
-<p>Before we run the new view, let's take a look at the manifest files that were 
-generated for us. First, double-click the plugin.xml file to open the plug-in
-editor and select the <strong>plugin.xml</strong> tab.</p>
-<pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
-&lt;?eclipse version=&quot;3.0&quot;?&gt;
-&lt;plugin&gt;
-	&lt;extension point=&quot;org.eclipse.ui.views&quot;&gt;
-		&lt;category
-			name=&quot;Hello Category&quot;
-			id=&quot;com.example.helloworld&quot;&gt;
-		&lt;/category&gt;
-		&lt;view
-			name=&quot;Hello View&quot;
-			icon=&quot;icons/sample.gif&quot;
-			category=&quot;com.example.helloworld&quot;
-			class=&quot;com.example.helloworld.HelloWorldView&quot;
-			id=&quot;com.example.helloworld.HelloWorldView&quot;&gt;
-		&lt;/view&gt;
-	&lt;/extension&gt;
-&lt;/plugin&gt;
-</pre>
-<p>
-The information about the view that we provided when we created the plug-in project was used to generate
-an entry in the plugin.xml file that defines our view extension.  In the extension definition,
-we define a <b>category</b> for the view, including its <b>name</b> and <b>id</b>.  We then define the view 
-itself, including its <b>name</b> and <b>id</b>, and we associate it with the <b>category</b> using the id we
-defined for our category.  We also specify the <b>class</b> that implements our view, <b>HelloWorldView</b>. 
-</p>
-<p>
-As you can see, the plug-in manifest file wraps up all the information about our extension and how to run it into
-a nice, neat package.
-</p>
-<p>The other manifest file that is generated by the PDE is the OSGi manifest, MANIFEST.MF.  This file is created
-in the META-INF directory of the plug-in project, but is most easily viewed by clicking on the
-<strong>MANIFEST.MF</strong> tab of the plug-in editor.  The OSGi manifest describes lower-level information
-about the packaging of the plug-in, using the OSGi bundle terminology.  It contains information such as
-the name of the plug-in (bundle) and the bundles that it requires.
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_minimal.htm b/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_minimal.htm
deleted file mode 100644
index e4f3c6b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_minimal.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-A minimal plug-in
-</TITLE>
-
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-A minimal plug-in</H2>
-<P >
-We all know what &quot;Hello World&quot; looks like in plain old Java without using any user interface frameworks or
-other specialized libraries.</P>
-<pre>
-   public class HelloWorld {
-      public static void main(String[] args) {
-         System.out.println(&quot;Hello World&quot;);
-      }
-   }
-</pre>
-<P >
-What happens to this old standard in the context of the Eclipse platform?  Instead of thinking of Hello World as a self-contained program, we recast it as an extension of the platform. Since we want to say hello to the world, we need to figure out how to extend the workbench to include our greeting.</P>
-<P >
-When we get deeper into the platform user interface components, we'll do an exhaustive review of the ways that you can extend and customize the workbench
-UI. For now, let's start with one of the simplest workbench extensions - a view.&nbsp;</P>
-
-<p>You can think of the workbench window as a frame that presents various visual
-parts. These parts fall into two major categories: views and editors.&nbsp; We
-will look at editors later.&nbsp; <b>Views</b>
-provide information about some object that the user is working with in the
-workbench. Views often change their content as the user selects different
-objects in the workbench.</p>
-
-<H3>
-Hello world view</H3>
-<P >
-For our hello world plug-in, we will implement our own view to greet the user with &quot;Hello World.&quot;</P>
-<P >
-The plug-in <b>org.eclipse.ui.workbench</b> defines most of the public interfaces that make up the workbench
-API. These interfaces can be found in the package <b><a href="../reference/api/org/eclipse/ui/package-summary.html"> org.eclipse.ui</a></b>
-and its sub packages.  Many of these interfaces have
-default implementation classes that you can extend to provide simple modifications to the system. In our hello world example, we will extend a workbench view to provide a label that says hello.</P>
-<P >
-The interface of interest is <b><a href="../reference/api/org/eclipse/ui/IViewPart.html">IViewPart</a></b>, which defines the methods that must be implemented to contribute a view to the workbench. The class
-<b><a href="../reference/api/org/eclipse/ui/part/ViewPart.html">ViewPart</a></b> provides a default implementation of this interface. In a nutshell, a view part is responsible for creating the widgets needed to show the view.</P>
-<P > The standard views in the workbench often display some information about 
-  an object that the user has selected or is navigating. Views update their contents 
-  based on actions that occur in the workbench. In our case, we are just saying 
-  hello, so our view implementation will be quite simple.</P>
-<p>
-Before jumping into the code, we need to make sure our environment is set up for plug-in development...
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_run.htm b/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_run.htm
deleted file mode 100644
index 3c7cb26..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_run.htm
+++ /dev/null

@@ -1,76 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Running the plug-in
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Running the plug-in</H2>
-<P > We have all the pieces needed to run our new plug-in. Now we need to build 
-  the plug-in. If your Eclipse workbench is set up to build automatically, then 
-  your new view class should have compiled as soon as you saved the new content. 
-  If not, then select your new project and choose <strong>Project &gt; Build Project</strong>. 
-  The class should compile without error.</p>
-<p>There are two ways to run a plug-in once it has been built.</p>
-<ol>
-<li>The plug-in's manifest files and jar file can be installed in the <strong>eclipse/plugins</strong> directory.  When
-the workbench is restarted, it will find the new plug-in.</li>
-<li>The PDE tool can be used to run another workbench from within your current workbench.  This
-<strong>runtime workbench</strong> is handy for testing new plug-ins immediately as you develop them
-from your workbench.  (For more information about how a runtime workbench works, check the PDE guide.)</li>
-</ol>
-<p>
-For simplicity, we'll run the new plug-in from within the Eclipse workbench. </p>
-<h3>Launching the workbench</h3>
-<p>To launch a runtime workbench, choose <strong>Run &gt; Run...</strong>. This 
-  dialog will show you all the different kinds of ways you can launch a program. 
-  Choose <strong>Eclipse Application</strong>, click <strong>New</strong> and accept all of the default settings. 
-  This will cause another instance of the Eclipse workbench, the runtime workbench, 
-  to start. </p>
-<h3>Running Hello World</h3>
-<P > So where is our new view? We can see all of the views that have been contributed 
-  by plug-ins using the <b>Window &gt; Show View</b> menu.</P>
-
-<img src="images/perspectivemenu.png" alt="" border="0">
-<P >
-This menu shows us what views are available for the current perspective. You can see all of the views that are contributed to the platform (regardless of perspective) by selecting
-<b>Other...</b>. This will display a list of view categories and the views available under each category. </P>
-<P >
-The workbench creates the full list of views by using the extension registry to
-find all the plug-ins that have provided extensions for the
-<a href="../reference/extension-points/org_eclipse_ui_views.html"><b> org.eclipse.ui.views</b></a> extension point. </P>
-
-<img src="images/showview.png" alt="Show View dialog with Hello entry" border="0">
-<P >
-There we are! The view called &quot;Hello View&quot; has been added to the <b> Show View</b> window underneath our category &quot;Hello Category.&quot; The labels for our category and view were obtained from the extension point configuration markup in the
-<b>plugin.xml</b>. </P>
-<P ><i><b>
-Up to this point, we still have not run our plug-in code!&nbsp; </b></i>The
-declarations we made in the <b>plugin.xml</b> (which can be seen by other plug-ins using the extension registry)
-are enough for the workbench to find out that there is a
-view called &quot;Hello View&quot; available in the &quot;Hello&quot; category. It even knows what class 
-implements the view. But none of our code will be run until we decide to
-show the view.</P>
-<P >
-If we choose the &quot;Hello View&quot; view from the <b> Show View</b> list, the
-workbench will activate our plug-in, instantiate and initialize our view class, and show the
-new view in the workbench along with all of the other views. Now our code is running.&nbsp;</P>
-
-<img src="images/workbenchwithhello.png" alt="Workbench with Hello World view" border="0">
-<P >
-There it is, our first plug-in! We'll cover more specifics about UI classes and extension points later on.</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_view.htm b/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_view.htm
deleted file mode 100644
index c12e9f7..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_view.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-The Hello World view
-</TITLE>
-
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-The Hello World view</H2>
-
-<P >Now that we've created a project, package, and view class for our plug-in, we're ready to study some code.&nbsp; Here is everything you need in
-your <b>HelloWorldView</b>.&nbsp; Copy the contents below into the
-class you created, replacing the auto-generated content.&nbsp;</P>
-<pre>
-   package com.example.helloworld;
-
-   import org.eclipse.swt.widgets.Composite;
-   import org.eclipse.swt.widgets.Label;
-   import org.eclipse.swt.SWT;
-   import org.eclipse.ui.part.ViewPart;
-
-   public class HelloWorldView extends ViewPart {
-      Label label;
-      public HelloWorldView() {
-      }
-      public void createPartControl(Composite parent) {
-         label = new Label(parent, SWT.WRAP);
-         label.setText(&quot;Hello World&quot;);
-      }
-      public void setFocus() {
-         // set focus to my widget.  For a label, this doesn't
-         // make much sense, but for more complex sets of widgets
-         // you would decide which one gets the focus.
-      }
-   }
-</pre>
-<P >
-The view part creates the widgets that will represent it in the <b> createPartControl</b> method. In this example, we create an SWT label and set the &quot;Hello World&quot; text into it.  This
-is about the simplest view that can be created.</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms.htm
deleted file mode 100644
index 6310608..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-UI Forms
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-UI Forms</H1>
-<p>UI Forms is an optional Rich Client plug-in based on SWT and JFace that 
-provides the support for creating portable web-style user interfaces across all 
-Eclipse UI categories. It provides a few carefully chosen custom widgets, 
-layouts and support classes required to achieve the desired Web look. Being 
-based on SWT, they are inherently portable across all the platforms where SWT is 
-supported.</p>
-<p>UI Forms break the established expectations on which classes of widgets can 
-be expected in Eclipse workbench UI categories (editors, views, wizards, 
-dialogs). An Eclipse form can appear in any and all of them, expanding the 
-possibilities of the UI developers to use the most appropriate concept for the 
-task regardless where they are.</p>
-<p>Eclipse Forms add the following to make web-style user interfaces possible:</p>
-<ul>
-	<li>A concept of a 'form' that is suitable for inclusion in the content 
-	areas such as views and editors 
-	</li>
-	<li>A toolkit that manages colors, hyperlink groups and other aspects of a 
-	form, as well as serve as a factory for a number of SWT controls 
-	</li>
-	<li>A new layout manager that lays out controls similar to HTML table layout 
-	algorithm 
-	</li>
-	<li>A set of custom control designed to fit in the form (hyperlink, image 
-	hyperlink, scrollable composite, section) 
-	</li>
-	<li>A multi-page editor where each page is a form (e.g. PDE manifest 
-	editors)</li>
-</ul>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_colors.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_colors.htm
deleted file mode 100644
index e9dcba8..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_colors.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Color and font management
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-Color and font management</H1>
-<p align="left">When using forms in a non-trivial way, it is important to share 
-as much as possible to conserve resources. For this reason, color management 
-should be separated from the toolkit when there are more than one form to 
-handle.</p>
-<p align="left">Of course, it is possible to create one toolkit per form, but 
-that is too wasteful if there are many forms. Instead:</p>
-<ul>
-	<li>
-	<p align="left">Create one toolkit for all the forms that have the same life 
-	cycle. For example, if creating a multi-page editor, create one toolkit per 
-	editor and dispose it when editor is disposed. All the pages in the editor 
-	should share this toolkit.</p></li>
-	<li>
-	<p align="left">Create one color manager (<code>FormColors</code>) per 
-	plug-in. When creating the toolkit, pass the color manager to the toolkit. 
-	The toolkit will know that the colors are shared and will not dispose them.</p>
-	</li>
-	<li>
-	<p align="left">Use platform support for fonts and if possible, use <code>
-	JFaceResources</code> predefined fonts. Between default, 'banner' and 
-	'header' fonts, you can accomplish a lot. Using many fonts is very confusing 
-	for the user, and if you do manage your own, you must ensure alternatives 
-	across platforms. The JFace fonts are guaranteed to work on all the 
-	platforms Eclipse ships on.</p></li>
-	<li>
-	<p align="left">Dispose the color manager on plug-in shutdown (don't assume 
-	that plug-in shutdown also means platform shutdown - Eclipse runtime can 
-	uninstall your plug-in dynamically while the platform is still running).</p></li>
-	<li>
-	<p align="left">Use form color manager to allocate all the colors needed by 
-	the forms.</p></li>
-</ul>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_controls.htm
deleted file mode 100644
index fed2988..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls.htm
+++ /dev/null

@@ -1,30 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-UI Forms controls
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-UI Forms controls</H1>
-<p>UI Forms are based on SWT and JFace. Consequently, standard SWT controls are 
-routinely used. However, a few custom controls have been added in order to 
-deliver a rich web-style user interface when combined with the standard SWT 
-control set:</p>
-<ul>
-	<li><a href="forms_controls_form.htm">Form</a></li>
-	<li><a href="forms_controls_link.htm">Hyperlink</a></li>
-	<li>
-	<a href="forms_controls_section.htm">ExpandableComposite and Section</a></li>
-	<li><a href="forms_controls_text.htm">FormText</a></li>
-</ul>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_form.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_form.htm
deleted file mode 100644
index ddca681..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_form.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Form control
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-Form control</H1>
-<p><b>Form</b> is a basic control used to host UI Forms. It provides for setting 
-a title and scrolling the content similar to a Web browser. What makes forms 
-appealing is the fact that the content is an SWT composite that can be used as 
-you would use it in other contexts. For example, consider the following code 
-snippet:</p>
-<blockquote>
-	<pre>public class FormView extends ViewPart {
-	private FormToolkit toolkit;
-	private ScrolledForm form;
-	/**
-	 * The constructor.
-	 */
-	public FormView() {
-	}
-	/**
-	 * This is a callback that will allow us to create the viewer and
-	 * initialize it.
-	 */
-	public void createPartControl(Composite parent) {
-		toolkit = new FormToolkit(parent.getDisplay());
-		form = toolkit.createScrolledForm(parent);
-		form.setText(&quot;Hello, Eclipse Forms&quot;);
-	}
-	/**
-	 * Passing the focus request to the form.
-	 */
-	public void setFocus() {
-		form.setFocus();
-	}
-	/**
-	 * Disposes the toolkit
-	 */
-	public void dispose() {
-		toolkit.dispose();
-		super.dispose();
-	}
-}</pre>
-</blockquote>
-<p>UI Forms manipulate SWT widgets in a number of ways in order to achieve the 
-desired effect. For that reason, controls are typically created using the <code>
-FormToolkit</code>. Normally an instance of a <code>ScrolledForm</code> is 
-created in order to get scrolling. When forms need to be nested, a <code>Form</code> 
-instance provides everything except for scrolling of the form content.</p>
-<p>Form content is rendered below the title. SWT widgets are created in the form 
-using <code>Form.getBody()</code> as a parent.</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_link.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_link.htm
deleted file mode 100644
index ceac3ea..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_link.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Hyperlink control
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-Hyperlink control</H1>
-<p>Hyperlink is a custom widget created to complement the standard SWT widget 
-set when used in the context of UI Forms. Hyperlink is a selectable text control 
-that acts like a Web browser hyperlink:</p>
-<pre>	Hyperlink link = toolkit.createHyperlink(form.getBody(), &quot;Click here.&quot;,
-				SWT.WRAP);
-		link.addHyperlinkListener(new HyperlinkAdapter() {
-			public void linkActivated(HyperlinkEvent e) {
-				System.out.println(&quot;Link activated!&quot;);
-			}
-		});
-		link.setText(&quot;A sample link&quot;);</pre>
-<p>Hyperlinks fire <code>HyperlinkEvent</code> objects when users interact with 
-them. By adding a <code>HyperlinkListener</code>, clients can capture when the 
-mouse enters and exits the link, as well as activates it (either by mouse click 
-or by 'Enter' key).</p>
-<p>Hyperlinks created by the form toolkit are automatically inserted into a <b>
-hyperlink group</b>. <code>HyperlinkGroup</code> manages common hyperlink 
-properties like normal and hover foreground color, underline style etc. for all 
-the links that belong to the group.</p>
-<p>Since many hyperlinks are combined with a small image, UI Forms provide a 
-subclass called <code>ImageHyperlink</code> that add the ability to combine text 
-and image in one clickable control. This class can also be used when a hyperlink 
-image (without text) is needed. If image is not set, <code>ImageHyperlink</code> 
-behaves identically to <code>Hyperlink</code>.</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_section.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_section.htm
deleted file mode 100644
index b534aa1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_section.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Expandable composite and Section controls
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-Expandable composite and Section controls</H1>
-<p><code>ExpandableComposite</code> acts similar to <code>Group</code> control 
-with the ability to collapse a portion of a page a toggle control:</p>
-<div align="left">
-	<pre>	ExpandableComposite ec = toolkit.createExpandableComposite(form.getBody(), 
-					ExpandableComposite.TREE_NODE|
-					ExpandableComposite.CLIENT_INDENT);
-	ec.setText(&quot;Expandable Composite title&quot;);
-	String ctext = &quot;We will now create a somewhat long text so that &quot;+
-	&quot;we can use it as content for the expandable composite. &quot;+
-	&quot;Expandable composite is used to hide or show the text using the &quot;+
-	&quot;toggle control&quot;;
-	Label client = toolkit.createLabel(ec, ctext, SWT.WRAP);
-	ec.setClient(client);
-	ec.addExpansionListener(new ExpansionAdapter() {
-		public void expansionStateChanged(ExpansionEvent e) {
-			form.reflow(true);
-		}
-	});</pre>
-</div>
-<p>The <code>ExpandableComposite</code> control accepts a number of styles that 
-affect its appearance and behavior. Style <code>TREE_NODE</code> will create the 
-toggle control used in a tree widget for expanding and collapsing nodes, while
-<code>TWISTIE</code> will create a triangle-style toggle. Using <code>EXPANDED</code> 
-will create the control in the initial expanded state. If style <code>COMPACT</code> 
-is used, control will report width in the collapsed state enough to fit in the 
-title line only (i.e. when collapsed, it will be as compact horizontally as 
-possible). Finally, <code>CLIENT_INDENT</code> will indent the client to align 
-with the title (otherwise, client will be aligned with the toggle control).</p>
-<p>Expandable composite itself is responsible for rendering the toggle control 
-and the title. The control to expand or collapse is set as a client. Note the 
-requirement that the client is a direct child of the expandable composite.</p>
-<p>Expandable composite fires <code>ExpansionEvent</code> objects when expansion 
-state changes. Adding an expansion listener to the control is needed in order to 
-reflow the form on state change. This is because expansion causes changes in 
-expandable composite size, but the change will not take effect until the next 
-time the parent is laid out (hence we need to force it).</p>
-<p><code>Section</code> is a subclass of the expandable composite that adds 
-additional capabilities. It is typically used to partition a form into a number 
-of sections, each with its own title and optional description. When <code>
-Section.TITLE_BAR</code> or <code>Section.SHORT_TITLE_BAR</code> styles are 
-used, decoration around the title area further enhances the grouping.</p>
-<p>Unlike <code>ExpandableComposite</code>, <code>Section</code> automatically 
-handles reflows on expansion state change. Other interesting uses of the 
-expansion state notification are lazy creation of the Section content that is 
-delayed until the section is expaned.</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_text.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_text.htm
deleted file mode 100644
index c9e0461..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_text.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-FormText control
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-FormText control</H1>
-<p align="left">It is possible to achieve highly polished results using images, 
-hyperlinks and text snippets mixed together in a form. However, when the mix of 
-these elements is needed as part of one integral text, it is very hard to do. To 
-remedy the problem, UI Forms offer a rudimentary text control that can do the 
-following:</p>
-<ul>
-	<li>
-	<p align="left">Render plain wrapped text</p></li>
-	<li>
-	<p align="left">Render plain text but convert any segment that starts with
-	<b>http://</b> into a hyperlink on the flyv</p></li>
-	<li>
-	<p align="left">Render text with XML tags</p></li>
-</ul>
-<p align="left">In all the modes, <code>FormText</code> control is capable of 
-rendering either a string or an input stream.</p>
-<h2 align="left">Rendering normal text (label mode)</h2>
-<div align="left">
-	<pre>	FormText rtext = toolkit.createFormText(form.getBody(), true);
-	String data = &quot;Here is some plain text for the text to render.&quot;;
-	rtext.setText(data, false, false);</pre>
-</div>
-<div align="left">
-	<p align="left">Second argument set to <code>false</code> means that we will 
-	treat input text as-is, and the third that we will not try to expand URLs if 
-	found.</p></div>
-<div align="left">
-	<h2>Automatic conversion of URLs into hyperlinks</h2>
-	<p>It is possible to still handle the text as normal but automatically 
-	convert segments with http:// protocol into hyperlinks:</p>
-	<pre>	FormText rtext = toolkit.createFormText(form.getBody(), true);
-	String data = &quot;Here is some plain text for the text to render; &quot;+
-                       &quot;this text is at http://www.eclipse.org web site.&quot;;
-	rtext.setText(data, false, <b>true</b>);</pre>
-	<p align="left">Similar to the <code>Hyperlink</code> control, <code>
-	FormText</code> accepts listeners that implement <code>HyperlinkListener</code>. 
-	These listeners will be notified about events related to the hyperlink 
-	segments within the control.</p></div>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_text_markup.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_text_markup.htm
deleted file mode 100644
index 64f1bfb..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_text_markup.htm
+++ /dev/null

@@ -1,74 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Parsing formatting markup
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-Parsing formatting markup</H1>
-<p align="left">The most powerful use of the <code>FormText</code> control is 
-when formatting tags are added to the text. The expected root tag is <code>form</code>. 
-It can have one or more children that can either be <code>&lt;p&gt;</code> or <code>&lt;li&gt;</code>. 
-Either of these can have normal text, text between <code>&lt;b&gt;</code> or <code>
-&lt;span&gt;</code> tags, images, links and <code>SWT</code> controls. Images are 
-declared using <code>&lt;img href=&quot;<i>image key</i>&quot;/&gt;</code> (no content), while 
-links are expressed using <code>&lt;a href=&quot;<i>href</i>&quot;&gt;text&lt;/a&gt;</code>.</p>
-<p align="left">Some of the tags mentioned above have additional attributes. Tag
-<code>&lt;a&gt;</code> can accept <code>nowrap=&quot;true&quot;</code> to block the link from 
-being wrapped into the new line. Tag <code>&lt;p&gt;</code> can have attribute <code>
-vspace=&quot;false&quot;</code> (<code>true</code> by default) that adds additional space 
-between paragraphs. Tag <code>&lt;li&gt;</code> has more attributes:</p>
-<ul>
-	<li>
-	<p align="left"><b>style</b> - can be <code>text</code>, <code>bullet</code> 
-	and <code>image</code> (default is <code>bullet</code>)</p></li>
-	<li>
-	<p align="left"><b>value</b> - not used for <code>bullet</code>; if style is
-	<code>text</code>, the value will be rendered instead in place of a bullet; 
-	if style is <code>image</code>, value represents a key in the image table of 
-	an image to be rendered in place of a bullet</p></li>
-	<li>
-	<p align="left"><b>vspace</b> - the same as for the '<code>p</code>' tag.</p>
-	</li>
-	<li>
-	<p align="left"><b>indent</b> - the number of pixels to indent text</p></li>
-	<li>
-	<p align="left"><b>bindent</b> - the number of pixels to indent the bullet 
-	(this number is independent from 'indent' - be careful not to overlap them)</p>
-	</li>
-</ul>
-<p>Tags that affect appearance of the normal text are <code>&lt;b&gt;</code> (works as 
-expected), and <code>&lt;span&gt;</code>. The later allows you to change font and/or 
-color of the text within the tag. Finally, soft line breaks can be added using
-<code>&lt;br/&gt;</code> tag (note that this is XML, so you cannot use open <code>&lt;br&gt;</code> 
-as in HTML).</p>
-<p>Since release 3.1, <code>FormText</code> can be used to mix SWT widgets 
-inside text, hyperlinks and images. SWT controls are created as children of
-<code>FormText</code>, which makes <code>FormText</code> a layout manager of a 
-sort, with instruction on where to place the control relative to text embedded 
-directly in the XML.</p>
-<p>One common theme that can be observed is that <code>FormText</code> is not 
-responsible for loading images, fonts, resolving links or colors. This is not a 
-browser and it is much better to separate concerns and simply assign images and 
-colors managed elsewhere. Both links and images simply have '<code>href</code>' 
-attribute to reference them. For links, the value of this attribute will be 
-provided in the hyperlink event when listeners are notified. Images need to be 
-registered with the text control using the matching 'href' key. This way, the 
-control does not need to worry about loading the images - it has them in the 
-hash table and can render them immediately.</p>
-<p>Similar approach has been used for colors and fonts. Colors are already 
-handled by the toolkit, so you can allocate as many as you want using a unique 
-key and RGB values by calling <code>toolkit.getColors().createColor()</code>. 
-What is left is to set all the colors referenced in the '<code>span</code>' tag 
-so that the control will be able to use them during rendering.</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_editors.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_editors.htm
deleted file mode 100644
index 95655bd..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_editors.htm
+++ /dev/null

@@ -1,98 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Multi-page form editors
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-Multi-page form editors</H1>
-<p align="left">UI Forms provide a basic support for multi-page editors you can 
-build on.</p>
-<p align="left">You should start building a UI Forms multi-page editor by 
-extending <code>FormEditor</code>:</p>
-<blockquote>
-	<pre>public class SimpleFormEditor extends FormEditor {
-
-	public SimpleFormEditor() {
-	}
-
-	protected FormToolkit createToolkit(Display display) {
-		// Create a toolkit that shares colors between editors.
-		return new FormToolkit(ExamplesPlugin.getDefault().getFormColors(
-				display));
-	}
-
-	protected void addPages() {
-		try {
-		addPage(new FreeFormPage(this));
-		addPage(new SecondPage(this));
-		addPage(new ThirdPage(this));
-		addPage(new MasterDetailsPage(this));
-		addPage(new PageWithSubPages(this));
-		}
-		catch (PartInitException e) {
-			//
-		}
-	}
-
-	public void doSave(IProgressMonitor monitor) {
-	}
-
-	public void doSaveAs() {
-	}
-
-	public boolean isSaveAsAllowed() {
-		return false;
-	}</pre>
-</blockquote>
-<p>A very simple way to get started is to create pages and add them as above. 
-Each page need to implement <code>FormPage</code> and override <code>
-createFormContent(IManagedForm managedForm)</code> method. Obviously there is a 
-managed form already created in the page, and you should create contents in the 
-enclosed form, and also register any form part that needs to be part of the 
-managed life cycle.</p>
-<p>In addition to form pages, you can add one or more text editors as a raw 
-source alternative to the GUI pages. For this, you should call '<code>addPage(IEditorPart, 
-IEditorInput input)</code>' method in the superclass.</p>
-<h2 align="left">Recommended practices for Eclipse Forms multi-page editors</h2>
-<p align="left">There are many ways you can go about writing a form-based 
-multi-page editor. It mostly depends on the type of content you are editing and 
-proficiency of your users. There are two ways you can approach it:</p>
-<ol>
-	<li>
-	<p align="left">If the typical users are using the editor infrequently, raw 
-	source is hard to edit by hand or complex, your users are not very technical 
-	etc., you should make COMPLETE pages that are fully capable of editing every 
-	aspect of the content without the need to turn to the raw source. In this 
-	approach, source page is there only for occasional validation, rather than 
-	for regular work. In that respect, you can get away with a basic text 
-	editor. PDE extension point schema editor falls into this group.</p></li>
-	<li>
-	<p align="left">If your users are more technical, have no problem editing 
-	the file by hand but would appreciate some help from time to time, consider 
-	providing a mixed experience - make a good source editor with all the 
-	add-ons like incremental outline, context assist, syntax highlighting etc. 
-	In turn, add complex value-add functionality in the form pages that are hard 
-	to achieve from source. We have learned from experience that it is very hard 
-	to convince seasoned users to switch from source editing if the value-add is 
-	marginal or debatable. However, function that was only available in GUI 
-	pages and was very high-quality was used readily.</p></li>
-</ol>
-<p align="left">Creating a high quality multi-page editor with mixed GUI and 
-source pages has its challenges. Accepting that users will switch pages 
-frequently requires a good model of the underlying content. The model should be 
-directly tied to the underlying document(s) so that it is in sync both when 
-users type in the text directly and when they change it structurally through the 
-GUI pages (don't forget the indirect changes caused by other workbench actions 
-while the editor is still up).</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts.htm
deleted file mode 100644
index fa3d3cf..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-UI Forms Layouts
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-UI Forms Layouts</H1>
-<p align="left">UI Forms offer two new layouts over those provided by SWT. These 
-layouts implement the common interface and can be used on any UI SWT composite, 
-but are typically used in conjunction with UI Forms. The purpose of these 
-layouts is to manage form layout in a way that is similar to Web browsers. 
-Controls are laid out with respect to the form width. The goal is to respect 
-form width as much as possible and compensate by growing the form vertically 
-(and employing scroll bars where needed).</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_column.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_column.htm
deleted file mode 100644
index b92a21e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_column.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-ColumnLayout
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-ColumnLayout</H1>
-<p>Another custom layout in UI Forms is a variation of the <code>RowLayout</code>. 
-If we configure <code>RowLayout</code> to place children vertically (in 
-columns), and to make all controls the same with within the column, we would get 
-several columns (depending on the width of controls), but the last column would 
-typically not be completely filled (depending on the number of controls). Again, 
-if placed in a form, we would get all the controls in one column because <code>
-RowLayout</code> cannot do 'vertical' wrapping. If we use <code>GridLayout</code>, 
-we must choose the number of columns up front and live with the choice.</p>
-<p>There are situations in more complex forms where we want the number of 
-columns to be adaptive. In other words, we would like the number to change 
-depending on the width of the form - use more when possible, drop the number 
-down as the width decreases. We would also like to fill the form area more-less 
-equally (with all the columns roughly the same height). All this can be achieved 
-with <code>ColumnLayout</code>.</p>
-<p>Compared to <code>TableWrapLayout</code>, <code>ColumnLayout</code> is much 
-simpler. Hardly any configuration is needed. The only choice you need to make is 
-the range of columns you want to have (default is 1 to 3).</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_table.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_table.htm
deleted file mode 100644
index a865920..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_table.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-TableWrapLayout
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-TableWrapLayout</H1>
-<p align="left">TableWrapLayout is a grid-based layout very similar to SWT's versatile 
- GridLayout. It differs from GridLayout in that it uses a layout algorithm that 
-works more like HTML tables. It tries to respect the provided client area width 
-and grows vertically to compensate. </p>
-<p align="left">There are many similarities between GridLayout and 
-TableWrapLayout. Both organize children in grids. Both have layout data that 
-instructs the layout how to treat each control. Both can accept hints on which 
-control should grab excess space, etc.</p>
-<p align="left">However, they fundamentally differ in the approach to the 
-layout. <code>TableWrapLayout</code> starts with columns. It computes minimal, 
-preferred and maximum widths of each column and uses this information to assign 
-excess space. It also tries to be fair when dividing space across columns so 
-that there is no excess wrapping of some controls.</p>
-<p align="left">It is possible to mix <code>GridLayout</code> and <code>
-TableWrapLayout</code> but the branch where <code>GridLayout</code> is used is 
-the one where wrapping stops. This is quite acceptable if you don't want it to 
-wrap (if the composite contains controls that cannot wrap anyway, like text, 
-buttons, trees etc.). However, you should have an unbroken path of TableWrapLayouts 
-from the form body to each text control that needs to wrap.</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_managed.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_managed.htm
deleted file mode 100644
index b111604..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_managed.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Managed forms
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-Managed forms</H1>
-<p align="left">Managed forms are wrappers that add life cycle management and 
-notification to form members. Managed form is not a form by itself. It <i>has</i> 
-a form and accepts registration of <code>IFormPart</code> element. For each
-<code>IFormPart</code>, it manages events like dirty state, saving, commit, 
-focus, selection changes etc. In order to reach to the wrapped form widget, call 
-the '<code>getForm()'</code> method.</p>
-<p align="left">There is a similarity between managed forms and JFace viewers - 
-the relationship between a form and a managed form is similar to the one between 
-a <code>Table</code> widget and <code>TableViewer</code> in JFace, for example.</p>
-<p align="left">Not every control on the form needs to be a form part. It is 
-better to group a number of controls and implement <code>IFormPart</code> 
-interface for the group. Section is a natural group and Eclipse Form provides
-<code>SectionPart</code> implementation. It implements the interface and 
-contains a <code>Section</code> instance (either created outside and passed into 
-the constructor, or created in the part itself).</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_master_details.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_master_details.htm
deleted file mode 100644
index 5dcd699..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_master_details.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Master/Details block
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-Master/Details block</H1>
-<p align="left">Master/Details is a pattern used throughout the UI world. It 
-consists of a list or a tree ('master') and a set of properties ('details') 
-driven by the selection in the master. Eclipse Forms provide the implementation 
-of the pattern as a useful building block with the following properties:</p>
-<ul>
-	<li>
-	<p align="left">While details part is created, master part factory method is 
-	abstract and must be implemented by the subclass</p></li>
-	<li>
-	<p align="left">Master and details parts are children of the sash form and 
-	the ratio of the form space allocated for each can be changed by moving the 
-	sash.</p></li>
-	<li>
-	<p align="left">Through the nature of the sash form, master and details 
-	parts can be organized horizontally or vertically in the form.</p></li>
-</ul>
-<p align="left">The idea of master/details block is to create a tree or a table 
-section that fires the selection notification via the managed form. If the 
-details part can handle the selected object, it should switch to the page for it 
-and display properties. When building on top of the provided master/details 
-block, subclasses should:</p>
-<ul>
-	<li>
-	<p align="left">Create the master part (the one that drives the details)</p>
-	</li>
-	<li>
-	<p align="left">Contribute actions to the form tool bar (consumes 
-	upper-right portion of the form in the title area)</p></li>
-	<li>
-	<p align="left">Register details pages, one for each distinct input that can 
-	arrive from the master part</p></li>
-</ul>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/DefaultContextView.PNG b/bundles/org.eclipse.platform.doc.isv/guide/images/DefaultContextView.PNG
deleted file mode 100644
index 631e75d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/DefaultContextView.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/MultiplexAllView.PNG b/bundles/org.eclipse.platform.doc.isv/guide/images/MultiplexAllView.PNG
deleted file mode 100644
index 048cda0..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/MultiplexAllView.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/NameViewNew.PNG b/bundles/org.eclipse.platform.doc.isv/guide/images/NameViewNew.PNG
deleted file mode 100644
index 5df5dc0..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/NameViewNew.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/OverrideInstanceView.PNG b/bundles/org.eclipse.platform.doc.isv/guide/images/OverrideInstanceView.PNG
deleted file mode 100644
index e32f51b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/OverrideInstanceView.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/RedirectAllView.PNG b/bundles/org.eclipse.platform.doc.isv/guide/images/RedirectAllView.PNG
deleted file mode 100644
index 6edb268..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/RedirectAllView.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/RedirectContextView.PNG b/bundles/org.eclipse.platform.doc.isv/guide/images/RedirectContextView.PNG
deleted file mode 100644
index 9280805..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/RedirectContextView.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/about.png b/bundles/org.eclipse.platform.doc.isv/guide/images/about.png
deleted file mode 100644
index 74085f7..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/about.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/actionseteditorretargets.png b/bundles/org.eclipse.platform.doc.isv/guide/images/actionseteditorretargets.png
deleted file mode 100644
index f7cd314..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/actionseteditorretargets.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/actionsetoutlineretargets.png b/bundles/org.eclipse.platform.doc.isv/guide/images/actionsetoutlineretargets.png
deleted file mode 100644
index 807adf5..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/actionsetoutlineretargets.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/actionsets.png b/bundles/org.eclipse.platform.doc.isv/guide/images/actionsets.png
deleted file mode 100644
index 1c8427a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/actionsets.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/arch-npi.jpg b/bundles/org.eclipse.platform.doc.isv/guide/images/arch-npi.jpg
deleted file mode 100644
index 99e4170..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/arch-npi.jpg
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/arch.jpg b/bundles/org.eclipse.platform.doc.isv/guide/images/arch.jpg
deleted file mode 100644
index cdc0386..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/arch.jpg
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/basicIntro.png b/bundles/org.eclipse.platform.doc.isv/guide/images/basicIntro.png
deleted file mode 100644
index c58bfba..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/basicIntro.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/browserexample.png b/bundles/org.eclipse.platform.doc.isv/guide/images/browserexample.png
deleted file mode 100644
index 10f186c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/browserexample.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/cheatsheets.png b/bundles/org.eclipse.platform.doc.isv/guide/images/cheatsheets.png
deleted file mode 100644
index 05678b4..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/cheatsheets.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/common_tab.png b/bundles/org.eclipse.platform.doc.isv/guide/images/common_tab.png
deleted file mode 100644
index b9c2e07..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/common_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/components_diagram.png b/bundles/org.eclipse.platform.doc.isv/guide/images/components_diagram.png
deleted file mode 100644
index 4926714..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/components_diagram.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/composite_view.PNG b/bundles/org.eclipse.platform.doc.isv/guide/images/composite_view.PNG
deleted file mode 100644
index fe3163b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/composite_view.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/cvsdecorators.png b/bundles/org.eclipse.platform.doc.isv/guide/images/cvsdecorators.png
deleted file mode 100644
index 639b5fa..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/cvsdecorators.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/dependencies_view.PNG b/bundles/org.eclipse.platform.doc.isv/guide/images/dependencies_view.PNG
deleted file mode 100644
index 421445c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/dependencies_view.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/editorAction.png b/bundles/org.eclipse.platform.doc.isv/guide/images/editorAction.png
deleted file mode 100644
index 6861c5d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/editorAction.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/editorInputLabel.png b/bundles/org.eclipse.platform.doc.isv/guide/images/editorInputLabel.png
deleted file mode 100644
index 4a8f02a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/editorInputLabel.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/editormenu.png b/bundles/org.eclipse.platform.doc.isv/guide/images/editormenu.png
deleted file mode 100644
index a158e8e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/editormenu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/editoroutlineretargets.png b/bundles/org.eclipse.platform.doc.isv/guide/images/editoroutlineretargets.png
deleted file mode 100644
index 1aa96ac..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/editoroutlineretargets.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/editorretargets.png b/bundles/org.eclipse.platform.doc.isv/guide/images/editorretargets.png
deleted file mode 100644
index 617e2d4..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/editorretargets.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/editortoolbar.png b/bundles/org.eclipse.platform.doc.isv/guide/images/editortoolbar.png
deleted file mode 100644
index 8fb9419..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/editortoolbar.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/emptyworkbench.png b/bundles/org.eclipse.platform.doc.isv/guide/images/emptyworkbench.png
deleted file mode 100644
index 98ddbe1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/emptyworkbench.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/exportwizard.png b/bundles/org.eclipse.platform.doc.isv/guide/images/exportwizard.png
deleted file mode 100644
index 33bb871..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/exportwizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/filetypes.png b/bundles/org.eclipse.platform.doc.isv/guide/images/filetypes.png
deleted file mode 100644
index 03a7066..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/filetypes.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/filtersmenu.png b/bundles/org.eclipse.platform.doc.isv/guide/images/filtersmenu.png
deleted file mode 100644
index 121725f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/filtersmenu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/filtersselection.png b/bundles/org.eclipse.platform.doc.isv/guide/images/filtersselection.png
deleted file mode 100644
index 44ec757..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/filtersselection.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/firstpluginpde.png b/bundles/org.eclipse.platform.doc.isv/guide/images/firstpluginpde.png
deleted file mode 100644
index 6a48e73..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/firstpluginpde.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/genericoutliner.png b/bundles/org.eclipse.platform.doc.isv/guide/images/genericoutliner.png
deleted file mode 100644
index dcb2a93..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/genericoutliner.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/help_contents.png b/bundles/org.eclipse.platform.doc.isv/guide/images/help_contents.png
deleted file mode 100644
index 8e3a975..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/help_contents.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/ignore.png b/bundles/org.eclipse.platform.doc.isv/guide/images/ignore.png
deleted file mode 100644
index 7545269..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/ignore.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/importwizard.png b/bundles/org.eclipse.platform.doc.isv/guide/images/importwizard.png
deleted file mode 100644
index b05fe78..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/importwizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/infopops.png b/bundles/org.eclipse.platform.doc.isv/guide/images/infopops.png
deleted file mode 100644
index 7f4c66d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/infopops.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/javacheatsheet.png b/bundles/org.eclipse.platform.doc.isv/guide/images/javacheatsheet.png
deleted file mode 100644
index 0481358..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/javacheatsheet.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/javacontentassist.png b/bundles/org.eclipse.platform.doc.isv/guide/images/javacontentassist.png
deleted file mode 100644
index 1f26da5..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/javacontentassist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/javacontentoutline.png b/bundles/org.eclipse.platform.doc.isv/guide/images/javacontentoutline.png
deleted file mode 100644
index dc24dc6..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/javacontentoutline.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/javacontextassist.png b/bundles/org.eclipse.platform.doc.isv/guide/images/javacontextassist.png
deleted file mode 100644
index d10fbbf..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/javacontextassist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditor.png b/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditor.png
deleted file mode 100644
index 935443d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorcontextmenu.png b/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorcontextmenu.png
deleted file mode 100644
index 980f42f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorcontextmenu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditoroverviewruler.png b/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditoroverviewruler.png
deleted file mode 100644
index 8a2f8b1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditoroverviewruler.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorsquiggly.png b/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorsquiggly.png
deleted file mode 100644
index 52f78e3..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorsquiggly.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorverticalruler.png b/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorverticalruler.png
deleted file mode 100644
index 5b549ff..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorverticalruler.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/javarulerhover.png b/bundles/org.eclipse.platform.doc.isv/guide/images/javarulerhover.png
deleted file mode 100644
index 55e7edd..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/javarulerhover.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/javatexthover.png b/bundles/org.eclipse.platform.doc.isv/guide/images/javatexthover.png
deleted file mode 100644
index 158a199..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/javatexthover.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/keybindings.png b/bundles/org.eclipse.platform.doc.isv/guide/images/keybindings.png
deleted file mode 100644
index 31df98d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/keybindings.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/launch.jpg b/bundles/org.eclipse.platform.doc.isv/guide/images/launch.jpg
deleted file mode 100644
index 9b5e2e3..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/launch.jpg
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/launchImage.png b/bundles/org.eclipse.platform.doc.isv/guide/images/launchImage.png
deleted file mode 100644
index 509c2ca..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/launchImage.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/lcd.png b/bundles/org.eclipse.platform.doc.isv/guide/images/lcd.png
deleted file mode 100644
index 36f5ce1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/lcd.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/markerquickfixmenu.png b/bundles/org.eclipse.platform.doc.isv/guide/images/markerquickfixmenu.png
deleted file mode 100644
index c562615..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/markerquickfixmenu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/markerresolution.png b/bundles/org.eclipse.platform.doc.isv/guide/images/markerresolution.png
deleted file mode 100644
index e367ccf..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/markerresolution.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/navigator.png b/bundles/org.eclipse.platform.doc.isv/guide/images/navigator.png
deleted file mode 100644
index 661af1a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/navigator.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/newwizardlist.png b/bundles/org.eclipse.platform.doc.isv/guide/images/newwizardlist.png
deleted file mode 100644
index e7ab955..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/newwizardlist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/newwizardmenu.png b/bundles/org.eclipse.platform.doc.isv/guide/images/newwizardmenu.png
deleted file mode 100644
index e640a9e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/newwizardmenu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/perspectivemenu.png b/bundles/org.eclipse.platform.doc.isv/guide/images/perspectivemenu.png
deleted file mode 100644
index 999d140..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/perspectivemenu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/preferences.png b/bundles/org.eclipse.platform.doc.isv/guide/images/preferences.png
deleted file mode 100644
index 2d2fb82..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/preferences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/projectset.png b/bundles/org.eclipse.platform.doc.isv/guide/images/projectset.png
deleted file mode 100644
index bd052f4..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/projectset.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionset.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionset.png
deleted file mode 100644
index 633836c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionset.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionsetmenu.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionsetmenu.png
deleted file mode 100644
index b21f379..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionsetmenu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionsettool.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionsettool.png
deleted file mode 100644
index 0d5b778..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionsettool.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionsettoolbar.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionsettoolbar.png
deleted file mode 100644
index c1dc995..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionsettoolbar.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmedialog.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmedialog.png
deleted file mode 100644
index 97201d3..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmedialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmemarkerhelp.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmemarkerhelp.png
deleted file mode 100644
index 62aa4a4..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmemarkerhelp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmemarkermenu.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmemarkermenu.png
deleted file mode 100644
index 4bd20d7..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmemarkermenu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeoutliner.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmeoutliner.png
deleted file mode 100644
index 5c66a24..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeoutliner.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeoutlinerpopup.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmeoutlinerpopup.png
deleted file mode 100644
index 80963bd..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeoutlinerpopup.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeoverview.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmeoverview.png
deleted file mode 100644
index 92853fa..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeoverview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmepopupmenu.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmepopupmenu.png
deleted file mode 100644
index ccc23f0..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmepopupmenu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmepreferences.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmepreferences.png
deleted file mode 100644
index 8251cfa..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmepreferences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeproperties.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmeproperties.png
deleted file mode 100644
index 9bc7b92..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeproperties.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeview.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmeview.png
deleted file mode 100644
index dd27d8e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeviewaction.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmeviewaction.png
deleted file mode 100644
index cef3257..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeviewaction.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmewizard.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmewizard.png
deleted file mode 100644
index 61a3b80..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmewizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/sdk-arch.jpg b/bundles/org.eclipse.platform.doc.isv/guide/images/sdk-arch.jpg
deleted file mode 100644
index eb19cab..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/sdk-arch.jpg
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/showview.png b/bundles/org.eclipse.platform.doc.isv/guide/images/showview.png
deleted file mode 100644
index 2d12f27..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/showview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/singleclick.png b/bundles/org.eclipse.platform.doc.isv/guide/images/singleclick.png
deleted file mode 100644
index 61057ba..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/singleclick.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/team-version_controlled.png b/bundles/org.eclipse.platform.doc.isv/guide/images/team-version_controlled.png
deleted file mode 100644
index ed401bd..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/team-version_controlled.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/team_synchronize_example_localhistory_overview.png b/bundles/org.eclipse.platform.doc.isv/guide/images/team_synchronize_example_localhistory_overview.png
deleted file mode 100644
index 4ad2a15..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/team_synchronize_example_localhistory_overview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/teamdecorators.png b/bundles/org.eclipse.platform.doc.isv/guide/images/teamdecorators.png
deleted file mode 100644
index 92e4b17..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/teamdecorators.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/teamintegration.png b/bundles/org.eclipse.platform.doc.isv/guide/images/teamintegration.png
deleted file mode 100644
index 0096e34..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/teamintegration.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/teamprefs.png b/bundles/org.eclipse.platform.doc.isv/guide/images/teamprefs.png
deleted file mode 100644
index dfdbfa2..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/teamprefs.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/texteditor.png b/bundles/org.eclipse.platform.doc.isv/guide/images/texteditor.png
deleted file mode 100644
index 9e226f0..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/texteditor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/textencoding.png b/bundles/org.eclipse.platform.doc.isv/guide/images/textencoding.png
deleted file mode 100644
index 127dd16..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/textencoding.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/ua_cheatsheet.png b/bundles/org.eclipse.platform.doc.isv/guide/images/ua_cheatsheet.png
deleted file mode 100644
index 203e15b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/ua_cheatsheet.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/ua_help.png b/bundles/org.eclipse.platform.doc.isv/guide/images/ua_help.png
deleted file mode 100644
index 8b82bca..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/ua_help.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/ua_intro.png b/bundles/org.eclipse.platform.doc.isv/guide/images/ua_intro.png
deleted file mode 100644
index dcc3098..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/ua_intro.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/win_only.png b/bundles/org.eclipse.platform.doc.isv/guide/images/win_only.png
deleted file mode 100644
index 7523f99..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/win_only.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/wiz_arch.jpg b/bundles/org.eclipse.platform.doc.isv/guide/images/wiz_arch.jpg
deleted file mode 100644
index 2af1d89..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/wiz_arch.jpg
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/workbench.png b/bundles/org.eclipse.platform.doc.isv/guide/images/workbench.png
deleted file mode 100644
index 7bc644b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/workbench.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/workbench_decomposed.png b/bundles/org.eclipse.platform.doc.isv/guide/images/workbench_decomposed.png
deleted file mode 100644
index 9c15480..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/workbench_decomposed.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/workbenchdecorators.png b/bundles/org.eclipse.platform.doc.isv/guide/images/workbenchdecorators.png
deleted file mode 100644
index 0e11205..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/workbenchdecorators.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/workbenchwithhello.png b/bundles/org.eclipse.platform.doc.isv/guide/images/workbenchwithhello.png
deleted file mode 100644
index 5da69fc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/workbenchwithhello.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/workingSetTypes.png b/bundles/org.eclipse.platform.doc.isv/guide/images/workingSetTypes.png
deleted file mode 100644
index 568e5e0..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/workingSetTypes.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/workingset.png b/bundles/org.eclipse.platform.doc.isv/guide/images/workingset.png
deleted file mode 100644
index 3d4984f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/workingset.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/implementing_components.htm b/bundles/org.eclipse.platform.doc.isv/guide/implementing_components.htm
deleted file mode 100644
index d752746..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/implementing_components.htm
+++ /dev/null

@@ -1,99 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Implementing multiplexing components</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>Implementing multiplexing components</H2>
-In order to be used in a Multiplexer, site interfaces need to register an alternative 
-default implementation with the <span
- style="font-style: italic;">org.eclipse.ui.part.SiteMultiplexerInitializer</span> 
-scope. Since this extends the site scope, the more specific multiplexer version 
-will take priority over the default version when used in a Multiplexer. <br>
-<br>
-A multiplexed component will almost always use the following pattern: 
-<ol>
-  <li>Implement the INestedComponent lifecycle interface;</li>
-  <li>Take an IMultiplexer in their constructor and use it to access the shared 
-    version of their interface; </li>
-  <li>Store the part's state;</li>
-  <li>Listen to state changes in the child and update the stored state appropriately;</li>
-  <li>Each time the component is activated, it should forward the stored state 
-    to the shared interface in the multiplexer; </li>
-  <li>While the component is active, it should forward state changes directly 
-    to the shared interface.</li>
-</ol>
-The following example demonstrates the code used by the workbench to multiplex 
-the ISelectionHandler interface with ChildSelectionHandler. 
-<pre>
-/**
- * Multiplexed version of the ISelectionHandler interface
- *
- * @since 3.1
- */
-public class ChildSelectionHandler implements ISelectionHandler, INestedComponent {
-
-    private ISelectionHandler parent;
-    private ISelection selection;
-    private boolean isActive = false;
-    private IMultiplexer multiplexer;
-
-    public ChildSelectionHandler(IMultiplexer mplex) throws DependencyException {
-        this.multiplexer = mplex;        
-        // Get access to the shared ISelectionHandler being multiplexed (we should        
-        // only modify it when we're the active child)        
-        this.parent = (ISelectionHandler)
-            mplex.getSharedComponents().getComponent(ISelectionHandler.class);        
-                
-        // Set the initial state (the part's initial selection will be null        
-        // until it explicitly sets it).        
-    }        
-
-    public IMultiplexer getMultiplexer() {        
-        // Return the multiplexer we were created with        
-        return multiplexer;        
-    }
-
-    public void activate() {        
-        // Forward our stored selection to the shared interface        
-        parent.setSelection(selection);        
-        isActive = true;        
-    }        
-            
-    public void deactivate() {        
-        isActive = false;        
-    }        
-
-    public void setSelection(ISelection newSelection) {        
-        // Remember the child's new selection        
-        selection = newSelection;        
-        if (isActive) {        
-             // If we're active, forward the selection directly to the
-             // shared interface        
-             parent.setSelection(newSelection);        
-        }        
-    }        
-}        
-</pre>
-Here is the associated extension point markup for ChildSelectionHandler.
-<pre>
-&lt;extension point="org.eclipse.core.component.types"&gt;        
-    &lt;component        
-            implementation="org.eclipse.ui.internal.part.services.ChildSelectionHandler"        
-            interface="org.eclipse.ui.part.services.ISelectionHandler"        
-            singleton="false"        
-            initializer="org.eclipse.ui.part.SiteMultiplexerInitializer"/&gt;        
- &lt;/extension&gt;        
-</pre>
-<div style="margin-left: 40px;"><img src="images/composite_view.PNG" alt="Screenshot of TestCompositeView"><br>
-  <br>
-</div>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/initializers.htm b/bundles/org.eclipse.platform.doc.isv/guide/initializers.htm
deleted file mode 100644
index d14ef67..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/initializers.htm
+++ /dev/null

@@ -1,78 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Initializers</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2> Initializers</H2>
-The main purpose of an initializer is to identify a scope. However, it is more 
-than just a unique identifier. It points to the Java class that supplies initialization 
-information to the scope. In order to create an object from the org.eclipse.core.component.types 
-extension point, Eclipse must manually construct an initializer of the appropriate 
-type. This allows Eclipse to pass required context to components from outside 
-the component framework. Any component is allowed to depend on the initializer 
-for its scope, it to access this context. Currently most of the initializers provided 
-by the workbench have an empty public interface, so most clients would not want 
-to do this yet. <br>
-<br>
-Inheritance <span style="font-style: italic;"><span
- style="font-weight: bold;">is</span> </span>taken into consideration between 
-initializer types. Registering a component type on an initializer's base class 
-will also affect the initializer and all of its subclasses. Initializers cannot 
-be interfaces, so only single inheritance is possible. For example, an interface 
-registered on <span
- style="font-style: italic;">org.eclipse.core.component.ExtensionInitializer </span>would 
-be visible both from a part and from its site since <span
- style="font-style: italic;">org.eclipse.core.component.ExtensionInitializer</span> 
-is a base class for both the part and site initializers.<br>
-<br>
-The workbench supplies the following initializer types:<br>
-<br>
-<table style="width: 100%; text-align: left;" border="1" cellpadding="2"
- cellspacing="2">
-  <tbody>
-    <tr> 
-      <td style="vertical-align: top; font-weight: bold;">Initializer<br> </td>
-      <td style="vertical-align: top; font-weight: bold;">Base class<br> </td>
-      <td style="vertical-align: top; font-weight: bold;">Used for<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top;">org.eclipse.core.component.ExtensionInitializer<br> 
-      </td>
-      <td style="vertical-align: top;">none<br> </td>
-      <td style="vertical-align: top;">Dependencies used by any component created 
-        from an extension point.<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top;">org.eclipse.ui.part.PartInitializer<br> 
-      </td>
-      <td style="vertical-align: top;">org.eclipse.core.component.ExtensionInitializer</td>
-      <td style="vertical-align: top;">Interfaces that can be implemented by a 
-        part.<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top;">org.eclipse.ui.part.SiteInitializer</td>
-      <td style="vertical-align: top;">org.eclipse.core.component.ExtensionInitializer</td>
-      <td style="vertical-align: top;">Components available from a site (such 
-        as things a part can take in its constructor).<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top;">org.eclipse.ui.part.SiteMultiplexerInitializer<br> 
-      </td>
-      <td style="vertical-align: top;">org.eclipse.ui.part.SiteInitializer</td>
-      <td style="vertical-align: top;">Dependencies that only apply to site inside 
-        a multiplexer (used to override the default component implementation provided 
-        by a site).<br> </td>
-    </tr>
-  </tbody>
-</table>
-<br>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/instantiating_parts.htm b/bundles/org.eclipse.platform.doc.isv/guide/instantiating_parts.htm
deleted file mode 100644
index 9126927..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/instantiating_parts.htm
+++ /dev/null

@@ -1,265 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Instantiating parts</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> 
-</H1>
-<div style="margin-left: 40px;">
-<h2> Instantiating parts</h2>
-  All interaction with a part happens through an ISite. From the point of view 
-  of someone creating a part, the ISite <span
- style="font-style: italic;">is</span> the part. An ISite can either be created 
-  from an IPartFactory or by directly instantiating the Site class.<br>
-  <br>
-  To destroy a part, dispose the control for its ISite.<br>
-  <h3>Instantiating parts using IPartFactory </h3>
- <p>Views and editors are normally created using an IPartFactory and IPartFactory 
-    can only create parts registered with the views or editors extension point. 
-    . Parts created by IPartFactory depend on an IWorkbenchPage and cannot outlive 
-    the IWorkbenchPage. IPartFactory creates parts by ID and the part's implementation 
-    class does not need to be API. An IPartFactory can be obtained from IWorkbenchPage. 
-    Parts can also take an IPartFactory in their constructor to create nested 
-    children. </p>
-  <p>This example demonstrates how to create a view using IPartFactory.<br>
-  </p>
-  <div style="margin-left: 40px;"><code>/**<br>
-    &nbsp;* Used to create instances of editors and views.<br>
-    &nbsp;* <br>
-    &nbsp;* @since 3.1<br>
-    &nbsp;*/<br>
-    public interface IPartFactory {<br>
-    &nbsp;&nbsp;&nbsp; /**<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * Creates an instance of a view. Returns an &lt;code&gt;ISite&lt;/code&gt; 
-    for the newly created view.<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * When the caller is done with the part it should 
-    dispose the part's main control. This can<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * be accomplished by calling &lt;code&gt;ISite.getControl().dispose()&lt;/code&gt;, 
-    or by disposing the <br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * parent composite.<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; *<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * @param viewId ID of the view, as registered with 
-    the org.eclipse.ui.views extension point<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * @param parentComposite parent composite for the 
-    view. If the view is successfully created, it<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; will 
-    create exactly one new child control in this composite. <br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * @param context local context for the view. This 
-    object can override any or all of the view's dependencies.<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If the 
-    view has a dependency that isn't found in the local context, a default implementation 
-    will<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; be supplied 
-    by the org.eclipse.core.component.types extension point.<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * @param savedState previously saved state of the 
-    part, or null if none<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * @return an ISite for the newly created view<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * @throws CoreException if unable to create the part<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; */<br>
-    &nbsp;&nbsp;&nbsp; public ISite createView(String viewId, Composite parentComposite, 
-    IContainerContext context, IMemento savedState) throws CoreException;<br>
-    &nbsp;&nbsp;&nbsp; <br>
-    &nbsp;&nbsp;&nbsp; /**<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * Creates an instance of an editor. Returns an &lt;code&gt;ISite&lt;/code&gt; 
-    for the newly created editor.<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * When the caller is done with the part it should 
-    dispose the part's main control. This can<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * be accomplished by calling &lt;code&gt;ISite.getControl().dispose()&lt;/code&gt;, 
-    or by disposing the <br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * parent composite.<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * <br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * @param editorId ID of the editor, as registered 
-    with the org.eclipse.ui.editors extension point<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * @param parentComposite parent composite for the 
-    editor. If the editor is successfully created,<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; it will 
-    create exactly one new child control in this composite.<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * @param context local context for the editor. This 
-    object can override any or all of the part's dependencies.<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If the 
-    part has a dependency that isn't found in the local context, a default implementation 
-    will<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; be supplied 
-    by the org.eclipse.core.component.types extension point.<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * @param input IEditorInput for this editor<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * @param savedState previously saved state for the 
-    part, or null if none<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * @return an ISite for the newly created editor<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * @throws CoreException if unable to create the part<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; */<br>
-    &nbsp;&nbsp;&nbsp; public ISite createEditor(String editorId, Composite parentComposite, 
-    IContainerContext context, IEditorInput input, IMemento savedState) throws 
-    CoreException;<br>
-    }</code><br>
-    </div>
-  <br>
-  <p>Here is an example of an action that creates 
-  a view using IPartFactory</p>
-  <div style="margin-left: 40px;"><code>/**<br>
-    &nbsp;* Demonstrate how to open a view by its ID from an IWorkbenchPage.<br>
-    &nbsp;*/<br>
-    public class CreateViewByIdAction implements IWorkbenchWindowActionDelegate 
-    {<br>
-    &nbsp;&nbsp;&nbsp; private IWorkbenchWindow window;<br>
-    <br>
-    &nbsp;&nbsp;&nbsp; public void run(IAction action) {&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-    <br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IWorkbenchPage page = window.getActivePage();<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if (page == null) {<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </code><code>// 
-    ...uninteresting error-handling code removed...</code><code><br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; return;<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; final Shell tempShell = new Shell(window.getShell(), 
-    SWT.DIALOG_TRIM | SWT.RESIZE);<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; tempShell.setLayout(new FillLayout());<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; tempShell.setText("Problems");<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
-    <span style="color: rgb(255, 0, 0);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-    IPartFactory factory = page.getPartFactory();</span><br
- style="color: rgb(255, 0, 0);">
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; try {<br>
-    <span style="color: rgb(255, 0, 0);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-    factory.createView(IPageLayout.ID_PROBLEM_VIEW, tempShell, new ContainerContext(), 
-    null);</span><br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; } catch (CoreException e) {<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </code><code>// 
-    ...uninteresting error-handling code removed...</code><code><br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Open the dialog<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; tempShell.open();<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Display d = tempShell.getDisplay();<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; while (!tempShell.isDisposed()) 
-    {<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if (!d.readAndDispatch())<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-    d.sleep();<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
-    &nbsp;&nbsp;&nbsp; }<br>
-    <br>
-    &nbsp;&nbsp;&nbsp; public void init(IWorkbenchWindow window) {<br>
-    &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; this.window = window;<br>
-    &nbsp;&nbsp;&nbsp; }<br>
-    <br>
-    &nbsp;&nbsp;&nbsp; // ...remaining (empty) methods removed...<br>
-    }<br>
-    <br>
-    </code>
-    <h3>Instantiating parts using the Site class</h3>
-    Not all parts are views or editors. Clients can also use the part API to create 
-    their own reusable components. Such parts are not registered with the view 
-    or editor extension points, but can make use of most of the API available 
-    to views and editors. Although there is nothing stopping clients from inventing 
-    their own API for reusable components, making use of the part pattern allows 
-    their components to be embedded inside anything that supports embedding of 
-    views or editors.<br>
-    <br>
-    Parts created using the Site class have the following properties: 
-    <ul>
-      <li>The part's implementation class must be known and loaded; </li>
-      <li>The part does not need to be a view or editor, and does not require 
-        any extension markup; </li>
-      <li>The part has access to a reduced set of site interfaces, so views and 
-        editors cannot be created in this manner unless their JavaDoc explicitly 
-        says so;</li>
-      <li>These parts can be created without a workbench page;</li>
-      <li>This pattern can only be used to create component-based parts. Views 
-        and editors that implement IViewPart or IEditorPart cannot be created 
-        in this manner.</li>
-    </ul>
-    The Site constructor must be given the part's implementation class and the 
-    associated plugin bundle. The plugin bundle determines where log error messages 
-    will be logged and where the part should search when looking for resources 
-    in its own plugin.<br>
-    <br>
-    The following example demonstrates how to use the Site class to instantiate 
-    a part directly. In this example, we instantiate the NameTestView part in 
-    a dialog. Although NameTestView is called a view and can make use of the view 
-    API, it doesn't actually need to be registered with the org.eclipse.ui.views 
-    extension point unless the workbench is actually supposed to use it as a view.<br>
-    <br>
-    <code><br>
-    </code> 
-    <div style="margin-left: 40px;"><code>/**</code><br>
-      <code>&nbsp;* Demonstrate how to open a part programmatically using the 
-      Site class.</code><br>
-      <code>&nbsp;*/</code><br>
-      <code>public class ProgrammaticViewCreationExampleAction implements IWorkbenchWindowActionDelegate 
-      {</code><br>
-      <code>&nbsp;&nbsp;&nbsp; private IWorkbenchWindow window;</code><br>
-      <br>
-      <code>&nbsp;&nbsp;&nbsp; public void run(IAction action) {&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-      </code><br>
-      <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Create a shell</code><br>
-      <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; final Shell tempShell = 
-      new Shell(window.getShell(), SWT.DIALOG_TRIM | SWT.RESIZE);</code><br>
-      <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; tempShell.setLayout(new 
-      FillLayout());</code><br>
-      <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; tempShell.setText("Name 
-      test view");</code><br>
-      <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </code><br>
-      <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bundle thisPlugin = ComponentExamplesPlugin.getDefault().getBundle(); 
-      </code><br>
-      <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </code><br>
-      <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; try {</code><br>
-      <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-      // Instantiate the NameTestView part (this line is the whole point of the 
-      example)</code><br>
-      <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-      // It demonstrates how the Site class can be used instead of calling NameTestView's 
-      constructor.</code><br>
-      <code style="color: rgb(255, 0, 0);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-      Site testPart = new Site(tempShell, new ContainerContext(), </code><br
- style="color: rgb(255, 0, 0);">
-      <code style="color: rgb(255, 0, 0);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-      thisPlugin, </code><br style="color: rgb(255, 0, 0);">
-      <code><span style="color: rgb(255, 0, 0);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-      NameTestView.class);&nbsp;&nbsp;&nbsp;&nbsp;</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-      </code><br>
-      <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-      </code><br>
-      <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; } catch (CoreException 
-      e) {<br>
-      &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // ...uninteresting 
-      error-handling code removed...<br>
-      </code><code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-      }</code><br>
-      <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </code><br>
-      <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Open a modal dialog</code><br>
-      <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; tempShell.open();</code><br>
-      <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Display d = tempShell.getDisplay();</code><br>
-      <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; while (!tempShell.isDisposed()) 
-      {</code><br>
-      <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-      if (!d.readAndDispatch())</code><br>
-      <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-      d.sleep();</code><br>
-      <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }</code><br>
-      <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </code><br>
-      <code>&nbsp;&nbsp;&nbsp; }</code><br>
-      \<br>
-      <code>&nbsp;&nbsp;&nbsp; public void init(IWorkbenchWindow window) {</code><br>
-      <code>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; this.window = window;</code><br>
-      <code>&nbsp;&nbsp;&nbsp; }<br>
-      <br>
-      &nbsp;&nbsp;&nbsp; </code><code>// ...remaining (empty) methods removed...</code><br>
-      <code>}</code></div>
-    <code> </code></div>
-    </div>
-<h2>&nbsp; </h2>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/int.htm b/bundles/org.eclipse.platform.doc.isv/guide/int.htm
deleted file mode 100644
index 1e40066..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/int.htm
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Welcome to Eclipse
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Welcome to Eclipse</H1>
-<p>Welcome to the Eclipse platform!&nbsp;</p>
-<p>The following sections discuss the issues and problems with building
-integrated tool suites, and how the Eclipse tooling platform can help solve
-these problems.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/int_eclipse.htm b/bundles/org.eclipse.platform.doc.isv/guide/int_eclipse.htm
deleted file mode 100644
index 6842799..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/int_eclipse.htm
+++ /dev/null

@@ -1,163 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-What is Eclipse?
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-What is Eclipse?</H2>
-<P >
- Eclipse is a platform that has been designed from the ground up for building integrated web and application development tooling. By design, the platform does not provide a great deal of
-end user functionality by itself. The value of the platform is what it encourages: rapid development of integrated features based on a
-<b> plug-in</b> model.</P>
-<P >
-Eclipse provides a common user interface (UI) model for working with tools.&nbsp; It is designed
-to run on multiple operating systems while providing robust integration with
-each underlying OS.&nbsp; Plug-ins can program to the Eclipse portable APIs and
-run unchanged on any of the supported operating systems.&nbsp;</P>
-<P >
-At the core of Eclipse is an architecture for dynamic discovery, loading, and running of plug-ins. The
-platform handles the logistics of finding and running the right code.  The platform UI provides a standard
-user navigation model.&nbsp; Each plug-in can then focus on doing a small number of tasks well. What
-kinds of tasks? Defining, testing, animating, publishing, compiling, debugging,
-diagramming...the
-only limit is your imagination.</P>
-
-<H3>
-Open architecture</H3>
-<P >
-The Eclipse platform defines an open architecture so that each plug-in development team can focus on their 
-area of expertise. Let the repository experts build the back ends and the usability experts build the end 
-user tools. If the platform is designed well, significant new features and levels of integration can be 
-added without impact to other tools.</P>
-<P >
-The Eclipse platform uses the model of a common workbench to integrate the tools from the end user's point of view. Tools that you develop can
-plug into the workbench using well defined hooks called <b>extension points</b>.</P>
-<P >
-The platform itself is built in layers of plug-ins, each one defining extensions to the extension points of 
-lower-level plug-ins, and in turn defining their own extension points for further customization.  This extension 
-model allows plug-in developers to add a variety of function to the basic tooling platform. The artifacts for each 
-tool, such as files and other data, are coordinated by a common platform resource model.</P>
-<P >
-The platform gives the users a common way to work with the tools, and provides integrated management o
-f the resources they create with plug-ins. </P>
-<P >Plug-in developers also gain from this architecture.&nbsp; The platform
-manages the complexity of different runtime environments, such as different
-operating systems or workgroup server environments.&nbsp; Plug-in
-developers can focus on their specific task instead of worrying about these
-integration issues.</P>
-
-
-
-<H3>
-Platform structure</H3>
-<P >
-The Eclipse platform itself is structured as subsystems which are implemented in
-one or more plug-ins.&nbsp; The subsystems are built on top of a small runtime engine.
-The figure below depicts a simplified view.   </P>
-
-<P >
-<img src="images/arch-npi.jpg" alt="Platform runtime base with groups of plug-ins adding function" border="0" > </P>
-
-<P >
-The plug-ins that make up a subsystem define extension points for adding behavior to the
-platform.&nbsp; The following table describes the major runtime components of the platform that
-are implemented as one or more plug-ins. </P>
-
-<table border="1" width="100%">
-  <tr>
-    <td width="29%">
-
-<H4>
-Platform runtime</H4>
-    </td>
-    <td width="71%">Defines the extension point and plug-in model. It dynamically 
-      discovers plug-ins and maintains information about the plug-ins and their extension points 
-      in a platform registry.
-      Plug-ins are started up when required according to user operation of the
-      platform.  The runtime is implemented using the OSGi framework.</td>
-  </tr>
-  <tr>
-    <td width="29%">
-<H4>Resource management (workspace)</H4>
-    </td>
-    <td width="71%">Defines API for creating and managing resources (projects,
-      files, and folders) that are produced by tools and kept in the file system.</td>
-  </tr>
-  <tr>
-    <td width="29%">
-<H4>
-Workbench UI</H4>
-    </td>
-    <td width="71%">Implements the user cockpit for navigating the platform. It defines extension points for adding UI components such as views or menu actions.&nbsp;
-      It supplies additional toolkits (JFace and SWT) for building user
-      interfaces. The UI services are structured so that a subset of the UI plug-ins can be used to build rich client applications that are
-      independent of the resource management and workspace model.  IDE-centric plug-ins define additional function for 
-      navigating and manipulating resources.</td>
-  </tr>
-  <tr>
-    <td width="29%">
-
-
-<H4>
-Help system</H4>
-    </td>
-    <td width="71%">Defines extension points for plug-ins to provide help or
-      other documentation as browsable books.</td>
-  </tr>
-  <tr>
-    <td width="40%">
-
-
-<H4>Team support</H4>
-    </td>
-    <td width="60%">Defines a team programming model for managing and versioning resources.&nbsp;</td>
-  </tr>
-  <tr>
-    <td width="40%">
-
-
-<h4>Debug support</h4>
-    </td>
-    <td width="60%">Defines a language independent debug model and UI classes
-      for building debuggers and launchers.</td>
-  </tr>
-  <tr>
-    <td width="40%">
-  
-<h4>Other utilities</h4>
-    </td>
-    <td width="60%">Other utility plug-ins supply function such as searching and comparing resources, performing builds using XML configuration files,
-    and dynamically updating the platform from a server.</td>
-  </tr>
-</table>
-
-
-
-<H3>
-Out of the box</H3>
-<P >
-Out of the box - or off the web - the basic platform is an integrated development environment (IDE) for anything (and nothing in particular). </P>
-<P >
-<img src="images/emptyworkbench.png" alt="Workbench window" border="0"></P>
-<P >
-It's the plug-ins that determine the ultimate functionality of the platform.&nbsp;
-That's why the Eclipse SDK ships with additional plug-ins to enhance the
-functionality of the SDK.</P>
-<P >
-Your plug-ins can provide support for editing and manipulating additional types of
-resources such as Java files, C programs, Word documents, HTML pages, and JSP files.</P>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/int_goal.htm b/bundles/org.eclipse.platform.doc.isv/guide/int_goal.htm
deleted file mode 100644
index 35ea919..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/int_goal.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-The holy grail
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-The holy grail</H2>
-<P >
-What we all want is a level of integration that magically blends separately developed tools into a
-well designed suite.&nbsp; And it should be simple enough that existing tools can be moved to the platform without using a shoehorn or
-a crowbar.</P>
-<P >
-The platform should be open, so that users can select tools from the best source and know that their supplier has a voice in the development of the underlying platform. </P>
-<P >
-It should be simple to understand, yet robust enough to support integration without a lot of extra glue.</P>
-<P >
-It should provide tools that help automate mundane tasks.&nbsp; It should be stable enough
-so that industrial strength tools can build on top of it. And it should be useful enough that the platform developers can use it to build itself.</P>
-<P >
-These are all goals of Eclipse.&nbsp; The remainder of this programming guide
-will help you determine how close Eclipse has come to delivering on these
-ideals.</P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/int_who.htm b/bundles/org.eclipse.platform.doc.isv/guide/int_who.htm
deleted file mode 100644
index b1b0020..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/int_who.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Who needs a platform?</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Who needs a platform?</H2>
-<P >
-On any given day, you can probably find an announcement about a strategic alliance,
-an open architecture, or a commercial API that promises to integrate all your tools, seamlessly move your data among applications, and simplify your programming life.</P>
-<P >
-Down in the trenches, you're trying to apply enough import/export duct tape to let marketing say &quot;suite&quot; with a straight face.</P>
-<P >
-Where is all this integration pressure coming from? Why is everyone trying to integrate their products into suites or build platforms to support open integration? Who needs these platforms?</P>
-
-<H3>
-End users</H3>
-<P >
-Let's face it. End users do not call the support line to say, &quot;What I really need is an open tools platform.&quot;</P>
-<P >
-But they do ask why your product doesn't integrate with their other tools. They ask for features outside of the scope of your application because they can't get their data to a tool that would do the job better. They run into problems importing and exporting between different programs. They wonder why their programs have completely different user interfaces for doing similar tasks. Doesn't it seem obvious that their web site design tool should be integrated with their scripting program?</P>
-<P >
-Your users want the freedom to pick the best tool for the task. They don't want to be constrained because
-your software only integrates with a few other programs. They have a job to do, and it's not managing the flow of files and data between their tools. They're busy solving their own problems. It's your job to make the tools
-work, and even better if you can make them work together.</P>
-
-
-<H3>
-Software developers</H3>
-<P >
-Meanwhile, you are slaving on your tool implementing the next round of critical features, fixing bugs, and shipping releases. The last thing you need is another emergency import feature added to your list.</P>
-<P >
-Wouldn't it be nice if you could just publish enough hooks to make integrating with your tool everyone else's problem?
-Unfortunately, unless you work for one of the giants, you just don't have enough clout to get away with that.
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/java_web_start.htm b/bundles/org.eclipse.platform.doc.isv/guide/java_web_start.htm
deleted file mode 100644
index 30afaed..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/java_web_start.htm
+++ /dev/null

@@ -1,173 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Deploying eclipse based application with Java Web Start
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Deploying eclipse based application with Java Web Start</h2>
-<p>
-Applications built on eclipse 3.1 can now be deployed using Java Web Start.</p><p>
-Java Web Start "is an application-deployment technology that gives you the power to launch full-featured 
-applications with a single click from your web browser".</p>
- <p>
-The prerequisites to start eclipse from Java Web Start are:</p>
-<ul>
-<li> The deployed application must be eclipse 3.1 based; </li>
-<li> All deployed plug-ins must be jar'ed;</li>
-<li> All plug-ins must be signed since the application need full permission from the client.</li>
-</ul> 
-The following steps describe how to setup a Java Web Start site serving up a feature based RCP application.
-
-<h3>Step 1, creating a wrappering feature</h3>
-<ul>
-<li> Create a feature including all the features that are listed in your product definition;</li>
-<li> Copy in a folder of your feature the startup.jar;</li>
-<li> Add the following line to the build.properties of the feature.
-<pre>
-root=&lt;folderContainingStartup.jar&gt;/
-</pre>
-</li>
-</ul>
-
-<h3> Step 2, exporting the wrappering feature and the startup.jar</h3>
-Note. Before proceeding with this step make sure to have a keystore available. Eclipse does not provide any
-facility to create keystores. You need to use keytool. In addition, ensure that the eclipse you are developing 
-with is running on a Java SDK instead of a JRE. If this constraint is not satisfied, the jar signing will fail.
-
-<ul>
-<li> Select the wrappering feature and do File > Export > Feature. In the wizard, select the wrappering feature, 
-choose the "directory" option to export your jnlp application to, and check the option "package features and 
-plug-ins as individual JAR archives". On the next page of the wizard, fill in the information relative to your keystore 
-in the "Signing JAR Archives" section. Then in the "JNLP section", enter the name of the server that will serve up your 
-application and the level of JRE required to start your application. That last value will be used to in the generated JNLP 
-files to fill in the value of <code>&lt;j2se version="1.4+" /&gt; </code>. Click finish.</li>
- 
-<li> Once the export is done you should have the following structure on disk
-<pre>
-site/   <i>(The root of your jnlp site)</i>
-  startup.jar
-  features/
-    WrapperingFeature_1.0.0.jar
-    WrapperingFeature_1.0.0.jnlp
-    com.xyz.abc_1.0.0.jar
-    com.xyz.abc_1.0.0.jnlp
-    ...
-  plugins/
-    org.eclipse.core.runtime_3.1.0.jar
-    com.foo.baz_1.0.0.jnlp
-    ...
-</pre>
-</li>
-
-<li>Using the same keystore than the one used to export the feature, sign startup.jar using jarsigner.<br>
-Tips: if you don't change keystore, replace the startup.jar from the feature with this signed version so you don't 
-have to do this manual step on every export.</li>
-</ul>
-
-<h3>Step 3, creating the main jnlp file</h3>
-<p>A Java Web Start application is described by JNLP files. They replace the eclipse.exe and the config.ini
-files by some equivalent mechanism. For example, JNLP has its own mechanism to control splash screen, ways
-to pass parameters and define what constitutes the application.</p>
-<p>
-When you did the export, all the simple JNLP files have been created, so you are left with writing
-the main file that will control the application. Because the majority of the main file is common to all 
-applications, it is recommended to start from the following self documented template.</p>
-<p>
-On the site serving up your application, the file must be located in the same folder than startup.jar.
-Once you will be done editing this file, your application will be ready.</p>
-<pre>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
-&lt;jnlp 
-    spec="1.0+" 
-    codebase="http://myCompany.org/jnlpServer" 
-    href="mail.jnlp"&gt; &lt;!-- URL to the site containing the jnlp application. It should match the value used on  export. Href, the name of this file --&gt;
-  &lt;information&gt;
-    &lt;!-- user readable name of the application --&gt;
-    &lt;title&gt; Mail Application &lt;/title&gt;  
-    &lt;!-- vendor name --&gt;
-    &lt;vendor&gt;My company&lt;/vendor&gt;
-    &lt;!-- vendor homepage --&gt; 
-    &lt;homepage href="My company website" /&gt; 
-    &lt;!-- product description --&gt;
-    &lt;description&gt;This is a mail client&lt;/description&gt; 
-    &lt;icon kind="splash" href="splash.gif"/&gt;
-  &lt;/information&gt;
- 
-  &lt;!--request all permissions from the application. This does not change--&gt;
-  &lt;security&gt;
-    &lt;all-permissions/&gt;
-  &lt;/security&gt;
- 
-  &lt;!-- The name of the main class to execute. This does not change--&gt;
-  &lt;application-desc main-class="org.eclipse.core.launcher.WebStartMain"&gt;
-    &lt;argument&gt;-nosplash&lt;/argument&gt;
-  &lt;/application-desc&gt;
- 
-  &lt;resources&gt;
-    &lt;!-- Reference to the startup.jar. This does not change --&gt;
-    &lt;jar href="startup.jar"/&gt;
- 
-    &lt;!-- Reference to all the plugins and features consituting the application --&gt;
-    &lt;!-- Here we are refering to the wrappering feature since it transitively refers to all the other plug-ins  necessary --&gt;
-    &lt;extension 
-        name="Wrappering feature"
-        href="features/Wrappering_1.0.0.jnlp"/&gt;
- 
-    &lt;!-- Information usually specified in the config.ini --&gt;
-    &lt;property 
-        name="osgi.instance.area" 
-        value="@user.home/Application Data/mail"/&gt;
-    &lt;property 
-        name="osgi.configuration.area" 
-        value="@user.home/Application Data/mail"/&gt;
-        
-    &lt;!-- The id of the product to run, like found in the overview page of the product editor --&gt;
-    &lt;property 
-        name="eclipse.product" 
-        value="mail.product"/&gt;
-  &lt;/resources&gt;
-
-  &lt;!-- Indicate on a platform basis which JRE to use --&gt; 
-  &lt;resources os="Mac"&gt;
-    &lt;j2se version="1.5+" java-vm-args="-XstartOnFirstThread"/&gt;
-  &lt;/resources&gt;
-  &lt;resources os="Windows"&gt;
-    &lt;j2se version="1.4+"/&gt;
-  &lt;/resources&gt;
-  &lt;resources os="Linux"&gt;
-    &lt;j2se version="1.4+"/&gt;
-  &lt;/resources&gt;
-&lt;/jnlp&gt;
-</pre>
-<p>Tips: once you have created this file, you can store it in the wrappering feature in the same folder than the startup.jar, such 
-that on every export you will get the complete structure.</p>
-
-<h3>Plug-ins based application</h3>
-<p>Even though your RCP application does not use features, Java Web Start-ing it is possible.</p><p>
-To do so, it is recommended to create a wrappering feature in order to facilitate the creation of the 
-main jnlp file and ease the deployement. This wrappering feature will list all the plug-ins of your application. Once the feature has been updated
-copy the generated JNLP file and modify it to become your main JNLP file.</p>
-
-
-<h3>Known limitations</h3>
-<ul>
-<li>Eclipse Update and Java Web Start<br>
-Those two deployment technologies can work together but under the following restrictions:
-plug-ins installed by Java Web Start can not be updated by Update and vice-versa. Features and plug-ins installed
-by Java Web Start can't be refered in the prerequisites of features that needs to be installed by Update;</li>
-<li> Help can not be deployed through Java Web Start. However it could be installed using eclipse Update, 
-or the server serving your application could run a help server;</li>
-<li> Request to exit the application with a restart code are ignored;</li>
-<li>On the mac, applications can only be webstarted by clients using java 1.5.</li>
-</ul>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/jface.htm b/bundles/org.eclipse.platform.doc.isv/guide/jface.htm
deleted file mode 100644
index 753468e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/jface.htm
+++ /dev/null

@@ -1,75 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>The JFace UI framework</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>The JFace UI framework</H1>
-<P >
-We've seen that the workbench defines extension points for plug-ins to contribute UI function to the platform. Many of these extension points,
-particularly wizard extensions, are implemented using classes in the
-<b>
-org.eclipse.jface.*</b> packages. What's the distinction? </P>
-<P >
-JFace is a UI toolkit that provides helper classes for developing UI features
-that can be tedious to implement. JFace operates above the level of a raw widget system. It provides classes for handling common UI programming tasks:</P>
-<ul>
-  <li>
-<b>
-Viewers</b> handle the drudgery of populating, sorting, filtering, and updating widgets.</li>
-  <li>
-<b>
-Actions</b> and <b> contributions</b> introduce semantics for defining user actions and specifying where to make them available.</li>
-  <li>
-<b>
-Image</b> and <b> font registries</b> provide common patterns for handling UI resources.</li>
-  <li>
-<b>
-Dialogs</b> and <b> wizards</b> define a framework for building complex interactions with the
-user.</li>
-</ul>
-<P >
-JFace frees you up to focus on the implementation of your specific
-plug-in's function, rather than focusing on the underlying widget system or solving problems that are common in almost any UI application. </P>
-
-<h2>
-JFace and the workbench</h2>
-<P >
-Where does JFace end and the workbench begin? Sometimes the lines aren't so obvious. In general, the JFace APIs (from the packages
-<b>org.eclipse.jface.*</b>) are independent of the workbench extension points and APIs. Conceivably, a JFace program could be written without using any workbench code at all.</P>
-<P >
-The workbench makes use of JFace but attempts to reduce dependencies where possible. For example, the workbench part model
-(<a href="../reference/api/org/eclipse/ui/IWorkbenchPart.html"><b>IWorkbenchPart</b></a>)
-is designed to be independent of
-JFace. We saw earlier that views and editors can be implemented using SWT widgets directly without using any JFace classes. The workbench attempts to remain &quot;JFace neutral&quot; wherever possible, allowing programmers to use the parts of JFace they find useful. In practice, the workbench uses JFace for much of its implementation and there are references to JFace types in API definitions. (For example, the JFace interfaces for
-<b><a href="../reference/api/org/eclipse/jface/action/IMenuManager.html">IMenuManager</a></b>,
-<b><a href="../reference/api/org/eclipse/jface/action/IToolBarManager.html">IToolBarManager</a></b>, and
-<b><a href="../reference/api/org/eclipse/jface/action/IStatusLineManager.html"> IStatusLineManager</a></b> show up as types in the workbench
-<b><a href="../reference/api/org/eclipse/ui/IActionBars.html">IActionBar</a></b>
-methods.)</P>
-<p>When using JFace API, it's a good idea to keep in mind the rules of engagement for
-using background threads.  See <a href="swt_threading.htm#workbench_threads">The workbench and threads</a> for more information.
-</p>
-
-<h2>JFace and SWT</h2>
-<P >
-The lines between SWT and JFace are much cleaner. SWT does not depend on any JFace or platform code at all. Many of the SWT examples show how you can build a standalone application. </P>
-<P >
-JFace is designed to provide common application UI function on top of the SWT
-library. JFace does not try to &quot;hide&quot; SWT or replace its function. It provides classes and interfaces that handle many of the common tasks associated with programming a dynamic UI using
-SWT.</P>
-<P >
-The relationship between JFace and SWT is most clearly demonstrated by looking at viewers and their relationship to SWT widgets.</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/jface_actions.htm b/bundles/org.eclipse.platform.doc.isv/guide/jface_actions.htm
deleted file mode 100644
index de06915..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/jface_actions.htm
+++ /dev/null

@@ -1,74 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Actions and contributions
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Actions and contributions</H2>
-<P >
-The action classes allow you to define user commands independently from their presentation in the UI. This gives you the flexibility to change the presentation of an action in your plug-in without changing the code that actually performs the command once it has been chosen. The contribution classes are used to manage the actual UI items representing the commands. You don't program to the contribution classes, but you will see them in some of the workbench and JFace API.</P>
-
-<H3>
-Actions</H3>
-<P >
-An action (<a href="../reference/api/org/eclipse/jface/action/IAction.html"><b>IAction</b></a>) represents a command
-that can be triggered by the end user. Actions are typically associated with buttons, menu items, and items in tool bars. </P>
-<P >
-Although actions do not place themselves in the UI, they do have UI oriented properties, such as tool tip text, label text,
-and an image. This allows other classes to construct widgets for the presentation of the action.</P>
-<P >
-When the user triggers the action in the UI, the action's run method is invoked to do the actual work. A common pattern in the run method is to query the workbench selections and manipulate the objects that are selected. Another common pattern is to launch a wizard or dialog when an action is chosen. </P>
-<P >
-You should not directly implement the <a href="../reference/api/org/eclipse/jface/action/IAction.html"><b> IAction</b></a> interface. Instead, you should subclass the
-<b><a href="../reference/api/org/eclipse/jface/action/Action.html"> Action</a></b> class. Browse the subclasses of this class to see many of the common patterns for actions. The code below implements the &quot;About&quot; action. It is one of the simpler actions in the workbench.</P>
-<pre>
-   public void run() {
-      new AboutDialog(workbenchWindow.getShell()).open();
-   }
-</pre>
-<P >
-Earlier we saw the workbench interfaces <b><a href="../reference/api/org/eclipse/ui/IViewActionDelegate.html"> IViewActionDelegate</a></b> and
-<b><a href="../reference/api/org/eclipse/ui/IEditorActionDelegate.html">IEditorActionDelegate</a></b>. These interfaces are used when contributing view actions or editor actions to the workbench. The workbench action delegates are initialized with a reference to their associated view or editor. With this knowledge, they can navigate to the workbench page or window, accessing selections or any other information needed to perform the action. </P>
-<P >
-You will implement your own action classes whenever you want to define a command in your plug-in. If you are contributing actions to other views and editors, you will implement action delegates.</P>
-
-
-<H3>
-Contribution items</H3>
-<P >
-A contribution item (<a href="../reference/api/org/eclipse/jface/action/IContributionItem.html"><b>IContributionItem</b></a>) represents the UI portion of an action. More specifically, it represents an item that is contributed to a shared UI resource such as a menu or tool bar.</P>
-<P >
-Contribution items know how to fill a specific SWT widget with the appropriate SWT item that represents the contribution.</P>
-<P >
-You don't have to worry about creating a contribution item when you are
-contributing actions to the workbench UI. This is done on your behalf when the workbench creates UI items for the actions that you have defined.</P>
-
-
-<H3>
-Contribution managers</H3>
-<P >
-A contribution manager (<b><a href="../reference/api/org/eclipse/jface/action/IContributionManager.html">IContributionManager</a></b>) represents a collection of contribution items that will be
-presented in the UI. You can add and insert contribution items using named contribution ids to place the items in the appropriate order. You can also find items by id and remove individual items.</P>
-<P >
-Each implementation of <a href="../reference/api/org/eclipse/jface/action/IContributionManager.html"><b> IContributionManager</b></a> knows how to fill a specific SWT widget with its items. JFace provides contribution managers for
-menus (<b><a href="../reference/api/org/eclipse/jface/action/IMenuManager.html">IMenuManager</a></b>),
-tool bars (<b><a href="../reference/api/org/eclipse/jface/action/IToolBarManager.html">IToolBarManager</a></b>), and status
-lines (<b><a href="../reference/api/org/eclipse/jface/action/IStatusLineManager.html">IStatusLineManager</a></b>).</P>
-<P >
-As a plug-in developer, you do not need to implement these interfaces, but you will see references to some of these managers in API methods.</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/jface_operations.htm b/bundles/org.eclipse.platform.doc.isv/guide/jface_operations.htm
deleted file mode 100644
index f7b4438..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/jface_operations.htm
+++ /dev/null

@@ -1,105 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Long-running operations</title>
-  <link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-<body bgcolor="#ffffff">
-<h2>
-Long-running operations</h2>
-<p>
-The <b><a
- href="../reference/api/org/eclipse/jface/operation/package-summary.html">
-org.eclipse.jface.operations</a></b> package defines interfaces for
-long-running operations that require progress indicators or allow user
-cancellation of the operation.  These interfaces are used in the implementation
-of the workbench progress dialogs and views.</p>
-<p>In general, plug-ins should use the workbench support provided in 
-<a href="../reference/api/org/eclipse/ui/progress/IProgressService.html">IProgressService</a>
-for running long operations, so that all plug-ins will have a consistent presentation
-of progress.  See <a href="workbench_jobs.htm">Workbench Concurrency Support</a> for
-a complete discussion of the available support for progress dialogs and views.  The remainder
-of this discussion highlights the details of the JFace operations infrastructure which is
-used by the workbench.</p>
-<h3>Runnables and progress</h3>
-<p>
-The platform runtime defines a common interface, <b><a
- href="../reference/api/org/eclipse/core/runtime/IProgressMonitor.html">IProgressMonitor</a></b>,
-which is used to report progress to the user while long running
-operations are in progress. The client can provide a monitor as a
-parameter in many platform API methods when it is important to show
-progress to the user.</p>
-<p>JFace defines more specific interfaces for objects that implement
-the user interface for a progress monitor.&nbsp;</p>
-<p>
-<b><a
- href="../reference/api/org/eclipse/jface/operation/IRunnableWithProgress.html">
-IRunnableWithProgress</a></b> is the interface for a long-running
-operation.&nbsp; The <b>run</b>
-method for this interface has an <b><a
- href="../reference/api/org/eclipse/core/runtime/IProgressMonitor.html">IProgressMonitor</a>
-</b>parameter that is used to report progress and check for user
-cancelation.</p>
-<p><a
- href="../reference/api/org/eclipse/jface/operation/IRunnableContext.html"><b>IRunnableContext</b></a>
-is the interface for the different places in the UI where progress can
-be
-reported.&nbsp; Classes that implement this interface may choose to use
-different techniques for showing progress and running the
-operation.&nbsp;
-For example, <b><a
- href="../reference/api/org/eclipse/jface/dialogs/ProgressMonitorDialog.html">ProgressMonitorDialog</a></b>
-implements this interface by showing a progress dialog.&nbsp; <b><a
- href="../reference/api/org/eclipse/ui/IWorkbenchWindow.html">IWorkbenchWindow</a></b>
-implements this interface by showing progress in the workbench window's
-status
-line.&nbsp; <a
- href="../reference/api/org/eclipse/jface/wizard/WizardDialog.html"><b>WizardDialog</b></a>
-implements this interface to show long running operations inside the wizard status line.</p>
-
-<blockquote><i>Note:&nbsp; The workbench UI provides additional support for operations in <b><a
-href="../reference/api/org/eclipse/ui/actions/WorkspaceModifyOperation.html">WorkspaceModifyOperation</a></b>.
-This class simplifies the implementation of long-running operations that modify the workspace. It maps between <a
-href="../reference/api/org/eclipse/jface/operation/IRunnableWithProgress.html"><b>IRunnableWithProgress</b></a>
-and <a href="../reference/api/org/eclipse/core/resources/IWorkspaceRunnable.html"><b>IWorkspaceRunnable</b></a>.&nbsp;
-See the javadoc for further detail.</i></blockquote>
-
-<h3>Modal operations</h3>
-<p>
-The <b><a
- href="../reference/api/org/eclipse/jface/operation/ModalContext.html">
-ModalContext</a></b> class is provided to run an operation that is
-modal from the client code's perspective.
-It is used inside the different implementations of <a
- href="../reference/api/org/eclipse/jface/operation/IRunnableContext.html"><b>IRunnableContext</b></a>.&nbsp;
-If your plug-in needs to wait on the completion of a long-running
-operation before continuing
-execution, <b><a
- href="../reference/api/org/eclipse/jface/operation/ModalContext.html">ModalContext</a></b>
-can be used to accomplish this while still keeping the user interface
-responsive.</p>
-<p>
-When you run an operation in a modal context, you can choose to fork
-the operation in a different thread. If
-<b>fork</b> is false, the operation will be run in the
-calling thread.&nbsp; If <b>fork</b> is true,&nbsp; the
-operation will be run in a new thread, the calling thread will be
-blocked, and
-the UI event loop will be run until the operation
-terminates.&nbsp;&nbsp;</p>
-<p>
-For more information on the UI event loop, see <a class="XRef"
- href="swt_threading.htm"> Threading issues for clients</a>.<br>
-</p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/jface_resources.htm b/bundles/org.eclipse.platform.doc.isv/guide/jface_resources.htm
deleted file mode 100644
index 1d1ca09..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/jface_resources.htm
+++ /dev/null

@@ -1,186 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-User interface resources
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-User interface resources</H2>
-<P >
-The <b><a href="../reference/api/org/eclipse/jface/resource/package-summary.html"> org.eclipse.jface.resource</a></b> package defines classes that help plug-ins manage UI resources such as fonts and icons.</P>
-<P >
-Many of the workbench extension points allow plug-ins to supply icons that can be used to show their contributions in the workbench. Since GUI operating systems support a limited number of images or fonts in memory at once, a plug-in's UI resources must be carefully managed and sometimes shared between widgets.</P>
-<P >
-We've already seen several references to icons in the readme tool plug-in. Some of its icons are specified in the
-<b> plugin.xml</b> markup.</P>
-<pre>&lt;extension
-   point=&quot;org.eclipse.ui.views&quot;&gt;
-	&lt;category
-	   id=&quot;org.eclipse.ui.examples.readmetool&quot;
-	   name=&quot;%Views.category&quot;&gt;
-	&lt;/category&gt;
-	&lt;view
-	   id=&quot;org.eclipse.ui.examples.readmetool.views.SectionsView&quot;
-	   name=&quot;%Views.ReadmeSections&quot;
-	   <b>icon</b>=&quot;icons/view16/sections.png&quot;
-	   category=&quot;org.eclipse.ui.examples.readmetool&quot;
-	   class=&quot;org.eclipse.ui.examples.readmetool.ReadmeSectionsView&quot;&gt;
-	&lt;/view&gt;
-&lt;/extension&gt;</pre>
-<P >
-We've also seen code that describes images on the fly. The following is from the readme tool's
-<b>ReadmeEditorActionBarContributor</b>.</P>
-<pre>public ReadmeEditorActionBarContributor() {
-      	...
-	action1 = new EditorAction(MessageUtil.getString(&quot;Editor_Action1&quot;));
-	action1.setToolTipText(MessageUtil.getString(&quot;Readme_Editor_Action1&quot;));
-<b>	action1.setDisabledImageDescriptor(ReadmeImages.EDITOR_ACTION1_IMAGE_DISABLE);
-	action1.setImageDescriptor(ReadmeImages.EDITOR_ACTION1_IMAGE_ENABLE);
-</b>	...
-</pre>
-<P >JFace provides the basic support classes that allow plug-ins to manage their icons and fonts without worrying about when the corresponding platform graphics objects
-are created and destroyed. These support classes are used directly by plug-ins as shown above, or indirectly when the workbench uses these classes to obtain images that are described in extension point markup.</P>
-
-<H3>
-Image descriptors and the registry</H3>
-<P >
-The SWT <b><a href="../reference/api/org/eclipse/swt/graphics/Image.html">Image</a></b> class represents an image from the operating system's perspective. Because most GUI operating systems have a limit on the number of images that can be open at once, plug-ins should be very careful when creating them,
-and ensure that they also dispose of them properly when finished using them. By using the JFace
-<b><a href="../reference/api/org/eclipse/jface/resource/ImageDescriptor.html"> ImageDescriptor</a></b> and
-<b><a href="../reference/api/org/eclipse/jface/resource/ImageRegistry.html"> ImageRegistry</a></b> classes instead of the SWT image, plug-ins can generally avoid creating, managing, and disposing these images directly.</P>
-
-<H4>
-Image descriptor</H4>
-<P >
-The <b><a href="../reference/api/org/eclipse/jface/resource/ImageDescriptor.html"> ImageDescriptor</a></b> class can be used as a lightweight description of an image. It specifies everything that is needed to create an image, such as the
-URL or filename where the image can be obtained.
-<b><a href="../reference/api/org/eclipse/jface/resource/ImageDescriptor.html"> ImageDescriptors</a></b> do not allocate an actual platform image unless specifically requested using the
-<b> createImage()</b> method. </P>
-<P >
-Image descriptors are the best strategy when your code is structured such that it defines all the icons in one place and allocates them as they are needed. Image descriptors can be created at any time without concern for OS resources, making it convenient to create them all in initialization code. </P>
-
-
-<H4>
-Image registry</H4>
-<P >
-The <a href="../reference/api/org/eclipse/jface/resource/ImageRegistry.html"><b> ImageRegistry</b></a> class is used to keep a list of named images. Clients can add image descriptors or SWT images directly to the list. When an image is requested by name from the registry, the registry will return the image if it has been created, or create one from the descriptor. This allows clients of the registry to share images.</P>
-<P >
-Images that are added to or retrieved from the registry must not be disposed by any client. The registry is responsible for disposing of the image since the images are shared by multiple clients. The registry will dispose of the images when the platform GUI system shuts down.</P>
-
-
-
-<H3>
-<a name="jface_resources_patterns">
-Plug-in patterns for using images</a></H3>
-
-<H4>
-Specifying the image in the plugin.xml</H4>
-<P >
-Where possible, specify the icon for your plug-in's UI objects in the <b> plugin.xml</b> file. Many of the workbench extension points include configuration parameters for an icon file. By defining your icons in your extension contribution in the plugin.xml, you leave the image management strategy up the platform. Since the icons are typically kept in your plug-in's directory, this allows you to specify the icons and manage the files all in one place.</P>
-<P >
-The other patterns should only be considered when you can't specify the icon as part of your extension contribution.</P>
-
-
-<H4>
-Explicit creation</H4>
-<P >
-Explicitly creating an image is the best strategy when the image is infrequently used and not shared. The image can be created directly in SWT and disposed after it is used.</P>
-<P >
-Images can also be created explicitly using an <b><a href="../reference/api/org/eclipse/jface/resource/ImageDescriptor.html"> ImageDescriptor</a></b> and invoking the
-<b> createImage()</b> method. As in the first case, the dispose() method for the image must be invoked after the image is
-no longer needed.&nbsp; For example, if a dialog creates an image when it is
-opened, it should dispose the image when it is closed.</P>
-
-
-<H4>
-Image registry</H4>
-<P >
-When an image is used frequently in a plug-in and shared across many different objects in the UI, it is useful to register the image descriptor with an
-<a href="../reference/api/org/eclipse/jface/resource/ImageRegistry.html"><b>ImageRegistry</b></a>. The images in the registry will be shared with any object that queries an image by the same name. You must not dispose any images in the registry since they are shared by other objects.</P>
-<P >
-Adding an image to the image registry is the best strategy when the image is used frequently, perhaps through the lifetime of the plug-in, and is shared by many objects. The disadvantage of using the registry is that images in the registry are not disposed until the
-GUI system shuts down. Since there is a limit on the number of platform (SWT) images that can be open at one time, plug-ins should be careful not to register too many icons in a registry.</P>
-<P >
-The class <b><a href="../reference/api/org/eclipse/ui/plugin/AbstractUIPlugin.html"> AbstractUIPlugin</a></b> includes protocol for creating a plug-in wide image registry.</P>
-
-
-<H4>
-Label providers</H4>
-<P >
-When an icon is used frequently to display items in a particular viewer, it can be shared among similar items in the viewer using a label provider. Since a label provider is responsible for returning an image for any
-object in a viewer, it can control the creation of the image and any sharing of images across objects in the viewer. </P>
-<P >
-The label provider can use any of the previously discussed techniques to produce an image. If you browse the various implementations of
-<b> getImage()</b> in the <b><a href="../reference/api/org/eclipse/jface/viewers/LabelProvider.html"> LabelProvider</a></b> subclasses, you will see a variety of approaches including caching a single icon for objects and maintaining a table of images by type.&nbsp;
-Images created by a label provider must be disposed in the provider's <b>dispose()
-</b>method, which is called when the viewer is disposed.</P>
-<P >
-Using a label provider is a good compromise between explicit creation and the image registry. It promotes sharing of icons like the image registry, yet still maintains control over the creation and disposal of the actual image.</P>
-
-
-<H4>
-Plug-in wide image class</H4>
-<P >
-When fine-tuning a plug-in, it is common to experiment with all of these different image creation patterns. It
-can be useful to isolate the decision making regarding image creation in a separate class and instruct all clients to use the class to obtain all images. This way, the creation sequence can be tuned to reflect the actual performance characteristics of the plug-in.&nbsp;</P>
-
-<H3> ResourceManager</H3>
-<P > The <a href="../reference/api/org/eclipse/jface/resource/ResourceManager.html"><b> 
-  ResourceManager</b></a> class is used to keep a mapping of ImageDescriptors 
-  to Images so that an Image can be reused be referring to it via it's descriptor.When 
-  an image is requested by descriptor from the registry, the registry will return 
-  the image if it has been created, or create one from the descriptor. This allows 
-  clients of the registry to share images. </P>
-<P >The top level ResourceManager is a <a href="../reference/api/org/eclipse/jface/resource/DeviceResourceManager.html"><strong>DeviceResourceManager</strong></a> 
-  which is created on a Display. The ResourceManager defined by <strong><a href="../reference/api/org/eclipse/jface/resource/JFaceResources.html">JFaceResources</a></strong>.<strong>getResources() 
-  </strong>is a DeviceResourceManager and can be used as the top level ResourceManager. 
-  If you need a ResourceManager with a shorter lifecycle than the DeviceResourceManager 
-  you can create a <strong><a href="../reference/api/org/eclipse/jface/resource/LocalResourceManager.html">LocalResourceManager</a></strong> 
-  as a child and dispose of it when you are done with it.</P>
-<P >A DeviceResourceManager will be disposed when the Display used to create it 
-  is disposed so no special management code is required.</P>
-<P > Images that are added to or retrieved from the manager must not be disposed 
-  by any client. The manager is responsible for disposing of the image since the 
-  images are shared by multiple clients. The registry will dispose of the images 
-  when the ResourceManager that holds onto them is disposed.</P>
-<H3> Font registry</H3>
-<P >
-Fonts are another limited resource in platform operating systems. The creation and disposal issues are the same for fonts as
-for images, requiring similar speed/space tradeoffs. In general, fonts are allocated in SWT by requesting a font with a platform dependent font name.</P>
-<P >
-The <b><a href="../reference/api/org/eclipse/jface/resource/FontRegistry.html"> FontRegistry</a></b> class keeps a table of fonts by their name. It manages the allocation and disposal of the font.</P>
-<P >
-In general, plug-ins should avoid allocating any fonts or describing fonts with platform specific names. Although the font registry is used internally in JFace, it is typically not used by plug-ins. The
-<b><a href="../reference/api/org/eclipse/jface/resource/JFaceResources.html"> JFaceResources</a></b> class should be used to access common fonts.</P>
-<P >It is very common to allow users to specify their preferences for the
-application's fonts in a preference page.&nbsp; In these cases, the
-<b><a href="../reference/api/org/eclipse/jface/preference/FontFieldEditor.html"> FontFieldEditor</a></b> should be used to obtain the font name from the user, and a
-<b><a href="../reference/api/org/eclipse/jface/resource/FontRegistry.html"> FontRegistry</a></b> may be used to keep the font.&nbsp;
-The
-<b><a href="../reference/api/org/eclipse/jface/preference/FontFieldEditor.html"> FontFieldEditor</a></b>
-is only used in preference pages.</P>
-
-
-<H3>
-JFaceResources</H3>
-<P >
-The class <a href="../reference/api/org/eclipse/jface/resource/JFaceResources.html"><b> JFaceResources</b></a> controls access to common platform fonts and images. It maintains an internal font and image registry so that clients can share named fonts and images.</P>
-<P >
-There are many techniques used in the workbench and other plug-ins to share images where required. The
-<a href="../reference/api/org/eclipse/jface/resource/JFaceResources.html"><b> JFaceResources</b></a> image registry is not widely used across the workbench and plug-in code.</P>
-<P >
-Use of fonts is much simpler. The workbench and most plug-ins use the <a href="../reference/api/org/eclipse/jface/resource/JFaceResources.html"><b> JFaceResources</b></a> class to request fonts by logical name. Methods such as
-<b> getDialogFont() </b> and <b> getDefaultFont()</b> are provided so that plug-ins can use the expected fonts in their UI.</P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/jface_viewers.htm b/bundles/org.eclipse.platform.doc.isv/guide/jface_viewers.htm
deleted file mode 100644
index 12d9901..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/jface_viewers.htm
+++ /dev/null

@@ -1,228 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Viewers
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Viewers</H2>
-<P >
-Why would you ever want to use a viewer when we have already seen that workbench
-UI contributions like views, editors, wizards, and dialogs can be implemented
-directly with SWT widgets?&nbsp;&nbsp;</P>
-<P >Viewers allow you to create widgets while still using your model
-objects.&nbsp; If you use an SWT widget directly, you have to convert your
-objects into the strings and images expected by SWT.&nbsp; Viewers act as
-adapters on SWT widgets, handling the common code for handling widget events
-that you would otherwise have to implement yourself.&nbsp;</P>
-<P > We first saw a viewer in the readme tool's view contribution, inside the
-<b>ReadmeSectionsView</b>.</P>
-<pre>
-   public void createPartControl(Composite parent) {
-      viewer = new ListViewer(parent);
-      ...
-   }
-</pre>
-<blockquote><i>
-Note:&nbsp; Viewers can be used to provide the implementation for both workbench views and editors. The term viewer does not imply that they are only useful for implementing views. For example, the
-<b> TextViewer</b> is used in the implementation in many of the workbench and plug-in editors.</i></blockquote>
-
-<H3>
-Standard viewers</H3>
-<P >JFace provides viewers for most of the non-trivial widgets in SWT. Viewers are most commonly used for
-list, tree, table, and text widgets.&nbsp;</P>
-<P >
-Each viewer has an associated SWT widget. This widget can be created implicitly by supplying the parent
-<b> Composite</b> in a convenience viewer constructor, or explicitly by creating it first and supplying it to the viewer in its constructor.</P>
-<h4 ><a name="listviewer">List-oriented viewers</a></h4>
-<P > Lists, trees, and tables share many common capabilities from a user's point of view, such as population with objects, selection, sorting, and filtering.&nbsp;</P>
-<P >These viewers keep
-a list of domain objects (called <b>elements</b>) and display them in their
-corresponding SWT widget. A list viewer knows how to get a text label from any
-element in the list.&nbsp; It obtains the label from an <a href="../reference/api/org/eclipse/jface/viewers/ILabelProvider.html"><b>ILabelProvider</b></a>
-which can be set on the viewer.&nbsp; List viewers know how to map from the widget callbacks back into the
-world of elements known by the viewer client.</P>
-<P >
-Clients that use a plain SWT widget have to operate
-at the SWT level - where items are strings and events often relate to an index within the list of strings. Viewers provide higher level semantics. Clients are notified of selections and changes to the list
-using the elements they provided to the viewer. The viewer handles all the grunt work for mapping indexes back to
-elements, adjusting for a filtered view of the objects, and re-sorting when necessary.</P>
-<P >
-Filtering and sorting capability is handled by designating a viewer sorter (<a href="../reference/api/org/eclipse/jface/viewers/ViewerSorter.html"><b>ViewerSorter</b></a>)
-and/or viewer filter (<a href="../reference/api/org/eclipse/jface/viewers/ViewerFilter.html"><b>ViewerFilter</b></a>)
-for the viewer. (These can be specified for tree and table viewers in addition to
-list viewers.) The client need only provide a class that can compare or filter the objects in the list. The viewer handles the details of populating the list according to the specified order and
-filter, and maintaining the order and filter as elements are added and removed.</P>
-
-
-<P >
-Viewers are not intended to be extended by clients.&nbsp; To customize a viewer,
-you can configure it with your own content and label providers.</P>
-
-
-<P >A <b><a href="../reference/api/org/eclipse/jface/viewers/ListViewer.html">ListViewer</a></b>
-maps elements in a list to an SWT <b><a href="../reference/api/org/eclipse/swt/widgets/List.html">List</a></b>
-control.</P>
-
-<P >
-A <a href="../reference/api/org/eclipse/jface/viewers/TreeViewer.html"><b> TreeViewer</b></a> displays hierarchical objects in an SWT
-<a href="../reference/api/org/eclipse/swt/widgets/Tree.html"><b> Tree</b></a> widget. It handles the
-details for expanding and collapsing items. There are several different kinds of tree viewers for different SWT tree controls (plain tree, table tree, checkbox tree).</P>
-<P >A <a href="../reference/api/org/eclipse/jface/viewers/TableViewer.html"><b>TableViewer</b></a> 
-  is very similar to a list viewer, but adds the ability to view multiple columns 
-  of information for each element in the table.&nbsp; Table viewers significantly 
-  extend the function of the SWT table widget by introducing the concept of editing 
-  a cell. Special cell editors can be used to allow the user to edit a table cell 
-  using a combo box, dialog, or text widget. The table viewer handles the creation 
-  and placement of these widgets when needed for user editing.&nbsp; This is done 
-  using the <b><a href="../reference/api/org/eclipse/jface/viewers/CellEditor.html">CellEditor</a></b> 
-  classes, such as <b><a href="../reference/api/org/eclipse/jface/viewers/TextCellEditor.html">TextCellEditor</a></b> 
-  and <b><a href="../reference/api/org/eclipse/jface/viewers/CheckboxCellEditor.html">CheckboxCellEditor</a></b>. 
-  A virtual table, only populated when viewed, the table viewer only runs a designated 
-  number of results regardless of what is actually created. The database &quot;lazily&quot; 
-  requests JIT and will only query a predetermined number at a time.</P>
-
-
-<H4>
-Text viewer</H4>
-<P >
- Text widgets have many common semantics such as double click behavior, undo, coloring, and navigating by index or line.&nbsp;
-A <b><a href="../reference/api/org/eclipse/jface/text/TextViewer.html">TextViewer</a></b>
-is an adapter for an SWT <a href="../reference/api/org/eclipse/swt/custom/StyledText.html"><b>StyledText</b></a>
-widget. Text viewers provide a document model to the client and manage the conversion of the document to the styled text information provided by the text widget.</P>
-<P >
-Text viewers are covered in more detail in <a HREF="editors.htm" CLASS="XRef">Workbench
-Editors</a>.</P>
-
-
-
-<H3>
-Viewer architecture</H3>
-<P >
-To understand a viewer, you must become familiar with the relationship between a viewer's input element, its contents, its selection, and the information actually displayed in the widget that it is manipulating.</P>
-
-<H4>
-Input elements</H4>
-<P >
-An <b> input element</b> is the main object that the viewer is displaying (or editing). From the viewer's point of view, an input element can be any object at all. It does not assume any particular interface is implemented by the input element. (We'll see why in a moment when we look at content providers.)</P>
-<P >
-A viewer must be able to handle a change of input element. If a new input element is set into a viewer, it must repopulate its widget according to the new element, and disassociate itself from the previous input element. The semantics
-for registering as a listener on an input element and populating the widget
-based on the element are different for each kind of viewer.</P>
-
-
-<H4>
-Content viewers</H4>
-<P >
-A <b> content viewer</b> is a viewer that has a well defined protocol for obtaining information from its input element. Content viewers use two specialized helper classes, the
-<b><a href="../reference/api/org/eclipse/jface/viewers/IContentProvider.html">IContentProvider</a></b> and
-<b><a href="../reference/api/org/eclipse/jface/viewers/ILabelProvider.html">ILabelProvider</a></b>, to populate their widget and display information about the input element.</P>
-<P >
-<b><a href="../reference/api/org/eclipse/jface/viewers/IContentProvider.html">
-IContentProvider</a></b> provides basic lifecycle protocol for associating a content provider with an input element and handling a change of input element. More specialized content providers are implemented for different kinds of viewers. The most common content provider is
-<b><a href="../reference/api/org/eclipse/jface/viewers/IStructuredContentProvider.html">IStructuredContentProvider</a></b>, which can provide a list of objects given an input element. It is used in list-like viewers, such as lists, tables, or trees. In general, the content provider knows how to map between the input element and the expected viewer content.</P>
-<P >
-<b><a href="../reference/api/org/eclipse/jface/viewers/ILabelProvider.html">
-ILabelProvider</a></b> goes a step further. Given the content of a viewer (derived from the input element and content provider), it can produce the specific UI elements, such as names and icons, that are needed to display the content in the viewer. Label providers can aid in saving icon resources since they can ensure the same instance of the icon is used for all like types in a viewer.</P>
-<blockquote><i>
-Note:&nbsp; Instances of particular content and label providers are not intended to be shared across multiple viewers. Even if all your viewers use the same type of content or label provider, each viewer should be initialized with
-its own instance of the provider class. The provider life cycle protocol is
-designed for a 1-to-1 relationship between a provider and its
-viewer.</i></blockquote>
-<P > Input elements, content providers, and label providers allow viewers to hide 
-  most of the implementation details for populating widgets. Clients of a viewer 
-  need only worry about populating a viewer with the right kind of input and content 
-  provider. The label provider must know how to derive the UI information from 
-  the viewer content.</P>
-<P >A label provider can show more than just text and an image. JFace provides 
-  several classes and interfaces to support the most popular extra functionality. 
-  The following classes are supported by the TableViewer, AbstractTreeViewer and 
-  TableTreeViewer. </P>
-<ul>
-  <li><b><a href="../reference/api/org/eclipse/jface/viewers/IColorProvider.html">
-IColorProvider</a></b> . If an label provider implements IColorProvider it will set 
-    the foreground and background color of an item in the viewer when it returns 
-    a color. It is recommended that unless system colors are used that these colors 
-    are cached to minimize the amount of system resources used.</li>
-  <li><b><a href="../reference/api/org/eclipse/jface/viewers/IFontProvider.html">
-IFontProvider</a></b> . If an label provider implements IFontProvider it will set 
-    the font of an item in the viewer when it returns a font. Fonts should also 
-    be cached. <b><a href="../reference/api/org/eclipse/swt/widgets/IFontProvider.html">
-Control#getFont()</a></b> should be called as little as possible as this 
-    will create a new instance of Font whenever it is called.</li>
-  <li><b><a href="../reference/api/org/eclipse/jface/viewers/ILabelDecorator.html">
-ILabelDecorator</a></b>  An ILabelDecorator is an object that can take an image or 
-    text and add adornments to them.</li>
-  <li><b><a href="../reference/api/org/eclipse/jface/viewers/DecoratingLabelProvider.html">
-DecoratingLabelProvider</a></b>  The DecoratingLabelProvider is a compound object 
-    that takes both a label provider and an ILabelDecorator. This allows a label 
-    provider to hook into a decorator mechanism such as the one provided in the 
-    Workbench.</li>
-  <li><b><a href="../reference/api/org/eclipse/jface/viewers/IViewerLabelProvider.html">
-IViewerLabelProvider</a></b>  The IViewerLabelProvider is a label provider that allows 
-    for building of labels by an external object such as a decorator. The DecoratingLabelProvider 
-    is an IViewerLabelProvider.</li>
-  <li><b><a href="../reference/api/org/eclipse/jface/viewers/IDelayedLabelDecorator.html">
-IDelayedLabelDecorator</a></b>  The IDelayedLabelDecorator is an ILabelDecorator 
-    that supports decoration that is delayed (such as an IDecoratorManager that 
-    decorates in a Thread). IDecoratorManagers are IDelayedLabelDecorators. You 
-    can get the Workbench <b><a href="../reference/api/org/eclipse/ui/IDecoratorManager.html">
-IDecoratorManager</a></b> 
-
-IDecoratorManager by calling <b><a href="../reference/api/org/eclipse/ui/IWorkbench.html">
-IWorkbench#getDecoratorManager()</a></b> 	
-	.</li>
-  <li><b><a href="../reference/api/org/eclipse/jface/viewers/IColorDecorator.html">
-IColorDecorator</a></b>  An IColorDecorator is an object that can support decorating 
-    foreground and background colors. This is supported internally in the Workbench 
-    DecoratorManager. </li>
-  <li><b><a href="../reference/api/org/eclipse/jface/viewers/IFontDecorator.html">
-IFontDecorator</a></b>  An IFontDecorator is an object that can support decorating 
-    fonts. This is supported internally in the Workbench DecoratorManager. </li>
-</ul>
-<P >It is possible to affect the colors of a view in two ways as of Eclipse 3.1 
-  - either with its own label provider or with a decorator that sets colors and 
-  fonts. Generally it is better to use the color and font support in label providers 
-  as decorators affect every view that show a particular type. If you do use a 
-  color or font decorator make sure it's values can be set in the Colors and Fonts 
-  preference page.</P>
-
-
-
-<H3>
-Viewers and the workbench</H3>
-<P >
-The flexibility provided by viewers, content providers, and label providers can be demonstrated by looking at how the workbench uses them.</P>
-<P >
-The <b><a href="../reference/api/org/eclipse/ui/model/WorkbenchContentProvider.html"> WorkbenchContentProvider</a></b> is a structured content provider that obtains contents from an input element by asking for its children. The concept of adapters is used again in order to implement generic function. When asked for the list of elements from its input element, the
-<b><a href="../reference/api/org/eclipse/ui/model/WorkbenchContentProvider.html"> WorkbenchContentProvider</a></b> obtains an
-<b><a href="../reference/api/org/eclipse/ui/model/IWorkbenchAdapter.html">IWorkbenchAdapter</a></b> for the input element. If an
-<b><a href="../reference/api/org/eclipse/ui/model/IWorkbenchAdapter.html">IWorkbenchAdapter</a></b> has been registered for the input element, then the content provider can safely assume that the element can be queried for its
-children.&nbsp; <b><a href="../reference/api/org/eclipse/ui/model/WorkbenchContentProvider.html">WorkbenchContentProvider</a>
-</b>also does the work needed to keep its viewer up to date when the
-workspace changes.&nbsp;</P>
-<P >
-The <b><a href="../reference/api/org/eclipse/ui/model/WorkbenchLabelProvider.html">WorkbenchLabelProvider</a></b>
-is a label provider that obtains an <b><a href="../reference/api/org/eclipse/ui/model/IWorkbenchAdapter.html">IWorkbenchAdapter</a></b> from an object in order to find its text and image. The concept of a label provider is particularly helpful for workbench objects because it allows a single label provider to cache images that are commonly used in a viewer. For example, once the
-<b><a href="../reference/api/org/eclipse/ui/model/WorkbenchLabelProvider.html">WorkbenchLabelProvider</a></b> obtains an image to use for an
-<b><a href="../reference/api/org/eclipse/core/resources/IProject.html">IProject</a></b>, it can cache that image and use it for all
-<b><a href="../reference/api/org/eclipse/core/resources/IProject.html"> IProject</a></b> objects shown in the viewer.</P>
-<P > By defining a common adapter, <b><a href="../reference/api/org/eclipse/ui/model/IWorkbenchAdapter.html">IWorkbenchAdapter</a></b>, 
-  and registering it for many of the platform types, we make it possible for these 
-  types to be represented correctly in many of the common viewers and the workbench 
-  views that contain them. </P>
-<P >&nbsp;</P>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/multiplexing_interface.htm b/bundles/org.eclipse.platform.doc.isv/guide/multiplexing_interface.htm
deleted file mode 100644
index c0f3976..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/multiplexing_interface.htm
+++ /dev/null

@@ -1,149 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Multiplexing an interface</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2> Multiplexing an interface</h2>
-<p>Many composite parts will have the notion of an active child. Such parts may 
-  want to dynamically attach a dependency to the child that is currently active. 
-  <br>
-  <br>
-  For example, we may want to create a view that arranges its children in a tab 
-  folder. The parent may want to set its own name and icon to match that of its 
-  active child. We could accomplish this using the following pattern: </p>
-<ul>
-  <li> Remember the current name and icon for each child part;</li>
-  <li> Set the initial name and icon to its default value (read from IPartDescriptor);</li>
-  <li> Attach an INameable to each child that listens to name and icon changes;</li>
-  <li> Whenever the name or icon of the active part changes, change the name and 
-    icon of the outer part to match;</li>
-  <li> Whenever the active child changes, change the name and icon of the outer 
-    part to the saved name and icon for the child.</li>
-</ul>
-We will refer to this as multiplexing the INameable interface.<br>
-<br>
-In general, the multiplexer pattern works like this: 
-<ul>
-  <li> Remember some state for each child, with an appropriate initial value;</li>
-  <li> Keep track of state changes in all children;</li>
-  <li> When the state of the active child changes, forward the change to a shared 
-    interface;</li>
-  <li> When a new child becomes active, forward its entire state to the shared 
-    interface.</li>
-</ul>
-Since this pattern is quite common, we supply a Multiplexer class to support it. 
-Clients that supply new types of interfaces using the <span
- style="font-style: italic;">org.eclipse.core.component.types </span>extension 
-point can also supply a multiplexed version of their interface. The multiplexed 
-version will: 
-<ul>
-  <li>Implement the interface;</li>
-  <li> Know what state to remember for each child and what the initial value should 
-    be;</li>
-  <li> Receive notifications when it is activated/deactivated;</li>
-  <li> Forward its state to a shared instance when it is active. </li>
-</ul>
-Clients using the Multiplexer don't need to know the details of multiplexing each 
-interface. They can simply attach an INameable to the multiplexer as though it 
-was a part, and attach the multiplexer to each child part as though it were an 
-INameable. This is shown in the following example, use of the multiplexer has 
-been highlighted in red. Multiplexers need to be explicitly disposed.<br>
-<code><br>
-</code> 
-<div style="margin-left: 40px;"><code>public class MultiplexNameView implements 
-  IDisposable {</code><br>
-  <code>&nbsp;&nbsp;&nbsp; private Multiplexer mplex;</code><br>
-  <code>&nbsp;&nbsp;&nbsp; </code><br>
-  <code>&nbsp;&nbsp;&nbsp; private ISite view1;</code><br>
-  <code>&nbsp;&nbsp;&nbsp; private ISite view2;</code><br>
-  <code>&nbsp;&nbsp;&nbsp; </code><br>
-  <code>&nbsp;&nbsp;&nbsp; private Listener focusListener = new Listener() {</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /* (non-Javadoc)</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * @see org.eclipse.swt.widgets.Listener#handleEvent(org.eclipse.swt.widgets.Event)</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; */</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; public void handleEvent(Event 
-  e) {</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if 
-  (e.widget == view1.getControl()) {</code><br>
-  <code style="color: rgb(255, 0, 0);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  mplex.setActivePart(view1);</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; } else 
-  if (e.widget == view2.getControl()) {</code><br>
-  <code style="color: rgb(255, 0, 0);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  mplex.setActivePart(view2);</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  </code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </code><br>
-  <code>&nbsp;&nbsp;&nbsp; };</code><br>
-  <code>&nbsp;&nbsp;&nbsp; </code><br>
-  <code>&nbsp;&nbsp;&nbsp; /**</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp; * Component constructor. Do not invoke directly.</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp; */</code><br>
-  <code>&nbsp;&nbsp;&nbsp; public MultiplexNameView(Composite parent, IPartFactory 
-  factory, INameable name) throws CoreException {</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Create a multiplexer. Redirect 
-  our INameable to the multiplexer</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span
- style="color: rgb(255, 0, 0);">mplex = new Multiplexer(new ContainerContext().addInstance(INameable.class, 
-  name));</span></code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Create a resource navigator. 
-  Give the navigator a multiplexed INameable, but use</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // defaults for all of the 
-  other interfaces.</code><br>
-  <code style="color: rgb(255, 0, 0);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  ContainerContext viewContext1 = new ContainerContext()</code><br
- style="color: rgb(255, 0, 0);">
-  <code style="color: rgb(255, 0, 0);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  .delegateTo(INameable.class, mplex); </code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; view1 = factory.createView(</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  IPageLayout.ID_RES_NAV, parent, viewContext1, null);</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; view1.getControl().addListener(SWT.Activate, 
-  focusListener);</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Create property view. Give 
-  the properties view a multiplexed INameable, but use</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // defaults for everything 
-  else.</code><br>
-  <code style="color: rgb(255, 0, 0);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  ContainerContext viewContext2 = new ContainerContext()</code><br
- style="color: rgb(255, 0, 0);">
-  <code style="color: rgb(255, 0, 0);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  .delegateTo(INameable.class, mplex);</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; view2 = factory.createView(IPageLayout.ID_PROP_SHEET, 
-  parent, viewContext2, null);</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; view2.getControl().addListener(SWT.Activate, 
-  focusListener);</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Make the navigator active 
-  initially</code><br>
-  <code style="color: rgb(255, 0, 0);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  mplex.setActivePart(view1);</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; parent.setLayout(new FillLayout());&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  </code><br>
-  <code>&nbsp;&nbsp;&nbsp; }</code><br>
-  <code>&nbsp;&nbsp;&nbsp; </code><br>
-  <code>&nbsp;&nbsp;&nbsp; /* (non-Javadoc)</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp; * @see org.eclipse.core.component.IDisposable#dispose()</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp; */</code><br>
-  <code>&nbsp;&nbsp;&nbsp; public void dispose() {</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mplex.dispose();</code><br>
-  <code>&nbsp;&nbsp;&nbsp; }</code><br>
-  <code>}</code><br>
-</div>
-<h2>&nbsp; </h2>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/nesting.htm b/bundles/org.eclipse.platform.doc.isv/guide/nesting.htm
deleted file mode 100644
index 207c0ca..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/nesting.htm
+++ /dev/null

@@ -1,74 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Nesting</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2> Nesting</H2>
-To the outside world, every part is a black box. The part can use IPartFactory 
-to create nested children however it sees fit, but it does not expose those children 
-directly to the outside world. The following example demonstrates a view with 
-two nested children. <br>
-<br>
-<div style="margin-left: 40px;"><code>/**<br>
-  &nbsp;* Example view containing a nested error log on the left and a nested 
-  property <br>
-  &nbsp;* view on the right.<br>
-  &nbsp;* <br>
-  &nbsp;* @since 3.1<br>
-  &nbsp;*/<br>
-  public class TestCompositeView {<br>
-  &nbsp;&nbsp;&nbsp; <br>
-  &nbsp;&nbsp;&nbsp; public TestCompositeView(Composite parent, IPartFactory factory) 
-  throws CoreException {&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; <br>
-  <span style="color: rgb(255, 0, 0);">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; // 
-  Create PDE error log view</span><br
- style="color: rgb(255, 0, 0);">
-  <span style="color: rgb(255, 0, 0);">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; ContainerContext 
-  logViewContext = new ContainerContext();&nbsp;&nbsp;&nbsp; </span><br
- style="color: rgb(255, 0, 0);">
-  <span style="color: rgb(255, 0, 0);">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; ISite 
-  logView = factory.createView(</span><br
- style="color: rgb(255, 0, 0);">
-  <span style="color: rgb(255, 0, 0);">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  "org.eclipse.pde.runtime.LogView", </span><br
- style="color: rgb(255, 0, 0);">
-  <span style="color: rgb(255, 0, 0);">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  parent, logViewContext, null);</span><br style="color: rgb(255, 0, 0);">
-  <br style="color: rgb(255, 0, 0);">
-  <span style="color: rgb(255, 0, 0);">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; // 
-  Create Property view</span><br
- style="color: rgb(255, 0, 0);">
-  <span style="color: rgb(255, 0, 0);">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; ContainerContext 
-  emptyContext = new ContainerContext();</span><br style="color: rgb(255, 0, 0);">
-  <span style="color: rgb(255, 0, 0);">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; ISite 
-  propertiesView = factory.createView(IPageLayout.ID_PROP_SHEET, parent, emptyContext, 
-  null);</span><br>
-  <br>
-  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; // Construct layout<br>
-  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; GridLayout layout = new GridLayout();<br>
-  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; layout.numColumns = 2;<br>
-  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; parent.setLayout(layout);<br>
-  <br>
-  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; // Arrange error log view<br>
-  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; GridData data1 = new GridData(GridData.FILL_BOTH);<br>
-  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; logView.getControl().setLayoutData(data1);<br>
-  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; <br>
-  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; // Arrange properties view<br>
-  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; GridData data2 = new GridData(GridData.FILL_BOTH);<br>
-  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; propertiesView.getControl().setLayoutData(data2);<br>
-  <br>
-  &nbsp;&nbsp;&nbsp; }<br>
-  }</code><br>
-  <br>
-</div>
-<span style="font-weight: bold;"> </span>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/part_interfaces.htm b/bundles/org.eclipse.platform.doc.isv/guide/part_interfaces.htm
deleted file mode 100644
index 527a113..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/part_interfaces.htm
+++ /dev/null

@@ -1,102 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Part interfaces</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<div style="margin-left: 40px;">
-<h2>Part interfaces</h2>
- <p>Parts do not need to implement any particular interface or inherit from any 
-    particular base class. However, parts may optionally implement certain interfaces 
-    in order to receive callbacks from their parent. For example, if a part implements 
-    the IFocusable interface then its parent will use that interface to give focus 
-    to the part. Parts are allowed to either implement the interface directly 
-    or implement IAdaptable and provide an adapter for the interface.<br>
-    <br>
-    Similarly to site interfaces, part interfaces are registered in the <span
- style="font-style: italic;">org.eclipse.core.component.types </span>extension 
-    point. There is a slight difference in the XML markup to distinguish between 
-    a site interface and a part interface. Any plugin can extend the set of interfaces 
-    available for a view to implement, and the PDE plugin registry can be used 
-    to find all such interfaces.<br>
-    <br>
-    The workbench provides the following interfaces to be implemented by parts: 
-  </p>
-  <table style="width: 100%; text-align: left;" border="1" cellpadding="2"
- cellspacing="2">
-    <tbody>
-      <tr> 
-        <td style="vertical-align: top; font-weight: bold;">Interface<br> </td>
-        <td style="vertical-align: top; font-weight: bold;">Description<br> </td>
-      </tr>
-      <tr> 
-        <td style="vertical-align: top;">IFocusable<br> </td>
-        <td style="vertical-align: top;">Allows the part to implement setFocus.<br> 
-        </td>
-      </tr>
-      <tr> 
-        <td style="vertical-align: top;">IPersistable<br> </td>
-        <td style="vertical-align: top;">Allows the part to save its state between 
-          sessions.<br> </td>
-      </tr>
-      <tr> 
-        <td style="vertical-align: top;">IMultiPart<br> </td>
-        <td style="vertical-align: top;">Indicates that the part has the notion 
-          of an active child.<br> </td>
-      </tr>
-      <tr> 
-        <td style="vertical-align: top;">ISite<br> </td>
-        <td style="vertical-align: top;">Although this is never actually implemented 
-          by a part, the implementations of other part interfaces can depend on 
-          ISite in order to gain access to their site.<br> </td>
-      </tr>
-    </tbody>
-  </table>
-  <br>
-  Parts may also implement lifecycle interfaces. Lifecycle interfaces are different 
-  from regular part interfaces in several ways: 
-  <ul>
-    <li>A lifecycle interface must be implemented directly (it cannot be provided 
-      as an adapter);</li>
-    <li>Any or all of a part's dependencies may also implement the lifecycle interface;</li>
-    <li>When a lifecycle notification is sent to a part, it is also sent to all 
-      of the part's dependencies;</li>
-    <li>Lifecycle interfaces are hardcoded, and are not registered with an extension 
-      point.<br>
-    </li>
-  </ul>
-  Parts support the following lifecycle interfaces:<br>
-  <table style="width: 100%; text-align: left;" border="1" cellpadding="2"
- cellspacing="2">
-    <tbody>
-      <tr> 
-        <td style="vertical-align: top; font-weight: bold;">Interface<br> </td>
-        <td style="vertical-align: top; font-weight: bold;">Description<br> </td>
-      </tr>
-      <tr> 
-        <td style="vertical-align: top;">IDisposable<br> </td>
-        <td style="vertical-align: top;">Receives a notification when the component 
-          is disposed.<br> </td>
-      </tr>
-      <tr> 
-        <td style="vertical-align: top;">INestedComponent<br> </td>
-        <td style="vertical-align: top;">Implemented by children of a multiplexer. 
-          Receives activate and deactivate messages when the active part changes.<br> 
-        </td>
-      </tr>
-    </tbody>
-  </table>
-  <br>
-  <br>
-
-</div>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/passing_arguments.htm b/bundles/org.eclipse.platform.doc.isv/guide/passing_arguments.htm
deleted file mode 100644
index 5421803..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/passing_arguments.htm
+++ /dev/null

@@ -1,206 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Passing arguments to a part</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2> Passing arguments to a part</h2>
-A parent passes arguments to its children using a ContainerContext. The context 
-can pass arguments to the constructor of a part or specify a factory for constructing 
-those arguments. For example, a particular ContainerContext might specify rules 
-like:<br>
-<ul>
-  <li>If the child asks for an INameable, use object X; </li>
-  <li>If the child asks for an IActionBars, construct one using factory Y;</li>
-  <li>If the child asks for any unknown type and object Z can be adapted to that 
-    type, return the adapter; </li>
-  <li>If the child asks for a dependency that can't be satisfied in any other 
-    way, redirect to some other context.</li>
-</ul>
-If the context doesn't supply a particular dependency, the child will use the 
-default implementation from the <span
- style="font-style: italic;">org.eclipse.core.component.types</span> extension 
-point. Since the context can override any of the arguments a part gets in its 
-constructor, the parent can override any of the interfaces the part normally obtains 
-from its site. For example, the parent could force its child to use a different 
-implementation of IActionBars by supplying an IActionBars in the context.<br>
-<p>The parent has several options for constructing the context:</p>
-<ul>
-  <li>Provide the child with a specific instance for one of its dependencies;</li>
-  <li>Provide the child with a factory to construct one of its dependencies, if 
-    needed; </li>
-  <li>Redirect some or all of its own dependencies to one of its children; </li>
-  <li>Use a multiplexer to dynamically redirect one or more dependencies to its 
-    active child; </li>
-  <li>Let the child use the default implementation for some or all of its dependencies. 
-  </li>
-</ul>
-The following <span style="font-weight: bold;">DefaultContextView</span>, <span style="font-weight: bold;">RedirectContextView</span> 
-and <span style="font-weight: bold;">OverrideInstanceView</span> examples demonstrate 
-each possibility. 
-<h3> Default context</h3>
-The following example shows the source for a view that creates two nested children 
-in the default context. The fact that the children are created in the default 
-context means that the parent doesn't care about the child's name, toolbar, selection, 
-and so on and isn't prepared to deal with them. If the parent wanted to do something 
-with, say, the current selection in one of its children, it would have needed 
-to pass an ISelectionHandler to that child. The end result is shown below the 
-example.<br>
-<br>
-<span style="font-weight: bold;"> </span> 
-<div style="margin-left: 40px;"><code>/**</code><br>
-  <code>&nbsp;* View that demonstrates how to create two nested children </code><br>
-  <code>&nbsp;* with the default context.</code><br>
-  <code>&nbsp;*/</code><br>
-  <code>public class DefaultContextView {</code><br>
-  <code>&nbsp;&nbsp;&nbsp; public DefaultContextView(Composite parent, IPartFactory 
-  factory) throws CoreException {</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Create a resource navigator</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ContainerContext viewContext1 
-  = new ContainerContext();&nbsp;&nbsp; </code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ISite view1 = factory.createView(</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  IPageLayout.ID_RES_NAV, parent, viewContext1, null);</code><br>
-  <code>&nbsp;&nbsp;&nbsp; </code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Create property view</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ContainerContext viewContext2 
-  = new ContainerContext();</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ISite view2 = factory.createView(IPageLayout.ID_PROP_SHEET, 
-  parent, viewContext2, null);</code><br>
-  <code>&nbsp;&nbsp;&nbsp; </code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; parent.setLayout(new FillLayout());&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  </code><br>
-  <code>&nbsp;&nbsp;&nbsp; }</code><br>
-  <code>}</code><br>
-  </div>
-<span style="font-weight: bold;"> <br>
-</span> 
-<div style="margin-left: 40px;"><img src="images/DefaultContextView.PNG" alt="Screenshot of DefaultContextView"><br>
-</div>
-<br>
-<h3>Redirecting dependencies from a parent to a child<br>
-</h3>
-This example demonstrates how to redirect 
-a site interface from the parent to a child. This composite view contains a resource 
-navigator and a property view. It redirects its selection handler to the resource 
-navigator and it redirects its action bars to the properties view. The result 
-is a view that provides a resource selection and contains the toolbar and menu 
-from the properties view, as shown below. <br>
-<span style="font-weight: bold;"><br>
-</span> 
-<div style="margin-left: 40px;"><code>public class RedirectContextView {</code><br>
-  <code>&nbsp;&nbsp;&nbsp; /**</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp; * Component constructor. Do not invoke directly.</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp; */</code><br>
-  <code>&nbsp;&nbsp;&nbsp; public RedirectContextView(Composite parent, IPartFactory 
-  factory, ISelectionHandler selection, IActionBars actionBars) throws CoreException 
-  {</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Create a resource navigator. 
-  Redirect the navigator's selection directly to our parent.</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ContainerContext viewContext1 
-  = new ContainerContext()</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .addInstance(ISelectionHandler.class, 
-  selection); </code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ISite view1 = factory.createView(</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  IPageLayout.ID_RES_NAV, </code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  parent, viewContext1, null);</code><br>
-  <code>&nbsp;&nbsp;&nbsp; </code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Create property view. Allow 
-  the property view to use our action bars directly.</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ContainerContext viewContext2 
-  = new ContainerContext()</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .addInstance(IActionBars.class, 
-  actionBars);</code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ISite view2 = factory.createView(IPageLayout.ID_PROP_SHEET, 
-  parent, viewContext2, null);</code><br>
-  <code>&nbsp;&nbsp;&nbsp; </code><br>
-  <code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; parent.setLayout(new FillLayout());&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  </code><br>
-  <code>&nbsp;&nbsp;&nbsp; }</code><br>
-  <code>}</code><br>
-  </div>
-<br>
-<br>
-<div style="margin-left: 40px;"><img src="images/RedirectContextView.PNG" alt="Screenshot of RedirectContextView"><br>
-</div>
-<h3>Providing dependencies directly<br>
-</h3>
-This example demonstrates how to supply a child with one of its dependencies directly. 
-In this example, we create a composite view containing a problems view and a properties 
-view. We supply the problem view with an ISelectionHandler in order to display 
-the number of selected problems in the content description. The end result is 
-shown below.<br>
-<br>
-<span style="font-weight: bold;"> </span> 
-<div style="margin-left: 40px;"><code>public class OverrideInstanceView {<br>
-  &nbsp;&nbsp;&nbsp; <br>
-  &nbsp;&nbsp;&nbsp; /**<br>
-  &nbsp;&nbsp;&nbsp;&nbsp; * Component constructor. Do not invoke directly.<br>
-  &nbsp;&nbsp;&nbsp;&nbsp; */<br>
-  &nbsp;&nbsp;&nbsp; public OverrideInstanceView(Composite parent, IPartFactory 
-  factory, final INameable name) throws CoreException {<br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ContainerContext viewContext1 = new 
-  ContainerContext();<br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Add an ISelectionHandler to the 
-  view's context. Whenever the view changes its selection,<br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // display the number of selected 
-  items in the content description<br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; viewContext1.addInstance(ISelectionHandler.class, 
-  new ISelectionHandler() {<br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /* (non-Javadoc)<br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * @see 
-  org.eclipse.ui.part.services.ISelectionHandler#setSelection(org.eclipse.jface.viewers.ISelection)<br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; */<br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; public void 
-  setSelection(ISelection newSelection) {<br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  if (newSelection instanceof IStructuredSelection) {<br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  IStructuredSelection sel = (IStructuredSelection)newSelection;<br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  int selectionSize = sel.size();<br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  <br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  name.setContentDescription(MessageFormat.format("{0} problems selected", <br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  new String[] {Integer.toString(selectionSize)}));<br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  }<br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; });<br>
-  <br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Create a problem view<br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ISite view1 = factory.createView(<br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-  IPageLayout.ID_PROBLEM_VIEW, parent, viewContext1, null);<br>
-  &nbsp;&nbsp;&nbsp; <br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Create property view<br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ContainerContext viewContext2 = new 
-  ContainerContext();<br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ISite view2 = factory.createView(IPageLayout.ID_PROP_SHEET, 
-  parent, viewContext2, null);<br>
-  &nbsp;&nbsp;&nbsp; <br>
-  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; parent.setLayout(new FillLayout());<br>
-  &nbsp;&nbsp;&nbsp; }<br>
-  }</code><br>
-  </div>
-<br>
-<span style="font-weight: bold;"> <br>
-</span> 
-<div style="margin-left: 40px;"><img src="images/OverrideInstanceView.PNG" alt="Screenshot of OverrideInstanceView"><br>
-  <br>
-</div>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs.htm b/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs.htm
deleted file mode 100644
index 66ed404..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Preference pages
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Preference pages</h2>
-<p>
-Once a plug-in has contributed extensions to the workbench user interface, it is common for
-the plug-in to allow the user to control some of the behavior of the plug-in through
-user preferences.
-</p>
-<p>
-The platform UI provides support for storing plug-in preferences and showing them to the user
-on pages in the workbench <b>Preferences</b> dialog. Plug-in preferences are key/value pairs, where the 
-key describes the name of the preference, and the value is one of several different types.  (See
-<a href="runtime_preferences.htm">Runtime preferences</a> for a detailed description of 
-the runtime preferences infrastructure.)</p>
-<p>How does a plug-in contribute a page for showing its preferences?  We will use the readme 
-tool example to see how it contributes a preference page to the
-workbench and then look at some of the underlying support for building preference pages.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_contribute.htm b/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_contribute.htm
deleted file mode 100644
index f43b0c1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_contribute.htm
+++ /dev/null

@@ -1,76 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Contributing a preference page
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Contributing a preference page</h3>
-<P > The <b><a href="../reference/extension-points/org_eclipse_ui_preferencePages.html"> 
-  org.eclipse.ui.preferencePages</a></b> extension point allows you to contribute 
-  pages to the general preferences (<b>Window-&gt;Preferences</b>) dialog. The 
-  preferences dialog presents a hierarchical list of user preference entries. 
-  Each entry displays a corresponding preference page when selected.</P>
-<P >
-The readme tool uses this extension point to add the Readme Example preferences page.</P>
-<pre>   &lt;extension
-      point = &quot;org.eclipse.ui.preferencePages&quot;&gt;
-       &lt;page id=&quot;org.eclipse.ui.examples.readmetool.Page1&quot;
-	    class=&quot;org.eclipse.ui.examples.readmetool.ReadmePreferencePage&quot;
-            name=&quot;%PreferencePage.name&quot;&gt;
-       &lt;/page&gt;
-   &lt;/extension&gt;</pre>
-<P >
-This markup defines a preference page named &quot;Readme Example&quot; which is implemented by the class
-<b>ReadmePreferencePage</b>. The class must implement the
-<b><a href="../reference/api/org/eclipse/ui/IWorkbenchPreferencePage.html"> IWorkbenchPreferencePage</a></b> interface.</P>
-<P > The workbench uses the core runtime's preference mechanisms to access all nodes in the preference tree 
-and their corresponding pages. This list can be initialized from information in the preferences service
-without running any plug-in code.</P>
-<P >
-<img src="images/preferences.png" alt="Workbench preferences page" border="0"></P>
-<P >
-The &quot;Readme Example&quot; preference is added to the top level of the
-preference tree on the left.&nbsp; Why? Because a preference page contribution will be added as a root of the tree unless a
-<b> category</b> attribute is specified. (The name <b> category</b> is somewhat misleading.
-Perhaps a better name is
-<b>path</b>.) The <b> category</b> attribute
-specifies the id (or a sequence of ids from the root) of the parent page. For example, the following markup would create a second readme tool preference page, &quot;Readme Example Child Page,&quot; as a child of the original page.</P>
-<pre>
-   &lt;extension
-      point = &quot;org.eclipse.ui.preferencePages&quot;&gt;
-      &lt;page
-         id=&quot;org.eclipse.ui.examples.readmetool.Page1&quot;
-         class=&quot;org.eclipse.ui.examples.readmetool.ReadmePreferencePage&quot;
-         name=&quot;%PreferencePage.name&quot;&gt;
-      &lt;/page&gt;
-      &lt;page
-         id=&quot;org.eclipse.ui.examples.readmetool.Page2&quot;
-         class=&quot;org.eclipse.ui.examples.readmetool.ReadmePreferencePage2&quot;
-         name=&quot;Readme Example Child Page&quot;
-         category=&quot;org.eclipse.ui.examples.readmetool.Page1&gt;
-      &lt;/page&gt;
-   &lt;/extension&gt;
-</pre>
-
-
-<P >
-Once the user selects the entry for a preference page in the tree on the left,
-the workbench will create and display a preference page using the <b> class</b> specified in the
-extension definition.&nbsp; This action is what activates the plug-in (if it
-wasn't already activated due to another user operation).</P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_fieldeditors.htm b/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_fieldeditors.htm
deleted file mode 100644
index e66764a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_fieldeditors.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Field editors
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H3>
-Field editors</H3>
-<P >
-The implementation of a preference page is primarily SWT code.&nbsp; SWT code is
-used to create the preference page controls, set the values of the controls, and
-retrieve the values of the controls. The
-<b><a href="../reference/api/org/eclipse/jface/preference/package-summary.html">org.eclipse.jface.preference</a></b> 
-package provides helper classes, called <b> field editors</b>, that create the widgets and implement the value setting 
-and retrieval code for the most common preference types. The platform provides field editors for displaying and updating 
-many value types, including booleans, colors, strings, integers, fonts, and file names.</P>
-<P >
- <b><a href="../reference/api/org/eclipse/jface/preference/FieldEditorPreferencePage.html"> FieldEditorPreferencePage</a></b> implements a
-page that uses these field editors to display and store the preference values on the page.&nbsp;
- Instead of creating SWT controls to fill its contents, a <b><a href="../reference/api/org/eclipse/jface/preference/FieldEditorPreferencePage.html"> FieldEditorPreferencePage</a></b> 
-subclass creates field editors to display the contents.&nbsp; All of the fields
- on the page must be implemented as field editors.&nbsp; The following is a
-snippet from the debug UI preferences page:</P>
-<pre>protected void createFieldEditors() {
-	addField(new BooleanFieldEditor(IDebugUIConstants.PREF_BUILD_BEFORE_LAUNCH, 
-		DebugPreferencesMessages.getString(&quot;DebugPreferencePage.auto_build_before_launch&quot;), 
-		SWT.NONE, getFieldEditorParent())); 
-	...	
-	String[][] perspectiveNamesAndIds = getPerspectiveNamesAndIds();
-	addField(new ComboFieldEditor(IDebugUIConstants.PREF_SHOW_DEBUG_PERSPECTIVE_DEFAULT,
-		DebugPreferencesMessages.getString(&quot;DebugPreferencePage.Default_perspective_for_Debug_2&quot;), //$NON-NLS-1$
-		perspectiveNamesAndIds,
-		getFieldEditorParent()));
-	...
-}</pre>
-<P >
-Each field editor is assigned the name of its corresponding preference key and the text label for the SWT
-control that it will create. The kind of control created depends on the type of field editor. For example, a boolean field editor creates a checkbox.</P>
-<P >
-Since the preference page is associated with a preference store (specified in the
-<b> doGetPreferenceStore</b> method), the code for storing the current values,
-for initializing the control values from the preference store, and for restoring the controls to
-their default values can all be implemented in the
-<b><a href="../reference/api/org/eclipse/jface/preference/FieldEditorPreferencePage.html">FieldEditorPreferencePage</a></b>.</P>
-<P >
-The <b><a href="../reference/api/org/eclipse/jface/preference/FieldEditorPreferencePage.html"> FieldEditorPreferencePage</a></b> 
-will use a grid layout with one column as the default layout for field editor
-widgets.&nbsp; For special layout requirements, you can override the <b>createContents</b> method.</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_implement.htm b/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_implement.htm
deleted file mode 100644
index bcdca88..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_implement.htm
+++ /dev/null

@@ -1,166 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Implementing a preference page
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Implementing a preference page</h3>
-
-<h4>
-Defining the page</h4>
-<p>
-The JFace plug-in provides a framework for implementing wizards, preference pages, 
-and dialogs.  The implementation for these dialogs follows a common pattern.
-The contents of a page or dialog is defined by implementing a <b>createContents</b> 
-method that creates the SWT controls representing the page content.  This method
-should also add listeners for any events of interest. The page is responsible for 
-creating and returning the composite that will parent all of the controls in the page.
-The following snippet shows the highlights:</p>
-<pre>
-protected Control createContents(Composite parent)
-{
-	...
-	//composite_textField &lt;&lt; parent
-	Composite composite_textField = createComposite(parent, 2);
-	Label label_textField = createLabel(composite_textField, MessageUtil.getString(&quot;Text_Field&quot;));	 
-	textField = createTextField(composite_textField);
-	pushButton_textField = createPushButton(composite_textField, MessageUtil.getString(&quot;Change&quot;)); 
-
-	//composite_tab &lt;&lt; parent
-	Composite composite_tab = createComposite(parent, 2);
-	Label label1 = createLabel(composite_tab, MessageUtil.getString(&quot;Radio_Button_Options&quot;)); 
-
-	//
-	tabForward(composite_tab);
-	//radio button composite &lt;&lt; tab composite
-	Composite composite_radioButton = createComposite(composite_tab, 1);
-	radioButton1 = createRadioButton(composite_radioButton, MessageUtil.getString(&quot;Radio_button_1&quot;)); 
-	radioButton2 = createRadioButton(composite_radioButton, MessageUtil.getString(&quot;Radio_button_2&quot;)); 
-	radioButton3 = createRadioButton(composite_radioButton, MessageUtil.getString(&quot;Radio_button_3&quot;)); 
-
-
-	//composite_tab2 &lt;&lt; parent
-	Composite composite_tab2 = createComposite(parent, 2);
-	Label label2 = createLabel(composite_tab2, MessageUtil.getString(&quot;Check_Box_Options&quot;)); //$NON-NLS-1$
-
-	//
-	tabForward(composite_tab2);
-	//composite_checkBox &lt;&lt; composite_tab2
-	Composite composite_checkBox = createComposite(composite_tab2, 1);
-	checkBox1 = createCheckBox(composite_checkBox, MessageUtil.getString(&quot;Check_box_1&quot;)); 
-	checkBox2 = createCheckBox(composite_checkBox, MessageUtil.getString(&quot;Check_box_2&quot;)); 
-	checkBox3 = createCheckBox(composite_checkBox, MessageUtil.getString(&quot;Check_box_3&quot;)); 
-
-	initializeValues();
-
-	return new Composite(parent, SWT.NULL);
-}</pre>
-<p>
-Most of the code in this method is concerned with creating and laying out the controls, so we won't dissect it here.&nbsp;
-Here is what the corresponding page looks like:</p>
-<p>
-<img src="images/readmepreferences.png" alt="Readme tool preferences page" border="0"></p>
-<p>
-The other primary responsibility of a preference page is to react to the <b> performOk</b> message. Typically, this 
-method updates and stores the user preferences and, if necessary, updates any other plug-in objects to reflect the 
-change in preferences.  The <b>performDefaults</b> method is used to restore preferences to their
-default state when the user presses the <b>Restore Defaults</b>
-button.&nbsp;&nbsp;</p>
-<p>
-You may override <b>performApply</b> if you have additional processing when the
-user selects <b>Apply</b>.&nbsp; The default implementation is to call <b>performOk</b>.&nbsp;&nbsp;</p>
-<p>
-Preference pages should override the <b> doGetPreferenceStore()</b> method to return a preference store for 
-storing their values. </p>
-
-
-<h4>
-Plug-in preference store</h4>
-<p>Preference stores are a convenience mechanism for accessing and storing preference values in a
-plug-in class.  They provide plug-in level access to preferences that are actually stored using 
-the runtime preferences service.  <a href="../reference/api/org/eclipse/ui/plugin/AbstractUIPlugin.html"><b>AbstractUIPlugin</b></a> 
-defines a plug-in wide preference store that is maintained during the lifetime of the plug-in.  Your plug-in
-can add entries to this preference store and update the values as the user changes the settings in your preferences page.   
-Since preference stores use the platform preferences service, they will take care of saving preference values at the 
-appropriate scope and location, and initializing the preference store using the appropriate mechanisms.</p>
-<p>
-The following code in the <b> ReadmePreferencePage</b> obtains the preference store for the
-<b>ReadmePlugin</b>.</p>
-<pre>
-   protected IPreferenceStore doGetPreferenceStore() {
-      return ReadmePlugin.getDefault().getPreferenceStore();
-   }
-</pre>
-<p>
-Because <b> ReadmePlugin</b> extends the <b><a href="../reference/api/org/eclipse/ui/plugin/AbstractUIPlugin.html"> AbstractUIPlugin</a></b> class, it automatically inherits a preference store. 
-This preference store is initialized using the platform preferences service. The only thing the <b>ReadmePlugin</b> has 
-to do is implement a method that initializes the preference controls to their default values. These values are used the 
-first time the preference page is shown or when the user presses the <b>Defaults</b> button in the preferences page.</p>
-<pre>
-protected void initializeDefaultPreferences(IPreferenceStore store) {
-	// These settings will show up when Preference dialog
-	// opens up for the first time.
-	store.setDefault(IReadmeConstants.PRE_CHECK1, true);
-	store.setDefault(IReadmeConstants.PRE_CHECK2, true);
-	store.setDefault(IReadmeConstants.PRE_CHECK3, false);
-	store.setDefault(IReadmeConstants.PRE_RADIO_CHOICE, 2);
-	store.setDefault(IReadmeConstants.PRE_TEXT, MessageUtil.getString(&quot;Default_text&quot;)); //$NON-NLS-1$
-}</pre>
-
-<blockquote><i>
-Note:&nbsp; If there are no preferences saved anywhere for a plug-in, the plug-in will get an empty preference
-store.</i></blockquote>
-<h4>
-Retrieving and saving preferences</h4>
-<p>
-Once you've associated your plug-in's preference store with your preference page, you can implement the logic for retrieving and saving the preferences.</p>
-<p>
-Preference pages are responsible for initializing the values of their controls using the preferences settings from the preference store. This
-process is similar to initializing dialog control values from dialog settings. The
-<b> ReadmePreferencePage</b> initializes all of its controls in a single method,
-<b>initializeValues</b>, which is called from its <b> createContents</b> method.</p>
-<pre>private void initializeValues() {
-	IPreferenceStore store = getPreferenceStore();
-	checkBox1.setSelection(store.getBoolean(IReadmeConstants.PRE_CHECK1));
-	checkBox2.setSelection(store.getBoolean(IReadmeConstants.PRE_CHECK2));
-	checkBox3.setSelection(store.getBoolean(IReadmeConstants.PRE_CHECK3));
-	...
-}</pre>
-<p>
-When the <b>OK</b> (or <b>Apply</b>) button is pressed, the current values of the controls on the preference page should be stored back into the
-preference store. The
-<b> ReadmePreferencePage</b> implements this logic in a separate method,
-<b>storeValues</b>.</p>
-<pre>
-private void storeValues() {
-	IPreferenceStore store = getPreferenceStore();
-	store.setValue(IReadmeConstants.PRE_CHECK1, checkBox1.getSelection());
-	store.setValue(IReadmeConstants.PRE_CHECK2, checkBox2.getSelection());
-	store.setValue(IReadmeConstants.PRE_CHECK3, checkBox3.getSelection());
-	...
-}</pre>
-<p>
-When the user presses the <b>Defaults</b> button, the platform will restore all preference store values to the default values specified in the plug-in class. However, your preference page is responsible for reflecting these default values
-in the controls on the preference page. The
-<b> ReadmePreferencePage</b> implements this in <b>initializeDefaults</b>.</p>
-<pre>
-   private void initializeDefaults() {
-      IPreferenceStore store = getPreferenceStore();
-      checkBox1.setSelection(store.getDefaultBoolean(IReadmeConstants.PRE_CHECK1));
-      checkBox2.setSelection(store.getDefaultBoolean(IReadmeConstants.PRE_CHECK2));
-      checkBox3.setSelection(store.getDefaultBoolean(IReadmeConstants.PRE_CHECK3));
-      ...
-   }</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prop_contribute.htm b/bundles/org.eclipse.platform.doc.isv/guide/preferences_prop_contribute.htm
deleted file mode 100644
index 037c87e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prop_contribute.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Contributing a property page
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Contributing a property page</h3>
-<P >
-You can contribute a property page for an object by using the
-<a href="../reference/extension-points/org_eclipse_ui_propertyPages.html"> <b> org.eclipse.ui.propertyPages</b></a> extension point.
-An object's property page is invoked using the <b>Properties </b>menu in any
-view that shows objects, such as the resource navigator view.&nbsp; This menu is available when a single
-object is
-selected.&nbsp;</P>
-<P >The readme tool contributes two property pages.</P>
-<pre>
-&lt;extension
-     point = &quot;org.eclipse.ui.propertyPages&quot;&gt;
-        &lt;page
-           id=&quot;org.eclipse.ui.examples.readmetool.FilePage&quot;
-           name=&quot;%PropertiesPage.filePage&quot;
-	   objectClass=&quot;org.eclipse.core.resources.IFile&quot;
-	   class=&quot;org.eclipse.ui.examples.readmetool.ReadmeFilePropertyPage&quot;
-           nameFilter=&quot;*.readme&quot;&gt;
-        &lt;/page&gt;
-         &lt;page
-            id=&quot;org.eclipse.ui.examples.readmetool.FilePage2&quot;
-            name=&quot;%PropertiesPage.filePage2&quot;
- 	   objectClass=&quot;org.eclipse.core.resources.IFile&quot;
- 	   class=&quot;org.eclipse.ui.examples.readmetool.ReadmeFilePropertyPage2&quot;
-            nameFilter=&quot;*.readme&quot;&gt;
-         &lt;/page&gt;
-  &lt;/extension&gt;
-</pre>
-<P >When you define a property page, you specify the <b>objectClass</b> for
-which this page is valid.&nbsp; Objects of this class will include your page
-when the properties are shown.&nbsp; You may optionally supply a <b>nameFilter</b>
-that further refines the class.&nbsp; In the readme tool example, both pages are contributed for objects of type <b><a href="../reference/api/org/eclipse/core/resources/IFile.html"> IFile</a></b> with a
-<b>.readme</b> file extension. </P>
-<P >Property pages are not limited to workbench resources.&nbsp; All objects
-showing up in the workbench (even domain-specific objects created by other
-plug-ins) may have property pages.&nbsp; Any plug-in may register property pages
-for any object type. </P>
-<P >
-Property pages look a lot like preference pages, except there is no hierarchy or categorization of property pages. In the dialog below, both readme property pages appear in the main list of pages.</P>
-<P >
-<img src="images/readmeproperties.png" alt="Properties dialog with readme entries" border="0" ></P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prop_implement.htm b/bundles/org.eclipse.platform.doc.isv/guide/preferences_prop_implement.htm
deleted file mode 100644
index 76c517d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prop_implement.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Implementing a property page
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Implementing a property page</h3>
-<P >
-When the workbench creates and launches a properties page, it sets the selected resource into the page. The page can use the
-<b> getElement()</b> method to obtain its element, an <b><a href="../reference/api/org/eclipse/core/runtime/IAdaptable.html">IAdaptable</a></b>. </P>
-<P >
-The pattern for creating property pages is similar to that of preference pages, so we will only focus on what is different. Property pages show information about their element. This information can be obtained
-by accessing the element in order to query or compute the relevant
-information.&nbsp; The information can also be stored and retrieved from the
-resource's properties.</P>
-<P >
-The <b> ReadmeFilePropertyPage</b> computes most of its information using its element. The following snippet shows how the number of sections is computed and displayed in a label.</P>
-<pre>
-   ...
-   IResource resource = (IResource) getElement();
-   ...
-   IAdaptable sections = getSections(resource);
-   if (sections instanceof AdaptableList) {
-      AdaptableList list = (AdaptableList)sections;
-      label = createLabel(panel, String.valueOf(list.size()));
-   ...
-</pre>
-<P >
-When a property is computed, there is no need for corresponding logic to save the value, since the user cannot update this value.</P>
-<P >
-Properties pages are commonly used for viewing and for setting the
-application-specific&nbsp; properties of a resource.
-(See <a HREF="resInt_properties.htm" CLASS="XRef">Resource properties</a>  for a
-discussion of session and persistent properties.)&nbsp;
-Since the property page knows its resource, the resources API can be used in the page to initialize control values or
-to set new property values based on user selections in the properties page.</P>
-<P >
-The following snippet shows a checkbox value being initialized from a property on a property page's element.</P>
-<pre>
-   private void initializeValues() {
-      ...
-      IResource resource = (IResource) getElement();
-      label.setText(resource.getPersistentProperty(&quot;MyProperty&quot;));
-      ...
-   }
-</pre>
-<P >
-The corresponding code for saving the checkbox value back into the property looks like this:</P>
-<pre>
-   private void storeValues() {
-      ...
-      IResource resource = (IResource) getElement();
-      resource.setPersistentProperty(&quot;MyProperty&quot;, label.getText());
-      ...
-   }
-</pre>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/product.htm b/bundles/org.eclipse.platform.doc.isv/guide/product.htm
deleted file mode 100644
index 0bac28c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/product.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Packaging and delivering Eclipse based products</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Packaging and delivering Eclipse based products</H1>
-<p>
-  The Eclipse platform is designed so you can add plug-ins that provide function
-  for the software development tools community.&nbsp; Commercial software
-  vendors can build, brand, and package products using the platform as a base
-  technology.&nbsp; These products can be sold and supported commercially.&nbsp;
-</p>
-<p>
-  The Eclipse SDK can be downloaded and used as a Java IDE and Eclipse plug-in
-  development tool, but it is not marketed as a commercial product.&nbsp; The
-  platform provides the raw ingredients for a product without a box, label, or
-  price tag.&nbsp; It defines a file and directory structure that lets you
-  easily customize the platform's about dialog and splash screen to brand your
-  product.</p>
-<p>
-  The license governing the Eclipse platform gives you a lot of freedom over how
-  to build and configure a product.&nbsp; However, Eclipse based products will
-  coexist more easily on a user's system if the products use similar standards
-  for packaging, configuring, and installing their products.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/product_config_install.htm b/bundles/org.eclipse.platform.doc.isv/guide/product_config_install.htm
deleted file mode 100644
index 097d0ab..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/product_config_install.htm
+++ /dev/null

@@ -1,132 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Product installation guidelines</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Product installation guidelines</h2>
-<p>The platform provides standard tools for updating and extending
-products.&nbsp; In order to participate in the platform mechanisms for updating
-and extending products, your packaged product should follow the following
-guidelines.&nbsp; This will allow your product to peacefully
-coexist with, or even enhance, other Eclipse based products.</p>
-<p>Consider again the sample directory structure for the acmeweb product:</p>
-<pre>acmeweb/
-	acmeweb.exe
-	eclipse/	
-		.eclipseproduct	
-		eclipse.exe	
-		startup.jar	
-		install.ini	
-		.config/	
-			platform.cfg
-		jre/
-		features/	
-			com.example.acme.acmefeature_1.0.0/
-				feature.xml
-			...
-		plugins/
-			com.example.acme.acmefeature_1.0.0/
-				plugin.xml
-				about.ini
-				about.html
-				about.mappings
-				about.properties
-				acme.png
-				plugin_customization.ini
-				splash.jpg
-				welcome.xml
-			com.example.acme.acmewebsupport_1.0.0/
-			...
-		links/
-			...</pre>
-
-<p>Where did these files come from?&nbsp; Let's look at the product content from
-the perspective of the development team.&nbsp; The installed files can be
-grouped into five main categories:</p>
-<ul>
-  <li>top-level product files (such as the acmeweb.exe)</li>
-  <li>product features and plug-ins</li>
-  <li>the Eclipse platform itself</li>
-  <li>the Java runtime environment (JRE)</li>
-  <li>files generated by the installation process itself</li>
-</ul>
-<p>A proper installation script will produce the appropriate directory structure
-by doing the following:</p>
-<ul>
-  <li>allow the user to specify the top level directory of the install (such as <b>c:\acmeweb.&nbsp;
-    </b>We will refer to it as <b>acmeweb</b> for the remaining steps.)</li>
-  <li>ensure that a product is not already installed in the location</li>
-  <li>copy the files as follows:
-    <ul>
-      <li>Top-level product files are copied to <b>acmeweb</b></li>
-      <li>Eclipse files are copied to <b>acmeweb/eclipse </b>using the expected
-        feature and plugin directory structures</li>
-      <li>JRE files are copied to <b>acmeweb/eclipse/jre</b>.&nbsp; If a JRE is
-        already located elsewhere, then the application shortcut should be setup
-        to invoke eclipse with the <b>-vm</b> command line argument so that the
-        location of the JRE is known by the platform</li>
-      <li>Product features and plug-ins are copied to <b>acmeweb/eclipse/features</b>
-        and <b>acmeweb/eclipse/plugins</b></li>
-    </ul>
-  </li>
-  <li>create a marker file, <b>.eclipseproduct</b>, in <b>acmeweb/eclipse</b>.&nbsp;
-    The marker file is a <b>java.io.Properties</b> format file that indicates
-    the name, id, and version of the product.</li>
-  <li>store any necessary install info (user, license, date) that is to be shown
-    in the about dialog in <b>acmeweb/eclipse/plugins/com.example.acmefeature_1.0.0/about.mappings</b></li>
-  <li>if the primary feature mechanism (pre R3.0) is used to define the product, replace the 
-  <b>acmeweb/eclipse/install.ini</b> with one that sets the property <b>feature.default.id
-    </b>to the product's primary feature</li>
-  <li>invoke the product executable using the <b>-initialize</b> option.&nbsp;
-    This causes the platform to quietly perform all time-consuming first-time
-    processing and cache the results, so that when the user starts the product
-    it comes up promptly in an open-for-business state.</li>
-</ul>
-<h3>Multi-user issues</h3>
-<p>When a product is installed with the intention of sharing the installation among multiple users,
-care must be taken to separate individual user's data (such as the <b>workspace</b>
-directory) from the shared product install directory.</p>
-<h3>Uninstall issues</h3>
-<p>When a product is uninstalled, the following concepts are important.</p>
-<ul>
-  <li><b>all</b> files in the <b>eclipse/features</b> and <b>eclipse/plugins</b>
-    directories should be removed, even if they weren't originally installed by
-    the installation program.&nbsp; This ensures that files added by the
-    platform update manager are removed when the product is
-    removed.</li>
-  <li>except for the point above, <b>only</b> those files installed by the
-    installation program in other directories should be removed.&nbsp; It is
-    important to preserve any important data, such as the <b> workspace</b>
-    directory, so
-    that reinstalling the product after an uninstall will produce expected
-    results.</li>
-</ul>
-<h3>Reinstalling the product</h3>
-<p>When the product is already installed, the installer should allow a service
-update or upgrade if one is available.&nbsp; The existence of the product can be
-confirmed by looking for <b>acmeweb/eclipse/.eclipseproduct</b>.&nbsp; The
-information in this marker file can be used to confirm with the user that the
-correct product is being updated.&nbsp; The availability of updates can be
-confirmed with pattern matches against feature names.&nbsp; For example, the
-presence of <b>acmeweb/eclipse/plugins/com.example.acmefeature_1.0.1 </b>would
-indicate that the 1.0.1 version update had already been applied to the product.</p>
-<p>Once the validity of the reinstall is established, the install program should
-copy or replace files as needed.&nbsp; If the version of the underlying Eclipse
-platform has not changed, there is a good chance that complete directories can
-be ignored.&nbsp; The version numbers appended to the platform features and
-plugins can be used to determine whether any changes underneath a plug-in or
-feature's directory are necessary.&nbsp; </p>
-<p>Additional information on installing products can be found in <a href="../reference/misc/eclipse-install.html">How
-to write an Eclipse installer</a>.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/product_configfeature.htm b/bundles/org.eclipse.platform.doc.isv/guide/product_configfeature.htm
deleted file mode 100644
index 1c9b584..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/product_configfeature.htm
+++ /dev/null

@@ -1,143 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Customizing a primary feature</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Customizing a primary feature</h3>
-<p>Product customization works differently when using the primary feature mechanism.
-The branding information for the feature is located in a plug-in identified by
-  the primary feature (or the plug-in of the same
-name as the primary feature if none is specified). The files that designate and
-  define branding information for our hypothetical acmeweb application are highlighted
-  in the
-sample directory structure below:</p>
-<pre>acmeweb/
-	<b>acmeweb.exe	</b><i>(product executable - invokes eclipse.exe and specifies the primary feature)</i>
-	eclipse/
-		.eclipseproduct
-		eclipse.exe
-		startup.jar
-		install.ini
-		.config/
-		platform.cfg
-		jre/
-		features/
-			<b>com.example.acme.acmefeature_1.0.0/</b>&nbsp;&nbsp;&nbsp; <i>(primary feature)</i>
-				feature.xml
-		plugins/
-			<b>com.example.acme.acmefeature_1.0.0/</b>&nbsp;&nbsp;&nbsp; <i>(plug-in for primary feature.  Contains branding info.)</i>
-				plugin.xml
-				<b>about.ini
-				about.html
-				about.mappings
-				about.properties
-				acme.png
-				plugin_customization.ini
-				splash.jpg
-				welcome.xml</b>
-			com.example.acme.acmewebsupport_1.0.0/
-			...
-		links/
-			...</pre>
-<p>The plug-in associated with a <a href="product_def_primary.htm">primary
-  feature</a> is where the branding information for a product is specified.&nbsp;
-  There are many customizable aspects of a product.&nbsp; Product-level
-  customizations are defined using the <b>about.ini</b> file and other files
-  described therein.&nbsp; Products can also control the default preference values
-  of other plug-ins.&nbsp; This is done using the <b>plugin_customization.ini</b>
-  file.</p>
-<p>Referring once again to our sample product's primary feature plug-in, let's
-look closer at how the product is customized.</p>
-<pre><b>com.example.acme.acmefeature_1.0.0/</b>
-		plugin.xml
-		<b>about.ini
-		about.html
-		about.mappings
-		about.properties
-		acme.png
-		plugin_customization.ini
-		plugin_customization.properties
-		splash.bmp
-		welcome.xml</b></pre>
-<p>We'll review the same customizations that we reviewed for the products extension point, focusing
-on how the specification differs using the primary feature mechanism.</p>
-<h3>About dialogs</h3>
-<p>As discussed with the product-level customization, all features and plug-ins should 
-contribute an <b>about.html</b> file that provides information about that particular plug-in.</p>
-<p>The primary feature also supplies the information and graphics for the
-overall product.&nbsp; Additional files are used to specify this information.</p>
-<ul>
-  <li><b>about.ini</b> specifies the about text and images for features,
-    windows, and the about dialog itself.&nbsp; It also specifies the welcome
-    page.&nbsp; See <a href="../reference/misc/about_customization.html">Customization
-    using about.ini </a>for a complete description of the format of this file.&nbsp;</li>
-  <li><b>about.properties</b> should be used to hold translated strings from the
-    <b>about.ini </b>file (using &quot;%var&quot; as the value in about.ini paired with an
-    entry for the key &quot;var&quot; in about.properties.&nbsp; This file is a <b>java.io.Properties</b>
-    format file.</li>
-  <li><b>about.mappings</b> can be used to fill in values for fill-in fields in
-    the about text.&nbsp; This is useful when the about text contains
-    information specific to a particular install, such as license key, install
-    date, or licensed user. For example, the about text could be defined as
-    &quot;AcmeWeb is licensed to {0}&quot;.&nbsp; The about.mappings file could
-    be generated at install time based on input from the user.&nbsp; The final
-    form should contain a mapping for the field, such as &quot;0=Joe Q. Webuser&quot;.&nbsp;
-    The about.mappings file is a <b>java.io.Properties</b> format file.</li>
-</ul>
-<h3>Window images</h3>
-<p>A 16x16 pixel color image can be used to brand windows created by the
-product.&nbsp; It will appear in the upper left hand corner of product
-windows.&nbsp; It is specified in the <b>windowImage</b> attribute in the <b>about.ini</b>
-file.&nbsp; The path should be specified as a plug-in relative path.&nbsp; A
-proper entry for the directory structure shown above would be as follows:</p>
-<pre>windowImage=acme.png</pre>
-<h3>Welcome page</h3>
-<p>Plug-ins using the Eclipse 2.1 Welcome mechanisms should specify the welcome
-page file in the welcomePage attribute in the about.ini file. The path should be specified as a plug-in
-relative path.&nbsp; A proper entry for the directory structure shown above
-would be as follows:</p>
-<pre>welcomePage=welcome.xml</pre>
-<p>You can also specify an national language lookup for the file.&nbsp; (See <a href="product_def_nl.htm">Locale
-specific files</a> for more detail.)</p>
-<pre>welcomePage=$nl$/welcome.xml</pre>
-<h3>Splash screens</h3>
-<p>The product splash screen is supplied in a <b>splash.bmp</b> file located in
-the primary feature plug-in directory.&nbsp; The image should be supplied in
-24-bit color BMP format (RGB format) and should be approximately 500x330 pixels in
-size.&nbsp; If splash screens need to be customized for different locales, they
-can be placed in a fragment of the primary feature's plug-in.</p>
-<a name="preferences"></a>
-<h3>Preferences defaults</h3>
-
-<p>The <b>plugin_customization.ini</b>
- file is used to set the default preference values for preferences defined by
-other plug-ins.&nbsp; This file is a <b>java.io.Properties</b> format file.
-Typically this file is used to set the values for preferences that are published
-as part of a plug-in's public API.&nbsp; That is, you are taking a risk if you
-refer to preferences that are used by plug-ins but not defined formally in the
-API.&nbsp;&nbsp;</p>
-<p>One common customization is to set the default perspective for the
-workbench.&nbsp; This preference is defined in the <b>org.eclipse.ui </b>plug-in.&nbsp;&nbsp;
-The
-following example assumes that the product should be launched with the resource
-perspective as the default perspective.</p>
-<pre>org.eclipse.ui/defaultPerspectiveId=org.eclipse.ui.resourcePerspective</pre>
-<p>If you discover you need to change the default value for one of another plug-in's
-preferences, consult the API documentation for that plug-in to see if the
-preference is considered public.</p>
-<p>The <b>plugin_customization.properties</b> file contains translated strings
-for the <b>plugin_customization.ini</b>
- file.<br>
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/product_configproduct.htm b/bundles/org.eclipse.platform.doc.isv/guide/product_configproduct.htm
deleted file mode 100644
index 8a7dfb9..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/product_configproduct.htm
+++ /dev/null

@@ -1,101 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Customizing a product</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Customizing a product</h3>
-<p>There are many customizable aspects of a product, such as its splash screen,
-  about dialog text,  window icons, etc. Most of these customizations are defined
-  in the contribution to the <a href="../reference/extension-points/org_eclipse_core_runtime_products.html"><b>org.eclipse.core.runtime.products</b></a>
-extension point.</p>
-<p>
-Let's look at how some of the more common customizable elements are defined.</p>
-<h3>About dialogs</h3>
-<p>The platform &quot;about&quot; dialog is shown whenever the user selects <b>Help &gt; About
-</b>in the workbench menu.&nbsp;&nbsp;</p>
-<p><img src="images/about.png" alt="About dialog" border="0" ></p>
-<p>The upper part of the about dialog shows product level information while the
-  lower part details the features (if any) and plug-ins installed.&nbsp; The
-  feature details (branding if you will) are supplied using<b> about.ini</b>, <b>about.properties</b> and <b>about.html</b>
-files in the plug-in associated with the feature.&nbsp; This
-information is displayed when the user requests feature details and selects a
-particular feature.</p>
-<p>The product branding (top half of the dialog) is specify by extension properties
-that describe the text and images that are shown in this dialog.
-For example, the following extract from the Eclipse Platform product declaration.</p>
-<pre>	&lt;property
-		name="aboutText"
-		value="%aboutText"/&gt;
-	&lt;property
-		name="aboutImage"
-		value="icons/eclipse_lg.png"/&gt;
-	&lt;/product&gt;</pre>
-<ul>
-  <li><b>aboutText</b> specifies the text to show in the about dialog</li>
-  <li><b>aboutImage</b> specifies an image that should be used in the about dialog.  Large
-  images will be shown by themselves, and smaller images will be shown along with the about
-  text.</li>
-</ul>
-<p>See <b><a href="../reference/api/org/eclipse/ui/branding/IProductConstants.html">IProductConstants</a></b>
-for more information about these properties.
-</p>
-<h3>Window images</h3>
-<p>A 16x16 pixel color image can be used to brand windows created by the
-product.&nbsp; It will appear in the upper left hand corner of product
-windows.&nbsp; It is specified in the <b>windowImage</b> attribute in the 
-products extension definition.  Alternatively, the <b>windowImages</b> attribute
-can be used to describe an array of images of different sizes that should be used in the
-upper left hand corner.</p>
-<pre>	&lt;property
-		name="windowImages"
-		value="icons/eclipse.png,icons/eclipse32.png"/&gt;</pre>
-<p>The <b>windowImages</b> property supercedes the <b>windowImage</b> property if
-both are specified.</p>
-<h3>Welcome page</h3>
-<p>Products using the Eclipse 2.1 welcome page mechanism can specify the name and location
-of their welcome page file in the <b>welcomePage</b> property.</p>
-<pre>	&lt;property
-		name="welcomePage"
-		value="$nl$/welcome.xml"/&gt;</pre>
-<p>Use of this property is 
-discouraged in Eclipse 3.0 in favor of the <b><a href="../reference/extension-points/org_eclipse_ui_intro.html">org.eclipse.ui.intro</a></b>
-extension point.  See <a href="workbench_advext_intro.htm">Intro support</a> for more
-detail about the new welcome/intro mechanisms.</p>
-<h3><a name="preferences"></a>Preferences defaults</h3>
-
-<p>The <b>preferenceCustomization</b> property can be used to specify a file containing
-default preference values for the product.</p>
-<pre>	&lt;property
-		name="preferenceCustomization"
-		value="plugin_customization.ini"/&gt;</pre>
-<p>This file is a <b>java.io.Properties</b> format file.
-  Typically this file is used to set the values for preferences that are published
-  as part of a plug-in's public API.&nbsp; That is, you are taking a risk if you
-  refer to preferences that are used by plug-ins but not defined formally in the
-  API.&nbsp;&nbsp;</p>
-<h3>Splash screens</h3>
-<p>The product splash screen is specified in the <tt>config.ini</tt> which is
-  located underneath the product's <tt>configuration</tt> directory. The <b>osgi.splashPath</b> property
-  in this file describes places to search for a file called <b>splash.bmp</b>.
-  The <strong>osgi.splashLocation </strong>property identifes a complete and
-  exact path to the splash screen file to use. Specifying a splash path allows
-  for locale specific splash screens to be used as the given search path can
-  indicate several plug-ins or fragments to search as well as <code>$nl$</code> style paths.
-  See the
-  platform
-  SDK's <tt>config.ini</tt> file
-  for a complete description of properties that can be configured in this file.
-  The image should be supplied in 24-bit color BMP format (RGB format) and should
-  be approximately 500x330 pixels in size.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/product_def.htm b/bundles/org.eclipse.platform.doc.isv/guide/product_def.htm
deleted file mode 100644
index a9f4277..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/product_def.htm
+++ /dev/null

@@ -1,81 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Products and features</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Products and features</h2>
-<p>An Eclipse based <b>product</b> is a stand-alone program built with the
-Eclipse platform.  A product may optionally be packaged and delivered as one or more
-<b>features</b>, which are simply groupings of plug-ins that are managed as a single entity by
-the Eclipse update mechanisms.</p>
-<p>Products include all the code and plug-ins needed to run them.&nbsp; This
-includes a Java runtime environment (JRE) and the Eclipse platform code.&nbsp;
-The plug-in code, JRE, and Eclipse platform are typically installed with a
-product-specific installation program.&nbsp; Product providers are free to use
-any installation tool or program that is appropriate for their needs.&nbsp; </p>
-<p>Once installed, the user launches the product and is presented with an
-Eclipse workbench configured specifically for the purpose supported by the
-product, such as web development, C++ program development, or any other
-purpose.&nbsp; The platform makes it easy to configure labels, about dialogs,
-graphics, and splash screens, so that the user has no concept of a platform
-workbench, but instead views the workbench as the main window of the product
-itself.</p>
-<p>The top level directory structure of such a product looks something like this
-for a hypothetical product called &quot;AcmeWeb&quot; that has been installed on
-a Windows platform:</p>
-<pre>acmeweb/
-	acmeweb.exe		<i>(product executable)</i>
-	eclipse/		<i>(directory for installed Eclipse files)</i>
-		.eclipseproduct	<i>(marker file)</i>
-		eclipse.exe	
-		startup.jar		
-		configuration/	
-			config.ini
-		jre/
-		features/	<i>(installed features if any)</i>
-			com.example.acme.acmefeature_1.0.0/
-				feature.xml
-			...
-		plugins/
-			com.example.acme.acmefeature_1.0.0/
-				plugin.xml
-				about.ini
-				about.html
-				about.mappings
-				about.properties
-				acme.png
-				splash.jpg
-			com.example.acme.acmewebsupport_1.0.0/
-			...
-		links/
-			...</pre>
-<p>There are actually two ways of defining a product in Eclipse.  The preferred
-  mechanism is to
-use the <a href="product_def_extpt.htm">products extension point</a> (new to
-Eclipse 3.0). This extension point allows you to define your product and customize
-branding such as splash screens, window icons, and
-the like.  The older mechanism (used in Eclipse 2.1) uses <a href="product_def_feature.htm">features</a>,
-and in
-particular assumes the existence of a <a href="product_def_primary.htm">primary
-feature</a>.
-Under the covers, Eclipse 3.0 uses the products extension point mechanism, but
-provides compatibility functions that integrate the legacy definitions into the
-new model if
-necessary.</p>
-<p>We'll look at both mechanisms and how they are used to customize a product.  Even when the
-products extension point mechanism is used, features can still be used as a way to group functionality
-that is delivered by the update manager.  In the next few topics, we'll assume that
-feature groupings are present in our plug-in, in addition to product definitions.</p>
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/product_def_extpt.htm b/bundles/org.eclipse.platform.doc.isv/guide/product_def_extpt.htm
deleted file mode 100644
index 0ae8e20..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/product_def_extpt.htm
+++ /dev/null

@@ -1,78 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Products extension point</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Products extension point</h3>
-<p>The preferred mechanism for defining a product based on the Eclipse platform
-  is to contribute to the
-<a href="../reference/extension-points/org_eclipse_core_runtime_products.html"><b>org.eclipse.core.runtime.products</b></a>
-extension point.  To do this, a plug-in simply declares the name and id of its
-product,
-as
-well as the id of the application extension that should be run when the product
-is
-invoked. This is the technique used by the Eclipse
-platform itself in defining the Eclipse product.  Here is the extension definition
-found in <b>org.eclipse.platform</b>:</p>
-<pre>&lt;extension id="ide" point="org.eclipse.core.runtime.products"&gt; 
-	&lt;<b>product name="%productName" application="org.eclipse.ui.ide.workbench" description="%productBlurb"</b>&gt; 
-		&lt;property name="windowImages" value="eclipse.png,eclipse32.png"/&gt; 
-		&lt;property name="aboutImage" value="eclipse_lg.png"/&gt; 
-		&lt;property name="aboutText" value="%productBlurb"/&gt; 
-		&lt;property name="appName" value="Eclipse"/&gt; 
-		&lt;property name="preferenceCustomization" value="plugin_customization.ini"/&gt; 
-	&lt;/product&gt; 
-&lt;/extension&gt; </pre>
-A product extension is defined whose <b>application</b> id is "org.eclipse.ui.ide.workbench".
-This is the application id defined by the plug-in <b>org.eclipse.ui.ide</b> in
-its
-contribution to the <a href="../reference/extension-points/org_eclipse_core_runtime_applications.html"><b>org.eclipse.core.runtime.applications</b></a>
-extension point.
-
-<pre>
-&lt;extension
-	<b>id="workbench"</b>
-	point="org.eclipse.core.runtime.applications"&gt;
-	&lt;application&gt;
-		&lt;run
-			class="org.eclipse.ui.internal.ide.IDEApplication"&gt;
-		&lt;/run&gt;
-	&lt;/application&gt;
-&lt;/extension&gt; 
-</pre>
-<p>
-This extension is defined with the same id that is referenced in the <b>application</b> property
-of the product extension. (The fully qualified name, with plug-in prefix, is
-used when referring to the
-application id from the other plug-in.)  Using this mechanism, a separate plug-in
-can define all of the product-specific branding, and then refer to an existing
-plug-in's application as the application that
-is actually run when the product is started.
-</p>
-<p>
-In addition to the application, the <a href="../reference/extension-points/org_eclipse_core_runtime_products.html"><b>org.eclipse.core.runtime.products</b></a>
-extension describes product customization properties that are used to configure the product's branding information.
-This information is described as named properties.  Let's look again at that portion of the markup for the 
-platform plug-in.</p>
-<pre>	&lt;property name="windowImages" value="eclipse.png,eclipse32.png"/&gt; 
-	&lt;property name="aboutImage" value="eclipse_lg.png"/&gt; 
-	&lt;property name="aboutText" value="%productBlurb"/&gt; 
-	&lt;property name="appName" value="Eclipse"/&gt; 
-	&lt;property name="preferenceCustomization" value="plugin_customization.ini"/&gt; </pre>
-The possible property names that are honored by the platform for product customization are defined in
-<b><a href="../reference/api/org/eclipse/ui/branding/IProductConstants.html">IProductConstants</a></b>.
-See the javadoc for a complete description of these properties and their values.  We'll look at these
-further in <a href="product_configproduct.htm">Customizing a product</a>.
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/product_def_feature.htm b/bundles/org.eclipse.platform.doc.isv/guide/product_def_feature.htm
deleted file mode 100644
index 782db21..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/product_def_feature.htm
+++ /dev/null

@@ -1,83 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Features</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Features</h3>
-<p>A <b>feature</b> is a way of grouping and describing different functionality
-that makes up a product. Grouping plug-ins into features allows the product to be
-installed and updated using the Eclipse update server and related support.  
-The platform itself is partitioned into three major features:</p>
-<ul>
-  <li>Platform</li>
-  <li>JDT (Java Development Tooling)</li>
-  <li>PDE (Plug-in Developer Environment)</li>
-</ul>
-<p>There are other minor features, such as examples and OS-dependent portions of
-the platform.&nbsp; </p>
-<blockquote>
-<p><i>Note:&nbsp; The platform installation and update framework
-allows you to build your own custom implementations of the concepts discussed
-here.&nbsp; That is, you can define your own types of <b>features</b>, (their
-packaging formats, install procedures, etc.), as well as your own types of
-server sites for updating your features.&nbsp; The remainder of this discussion
-is focused on the platform default implementations for features and update
-sites.</i> </p>
-</blockquote>
-<p>Features do not contain any code.&nbsp; They merely describe a set of
-plug-ins that provide the function for the feature and information about how to
-update it. Features are packaged in a <a href="../reference/misc/feature_archive.html">feature
-archive</a> file and described using a <a href="../reference/misc/feature_manifest.html">feature
-manifest file</a>, feature.xml. The following is the first part of the manifest for
-the platform feature:</p>
-<pre>
-&lt;?xml version="1.0" encoding="UTF-8"?&gt;
-&lt;feature
-      id="org.eclipse.platform"
-      label="%featureName"
-      version="3.0.0"
-      provider-name="%providerName"
-      plugin=""
-      image="eclipse_update_120.jpg"
-      primary="true"
-      application="org.eclipse.ui.ide.workbench"&gt;
-
-   &lt;description&gt;
-      %description
-   &lt;/description&gt;
-
-   &lt;license url="%licenseURL"&gt;
-      %license
-   &lt;/license&gt;
-
-   &lt;url&gt;
-      &lt;update label="%updateSiteName" url="http://update.eclipse.org/updates/3.0"/&gt;
-      &lt;discovery label="%updateSiteName" url="http://update.eclipse.org/updates/3.0"/&gt;
-   &lt;/url&gt;
-
-   &lt;plugin
-         id="org.apache.ant"
-         download-size="0"
-         install-size="0"
-         version="1.6.1"/&gt;
-
-   &lt;plugin
-         id="org.apache.lucene"
-         download-size="0"
-         install-size="0"
-         version="1.3.0"/&gt;
-	...
-&lt;/feature&gt;
-</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/product_def_nl.htm b/bundles/org.eclipse.platform.doc.isv/guide/product_def_nl.htm
deleted file mode 100644
index fb7b391..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/product_def_nl.htm
+++ /dev/null

@@ -1,128 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Locale specific files</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Locale specific files</h2>
-<p>Fragments are a convenient way to package national language
-translations.&nbsp; Let's look more closely at the directory structure used for
-installing locale-specific translation files.&nbsp; This directory structure is
-used regardless of whether the translated files are packaged in a fragment or
-delivered in the original plug-in.</p>
-<p>There are three mechanisms for locating locale specific files in a
-plug-in.&nbsp;&nbsp;</p>
-<ul>
-  <li><b>Platform core mechanism</b> (the platform's runtime locale-specific
-    sub-directory search)</li>
-  <li><b>Java resource bundles</b> (java.util.ResourceBundle)</li>
-  <li><b>The plugin.properties mechanism</b> (Translating values from the plugin.xml files)</li>
-</ul>
-<p>It is important to understand which mechanism is used to access any given
-file that must be translated so that you'll know what to name the file and where
-to put it in the file system relative to the plug-in.</p>
-<h4><a name="platform">Platform core mechanism</a></h4>
-<p>The platform core defines a directory structure that uses locale-specific
-subdirectories for files that differ by locale.&nbsp; Translated files are
-placed in a directory called <b>nl</b> under the plug-in.&nbsp; For example, the
-following install tree shows a trivial (no code) plug-in with locale-specific
-translations of its <b>about.properties</b> file.&nbsp; The various translations
-are shown as coming from a plug-in fragment rather than the plug-in
-itself.&nbsp; This is typical for shipping translations separately from the
-base, but you could also place the <b>nl</b> sub-directory under the plug-in
-itself.</p>
-<pre>acmeweb/
-  eclipse/
-    plugins/
-      com.example.acme.acmewebsupport_1.0.0/
-        plugin.xml
-        about.properties    <i>(default locale)</i>
-      com.example.acme.fragmentofacmewebsupport_1.0.0/
-        fragment.xml   <i>(a fragment of com.example.acme.acmewebsupport 1.0.0)</i>
-        nl/
-          fr/
-            about.properties  <i>(French locale)</i>
-            CA/
-              about.properties  <i>(French Canadian locale)</i>
-            FR/
-              EURO/
-                about.properties <i>(French France Euros)</i>
-          en/
-            about.properties  <i>(English locale)</i>
-            CA/
-              about.properties  <i>(English Canadian locale)</i>
-            US/
-              about.properties <i>(English US locale)</i>
-         de/
-            about.properties <i>(German locale)</i> </pre>
-<p>The files to be translated are not contained in JAR files.&nbsp; Each file
-should have exactly the same file name, but be located in subdirectories
-underneath the <b>nl</b> sub-directory in the fragment's (or plug-in's) root.</p>
-<p>Only the most specific file is accessed at runtime.&nbsp; The file paths are
-searched as part of the <a href="../reference/api/org/eclipse/core/runtime/Platform.html"><b>Platform.find</b></a>, <a href="../reference/api/org/eclipse/core/runtime/IPluginDescriptor.html"><b>IPluginDescriptor.find</b></a>
-and <b><a href="../reference/api/org/eclipse/core/runtime/Plugin.html">Plugin.find</a></b>
-mechanism.&nbsp; For example, suppose the default locale is <b>en_CA</b>,
-and a plug-in searches for the <b>about.properties</b> as follows:</p>
-<pre>somePlugin.find(&quot;$nl$/about.properties&quot;);</pre>
-<p>The method will return a URL corresponding to the first place <b>about.properties</b> is found according to the following
-order:</p>
-<pre>com.example.acme.acmewebsupport_1.0.0/nl/en/CA/about.properties
-com.example.acme.fragmentofacmewebsupport_1.0.0/nl/en/CA/about.properties
- ...  		&lt;any other fragments&gt;
-com.example.acme.acmewebsupport_1.0.0/nl/en/about.properties
-com.example.acme.fragmentofacmewebsupport_1.0.0/nl/en/about.properties
- ...
-com.example.acme.acmewebsupport_1.0.0/about.properties
-com.example.acme.fragmentofacmewebsupport_1.0.0/about.properties</pre>
-<p>This mechanism is used by plug-ins to search for well known file names inside
-other plug-ins.&nbsp; This includes the following well known file names:</p>
-<ul>
-  <li><b>preferences.properties</b>&nbsp; (externalized strings for plug-in
-    -specific preference default overrides)</li>
-  <li><b>about.properties</b>&nbsp; (externalized strings for feature
-    &quot;about&quot; information)</li>
-  <li><b>plugin_customization.properties</b>&nbsp; (externalized strings for
-    product-specific preference default overrides)</li>
-  <li><b>splash.bmp</b>&nbsp; (product-specific splash screens)</li>
-</ul>
-<blockquote>
-  <p><i>(Note:&nbsp; The <b>plugin.properties</b> and <b>fragment.properties </b>are
-  conspicuously absent from this list. They are treated in a sightly different way described below.)</i></p>
-</blockquote>
-<h4>Java resource bundles</h4>
-<p>The standard Java handling of property resource bundles is used for other
-files.&nbsp; Translated files are contained in a JAR file, with each properties
-file having a locale-specific name, such as &quot;<b>message_en_CA.properties</b>&quot;.&nbsp;
-The files are in package-specific subdirectories and may appear in the plug-in
-itself or one of its fragments.&nbsp; Each translated properties file may be
-partial since lookup of keys accesses a well-defined chain of properties files.</p>
-
-<h4>The plugin.properties mechanism</h4>
-The mechanism used to translate plugin.properties files uses the Java resource bundles naming convention. However the files must be located in the root 
-of the plug-in or in the root of a fragment of this plug-in. 
-The same rules apply to the translation of MANIFEST.MF.
-
-<h3>Defining NL fragments</h3>
-<p>The shape of NL fragments has evolved slightly since 2.1. 
-Previously all translation files (including the plugin.properties) were provided in a jar. 
-This was inconsistent since the plugin.properties file was provided at the root of the plug-in.
-<br>
-To adapt your NL fragment to the new model, remove the plugin.properties translation files from the jar and put them at the root of the fragment as siblings of fragment.xml.
-For example, the new shape of the NL fragment for org.eclipse.ui.workbench is the following:</p>
-<pre>  org.eclipse.ui.workbench.nl/
-     fragment.xml
-     plugin_fr.properties
-     plugin_pt_BR.properties
-     ...
-     nl1.jar</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/product_def_plugins.htm b/bundles/org.eclipse.platform.doc.isv/guide/product_def_plugins.htm
deleted file mode 100644
index c4069db..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/product_def_plugins.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Plug-ins</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Plug-ins and fragments</h2>
-<p>Features are described in terms of the plug-ins that comprise them.&nbsp;
-This means that plug-ins are the fundamental unit for packaging
-function.&nbsp;&nbsp;</p>
-<p>While features are organized for the purposes of distributing and updating
-products, plug-ins are organized to facilitate the development of the product
-function among the product team.&nbsp; The development team determines when to
-carve up program function into a separate plug-in.&nbsp;&nbsp;</p>
-<p>Plug-ins are packaged in a <a href="../reference/misc/plugin_archive.html">plug-in
-archive</a> file and described using a <a href="../reference/misc/plugin_manifest.html">plug-in
-manifest file</a>, <b>plugin.xml</b>.&nbsp;&nbsp;</p>
-<p>Plug-in <b>fragments</b> are separately packaged files whose contents are
-treated as if they were in the original plug-in archive file.&nbsp; They are
-useful for adding plug-in functionality, such as additional national language
-translations, to an existing plug-in after it has been installed.&nbsp;
-Fragments are ideal for shipping function that may trail the initial product
-release, since they can be used to add function without repackaging or
-reinstalling the original plug-in.&nbsp; When a fragment is detected by the
-platform, its contents are merged with the function in the original
-plug-in.&nbsp; In other words, if you query the platform plug-in registry, you
-would see the extensions and other function provided in the fragment as if it
-was in the original plug-in.</p>
-<p>Fragments are described using a fragment manifest file, <b>fragment.xml.</b>&nbsp;
-It is similar to the plug-in manifest file.&nbsp; Since a fragment shares many
-properties with its plug-in, some attributes in the plug-in manifest are not
-valid, such as the plug-in class and plug-in imports.</p>
-<p><a href="../reference/misc/plugin_archive.html">Plug-in
-archive</a> files can contain plug-ins or fragments.&nbsp; </p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/product_def_primary.htm b/bundles/org.eclipse.platform.doc.isv/guide/product_def_primary.htm
deleted file mode 100644
index 5a92ea0..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/product_def_primary.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Primary feature</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Primary feature</h3>
-<p>In Eclipse 2.1, the notion of a <b>primary feature</b> was used to customize
-  the product-branding aspects of a product. This mechanism is still supported
-  in Eclipse 3.0,
-but is effectively deprecated.  Newly developed products should use the <a href="product_def_extpt.htm">products
-extension point</a>
-to define a product.
-</p>
-<p>The remainder of this discussion describes the legacy product definition using
-  primary features.</p>
-<p>When the Eclipse platform is started, exactly one feature can control
-  the overall &quot;personality&quot; or &quot;branding&quot; of the platform,
-  including the splash screen, window images, about box, welcome page, and other
-  customizable aspects of the platform.&nbsp; This feature is called the product's <b>primary feature</b>.</p>
-<p>Let's look again at the description of the platform feature from Eclipse 2.1:</p>
-<pre>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
-&lt;feature
-      id="org.eclipse.platform"
-      label="%featureName"
-      version="2.1.0"
-      provider-name="%providerName"
-      plugin=""
-      image="eclipse_update_120.jpg"
-      <b>primary="true"</b>
-      application="org.eclipse.ui.ide.workbench"&gt;
-      ...</pre>
-<p>The platform feature has been designated as a primary feature. Although it's
-possible to designate many features as primary features in their <b>feature.xml</b> 
-files, only one primary feature gets control when the platform is launched. This
-is controlled by setting the <b>eclipse.product</b> property in the  product's <b>config.ini </b>file
-underneath
-the <b>eclipse/configuration</b>
-directory.&nbsp; If there are multiple eligible primary features, the <b>-product </b>command
-line option for <b>eclipse.exe</b> overrides the choice made in <b>config.ini</b>.</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/product_extension.htm b/bundles/org.eclipse.platform.doc.isv/guide/product_extension.htm
deleted file mode 100644
index 8db4d26..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/product_extension.htm
+++ /dev/null

@@ -1,85 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Product extensions</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Product extensions</h2>
-<p>An <b>extension</b> is a set of Eclipse features and plug-ins that are
-designed to extend the functionality of already-installed Eclipse based
-products.&nbsp; Extensions are installed separately, but used only in
-conjunction with other Eclipse based products.&nbsp; This means that an extension does not
-need to install a JRE, the Eclipse platform, or a primary feature.&nbsp; The
-recommended directory structure for extensions allows a single installation to be
-used with multiple Eclipse based products.</p>
-<p>The following directory structure shows how an extension for a hypothetical
-product, <b>betterwebs</b>, could be used to extend the function of the <b>acmeweb</b>
-product.</p>
-<pre>betterwebs/
-	eclipse/			<i>(directory for installed Eclipse files)</i>
-		.eclipseextension	(marker file)
-		features/		<i>(installed features)</i>
-			com.example.betterwebs.betterfeature_1.0.0/
-				feature.xml
-		plugins/
-			com.example.betterwebs.betterfeature_1.0.0/
-				plugin.xml
-				about.html
-			com.example.betterwebs.betterwebsupport_1.0.0/
-</pre>
-
-<p>The relationship between an extension and the product that it is designed to
-enhance is set up in the <b>links</b> directory of the original product.&nbsp;
-Recall the following directory in the acmeweb product:</p>
-<pre>acmeweb/
-	...
-	eclipse/		<i>(directory for installed Eclipse files)</i>
-		...
-		jre/
-		features/	<i>(installed features)</i>
-			...
-		plugins/
-			...
-<b>		links/
-</b>			com.example.betterwebs.betterfeature.link</pre>
-
-<p>When an extension is installed, it creates a link file in the <b>links</b>
-directory of any product that it is intending to extend.&nbsp; This link file
-makes the original product aware of the existence of the extension.</p>
-
-<h3>Installing and uninstalling extensions</h3>
-
-<p>The install process for extensions is similar to that for products except for
-the following differences:</p>
-
-<ul>
-  <li>Determine which already-installed product is to be extended (by asking the
-    user or searching the computer for the appropriate marker file)</li>
-  <li>Create an <b>.eclipseextension</b> marker file (instead of an <b>.eclipseproduct</b>
-    marker file).&nbsp; The format and content are similar to the product
-    markers.</li>
-  <li>Create a link file for the extension and write it into the <b>links</b>
-    directory of the associated product.&nbsp; The link file has the same name
-    as the extension's feature directory without the version suffix.&nbsp; The
-    link file is a <b>java.io.Properties </b>format file which defines the path
-    to the installed extension.</li>
-</ul>
-<p>The uninstall process for extensions is similar to that for products except
-that the uninstall must remove the link file from any products where it added
-one. </p>
-<p>Additional information on installing extensions can be found in <a href="../reference/misc/eclipse-install.html">How
-to write an Eclipse installer</a>.</p>
-
-<p>A product extension can be "softly" linked to an eclipse installation by using the update manager: open <b>Help > Software Updates > Manage Configuration</b> 
-and click on the "Add an extension location" link on the right pane.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/product_update.htm b/bundles/org.eclipse.platform.doc.isv/guide/product_update.htm
deleted file mode 100644
index af4139a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/product_update.htm
+++ /dev/null

@@ -1,83 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Updating a product or extension</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Updating a product or extension</h2>
-<p>By following the prescribed procedures for packaging and installing products,
-we can take advantage of the <b>platform update manager,</b> which treats
-products and extensions in a uniform way and allows users to discover and
-install updated versions of products and extensions.</p>
-<p>Before looking at the implementation of such a server, it's important to
-revisit some important concepts:</p>
-<ul>
-  <li>The platform provides a framework for defining <b>features</b> and update <b>sites</b>.&nbsp;
-    The platform itself defines a concrete implementation of features and
-    sites.&nbsp; This concrete implementation is what allows the update server
-    to upgrade and install additional features.</li>
-  <li>The platform <b>update server</b> can be used to <b>update</b> products by
-    installing new versions of features.&nbsp; It can also be used to <b>install</b>
-    or <b>update</b> extensions by adding or upgrading features.&nbsp;&nbsp;
-    This is only possible for products and extensions that conform to the
-    platform's concrete implementation of features and sites and conform to the
-    appropriate install guidelines.</li>
-  <li>Developers are free to use native installers and uninstallers to upgrade
-    their own products and extensions without regard to sites and the
-    update manager.</li>
-</ul>
-<p>That said, what do we do if we want to fully participate in the platform
-implementation of product updating and use its update server?</p>
-<h3>Feature and plug-in packaging</h3>
-<p>The previous example product and extension directory structures show how
-features and plug-ins are laid out once they are installed.&nbsp; In order to
-install features using the update server, the features must be packaged in a
-feature archive file.&nbsp; This is described in <a href="../reference/misc/feature_archive.html"> Feature
-Archive Files</a>. </p>
-<p>Plug-ins and fragments must be packaged according to the format described in <a href="../reference/misc/plugin_archive.html"> Plug-in
-Archive Files</a>.</p>
-<h3>Update server layout</h3>
-<p>The update server must be a URL-accessible server with a fixed layout.&nbsp;
-The list of available features and plug-ins provided by the server is described
-in a site map file, <b>site.xml</b>.&nbsp; The update server URL can be
-specified as a full URL to the site map file, or a URL of a directory path
-containing the site map.&nbsp; The site map file contains a list of all the
-available features and the location of the feature archives on the server.&nbsp;
-It also describes the locations of the plug-in archives that are referenced in
-the feature manifest.</p>
-<p>A simple site layout for our example web product and extension could look something like this:</p>
-<pre>&lt;site root&gt;/
-	site.xml
-	features/	<i>(contains feature archive files)</i>
-		com.example.acme.acmefeature_1.0.1.jar
-		com.example.betterwebs.betterfeature_1.0.1.jar
-		...
-	plugins/	<i>(contains plug-in archive files)</i>
-		com.example.acme.acmefeature_1.0.1.jar
-		com.example.acme.acmewebsupport_1.0.3.jar
-		com.example.betterwebs.betterfeature_1.0.1.jar
-		com.example.betterwebs.betterwebsupport_1.0.1.jar
-		...</pre>
-<p>The complete definition for the site map is described in <a href="../reference/misc/update_sitemap.html"> Update Server Site Map</a>.</p>
-<h3>Update servers and policies</h3>
-<p>An Eclipse update server is provided for updating the platform
-itself.  In addition, the platform update UI allows users can maintain a list of update servers that
-can be searched for new features.  Any site that conforms to the specified update server
-layout may be added to the list.   Users can choose to manually or automatically search for
-additional features or upgrades to their installed features.  </p>
-<p>Some organizations may wish to have more control over how their user installations are updated.
-This can be accomplished with an update <b>policy</b> file that specifies which features can be updated
-and which servers can be used to update a particular feature.   See <a href="../reference/misc/update_policy.html"> Update Policy Control</a>
-for a complete definition of the policy file and how it is used.
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/rcp.htm b/bundles/org.eclipse.platform.doc.isv/guide/rcp.htm
deleted file mode 100644
index a7314d4..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/rcp.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Building a Rich Client Platform application
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>Building a Rich Client Platform application</h1>
-<P>
-While the Eclipse platform is designed to serve as an open tools platform, it is architected so that its components could be 
-used to build just about any client application.  The minimal set of plug-ins needed to build a rich client application is collectively
-known as the <b>Rich Client Platform</b>.  
-</P>
-<p>
-Applications that don't require a common resource model can be built using a subset of the platform.  These rich applications
-are still based on a dynamic plug-in model, and the UI is built using the same toolkits and extension points.  The layout and
-function of the workbench is under fine-grained control of the plug-in developer in this case.  Up until now, we've been adding
-all of our visible function to the platform SDK workbench.  In a rich client application, we are responsible for defining the
-application and its workbench.
-</P>
-<p>
-When we say that the Rich Client Platform is the minimal set of plug-ins needed to build a platform application with
-a UI, we mean that your application need only require two plug-ins, <b>org.eclipse.ui</b> and <b>org.eclipse.core runtime</b>.  
-However, rich client applications are free to use any API deemed necessary 
-for their feature set, and can require any plug-ins above the bare minimum.  The 
-<a href="../reference/misc/overview-platform.html">Map of platform plug-ins</a> is a useful 
-reference when determing what plug-ins should be required when using various platform
-API.</P>
-<p>The main thing that differentiates a rich client application from the platform workbench is that the application
-is responsible for defining which class should be run as the main application.  We'll look at how this is done in
-the context of an example.
-</p>
-
-
-</BODY></HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/rcp_actions.htm b/bundles/org.eclipse.platform.doc.isv/guide/rcp_actions.htm
deleted file mode 100644
index 06ec041..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/rcp_actions.htm
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Defining the actions
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-Defining the actions</H3>
-<P>
-The primary customization provided by the <b>BrowserAdvisor</b> in the browser example is the
-designation of the action bar content for the workbench window:</p>
-<pre>	public void fillActionBars(IWorkbenchWindow window, IActionBarConfigurer configurer, int flags) {
-		...
-		BrowserActionBuilder builder = new BrowserActionBuilder(window);
-		getWorkbenchConfigurer().getWindowConfigurer(window).setData(BUILDER_KEY, builder); 
-		builder.fillActionBars(configurer, flags);
-	}
-</pre> 
-<p>Let's take a closer look at how these actions are defined in the <b>BrowserActionBuilder</b>.  In particular,
-let's look at the actions that are handled by the browser view.</p>
-<pre>private void makeActions() {
-		...				
-		backAction = new RetargetAction("back", "&amp;Back");  
-		backAction.setToolTipText("Back");
-		backAction.setImageDescriptor(images.getImageDescriptor(ISharedImages.IMG_TOOL_BACK));
-		window.getPartService().addPartListener(backAction);
-		
-		forwardAction = new RetargetAction("forward", "&amp;Forward");  
-		forwardAction.setToolTipText("Forward");
-		forwardAction.setImageDescriptor(images.getImageDescriptor(ISharedImages.IMG_TOOL_FORWARD));
-		window.getPartService().addPartListener(forwardAction);
-		
-		stopAction = new RetargetAction("stop", "Sto&amp;p"); 
-		stopAction.setToolTipText("Stop");
-		window.getPartService().addPartListener(stopAction);
-		
-		refreshAction = new RetargetAction("refresh", "&amp;Refresh");  
-		refreshAction.setToolTipText("Refresh");
-		window.getPartService().addPartListener(refreshAction);
-		...
-	}
-</pre> 
-<p>The actions are defined as retargetable actions so that individual views can implement the handler actions.
-The <b>BrowserView</b> associates its handler actions with the window's retargetable actions when it creates 
-the controls for the view:</p>
-<pre>	private Browser createBrowser(Composite parent, final IActionBars actionBars) {
-		
-		...
-		actionBars.setGlobalActionHandler("back", backAction); 
-		actionBars.setGlobalActionHandler("forward", forwardAction); 
-		actionBars.setGlobalActionHandler("stop", stopAction); 
-		actionBars.setGlobalActionHandler("refresh", refreshAction); 
-		...
-	}
-</pre>
-<p>These actions are created when the view is first created.</p>
-<pre>	private Action backAction = new Action("Back") {
-		public void run() {
-			browser.back();
-		}
-	};
-</pre>
-<p>
-See <a href="wrkAdv_retarget.htm">Retargetable actions</a> for a complete discussion of retargetable actions and how they
-are defined and implemented.
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/rcp_advisor.htm b/bundles/org.eclipse.platform.doc.isv/guide/rcp_advisor.htm
deleted file mode 100644
index f4a3d08..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/rcp_advisor.htm
+++ /dev/null

@@ -1,124 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Customizing the workbench
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Customizing the workbench</H2>
-<p>The "entry point" for supplying custom workbench behavior is the designation of a
-<b><a href="../reference/api/org/eclipse/ui/application/WorkbenchAdvisor.html">WorkbenchAdvisor</a></b>
-for configuring the workbench.  Your rich client plug-in should extend this abstract class to provide
-the application-specific configuration for the workbench.  The browser example does this using the 
-<b>BrowserAdvisor</b> class.</p>
-<pre>
-	...
-	int code = PlatformUI.createAndRunWorkbench(display,
-			<b>new BrowserAdvisor()</b>);
-	...
-</pre>
-<p>A workbench advisor is responsible for overriding methods to configure the workbench with its desired layout and
-features, such as the action bar items or intro page.  
-</p>
-<h3>The workbench life-cycle</h3>
-<p>Life-cycle methods provided by the workbench advisor allow
-your application to hook into the creation of the workbench at any point in time and influence the behavior.
-The following list of advisor life-cycle methods that can be overridden
-comes from the javadoc for <b><a href="../reference/api/org/eclipse/ui/application/WorkbenchAdvisor.html">WorkbenchAdvisor</a></b>.</p>
-<ul>
-<li><code>initialize</code> - called first; before any windows; use to
-register things</li>
-<li><code>preStartup</code> - called second; after initialize but
-before first window is opened; use to temporarily disable things during
-startup or restore</li>
-<li><code>postStartup</code> - called third; after first window is
-opened; use to reenable things temporarily disabled in previous step</li>
-<li><code>postRestore</code> - called after the workbench and its windows
-have been recreated from a previously saved state; use to adjust the
-restored workbench</li>
-<li><code>preWindowOpen</code> - called as each window is being opened; 
-use to configure aspects of the window other than action bars </li>
-<li><code>fillActionBars</code> - called after <code>preWindowOpen</code> to
-configure a window's action bars</li>
-<li><code>postWindowRestore</code> - called after a window has been
-recreated from a previously saved state; use to adjust the restored
-window</li>
-<li><code>postWindowCreate</code> -  called after a window has been created,
-either from an initial state or from a restored state;  used to adjust the
-window</li>
-<li><code>openIntro</code> - called immediately before a window is opened in
-order to create the introduction component, if any.</li>
-<li><code>postWindowOpen</code> - called after a window has been
-opened; use to hook window listeners, etc.</li>
-<li><code>preWindowShellClose</code> - called when a window's shell
-is closed by the user; use to pre-screen window closings</li>
-<li><code>eventLoopException</code> - called to handle the case where the
-event loop has crashed; use to inform the user that things are not well</li>
-<li><code>eventLoopIdle</code> - called when there are currently no more
-events to be processed; use to perform other work or to yield until new
-events enter the queue</li>
-<li><code>preShutdown</code> - called just after event loop has terminated
-but before any windows have been closed; allows the application to veto
-the shutdown</li>
-<li><code>postShutdown</code> - called last; after event loop has terminated
-and all windows have been closed; use to deregister things registered during
-initialize</li>
-</ul> 
-<p>
-As you can see, a rich client application has a lot of control over how the workbench is configured
-and implemented.  In the browser example, the primary function of the <b>BrowserAdvisor</b> is to configure the action bars with
-menu items appropriate for a browser.  This is done in the <b>fillActionBars</b> method:</p>
-<pre>
-	public void fillActionBars(IWorkbenchWindow window, IActionBarConfigurer configurer, int flags) {
-		...
-		BrowserActionBuilder builder = new BrowserActionBuilder(window);
-		getWorkbenchConfigurer().getWindowConfigurer(window).setData(BUILDER_KEY, builder); 
-		builder.fillActionBars(configurer, flags);
-	}
-</pre> 
-<p>In this method, the workbench is configured with a specialized action builder.  This action builder
-is used to fill the action bars of the workbench.  We'll look at the details for how the actions are specified
-in <a href="rcp_actions.htm">Defining the actions</a>.  For now, we are focusing on how we configure
-the workbench.</p>
-<p>Note the use of the <b>getWorkbenchConfigurer()</b> method above.  The 
-<b><a href="../reference/api/org/eclipse/ui/application/IWorkbenchConfigurer.html">IWorkbenchConfigurer</a></b> and
-<b><a href="../reference/api/org/eclipse/ui/application/IWorkbenchWindowConfigurer.html">IWorkbenchWindowConfigurer</a></b> are
-used in conjunction with the <b><a href="../reference/api/org/eclipse/ui/application/WorkbenchAdvisor.html">WorkbenchAdvisor</a></b>
-to customize the window.  These classes allow you to override many aspects of workbench creation at different levels.
-For example, the <b><a href="../reference/api/org/eclipse/ui/application/IWorkbenchWindowConfigurer.html">IWorkbenchWindowConfigurer</a></b> defines
-protocol that assumes a particular configuration of controls in the workbench window, such an action bar, status line, perspective bar,
-cool bar, etc.  Its protocol allows you customize and populate these items.  The 
-<b><a href="../reference/api/org/eclipse/ui/application/IWorkbenchConfigurer.html">IWorkbenchConfigurer</a></b> 
-operates at a higher level, allowing you to store application-specific data with the workbench.  The
-<b><a href="../reference/api/org/eclipse/ui/application/WorkbenchAdvisor.html">WorkbenchAdvisor</a></b> provides
-access to these configurers in the life-cycle methods noted above.  Lower level methods inside 
-<b><a href="../reference/api/org/eclipse/ui/application/WorkbenchAdvisor.html">WorkbenchAdvisor</a></b> may be overridden
-to completely replace default behavior.  For example, your workbench advisor could
-override the method that creates the SWT controls in the window in order to provide a completely
-different implementation for the main window.</p>
-<p>
-In other words, there are many ways to customize the workbench and several different levels at which these
-techniques can be used.
-The javadoc for <b><a href="../reference/api/org/eclipse/ui/application/WorkbenchAdvisor.html">WorkbenchAdvisor</a></b>,
-<b><a href="../reference/api/org/eclipse/ui/application/IWorkbenchConfigurer.html">IWorkbenchConfigurer</a></b>, and
-<b><a href="../reference/api/org/eclipse/ui/application/IWorkbenchWindowConfigurer.html">IWorkbenchWindowConfigurer</a></b>
-includes a complete description of the available protocol.  See also the complete implementation of
-<b>BrowserAdvisor</b> for comments on alternate implementations. 
-</p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/rcp_browser.htm b/bundles/org.eclipse.platform.doc.isv/guide/rcp_browser.htm
deleted file mode 100644
index 17bd5da..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/rcp_browser.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-The browser example
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-The browser example</H2>
-<P>
-
-We will look at how to build a Rich Client Platform application by going through a simple
-web browser example.  This example is not included in the R3.0 SDK, but can be downloaded from the project
-<a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ui.examples.rcp.browser/">org.eclipse.ui.examples.rcp.browser</a>.
-If you are working in Eclipse, you may simply check out the project from the Eclipse CVS repository (see the
-<a href="http://dev.eclipse.org/cvshowto.html">Eclipse CVS How-To</a> if you are not familiar with the procedure for
-checking out projects from CVS).
-</p>
-<p>
-To run the RCP Browser example from within the Eclipse SDK: </p>
-<ol>
-<li>Load the project <tt>org.eclipse.ui.examples.rcp.browser</tt> from the Eclipse CVS repository. </li>
-<li>Choose <b>Run&gt;Run...</b> from the workbench menu bar and create a new "Run-time workbench" 
-configuration named "Browser Example". </li>
-<li>On the <b>Arguments</b> tab, select <b>Run a product</b> and select "org.eclipse.ui.examples.rcp.browser.product" from the drop-down. </li>
-<li>On the <b>Plug-ins</b> tab, select <b>Choose plug-ins and fragments to launch from the list</b> so that you can select which
-plug-ins are needed. </li>
-<li>Press <b>Deselect All</b> to start with a clean slate. </li>
-<li>Check "org.eclipse.ui.examples.rcp.browser" </li>
-<li>Press <b>Add Required Plug-ins</b>. </li>
-<li>Check "org.eclipse.update.configurator" </li>
-<li>Run or debug the new run configuration. </li>
-</ol>
-<img border="0" src="images/browserexample.png" alt="Browser Example Window">
-<p>
-As you can see, it's hard to tell that this application has anything at all to do with Eclipse (apart from the default
-web site that it browses!).  There is no resource navigator, no mention of the Eclipse Platform, and none of the familiar
-menu bar items from the platform workbench.  (The few Eclipse-related features, such as the window icon, could
-also be reconfigured if desired.)
-</p>
-<p>
-Hopefully this example helps clarify what's exciting about the Rich Client Platform.  Let's take a look under the covers so we
-can learn what's involved in building one.  We'll assume that you are familiar with the basic workbench extensions discussed in
-<a href="workbench.htm">Plugging into the workbench</a>.  
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/rcp_define.htm b/bundles/org.eclipse.platform.doc.isv/guide/rcp_define.htm
deleted file mode 100644
index 4d05bf1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/rcp_define.htm
+++ /dev/null

@@ -1,87 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Defining a rich client application
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Defining a rich client application</H2>
-<p>
-The definition of a rich client application plug-in starts out similarly to the other plug-ins we've been
-studying.  The only difference in the first part of the markup is that the list of required plug-ins is much
-smaller than we've been used to!</p>
-<pre>
-&lt;?xml version="1.0" encoding="UTF-8"?&gt;
-&lt;?eclipse version="3.0"?&gt;
-&lt;plugin
-   id="org.eclipse.ui.examples.rcp.browser"
-   name="%pluginName"
-   version="3.0.0"
-   provider-name="%providerName"&gt;
-
-   &lt;runtime&gt;
-      &lt;library name="browser.jar"&gt;
-      &lt;/library&gt;
-   &lt;/runtime&gt;
-   &lt;requires&gt;
-      &lt;import plugin="org.eclipse.core.runtime"/&gt;
-      &lt;import plugin="org.eclipse.ui"/&gt;
-   &lt;/requires&gt;
-</pre>
-<P>
-Up to now, we've contributed function to the platform workbench by declaring extensions that
-add elements to the workbench.  In all of the <tt>plugin.xml</tt> content that we've reviewed so far,
-we've only looked at individual contributions to a workbench that is assumed to be there.  On the rich
-client platform, there is no application already defined.  Your rich client plug-in is the one
-responsible for specifying the class that should be executed when the platform is started.  This 
-is done in the <a href="../reference/extension-points/org_eclipse_core_runtime_applications.html"><b>org.eclipse.core.runtime.applications</b></a>
-extension.</p>
-<pre>   &lt;extension
-         point="org.eclipse.core.runtime.applications"
-         id="app"
-         name="%appName"&gt;
-      &lt;application&gt;
-         &lt;run
-            class="org.eclipse.ui.examples.rcp.browser.BrowserApp"&gt;
-         &lt;/run&gt;
-      &lt;/application&gt;
-   &lt;/extension&gt;
-</pre> 
-<p>In this extension, we specify the class that should be run when the platform is first started.
-This class must implement <b><a href="../reference/api/org/eclipse/core/runtime/IPlatformRunnable.html">IPlatformRunnable</a></b>,
-which simply means that it must implement a <b>run</b> method.  The run method is responsible for creating the SWT display and
-starting up a workbench.  The class <b><a href="../reference/api/org/eclipse/ui/PlatformUI.html">PlatformUI</a></b>
-implements convenience methods for performing these tasks.</p>
-<pre>	public Object run(Object args) throws Exception {
-		Display display = PlatformUI.createDisplay();
-		try {
-			int code = PlatformUI.createAndRunWorkbench(display,
-					<b>new BrowserAdvisor()</b>);
-			// exit the application with an appropriate return code
-			return code == PlatformUI.RETURN_RESTART
-					? EXIT_RESTART
-					: EXIT_OK;
-		} finally {
-			if (display != null)
-				display.dispose();
-		}
-	}
-</pre>
-<p>The call to <b>createAndRunWorkbench</b> will not return until the workbench is closed.  The SWT event loop and other
-low-level logistics are handled inside this method.  At this stage, it's not so important
-that you understand the underlying mechanics in running an SWT application.  This code can be copied to your rich client
-application with minimal changes.  In fact, the hook for you to add your own functionality is the <b>WorkbenchAdvisor</b>
-that is passed as an argument when the workbench is created.  Let's take a closer look.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/rcp_dynamic.htm b/bundles/org.eclipse.platform.doc.isv/guide/rcp_dynamic.htm
deleted file mode 100644
index 9303fa9..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/rcp_dynamic.htm
+++ /dev/null

@@ -1,154 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Dynamic Plug-ins
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2> Dynamic Plug-ins</H2>
-
-<p>Dynamic Plug-ins provide the ability to insert and remove 
-  plug-ins into a running instance of Eclipse. A reusable component with the potential 
-  to be unloaded, Dynamic Plug-ins provide an easy way to help you track the comings 
-  and goings of plug-ins. </p>
-<p> A dynamic plug-in may not remain for the life of the 
-  application, as such, it is essential to ensure that when the component goes 
-  away everything is cleaned up. When listeners are 
-  hooked on the Workbench and items are registered, they remain there after shut 
-  down, these plug-ins must be aware that they need to clean up.</p>
-<p>The assumption that on start up, a read through of all 
-  the implementations of the extension point will be sufficient for the life of 
-  the application is false as that will not work. You must ensure that either 
-  the listener is hooked or that nothing is ever cached, so that registry changes 
-  are listened for. It is important to understand that items in the workbench 
-  are not necessarily static, they are in fact transient and could go away at 
-  any time. If you're writing a plug-in for a specific view first ensure that 
-  the view is still there.</p>
-<p>As a plug-in developer you need to ensure that any extensions 
-  you may utilize are allowed to appear and disappear at any given point. When 
-  they disappear you should acknowledge their disappearance by cleaning up any 
-  internal structures that may represent the extensions and remove any UI artifacts 
-  that they may drive. When they appear you should augment your internal structures 
-  and possibly create new UI artifacts. Assume that 
-  your application is reading from the registry and has an extension, you create 
-  a record for it and assign its location. Upon its conclusion, you would be notified 
-  that a clean up is required. In addition, a listener will announce when new 
-  items come in and create them. </p>
-<p>The org.eclipse.core.runtime.dynamicHelpers.IExtensionTracker and associated 
-  interfaces provide a mechanism by which plug-in developers can easily track 
-  the coming and going of extensions and manage the resources generated by such 
-  actions.</p>
-<p>The following example assumes that you have an extension point in your plug-in 
-  called widgets and that you are using IExtensionTracker. Internally, you have 
-  WidgetDescriptors that encapsulate widget extensions and a WidgetRegistry to 
-  manage them. </p>
-  <pre>
-
-
-	public class WidgetRegistry implements IExtensionChangeHandler {
-
-	
-	
-	  public WidgetRegistry() {
-		
-		IExtensionTracker tracker = PlatformUI.getWorkbench()
-	
-  	.getExtensionTracker();<br>
-  	IExtensionPoint point = Platform.getExtensionRegistry()
-    
-		.getExtensionPoint(&quot;my.plugin.namespace&quot;, &quot;widget&quot;);<br>	
-  	IExtension[] extensions = point.getExtensions();<br>
-  	// initial population<br>
- 	    for (int i = 0; i &lt; extensions.length; i++) {
-		
-			addExtension(tracker, extensions[i]);<br>
-		}
-		 
-
-		tracker<br>
-  	.registerHandler(this, tracker<br>
-		.createExtensionPointFilter(point));
-	}
-
-
-
-	 public void addExtension(IExtensionTracker tracker, IExtension extension){
-  
-	 	WidgetDescriptor descriptor = new WidgetDescriptor(extension);
-	 
-		tracker.registerObject(extension, descriptor,<br>
-  	IExtensionTracker.REF_STRONG);
-		
-		addToInternalStructure(descriptor)
-	
-	}
-
-
-
-	private void addToInternalStructure(WidgetDescriptor descriptor) {
-
-		// registry specific logic
-  }
-
-
-
-public void removeExtension(IExtension extension, Object[] objects) {
-
-	for (int i = 0; i &lt; objects.length; i++) {
-
-		WidgetDescriptor descriptor = (WidgetDescriptor) objects[i];<br>
-	  	removeFromInternalStructure(descriptor);<br>
-  }<br>
- }
-
-	private void removeFromInternalStructure(WidgetDescriptor 
-  descriptor) {
-	
-		// registry specific logic
-  }<br>
-}
-
- 
-  public void dispose() {
-
-		PlatformUI.getWorkbench()
-	
-	    .getExtensionTracker().unregisterHandler(this)<br>
-  }
-
-}<br>
-  
-  </pre>
-
-
-<p>In this example Platform UI provides IExtensionTracker instances at various 
-  levels of the Workbench. If you're tracking objects that live for the life of 
-  the workbench you should use the tracker provided by IWorkbench.getExtensionTracker(). 
-  If your objects are relevant to particular workbench windows or pages, you should 
-  use the trackers provided by IWorkbenchWindow.getExtensionTracker() or IWorkbenchPage.getExtensionTracker(). 
-  For instance, Workbench tracks view descriptors at the Workbench level but tracks 
-  actual view instances at the workbench page level. Your handlers may be registered 
-  against particular extension points via providing an IFilter instance to IExtensionTracker.registerHandler(). 
-  Your handler will only be called when extensions matching the IFilter object 
-  are added or removed. </p>
-<p>When an extension enters the runtime this method will be called. Your handler 
-  then has the opportunity to incorporate the new extension into its associated 
-  model. Any objects created based on the IExtension provided to this interface 
-  should be registered against the tracker via IExtensionTracker.registerObject(). 
-  When an extension leaves the runtime this method will be called. Any objects 
-  previously registered against the extension will be passed as arguments. Your 
-  handler may then clean up and dispose of the objects as necessary. It's good 
-  practice to unregister your handlers so that your registries are not leaked.</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/rcp_extensions.htm b/bundles/org.eclipse.platform.doc.isv/guide/rcp_extensions.htm
deleted file mode 100644
index 955e642..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/rcp_extensions.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Making UI contributions
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Making UI contributions</H2>
-<P>
-So far, we've seen that the main difference between a rich client platform plug-in and an 
-Eclipse SDK plug-in is that the rich client plug-in is responsible for specifying the  
-class that should be run when the platform is started.  This class creates and runs a
-workbench window that is configured appropriately.  What else is different about a rich
-client application?  Not much, actually.
-</p>
-<p>Once the infrastructure for the application workbench is in place, the techniques for 
-adding function to the workbench are the same as those we used when we were extending the
-platform SDK workbench.  The workbench UI extension points are used to add views, editors,
-menus, and all of the other contributions we know and love.  In the case of the browser example,
-we'll be adding extensions for a perspective and a couple of views. </p>
-<p>
-We were introduced to these extensions in <a href="workbench.htm">Plugging into the workbench</a>.
-For completeness, we'll take a look at how the browser example uses these extensions, but we'll
-assume that we already have a working knowledge of these concepts.
-</p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/rcp_perspective.htm b/bundles/org.eclipse.platform.doc.isv/guide/rcp_perspective.htm
deleted file mode 100644
index 33eea6a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/rcp_perspective.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Adding the perspective
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-Adding the perspective</H3>
-<P>
-When a rich client application uses the <b><a href="../reference/api/org/eclipse/ui/application/WorkbenchAdvisor.html">WorkbenchAdvisor</a></b>
-as the primary means for customizing the workbench, it must supply a perspective that is shown in the workbench window.
-This perspective must be identified in the application's workbench advisor class.  The following is specified in the
-<b>BrowserAdvisor</b> class:</p>
-<pre>	public String getInitialWindowPerspectiveId() {
-		return BrowserApp.BROWSER_PERSPECTIVE_ID; 
-	}
-</pre> 
-<p>While <b>BrowserApp</b> defines:</p>
-<pre>	public static final String PLUGIN_ID = "org.eclipse.ui.examples.rcp.browser";
-	public static final String BROWSER_PERSPECTIVE_ID = PLUGIN_ID + ".browserPerspective";
-</pre> 
-<p>The corresponding perspective is defined in the browser plug-in's manifest:</p>
-<pre>   &lt;extension
-         point="org.eclipse.ui.perspectives"&gt;
-      &lt;perspective
-            id="org.eclipse.ui.examples.rcp.browser.browserPerspective"
-            name="%perspectives.browser.name"
-            class="<b>org.eclipse.ui.examples.rcp.browser.BrowserPerspectiveFactory</b>"
-            fixed="true"/&gt;
-   &lt;/extension&gt;
-</pre> 
-<p>The <b>BrowserPerspectiveFactory</b> is responsible for laying out the views appropriately.</p>
-<pre>	public void createInitialLayout(IPageLayout layout) {
-		layout.addView(BrowserApp.BROWSER_VIEW_ID, IPageLayout.RIGHT, .25f, IPageLayout.ID_EDITOR_AREA);
-		layout.addPlaceholder(BrowserApp.HISTORY_VIEW_ID, IPageLayout.LEFT, .3f, IPageLayout.ID_EDITOR_AREA); 
-		IViewLayout historyLayout = layout.getViewLayout(BrowserApp.HISTORY_VIEW_ID);
-		historyLayout.setCloseable(true);
-		layout.setEditorAreaVisible(false);
-	}
-</pre>
-<p>The browser perspective defines two views (one visible, with a placeholder for the other), and makes the
-editor area invisible.  For a complete discussion of perspectives and their corresponding layout, see <a href="workbench_perspectives.htm">Perspectives</a>.
-</p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/rcp_view.htm b/bundles/org.eclipse.platform.doc.isv/guide/rcp_view.htm
deleted file mode 100644
index 8eef2d8..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/rcp_view.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Adding views
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-Adding views</H3>
-<P>
-The browser example defines two views in its workbench.  One view shows the browser content and the other
-displays the history of visited links.  We first saw these views when they were added to the browser's perspective:</p> 
-<pre>	public void createInitialLayout(IPageLayout layout) {
-		<b>layout.addView(BrowserApp.BROWSER_VIEW_ID, IPageLayout.RIGHT, .25f, IPageLayout.ID_EDITOR_AREA);
-		layout.addPlaceholder(BrowserApp.HISTORY_VIEW_ID, IPageLayout.LEFT, .3f, IPageLayout.ID_EDITOR_AREA); </b>
-		IViewLayout historyLayout = layout.getViewLayout(BrowserApp.HISTORY_VIEW_ID);
-		historyLayout.setCloseable(true);
-		layout.setEditorAreaVisible(false);
-	}
-</pre>
-<p> The corresponding views are also defined in the browser plug-in's manifest:</p> 
-<pre>   &lt;extension
-         point="org.eclipse.ui.views"&gt;
-      &lt;category
-            id="org.eclipse.ui.examples.rcp.browser"
-            name="%views.category.name"/&gt;
-      &lt;view
-            id="org.eclipse.ui.examples.rcp.browser.browserView"
-            name="%views.browser.name"
-            icon="icons/eclipse.png"
-            <b>class="org.eclipse.ui.examples.rcp.browser.BrowserView"</b>
-            category="org.eclipse.ui.examples.rcp.browser"
-            allowMultiple="true"/&gt;
-      &lt;view
-            id="org.eclipse.ui.examples.rcp.browser.historyView"
-            name="%views.history.name"
-            icon="icons/eclipse.png"
-            <b>class="org.eclipse.ui.examples.rcp.browser.HistoryView"</b>
-            category="org.eclipse.ui.examples.rcp.browser"/&gt;
-   &lt;/extension&gt;
-</pre>
-<p>The <b>BrowserView</b> and <b>HistoryView</b> create the necessary SWT controls for showing the browser content
-and history.  The implementation of these views is no different for rich client plug-ins, so we won't
-review them here.  See the example classes and <a href="workbench_basicext_views.htm">
-org.eclipse.ui.views</a> for more information.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_batching.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_batching.htm
deleted file mode 100644
index ba10497..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_batching.htm
+++ /dev/null

@@ -1,144 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Batching resource changes
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-Batching resource changes</H3>
-<p>When you need to modify resources in the workspace, it is important to keep in mind that other plug-ins might be
-working with the same resources.  The resources API provides robust mechanisms for keeping plug-ins informed about
-changes in the workspace, and for making sure that multiple plug-ins do not modify the same resource at the same time.
-Where possible, your plug-in's modifications to the workspace should be batched in units of work inside a <b>workspace runnable</b>.
-These runnables help to reduce the amount of change notifications generated by changes.  They also allow you to declare
-which part of the workspace is to be modified, so that other plug-ins can be locked out of changing the same part of the
-workspace.
-</p>
-<p>The protocol for <b><a href="../reference/api/org/eclipse/core/resources/IWorkspaceRunnable.html">IWorkspaceRunnable</a></b> 
-is fairly simple.  A workspace runnable looks just like a long-running operation or platform job.  The actual work is done inside
-a <b>run</b> method, with progress reported to the supplied 
-<b><a href="../reference/api/org/eclipse/core/runtime/IProgressMonitor.html">IProgressMonitor</a></b>.  Code that
-manipulates the workspace is performed inside the <b>run</b> method.
-</p>
-<pre>IWorkspaceRunnable myRunnable = 
-	new IWorkspaceRunnable() {
-		<b>public void run(IProgressMonitor monitor) throws CoreException {</b>
-			//do the actual work in here
-			...
-		}
-}
-</pre>
-<p>When it is time to the run the code, your plug-in tells the workspace to run the code on its behalf.  This way, the
-workspace can generate any necessary change events and ensure that no two plug-ins are modifying the same resource
-at the same time.  (Even if your plug-in is not using background jobs and the concurrency framework to modify the
-workspace, other plug-ins may be doing so.)
-</p>
-<h4>Scheduling rules and locking</h4>
-<p><b><a href="../reference/api/org/eclipse/core/resources/IWorkspace.html">IWorkspace</a></b> protocol is used to
-run a workspace runnable.  The preferred technique is using the long form of the <b>run</b> method which supplies 
-a scheduling rule and specifies how resource change events are broadcast.
-</p>
-<p>Specifying a scheduling rule when running a workspace runnable allows the workspace to determine whether
-the resource changes will conflict with workspace changes happening in other threads.  (See 
-<a href="runtime_jobs_rules.htm">Scheduling rules</a> for an overview of scheduling rules and 
-<b><a href="../reference/api/org/eclipse/core/runtime/jobs/ISchedulingRule.html">ISchedulingRule</a></b> protocol.)
-Fortunately, <b><a href="../reference/api/org/eclipse/core/resources/IResource.html">IResource</a></b> 
-protocol includes the protocol for <b><a href="../reference/api/org/eclipse/core/runtime/jobs/ISchedulingRule.html">ISchedulingRule</a></b>,
-which means that a resource can often be used as a scheduling rule for itself.
-</p>
-<p>Confused?  Code can help to clarify this point.  Suppose your plug-in is getting ready to modify a bunch of
-resources in a particular project.  It can use the project itself as the scheduling rule for making the changes.
-The following snippet runs the workspace runnable that we created earlier:
-</p>
-<pre>IWorkspace workspace = ResourcesPlugin.getWorkspace();
-workspace.run(myRunnable, <b>myProject</b>, <b>IWorkspace.AVOID_UPDATE</b>, null);
-</pre>
-<p>The runnable is passed to the workspace, followed by the project that the 
-code is manipulating.  This tells the workspace that all of the changes in the 
-runnable are confined to <tt>myProject</tt>.  Any requests by other threads
-to change <tt>myProject</tt> will be blocked until this runnable completes.  
-Likewise, this call will block if some other thread is already modifying 
-<tt>myProject</tt>.  By specifying which part of the resource tree will be 
-modified by the runnable, you are allowing other threads to continue modifying 
-other portions of the workspace.  It is important to be sure that your resource rule 
-matches the work being done inside the runnable.  When a non-null scheduling 
-rule is used, any attempt to access a resource outside the scope of the scheduling 
-rule will trigger an exception.
-</p>
-<p>
-There are two special scheduling rules that are important to consider.  First,
-if you use an instance of <tt>IWorkspaceRoot</tt> as the scheduling rule,
-it means your thread is blocking access to <b>all</b> resources in the tree.
-While a thread holds the root rule, no other thread is allowed to modify the
-workspace.  Conversely, a rule of <tt>null</tt> indicates that the thread
-will block access to <b>no</b> resources in the tree.  While a thread with the
-null rule is free to modify the workspace itself, other threads will not be prevented
-from performing their own modifications.  The <tt>IWorkspaceRoot</tt> and
-<tt>null</tt> scheduling rules occupy opposite ends of the concurrency spectrum.  
-With <tt>IWorkspaceRoot</tt> there is no concurrency
-and only one thread is modifying the workspace at a time.  With a <tt>null</tt> rule,
-there is maximum concurrency as all threads can modify the workspace concurrently.
-</p>
-<p>The third parameter to the <b>run</b> method specifies whether any periodic resource change events should
-be broadcast during the scope of this call.  Using <tt>IWorkspace.AVOID_UPDATE</tt> tells the platform to suppress any
-resource change events while the runnable is running and to broadcast one event at the end of the changes.
-During this call, any other runnables created in the runnable will be considered part of the parent batch
-operation.  Resource changes made in those runnables will appear in the parent's resource change notification.
-</p>
-<h4>Resource rule factory</h4>
-<p>In the example above, we assumed that the code inside our runnable only modified resources in a particular project.
-This made it very easy to specify a scheduling rule for the runnable.  In practice, it can be more difficult
-to compute what parts of the workspace are affected by a particular change.  For example, moving a resource from one
-project to another affects both projects.  <b><a href="../reference/api/org/eclipse/core/resources/IResourceRuleFactory.html">IResourceRuleFactory</a></b> 
-can be used to help compute an appropriate resource rule for certain kinds of resource changes.  You can get
-a resource rule factory from the workspace itself.
-</p>
-<pre>IWorkspace workspace = ResourcesPlugin.getWorkspace();
-IResourceRuleFactory ruleFactory = <b>workspace.getRuleFactory()</b>;
-</pre>
-<p>The factory can supply rules appropriate for many kinds of operations.  If your runnable is moving a resource
-from one location to another, it can obtain a rule appropriate for this operation:
-</p>
-<pre>ISchedulingRule movingRule = ruleFactory.moveResource(sourceResource, destinationResource);
-workspace.run(myRunnable, <b>movingRule</b>, IWorkspace.AVOID_UPDATE, null);
-</pre>
-<p>See the javadoc for <b><a href="../reference/api/org/eclipse/core/resources/IResourceRuleFactory.html">IResourceRuleFactory</a></b> 
-for the list of available rules.  The resources plug-in uses these rules itself to implement most resource operations.
-Browsing the code that references these rule methods will help demonstrate how they are used in practice.
-</p>
-<p>Multiple rules can be combined using 
-<b><a href="../reference/api/org/eclipse/core/runtime/jobs/MultiRule.html">MultiRule</a></b>.
-</p>
-<pre>ISchedulingRule movingRule = ruleFactory.moveResource(sourceResource, destinationResource);
-ISchedulingRule modifyRule = ruleFactory.modifyResource(destinationResource);
-workspace.run(myRunnable, <b>MultiRule.combine(movingRule, modifyRule)</b>, IWorkspace.AVOID_UPDATE, null);
-</pre>
-<h4>Ignoring the rules</h4>
-<p>The short form of the <b>run</b> method in
-<b><a href="../reference/api/org/eclipse/core/resources/IWorkspace.html">IWorkspace</a></b>
-is also available.  It is retained for backward compatibility.  The short form does not include a rule or an update
-flag.
-</p>
-<pre>workspace.run(myRunnable, null);
-</pre>
-<p>is effectively the same as calling
-</p>
-<pre>workspace.run(myRunnable, workspace.getRoot(), IWorkspace.AVOID_UPDATE, null);
-</pre>
-<p>Specifying the workspace root as the scheduling rule will put a lock on the entire workspace until the runnable
-is finished.  This is the most conservative way to perform a workspace update, but it is not very friendly to
-other concurrency-minded plug-ins.
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_builders.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_builders.htm
deleted file mode 100644
index 782593c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_builders.htm
+++ /dev/null

@@ -1,253 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Incremental project builders</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Incremental project builders</H2>
-<P >
-An <b>incremental project builder</b> is an object that manipulates the resources in a project in
-a particular way.  Incremental project builders are often used to apply a
-transformation on a resource to produce a resource or artifact of another kind.
-</P>
-<p>Plug-ins contribute incremental project builders to the platform in order to implement specialized resource 
-transformations. For example, the Java development tools (JDT)define an incremental project builder that compiles
-a Java source file into a class file any time a file is added or modified in a Java project.  It also
-keeps track of dependent files and recompiles them when necessary.
-</p>
-<p>From an API point of view, the platform defines two basic types of builds:
-</p>
-<ul>
-<li>A <b> full build </b> performs a build from scratch. It treats all resources in a project
-as if they have never been seen by the builder.</li>
-<li>An <b> incremental build</b> uses a &quot;last build state,&quot; maintained internally by the builder,
-to do an optimized build based on the changes in the project since the last build.</li>
-</ul>
-<p>Incremental builds are seeded with a resource change delta. The delta reflects the net effect of all resource 
-changes since the builder last built the project.  This delta is similar to the one used inside resource change events.
-</p>
-<p>Projects can be periodically <b>cleaned</b> by the user in order to force a rebuild of a complete project
-the next time an incremental build is performed on that project.  Cleaning a project removes build information
-such as problem markers and class files.
-</p>
-<p>Builders are best understood by example. The JDT Java compiler is driven by a Java incremental project builder 
-which recompiles the files in a project that are affected by changes. When a full build is triggered, (or an incremental
-build after a clean), all of the <b> .java</b> files in the project are compiled. Any compile problems encountered 
-are added as problem markers on the affected <b> .java</b> files. When an incremental build is triggered, the builder 
-selectively recompiles the added, changed, or otherwise affected <b>.java</b> files that are described in the 
-resource delta and updates the problem markers as necessary. Any <b>.class</b> files or markers that are no 
-longer appropriate are removed.
-</p>
-<p>Incremental building has obvious performance benefits for projects with hundreds or thousands of resources, 
-most of which are unchanging at any given point in time.
-</p>
-<P >
-The technical challenge for incremental building is to determine exactly what needs to be rebuilt. For example, the
-internal state maintained by the Java builder includes things like a dependency
-graph and a list of compilation problems reported.  This information is used during an incremental build to 
-identify which classes need to be recompiled in response to a change in a Java resource. </P>
-<P >
-Although the basic structure for building is defined in the platform, the real work is done in the builder
-code.  Patterns for implementing complex incremental builders are beyond the scope of this discussion, since the 
-implementation is dependent on the specific builder design. </P>
-
-<H3>Invoking a build</H3>
-<p>A builder can be invoked explicitly in one of the following ways:
-</p>
-<ul>
-<li><b>IProject.build()</b> runs the build processing on the receiving project according to the build
-method's arguments.</li>
-<li><b>IWorkspace.build()</b> runs the build processing on all open projects in the workspace.</li>
-</ul>
-<P >
-In practice, the workbench user triggers a build by selecting corresponding commands in the resource 
-navigator menu.</P>
-<P >
-Incremental project builders are also invoked implicitly by the platform during an auto-build.
-If enabled, auto-builds run whenever the workspace is changed.</P>
-<H3>
-Defining an incremental project builder</H3>
-<P >
-The <a href="../reference/extension-points/org_eclipse_core_resources_builders.html"> <b> org.eclipse.core.resources.builders</b></a> extension point is used to contribute an
-incremental project builder to the platform. The following markup shows how the hypothetical plug-in
-<b> com.example.builders</b> could contribute an incremental project builder.</P>
-<pre>
-   &lt;extension
-      id=&quot;mybuilder&quot; name=&quot;My Sample Builder&quot; point=&quot;org.eclipse.core.resources.builders&quot;&gt;
-      &lt;builder
-         &lt;run 
-            <b>class=&quot;com.example.builders.BuilderExample&quot;</b>&gt;
-            &lt;parameter name=&quot;optimize&quot; value=&quot;true&quot; /&gt;
-            &lt;parameter name=&quot;comment&quot; value=&quot;Builder comment&quot; /&gt;
-         &lt;/run&gt;
-      &lt;/builder&gt;
-   &lt;/extension&gt;
-</pre>
-<P >
-The <b> class</b> identified in the extension point must extend the platform class 
-<b><a href="../reference/api/org/eclipse/core/resources/IncrementalProjectBuilder.html">IncrementalProjectBuilder</a></b>. </P>
-<pre>
-   public class BuilderExample extends IncrementalProjectBuilder {
-      IProject[] build(int kind, Map args, IProgressMonitor monitor)
-            throws CoreException {
-         // add your build logic here
-         return null;
-      }
-      protected void startupOnInitialize() {
-         // add builder init logic here
-      }
-      protected void clean(IProgressMonitor monitor) {
-         // add builder clean logic here
-      }
-   }
-</pre>
-<P >
-Build processing begins with the <b> build()</b> method, which includes information about the kind of build that 
-has been requested.  The build is one of the following values:</p>
-<ul>
-<li><b>FULL_BUILD</b> indicates that all resources in the project should be built.</li>
-<li><b>INCREMENTAL_BUILD</b> indicates that the build is incremental.</li>
-<li><b>AUTO_BUILD</b> indicates that an incremental build is being triggered automatically because a
-resource has changed and the autobuild feature is on.</li>
-</ul>
-<p>If an incremental build has been requested, a resource delta is provided to describe the changes in the 
-resources since the last build. The following snippet further refines the
-<b> build() </b> method.
-</P>
-<pre>   protected IProject[] build(int kind, Map args, IProgressMonitor monitor
-         throws CoreException {
-      if (kind == IncrementalProjectBuilder.FULL_BUILD) {
-         fullBuild(monitor);
-      } else {
-         IResourceDelta delta = getDelta(getProject());
-         if (delta == null) {
-            fullBuild(monitor);
-         } else {
-            incrementalBuild(delta, monitor);
-         }
-      }
-      return null;
-   }
-</pre>
-
-<P>It sometimes happens that when building project &quot;X,&quot; a builder
-needs information about changes in some other project &quot;Y.&quot;&nbsp; (For
-example, if a Java class in X implements an interface provided in Y.)&nbsp;
-While building X, a delta for Y is available by calling <b>getDelta(Y)</b>.&nbsp;
-To ensure that the platform can provide such deltas, X's builder must have
-declared the dependency between X and Y by returning an array containing Y from
-a previous <b>build()</b> call.&nbsp; If a builder has no dependencies, it can simply return null.
-See <b><a href="../reference/api/org/eclipse/core/resources/IncrementalProjectBuilder.html">IncrementalProjectBuilder</a></b>
-for further information.</P>
-
-<H4>
-Full build</H4>
-<P >
-The logic required to process a full build request is specific to the plug-in. It may involve visiting every 
-resource in the project or even examining other projects if there are dependencies between projects.
-The following snippet suggests how a full build might be implemented.</P>
-<pre>
-   protected void fullBuild(final IProgressMonitor monitor) throws CoreException {
-      try {
-         getProject().accept(new MyBuildVisitor());
-      } catch (CoreException e) { }
-   }
-</pre>
-<P >
-The build visitor would perform the build for the specific resource (and answer true to continue visiting all 
-child resources).</P>
-<pre>
-   class MyBuildVisitor implements IResourceVisitor {
-      public boolean visit(IResource res) {
-         //build the specified resource.
-         //return true to continue visiting children.
-         return true;
-      }
-   }
-</pre>
-<P >
-The visit process continues until the full resource tree has been traveled.</P>
-
-
-<H4>
-Incremental build</H4>
-<P >
-When performing an incremental build, the builder works with a resource change delta instead of a complete
-resource tree.</P>
-<pre>
-   protected void incrementalBuild(IResourceDelta delta, 
-         IProgressMonitor monitor) throws CoreException {
-      // the visitor does the work.
-      delta.accept(new MyBuildDeltaVisitor());
-   }
-</pre>
-<P >
-The visit process continues until the complete resource delta tree has been traveled. The specific nature of changes
-is similar to that described in
-<a HREF="resAdv_events.htm#resAdv_events_listener" CLASS="XRef">Implementing a resource change listener</a>.&nbsp;
-One important difference is that with incremental project builders, you are working with a resource delta based 
-on a particular project, not the entire workspace.</P>
-
-<H4>
-Cleaning before a build</H4>
-<P>
-The workbench allows users to <b>clean</b> a project or set of projects before initiating a build.  This feature
-allows the user to force a rebuild from scratch on only certain projects.  Builders should implement 
-this method to clean up any problem markers and derived resources in the project.
-</P>
-
-<H3>
-Associating an incremental project builder with a project</H3>
-<P >
-To make a builder available for a given project, it must be included in the build spec for the project. 
-A project's build spec is a list of commands to run, in sequence, when the project is built. Each command 
-names a single incremental project builder. </P>
-<P>
-<b>NOTE:</b> The builder name in a build command is the fully qualified id
-of the builder extension. The fully qualified id of an extension is created by combining
-the plug-in id with the simple extension id in the plugin.xml file. For example, a builder with simple extension
-id &quot;mybuilder&quot; in the plug-in &quot;com.example.builders&quot; would have the
-name &quot;com.example.builders.mybuilder&quot;</p>
-<P >
-The following snippet adds a new builder as the first builder in the existing list of builders.</P>
-<pre>
-   final String BUILDER_ID = "com.example.builders.mybuilder";
-   IProjectDescription desc = project.getDescription();
-   ICommand[] commands = desc.getBuildSpec();
-   boolean found = false;
-
-   for (int i = 0; i &lt; commands.length; ++i) {
-      if (commands[i].getBuilderName().equals(BUILDER_ID)) {
-         found = true;
-         break;
-      }
-   }
-   if (!found) { 
-      //add builder to project
-      ICommand command = desc.newCommand();
-      command.setBuilderName(BUILDER_ID);
-      ICommand[] newCommands = new ICommand[commands.length + 1];
-
-      // Add it before other builders.
-      System.arraycopy(commands, 0, newCommands, 1, commands.length);
-      newCommands[0] = command;
-      desc.setBuildSpec(newCommands);
-      project.setDescription(desc, null);
-   }
-</pre>
-<P >
-Configuring a project's builder is done just once, usually as the project is being created.</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_concurrency.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_concurrency.htm
deleted file mode 100644
index 3165d92..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_concurrency.htm
+++ /dev/null

@@ -1,81 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Concurrency and the workspace
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Concurrency and the workspace</h3>
-
-<p>We've already seen that workspace code must be aware of concurrency even if it is not using the 
-concurrency framework.  Batching of workspace changes and use of scheduling rules helps in sharing 
-the workspace with other plug-ins (and their threads) that are modifying the workspace.  Once your plug-in
-is using batching and rules (see <a href="resAdv_batching.htm">Batching resource changes</a>), it is
-easy to perform the same work using the platform concurrency mechanisms.
-</p>
-
-<h4>Workspace jobs</h4>
-<p>A <b><a href="../reference/api/org/eclipse/core/runtime/jobs/Job.html">Job</a></b> is a basic unit of 
-asynchronous work running concurrently with other jobs.  The resources plug-in defines 
-<b><a href="../reference/api/org/eclipse/core/resources/WorkspaceJob.html">WorkspaceJob</a></b>
-as a convenient mechanism for defining asynchronous resource modifications.  Code that would
-normally be batched in an <b><a href="../reference/api/org/eclipse/core/resources/IWorkspaceRunnable.html">IWorkspaceRunnable</a></b> 
-is instead put in the <b>runInWorkspace</b> method of a workspace job subtype.  Instead of running the code using 
-<b><a href="../reference/api/org/eclipse/core/resources/IWorkspace.html">IWorkspace</a></b> protocol,
-the job is scheduled just like any other job.  The appropriate scheduling rules must be added on the job before 
-it is scheduled.
-</p>
-<p>Let's look at an example workspace runnable and what we should do to make it a job:
-</p>
-<pre>IWorkspaceRunnable myRunnable = 
-	new IWorkspaceRunnable() {
-		public void run(IProgressMonitor monitor) throws CoreException {
-			//do the actual work in here
-			doSomeWork();
-			...
-		}
-}
-</pre>
-<p>The work is moved to the appropriate method of our
-<b><a href="../reference/api/org/eclipse/core/resources/WorkspaceJob.html">WorkspaceJob</a></b>
-subtype.
-</p>
-<pre>class MyWorkspaceJob extends WorkspaceJob {
-	public MyWorkspaceJob() {
-		super("My Workspace Job");
-	}
-	public IStatus runInWorkspace(IProgressMonitor monitor) {
-		//do the actual work in here
-		doSomeWork();
-		return Status.OK_STATUS;
-	}
-}
-</pre>
-<p>Our runnable had to be invoked specifically:
-</p>
-<pre>IWorkspace workspace = ResourcesPlugin.getWorkspace();
-workspace.run(myRunnable, myProject, IWorkspace.AVOID_UPDATE, null);
-</pre>
-<p>Our job is scheduled like any other job.  The platform job manager will run it according to its
-priority, other jobs in the queue, and the scheduling rules.  Note that we must attach the 
-scheduling rule to the job in order to prevent simultaneous modification of <tt>myProject</tt>.
-</p>
-<pre>MyWorkspaceJob job = new MyWorkspaceJob();
-<b>job.setRule(myProject);</b>
-job.schedule();
-</pre>
-<p>Now that the operation has been structured as a job, all of the scheduling mechanisms (priority, delay, rescheduling) can
-be used.  Resource change events will be batched until the job is finished running.
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_derived.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_derived.htm
deleted file mode 100644
index 5327691..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_derived.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Derived resources
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Derived resources</h2>
-
-<p>Many resources get created in the course of translating, compiling, copying,
-or otherwise processing files that the user creates and edits.&nbsp; <b>Derived
-resources</b> are resources that are not original data, and can be recreated
-from their source files.&nbsp; It is common for derived files to be excluded
-from certain kinds of processing.&nbsp;&nbsp;</p>
-<p>For example, derived resources are typically not kept in a team repository,
-since they clutter the repository, change regularly, and can be recreated from
-their source files.&nbsp; It is not practical for team providers to make
-decisions about which files are derived.&nbsp; The resource API provides a
-common mechanism for plug-ins to indicate the resources they create that are
-derived.</p>
-<p>Plug-ins may use <a href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a>.<b>setDerived(boolean)
-</b>to indicate that a resource is derived from other resources. Newly created resources are not
-derived by default, so this
-method must be used to explicitly mark the resource as derived.&nbsp; A
-common use is to mark a subfolder of the project as derived when an
-&quot;output&quot; folder (such as the &quot;bin&quot; folder in Java projects)
-is created by the plug-in.</p>
-<p>Other plug-ins, usually team providers, can use <a href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a>.<b>isDerived
-</b>to determine whether a particular resource should be managed by the
-repository.&nbsp; Attempts to mark projects or the workspace root as derived will be
-ignored.</p>
-<blockquote>
-<p><i>Note:&nbsp; The concept of derived resources is provided for other
-(non-team) plug-ins to indicate which resources are inappropriate for repository
-management.&nbsp; Special files created by team implementations to manage their
-data should not be marked as derived resources.&nbsp; See <a href="team_resources_private.htm">Team
-private resources</a> for a technique for marking team-related implementation
-resources hidden.</i></p>
-</blockquote>
-<p>&nbsp;</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_events.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_events.htm
deleted file mode 100644
index 2739daa..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_events.htm
+++ /dev/null

@@ -1,291 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Tracking resource changes
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-Tracking resource changes</H3>
-<p>We've just seen how to batch resource changes in a runnable (<a href="resAdv_batching.htm">Batching resource changes</a>).
-Let's look at the other side of the coin.  What if you want to keep track of all of the changes to the workspace that happen
-while your plug-in is running?  You can register an
-<b><a href="../reference/api/org/eclipse/core/resources/IResourceChangeListener.html"> IResourceChangeListener</a></b> 
-with the workspace. Your listener will be notified of the changes via an
-<b><a href="../reference/api/org/eclipse/core/resources/IResourceChangeEvent.html"> IResourceChangeEvent</a></b> 
-object, which describes the changes.
-</p>
-<h4>Registering a listener</h4>
-
-<p>First, you must register a resource change listener with the workspace.
-</p>
-<pre>   IResourceChangeListener listener = new MyResourceChangeReporter();
-   ResourcesPlugin.getWorkspace().addResourceChangeListener(
-      listener, IResourceChangeEvent.POST_CHANGE);
-</pre>
-
-<p>Your listener will be notified after modifications to the workspace resources
-have been made. Resource API methods that modify resources trigger these events as part of their documented 
-behavior. The method comment for a resource API method explicitly states whether or not it triggers a resource 
-change event. For example, the following is included in the <b> IFile.setContents()</b> comment:
-</p>
-<pre>   This method changes resources; these changes will be reported in a subsequent
-   resource change event, including an indication that this file's content have
-   been changed.
-</pre>
-
-<p>Methods that create, delete, or change a resource typically trigger these events. Methods that read, but 
-do not write, resources typically do not trigger these events.
-</p>
-<h4>Resource change events</h4>
-
-<p>The resource change event describes the specifics of the change (or set of changes) that have occurred in the 
-workspace. The event contains a <b> resource delta</b> that describes the <i> net</i> effect of the changes. 
-For example, if you add a resource and later delete it during one batch of changes, the resource will not appear 
-in the delta.
-</p>
-<p>The resource delta is structured as a tree rooted at the workspace root. The resource delta tree describes 
-these types of changes:
-</p>
-<ul>
-  <li>
-Resources that have been created, deleted, or changed. If you have deleted (or added) a folder, 
-the resource delta will include the folder and all files contained in the folder.</li>
-  <li>
-Resources that have been moved or renamed using the <b> IResource.move()</b> API.</li>
-  <li>
-Markers that have been added, removed, or changed. Marker modification is considered to be a 
-workspace modification operation.</li>
-  <li>
-Files that have been modified. Changed files are identified in the resource delta, but you do not 
-have access to the previous content of the file in the resource delta.</li>
-</ul>
-<p>To traverse a resource delta tree, you may implement the 
-<b><a href="../reference/api/org/eclipse/core/resources/IResourceDeltaVisitor.html"> IResourceDeltaVisitor</a></b> 
-interface or traverse the tree explicitly using <b>IResource.getAffectedChildren</b>. Resource delta visitors 
-implement a <b> visit</b> method that is called by the resource delta as it enumerates each change in the tree.
-</p>
-<blockquote><i>
-Note:&nbsp; Changes made to resource session properties or resource persistent properties are not identified 
-in the resource delta.</i></blockquote>
-<p>Resource change events are sent whenever a change (or batched set of changes) is made to the workspace. In 
-addition, resource change events are sent for certain specific workspace operations. The table below summarizes 
-the types of resource change events and when they are reported.
-</p>
-<TABLE BORDER="1">
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="CellHeading">
-Event type</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="CellHeading">
-Description</P>
-</TH>
-</TR>
-<TR>
-<TD>
-<P CLASS="CellBody">
-<b>
-PRE_CLOSE</b></P>
-</TD>
-<TD>
-<P CLASS="CellBody">
-Notifies listeners that a project is about to be closed. This event can be used to extract and save necessary information from the in-memory representation
-(e.g., session properties) of a project before it is closed. (When a project is closed, the in-memory representation is disposed). The workspace is locked (no resources can be updated) during this event.
-The event contains the project that is being closed.</P>
-</TD>
-</TR>
-<TR>
-<TD>
-<P CLASS="CellBody">
-<b>
-PRE_DELETE</b></P>
-</TD>
-<TD>
-<P CLASS="CellBody">
-Notifies listeners that a project is about to deleted. This event can be used to
-perform clean-up operations, such as removing any saved state that is related to
-the project from your plug-in's directory.&nbsp; The workspace is locked (no resources can be updated) during this event. The event contains the project that is being deleted.</P>
-</TD>
-</TR>
-<TR>
-<TD>
-<P CLASS="CellBody"><b>PRE_AUTOBUILD</b></P>
-</TD>
-<TD>
-<P CLASS="CellBody">
-Notifies listeners before any auto-building occurs.&nbsp; This event is
-broadcast when the platform detects an auto-build needs to occur, regardless of
-whether auto-building is actually enabled.&nbsp; The workspace is <b> not</b> locked during this event (resources can be updated). 
-The event contains a resource delta describing the changes that have occurred since the last
-<b>POST_CHANGE</b> event was reported.</P>
-</TD>
-</TR>
-<tr>
-<TD>
-<P CLASS="CellBody">
-<b>
-POST_AUTOBUILD</b></P>
-</TD>
-<TD>
-<P CLASS="CellBody">
-Notifies listeners after any auto-building has occurred. This event is broadcast
-after the platform would have performed an auto-build, regardless of whether
-auto-building is actually enabled.&nbsp; The workspace is <b> not</b> locked during this event (resources can be updated). The event contains a resource delta describing the changes that have occurred since the last
-<b>POST_CHANGE</b> event was reported.</P>
-</TD>
-</tr>
-<tr>
-<TD>
-<P CLASS="CellBody">
-<b>
-POST_CHANGE</b></P>
-</TD>
-<TD>
-<P CLASS="CellBody">
-Describes a set of changes that have occurred to the workspace since the last <b> POST_CHANGE</b> event was reported. Triggered after a resource change API is used individually or in a batched set of workspace changes. Also triggered after any
-<b>PRE_AUTOBUILD</b> or <b>POST_AUTOBUILD</b>
-notification is complete. The event contains a resource delta describing the net changes since the last
-<b> POST_CHANGE</b> event.&nbsp; The workspace is
-locked (no resources can be updated) during this event.</P>
-</TD>
-</tr>
-</TABLE>
-
-<h4><a name="resAdv_events_listener">Implementing a resource change listener</a></h4>
-
-<p>The following example implements a console-based resource change listener. A resource change listener 
-is registered for specific types of events and information about these events is printed to the console:
-</p>
-<pre>   IResourceChangeListener listener = new MyResourceChangeReporter();
-   ResourcesPlugin.getWorkspace().addResourceChangeListener(listener,
-      IResourceChangeEvent.PRE_CLOSE
-      | IResourceChangeEvent.PRE_DELETE
-      | IResourceChangeEvent.PRE_AUTO_BUILD
-      | IResourceChangeEvent.POST_AUTO_BUILD
-      | IResourceChangeEvent.POST_CHANGE);
-</pre>
-<p>The listener checks for each event type and reports information about the resource that was changed and the kinds of changes that occurred.&nbsp;
-Although this example is designed to show a general listener that handles all
-the types of resource events, a typical listener would register for just one
-type of event.
-</p>
-<p>The implementation for <b> POST_CHANGE </b> uses another class that can be used to
-visit the changes in the resource delta.
-</p>
-<pre>   import org.eclipse.resources.*;
-   import org.eclipse.runtime.*;
-
-   public class MyResourceChangeReporter implements IResourceChangeListener {
-      public void resourceChanged(IResourceChangeEvent event) {
-         IResource res = event.getResource();
-         switch (event.getType()) {
-            case IResourceChangeEvent.PRE_CLOSE:
-               System.out.print(&quot;Project &quot;);
-               System.out.print(res.getFullPath());
-               System.out.println(&quot; is about to close.&quot;);
-               break;
-            case IResourceChangeEvent.PRE_DELETE:
-               System.out.print(&quot;Project &quot;);
-               System.out.print(res.getFullPath());
-               System.out.println(&quot; is about to be deleted.&quot;);
-               break;
-            case IResourceChangeEvent.POST_CHANGE:
-               System.out.println(&quot;Resources have changed.&quot;);
-               event.getDelta().accept(new DeltaPrinter());
-               break;
-            case IResourceChangeEvent.PRE_AUTO_BUILD:
-               System.out.println(&quot;Auto build about to run.&quot;);
-               event.getDelta().accept(new DeltaPrinter());
-               break;
-            case IResourceChangeEvent.POST_AUTO_BUILD:
-               System.out.println(&quot;Auto build complete.&quot;);
-               event.getDelta().accept(new DeltaPrinter());
-               break;
-         }
-      }
-   }
-</pre>
-<p>The <b> DeltaPrinter</b> class implements the <b><a href="../reference/api/org/eclipse/core/resources/IResourceDeltaVisitor.html">IResourceDeltaVisitor</a></b> interface to interrogate the resource delta. The
-<b> visit()</b> method is called for each resource change in the resource delta. The visitor uses a return value to indicate whether
-deltas for child resources should be visited.
-</p>
-<pre>   class DeltaPrinter implements IResourceDeltaVisitor {
-      public boolean visit(IResourceDelta delta) {
-         IResource res = delta.getResource();
-         switch (delta.getKind()) {
-            case IResourceDelta.ADDED:
-               System.out.print(&quot;Resource &quot;);
-               System.out.print(res.getFullPath());
-               System.out.println(&quot; was added.&quot;);
-               break;
-            case IResourceDelta.REMOVED:
-               System.out.print(&quot;Resource &quot;);
-               System.out.print(res.getFullPath());
-               System.out.println(&quot; was removed.&quot;);
-               break;
-            case IResourceDelta.CHANGED:
-               System.out.print(&quot;Resource &quot;);
-               System.out.print(res.getFullPath());
-               System.out.println(&quot; has changed.&quot;);
-               break;
-         }
-         return true; // visit the children
-      }
-   }
-</pre>
-<p>Further information can be obtained from the supplied resource delta. The following snippet shows how
-the <b>IResourceDelta.CHANGED</b> case could be implemented to further describe the resource changes.
-</p>
-<pre>   ...
-   case IResourceDelta.CHANGED:
-      System.out.print(&quot;Resource &quot;);
-      System.out.print(delta.getFullPath());
-      System.out.println(&quot; has changed.&quot;);
-      int flags = delta.getFlags();
-      if ((flags &amp; IResourceDelta.CONTENT) != 0) {
-            System.out.println(&quot;--&gt; Content Change&quot;);
-      }
-      if ((flags &amp; IResourceDelta.REPLACED) != 0) {
-            System.out.println(&quot;--&gt; Content Replaced&quot;);
-      }
-      if ((flags &amp; IResourceDelta.MARKERS) != 0) {
-            System.out.println(&quot;--&gt; Marker Change&quot;);
-            IMarkerDelta[] markers = delta.getMarkerDeltas();
-            // if interested in markers, check these deltas
-      }
-      break;
-   ...
-</pre>
-<p>For a complete description of resource deltas, visitors, and marker deltas, consult the
-API specification for <b><a href="../reference/api/org/eclipse/core/resources/IResourceDelta.html">IResourceDelta</a></b>,
-<b><a href="../reference/api/org/eclipse/core/resources/IResourceDeltaVisitor.html">IResourceDeltaVisitor</a></b>, and
-<b><a href="../reference/api/org/eclipse/core/resources/IMarkerDelta.html">IMarkerDelta</a></b>.</P>
-<blockquote><i>
-Note:&nbsp; Resource change listeners are useful for tracking changes that occur to resources while 
-your plug-in is activated. If your plug-in registers a resource change listener during its startup code, 
-it's possible that many resource change events have been triggered before the activation of your plug-in. 
-The resource delta contained in the first resource change event received by your plug-in will not contain 
-all of the changes made since your plug-in was last activated. If you need to track changes made between 
-activations of your plug-in, you should use the support provided for workspace saving. This is described in
-<a HREF="resAdv_saving.htm" CLASS="XRef"> Workspace save participation</a>.</i></blockquote>
-<blockquote><i>
-Note:&nbsp; Some resource change events are triggered during processing that occurs in a background thread.  Resource
-change listeners should be thread-safe.  See <a href="swt_threading.htm">Threading issues</a> for a discussion about
-thread safety with the UI.
-</i></blockquote>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_hooks.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_hooks.htm
deleted file mode 100644
index 73637eb..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_hooks.htm
+++ /dev/null

@@ -1,117 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Resource modification hooks
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<body>
-<H2>
-Resource modification hooks</H2>
-<P >So far, we've assumed that resource API is being used to modify resources
-that are located in the user's file system.&nbsp; This is indeed the fundamental
-structure of the workspace, but it's also possible that a plug-in adds
-capabilities for manipulation of resources that are managed somewhere
-else.&nbsp; For example, the platform <a href="team.htm">Team support</a>
-plug-ins add the ability to work with resources that are under the management of
-a versioning repository.</P>
-
-<P > The resource API includes capabilities that have been added specifically 
-  to enable the team support plug-ins and plug-ins that implement repository providers 
-  using the team support.&nbsp; The following discussion covers the generic mechanism 
-  for registering resource hooks.&nbsp; See <a href="team_provider_repository.htm#hooks">Implementing 
-  a repository provider</a> for a discussion of how team uses these hooks.&nbsp;&nbsp;</P>
-
-<h3 >
-Resource move/delete hooks</h3>
-
-<P >
-This hook allows the team plug-in and its providers to control
-    how resource moves and deletes are implemented.&nbsp; The hook includes the ability to prevent
-these operations from
-    happening.&nbsp; Implementors can provide alternate implementations for
-    moving or deleting files, folders, and projects.&nbsp;</P>
-
-<P >
-The team plug-in uses the <a href="../reference/extension-points/org_eclipse_core_resources_moveDeleteHook.html"><b>org.eclipse.core.resources.moveDeleteHook</b></a>
-extension point to register its hook:</P>
-
-<pre >&lt;extension point=&quot;org.eclipse.core.resources.moveDeleteHook&quot; id=&quot;MoveDeleteHook&quot;&gt;
-	&lt;moveDeleteHook class=&quot;org.eclipse.team.internal.core.MoveDeleteManager&quot;/&gt;
-&lt;/extension&gt;
-</pre>
-
-<P >
-The supplied class must implement <a href="../reference/api/org/eclipse/core/resources/team/IMoveDeleteHook.html"><b>IMoveDeleteHook</b></a>,
-which is called by the platform whenever a resource is moved or deleted.&nbsp;
-The team plug-in installs a move delete hook manager that can determine which
-team provider is managing a resource and invoke its specific hook.</P>
-
-<h3 >
-File modification validators</h3>
-
-<p>It's also possible that team repository providers will need to prevent or
-intervene in the editing or saving of a file.&nbsp; The team plug-in
-accomplishes this by using the extension point <a href="../reference/extension-points/org_eclipse_core_resources_moveDeleteHook.html"><b>org.eclipse.core.resources.fileModificationValidator</b></a>
-to register a validator that is called whenever a resource is to be modified.</p>
-
-<pre >&lt;extension point=&quot;org.eclipse.core.resources.fileModificationValidator&quot; id=&quot;FileValidator&quot;&gt;
-	&lt;fileModificationValidator class=&quot;org.eclipse.team.internal.core.FileModificationValidatorManager&quot;/&gt;
-&lt;/extension&gt;</pre>
-
-<P >The supplied class must implement <a href="../reference/api/org/eclipse/core/resources/IFileModificationValidator.html"><b>IFileModificationValidator</b></a>,
-which is called by the platform whenever a resource is saved or
-opened.&nbsp;&nbsp; The team plug-in installs a file modification manager that
-can determine which team provider is managing a resource and invoke its specific
-validator.</P>
-
-<h3 >General team hook</h3>
-<p>
-Repository providers sometimes need to hook into additional workspace operations
-in order to impose extra restrictions or customize workspace behavior.  The
-<a href="../reference/extension-points/org_eclipse_core_resources_teamHook.html"><b>org.eclipse.core.resources.teamHook</b></a>
-extension point provides some other special functions for team providers.  In particular,
-this hook allows a team provider to decide whether linked folders and files should
-be allowed for a given project.  Some repository systems have strict rules about the
-physical layout of projects on disk, and are not able to handle resources linked to
-arbitrary locations.</p>
-<p>
-The team hook also allows a repository provider to supply a 
-<a href="runtime_jobs_rules.htm">scheduling rule</a>
-factory that will be used by all workspace operations.  Each time an API method is called
-that modifies the workspace in some way, a scheduling rule is obtained by the workspace.
-This scheduling rule prevents other threads from modifying those resources during
-the invocation of the API method.  If a repository provider is performing additional
-work inside a file modification validator or move/delete hook, the provider must
-also tell the workspace what additional scheduling rules it will need. See
-the section on <a href="resAdv_batching.htm">resource batching</a> for more
-details on how the workspace uses scheduling rules.
-</p>
-<P >The supplied class for the team hook must implement <a href="../reference/api/org/eclipse/core/resources/TeamHook.html"><b>TeamHook</b></a>.
-The team plug-in installs the single team hook that
-can determine which team provider is managing a resource and invoke its specific
-hook.</P>
-
-<blockquote>
-
-  <P ><i>Note:&nbsp; All three of these team hooks are designed specifically 
-    for use by the team core plug-in.&nbsp; They are not intended for general use.&nbsp; 
-    Team providers should not install hooks using these extension points, but 
-    instead implement their hooks in their Repository Provider class.&nbsp;&nbsp; 
-    See <a href="team_provider_repository.htm#hooks">Team resource modification 
-    hooks</a> for more information about using these hooks.</i></P>
-
-</blockquote>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_markers.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_markers.htm
deleted file mode 100644
index 264d4f5..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_markers.htm
+++ /dev/null

@@ -1,274 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Resource markers
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<body>
-<H2>
-Resource markers</H2>
-<P >
-We know that plug-ins can define specialized file extensions and contribute editors that provide
-specialized editing features for these file types.&nbsp; During the course of editing (or building) a resource, a plug-in may need to tag resources to communicate problems or other information to the user. The resource marker mechanism is used to manage this kind of information.</P>
-<P >
-A <b> marker</b> is like a yellow sticky note stuck to a resource.  On the marker you can record information about a
-problem (e.g., location, severity) or a task to be done.&nbsp; Or you can simply
-record a location for a marker as a bookmark.&nbsp;</P>
-<P >
-  Users can quickly jump to the marked location within a resource. The workbench UI supports presentation of
-bookmarks, breakpoints, tasks, and problems along the side of the editor.&nbsp;
-These markers can also be shown as items in views, such as the tasks or bookmarks view.</P>
-<P >
-The platform resources API defines methods for creating markers, setting marker values, and extending the platform with new marker types. While the platform manages markers, it is the plug-ins that control their creation, removal and attribute values. </P>
-<P >
-Markers are intended to be small, lightweight objects.  There could be hundreds, even thousands of markers in a single
-project.&nbsp; For example, the Java compiler uses a marker to flag each problem
-it finds in source code.</P>
-<P >
-The platform will throw away markers attached to resources that are deleted, but plug-ins are responsible for removing
-their stale markers when they no longer apply to a resource that still exists.</P>
-
-<H3>
-Marker operations</H3>
-<P >
-Manipulating a marker is similar to manipulating a resource.&nbsp; Markers are <b>handle</b>
-objects.&nbsp; You can obtain a marker handle from a resource, but you don't
-know if it actually exists until you use <b>exists()</b>
-protocol or otherwise try to manipulate it.&nbsp; Once you've established that a
-marker exists, you can query named attributes that may have been assigned to it.</P>
-
-<P >
-Markers are owned and managed by the platform, which takes care of making
-markers persistent and notifying listeners as markers are added, deleted, or
-changed.&nbsp; Plug-ins are responsible for creating any necessary markers, changing their attributes, and removing them when they are
-no longer needed.</P>
-
-<H4>
-Marker creation</H4>
-<P >
-Markers are not directly created using a constructor. They are created using a factory method
-(<b>IResource.createMarker()</b>) on the associated resource. </P>
-<pre>
-   IMarker marker = file.createMarker(IMarker.TASK);
-</pre>
-<P >
-To create a marker that has global scope (not associated with any specific resource), you can use
-the workspace root
-(<b>IWorkspace.getRoot()</b>) as the resource. </P>
-
-
-<H4>
-Marker deletion</H4>
-<P >
-The code for deleting a marker is straightforward.</P>
-<pre>
-   try {
-      marker.delete();
-   } catch (CoreException e) {
-      // Something went wrong
-   }
-</pre>
-<P >
-When a marker is deleted, its marker object (handle) becomes &quot;stale.&quot; Plug-ins should use the
-<b> IMarker.exists()</b> protocol to make sure a marker object is still valid.</P>
-<P >
-Markers can be deleted in batch by asking a resource to delete its markers. This method is useful when removing
-many markers at once or if individual marker references or ids are not available.</P>
-<pre>
-   int depth = IResource.DEPTH_INFINITE;
-   try {
-      resource.deleteMarkers(IMarker.PROBLEM, true, depth);
-   } catch (CoreException e) {
-      // something went wrong
-   }
-</pre>
-<P >
-When deleting a group of markers, you specify a marker <b> type</b> to delete, such as <b> IMarker.PROBLEM</b>, or
-<b> null</b> to delete all markers. The second argument
-indicates whether you want to delete subtype markers.&nbsp; (We'll look a
-subtypes in a moment when we define new marker types.)&nbsp; The <b> depth</b> argument controls the depth of deletion.&nbsp; </P>
-
-
-<P >
-You can also delete markers using <b>IWorkspace.deleteMarkers(IMarker
-[])</b>. </P>
-
-
-<H4>
-Marker attributes</H4>
-<P >
-Given a marker, you can ask for its associated resource, its id (unique relative to that resource), and its type. You can also access additional information
-via generic attributes. </P>
-<P >
-Each type of marker has a specific set of attributes that are defined by the
-creator of the marker type using naming conventions.&nbsp; The
-<b><a href="../reference/api/org/eclipse/core/resources/IMarker.html"> IMarker</a></b> interface defines a set of constants containing
-the standard attribute names (and some of the expected values) for the platform marker types.  The following method manipulates attributes using the platform constants.</P>
-<pre>
-   IMarker marker = file.createMarker(IMarker.TASK);
-   if (marker.exists()) {
-      try {
-         marker.setAttribute(IMarker.MESSAGE, &quot;A sample marker message&quot;);
-         marker.setAttribute(IMarker.PRIORITY, IMarker.PRIORITY_HIGH);
-      } catch (CoreException e) {
-         // You need to handle the case where the marker no longer exists      }
-   }</pre>
-
-
-<P>
-Attributes are maintained generically as name/value pairs, where the names are strings and a value can be any one of the supported value types
-(boolean, integer, string). The limitation on value types allows the platform to persist the markers quickly and simply.</P>
-
-
-<H4>
-Querying markers</H4>
-<P >
-Resources can be queried for their markers and the markers of their children. For example, querying the workspace root with infinite depth considers all of the markers in the workspace.</P>
-<pre>
-   IMarker[] problems = null;
-   int depth = IResource.DEPTH_INFINITE;
-   try {
-      problems = resource.findMarkers(IMarker.PROBLEM, true, depth);
-   } catch (CoreException e) {
-      // something went wrong
-   }
-</pre>
-<P >
-The result returned by <b>findMarkers</b>  depends on
-the arguments passed.&nbsp; In the snippet above, we are looking for all markers
-of type <b>PROBLEM</b> that appear on the resource and
-all of its direct and indirect descendants.&nbsp; </P>
-
-
-<P >
-If you pass
-<b> null</b>  as the marker type, you will get all the
-marker types associated with the resource. The second argument specifies whether
-you want to look at the resource's children.&nbsp; The
-<b> depth</b> argument controls the depth of the search
-when you are looking at the resource's children. The depth can be <b>DEPTH_ZERO</b>
-(just the given resource), <b>DEPTH_ONE</b> (the resource and all
-of its direct children) or
-<b>DEPTH_INFINITE</b> (the resource and all of its direct and indirect
-descendants). </P>
-
-
-<H4>
-Marker persistence</H4>
-<P >
-The platform standard markers (task, problem, and bookmark) are <b>persistent</b>. This means that their state will be saved across workbench shutdown and startup.
-However, markers of a persistent type may be selectively made transient by setting the reserved attribute <strong>transient</strong> to true.
-</P>
-<P >
-New marker types declared by plug-ins are not persistent unless they are declared as such.</P>
-
-
-
-<H3>
-<a name="resAdv_markers_extending">
-Extending the platform with new marker types</a></H3>
-<P >
-Plug-ins can declare their own marker types using the <b><a href="../reference/extension-points/org_eclipse_core_resources_markers.html"> org.eclipse.core.resources.markers</a></b> 
-extension point. The standard marker types for problems, tasks and bookmarks are declared by the platform in the resources plug-in's markup.</P>
-<pre>
-   &lt;extension
-      id=&quot;problemmarker&quot; 
-      point=&quot;org.eclipse.core.resources.markers&quot; 
-      name=&quot;%problemName&quot;&gt;
-      &lt;super type=&quot;org.eclipse.core.resources.marker&quot;/&gt;
-      &lt;persistent value=&quot;true&quot;/&gt;
-      &lt;attribute name=&quot;severity&quot;/&gt;
-      &lt;attribute name=&quot;message&quot;/&gt;
-      &lt;attribute name=&quot;location&quot;/&gt;
-   &lt;/extension&gt;
-   &lt;extension
-      id=&quot;taskmarker&quot; 
-      point=&quot;org.eclipse.core.resources.markers&quot; 
-      name=&quot;%taskName&quot;&gt;
-      &lt;super type=&quot;org.eclipse.core.resources.marker&quot;/&gt;
-      &lt;persistent value=&quot;true&quot;/&gt;
-      &lt;attribute name=&quot;priority&quot;/&gt;
-      &lt;attribute name=&quot;message&quot;/&gt;
-      &lt;attribute name=&quot;done&quot;/&gt;
-      &lt;attribute name=&quot;userEditable&quot;/&gt;      
-   &lt;/extension&gt;
-   &lt;extension
-      id=&quot;bookmark&quot; 
-      point=&quot;org.eclipse.core.resources.markers&quot; 
-      name=&quot;%bookmarkName&quot;&gt;
-      &lt;super type=&quot;org.eclipse.core.resources.marker&quot;/&gt;
-      &lt;persistent value=&quot;true&quot;/&gt;
-      &lt;attribute name=&quot;message&quot;/&gt;
-      &lt;attribute name=&quot;location&quot;/&gt;
-   &lt;/extension&gt;
-</pre>
-<P >
-New marker types are derived from existing ones using multiple inheritance. New marker types inherit all of the attributes from their
-super types and add any new attributes defined as part of the declaration. They also transitively inherit
-attributes from the super types of their super types.  The following markup defines a new kind of marker in a hypothetical
-<b>com.example.markers</b> plug-in.</P>
-<pre>
-   &lt;extension
-      id=&quot;mymarker&quot;
-      point=&quot;org.eclipse.core.resources.markers&quot; /&gt;
-   &lt;extension
-      id=&quot;myproblem&quot;
-      point=&quot;org.eclipse.core.resources.markers&quot;&gt;
-      &lt;super type=&quot;org.eclipse.core.resources.problemmarker&quot;/&gt;
-      &lt;super type=&quot;com.example.markers.mymarker&quot;/&gt;
-      &lt;attribute name=&quot;myAttribute&quot; /&gt;
-      &lt;persistent value=&quot;true&quot; /&gt;
-   &lt;/extension&gt;
-</pre>
-<P >
-Note that the type <b> org.eclipse.core.resources.problemmarker</b> is actually one of the pre-defined types (aka
-<b>IMarker.PROBLEM</b>).&nbsp; </P>
-<P >
-  The only aspect of a marker
-super type that is not inherited is its <b> persistence</b> flag.&nbsp;
-  The default value for persistence is false, so any marker type that should be
-  persistent must specify <b>&lt;persistent
-  value=&quot;true&quot;/&gt;</b>. </P>
-<P >
-After declaring the new marker type in your plug-in manifest file, you can create instances of
-<b>com.example.markers.myproblem</b> marker type and freely set or get the
-<b> myAttribute</b> attribute.</P>
-<P >
-Declaring new attributes allows you to associate data with markers that you plan to use elsewhere (in your
-views and editors).  Markers of a particular type do not have to have values for all of the declared attributes.  The attribute declarations are more for solving naming convention problems (so everyone uses &quot;message&quot; to talk about a marker's description) than
-for constraining content. </P>
-<pre>
-   public IMarker createMyMarker(IResource resource) {
-      try {
-         IMarker marker = resource.createMarker(&quot;com.example.markers.myproblem&quot;);
-         marker.setAttribute(&quot;myAttribute&quot;, &quot;MYVALUE&quot;);
-         return marker;
-      } catch (CoreException e) {
-         // You need to handle the cases where attribute value is rejected
-      }
-   }
-</pre>
-<P >
-You can query your own marker types in the same way you query the platform marker
-types.&nbsp; The method below finds all <b>mymarkers</b> associated with the given target resource and all
-of its descendents.  Note that this will also find all
-<b>myproblems</b> since true is passed for the <b>includeSubtypes</b>
-argument.</P>
-<pre>
-   public IMarker[] findMyMarkers(IResource target) {
-      String type = &quot;com.example.markers.mymarker&quot;;
-      IMarker[] markers = target.findMarkers(type, true, IResource.DEPTH_INFINITE);
-   }
-</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_modify.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_modify.htm
deleted file mode 100644
index 71f4023..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_modify.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Modifying the workspace
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Modifying the workspace</h2>
-<p>In the course of performing its function, your plug-in may need to make changes to resources in the workspace.
-The workspace is an important data model for many plug-ins in the system, many of which rely on keeping up with
-the current state of the workspace.  Plug-ins may even be concurrently updating the workspace.  It's important
-for your plug-in to act as a responsible workspace citizen when making changes to resources.  What makes a plug-in 
-a good workspace citizen?
-</p>
-
-<ul>
-<li><b>Batching</b> of changes where possible to avoid flooding the system with unnecessary events or triggering
-unnecessary processing on an interim state.</li>
-<li><b>Listening</b> to resource change events and updating models as the workspace changes.</li>
-<li><b>Fine-grained locking</b> of the workspace when making modifications instead of locking the entire workspace.</li>
-</ul>
-
-<p>The next few sections look at these concepts in more detail. 
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_natures.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_natures.htm
deleted file mode 100644
index a9fd216..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_natures.htm
+++ /dev/null

@@ -1,176 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Project natures
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Project natures</H2>
-<P >
-Project natures allow a plug-in to tag a project as a specific kind of project. For example, the Java development tools (JDT) use a &quot;Java nature&quot; to add
-Java-specific behavior to projects.&nbsp; Project natures are defined by
-plug-ins, and are typically added or removed per-project when the user performs
-some action defined by the plug-in.</P>
-<P >A project can have more than one nature.&nbsp; However, when you define a
-project nature, you can define special constraints for the nature:</P>
-<ul>
-  <li><b>one-of-nature</b> - specifies that the nature is one of a named
-    set.&nbsp; Natures in a set are mutually exclusive; that is, only one nature
-    belonging to the set can exist for a project.</li>
-  <li><b>requires-nature</b> - specifies that the nature depends on another
-    nature and can only be added to a project that already has the required
-    nature.</li>
-</ul>
-<P >
-To implement your own nature, you need to define an extension and supply a class
-which implements <b><a href="../reference/api/org/eclipse/core/resources/IProjectNature.html">IProjectNature</a></b>.</P>
-
-<H3>
-Defining a nature</H3>
-<P >
-The <a href="../reference/extension-points/org_eclipse_core_resources_natures.html"> <b> org.eclipse.core.resources.natures</b></a> extension point is used to add a project nature definition. The following markup adds a nature for the hypothetical
-<b> com.example.natures</b> plug-in.</P>
-<pre>
-   &lt;extension
-      point=&quot;org.eclipse.core.resources.natures&quot;
-      id=&quot;mynature&quot;
-      name=&quot;My Nature&quot;&gt;
-      &lt;runtime&gt;
-         &lt;run class=&quot;com.example.natures.MyNature&quot;&gt;
-         &lt;/run&gt;
-      &lt;/runtime&gt;
-   &lt;/extension&gt;
-</pre>
-<P >
-The class identified in the extension must implement the platform interface
-<b><a href="../reference/api/org/eclipse/core/resources/IProjectNature.html">IProjectNature</a></b>. This class implements plug-in specific behavior for associating nature-specific information with a project when
-the nature is configured.</P>
-<pre>
-   public class MyNature implements IProjectNature {
-
-      private IProject project;
-
-      public void configure() throws CoreException {
-         // Add nature-specific information
-         // for the project, such as adding a builder
-         // to a project's build spec.
-      }
-      public void deconfigure() throws CoreException {
-         // Remove the nature-specific information here.
-      }
-      public IProject getProject() {
-         return project;
-      }
-      public void setProject(IProject value) {
-         project = value;
-      }
-   }
-</pre>
-<P >
-The <b> configure()</b> and <b> deconfigure()</b> methods are sent by the platform
-when natures are added and removed from a project.&nbsp; You can implement the
-<b> configure()</b> method to add a builder to a project as discussed in
-<a HREF="resAdv_builders.htm" CLASS="XRef">Builders</a>.</P>
-
-
-<H3>
-Associating the nature with a project</H3>
-<P >
-Defining the nature is not enough to associate it with a project.&nbsp; You must
-assign a nature to a project by updating the project's description to include
-your nature.&nbsp; This usually happens when the user creates a new project with a specialized new project wizard that assigns the
-nature.&nbsp; The following snippet
-shows how to assign our new nature to a given project.</P>
-<pre>
-   try {
-      IProjectDescription description = project.getDescription();
-      String[] natures = description.getNatureIds();
-      String[] newNatures = new String[natures.length + 1];
-      System.arraycopy(natures, 0, newNatures, 0, natures.length);
-      newNatures[natures.length] = &quot;com.example.natures.mynature&quot;;
-      description.setNatureIds(newNatures);
-      project.setDescription(description, null);
-   } catch (CoreException e) {
-      // Something went wrong
-   }
-</pre>
-<P>
-<b>NOTE:</b> The nature id is the fully qualified id
-of the nature extension. The fully qualified id of an extension is created by combining
-the plug-in id with the simple extension id in the plugin.xml file. For example, a nature with simple extension
-id &quot;mynature&quot; in the plug-in &quot;com.example.natures&quot; would have the
-name &quot;com.example.natures.mynature&quot;
-</p>
-<P>The natures are not actually assigned to (and configured) for the project
-until you set the project description into the project.&nbsp; Also note that the identifier used for the nature is the fully qualified name (plug-in id + extension id) of the nature extension. </P>
-<P>
-If the nature has been defined with constraints, then workspace API can be used
-to validate the new nature.&nbsp; For example, suppose a nature is defined with
-a prerequisite: </P>
-<pre>   &lt;extension
-      point=&quot;org.eclipse.core.resources.natures&quot;
-      <b>id=&quot;myOtherNature&quot;</b>
-      name=&quot;My Other Nature&quot;&gt;
-      &lt;runtime&gt;
-         &lt;run class=&quot;com.example.natures.MyOtherNature&quot;&gt;
-         &lt;/run&gt;
-      &lt;/runtime&gt;
-<b>   &lt;requires-nature id=&quot;com.example.natures.mynature&quot;/&gt;
-</b>   &lt;/extension&gt;
-</pre>
-<P >
-The new nature is not valid unless the first nature exists for the
-project.&nbsp; Depending on the design of your plug-in, you may want to check
-whether the prerequisite nature has been installed, or you may want to add the
-prerequisite nature yourself.&nbsp; Either way, you can check on the validity of
-proposed combinations of project natures using workspace API. </P>
-
-<pre>   try {
-      IProjectDescription description = project.getDescription();
-      String[] natures = description.getNatureIds();
-      String[] newNatures = new String[natures.length + 1];
-      System.arraycopy(natures, 0, newNatures, 0, natures.length);
-<b>      newNatures[natures.length] = &quot;com.example.natures.myOtherNature&quot;;
-</b>      IStatus status = <b>workspace.validateNatureSet(natures);
-</b>
-      // check the status and decide what to do
-      if (status.getCode() == IStatus.OK) {
-      	description.setNatureIds(newNatures);
-      	project.setDescription(description, null);
-      } else {
-      	// raise a user error
-	...
-      }
-   } catch (CoreException e) {
-      // Something went wrong
-   }
-</pre>
-
-
-<H3>Nature descriptors</H3>
-<p>In addition to working with natures by their id, you can obtain the
-descriptor (<a href="../reference/api/org/eclipse/core/resources/IProjectNatureDescriptor.html"><b>IProjectNatureDescriptor</b></a>)
-which describes a nature, its constraints, and its label.&nbsp; You can query a
-particular nature for its descriptor, or get descriptors from the
-workspace.&nbsp; The following snippet gets the project nature descriptor for
-our new nature:
-</p>
-<pre>      IProjectNatureDescriptor descriptor = workspace.getNatureDescriptor(&quot;com.example.natures.myOtherNature&quot;);
-</pre>
-<p>You can also get an array of descriptors for all installed natures:
-</p>
-<pre>      IProjectNatureDescriptor[] descriptors = workspace.getNatureDescriptors();
-</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_refresh.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_refresh.htm
deleted file mode 100644
index 916378d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_refresh.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Refresh providers
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Refresh providers</H2>
-<P >
-The <a href="../reference/extension-points/org_eclipse_core_resources_refreshProviders.html"><b>org.eclipse.core.resources.refreshProviders</b></a> 
-extension point allows plug-ins to register and implement their own mechanisms for monitoring the external file system
-and refreshing the workspace appropriately.  This extension point is intended for plug-ins that implement
-specialized, often native, schemes for monitoring file system changes.</P>
-<p>
-The plug-in fragment <b>org.eclipse.core.resources.win32</b> implements a native refresh monitor based on
-file system callbacks.  A more naive refresh monitor based on polling is defined for other platforms.
-</p>
-<p>The following snippet shows the definition for this extension in the <b>org.eclipse.core.resources.win32</b>
-fragment.
-</p>
-<pre>   &lt;extension
-         id="win32"
-         point="org.eclipse.core.resources.refreshProviders"&gt;
-      &lt;refreshProvider
-            name="%win32MonitorFactoryName"
-            <b>class="org.eclipse.core.internal.resources.refresh.win32.Win32RefreshProvider"</b>&gt;
-      &lt;/refreshProvider&gt;
-   &lt;/extension&gt;
-</pre>
-<p>The <b>class</b> attribute must be a class that extends 
-<b><a href="../reference/api/org/eclipse/core/resources/refresh/RefreshProvider.html">RefreshProvider</a></b>.
-This class is responsible for installing a monitor on a specific resource and its resource subtree if it is a 
-project or folder.  The monitor must implement 
-<b><a href="../reference/api/org/eclipse/core/resources/refresh/IRefreshMonitor.html">IRefreshMonitor</a></b>.
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_saving.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_saving.htm
deleted file mode 100644
index fcea898..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_saving.htm
+++ /dev/null

@@ -1,263 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Workspace save participation
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Workspace save participation</H2>
-<P >
-Workspace save processing is triggered when the workbench is shut down by the user and at other times
-periodically by the platform.&nbsp; Plug-ins can participate in the workspace save process so that critical
-plug-in data is saved to disk whenever the rest of the workspace's persistent data is saved. </P>
-<P >
-The workspace save process can also be used to track changes that occur between activations of your plug-in.</P>
-
-<H3>
-Implementing a save participant</H3>
-<P >
-To participate in workspace saving, you must add a save participant to the workspace. This is typically done during your plug-in's startup method.&nbsp;
-This is also where you read any state that you might have saved
-when your plug-in was last shut down.</P>
-<P >
-Let's look at a simple plug-in which will demonstrate the save process.</P>
-<pre>
-   package com.example.saveparticipant;
-
-   import org.eclipse.core.runtime.*;
-   import org.eclipse.core.resources.*;
-   import java.io.File;
-   import java.util.*;
-
-   public class MyPlugin extends Plugin {
-      private static MyPlugin plugin;
-
-      public MyPlugin(IPluginDescriptor descriptor) {
-         super(descriptor);
-         plugin = this;
-      }
-
-      public static MyPlugin getDefault() {
-         return plugin;
-      }
-
-      protected void readStateFrom(File target) {
-      }
-
-      public void startup() throws CoreException {
-         super.startup();
-         ISaveParticipant saveParticipant = new MyWorkspaceSaveParticipant();
-         ISavedState lastState =
-            <b>ResourcesPlugin.getWorkspace().addSaveParticipant(this, saveParticipant);</b>
-         if (lastState == null)
-            return;
-         IPath location = lastState.lookup(new Path(&quot;save&quot;));
-         if (location == null)
-            return;
-         // the plugin instance should read any important state from the file.
-         File f = getStateLocation().append(location).toFile();
-         readStateFrom(f);
-      }
-
-      protected void writeImportantState(File target) {
-      }
-   }</pre>
-<P >
-<b><a href="../reference/api/org/eclipse/core/resources/ISaveParticipant.html">
-ISaveParticipant</a></b> defines the protocol for a workspace save participant. Implementors of this
-interface can provide behavior for different stages of the save process.&nbsp;
-Let's look at the stages and how our class <b>WorkspaceSaveParticipant</b>
-implements each of these steps.</P>
-<ul>
-  <li>
-<b>
-prepareToSave</b> notifies the participant that the workspace is about to be saved and that it should suspend normal operation until further notice.&nbsp;
-Our save particpant does nothing here.</li>
-</ul>
-<pre>
-      public void prepareToSave(ISaveContext context) throws CoreException {
-      }
-</pre>
-<ul>
-  <li>
-<b>
-saving</b> tells the participant to save its important state.</li>
-</ul>
-<pre>
-      public void saving(ISaveContext context) throws CoreException {
-         switch (context.getKind()) {
-            case ISaveContext.FULL_SAVE:
-               MyPlugin myPluginInstance = MyPlugin.getDefault();
-               // save the plug-in state
-               <b>int saveNumber = context.getSaveNumber();
-               String saveFileName = &quot;save-&quot; + Integer.toString(saveNumber);
-               File f = myPluginInstance.getStateLocation().append(saveFileName).toFile();
-               </b>// if we fail to write, an exception is thrown and we do not update the path
-               <b>myPluginInstance.writeImportantState(f);
-               context.map(new Path(&quot;save&quot;), new Path(saveFileName));
-               context.needSaveNumber();</b>
-               break;
-            case ISaveContext.PROJECT_SAVE:
-               // get the project related to this save operation
-               IProject project = context.getProject();
-               // save its information, if necessary
-               break;
-            case ISaveContext.SNAPSHOT:
-               // This operation needs to be really fast because
-               // snapshots can be requested frequently by the
-               // workspace.
-               break;
-         }
-      }
-</pre>
-<blockquote>
-  <p>The <a href="../reference/api/org/eclipse/core/resources/ISaveContext.html"><b> ISaveContext</b></a> describes information about the save operation.&nbsp;
-There are three kinds of save operations:&nbsp; <b>FULL_SAVE</b>,
-<b>SNAPSHOT</b>, and <b>PROJECT_SAVE</b>.&nbsp;
-Save participants should be careful to perform the processing appropriate for
-the kind of save event they have received.&nbsp; For example, snapshot events
-may occur quite frequently and are intended to allow plug-ins to save their
-critical state.&nbsp; Taking a long time to save state which can be recomputed
-in the event of a crash will slow down the platform.</p>
-<P >
-A save number is used to create data save files that are named using sequential numbers (<b>save-1</b>,
-<b>save-2</b>, etc.)&nbsp; Each save file is mapped to a logical file name (<b>save</b>) that is independent of the save number. Plug-in data is written to the corresponding file and can be retrieved later without knowing the specific save number of the last successful save operation.&nbsp;
-Recall that we saw this technique in our&nbsp; plug-in's startup code:</P>
-<pre>
-<b>IPath location = lastState.lookup(new Path(&quot;save&quot;));</b>
-</pre>
-<P >
-After we have saved our data and mapped the file name, we call <b>needSaveNumber</b> 
-to indicate that we have actively participated in a workspace save and want to assign a number to the save activity.
-The save numbers can be used to create data files as above.&nbsp;</P>
-
-
-</blockquote>
-<ul>
-  <li>
-<b>
-doneSaving</b> notifies the participant that the workspace has been saved and the participant can continue normal operation.</li>
-</ul>
-<pre>
-      public void doneSaving(ISaveContext context) {
-         MyPlugin myPluginInstance = MyPlugin.getDefault();
-
-         // delete the old saved state since it is not necessary anymore
-         int previousSaveNumber = <b>context.getPreviousSaveNumber()</b>;
-         String oldFileName = &quot;save-&quot; + Integer.toString(previousSaveNumber);
-         File f = myPluginInstance.getStateLocation().append(oldFileName).toFile();
-         f.delete();
-      }
-</pre>
-<blockquote>
-  <p>Here, we clean up the save information from the previous save
-  operation.&nbsp; We use <b>getPreviousSaveNumber</b> 
-  to get the save number that was assigned in the previous save operation (not
-  the one we just completed).&nbsp; We use this number to construct the name of
-  the file that we need to delete.&nbsp; Note that we do not use the save
-  state's logical file map since we've already mapped our current save file
-  number.&nbsp;</p>
-</blockquote>
-<ul>
-  <li>
-<b>
-rollback</b> tells the participant to rollback the important state because the save operation has failed.</li>
-</ul>
-<pre>
-      public void rollback(ISaveContext context) {
-         MyPlugin myPluginInstance = MyPlugin.getDefault();
-
-         // since the save operation has failed, delete the saved state we have just written
-         int saveNumber = context.getSaveNumber();
-         String saveFileName = &quot;save-&quot; + Integer.toString(saveNumber);
-         File f = myPluginInstance.getStateLocation().append(saveFileName).toFile();
-         f.delete();
-      }
-</pre>
-<blockquote>
-  <p>Here, we delete the state that we just saved.&nbsp; Note that we use the
-  current save number to construct the file name of the file we just saved.&nbsp;
-  We don't have to worry about the fact that we mapped this file name into the <a href="../reference/api/org/eclipse/core/resources/ISaveContext.html"><b> ISaveContext</b></a><b>.
-  </b>The platform will discard the context when a save operation fails.</p>
-</blockquote>
-
-
-<p>If your plug-in throws an exception at any time during the save lifecycle, it
-will be removed from the current save operation and will not get any of the
-remaining lifecycle methods.&nbsp; For example, if you fail during your <b>saving</b> 
-method, you will not receive a
-<b>
-rollback</b>  or
-<b>
-doneSaving</b>  message.&nbsp;</p>
-
-
-<H3>
-Using previously saved state</H3>
-<P >
-When you add a save participant to the workspace, it will return an <b><a href="../reference/api/org/eclipse/core/resources/ISavedState.html"> ISavedState</a></b> 
-object, which describes what your plug-in saved during its last save operation (or
-<b> null</b> if your plug-in has not previously saved any state). This
-object can be used to access information from the previous save file (using the save number and file map) or to process changes that have occurred between activations of a plug-in.</P>
-
-<H4>
-Accessing the save files</H4>
-<P >
-If a file map was used to save logically named files according to the save number, this same map can be used to retrieve the data from the last known save state.</P>
-<pre>
-   ISaveParticipant saveParticipant = new MyWorkspaceSaveParticipant();
-   ISavedState lastState =
-      ResourcesPlugin.getWorkspace().addSaveParticipant(myPluginInstance, saveParticipant);
-
-   if (lastState != null) {
-      String saveFileName = lastState.lookup(new Path(&quot;save&quot;)).toString();
-      File f = myPluginInstance.getStateLocation().append(saveFileName).toFile();
-      // the plugin instance should read any important state from the file.
-      myPluginInstance.readStateFrom(f);
-   }
-</pre>
-
-
-<H4>
-Processing resource deltas between activations</H4>
-<P >
-Recall that any number of resource change events could occur in the workspace before your plug-in is ever activated. If you want to know what changes have occurred since your plug-in was
-deactivated, you can use the save mechanism to do so, even if you don't need to save any other data.</P>
-<P >
-The save participant must request that the platform keep a resource delta on its behalf. This is done as part of the save operation.</P>
-<pre>
-   public void saving(ISaveContext context) throws CoreException {
-      // no state to be saved by the plug-in, but request a
-      // resource delta to be used on next activation.
-      context.needDelta();
-   }
-</pre>
-<P >
-During plug-in startup, the previous saved state can be accessed and change events will be created for all changes that have occurred since the last save.</P>
-<pre>
-   ISaveParticipant saveParticipant = new MyWorkspaceSaveParticipant();
-   ISavedState lastState =
-      ResourcesPlugin.getWorkspace().addSaveParticipant(myPluginInstance, saveParticipant);
-   if (lastState != null) {
-      lastState.processResourceChangeEvents(new MyResourceChangeReporter());
-   }
-</pre>
-<P >
-The provided class must implement <a href="../reference/api/org/eclipse/core/resources/IResourceChangeListener.html"><b>IResourceChangeListener</b></a>, as described in
-<a HREF="resAdv_events.htm" CLASS="XRef"> Tracking resource changes</a>.&nbsp; The changes since the last save are reported as part of the <b> POST_AUTO_BUILD</b> resource change event.</P>
-<blockquote><i>
-Note:&nbsp; Marker changes are not reported in the change events stored in an <b> ISavedState</b>. 
-You must assume that any or all markers have changed since your last state was saved.</i></blockquote>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resInt.htm b/bundles/org.eclipse.platform.doc.isv/guide/resInt.htm
deleted file mode 100644
index 99d2e02..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resInt.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Resources overview</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Resources overview</H1>
-<p> An essential plug-in for Eclipse IDE applications is the resources plug-in 
-  (named <b>org.eclipse.core.resources</b>). The resources plug-in provides services 
-  for accessing the projects, folders, and files that a user is working with. 
-</p>
-<p>For more information on workspace resources, check out some of the following 
-  documents:</p>
-<ul>
-  <li><a href="resInt_workspace.htm">Resources and the workspace</a></li>
-  <li><a href="resInt_filesystem.htm">Resources and the local file system</a></li>
-  <li><a href="resInt_properties.htm">Resource properties</a></li>
-  <li><a href="resInt_preferences.htm">Project-scoped preferences</a></li>
-  <li><a href="resInt_content.htm">File encoding and content types</a></li>
-  <li><a href="resInt_linked.htm">Linked resources</a></li>
-  <li><a href="resAdv_markers.htm">Resource markers</a></li>
-  <li><a href="resAdv_modify.htm">Modifying the workspace </a> 
-    <ul>
-      <li><a href="resAdv_batching.htm">Batching resource changes</a></li>
-      <li><a href="resAdv_events.htm">Tracking resource changes</a></li>
-      <li><a href="resAdv_concurrency.htm">Concurrency and the workspace</a></li>
-    </ul>
-  </li>
-  <li><a href="resAdv_builders.htm">Incremental project builders</a></li>
-  <li><a href="resAdv_derived.htm">Derived resources</a></li>
-  <li><a href="resAdv_saving.htm">Workspace save participation</a></li>
-  <li><a href="resAdv_natures.htm">Project natures</a></li>
-  <li><a href="resAdv_hooks.htm">Resource modification hooks</a></li>
-  <li><a href="resAdv_hooks.htm">Refresh providers</a></li>
-</ul>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resInt_content.htm b/bundles/org.eclipse.platform.doc.isv/guide/resInt_content.htm
deleted file mode 100644
index 9bbf597..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resInt_content.htm
+++ /dev/null

@@ -1,83 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-File encoding and content types
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-File encoding and content types</H2>
-<P >
-The platform runtime plug-in defines infrastructure for defining and discovering <b>content types</b> for data
-streams.  (See <a href="runtime_content.htm">Content types</a> for an overview of the content framework.)  
-An important part of the content type system is the ability to specify different encodings (character sets)
-for different kinds of content.  The resources API further allows default character sets to be established for 
-projects, folders, and files.  These default character sets are consulted if the content of the file itself
-does not define a particular encoding inside its data stream.
-</P>
-<h3>
-Setting a character set
-</h3>
-<p>
-We've seen in <a href="runtime_content.htm">Content types</a> that default file encodings can be established
-for content types.  More fine-grained control is provided by the resources API.
-</p>
-<p>
-<b><a href="../reference/api/org/eclipse/core/resources/IContainer.html">IContainer</a></b> 
-defines protocol for setting the default character set for a particular project or folder.  This gives 
-plug-ins (and ultimately the user) more freedom in determining an appropriate character set for a set of files when
-the default character sets from the content type may not be appropriate.</p>
-<p>
-<b><a href="../reference/api/org/eclipse/core/resources/IFile.html">IFile</a></b> defines API for setting
-the default character set for a particular file.  If no encoding is specified inside the file contents,
-then this character set will be used.  The file's default character set takes precedence over any default
-character set specified in the file's folder, project, or content type.
-</p>
-<p>
-Both of these features are available to the end-user in the properties page for a resource.
-</p>
-<h3>Querying the character set</h3>
-
-<p><b><a href="../reference/api/org/eclipse/core/resources/IFile.html">IFile</a></b> also defines API for
-querying the character set of a file.  A boolean flag specifies whether only the character set explicitly 
-defined for the file should be returned, or whether an implied character set should be returned.  For example:
-</p>
-<pre>	String charset = myFile.getCharset(false);
-</pre>
-<p>returns null if no character set was set explicitly on myFile.  However, 
-</p>
-<pre>	String charset = myFile.getCharset(true);
-</pre>
-<p>will first check for a character set that was set explicitly on the file.  If none is found, then the content of the file
-will be checked for a description of the character set.  If none is found, then the file's containing folders and projects 
-will be checked for a default character set.  If none is found, the default character set defined for the content type 
-itself will be checked.  And finally, the platform default character set will be returned if there is no other designation
-of a default character set.  The convenience method <b>getCharset()</b> is the same as using <b>getCharset(true)</b>.
-</p>
-<h3>Content types for files in the workspace</h3>
-<p>For files in the workspace, <a href="../reference/api/org/eclipse/core/resources/IFile.html"><strong>IFile</strong></a> provides API for obtaining 
-  the file content description:</p>
-<pre>IFile file = ...;
-IContentDescription description = file.getDescription();</pre>
-<p>This API should be used even when clients are only interested in determining 
-  the content type - the content type can be easily obtained from the content 
-  description. It is possible to detect the content type or describe files in 
-  the workspace by obtaining the contents and name and using the API described 
-  in <a href="runtime_content_using.htm">Using content types</a>, but that is not recommended. Content type determination 
-  using <strong>IFile.getContentDescription()</strong> takes into account <a href="resAdv_natures.htm">project 
-  natures</a> and project-specific settings. If you go directly to the content 
-  type manager, you are ignoring that. But more importantly, because reading the 
-  contents of files from disk is very expensive. The Resources plug-in maintains 
-  a cache of content descriptions for files in the workspace. This reduces the 
-  cost of content description to an acceptable level.</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resInt_filesystem.htm b/bundles/org.eclipse.platform.doc.isv/guide/resInt_filesystem.htm
deleted file mode 100644
index a0bbd0c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resInt_filesystem.htm
+++ /dev/null

@@ -1,242 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Resources and the local file system
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Resources and the local file system</H2>
-<P >
-When the platform is running and the resources plug-in is active, the workspace is represented by an instance of
-<b><a href="../reference/api/org/eclipse/core/resources/IWorkspace.html"> IWorkspace</a></b>, which provides 
-protocol for accessing the resources it contains.  An <b><a href="../reference/api/org/eclipse/core/resources/IWorkspace.html"> IWorkspace</a></b> 
-instance represents an associated collection of files and directories in the local file system.  You can access the 
-workspace from the resources plug-in class (defined in 
-<b><a href="../reference/api/org/eclipse/core/resources/package-summary.html">org.eclipse.core.resources</a></b>). </P>
-<pre>
-   IWorkspace workspace = ResourcesPlugin.getWorkspace(); 
-</pre>
-<P >
-When the resources plug-in is not running, the workspace exists solely in the local file system and is viewed or manipulated by the user
-via standard file-based tools. Let's look at what a workspace looks like on disk as we explain the
-resources plug-in API. </P>
-
-<H3>
-Our sample tree on disk</H3>
-<P >
-When you installed the platform SDK, you unzipped the files into a directory of your choosing.  We will call this 
-directory the platform root directory.  This is the directory that contains the <b> plugins</b> directory, among others.  
-Inside the platform root directory, there is a <b>workspace</b> directory which is used to hold the resources that are 
-created and manipulated by the platform. If you look in your <b>workspace</b> directory, you'll see separate subdirectories 
-for each project that exists in the workspace.  Within these subdirectories are the folders and files that
-each project contains.  </P>
-<P >
-If the SDK in our example is installed in <b> c:\MySDK</b>, then inside
-the <b>c:\MySDK\workspace</b> directory we find subdirectories named after the workspace's projects,
-<b> MyWeb</b> and <b>MyServlet</b>.  These are called the projects' content directories.
-Content directories are created by the platform when the user creates a project.</P>
-<P >
-Inside each directory, we find the files and folders within the project, laid out exactly the same as they are in the 
-workspace's resource tree.  All file names are the same, and the files' contents are the same
-whether accessed from the file system or from the workspace. The only surprise
-is the <b>.project</b> file, explained in a moment.</P>
-<pre>
-   C:\MySDK\workspace  (workspace root)
-      .metadata\ (platform metadata directory
-      MyWeb\ (project content directory for MyWeb)
-	 .project
-         index.html
-         images\
-            logo.png
-      MyServlet\ (project content directory for MyServlet)
-	 .project
-         src\
-            main.java
-         bin\
-            main.class</pre>
-<P >
-The platform has a special <b>.metadata</b> directory for holding platform internal information.  The
-<b>.metadata</b> directory of a workspace is considered to be a &quot;black box.&quot;  Important information about the 
-workspace structure, such as a project's references or a resource's properties,
-is stored in the metadata portion of the workspace and should only be accessed by tools through the
-platform API.&nbsp; These files should never be edited or manipulated using
-generic file system API. </P>
-<P >In addition, each project has its own <b>.project</b> file, where metadata
-about the project is kept.&nbsp; This file is basically an on-disk equivalent of
-the information found in a project's
-<b><a href="../reference/api/org/eclipse/core/resources/IProjectDescription.html">IProjectDescription</a></b>.&nbsp;&nbsp; </P>
-<P >Apart from the <b>.metadata</b>  directory and the <b>.project</b> files, the folders and files in the workspace directory are fair game for other
-tools.&nbsp; The files and folders can be manipulated by non-integrated tools, such as text editors and file system
-utilities.&nbsp; The only issue is that the user must be careful when editing
-these files both in the workbench and externally.&nbsp; (This is no
-different than when a user edits a file using two independent stand-alone
-tools.)&nbsp; The workbench provides refresh operations to reconcile the
-workspace view of resources with the actual state in the file system and periodically refreshes
-the workspace based on the state of the file system.</P>
-
-
-<H3>
-Our sample tree in code</H3>
-<P >
-The resource API allows us to manipulate this resource tree in code.  Here we will look at some code snippets for a quick taste of the resource
-API.  The resource API is defined in a series of interfaces in
-<b><a href="../reference/api/org/eclipse/core/resources/package-summary.html">org.eclipse.core.resources</a></b>.  There are interfaces for all of the resource types, such as
-<b><a href="../reference/api/org/eclipse/core/resources/IProject.html">IProject</a></b>,
-<b><a href="../reference/api/org/eclipse/core/resources/IFolder.html">IFolder</a></b>, and
-<b><a href="../reference/api/org/eclipse/core/resources/IFile.html">IFile</a></b>.  Extensive common protocol is defined in
-<b><a href="../reference/api/org/eclipse/core/resources/IResource.html">IResource</a></b>.  We also make use of the
-<b><a href="../reference/api/org/eclipse/core/runtime/package-summary.html">org.eclipse.core.runtime</a></b> interface
-<b><a href="../reference/api/org/eclipse/core/runtime/IPath.html">IPath</a></b>, which represents segmented paths such as resource or file system paths.</P>
-<P >
-Manipulating resources is very similar to manipulating files using <b> java.io.File</b>.&nbsp;
-The API is based on <b>handles</b>.&nbsp; When you use API like <b>getProject</b>
-or <b>getFolder</b>, you are returned a handle to the
-resource.&nbsp;&nbsp; There is no guarantee or requirement that the resource itself exists
-until you try to do something with the handle.&nbsp; If you expect a resource to
-exist, you can use <b>exists</b> method to ensure
-this is the case.&nbsp;&nbsp;  </P>
-<P >
-To navigate the workspace from a plug-in, we must first obtain the <a href="../reference/api/org/eclipse/core/resources/IWorkspaceRoot.html"><b>IWorkspaceRoot</b></a>, which represents the top of the resource hierarchy in the workspace.</P>
-<pre>
-   IWorkspaceRoot myWorkspaceRoot = ResourcesPlugin.getWorkspace().getRoot();</pre>
-<P >
-Once we have a workspace root, we can access the projects in the workspace. </P>
-<pre>
-   IProject myWebProject = myWorkspaceRoot.getProject(&quot;MyWeb&quot;);
-   // open if necessary
-   if (myWebProject.exists() &amp;&amp; !myWebProject.isOpen())
-      myWebProject.open(null);
-</pre>
-<P >
-Before we can manipulate a project, we must open it.  Opening the project reads the project's
-structure from disk and creates the in-memory object representation of the project's resource tree.  Opening a project is an explicit operation since each open project consumes memory to represent the resource tree
-internally and open projects participate in various resource lifecycle events
-(such as building) which can be lengthy.&nbsp; In general, closed projects
-cannot be accessed and will appear empty even though the resources are still present in the file system.</P>
-<P >
-You'll notice that many of these resource examples pass a <b> null</b> parameter when manipulating resources.
-Many resource operations are potentially heavyweight enough to warrant progress reporting and
-user cancellation.  If your code has a user interface, you will typically pass an <b><a href="../reference/api/org/eclipse/core/runtime/IProgressMonitor.html"> IProgressMonitor</a></b>,
-which allows the
-resources plug-in to report progress as the resource is manipulated and allows the user to cancel the operation if desired.&nbsp;
-For now, we simply pass <b>null</b>, indicating no
-progress monitor.</P>
-<P >
-Once we have an open project, we can access its folders and files, as well as create additional ones.&nbsp;
-In the following example we create a file resource from the contents of a file
-located outside of our workspace.  </P>
-<pre>
-   IFolder imagesFolder = myWebProject.getFolder(&quot;images&quot;);
-   if (imagesFolder.exists()) {
-      // create a new file
-      IFile newLogo = imagesFolder.getFile(&quot;newLogo.png&quot;);
-      FileInputStream fileStream = new FileInputStream(
-         &quot;c:/MyOtherData/newLogo.png&quot;);
-      newLogo.create(fileStream, false, null);
-      // create closes the file stream, so no worries.   
-   }
-</pre>
-<P >
- In the example above, the
-first line obtains a handle to the images folder.&nbsp; We must check that the
-folder <b>exists</b> before we can do anything
-interesting with it.&nbsp; Likewise, when we get the file <b>newLogo</b>,
-the handle does not represent a real file until we create the file in the last
-line.&nbsp; In this example, we create the file by populating it with the
-contents of <b>logo.png</b>.  </P>
-<P >
-The next snippet is similar to the previous one, except that it copies the <b> newLogo</b> file from the original logo rather than create a new
-one from its contents.</P>
-<pre>
-   IFile logo = imagesFolder.getFile(&quot;logo.png&quot;);
-   if (logo.exists()) {
-      IPath newLogoPath = new Path(&quot;newLogo.png&quot;);
-      logo.copy(newLogoPath, false, null);
-      IFile newLogo = imagesFolder.getFile(&quot;newLogo.png&quot;);
-      ...
-   }
-</pre>
-<P >
-Finally, we'll create another images folder and move the newly created file to it.  We rename the file as a side effect of moving it.</P>
-<pre>
-   ...
-   IFolder newImagesFolder = myWebProject.getFolder(&quot;newimages&quot;);
-   newImagesFolder.create(false, true, null);
-   IPath renamedPath = newImagesFolder.getFullPath().append(&quot;renamedLogo.png&quot;);
-   newLogo.move(renamedPath, false, null);
-   IFile renamedLogo = newImagesFolder.getFile(&quot;renamedLogo.png&quot;);
-</pre>
-
-
-<P>Many of the resource API methods include a <b>force</b>
-boolean flag which specifies whether resources that are out of synch with the
-corresponding files in the local file system will be updated anyway.&nbsp; See <a href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a>
-for more information.&nbsp; You can also use <a href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a><b>.isSynchronized
-</b>to determine whether a particular resource is in synch with the file system.</P>
-
-
-<H3>
-<a name="mapping">
-Mapping resources to disk locations</a></H3>
-<P >
-  In the sample resource tree, we've assumed that all of the project content directories are
-in the <b>workspace</b> directory underneath the platform root
-directory (<b>C:\MySDK\workspace)</b>.  This is the default configuration
-for projects.&nbsp; However, a project's content directory can be remapped to any arbitrary directory in the file system, perhaps on a different disk drive.</P>
-<P >
-The ability to map the location of a project independent of other projects allows the user to
-store the contents of a project in a place that makes sense for the project and the project team.  A project's content directory should be considered &quot;out in the open.&quot;  This means that users can create, modify, and delete resources
-by using the workbench and plug-ins, or by directly using file system based tools and editors.</P>
-<P> Resource path names are not complete file system paths.  Resource paths are always
-based on the project's location (usually the <b>workspace</b>
-directory).&nbsp; To obtain the full file system path to a resource, you must query its location using
-<b>
-<a href="../reference/api/org/eclipse/core/resources/IResource.html">IResource</a>.getLocation.&nbsp;
-</b>Howevever, you cannot use
-<b> <a href="../reference/api/org/eclipse/core/resources/IProjectDescription.html">IProjectDescription</a>.setLocation
-</b>to change its location, because that method is just a simple setter for a
-data structure.&nbsp;&nbsp;</P>
-<P>Conversely, if you want to get the corresponding resource object given a file
-system path, you can use <a href="../reference/api/org/eclipse/core/resources/IWorkspaceRoot.html"><b>IWorkspaceRoot</b></a>.<b>getFileForLocation</b>
-or <a href="../reference/api/org/eclipse/core/resources/IWorkspaceRoot.html"><b>IWorkspaceRoot</b></a>.<b>getContainerForLocation</b>.</P>
-
-
-<H3>
-Resource API and the file system</H3>
-<P >
-When we use the resources API to modify our workspace's resource tree, the files
-are changed in the file system in addition to updating our resource objects.  What about changes to
-resource files that happen outside of the platform's API?  </P>
-<P >
-External changes to resources will not be reflected in the workspace and resource objects until 
-detected by the resources plug-in.  The resources plug-in also uses a mechanism appropriate for
-each particular native operating system for discovering external changes made in the file system.
-In addition, clients can use resource API to 
-reconcile workspace and resource objects with the local file system quietly and without user intervention.
-The user can also explicitly force a refresh in the resource navigator view of the workbench.  </P>
-<p>Many of the methods in the resource APIs include a force parameter which specifies how resources that
-are out of sync with the file system should be handled.  The API Reference for each method provides specific information 
-about this parameter. Additional methods in the API allow programmatic control of file system refresh, such as
-<b>IResource.refreshLocal(int depth, IProgressMonitor monitor)</b>. See 
-<b><a href="../reference/api/org/eclipse/core/resources/IResource.html">IResource</a></b>
-for information on correct usage and costs.</p>
-<p>
-Plug-ins that wish to supply their own mechanism for periodically refreshing the workspace based on
-the state of the external file system may do so using the
-<a href="../reference/extension-points/org_eclipse_core_resources_refreshProviders.html"><b>org.eclipse.core.resources.refreshProviders</b></a> 
-extension point.  See <a href="resAdv_refresh.htm">Refresh providers</a> for more information. </p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resInt_linked.htm b/bundles/org.eclipse.platform.doc.isv/guide/resInt_linked.htm
deleted file mode 100644
index 76a1d9f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resInt_linked.htm
+++ /dev/null

@@ -1,197 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Linked resources
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>Linked resources</H2>
-<P >Earlier discussions of resources and the file system (<a href="resInt_filesystem.htm#mapping">Mapping
-resources to disk locations)</a> assumed that all resources in a project are
-located in the same place in the file system.&nbsp; This is generally
-true.&nbsp; However, the concept of <b>linked resources</b> in the workbench is
-provided so that files and folders inside a project can be stored in the file system outside of the project's location.&nbsp;
-</P>
-<P >Linked resources can
-be located virtually anywhere in the file system.  They can reside outside the project location,
-or even within another project.  There are only a few restrictions on linked
-resource locations. The method 
-<b><a href="../reference/api/org/eclipse/core/resources/IWorkspace.html">IWorkspace</a>.validateLinkLocation</b>
-can be used to ensure that a given location is valid for creating a linked
-resource.
-</P>
-<P>
-Linked resources are created using the method 
-<b><a href="../reference/api/org/eclipse/core/resources/IFolder.html">IFolder</a>.createLink</b> or
-<b><a href="../reference/api/org/eclipse/core/resources/IFile.html">IFile</a>.createLink</b>.  
-To determine programmatically whether a given resource is a linked resource, you
-can use the method
-<b><a href="../reference/api/org/eclipse/core/resources/IResource.html">IResource</a>.isLinked</b>.
-Note that this method will only return <code>true</code> for linked resources, not for children 
-of linked resources.
-</P>
-<P>
-Apart from these special methods for creating linked resources and
-finding out if a resource is linked, you can use normal workspace API when manipulating linked
-resources.  In most respects, linked resources act exactly like any other resource in
-the workspace.  However, some restrictions apply when moving, copying, or
-deleting linked resources.&nbsp; See <b><a href="../reference/api/org/eclipse/core/resources/IResource.html">IResource</a></b>
-and its sub-classes for information on individual operations and their limitations.
-</P>
-<h3>Path variables</h3>
-<P>
-  Path variables can be used
-when specifying the location of linked resources.&nbsp; A path variable is a simple (String -&gt;
-<b><a href="../reference/api/org/eclipse/core/runtime/IPath.html">IPath</a></b>) mapping that 
-defines a shortcut for a location in the file system.&nbsp; Variables can ease
-the management of linked resources by reducing the number of places where
-hard-coded, absolute file system paths are used.</p><P>Path variables
-streamline the management of linked resources for users in several ways:</p>
-<ul>
-<li>Allows a single reference to the absolute path when defining several linked resources under a common
-  root</li>
-<li>Allows the location of several resources to be redefined by changing a
-  single variable</li>
-<li>Allows users to share projects containing linked resources without updating
-  the paths of each resource (since the absolute path can vary from one machine
-  to another.)</li>
-</ul>
-<p>
-The last item in this list deserves a bit of explanation.  When a user creates a
-linked resource in a project, a description of the linked resource is added to the
-project description file (&quot;.project&quot;) in the project's location. By
-using a path variable, users can share a project (by copying the project's
-content or by using a repository), and redefine the variable to suit each
-individual workstation.&nbsp; For example, one user might store external resources under c:\temp on
-one system,
-while another user using Unix might store the same resources in /home/username/tmp.&nbsp;
-Defining a path variable on each workspace (<code>TEMP=c:\temp</code> and <code>TEMP=/home/userb/tmp)</code>
- allows users to work around this difference and share the projects with linked
-resources as is.</p>
-<p><b><a href="../reference/api/org/eclipse/core/resources/IPathVariableManager.html">IPathVariableManager</a></b>
- defines the API for creating, manipulating, and resolving path variables. It also provides methods for validating variable names and values before
-creating them, and for installing a listener to be notified when path variable definitions
-change.  You can obtain an instance of this class using
-<b><a href="../reference/api/org/eclipse/core/resources/IWorkspace.html">IWorkspace</a>.getPathVariableManager</b>.
-See the code examples at the end of this section for more detail.</p>
-<p>
-The method 
-<b><a href="../reference/api/org/eclipse/core/resources/IResource.html">IResource</a>.getRawLocation</b>
-can be used to find out the unresolved location of a linked resource. That is,
-to get the actual path variable name instead of resolving it to its value.&nbsp;
-If a resource location is not defined with a path variable, the <b>getRawLocation</b>
-method acts exactly like the <b>getLocation</b> method.
-</p>
-<h3>Broken links</h3>
-<p>
-Clients that manipulate resources programmatically need to be aware of the possibility of
-broken links.  Broken links occur when a linked resource's location does not
-exist, or is specified relative to an undefined path variable. The following
-special cases apply when using <b><a href="../reference/api/org/eclipse/core/resources/IResource.html">IResource</a></b>
-protocol:</p>
-<ul>
-<li>The <b>copy</b> and <b>move</b> methods will fail when called on broken links.</li>
-<li>Calling <b>refreshLocal</b> on a broken link will not cause the resource to be removed
-from the workspace, as it does for normal resources that are missing from the file system.</li>
-<li>The method <b>getLocation</b> will return <code>null</code> for linked resources
-whose locations are relative to undefined path variables.</li>
-<li>You can still use <b>delete</b> to remove broken links from the workspace.</li>
-</ul>
-<H3>Compatibility with installed plug-ins</H3>
-<p>
-Some plug-ins may not be able to handle linked resources, so there are a number
-of mechanisms available for disabling them.  If you are writing a plug-in that absolutely
-needs all of a project's contents to be located in the project's default location, you 
-can use these mechanisms to prevent users from creating linked resources where
-you don't want them to appear.
-</p>
-<p>
-The first mechanism is called the <i>project nature veto</i>.  If you define your
-own <a href="resAdv_natures.htm">project nature</a>, you can specify in the nature 
-definition that the nature is not compatible with linked resources.  Here is an example 
-of a nature definition that 
-employs the nature veto:</p>
-<pre>&lt;extension
-	id=&quot;myNature&quot;
-	name=&quot;My Nature&quot;
-	point=&quot;org.eclipse.core.resources.natures&quot;&gt;
-	&lt;runtime&gt;
-		&lt;run class=&quot;com.xyz.MyNature&quot;/&gt;
-	&lt;/runtime&gt;
-	&lt;options <b>allowLinking=&quot;false&quot;</b>/&gt;
-&lt;/extension&gt;
-</pre>
-<p>
-The second mechanism for preventing linked resource creation is the <i>team hook</i>.
-If you define your own repository implementation, you can make use of the <b><a href="../reference/extension-points/org_eclipse_core_resources_teamHook.html">org.eclipse.core.resources.teamHook</a></b>
-extension point to prevent the creation of linked
-resources in projects that are shared with your repository type.  By default, 
-repository providers do <em>not</em> allow linked resources in projects
-connected to the repository.&nbsp;
-</p>
-<p>If the repository support is provided by an older plug-in
-that is not aware of linked resources, you will not be able to create linked resources
-in those projects.&nbsp;
-</p>
-<p>
-Finally, there is a preference setting that can be used to disable linked resources
-for the entire workspace.  While the previous two veto mechanisms work
-on a per-project basis, this preference affects all projects in the workspace.  To
-set this preference programatically, use the preference <code>ResourcesPlugin.PREF_DISABLE_LINKING</code>.
-Note that even when set, users or plug-ins can override this by turning the preference
-off.
-</p>
-
-<H3>Linked resources in code</H3>
-<P >
-Let's go into some examples of using linked resources in code. We'll start by 
-defining a path variable:</p>
-<pre>   IWorkspace workspace = ResourcesPlugin.getWorkspace();
-   IPathVariableManager pathMan = workspace.getPathVariableManager();
-   String name = &quot;TEMP&quot;;
-   IPath value = new Path(&quot;c:\\temp&quot;);
-   if (pathMan.validateName(name).isOK() &amp;&amp; pathMan.validateValue(value).isOK()) {
-      pathMan.setValue(name, value);
-   } else {
-      //invalid name or value, throw an exception or warn user
-   }
-</pre>
-<p>Now we can create a linked resource relative to the defined path variable:</p>
-<pre>   IProject project = workspace.getProject(&quot;Project&quot;);//assume this exists
-   IFolder link = project.getFolder(&quot;Link&quot;);
-   IPath location = new Path(&quot;TEMP/folder&quot;);
-   if (workspace.validateLinkLocation(location).isOK()) {
-      link.createLink(location, IResource.NONE, null);
-   } else {
-      //invalid location, throw an exception or warn user
-   }
-</pre>
-<p>That's it!  You now have a linked folder in your workspace called &quot;Link&quot;
-that is located at &quot;c:\temp\folder&quot;.</p>
-<p>
-Let's end with some code snippets on this linked resource to illustrate the behavior other
-methods related to linked resources:</p>
-<pre>
-   link.getFullPath() ==&gt; &quot;/Project/Link&quot;
-   link.getLocation() ==&gt; &quot;c:\temp\folder&quot;
-   link.getRawLocation() ==&gt; &quot;TEMP/folder&quot;
-   link.isLinked() ==&gt; &quot;true&quot;
-   
-   IFile child = link.getFile(&quot;abc.txt&quot;);
-   child.create(...);
-   child.getFullPath() ==&gt; &quot;/Project/Link/abc.txt&quot;
-   child.getLocation() ==&gt; &quot;c:\temp\folder\abc.txt&quot;
-   child.getRawLocation() ==&gt; &quot;c:\temp\folder\abc.txt&quot;
-   child.isLinked() ==&gt; &quot;false&quot;
-</pre>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resInt_preferences.htm b/bundles/org.eclipse.platform.doc.isv/guide/resInt_preferences.htm
deleted file mode 100644
index 119e240..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resInt_preferences.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Project-scoped preferences
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Project-scoped preferences</H2>
-<P >
-In <a href="runtime_preferences.htm">Runtime preferences</a>, we looked at the infrastructure for defining and 
-storing preferences with different scopes.  We also saw that the
-<a href="../reference/extension-points/org_eclipse_core_runtime_preferences.html"><b>org.eclipse.core.runtime.preferences</b></a> 
-extension can be used to define additional scopes for preferences.  The platform resources plug-in defines its own
-preference scope, called &quot;Project,&quot; in order to define project-scoped preferences.  Project-scoped preferences are stored in a file located
-inside the project.  This makes it easy to store a set of preferences and exchange them with other users using 
-resource-oriented mechanisms such as a version control system.
-</p>
-<h3>Specifying the scope</h3>
-
-<p>The definition for new scopes is pretty simple.  The plug-in defines the name of the scope, as well as the class
-that implements it.  The resources plug-in defines the project scope 
-as follows:
-</p>
-<pre>	&lt;extension id="preferences" point="org.eclipse.core.runtime.preferences" name="preferences"&gt;
-		&lt;scope name="project" class="org.eclipse.core.internal.resources.ProjectPreferences"/&gt;
-	&lt;/extension&gt;
-</pre>
-<p>The specified class must implement the 
-<b><a href="../reference/api/org/eclipse/core/runtime/preferences/IScope.html">IScope</a></b> interface, which means
-it must be capable of creating preference nodes for the scope.
-</p>
-
-<h3>Project-scoped preference nodes</h3>
-
-<p>Since the project scope for preferences is not one of the standard runtime scopes, the node representing a project-level
-preference must be obtained specifically.  From the root preference node, you must navigate to the project-scoped
-preference.  This can be achieved using the <b>ProjectScope</b>:
-</p>
-<pre>	IScopeContext projectScope = new ProjectScope(MyProject);
-</pre>
-<p>Once the project scope for a particular is project is found, the preference values can
-be obtained using the same mechanisms seen earlier.  Preferences are named using the string name of the 
-preference.  The names are qualified with another string (often a plug-in id) that qualifies the namespace
-of the preference.  The following snippet gets a preference node from the project scope.  You'll notice that once
-the correct scope is obtained, working with the nodes is no different than with nodes from other scopes.
-</p>
-<pre>	...
-	Preferences projectNode = projectScope.node(&quot;com.example.myplugin&quot;);
-	if (projectNode != null) {
-		value = node.getBoolean(&quot;MyPreference&quot;, &quot;true&quot;);
-		//do something with the value.
-	}
-	...
-</pre>
-<p>To save the value to a file in the project, the node is flushed.  The resources plug-in handles the logistics
-for managing the project-level preferences file.
-</p>
-<pre>	projectNode.flush();
-</pre>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resInt_properties.htm b/bundles/org.eclipse.platform.doc.isv/guide/resInt_properties.htm
deleted file mode 100644
index 1ab56e1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resInt_properties.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Resource properties
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h2>Resource properties</h2>
-<p>Resources have properties that can be used to store meta-information about the resource.  Your plug-in
-can use these properties to hold information about a resource that is specific to your purpose.
-Resource properties are declared, accessed, and maintained by various plug-ins, and are not interpreted 
-by the platform.  When a resource is deleted from the workspace, its properties are also deleted.
-</p>
-<p>There are two kinds of resource properties:
-</p>
-<ul>
-<li><b>Session properties</b> allow your plug-ins to easily cache information about a resource in key-value pairs.
-The values are arbitrary objects.&nbsp; These properties are maintained in memory and lost when a resource is 
-deleted from the workspace, or when the project or workspace is closed.</li>
-<li><b>Persistent properties</b> are used to store resource-specific information on disk.  The value of a 
-persistent property is an arbitrary string. Your plug-in decides how to interpret the string.  The strings are 
-intended to be short (under 2KB).  Persistent properties are stored on disk with the platform metadata and 
-maintained across platform shutdown and restart.</li>
-</ul>
-<p>If you follow the convention of qualifying property key names with the unique id of your plug-in, you won't 
-have to worry about your property names colliding with those of other plug-ins.
-</p>
-<p>If your plug-in needs to store persistent information about a project that is much larger than 2 KB, then these
-properties should be exposed as resources in their own right, rather than using the persistent properties API.
-</p>
-<p>See <b><a href="../reference/api/org/eclipse/core/resources/IResource.html">
-IResource</a></b> for a description of the API for getting and setting the different kinds
-of resource properties.
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resInt_workspace.htm b/bundles/org.eclipse.platform.doc.isv/guide/resInt_workspace.htm
deleted file mode 100644
index dc531f2..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resInt_workspace.htm
+++ /dev/null

@@ -1,80 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Resources and the workspace
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Resources and the workspace</H2>
-<P >
-The central hub for your user's data files is called a <b>workspace</b>.  You can think of the platform 
-workbench as a tool that allows the user to navigate and manipulate the workspace.  The resources 
-plug-in provides APIs for creating, navigating, and manipulating resources in a workspace. The workbench 
-uses these APIs to provide this functionality to the user. Your plug-in can also use these APIs.</P>
-<P >
-From the standpoint of a resource-based plug-in, there is exactly one workspace, and it is always open for 
-business as long as the plug-in is running.  The workspace gets opened automatically when the resources 
-plug-in is activated, and closed when the platform is shut down.  If your plug-in requires the resources 
-plug-in, then the resources plug-in will be started before your plug-in, and the workspace will be available to you.</P>
-<P >
-The workspace contains a collection of resources.  From the user's perspective, there are three different types 
-of resources:  <b>projects</b>, <b>folders</b>, and <b>files</b>. A project is a collection of any number of 
-files and folders.  It is a container for organizing other resources that relate to a specific area.  Files and 
-folders are just like files and directories in the file system.  A folder contains other folders or files.  
-A file contains an arbitrary sequence of bytes.  Its content is not interpreted by the platform.</P>
-<P >
-A workspace's resources are organized into a tree structure, with projects at the top, and folders and files 
-underneath. A special resource, the workspace root resource, serves as the root of the resource tree. 
-The workspace root is created internally when a workspace is created and exists as long as the workspace exists.</P>
-<P >
-A workspace can have any number of projects, each of which can be stored in
-a different location on disk.</P>
-<P>
-The workspace resource namespace is always case-sensitive and  case-preserving. 
-Thus the workspace allows multiple sibling resources to exist with names that 
-differ only in case.  The workspace also doesn't put any restrictions on valid characters 
-in resource names, the length of resource names, or the size of resources on disk.  
-Of course, if you store resources on a disk that is not case-sensitive, or that does
-have restrictions on resource names, then those restrictions will show through
-when you actually try to create and modify resources.
-</P>
-<H3>
-A sample resource tree</H3>
-<P >
-The tree below (represented in the workbench navigator view) illustrates a typical hierarchy of resources in a 
-workspace. The (implied) root of the tree is the workspace root.  The projects are immediate children of the 
-workspace root.  Each node (other than the root) is one of the three kinds of resources, and each has a name that 
-is different from its siblings. </P>
-<P >
-
-<img src="images/navigator.png" alt="Navigator view with sample workspace" border="0">
-
-
- </P>
-
-
-<P >
-Resource names are arbitrary strings (almost -- they must be legal file names).  The platform itself does not dictate resource names, nor does it specify any names with special
-significance.&nbsp; (One exception is that you cannot name a project &quot;<b>.metadata</b>&quot;
-since this name is used internally.) </P>
-<P >
-Projects contain files and folders, but not other projects. Projects and folders
-are like directories in a file system.&nbsp; When you delete a project, you will
-be asked whether you want to delete all of the files and folders that it
-contains.&nbsp; Deleting a folder from a project will delete
-the folder and all of its children.  Deleting a file is analogous to deleting a file in the file system.  </P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime.htm
deleted file mode 100644
index 8b34bf9..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Runtime overview</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Runtime overview</H1>
-<p>
-The Eclipse runtime defines the plug-ins (<b>org.eclipse.osgi</b> and <b>org.eclipse.core.runtime</b>) on which all
-other plug-ins depend.  The runtime is responsible for defining a structure for plug-ins and the implementation
-detail (bundles and classloaders) behind them.  The runtime is also responsible for finding and executing the main
-Eclipse application and for maintaining a registry of plug-ins, their extensions, and extension points.
-</p>
-<p>
-The runtime also provides an assortment of utilities, such as logging, debug trace options, 
-adapters, a preference store, and a concurrency infrastructure. Of course, as 
-a minimal kernel, the runtime is only interesting once plug-ins that make use of it and
-perform some kind of task are created.  Like Atlas, the runtime plug-in stoically resides at the bottom
-of the plug-in heap, holding the Eclipse universe aloft on its steady shoulders.
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_content.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_content.htm
deleted file mode 100644
index c1d2796..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_content.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Content types</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h2>Content types</h2>
-<p>The <b><a href="../reference/api/org/eclipse/core/runtime/content/package-summary.html">org.eclipse.core.runtime.content</a></b> 
-  package provides support for detecting the content type for data streams. Content 
-  types are used by several content-sensitive features of Eclipse, such as automatic 
-  encoding determination, editor selection, and menu contributions. A central 
-  content registry allows plug-ins to request content type detection and to find 
-  out what content types are available and how they related to each other. The 
-  content type registry is extensible so plug-ins can contribute new content type 
-  definitions.</p>
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_content_contributing.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_content_contributing.htm
deleted file mode 100644
index d867f7e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_content_contributing.htm
+++ /dev/null

@@ -1,132 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Contributing content types</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h2>Contributing content types</h2>
-<h3>Providing a new content type</h3>
-<p>The platform defines some fundamental content types, such as plain text and 
-  XML. These content types are defined the same way as those contributed by any 
-  other plug-ins. We will look at how the platform defines some of its content 
-  types in order to better understand the content type framework.</p>
-<p>Plug-ins define content types by contributing an extension for the extension 
-  point <b><a href="../reference/extension-points/org_eclipse_core_runtime_contentTypes.html">org.eclipse.core.runtime.contentTypes</a></b>. 
-  In this extension, a plug-in specifies a simple id and name for the content 
-  type (the full id is always the simple id prefixed by the current namespace). 
-  The following snippet shows a trimmed down version of the <code>org.eclipse.core.runtime.text</code> 
-  content type contribution:</p>
-<pre>
-	&lt;extension point="org.eclipse.core.runtime.contentTypes"&gt;
-		&lt;content-type 
-			id="text"
-			name="%textContentTypeName"&gt;
-			file-extensions="txt"&gt;
-			&lt;describer class=&quot;org.eclipse.core.internal.content.TextContentDescriber&quot;/&gt;
-		&lt;/content-type&gt;
-		...</pre>
-<p>The <code>file-extensions</code> attribute defines what file extensions are 
-  associated with the content type (in this example, &quot;.txt&quot;). The <code>file-names</code> 
-  attribute (not used in this case) allows associating full names. Both attributes 
-  are taken into account by the platform when performing content type detection 
-  and description (if the client provides a file name).</p>
-<p>The <code>describer</code> element is used to define a <em>content describer</em> 
-  for the content type.</p>
-<h3>Detecting and describing content</h3>
-<p>A content type should provide a content describer if there are any identifiable 
-  characteristics that allow automatic content type detection, or any interesting 
-  properties in data belonging to the content type. In the case of <code>org.eclipse.core.runtime.text</code>, 
-  it is not possible to figure out the content type by just looking at the contents. 
-  However, text streams might be prepended by a <em>byte order mark</em>, which 
-  is a property clients might be interested in knowing about, so this warrants 
-  a content describer.</p>
-<p>The describer is an implementation of <b><a href="../reference/api/org/eclipse/core/runtime/content/IContentDescriber.html">IContentDescriber</a></b> 
-  or <b><a href="../reference/api/org/eclipse/core/runtime/content/ITextContentDescriber.html">ITextContentDescriber</a></b>. 
-  The latter is a specialization of the former that must be implemented by describers 
-  of text-oriented content types. Regardless the nature of the content type, the 
-  describer has two responsibilities: helping determining whether its content 
-  type is appropriate for a given data stream, and extracting interesting properties 
-  from a data stream that supposedly belongs to its content type.</p>
-<p>The method <b>describe(stream, description)</b> is called whenever the platform 
-  is trying to determine the content type for a particular data stream or describe 
-  its contents. The description is <code>null</code> when only detection is requested. 
-  Otherwise, the describer should try to fill the content description with any 
-  properties that could be found <em>by reading the stream</em>, and only those. 
-  The content type markup should be used to declare any properties that have default 
-  values (for example, <code>org.eclipse.core.runtime.xml</code> declares UTF-8 
-  as the default charset).</p>
-<p>When performing its duty, the content describer is expected to execute as quickly 
-  as possible. The less the data stream has to be read, the better. Also, <em>it 
-  is expected that the content describer implementation be declared in a package 
-  that is exempt from plug-in activation (see the <a href="../reference/misc/bundle_manifest.html">Eclipse-AutoStart</a> 
-  bundle manifest header). Since all describers are instantiated when the content 
-  type framework is initialized, failure in complying with this requirement causes 
-  premature activation, which must be avoided. Future implementations of the platform 
-  might refuse to instantiate describers if doing so would trigger activation 
-  of the corresponding plug-in.</em></p>
-<h3>Extending an existing content type</h3>
-
-<p>Content types are hierarchical in nature. This allows new content types to 
-  leverage the attributes or behavior of more general content types. For example, 
-  a content type for XML data is considered a child of the text content type: 
-</p>
-<pre>&lt;content-type 
-	id=&quot;xml&quot;
-	name=&quot;%xmlContentTypeName&quot;
-	base-type=&quot;org.eclipse.core.runtime.text&quot;
-	file-extensions=&quot;xml&quot;&gt;
-	&lt;describer class=&quot;org.eclipse.core.internal.content.XMLContentDescriber&quot;/&gt;
-	&lt;property name=&quot;charset&quot; default=&quot;UTF-8&quot;/&gt;
-&lt;/content-type&gt;</pre>
-<p>A XML file is deemed a kind of text file, so any features applicable to the 
-  latter should be applicable to the former as well.</p>
-<p>Note that the XML content type overrides several content type attributes originally 
-  defined in the Text content type such as the file associations and the describer 
-  implementation. Also, this content type declares a default property value for 
-  <code>charset</code> property. That means that during content description for 
-  a data stream considered as belonging to the XML content type, if the describer 
-  does not fill in the charset property, the platform will set it to be &quot;UTF-8&quot;.</p>
-<p>As another example, the <code>org.eclipse.ant.core.antBuildFile</code> content 
-  type (for Ant Build Scripts) extends the XML content type:</p>
-<pre>&lt;content-type  <br>	id=&quot;antBuildFile&quot; <br>	name=&quot;%antBuildFileContentType.name&quot; <br>	base-type=&quot;org.eclipse.core.runtime.xml&quot;<br>	file-names=&quot;build.xml&quot;<br>	file-extensions=&quot;macrodef,ent,xml&quot;&gt; <br>	&lt;describer <br>		class=&quot;org.eclipse.ant.internal.core.contentDescriber.AntBuildfileContentDescriber&quot;&gt;<br>	&lt;/describer&gt; <br>&lt;/content-type&gt;</pre>
-<p>Note that the default value for the charset property is inherited. It is possible 
-  to cancel an inherited property or describer by redeclaring them with the empty 
-  string as value.</p>
-<h4>Additional file associations</h4>
-<p>New file associations can be added to existing content types. For instance, 
-  the Resources plug-in associates the <code>org.eclipse.core.runtime.xml</code> 
-  to &quot;.project&quot; files:</p>
-<pre>&lt;extension point="org.eclipse.core.runtime.contentTypes"&gt;
-	&lt;file-association content-type=&quot;org.eclipse.core.runtime.xml&quot; file-names=&quot;.project&quot;/&gt;
-	...
-</pre>
-<h4>Content type aliasing</h4>
-<p>Due to the extensible nature of Eclipse, a content type a plug-in rely on may 
-  not be available in a given product configuration. This can be worked around 
-  by using content type aliasing. A <em>content type alias</em> is a placeholder 
-  for another preferred content type whose availability is not guaranteed. For 
-  instance, the Runtime declares an alias (<code>org.eclipse.core.runtime.properties</code>) 
-  for the Java properties content type provided by the Java Development Tooling 
-  (<code>org.eclipse.jdt.core.javaProperties</code>):</p>
-<pre>&lt;!-- a placeholder for setups where JDT's official type is not available --&gt;			<br>&lt;content-type 
-	id=&quot;properties&quot; 
-	name=&quot;%propertiesContentTypeName&quot; <br>	base-type=&quot;org.eclipse.core.runtime.text&quot;<br>	alias-for=&quot;org.eclipse.jdt.core.javaProperties&quot;<br>	file-extensions=&quot;properties&quot;&gt;<br>	&lt;property name=&quot;charset&quot; default=&quot;ISO-8859-1&quot;/&gt;<br>&lt;/content-type&gt;		</pre>
-
-
-
-<p>This provides plug-ins with a placeholder they can refer to regardless the 
-  preferred content type is available or not. If it is, the alias content type 
-  is supressed from the content type catalog and any references to it are interpreted 
-  as references to the target content type. If it is not, the alias will be used 
-  as an ordinary content type.</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_content_using.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_content_using.htm
deleted file mode 100644
index 3c7ea2c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_content_using.htm
+++ /dev/null

@@ -1,91 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Using content types</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h2>Using content types</h2>
-<blockquote><i> Note:&nbsp; For this discussion, we specifically avoid the use 
-  of the word <b>file</b> when talking about content. The runtime content engine 
-  does not assume that content is contained in a file in the file system. However, 
-  it does include protocol that allows content types to be associated with file-naming 
-  patterns. In practice, these file names represent files in the file system, 
-  but nothing in the implementation of the content system assumes that the content 
-  is located in the file system. <a HREF="resInt_content.htm">File encoding and 
-  content types</a> discusses the file-oriented content type capabilities contributed 
-  by the platform resources plug-in and is a must-read for developers interested 
-  in using the content type API in that context.</i></blockquote>
-<h3>Finding out about content types</h3>
-<p>Content types are represented by <b><a href="../reference/api/org/eclipse/core/runtime/content/IContentType.html">IContentType</a></b>. 
-  This interface represents a unique content type that knows how to read a data 
-  stream and interpret content type-specific information. Content types are hierarchical 
-  in nature. For example, a content type for XML data is considered a child of 
-  the text content type. This allows new content types to leverage the attributes 
-  or behavior of more general content types. </p>
-<p>The <b><a href="../reference/api/org/eclipse/core/runtime/content/IContentTypeManager.html">IContentTypeManager</a></b> 
-  is the entry point that gives access to most of the content type related API 
-  provided by the platform runtime. To obtain a reference to the platform <b><a href="../reference/api/org/eclipse/core/runtime/content/IContentTypeManager.html">IContentTypeManager</a></b>, 
-  clients can use the <b><a href="../reference/api/org/eclipse/core/runtime/Platform.html">Platform</a></b> 
-  API:</p>
-<pre>IContentTypeManager contentTypeManager = Platform.getContentTypeManager();</pre>
-<p> Clients can use the platform <b><a href="../reference/api/org/eclipse/core/runtime/content/IContentTypeManager.html">IContentTypeManager</a></b> 
-  to find out about the content types in the system. </p>
-<ul>
-  <li><b>getAllContentTypes</b> allows clients to get all of the content types 
-    defined in the platform. </li>
-  <li><b>getContentType</b> allows clients to obtain a content type by its unique 
-    identifier.</li>
-</ul>
-<h3>Detecting the content type for a data stream</h3>
-<p>Given a stream of bytes, it is possible to determine its content type by calling 
-  the <b><a href="../reference/api/org/eclipse/core/runtime/content/IContentTypeManager.html">IContentTypeManager</a></b> 
-  API as follows:</p>
-<pre>
-InputStream stream = ...;
-IContentType contentType = contentTypeManager.findContentTypeFor(stream, &quot;file.xml&quot;);
-stream.close();
-</pre>
-<p>This will return the most appropriate <a href="../reference/api/org/eclipse/core/runtime/content/IContentType.html"><strong>IContentType</strong></a> 
-  given the input provided, or <code>null</code> if none can be found. Multiple 
-  content types might be deemed appropriate for a given data stream. In that case, 
-  the platform uses some heuristics to determine which one should be selected. 
-  The file name is the first criterion by which content types are selected. It 
-  can be omitted, but this has two issues: the results might not be as correct 
-  because many unrelated content types might accept the same input; there is also 
-  a big performance hit, since all content types in the platform have to be given 
-  a chance of analysing the stream. So, unless it is not available, clients should 
-  always provide a file name along with the stream.</p>
-<h3>Describing a data stream</h3>
-<p>Another interesting feature of the content type support in the platform is 
-  the ability of <em>describing the contents</em> of a binary or character stream. 
-  The following code snippet shows how to do that:</p>
-<pre>InputStream stream = ...; 
-IContentDescription description = contentTypeManager.getDescriptionFor(stream, &quot;file.xml&quot;);
-stream.close();</pre>
-<p>The returned <strong><a href="../reference/api/org/eclipse/core/runtime/content/IContentDescription.html">IContentDescription</a></strong> 
-  instance describes the content type and additional relevant information extracted 
-  from the contents provided. The content description stores content-specific 
-  properties in form of key/value pairs. The platform itself is able to describe 
-  properties such as the character set and the byte order of text-based streams, 
-  but others can be defined by content type providers.</p>
-<h3>Providing content-sensitive features</h3>
-<p>New content types are often defined as specialization of existing ones. This 
-  hierarchy establishes a &quot;is a&quot; relationship between a derived content 
-  type and its base type. Plug-in developers must honor this when implementing 
-  content sensitive features. If a given feature is applicable to a given content 
-  type, the feature must be applicable to any derived content types as well. The 
-  <strong>IContentType.isKindOf(IContentType superType) </strong>method allows 
-  determining whether two <a href="../reference/api/org/eclipse/core/runtime/content/IContentType.html"><strong>IContentType</strong></a>s 
-  are related. The method <strong>IContentType.getBaseType()</strong> allows determining 
-  the base type of a given <a href="../reference/api/org/eclipse/core/runtime/content/IContentType.html"><strong>IContentType</strong></a>.</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs.htm
deleted file mode 100644
index e93e3d2..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs.htm
+++ /dev/null

@@ -1,222 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Concurrency infrastructure</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Concurrency infrastructure</H2>
-<p>
-One of the major challenges of a complex system is to remain responsive while tasks are being performed.  This
-challenge is even greater in an extensible system, when components that weren't designed to run together are
-sharing the same resources.  The
-<b><a href="../reference/api/org/eclipse/core/runtime/jobs/package-summary.html"> org.eclipse.core.runtime.jobs</a></b> 
-package addresses this challenge by providing infrastructure for scheduling, executing, and managing 
-concurrently running operations.   This infrastructure is based on the use of <i>jobs</i> to represent
-a unit of work that can run asynchronously.</p>
-<h3>Jobs</h3>
-The <b><a href="../reference/api/org/eclipse/core/runtime/jobs/Job.html">Job</a></b> class represents
-a unit of asynchronous work running concurrently with other jobs.  To perform a task, a plug-in creates 
-a job and then <i>schedules</i> it.  Once a job is scheduled, it is added to a job queue managed by the 
-platform.  The platform uses a background scheduling thread to manage all of the pending jobs.  As a running
-job completes, it is removed from the queue and the platform decides which job to run next.  When a job 
-becomes active, the platform invokes its <b>run()</b> method.  Jobs are best demonstrated with a simple example:
-<pre>
-   class TrivialJob extends Job {
-      public TrivialJob() {
-         super("Trivial Job");
-      }
-      public IStatus run(IProgressMonitor monitor) {
-         System.out.println("This is a job");
-         return Status.OK_STATUS;
-      }
-   }
-</pre>
-The job is created and scheduled in the following snippet:
-<pre>
-   TrivialJob job = new TrivialJob();
-   System.out.println("About to schedule a job");
-   job.schedule();
-   System.out.println("Finished scheduling a job");
-</pre>
-The output of this program is timing dependent.  That is, there is no way
-to be sure when the job's <b>run</b> method will execute in relation
-to the thread that created the job and scheduled it.  The output will
-either be:
-<pre>
-   About to schedule a job
-   This is a job
-   Finished scheduling a job
-</pre>
-or:
-<pre>
-   About to schedule a job
-   Finished scheduling a job
-   This is a job
-</pre>
-
-<p>
-If you want to be certain that a job has completed before continuing, you can use
-the <b>join()</b> method.  This method will block the caller until the job has completed, or 
-until the calling thread is interrupted.  Let's rewrite our snippet from above in a more 
-deterministic manner:
-</p>
-<pre>   TrivialJob job = new TrivialJob();
-   System.out.println("About to schedule a job");
-   job.schedule();
-   job.join();
-   if (job.getResult().isOk())
-      System.out.println("Job completed with success");
-   else
-      System.out.println("Job did not complete successfully");
-</pre>
-Assuming the <b>join()</b> call is not interrupted, this method is guaranteed to
-return the following result:
-<pre>
-   About to schedule a job
-   This is a job
-   Job completed with success
-</pre>
-<p>
-Of course, it is generally not useful to join a job immediately after scheduling it,
-since you obtain no concurrency by doing so. In this case you might as well do the work
-from the job's run method directly in the calling thread.  We'll look at some examples later on where 
-the use of join makes more sense.
-</p>
-<p>
-The last snippet also makes use of the job <b>result</b>.  The result
-is the <b><a href="../reference/api/org/eclipse/core/runtime/IStatus.html">IStatus</a></b>
-object that is returned from the job's <b>run()</b> method.  You can use this result
-to pass any necessary objects back from the job's run method.  The result can also be used to
-indicate failure (by returning an <b><a href="../reference/api/org/eclipse/core/runtime/IStatus.html">IStatus</a></b>
-with severity <b>IStatus.ERROR</b>), or cancellation (<b>IStatus.CANCEL</b>).
-</p>
-<h3>Common job operations</h3>
-<p>
-We've seen how to schedule a job and wait for it complete, but there are many other
-interesting things you can to do jobs.  If you
-schedule a job but then decide it is no longer needed, the job can be stopped using
-the <b>cancel()</b> method.  If the job has not yet started running when canceled,
-the job is immediately discarded and will not run.  If, on the other hand, the job 
-has already started running, it is up to the job whether it wants to respond to the cancellation.
-When you are trying to cancel a job, waiting for it using the <b>join()</b> method comes in handy.
-Here is a common idiom for canceling a job, and waiting until the job is finished before
-proceeding:</p>
-<pre>   if (!job.cancel())
-      job.join();
-</pre>
-<p>If the cancellation does not take effect immediately, then <b>cancel()</b> will return 
-false and the caller will use <b>join()</b> to wait for the job to successfully cancel.
-</p>
-<p>
-Slightly less drastic than cancellation is the <b>sleep()</b> method.  Again,
-if the job has not yet started running, this method will cause the
-job to be put on hold indefinitely.  The job will still be remembered by the platform,
-and a <b>wakeUp()</b> call will cause the job to be added to the wait
-queue where it will eventually be executed. 
-</p>
-<h3>Job states</h3>
-<p>
-A job goes through several states during its lifetime.  Not only can it be manipulated through API
-such as <b>cancel()</b> and <b>sleep()</b>, but its state also changes as the platform runs and completes the
-job.  Jobs can move through the following states:</p>
-<ul>
-<li><b>WAITING</b> indicates that the job been scheduled to run, but is not running yet.</li>
-<li><b>RUNNING</b> indicates that the job is running.</li>
-<li><b>SLEEPING</b> indicates that the job is sleeping due to a sleep request or because it was scheduled
-to run after a certain delay.</li>
-<li><b>NONE</b> indicates that the job is not waiting, running, or sleeping.  A job is in this state when
-it has been created but is not yet scheduled.  It is also in this state after it is finished running or when
-it has been canceled.</li>
-</ul>
-<p>A job can only be put to sleep if it is currently <b>WAITING</b>.  Waking up a sleeping job will put it back in the
-<b>WAITING</b> state.  Canceling a job will return it to the <b>NONE</b> state.
-</p>
-<p>
-If your plug-in needs to know the state of a particular job, it can register a <i>job change listener</i> that is
-notified as the job moves through its life-cycle.  This is useful for showing progress or otherwise reporting on
-a job.  
-</p>
-<h3>Job change listeners</h3>
-<p>
-The <b><a href="../reference/api/org/eclipse/core/runtime/jobs/Job.html">Job</a></b> method
-<b>addJobChangeListener</b> can be used to register a listener on a particular job.  
-<b><a href="../reference/api/org/eclipse/core/runtime/jobs/IJobChangeListener.html">IJobChangeListener</a></b>
-defines protocol for responding to the state changes in a job:
-</p>
-<ul>
-<li><b>aboutToRun</b> is sent when the job is about to be run.</li>
-<li><b>awake</b> is sent when a previously sleeping job is now waiting to be run.</li>
-<li><b>done</b> is sent when a job finishes execution.</li>
-<li><b>running</b> is sent when a job starts running.</li>
-<li><b>scheduled</b> is sent when a job is scheduled and waiting in the queue of jobs.</li>
-<li><b>sleeping</b> is sent when a waiting job is put to sleep.</li>
-</ul>
-<p>In all of these cases, the listener is provided with an
-<b><a href="../reference/api/org/eclipse/core/runtime/jobs/IJobChangeEvent.html">IJobChangeEvent</a></b>
-that specifies the job undergoing the state change and status on its completion (if it is done).
-</p>
-<blockquote><i>
-Note:  Jobs also define the <b>getState()</b> method for obtaining the (relatively) current
-state of a job.  However, this result is not always reliable since jobs run in a different thread and may
-change state again by the time the call returns.  Job change listeners are the recommended mechanism
-for discovering state changes in a job.
-</i></blockquote>
-<h3>The job manager</h3>
-<p>
-<b><a href="../reference/api/org/eclipse/core/runtime/jobs/IJobManager.html">IJobManager</a></b>
-defines protocol for working with all of the jobs in the system.  Plug-ins that show progress or otherwise
-work with the job infrastructure can use <b><a href="../reference/api/org/eclipse/core/runtime/jobs/IJobManager.html">IJobManager</a></b>
-to perform tasks such as suspending all jobs in the system, finding out which job is running, or receiving progress
-feedback about a particular job.  The platform's job manager can be obtained using 
-<b><a href="../reference/api/org/eclipse/core/runtime/Platform.html">Platform</a></b> API:</p>
-<pre>   IJobManager jobMan = Platform.getJobManager();
-</pre>
-<p>Plug-ins interested in the state of all jobs in the system can register a job change listener on the job manager rather
-than registering listeners on many individual jobs.  
-</p>
-<h3>Job families</h3>
-<p>
-It is sometimes easier for a plug-in to work with a group of related jobs as a single unit.
-This can be accomplished using <i>job families</i>.  A job declares that it belongs to a certain family by 
-overriding the <b>belongsTo</b> method:</p>
-<pre>
-   public static final String MY_FAMILY = "myJobFamily";
-   ...
-   class FamilyJob extends Job {
-      ...
-      public boolean belongsTo(Object family) {
-         return family == MY_FAMILY;
-      }
-   }
-</pre>
-<b><a href="../reference/api/org/eclipse/core/runtime/jobs/IJobManager.html">IJobManager</a></b>
-protocol can be used to cancel, join, sleep, or find all jobs in a family:
-<pre>
-   IJobManager jobMan = Platform.getJobManager();
-   jobMan.cancel(MY_FAMILY);
-   jobMan.join(MY_FAMILY, null);
-</pre>
-<p>Since job families are represented using arbitrary objects, you can store interesting
-state in the job family itself, and jobs can dynamically build family objects as needed.
-It is important to use family objects that are 
-fairly unique, to avoid accidental interaction with the families created by
-other plug-ins. 
-</p>
-<p>
-Families are also a convenient way of locating groups of jobs.  The method <b>IJobManager.find(Object family)</b> can
-be used to locate instances of all running, waiting, and sleeping jobs at any
-given time.
-</p>
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_locks.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_locks.htm
deleted file mode 100644
index cc7ff30..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_locks.htm
+++ /dev/null

@@ -1,77 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Locks</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-Locks</H3>
-<p>
-It's possible that multiple jobs in the system need to access and manipulate the same object.
-<b><a href="../reference/api/org/eclipse/core/runtime/jobs/ILock.html">ILock</a></b> defines protocol
-for granting exclusive access to a shared object.  When a job needs access to the shared object, it <i>acquires</i> a lock
-for that object.  When it is finished manipulating the object, it <i>releases</i> the lock. 
-</p>
-<p>A lock is typically created when the shared object is created or first accessed by a plug-in.  That is, code that
-has a reference to the shared object also has a reference to its lock.  We'll start by creating a lock, <b>myLock</b>, that
-will be used to control access to <b>myObject</b>:
-</p>
-<pre>   ...
-   myObject = initializeImportantObject();
-   IJobManager jobMan = Platform.getJobManager();
-   <b>myLock = jobMan.newLock();</b>
-   ...
-</pre>
-<p>A robust implementation of  <b><a href="../reference/api/org/eclipse/core/runtime/jobs/ILock.html">ILock</a></b> 
-is provided by the platform.  The job manager provides instances of this lock for use by clients.  These locks
-are aware of each other and can avoid circular deadlock.(We'll explain more about that statement in a moment.)
-</p>
-<p>Whenever code in a job requires access to <b>myObject</b>, it must first acquire 
-the lock on it.  The following snippet shows a common idiom for working with a lock:
-</p>
-<pre>...
-// I need to manipulate myObject, so I get its lock first.
-try {		
-	<b>myLock.acquire();</b>
-	updateState(myObject);  // manipulate the object
-} finally {
-	<b>lock.release();</b>
-}
-...
-</pre>
-<p>The <b>acquire()</b> method will not return until the calling job can be granted exclusive access to the lock.  
-In other words, if some other job has already acquired the lock, then this code will be blocked until the lock 
-is available.  Note that the code that acquires the lock and manipulates <b>myObject</b> is wrapped in 
-a <tt>try</tt> block, so that the lock can be released if any exceptions occur while working with the object.  
-</p>
-<p>Seems simple enough, right?  Fortunately, locks are pretty straightforward to use.  They are also reentrant, which
-means you don't have to worry about your job acquiring the same lock multiple times.  Each lock keeps a count of the
-number of acquires and releases for a particular thread, and will only release from a job when the number of 
-releases equals the number of acquires.
-</p>
-<h4>Deadlock</h4>
-<p>Earlier we noted that locks provided by the job manager are aware of each other and can avoid circular deadlock. 
-To understand how deadlock occurs, let's look at a simple scenario.  Suppose &quot;Job A&quot; acquires &quot;Lock A&quot; and 
-subsequently tries to acquire &quot;Lock B.&quot; Meanwhile, &quot;Lock B&quot; is held by &quot;Job B&quot; 
-which is now blocked waiting on &quot;Lock A.&quot;  This kind of deadlock indicates an underlying design problem
-with the use of the locks between the jobs.  While this simple case can be avoided easily enough, the chances
-of accidentally introducing deadlock increase as the number of jobs and locks used in your design increase.  
-</p> 
-<p>Fortunately, the platform will help you in identifying deadlocks.  When the job manager detects a deadlock 
-condition, it prints diagnostic information to the log describing the deadlock condition.  Then it breaks the 
-deadlock by temporarily granting access to the locks owned by a blocked job to other jobs that are waiting on them.  
-It is important to carefully test any implementation involving multiple locks and fix any deadlock conditions that
-are reported by the platform.
-</P>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_progress.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_progress.htm
deleted file mode 100644
index 8830a35..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_progress.htm
+++ /dev/null

@@ -1,157 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Reporting progress</title>
-  <link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-<body bgcolor="#ffffff">
-<h3>
-Reporting progress</h3>
-<p>
-Long running jobs (those lasting more than a second) should report
-progress to the
-<b><a
- href="../reference/api/org/eclipse/core/runtime/IProgressMonitor.html">IProgressMonitor</a></b>
-that is passed to the job's <b>run</b> method. The workbench progress
-view will
-show all progress messages and units of completed work given to this
-monitor. </p>
-<p>The supplied progress monitor should also be used to check for
-cancellation requests made from the progress view. When a user (or
-plug-in using job API) attempts to cancel a job, the <b><a
- href="../reference/api/org/eclipse/core/runtime/IProgressMonitor.html">IProgressMonitor</a></b>
-method <b>isCanceled()</b> will return <tt>true</tt>. It is the job's
-responsibility to frequently
-check the cancellation status of a job and respond to a cancellation by
-exiting the <b>run</b> method as soon as possible once it detects a
-cancellation. The following <b>run</b> method reports progress
-and responds to job cancellation:
-</p>
-<pre>   public IStatus run(IProgressMonitor monitor) {
-      final int ticks = 6000;
-      monitor.<b>beginTask</b>("Doing some work", ticks);
-      try {
-         for (int i = 0; i &lt; ticks; i++) {
-            if (monitor.<b>isCanceled</b>())
-               return Status.CANCEL_STATUS;
-            monitor.<b>subTask</b>("Processing tick #" + i);
-            //... do some work ...
-            monitor.<b>worked</b>(1);
-         }
-      } finally {
-         monitor.<b>done</b>();
-      }
-      return Status.OK_STATUS;<br>   }
-</pre>
-<p>The <b>beginTask</b> method is used to name the task in the
-corresponding progress view and to
-establish the total amount of work to be done so that the view can
-compute progress. The
-<b>subTask</b> messages will appear as a child in the progress tree as
-work is done. The progress view will calculate and display a percent
-completion based on the amount of work
-reported in the <b>worked</b> calls.
-</p>
-<h3>Progress monitors and the UI</h3>
-<p>
-As you can see, the <b><a
- href="../reference/api/org/eclipse/core/runtime/IProgressMonitor.html">IProgressMonitor</a></b>
-class is designed with corresponding UI support in mind. The platform's
-UI plug-in provides support so that
-the workbench can show progress for jobs that are running. You can set
-up your jobs with this in mind, so that
-you can control how they are presented.<br>
-</p>
-<p>See <a href="workbench_jobs.htm">Workbench Concurrency Support</a>
-for a detailed look at the APIs available for showing progress for jobs.<br>
-</p>
-<h4>System jobs</h4>
-
-<p>What if your job is a low-level implementation detail that you don't
-want to show to users? You can flag your job as a <i>system job</i>. A
-system job is just like any other job, except the corresponding UI
-support will not set up a progress view or show any other UI
-affordances associated with running a job. If your job is not either
-directly initiated by a user, or a periodic task that can be configured
-by a user, then your job should be a system job. The protocol for
-setting a system job is simple:
-</p>
-<pre>   class TrivialJob extends Job {
-      public TrivialJob() {
-         super("Trivial Job");
-         <b>setSystem(true)</b>;
-      }
-      ...
-   }
-</pre>
-<p>The <b>setSystem</b> call must be made before the job is
-scheduled. An exception will be triggered if you attempt this call on a
-job that is currently waiting, sleeping, or running.
-</p>
-<h4>User jobs</h4>
-
-<p>If your job is a long running operation that is initiated by a user,
-then you should flag your job as a <i>user job</i>. A user job will
-appear in a modal progress dialog that provides a button
-for moving the dialog into the background. The workbench defines a user
-preference that controls whether
-these dialogs are ever modal. By defining your job as a user job, your
-progress feedback will
-automatically conform with the user preference for progress viewing.
-The protocol for setting a user job
-is similar:
-</p>
-<pre>   class TrivialJob extends Job {
-      public TrivialJob() {
-         super("Trivial Job");
-         <b>setUser(true)</b>;
-      }
-      ...
-   }
-</pre>
-<p>The <b>setUser</b> call must also be made before the job is scheduled. 
-</p>
-
-<h3>Progress groups</h3>
-
-<p><i>Progress groups</i> are another mechanism that can be used to
-influence the way that a job is shown in the UI. When it is more
-appropriate to show the aggregate progress of several related jobs in
-the UI, a special
-<b><a
- href="../reference/api/org/eclipse/core/runtime/IProgressMonitor.html">IProgressMonitor</a></b>
-that represents
-a group of related jobs can be created. This monitor is created using <b><a
- href="../reference/api/org/eclipse/core/runtime/jobs/IJobManager.html">IJobManager</a></b>
-protocol. The following snippet shows how to create a progress group
-and associate it with a job.
-</p>
-<pre>   ...
-   IJobManager jobMan = Platform.getJobManager();
-   myGroup = jobMan.createProgressGroup();
-   job.setProgressGroup(myGroup, 600);  // specify the units of work the job needs to show.
-   job.schedule()
-   ...
-</pre>
-<p>The group facility allows plug-ins to break tasks into multiple
-jobs if needed, but to report them to the user as if
-they are a single task. The progress group monitor will handle the
-details for computing the percentage completion
-relative to all of the jobs in the group.
-</p>
-<p>A job must be placed into the progress group before it is scheduled.
-After a job finishes running, its reference to the progress group is
-lost. If the job is to be scheduled again, it must be set into the
-group
-once again before it is scheduled.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_rules.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_rules.htm
deleted file mode 100644
index 02248a2..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_rules.htm
+++ /dev/null

@@ -1,228 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Scheduling rules</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-Scheduling rules</H3>
-<p>
-Job <i>scheduling rules</i> can be used to control when your jobs run in relation to
-other jobs. In particular, scheduling rules allow you to prevent multiple jobs
-from running concurrently in situations where concurrency can lead to inconsistent
-results. They also allow you to guarantee the execution order of a series of jobs.
-The power of scheduling rules is best illustrated by an example. Let's start by 
-defining two jobs that are used to turn a light switch on and off concurrently:</p>
-<pre>   public class LightSwitch {
-      private boolean isOn = false;
-      public boolean isOn() {
-         return isOn;
-      }
-      public void on() {
-         new LightOn().schedule();
-      }
-      public void off() {
-         new LightOff().schedule();
-      }
-      class LightOn extends Job {
-         public LightOn() {
-            super("Turning on the light");
-         }
-         public IStatus run(IProgressMonitor monitor) {
-            System.out.println("Turning the light on");
-            isOn = true;
-            return Status.OK_STATUS;
-         }
-      }
-      class LightOff extends Job {
-         public LightOff() {
-            super("Turning off the light");
-         }
-         public IStatus run(IProgressMonitor monitor) {
-            System.out.println("Turning the light off");
-            isOn = false;
-            return Status.OK_STATUS;
-         }
-      }
-   }
-</pre>
-<p>Now we create a simple program that creates a light switch and turns it
-on and off again:</p>
-<pre>   LightSwitch light = new LightSwitch();
-   light.on();
-   light.off();
-   System.out.println("The light is on? " + switch.isOn());
-</pre>
-<p>If we run this little program enough times, we will eventually obtain the following output:</p>
-<pre>   Turning the light off
-   Turning the light on
-   The light is on? true
-</pre>
-<p>How can that be?  We told the light to turn on and then off, so its final state
-should be off!  The problem is that there was nothing preventing the
-<tt>LightOff</tt> job from running at the same time as the <tt>LightOn</tt>
-job.  So, even though the &quot;on&quot; job was scheduled first, their
-concurrent execution means that there is no way to predict the exact
-execution order of the two concurrent jobs. If the <tt>LightOff</tt> job ends
-up running before the <tt>LightOn</tt> job, we get this invalid result.
-What we need is a way to prevent the two jobs from running concurrently, and 
-that's where scheduling rules come in.</p>
-<p>
-We can fix this example by creating a simple scheduling rule that acts as a 
-<i>mutex</i> (also known as a <i>binary semaphore</i>):</p>
-<pre>   class Mutex implements ISchedulingRule {
-      public boolean isConflicting(ISchedulingRule rule) {
-         return rule == this;
-      }
-      public boolean contains(ISchedulingRule rule) {
-         return rule == this;
-      }
-   }
-</pre>
-<p>This rule is then added to the two light switch jobs from our previous example:</p>
-<pre>   public class LightSwitch {
-      <b>final MutextRule rule = new MutexRule();</b>
-      ...
-      class LightOn extends Job {
-         public LightOn() {
-            super("Turning on the light");
-            <b>setRule(rule);</b>
-         }
-         ...
-      }
-      class LightOff extends Job {
-         public LightOff() {
-            super("Turning off the light");
-            <b>setRule(rule);</b>
-         }
-         ...
-      }
-   }
-</pre>
-<p>
-Now, when the two light switch jobs are scheduled, the job infrastructure will
-call the <tt>isConflicting</tt> method to compare the scheduling rules of the
-two jobs. It will notice that the two jobs have conflicting scheduling rules, and 
-will make sure that they run in the correct order. It will also make sure they never
-run at the same time. Now, if you run the example program a million times,
-you will always get the same result:</p>
-<pre>   Turning the light on
-   Turning the light off
-   The light is on? false
-</pre>
-<p>
-Rules can also be used independently from jobs as a general locking mechanism.
-The following example acquires a rule within a try/finally block, preventing other
-threads and jobs from running with that rule for the duration between 
-invocations of <tt>beginRule</tt> and <tt>endRule</tt>.</p>
-<pre>   IJobManager manager = Platform.getJobManager();
-   try {
-      manager.beginRule(rule, monitor);
-      ... do some work ...
-   } finally {
-      manager.endRule(rule);
-   }
-</pre>
-<p>You should exercise extreme caution when acquiring and releasing scheduling
-rules using such a coding pattern. If you fail to end a rule for which you
-have called <tt>beginRule</tt>, you will have locked that rule forever.</p>
-<H3>Making your own rules</H3>
-<p>
-Although the job API defines the contract of scheduling rules, it does not actually
-provide any scheduling rule implementations. Essentially, the generic infrastructure
-has no way of knowing what sets of jobs are ok to run concurrently. By default,
-jobs have no scheduling rules, and a scheduled job is executed as fast as a 
-thread can be created to run it.</p> 
-<p>
-When a job does have a scheduling rule,
-the <tt>isConflicting</tt> method is used to determine if the rule conflicts with
-the rules of any jobs that are currently running. Thus, your implementation
-of <tt>isConflicting</tt> can define exactly when it is safe to execute your job.
-In our light switch example, the <tt>isConflicting</tt> implementation simply uses
-an identity comparison with the provided rule. If another job has the identical rule,
-they will not be run concurrently.  When writing your own scheduling rules, be
-sure to read and follow the API contract for <tt>isConflicting</tt> carefully.</p>
-<p>
-If your job has several unrelated constraints, you can compose multiple
-scheduling rules together using a 
-<a href="../reference/api/org/eclipse/core/runtime/jobs/MultiRule.html">MultiRule</a>.
-For example, if your job needs to turn on a light switch, and also write information to
-a network socket, it can have a rule for the light switch and a rule for write access to the socket,
-combined into a single rule using the factory method <tt>MultiRule.combine</tt>.</p>
-<H3>Rule hierarchies</H3>
-<p>
-We have discussed the <tt>isConflicting</tt> method on 
-<a href="../reference/api/org/eclipse/core/runtime/jobs/ISchedulingRule.html">ISchedulingRule</a>,
-but thus far have not mentioned the <tt>contains</tt> method. This method is
-used for a fairly specialized application of scheduling rules that many clients will not require.
-Scheduling rules can be logically composed into hierarchies for controlling access to
-naturally hierarchical resources. The simplest example to illustrate this concept is
-a tree-based file system. If an application wants to acquire an exclusive lock
-on a directory, it typically implies that it also wants exclusive access to the files
-and sub-directories within that directory. The <tt>contains</tt> method is
-used to specify the hierarchical relationship among locks. If you do not need
-to create hierarchies of locks, you can implement the <tt>contains</tt> method
-to simply call <tt>isConflicting</tt>.</p>
-<p>
-Here is an example of a hierarchical lock for controlling write access to <tt>java.io.File</tt> handles.
-</p>
-<pre>   public class FileLock implements ISchedulingRule {
-      private String path;
-      public FileLock(java.io.File file) {
-         this.path = file.getAbsolutePath();
-      }
-      public boolean <b>contains</b>(ISchedulingRule rule) {
-         if (this == rule)
-            return true;
-         if (rule instanceof FileLock)
-            return path.startsWith(((FileLock) rule).path);
-         if (rule instanceof MultiRule) {
-            MultiRule multi = (MultiRule) rule;
-            ISchedulingRule[] children = multi.getChildren();
-            for (int i = 0; i &lt; children.length; i++)
-               if (!contains(children[i]))
-                  return false;
-               return true;
-            }
-         return false;
-      }
-      public boolean <b>isConflicting</b>(ISchedulingRule rule) {
-         if (!(rule instanceof FileLock))
-            return false;
-         String otherPath = ((FileLock)rule).path;
-         return path.startsWith(otherPath) || otherPath.startsWith(path);
-      }
-   }
-</pre>
-<p>The <tt>contains</tt> method comes into play if a thread tries to acquire
-a second rule when it already owns a rule. To avoid the possibility of deadlock,
-any given thread can only own <em>one</em> scheduling rule at any given time.
-If a thread calls <tt>beginRule</tt> when it already owns a rule, either through 
-a previous call to <tt>beginRule</tt> or by executing a job with a scheduling rule, 
-the <tt>contains</tt> method is consulted to see if the two rules are equivalent.
-If the <tt>contains</tt> method for the rule that is already owned returns <tt>true</tt>,
-the <tt>beginRule</tt> invocation will succeed. If the <tt>contains</tt> method returns
-<tt>false</tt> an error will occur.</p>
-<p>
-To put this in more concrete terms, say a thread owns our example <tt>FileLock</tt>
-rule on the directory at &quot;c:\temp&quot;. While it owns this rule, it is only allowed
-to modify files within that directory subtree. If it tries to modify files in other directories that
-are not under &quot;c:\temp&quot;, it should fail. Thus a scheduling rule is a 
-concrete specification for what a job or thread is allowed or not allowed to do. 
-Violating that specification will result in a runtime exception. In
-concurrency literature, this technique is known as <i>two-phase locking</i>. In a
-two-phase locking scheme, a process much specify in advance all locks it will need for a particular
-task, and is then not allowed to acquire further locks during the operation. Two-phase locking eliminates
-the hold-and-wait condition that is a prerequisite for circular wait deadlock. Therefore, it is impossible
-for a system using only scheduling rules as a locking primitive to enter a deadlock.
-</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_scheduling.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_scheduling.htm
deleted file mode 100644
index b3f571a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_scheduling.htm
+++ /dev/null

@@ -1,106 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Job scheduling</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-Job scheduling</H3>
-<p>
-Our examples so far have demonstrated simple job creation, scheduling, and progress reporting.  
-The job scheduling mechanism is actually more powerful than we've shown so far.  You can have more
-fine-grained control over the way your job is scheduled by using priorities, delays, and custom
-scheduling conditions.
-</p>
-<h4>
-Job priorities</h4>
-<p>
-A job <i>priority</i> can be used to establish the importance of a job relative to other jobs in the
-system.  Setting the priority of a job won't affect a job that is already running, but it will affect how
-a waiting job is scheduled relative to other jobs.  The priority of a job can be one of several pre-defined
-priority constants:</p>
-<ul>
-<li><b>INTERACTIVE</b> jobs generally have priority over other jobs.  They should be short-running or low
-on processor usage, so that they don't block other INTERACTIVE jobs from running.</li>
-<li><b>SHORT</b> jobs typically complete within a second, but may take a little longer.  They run in the
-background and have priority over all jobs except INTERACTIVE jobs. </li>
-<li><b>LONG</b> jobs are for longer running background jobs.  They run only after INTERACTIVE and
-SHORT jobs have been run. </li>
-<li><b>BUILD</b> jobs are for jobs associated with building tasks.  They are a lower priority than LONG.  BUILD jobs
-only run when all LONG jobs are complete.</li>
-<li><b>DECORATE</b> jobs are the lowest priority in the system.  They are used for tasks that provide information that
-may help supplement the UI, but that the user is not generally waiting for.</li>
-</ul>
-<p>The default priority for a job is LONG.  The following snippet creates the trivial job we used earlier, 
-but sets the priority to DECORATE to indicate that it is the lowest level priority:
-</p>
-<pre>   TrivialJob job = new TrivialJob();
-   <b>job.setPriority(Job.DECORATE);</b>
-   job.schedule();
-</pre>
-
-<h4>Scheduling with a delay</h4>
-
-<p>Another technique for controlling how a job is scheduled is to use a scheduling delay.  A scheduling delay
-can be specified when the job is scheduled.  The job will be delayed for the specified number of milliseconds
-before it is scheduled.
-</p>
-<pre>   TrivialJob job = new TrivialJob();
-   <b>job.schedule(1000);  // wait one second before scheduling</b>
-</pre>
-
-<h4>Rescheduling a job</h4>
-
-<p>Scheduling a job that is already waiting or is sleeping has no effect.  However, scheduling a job that is 
-already running will cause it to be rescheduled after it is finished.  This is a convenient mechanism for
-repetitive jobs such as background polling loops.  If the job is rescheduled multiple 
-times while it is running, it will only be rescheduled once with the most recently supplied delay.  The
-following snippet defines a job that reschedules itself to run 10 seconds after it finishes the
-current iteration.
-</p>
-<pre>   class RepetitiveTrivialJob extends Job {
-      public RepetitiveTrivialJob() {
-         super("Repetitive Trivial Job");
-      }
-      public IStatus run(IProgressMonitor monitor) {
-         System.out.println("Running the job.");
-         // reschedule after 10 seconds
-         <b>schedule(10000);</b>
-         return Status.OK_STATUS;
-      }
-   }
-</pre>
-
-<h4>Custom scheduling conditions</h4>
-
-<p>Additional protocol in the <b><a href="../reference/api/org/eclipse/core/runtime/jobs/Job.html">Job</a></b> class
-allows a job to check for preconditions just before it is scheduled or run.  This is best demonstrated by example:
-</p>
-<pre>class JobWithPreconditions extends Job {
-	...
-	public boolean <b>shouldSchedule()</b> {
-		return super.shouldSchedule() &amp;&amp; checkJobPreconditions();
-	}
-	public boolean <b>shouldRun()</b> {
-		return super.shouldRun() &amp;&amp; checkJobPreconditions();
-	}
-	...
-}
-</pre>
-<p>The <b>shouldSchedule</b> method is called just before the job manager places the job in the queue.  This allows the job
-to cancel itself if basic preconditions for scheduling are not met.  The job should return <tt>false</tt> it
-is inappropriate to schedule it.  Likewise, the <b>shouldRun</b> method is called just before the job manager 
-runs the job.  Any additional conditions that must be met before the job is run must be checked at this time.  
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_model.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_model.htm
deleted file mode 100644
index 1d7d785..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_model.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>The runtime plug-in model</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-The runtime plug-in model</H2>
-<P >
-The platform runtime engine is started when a user starts an application developed with Eclipse.  
-The runtime implements the basic <b>plug-in</b> model and infrastructure used by the platform.  
-It keeps track of all of the installed plug-ins and the function that they provide. 
-</p>
-<p>A plug-in is a structured component that contributes code (or documentation or both) to the system and describes
-it in a structured way. Plug-ins can define <b>extension points</b>, well-defined 
-function points that can be extended by other plug-ins. When a plug-in contributes an implementation for an 
-extension point, we say that it adds an <b>extension</b> to the platform. These extensions and extension points
-are declared in the plug-ins's manifest (<b>plugin.xml</b>) file.
-</p>
-<P >
-Using a common extension model provides a structured way for plug-ins to describe the ways they can be extended, and 
-for client plug-ins to describe the extensions they supply.  Defining an extension point is much like defining 
-any other API.  The only difference is that the extension point is declared using XML instead of a code signature.
-Likewise, a client plug-in uses XML to describe its specific extension to the system.  
-</p>
-<p>A general goal of the runtime is that the end user should not pay a memory 
-  or performance penalty for plug-ins that are installed, but not used. The declarative 
-  nature of the platform extension model allows the runtime engine to determine 
-  what extension points and extensions are supplied by a plug-in without ever 
-  running it. Thus, many plug-ins can be installed, but none will be activated 
-  until a function provided by a plug-in has been requested according to the user's 
-  activity. This is an important feature in providing a scalable, robust platform. 
-</p>
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_model_bundles.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_model_bundles.htm
deleted file mode 100644
index 9c79068..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_model_bundles.htm
+++ /dev/null

@@ -1,103 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Plug-ins and bundles</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-Plug-ins and bundles</H3>
-<p>
-The mechanics for supporting plug-ins are implemented using the <a href="http://www.osgi.org">OSGi</a> framework.  From this
-standpoint, a plug-in is the same thing as an OSGi <b>bundle</b>.  The bundle and its associated classes specify and implement
-the process for Java class-loading, prequisite management, and the bundle's life-cycle.  For the rest of this discussion, we use
-the terms <b>plug-in</b> and <b>bundle</b> interchangeably, unless discussing a particular class in the framework.  
-</p>
-<h4>Plugin</h4>
-<p>
-The <b><a href="../reference/api/org/eclipse/core/runtime/Plugin.html">Plugin</a></b> class represents a plug-in that
-is running in the platform.  It is a convenient place to centralize the life-cycle aspects and overall 
-semantics of a plug-in.  A plug-in can implement specialized function for the <b>start</b> and <b>stop</b>
-aspects of its life-cycle.  Each life-cycle method includes a reference to a  
-<b><a href="../reference/osgi/org/osgi/framework/BundleContext.html">BundleContext</a></b> which can supply
-additional information.</p>
-<p>
-The <b>start</b> portion of the life-cycle is worth particular discussion.  We've seen already that information 
-about a plug-in can be obtained from the plug-in's manifest file without ever running any of the 
-plug-in's code.  Typically, some user action in the workbench causes a chain of events that 
-requires the starting of a plug-in.  From an implementation point of view, a plug-in is
-never started until a class contained the in the plug-in needs to be loaded.
-</p>
-<p>
-The <b>start</b> method has been a convenient place to implement initialization and
-registration behavior for a plug-in.  However, it is important to realize that your plug-in
-can be started in many different circumstances.  Something as simple as obtaining an icon to decorate
-an object can cause one of your plug-in's classes to be loaded, thus starting your plug-in.  Over-eager 
-initialization can cause your plug-in's code and data to be loaded long before it is necessary.  Therefore,
-it's important to look closely at your plug-in's initialization tasks and consider alternatives
-to performing initialization at start-up.</p>
-<ul>
-<li><b>Registration</b> activities such as registering listeners or starting background threads are appropriate
-during plug-in start-up if they can be performed quickly.  However, it is advisable to trigger these
-actions as part of accessing the plug-in's data if the registration activities have side-effects such
-as initializing large data structures or performing unrelated operations. </li>
-<li><b>Initialization</b> of data is best done lazily, when the data is first accessed, rather than automatically
-in the start-up code.  This ensures that large data structures are not built until they are truly necessary.</li>
-</ul>
-
-<h4>Bundle Context</h4>
-<p>
-Life-cycle management is where the OSGi &quot;bundle&quot; terminology and the platform's 
-&quot;plug-in&quot; terminology meet.  When your plug-in is started, it is given a reference to a <b><a href="../reference/osgi/org/osgi/framework/BundleContext.html">
-BundleContext</a></b> from which it can obtain information related to the plug-in.  The
-<b><a href="../reference/osgi/org/osgi/framework/BundleContext.html">BundleContext</a></b>
-can also be used to find out about other bundles/plug-ins in the system.  
-</p>
-<p>
-<b>BundleContext.getBundles()</b> can be used to obtain an array of all bundles in the system.  Listeners for
-<b>BundleEvent</b> can be registered so that your plug-in is aware when another bundle has a change
-in its life-cycle status.  See the javadoc for 
-<b><a href="../reference/osgi/org/osgi/framework/BundleContext.html">BundleContext</a></b> and
-<b><a href="../reference/osgi/org/osgi/framework/BundleEvent.html">BundleEvent</a></b> for more information.
-</p>
-<blockquote><i>
-Prior to 3.0, a plugin registry (<b>IPluginRegistry</b>) was provided to supply similar information.  For example,
-it could be queried for the plug-in descriptors of all plug-ins in the system.  This registry is now deprecated and
-<b><a href="../reference/osgi/org/osgi/framework/BundleContext.html">BundleContext</a></b> should be
-used for this purpose.  The platform registry is now used exclusively for information about extensions 
-and extension points.
-</i></blockquote>
-<h4>Bundle Activator</h4>
-<p>
-The <b><a href="../reference/osgi/org/osgi/framework/BundleActivator.html">BundleActivator</a></b> interface defines
-the start and stop behavior implemented in 
-<b><a href="../reference/api/org/eclipse/core/runtime/Plugin.html">Plugin</a></b>.  Although the
-<b><a href="../reference/api/org/eclipse/core/runtime/Plugin.html">Plugin</a></b> class is a convenient place
-to implement this function, a plug-in developer has complete freedom to implement the interface for
-<b><a href="../reference/osgi/org/osgi/framework/BundleActivator.html">BundleActivator</a></b> in any class
-appropriate for the plug-in's design.  In fact, your plug-in need not implement this interface at all if it
-does not have specific life-cycle management needs.  </p>
-<h4>Bundles</h4>
-<p>
-Underneath every plug-in lies an OSGi bundle managed by the framework.
-The <b><a href="../reference/osgi/org/osgi/framework/Bundle.html">Bundle</a></b> is the OSGi unit of modularity.  Fundamentally, a 
-bundle is just a collection of files (resources and code) installed in the 
-platform.  Each bundle has its own Java
-class loader, and includes protocol for starting, stopping, and uninstalling itself.  From the Eclipse platform 
-point of view, <b><a href="../reference/osgi/org/osgi/framework/Bundle.html">Bundle</a></b> is merely an implementation 
-class.   Plug-in developers do not extend the bundle class, but use <b><a href="../reference/api/org/eclipse/core/runtime/Plugin.html">Plugin</a></b>
-or other <b><a href="../reference/osgi/org/osgi/framework/BundleActivator.html">BundleActivator</a></b> implementations
-to represent the plug-in.</p>
-
-
-</BODY>
-</HTML>
-
-

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_preferences.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_preferences.htm
deleted file mode 100644
index aebb0fd..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_preferences.htm
+++ /dev/null

@@ -1,136 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Runtime preferences</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Runtime preferences</H2>
-<p> The <b><a href="../reference/api/org/eclipse/core/runtime/preferences/package-summary.html">org.eclipse.core.runtime.preferences</a></b> 
-  package provides infrastructure for storing a plug-in's preferences. Preferences 
-  typically map to settings controlled by the user on the <b>Preferences</b> page, 
-  although this is not required by the underlying infrastructure. Plug-in preferences 
-  are key/value pairs, where the key describes the name of the preference, and 
-  the value is one of several different types (boolean, double, float, int, long, 
-  or string). Preferences can be stored and retrieved by the platform from the 
-  file system. The exact location of the saved preferences depends upon the <b>scope</b> 
-  of the preference. </P>
-<h3>
-Preference scopes
-</h3>
-The <b>scope</b> of a preference is closely related to where the preference is stored.  Plug-in
-developers can decide which of the standard scopes apply for their preferences, or can define 
-new scopes that make sense for their plug-in.  Let's look first at the scopes defined by
-the platform runtime:
-<ul>
-<li><b>Instance</b> scoped preferences are stored per workspace, or per running instance of the platform.</li>
-<li><b>Configuration</b> scoped preferences are stored per installation of the platform.  They are shared between
-workspaces.  For example, if a user has a single installation of the platform, but runs several different workspaces, 
-preferences scoped at the configuration level will be shared between the workspaces.</li>
-<li><b>Default</b> scoped preferences represent the default values for preferences.  These are not changed or stored
-by the platform.  However, the values originate from files stored with the plug-in's product
-or primary feature. (See <a href="product_def.htm">What is a product?</a> for an explanation of products and
-primary features, and their related files.)</li>
-</ul>
-<p>
-You can think of the overall preference store as a hierarchy of nodes, where each main branch of the hierarchy
-represents a particular scope.  The children of any particular node depend upon how that scope is defined.
-For the instance and configuration scopes, the child nodes are the preferences for a particular plug-in as specified
-by a preference <b>qualifier</b>, usually the plug-in's <b>id</b>.
-</p>
-<p>
-If all of this sounds confusing, don't worry.  If you don't care about scopes and nodes,
-you need not worry about any particular scope or about which node of the tree actually contains your preference value.
-The preferences API will automatically traverse the nodes in the proper order (instance, configuration, default)
-when you query a preference value and use the supplied qualifier and preference name to find the node that actually
-contains the value.
-</p>
-<p>Preferences are accessed using <b><a href="../reference/api/org/eclipse/core/runtime/preferences/IPreferencesService.html">
-IPreferencesService</a></b> protocol.  The platform's default preference service can be accessed using the
-<b><a href="../reference/api/org/eclipse/core/runtime/Platform.html">Platform</a></b> class.
-</p>
-<pre>
-	...
-	IPreferencesService service = <b>Platform.getPreferencesService()</b>;
-	...
-</pre>
-<p>
-Once the preference service is obtained, preference values can be queried by name using any of
-<b>get...</b> methods provided in <b><a href="../reference/api/org/eclipse/core/runtime/preferences/IPreferencesService.html">IPreferencesService</a></b>.
-For example, the following snippet queries the value of the &quot;MyPreference&quot; preference in the plug-in
-&quot;com.example.myplugin&quot;.
-</p>
-<pre>
-	...
-	IPreferencesService service = Platform.getPreferencesService();
-	boolean value = service.getBoolean(&quot;com.example.myplugin&quot;, &quot;MyPreference&quot;, true, <b>null</b>);
-	//do something with the value.
-	...
-</pre>
-<p>The last parameter in the query method is an array of scope contexts to use when searching for the
-preference node. If the 
-array is <b>null</b>, then the platform assumes that the default scope search order should be used and guesses
-the appropriate preference node.  If an array of scopes contexts is passed, then this determines
-the scope lookup order that should be used to find the preference node.  The default scope lookup order
-is always consulted if no node can be found using the specified scopes.
-</p>
-<h3>
-Using scopes and nodes
-</h3>
-<p>
-If a plug-in needs finer control over the scope search order, classes that represent the scopes can be used
-to access the actual node that represents the preference at a particular scope.  In this way, an array of 
-nodes can be created that specifies the particular search order required.  The following snippet queries the
-preferences service for the same preference used above, but searches the configuration scope for the plug-in, 
-followed by the instance scope for the plug-in. When nodes are specified for the search order, the default
-scoping is not considered.  That is, the platform will only search the exact nodes that have been provided.</p>
-<pre>
-	...
-	IPreferencesService service = Platform.getPreferencesService();
-	Preferences configurationNode = new ConfigurationScope().getNode(&quot;com.example.myplugin&quot;);
-	Preferences instanceNode = new InstanceScope().getNode(&quot;com.example.myplugin&quot;);
-	Preferences[] nodes = new Preferences[] {configurationNode, instanceNode};
-	stringValue = service.get(&quot;MyPreference&quot;, &quot;true&quot;, nodes);
-	//do something with the value.
-	...
-</pre>
-<p>
-A plug-in may also implement its own traversal through the preference tree nodes. The root node of the preference tree
-can be obtained from the preferences service.  The scope classes can be used to further traverse the tree.
-The following snippet traverses to a specific node and retrieves the preference value from the node itself.
-</p>
-<pre>
-	...
-	IPreferencesService service = Platform.getPreferencesService();
-	Preferences root = service.getRootNode();
-	Preferences myInstanceNode = root.node(InstanceScope.SCOPE).node(&quot;com.example.myplugin&quot;);
-	if (myInstanceNode != null) {
-		value = node.getBoolean(&quot;MyPreference&quot;, &quot;true&quot;);
-		//do something with the value.
-	}
-	...
-</pre>
-<h3>
-Extending the scopes
-</h3>
-<p>
-Plug-ins may define their own specialized scopes using the 
-<a href="../reference/extension-points/org_eclipse_core_runtime_preferences.html"><b>org.eclipse.core.runtime.preferences</b></a> 
-extension.  In this extension, the plug-in defines the name of the new scope, as well a class that can create
-preference nodes for the new scope.  Optionally, it can specify the name of a class that initializes the default
-preference values at that scope.  When a plug-in defines a new scope, it is up to that plug-in to implement the 
-traversal order for any new scope relative to the platform traversal order.  We'll look at this capability in more 
-detail using the specific example of <a href="resInt_preferences.htm">Project-scoped preferences</a>.
-</p>
- 
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_registry.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_registry.htm
deleted file mode 100644
index 1b34008..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_registry.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Extension points and the registry</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-Extension points and the registry</H3>
-<p>
-While the "bundle" aspects of a plug-in may be interesting to the runtime plug-in and runtime tools,
-it is much more common that a plug-in is concerned with what extension points have been defined
-by plug-ins and what extensions are contributed by plug-ins.  This information is provided 
-by the platform extension registry, <b><a href="../reference/api/org/eclipse/core/runtime/IExtensionRegistry.html">
-IExtensionRegistry</a></b>.
-</p>
-<p>Why might a plug-in want to know what extensions are present?  A concrete example will help show
-the need for this information and the protocol for getting it.</p>
-<p>Recall the workbench <b>Show View</b> dialog which shows all of the available views that have
-been installed in the platform.</p>
-<img src="images/showview.png" alt="Show View dialog with Hello entry" border="0">
-<p>
-We know that the category names and view names of all contributed views are specified in the
-<b>plugin.xml</b> file for any plug-in that contributes an extension for <b>org.eclipse.ui.views</b>.
-But how does the workbench find out this information?  From the platform extension registry.  The following 
-code is a simplified snippet based on the workbench implementation of the <b>Show View</b> dialog:
-</p>
-<pre>
-	...
-	IExtensionRegistry registry = <b>Platform.getExtensionRegistry()</b>;
-	IExtensionPoint point = <b>registry.getExtensionPoint(&quot;org.eclipse.ui.views&quot;)</b>;
-	if (point == null) return;
-	IExtension[] extensions = <b>point.getExtensions()</b>;
-	for (int i = 0; i &lt; extensions.length; i++)
-		readExtension(extensions[i]);  //get the information about each extension
-	...
-</pre>
-<p>
-We see above that the registry can be obtained from the <b><a href="../reference/api/org/eclipse/core/runtime/Platform.html">
-Platform</a></b> class.  The protocol in <b><a href="../reference/api/org/eclipse/core/runtime/IExtensionRegistry.html">
-IExtensionRegistry</a></b> is used to find the extension point named <b>org.eclipse.ui.views</b>.  Information in the registry
-about particular extension points or extensions can be found using protocol defined in
-<b><a href="../reference/api/org/eclipse/core/runtime/IExtensionRegistry.html">IExtensionRegistry</a></b>,
-<b><a href="../reference/api/org/eclipse/core/runtime/IExtensionPoint.html">IExtensionPoint</a></b>,
-and <b><a href="../reference/api/org/eclipse/core/runtime/IExtension.html">IExtension</a></b>.  
-The javadoc for these classes provides detailed information about the registry protocol.
-</p>
-<p>
-Once the extension definition of interest has been found, protocol in 
-<b><a href="../reference/api/org/eclipse/core/runtime/IConfigurationElement.html">IConfigurationElement</a></b>
-can be used to examine the individual attributes of an extension.
-</p>
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/search.htm b/bundles/org.eclipse.platform.doc.isv/guide/search.htm
deleted file mode 100644
index 61550a3..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/search.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Search support</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Search support</H1>
-
-
-<p>
-If your plug-in defines and manipulates its own resource types, you may have
-special requirements for searching a resource.&nbsp; For example, the Java IDE
-plug-in implements a search engine specialized for Java files.&nbsp;&nbsp;&nbsp;</p>
-
-
-<p>
-The <b>search</b> plug-in allows you to add a specialized page describing your
-search to the workbench search dialog.&nbsp; This allows you to obtain any
-specialized information needed from the user and perform a search using your
-plug-in's internal model.</p>
-
-
-<p>
-You should also provide a specialized class for displaying the search results.
-Abstract implementations of a search result page are provided to give you a head
-start.</p>
-
-
-<p>
-These services are contributed using search plug-in extension points.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/search_page.htm b/bundles/org.eclipse.platform.doc.isv/guide/search_page.htm
deleted file mode 100644
index d97640d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/search_page.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Contributing a search page</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Contributing a search page</H2>
-
-
-<p>When the user selects a resource and chooses the search command, the search
-plug-in launches a dialog containing pages for different kinds of content
-searches.&nbsp; These pages are contributed using the <a href="../reference/extension-points/org_eclipse_search_searchPages.html"><b>org.eclipse.search.searchPages</b></a>
-extension point.</p><p>The markup for contributing a search page is
-straightforward.&nbsp; The following example is the JDT plug-in's contribution
-of the Java search page:</p>
-<pre>&lt;extension point=&quot;org.eclipse.search.searchPages&quot;&gt;
-   &lt;page id=&quot;org.eclipse.jdt.ui.JavaSearchPage&quot;
-		icon=&quot;icons/full/obj16/jsearch_obj.png&quot;
-		label=&quot;%JavaSearchPage.label&quot;
-		sizeHint=&quot;460,160&quot;
-		extensions=&quot;java:90, jav:90&quot;
-		showScopeSection=&quot;true&quot;
-		canSearchEnclosingProjects=&quot;true&quot;
-		<b>class=&quot;org.eclipse.jdt.internal.ui.search.JavaSearchPage&quot;</b>&gt;
-	&lt;/page&gt;
-&lt;/extension&gt;
-</pre>
-<p>The <b>class</b> that implements the
-search page must be specified.&nbsp; This class must implement the <a href="../reference/api/org/eclipse/search/ui/ISearchPage.html"><b>ISearchPage</b></a>
-nterface and typically extends <a href="../reference/api/org/eclipse/jface/dialogs/DialogPage.html"><b>DialogPage</b></a>.&nbsp;
-The <b>label</b> and <b>icon</b> that can be
-used to describe the search in the search dialog are also specified.&nbsp;
-Additional parameters control the size of the page and the location of the page
-within the search dialog.</p>
-<p>The <b>extensions</b> attribute specifies the
-resources on which the search page can operate.&nbsp; It is formatted as a comma
-separated list of file extensions.&nbsp; Each file extension should be followed
-by a numeric weight value, where 0 is the lowest weight, separated by a
-colon.&nbsp; The weight value is a relative value used to allow the search
-infrastructure to find the search page most appropriate for a given resource.</p>
-<p>If a search page can search all possible resources then &quot;*&quot; should be used.</p>
-<h3>Implementing
-the search page</h3>
-<p>The
-protocol for <a href="../reference/api/org/eclipse/search/ui/ISearchPage.html"><b>ISearchPage</b></a>
-is simple.&nbsp; Your search page must implement <code>performAction()</code> which
-is called when the <b>Search</b> button is pressed.&nbsp; Of course, your
-particular search implementation depends on your plug-in's function, but it is
-typical to open a results viewer in this method using
-the <a href="../reference/api/org/eclipse/search/ui/NewSearchUI.html"><b>NewSearchUI</b></a>
-method <tt>activateSearchResultView().</tt>	</p>
-<p>Your plug-in is responsible for
-showing its results in the search result view.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/search_result.htm b/bundles/org.eclipse.platform.doc.isv/guide/search_result.htm
deleted file mode 100644
index 4ee30e0..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/search_result.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Contributing a search result page</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Contributing a search result page</H2>
-
-<p>You can contribute a customized search results page using
-the <a href="../reference/extension-points/org_eclipse_search_searchResultViewPages.html"><b>org.eclipse.search.searchResultViewPages</b></a>
-extension point.
-</p>
-<p>When contributing a search result view page, you specify the class of search result that the page should
-be used for, and the name of the class that implements the page.  The following example is the JDT plug-in's 
-contribution of the Java search results page:</p>
-<pre>&lt;extension
-	id="JavaSearchResultPage"
-	point="org.eclipse.search.searchResultViewPages"&gt;
-	&lt;viewPage
-		id="org.eclipse.jdt.ui.JavaSearchResultPage"
-		searchResultClass="org.eclipse.jdt.internal.ui.search.JavaSearchResult"
-		class="org.eclipse.jdt.internal.ui.search.JavaSearchResultPage"&gt;
-	&lt;/viewPage&gt;
-&lt;/extension&gt;
-</pre>
-<p>The <b>class</b> must implement the <a href="../reference/api/org/eclipse/search/ui/ISearchResultPage.html"><b>ISearchResultPage</b></a>
-interface and often extends <a href="../reference/api/org/eclipse/search/ui/text/AbstractTextSearchViewPage.html"><b>AbstractTextSearchViewPage</b></a>.
-</p> 
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/site_interfaces.htm b/bundles/org.eclipse.platform.doc.isv/guide/site_interfaces.htm
deleted file mode 100644
index 8dd1516..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/site_interfaces.htm
+++ /dev/null

@@ -1,245 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Site interfaces</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2> Site interfaces</H2>
-The arguments in a part's constructor are known as dependencies. Part dependencies 
-replace the various adapters and get methods, for example, to access a site's 
-IActionBars, a component-based part would take an IActionBars instance in its 
-constructor. <br>
-<br>
-New-style sites offer an open-ended set of interfaces. Any plug-in can extend 
-the set of site interfaces using the <span
- style="font-style: italic;">org.eclipse.core.component.types</span> extension 
-point. Although the set of site interfaces can be extended, all sites support 
-the same set, ensuring that any part can be plugged into any site. It is possible 
-to view the complete set of site interfaces using the PDE plug-in registry view.<br>
-<br>
-The workbench supplies the following site interfaces:<br>
-<br>
-<table style="width: 100%; text-align: left;" border="1" cellpadding="2"
- cellspacing="2">
-  <tbody>
-    <tr> 
-      <td style="vertical-align: top; font-weight: bold;">Interface<br> </td>
-      <td style="vertical-align: top; font-weight: bold;">Description<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top;">IErrorContext<br> </td>
-      <td style="vertical-align: top;">Constructs and logs IStatus messages to 
-        the plug-in log.<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top;">Bundle<br> </td>
-      <td style="vertical-align: top;">The plug-in bundle containing the part's 
-        implementation. This informs other components, such as the implementation 
-        of IErrorContext, automatically of their plug-ins.<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top;">IContainer<br> </td>
-      <td style="vertical-align: top;">The site's container. This object can be 
-        queried for any of the other site interfaces, which can be useful if the 
-        part wants to redirect or multiplex everything from its site to its children.<br> 
-      </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top;">INameable<br> </td>
-      <td style="vertical-align: top;">Allows a part to set its name, icon, tooltip, 
-        and content description. Replaces the various get methods and listeners 
-        on IWorkbenchPart.<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top;">Composite<br> </td>
-      <td style="vertical-align: top;">Parent composite for the part. This composite 
-        is not shared with any other parts, and will be disposed at the same time 
-        as the part. The part is allowed to set the layout and attach listeners 
-        to this composite.<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top;">ISecondaryId<br> </td>
-      <td style="vertical-align: top;">Interface that returns a part's secondary 
-        ID when used as a multi-instance view.<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top;">ResourceManager<br> </td>
-      <td style="vertical-align: top;">Safely allocates and deallocates Images, 
-        Fonts, Colors, and other SWT resources. Ensures that identical resources 
-        are shared between parts and that any leaks get cleaned up when the part 
-        is closed.<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top;">IDirtyHandler<br> </td>
-      <td style="vertical-align: top;">Allows parts to set or clear their dirty 
-        state.<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top;">IMessageDialogs<br> </td>
-      <td style="vertical-align: top;">Displays error, warning, and info dialogs 
-        to the user.<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top;">IActionBars<br> </td>
-      <td style="vertical-align: top;"><font color="#FF0000">Serves the same purpose 
-        as getViewSite().getActionBars() did with the Eclipse 3.0 API.<br>
-        </font> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top;">IMultiplexer<br> </td>
-      <td style="vertical-align: top;">Provides a multiplexed component with access 
-        to its multiplexer and any shared interfaces<br>
-        . </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top;">ISavedState<br> </td>
-      <td style="vertical-align: top;">Holds the previously-persisted state of 
-        the part.<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top;">IPartFactory<br> </td>
-      <td style="vertical-align: top;">Allows a part to create nested views and 
-        editors.<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top;">IPartDescriptor<br> </td>
-      <td style="vertical-align: top;">Holds meta-info about a part such as its 
-        ID, title, default image, and so on.<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top;">IEditorInput<br> </td>
-      <td style="vertical-align: top;">Holds the editor input for an editor. Points 
-        to an empty editor input for views.<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top;">ISelectionHandler<br> </td>
-      <td style="vertical-align: top;">Handles selection changes. Parts can use 
-        this to change the selection they provide to the workbench.<br> </td>
-    </tr>
-  </tbody>
-</table>
-<p>It is up to the part's containing context to determine whether the part gets 
-  a unique instance for each interface or an object shared among several parts. 
-  The part's constructor never receives a null argument.</p>
-<p>&nbsp;</p>
-<h3>Using new site interfaces with existing parts</h3>
-<p>Although constructor injection is convenient, it would be impractical to rewrite 
-  every existing editor and view to use constructor injection in order to take 
-  advantage of the new site interfaces. For this reason, all of the new interfaces 
-  are also available to existing views as adapters on IWorkbenchPartSite. <br>
-</p>
-<p>Here is a view containing a single button that opens a message dialog.</p>
-<p><img
- src="images/dependencies_view.PNG" alt="Image of DependenciesViewOld"></p>
-<p> The following example shows the source for a new-style view that opens the 
-  dialog using the new IMessageDialogs interface.</p> 
-<div style="margin-left: 40px;">
-  <p><code>/**<br>
-    &nbsp;* Demonstrates how to use component dependencies in a new-style part.<br>
-    &nbsp;* <br>
-    &nbsp;* @since 3.1<br>
-    &nbsp;*/<br>
-    public class DependenciesViewNew {<br>
-    &nbsp;&nbsp;&nbsp; // Dependencies<br>
-    &nbsp;&nbsp;&nbsp; private IMessageDialogs dialogs;<br>
-    &nbsp;&nbsp;&nbsp; <br>
-    &nbsp;&nbsp;&nbsp; /**<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * Component constructor. Do not invoke directly.<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; */<br>
-    &nbsp;&nbsp;&nbsp; public DependenciesViewNew(Composite parent, <span
- style="color: rgb(255, 0, 0);">IMessageDialogs dialogs</span>) {<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span
- style="color: rgb(255, 0, 0);">this.dialogs = dialogs;</span><br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Button testButton = new Button(parent, 
-    SWT.PUSH);<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; testButton.setText("Open a dialog");<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; testButton.addSelectionListener(new 
-    SelectionAdapter() {<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /* (non-Javadoc)<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * @see org.eclipse.swt.events.SelectionAdapter#widgetSelected(org.eclipse.swt.events.SelectionEvent)<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; */<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; public void widgetSelected(SelectionEvent 
-    e) {<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; openADialog();<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; } <br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; });<br>
-    &nbsp;&nbsp;&nbsp; }<br>
-    &nbsp;&nbsp;&nbsp; <br>
-    &nbsp;&nbsp;&nbsp; private void openADialog() {<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span
- style="color: rgb(255, 0, 0);">dialogs.open(IStatus.INFO, "This is a message");</span><br>
-    &nbsp;&nbsp;&nbsp; }<br>
-    }</code><br>
-  </p>
-  </div>
-<p>This example shows a traditional view that opens a dialog using IMessageDialogs 
-  demonstartes that this is also possible using a traditional workbench part. 
-  The lines in red font show how the IMessageDialogs interface is initialized 
-  and used in each case. <br>
-  </p>
-<div style="margin-left: 40px;">
-  <p><code>/**<br>
-    &nbsp;* Demonstrates how to use component dependencies in an old-style view<br>
-    &nbsp;* <br>
-    &nbsp;* @since 3.1<br>
-    &nbsp;*/<br>
-    public class DependenciesViewOld extends ViewPart {<br>
-    &nbsp;&nbsp;&nbsp; // Dependencies<br>
-    &nbsp;&nbsp;&nbsp; private IMessageDialogs dialogs;<br>
-    &nbsp;&nbsp; &nbsp;<br>
-    &nbsp;&nbsp;&nbsp; // Main widget<br>
-    &nbsp;&nbsp;&nbsp; private Composite parent;<br>
-    &nbsp;&nbsp; &nbsp;<br>
-    &nbsp;&nbsp;&nbsp; /* (non-Javadoc)<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * @see org.eclipse.ui.IWorkbenchPart#createPartControl(org.eclipse.swt.widgets.Composite)<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; */<br>
-    &nbsp;&nbsp;&nbsp; public void createPartControl(Composite parent) {<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; this.parent = parent;<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span
- style="color: rgb(255, 0, 0);">this.dialogs = (IMessageDialogs)getSite().getAdapter(IMessageDialogs.class);</span><br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Button testButton = new Button(parent, 
-    SWT.PUSH);<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; testButton.setText("Open a dialog");<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; testButton.addSelectionListener(new 
-    SelectionAdapter() {<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /* (non-Javadoc)<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * @see org.eclipse.swt.events.SelectionAdapter#widgetSelected(org.eclipse.swt.events.SelectionEvent)<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; */<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; public void widgetSelected(SelectionEvent 
-    e) {<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; openADialog();<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; } <br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; });<br>
-    &nbsp;&nbsp;&nbsp; }<br>
-    &nbsp;&nbsp; &nbsp;<br>
-    &nbsp;&nbsp;&nbsp; private void openADialog() {<br>
-    <span style="color: rgb(255, 0, 0);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-    if (dialogs != null) {</span><br style="color: rgb(255, 0, 0);">
-    <span style="color: rgb(255, 0, 0);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-    dialogs.open(IStatus.INFO, "This is a message");</span><br
- style="color: rgb(255, 0, 0);">
-    <span style="color: rgb(255, 0, 0);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-    }</span><br>
-    &nbsp;&nbsp;&nbsp; }<br>
-    <br>
-    &nbsp;&nbsp;&nbsp; /* (non-Javadoc)<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; * @see org.eclipse.ui.IWorkbenchPart#setFocus()<br>
-    &nbsp;&nbsp;&nbsp;&nbsp; */<br>
-    &nbsp;&nbsp;&nbsp; public void setFocus() {<br>
-    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; parent.setFocus();<br>
-    &nbsp;&nbsp;&nbsp; }<br>
-    }</code></p>
-  <p>&nbsp; </p>
-</div>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/sites_work.htm b/bundles/org.eclipse.platform.doc.isv/guide/sites_work.htm
deleted file mode 100644
index 025638a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/sites_work.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>How sites work</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>How sites work</H2>
-<p>The following example shows the internal structure of a Site. Sites procure 
-  some context from their owner as well as expose a set of adapters. The site 
-  combines the context from its parent with the default dependencies from the 
-  <span style="font-style: italic;">org.eclipse.core.components.types </span>extension 
-  point to compute the dependencies for its part. If it needs to create any dependencies 
-  from a factory, it remembers those objects so that it can send them lifecycle 
-  notifications later. <br>
-  <br>
-  The adapters that a site returns to its owner are created in a similar manner. 
-  If the part implements an adapter, the site returns it directly. Otherwise, 
-  it looks for a default adapter from the <span
- style="font-style: italic;">org.eclipse.core.components.types </span>extension 
-  point. <br>
-  <br>
-  To avoid any confusion, this should be said explicitly: the adapters that a 
-  site returns to its owner are not the same as the adapters it returns to an 
-  old-style part. The adapters that an old-style part gets from its site are dependencies, 
-  whereas the adapters that a site returns to its parent are adapters for the 
-  part itself.<br>
-  <br>
-  <br>
-  <img alt="Anatomy of a Site" src="images/components_diagram.png"></p>
-<h2> <br>
-  <br>
-</h2>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/swt.htm b/bundles/org.eclipse.platform.doc.isv/guide/swt.htm
deleted file mode 100644
index 27b020e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/swt.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Standard Widget Toolkit</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>The Standard Widget Toolkit</H1>
-
-<P>The Standard Widget Toolkit (SWT) is a widget toolkit for Java developers
-that provides a portable API and tight integration with the underlying native
-OS GUI platform.</P>
-
-<P>Many low level UI programming tasks are handled in higher layers of the
-Eclipse platform.  For example, JFace viewers and actions provide
-implementations for the common interactions between applications and widgets.
-However, knowledge of SWT is important for understanding how the rest of the
-platform works.</P>
-
-
-<h2>Portability and platform integration</h2>
-
-<P>SWT defines a common portable API that is provided on all supported
-platforms, and implements the API on each platform using native widgets
-wherever possible.  This allows the toolkit to immediately reflect any
-changes in the underlying OS GUI look and feel while maintaining a consistent
-programming model on all platforms.</P>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/swt_error.htm b/bundles/org.eclipse.platform.doc.isv/guide/swt_error.htm
deleted file mode 100644
index 15fae97..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/swt_error.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Error handling</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H2>Error handling</H2>
-
-<P>SWT can trigger three types of exceptions:
-<strong>IllegalArgumentException</strong>,
-<strong><a href="../reference/api/org/eclipse/swt/SWTException.html">SWTException</a></strong>, and
-<strong><a href="../reference/api/org/eclipse/swt/SWTError.html">SWTError</a></strong>.
-Applications should not have to catch any other kind of exception or error
-when calling SWT.</P>
-
-<blockquote><em>Note: If any other exception besides these three is thrown
-from SWT, it should be considered a bug in the SWT implementation.</em></blockquote>
-
-<P>Where possible, exceptions are triggered consistently across platforms.
-However, some errors are specific to an SWT implementation on a particular
-platform.</P>
-
-
-<H3>IllegalArgumentException</H3>
-
-<P>The arguments passed in SWT API methods are checked for appropriate state
-and range before any other work is done. An <strong>IllegalArgumentException</strong>
-will be thrown when it is determined that an argument is invalid.</P>
-
-<P>Code that causes an <strong>IllegalArgumentException</strong> on one platform 
-will cause the same exception on a different platform.</P>
-
-
-<H3>SWTException</H3>
-
-<P><strong><a href="../reference/api/org/eclipse/swt/SWTException.html">SWTException</a></strong>
-is thrown when a recoverable error occurs internally in SWT. The error code and
-message text provide a further description of the problem.</P>
-
-<P>SWT remains in a known stable state after throwing the exception.
-For example, this exception is thrown when an SWT call is made from a non-UI
-thread.</P>
-
-
-<H3>SWTError</H3>
-
-<P><a href="../reference/api/org/eclipse/swt/SWTError.html"><strong>SWTError</strong></a>
-is thrown when an unrecoverable error occurs inside SWT.</P>
-
-<P>SWT will throw this error when an underlying platform call fails, leaving
-SWT in an unknown state, or when SWT is known to have an unrecoverable error,
-such as running out of platform graphics resources.</P>
-
-<P>Once an SWT error has occurred, there is little that an application can do
-to correct the problem. These errors should not be encountered during normal
-course of operation in an application, but high reliability applications
-should still catch and report the errors.</P>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/swt_graphics.htm b/bundles/org.eclipse.platform.doc.isv/guide/swt_graphics.htm
deleted file mode 100644
index 94d9eb0..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/swt_graphics.htm
+++ /dev/null

@@ -1,206 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Graphics</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H2>Graphics</H2>
-
-<P>SWT provides a graphics engine for drawing graphics and displaying
-images in widgets. You can get pretty far without ever programming to the
-graphics interface, since widgets handle the painting of icons, text, and other
-data for you. However, if your application displays custom graphics, or if
-you are implementing a custom drawn widget, then you will need to understand
-some basic drawing objects in SWT.</P>
-
-
-<H3>Graphics context</H3>
-
-<P>The graphics context,
-<strong><a href="../reference/api/org/eclipse/swt/graphics/GC.html">GC</a></strong>,
-is the focal point for SWT graphics support. Its API describes all of the
-drawing capabilities in SWT.</P>
-
-<P>A GC can be used for drawing on a control (the most common case), on an image,
-on a display, or to a printer. When drawing on a control, you use the GC
-supplied to you in the control's paint event. When drawing on an image,
-display, or printer, you must create a GC configured for it, and dispose of the
-GC when you are finished using it.</P>
-
-<P>Once you've got a GC, you can set its attributes, such as color, line width, and font, which control
-the appearance of the graphics drawn in the GC.</P>
-
-<P>The API Reference for
-<strong><a href="../reference/api/org/eclipse/swt/graphics/GC.html">GC</a></strong>
-describes the complete set of graphics functions.</P>
-
-
-<H3>Fonts</H3>
-
-<P>The <strong><a href="../reference/api/org/eclipse/swt/graphics/Font.html">Font</a></strong> and
-<strong><a href="../reference/api/org/eclipse/swt/graphics/FontData.html">FontData</a></strong>
-classes are used when manipulating fonts in SWT.</P>
-
-<P>FontData describes the characteristics of a font. You can create a FontData
-by specifying a font name, style, and size.  FontData includes API for querying 
-these attributes. Since FontData does not allocate any OS resources, you do not
-need to dispose of it.</P>
-
-<P>The Font is the actual graphic object representing a font that is used in the
-drawing API. You create a Font for a 
-<strong><a href="../reference/api/org/eclipse/swt/widgets/Display.html">Display</a></strong>
-by specifying the Display and the FontData of the font that you want. You can 
-also query a Font for its FontData.</P>
-
-<P>You must dispose of an allocated Font when you are finished using it.</P>
-
-
-<H3>Colors</H3>
-
-<P>Colors are similar to fonts. You create a
-<strong><a href="../reference/api/org/eclipse/swt/graphics/Color.html">Color</a></strong>
-for a Display by specifying the RGB values for the desired color. You must dispose of an
-allocated color when you are finished using it.</P>
-
-<P>The Display method <code>getSystemColor(int)</code> allows you to query the predefined
-system colors for the OS platform. You should not free colors obtained using
-this technique.</P>
-
-
-<P >The color model is discussed in detail in the article 
-<a href="http://www.eclipse.org/articles/SWT%20Color%20Model/swt-color-model.htm">SWT color model</a>.</P>
-
-
-<H3>Images</H3>
-
-<P>The <strong><a href="../reference/api/org/eclipse/swt/graphics/Image.html">Image</a></strong>,
-<strong><a href="../reference/api/org/eclipse/swt/graphics/ImageData.html">ImageData</a></strong>, and
-<strong><a href="../reference/api/org/eclipse/swt/graphics/ImageLoader.html">ImageLoader</a></strong>
-classes are used when manipulating Images in SWT.</P>
-
-<P>ImageData describes the actual pixels in the image, using the
-<a href="../reference/api/org/eclipse/swt/graphics/PaletteData.html"><strong>PaletteData</strong></a>
-class to describe the utilized color values.  ImageData is a device- and 
-platform-independent description of an image.</P>
-
-<P>ImageLoader loads and saves ImageData in different file formats. SWT 
-currently supports loading and saving of image formats including <em>BMP</em> 
-(Windows Bitmap), <em>ICO</em> (Windows Icon), <em>JPEG</em>, <em>GIF</em>, and 
-<em>PNG</em>.</P>
-
-<P>The Image is the actual graphic object representing the image that is used 
-in the drawing API.  You create an image for a particular Display.  Images can 
-be created in several ways:</P>
-
-<ul>
-  <li>use an ImageData to initialize the image's contents</li>
-  <li>copy an existing Image</li>
-  <li>load an Image from a file</li>
-</ul>
-
-<p>Regardless of how you create the Image, you are responsible for disposing
-it.</p>
-
-
-<H3>Graphics object lifecycle</H3>
-
-<P>Most of the graphics objects used for drawing in SWT allocate resources in
-the underlying OS and must be explicitly freed. The same rule discussed earlier
-applies here. If you create it using a constructor, you should free it. If you
-get access to it from somewhere else, do not free it.</P>
-
-
-<H4>Creation</H4>
-
-<P>Graphics objects such as graphics contexts, fonts, colors, and images are
-allocated in the OS as soon as the object is created. How you plan to use your
-graphics objects determines when you should create them.</P>
-
-<P>For graphics objects that are used heavily throughout the application, you
-can create them at the time that you create your widgets. This is commonly
-done for colors and fonts. In other cases, it is more appropriate to create
-your graphics objects on the fly. For example, you might create a graphics
-context in one of your widget event handlers in order to perform some
-calculations.</P>
-
-<P>If you are implementing a custom widget, you typically allocate graphics
-objects in the constructor if you always make use of them. You might allocate
-them on the fly if you do not always use them or if they are dependent upon
-the state of some attribute.</P>
-
-
-<H4>Painting</H4>
-
-<P>Once you have allocated your graphics objects, you are ready to paint.
-<em>You should always do your painting inside of a paint listener.</em>  There
-are rare cases, particularly when implementing custom widgets, when you paint
-while responding to some other event. However this is generally discouraged.
-If you think you need to paint while handling some other event, you should
-first try to use the <strong> redraw()</strong> method, which will generate
-another paint event in the OS.  Drawing outside of the paint method defeats
-platform optimizations and can cause bugs depending upon the number of pending
-paints in the event queue.</P>
-
-<P>When you receive a paint event, you will be supplied with a
-<strong><a href="../reference/api/org/eclipse/swt/graphics/GC.html">GC</a></strong>
-pre-configured for drawing in the widget. <em>Do not free this</em>
-<strong><a href="../reference/api/org/eclipse/swt/graphics/GC.html">GC</a></strong>!
-You did not create it.</P>
-
-<P>Any other graphics objects must be allocated while handling the event (or
-beforehand). Below is a snippet based on the
-<strong>org.eclipse.swt.examples.HelloWorld5</strong> sample. The color red was
-previously allocated when creating the widget, so it can be used here.</P>
-
-<pre>
-   shell.addPaintListener (new PaintListener () {
-      public void paintControl (PaintEvent event) {
-         GC gc = event.gc;
-         gc.setForeground (red);
-         Rectangle rect = event.widget.getClientArea ();
-         gc.drawRectangle (rect.x + 10, rect.y + 10, rect.width - 20, rect.height - 20);
-         gc.drawString (resHello.getString(&quot;Hello_world&quot;), rect.x + 20, rect.y + 20);
-      }
-   });
-</pre>
-
-
-<H4>Disposal</H4>
-
-<P>Every graphics object that you allocate must be freed when you are finished
-using it.</P>
-
-<P>The timing of the disposal depends upon when you created the object. If you
-create a graphics object while creating your widget, you should generally add
-a dispose listener onto the widget and dispose of the graphics when the widget
-is disposed. If you create an object on the fly while painting, you should
-dispose of it when finished painting.</P>
-
-<P>The next code snippet shows a slightly modified version of our paint listener.
-In this example, it allocates and frees the color red while painting.</P>
-
-<pre>
-   shell.addPaintListener (new PaintListener () {
-      public void paintControl (PaintEvent event) {
-         GC gc = event.gc;
-         Color red = new Color (event.widget.getDisplay (), 0xFF, 0, 0);
-         gc.setForeground (red);
-         Rectangle rect = event.widget.getClientArea ();
-         gc.drawRectangle (rect.x + 10, rect.y + 10, rect.width - 20, rect.height - 20);
-         gc.drawString (resHello.getString (&quot;Hello_world&quot;), rect.x + 20, rect.y + 20);
-         red.dispose ();
-      }
-   });
-</pre>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/swt_layouts.htm b/bundles/org.eclipse.platform.doc.isv/guide/swt_layouts.htm
deleted file mode 100644
index ec18786..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/swt_layouts.htm
+++ /dev/null

@@ -1,123 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Layouts</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H2>Layouts</H2>
-
-<P>Often the best way to handle simple widget positioning is in a resize event
-listener.  However, there are common patterns used by applications when placing
-widgets.  These patterns can be structured as configurable layout algorithms
-that can be reused by many different applications.</P>
-
-<P>SWT defines <em>layouts</em> that provide general purpose positioning and
-sizing of child widgets in a composite.  Layouts are subclasses of the abstract
-class <strong><a href="../reference/api/org/eclipse/swt/widgets/Layout.html">Layout</a></strong>.
-The SWT standard layouts can be found in the
-<strong><a href="../reference/api/org/eclipse/swt/layout/package-summary.html">org.eclipse.swt.layout</a></strong>
-package.</P>
-
-<P>There are some general definitions used when resizing and positioning
-widgets:</P>
-
-<ul>
-  <li>The <em>location</em> of a widget is its x,y coordinate location within
-    its parent widget.</li>
-  <li>The <em>preferred size</em> of a widget is the minimum size needed to
-    show its content. This is computed differently for each kind of widget.</li>
-  <li>The <em>clientArea</em> is the area in which a child can be placed without
-    being clipped.</li>
-  <li>The <em>trim</em> is the distance between a widget's client area and its
-    actual border.  Trim is occupied by the widget's borders or extra space
-    at its edge.  The size and appearance of the trim is widget and platform
-    dependent.</li>
-</ul>
-
-<P>These concepts are relevant for applications regardless of whether a layout
-is used. You can think of a layout as a convenient way to package resize
-functionality for reuse.</P>
-
-<P>Some additional concepts are introduced by layouts:</P>
-
-<ul>
-  <li>Some layouts support <em>spacing</em> between widgets in the layout.</li>
-  <li>Some layouts support a <em>margin</em> between the edge of the layout and
-    the widget adjacent to the edge.</li>
-</ul>
-
-<P>See <a href="http://www.eclipse.org/articles/Understanding%20Layouts/Understanding%20Layouts.htm">Understanding
-layouts in SWT</a> for further discussion and pictures demonstrating these concepts.</P>
-
-<P>The following code snippet shows the simple case of an application using a
-resize callback to size a label to the size of its parent shell:</P>
-
-<pre>
-   Display display = new Display ();
-   Shell shell = new Shell (display);
-   Label label = new Label (shell, SWT.CENTER);
-   shell.addControlListener (new ControlAdapter () {
-      public void controlResized (ControlEvent e) {
-         label.setBounds (shell.getClientArea ());
-      }
-   });
-</pre>
-
-<P>The next snippet uses a layout to achieve the same effect:</P>
-
-<pre>
-   Display display = new Display ();
-   Shell shell = new Shell (display);
-   Label label = new Label (shell, SWT.CENTER);
-   shell.setLayout (new FillLayout ());
-</pre>
-
-<P>Even for this simple example, using a layout reduces the application code.
-For more complex layouts, the simplification is much greater.</P>
-
-<p>The following table summarizes the standard layouts provided by SWT.</p>
-
-<table border="1" width="600">
-<colgroup>
-    <col width="34%">
-    <col width="66%">
-</colgroup>
-<tr>
-<th><div CLASS="CellHeading">Layout</div></th>
-<th><div CLASS="CellHeading">Purpose</div></th>
-</tr>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/layout/FillLayout.html">FillLayout</a></strong></td>
-<td>Lays out controls in a single row or column, forcing them to be the same
-size.</td>
-</tr>
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/layout/FormLayout.html">FormLayout</a></strong></td>
-<td>Positions the children by using FormAttachments to optionally configure the
-left, top, right and bottom edges of each child.</td>
-</tr>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/layout/GridLayout.html">GridLayout</a></strong></td>
-<td>Positions the children by rows and columns.</td>
-</tr>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/layout/RowLayout.html">RowLayout</a></strong></td>
-<td>Places the children either in horizontal rows or vertical columns.</td>
-
-</tr>
-</table>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/swt_layouts_custom.htm b/bundles/org.eclipse.platform.doc.isv/guide/swt_layouts_custom.htm
deleted file mode 100644
index a634d3d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/swt_layouts_custom.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Custom Layouts</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H3>Custom layouts</H3>
-
-<P>Occasionally you may need to write your own custom
-<a href="../reference/api/org/eclipse/swt/widgets/Layout.html"><strong>Layout</strong></a>
-class. This is most appropriate when you have a complex layout that is used
-in many different places in your application.   Note that unless you are
-writing a very generic layout that will be used by several
-<strong><a href="../reference/api/org/eclipse/swt/widgets/Composite.html">Composite</a></strong>
-widgets, it is sometimes simpler and easier to calculate sizes and position
-children in a resize listener.</P>
-
-<P>Layouts are responsible for implementing two methods:</P>
-
-<ul>
-  <li><strong>computeSize(...)</strong> calculates the width and height of a
-      rectangle that encloses all of the composite's children once they have
-      been sized and placed according to the layout algorithm. The hint
-      parameters allow the width and/or height to be constrained.  For example,
-      a layout may choose to grow in one dimension if constrained in another.</li>
-  <li><strong>layout(...)</strong> positions and sizes the composite's children.
-      A layout can choose to cache layout-related information, such as the
-      preferred extent of each of the children. The <strong>flushCache</strong>
-      parameter tells the <a href="../reference/api/org/eclipse/swt/widgets/Layout.html"><strong>Layout</strong></a>
-      to flush cached data, which is necessary when other factors besides the
-      size of the composite have changed, such as the creation or removal of
-      children, or a change in the widget's font.</li>
-</ul>
-
-<p>A third method, <strong>flushCache(...)</strong>, can be optionally
-implemented to clear any cached data associated with a specific control.
-Often, the computeSize() method of a widget can be expensive, and so layouts
-can cache results to improve performance.</p>
-
-<p>Further discussion of custom layouts can be found in
-<a href="http://www.eclipse.org/articles/Understanding%20Layouts/Understanding%20Layouts.htm">Understanding
-layouts in SWT</a>.</p>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/swt_threading.htm b/bundles/org.eclipse.platform.doc.isv/guide/swt_threading.htm
deleted file mode 100644
index 2ce9366..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/swt_threading.htm
+++ /dev/null

@@ -1,186 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Threading issues</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H2>Threading issues</H2>
-
-<p>When working with a widget toolkit, it is important to understand the
-underlying thread model that is used for reading and dispatching platform
-GUI events.  The implementation of the UI thread affects the rules that
-applications must follow when using Java threads in their code.</p>
-
-
-<h3>Native event dispatching</h3>
-
-<p>Underneath any GUI application, regardless of its language or UI toolkit,
-the OS platform detects GUI events and places them in application event queues.
-Although the mechanics are slightly different on different OS platforms, the
-basics are similar. As the user clicks the mouse, types characters, or surfaces
-windows, the OS generates application GUI events, such as mouse clicks,
-keystrokes, or window paint events. It determines which window and application
-should receive each event and places it in the application's event queue.</p>
-
-<p>The underlying structure for any windowed GUI application is an event loop.
-Applications initialize and then start a loop which simply reads the GUI events
-from the queue and reacts accordingly. Any work that is done while handling one
-of these events must happen quickly in order to keep the GUI system responsive
-to the user.</p>
-
-<p>Long operations triggered by UI events should be performed in a separate
-thread in order to allow the event loop thread to return quickly and fetch the
-next event from the application's queue. However, access to the widgets and
-platform API from other threads must be controlled with explicit locking and
-serialization.  An application that fails to follow the rules can cause an OS
-call to fail, or worse, lock up the entire GUI system.</p>
-
-
-<H3>SWT UI thread</H3>
-
-<P>SWT follows the threading model supported directly by the platforms.  The
-application program runs the event loop in its main thread and dispatches
-events directly from this thread.  The UI thread is the thread in which the
-<strong><a href="../reference/api/org/eclipse/swt/widgets/Display.html">Display</a></strong>
-was created.  All other widgets must be created in the UI thread.</p>
-
-<P>Since all event code is triggered from the application's UI thread,
-application code that handles events can freely access the widgets and
-make graphics calls without any special techniques.  However, the application
-is responsible for forking computational threads when performing long
-operations in response to an event.</P>
-
-<blockquote><em>Note:  SWT will trigger an 
-<strong><a href="../reference/api/org/eclipse/swt/SWTException.html">SWTException</a></strong>
-for any calls made from a non-UI thread that must be made from the UI
-thread.</em></blockquote>
-
-<P>The main thread, including the event loop, for an SWT application has
-the following structure:</p>
-
-<pre>
-   public static void main (String [] args) {
-      Display display = new Display ();
-      Shell shell = new Shell (display);
-      shell.open ();
-      // start the event loop. We stop when the user has done
-      // something to dispose our window.
-      while (!shell.isDisposed ()) {
-         if (!display.readAndDispatch ())
-            display.sleep ();
-      }
-      display.dispose ();
-   }
-</pre>
-
-<P>Once the widgets are created and the shell is opened, the application
-reads and dispatches events from the OS queue until the shell window is
-disposed. If there are no events available for us in the queue, we tell the
-display to sleep to give other applications a chance to run.</P>
-
-<P>SWT provides special access methods for calling widget and graphics code
-from a background thread.</P>
-
-
-<H3><a name="syncExec">Executing code from a non-UI thread</a></H3>
-
-<P>Applications that wish to call UI code from a non-UI thread must provide a
-<strong>Runnable</strong> that calls the UI code. The methods
-<strong>syncExec(Runnable)</strong> and <strong>asyncExec(Runnable)</strong>
-in the <strong><a href="../reference/api/org/eclipse/swt/widgets/Display.html">Display</a></strong>
-class are used to execute these runnables in the UI thread during the event
-loop.</p>
-
-<ul>
-  <li><strong>syncExec(Runnable)</strong> should be used when the application
-      code in the non-UI thread depends on the return value from the UI code
-      or otherwise needs to ensure that the runnable is run to completion
-      before returning to the thread. SWT will block the calling thread until
-      the runnable has been run from the application's UI thread. For example,
-      a background thread that is computing something based on a window's
-      current size would want to synchronously run the code to get the window's
-      size and then continue with its computations.</li>
-  <li><strong>asyncExec(Runnable)</strong> should be used when the application
-      needs to perform some UI operations, but is not dependent upon the
-      operations being completed before continuing. For example, a background
-      thread that updates a progress indicator or redraws a window could
-      request the update asynchronously and continue with its processing.  In
-      this case, there is no guaranteed relationship between the timing of the
-      background thread and the execution of the runnable.</li>
-</ul>
-
-<P>The following code snippet demonstrates the pattern for using these methods:</P>
-
-<pre>
-   // do time-intensive computations
-   ...
-   // now update the UI. We don't depend on the result,
-   // so use async.
-   display.asyncExec (new Runnable () {
-      public void run () {
-         if (!myWindow.isDisposed())
-            myWindow.redraw ();
-      }
-   });
-   // now do more computations
-   ...
-</pre>
-
-<p>It is good practice to check if your widget is disposed from within the runnable
-when using asyncExec.  Since other things can happen in the UI thread between
-the call to <code>asyncExec</code> and the execution of your runnable,
-you can never be sure what state your widgets are in by the time your runnable
-executes.</p>
-
-
-<H3><a name="workbench_threads">The workbench and threads</a></H3>
-
-<p>The threading rules are very clear when you are implementing an SWT
-application from the ground up since you control the creation of the event
-loop and the decision to fork computational threads in your application.</P>
-
-<P>Things get a bit more complicated when you are contributing plug-in code
-to the workbench.  The following rules can be considered "rules of engagement"
-when using platform UI classes, although from release to release there may be
-exceptions to these rules:</P>
-
-<ul>
-  <li>In general, any workbench UI extensions you add to the platform will be
-  executing in the workbench's UI thread, unless they are specifically related
-  to threads or background jobs (such as background job progress indication).</li>
-  <li>If you receive an event from the workbench, it is not guaranteed that it is
-  executing in the UI thread of the workbench.  Consult the javadoc for the particular
-  class that defines the listener or event.  If there is no specific documentation
-  discussing threading, and the class is clearly a UI-related class, you may expect that
-  the event arrives in the UI thread of the workbench.</li>
-  <li>Likewise, a platform UI library should not be considered thread-safe unless it is
-  specifically documented as such.  Note that most platform UI classes dispatch listeners
-  from the calling thread that triggered the event.  Workbench and JFace API calls do not 
-  check that the caller is executing in the UI thread.This means that your plug-in may
-  introduce a problem if you call a method that triggers an event from a non-UI thread.
-  SWT triggers an <strong><a href="../reference/api/org/eclipse/swt/SWTException.html">SWTException</a></strong>
-  for all API calls made from a non-UI thread. In general, avoid calling platform UI code from 
-  another thread unless the javadoc specifically allows it.</li>
-   <li>If your plug-in forks a computational thread or uses a workbench Job, it must use the
-      <strong><a href="../reference/api/org/eclipse/swt/widgets/Display.html">Display</a></strong>
-      <strong>asyncExec(Runnable)</strong> or <strong>syncExec(Runnable)</strong>
-      methods when calling any API for the workbench, JFace, or SWT, unless the API specifically
-      allows call-in from a background thread.</li>
-  <li>If your plug-in uses the JFace
-      <a href="../reference/api/org/eclipse/jface/operation/IRunnableContext.html"><strong>IRunnableContext</strong></a>
-      interface to invoke a progress monitor and run an operation, it supplies
-      an argument to specify whether a computational thread is forked for
-      running the operation.</li>
-</ul>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets.htm b/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets.htm
deleted file mode 100644
index d6e1999..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets.htm
+++ /dev/null

@@ -1,180 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Widgets</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H2>Widgets</H2>
-
-<P>SWT includes many rich features, but a basic knowledge of the system's core -
-<em>widgets</em>, <em>layouts</em>, and <em>events</em> - is all that is needed
-to implement useful and robust applications.</P>
-
-
-<H3>Widget application structure</H3>
-
-<P>When you are contributing UI elements using platform workbench extensions,
-the mechanics of starting up SWT are handled for you by the workbench.</P>
-
-<P>If you are writing an SWT application from scratch outside of the
-workbench, you must understand more about SWT's application structure.</P>
-
-<P>A typical stand-alone SWT application has the following structure:</P>
-
-<ul>
-  <li>Create a
-      <strong><a href="../reference/api/org/eclipse/swt/widgets/Display.html">Display</a></strong>
-      which represents an SWT session.</li>
-  <li>Create one or more
-      <strong><a href="../reference/api/org/eclipse/swt/widgets/Shell.html"> Shell</a></strong>s
-      which serve as the main window(s) for the application.</li>
-  <li>Create any other widgets that are needed inside the shell.</li>
-  <li>Initialize the sizes and other necessary state for the widgets. Register
-      listeners for widget events that need to be handled.</li>
-  <li>Open the shell window.</li>
-  <li>Run the event dispatching loop until an exit condition occurs, which
-      is typically when the main shell window is closed by the user.</li>
-  <li>Dispose the display.</li>
-</ul>
-
-<P>The following code snippet is adapted from the
-<strong><a href="../samples/org.eclipse.swt.examples/doc-html/swt_helloworld_ex.html">org.eclipse.swt.examples.helloworld.HelloWorld2</a></strong>
-application. Since the application only displays the string &quot;Hello World,&quot;
-it does not need to register for any widget events.</P>
-
-<pre>
-   public static void main (String [] args) {
-      Display display = new Display ();
-      Shell shell = new Shell (display);
-      Label label = new Label (shell, SWT.CENTER);
-      label.setText (&quot;Hello_world&quot;);
-      label.setBounds (shell.getClientArea ());
-      shell.open ();
-      while (!shell.isDisposed ()) {
-         if (!display.readAndDispatch ()) display.sleep ();
-      }
-      display.dispose ();
-   }
-</pre>
-
-
-<H4>Display</H4>
-
-<P>The <strong><a href="../reference/api/org/eclipse/swt/widgets/Display.html">Display</a></strong>
-represents the connection between SWT and the underlying platform's GUI system.
-Displays are primarily used to manage the platform event loop and control
-communication between the UI thread and other threads. (See
-<a HREF="swt_threading.htm" CLASS="XRef">Threading issues for clients</a> for
-a complete discussion of UI threading issues.)</P>
-
-<P>For most applications you can follow the pattern that is used above.  You
-must create a display before creating any windows, and you must dispose of
-the display when your shell is closed. You don't need to think about the
-display much more unless you are designing a multi-threaded application.</P>
-
-
-<H4>Shell</H4>
-
-<P>A <strong><a href="../reference/api/org/eclipse/swt/widgets/Shell.html">Shell</a></strong>
-is a &quot;window&quot; managed by the OS platform window manager. Top level
-shells are those that are created as a child of the display. These windows are
-the windows that users move, resize, minimize, and maximize while using the
-application. Secondary shells are those that are created as a child of another
-shell. These windows are typically used as dialog windows or other transient
-windows that only exist in the context of another window.</P>
-
-
-<H4>Parents and children</H4>
-
-<P>All widgets that are not top level shells must have a parent. Top level
-shells do not have a parent, but they are created in association with a
-particular
-<strong><a href="../reference/api/org/eclipse/swt/widgets/Display.html">Display</a></strong>.
-You can access this display using <strong>getDisplay()</strong>.
-All other widgets are created as descendants (direct or indirect) of top level
-shells.</P>
-
-<P><strong><a href="../reference/api/org/eclipse/swt/widgets/Composite.html">Composite</a></strong>
-widgets are widgets that can have children.</P>
-
-<P>When you see an application window, you can think of it as a widget tree, or
-hierarchy, whose root is the shell. Depending on the complexity of the
-application, there may be a single child of the shell, several children, or
-nested layers of composites with children.</P>
-
-
-<H4>Style bits</H4>
-
-<P>Some widget properties must be set at the time a widget is created and
-cannot be subsequently changed. For example, a list may be single or
-multi-selection, and may or may not have scroll bars.</P>
-
-<P>These properties, called <em>styles</em>, are set in the constructor.  All
-widget constructors take an <strong>int</strong> argument that specifies
-the bitwise <strong>OR</strong> of all desired styles. In some cases, a
-particular style is considered a hint, which means that it may not be
-available on all platforms, but will be gracefully ignored on platforms that
-do not support it.</P>
-
-<P>The style constants are located in the
-<strong><a href="../reference/api/org/eclipse/swt/SWT.html">SWT</a></strong>
-class as public static fields. A list of applicable constants for each
-widget class is contained in the API Reference for
-<strong><a href="../reference/api/org/eclipse/swt/SWT.html">SWT</a></strong>.</P>
-
-
-<H4>Resource disposal</H4>
-
-<P>The platforms underneath SWT require explicit allocation and freeing of
-OS resources.  In keeping with the SWT design philosophy of reflecting the
-platform application structure in the widget toolkit, SWT requires that you
-explicitly free any OS resources that you have allocated.  In SWT, the
-<strong>Widget.dispose()</strong> method is used to free resources associated
-with a particular toolkit object.</P>
-
-<P>The rule of thumb is that if you create the object, you must dispose of it.
-Here are some specific ground rules that further explain this philosophy:</P>
-
-<ul>
-  <li>If you create a graphic object or widget using a constructor, you must
-      explicitely dispose of it when you are finished using it.</li>
-  <li>When a
-      <a href="../reference/api/org/eclipse/swt/widgets/Composite.html"><strong>Composite</strong></a>,
-      is disposed, the composite and all of its child widgets are recursively disposed. In this
-      case, you do not need to dispose of the widgets themselves. However, you
-      must free any graphics resources allocated in conjunction with those widgets.</li>
-  <li>If you get a graphic object or widget without using a constructor (e.g. Control.getBackground()),
-      do not dispose of it since you did not allocate it.</li>
-  <li>If you pass a reference to your widget or graphic object to another
-      object, you must take care not to dispose of it while it is still
-      being used.  (Similar to the rule described in
-      <a HREF="jface_resources.htm#jface_resources_patterns" CLASS="XRef">Plug-in
-      patterns for using images</a>.)</li>
-  <li>If you create a graphic object for use during the lifetime of one of your
-      widgets, you must dispose of the graphic object when the widget is
-      disposed. This can be done by registering a dispose listener for your
-      widget and freeing the graphic object when the <strong>dispose</strong>
-      event is received.</li>
-</ul>
-
-<p>There is one exception to these rules.  Simple data objects, such as
-<strong><a href="../reference/api/org/eclipse/swt/graphics/Rectangle.html">Rectangle</a></strong> and
-<strong><a href="../reference/api/org/eclipse/swt/graphics/Point.html">Point</a></strong>,
-do not use operating system resources. They do not have a
-<strong>dispose()</strong> method and you do not have to free them.  If in
-doubt, check the javadoc for a particular class.</p>
-
-<p>See <a href="http://www.eclipse.org/articles/swt-design-2/swt-design-2.html">Managing
-operating resources</a> for further discussion of this topic.</p>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_controls.htm b/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_controls.htm
deleted file mode 100644
index a46df2f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_controls.htm
+++ /dev/null

@@ -1,239 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Controls</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H3>Controls</H3>
-
-<p>A <a href="../reference/api/org/eclipse/swt/widgets/Control.html"><strong>Control</strong></a>
-is a widget that you can create and place anywhere you want in your widget
-parent/child tree.  The <a href="../reference/api/org/eclipse/swt/package-summary.html">SWT
-API reference</a> and examples contains detailed information about the
-different kinds of controls and their usage.  The
-<strong><a href="../reference/api/org/eclipse/swt/widgets/package-summary.html">org.eclipse.swt.widgets</a></strong>
-package defines the core set of widgets in SWT.  The following table summarizes
-the concrete types of controls provided in this package.</p>
- 
-
-<table border="1" width="600">
-<colgroup>
-    <col width="34%">
-    <col width="66%">
-</colgroup>
-<tr>
-<th><div CLASS="CellHeading">Widget</div></th>
-<th><div CLASS="CellHeading">Purpose</div></th>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/browser/Browser.html">Browser</a></strong></td>
-<td>Control containing a native HTML renderer.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Button.html">Button</a></strong></td>
-<td>Selectable control that issues notification when pressed and/or
-released.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Canvas.html">Canvas</a></strong></td>
-<td>Composite control that provides a surface for drawing arbitrary graphics.
-Often used to implement custom controls.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Caret.html">Caret</a></strong></td>
-<td>An i-beam that is typically used as the insertion point for text.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Combo.html">Combo</a></strong></td>
-<td>Selectable control that allows the user to choose a string from a list of
-strings, or optionally type a new value into an editable text field.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Composite.html">Composite</a></strong></td>
-<td>Control that is capable of containing other widgets.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/CoolBar.html">CoolBar</a></strong></td>
-<td>Composite control that allows users to dynamically reposition the cool items
-contained in the bar.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/CoolItem.html">CoolItem</a></strong></td>
-<td>Selectable user interface object that represents a dynamically positionable
-area of a cool bar.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Group.html">Group</a></strong></td>
-<td>Composite control that groups other widgets and surrounds them with an
-etched border and/or label.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Label.html">Label</a></strong></td>
-<td>Non-selectable control that displays a string or an image.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Link.html">Link</a></strong></td>
-<td>Selectable control that displays a text with links.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/List.html">List</a></strong></td>
-<td>Selectable control that allows the user to choose a string or strings from a
-list of strings.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Menu.html">Menu</a></strong></td>
-<td>User interface object that contains menu items.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/MenuItem.html">MenuItem</a></strong></td>
-<td>Selectable user interface object that represents an item in a menu.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/ProgressBar.html">ProgressBar</a></strong></td>
-<td>Non-selectable control that displays progress to the user, typically in the
-form of a bar graph.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Sash.html">Sash</a></strong></td>
-<td>Selectable control that allows the user to drag a rubber banded outline of
-the sash within the parent window.  Used to allow users to resize child widgets
-by repositioning their dividing line.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Scale.html">Scale</a></strong></td>
-<td>Selectable control that represents a range of numeric values.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/ScrollBar.html">ScrollBar</a></strong></td>
-<td>Selectable control that represents a range of positive numeric values. Used
-in a Composite that has V_SCROLL and/or H_SCROLL styles.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Shell.html">Shell</a></strong></td>
-<td>Window that is managed by the OS window manager. Shells can be parented by
-a Display (top level shells) or by another shell (secondary shells).</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Slider.html">Slider</a></strong></td>
-<td>Selectable control that represents a range of numeric values.  A slider is
-distinguished from a scale by providing a draggable thumb that can adjust the
-current value along the range.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Spinner.html">Spinner</a></strong></td>
-<td>Selectable control that allows the user to enter and modify numeric
-values.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/TabFolder.html">TabFolder</a></strong></td>
-<td>Composite control that groups pages that can be selected by the user using
-labeled tabs.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/TabItem.html">TabItem</a></strong></td>
-<td>Selectable user interface object corresponding to a tab for a page in a tab
-folder.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Table.html">Table</a></strong></td>
-<td>Selectable control that displays a list of table items that can be selected
-by the user.  Items are presented in rows that display multiple columns
-representing different aspects of the items.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/TableColumn.html">TableColumn</a></strong></td>
-<td>Selectable user interface object that represents a column in a table.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/TableItem.html">TableItem</a></strong></td>
-<td>Selectable user interface object that represents an item in a table.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Text.html">Text</a></strong></td>
-<td>Editable control that allows the user to type text into it.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/ToolBar.html">ToolBar</a></strong></td>
-<td>Composite control that supports the layout of selectable tool bar
-items.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/ToolItem.html">ToolItem</a></strong></td>
-<td>Selectable user interface object that represents an item in a tool bar.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Tracker.html">Tracker</a></strong></td>
-<td>User interface object that implements rubber banding rectangles.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Tray.html">Tray</a></strong></td>
-<td>Represents the system tray that is part of the task bar status area on some
-operating systems.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/TrayItem.html">TrayItem</a></strong></td>
-<td>Selectable user interface object that represents an item in the operating
-system's system tray.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Tree.html">Tree</a></strong></td>
-<td>Selectable control that displays a hierarchical list of tree items that can
-be selected by the user.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/TreeColumn.html">TreeColumn</a></strong></td>
-<td>Selectable user interface object that represents a column in a tree.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/TreeItem.html">TreeItem</a></strong></td>
-<td>Selectable user interface object that represents a hierarchy of tree items
-in a tree.</td>
-</tr>
-</table>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_custom.htm b/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_custom.htm
deleted file mode 100644
index 45e1c37..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_custom.htm
+++ /dev/null

@@ -1,171 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Custom widgets</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Custom widgets</h3>
-
-<P>You may want to extend SWT by implementing your own custom widget. SWT itself provides a package,
-<strong><a href="../reference/api/org/eclipse/swt/custom/package-summary.html">org.eclipse.swt.custom</a></strong>,
-which contains custom controls that are not in the core set of SWT controls but are
-needed to implement the platform workbench.</P>
-
-<table border="1" width="600">
-<colgroup>
-    <col width="34%">
-    <col width="66%">
-</colgroup>
-<tr>
-<th><div CLASS="CellHeading">Control</div></th>
-<th><div CLASS="CellHeading">Purpose</div></th>
-</tr>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/custom/CBanner.html">CBanner</a></strong></td>
-<td>CBanner is used in the workbench to layout the toolbar area and
-perspective switching toolbar.</td>
-</tr>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/custom/CCombo.html">CCombo</a></strong></td>
-<td>Similar to Combo, but is vertically resizable allowing it to fit inside table cells.</td>
-</tr>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/custom/CLabel.html">CLabel</a></strong></td>
-<td>Similar to Label, but supports shortening of text with an ellipsis. Also supports
-a gradient effect for the background color as seen in the active workbench view.
-Does not support wrapping.</td>
-</TR>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/custom/CTabFolder.html">CTabFolder</a></strong></td>
-<td>Similar to TabFolder, but supports additional configuration of the visual
-appearance of tabs (top or bottom) and borders.</td>
-</TR>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/custom/CTabItem.html">CTabItem</a></strong></td>
-<td>Selectable user interface object corresponding to a tab for a page in a
-CTabFolder.</td>
-</TR>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/custom/SashForm.html">SashForm</a></strong></td>
-<td>Composite control that lays out its children in a row or column arrangement
-and uses a Sash to separate them so that the user can resize them.</td>
-</TR>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/custom/ScrolledComposite.html">ScrolledComposite</a></strong></td>
-<td>Composite control that scrolls its contents and optionally stretches its
-contents to fill the available space.</td>
-</TR>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/custom/StyledText.html">StyledText</a></strong></td>
-<td>Editable control that allows the user to type text.  Ranges of text inside
-the control can have distinct colors and font styles.</td>
-</TR>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/custom/ViewForm.html">ViewForm</a></strong></td>
-<td>ViewForm is used in the workbench to position and size a view's label/toolbar/menu local bar.</td>
-</tr>
-</table>
-
-
-
-<h4>Implementing a custom widget</h4>
-
-<p>Once you've determined that you need a custom widget and have decided which
-platforms must be supported, you can consider several implementation techniques
-for your widget. These techniques can be mixed and matched depending on what
-is available in the underlying OS platform.</p>
-
-
-<h4>Native implementation</h4>
-
-<p>If your application requires a native widget that is not provided by SWT,
-you will need to implement it natively. This may be a platform widget, a third
-party widget, or any other widget in a platform shared library.  A complete
-example of a native custom widget implementation can be found in
-<a href="http://www.eclipse.org/articles/Article-Writing%20Your%20Own%20Widget/Writing%20Your%20Own%20Widget.htm">Creating
-Your Own Widgets using SWT</a>.</p>
-
-
-<h4>Combining existing widgets</h4>
-
-<p>Widgets can be combined to form widgets that are more sophisticated.  For
-example, a Combo can be implemented using a text entry widget along with a
-button and a drop-down list.  To implement a combined widget, you create a
-subclass of
-<a href="../reference/api/org/eclipse/swt/widgets/Composite.html"><strong>Composite</strong></a>
-and manage the children internally.</p>
-
-<p>A simple example can be found in
-<a href="../reference/api/org/eclipse/swt/custom/CCombo.html"><strong>CCombo</strong></a>.</p>
-
-<h4>Custom drawn implementation</h4>
-
-<p>In some cases, you don't have any native code or existing widgets that help
-you in the implementation of your new widget. This means you must draw the
-widget yourself in the handler for the Paint event.  Although this technique
-can become quite complicated, it has the advantage of producing a completely
-portable implementation.</p>
-
-<p>Custom drawn controls are implemented by subclassing the
-<a href="../reference/api/org/eclipse/swt/widgets/Canvas.html"><strong>Canvas</strong></a> or
-<a href="../reference/api/org/eclipse/swt/widgets/Composite.html"><strong>Composite</strong></a>.
-Subclass <a href="../reference/api/org/eclipse/swt/widgets/Canvas.html"><strong>Canvas</strong></a>
-if your widget will not contain any child controls.</p>
-
-<P>The internal implementation of a custom drawn widget usually involves these
-major tasks:</P>
-
-<ul>
-  <li>Create any graphics objects needed in your constructor and store them in
-      an instance variable. Register a listener for the <strong>dispose</strong>
-      event on your canvas or composite so that you can free these objects
-      when the widget is destroyed.</li>
-  <li>Add a <strong>paintListener</strong> to your canvas or composite and
-      paint the widget according to your design. For complex widgets, a lot
-      of work goes into optimizing this process by calculating and repainting
-      only what's absolutely necessary.</li>
-  <li>Ensure that any API calls that affect the appearance of your widget
-      trigger a repaint of the widget. In general, you should use
-      <strong>redraw</strong> to damage your widget when you know you must
-      repaint, rather than call your internal painting code directly. This
-      gives the platform a chance to collapse the paint you want to generate
-      with any other pending paints and helps streamline your code by funneling
-      all painting through one place.</li>
-  <li>If your widget defines events in its API, determine what low level
-      <a href="../reference/api/org/eclipse/swt/widgets/Canvas.html"><strong>Canvas</strong></a> or
-      <a href="../reference/api/org/eclipse/swt/widgets/Composite.html"><strong>Composite</strong></a>
-      events will trigger your widget's events. For example, if you have a
-      clicked event, you will want to register a mouse event on your canvas and
-      perform calculations (such as hit testing) to determine whether the mouse
-      event in your canvas should trigger your widget event.</li>
-</ul>
-
-<P>Many of the widgets implemented in the
-<a href="../reference/api/org/eclipse/swt/custom/package-summary.html"><strong>org.eclipse.swt.custom</strong></a>
-use this approach. A simple example can be found in
-<a href="../reference/api/org/eclipse/swt/custom/CLabel.html"><strong>CLabel</strong></a>.</P>
-
-<P>Further information on custom widgets can be found in
-<a href="http://www.eclipse.org/articles/Article-Writing%20Your%20Own%20Widget/Writing%20Your%20Own%20Widget.htm">Creating
-your own widgets using SWT.</a></P>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_events.htm b/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_events.htm
deleted file mode 100644
index e4bfb78..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_events.htm
+++ /dev/null

@@ -1,245 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Events</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H3>Events</H3>
-
-<P>Once we create a display and some widgets, and start up the application's
-message loop, where does the real work happen? It happens every time an event is
-read from the queue and dispatched to a widget. Most of the application logic is
-implemented as responses to user events.</P>
-
-<P>The basic pattern is that you add a listener to some widget that you have
-created, and when the appropriate event occurs the listener code will be
-executed. This simple example is adapted from
-<strong>org.eclipse.swt.examples.helloworld.HelloWorld3</strong>:</P>
-
-<pre>
-   Display display = new Display ();
-   Shell shell = new Shell (display);
-   Label label = new Label (shell, SWT.CENTER);
-   ...
-   shell.addControlListener (new ControlAdapter () {
-      public void controlResized (ControlEvent e) {
-         label.setBounds (shell.getClientArea ());
-      }
-   });
-</pre>
-
-<P>For each type of listener, there is an interface that defines the listener
-(<em>Xyz</em><strong>Listener</strong>), a class that provides event information
-(<em>Xyz</em><strong>Event</strong>), and an API method to add the listener
-(<strong>add</strong><em>Xyz</em><strong>Listener</strong>).  If there is more
-than one method defined in the listener interface then there is an adapter
-(<em>Xyz</em><strong>Adapter</strong>) that implements the listener interface
-and provides empty methods.   All of the events, listeners,
-and adapters are defined in the package
-<strong><a href="../reference/api/org/eclipse/swt/events/package-summary.html">org.eclipse.swt.events</a></strong>.</P>
-
-<P>The following tables summarize the events that are available and the widgets
-that support each event.  Events can be split into two general categories:
-high level events which represent a logical operation on a control, and low
-level events which describe more specific user interactions.  High level events
-may be represented by multiple low level events which may differ per
-platform.  Low level events should generally only be used for custom widget
-implementations.</P>
-
-
-<h4>High level events</h4>
-
-<TABLE BORDER="1" width="600">
-<colgroup>
-    <col width="34%">
-    <col width="66%">
-</colgroup>
-<TR>
-<TH><P CLASS="CellHeading">Event Type</P></TH>
-<TH><P CLASS="CellHeading">Description</P></TH>
-</TR>
-
-<tr>
-<td><strong>Activate</strong>, <strong>Decativate</strong></td>
-<td>Generated when a Control is activated or deactivated.</td>
-</tr>
-
-<TR>
-<td><strong>Arm</strong></td>
-<td>A MenuItem is armed (highlighted and ready to be selected).</td>
-</TR>
-
-<TR>
-<td><strong>Close</strong></td>
-<td>A Shell is about to close as requested by the window manager.</td>
-</TR>
-
-<TR>
-<td><strong>DefaultSelection</strong></td>
-<td>The user selects an item by invoking a default selection action.  For
-example, by hitting Enter or double clicking on a row in a Table.</td>
-</tr>
-
-<TR>
-<td><strong>Dispose</strong></td>
-<td>A widget is about to be disposed, either programmatically or by user.</td>
-</TR>
-
-<tr>
-<td><strong>DragDetect</strong></td>
-<td>The user has initiated a possible drag operation.</td>
-</tr>
-
-<TR>
-<td><strong>Expand</strong>, <strong>Collapse</strong></td>
-<td>An item in a Tree is expanded or collapsed.</td>
-</TR>
-
-<TR>
-<td><strong>Help</strong></td>
-<td>The user has requested help for a widget.  For example, this occurs when
-the F1 key is pressed under Windows.</td>
-</TR>
-
-<TR>
-<td><strong>Iconify</strong>, <strong>Deiconify</strong></td>
-<td>A Shell has been minimized, maximized, or restored.</td>
-</TR>
-
-<tr>
-<td><strong>MenuDetect</strong></td>
-<td>The user has requested a context menu.</td>
-</tr>
-
-<TR>
-<td><strong>Modify</strong></td>
-<td>The widget's text has been modified.</td>
-</TR>
-
-<TR>
-<td><strong>Move</strong>, <strong>Resize</strong></td>
-<td>A control has changed position or has been resized, either programmatically
-or by user.</td>
-</TR>
-
-<tr>
-<td><strong>Selection</strong></td>
-<td>The user selects an item in the control.  For example, by single clicking
-on a row in a Table or by keyboard navigating through the items.</td>
-</tr>
-
-<tr>
-<td><strong>SetData</strong></td>
-<td>Data needs to be set on a TableItem when using a virtual table.</td>
-</tr>
-
-<tr>
-<td><strong>Show</strong>, <strong>Hide</strong></td>
-<td>A control's visibility has changed.</td>
-</tr>
-
-<TR>
-<td><strong>Traverse</strong></td>
-<td>The user is trying to traverse out of the control using a keystroke.  For
-example, the escape or tab keys are used for traversal.</td>
-</TR>
-
-<TR>
-<td><strong>Verify</strong></td>
-<td>A widget's text is about to be modified.  This event gives the application
-a chance to alter the text or prevent the modification.</td>
-</TR>
-</TABLE>
-
-
-<h4>Low level events</h4>
-
-<TABLE BORDER="1" width="600">
-<colgroup>
-    <col width="34%">
-    <col width="66%">
-</colgroup>
-<TR>
-<TH><P CLASS="CellHeading">Event Type</P></TH>
-<TH><P CLASS="CellHeading">Description</P></TH>
-</TR>
-
-<TR>
-<td><strong>FocusIn</strong>, <strong>FocusOut</strong></td>
-<td>A control has gained or lost focus.</td>
-</TR>
-
-<TR>
-<td><strong>KeyDown</strong>, <strong>KeyUp</strong></td>
-<td>The user has pressed or released a keyboard key when the control has
-keyboard focus.</td>
-</TR>
-
-<TR>
-<td><strong>MouseDown</strong>, <strong>MouseUp</strong>,
-<strong>MouseDoubleClick</strong></td>
-<td>The user has pressed, released, or double clicked the mouse over the
-control.</td>
-</TR>
-
-<TR>
-<td><strong>MouseMove</strong></td>
-<td>The user has moved the mouse above the control.</td>
-</TR>
-
-<TR>
-<td><strong>MouseEnter</strong>, <strong>MouseExit</strong>,
-<strong>MouseHover</strong></td>
-<td>The mouse has entered, exited, or hovered over the control.</td>
-</TR>
-
-<TR>
-<td><strong>MouseWheel</strong></td>
-<td>The mouse wheel has been rotated.</td>
-</TR>
-
-<TR>
-<td><strong>Paint</strong></td>
-<td>The control has been damaged and requires repainting.</td>
-</TR>
-</table>
-
-
-<H4>Untyped events</H4>
-<P>In addition to the typed event system described above, SWT supports a low level,
-untyped widget event mechanism.  The untyped mechanism relies on a constant to 
-identify the event type and defines a generic listener that is supplied with 
-this constant. This allows the listener to implement a &quot;case style&quot; listener.
-In the following snippet, we define a generic event handler and add several listeners to a shell.</P>
-
-<pre>
-   Shell shell = new Shell ();
-   Listener listener = new Listener () {
-      public void handleEvent (Event e) {
-         switch (e.type) {
-            case SWT.Resize:
-               System.out.println (&quot;Resize received&quot;);
-               break;
-            case SWT.Paint:
-               System.out.println (&quot;Paint received&quot;);
-               break;
-            default:
-               System.out.println (&quot;Unknown event received&quot;);
-         }
-      }
-   };
-   shell.addListener (SWT.Resize, listener);
-   shell.addListener (SWT.Paint, listener);
-</pre>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team.htm b/bundles/org.eclipse.platform.doc.isv/guide/team.htm
deleted file mode 100644
index 680b0be..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team.htm
+++ /dev/null

@@ -1,111 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Team support</title>
-  <link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-<body bgcolor="#ffffff">
-<h1>
-Team support</h1>
-<p>The Eclipse Team support defines API that allow plug-ins to
-integrate the function of a versioning and configuration management
-repository. The function provided by a repository fundamentally affects
-the user workflow, since there are additional steps for retrieving
-files, comparing their content with local content, versioning them, and
-returning updated files to the repository. The goal of the team plug-in
-API is to be passive enough to allow repository plug-in providers to
-define their own workflow so that users familiar with their product can
-use the platform in a similar fashion and provide support for worflows
-that we have found are useful for team plug-ins. </p>
-<p>
-This goal is accomplished by supplying several building blocks:
-</p>
-<ul>
-  <li><a href="team_provider_repository.htm">Repository Providers</a>
-    <blockquote> A repository provider allows synchronization of
-workspace resources with a remote location. At a minimum it allows
-pushing resources in the workspace to a remote location and pulling
-resources from a remote location into the workspace. A repository
-provider is associated with a project and controls the resources in the
-project by optionally providing a <a
- href="../reference/api/org/eclipse/core/resources/IFileModificationValidator.html">IFileModificationValidator
-      </a>and <a
- href="../reference/api/org/eclipse/core/resources/team/IMoveDeleteHook.html">IMoveDeleteHook</a>.
-There is only one repository provider associated with each project. A
-user associates a repository provider with a project by providing a <a
- href="../reference/api/org/eclipse/team/ui/IConfigurationWizard.html">IConfigurationWizard</a>.
-Repository providers can also participate in exporting and importing of
-projects into the workspace via the team project set feature. To
-support this a repository provider should implement a <a
- href="../reference/api/org/eclipse/team/core/ProjectSetCapability.html">ProjectSetCapability</a>.<br>
-    </blockquote>
-  </li>
-  <li><a href="team_resources.htm">Resource Management</a>
-    <blockquote> Allows other plug-ins to indicate special handling of resources 
-      with respect to team operations. The repository provider can mark resources 
-      as team-private which essentially hides the resource from other plug-ins. 
-      This is done via the <a href="../reference/api/org/eclipse/core/resources/IResource.html#setTeamPrivateMember(boolean)">IResource#setTeamPrivateMember</a> 
-      method and is commonly done to hide repository provider specific meta-files 
-      from the user. Also, builders will often mark build output as derived which 
-      is a hint to a repository provider that the resource is transient and could 
-      be ignored by the repository provider. A provider can check this flag on 
-      a resource via the <a href="../reference/api/org/eclipse/core/resources/IResource.html#isDerived()">IResource#isDerived</a> 
-      method.<br>
-      <br>
-      In addition, other plug-ins can add provide hints to the repository provider 
-      about file type information via the <a
- href="../reference/extension-points/org_eclipse_team_core_fileTypes.html">org.eclipse.team.core.fileTypes</a> 
-      extension and about common files that should be ignored by the repository 
-      via the <a
- href="../reference/extension-points/org_eclipse_team_core_ignore.html">org.eclipse.team.core.ignore</a> 
-      extension.<br>
-    </blockquote>
-  </li>
-</ul>
-<ul>
-  <li><a href="team_synchronize.htm">Synchronization Support</a> [<b>new
-in 3.0</b>]
-    <blockquote> Synchronize support provides classes and interfaces
-for managing dynamic collections of synchronization information (<a
- href="../reference/api/org/eclipse/team/core/synchronize/SyncInfo.html">SyncInfo</a>,
-      <a href="../reference/api/org/eclipse/team/core/synchronize/SyncInfoSet.html">SyncInfoSet</a>).
-This support helps you manage information about variants of the
-resources in the workspace. For example, with FTP you could store
-timestamps for the latest remote file and the base for the currently
-loaded resource. Synchronization support provides APIs to help manage
-and persist resource variants and display synchronization state to the
-user.<br>
-    </blockquote>
-  </li>
-</ul>
-
-<p>The UI support is also structured passively.&nbsp; Placeholders for
-team
-provider actions, preferences, and properties are defined by the team
-UI
-plug-in, but it's up to the team plug-in provider to define these UI
-elements.&nbsp; The team UI plug-in also includes a simple, extendable
-configuration wizard that lets users associate projects with
-repositories.&nbsp;
-Plug-ins can supply content for this wizard that let the user specify
-repository
-specific information.&nbsp;
-</p>
-<p>Multiple repository providers can coexist peacefully within the
-platform.&nbsp; In fact, it's even possible to have different client
-implementations for the same repository installed. For example, one
-could
-install a CVS client designed for experts and a different one for
-novice users.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_howto.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_howto.htm
deleted file mode 100644
index 4618ef6..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_howto.htm
+++ /dev/null

@@ -1,274 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Rich Team Integration</title>
-  <link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-<body bgcolor="#ffffff">
-<h2>Rich Team Integration</h2>
-<p>
-Integrating your repository's support with the platform starts with
-good solid
-design.&nbsp; The goal is to integrate the workflow that your
-repository users
-know with the concepts defined in the workbench.&nbsp; Because there
-are many
-ways to extend workbench UI and functionality, you have a lot of
-flexibility in
-how you achieve integration.&nbsp; So where to start?</p>
-<p>Building a team provider is not just a matter of learning Team
-API.&nbsp; (Subsequent sections will focus on the specific support
-introduced by the team plug-in.)&nbsp; It's a matter of understanding <a
- href="workbench.htm">workbench integration</a>.&nbsp; So let's start
-with the big picture.&nbsp; We'll be using the CVS client as a case
-study for integrating a team provider with the platform. Let's look at
-some of the function the CVS provider supplies and what workbench and
-team facilities you can use to achieve similar levels of integration.</p>
-<p>
-<img
- alt="Workbench with CVS menu items, views, tasks, and decorators"
- src="images/teamintegration.png"></p>
-<p>The CVS client integrates seamlessly with the existing workbench
-resource perspective.&nbsp; It allows users to configure a project for
-CVS, adds functionality to a resource's menu, decorates resources with
-team-specific information, provides customized views that show
-team-specific information, adds team-oriented tasks to the task
-list...&nbsp; The list goes on and on.&nbsp; How can your provider
-achieve similar integration?&nbsp; Here are some basic steps to start
-with and links for information (both team-specific and
-workbench-oriented) on these topics.</p>
-<h3>Getting started</h3>
-<table width="73%" cellspacing="0" cellpadding="0" border="1">
-  <tbody>
-    <tr>
-      <td width="32%">Define a
-       <b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a>
-      </b>that represents your implementation.</td>
-      <td width="68%">
-      <ul>
-          <li><a href="team_provider_repository.htm#repository_pt">Define your 
-            provider using <b>org.eclipse.team.core.repository</b>.</a></li>
-          <li>Subclass <b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a> 
-            </b>and <a href="team_provider_repository.htm#repo_impl">implement 
-            the necessary methods.</a></li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td width="32%">Provide a configuration wizard so that users can
-associate your provider with their projects.</td>
-      <td width="68%">
-      <ul>
-          <li><a href="team_provider_repository.htm#ui_conf">Contribute a wizard 
-            using <b>org.eclipse.team.ui.configurationWizards</b>.</a></li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td width="32%">Add your actions to the Team menu.</td>
-      <td width="68%">
-      <ul>
-        <li><a href="team_ui_actions.htm">Add your actions to the Team
-menu.</a></li>
-        <li>Use the <a href="workbench_basicext_popupMenus.htm"><b>popupMenus</b></a>
-extension to define the menu items.</li>
-      </ul>
-      </td>
-    </tr>
-  </tbody>
-</table>
-<h3>Enhancing resource views</h3>
-<table width="73%" cellspacing="0" cellpadding="0" border="1">
-  <tbody>
-    <tr>
-      <td width="32%">Add provider-specific properties to the
-properties page for a resource.</td>
-      <td width="68%">
-      <ul>
-          <li> <a href="preferences_prop_implement.htm">Implement</a> and <a href="preferences_prop_contribute.htm">contribute</a> 
-            property pages to show team-specific properties for your resource.</li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td width="32%">Implement specialized decorators to show
-team-related attributes</td>
-      <td width="68%">
-      <ul>
-        <li><a href="team_ui_decorators.htm">Contribute decorators</a>
-to resource views.</li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td width="32%">Reduce clutter by filtering out any resources
-that are used in implementing team support.&nbsp;</td>
-      <td width="68%">
-      <ul>
-        <li>Use <a href="team_resources_private.htm">team-private
-resources</a> to hide implementation files and folders.</li>
-      </ul>
-      </td>
-    </tr>
-  </tbody>
-</table>
-<h3>Handling user editing and changes to resources</h3>
-<table width="73%" cellspacing="0" cellpadding="0" border="1">
-  <tbody>
-    <tr>
-      <td width="32%">Intervene in the saving of resources so you can
-check permissions before a user changes a file.</td>
-      <td width="68%">
-      <ul>
-        <li>Implement the <a href="team_provider_repository.htm#hooks">fileModificationValidator</a>
-hook.</li>
-        <li>Use <a
- href="../reference/api/org/eclipse/core/resources/IFileModificationValidator.html#validateSave(org.eclipse.core.resources.IFile)"><b>validateSave</b></a>
-to prevent or intervene in saving of files.</li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td width="32%">Intervene before a user edits a file to see if
-it's allowed.</td>
-      <td width="68%">
-      <ul>
-        <li>Implement the <a href="team_provider_repository.htm#hooks">fileModificationValidator</a>
-hook.</li>
-        <li>Use <a
- href="../reference/api/org/eclipse/core/resources/IFileModificationValidator.html#validateEdit(org.eclipse.core.resources.IFile[], java.lang.Object)"><b>validateEdit</b></a>
-to prevent or intervene in saving of files.</li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td width="32%">Track changes to resources in the workspace so
-you can allow associated changes in the repository.</td>
-      <td width="68%">
-      <ul>
-        <li>Use the <a href="team_provider_repository.htm#hooks">move/delete
-hooks</a> to prevent or enhance moving and deleting of resources.</li>
-        <li>See <a
- href="../reference/api/org/eclipse/core/resources/team/IMoveDeleteHook.html"><b>IMoveDeleteHook</b></a>
-          <b> </b>for more detail about what you can do.</li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td>Ensure that the proper resource locks are obtained for
-resource operations that invoke the move/delete hook or
-fileModificatonValidator.</td>
-      <td>
-      <ul>
-        <li>Use the <a href="team_provider_repository.htm#hooks">resource
-rule factory </a> to ensure that the proper rules are obtained for
-resource operations.</li>
-        <li>See <a
- href="../reference/api/org/eclipse/core/resources/team/ResourceRuleFactory.html"><b>ResourceRuleFactory</b></a>
-          <b> </b>for more details.</li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td width="32%">Enable the use of linked resources</td>
-      <td width="68%">
-      <ul>
-        <li>See <a href="team_resources_linked.htm"><b>Team and linked
-resources</b></a></li>
-      </ul>
-      </td>
-    </tr>
-  </tbody>
-</table>
-<h3>Streamlining repository-related tasks</h3>
-<table width="73%" cellspacing="0" cellpadding="0" border="1">
-  <tbody>
-    <tr>
-      <td width="32%">Provide an easy way to export a description of
-your projects.</td>
-      <td width="68%">
-      <ul>
-        <li>Use <a href="team_resources_projects.htm">project sets</a>
-to export your projects without exporting the content so that users can
-rebuild projects from the repository.</li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td width="32%">Reduce clutter in the repository by ignoring
-files that can be regenerated.</td>
-      <td width="68%">
-      <ul>
-        <li>Honor the <a href="team_resources_filetypes.htm"><b>ignore</b></a>
-extension when handling files and use ignore for your plug-in's derived
-files.</li>
-      </ul>
-      </td>
-    </tr>
-  </tbody>
-</table>
-<h3> Enhancing platform integration</h3>
-<table width="73%" cellspacing="0" cellpadding="0" border="1">
-  <tbody>
-    <tr>
-      <td width="32%">Add provider-specific preferences to the
-preferences page.</td>
-      <td width="68%">
-      <ul>
-        <li><a href="team_ui_prefs.htm">Add your preferences to the
-Team category.</a></li>
-        <li><a href="preferences_prefs_implement.htm">Build your
-preference page</a> using workbench support.</li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td width="32%">Implement custom views to show detailed
-information about repositories or their resources.</td>
-      <td width="68%">
-      <ul>
-        <li>Use the <a href="workbench_basicext_views.htm"><b>views</b></a>
-extension to contribute a view.</li>
-        <li>See the CVS provider's repository view for an example.</li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td width="32%">Add your views or actions to existing workbench
-perspectives if appropriate.</td>
-      <td width="68%">
-      <ul>
-        <li>Use the <a href="workbench_advext_perspectiveExtension.htm"><b>perspectiveExtensions</b></a>
-extension to add your plug-in's shortcuts or views to existing
-perspectives.</li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td width="32%">Implement a repository-specific perspective to
-streamline repository administration or browsing.</td>
-      <td width="68%">
-      <ul>
-        <li>Use the <a href="workbench_advext_perspectives.htm"><b>perspectives</b></a>
-extension to define your own perspective, views, short cuts, and page
-layout.</li>
-      </ul>
-      </td>
-    </tr>
-  </tbody>
-</table>
-<p>&nbsp;</p>
-<p>&nbsp; </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_provider_repository.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_provider_repository.htm
deleted file mode 100644
index 540d0f5..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_provider_repository.htm
+++ /dev/null

@@ -1,278 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Implementing a repository provider</title>
-  <link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-<body style="background-color: rgb(255, 255, 255);">
-<h2>Repository providers</h2>
-<p>
-A repository provider (<b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a></b>)
-is the central class in the implementation of your
-repository.&nbsp; This class is responsible for configuring a project
-for
-repository management and providing the necessary hooks for resource
-modification.&nbsp; Providers are mapped to a project using <a
- href="resInt_properties.htm">project
-persistent properties</a>.&nbsp; The mechanism for mapping providers to
-a
-project is not central to the team API, but you'll need to be aware of
-it when
-filtering out resources in your UI.&nbsp; For the most part, you'll be
-using
-team API to work with projects and associate them to your
-provider.&nbsp;&nbsp;</p>
-<p>
-To implement a provider, you must define a repository using <a
- href="../reference/extension-points/org_eclipse_team_core_repository.html"><b>org.eclipse.team.core.repository</b></a>
-and supply a class
-derived from&nbsp; <b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a></b>.&nbsp;
-We'll use the CVS client as an example to see how this
-works.</p>
-<h3><a name="repository_pt"></a>Extension point</h3>
-<p>
-The <a
- href="../reference/extension-points/org_eclipse_team_core_repository.html">
-<b> org.eclipse.team.core.repository</b></a> extension point is used to
-add a
-repository definition.&nbsp;
-Here is the markup for the CVS client.</p>
-<pre>&lt;extension<br>    point="org.eclipse.team.core.repository"&gt;<br>      &lt;repository<br>            class="org.eclipse.team.internal.ccvs.core.CVSTeamProvider"<br>            id="org.eclipse.team.cvs.core.cvsprovider"&gt;<br>      &lt;/repository&gt;<br>&lt;/extension&gt;<br></pre>
-<p>This registers your team provider with the team support plug-in and
-assigns
-an id that should be used when your provider is associated with a
-project.&nbsp;
-The specified <b>class</b> for the repository must extend <b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a></b>.
-</p>
-<h3><a name="repo_impl"></a>Implementing a RepositoryProvider</h3>
-<p>
-The class identified in the extension must be a subclass of <b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a></b>.
-Its primary responsibilities are to configure and deconfigure a project
-for
-repository support, and supply any necessary resource modification
-hooks.&nbsp;
-The CVS client serves as a good example.&nbsp; Its repository provider
-is <b>CVSTeamProvider</b>.</p>
-
-<pre>public class CVSTeamProvider extends RepositoryProvider {<br>...<br>	</pre>
-<p> <b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a>
-</b>defines two abstract methods, <b>configureProject</b> and <b>deconfigure</b>.&nbsp;
-All providers must implement these methods.&nbsp; </p>
-<p>A project is configured
-when it is first associated with a particular repository
-provider.&nbsp; This
-typically happens when the user selects a project and uses the team
-wizards to
-associate a project with your repository.&nbsp; Regardless of how the
-operation
-is triggered, this is
-the appropriate time to compute or cache any data about the project
-that you'll
-need to provide your repository function.&nbsp; (Assume that mapping
-the project
-to your provider has already happened.&nbsp; You'll be taking care of
-this in
-your configuration wizard.)</p>
-<p>The
-CVS provider simply broadcasts the fact that a project has been
-configured:</p>
-<pre>public void configureProject() throws CoreException {<br>	CVSProviderPlugin.broadcastProjectConfigured(getProject());<br>}</pre>
-<p>We won't follow the implementation of the plug-in broadcast
-mechanism.&nbsp; Suffice to say that any parties that need to compute
-or
-initialize project specific data can do so at this time.</p>
-<p>A project is
-deconfigured when the user no longer wants to associate a team provider
-with a
-project.&nbsp;&nbsp; It is up to your plug-in to implement the user
-action that
-causes this to happen (and unmapping the project from your team
-provider will
-happen there).&nbsp; The <b>deconfigure</b> method&nbsp; is the
-appropriate time to delete any project related caches or remove any
-references
-to the project in the UI.&nbsp; The CVS provider flushes project
-related caches
-kept in its views and broadcasts the fact that the project is
-deconfigured.</p>
-<pre>public void deconfigure() throws CoreException {<br>	...<br>	try {<br>		EclipseSynchronizer.getInstance().flush(getProject(), true, true /*flush deep*/, null);<br>	} catch(CVSException e) {<br>		throw new CoreException(e.getStatus());<br>	} finally {<br>		CVSProviderPlugin.broadcastProjectDeconfigured(getProject());<br>	}<br>}</pre>
-<h3> <a name="ui_conf"></a>Configuring a project </h3>
-<p>Typically, the first step in building a team UI is implementing a
-wizard
-page that allows users to configure a project for your plug-in's team
-support.&nbsp; This is where your team provider's id will be added to
-the
-project's properties.&nbsp; You participate in project configuration by
-contributing to the <a
- href="../reference/extension-points/org_eclipse_team_ui_configurationWizards.html"><b>org.eclipse.team.ui.configurationWizards</b></a>
-extension point.&nbsp; This wizard is shown when the user chooses <b>Team-&gt;Share
-Project...</b>
-</p>
-<p>We'll look at this in the context of the CVS client
-implementation.&nbsp;
-Here is the CVS UI markup for its configuration wizard:
-</p>
-<pre>&lt;extension<br>      point="org.eclipse.team.ui.configurationWizards"&gt;<br>   &lt;wizard<br>        name="%SharingWizard.name"<br>        icon="icons/full/wizards/newconnect_wiz.png"<br>        class="org.eclipse.team.internal.ccvs.ui.wizards.SharingWizard"<br>        id="org.eclipse.team.ccvs.ui.SharingWizard"&gt;<br>   &lt;/wizard&gt;<br>&lt;/extension&gt;</pre>
-<p>As usual, plug-ins supply a <b>class</b> that implements the
-extension and a
-unique <b>id</b> to identify their extension.&nbsp; The <b>name</b>
-and <b>icon</b>
-are shown in the first page of the project configuration wizard if
-there are
-multiple providers to choose from.
-</p>
-<p>Once the user has selected a provider, the next page shows the
-specific
-configuration information for your provider.&nbsp; (If your provider is
-the only
-team provider plug-in installed, then the wizard skips directly to your
-page.)&nbsp; Your wizard must implement <a href="../reference/api/org/eclipse/team/ui/IConfigurationWizard.html"><b>IConfigurationWizard</b></a>,
-which initializes the wizard for a specified workbench and
-project.&nbsp; The rest of the implementation depends on the design of your wizard.
-You must gather up any information needed to associate the project with your
-team support.
-</p>
-<p> When the wizard is completed, you must map your team provider to
-the project
-using <b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html#map(org.eclipse.core.resources.IProject, java.lang.String)">RepositoryProvider.map(IProject,
-String)</a></b>.&nbsp; Mapping handles the assignment of the
-correct
-project persistent property to your project.
-</p>
-<p> The CVS client does this work in its provider's <b>setSharing</b>
-method, which is called when its wizard is finished:
-</p>
-<pre>public void setSharing(IProject project, FolderSyncInfo info, IProgressMonitor monitor) throws TeamException {<br>	<br>	// Ensure provided info matches that of the project<br>	...		<br>	// Ensure that the provided location is managed<br>	...		<br>	// Register the project with Team<br><b>	RepositoryProvider.map(project, CVSProviderPlugin.getTypeId());<br></b>}</pre>
-<h3> Finding a provider
-</h3>
-<p>Static methods in <b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a></b> 
-  make it easy for clients to map projects to providers and to find the providers 
-  associated with a given project. </p>
-<ul>
-  <li><b>map(IProject, String)</b> - instantiates a provider of the
-specified provider id and maps the specified project to it.&nbsp; This
-call sets the proper project persistent property on the project. </li>
-  <li><b>unmap(IProject, String)</b> - removes the association of the
-specified provider id from the specified project.&nbsp; Leaves the
-project unassociated with any team provider. </li>
-  <li><b>getProvider(IProject)</b> - answers the provider for a given
-project.&nbsp; Can be used to find any team provider for a
-project.&nbsp; </li>
-  <li><b>getProvider(IProject, String) </b>- answers the provider for
-a given project with the specified provider id.&nbsp; Can be used to
-check whether a particular team provider type is associated with a
-given project.&nbsp; It is commonly used by providers to quickly check
-whether a given project is under their care.&nbsp; This call is safer
-for clients since it does not return a provider that does not match the
-client's id.</li>
-</ul>
-<h3>Repository Providers and Capabilities</h3>
-<p>
-If a product chooses to add a Repository plug-in to a capability, it
-should bind the capability to the repository id. Here are the two steps
-to take to enable a RepositoryProvider as a capability:
-</p>
-<ol>
-<li>Bind the capability to the repository provider id. This allows the
-Team plug-in to activate/disable based on repository provider ids.<br>
-<pre>&lt;activityPatternBinding<br>&nbsp;&nbsp;&nbsp; activityId="org.eclipse.team.cvs"<br>&nbsp;&nbsp;&nbsp; pattern="org\.eclipse\.team\.cvs\.core/.*cvsnature"&gt;<br>&lt;/activityPatternBinding&gt;</pre>
-</li>
-<li>Next bind the capability to all UI packages for the provider:<br>
-<pre>&lt;activityPatternBinding<br>&nbsp;&nbsp;&nbsp;&nbsp; activityId="org.eclipse.team.cvs"<br>&nbsp;&nbsp;&nbsp;&nbsp; pattern="org\.eclipse\.team\.cvs\.ui/.*"&gt;<br>&lt;/activityPatternBinding&gt;</pre>
-</li>
-</ol>
-<p>
-There are two capability triggers points defined by the Team plug-ins.
-The first is the <span style="font-weight: bold;">Team &gt; Share
-Project...</span> wizard which allows filtering of repository providers
-based on the enabled/disabled state of workbench capabilities, and the
-other is the Team plug-in auto-enablement trigger.</p>
-<h3>Resource modification hooks<a name="hooks"></a></h3>
-<p>Most of the interesting function associated with a repository
-provider occurs as the user works with resources in the project that is
-configured for the provider.&nbsp; In order to be aware of changes the
-user makes to a resource, the provider can implement <a
- href="resAdv_hooks.htm">resource modification hooks</a>.&nbsp; The
-resources plug-in provides these hooks as extension points.&nbsp; The
-documentation for <a
- href="../reference/api/org/eclipse/core/resources/team/IMoveDeleteHook.html"><b>IMoveDeleteHook</b></a>,
-<a
- href="../reference/api/org/eclipse/core/resources/IFileModificationValidator.html"><b>IFileModificationValidator</b></a>
-and <a
- href="../reference/api/org/eclipse/core/resources/team/ResourceRuleFactory.html"><strong>ResourceRuleFactory</strong></a>
-describe the details for implementing these hooks.</p>
-<p>The team plug-in optimizes and simplifies the association of the
-hook with
-appropriate resources by registering generic hooks with the resources
-plug-in.&nbsp; These generic hooks simply look up the repository
-provider for a
-given resource and obtain its hook.&nbsp; This has the advantage of
-calling only
-one provider hook rather than having each provider implementation
-register a
-hook that must first check whether the resource is managed by the
-provider.</p>
-<p>What this means to your plug-in is that you provide any necessary
-hooks by overriding methods in <b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a></b>.&nbsp;
-The default implementation of these methods answers null,
-indicating that no hook is necessary (except for the resource rule
-factory, as described below): </p>
-<ul>
-  <li><b>getMoveDeleteHook</b> - answers an <a
- href="../reference/api/org/eclipse/core/resources/team/IMoveDeleteHook.html"><b>IMoveDeleteHook</b></a>
-appropriate for the provider.&nbsp; This hook allows providers to
-control how moves and deletes occur and includes the ability to prevent
-them from happening.&nbsp; Implementors can provide alternate
-implementations for moving or deleting files, folders, and
-projects.&nbsp; The CVS client uses this hook to monitor folder
-deletions and ensure that any files contained in deleted folders are
-remembered so that they can later be deleted from the repository if
-desired.</li>
-  <li><b>getFileModificationValidator</b> - answers an <a
- href="../reference/api/org/eclipse/core/resources/IFileModificationValidator.html"><b>IFileModificationValidator</b></a>
-appropriate for the provider.&nbsp; This hook allows providers to
-pre-check any modifications or saves to files.&nbsp; This hook is
-typically needed when a repository provider wants to implement <b>pessimistic
-versioning</b>.&nbsp; In pessimistic versioning, a file must be checked
-out before modifying it, and only one client can check out a file at
-any given time.&nbsp; Pessimistic versioning could be implemented by
-checking out a file (if not already checked out) whenever a file is
-edited, and checking the file back in when it is saved. Since CVS uses
-an optimistic versioning scheme, it does not implement this hook.</li>
-  <li><strong>getRuleFactory</strong> - answers a resource rule factory
-appropriate for the provider. Providers should always override this
-method as the default factory locks the workspace for all operations
-for backwards compatibility reasons. Provides should subclass <a
- href="../reference/api/org/eclipse/core/resources/team/ResourceRuleFactory.html"><strong>ResourceRuleFactory</strong></a>
-and override those rules required to ensure that the proper rules are
-obtained for operations that invoke the move/delete hook and file
-modification validator. The rule methods of particular interest to
-repository providers are:
-    <ul>
-      <li><em>deleteRule</em> - move/delete hook</li>
-      <li><em>moveRule</em> -move/delete hook</li>
-      <li><em>validateEditRule</em> - file modification validator
-validateEdit</li>
-      <li><em>modifyRule</em> - file modification validator validateSave</li>
-    </ul>
-  </li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_resources.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_resources.htm
deleted file mode 100644
index 06cff80..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_resources.htm
+++ /dev/null

@@ -1,239 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Repository resource management</title>
-  <link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-<body style="background-color: rgb(255, 255, 255);">
-<h2>Repository resource management</h2>
-<p>Once you have created a <b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a></b>,
-there are other resource management mechanism that should be understood:<br>
-</p>
-<ul>
-  <li>In order to allow other plug-ins to indicate special handling for
-their projects
-and files the team plug-in defines extension points that other
-providers and other plug-ins can use to register <a href="#filetypes">file
-types</a> and to
-declare files that should be <a href="#ignored">ignored </a>by a
-repository provider.</li>
-  <li>Team providers can also register a class that can be used to
-persist
-a <a href="#projectsets">set a projects</a> so that references to the
-project can be shared across
-a team, with the actual contents coming from the repository.</li>
-  <li>Repository providers should consider how they will handle <a
- href="#linked">linked resources</a>.<br>
-  </li>
-  <li>Finally, team providers can mark resources that should be hidden
-from the user as <a href="#teamprivate">team private</a>.<br>
-  </li>
-</ul>
-<h3><a name="ignored"></a>Ignored files</h3>
-<p>In several cases, it may be unnecessary to keep certain files under
-repository control.&nbsp; For example, resources that are derived from
-existing
-resources can often be omitted from the repository.&nbsp; For example,
-compiled
-source files, (such as Java ".class" files), can be omitted since
-their corresponding source (".java") file is in the repository.&nbsp;
-It also may be inappropriate to version control metadata files that are
-generated by repository providers.&nbsp; The <a
- href="../reference/extension-points/org_eclipse_team_core_ignore.html"><b>org.eclipse.team.core.ignore</b></a>
-extension point allows providers to declare file types that should be
-ignored
-for repository provider operations.&nbsp; For example, the CVS client
-declares
-the following:</p>
-<pre>&lt;extension point="org.eclipse.team.core.ignore"&gt;<br>	&lt;ignore pattern = ".#*" selected = "true"/&gt;<br>&lt;/extension&gt;</pre>
-<p>The markup simply declares a file name <b>pattern</b> that should
-be ignored
-and a <b>selected</b> attribute which declares the default selection
-value of
-the file type in the preferences dialog.&nbsp; It is ultimately up to
-the user
-to decide which files should be ignored.&nbsp; The user may select,
-deselect,
-add or delete file types from the default list of ignored files.</p>
-<p><img src="images/ignore.png" alt="" border="0"></p>
-<h3><a name="filetypes"></a>File Types<br>
-</h3>
-<p>Some repositories implement different handling for text vs. binary
-files.&nbsp; The <a
- href="../reference/extension-points/org_eclipse_team_core_fileTypes.html"><b>org.eclipse.team.core.fileTypes</b></a>
-extension allows plug-ins to declare file types as text or binary
-files.&nbsp;
-For example, the Java tooling declares the following:
-</p>
-<pre>&lt;extension point="org.eclipse.team.core.fileTypes"&gt;<br>  &lt;fileTypes extension="java" type="text"/&gt;<br><br>  &lt;fileTypes extension="classpath" type="text"/&gt;<br>  &lt;fileTypes extension="properties" type="text"/&gt;<br>  &lt;fileTypes extension="class" type="binary"/&gt;<br><br>  &lt;fileTypes extension="jar" type="binary"/&gt;<br>  &lt;fileTypes extension="zip" type="binary"/&gt;<br>&lt;/extension&gt;</pre>
-<p>The markup lets plug-ins define a file type by <b>extension</b> and
-assign a <b>type</b>
-of text or binary.&nbsp; As with ignored files, it is ultimately up to
-the user
-to manage the list of text and binary file types.
-</p>
-<p><img src="images/filetypes.png" alt="" border="0"> 
-</p>
-<h3><a name="linked"></a>Team and linked resources</h3>
-<p>A project may contain resources that are not located within the
-project's directory in the local file system. These resources are
-referred to as <a href="resInt_linked.htm">linked resources</a>. </p>
-<h4>Consequences for Repository Providers</h4>
-<p>Linked resources can pose particular challenges for repository
-providers which operate directly against the file system. This is a
-consequence of the fact that linked resources by design do not exist in
-the immediate project directory tree in the file system. </p>
-<p>Providers which exhibit the following characteristics may be
-affected by linked resources:</p>
-<ol>
-  <li>Those which call out to an external program that then operates
-directly against the file system.</li>
-  <li>Those which are implemented in terms of IResource but assume that
-all the files/folders in a project exist as direct descendents of that
-single rooted directory tree.</li>
-</ol>
-<p>In the first case, lets assume the user picks a linked resource and
-tries to perform a provider operation on it. Since the provider calls a
-command line client, we can assume that the provider does something
-equivalent to first calling <a
- href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a>.getLocation().toOSString(),
-feeding the resulting file system location as an argument to the
-command line program. If the resource in question is a linked resource,
-this will yield a file/folder outside of the project directory tree.
-Not all command line clients may expect and be able to handle this
-case. In short, if your provider ever gets the file system location of
-a resource, it will likely require extra work to handle linked
-resources. </p>
-<p>The second case is quite similar in that there is an implicit
-assumption that the structure of the project resources is 1:1 with that
-of the file system files/folders. In general, a provider could be in
-trouble if they mix IResource and java.io.File operations. For example,
-for links, the parent of <a
- href="../reference/api/org/eclipse/core/resources/IFile.html"><b>IFile</b></a>
-is not the same as the java.io.File's parent and code which assumes
-these to be the same will fail.
-</p>
-<h4>Backwards Compatibility</h4>
-<p>It was important that the introduction of linked resources did not inadvertently 
-  break existing providers. Specifically, the concern was for providers that reasonably 
-  assumed that the local file system structure mirrored the project structure. 
-  Consequently, by default linked resources can not be added to projects that 
-  are mapped to such a provider. Additionally, projects that contain linked resources 
-  can not by default be shared with that provider.</p>
-<h4>Strategies for Handling Linked Resources</h4>
-<p>In order to be "link friendly", a provider should allow projects
-with linked resources to be version controlled, but can disallow the
-version controlling of linked resources themselves. </p>
-<p>A considerably more complex solution would be to allow the
-versioning of the actual linked resources, but this should be
-discouraged since it brings with it complex scenarios (e.g. the file
-may already be version controlled under a different project tree by
-another provider). Our recommendation therefore is to support version
-controlled projects which contain non-version controlled linked
-resources.</p>
-<h4>Technical Details for Being "Link Friendly"</h4>
-<p>Repository provider implementations can be upgraded to support
-linked resources by overriding the <b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a>.canHandleLinkedResources()</b>
-method to return <strong>true</strong>. Once this is done, linked
-resources will be allowed to exist in projects shared with that
-repository provider. However, the repository provider must take steps
-to ensure that linked resources are handled properly. As mentioned
-above, it is strongly suggested that repository providers ignore all
-linked resources. This means that linked resources (and their children)
-should be excluded from the actions supported by the repository
-provider. Furthermore, the repository provider should use the default
-move and delete behavior for linked resources if the repository
-provider implementation overrides the default <a
- href="../reference/api/org/eclipse/core/resources/team/IMoveDeleteHook.html"><b>IMoveDeleteHook</b></a>.</p>
-<p>Team providers can use <a
- href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a>.<b>isLinked()
-</b>to determine if a resource is a link. However, this method only
-returns true for the root of a link. The following code segment can be
-used to determine if a resource is the child of a link.</p>
-<pre>String linkedParentName = resource.getProjectRelativePath().segment(0);<br>IFolder linkedParent = resource.getProject().getFolder(linkedParentName);<br>boolean isLinked = linkedParent.isLinked();</pre>
-<p>Repository providers should ignore any resource for which the above
-code evaluates to <strong>true</strong>.</p>
-<h3><a name="teamprivate"></a>Team private resources</h3>
-<p>It is common for repository implementations to use extra files and
-folders to
-store information specific about the repository implementation.&nbsp;
-Although
-these files may be needed in the workspace, they are of no interest to
-other
-plug-ins or to the end user.</p>
-<p>Team providers may use <a
- href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a>.<b>setTeamPrivateMember(boolean)
-</b>to indicate that a resource is private to the implementation of a
-team
-provider. Newly created resources are not private members by default,
-so this
-method must be used to explicitly mark the resource as team
-private.&nbsp; A
-common use is to mark a subfolder of the project as team private when
-the
-project is configured for team and the subfolder is created.</p>
-<p>Other resource API that enumerates resources (such as resource delta
-trees)
-will exclude team private members unless explicitly requested to
-include
-them.&nbsp; This means that most clients will not "see" the team
-private resources and they will not be shown to the user.&nbsp; The
-resource
-navigator does not show team private members by default, but users can
-indicate
-via Preferences that they would like to see team private resources.</p>
-<p>Attempts to mark projects or the workspace root as team private will
-be
-ignored.</p>
-<h3><a name="projectsets"></a>Project sets</h3>
-<p>Since the resources inside a project under version control are kept
-in the
-repository, it is possible to share projects with team members by
-sharing a
-reference to the repository specific information needed to reconstruct
-a project
-in the workspace.&nbsp; This is done using a special type of file
-export for <b>team
-project sets</b>.&nbsp;&nbsp;</p>
-<p><img  border="0" alt=""
- src="images/projectset.png"></p>
-<p>&nbsp;</p>
-<p>In 3.0, API was added to <a
- href="../reference/api/org/eclipse/team/core/ProjectSetCapability.html">ProjectSetCapability</a>
-to allow repository providers to declare a class that implements
-project saving for projects under their control.&nbsp; When the user
-chooses to export project sets, only the projects configured with
-repositories that define project sets are shown as candidates for
-export. This API replaces the old project set serialization API (see
-below). </p>
-<p>The project set capability class for a repository provider is obtained from 
-  the <a
- href="../reference/api/org/eclipse/team/core/RepositoryProviderType.html">RepositoryProviderType</a> 
-  class which is registered in the same extension as the repository provider. 
-  For example:</p>
-<pre>&lt;extension point="org.eclipse.team.core.repository"&gt;<br>    &lt;repository<br>          typeClass="org.eclipse.team.internal.ccvs.core.CVSTeamProviderType"<br><br>          class="org.eclipse.team.internal.ccvs.core.CVSTeamProvider"<br>          id="org.eclipse.team.cvs.core.cvsnature"&gt;<br>    &lt;/repository&gt;<br>&lt;/extension&gt;</pre>
-<p>Prior to 3.0, The <a
- href="../reference/extension-points/org_eclipse_team_core_projectSets.html"><b>org.eclipse.team.core.projectSets</b></a>
-extension point allowed repository providers to declare a class that
-implements project saving for projects under their control.&nbsp; When
-the user chooses to export project sets, only the projects configured
-with repositories that define project sets are shown as candidates for
-export.</p>
-<p>For example, the CVS client declares the following:</p>
-<pre>&lt;extension point="org.eclipse.team.core.projectSets"&gt;<br>	&lt;projectSets id="org.eclipse.team.cvs.core.cvsnature" class="org.eclipse.team.internal.ccvs.ui.CVSProjectSetSerializer"/&gt;<br>&lt;/extension&gt;</pre>
-<p>The specified class must implement <a
- href="../reference/api/org/eclipse/team/core/IProjectSetSerializer.html"><b>IProjectSetSerializer</b></a>.
-Use of this interface is still supported in 3.0 but has been deprecated.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_resources_filetypes.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_resources_filetypes.htm
deleted file mode 100644
index 808ad5d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_resources_filetypes.htm
+++ /dev/null

@@ -1,76 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>File types</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>File types</h3>
-<p>The presence of a repository management system may dictate special handling
-needs for files.&nbsp; For example, some files should be omitted from version
-control.&nbsp; Some providers have special handling for text vs. binary
-files.&nbsp; The team plug-in defines extension points that allow other plug-ins
-to provide information about their file types.&nbsp; In all cases, special
-handling is ultimately left up to the user via the team Preferences page.&nbsp;
-These extensions allow plug-ins to seed the preferences with values appropriate
-for the plug-in.</p>
-<h4>Ignored files</h4>
-<p>In several cases, it may be unnecessary to keep certain files under
-repository control.&nbsp; For example, resources that are derived from existing
-resources can often be omitted from the repository.&nbsp; For example, compiled
-source files, (such as Java &quot;.class&quot; files), can be omitted since
-their corresponding source (&quot;.java&quot;) file is in the repository.&nbsp;
-It also may be inappropriate to version control metadata files that are
-generated by repository providers.&nbsp; The <a href="../reference/extension-points/org_eclipse_team_core_ignore.html"><b>org.eclipse.team.core.ignore</b></a>
-extension point allows providers to declare file types that should be ignored
-for repository provider operations.&nbsp; For example, the CVS client declares
-the following:</p>
-<pre>&lt;extension point=&quot;org.eclipse.team.core.ignore&quot;&gt;
-	&lt;ignore pattern = &quot;.#*&quot; selected = &quot;true&quot;/&gt;
-&lt;/extension&gt;</pre>
-<p>The markup simply declares a file name <b>pattern</b> that should be ignored
-and a <b>selected</b> attribute which declares the default selection value of
-the file type in the preferences dialog.&nbsp; It is ultimately up to the user
-to decide which files should be ignored.&nbsp; The user may select, deselect,
-add or delete file types from the default list of ignored files.</p>
-<p><img src="images/ignore.png" alt="" border="0" ></p>
-<h4>Text vs. binary files</h4>
-<p>Some repositories implement different handling for text vs. binary
-files.&nbsp; The <a href="../reference/extension-points/org_eclipse_team_core_fileTypes.html"><b>org.eclipse.team.core.fileTypes</b></a>
-extension allows plug-ins to declare file types as text or binary files.&nbsp;
-For example, the Java tooling declares the following:
-</p>
-
-<pre>&lt;extension point=&quot;org.eclipse.team.core.fileTypes&quot;&gt;
-  &lt;fileTypes extension=&quot;java&quot; type=&quot;text&quot;/&gt;
-  &lt;fileTypes extension=&quot;classpath&quot; type=&quot;text&quot;/&gt;
-  &lt;fileTypes extension=&quot;properties&quot; type=&quot;text&quot;/&gt;
-  &lt;fileTypes extension=&quot;class&quot; type=&quot;binary&quot;/&gt;
-  &lt;fileTypes extension=&quot;jar&quot; type=&quot;binary&quot;/&gt;
-  &lt;fileTypes extension=&quot;zip&quot; type=&quot;binary&quot;/&gt;
-&lt;/extension&gt; </pre>
-
-<p>The markup lets plug-ins define a file type by <b>extension</b> and assign a <b>type</b>
-of text or binary.&nbsp; As with ignored files, it is ultimately up to the user
-to manage the list of text and binary file types.
-</p>
-
-
-
-
-<p><img src="images/filetypes.png" alt="" border="0" >
-</p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_resources_linked.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_resources_linked.htm
deleted file mode 100644
index a66ffd6..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_resources_linked.htm
+++ /dev/null

@@ -1,91 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Team and linked resources</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Team and linked resources</h3>
-<p>A project may contain resources that are not located within the project's directory 
-  in the local file system. These resources are referred to as <a href="resInt_linked.htm">linked 
-  resources</a>. </p>
-<h4>Consequences for Repository Providers</h4>
-<p>Linked resources can pose particular challenges for repository providers which 
-  operate directly against the file system. This is a consequence of the fact 
-  that linked resources by design do not exist in the immediate project directory 
-  tree in the file system. </p>
-<p>Providers which exhibit the following characteristics may be affected by linked 
-  resources:</p>
-<ol>
-  <li>Those which call out to an external program that then operates directly 
-    against the file system.</li>
-  <li>Those which are implemented in terms of IResource but assume that all the 
-    files/folders in a project exist as direct descendents of that single rooted 
-    directory tree.</li>
-</ol>
-<p>In the first case, lets assume the user picks a linked resource and tries to perform
-  a provider operation on it.  Since the provider calls a command line client, we can assume that
-  the provider does something equivalent to first calling
-   <a href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a>.getLocation().toOSString(),
-  feeding the resulting file system location as an argument to the command line program.  If the resource in question is
-  a linked resource, this will yield a file/folder outside of the project directory tree.  Not all
-  command line clients may expect and be able to handle this case.
-  In short, if your provider ever gets the file system location of a resource, it will likely require
-  extra work to handle linked resources.  
-</p>
-<p>The second case is quite similar in that there is an implicit assumption that the structure of
-  the project resources is 1:1 with that of the file system files/folders.  In general,
-  a provider could be in trouble if they mix IResource and java.io.File operations. 
-  For example, for links, the parent of 
-  <a href="../reference/api/org/eclipse/core/resources/IFile.html"><b>IFile</b></a>
-  is not the same
-  as the java.io.File's parent and code which assumes these to be the same will fail.
-</p>
-<h4>Backwards Compatibility</h4>
-<p>It was important that the introduction of linked resources did not inadvertently 
-  break existing providers. Specifically, the concern was for providers that reasonably 
-  assumed that the local file system structure mirrored the project structure. 
-  Consequently, by default linked resources can not be added to projects that 
-  are mapped to such a provider. Additionally, projects that contain linked resources 
-  can not by default be shared with that provider.</p>
-<h4>Strategies for Handling Linked Resources</h4>
-<p>In order to be &quot;link friendly&quot;, a provider should allow projects 
-  with linked resources to be version controlled, but can disallow the version 
-  controlling of linked resources themselves. </p>
-<p>A considerably more complex solution would be to allow the versioning of the 
-  actual linked resources, but this should be discouraged since it brings with 
-  it complex scenarios (e.g. the file may already be version controlled under 
-  a different project tree by another provider). Our recommendation therefore 
-  is to support version controlled projects which contain non-version controlled 
-  linked resources.</p>
-<h4>Technical Details for Being &quot;Link Friendly&quot;</h4>
-<p>Repository provider implementations can be upgraded to support linked resources 
-  by overriding the <b><a href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a>.canHandleLinkedResources()</b> 
-  method to return <strong>true</strong>. Once this is done, linked resources 
-  will be allowed to exist in projects shared with that repository provider. However, 
-  the repository provider must take steps to ensure that linked resources are 
-  handled properly. As mentioned above, it is strongly suggested that repository 
-  providers ignore all linked resources. This means that linked resources (and 
-  their children) should be excluded from the actions supported by the repository 
-  provider. Furthermore, the repository provider should use the default move and 
-  delete behavior for linked resources if the repository provider implementation 
-  overrides the default <a href="../reference/api/org/eclipse/core/resources/team/IMoveDeleteHook.html"><b>IMoveDeleteHook</b></a>.</p>
-<p>Team providers can use <a href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a>.<b>isLinked() 
-  </b>to determine if a resource is a link. However, this method only returns 
-  true for the root of a link. The following code segment can be used to determine 
-  if a resource is the child of a link.</p>
-<pre>String linkedParentName = resource.getProjectRelativePath().segment(0);
-IFolder linkedParent = resource.getProject().getFolder(linkedParentName);
-boolean isLinked = linkedParent.isLinked();</pre>
-<p>Repository providers should ignore any resource for which the above code evaluates 
-  to <strong>true</strong>.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_resources_private.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_resources_private.htm
deleted file mode 100644
index 12408af..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_resources_private.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Team private resources</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Team private resources</h3>
-<p>It is common for repository implementations to use extra files and folders to
-store information specific about the repository implementation.&nbsp; Although
-these files may be needed in the workspace, they are of no interest to other
-plug-ins or to the end user.</p>
-<p>Team providers may use <a href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a>.<b>setTeamPrivateMember(boolean)
-</b>to indicate that a resource is private to the implementation of a team
-provider. Newly created resources are not private members by default, so this
-method must be used to explicitly mark the resource as team private.&nbsp; A
-common use is to mark a subfolder of the project as team private when the
-project is configured for team and the subfolder is created.</p>
-<p>Other resource API that enumerates resources (such as resource delta trees)
-will exclude team private members unless explicitly requested to include
-them.&nbsp; This means that most clients will not &quot;see&quot; the team
-private resources and they will not be shown to the user.&nbsp; The resource
-navigator does not show team private members by default, but users can indicate
-via Preferences that they would like to see team private resources.</p>
-<p>Attempts to mark projects or the workspace root as team private will be
-ignored.</p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_resources_projects.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_resources_projects.htm
deleted file mode 100644
index 84ddde2..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_resources_projects.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Project sets</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Project sets</h3>
-<p>Since the resources inside a project under version control are kept in the
-repository, it is possible to share projects with team members by sharing a
-reference to the repository specific information needed to reconstruct a project
-in the workspace.&nbsp; This is done using a special type of file export for <b>team
-project sets</b>.&nbsp;&nbsp;</p>
-<p><img src="images/projectset.png" alt="" border="0" ></p>
-<p>&nbsp;</p>
-<p>In 3.0, API was added to <a href="../reference/api/org/eclipse/team/core/ProjectSetCapability.html">ProjectSetCapability</a> 
-  to allow repository providers to declare a class that implements project saving 
-  for projects under their control.&nbsp; When the user chooses to export project 
-  sets, only the projects configured with repositories that define project sets 
-  are shown as candidates for export. This API replaces the old project set serialization 
-  API (see below). </p>
-<p>The project set capability class for a repository provider is obtained from 
-  the <a href="../reference/api/org/eclipse/team/core/ProjectSetCapability.html">RepositoryProviderType</a> 
-  class which is registered in the same extension as the repository provider. 
-  For example:</p>
-<pre>&lt;extension point="org.eclipse.team.core.repository"&gt;
-    &lt;repository
-          typeClass=&quot;org.eclipse.team.internal.ccvs.core.CVSTeamProviderType&quot;
-          class=&quot;org.eclipse.team.internal.ccvs.core.CVSTeamProvider&quot;
-          id=&quot;org.eclipse.team.cvs.core.cvsnature&quot;&gt;
-    &lt;/repository&gt;
-&lt;/extension&gt;</pre>
-<p>Prior to 3.0, The <a href="../reference/extension-points/org_eclipse_team_core_projectSets.html"><b>org.eclipse.team.core.projectSets</b></a> 
-  extension point allowed repository providers to declare a class that implements 
-  project saving for projects under their control.&nbsp; When the user chooses 
-  to export project sets, only the projects configured with repositories that 
-  define project sets are shown as candidates for export.</p>
-<p>For example, the CVS client declares the following:</p>
-<pre>&lt;extension point=&quot;org.eclipse.team.core.projectSets&quot;&gt;
-	&lt;projectSets id=&quot;org.eclipse.team.cvs.core.cvsnature&quot; class=&quot;org.eclipse.team.internal.ccvs.ui.CVSProjectSetSerializer&quot;/&gt;
-&lt;/extension&gt;</pre>
-<p>The specified class must implement <a href="../reference/api/org/eclipse/team/core/IProjectSetSerializer.html"><b>IProjectSetSerializer</b></a>. 
-  Use of this interface is still supported in 3.0 but has been deprecated.</p>
-<p>&nbsp;
-   
-</p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_synchronize.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_synchronize.htm
deleted file mode 100644
index 23f2a64..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_synchronize.htm
+++ /dev/null

@@ -1,229 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Synchronization Support</title>
-  <link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-<body style="background-color: rgb(255, 255, 255);">
-<h2>Synchronization Support</h2>
-<p>New in Eclipse 3.0 are APIs for managing and displaying synchronization state 
-  between workspace resources and resources in another location. We refer to a 
-  resource outside of the workspace as a variant. Synchronizing is the act of 
-  displaying the changes between resources in different locations and optionally 
-  allowing the user to affect the synchronization state by performing an action. 
-  The synchronize APIs are orthogonal to the RepositoryProvider APIs and can be 
-  used without a repository provider. The purpose of the synchronization API is 
-  to ease the task of implementing different ways of presenting the synchronization 
-  state of resources. As such, the API requires a means to query the synchronization 
-  state of resources but does not require a means to affect the state. The means 
-  of affecting the state is left to the implementer (although the UI does provide 
-  hooks for adding provider specific menu items to menus).</p>
-<h3>Terminology </h3>
-<p>Before the synchronization API is described, it is helpful to
-present some of the terminology and concepts that apply when discussing
-workspace synchronization.</p>
-<blockquote>
-  <p><em>Resource Variant</em>: A local resource that is mapped to a resource 
-    that exists at another location can be referred to as a variant of that resource. 
-    That is, the resources are usually very similar but may differ slightly (either 
-    due to modifications to the local resource or changes made the remote copy 
-    by other users). We take a local workspace centric view of this, referring 
-    to the local copy as the resource and any remote copy as resource variants.</p>
-  <p><em>Synchronize</em>: We refer to synchronize as the action of displaying 
-    to the user the differences between resource variants. Synchronizing doesn't 
-    affect the state of the variants, but instead provides a view to help the 
-    user understand the differences between different sets of variants. It is 
-    common however to allow users to affect the states of the variants (e.g. allowing 
-    to check-in, or revert) while synchronizing.</p>
-  <p><em>Two-way vs. Three-way Synchronization</em>: There are two basic types 
-    of synchronization state determination: two-way and three-way. A two-way comparison 
-    only considers the local resource and a single resource variant, referred 
-    to as the remote resource variant. This type of comparison can only show the 
-    differences between the two resources but cannot offer hints as to how the 
-    changes interrelate. Most code repository systems support a three-way comparison 
-    for synchronization state determination. This type of comparison involves 
-    the local resource, a remote resource variant and a base resource variant. 
-    The base resource variant represents a common ancestor for the local and remote 
-    resources. This allows for more sophisticated synchronization states that 
-    indicate the direction of the change.<br>
-  </p>
-  <p>Table 1: The synchronization states<br>
-  </p>
-  <table style="text-align: left; width: 100%;" border="1"
- cellspacing="2" cellpadding="2">
-    <tbody>
-      <tr>
-        <td style="vertical-align: top;"><span
- style="font-weight: bold;">Two-Way</span></td>
-        <td style="vertical-align: top;"><span
- style="font-weight: bold;">Three-Way</span></td>
-      </tr>
-      <tr>
-        <td style="vertical-align: top;">Changed<br>
-Deleted<br>
-Added</td>
-        <td style="vertical-align: top;">Outgoing Change<br>
-Incoming Change<br>
-Outgoing Deletion<br>
-Incoming Deletion<br>
-Outgoing Addition<br>
-Incoming Addition<br>
-Conflicting Change<br>
-Conflicting Deletion<br>
-Conflicting Addition</td>
-      </tr>
-    </tbody>
-  </table>
-</blockquote>
-<h3>The Basics - SyncInfo</h3>
-<p>
-The classes in the <a
- href="../reference/api/org/eclipse/team/core/synchronize/package-summary.html">org.eclipse.team.core.synchronize</a>
-are used to describe the synchronization state. The most important
-class is <a
- href="../reference/api/org/eclipse/team/core/synchronize/SyncInfo.html">SyncInfo</a>
-because it is the class that actually defines the synchronization
-state. It can be used as follows:
-</p>
-<pre><span style="color: rgb(68, 68, 204);">SyncInfo info = getSyncInfo(resource); // this is a simulated method of obtaining the sync info for a resource<br>int changekind = info.getKind();<br>if(info.getResourceComparator().isThreeWay()) {<br>  if((changeKind &amp; SyncInfo.DIRECTION_MASK) == SyncInfo.INCOMING) {<br>    // do something<br>  }<br>} else if(changeKind == SyncInfo.CHANGE) {<br>    // do something else<br>}</span></pre>
-<p>
-The SyncInfo class provides both the two-way and three-way comparison algorithms, 
-a client must provide the resources and a class that can compare the resources 
-(<a
- href="../reference/api/org/eclipse/team/core/variants/IResourceVariantComparator.html">IResourceVariantComparator</a>). 
-Here is an example variant comparator:
-</p>
-<pre style="color: rgb(68, 68, 204);">public class TimestampVariantComparator implements IResourceVariantComparator {	<br>  protected boolean compare(IResourceVariant e1, IResourceVariant e2) {<br>    if(e1.isContainer()) {<br>      if(e2.isContainer()) {<br>        return true;<br>      }<br>      return false;<br>    }<br>    if(e1 instanceof MyResourceVariant &amp;&amp; e2 instanceof MyResourceVariant) {<br>      MyResourceVariant myE1 = (MyResourceVariant)e1; <br>      MyResourceVariant myE2 = (MyResourceVariant)e2; <br>      return myE1.getTimestamp().equals(myE2.getTimestamp());<br>    }<br>    return false;<br>  }<br>  protected boolean compare(IResource e1, IResourceVariant e2) {<br>      <br>  }<br>  public boolean isThreeWay() {<br>    return true;<br>  }<br>}<br><br>SyncInfo info = new SyncInfo(resource, variant1, variant2, new TimestampComparator());<br>info.init(); // calculate the sync info</pre>
-<p>This package also contains collections specifically designed to contain
-SyncInfo and filters that can be applied to SyncInfo instances.
-</p>
-<h3>Managing the synchronization state</h3>
-<p>
-As we have seen in the examples above, <a
- href="../reference/api/org/eclipse/team/core/synchronize/SyncInfo.html">SyncInfo
-</a>and
-<a
- href="../reference/api/org/eclipse/team/core/variants/IResourceVariantComparator.html">IResourceVariantComparator</a>
- classes provide access to the
-synchronization state of resources. But what we haven't seen yet is how
-the state is managed. A <a
- href="../reference/api/org/eclipse/team/core/subscribers/Subscriber.html">Subscriber</a>
-provides access to the synchronization state between the resources in
-the local workspace and a set of resource variants for these resources
-using either a two-way or three-way comparison, depending on the nature
-of the subscriber. A subscriber provides the following capabilities:
-</p>
-
-<ul>
-  <li><span style="font-weight: bold;">local workspace traversal</span>: a subscriber 
-    supports the traversal of the local workspace resources that are <em>supervised</em> 
-    by the subscriber. As such, the subscriber has a set of <em>root</em> resources 
-    that define the workspace subtrees under the subscriber's control, as well 
-    as a <em>members</em> method that returns the supervised members of a workspace 
-    resource. This traversal differs from the usual workspace resource traversal 
-    in that the resources being traversed may include resources that do not exist 
-    locally, either because they have been deleted by the user locally or created 
-    by a 3rd party. <br>
-  </li>
-  <li><span style="font-weight: bold;">resource synchronization state determination</span>: 
-    For supervised resources, the subscriber provides access to the synchronization 
-    state of the resource, including access to the variants of the resource. For 
-    each supervised resource, the subscriber provides a <em>SyncInfo</em> object 
-    that contains the synchronization state and the <em>variants</em> used to 
-    determine the state.The subscriber also provides an <em>IResourceVariantComparator</em> 
-    which determines whether two-way or three-way comparison is to be used and 
-    provides the logic used by the SyncInfo to comparing resource variants when 
-    determining the synchronization state. <br>
-  </li>
-  <li><span style="font-weight: bold;">refresh of synchronization state and change 
-    notification</span>: Clients can react to changes that happen to local resources 
-    by listening to the Core resource deltas. When a local resource is changed, 
-    the synchronization state of the resource can then be re-obtained from the 
-    subscriber. However, clients must explicitly query the server to know if there 
-    are changes to the resource variants. For subscribers, this process is broken 
-    up into two parts. A client can explicitly <em>refresh</em> a subscriber. 
-    In response the subscriber will obtain the latest state of the resource variants 
-    from the remote location and fire <em>synchronization state change</em> events 
-    for any resource variants that have changed. The change notification is separate 
-    from the refresh since there may be other operations that contact the remote 
-    location and obtain the latest remote state.&nbsp;</li>
-</ul>
-<p> The APIs do not not define how a Subscriber is created, this is left to the 
-  specific implementations. For example the CVS plug-in creates a Subscriber when 
-  a merge is performed, another for a comparison, and another when synchronizing 
-  the local workspace with the current branch. </p>
-<p>
-So let's revisit our first example of using SyncInfo and see how a
-Subscriber could be used to access SyncInfo.</p>
-
-<pre><span style="color: rgb(68, 68, 204);">// Create a file system subscriber and specify that the<br>// subscriber will synchronize with the provided file system location<br>Subscriber subscriber = new FileSystemSubscriber("c:\temp\repo");<br><br>// Allow the subscriber to refresh its state<br>subscriber.refresh(subscriber.roots(), IResource.DEPTH_INFINITE, monitor);<br><br>// Collect all the synchronization states and print<br>IResource[] children = subscriber.roots();<br>for(int i=0; i &lt; children.length; i++) {<br>  printSyncState(children[i]);<br>}<br><br>...<br><br>void printSyncState(Subscriber subscriber, IResource resource) {<br>  System.out.println(subscriber.getSyncInfo(resource).toString());<br></span><span
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">  IResource[] children = subscriber.members(resource);<br>  for(int i=0; i &lt; children.length; i++) {<br>    IResource child = children[i];<br>    if(! child.exists()) {<br>      System.out.println(resource.getFullPath() + " doesn't exist in the workspace");<br>    }<br>    printSyncState(subscriber, children[i]);<br>  }<br>}<br></span></span></pre>
-<p>
-The important point to remember is that the Subscriber knows about
-resources that do not exist in the workspace and non-existing resources
-can be returned from the <a
- href="../reference/api/org/eclipse/team/core/subscribers/Subscriber.html#members(org.eclipse.core.resources.IResource)">Subscriber#members()</a>
-and <a
- href="../reference/api/org/eclipse/team/core/synchronize/SyncInfo.html#getLocal()">SyncInfo#getLocal()</a>.
- </p>
-<h3>Displaying the synchronizations state in the UI</h3>
-<p>
-We could spend more time explaining how to manage synchronization state
-but instead let's see how to actually get the state shown to the user.
-A <a
- href="../reference/api/org/eclipse/team/ui/synchronize/ISynchronizeParticipant.html">ISynchronizeParticipant
-</a>is the user interface component that displays synchronization state
-and allows the user to affect its state. The Synchronize View displays
-synchronize participants, but it is also possible to show these in
-dialogs and wizards. In order to provide support for users to show any
-type of synchronization state to the user, even those not based on
-SyncInfo and Subscribers, a participant is a very generic component.</p>
-<p>
-There is also an extension point called <a
- href="../reference/extension-points/org_eclipse_team_ui_synchronizeWizards.html">org.eclipse.team.ui.synchronizeWizards</a>
-to add a synchronization creation wizard. This will put your wizard in
-the global synchronize action and in the Synchronize View, so that
-users can easily create a synchronization of your type.
-</p>
-<p>
-However, if you have implemented a Subscriber you can benefit from a
-concrete participant called <a
- href="../reference/api/org/eclipse/team/ui/synchronize/SubscriberParticipant.html">SubscriberParticipant
-</a>which will provide
-the following functionality:
-</p>
-
-<ul>
-  <li>Collects SyncInfo from a Subscriber in the background.</li>
-  <li>Listens to changes in the workspace and those found when a
-Subscriber is refreshed and keeps the synchronization state updated
-dynamically.</li>
-  <li>Provides the user interface that support modes for filtering the
-changes, and layouts.</li>
-  <li>Support scheduling a refresh with the Subscriber so that the
-synchronization states are kept up-to-date.</li>
-  <li>Supports refreshing a Subscriber in the background.</li>
-  <li>Supports navigation of the changes and showing the differences
-between the files.</li>
-  <li>Supports configuration of the actions, toolbars, and decorators
-by subclasses.<br>
-  </li>
-</ul>
-<p>The best way to explain these concepts are to see them used in the context 
-  of a simple example. Go to the <a
- href="team_synchronize_localhistory_example.htm">local history synchronization</a> 
-  example to see how all of these pieces can be used together. Or if you want 
-  pointers on how to use the more advanced APIs, go to <a
- href="team_synchronize_beyond_basics.htm">Beyond The Basics</a>.<br>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_synchronize_beyond_basics.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_synchronize_beyond_basics.htm
deleted file mode 100644
index 3e3fa5b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_synchronize_beyond_basics.htm
+++ /dev/null

@@ -1,177 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Synchronization Support - Beyond the basics</title>
-  <link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-<body style="background-color: rgb(255, 255, 255);">
-<h2>Beyond the Basics</h2>
-<p>If you plan on providing synchronization support and don't have an existing 
-  mechanism for managing synchronization state, this section explains how to implementing 
-  a Subscriber from scratch. This means that there is no existing synchronization 
-  infrastructure and illustrates how to use some API that is provided to maintain 
-  the synchronization state.<br>
-</p>
-<p>For the remainder of this example we will make use of a running
-example. The source code can be found in the file system provider
-package of the <a
- href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.team.examples.filesystem/">org.eclipse.team.examples.filesystem</a>
-plug-in. You should check the project out from the CVS repository and
-use as a reference while you are reading this tutorial. </p>
-<h3>Implementing a Subscriber From Scratch</h3>
-<p>This first example assumes that there is no existing infrastructure for maintaining 
-  the synchronization state of the local workspace. When implementing a subscriber 
-  from scratch, you can make use of some additional API provided in the <em>org.eclipse.team.core</em> 
-  plug-in. The <a
- href="../reference/api/org/eclipse/team/core/variants/package-summary.html">org.eclipse.team.core.variants</a> 
-  package contains two subclasses of <a
- href="../reference/api/org/eclipse/team/core/subscribers/Subscriber.html">Subscriber 
-  </a>which can be used to simplify implementation. The first is <a
- href="../reference/api/org/eclipse/team/core/variants/ResourceVariantTreeSubscriber.html">ResourceVariantTreeSubscriber 
-  </a>which will be discussed in the second example below. The second is a subclass 
-  of the first: <a
- href="../reference/api/org/eclipse/team/core/variants/ThreeWaySubscriber.html">ThreeWaySubscriber</a>. 
-  This subscriber implementation provides several helpful classes for managing 
-  the synchronization state of a local workspace. If you do not have any existing 
-  infrastructure, this is a good place to start. </p>
-<p>Implementing a subscriber from scratch will be illustrated using the file system 
-  example available in the <a
- href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.team.examples.filesystem/">org.eclipse.team.examples.filesystem</a> 
-  plug-in. The code in the following description is kept to a minimum since it 
-  is available from the Eclipse CVS repository. Although not technically a three-way 
-  subscriber, the file system example can still make good use of this infrastructure. 
-  The FTP and WebDAV plug-ins also are built using this infrastructure.</p>
-<h3>ThreeWaySubscriber</h3>
-<p>For the file system example, we already had an implementation of a <a href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider 
-  </a>that associated a local project with a file system location where the local 
-  contents were mirrored. FileSystemSubscriber was created as a subclass of <a href="../reference/api/org/eclipse/team/core/variants/ThreeWaySubscriber.html">ThreeWaySubscriber</a> 
-  in order to make use of a <a href="../reference/api/org/eclipse/team/core/variants/ThreeWaySynchronizer.html">ThreeWaySynchronizer</a> 
-  to manage workspace synchronization state. Subclasses of this class must do 
-  the following:</p>
-<ul>
-  <li>create a <a href="../reference/api/org/eclipse/team/core/variants/ThreeWaySynchronizer.html">ThreeWaySynchronizer</a> 
-    instance to manage the local workspace synchronization state.</li>
-  <li>create an instance of a <a href="../reference/api/org/eclipse/team/core/variants/ThreeWayRemoteTree.html">ThreeWayRemoteTree</a> 
-    subclass to provide remote tree refresh. 
-  <ul>
-    <li>The class FileSystemRemoteTree was defined for this
-purpose</li>
-  </ul></li>
-  <li>implement a method to create the resource variant handles used to
-calculate the synchronization state.
-    <ul>
-      <li>The class FileSystemResourceVariant (a subclass of <a href="../reference/api/org/eclipse/team/core/variants/CachedResourceVariant.html">CachedResourceVariant</a>) 
-        was defined for this</li>
-    </ul>
-  </li>
-  <li>implement the roots method.
-    <ul>
-      <li>The roots for the subscriber are all the projects mapped to
-the FileSystemProvider. Callbacks were added to FileSystemProvider
-in order to allow the FileSystemSubscriber to generate change
-events when projects are mapped and unmapped.</li>
-    </ul>
-  </li>
-</ul>
-<p>In addition to the subscriber implementation, the get and put
-operations for the file system provider were modified to update the
-synchronization state in the ThreeWaySynchronizer. The
-operations are implemented in the class
-org.eclipse.team.examples.filesystem.FileSystemOperations.</p>
-<h3>ThreeWaySynchronizer</h3>
-<p><a href="../reference/api/org/eclipse/team/core/variants/ThreeWaySynchronizer.html">ThreeWaySynchronizer</a> 
-  manages the synchronization state between the local workspace and a remote location. 
-  It caches and persists the local, base and remote timestamps in order to support 
-  the efficient calculation of the synchronization state of a resource. It also 
-  fires change notifications to any registered listeners. The <a href="../reference/api/org/eclipse/team/core/variants/ThreeWaySubscriber.html">ThreeWaySubscriber</a> 
-  translates these change events into the proper format to be sent to listeners 
-  registered with the subscriber.</p>
-<p>The <a href="../reference/api/org/eclipse/team/core/variants/ThreeWaySynchronizer.html">ThreeWaySynchronizer</a> 
-  makes use of Core scheduling rules and locks to ensure thread safety and provide 
-  change notification batching.</p>
-<h3>ThreeWayRemoteTree</h3>
-<p>A <a href="../reference/api/org/eclipse/team/core/variants/ThreeWayRemoteTree.html">ThreeWayRemoteTree</a> 
-  is a subclass of <a href="../reference/api/org/eclipse/team/core/variants/ResourceVariantTree.html">ResourceVariantTree</a> 
-  that is tailored to the <a href="../reference/api/org/eclipse/team/core/variants/ThreeWaySubscriber.html">ThreeWaySubscriber</a>. 
-  It must be overridden by clients to provide the mechanism for fetching the remote 
-  state from the server. <a href="../reference/api/org/eclipse/team/core/variants/ResourceVariantTree.html">ResourceVariantTree</a> 
-  is discussed in more detail in the next example.</p>
-<h3>CachedResourceVariant</h3>
-<p>A <a href="../reference/api/org/eclipse/team/core/variants/CachedResourceVariant.html">CachedResourceVariant</a> 
-  is a partial implementation of IResourceVariant that caches any fetched contents 
-  for a period of time (currently 1 hour). This is helpful since the contents 
-  may be accessed several times in a short period of time (for example, to determine 
-  the synchronization state and display the contents in a compare editor). Subclasses 
-  must still provide the unique content identifier along with the byte array that 
-  can be persisted in order to recreate the resource variant handle.</p>
-<h3>Building on Top of Existing Workspace Synchronization</h3>
-<p>Many repository providers may already have a mechanism for managing their synchronization 
-  state (e.g. if they have existing plug-ins). The <a href="../reference/api/org/eclipse/team/core/variants/ResourceVariantTreeSubscriber.html">ResourceVariantTreeSubscriber</a> 
-  and its related classes provide the ability to build on top of an existing synchronization 
-  infrastructure. For example, this is the superclass of all of the CVS subscribers.</p>
-<h4>ResourceVariantTreeSubscriber</h4>
-<p>As was mentioned in the previous example, the <a href="../reference/api/org/eclipse/team/core/variants/ThreeWaySubscriber.html">ThreeWaySubscriber</a> 
-  is a subclass of <a href="../reference/api/org/eclipse/team/core/variants/ResourceVariantTreeSubscriber.html">ResourceVariantTreeSubscriber</a> 
-  that provides local workspace synchronization using a <a href="../reference/api/org/eclipse/team/core/variants/ThreeWaySynchronizer.html">ThreeWaySynchronizer</a>. 
-  Subclasses of <a href="../reference/api/org/eclipse/team/core/variants/ResourceVariantTreeSubscriber.html">ResourceVariantTreeSubscriber</a> 
-  must provide:</p>
-<ul>
-  <li>
-    <p>Subclasses of <a href="../reference/api/org/eclipse/team/core/variants/ResourceVariantTree.html">ResourceVariantTree</a> 
-      (or <a href="../reference/api/org/eclipse/team/core/variants/AbstractResourceVariantTree.html">AbstractResourceVariantTree</a>) 
-      that provide the behavior for traversing and refreshing the remote resource 
-      variants and, for subscribers that support three-way comparisons, the base 
-      resource variants.</p>
-  </li>
-  <li>An implementation of <a href="../reference/api/org/eclipse/team/core/variants/IResourceVariantComparator.html">IResourceVariantComparator</a> 
-    that performs the two-way or three-way comparison for a local resource and 
-    its base and remote resource variants.It is common to also provide a subclass 
-    of <a href="../reference/api/org/eclipse/team/core/synchronize/SyncInfo.html">SyncInfo</a> 
-    in order to customize the synchronization state determination algorithm. </li>
-  <li>An implementation of the roots method for providing the roots of the subscriber 
-    and an implementation of the isSupervised method for determining what resources 
-    are supervised by the subscriber.</li>
-</ul>
-<p>The other capabilities of the subscriber are implemented using these
-facilities.</p>
-<h4>ResourceVariantTree</h4>
-<p><a href="../reference/api/org/eclipse/team/core/variants/ResourceVariantTree.html">ResourceVariantTree</a> 
-  is a concrete implementation of <a href="../reference/api/org/eclipse/team/core/variants/IResourceVariantTree.html">IResourceVariantTree</a> 
-  that provides the following:</p>
-<ul>
-  <li>traversal of the resource variant tree</li>
-  <li>logic to merge the previous resource variant tree state with the
-current fetched state.</li>
-  <li>caching of the resource variant tree using a <a href="../reference/api/org/eclipse/team/core/variants/ResourceVariantByteStore.html">ResourceVariantByteStore</a>.</li>
-</ul>
-<p>The following must be implemented by subclasses:</p>
-<ul>
-  <li>creation of resource variant handles from the cached bytes that
-represent a resource variant</li>
-  <li>fetching of the current remote state from the server</li>
-  <li>creation of the byte store instance used to cache the bytes that
-uniquely identify a resource variant</li>
-</ul>
-<p>Concrete implementations of <a href="../reference/api/org/eclipse/team/core/variants/ResourceVariantByteStore.html">ResourceVariantByteStore</a> 
-  are provided that persist bytes across workbench invocations (<a href="../reference/api/org/eclipse/team/core/variants/PersistantResourceVariantByteStore.html">PersistantResourceVariantByteStore</a>) 
-  or cached the bytes only for the current session (<a href="../reference/api/org/eclipse/team/core/variants/SessionResourceVariantByteStore.html">SessionResourceVariantByteStore</a>). 
-  However, building a subscriber on top of an existing workspace synchronization 
-  infrastructure will typically require the implementation of <a href="../reference/api/org/eclipse/team/core/variants/ResourceVariantByteStore.html">ResourceVariantByteStore</a> 
-  subclasses that interface with the underlying synchronizer. For example the 
-  <a href="../reference/api/org/eclipse/team/core/variants/ThreeWayRemoteTree.html">ThreeWayRemoteTree</a> 
-  makes use of a byte store implementation that stores the remote bytes in the 
-  <a href="../reference/api/org/eclipse/team/core/variants/ThreeWaySynchronizer.html">ThreeWaySynchronizer</a>.</p>
-<p>The creation of resource variant handles for this example does not differ from 
-  the previous example except that the handles are requested from a resource variant 
-  tree instance instead of the subscriber.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_synchronize_localhistory_example.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_synchronize_localhistory_example.htm
deleted file mode 100644
index 1f26f67..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_synchronize_localhistory_example.htm
+++ /dev/null

@@ -1,277 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-<meta content="text/css" http-equiv="Content-Style-Type">
-<link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-<title>Synchronization Support - Local History Example</title>
-<link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-<body style="background-color: rgb(255, 255, 255);">
-<h2>Local History Example</h2>
-<p>The best way to understand the Synchronize APIs is to create a simple example 
-  that actually works. In this example we will be creating a page in the Synchronize 
-  View that will display the latest local history state for all files in the workspace. 
-  The local history synchronization will update automatically when changes are 
-  made to the workspace, and a compare editor can open to browse, merge, then 
-  changes. We will also add a custom decorator to show the last timestamp of the 
-  local history element and an action to revert the workspace files to their latest 
-  saved local history state. This is an excellent example because we already have 
-  a store of resource variants available and we don't have to manage it.</p>
-<p>For the remainder of this example we will make use of a running example. Much, 
-  but not all, of the source code will be included on this page. The full source 
-  code can be found in the local history package of the <a
- href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.team.examples.filesystem/">org.eclipse.team.examples.filesystem</a> 
-  plug-in. You can check the project out from the CVS repository and use it as 
-  a reference while you are reading this tutorial. <em>Disclaimer</em>: The source 
-  code in the example plug-ins may change over time. To get a copy that matches 
-  what is used in this example, you can check out the project using the 3.0 version 
-  tag (most likely R3_0) or a date tag of June 28, 2004.<br>
-  <br>
-  <img src="images/team_synchronize_example_localhistory_overview.png" alt="local history overview"><br>
-  <br>
-  This screen shot shows the local history synchronization in the Synchronize 
-  View. With it you can browse the changes between the local resource and the 
-  latest state in history. It has a custom decorator for displaying the timestamp 
-  associated with the local history entry and a custom action to revert your file 
-  to the contents in the local history. Notice also that the standard Synchronize 
-  View presentation is used which provide problem annotations, compressed folder 
-  layout, and navigation buttons.</p>
-<h3>Defining the variants for local history</h3>
-<p>The first step is to define a variant to represent the elements from local 
-  history. This will allow the synchronize APIs to access the contents from the 
-  local history so it can be compared with the current contents and displayed 
-  to the user.</p>
-<pre><span style="color: rgb(68, 68, 204);">public class LocalHistoryVariant implements IResourceVariant {</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">  private final IFileState state;</span><br
- style="color: rgb(68, 68, 204);"><br style="color: rgb(68, 68, 204);"><span
- style="color: rgb(68, 68, 204);">  public LocalHistoryVariant(IFileState state) {</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">    this.state = state;</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">  }</span><br
- style="color: rgb(68, 68, 204);"><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">  public String getName() {</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">    return state.getName();</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">  }</span><br
- style="color: rgb(68, 68, 204);"><br style="color: rgb(68, 68, 204);"><span
- style="color: rgb(68, 68, 204);">  public boolean isContainer() {</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">    return false;</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">  }</span><br
- style="color: rgb(68, 68, 204);"><br style="color: rgb(68, 68, 204);"><span
- style="color: rgb(68, 68, 204);">  public IStorage getStorage(IProgressMonitor monitor) throws TeamException {</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">    return state;</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">  }</span><br
- style="color: rgb(68, 68, 204);"><br style="color: rgb(68, 68, 204);"><span
- style="color: rgb(68, 68, 204);">  public String getContentIdentifier() {</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">    return Long.toString(state.getModificationTime());</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">  }</span><br
- style="color: rgb(68, 68, 204);"><br style="color: rgb(68, 68, 204);"><span
- style="color: rgb(68, 68, 204);">  public byte[] asBytes() {</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">    return null;</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">  }</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">}</span></pre>
-<p>Since the IFileState interface already provides access to the contents of the 
-  file from local history (i.e. implements the IStorage interface), this was easy. 
-  Generally, when creating a variant you have to provide a way of accessing the 
-  content, a content identifier that will be displayed to the user to identify 
-  this variant, and a name. The asBytes() method is only required if persisting 
-  the variant between sessions. <br>
-  <br>
-  Next, let's create a variant comparator that allows the SyncInfo calculation 
-  to compare local resources with their variants. Again, this is easy because 
-  the existence of a local history state implies that the content of the local 
-  history state differs from the current contents of the file. This is because 
-  the specification for local history says that it won't create a local history 
-  state if the file hasn't changed. </p>
-<pre><span style="color: rgb(68, 68, 204);">public class LocalHistoryVariantComparator implements IResourceVariantComparator {</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">  public boolean compare(IResource local, IResourceVariant remote) {</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">    return false;</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">  }</span><br
- style="color: rgb(68, 68, 204);"><br style="color: rgb(68, 68, 204);"><span
- style="color: rgb(68, 68, 204);">  public boolean compare(IResourceVariant base, IResourceVariant remote) {</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">    return false;</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">  }</span><br
- style="color: rgb(68, 68, 204);"><br style="color: rgb(68, 68, 204);"><span
- style="color: rgb(68, 68, 204);">  public boolean isThreeWay() {</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">    return false;</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">  }</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">}</span></pre>
-<p>Because we know that the existence of the local history state implies that 
-  it is different from the local, we can simply return <strong>false</strong> 
-  when comparing the file to it's local history state. Also, synchronization with 
-  the local history is only two-way because we don't have access to a base resource 
-  so the method for comparing two resource variants is not used.</p>
-<p> Note that the synchronize calculation won't call the compare method of the 
-  comparator if the variant doesn't exist (i.e. is null). It is only called if 
-  both elements exist. In our example, this would occur both for files that don't 
-  have a local history and for all folders (which never have a local history). 
-  To deal with this, we need to define our own subclass of SyncInfo in order to 
-  modify the calculated synchronization state for these cases.</p>
-<pre><span style="color: rgb(68, 68, 204);">public class LocalHistorySyncInfo extends SyncInfo {
-  public LocalHistorySyncInfo(IResource local, IResourceVariant remote, IResourceVariantComparator comparator) {
-    super(local, null, remote, comparator);
-  }
-
-  protected int calculateKind() throws TeamException {
-    if (getRemote() == null)
-      return IN_SYNC;
-    else
-      return super.calculateKind();
-  }
-}</span></pre>
-<p>We have overridden the constructor to always provide a base that is <em>null</em> 
-  (since we are only using two-way comparison) and we have modified the synchronization 
-  kind calculation to return <em>IN_SYNC</em> if there is no remote (since we 
-  only care about the cases where there is a local file and a file state in the 
-  local history.</p>
-<h3>Creating the Subscriber</h3>
-<p>Now we will create a Subscriber that will provide access to the resource variants 
-  in the local history. Since local history can be saved for any file in the workspace, 
-  the local history Subscriber will supervise every resource and the set of roots 
-  will be all projects in the workspace. Also, there is no need to provide the 
-  ability to refresh the subscriber since the local history changes only when 
-  the contents of a local file changes. Therefore, we can update our state whenever 
-  a resource delta occurs. That leaves only two interesting method on our local 
-  history subscriber: obtaining a SyncInfo and traversing the workspace. </p>
-<pre><span style="color: rgb(68, 68, 204);">public SyncInfo getSyncInfo(IResource resource) throws TeamException {
-  try {
-    IResourceVariant variant = null;
-    if(resource.getType() == IResource.FILE) {
-      IFile file = (IFile)resource;
-      IFileState[] states = file.getHistory(null);
-      if(states.length > 0) {
-        // last state only
-        variant = new LocalHistoryVariant(states[0]);
-      } 
-    }
-    SyncInfo info = new LocalHistorySyncInfo(resource, variant, comparator);
-    info.init();
-    return info;
-  } catch (CoreException e) {
-    throw TeamException.asTeamException(e);
-  }
-}</span></pre>
-<p>The Subscriber will return a new SyncInfo instance that will contain the latest 
-  state of the file in local history. The SyncInfo is created with a local history 
-  variant for the remote element. For projects, folders and files with no local 
-  history, no remote resource variant is provided, which will result in the resource 
-  being considered in-sync due to the <em>calculateKind</em> method in our LocalHistorySyncInfo. 
-</p>
-<p>The remaining code in the local history subscriber is the implementation of 
-  the <em>members</em> method:</p>
-<pre><span style="color: rgb(68, 68, 204);">public IResource[] members(IResource resource) throws TeamException {
-  try {
-    if(resource.getType() == IResource.FILE)
-      return new IResource[0];
-    IContainer container = (IContainer)resource;
-    List existingChildren = new ArrayList(Arrays.asList(container.members()));
-    existingChildren.addAll(
-      Arrays.asList(container.findDeletedMembersWithHistory(IResource.DEPTH_INFINITE, null)));
-    return (IResource[]) existingChildren.toArray(new IResource[existingChildren.size()]);
-  } catch (CoreException e) {
-    throw TeamException.asTeamException(e);
-  }
-}</span></pre>
-<p>The interesting detail of this method is that it will return non-existing children 
-  if a deleted resource has local history. This will allow our Subscriber to return 
-  SyncInfo for elements that only exist in local history and are no longer in 
-  the workspace.</p>
-<h3>Adding a Local History Synchronize Participant</h3>
-<p>So far we have created the classes which provide access to SyncInfo for elements 
-  in local history. Next, we will create the UI elements that will allow us to 
-  have a page in the Synchronize View to display the last history state for every 
-  element in local history. Since we have a Subscriber, adding this to the Synchronize 
-  View is easy. Let's start by adding an synchronize participant extension point:</p>
-<pre><span style="color: rgb(68, 68, 204);">&lt;extension
-       </span><span style="color: rgb(68, 68, 204);">point="org.eclipse.team.ui.synchronizeParticipants"&gt;</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">    &lt;participant</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">        persistent="false"</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">        icon="synced.png"</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">        class="org.eclipse.team.synchronize.example.LocalHistoryParticipant"</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">        name="Latest From Local History"</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">        id="org.eclipse.team.synchronize.example"/&gt;</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);"> &lt;/extension&gt;</span></pre>
-<p>Next we have to implement the LocalHistoryParticipant. It will subclass SubscriberParticipant 
-  which will provide all the default behavior for collecting SyncInfo from the 
-  subscriber and updating sync states when workspace changes occur. In addition, 
-  we will add an action to revert the workspace resources to the latest in local 
-  history.</p>
-<p>First, we will look at how a custom action is added to the participant.</p>
-<pre><span style="color: rgb(68, 68, 204);">public static final String CONTEXT_MENU_CONTRIBUTION_GROUP = "context_group_1"; //$NON-NLS-1$
-  
-private class LocalHistoryActionContribution extends SynchronizePageActionGroup {
-  public void initialize(ISynchronizePageConfiguration configuration) {
-    super.initialize(configuration);
-    appendToGroup(
-      ISynchronizePageConfiguration.P_CONTEXT_MENU, CONTEXT_MENU_CONTRIBUTION_GROUP, 
-      new SynchronizeModelAction("Revert to latest in local history", configuration) { //$NON-NLS-1$
-        protected SynchronizeModelOperation getSubscriberOperation(ISynchronizePageConfiguration configuration, IDiffElement[] elements) {
-          return new RevertAllOperation(configuration, elements);
-        }
-      });
-  }
-}</span></pre>
-<p>Here we are adding a specific SynchronizeMoidelAction and operation. The behavior 
-  we get for free here is the ability to run in the background and show busy status 
-  for the nodes that are being worked on. The action reverts all resources in 
-  the workspace to their latest state in local history. The action is added by 
-  adding an action contribution to the participants configuration. The configuration 
-  is used to describe the properties used to build the participant page that will 
-  display the actual synchronize UI. </p>
-<p>The participant will initialize the configuration as follows in order to add 
-  the local history action group to the context menu:</p>
-<pre><span style="color: rgb(68, 68, 204);">protected void initializeConfiguration(ISynchronizePageConfiguration configuration) {</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">  super.initializeConfiguration(configuration);</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">  configuration.addMenuGroup(</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">      ISynchronizePageConfiguration.P_CONTEXT_MENU, </span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">      CONTEXT_MENU_CONTRIBUTION_GROUP);</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">  configuration.addActionContribution(new LocalHistoryActionContribution());
-  configuration.addLabelDecorator(new LocalHistoryDecorator());</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">}</span></pre>
-<p>Now lets look at how we can provide a custom decoration. The last line of the 
-  above method registers the following decorator with the page's configuration.</p>
-<pre><span style="color: rgb(68, 68, 204);">public</span><span style="color: rgb(68, 68, 204);"> class LocalHistoryDecorator extends LabelProvider implements ILabelDecorator {<br>  public String decorateText(String text, Object element) {<br>    if(element instanceof ISynchronizeModelElement) {<br>      ISynchronizeModelElement node = (ISynchronizeModelElement)element;<br>      if(node instanceof IAdaptable) {<br>        SyncInfo info = (SyncInfo)((IAdaptable)node).getAdapter(SyncInfo.class);<br>        if(info != null) {<br>          LocalHistoryVariant state = (LocalHistoryVariant)info.getRemote();<br>          return text+ &quot; (&quot;+ state.getContentIdentifier() + &quot;)&quot;;<br>        }<br>      }<br>    }<br>    return text;<br>  }<br>    <br>  public Image decorateImage(Image image, Object element) {<br>    return null;<br>  }<br>}</span></pre>
-<p>The decorator extracts the resource from the model element that appears in 
-  the synchronize view and appends the content identifier of the local history 
-  resource variant to the text label that appears in the view.</p>
-<p>The last and final piece is to provide a wizard that will create the local 
-  history participant. The Team Synchronizing perspective defines a global synchronize 
-  action that allows users to quickly create a synchronization. In addition, the 
-  ability to create synchronizations in available from the Synchronize view toolbar. 
-  To start, create a synchronizeWizards extension point:</p>
-<pre><span style="color: rgb(68, 68, 204);">&lt;extension</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">         point="org.eclipse.team.ui.synchronizeWizards"&gt;</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">    &lt;wizard</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">        class="org.eclipse.team.synchronize.example.LocalHistorySynchronizeWizard"</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">        icon="synced.png"</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">        description="Creates a synchronization against the latest local history state of all resources in the workspace"</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">        name="Latest From Local History Synchronize"</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">        id="ExampleSynchronizeSupport.wizard1"/&gt;</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">&lt;/extension&gt;</span></pre>
-<p>This will add our wizard to the list and in the wizards finish() method we 
-  will simply create our participant and add it to the synchronize manager.</p>
-<pre><span style="color: rgb(68, 68, 204);">LocalHistoryPartipant participant = new LocalHistoryPartipant();</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">ISynchronizeManager manager = TeamUI.getSynchronizeManager();</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">manager.addSynchronizeParticipants(new ISynchronizeParticipant[] {participant});</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">ISynchronizeView view = manager.showSynchronizeViewInActivePage();</span><br
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">view.display(participant);</span></pre>
-<h3>Conclusion</h3>
-<p>This is a simple example of using the synchronize APIs and we have glossed 
-  over some of the details in order to make the example easier to understand. 
-  Writing responsive and accurate synchronization support is non-trivial, the 
-  hardest part being the management of synchronization information and the notification 
-  of synchronization state changes. The user interface, if the one associated 
-  with SubscriberParticipants is adequate, is the easy part once the Subscriber 
-  implementation is complete. For more examples please refer to the org.eclipse.team.example.filesystem 
-  plug-in and browse the subclasses in the workspace of Subscriber and ISynchronizeParticipant.<br>
-  <br>
-  The next section describes some class and interfaces that can help you write 
-  a Subscriber from scratch including how to cache synchronization states between 
-  workbench sessions.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_ui.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_ui.htm
deleted file mode 100644
index 0cb4ccc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_ui.htm
+++ /dev/null

@@ -1,48 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Building a team UI</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-   Building a team UI
-</h2><p>
-   The team UI plug-in is based on the philosophy that the team subsystem should
-   provide simple hooks and slots for providers to add their UI
-   implementation.&nbsp; Rather than define standard team operations, the team
-   plug-in leaves the workflow up to the provider implementation.&nbsp; The team
-   UI implements a few standard wizards and dialog pages that providers can
-   enhance, such as the project configuration wizard, the project set export
-   dialog, and the preferences for file types and ignored files.&nbsp; More
-   importantly, it also defines a
-   &quot;Team&quot; slot for actions and preferences that serve as a single
-   point of integration for UI contributed by provider's.&nbsp; In this way, the
-   user learns where to find all team related function.
-</p>
-<p>To build a team UI, you must start with basic design work.&nbsp; Identify the actions that your
-repository supports and in what views and editors these actions should be accessible.&nbsp; The implementation for your UI is done with the <a href="workbench_basicext.htm">standard
-workbench extension points</a>.&nbsp; In addition, you can define your own
-preferences which plug in to the standard framework.&nbsp; You may even need to
-build your own views to present repository specific information and operations.
-(The CVS client implements its own views for synchronizing with the repository
-and navigating the repository.)
-</p>
-<p>In short, building a team UI involves knowledge of a few team-specific UI
-classes, but is mostly accomplished using workbench UI design and development
-principles.
-</p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_ui_actions.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_ui_actions.htm
deleted file mode 100644
index 965d9ba..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_ui_actions.htm
+++ /dev/null

@@ -1,100 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Adding team actions</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-   Adding team actions
-</h3>
-<p>The team UI plug-in defines a popup menu extension in order to consolidate
-all team-related actions in one place.&nbsp; The team menu includes many
-subgroup slots so that team provider plug-ins can contribute actions and have
-some amount of control over the order of items in the menu.&nbsp; The following
-markup is from the team UI's plug-in manifest:</p>
-<pre>&lt;extension
-     point=&quot;org.eclipse.ui.popupMenus&quot;&gt;
-	&lt;objectContribution
-       	   id=&quot;org.eclipse.team.ui.ResourceContributions&quot;
-           objectClass=&quot;org.eclipse.core.resources.IResource&quot; adaptable=&quot;true&quot;&gt;
-		&lt;menu
-			id=&quot;<b>team.main</b>&quot;
-			path=&quot;additions&quot;
-			label=&quot;%TeamGroupMenu.label&quot;&gt;
-			<b>&lt;separator name=&quot;group1&quot;/&gt;
-			&lt;separator name=&quot;group2&quot;/&gt;
-			&lt;separator name=&quot;group3&quot;/&gt;
-			&lt;separator name=&quot;group4&quot;/&gt;
-			&lt;separator name=&quot;group5&quot;/&gt;
-			&lt;separator name=&quot;group6&quot;/&gt;
-			&lt;separator name=&quot;group7&quot;/&gt;
-			&lt;separator name=&quot;group8&quot;/&gt;
-			&lt;separator name=&quot;group9&quot;/&gt;
-			&lt;separator name=&quot;group10&quot;/&gt;</b>
-			&lt;separator name=&quot;targetGroup&quot;/&gt;
-			&lt;separator name=&quot;projectGroup&quot;/&gt;
-		&lt;/menu&gt;
-	... 
-&lt;/extension&gt;</pre>
-<p>A team menu is added to the popup menu of all views that show resources (or
-objects that adapt to resources.)&nbsp; Your plug-in can use the id of this menu
-and the separator groups in order to add your own menu items.&nbsp; There is
-nothing to keep you from defining your own popup menus, action sets, or view and
-editor actions.&nbsp; However, adding your actions to the predefined team menu
-makes it easier for the end user to find your actions.</p>
-<p>Let's look at a CVS action that demonstrates some interesting points:</p>
-<pre>&lt;extension
-    point=&quot;org.eclipse.ui.popupMenus&quot;&gt;
-     &lt;objectContribution
-           objectClass=&quot;org.eclipse.core.resources.IFile&quot;
-           adaptable=&quot;true&quot;
-           id=&quot;org.eclipse.team.ccvs.ui.IFileContributions&quot;&gt;
-        &lt;filter
-              <b>name=&quot;projectPersistentProperty&quot;</b>
-              <b>value=&quot;org.eclipse.team.core.repository=org.eclipse.team.cvs.core.cvsnature&quot;&gt;</b>
-        &lt;/filter&gt;
-        &lt;action
-              label=&quot;%IgnoreAction.label&quot;
-              tooltip=&quot;%IgnoreAction.tooltip&quot;
-              class=&quot;org.eclipse.team.internal.ccvs.ui.actions.IgnoreAction&quot;
-              menubarPath=&quot;<b>team.main/group3</b>&quot;
-              helpContextId=&quot;org.eclipse.team.cvs.ui.team_ignore_action_context&quot;
-              id=&quot;org.eclipse.team.ccvs.ui.ignore&quot;&gt;
-        &lt;/action&gt;
-	...</pre>
-<p>Note that the action is contributed using the <a href="../reference/extension-points/org_eclipse_ui_popupMenus.html"><b>org.eclipse.ui.popupMenus
-</b>
-</a>workbench extension point.&nbsp; Here are some team-specific things
-happening in the markup:</p>
-<ul>
-  <li>the action is filtered by a project persistent property which identifies
-    team providers.&nbsp; The value of the property must be of the format <b>&quot;org.eclipse.team.core.repository=&lt;your
-    repository id&gt;&quot;</b> where <b>&lt;your repository id&gt;</b> is the <b>id</b>
-    provided in the <a href="../reference/extension-points/org_eclipse_team_core_repository.html"> <b> org.eclipse.team.core.repository</b></a> 
-    markup.&nbsp; This filter ensures that the CVS popup menu items only appear for
-    files that appear in projects that have been mapped to the CVS repository
-    id.</li>
-  <li>the action is added to a group in the menu that was specified above in the
-    team UI plug-in</li>
-</ul>
-<p>The implementation of an action is largely dependent on your specific
-provider.</p>
-<p>&nbsp;</p>
-<p>
-   &nbsp;
-</p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_ui_decorators.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_ui_decorators.htm
deleted file mode 100644
index c9f8256..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_ui_decorators.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Team decorators</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Team decorators </h3>
-<p>Since any view that shows resources can contain projects that are configured 
-  with different team providers, it is helpful for team providers to contribute 
-  <a href="workbench_advext_decorators.htm">decorators</a> that distinguish resources 
-  configured for their repository.&nbsp; The CVS client uses decorators to show 
-  information such as a dirty flag (the &gt; symbol), tags, keywords (e.g. &quot;(ASCII 
-  -kkv)&quot;), and revisions (e.g. &quot;1.15&quot;). Icons can also be decorated 
-  (e.g. the <img src="images/team-version_controlled.png" alt="version control icon"> 
-  symbol indicates that the resource is managed by CVS).</p>
-
-
-
-
-<p><img src="images/teamdecorators.png" alt="Resource navigator with team decorators turned on" border="0" >
-</p>
-
-
-
-
-<p>Some decorators may be expensive to compute, so it's a good idea to allow the
-users some control over the use, or even content, of decorators.&nbsp; The CVS
-client provides a preference page that allows users to control the presentation
-and content of decorators.
-</p>
-
-
-
-
-<p>See <a href="../reference/extension-points/org_eclipse_ui_decorators.html"><b>org.eclipse.ui.decorators</b></a>
-for a complete description of the decorator extension point.&nbsp; The CVS
-decorator markup is as follows:
-</p>
-
-<pre>&lt;extension
-     point=&quot;org.eclipse.ui.decorators&quot;&gt;
-  &lt;decorator
-        objectClass=&quot;org.eclipse.core.resources.IResource&quot;
-        adaptable=&quot;true&quot;
-        label=&quot;%DecoratorStandard.name&quot;
-        state=&quot;false&quot;
-        class=&quot;org.eclipse.team.internal.ccvs.ui.CVSDecorator&quot;
-        id=&quot;org.eclipse.team.cvs.ui.decorator&quot;&gt;
-     &lt;description&gt;
-        %DecoratorStandard.description
-     &lt;/description&gt;
-  &lt;/decorator&gt;
-&lt;/extension&gt;</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_ui_prefs.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_ui_prefs.htm
deleted file mode 100644
index aaa70e3..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_ui_prefs.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Adding preferences and properties</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Adding preferences and properties</h3>
-<p><a href="preferences_prefs.htm">Preferences</a> and <a href="preferences_prop_contribute.htm">properties</a>
-can be contributed by team UI plug-ins using the standard techniques.&nbsp; The
-only difference for a team plug-in is that preferences should be contributed
-using the team category, so that all team related preferences are grouped
-together.&nbsp; The CVS markup for the main preferences page looks like this:</p>
-<pre>&lt;extension
-      point=&quot;org.eclipse.ui.preferencePages&quot;&gt;
-   &lt;page
-         name=&quot;%PreferencePage.name&quot;
-         <b>category=&quot;org.eclipse.team.ui.TeamPreferences&quot;</b>
-         class=&quot;org.eclipse.team.internal.ccvs.ui.CVSPreferencesPage&quot;
-         id=&quot;org.eclipse.team.cvs.ui.CVSPreferences&quot;&gt;
-   &lt;/page&gt;
-&lt;/extension&gt;</pre>
-<p>The preferences dialog shows the CVS preferences underneath the team
-category.</p>
-<p><img src="images/teamprefs.png" alt="" border="0" ></p>
-<p>&nbsp;</p>
-<p>Properties are added as described by <a href="../reference/extension-points/org_eclipse_ui_propertyPages.html"><b>org.eclipse.ui.propertyPages</b></a>.&nbsp;
-There is no special team category for properties, since a resource can only be
-configured for one repository provider at a time.&nbsp; However, you must set up
-your property page to filter on the team project persistent property (similar to
-the way we filtered resources for popup menu actions.)</p>
-<pre>
-  &lt;extension
-    point=&quot;org.eclipse.ui.propertyPages&quot;&gt;
-     &lt;page
-           objectClass=&quot;org.eclipse.core.resources.IFile&quot;
-           adaptable=&quot;true&quot;
-           name=&quot;%CVS&quot;
-           class=&quot;org.eclipse.team.internal.ccvs.ui.CVSFilePropertiesPage&quot;
-           id=&quot;org.eclipse.team.ccvs.ui.propertyPages.CVSFilePropertiesPage&quot;&gt;
-        &lt;filter
-<b>              name=&quot;projectPersistentProperty&quot;
-              value=&quot;org.eclipse.team.core.repository=org.eclipse.team.cvs.core.cvsnature&quot;&gt;
-</b>        &lt;/filter&gt;
-     &lt;/page&gt;
-     ...</pre>
-<p>
-   &nbsp;
-</p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua.htm
deleted file mode 100644
index ed437ca..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua.htm
+++ /dev/null

@@ -1,75 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
-<meta content="text/css" http-equiv="Content-Style-Type">
-<link type="text/css" charset="ISO-8859-1" href="../book.css" rel="STYLESHEET">
-<link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-
-<body bgcolor="#ffffff">
-
-<h1>User Assistance</h1>
-
-<p><b>What is user assistance?</b></p>
-
-<p>User assistance is a set of components that together introduce the user
-to the product, guide the user through tasks, and help the user find more
-information about the product. There are three basic components:</p>
-
-<ul>
-<li><a href="#welcome">Welcome</a></li>
-<li><a href="#help">Help</a></li>
-<li><a href="#cheatsheet">Cheat Sheets</a></li>
-</ul>
-
-<a name="welcome"><p><b>Welcome</b></p></a>
-
-<p>Welcome (also referred to as Intro) support is a set of
-extension points and workbench parts that allow plug-ins to define specialized
-pages that introduce a platform product to new users. These extension points
-can be used to create the &quot;Initial User Experience&quot; of the product in
-the form of welcome pages. Welcome pages are intended to guide users into
-discovering a product's functionality. They are typically shown the first time
-a product is started.</p>
-
-<p>For information on how to construct welcome content, <a href="ua_intro.htm">click
-here</a>.</p>
-
-<p align=center><img src="images/ua_intro.png"></p>
-
-<a name="help"><p><b>Help</b></p></a>
-
-<p>The help system provides the raw building blocks to
-structure and contribute documentation to the platform. It does not dictate
-structure or granularity of documentation. You can choose the tools and
-structure for your documentation that suits your needs.&nbsp; The help plug-in
-allows you to describe your documentation structure to the platform using a
-table of contents (toc) file.</p>
-
-<p>To learn more about contributing help, <a href="ua_help.htm">click
-here</a>.</p>
-
-<p align=center><img src="images/ua_help.png"></p>
-
-<p>Help also includes context help support, where a user can
-summon help for a particular element in the UI (e.g. by pressing F1 on Windows).
-In addition, help provides the ability to perform a single search that finds
-information from any number of sources (federated information search).</p>
-
-<a name="cheatsheet"><p><b>Cheat Sheets</b></p></a>
-
-<p>Cheat sheets guide users through tasks. The task is broken down into steps and
-presented to the user one step at a time, and the user checks off the steps as
-he/she completes them. Cheat sheets come in two forms: simple (one task,
-several steps), and composite (many sub-tasks, each having many steps). Which
-one you use depends on the size and complexity of the task you want to guide
-the user through.</p>
-
-<p>To learn more about constructing cheat sheets, <a href="ua_cheatsheet.htm">click here</a>.</p>
-
-<p align=center><img src="images/ua_cheatsheet.png"></p>
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet.htm
deleted file mode 100644
index 4b07498..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Guiding the user through tasks</title>
-
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body bgcolor="#ffffff">
-
-<h2>Cheat sheets</h2>
-
-<b>Guiding the user through tasks</b>
-
-<p>
-Even when the platform UI filters out unneeded functionality, there is still a steep learning
-curve faced by a new user.  The platform UI introduces several mechanisms for helping the user choose what
-task needs to be done and guiding the user through the steps in that task.  These mechanisms are used by
-the workbench itself to help guide Eclipse SDK users through tasks.
-</p>
-<ul>
-<li><b><a href="ua_cheatsheet_simple.htm">Cheat sheets</a></b> can help guide the user through a series of 
-steps in order to achieve some
-overall goal.  Some steps can be performed by the cheat sheet, and some are described so that the user
-can manually complete the step.</li>
-<li><b><a href="ua_cheatsheet_composite.htm">Composite cheat sheets</a></b> 
-can guide the user through larger problems by breaking that problem into tasks. 
-Each task is represented by a simple cheat sheet. </li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite.htm
deleted file mode 100644
index b56bcc8..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite.htm
+++ /dev/null

@@ -1,120 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Contributing composite cheat sheets</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Contributing Composite Cheat Sheets</h3>
-
-<p>
-<a href="../../org.eclipse.platform.doc.user/reference/ref-composite-cheatsheets.htm">
-Composite cheat sheets</a> provide guidance through complex problems by breaking 
-the problem into a set of smaller tasks. Composite cheat sheets are registered 
-using the&nbsp; the <b>
-<a href="../reference/extension-points/org_eclipse_ui_cheatsheets_cheatSheetContent.html">
-org.eclipse.ui.cheatsheets.cheatSheetContent</a></b> extension point. </p>
-<h3>Content file format</h3>
-<p>The composite cheat sheet content itself is defined in a separate file which 
-conforms to the&nbsp; <a href="workbench_advext_compositeContentFile.html">
-composite cheat sheet schema</a>. The content file is&nbsp; an XML file and 
-consists of&nbsp; a set of tasks organized in groups into a tree structure. </p>
-<p>&lt;compositeCheatsheet&gt; is the root element of a composite cheat sheet. It will 
-have a single root task which may be a &lt;task&gt; or &lt;taskGroup&gt;. &lt;taskGroup&gt; 
-elements may have one or more children each of which can be a &lt;task&gt; or &lt;taskGroup&gt;. 
-A &lt;task&gt; does not have child tasks.</p>
-<p>Tasks and task groups may contain &lt;intro&gt; elements which contain the text to 
-be displayed before the task has been started and &lt;onCompletion&gt; elements which 
-contain the text to be displayed once the task is completed. Both the &lt;intro&gt; 
-and &lt;onCompletion&gt; elements may contain form text markup, in the example below 
-the tags &lt;b&gt; and &lt;/b&gt; are used to make text bold.</p>
-<p>Tasks may also contain &lt;param&gt; elements. A cheat sheet task may have any 
-of the following parameters: &quot;id&quot; is the id of a registered cheatsheet, &quot;path&quot; 
-is the relative path or URL of the cheat sheet content file and &quot;skipIntro&quot; is&nbsp; 
-a boolean parameter which if true causes&nbsp; the cheat sheet to start at the 
-first step rather than at the introduction. Either &quot;id&quot; or &quot;path&quot; but not both 
-must be specified.</p>
-<p>A &lt;dependency&gt; node from task &quot;B&quot; to task &quot;A&quot; represents a requirement that 
-task A is completed before task B can be started.</p>
-<h4>Example of a composite cheat sheet</h4>
-<p>The file below is an example of how to create a composite cheat sheet from 
-existing cheat sheets and how to create task groups and make tasks skippable.</p>
-<pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
-&lt;compositeCheatsheet name=&quot;Building and Publishing Plugins&quot;&gt;
-    &lt;taskGroup name= &quot;Introduction to the PDE&quot;&gt;
-         &lt;intro&gt; This composite cheat sheet contains tasks which can guide you through the &lt;b&gt;PDE&lt;/b&gt;, 
-                 from creating a simple project to deploying a feature 
-         &lt;/intro&gt;
-         &lt;taskGroup name= &quot;Build and deploy a plugin project&quot; kind = &quot;sequence&quot;&gt;
-             &lt;intro&gt; First you will learn how to create a java project, then you will deploy 
-                     that project.
-             &lt;/intro&gt;
-         &lt;task kind=&quot;cheatsheet&quot; name= &quot;Create a java project&quot; id = &quot;createJavaProject&quot;&gt;
-             &lt;param name=&quot;id&quot; value = &quot;org.eclipse.jdt.helloworld&quot;/&gt;
-             &lt;intro&gt;This task guide walks through the process of creating a simple hello world application. 
-                    The guide can launch wizards to create a new project and a new class. 
-             &lt;/intro&gt;
-             &lt;onCompletion&gt;Congratulations you have succeeded in creating a hello world application&lt;/onCompletion&gt;
-         &lt;/task&gt;
-         &lt;task kind=&quot;cheatsheet&quot; name= &quot;Deploy a java project&quot;&gt;
-             &lt;intro&gt;In this task the hello world project created in a previous task will be deployed. 
-                     This task guide shows show to create &lt;b&gt;features&lt;/b&gt; and &lt;b&gt;update sites&lt;/b&gt; 
-             &lt;/intro&gt;
-             &lt;dependsOn task = &quot;createJavaProject&quot; /&gt;
-             &lt;param name = &quot;id&quot; value = &quot;org.eclipse.pde.updates&quot; /&gt;
-         &lt;/task&gt;
-         
-         &lt;/taskGroup&gt;
-       
-         &lt;taskGroup name= &quot;Next Steps&quot;&gt;
-             &lt;intro&gt;Once you have learned how to create and deploy a java project you may want to learn 
-                     about SWT and Rich Clients. 
-             &lt;/intro&gt;
-             &lt;task kind=&quot;cheatsheet&quot; name= &quot;Create an SWT application&quot;&gt;
-                  &lt;param name = &quot;id&quot; value = &quot;org.eclipse.jdt.helloworld.swt&quot; /&gt;
-                  &lt;intro&gt;Eclipse plugins which contribute to the user interface use The Standard Widget Toolkit (SWT). 
-                        This task guide can be used to learn more about SWT. 
-                  &lt;/intro&gt;
-             &lt;/task&gt;
-             &lt;task kind=&quot;cheatsheet&quot; name= &quot;Create a Rich Client application&quot;&gt; 
-                &lt;param name = &quot;id&quot; value =&quot;org.eclipse.pde.rcpapp&quot; /&gt;
-                &lt;intro&gt;
-                     The minimal set of plug-ins needed to build a rich client application is 
-                     collectively known as the Rich Client Platform. This task guide walks through the steps 
-                     to create a rich client application.
-                &lt;/intro&gt;
-             &lt;/task&gt;
-         &lt;/taskGroup&gt;
-    &lt;/taskGroup&gt;
-&lt;/compositeCheatsheet&gt;</pre>
-<h3>Composite Cheat Sheet Extensibility - Provisional in Eclipse 3.2</h3>
-<p>Composite cheat sheets are extensible, however in Eclipse 3.2 this 
-extensibility is provisional and the classes could change before they become 
-API. Composite cheat sheet support can be extended by using the extension point 
-org.eclipse.ui.cheatsheets.cheatSheetContent which has two new elements 
-taskEditor and taskExplorer which allow for contribution of task editors and 
-task explorers.</p>
-<p>Contributing a task editor defines a new kind of task which displays in the 
-task detail section. To contribute a task editor implement a concrete subclass 
-of&nbsp; TaskEditor, then&nbsp; add a taskEditor element to plugin.xml.</p>
-<p>The representation of the task explorer is also configurable with an 
-extension point,&nbsp; a tree explorer&nbsp; is included with the Eclipse platform. By 
-default the explorer for a composite cheat sheet when first opened is a tree, an 
-attribute on the &lt;compositeCheatSheet&gt; element will allow that default to be 
-overridden. If more than one explorer is registered the view menu will contain a 
-menu item to switch between explorers. To contribute a task explorer first 
-implement a concrete subclass of&nbsp; TaskExplorer, then&nbsp; add a taskExplorer element 
-to plugin.xml.</p>
-<pre>&nbsp;</pre>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite_content.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite_content.htm
deleted file mode 100644
index 9adb3c9..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite_content.htm
+++ /dev/null

@@ -1,93 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Composite Cheat Sheets</title>
-<style>@import url("file:/E:/EclipseBuilds/eclipse-SDK-N20060320-0010-win32/eclipse/plugins/org.eclipse.sdk_3.2.0.N20060320-0010/book.css");</style>
-<style>@import url("file:/E:/EclipseBuilds/eclipse-SDK-N20060320-0010-win32/eclipse/configuration/org.eclipse.osgi/bundles/67/1/.cp/schema.css");</style>
-</HEAD>
-<BODY>
-
-<h3><CENTER>Composite Cheat Sheets</CENTER></h3>
-<p></p>
-<h6 class=CaptionFigColumn id=header>Identifier: </h6>org.eclipse.ui.cheatsheets.composite_schema<p></p>
-<h6 class=CaptionFigColumn id=header>Since: </h6>3.2
-<p></p>
-
-<p>
-<h6 class=CaptionFigColumn id=header>Description: </h6>The schema definition for a composite cheat sheet content file. A composite cheat sheet consists of a set of tasks organized into task groups. Each task can be a simple cheat sheet or a user contributed task kind.</p>
-<p><h6 class=CaptionFigColumn id=header>Configuration Markup:</h6></p>
-<p class=code id=dtd>&lt;!ELEMENT <a name="e.compositeCheatsheet">compositeCheatsheet</a> (<a href="#e.taskGroup">taskGroup</a> | <a href="#e.task">task</a>)&gt;</p>
-<p class=code id=dtd>&lt;!ATTLIST compositeCheatsheet</p>
-<p class=code id=dtdAttlist>name&nbsp;CDATA #REQUIRED&gt;</p>
-<p></p>
-<p class=ConfigMarkup id=elementDesc>
-The root element of a composite cheatsheet</p>
-<br>
-<ul class=ConfigMarkup id=attlistDesc>
-<li><b>name</b> - The name of the composite cheat sheet which will be displayed in large font when the composite cheat sheet is opened.</li>
-</ul>
-<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.taskGroup">taskGroup</a> ((<a href="#e.task">task</a> | <a href="#e.taskGroup">taskGroup</a>) , <a href="#e.intro">intro</a>? , <a href="#e.onCompletion">onCompletion</a>? , <a href="#e.dependency">dependency</a>*)&gt;</p>
-<p class=code id=dtd>&lt;!ATTLIST taskGroup</p>
-<p class=code id=dtdAttlist>kind&nbsp;CDATA "set"<p class=code id=dtdAttlist>name&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class=code id=dtdAttlist>skip&nbsp;(true | false) "false"&gt;</p>
-<p></p>
-<p class=ConfigMarkup id=elementDesc>
-A task group represents a collection of related tasks. If the kind is "choice" only one of the child tasks need to be completed. If the kind is "set" or "sequence" all children must be completed.</p>
-<br>
-<ul class=ConfigMarkup id=attlistDesc>
-<li><b>kind</b> - The kind of this task group which can be "set", "sequence" or "choice". If the kind is set or sequence this task group is complete when all of its child tasks/task groups have been completed. In addition the subtasks of a sequence must be completed in order. A choice is complete when any of its subtasks has been completed.</li>
-<li><b>name</b> - The name of this task group which will be displayed in the task explorer.</li>
-<li><b>id</b> - An id for this task group which is required if this task group is referenced by a dependency element.</li>
-<li><b>skip</b> - If true this group of tasks may be skipped.</li>
-</ul>
-<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.task">task</a> (<a href="#e.intro">intro</a>? , <a href="#e.onCompletion">onCompletion</a>? , <a href="#e.param">param</a>* , <a href="#e.dependency">dependency</a>*)&gt;</p>
-<p class=code id=dtd>&lt;!ATTLIST task</p>
-<p class=code id=dtdAttlist>kind&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>name&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class=code id=dtdAttlist>skip&nbsp;(true | false) "false"&gt;</p>
-<p></p>
-<p class=ConfigMarkup id=elementDesc>
-A leaf task within a composite cheat sheet. A task does not have children, but it does have a task editor which shows in the lower/right hand pane of the cheat sheet view. The task kind determines which task editor will be opened, a task kind of "cheatsheet" represents a simple cheatsheet. Other task kinds may be contributed.</p>
-<br>
-<ul class=ConfigMarkup id=attlistDesc>
-<li><b>kind</b> - The task kind. A task kind of "cheatsheet" represents a simple cheatsheet, other task kinds can be contributed using the extension point org.eclipse.ui.cheatsheets.cheatSheetContent.</li>
-<li><b>name</b> - The name of this task which will be displayed in the task explorer.</li>
-<li><b>id</b> - An id for this task group which is required if this task group is referenced by a dependency element.</li>
-<li><b>skip</b> - If true this task may be skipped.</li>
-</ul>
-<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.param">param</a> EMPTY&gt;</p>
-<p class=code id=dtd>&lt;!ATTLIST param</p>
-<p class=code id=dtdAttlist>name&nbsp;&nbsp;CDATA #REQUIRED<p class=code id=dtdAttlist>value&nbsp;CDATA #REQUIRED&gt;</p>
-<p></p>
-<p class=ConfigMarkup id=elementDesc>
-A parameter to a task within a composite cheatsheet. Each parameter has a name and value, both of which are strings. A task may have any number of parameters, two parameters for a single task may not share the same name.</p>
-<br>
-<ul class=ConfigMarkup id=attlistDesc>
-<li><b>name</b> - The name of this parameter.</li>
-<li><b>value</b> - The value of this parameter.</li>
-</ul>
-<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.intro">intro</a> (#PCDATA)&gt;</p>
-<p></p>
-<p class=ConfigMarkup id=elementDesc>
-Contains the text which will be displayed before this task has been started. May contain form text markup.</p>
-<br><br>
-<p class=code id=dtd>&lt;!ELEMENT <a name="e.onCompletion">onCompletion</a> (#PCDATA)&gt;</p>
-<p></p>
-<p class=ConfigMarkup id=elementDesc>
-Contains the text which will be displayed in the completion panel for this task. May contain form text markup.</p>
-<br><br>
-<p class=code id=dtd>&lt;!ELEMENT <a name="e.dependency">dependency</a> EMPTY&gt;</p>
-<p class=code id=dtd>&lt;!ATTLIST dependency</p>
-<p class=code id=dtdAttlist>task&nbsp;CDATA #REQUIRED&gt;</p>
-<p></p>
-<p class=ConfigMarkup id=elementDesc>
-Creates a dependency between two tasks or subtasks.</p>
-<br>
-<ul class=ConfigMarkup id=attlistDesc>
-<li><b>task</b> - The id of the task or task group which must be completed before this task can be started.</li>
-</ul>
-<br><br>
-<p class=note id=copyright>
-Copyright (c) 2006 IBM Corporation and others.
-<p></p>
-
-</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_simple.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_simple.htm
deleted file mode 100644
index d866daf..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_simple.htm
+++ /dev/null

@@ -1,230 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Cheat sheets</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>
-Cheat sheets</h3>
-<P >
-Cheat sheets are special views that help guide the user through a series of complex tasks to achieve
-an overall goal.  For example, a cheat sheet could be used to help guide the user through all the steps needed to
-create, compile, and run a simple Java program.  Cheat sheets are launched from the <b>Help&gt;Cheat Sheets...</b>
-menu item.  Cheat sheets can also be launched from an intro page.  
-</p>
-<p>Cheat sheets are defined using the
-<b><a href="../reference/extension-points/org_eclipse_ui_cheatsheets_cheatSheetContent.html">org.eclipse.ui.cheatsheets.cheatSheetContent</a></b>
-extension point.  The cheat sheet content itself is defined in a separate file so that it can be more easily
-translated into other languages.
-</P>
-<h4>
-Contributing a cheat sheet</h4>
-<p>Contributing a cheat sheet is pretty straightforward.  Let's look at a cheat sheet contributed by the
-JDT for building a simple Java application.
-</p>
-<pre>
-&lt;extension point="org.eclipse.ui.cheatsheets.cheatSheetContent"&gt;
-	&lt;cheatsheet
-		name="%cheatsheet.helloworld.name"
-		contentFile="$nl$/cheatsheets/HelloWorld.xml"
-		id="org.eclipse.jdt.helloworld"&gt;
-		&lt;description>%cheatsheet.helloworld.desc&lt;/description&gt;
-	&lt;/cheatsheet>
-	...
-</pre>
-Much like other workbench contributions, a name, description, and id can be specified for the cheat
-sheet.  The name and description are shown when the user accesses the
-<b>Help&gt;Cheat Sheets...</b> list.  A category for the cheat sheet can also be defined if you want 
-to place several cheat sheets into a logical grouping.  If no category is specified, the cheat sheet will
-appear in the <b>Other</b> category.
-<p align="center"><img border="0" src="images/cheatsheets.png" alt="Cheat sheet dialog"></p>
-<h4>Cheat sheet items</h4>
-<p>
-The real work for cheat sheets is done in the content file.  The content file is an XML file whose name and location
-are specified in the <b>contentFile</b> attribute.  The path for the file is relative to the plug-in's directory.  (Note
-the use of the <tt>$nl$</tt> variable in the directory name, which means the file will be located in a directory specific
-to the national language of the target environment.)
-</p>
-<p>The file format itself includes overview information about the cheat sheet followed
-by a description of each step (called an <i>item</i>) that
-the user will perform.  At its simplest, an item is just a detailed description of the step that the user should
-take.  However, an item can also specify an action that can be run to perform the step on behalf of the
-user.  Let's look at the first part of the content file (<tt>HelloWorld.xml</tt>) 
-for the Java cheat sheet.
-</p>
-<pre>
-&lt;?xml version="1.0" encoding="UTF-8" ?&gt; 
-&lt;cheatsheet title="Simple Java Application"&gt;
-	&lt;intro 
-		href="/org.eclipse.ui.cheatsheets.doc/tasks/tcheatst.htm"&gt;
-		&lt;description&gt;
-Welcome to the Hello, World Java tutorial.
-It will help you build the famous "hello world" application and try it out. You will create a java project, and a java class that will print "hello world" in the console when run.
-Let's get started!
-		&lt;/description&gt;
-&lt;/intro&gt;
-	&lt;item
-		href="/org.eclipse.platform.doc.user/concepts/concepts-4.htm"
-		title="Open the Java Perspective"&gt;
-		<b>&lt;action
-			pluginId="org.eclipse.ui.cheatsheets"
-			class="org.eclipse.ui.internal.cheatsheets.actions.OpenPerspective"
-			param1="org.eclipse.jdt.ui.JavaPerspective"/&gt;</b>
-		&lt;description&gt;
-Select Window-&gt;Open Perspective-&gt;Java in the menu bar at the top of the workbench.
-This step changes the perspective to set up the Eclipse workbench for Java development.
-You can click the "Click to Perform" button to have the "Java" perspective opened automatically.
-		&lt;/description&gt;
-&lt;/item&gt;
-...
-</pre>
-<p align="center">
-<img border="0" src="images/javacheatsheet.png" alt="Simple java cheat sheet">
-</p>
-<p>
-The title and intro information are shown at the top of the cheat sheet.  Then, the items are described. 
-The first item for this cheat sheet describes how to open the Java perspective.  Better still, the <b>action</b>
-attribute specifies a class that can be used to run the action on behalf of the user.  The class must
-implement <a href="../reference/api/org/eclipse/jface/action/IAction.html"><b>IAction</b></a>.  This is rather
-convenient, as it allows you to reuse the action classes written for menu or toolbar contributions.
-</p>
-<p>
-The class for the action can optionally implement 
-<a href="../reference/api/org/eclipse/ui/cheatsheets/ICheatSheetAction.html"><b>ICheatSheetAction</b></a>
-if the action uses parameters or needs to be aware of the cheat sheet and its state.  In this case, the action
-will be passed an array of parameters and a reference to the 
-<a href="../reference/api/org/eclipse/ui/cheatsheets/ICheatSheetManager.html"><b>ICheatSheetManager</b></a>
-so that it can request additional information about the cheat sheet. 
-Any necessary parameters can be passed to the action's run method using the <b>param<i>N</i></b> attributes.
-</p>
-<p>
-It is strongly recommended that actions invoked from cheat sheets report a success/fail outcome if running the
-action might fail.  (For example, the user might cancel the action from its dialog.)  See 
-<b><a href="../reference/api/org/eclipse/jface/action/IAction.html">IAction</a>.notifyResult(boolean)</b> for
-more detail.
-</p>
-<p>
-Items do not have to define actions.  If your item must be performed manually by the user, you need not
-specify an action at all.  Below is the third step of the Java cheat sheet, which merely
-tells the user how to code the simple application.  When no action is specified, the item description
-must instruct the user to press the appropriate button after the task has been completed.
-</p>
-<pre>
-&lt;item
-	href="/org.eclipse.jdt.doc.user/tasks/tasks-54.htm"
-	title="Add a System.out.println line in your main method"&gt;
-	&lt;description&gt;
-Now that you have your HelloWorld class,
-In the "public static void main" method, add the following statement:  System.out.println("Hello world!"); and save your changes.  Press the "click when done" button below when finished.
-	&lt;/description&gt;
-&lt;/item&gt;
-</pre>
-Additional attributes control whether the item can be skipped completely and what document should be
-launched if the user requests help during the step.  See the 
-<b><a href="../reference/extension-points/org_eclipse_ui_cheatsheets_cheatSheetContent.html">org.eclipse.ui.cheatsheets.cheatSheetContent</a></b>
-extension point documentation for a description of all of the attributes that can be defined inside
-a cheat sheet.
-<h5>Subitems</h5>
-<p>
-Subitems may be defined to further organize the presentation of an item.  Unlike items, subitems do not have to
-be visited in any particular order.  Subitems may also define actions that automatically perform the subtask for
-the user.  Subitem actions are described in the same way as item actions. 
-</p>
-<h5>Conditional expressions and cheat sheet variables</h5>
-<p>
-Conditional expressions can be used to define cheat sheet elements whose content or behavior depends upon a
-particular condition being true.  Conditions are described in the <b>condition</b> element of a subitem
-using arbitrary string values that are matched
-against the <b>when</b> attribute for each choice.  Conditions typically reference cheat sheet
-variables using the form  <tt>${<i>var</i>}</tt>, where <i>var</i> refers to the name of a cheet sheet variable.
-A few simple examples will help demonstrate how conditional expressions work.
-</p>
-<p>
-<b>Conditional subitems</b> can be used to chose one subitem from a list of possible subitems.
-Only the first subitem whose <b>when</b> attribute matches the condition attribute is included in the
-cheat sheet.  For example:
-</p>
-<pre>
-&lt;item ...&gt;
-	&lt;conditional-subitem condition="${v1}"&gt;
-		&lt;subitem when="a" label="Step for A." /&gt;
-		&lt;subitem when="b" label="Step for B." /&gt;
-	&lt;/conditional-subitem&gt;
-&lt;/item&gt;
-</pre>
-This item specifies two possible subitems that depend on the value of the variable <tt>v1</tt>.
-If the variable value is <tt>a</tt>, then the first subitem will be included.  If the variable value
-is <tt>b</tt>, then the second subitem will be included.  If the variable is neither value, it is considered
-an error.
-<p>
-<b>Conditional actions</b> are similar to conditional subitems.  The <b>perform-when</b> element specifies
-a condition for performing one action among a list of possible actions.  The condition is described the same way,
-using an arbitrary string that often references a variable.  The action whose <b>when</b> attribute
-matches the condition is the one that will be performed.   For example:
-</p>
-<pre>
-&lt;item ...&gt;
-	&lt;perform-when condition="${v1}"&gt;
-		&lt;action when="a" class="com.example.actionA" pluginId-"com.example" /&gt;
-		&lt;action when="b" class="com.example.actionB" pluginId-"com.example" /&gt;
-	&lt;/perform-when&gt;
-&lt;/item&gt;
-</pre>
-The action to be performed is chosen based on the value of the <tt>v1</tt> variable.  If the variable
-value is neither <tt>a</tt> or <tt>b</tt>, it is considered an error.
-<h5>Repeated subitems</h5>
-<p>Repeated subitems describe a subitem that can can expand into 0, 1, or more similar substeps.  The
-substeps are individualized using the special variable <tt>${this}</tt>.  This variable will be replaced by
-the values specified in the <b>values</b> attribute.  The values attribute is a string of values that are separated
-by commas.  A variable that expands into a list of values may be used in the values attribute.
-For example:
-</p>
-<pre>&lt;item ...&gt;
-	&lt;repeated-subitem values="${v1}"&gt;
-		&lt;subitem label="Step ${this}" /&gt;
-	&lt;/repeated-subitem&gt;
-&lt;/item&gt;
-</pre>
-If the value of the variable is <tt>1,b,three</tt>, then three subitems will appear in the cheat sheet, each
-having a unique label ("Step 1," "Step b," "Step three").  The variable can be used in the label or the
-action paramater value.  It can also be accessed from the 
-<a href="../reference/api/org/eclipse/ui/cheatsheets/ICheatSheetManager.html"><b>ICheatSheetManager</b></a>
-while the action is executing.
-<h4>
-Cheat sheet listeners</h4>
-<p>
-In some cases, you may want to change other parts of your UI if a cheat sheet is active.
-For example, you may have an editor that shows special annotations if a cheat sheet is guiding the
-user through an editing task.  In this case, a <b>listener</b> can be specified as an attribute of
-the cheatsheet.  The listener attribute must be the fully qualified name of a Java class that
-subclasses
-<a href="../reference/api/org/eclipse/ui/cheatsheets/CheatSheetListener.html"><b>CheatSheetListener</b></a>.  
-Listeners will receive notifications along with an 
-<a href="../reference/api/org/eclipse/ui/cheatsheets/ICheatSheetEvent.html"><b>ICheatSheetEvent</b></a> when there
-is a change in the cheat sheet's life cycle, such as when it opens, closes, or completes.  
-</p>
-<h4>
-Contributing attributes to an existing cheat sheet</h4>
-<p>
-The <b><a href="../reference/extension-points/org_eclipse_ui_cheatsheets_cheatSheetItemExtension.html">org.eclipse.ui.cheatsheets.cheatSheetItemExtension</a></b>
-extension can be used to contribute arbitrary attributes to a pre-existing cheat sheet.  
-The purpose of this extension point is to allow a plug-in to add additional buttons that will
-aid the user for a given step.  These additional buttons are displayed beside the help icon.  </p>
-<p>To use this mechanism, you can
-define any arbitrary attribute inside an item definition in the cheat sheet XML file.  The attribute name will be matched against any
-attributes contributed in extensions to <b><a href="../reference/extension-points/org_eclipse_ui_cheatsheets_cheatSheetItemExtension.html">org.eclipse.ui.cheatsheets.cheatSheetItemExtension</a></b>.
-See the extension point documentation for more detail.
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic.htm
deleted file mode 100644
index 0c1306e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic.htm
+++ /dev/null

@@ -1,106 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
-<meta content="text/css" http-equiv="Content-Style-Type">
-<link type="text/css" charset="ISO-8859-1" href="../book.css" rel="STYLESHEET">
-<link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-
-<body bgcolor="#ffffff">
-
-<h2>Dynamic content</h2>
-
-<p><b>What is dynamic content?</b></p>
-
-<p>
-Several user assistance components allow you to provide dynamic content. This
-means the content can change depending on the user's environment or context. For
-example, you may want a section of your help document or welcome page to only
-appear if the user has a certain functionality enabled.
-</p>
-
-<p>
-There are two basic ways to create dynamic content. One is to add tags and attributes
-(annotations) to your XML markup instructing the system to filter out sections or
-documents, include sections from other documents, or specify anchors allowing
-other components to extend your documentation.
-</p>
-
-<p>
-The other method is to write your own content producer by plugging in some
-Java code that will write the content from scratch or process existing static
-documents on-the-fly. Let's examine both approaches.
-</p>
-
-<p><b>XML Annotations</b></p>
-
-The simplest way to create dynamic content is to use the XML markup annotations.
-You simply add some special attributes and tags to your XML markup and the system
-will process the instructions. You can use this markup to:
-
-<ul>
-<li><a href="ua_dynamic_filters.htm">Filter</a> out documents or parts of documents</li>
-<li><a href="ua_dynamic_includes.htm">Include</a> sections from other documents, and</li>
-<li>Specify <a href="ua_dynamic_anchors.htm">anchors</a> where other components can extend your documents</li>
-</ul>
-
-<p>
-To learn more about each aspect of the markup, follow the links above or find the
-topics in the table of contents.
-</p>
-
-<p>
-This is demonstrated in the XHTML fragment shown below:
-</p>
-
-<p>
-<hr>
-<pre>
-
-&lt;p&gt;
-This is a static paragraph.
-&lt;/p&gt;
-
-&lt;!-- This tag will be replaced with the referenced tag --&gt;
-<font color="blue">&lt;include path="my.plugin.id/path/my_other_document.xhtml/element_id"/&gt;</font>
-
-&lt;ul&gt;
-   &lt;li&gt;
-      This is a static list item.
-   &lt;/li&gt;
-   &lt;li <font color="blue">filter="os=win32"</font>&gt;
-      This only shows when running on Windows.
-   &lt;/li&gt;
-   &lt;li <font color="blue">filter="plugin!=org.eclipse.help"</font>&gt;
-      This only shows when plugin org.eclipse.help is NOT installed.
-   &lt;/li&gt;
-&lt;/ul&gt;
-
-&lt;!-- A place where others can add content --&gt;
-<font color="blue">&lt;anchor id="my.anchor.id"/&gt;</font>
-
-</pre>
-<hr>
-</p>
-
-<p><b>Content producers</b></p>
-
-<p>
-A content producer is a mechanism for plugging-in Java code to produce the document
-content on-the-fly. Content producers are more powerful than XML annotations, but
-are more complex to use.
-</p>
-
-<p>
-Content producers are supported in the following areas of user assistance:
-</p>
-
-<ul>
-   <li><a href="ua_intro_xhtml.htm">Welcome XHTML</a></li>
-   <li><a href="ua_help_dynamic.htm">Help Documents (any format)</a></li>
-   <li><a href="ua_help_context_dynamic.htm">Context-sensitive help</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_anchors.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_anchors.htm
deleted file mode 100644
index 551582d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_anchors.htm
+++ /dev/null

@@ -1,66 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
-<meta name=copyright content="Copyright (c) IBM Corporation and others 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-</head>
-
-<body bgcolor="white">
-
-<h3>Anchors</h3>
-
-<p>
-Anchors can be thought of as the extension point equivalent for user assistance
-documents. The same way components use extension points to allow other components
-to extend their functionality, documents can use anchors to allow other components
-to extend their user assistance content.
-</p>
-
-<p>
-Let's say component A's documentation provides a listing of file formats it
-supports. If component B extends A's support to several more formats,
-you can place an anchor in A's list, and extend the list from B. For example:
-</p>
-
-<pre>
-   &lt;p&gt;The following list shows the supported formats:&lt;/p&gt;
-   &lt;ul&gt;
-      &lt;li&gt;Portable Network Graphics (.png)&lt;/li&gt;
-      &lt;li&gt;Joint Photographic Experts Group (.jpeg)&lt;/li&gt;
-      &lt;li&gt;Graphical Interchange Format (.gif)&lt;/li&gt;
-      
-      &lt;!-- Extra formats go here --&gt;
-      <font color="blue">&lt;anchor id="image_format_list"/&gt;</font>
-   &lt;/ul&gt;
-</pre>
-
-Then component be can make a contribution to the anchor to add more formats
-to the list.
-
-<p><b>How do I contribute content into an anchor?</b></p>
-
-<p>
-This depends on the type of document. Generally you define an extension that
-points to an XML file containing the content to be added. Follow the links
-in the section below to learn how to do it in the document type you're using:
-</p>
-
-<p><b>Where can I use anchors?</b></p>
-
-<p>
-See below for a list of the document types in which includes can be used. The
-format of the <code>path</code> element of the include <i>depends on the type of
-document you're including from</i>. As you can see in the example above,
-the format for XHTML help documents is
-"&lt;plugin_id&gt;/&lt;path_to_file&gt;/&lt;element_id&gt;". Refer to the links
-below for the format for your document type.
-</p>
-
-<ul>
-   <li><a href="ua_intro_define_content.htm">Welcome/Intro XML</a></li>
-   <li><a href="ua_intro_xhtml.htm">Welcome/Intro XHTML</a></li>
-   <li><a href="ua_help_content_xhtml.htm">Help XHTML</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_filters.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_filters.htm
deleted file mode 100644
index c6bfdd1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_filters.htm
+++ /dev/null

@@ -1,228 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
-<meta name=copyright content="Copyright (c) IBM Corporation and others 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-</head>
-
-<body bgcolor="white">
-
-<h3>Filters</h3>
-
-<p>If certain sections of your document should only appear within a specific
-context, you can use filtering markup to specify criteria that must be
-met in order for the section of the document to appear. If the criteria are not
-met, that section of the document will not be visible to the user. Filters can
-be specified on <i>any</i> XML element as long as the markup will still be valid
-after processing. If an element is filtered, all elements and text contained under
-that element will also be filtered.</p>
-
-<p>The table below contains a complete list of all the filter properties and
-their possible values.</p>
-
-<table border="1">
-   <tr>
-      <td>
-         <b>Property</b>
-      </td>
-      <td>
-         <b>Meaning</b>
-      </td>
-      <td>
-         <b>Possible Values</b>
-      </td>
-   </tr>
-   <tr>
-      <td>
-         <code>os</code>
-      </td>
-      <td>
-         operating system
-      </td>
-      <td>
-         <code>win32, win32, linux, macosx, aix, solaris, hpux, qnx</code>
-      </td>
-   </tr>
-   <tr>
-      <td>
-         <code>ws</code>
-      </td>
-      <td>
-         windowing system
-      </td>
-      <td>
-         <code>win32, motif, gtk, photon, carbon</code>
-      </td>
-   </tr>
-   <tr>
-      <td>
-         <code>arch</code>
-      </td>
-      <td>
-         processor architecture
-      </td>
-      <td>
-         <code>x86, x86_64, ia64, ia64_32, ppc, PA_RISC, sparc</code>
-      </td>
-   </tr>
-   <tr>
-      <td>
-         <code>product</code>
-      </td>
-      <td>
-         eclipse product identifier
-      </td>
-      <td>
-         Any product identifier (e.g., for SDK, <code>org.eclipse.sdk.ide</code>)
-      </td>
-   </tr>
-   <tr>
-      <td>
-         <code>plugin</code>
-      </td>
-      <td>
-         plug-in presence
-      </td>
-      <td>
-         Any plug-in identifier (e.g. <code>org.eclipse.help</code>)
-      </td>
-   </tr>
-   <tr>
-      <td>
-         <code>category</code>
-      </td>
-      <td>
-         category of activities
-      </td>
-      <td>
-         Any activity category identifier (e.g. for Team category,
-         <code>org.eclipse.categories.teamCategory</code>)
-      </td>
-   </tr>
-   <tr>
-      <td>
-         <code>activity</code>
-      </td>
-      <td>
-         activity (capability)
-      </td>
-      <td>
-         Any activity identifier (e.g. for CVS Support activity, 
-         <code>org.eclipse.team.cvs</code>)
-      </td>
-   </tr>
-</table>
-
-<p>If the name does not match any pre-defined property, the help system will
-use the JVM's system property of that name. For example, you can pass in any
-user-defined property at launch, such as <code>-Dlocation=paris,france</code>
-and filter by that property.</p>
-
-<p>There are two ways to specify filters on an element; using attributes, or
-elements.</p>
-
-<p><b>Filter Attribute</b></p>
-
-<p>The first form is to add a <font color="blue"><code>filter</code></font> attribute
-to the element. The general form is:</p>
-
-<pre>
-   &lt;element <font color="blue">filter="[name][operator][value]"</font>&gt;
-      Some text.
-   &lt;/element&gt;
-</pre>
-
-<p>The <font color="blue"><code>name</code></font> is the name of the property
-by which to filter, for example, <code>os</code> for operating system. The
-<font color="blue"><code>operator</code></font> is either <code>=</code> to denote
-a <i>match</i> (exact match, case sensitive), or <code>!=</code> to denote <i>does
-not match</i>. The <font color="blue"><code>value</code></font> is what the property
-should (or shouldn't) match. For example, for <code>os</code>, one of the possible
-values is <code>win32</code> (Windows). A complete list of filter properties and their
-values is available in a table below.</p>
-
-<p>The example below shows how to display a paragraph of text in an XHTML document
-when running on Linux only.</p>
-
-<pre>
-   &lt;p filter="os=linux"&gt;
-      This message will only appear when viewed on Linux.
-   &lt;/p&gt;
-</pre>
-
-<p>In this second example, the link will only appear when plugin
-<code>com.my.plugin</code> is not installed:</p>
-
-<pre>
-   &lt;a href="..." filter="plugin!=com.my.plugin"&gt;
-      Click here to download plugin com.my.plugin.
-   &lt;/a&gt;
-</pre>
-
-<p><b>Filter Element</b></p>
-
-<p>The second form is to use a <code>filter</code> element as a <i>child</i> of
-the element you wish to filter. This form is slightly longer than the attribute
-form, but it is more powerful because you can specify any number of filters on an
-element. The general form is:</p>
-
-<pre>
-   &lt;element attribute="value"&gt;
-      <font color="blue"><code>&lt;filter name="[name]" value="[modifier][value]"/&gt;</code></font>
-   &lt;/element&gt;
-</pre>
-
-<p>The <font color="blue"><code>name</code></font> and <font color="blue"><code>
-value</code></font> here are the same as with the attribute. However, since they
-are separated, we need another way to specify whether or not it should match. By
-default, if you do not provide a <font color="blue"><code>modifier</code></font>,
-match is assumed. If it should <i>not</i> match, set the modifier to "<code>!</code>
-"</p>
-
-<p>Here is the first example shown above in the second form:</p>
-
-<pre>
-   &lt;p&gt;
-      &lt;filter name="os" value="linux"/&gt;
-      This message will only appear when viewed on Linux.
-   &lt;/p&gt;
-</pre>
-
-<p>And the second example:</p>
-
-<pre>
-   &lt;a href="..."&gt;
-      &lt;filter name="plugin" value="!com.my.plugin"/&gt;
-      Click here to download plugin com.my.plugin.
-   &lt;/a&gt;
-</pre>
-
-<p><b>Where can I use filters?</b></p>
-
-<p>
-Filtering can be used in the following types of documents:
-</p>
-
-<ul>
-   <li><a href="ua_intro_define_content.htm">Welcome XML</a></li>
-   <li><a href="ua_intro_xhtml.htm">Welcome XHTML</a></li>
-   <li><a href="ua_help_content.htm">Help XHTML</a>*</li>
-   <li><a href="ua_help_content_toc.htm">Help table of contents</a></li>
-   <li><a href="ua_help_context_xml.htm">Help topics in context-help</a></li>
-</ul>
-
-<p>
-* Note: There are a few <a href="ua_help_content_xhtml.htm">extra steps</a> required
-to enable dynamic content in your XHTML documents.
-</p>
-
-<p>
-In any case, you <b>must not</b> place filters on any element where removing that
-element would result in <i>invalid</i> XML. For example, you should not place a
-filter on the <code>html</code> element in XHTML, because without that element it
-is no longer valid
-XHTML.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_includes.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_includes.htm
deleted file mode 100644
index 9980a89..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_includes.htm
+++ /dev/null

@@ -1,70 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
-<meta name=copyright content="Copyright (c) IBM Corporation and others 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-</head>
-
-<body bgcolor="white">
-
-<h3>Includes</h3>
-
-<p>
-Includes are used include parts of other documents into your document. The
-markup specifies the document and element to include, and before the document is
-shown to the user, the include element will be <i>replaced</i> with the element
-referred to.
-</p>
-
-<p>
-For example, you may wish to show a copyright at the end of each help document
-you provide. You could copy and paste it in each document, but if the copyright
-changes (e.g. the copyright year), you have to modify <i>every</i> one of your
-documents.
-</p>
-
-<p>
-Instead, you can place the copyright in a separate XHTML file called <code>
-copyright.xhtml</code> and assign it a unique identifier, like this:
-</p>
-
-<pre>
-   &lt;p <font color="blue">id="copyright"</font>&gt;
-      Copyright 2006 My Company. All rights reserved.
-   &lt;/p&gt;
-</pre>
-
-<p>
-Then for each document, simply include the copyright paragraph:
-</p>
-
-<pre>
-   &lt;p&gt;
-      This is my document. It should have a copyright at the end.
-   &lt;/p&gt;
-   <font color="blue">&lt;include path="my.plugin.id/path/copyright.xhtml/copyright"/&gt;</font>
-</pre>
-
-<p>
-Before the document is sent to the browser to be displayed, the <code>include</code>
-element will be <i>replaced</i> by the copyright paragraph.
-</p>
-
-<p><b>Where can I use includes?</b></p>
-
-<p>
-See below for a list of the document types in which includes can be used. The
-format of the <code>path</code> element of the include <i>depends on the type of
-document you're including from</i>. As you can see in the example above,
-the format for XHTML help documents is <code>
-"&lt;plugin_id&gt;/&lt;path_to_file&gt;/&lt;element_id&gt;"</code>. Refer to the links
-below for the format for your document type.
-</p>
-
-<ul>
-   <li><a href="ua_intro_xhtml.htm">Welcome/Intro XML/XHTML format</a></li>
-   <li><a href="ua_help_content_xhtml.htm#include_format">Help XHTML format</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help.htm
deleted file mode 100644
index 5d3519b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Plugging in help
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h2>Plugging in help</h2>
-<P >
-The Eclipse platform's help facilities provide you with the raw building blocks to structure and contribute
-documentation to the platform. It does not dictate structure or granularity of documentation.
-You can choose the tools and structure for your documentation that suits your
-needs.&nbsp; The help plug-in allows you to describe your documentation
-structure to the platform using a table of contents (toc) file.</P>
-<P >Your plug-in's online help is contributed using the <a href="../reference/extension-points/org_eclipse_help_toc.html"> <b> org.eclipse.help.toc</b></a> extension point. You can either contribute the online help as part of your code plug-in or provide it separately in its own documentation plug-in.</P>
-<P >
-Separating the documentation into a separate plug-in is beneficial in those situations where the code and documentation teams are different groups or where you want to reduce the coupling between the documentation and code. </P>
-<P >
-Advanced features of the help system include context-sensitive help with
-reference links and the ability to invoke platform
-code from the documentation.&nbsp;A help browser lets you view, print, and 
-search your documentation. Since 3.1, the new Help view adds dynamic help and 
-federated information search capability.</P>
-<P >
-The best way to demonstrate the contribution of help is to create a
-documentation plug-in.</P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content.htm
deleted file mode 100644
index 50dd7c9..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Building a help plug-in
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Building a help plug-in</h3>
-<P >
-In this example, we assume that a documentation author has already supplied you with the raw documentation in the form of HTML files. The granularity
-and structure of these files is completely up to the documentation team. Once the documentation is delivered, setting up the plug-in and topics can be done independently.</P>
-
-<P >
-We start by assuming that the documentation has already been provided in the following tree.</P>
-<pre>
-   html/
-      concepts/
-         concept1.html
-         concept1_1.html
-         concept1_2.html
-      tasks/
-         task1.html
-         task2.html
-         task3_1.html
-         task3_2.html
-      ref/
-         ref1.html
-         ref2.html
-</pre>
-<P >
-We will assume that the plug-in name is <b>com.example.helpexample</b>.</P>
-<P >
-The first step is to create a plug-in directory, <b>com.example.helpexample</b> underneath the platform
-<b>plugins</b> directory. The <b>doc\</b>
-sub tree shown above should be copied into the directory. </P>
-<P >
-Documentation plug-ins need a manifest just like code plug-ins. The following markup defines the documentation plug-in.</P>
-
-<pre>
-   &lt;?xml version=&quot;1.0&quot; ?&gt;
-   &lt;plugin name=&quot;Online Help Sample&quot;
-      id=&quot;com.example.helpexample&quot;
-      version=&quot;1.0&quot;
-      provider-name=&quot;MyExample&quot; /&gt;
-</pre>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active.htm
deleted file mode 100644
index 11c4e92..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Active help
-</TITLE>
-<script language="JavaScript" src="../../org.eclipse.help/livehelp.js"> </script>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<body bgcolor="white">
-
-<h3>Active help</h3>
-
-<p>Active help is the ability to invoke Eclipse code from on-line
-documentation.&nbsp;It is implemented by including some JavaScript in your
-documentation that describes a class that should be run inside the Eclipse
-platform. </p>
-
-<p>For example, instead of writing, &quot;Go to the Window Menu and open the
-message dialog,&quot; your on-line help can include a link that will open your
-application's message dialog for the user.&nbsp; Active help links look like hyperlinks in
-the on-line help.</p>
-
-<p>Below is an active help link that opens a message dialog in the workbench.&nbsp;
-We will take a look at how to make this work.</p>
-
-<p><a href='javascript:liveAction(
-	"org.eclipse.platform.doc.isv", 
-	"org.eclipse.platform.doc.isv.activeHelp.ActiveHelpOpenDialogAction",
-	"")'>Click here for a Message.</a></p>
-
-<p>&nbsp;</p>
-
-
-</body>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_action.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_action.htm
deleted file mode 100644
index ac4f889..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_action.htm
+++ /dev/null

@@ -1,89 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Writing the help action</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Writing the help action</h3>
-
-
-<p>The interface <a href="../reference/api/org/eclipse/help/ILiveHelpAction.html"><b>ILiveHelpAction</b></a>
-is used to build an active help action.</p>
-
-
-<p>It is straightforward to implement an <a href="../reference/api/org/eclipse/help/ILiveHelpAction.html"><b>ILiveHelpAction</b></a><b>.</b>&nbsp;
-You must implement two methods.</p>
-
-
-<ul>
-  <li><b>run()</b> - This method is called to run the live help action.&nbsp;
-    This method will be called by the help system from a non-UI thread, so UI
-    access must be wrapped in a <b><a href="../reference/api/org/eclipse/swt/widgets/Display.html">Display.syncExec()</a></b>
-    method.&nbsp;&nbsp;</li>
-  <li><b>setInitializationString(String)</b> - This method is called to
-    initialize your action with a String data parameter you can specify in the
-    HTML which runs the JavaScript <b>liveAction</b>.&nbsp;&nbsp;
-If you don't need initialization data, you can just implement
-this method to do nothing.&nbsp; This method is called before <b>run()</b>.</li>
-</ul>
-
-
-<p>Here is a simple implementation of a live help action that opens a message
-dialog. We don't need any information from the JavaScript, so the
-initialization data is ignored.</p>
-
-
-<pre>package org.eclipse.platform.doc.isv.activeHelp;
-
-import org.eclipse.help.ILiveHelpAction;
-import org.eclipse.jface.dialogs.MessageDialog;
-import org.eclipse.swt.widgets.*;
-import org.eclipse.ui.*;
-/**
- * Sample Active Help action.
- */
-public class ActiveHelpOpenDialogAction implements ILiveHelpAction {
-
-     public void setInitializationString(String data) {
-          // ignore the data.  We do not use any javascript parameters.
-     }
-
-     public void run() {
-          // Active help does not run on the UI thread, so we must use syncExec
-          Display.getDefault().syncExec(new Runnable() {
-               public void run() {
-                    IWorkbenchWindow window =
-                         PlatformUI.getWorkbench().getActiveWorkbenchWindow();
-                    if (window != null) {
-                         // Bring the Workbench window to the top of other windows;
-                         // On some Windows systems, it will only flash the Workbench
-                         // icon on the task bar
-                         Shell shell = window.getShell();
-                         shell.setMinimized(false);
-                         shell.forceActive();
-                         // Open a message dialog
-                         MessageDialog.openInformation(
-                              window.getShell(),
-                              &quot;Hello World.&quot;,
-                              &quot;Hello World.&quot;);
-                    }
-               }
-          });
-     }
-}</pre>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_debug.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_debug.htm
deleted file mode 100644
index bf8cea3..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_debug.htm
+++ /dev/null

@@ -1,93 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Tips for debugging active help</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Tips for debugging active help</h3>
-
-
-<p>The code and markup that triggered our active help link looks pretty
-straightforward.&nbsp; But what do you do if your active help link doesn't seem
-to work?</p>
-
-
-<h4>Test your action ahead of time</h4>
-
-
-<p>If your action implementation is fairly involved, you should invoke the
-action yourself with some test code inside Eclipse.&nbsp; This way, you'll know
-that the action is error-free before invoking it from the JavaScript.&nbsp; </p>
-
-
-<h4>Ensure the JavaScript is running</h4>
-
-
-<p>You can modify &quot;plugins/org.eclipse.help_2.1.0/<b>liveHelp.js</b>&quot;
-to include a call to the <b>alert</b> function as the first statement in the <b>liveAction</b>
-function:</p>
-
-
-<pre>function liveAction(pluginId, className, argument)
-{
-<b>	alert(&quot;liveAction called&quot;);
-	...</b></pre>
-
-
-<p>The <b>alert</b> function opens a warning dialog in the browser and can be
-used to verify that the <b>liveAction</b> was properly invoked in your
-HTML.&nbsp; If you don't see a warning dialog when you click on your help link,
-then you have a problem in the HTML markup.</p>
-
-
-<h4>Debug the active help action</h4>
-
-
-<p>Once you know that the JavaScript is running, you can debug your action from
-inside Eclipse.&nbsp; To do this, you can set a breakpoint in your help action
-class and start up a self-hosted Eclipse instance.&nbsp; You must test your
-active help with the Help browser from the newly launched Eclipse instance, not
-from your host instance, since the JavaScript from your help HTML calls a
-servlet on the Eclipse help server that launched the browser.</p>
-
-
-<p>If nothing happens after you've set up the breakpoint and clicked on the
-active help link, it's likely that your plug-in and active help class were not
-correctly specified in the JavaScript.&nbsp; </p>
-
-
-<p>Once you've managed to stop at the breakpoint in your action, you can debug
-the action as you would any other Java code.</p>
-
-
-<h4>Make sure your UI code is wrapped in Display.syncExec</h4>
-
-
-<p>A common runtime problem is improperly accessing UI code from the thread that
-invokes the active help.&nbsp; If your live help action came from code that ran
-originally in a UI thread, it will need to be modified to handle the fact that
-it is running from a non-UI thread.&nbsp; </p>
-
-
-<pre>public void run() {
-		// Active help does not run on the UI thread, so we must use syncExec
-		Display.getDefault().syncExec(new Runnable() {
-							public void run() {
-								//do the UI work in here;
-							}
-		});		
-	}
-
-</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_invoke.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_invoke.htm
deleted file mode 100644
index 1906c60..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_invoke.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Invoking the action from HTML</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Invoking the action from HTML</h3>
-
-<P>
-To include active help links in your documentation, you must first declare the
-use of the supporting JavaScript code. The live help JavaScript is located in the <b>org.eclipse.help</b>
-plug-in.&nbsp; You refer to it using the help system's <a href="ua_help_content_files.htm#help_plugin_files_xref">cross
-plug-in referencing</a> technique. This script reference should be placed in the <b>HEAD</b> section of your HTML:
-</P>
-
-<pre >&lt;script language=&quot;JavaScript&quot; src=&quot;PLUGINS_ROOT/org.eclipse.help/livehelp.js&gt; &lt;/script&gt;</pre>
-
-<P >
- In the body of your documentation, you invoke the liveAction script.&nbsp;&nbsp; </P>
-
-
-<pre >&lt;a href='javascript:liveAction(
-	&quot;org.eclipse.platform.doc.isv&quot;, 
-	&quot;org.eclipse.platform.doc.isv.activeHelp.ActiveHelpOpenDialogAction&quot;,
-	&quot;&quot;)'&gt;Click here for a Message.&lt;/a&gt;</pre>
-
-
-<P >The parameters for <b>liveAction </b> are&nbsp; </P>
-
-
-<ul>
-  <li> the ID of the plug-in that
-contains the action</li>
-  <li>the name of the class that implements the action</li>
-  <li>the String that will be passed to the live help action using <b>setInitializationString</b>.&nbsp;
-    We don't need to pass any information from the HTML page, so we just
-    pass an empty string.</li>
-</ul>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command.htm
deleted file mode 100644
index afb340f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command.htm
+++ /dev/null

@@ -1,105 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Active help
-</TITLE>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<body bgcolor="white">
-
-<h3>Embedding Commands in Help</h3>
-
-<p>It is possible to create links to workbench commands in help content.  When
-the user clicks the link, the command will be executed.  This feature is similar
-to <a href="help_active.htm">Active Help</a> in that it uses JavaScript to bridge between the documentation
-HTML and the Eclipse Java runtime.  Also like Active Help, the command framework is extensible;
-so you can contribute new commands with interesting behaviors.
-However, unlike Active Help, there are a large number of useful commands already defined
-in the workbench and more are being added all the time.  This should be appealing to
-documentation authors because linking to an existing command does not require
-writing any Java code.
-</p>
-<p>
-Command links can be used to:
-<ul>
-<li>
-Open a specific preference page, such as
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Views)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png">
-<b>General &gt; Appearance</b></a>.
-</li>
-<li>
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png">
-Select a new perspective</a>
-or switch to a pre-determined perspective like the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.jdt.ui.JavaBrowsingPerspective)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png">
-<b>Java Browsing</b> perspective</a>.
-</li>
-<li>
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png">
-Select a view to open</a> or open a pre-determined view like the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.BookmarkView)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png">
-<b>Bookmarks</b> view</a>.
-</li>
-<li>
-Open wizards like the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.pde.ui.NewProjectWizard)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png">
-<b>New Plug-in Project</b> wizard</a> and the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export(exportWizardId=org.eclipse.ui.wizards.export.Preferences)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png">
-<b>Export Preferences</b> wizard</a>.
-</li>
-<li>
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.cheatsheets.openCheatSheet(cheatSheetId=org.eclipse.jdt.helloworld)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png">
-Open a Cheat Sheet</a>.
-</li>
-<li>
-Open a
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.dialogs.openMessageDialog(imageType=3,buttonLabel2=Maybe,title=Opinion Poll,message=Do you like command links?,buttonLabel0=Yes,defaultIndex=0,buttonLabel1=No)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png">
-message dialog</a>.
-</li>
-<li>
-Open the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.help.aboutAction")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png">
-<b>About Eclipse SDK</b> dialog</a>.
-</li>
-<li>
-And much more!
-</li>
-</ul>
-</p>
-
-<p>
-To get an idea of the range of commands available, look at the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Keys)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png">
-<b>General &gt; Keys</b> preference page</a>.  This page is used to bind key sequences to commands
-so it shows the list of available commands.  <i>Note that not every command will do something useful from
-help content.  Many commands are designed to work within a somewhat narrow context (like a particular view,
-or expecting a certain type of selection).</i>
-</p>
-
-<p>
-If you want to define your own commands, refer to the documentation for the
-<a href="../reference/api/org/eclipse/core/commands/package-summary.html"><tt>org.eclipse.core.commands</tt></a> API package
-and the <a href="../reference/extension-points/org_eclipse_ui_commands.html"><tt>org.eclipse.ui.commands</tt></a> and
-<a href="../reference/extension-points/org_eclipse_ui_handlers.html"><tt>org.eclipse.ui.handlers</tt></a> extension-points.
-</p>
-
-</body>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command_authoring.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command_authoring.htm
deleted file mode 100644
index b7743fe..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command_authoring.htm
+++ /dev/null

@@ -1,78 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Invoking the action from HTML</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Authoring a Command Link</h3>
-
-<P>
-To include command links in your documentation, you must first declare the
-use of the supporting JavaScript code. The live help JavaScript is located in the <b>org.eclipse.help</b>
-plug-in.&nbsp; You refer to it using the help system's <a href="ua_help_content_files.htm#help_plugin_files_xref">cross
-plug-in referencing</a> technique. This script reference should be placed in the <b>HEAD</b> section of your HTML:
-</P>
-
-<pre >&lt;script language=&quot;JavaScript&quot; src=&quot;PLUGINS_ROOT/org.eclipse.help/livehelp.js&gt; &lt;/script&gt;</pre>
-
-<P>
-Now in the body of your documentation you may invoke the <b>executeCommand</b> function.
-Here is an example:
-</P>
-
-<pre>&lt;a href='javascript:executeCommand("org.eclipse.ui.help.aboutAction")'&gt;
-Open the About dialog&lt;/a&gt;</pre>
-
-<P>
-The parameter for the <b>executeCommand</b> function is a serialized
-<a href="../reference/api/org/eclipse/core/commands/ParameterizedCommand.html">
-<b>ParameterizedCommand</b></a>.
-See the
-<a href="../reference/api/org/eclipse/core/commands/ParameterizedCommand.html#serialize()">
-<b>ParameterizedCommand.serialize()</b></a> method for full details on this format.
-</P>
-
-<P>
-The example above shows the bare minimum required to embed a command in an HTML link.
-The Eclipse documentation supplements this with two extra pieces of information.
-First a <tt>class</tt> attribute is specified to allow for tuning the look of the link
-via CSS.  Second, an image tag is included before the link text.  The image serves
-to distinguish command links from ordinary links to other HTML pages.  Supplementing
-our initial example with these two extra features will look like this:
-</P>
-
-<pre>&lt;a class="command-link" href='javascript:executeCommand("org.eclipse.ui.help.aboutAction")'&gt;
-&lt;img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"&gt;
-Open the About dialog&lt;/a&gt;</pre>
-
-<P>
-In the examples above, the About dialog command does not require any parameters, so the
-serialization is merely its command id: <tt>org.eclipse.ui.help.aboutAction</tt>.
-Below is another example showing a command with a parameter.  Note the command id is
-followed by the parameter id and value in parentheses:
-</P>
-
-<pre>&lt;a href='javascript:executeCommand(
-	"org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Views)")'&gt;
-	Show a preference page&lt;/a&gt;</pre>
-
-<P>
-Another example demonstrates that multiple parameters are possible.  They are comma
-separated and the order of the parameters is not important.
-</P>
-
-<pre>&lt;a href='javascript:executeCommand(
-	"org.eclipse.ui.dialogs.openMessageDialog(imageType=3,buttonLabel2=Maybe,title=Opinion Poll,message=Do you like command links?,buttonLabel0=Yes,defaultIndex=0,buttonLabel1=No)")'&gt;
-	Open a message dialog&lt;/a&gt;</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_files.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_files.htm
deleted file mode 100644
index a9bbac3..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_files.htm
+++ /dev/null

@@ -1,125 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Help server and file locations</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Help server and file locations</h3>
-<P >
-The platform utilizes its own documentation server to provide the actual web pages
-for your plug-in's documentation.&nbsp; A custom server allows the platform to handle HTML content
-in a browser independent manner and to provide plug-in aware support.&nbsp; The
-main difference to you as a plug-in developer is that you have a little more
-flexibility in the way you structure your files and specify your links. </P>
-<P >
-A documentation plug-in can run from a jar file or unpacked into plug-in directory
-during installation. A plug-in archive jar is not
- expanded into a plug-in directory when value of <code>unpack</code> attribute
- of the <code>plugin</code> element is specified as true in the <a href="../reference/misc/feature_manifest.html">feature
- manifest</a>. In such plug-in, the documentation is compressed in the plug-in's
-jar, together with other plug-in files. </P>
-<P >In plug-ins that run unpacked, the documentation can be delivered
-  in a zip file, avoiding problems that may result
-  when a large number of files
-  are
-  present
-  in a plug-in
-  directory.
-  In
-  our example
-plug-in, we created a sub-directory called <b>html</b>.&nbsp;
-Alternatively, we could have placed our html files into a zip file called
-<b>doc.zip</b>.&nbsp; This zip file must mimic the file
-structure underneath the plug-in directory.&nbsp; In our case, it must contain
-the sub-directory <b>html</b> and all the contents
-underneath <b>html</b>.</P>
-<P >Note that for plug-ins running from a jar, there is no need for documentation
-  to be additionally contained in doc.zip, and such set-up of doc.zip in an unexploded
-   plug-in jar
-is not supported by help system</P>
-<P >When resolving file names in a plug-in that runs unpacked, the help server
-  looks in the <b>doc.zip</b>
-file for documents before it looks in the plug-in directory itself.&nbsp; When
-used as a link, the argument in an
-<b> href</b> is assumed to be relative to the current plug-in.&nbsp; Consider
-the following link: </P>
-
-
-<pre>   &lt;topic label=&quot;Ref1&quot; href=&quot;html/ref/ref1.html&quot;/&gt;</pre>
-
-
-<P>The help plug-in will look for this file as follows: </P>
-
-
-<ul>
-  <li>look in <b> doc.zip</b> for the file <b>/html/ref/ref1.html</b></li>
-  <li>look for the file <b>ref1.html</b> in the <b>/html/ref </b>sub-directory structure underneath the plug-in
-    directory.</li>
-</ul>
-<P >A fully qualified link can be used to refer to any content on the web.&nbsp; </P>
-
-
-<pre >   &lt;topic label=&quot;Ref1&quot; href=&quot;http://www.example.com/myReference.html&quot;/&gt;</pre>
-
-
-<h4 >National language and translated documentation</h4>
-
-
-<p >The platform help system uses the same national language directory lookup
-scheme used by the rest of the platform for finding translated files.&nbsp; (See
-<a href="product_def_nl.htm#platform">Locale specific files</a> for an
-explanation of this directory structure.)&nbsp; If you are using a <b>doc.zip</b>
-file, you should produce a <b>doc.zip</b> file for <b>each</b> locale and place
-it inside the correct locale directory.&nbsp; (You should not replicate the <b>nl</b>
-locale directory structure inside the doc.zip file.)</p>
-<p >In addition to locale specific directories, help system checks windowing
-  system and operating system directories when locating help resources. Look-up
-  is performed in the following order: <strong>ws</strong>, <strong>os</strong>, <strong>nl</strong> subdirectories, then
-  the root of the plug-in, until the resource is located. Documents, and other
-  resource, like images which differ between system, should be placed under ws
-  or os directories for specific platform.</p>
-<h4 ><a name="help_plugin_files_xref">Cross plug-in referencing</a></h4>
-
-
-<P >The <b>href</b> argument can also refer to content from another
-plug-in.&nbsp; This is done by using a special cross plug-in referencing
-notation that is resolved by the help server: </P>
-
-
-<pre >   &lt;topic label=&quot;Ref1&quot; href=&quot;<b>../&quot;another_plugin_id&quot;</b>/ref/ref1.html&quot;/&gt;</pre>
-
-
-<P >
-For example, you could link to this chapter of the programmer's guide using the
-following topic: </P>
-
-
-<pre >   &lt;topic label=&quot;Help Chapter in Platform Doc&quot; href=&quot;<b>../org.eclipse.platform.doc.isv/guide/help.html</b>&quot;/&gt;</pre>
-
-
-<p class="Note">Note:&nbsp; When referencing content from another plug-in, be
-sure to use the plug-in's <b>id</b>, as declared in its <b>plugin.xml </b>file,
-not its directory name.&nbsp; While these are often the same in practice, it's
-important to check that you are using the id and not the directory name.</p>
-
-<h4 >Referencing the Product Plug-in.</h4>
-
-<p>Branding information is often placed in a plug-in defining a
-  product as explained in <a href="product_def.htm">Defining a Product</a>. Help
-  resources in the product plug-in can be referenced from the table of contents
-  or topics using special identifier &quot;PRODUCT_PLUGIN&quot; for the plug-in ID. For
-  example,</p>
-<pre >   href=&quot;../<b>PRODUCT_PLUGIN</b>/book.css&quot;</pre>
-<p>refers to a style sheet residing in the plug-in for the currently
-  running product. </p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_manifest.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_manifest.htm
deleted file mode 100644
index 1e182f8..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_manifest.htm
+++ /dev/null

@@ -1,73 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Completing the plug-in manifest</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Completing the plug-in manifest</h3>
-
-<P >
-We started this example by creating our plug-in and document files. Next we created
-toc files to describe the organization of our content.
-The remaining piece of work is to pull everything together into a master toc and
-update our <b> plugin.xml</b> to actually contribute the master toc.&nbsp; </P>
-
-<P >
- We start by creating a <b>toc.xml</b> to contribute the three tocs we created
- initially.&nbsp; Instead of providing an <b>href</b> for each topic, we use the
- <b>link</b> attribute to refer to our existing toc files. </P>
-
-<pre>&lt;toc label=&quot;Online Help Sample&quot; topic=&quot;html/book.html&quot;&gt;
-	&lt;topic label=&quot;Concepts&quot;&gt;
-		&lt;link toc=&quot;toc_Concepts.xml&quot; /&gt;
-	&lt;/topic&gt;
-	&lt;topic label=&quot;Tasks&quot;&gt;
-		&lt;link toc=&quot;toc_Tasks.xml&quot; /&gt;
-	&lt;/topic&gt;
-	&lt;topic label=&quot;Reference&quot;&gt;
-		&lt;link toc=&quot;toc_Ref.xml&quot; /&gt;
-	&lt;/topic&gt;
-&lt;/toc&gt;</pre>
-
-<P >
- Then we update the <b>plugin.xml</b> to contribute our master toc: </P>
-<pre>
-   &lt;extension point=&quot;org.eclipse.help.toc&quot;&gt;
-      &lt;toc file=&quot;toc.xml&quot; <b>primary</b>=&quot;true&quot; /&gt;
-   &lt;/extension&gt;</pre>
-<P >Note the use of the <b>primary</b> attribute.&nbsp; Setting this attribute
-to true indicates that the toc should always appear in the navigation, even if
-it is not referenced by any other toc.&nbsp; This way, our &quot;master&quot;
-toc is always guaranteed to show up in the topics list.&nbsp; It appears at the
-top level list of books since no other toc references it.&nbsp;<I><BR>
-Note</I>: 
-If more files were associated with this toc but not present in the navigation, but just linked from other topics, then to have those topics available to the search engine we would have to use the <B>extradir</B> attribute in the toc.</P>
-<P >Finally, we contribute our individual toc files. </P>
-<pre>   &lt;extension point=&quot;org.eclipse.help.toc&quot;&gt;
-       &lt;toc file=&quot;toc_Concepts.xml&quot; /&gt;
-       &lt;toc file=&quot;toc_Tasks.xml&quot; /&gt;
-       &lt;toc file=&quot;toc_Reference.xml&quot; /&gt;
-   &lt;/extension&gt;</pre>
-<P >These toc files will not appear in the top level list of books because we
-did not set the <b>primary</b> attribute.&nbsp; Toc files that are not
-designated as primary will only appear in the documentation web if they are
-referred to from some toc that is a primary toc or is linked in by a primary
-toc. </P>
-
-<P >That's it. If you copy your plug-in directory to the platform's <b> plugins</b> directory, start the platform, and choose
-<b> Help-&gt;Help Contents</b>, you should see your example appear in the list
-of books. If you click on the "Online Help Sample", you'll see your toc structure:</P>
-
-<p><img src="images/help_contents.png" alt="On-line help browser with sample book structure" border="0" ></p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_nested.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_nested.htm
deleted file mode 100644
index d41e3a6..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_nested.htm
+++ /dev/null

@@ -1,86 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Building nested documentation structures</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<body bgcolor="white">
-
-<h3>Building nested documentation structures</h3>
-
-<p>As plug-ins contribute function to the platform, it's common to add
-documentation that describes the new function.&nbsp; How can this documentation
-be structured so that the user sees a cohesive and complete set of documentation
-instead of many individual contributions?&nbsp; The table of contents definition
-provides mechanisms for building documentation in both a top-down and bottom-up
-fashion.</p>
-
-<h4>Top-down nesting</h4>
-
-<p>Top-down nesting refers to the technique of defining a master table of
-contents which refers to all other included tocs.&nbsp; Top-down nesting is a
-convenient method for breaking up known content into smaller pieces.&nbsp; With
-top-down nesting, the <b>link</b> attribute is used in the table of contents
-definition to refer to linked tocs rather than providing an <b>href</b>.&nbsp; </p>
-
-<pre>&lt;toc label=&quot;Online Help Sample&quot; topic=&quot;html/book.html&quot;&gt;
-	&lt;topic label=&quot;Concepts&quot;&gt;
-		&lt;link toc=&quot;toc_Concepts.xml&quot; /&gt;
-	&lt;/topic&gt;
-	&lt;topic label=&quot;Tasks&quot;&gt;
-		&lt;link toc=&quot;toc_Tasks.xml&quot; /&gt;
-	&lt;/topic&gt;
-	&lt;topic label=&quot;Reference&quot;&gt;
-		&lt;link toc=&quot;toc_Ref.xml&quot; /&gt;
-	&lt;/topic&gt;
-&lt;/toc&gt;</pre>
-
-
-<p>The basic structure stays the same (Concepts, Tasks, Reference), but the
-individual tocs are free to evolve.&nbsp; They in turn might link to other sub-tocs.
-</p>
-
-<h4>Bottom-up composition</h4>
-
-<p>Bottom-up composition is more flexible in that it lets new plug-ins decide
-where the documentation should exist in the toc structure.&nbsp; Bottom-up
-composition is accomplished using <b>anchor</b> attributes.&nbsp; A toc defines
-named anchor points where other plug-ins can contribute documentation.&nbsp; In
-our example, we could add anchors so that plug-ins can contribute additional
-material between the concepts, tasks, and reference sections.</p>
-
-<pre>&lt;toc label=&quot;Online Help Sample&quot; topic=&quot;html/book.html&quot;&gt;
-	&lt;topic label=&quot;Concepts&quot;&gt;
-		&lt;link toc=&quot;toc_Concepts.xml&quot; /&gt;
-		&lt;<b>anchor</b> id=&quot;postConcepts&quot; /&gt;
-	&lt;/topic&gt;
-	&lt;topic label=&quot;Tasks&quot;&gt;
-		&lt;link toc=&quot;toc_Tasks.xml&quot; /&gt;
-		&lt;<b>anchor</b> id=&quot;postTasks&quot; /&gt;
-	&lt;/topic&gt;
-	&lt;topic label=&quot;Reference&quot;&gt;
-		&lt;link toc=&quot;toc_Ref.xml&quot; /&gt;		
-		&lt;<b>anchor</b> id=&quot;postReference&quot; /&gt;
-	&lt;/topic&gt;
-&lt;/toc&gt;</pre>
-<p>Other plug-ins can then contribute to the anchor from their plug-in.&nbsp;
-This is done using the <b>link_to</b> attribute when defining a toc.</p>
-<pre>&lt;toc <b>link_to=&quot;../com.example.helpexample/toc.xml#postConcepts&quot;</b> label=&quot;Late breaking info about concepts&quot;&gt;
-	&lt;topic&gt;
-		...
-	&lt;/topic&gt;
-&lt;/toc&gt;</pre>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_toc.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_toc.htm
deleted file mode 100644
index 2c3e8d1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_toc.htm
+++ /dev/null

@@ -1,98 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Table of contents (toc) files</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Table of contents (toc) files</h3>
-
-<P >
-Now that we have our sample content files we can create a table of contents (<b>toc</b>)
-file. A toc file defines the key entry points into the HTML content files by mapping a topic
-label to a reference in one of the HTML files.&nbsp; </P>
-<P >
-Applications that are being migrated to the platform can reuse existing documentation by
-using the toc file to define entry points into that documentation. </P>
-<P >
-A plug-in can have one or more toc files. Our example documentation is organized into three main categories: concepts, tasks and reference. How do we make
-toc files that represent this structure?</P>
-<P >
-We could make one large toc file, or we could create a separate toc file for each main category of content. This decision should be made according to the way your documentation teams work together.
-If a different author owns each category, it might be preferable to keep
-separate toc files for each category.&nbsp; It is not dictated by the platform architecture. </P>
-<P >
-In this example, we will create a toc file for each major content category. For such a small number of files,
-having separate toc files for each category may not be necessary.&nbsp; We
-will build this example as if we had many more files or had separate authors who
-own each content category.</P>
-<P >
-Our files look like this:</P>
-
-<H4>toc_Concepts.xml</H4>
-<pre>
-   &lt;toc label=&quot;Concepts&quot;&gt;
-      &lt;topic label=&quot;Concept1&quot; href=&quot;html/concepts/concept1.html&quot;&gt;
-         &lt;topic label=&quot;Concept1_1&quot; href=&quot;html/concepts/concept1_1.html&quot;/&gt;
-         &lt;topic label=&quot;Concept1_2&quot; href=&quot;html/concepts/concept1_2.html&quot;/&gt;
-      &lt;/topic&gt; 
-   &lt;/toc&gt;
-</pre>
-
-<H4>
-toc_Tasks.xml</H4>
-<pre>
-   &lt;toc label=&quot;Tasks&quot;&gt;
-      &lt;topic id=&quot;plainTasks&quot; label=&quot;Plain Stuff&quot;&gt;
-         &lt;topic label=&quot;Task1&quot; href=&quot;html/tasks/task1.html&quot;/&gt;
-         &lt;topic label=&quot;Task2&quot; href=&quot;html/tasks/task2.html&quot;/&gt;
-      &lt;/topic&gt;
-      &lt;topic id=&quot;funTasks&quot; label=&quot;Fun Stuff&quot; &gt;
-         &lt;topic label=&quot;Task3_1&quot; href=&quot;html/tasks/task3_1.html&quot;/&gt;
-         &lt;topic label=&quot;Task3_2&quot; href=&quot;html/tasks/task3_2.html&quot;/&gt;
-      &lt;/topic&gt;
-   &lt;/toc&gt;
-</pre>
-
-<H4>
-toc_Ref.xml</H4>
-<pre>
-   &lt;toc label=&quot;Reference&quot;&gt;
-      &lt;topic label=&quot;Ref1&quot; href=&quot;html/ref/ref1.html&quot;/&gt;
-      &lt;topic label=&quot;Ref2&quot; href=&quot;html/ref/ref2.html&quot;/&gt;
-   &lt;/toc&gt;
-</pre>
-<P >
- A topic can be a simple link to content.&nbsp;
-For example, &quot;Task1&quot; provides a <b>label</b>
-and an <b>href</b> linking to the content.&nbsp; A
-topic can also be a hierarchical grouping of sub topics with no content of its
-own.&nbsp; For example, &quot;Fun Stuff&quot; has only a <b>label</b>
-and sub topics, but no <b>href</b> .&nbsp; Topics can
-do both, too.&nbsp; &quot;Concept1&quot; has an <b>href</b>
-and sub topics. </P>
-
-<p><b>Dynamic content</b></p>
-
-<p>
-Dynamic content is available for the table of contents in the form of
-<a href="ua_dynamic_filters.htm">filters</a> and <a href="ua_dynamic_anchors.htm">
-anchors</a>. For example, you may want a topic to show up in the table of contents
-only when running on a specific operating system.
-</p>
-
-<p>
-<a href="ua_dynamic_includes.htm">Includes</a> are not supported here because they
-are not needed; use <a href="ua_help_content_nested.htm">links</a> instead.
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_xhtml.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_xhtml.htm
deleted file mode 100644
index 4df3086..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_xhtml.htm
+++ /dev/null

@@ -1,128 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
-<meta content="text/css" http-equiv="Content-Style-Type">
-<link type="text/css" charset="ISO-8859-1" href="../book.css" rel="STYLESHEET">
-<link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-<body bgcolor="white">
-
-<h3>Contributing XHTML help documents</h3>
-
-<p><b>Why use XHTML?</b></p>
-
-<p>
-The help system provides the ability to produce <a href="ua_dynamic.htm">dynamic help
-content</a> by annotating your XHTML markup with special tags to
-<a href="ua_dynamic_filters.htm">filter</a>,
-<a href="ua_dynamic_includes.htm">includes</a>, and specify
-<a href="ua_dynamic_anchors.htm">anchors</a> for extensions. These features are not
-available when using HTML.
-</p>
-
-<p><b>How to contribute XHTML</b></p>
-
-<p>
-XHTML help documents are contributed in much the same way as HTML, except there are
-a few important differences that must be there in order to support dynamic content
-and searching. These required modifications are listed below:
-</p>
-
-<ul>
-   <li>
-      <p>
-         You <b>must</b> bind the XHTML search participant to your
-         doc plugin.
-      </p>
-      <p>
-         The eclipse help implementation uses <a href="http://lucene.apache.org/">
-         Lucene</a> to index its documents to speed up searching. In order to index
-         a document, Lucene must be able to read the format. Eclipse already provides
-         a search participant for indexing XHTML documents, so you simply need to
-         tell the help system to use it for your documents. Add the following extension
-         to your plug-in manifest:
-      </p>
-      <p>
-         <pre>
-   &lt;extension
-         point="org.eclipse.help.base.luceneSearchParticipants"&gt;
-      &lt;binding participantId="org.eclipse.help.base.xhtml"/&gt;
-   &lt;/extension&gt;
-         </pre>
-      </p>
-   </li>
-   <li>
-      <p>
-         If using dyamic content, you <b>must</b> bind the XHTML dynamic content
-         producer to your doc plugin.
-      </p>
-      <p>
-         If you want to produce dynamic content using the XML annotations, you need
-         to tell the help system that it should process your documents. This is
-         done by binding the XHTML dynamic content producer to your plugin.
-      </p>
-      <p>
-         <pre>
-   &lt;extension
-         point="org.eclipse.help.contentProducer"&gt;
-      &lt;binding producerId="org.eclipse.help.dynamic"/&gt;
-   &lt;/extension>
-         </pre>
-      </p>
-   </li>
-</ul>
-
-<a name="include_format"><p><b>XHTML include format</b></p></a>
-
-<p>
-If you wish to use <a href="ua_dynamic_includes.htm">includes</a> in your XHTML,
-the format of the <code>path</code> attribute is as follow: (explained below)
-</p>
-
-<p>
-<pre>
-   &lt;plugin_id&gt;/&lt;path_to_xhtml_file&gt;/&lt;filename_xhtml&gt;/&lt;element_id&gt;
-</pre>
-</p>
-
-<p>
-Where the fields are:
-</p>
-
-<p>
-<ul>
-   <li>
-      <b>plugin_id</b>: The id of the plug-in containing the content to include
-      (e.g. <code>org.eclipse.help</code>)
-   </li>
-   <li>
-      <b>path_to_xhtml_file</b>: The plug-in relative path to the file (e.g. <code>
-      /my_folder/my_sub_folder/</code>)
-   </li>
-   <li>
-      <b>filename_xhtml</b>: The name of the XHTML file, including extension (e.g.
-      <code>my_file.xhtml</code>)
-   </li>
-   <li>
-      <b>element_id</b>: The unique identifier for the element you wish to include. This
-      is set by adding an <code>id</code> attribute to that element (e.g. <code>
-      my.element.id</code>)
-   </li>
-</ul>
-</p>
-
-<p>
-For example, if you wish to include the paragraph (<code>&lt;p&gt;</code> element)
-with the id <code>my_copyright</code> from the file <code>/copyrights/copyright.xhtml
-</code> in plugin <code>my.product.plugin</code>, you would specify the following:
-</p>
-
-<p>
-<pre>
-   my.product.plugin/copyrights/copyright.xhtml/my_copyright
-</pre>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context.htm
deleted file mode 100644
index 1945560..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Context-sensitive help</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Context-sensitive help</h3>
-<p>A focused set of help topics that is related to the current context can be 
-shown to users on demand using <b>context-sensitive help</b>. This form of user 
-assistance is delivered to users when a platform-specific trigger is activated 
-(e.g. F1 key on Windows, Ctrl+F1 on GTK, Help key on Carbon). Until Eclipse 3.1, 
-context-sensitive help was presented in infopop windows. Since 3.1, a new Help 
-view is the preferred way to deliver context-sensitive information to the user.</p>
-<p>Context-sensitive help can be associated with widgets statically using 
-context IDs, or dynamically using context providers. The new help view also adds 
-dynamic help capability by searching help for topics relevant for the current 
-context.</p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_dynamic.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_dynamic.htm
deleted file mode 100644
index 6febf6d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_dynamic.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Dynamic creation of context help</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>
-Dynamic creation of context help</h1>
-<p>
-In addition to statically associating widgets and context Ids, it is possible to 
-provide this information dynamically for a more dynamic context-sensitive help 
-capability. Help system uses context Ids to locate the matching
-<a href="../reference/api/org/eclipse/help/IContext.html">
-org.eclipse.help.IContext</a> object. The new Help view tracks activation of the 
-workbench parts (views and editors) and checks if they adapt to
-<a href="../reference/api/org/eclipse/help/IContextProvider2.html">
-org.eclipse.help.IContextProvider</a> interface. If they do, the view will use 
-the context provider to locate the <code>IContext</code> object and get the 
-required information from it. This object can be cached or created on the fly.</p>
-<p>
-Workbench parts that want to create the context object dynamically should adapt 
-to the <code>IContextProvider.class</code> object as a key:</p>
-<blockquote>
-	<pre>public Object getAdapter(Class key) {
-	if (key.equals(IContextProvider.class)) {
-		return new MyContextProvider();
-	}
-	return super.getAdapter(key);
-}</pre>
-</blockquote>
-<p>The context provider interface requires implementation of three methods:</p>
-<blockquote>
-	<pre>public class MyContextProvider implements IContextProvider {
-	int getContextChangeMask() {
-		return NONE;
-	}
-	IContext getContext(Object target) {
-		return myContext;
-	}
-	String getSearchExpression(Object target) {
-		return null;
-	}
-}</pre>
-</blockquote>
-<p>If context change mask returns <code>NONE</code>, context object will need to 
-be provided when the workbench part is activated. If <code>SELECTION</code> is 
-returned, you will need to provide context object that is sensitive to the 
-current selection in the part. Each time part selection provider fires a 
-selection change event, the context provider will be asked to provide context 
-object.</p>
-<p>Optionally, search expression for the dynamic help can be provided. 
-Otherwise, a combination of the part name and perspective name will be used with 
-good results in most cases.
-</p>
-
-<p>
-<b>Note:</b> In addition to using context providers (or alternatively), you can use
-XML annotations to <a href="ua_dynamic_filters.htm">filter</a> topics in context
-help.
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_id.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_id.htm
deleted file mode 100644
index dd1392c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_id.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Declaring a context id</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>
-Declaring a context id</h1>
-
-<P >The <b>setHelp</b> method in <b>
-<a href="../reference/api/org/eclipse/ui/help/IWorkbenchHelpSystem.html">org.eclipse.ui.help.IWorkbenchHelpSystem</a></b>
-is used to associate a context id with a <code>Control</code>, <code>IAction</code>, 
-<code>Menu</code>, or <code>MenuItem</code>.&nbsp;
-The context id should be fully qualified with the plug-in id.&nbsp; For example,
-the following snippet associates the id &quot;com.example.helpexample.panic_button&quot;
-with a button in the application. </P>
-
-
-<pre>PlatformUI.getWorkbench().getHelpSystem().setHelp(myButton, com.example.helpexample.panic_button);</pre>
-
-
-<P >The following UI controls cannot have context ids (and therefore cannot have
-context-sensitive help): </P>
-
-
-<ul>
-  <li>Toolbar buttons (ToolItem)</li>
-  <li>CTabItem</li>
-  <li>TabItem</li>
-  <li>TableColumn</li>
-  <li>TableItem</li>
-  <li>TableTreeItem</li>
-  <li>TreeItem</li>
-</ul>
-<p>Widgets that do not get focus should not be assigned context ids, since they
-will never trigger a context-sensitive help.</p>
-<p>&nbsp;</p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_infopops.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_infopops.htm
deleted file mode 100644
index 6397a99..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_infopops.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Infopops
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Infopops</H1>
-
-<p>An infopop is a small window associated with a
-particular SWT widget in a plug-in's user interface.&nbsp; It displays
-context-sensitive help and links to related help topics for the widget.&nbsp;It
-is activated when the user puts focus on the widget and presses the <code>F1</code>
-key (<code>Ctrl+F1</code> on GTK, and <code>Help</code> key on Carbon).</p>
-<p>Since Eclipse 3.1, the preferred way to show the context help is in the help 
-window. However, it is still possible to configure context help presentation to 
-use infopops in the Help preferences. For example, here is an infopop that has been defined on 
-the General/Search page: </p>
-<p align="center">
-<img border="0" src="images/infopops.png" width="614" height="353">
-</p>
-
-
-
-<p>Since Eclipse 3.1, infopops have a link to show the currently displayed 
-context help in the new Help view.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_xml.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_xml.htm
deleted file mode 100644
index 1dfba0f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_xml.htm
+++ /dev/null

@@ -1,101 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Describing and packaging context-sensitive help content</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>
-Describing and packaging context-sensitive help content</h1>
-
-
-<p>Content-sensitive help is described by associating the context id declared in the UI code
-with a description and list of links to related topics in the online help.&nbsp;
-These associations are made inside an XML file.&nbsp; You can create any number
-of XML files containing context help associations for each plug-in.&nbsp; The
-description and links for each context id is made inside <b>&lt;context&gt;</b>
-elements in the XML file.&nbsp; Each context element can have an optional <b>&lt;description&gt;</b>
-element which is used to describe the UI object and any number of <b>&lt;topic&gt;</b>
-elements which link to the on-line documentation.</p>
-<p>Since 3.1, context elements can optionally override the default title used to 
-present the context help information in the Help view.</p>
-<pre>&lt;contexts&gt;
-	&lt;context id=&quot;panic_button&quot; title=&quot;Panic Button Title&quot;&gt;
-		&lt;description&gt;This is the panic button.&lt;/description&gt;
-		&lt;topic href=&quot;tasks/pushing_the_panic_button.htm&quot; label=&quot;Pushing the panic button&quot;/&gt;
-		&lt;topic href=&quot;reference/panic_button.htm&quot; label=&quot;Panic Button Reference&quot;/&gt;
-	&lt;/context&gt;
-	...
-&lt;/contexts&gt;</pre>
-<p>Once the contexts have been described in the XML file (or files), you are
-ready to refer to the context files in your plug-in manifest.&nbsp; Note that
-the context id is not fully qualified above.&nbsp; This is allowed, as long as
-the context file is contributed in the manifest of the plug-in that defined the
-context id.&nbsp; In other words, the context id is resolved to the id of the
-plug-in that contributed the XML file.&nbsp;&nbsp;</p>
-<p>A plug-in contributes context files using the <b><a href="../reference/extension-points/org_eclipse_help_contexts.html">org.eclipse.help.contexts</a></b>
-extension point.&nbsp;&nbsp;</p>
-
-<pre>   &lt;extension point=&quot;org.eclipse.help.contexts&quot;&gt;
-      &lt;contexts name=&quot;myContextHelp.xml&quot;  /&gt;
-   &lt;/extension&gt;</pre>
-
-<p>You can reference context files from other plug-ins by including the <b>plugin</b>
-attribute.&nbsp; This allows you to group all of your documentation, including
-content-sensitive help, in one plug-in, and refer to it from the UI code plug-in or some other
-related plug-in.</p>
-
-<pre>   &lt;extension point=&quot;org.eclipse.help.contexts&quot;&gt;
-      &lt;contexts name=&quot;myContextHelp.xml&quot; <b>plugin</b>=&quot;com.example.helpExample&quot;  /&gt;
-   &lt;/extension&gt;</pre>
-
-<p>As you can see, you have a lot of flexibility in organizing your contexts
-into one or more files contained in one or more plug-ins.&nbsp; The main
-consideration is that the context ids in the files resolve correctly.&nbsp; If
-you do not fully qualify a context id, then you must contribute the context XML
-files in the plug-in that declared the context ids.&nbsp; If you use fully
-qualified context ids in your context XML file, then you have complete
-flexibility in the location of your XML files and which plug-in contributes the
-contexts.</p>
-
-
-<h4>
-Context-sensitive help from multiple plug-ins</h4>
-
-
-<p>Another level of flexibility is the ability to contribute context-sensitive 
-help for the
-same context id from different plug-ins.&nbsp; This is useful, for example, if
-there are different sets of documentation plug-ins that may or may not be
-installed in a user's configuration.&nbsp; This allows each documentation
-plug-in to declare its contexts independently.&nbsp; The end user will see the
-merged context-sensitive help content for all plug-ins that contributed contexts for the
-widget's id.</p>
-
-
-<p>Note that the fully
-qualified context id for the widget must be used, since none of the documentation plug-ins
-declared the context id.&nbsp; When multiple plug-ins contribute 
-context-sensitive help for
-the same context ID, the content defined in the plug-in that declared the
-context (the UI plug-in) is shown first.&nbsp; Additional descriptions and links
-are appended in no guaranteed order.</p>
-
-<p><b>Dynamic content</b></p>
-
-<p>
-Dynamic content is available for the context help in the form of
-<a href="ua_dynamic_filters.htm">filters</a> on context help topic links. For
-example, you may want a topic link to show up in the context help only when running
-on a specific operating system.
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_search.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_search.htm
deleted file mode 100644
index 143593d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_search.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Information Search</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>
-Information Search</h1>
-
-
-
-
-
-<p>Since Eclipse 3.1, search in the workbench has been partitioned into two 
-major categories: development artifact search and information search. The former 
-is handled by the search dialog opened from the Search menu. The later is 
-available from Help&gt;Search menu item which opens the new Help view into the 
-Search page.</p>
-<p>The new information search facility uses multiple search engines run in 
-parallel using the same search expression. Eclipse provides a number of 
-preconfigured search engines. New engines can be added programmatically or by 
-the user. All the results are collated in the Search page directly.</p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_search_types.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_search_types.htm
deleted file mode 100644
index 1a197ce..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_search_types.htm
+++ /dev/null

@@ -1,100 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Federated search engine types</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>
-Federated search engine types</h1>
-<p>
-The new federated information search in Help system uses the notion of <b>search 
-engine types</b> and <b>search engines</b>. An engine type is a meta-engine from 
-which a number of concrete search engines can be created by parameterization.</p>
-<p>New engine types are contributed through the
-<a href="../reference/extension-points/org_eclipse_help_ui_searchEngine.html">
-org.eclipse.help.ui.searchEngine</a>:</p>
-<blockquote>
-	<pre>&lt;extension point=&quot;org.eclipse.help.ui.searchEngine&quot;&gt;
-	&lt;engineType
-		scopeFactory=&quot;com.example.xyz.XYZScopeFactory&quot;
-		label=&quot;XYZ Search&quot;
-		class=&quot;com.example.xyz.search.XYZSearch&quot;
-		icon=&quot;icons/etool16/xyzsearch.gif&quot;
-		pageClass=&quot;com.example.xyz.search.XYZSearchPage&quot;
-		id=&quot;com.example.xyz.XYZSearch&quot;&gt;
-		&lt;description&gt;
-			Instances of XYZ Search search the XYZ site.
-		&lt;/description&gt;
-	&lt;/engineType&gt;</pre>
-</blockquote>
-This extension point is used to plug in search participants in the information 
-search. Each search engine can be configured individually. When search is 
-initiated, each search engine is executed as a background job, and the results 
-are collated in the help view immediately under the query. 
-<p>Search engines defined here will not automatically show up as federated 
-search participants until engine product binding is established, unless <code>
-productId</code> attribute is left undefined. For engines that define it, only 
-those bound to a particular product will show up when that product is running.
-</p>
-<p>Search engines can simply compose a URL and provide only one hit containing 
-that URL as <code>href</code>. Popular search engines for which API support 
-requires license can be plugged in like this. On the other end of the spectrum, 
-search engines can communicate with the server and receive individual hits with 
-information like label, href, short description, score etc. Local help engine 
-can produce hits this way.</p>
-<p>Regardless of the search mechanism, engines can provide various search scope 
-settings using JFace preference pages. These pages are shown when 'Advanced 
-Settings' link is followed from the Help view. In addition to root preference 
-pages defined with the engine, additional preference sub-pages can be plugged in 
-for more advanced settings. </p>
-<p>Scope settings are loaded and stored using <code>IPreferenceStore</code> 
-objects. Scope settings for all engines are grouped together under a named <b>
-scope set</b>. When first opened, default scope set ('Default') is created, but 
-users can define more scope sets and flip between them. </p>
-<p>Since federated search support is part of <code>org.eclipse.help.base</code> 
-plug-in, a factory is needed to create search scope objects from the data in the 
-preference store. Clients that plug in scope preference pages are required to 
-plug in scope factories as well. </p>
-<p>Engines defined in this extension point do not show up in the UI by default. 
-What is shown there is a concrete <b>instance</b> of a search engine that can be 
-individually modified. Products can pre-configure the help system with a number 
-of instances of the registered engine types, possibly parameterized to perform 
-in a desired way. In addition, users can add their own instances of the 
-registered engines and configure them to their liking:</p>
-<blockquote>
-	<pre>
-&lt;engine
-	enabled=&quot;true&quot;
-	engineTypeId=&quot;com.example.xyz.search.XYZSearch&quot;
-	id=&quot;com.example.xyz.XYZSearch&quot;
-	label=&quot;XYZ Search&quot;&gt;
-&lt;/engine&gt;
-&lt;engine
-	enabled=&quot;true&quot;
-	engineTypeId=&quot;org.eclipse.help.ui.web&quot;
-	id=&quot;org.eclipse.sdk.Eclipse&quot;
-	label=&quot;%search.Eclipse.label&quot;&gt;
-	&lt;description&gt;
-		%search.Eclipse.desc
-	&lt;/description&gt;
-	&lt;param 
-		name=&quot;url&quot; 
-		value=&quot;http://eclipse.org/search/search.cgi?q={expression}&amp;amp;ul=&amp;amp;ps=20&amp;amp;m=all&quot;&gt;
-	&lt;/param&gt;
-&lt;/engine&gt;</pre>
-</blockquote>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro.htm
deleted file mode 100644
index 6c162fb..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
-<title>Intro support</title>
-<link rel=Stylesheet type="text/css" media=all href="../book.css">
-<meta name=copyright
-content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv=Content-Style-Type content="text/css">
-</head>
-
-<body bgcolor=white>
-
-<h2>Welcome/Intro support</h2>
-
-<p>Intro support is a set of extension points and workbench parts that allow
-plug-ins to define specialized pages that introduce a platform product to new
-users. These extension points can be used to create the &quot;Initial User
-Experience&quot; of the product in the form of welcome pages. Welcome pages are
-intended to guide users into discovering a product's functionality. They are
-typically shown the first time a product is started. They can be anything from
-a single page displaying a Macromedia Flash demo, to multiple pages that are
-extensible and follow the Eclipse platform's pluggable architecture. </p>
-
-<p>Intro support is typically configured at the product level, although
-individual plug-ins can contribute intro information to known product intro
-configurations.</p>
-
-<p>From a workbench point of view, the root of the intro support is in the <b>intro
-part</b>. This part is specified in an extension definition. When the workbench
-initializes, it creates an intro site that reserves space for the intro page.
-The intro part implementation for the site is determined using product
-configuration information. Once an intro part is shown, it can move between two
-modes: </p>
-
-<ul>
- <li>in <b>full mode</b>, the intro part takes over the main workbench area.</li>
- <li>in <b>standby mode</b>, the intro part moves to the side, allowing the current
-     perspective to remain visible.</li>
-</ul>
-
-<p>Once an intro part is established, it must be configured with intro
-information. This is done using an <b>intro config</b> which is also
-contributed using an extension. Individual plug-ins can add to the basic
-product intro config using their own extensions.</p>
-
-<p>We'll look at the platform SDK intro page as an example in order to better
-understand these concepts.</p>
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_cust_intro_part.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_cust_intro_part.htm
deleted file mode 100644
index 3f7d816..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_cust_intro_part.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Using the CustomizableIntroPart</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Using the CustomizableIntroPart</h3>
-<p>The platform's <a href="../reference/api/org/eclipse/ui/intro/config/CustomizableIntroPart.html"><b>CustomizableIntroPart</b></a>
-allows for the content and presentation of the intro to be customized using the
-<b><a href="../reference/extension-points/org_eclipse_ui_intro_config.html">org.eclipse.ui.intro.config</a></b>
-extension point.  (This intro config can be extended using the 
-<b><a href="../reference/extension-points/org_eclipse_ui_intro_configExtension.html">org.eclipse.ui.intro.configExtension</a></b>
-extension point.)  This structure allows product plug-in developers to focus on developing their intro content rather than
-implementing an intro part scheme from scratch.  If a different intro class is specified, then these two extension points
-are not utilized and the specified class must implement its own scheme for intro content format and configuration.
-</p>
-<h4>&nbsp;</h4>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_cust_static.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_cust_static.htm
deleted file mode 100644
index b10fae8..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_cust_static.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Displaying static HTML content in a CustomizableIntroPart</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Displaying static HTML content in a CustomizableIntroPart</h3>
-<p>Just like any intro part implementation, to use a CustomizableIntroPart you need to follow the basic steps to bind it to a product. However, there is an extra step needed to use this intro part and it is binding a "configuration" with it. Just like you bind an intro to a product, you must bind an <em>introConfig </em> to a customizableIntroPart. Here is a sample configuration: </p>
-<pre>
-
-&lt;extension point="org.eclipse.ui.intro.config"&gt;
-	&lt;config id = "static001_configId"
-		introId="org.eclipse.ui.intro.examples.static_introId"
-		content="introContent.xml"&gt;
-		&lt;presentation&nbsp; home-page-id="homePageId" 
-			standby-page-id="standbyPageId"&gt;
-			&lt;implementation os="win32" kind="html" /&gt; 
-			&lt;implementation kind="swt" /&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-		&lt;/presentation&gt;
-	&lt;/config&gt;&nbsp;&nbsp; 
-&lt;/extension&gt; 
-
-</pre>
-<p> In the above contribution a <em>configuration </em> is registered with an intro part with id <em>org.eclipse.ui.intro.examples.static_introId. </em>(It is assumed that this intro part is a customizable intro part instance that has already been registered with the workbench). This configuration defines the content to be presented in the intro part and dictates how it is presented to the user.&nbsp; The content is defined in an xml markup file, <em>introContent.xml, </em>while the presentation is dictated by two <em> implementation </em> elements in the markup.</p>
-<p>A config presentation can be either an SWT browser based or a UI forms based presentation. In the above contribution, the presentation will be&nbsp;"html", ie browser based on win32 platforms, while it will be "swt" ie: UI forms based on all other platforms. At runtime, when the workbench is trying to instantiate the CustomizableIntroPart, the operating system is determined and the correct implementation of the presentation is chosen. <br>
-  Also, a <em>home-page-id </em>or root page needs to be specified as it will be the first page displayed by the customizableIntroPart. If a <em>standby-page-id </em> is also specified, it will be displayed in the intro part when the intro part is put into standby mode.</p>
-<p>The details of what the content file can be found in the extension point documentation. For a simpleexample, and to contribute static content we will use the following as content: </p>
-<pre>&lt;?xml version="1.0" encoding="UTF-8" ?&gt; &nbsp;&nbsp;&nbsp; 
-&lt;introContent&gt;
-	&lt;page id="homePageId" url="http://eclipse.org"/&gt;
-	&lt;page id="standbyPageId" url="./static001/standby.html"/&gt; &nbsp;&nbsp;&nbsp; 
-&lt;/introContent&gt; 
-
-</pre>
-<p> In the above contribution, a simple url is used as the root page, in this case is a url pointing to the eclipse.org web site. This was done for simplicity. The root page could have been any html file, for example, a local html file that loads a flash demo. There is also a standby page defined that will be displayed when the intro is placed into standby mode.
-</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_define_content.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_define_content.htm
deleted file mode 100644
index 08faa3a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_define_content.htm
+++ /dev/null

@@ -1,85 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Defining intro content</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Defining intro content</h3>
-<p>
-Now we can look at the content itself.  Content is described in terms of pages.  All pages have an <b>id</b> attribute.
-This is the id that is used when defining the home and standby pages, and other places where there is a reference
-to a page.  Otherwise, the relevant attributes depend on the kind of page that is defined.
-There are two basic types of pages:
-</p>
-<ul>
-<li><b>Static pages</b> are plain HTML files.  These pages use the normal HTML mechanisms to link to other
-pages.  Static pages need not be defined in the config content file, except for the home page.  Since the home
-page is specified by id (<b>home-page-id</b>) in the <b>presentation</b> element, there must be a page definition
-using that id in the content file.  This page need only define a <b>url</b>.  All other subelements will be ignored
-since the HTML page itself will describe the page content. All other HTML intro pages contributed by the plug-in
-must be included with the plug-in, but do not need to be specified in the content file. HTML files located in other
-plug-ins or on the web may be referenced also. </li>
-<li><b>Dynamic pages</b> are described in the XML content file using subelements that describe the content of the
-page.  The subelements are UI items often found in HTML-like pages.  Depending on the implementation, these pages
-will either be dynamically translated to HTML (when the implementation <b>kind</b> is html) or else dynamically
-created as SWT-based UI forms (when the implementation <b>kind</b> is swt).  The following subelements
-can be defined in a page: 
-<ul>
-<li>A <b>group</b> is used to group other subelements and define a consistent style across the group.</li>
-<li>A <b>link</b> defines a link that can be displayed using an image and text.  The link can navigate to another
-page and optionally run an intro action.  Actions are specified as commands in the URL.</li>
-<li>The <b>text</b> and <b>img</b> elements show text and image content.</li>
-<li>The <b>include</b> element includes a previously defined subelement.  The element is referred to by its id.  </li>
-<li>The <b>head</b> element defines additional HTML to be included in the head section of the page
-when the html implementation is used. </li>
-<li>The <b>html</b> element defines additional HTML to be included in the body of the page
-when the html implementation is used.</li>
-</ul>
-A <b>title</b> for a page may also be defined.  A page may also specify that
-its content is defined in a separate <b>content</b> file.  Breaking up pages into separate
-files may be useful when performance is a concern, since an intro page's contents won't be initialized until needed.
-</li>
-</ul>
-<p>
-The best way to get a feel for the content definition format is to browse the implementations in the SDK.  The following
-snippet shows just the first part of the content for the SDK root page, which is the first intro page shown.
-</p>
-<pre>&lt;introContent&gt;
-  &lt;page alt-style="css/root_swt.properties" style="css/root.css" id="root" style-id="page"&gt;
-    &lt;title style-id="intro-header">Welcome to Eclipse Platform 3.0&lt;/title&gt;
-    &lt;group id="links-background"&gt;
-      &lt;group id="page-links"&gt;
-        &lt;link label="Overview" url="http://org.eclipse.ui.intro/showPage?id=overview" id="overview" style-id="left"&gt;
-          &lt;text&gt;Find out what Eclipse is all about&lt;/text&gt;
-        &lt;/link&gt;
-        &lt;link label="Tutorials" url="http://org.eclipse.ui.intro/showPage?id=tutorials" id="tutorials" style-id="left"&gt;
-          &lt;text&gt;Let us guide you through Eclipse end-to-end tutorials&lt;/text&gt;
-        &lt;/link&gt;
-        &lt;link label="Samples" url="http://org.eclipse.ui.intro/showPage?id=samples" id="samples" style-id="right"&gt;
-          &lt;text>Explore Eclipse development through code samples&lt;/text&gt;
-        &lt;/link&gt;
-        &lt;link label="Whats New" url="http://org.eclipse.ui.intro/showPage?id=news" id="news" style-id="right"&gt;
-          &lt;text&gt;Find out what is new in this release&lt;/text&gt;
-        &lt;/link&gt;
-      &lt;/group&gt;
-    &lt;/group&gt;
-</pre>
-<p>
-Elements on a page can also be <b>filteredFrom</b> a particular implementation.  This allows page designers
-to design with particular platforms in mind.  There are many more powerful attributes that 
-can be used when describing a page and its contents.  See the extension point documentation for 
-<b><a href="../reference/extension-points/org_eclipse_ui_intro_config.html">org.eclipse.ui.intro.config</a></b>
-and its associated <a href="../reference/extension-points/introContentFileSpec.html">intro content file format specification</a> for a complete reference of 
-valid elements, subelements, and their attributes.
-</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining.htm
deleted file mode 100644
index b6b0b55..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining.htm
+++ /dev/null

@@ -1,70 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Defining an intro part</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Defining an intro part</h3>
-<p>
-The <a href="../reference/api/org/eclipse/ui/intro/IIntroPart.html"><b>IIntroPart</b></a> interface
-and the <b><a href="../reference/extension-points/org_eclipse_ui_intro.html">org.eclipse.ui.intro</a></b>
-extension point make up the generic mechanism that can be used to create your own intro support for
-a given product.  The main purpose of this extension is to define the class that implements
-<a href="../reference/api/org/eclipse/ui/intro/IIntroPart.html"><b>IIntroPart</b></a> and to
-specify the binding between a product id and an intro part.  For example, the following contribution
-defines a hypothetical intro part to be shown by the workbench on startup:
-</p>
-<pre>&lt;extension  
-	point="org.eclipse.ui.intro"&gt;
-	&lt;intro
-		class="com.example.SampleIntroPart"
-		id="someId"&gt;
-		icon="someIcon.png"
-	&lt;/intro>
-	&lt;introProductBinding
-		introId="someId"
-		productId="com.example.someProductId"&gt;
-	&lt;/introProductBinding&gt;
-&lt;/extension>
-</pre>
-This contribution first defines the intro part and assigns it the id "someId".  It then binds this
-intro part to a product whose id is "com.example.someProductId".  On platform startup, the class specified
-in the <b>class</b> attribute will be instantiated by the workbench and presented to the user as the
-introduction to the product.  This is the lowest level integration into the 
-<a href="../reference/api/org/eclipse/ui/intro/IIntroPart.html"><b>IIntroPart</b></a>
-interface.
-<p>The platform supplies its own <a href="../reference/api/org/eclipse/ui/intro/IIntroPart.html"><b>IIntroPart</b></a>
-implementation called <a href="../reference/api/org/eclipse/ui/intro/config/CustomizableIntroPart.html"><b>CustomizableIntroPart</b></a>
-that allows for the content and presentation of the intro to be customized.  Below is the snippet that defines the intro part for the workbench.
-We won't go over the mechanics of implementing an intro part since we want to focus on defining
-the intro content.  (See the extension point documentation and javadoc referenced above for more detail
-if you need it.)
-</p>
-<pre>&lt;extension  
-	point="org.eclipse.ui.intro"&gt;
-	&lt;intro
-		class="org.eclipse.ui.intro.config.CustomizableIntroPart"
-		id="org.eclipse.platform.intro"&gt;
-	&lt;/intro>
-	&lt;introProductBinding
-		introId="org.eclipse.platform.intro"
-		productId="org.eclipse.platform"&gt;
-	&lt;/introProductBinding&gt;
-&lt;/extension>
-</pre>
-The above contribution defines the 
-<a href="../reference/api/org/eclipse/ui/intro/config/CustomizableIntroPart.html"><b>CustomizableIntroPart</b></a> as the
-intro part to be used for the Eclipse SDK platform.  The rest of this discussion shows you how to use and extend
-this part.
-<h4>&nbsp;</h4>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining_config.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining_config.htm
deleted file mode 100644
index 1034b5e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining_config.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Defining an intro config</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Defining an intro config</h3>
-<p>
-<b><a href="../reference/extension-points/org_eclipse_ui_intro_config.html">org.eclipse.ui.intro.config</a></b>
-describes the id of the intro config that is to show our content, and the name of the
-XML file that contains the specific definition for the intro content.  It is expected that only one
-intro config should be defined for a given <a href="../reference/api/org/eclipse/ui/intro/config/CustomizableIntroPart.html"><b>CustomizableIntroPart</b></a>.
-(Only the first intro config found can be shown in a
-<a href="../reference/api/org/eclipse/ui/intro/config/CustomizableIntroPart.html"><b>CustomizableIntroPart</b></a>.)
-</p>
-<pre>&lt;extension   
-	id="intro"
-	point="org.eclipse.ui.intro.config"&gt;
-	<b>&lt;config
-		introId="org.eclipse.platform.intro"
-		id="org.eclipse.platform.introConfig"
-		content="$nl$/introContent.xml"&gt;</b>
-	&lt;presentation
-		home-page-id="root" standby-page-id="standby"&gt;
-			&lt;implementation
- 				ws="win32"
-				style="css/shared.css"
-				kind="html"
-				os="win32"&gt;
-			&lt;/implementation&gt;
-			&lt;implementation
-				kind="swt"&gt;
-			&lt;/implementation&gt;
-	&lt;/presentation&gt;
-	&lt;/config&gt;
-&lt;/extension&gt;  
-</pre>
-The path for the file is relative to the plug-in's directory.  (Note
-the use of the <tt>$nl$</tt> variable in the directory name, which means the file will be located in a directory specific
-to the national language of the target environment.)
-<p>
-The config extension allows you to specify both the content and the presentation of the content.
-While the <b>content</b> element focuses on defining pages, the
-<b>presentation</b> element describes presentation-related attributes that describe how
-pages will be shown.  The page id for the intro home page (in <b>full mode</b>) must be specified,
-and the standby page id (in <b>standby mode</b>) is optional.  The home page is the page that is shown when the product is first started.
-A presentation can specify one or more <b>implementations</b> for showing the pages.  Implementations are specified
-per platform and windowing system, allowing you to take advantage of platform-specific features for showing
-page content. For example, the windows platform has a robust HTML browser widget, so an HTML-based implementation
-is used for intro content.  Other platforms without this capability use an SWT-based implementation that maps
-page descriptions to an SWT-based form.  An implementation that does not specify either a windowing system or operating system will be considered
-the generic implementation; to ensure an intro is shown on all platforms, it is important to define
-such an implementation.  The workbench will first look for an implementation that matches the current operating system and
-windowing system.  If one cannot be found, it will choose the generic implementation.  Most of these details
-are handled at the product configuration level, so we won't discuss them any further here.
-</p>
-<h4>&nbsp;</h4>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_custom_url.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_custom_url.htm
deleted file mode 100644
index 6681dcc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_custom_url.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Defining a custom IntroURL action</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Defining a custom IntroURL action</h3>
-<p>
-Using the <b><a href="../reference/extension-points/org_eclipse_ui_intro_configExtension.html">org.eclipse.ui.intro.configExtension</a></b>
-extension point, plug-ins can contribute their own custom actions that can be used as a <b>url</b> value for a link element in a page.
-For example, consider the following link:
-</p>
-<p><tt>http://org.eclipse.ui.intro/runAction?pluginId=org.eclipse.pde.ui&amp;class=org.eclipse.pde.ui.internal.samples.ShowSampleAction&amp;id=org.eclipse.sdk.samples.swt.examples</tt></p>
-<p>This IntroURL will run an action class called <b>ShowSampleAction</b>, which is in a package "org.eclipse.pde.ui.internal.samples" in the plug-in
-"org.eclipse.pde.ui".  The id of the sample to run is "org.eclipse.sdk.samples.swt.examples".
-</p>
-<p>To define a custom version of this intro URL, you can use the following markup:</p>
-<pre>&lt;extension point="org.eclipse.ui.intro.configExtension"&gt;
-	&lt;action
-		name="myCommand"
-		<b>replaces="runAction?pluginId=org.eclipse.pde.ui&amp;class=org.eclipse.pde.ui.internal.samples.ShowSampleAction"</b>&gt;
-	&lt;/action&gt;
-&lt;/extension&gt;
-</pre>
-With the above extension you can now use the following URL to run the same action:
-<p><tt>http://org.eclipse.ui.intro/myCommand?id=org.eclipse.sdk.samples.swt.examples</tt></p>
-<p>
-The action "myCommand" will be replaced by the value of the <b>replaces</b> attribute and any remaining URL
-parameters will be appended to the end.  Once the substitution is made, the resulting URL will be expanded back into:</p>
-<p><tt>http://org.eclipse.ui.intro/runAction?pluginId=org.eclipse.pde.ui&amp;class=org.eclipse.pde.ui.internal.samples.ShowSampleAction&amp;id=org.eclipse.sdk.samples.swt.examples</tt></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_standbypart.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_standbypart.htm
deleted file mode 100644
index 01606ae..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_standbypart.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Contributing a standby content part</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Contributing a standby content part</h3>
-<p>
-Plug-ins can also implement a part for displaying alternative content when the intro page is in standby mode.  For
-example, the platform defines a standby part that will show a cheat sheet for related intro content.  The part is launched using a page
-link with a specialized URL.  Standby parts are launched using a URL containing a special command for showing
-a standby part, such as <tt>http://org.eclipse.ui.intro/showStandby?partId=somePartId</tt>.
-The part is defined in the <b>standbyContentPart</b> subelement in the 
-<b><a href="../reference/extension-points/org_eclipse_ui_intro_configExtension.html">org.eclipse.ui.intro.configExtension</a></b>
-extension. An <b>id</b>, <b>pluginId</b>, and <b>class</b> must be specified for the part.  The class must implement
-<a href="../reference/api/org/eclipse/ui/intro/config/IStandbyContentPart.html"><b>IStandbyContentPart</b></a>.
-The following snippet shows how the platform defines a standby part for showing cheat sheets.
-</p>
-<pre>&lt;extension point="org.eclipse.ui.intro.configExtension"&gt;
-	&lt;standbyContentPart
-		id="org.eclipse.platform.cheatsheet"
-		class="org.eclipse.platform.internal.CheatSheetStandbyContent"
-		pluginId="org.eclipse.platform"/&gt;
-&lt;/extension&gt;
-</pre>
-This cheat sheet could be launched from an intro page using a <b>link</b> subelement whose
-URL is <tt>http://org.eclipse.ui.intro/showStandby?partId=org.eclipse.platform.cheatsheet&amp;input=org.eclipse.pde.helloworld</tt>.
-This IntroURL would launch the org.eclipse.platform.cheatsheet standby content part and set its input to
-"org.eclipse.pde.helloworld".  The detailed mechanics for implementing a standby part are beyond the scope
-of this discussion.   See <a href="../reference/api/org/eclipse/ui/intro/config/IStandbyContentPart.html"><b>IStandbyContentPart</b></a>
-and its related classes for more information.
-<h5>&nbsp;</h5>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending.htm
deleted file mode 100644
index 14c03f1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Extending an intro config</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Extending an intro config</h3>
-<p>
-An intro configuration can be extended in three ways:
-</p>
-<ul>
-<li>content of an existing intro config can be extended.</li>
-<li>a custom standby content part, such as Cheat Sheet, can be contributed to provide 
-content for the standby area of the Intro part.</li>
-<li>custom IntroURL actions can be defined.</li>
-</ul>
-<h5>&nbsp;</h5>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending_content.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending_content.htm
deleted file mode 100644
index e4e1ce1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending_content.htm
+++ /dev/null

@@ -1,78 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Extending the content of an intro config</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Extending the content of an intro config</h3>
-<p>
-Plug-ins can contribute intro content to a page defined elsewhere.  However, the defining page must define an
-<b>anchor</b> attribute that acts as a location placeholder for new content.  The SDK overview page defines
-two anchors for adding JDT and PDE related elements on the overview page.
-</p>
-<pre> &lt;group id="page-content"&gt;
-	&lt;text style-id="page-title" id="page-title"&gt;OVERVIEW&lt;/text&gt;
-	&lt;text style-id="page-description" id="page-description"&gt;Eclipse is a kind of universal tool platform - an open extensible IDE for anything and nothing in particular. It provides a feature-rich development environment that allows the developer to efficiently create tools that integrate seamlessly into the Eclipse Platform.&lt;/text&gt;
-	&lt;group id="overview-links"&gt;
-		&lt;link label="Workbench basics" url="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.platform.doc.user/concepts/concepts-2.htm" id="basics"&gt;
-			&lt;text>Learn about basic Eclipse workbench concepts&lt;/text&gt;
-        &lt;/link&gt;
-        &lt;link label="Team support" url="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.platform.doc.user/concepts/concepts-26.htm" id="team"&gt;
-			&lt;text&gt;Find out how to collaborate with other developers&lt;/text&gt;
-        &lt;/link&gt;
-		<b>&lt;anchor id="jdtAnchor"/&gt;
-		&lt;anchor id="pdeAnchor"/&gt;</b>
-	&lt;/group&gt;
-&lt;/group&gt;
-</pre>
-These anchors can be referenced by plug-ins that add content to the page.  Content is added using the
-<b><a href="../reference/extension-points/org_eclipse_ui_intro_configExtension.html">org.eclipse.ui.intro.configExtension</a></b>
-extension.  In addition to extending page content, this extension point also allows one to contribute standby content
-parts and custom actions.
-<p>
-To extend an existing intro config, you can use the <b>configExtension</b> element.  In this element,
-you specify the <b>configId</b> of the intro config being extended and the <b>content</b> file that describes the new
-content.
-</p>
-<pre>&lt;extension
-	point="org.eclipse.ui.intro.configExtension"&gt;
-	&lt;configExtension
-		configId="org.eclipse.platform.introConfig"
-		content="$nl$/overviewExtensionContent.xml"/&gt;  
-    ...
-&lt;/extension&gt;
-</pre>
-The format of the content file is similar to that of the intro config content, except that it must
-contain an <b>extensionContent</b> element that defines the path to the anchor where the extension content
-should be inserted.
-<pre>
-&lt;introContent&gt;
-	&lt;extensionContent alt-style="css/swt.properties" style="css/overview.css" <b>path="overview/page-content/overview-links/jdtAnchor"</b>&gt;
-		&lt;link label="Java development" url="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.jdt.doc.user/gettingStarted/qs-BasicTutorial.htm" id="java"&gt;
-			&lt;text&gt;Get familiar with developing Java programs using Eclipse&lt;/text&gt;
-		&lt;/link&gt;
-	&lt;/extensionContent&gt;
-&lt;/introContent&gt;
-</pre>
-After contributing custom content to an intro's predefined anchor points, a given product can bind itself to that
-intro using the <b><a href="../reference/extension-points/org_eclipse_ui_intro.html">org.eclipse.ui.intro</a></b>
-discussed above.  When the product is run, the intro that was extended will be shown with the additional
-content.  This allows the product to have its own branding and other product-specific information, while reusing
-a closely related product's intro along with key content of its own.
-<p>A given intro could also selectively include pieces of a related product's intro.  In this case, the product could define its
-own intro and intro config, and then reference important elements defined in another intro's config
-using an <b>include</b> in the content file.  This mechanism is valuable in situations where related products
-are built on top of one another and it is necessary to introduce users to key concepts in the higher level
-products.</p>
-<h5>&nbsp;</h5>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_hello_world.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_hello_world.htm
deleted file mode 100644
index 4066da2..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_hello_world.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Contributing a HelloWorld Intro Part</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Contributing a HelloWorld Intro Part</h3>
-<p>
- We will now contribute a very basic intro part just to illustrate the steps needed to contribute a part implementation to the Workbench and get it to show up as the welcome page. To do this:</p>
-<ol>
-  <li>use the <em>org.eclipse.ui.intro </em> extension point to register an intro part implementation and bind this intro part to your product.</li>
-  <li>implement the <em>org.eclipse.ui.intro.IIntroPart </em> interface and use this class as the class attribute in the above extension point contribution.</li>
-  <li>run your Eclipse based product with the correct product id. </li>
-</ol>
-<p> Here is the <em>org.eclipse.ui.intro </em>extension point registration needed: </p>
-<pre>
-
-&lt;extension point="org.eclipse.ui.intro"&gt; 
-	&lt;intro class="org.eclipse.ui.intro.HelloWorldIntroPart" &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-		id="org.eclipse.ui.intro.examples.basic001_introId" &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-		icon="some_icon.jpg"/&gt;
-	&lt;introProductBinding
-		introId="org.eclipse.ui.intro.HelloWorld_introId" &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-		productId="org.eclipse.ui.intro.HelloWorld_product"&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-	&lt;/introProductBinding&gt;
-&lt;/extension&gt; 
-</pre>
-<p>An <em>intro </em> part is registered with the workbench. The class that implements this intro part is <em>org.eclipse.ui.intro..HelloWorldIntroPart </em>. An icon is also registered with the intro part and it will appear at the top right corner of the intro part window. An <em>introProductBinding </em> contribution tells the workbench that the intro part we just created is bound to our product with the id <em>org.eclipse.ui.intro.HelloWorld_product</em>. On startup, the workbench looks for the first intro bound to the current product, and instantiates the class registered with this intro contribution.</p>
-<p>The second step is to implement the <em>org.eclipse.ui.intro.IIntroPart </em> interface. The following is sample code that simply creates a label and centers it in the parent composite. This code can be used to actually create the IntroPart:</p> 
-<pre>public void <strong>createPartControl </strong>(Composite container) { &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-		Composite outerContainer = new Composite(container, SWT.NONE); &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-		GridLayout gridLayout = new GridLayout(); &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-		outerContainer.setLayout(gridLayout); &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-		outerContainer.setBackground
-			(outerContainer.getDisplay().getSystemColor(SWT.COLOR_TITLE_BACKGROUND_GRADIENT)); &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-		label = new Label(outerContainer, SWT.CENTER); &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-		label.setText("WELCOME TO ECLIPSE"); &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-		GridData gd = new GridData(GridData.GRAB_HORIZONTAL | GridData.GRAB_VERTICAL); &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-		gd.horizontalAlignment = GridData.CENTER; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-		gd.verticalAlignment = GridData.CENTER;
-		label.setLayoutData(gd); &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-		label.setBackground(outerContainer.getDisplay().
-				getSystemColor(SWT.COLOR_TITLE_BACKGROUND_GRADIENT)); &nbsp;&nbsp;&nbsp; 
-			
-		}
-
-</pre>
-<p> The third and last step is to make sure you run the correct product. For example, if you are self hosting, create a new runtime-workbench launch configuration, choose the "Run a product" option, and select <em>org.eclipse.ui.intro.HelloWorld_product </em>from the dropdown. <br>
-This is what you will see if you run the above HelloWorld sample:</p>
-<p align="center">	 <img src="images/basicIntro.png" width="519" height="348" border="0"></p>
-<p>Note that the intro part is in control of the full real-estate of the window. A more elaborate intro part can be created that interacts with the workbench and progressively reveals the functionality of the product. <br>
-  <br>
-</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_xhtml.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_xhtml.htm
deleted file mode 100644
index 71a2643..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_xhtml.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Using XHTML as intro content</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Using XHTML as intro content</h3>
-<p>Depending on the usage scenario of the intro framework,  XHTML files can be contributed as intro content. <span id="tooltip1" style="position: relative; display:none;" onclick="FP_changeProp(/*id*/'tooltip1',0,'style.display','none')"> <font color="#0000FF" style="cursor: hand;">(A reformulation of the three HTML 4 document types as applications of XML 1.0. For M5, only XHTML 1.0 is supported. XHTML 1.1 (module-based XHTML) can be supported, based on fee</font></span>The idea is to use the fact that XHTML is well formed XML and parse each document, manipulating the DOM to allow for contributions and extensions to be merged. Three xml elements from the 3.0 intro markup where used to extend the XHTML 1.0 element list. These where <code>include</code>, <code>anchor</code>, and <code> contentProvider</code>. </p>
-<ul>
-  <li>&nbsp;<code><b>include</b>: </code>this element can be added to a valid XHTML document to include content from another XHTML document. The content to be included must be a valid XHTML snippet.</li>
-</ul>
-<blockquote>
-  <dl>
-    <dd>e.g.: <code>&lt;include path=&quot;root/foo&quot; /&gt;</code> will include an element with id <code>foo</code> from a welcome page with id <code>root</code>. </dd>
-  </dl>
-</blockquote>
-<ul>
-  <li>&nbsp;<code><b>anchor</b>: </code>this element can be added to a valid XHTML document to declare that content can be contributed to this page by other welcome contributions. A page declares locations that are suitable to be extended by defining these anchor points.</li>
-</ul>
-<blockquote>
-  <dl>
-    <dd>e.g.: <code>&lt;anchor id=&quot;anchor1&quot; /&gt;</code> will allow for contribution into this page from other plugins. </dd>
-  </dl>
-</blockquote>
-<ul>
-  <li><code><b>contentProvider</b>: </code>this element can be added to a valid XHTML document to establish a hook into the workbench. When the intro framework encounters this element, an interface is called allowing for the manipulation of the DOM of the XHTML page. &nbsp;&nbsp; </li>
-</ul>
-<dl>
-  <dd>
-    <dl>
-      <dd>e.g.: <code>&lt;contentProvider id=&quot;contentProviderId&quot; class=&quot;org.eclipse.ui.intro.template2.IntroXHTMLContentProvider&quot; pluginId=&quot;org.eclipse.ui.intro.template2&quot;&gt; &lt;/contentProvider&gt; <br>
-      </code>&nbsp;will allow for dynamic content to be generated from the <code> org.eclipse.ui.intro.template2.IntroXHTMLContentProvider</code> class.</dd>
-    </dl>
-  </dd>
-</dl>
-<p>With these three elements, XHTML pages can be used to assemble a pluggable and dynamic welcome pages, just like what used to happen with the custom intro xml markup. PDE has a new template that allow for the creation of a sample RCP application with an Intro. That template is a good sample project for using Intro. </p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench.htm
deleted file mode 100644
index 178d384..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench.htm
+++ /dev/null

@@ -1,75 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Plugging into the workbench
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Plugging into the workbench</H1>
-<P >
-By now, you should be quite familiar with the operation of the workbench and how it uses views and editors to display information.
-If not, read the quick tour of the workbench below.</P>
-<P >
-The sections following the quick tour will look at the workbench user interface from an API
-perspective.&nbsp; We will show how a plug-in can contribute to the workbench
-UI.</P>
-<h2>
-Quick tour of the workbench</h2>
-<P >
-The workbench is the cockpit for navigating all of the function provided by plug-ins.
-By using the workbench, we can navigate resources and we can view and edit
-the content and properties of these resources. </P>
-<P >
-When you open your workbench on a set of projects, it looks something like this.</P>
-
-<p align="left"><img src="images/workbench.png" alt="Workbench with navigator view, editor, outliner, and task list" border="0" ></p>
-<P >
-The workbench is just a frame that can present various visual parts. These parts fall into two major categories:
-<b> views</b> and <b>editors</b>.</P>
-<ul>
-  <li>
-<b>
-Editors</b> allow the user to edit something in the workbench. Editors are &quot;document-centric,&quot; much like a file system editor.
-Like file system editors, they follow an open-save-close lifecycle.&nbsp; Unlike
-file system editors, they are tightly integrated into the workbench.</li>
-  <li>
-<b>
-Views</b> provide information about some object that the user is working with in the workbench. Views often change their content as the user selects different objects in the workbench.&nbsp;
-Views often support editors by providing information about the content in the
-active editor.</li>
-</ul>
-
-
-<h3>
-Views</h3>
-<P >
-The workbench provides several standard views that allow the user to navigate or view something of interest. For example, the resource navigator lets the user navigate the workspace and select resources.</P>
-
-<img src="images/navigator.png" alt="" border="0">
-
-
-
-<h3>
-Editors</h3>
-<P >
-Editors allow the user to open, edit, and save objects. The workbench provides a standard editor for text resources.</P>
-
-<img src="images/texteditor.png" alt="" border="0">
-<P >
-Additional editors, such as Java code editors or HTML editors, can be supplied by
-plug-ins</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_actionfilters.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_actionfilters.htm
deleted file mode 100644
index 9a18529..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_actionfilters.htm
+++ /dev/null

@@ -1,242 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Boolean expressions and action filters
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Boolean expressions and action filters</H2>
-<p>
-When a plug-in contributes an action to the workbench UI using one of the menu
-extension points, it can specify the conditions under which the menu item is
-visible and/or enabled in the menu. In addition to supplying simple enabling
-conditions, such as selection counts and selection classes, plug-ins can use <b>boolean
-expressions</b> for more flexibility in determining when an action should be visible or enabled.</p>
-
-
-<h3>Boolean enablement expressions</h3>
-<p>Boolean expressions can contain the boolean operators (NOT, AND, OR) combined with a predefined syntax
-for evaluating certain conditions.  Many of these conditions test a particular object.  The identity of the
-"object in focus" (the object being tested) depends upon the specific context of the enablement expression:
-</p>
-<ul>
-<li><b>instanceof</b> tests whether the type of the object in focus is a subtype of the specified type name.</li>
-<li><b>test</b> tests whether the value of a named property of the object in focus matches the specified value.</li>
-<li><b>systemTest</b> tests whether the value of a named system property matches the specified value. </li>
-<li><b>equals</b> tests whether the object in focus is equal to the specified value.</li>
-<li><b>count</b> tests the number of elements in a list.</li>
-<li><b>with</b> changes the object in focus to the object referenced by a supplied variable.</li>
-<li><b>resolve</b> changes the object in focus to the object referenced by a supplied variable, supplying additional
-arguments with the variable.</li>
-<li><b>adapt</b> adapts the object in focus to the type specified.</li>
-<li><b>iterate</b> iterates over a variable that is a collection and combines the boolean value of each value using AND or OR.</li>
-</ul>
-<p>
-When specifying a value to be tested against any of these expressions, the value is assumed to be a string except for when
-the following conversions are successful:
-</p>
-<ul>
-<li>the string "true" is converted into Boolean.TRUE</li>
-<li>the string "false" is converted into Boolean.FALSE</li>
-<li>if the string contains a dot, the interpreter tries to convert the value into a Float object</li>
-<li>if the string only consists of numbers, the interpreter converts the value into an Integer object</li>
-<li>the conversion into a Boolean, Float, or Integer can be suppressed by surrounding the string with single quotes.</li>
-</ul>
-<p>A complete definition of enablement XML syntax can be found in the extension point reference documentation for any
-extension that defines an <b>enablement</b> element, such as
-<b><a href="../reference/extension-points/org_eclipse_ui_popupMenus.html#e.enablement"> org.eclipse.ui.popupMenus</a></b>.
-</p>
-<p>Prior to R3.0, these generalized boolean expressions were not available.  The following predefined expressions were used to
-evaluate certain conditions without building a general expression.  Note that any of these expressions could now be expressed with
-the more generalized syntax.  The predefined expressions can still be used as follows:</p>
-<ul>
-  <li>
-    <p><b>objectClass</b> - true if each object in the
-    selection subclasses or implements the class.</p>
-  </li>
-  <li>
-    <p><b>objectState</b> - true if the named attribute equals the specified value.&nbsp; <b><a href="../reference/api/org/eclipse/ui/IActionFilter.html">IActionFilter</a>
-    </b>assists in evaluating the expression.&nbsp; An action filter dynamically computes the enablement
-criteria for an action based on the target selection and the value of named
-attributes.</p>
-  </li>
-  <li>
-    <p><b>systemProperty</b> - true if the named system
-    property equals the specified value.</p>
-  </li>
-  <li>
-    <p><b>pluginState</b> - specifies whether the specified
-    plugin (by <b>id</b>) should be <b>installed</b> or <b>activated</b> </p>
-  </li>
-</ul>
-    <p>For example, the following snippets represent enablement
-    expressions that could be used on a hypothetical action in an action set: </p>
-    <pre>&lt;action id=&quot;org.eclipse.examples.actionEnablement.class&quot; 
-       label=&quot;Red Element&quot; 
-       menubarPath=&quot;additions&quot; 
-       class=&quot;org.eclipse.examples.actionEnablement.ObjectTestAction&quot;&gt; 
-       &lt;enablement&gt; 
-<b>	 &lt;and&gt;
-	   &lt;objectClass name=&quot;org.eclipse.examples.actionEnablement.TestElement&quot;/&gt; 
-           &lt;objectState name=&quot;name&quot; value=&quot;red&quot;/&gt; 
-	 &lt;/and&gt;
-</b>       &lt;/enablement&gt; 
-&lt;/action&gt;</pre>
-    <pre>&lt;action id=&quot;org.eclipse.examples.actionEnablement.property&quot; 
-       label=&quot;Property&quot; 
-       menubarPath=&quot;additions&quot; 
-       class=&quot;org.eclipse.examples.actionEnablement.PropertyTestAction&quot;&gt; 
-       &lt;enablement&gt; 
-<b>           &lt;systemProperty name=&quot;MyTestProperty&quot; value=&quot;puppy&quot;/&gt; 
-</b>       &lt;/enablement&gt; 
-&lt;/action&gt; </pre>
-    <pre>&lt;action id=&quot;org.eclipse.examples.actionEnablement.pluginState&quot; 
-       label=&quot;Installed&quot; 
-       menubarPath=&quot;additions&quot; 
-       class=&quot;org.eclipse.examples.actionEnablement.PluginTestAction&quot;&gt; 
-       &lt;enablement&gt; 
-           <b>&lt;pluginState id=&quot;x.y.z.anotherPlugin&quot; value=&quot;installed&quot;/&gt; </b>
-       &lt;/enablement&gt; 
-&lt;/action&gt; </pre>
-<p>See the reference documentation of the extension points
-for more elaborate samples of these expressions and a complete description of
-the XML.</p>
-
-
-<p>
-The following table lists extension points that contribute actions and
-summarizes how XML markup attributes and boolean expressions can be used to
-affect enablement.</p>
-
-
-<TABLE BORDER="1" width="671">
-<TR>
-<TH ROWSPAN="1" COLSPAN="1" width="118">
-<P CLASS="CellHeading">
-Extension point name</p>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1" width="359">
-<P CLASS="CellHeading">
-Attributes affecting enablement</p>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1" width="335">
-<P CLASS="CellHeading">
-Boolean expressions</p>
-</TH>
-</TR>
-<TR>
-<TD width="118">
-<p>
-<b>
-<a href="../reference/extension-points/org_eclipse_ui_viewActions.html">
-viewActions</a></b>,</p>
-<p><b><a href="../reference/extension-points/org_eclipse_ui_editorActions.html">editorActions</a></b>,</p>
-<p><b><a href="../reference/extension-points/org_eclipse_ui_actionSets.html">actionSets</a></b></p>
-</TD>
-<TD width="359">
-<p>
-<b>enablesFor</b> - specifies the selection count that must be met for the
-action to be enabled</p>
-<p>
-<b>selection</b> <b>class</b> - the class that the selected objects must
-subclass or implement in order for the action to be enabled</p>
-<p>
-<b>selection</b> <b>name</b> - a wild card filter that can be applied to the
-objects in the selection.</p>
-</TD>
-<TD width="335">
-<p>
-<b>visibility</b> - a boolean expression.&nbsp; Controls whether the menu item
-is visible in the menu.</p>
-<p>
-<b>enablement</b> - a boolean expression.&nbsp; Controls whether the menu item
-is enabled in the menu.&nbsp; The <b>enablesFor</b>  attribute and the <b>selection</b> <b>class</b>
-and <b>name</b>, and must be
-satisfied before applying the enablement expression.</p>
-</TD>
-</TR>
-<TR>
-<TD width="118">
-<p>
-<b>
-<a href="../reference/extension-points/org_eclipse_ui_popupMenus.html">
-popupMenus</a></b></p>
-</TD>
-<TD width="359">
-<p>
-(For object contributions only.)</p>
-<p>
-<b>objectClass</b> - specifies the class that objects in the selection must
-subclass or implement</p>
-<p>
-(For both object and viewer contributions)</p>
-<p>
-<b>enablesFor</b> - specifies the selection count that must be met for the
-action to be enabled</p>
-<p>
-<b>selection</b> <b>class</b> - the class that the selected objects must
-subclass or implement to enable the action</p>
-<p>
-<b>selection</b> <b>name</b> - a wild card filter that can be applied to the
-objects in the selection.</p>
-<p>
-&nbsp;</p>
-</TD>
-<TD width="335">
-<p>
-(For both object and viewer contributions)</p>
-<p>
-<b>visibility</b> - a boolean expression.&nbsp; Controls whether the menu item
-is visible in the menu.</p>
-<p><b>enablement</b> - a boolean expression.&nbsp; Controls
-whether the menu item is enabled in the menu.&nbsp;
-The <b>enablesFor</b>  attribute and the <b>selection</b> <b>class</b> and <b>name</b>, and must be
-satisfied before applying the enablement expression.</p>
-</TD>
-</TR>
-</TABLE>
-
-<h3>Using objectState with content types</h3>
-<p>The ability to define content types (see <a href="runtime_content.htm">Content types</a>) can be combined
-with boolean expressions to define very specific enablement or visibility conditions based on
-the content type of a resource.  For example, the following snippet makes a popup menu item visible only if the
-selected file's content matches the plug-in's specialized content types.
-</p>
-<pre>
-&lt;extension point="org.eclipse.ui.popupMenus"&gt;
-   &lt;objectContribution
-      id="com.example.objectContributions"
-      objectClass="org.eclipse.core.resources.IFile"
-      nameFilter="*.xml"&gt;
-         &lt;visibility&gt;
-            &lt;or&gt;
-               &lt;objectState
-                  <b>name="contentTypeId"</b>
-                  value="com.example.employeeRecordContentType"/&gt;
-               &lt;objectState
-                  <b>name="contentTypeId"</b>
-                  value="com.example.customerRecordContentType"/&gt;
-            &lt;/or&gt;
-         &lt;/visibility&gt;
-         &lt;action id="com.example.action1"
-         ...
-</pre>
-The <b>contentTypeId</b> attribute can be used in an objectState expression to check the content type of
-the selected xml file.  This allows a plug-in to apply very specific content checking before enabling or showing
-menu actions related to specific types of files.  See <a href="runtime_content.htm">Content types</a> for more detail
-about the content type extension.
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_activities.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_activities.htm
deleted file mode 100644
index 74ff61b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_activities.htm
+++ /dev/null

@@ -1,231 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Activities</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>
-Activities</h3>
-<P >
-An <b>activity</b> is a logical grouping of function that is centered around a certain kind of task.  For
-example, developing Java software is an activity commonly performed by users of the platform, and the JDT 
-defines many UI contributions (views, editors, perspectives, preferences, etc.) that are only useful when performing
-this activity.  Before we look at the mechanics for defining  an activity, let's look at how they are used to help
-&quot;declutter&quot; the UI.
-</P>
-<p>
-The concept of an activity is exposed to the user, although perhaps not apparent to a new user.  When an activity
-is enabled in the platform, the UI contributions associated with that activity are shown.  When an activity is disabled
-in the platform, its UI contributions are not shown.  Users can enable and disable activities as needed using the
-<b>Workbench&gt;Capabilities</b> preference page.  (Activities are referred to as "capabilities" in the user interface,
-even though we use activity terminology in the API).
-</p>
-<p>Certain user
-operations serve as <b>trigger points</b> for enabling an activity.  For example, creating a new Java project could
-trigger the enabling of the Java development activity.  In this way, users are exposed to new function as they need it, and
-gradually learn about the activities that are available to them and how they affect the UI.  When a user first starts the 
-platform, it is desirable for as many activities as possible to be disabled, so that the application is as simple as 
-possible.  Choices made in the welcome page can help determine what activities should be enabled.
-</p>
-<h3>Activities vs. perspectives</h3>
-<p>
-We've seen (in <a href="workbench_perspectives.htm">Perspectives</a>) how perspectives are used to organize different 
-view layouts and action sets into tasks.  Why do we need activities?  While perspectives and activities define similar 
-kinds of tasks, the main difference is how the UI contributions for a plug-in are associated with them.  UI 
-contributions are associated with perspectives in the extension definition of the contribution.  That is, a plug-in is 
-in charge of determining what perspectives its views and action sets belong to.  Plug-ins are also free to define their 
-own perspectives.  Even when a perspective is not active, the user can access the views and actions associated with the 
-perspective through commands such as <b>Show View</b>.  
-</p>
-<p>Activities are a higher level of organization.  Individual UI contributions are not aware of activities and
-do not refer to the activities in their extension definitions.  Rather, the activities are expected to be configured 
-at a higher level such as platform integration/configuration or product install. Individual plug-ins typically do not define new activities, 
-unless the plug-in is a systems-level plug-in defined by a systems integrator.  In a typical scenario, a systems 
-integrator determines how function is grouped into activities and which ones are enabled by default.  Activities are
-associated with UI contributions using <b>activity pattern bindings</b>, patterns that are matched
-against the id of the UI contributions made by plug-ins. An example will help demonstrate these concepts.  
-</p>
-<h4>Defining an activity</h4>
-<p>
-Activities are defined using the 
-<b><a href="../reference/extension-points/org_eclipse_ui_activities.html">org.eclipse.ui.activities</a></b>
-extension point.  Let's look at a simplified version of how the Eclipse SDK plug-in defines two activities -
-one for developing Java software and one for developing plug-ins:</p>
-<pre>&lt;extension
-	point="org.eclipse.ui.activities"&gt;
-	&lt;activity
-		name="Java Activity"
-		description="Developing Java Software"
-		id="org.eclipse.javaDevelopment"&gt;
-	&lt;/activity&gt;
-	
-	&lt;activity
-		name="Plug-in Activity"
-		description="Developing Eclipse Plug-ins"
-		id="org.eclipse.plugInDevelopment"&gt;
-	&lt;/activity&gt;
-	...
-</pre>
-<p>Activities are assigned a name and description that can be shown to the user whenever the user is enabling and disabling
-activities, or otherwise shown information about an activity.  The id of the activity is used when defining
-pattern bindings or other relationships between activities.  For example, we can decide that one activity requires
-another activity.</p>
-<pre>&lt;activityRequirementBinding
-	activityId="org.eclipse.plugInDevelopment"
-	requiredActivityId="org.eclipse.javaDevelopment"&gt;
-&lt;/activityRequirementBinding&gt;
-</pre>
-<p>The requirement binding states that the plug-in development activity can only be enabled when the Java development 
-activity is enabled.  Related activities can also be bound into <b>categories</b>, that are shown to the user when
-the user is working with activities.</p>
-<pre>&lt;category
-	name="Development"
-	description="Software Development"
-	id="org.eclipse.categories.developmentCategory"&gt;
-&lt;/category>
-
-&lt;categoryActivityBinding
-	activityId="org.eclipse.javaDevelopment"
-	categoryId="org.eclipse.categories.developmentCategory"&gt;
-&lt;/categoryActivityBinding>
-      
-&lt;categoryActivityBinding
-	activityId="org.eclipse.plugInDevelopment"
-	categoryId="org.eclipse.categories.developmentCategory"&gt;
-&lt;/categoryActivityBinding&gt;
-</pre>
-<p>The category groups the related development activities together.  This category is shown to the user when the user
-manually configures activities.</p>
-<h4>Binding activities to UI contributions</h4>
-<p>
-Activities are associated with UI contributions using pattern matching.  The pattern matching used in
-activity pattern bindings follows the rules described in the <b>java.util.regex</b> package for regular expressions.
-The patterns used by the workbench are composed of two parts.  The first part uses the identifier of the plug-in 
-that is contributing the UI extension.  The second part is the id used by plug-in itself when defining
-the contribution (which may or may not also include the plug-in id as part of the identifier).  
-The following format is used:
-</p>
-<pre>
-plug-in-identifier + &quot;/&quot; + local-identifier
-</pre>
-For example, the following activity pattern binding states that a UI contribution from any
-JDT plug-in id (<tt>org.eclipse.jdt.*</tt>) is associated with the Java development activity regardless
-of its local identifier (<tt>.*</tt>).
-<pre>
-&lt;activityPatternBinding
-	activityId="org.eclipse.javaDevelopment"
-	pattern="org\.eclipse\.jdt\..*/.*"&gt;
-&lt;/activityPatternBinding&gt;
-</pre>
-The next binding is more specific.  It states that the contribution named <tt>javanature</tt> defined in the
-JDT core (<tt>org.eclipse.jdt.core</tt>) is associated with the Java development activity.
-<pre>
-&lt;activityPatternBinding
-	activityId="org.eclipse.javaDevelopment"
-	pattern="org\.eclipse\.jdt\.core/javanature"&gt;
-&lt;/activityPatternBinding&gt;
-</pre>
-As you can see, activity pattern bindings can be used to associate large groups of contributions with a particular activity,
-or to associate very specific contributions to an activity.  The following contributions are affected by activities:
-<ul>
-<li>Views and editors</li>
-<li>Perspectives</li>
-<li>Preference and property pages</li>
-<li>Menus and toolbars</li>
-<li>New project wizard</li>
-</ul>
-
-<p>The convention used by the workbench (plug-in id + local id) allows easy binding to plug-ins that do not
-necessarily follow the naming practice of prefixing their UI contribution identifiers with their plug-in's identifier.
-Plug-ins that directly interact with the activity API are free to use their own format for identifying
-contributions and for pattern-matching against those names.
-</p>
-<h4>Binding activities to help contributions</h4>
-<p>
-Activities are associated with help contributions using the same pattern matching scheme used
-for UI contributions.  The second part of the identifier (the local identifier)
-indicates the name of the table of contents (TOC) file.
-For example, the following activity pattern binding associates all TOC files
-contributed by JDT plug-ins (org.eclipse.jdt.*) with the Java development activity:
-</p>
-<pre>
-&lt;activityPatternBinding
-	activityId="org.eclipse.javaDevelopment"
-	pattern="org\.eclipse\.jdt\..*/.*"&gt;
-&lt;/activityPatternBinding&gt;
-</pre>
-When the Java development activity is disabled, help books contributed by JDT plug-ins,
-or any sub-books (TOCs linked to, or linked by JDT books), even if contributed
-by a different plug-in, will not show in the help UI.  The topics defined in these books
-will also not show in the search results.  In the case where JDT TOCs were not displayed
-as primary TOCs, but were instead linked from another TOC to appear as sub-trees in a book,
-disabling the JDT activity has the effect of hiding the sub-trees.  The containing book will
-appear to define less topics in the UI.
-
-<p>
-Using more specific binding, it is possible to associate activities with selected TOCs from plug-ins
-that contribute multiple TOCs to the help system.  For example, the following
-activity pattern binding associates the "Examples" TOC with the Java development examples activity.
-</p>
-<pre>
-&lt;activityPatternBinding
-	activityId="org.eclipse.javaDevelopmentExamples"
-	pattern="org\.eclipse\.jdt\.doc\.isv\.topics_Samples.xml"&gt;
-&lt;/activityPatternBinding&gt;
-</pre>
-With such pattern binding, disabling the Java development examples activity will
-hide the "Examples" section from the "JDT Plug-in Developer Guide" book.
-
-<h4>Using the activities API</h4>
-<p>
-The workbench activity support includes an API for working with the defined activities and changing their 
-enabled state.  Most plug-ins need not be concerned with this API, but it is useful when implementing function that
-allows the user to work with activities, or for implementing the trigger points that enable a particular activity.
-It is assumed that any plug-in that is manipulating activities through API is quite aware of the ways that activities
-are configured for a particular product.  For example, the workbench itself uses the API to trigger the enablement of
-activities such as Java development.  We'll look at how the workbench uses the generic activity API to implement
-triggers.
-</p>
-<p>
-The hub of all activity in the workbench is <a href="../reference/api/org/eclipse/ui/activities/IWorkbenchActivitySupport.html"><b>IWorkbenchActivitySupport</b></a>.
-The activity support works in tandem with an 
-<a href="../reference/api/org/eclipse/ui/activities/IActivityManager.html"><b>IActivityManager</b></a>.
-Plug-ins can obtain the activity support instance from the workbench, and the activity manager from there.
-</p>
-<pre>
-IWorkbenchActivitySupport workbenchActivitySupport = PlatformUI.getWorkbench().getActivitySupport();
-IActivityManager activityManager = workbenchActivitySupport.getActivityManager();
-</pre>
-The following snippet enables the Java development activity (if it is not already enabled).  It shows a
-simplified version of a trigger.
-<pre>
-...
-//the user did something Java related.  Enable the Java activity.
-Set enabledActivityIds = new HashSet(activityManager.getEnabledActivityIds());
-if (enabledIds.add(&quot;org.eclipse.javaDevelopment&quot;))
-	workbenchActivitySupport.setEnabledActivityIds(enabledActivityIds);
-</pre>
-<p>
-<a href="../reference/api/org/eclipse/ui/activities/IActivityManager.html"><b>IActivityManager</b></a> also defines
-protocol for getting all defined activity and category ids, and for getting the associated 
-<a href="../reference/api/org/eclipse/ui/activities/IActivity.html"><b>IActivity</b></a> or
-<a href="../reference/api/org/eclipse/ui/activities/IActivity.html"><b>ICategory</b></a> for a particular id.
-These objects can be used to traverse the definition for an activity or category in API, such as getting the
-pattern bindings or requirement bindings.  Listeners can be registered on the activity manager or on the activities 
-and categories themselves to detect changes in the definition of a particular activity or in the activity manager
-itself.  See the package <b><a href="../reference/api/org/eclipse/ui/activities/package-summary.html">org.eclipse.ui.activities</a></b>
-for more information.
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_contexts.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_contexts.htm
deleted file mode 100644
index 7ac6d3b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_contexts.htm
+++ /dev/null

@@ -1,120 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Contexts</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>
-Contexts</h3>
-<P >
-A <b>context</b> can be used to influence what commands are available to the user at any given moment.
-Contexts are much more dynamic than activities.  While an activity represents a broad set of function that
-is available to the user most of the time, contexts describe a focus of the user at a specific point
-in time.  For example, the commands available to a user while editing text might be different than those
-available to a user while editing Java text or browsing packages in the package explorer.
-</P>
-<h4>Defining a context</h4>
-<p>
-Contexts are declared in the
-<b><a href="../reference/extension-points/org_eclipse_ui_contexts.html">org.eclipse.ui.contexts</a></b>
-extension point. Consider the following context which is defined for editing text:
-</p>
-<pre>&lt;extension
-	point="org.eclipse.ui.contexts"&gt;
-	&lt;context
-		name="%context.editingText.name"
-		description="%context.editingText.description"
-		id="org.eclipse.ui.textEditorScope"
-		parentId="org.eclipse.ui.contexts.window"&gt;
-	&lt;/context&gt;
-</pre>
-Contexts are assigned a name and description that are used when showing information about the context to the user.
-The id of the context is used when binding UI contributions such as commands to a particular context.
-<h4>Context hierarchies</h4>
-<p>
-Contexts are hierarchical in nature.  When a context is active, the commands available in the context and in its parent contexts
-are also available.  This is useful for defining levels of contexts that move from very general situations down to more
-specific contexts.  In the context definition above, note that there is an id of a parent assigned to the context:
-</p>
-<pre>	&lt;context
-		name="%context.editingText.name"
-		description="%context.editingText.description"
-		id="org.eclipse.ui.textEditorScope"
-		<b>parentId="org.eclipse.ui.contexts.window"</b>&gt;
-	&lt;/context&gt;
-</pre>
-The parent context defines the more general context of working within a window.  Its parent defines an even
-more general context of working within a window or a dialog.
-<pre>
-&lt;context
-	name="%context.window.name"
-	description="%context.window.description"
-	id="org.eclipse.ui.contexts.window"
-	<b>parentId="org.eclipse.ui.contexts.dialogAndWindow"</b>&gt;
-&lt;/context&gt;
-&lt;context
-	name="%context.dialogAndWindow.name"
-	description="%context.dialogAndWindow.description"
-	id="org.eclipse.ui.contexts.dialogAndWindow"&gt;
-&lt;/context&gt;
-</pre>
-<h4>Associating a contribution with a context</h4>
-<p>
-So far, all we've done is define a hierarchy of contexts.  The context becomes useful when it is referenced in the
-description of another UI contribution.  The most common use of contexts is in key bindings.  When a context is
-associated with a key binding, the key binding will only be active when the user is in that context.  For example,
-the following markup specifies the root dialog and window context as the context for a key binding:
-</p>
-<pre>&lt;keyBinding
-	commandId="org.eclipse.ui.edit.cut"
-	<b>contextId="org.eclipse.ui.contexts.dialogAndWindow"</b>
-	keySequence="M1+X"
-	keyConfigurationId="org.eclipse.ui.defaultAcceleratorConfiguration"&gt;
-&lt;/keyBinding&gt;
-</pre>
-<h4>
-Using Context API</h4>
-<p>
-The workbench context support includes an API for working with the defined contexts and defining
-criteria under which a particular context should become enabled.  Most plug-ins need not be 
-concerned with this API, but it is useful when defining specialized views or editors that define
-new contexts.  
-</p>
-<p>
-The starting point for working with contexts in the workbench is <a href="../reference/api/org/eclipse/ui/contexts/IWorkbenchContextSupport.html"><b>IWorkbenchContextSupport</b></a>.
-Plug-ins can obtain the context support instance from the workbench.  
-</p>
-<pre>IWorkbenchContextSupport workbenchContextSupport = PlatformUI.getWorkbench().getContextSupport();
-</pre>
-The workbench context support API can be used to add or remove an 
-<a href="../reference/api/org/eclipse/ui/contexts/EnabledSubmission.html"><b>EnabledSubmission</b></a>,
-which describes criteria that should cause a particular context to become enabled.  Criteria include
-information such as the active part or active shell.  The workbench support also provides access to an
-<a href="../reference/api/org/eclipse/ui/contexts/IContextManager.html"><b>IContextManager</b></a>.
-<pre>
-IContextManager contextManager = workbenchContextSupport.getContextManager();
-</pre>
-<p>
-<a href="../reference/api/org/eclipse/ui/contexts/IContextManager.html"><b>IContextManager</b></a> defines
-protocol for getting all defined or enabled context ids, and for getting the associated 
-<a href="../reference/api/org/eclipse/ui/contexts/IContext.html"><b>IContext</b></a> for a particular id.
-These objects can be used to traverse the definition for a context in API, such as getting the
-id, name, or id of the parent context.  Listeners can be registered on the context manager or on the contexts 
-themselves to detect changes in the definition of a particular context or in the context manager
-itself.  See the package <b><a href="../reference/api/org/eclipse/ui/contexts/package-summary.html">org.eclipse.ui.contexts</a></b>
-for more information.
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_decorators.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_decorators.htm
deleted file mode 100644
index 18650c5..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_decorators.htm
+++ /dev/null

@@ -1,156 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Decorators</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H3>
-Decorators</H3>
-
-<p>Your plug-in can use <b>decorators</b> to annotate the images for resources
-and other objects that appear in the workbench views.&nbsp; Decorators are
-useful when your plug-in adds functionality for existing resource types.&nbsp;
-Many of the standard workbench views participate in showing decorations.&nbsp;&nbsp;</p>
-
-
-<p>For example, PDE contributes decorators that allow you to distinguish between
-binary and source projects.</p>
-
-
-<p><img src="images/workbenchdecorators.png" alt="Package explorer view with PDE decorators" border="0"></p>
-
-
-<p>The <b>com.example.helloworld&nbsp; </b>project is the only source project
-shown in the navigator.&nbsp; Note how all of the other binary projects show the
-binary decorator at the top left of the Java project icon.&nbsp; This decorator
-is contributed by PDE using the <a href="../reference/extension-points/org_eclipse_ui_decorators.html"><b>org.eclipse.ui.decorators</b></a>
-extension point.</p>
-
-
-<pre>&lt;extension
-         point=&quot;org.eclipse.ui.decorators&quot;&gt;
-      &lt;decorator
-            <b>lightweight=&quot;true&quot;
-</b>            <b>quadrant=&quot;TOP_LEFT&quot;</b>
-            adaptable=&quot;true&quot;
-            label=&quot;%decorator.label&quot;
-            <b>icon=&quot;icons/full/ovr16/binary_co.png&quot;</b>
-            state=&quot;false&quot;
-            id=&quot;org.eclipse.pde.ui.binaryProjectDecorator&quot;&gt;
-         &lt;description&gt;
-            %decorator.desc
-         &lt;/description&gt;
-         &lt;enablement&gt;
-            ...
-         &lt;/enablement&gt;
-      &lt;/decorator&gt;
- &lt;/extension&gt;</pre>
-
-
-<p>There are several different ways to supply a decorator implementation.&nbsp;
-This markup uses the simplest way, known as a <b>declarative</b> <b>lightweight</b>
-decorator.&nbsp; When a declarative lightweight decorator is defined, the markup
-contains a complete description of the decorator's icon, placement, and enabling
-conditions.&nbsp; Declarative decorators are useful when only an icon is used to
-decorate the label.&nbsp; The plug-in need only specify the <b>quadrant</b> where the decorator should be
-overlayed on the regular icon and the <b>icon</b> for the overlay.&nbsp; As
-shown in the picture, the PDE binary icon is overlayed in the top left quadrant of the
-package icon.</p>
-
-
-<p>If your plug-in needs to manipulate the label text in addition to the icon,
-or if the type of icon is determined dynamically, you can use a non-declarative <b>lightweight</b>
- decorator.&nbsp; In this case, an implementation <strong>class</strong> that implements <a href="../reference/api/org/eclipse/jface/viewers/ILightweightLabelDecorator.html"><b>ILightweightLabelDecorator</b></a>
-must be defined.&nbsp; The designated class is responsible for supplying a prefix,
-suffix, and overlay image at runtime which are applied to the label.&nbsp; The mechanics of
-concatenating the prefix and suffix with the label text and performing the overlay
-are handled by the workbench code in a background thread.&nbsp; Thus, any work
-performed by your plug-in in its <a href="../reference/api/org/eclipse/jface/viewers/ILightweightLabelDecorator.html"><b>ILightweightLabelDecorator</b></a>
-implementation must be UI-thread safe.&nbsp; (See <a href="swt_threading.htm#syncExec">Executing
-code from a non-UI thread</a> for more details.)</p>
-
-
-<p>&nbsp; The following markup shows how the CVS
-client defines its decorator using this technique:</p>
-
-
-<pre>&lt;extension
-         point=&quot;org.eclipse.ui.decorators&quot;&gt;
-    &lt;decorator
-            objectClass=&quot;org.eclipse.core.resources.IResource&quot;
-            adaptable=&quot;true&quot;
-            label=&quot;%DecoratorStandard.name&quot;
-            state=&quot;false&quot;
-            <b>lightweight= &quot;true&quot;</b>
-            <b>quadrant = &quot;BOTTOM_RIGHT&quot;</b>
-            <b>class=&quot;org.eclipse.team.internal.ccvs.ui.CVSLightweightDecorator&quot;</b>
-            id=&quot;org.eclipse.team.cvs.ui.decorator&quot;&gt;
-         &lt;description&gt;
-            %DecoratorStandard.desc
-         &lt;/description&gt;
-    &lt;/decorator&gt;
-&lt;/extension&gt;</pre>
-
-
-<p>Decorators are ultimately controlled by the user via the workbench <b>Label
-Decorations</b> preferences page.&nbsp;
-Individual decorators can be turned on and off.&nbsp; Even so, it is a good idea
-to design your decorators so that they do not overlap or conflict with existing
-platform SDK decorators.&nbsp;If multiple plug-ins contribute lightweight
-decorators to the same quadrant, the conflicts are resolved
-non-deterministically.&nbsp;&nbsp;</p>
-
-
-<p>Your plug-in may also do all of the image and label management
-itself.&nbsp; In this case, the <b>lightweight</b> attribute should be set to
-false and the <b>class </b>attribute should name a class that implements <a href="../reference/api/org/eclipse/jface/viewers/ILabelDecorator.html"><b>ILabelDecorator</b></a>.&nbsp;
-This class allows you to decorate the original label's image and text with your
-own annotations.&nbsp;&nbsp;It gives you increased flexibility since you aren't
-limited to prefixes, suffixes, and simple quadrant overlays.</p>
-
-
-<p>Other attributes of a decorator are independent of the particular
-implementation style.&nbsp; The <b>label</b> and <b>description</b> attributes
-designate the text that is used to name and describe the decorator in the
-preferences dialog.&nbsp; The <b>objectClass</b> names the class of objects to
-which the decorator should be applied.&nbsp; The <b>enablement</b> attribute
-allows you to describe the conditions under which the object should be
-decorated.&nbsp;&nbsp; The <b>adaptable</b> flag indicates
-whether objects that adapt to <b><a href="../reference/api/org/eclipse/core/resources/IResource.html">IResource</a></b>
-should also be decorated.&nbsp; The <b>
-state</b> flag controls whether the decorator is visible by default.</p>
-
-
-<p> If your decorators include information that is
-expensive to compute or potentially distracting, you may want to contribute your
-own preferences that allow the user to further fine-tune the decorator once it
-is on.&nbsp; This technique is used by the CVS client.</p>
-
-
-<p><img src="images/cvsdecorators.png" alt="CVS decorators preference page" border="0"></p>
-
-
-<p>&nbsp;</p>
-<p><strong>Decorator Update Cycle</strong></p>
-<p>Decoration is initiated by refreshing label providers that use the DecoratorManager 
-  to provide decoration. As decoration processing is done in the background there 
-  will be a period between when the label is requested and the labelProviderChanged 
-  event is fired that will be taken up by decoration calculation. During this 
-  time decoration on an Object will only be calculated once for effeciency reasons. 
-  If the decorator changes during this time it is possible that a stale result 
-  will be broadcast as the second and subsequent calls to decorate an element 
-  will be ignored.</p>
-<p>Decorator contributors should avoid changing thier decorators while decoration 
-  is occuring. If this is not possible a second call to decorate an element after 
-  the labelProviderChanged in processed will be required.</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_elementFactories.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_elementFactories.htm
deleted file mode 100644
index bc03d8f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_elementFactories.htm
+++ /dev/null

@@ -1,123 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Element factories</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-<H3>Element factories</H3>
-<P >
-Element factories are used to recreate workbench model objects from data that was saved during workbench shutdown.</P>
-<P >
-Before we look closely at the element factory extension, we need to review a general technique
-that is used throughout the platform to add plug-in specific behavior to common platform model objects.</P>
-
-<H4>
-<a name="workbench_advext_adaptables">
-IAdaptables and workbench adapters</a></H4>
-<P >
-When browsing the various workbench classes, you will notice that many of the workbench interfaces extend the
-<b><a href="../reference/api/org/eclipse/core/runtime/IAdaptable.html"> IAdaptable</a></b> interface.</P>
-<P >
-Plug-ins use adapters to add specific behavior to pre-existing types in the system. For example, the workbench may want
-resources to answer a label and an image for display purposes. We know that it's not good design to add UI specific 
-behavior to low-level objects, so how can we add this behavior to the resource types?</P>
-<P >
- Plug-ins can register adapters that add behavior to pre-existing types.
-Application code can then query an object for a particular adapter. If there is one registered for it,
-the application can obtain the adapter and use the new behaviors defined in the adapter.</P>
-<P >
-By providing a facility to dynamically query an adapter for an object, we can improve the flexibility of the system 
-as it evolves. New adapters can be registered for platform types by new plug-ins without having to change the 
-definitions of the original types. The pattern to ask an object for a particular
-adapter is as follows: </P>
-<pre>
-   //given an object o, we want to do &quot;workbench&quot; things with it.
-   if (!(o instanceof IAdaptable)) {
-      return null;
-   }
-   IWorkbenchAdapter adapter = (IWorkbenchAdapter)o.getAdapter(IWorkbenchAdapter.class);
-   if (adapter == null)
-      return null;
-   // now I can treat o as an IWorkbenchAdapter
-   ...
-</pre>
-<P >
-If there is no adapter registered for the object in hand, null will be returned as the adapter. Clients must be 
-prepared to handle this case.  There may be times when an expected adapter has not been registered.</P>
-<P >
-The workbench uses adapters to obtain UI information from the base platform types, such as
-<b><a href="../reference/api/org/eclipse/core/resources/IResource.html">IResource</a></b>.
-Adapters shield the base types from UI-specific knowledge and allow the workbench to evolve its interfaces 
-without changing the definitions of the base. </P>
-<P >
-Without adapters, any class that might be passed around in the workbench API would have to implement the UI
-interfaces, which would increase the number of class definitions, introduces tight
-coupling, and create circular dependencies between the core and UI classes. With adapters, each class implements
-<b><a href="../reference/api/org/eclipse/core/runtime/IAdaptable.html"> IAdaptable</a></b>
-and uses the adapter registry to allow plug-ins to extend the behavior of the base types.</P>
-<P >
-Throughout the workbench code, you'll see cases where a platform core type is queried for an adapter.
-The query is used to obtain an object that knows how to answer UI oriented information about
-the type.</P>
-
-
-<H4>
-Element factories</H4>
-<P >
-When the workbench is shut down by the user, it must save the current state of the
-<b><a href="../reference/api/org/eclipse/core/runtime/IAdaptable.html"> IAdaptable</a></b>
-objects that are shown in the workbench. An object's state is stored by saving
-the primitive data parameters of the object in a special format, an
-<a href="../reference/api/org/eclipse/ui/IMemento.html"><b>IMemento</b></a>. The id of a factory that can recreate 
-the object from an <a href="../reference/api/org/eclipse/ui/IMemento.html"><b>IMemento</b></a>
-is also stored and the data is saved in the file system.</P>
-<P >
-When the platform is restarted, the workbench finds the element factory associated with the
-<a href="../reference/api/org/eclipse/ui/IMemento.html"><b>IMemento</b></a>'s
-factory id. It finds the factory by checking the plug-in registry for contributions to the
-<a href="../reference/extension-points/org_eclipse_ui_elementFactories.html"><b> org.eclipse.ui.elementFactories</b></a>
-extension.</P>
-<P >
-The markup is pretty simple. We just have to specify the id of the factory and the corresponding class that 
-implements the factory.</P>
-<P >
-The following code snippet is from the workbench <b>plugin.xml</b>.</P>
-<pre>
-&lt;extension
-         point=&quot;org.eclipse.ui.elementFactories&quot;&gt;
-      &lt;factory
-            class=&quot;org.eclipse.ui.internal.model.ResourceFactory&quot;
-            id=&quot;org.eclipse.ui.internal.model.ResourceFactory&quot;&gt;
-      &lt;/factory&gt;
-      &lt;factory
-            class=&quot;org.eclipse.ui.internal.model.WorkspaceFactory&quot;
-            id=&quot;org.eclipse.ui.internal.model.WorkspaceFactory&quot;&gt;
-      &lt;/factory&gt;
-      &lt;factory
-            class=&quot;org.eclipse.ui.part.FileEditorInputFactory&quot;
-            id=&quot;org.eclipse.ui.part.FileEditorInputFactory&quot;&gt;
-      &lt;/factory&gt;
-      &lt;factory
-            class=&quot;org.eclipse.ui.internal.dialogs.WelcomeEditorInputFactory&quot;
-            id=&quot;org.eclipse.ui.internal.dialogs.WelcomeEditorInputFactory&quot;&gt;
-      &lt;/factory&gt;
-      &lt;factory
-            class=&quot;org.eclipse.ui.internal.WorkingSetFactory&quot;
-            id=&quot;org.eclipse.ui.internal.WorkingSetFactory&quot;&gt;
-      &lt;/factory&gt;
-&lt;/extension&gt;
-
-</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_perspectiveExtension.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_perspectiveExtension.htm
deleted file mode 100644
index fbef612..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_perspectiveExtension.htm
+++ /dev/null

@@ -1,126 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>org.eclipse.ui.perspectiveExtensions</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-
-<H3>
-org.eclipse.ui.perspectiveExtensions</H3>
-<P >
- Plug-ins can add their own action sets, views, and various shortcuts to existing
- perspectives by contributing to the <b><a href="../reference/extension-points/org_eclipse_ui_perspectiveExtensions.html">org.eclipse.ui.perspectiveExtensions</a></b>
- extension point.</P>
-
-
-<P >The contributions that can be defined for new perspectives (action sets, wizard entries, view layout,
-view shortcuts, and perspective shortcuts) can also be supplied for
-an existing perspective.&nbsp; One important difference is that these
-contributions are
-specified in the <b>plugin.xml</b> markup instead of
-configuring them into an
- <b><a href="../reference/api/org/eclipse/ui/IPageLayout.html"> IPageLayout</a>.</b>
-</P>
-
-
-<P >The following markup shows how the JDT extends the platform's debug
-perspective.</P>
-
-
-<pre>
-&lt;extension point=&quot;org.eclipse.ui.perspectiveExtensions&quot;&gt;
-  &lt;perspectiveExtension 
-	<b>targetID</b>=&quot;org.eclipse.debug.ui.DebugPerspective&quot;&gt;
-	&lt;actionSet id=&quot;org.eclipse.jdt.debug.ui.JDTDebugActionSet&quot;/&gt;
-    	&lt;view id=&quot;org.eclipse.jdt.debug.ui.DisplayView&quot; 
-        	relative=&quot;org.eclipse.debug.ui.ExpressionView&quot; 
-    		relationship=&quot;stack&quot;/&gt;	
-        &lt;view id=&quot;org.eclipse.jdt.ui.PackageExplorer&quot; 
-                relative=&quot;org.eclipse.debug.ui.DebugView&quot; 
-                relationship=&quot;stack&quot;
-                visible=&quot;false&quot;/&gt;
-        &lt;view id=&quot;org.eclipse.jdt.ui.TypeHierarchy&quot; 
-                relative=&quot;org.eclipse.debug.ui.DebugView&quot; 
-                relationship=&quot;stack&quot;
-                visible=&quot;false&quot;/&gt;
-        &lt;view id=&quot;org.eclipse.search.SearchResultView&quot; 
-                relative=&quot;org.eclipse.debug.ui.ConsoleView&quot; 
-                relationship=&quot;stack&quot;
-                visible=&quot;false&quot;/&gt; 
-    	&lt;viewShortcut id=&quot;org.eclipse.jdt.debug.ui.DisplayView&quot;/&gt;
-  &lt;/perspectiveExtension&gt; 
-&lt;/extension&gt;</pre>
-
-
-<P >The <b>targetID</b> is the id of the perspective to which the plug-in is
-contributing new behavior.&nbsp; The <b>actionSet</b> parameter identifies the <b>id</b>
-of a previously declared action set that should be added to the target
-perspective.&nbsp; This markup is analogous to using<b>
-IPageLayout.addActionSet</b> in the&nbsp;<b><a href="../reference/api/org/eclipse/ui/IPerspectiveFactory.html">IPerspectiveFactory</a></b>.</P>
-
-
-<P >Contributing a view to a perspective is a little more involved, since the
-perspective page layout information must be declared.&nbsp; The <b>visible</b>
-attribute controls whether the contributed view is initially visible when the perspective is
-opened.&nbsp; In addition to
-supplying the <b>id</b> of the contributed view, the id
-of a view that already exists in the perspective ( a <b>relative</b>
-view) must be specified as a reference point for placing the new view.&nbsp; The
-<b>relationship</b> parameter specifies the layout
-relationship between the new view and the <b>relative</b>
-view.&nbsp;&nbsp;</P>
-
-
-<ul>
-  <li> <b>stack</b> indicates that the
-view will be stacked with the relative view in a folder</li>
-  <li><b>fast</b> indicates that the view will be shown as a fast
-    view&nbsp;&nbsp;</li>
-  <li> <b>left</b>, <b>right</b>,
-<b>top</b>, or <b>bottom</b> indicate that the new view will be placed beside the <b>relative</b>
-view.&nbsp; In this case, a <b> ratio</b> between 0.0 and 1.0 must be defined, which
-indicates the percentage of area in the <b>relative</b>
-view that will be allocated to the new view.&nbsp;&nbsp;</li>
-</ul>
-
-
-<P >Specifying a <b>perspectiveShortcut</b>
-indicates that another perspective (specified by <b>id</b>)
-should be added to the <b>Window-&gt;Open Perspective... </b>menu of the target
-perspective.&nbsp; This markup is analogous to calling <b>IPageLayout.addPerspectiveShortcut</b>
-in the original perspective definition in the <b><a href="../reference/api/org/eclipse/ui/IPerspectiveFactory.html">IPerspectiveFactory</a></b>.&nbsp;
-Plug-ins can also add view shortcuts and new wizard shortcuts in a similar
-manner.&nbsp;&nbsp;</P>
-
-
-<P >You can also specify one or more views as a valid <b>showInPart</b>.&nbsp; The
-views should be specified by the id used in their <b><a href="../reference/extension-points/org_eclipse_ui_views.html">org.eclipse.ui.views</a></b>
-extension contribution.&nbsp;&nbsp; This controls which views are available as
-targets in the <b>Navigate &gt; Show In </b>menu.&nbsp; The ability to specify a
-&quot;show in&quot; view in the extension markup allows you to add your
-newly contributed views as targets in another perspective's &quot;show in&quot;
-menus.&nbsp; See <a href="workbench_perspectives.htm#showin">Linking views and
-editors</a> for more information on &quot;show in.&quot;</P>
-
-
-<P > See <b><a href="../reference/extension-points/org_eclipse_ui_perspectiveExtensions.html">org.eclipse.ui.perspectiveExtensions</a></b>
-for a complete definition of the extension point.</P>
-
-
-<P >&nbsp;</P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_perspectives.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_perspectives.htm
deleted file mode 100644
index d6802de..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_perspectives.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>org.eclipse.ui.perspectives</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H3>
-org.eclipse.ui.perspectives</H3>
-<P >
-The platform itself defines one perspective, the <b> Resource</b> perspective. Other platform plug-ins, such as
-the help system and the Java tooling, define additional perspectives. Your plug-in can define its own
-perspective by contributing to the <b><a href="../reference/extension-points/org_eclipse_ui_perspectives.html">org.eclipse.ui.perspectives</a></b>
-extension point.</P>
-<P >
-The specification of the perspective in the <b> plugin.xml</b> is straightforward. The following markup is used by the workbench in defining its own resource perspective.</P>
-<pre>
-&lt;extension
-         point=&quot;org.eclipse.ui.perspectives&quot;&gt;
-      &lt;perspective
-            name=&quot;%Perspective.resourcePerspective&quot;
-            icon=&quot;icons/full/cview16/resource_persp.png&quot;
-            class=&quot;org.eclipse.ui.internal.ResourcePerspective&quot;
-            id=&quot;org.eclipse.ui.resourcePerspective&quot;&gt;
-      &lt;/perspective&gt;
-   &lt;/extension&gt;</pre>
-<P >
-A plug-in must supply an <b> id</b> and <b> name</b> for the perspective, along with the name of the
-<b> class</b> that implements the perspective. An <b> icon</b> can also be specified. The perspective class should implement
-<b><a href="../reference/api/org/eclipse/ui/IPerspectiveFactory.html">IPerspectiveFactory</a></b>.</P>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_resourceFilters.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_resourceFilters.htm
deleted file mode 100644
index e118861..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_resourceFilters.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Contributing resource filters</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-
-<H3>
-Contributing resource filters</H3>
-<P >
-The resource filters extension allows plug-ins to define filters that are useful for filtering out file types in the resource navigator view. This
-extension is useful when special file types are used to represent internal plug-in information
-but you do not want the files to be shown in the workbench or manipulated by the user.</P>
-<P >
-The workbench filters out the pattern &quot;<b>.*</b>&quot; to exclude internal files such as .metadata from the resource navigator. Likewise, the JDT plug-in filters out &quot;<b>*.class</b>&quot; files to hide compiled classes.</P>
-<P >
-The markup for the resource filters extension is simple.&nbsp; The following is
-from the workbench <b>plugin.xml</b>.</P>
-<pre>
-&lt;extension
-         point=&quot;org.eclipse.ui.ide.resourceFilters&quot;&gt;
-      &lt;filter
-            selected=&quot;false&quot;
-            pattern=&quot;.*&quot;&gt;
-      &lt;/filter&gt;
-   &lt;/extension&gt;
-</pre>
-<P >The filters can be enabled by the user using the resource navigator's local
-pull-down menu.</P>
-
-
-<P ><img src="images/filtersmenu.png" alt="Resource filters menu" border="0" ></P>
-
-
-<P >In addition to declaring the <b>filter pattern</b>,
-the plug-in can use the <b>selected</b> attribute to
-specify whether the filter should be enabled in the resource navigator.&nbsp;
-This attribute only determines the initial state of the filter pattern.&nbsp; The user can
-control which filter patterns are active.</P>
-
-
-<P ><img src="images/filtersselection.png" alt="Filter selection dialog" border="0" ></P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext.htm
deleted file mode 100644
index ce20bc1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Basic workbench extension points
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Basic workbench extension points</H2>
-<P >
-The workbench defines extension points that allow plug-ins to contribute
-behaviors to existing views and editors or to provide implementations for
-new&nbsp; views and editors. We are going to take a look at the
-contributions to these extension points from one of the workbench sample applications, the readme tool. </P>
-<P >
-The readme tool is a plug-in that provides custom editing and navigation for a specific resource
-, a
-<b> .readme</b> file. The example shows many typical (but simplified) ways that extensions can be used to provide specialized tools.</P>
-<P >
-The readme tool contributes to the menus of the navigator view, adds editor related actions to the workbench menus and
-tool bar, defines a custom view and content outliner, and defines markers
-and marker resolutions. The figure below shows some of the
-customized features added to the workbench by the readme tool.</P>
-<P >
-<img src="images/readmeoverview.png" alt="Workbench with readme tool contributing action sets, view and editor actions, custom editors and views, and outliner" border="0"></P>
-<P >
-The readme tool also contributes preference and properties pages to the workbench.  Later we'll also look
-at some wizard contributions in 
-<a HREF="dialogs.htm" CLASS="XRef"> Dialogs and wizards</a>.</P>
-<P >
-The readme tool is located in the <b>org.eclipse.ui.examples.readmetool</b> package. The
-<b> readmetool.jar</b> and <b> plugin.xml</b> can be found in the
-<b> org.eclipse.ui.examples.readmetool</b> directory underneath the
-<b> plugins</b> directory. To follow along, you will need to make sure that
-you have installed the platform examples.&nbsp; (See the <a href="../samples/samples.html">Examples
-Guide </a> for more information.)&nbsp; </P>
-<P >
-The <a href="../samples/org.eclipse.ui.examples.readmetool/doc-html/ui_readmetool_ex.html">readme
-tool</a> implements many different workbench extensions.&nbsp; We will start
-with one of the simplest workbench extension points, a view.&nbsp; We'll
-continue by looking at additional readme tool extensions. </P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_actionSetPartAssociations.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_actionSetPartAssociations.htm
deleted file mode 100644
index b34aa2e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_actionSetPartAssociations.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Action set part associations</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Action set part associations</H2>
-
-<P >
-Once your plug-in defines an <a href="workbench_basicext_actionSets.htm">action
-set</a>, it can use the
-<a href="../reference/extension-points/org_eclipse_ui_actionSets.html"><b> org.eclipse.ui.actionSetPartAssociations</b></a> 
-extension point to specify that an action set should be made visible when a
-particular view or editor is active.&nbsp;&nbsp; </P>
-
-<P >
- Ultimately, the user controls the
-appearance of action sets using <b>Window-&gt;Customize Perspectives...</b> in
-the workbench menu.&nbsp;If the user marks an action set visible, it will always be visible when the
-perspective is active, regardless of
-the active view or editor.&nbsp; Likewise, if the user marks the action set as hidden, it will always be hidden when the perspective is active.&nbsp; If the user does not change the state of
-an action set in this dialog, then the action set part associations are used to
-determine the visibility of the action set.</P>
-
-
-<P >
-The markup for an action set part association is straightforward.&nbsp; The
-following example comes from the Java development tools (JDT) UI plug-in.</P>
-<pre>
-   &lt;extension point=&quot;org.eclipse.ui.actionSetPartAssociations&quot;&gt;
-	&lt;actionSetPartAssociation 
-		<b>targetID</b>=&quot;org.eclipse.jdt.ui.CodingActionSet&quot;&gt;
-		&lt;part id=&quot;org.eclipse.jdt.ui.PackageExplorer&quot;/&gt;
-		&lt;part id=&quot;org.eclipse.jdt.ui.TypeHierarchy&quot; /&gt;
-		&lt;part id=&quot;org.eclipse.jdt.ui.CompilationUnitEditor&quot;/&gt;
-		&lt;part id=&quot;org.eclipse.jdt.ui.ClassFileEditor&quot;/&gt;
-		&lt;part id=&quot;org.eclipse.jdt.ui.ProjectsView&quot;/&gt;
-		&lt;part id=&quot;org.eclipse.jdt.ui.PackagesView&quot;/&gt;
-		&lt;part id=&quot;org.eclipse.jdt.ui.TypesView&quot;/&gt;
-		&lt;part id=&quot;org.eclipse.jdt.ui.MembersView&quot;/&gt;
-	&lt;/actionSetPartAssociation&gt;
-&lt;/extension&gt;
-</pre>
-<P >The <b>targetID</b> specifies the action set.&nbsp; (The <b> CodingActionSet</b> was
-previously defined in the JDT plug-in manifest.)&nbsp; One or more <b>part</b>
-attributes can be specified to indicate which views and editors will cause the
-action set to become visible in the menus and toolbar.&nbsp; The effect of this extension
-contribution is that the actions associated with writing Java code will only be
-visible when one of the specified views is active.</P>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_actionSets.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_actionSets.htm
deleted file mode 100644
index ac4ab0c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_actionSets.htm
+++ /dev/null

@@ -1,143 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>org.eclipse.ui.actionSets</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-org.eclipse.ui.actionSets</H3>
-
-<P >
-Your plug-in can contribute menus, menu items, and tool bar items to the workbench menus and toolbar
-by using the
-<a href="../reference/extension-points/org_eclipse_ui_actionSets.html"><b> org.eclipse.ui.actionSets</b></a> 
-extension point. In order to reduce the clutter that would be caused by having every plug-in's menu contributions shown at once, the contributions are grouped into action sets which can be made visible by user preference.</P>
-<P >
-You can see which action sets have been contributed to your workbench by choosing
-<b>Window-&gt;Customize Perspective...</b> from the workbench menu. This option will show you a dialog that lists
-action sets as groups of commands.  A checkmark by a command group means that the menu and tool bar actions are visible in the workbench. 
-You can select the name of the command group to see the list of available menu and toolbar actions to the right. The figure below shows the
-list of command groups available in our workbench.&nbsp; (Your workbench may look different depending on which plug-ins you have
-installed and which perspective is active.)</P>
-
-<img src="images/actionsets.png" alt="Customize Perspective dialog with action set list" border="0">
-
-
-<P >
-The readme tool uses an action set to contribute several different &quot;Open Readme
-Browser&quot; actions to the workbench menu.&nbsp; (We contributed a similar
-action to the popup menu of the resource navigator.)&nbsp; The markup follows:</P>
-<pre>
-&lt;extension point = &quot;org.eclipse.ui.actionSets&quot;&gt;
-	   &lt;actionSet id=&quot;org_eclipse_ui_examples_readmetool_actionSet&quot;
-		   label=&quot;%ActionSet.name&quot;
-		   visible=&quot;true&quot;&gt;
-		   &lt;menu id=&quot;org_eclipse_ui_examples_readmetool&quot;
-			   label=&quot;%ActionSet.menu&quot;
-			   path=&quot;window/additions&quot;&gt; 
-			   &lt;separator name=&quot;slot1&quot;/&gt;
-			   &lt;separator name=&quot;slot2&quot;/&gt;
-			   &lt;separator name=&quot;slot3&quot;/&gt;
-		   &lt;/menu&gt;
-		   &lt;action id=&quot;org_eclipse_ui_examples_readmetool_readmeAction&quot;
-			   menubarPath=&quot;window/org_eclipse_ui_examples_readmetool/slot1&quot;
-			   toolbarPath=&quot;readme&quot;
-			   label=&quot;%ReadmeAction.label&quot;
-			   tooltip=&quot;%ReadmeAction.tooltip&quot;
-			   helpContextId=&quot;org.eclipse.ui.examples.readmetool.open_browser_action_context&quot;
-			   icon=&quot;icons/ctool16/openbrwsr.png&quot;
-			   class=&quot;org.eclipse.ui.examples.readmetool.<b>WindowActionDelegate</b>&quot;
-			   enablesFor=&quot;1&quot;&gt;
-			   &lt;selection class=&quot;org.eclipse.core.resources.IFile&quot;
-					name=&quot;*.readme&quot;&gt;
-			   &lt;/selection&gt;
-		   &lt;/action&gt;
-		   ...
-	   &lt;/actionSet&gt;
-   &lt;/extension&gt;</pre>
-<P >
-Wow, there's a lot going on here!&nbsp; Let's take it a step at a time, looking
-only at the first action for now.&nbsp;&nbsp;</P>
-<P >
-First, the action set is declared and given a <b>label</b>.&nbsp;
-The label &quot;ReadMe Actions&quot; (defined for <b> %ActionSet.name</b>  key in the plug-in's
-properties file) is used to display the action set in the
-dialog shown above.&nbsp; Since we set <b> visible</b> to true, the workbench will initially have the action set
-checked in the action set list and the actions will be visible.</P>
-<P >
-The rest of the action set declaration is concerned with defining the menu in
-which the actions appears and the actions themselves.</P>
-<P >
-We define a menu whose <b>label</b> appears in the workbench menus.&nbsp; The menu's <b>path</b>
-tells the workbench to place the new menu in the <b>additions</b>
-slot of the <b>window</b> menu.&nbsp; (For a discussion
-of menu paths and slots, see <a HREF="workbench_menupaths.htm" CLASS="XRef"> Menu and toolbar paths</a>.)&nbsp;
-We also define some slots in our new menu so that actions can be inserted at specific locations in our menu.</P>
-<P >
-This markup alone is enough to cause the menu to appear in the workbench <b>Window</b>
-menu.</P>
-<P >
-<img src="images/readmeactionset.png" alt="Workbench Window menu with Readme File Editor entry" border="0" ></P>
-<P >
-Next, we define the actions themselves.&nbsp;&nbsp;</P>
-<P >
-The action definition (<b>id</b>,
-<b>label</b>, <b>icon</b>, <b>class</b>) is
-similar to the other actions we've seen in views, editors, and popups.&nbsp;
-We'll focus here on what's different:&nbsp; where does the action go?&nbsp; We
-use&nbsp; <b>menubarPath</b> and <b>toolbarPath</b>
-to indicate its location.&nbsp; First, we define the <b>menubarPath</b> to add the
-action to a slot in the menu
-that we just defined (&nbsp;<b>&quot;window/org_eclipse_ui_examples_readmetool/slot1&quot;</b>).</P>
-<P >
-<img src="images/readmeactionsetmenu.png" alt="Readme File Editor menu with menu items" border="0" ></P>
-<P >
-Then, we define a new <b> toolbarPath</b> to insert our actions in the workbench tool
-bar.&nbsp; Since we've defined a new tool path, <b>&quot;readme&quot;</b>, the workbench will decide where it goes
-relative to other plug-in's toolbar contributions.</P>
-<P >
-<img src="images/readmeactionsettoolbar.png" alt="Workbench tool bar with readme action" border="0" ></P>
-<P >
-What happens when the action is selected by the user?&nbsp; The action is
-implemented by the class specified in the <b>class</b>
-attribute.&nbsp; The action <b> class</b> must implement
-<b><a href="../reference/api/org/eclipse/ui/IWorkbenchWindowActionDelegate.html"> IWorkbenchWindowActionDelegate</a></b>,
-or
-<b><a href="../reference/api/org/eclipse/ui/IWorkbenchWindowPulldownDelegate.html"> IWorkbenchWindowPulldownDelegate</a></b> 
-if the action will be shown as a pull-down tool item in the tool bar.&nbsp; Since we are not
-creating a pull-down tool item, we provide <b>WindowActionDelegate</b>.&nbsp;
-This class is similar to <b>ObjectActionDelegate</b>.&nbsp;
-It launches the readme sections dialog when the user chooses the action.&nbsp; (We'll
-discuss the sections dialog in <a href="dialogs_applications.htm">Application
-dialogs</a>.)</P>
-
-
-<P >
-The action also supplies enabling conditions for its menu item and tool bar
-item.&nbsp; The menu and tool bar items will only be enabled when a single (<b>enablesFor=&quot;1&quot;</b>)
-readme file (<b>selectionClass =&quot;org.eclipse.core.resources.IFile&quot;
-name=&quot;*.readme&quot;</b>) is selected.&nbsp; This action's menu and toolbar
-item appear and are enabled by virtue of the markup
-in the <b>plugin.xml</b> file.&nbsp; None of the
-plug-in code will execute until the user chooses the action and the workbench
-runs the action <b>class</b>.</P>
-
-
-<P >
-We'll look at the other two actions later in the context of <a href="wrkAdv_retarget_contribute.htm">retargetable
-actions</a>.</P>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_editorActions.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_editorActions.htm
deleted file mode 100644
index 672b20a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_editorActions.htm
+++ /dev/null

@@ -1,70 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>org.eclipse.ui.editorActions</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-org.eclipse.ui.editorActions</H3>
-
-<P >
-We've just seen how editors
-can contribute their own actions to the workbench menus and tool bar when they
-become active.&nbsp; The <b><a href="../reference/extension-points/org_eclipse_ui_editorActions.html">org.eclipse.ui.editorActions</a></b> extension
-point allows a plug-in to add
-to the workbench menus and tool bar when another plug-in's editor becomes active.</P>
-<P >
-In the readme example, the plug-in uses the <b>editorActions</b>
-extension point to contribute additional actions to the menu contributed by the
-readme editor. The definition in our
-<b> plugin.xml</b> should look pretty familiar by now.</P>
-<pre>
-&lt;extension
-    point = &quot;org.eclipse.ui.editorActions&quot;&gt;
-      &lt;editorContribution 
-         id=&quot;org.eclipse.ui.examples.readmetool.ec1&quot; 
-         targetID=&quot;org.eclipse.ui.examples.readmetool.ReadmeEditor&quot;&gt;        
-	   &lt;action id=&quot;org.eclipse.ui.examples.readmetool.ea1&quot; 
-              label=&quot;%Editors.Action.label&quot; 
-	      toolbarPath=&quot;ReadmeEditor&quot; 
-              icon=&quot;icons/obj16/editor.png&quot; 
-              tooltip=&quot;%Editors.Action.tooltip&quot; 
-              class=&quot;org.eclipse.ui.examples.readmetool.EditorActionDelegate&quot; 
-              /&gt; 
-      &lt;/editorContribution&gt;
- &lt;/extension&gt;</pre>
-<P >Similar to a view action, the extension must specify the <b> targetID</b> of the
-editor to which it is contributing actions.&nbsp; The action itself is very
-similar to a view action (<b>id</b>, <b>label</b>, <b>icon</b>, <b>toolbarPath</b>,
-...), except that the specified class
-must implement <b><a href="../reference/api/org/eclipse/ui/IEditorActionDelegate.html">IEditorActionDelegate</a></b>.&nbsp;&nbsp;</P>
-<P >Note that a menu bar path is not specified in this markup.&nbsp; Therefore,
-the action will appear in the workbench tool bar when the editor is active,
-but not in the workbench menu bar.&nbsp; (See <a HREF="workbench_menupaths.htm" CLASS="XRef"> Menu and toolbar paths</a> for a discussion of toolbar and menu paths.)</P>
-<P >Sure enough, when the editor is active, we see our editor action on the tool
-bar next to the actions that were contributed by the editor itself.</P>
-<P ><img src="images/editorAction.png" alt="Editor action appears next to original editor contributions in workbench toolbar" border="0" ></P>
-<P >
-The readme tool supplies <b> EditorActionDelegate</b>
-to implement the action.&nbsp; This class is very similar to the view action delegate
-we saw earlier.</P>
-
-<pre>
-public void run(IAction action) {
-	MessageDialog.openInformation(editor.getSite().getShell(),
-		MessageUtil.getString(&quot;Readme_Editor&quot;),  
-		MessageUtil.getString(&quot;Editor_Action_executed&quot;)); 
-}</pre>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_editors.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_editors.htm
deleted file mode 100644
index c4ba85c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_editors.htm
+++ /dev/null

@@ -1,168 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>org.eclipse.ui.editors</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-org.eclipse.ui.editors</H3>
-
-<P >
-An editor is a workbench part that allows a user to edit an object (often a
-file). Editors operate in a manner similar to file system editing tools, except that they are tightly integrated into the platform workbench UI. An editor is always associated with an input object
-(<a href="../reference/api/org/eclipse/ui/IEditorInput.html"><b>IEditorInput</b></a>). You can think of the input object as
-the document or file that is being edited. Changes made in an editor are not
-committed until the user saves them. </P>
-<P >
-Only one editor can be open for any particular editor input in a workbench page. For example, if the user is editing
-<b> readme.txt</b> in the workbench, opening it again
-in the same perspective will activate the same editor. (You can open another
-editor on the same file from a different workbench window or perspective).&nbsp;
-Unlike views, however, the same editor type, such as a text editor, may be open
-many times
-within one workbench page for different inputs.</P>
-<P >
-The workbench extension point <b><a href="../reference/extension-points/org_eclipse_ui_editors.html">org.eclipse.ui.editors</a></b>
-is used by plug-ins to add editors to the workbench. Plug-ins that contribute an editor must register the editor
-extension in their <b>plugin.xml </b> file, along with configuration information
-for the editor. Some
-of the editor information, such as the implementation <b> class</b> and the
-<b> name</b> and the <b>icon</b>  to be used in the workbench menus and
-labels, is similar to the view information. In addition, editor extensions specify the file extensions or file name patterns of the file types that the editor understands. Editors can also define a
-<b> contributorClass</b>, which is a class that adds actions to workbench menus and tool bars when the editor is active.</P>
-<P >
-The interface for editors is defined in <b><a href="../reference/api/org/eclipse/ui/IEditorPart.html">IEditorPart</a></b>, but plug-ins
-can choose to extend the
-<b><a href="../reference/api/org/eclipse/ui/part/EditorPart.html"> EditorPart</a></b> class rather than implement an
-<b><a href="../reference/api/org/eclipse/ui/IEditorPart.html">IEditorPart</a></b>
-from scratch.</P>
-<blockquote><i>
-Note:&nbsp; An editor extension can also be configured to launch an external program
-or to call pre-existing java code. In this discussion, we are focusing on those editors that are actually tightly integrated with the workbench and
-are implemented using
-<b><a href="../reference/api/org/eclipse/ui/IEditorPart.html">IEditorPart</a></b>.</i></blockquote> 
-<P >
-The readme tool provides a custom editor primarily for the purpose of contributing its own content outliner page to the
-workbench outline view.&nbsp;&nbsp;</P>
-<P >
- The configuration for the editor extension is defined as follows.</P>
-<pre>
-&lt;extension
-    point = &quot;org.eclipse.ui.editors&quot;&gt;
-	&lt;editor
-  	   id = &quot;org.eclipse.ui.examples.readmetool.ReadmeEditor&quot;
-  	   name=&quot;%Editors.ReadmeEditor&quot;
-      	   icon=&quot;icons/obj16/editor.png&quot;
-      	   class=&quot;org.eclipse.ui.examples.readmetool.ReadmeEditor&quot;
-	   extensions=&quot;readme&quot;
-           contributorClass=&quot;org.eclipse.ui.examples.readmetool.ReadmeEditorActionBarContributor&quot;&gt;
-	&lt;/editor&gt;
-&lt;/extension&gt;</pre>
-<P >
-We see the familiar configuration markup for <b>id</b>,
-<b>name</b>,
-<b>icon</b>, and <b>class</b>.&nbsp;&nbsp; The <b>extensions</b> attribute
-describes the file types that the editor understands.&nbsp; (You could also
-specify <b>filenames</b> if you need to be more specific.)&nbsp; The <b>class</b>
-implements the editor, and the <b>contributorClass</b> is responsible for
-providing editor-related actions.&nbsp; Let's look at the contributor in more
-detail.</P>
-
-<H4>
-Editor action contributors</H4>
-<P >
-The contributor class adds editor-related actions to the workbench menu and toolbar. It must implement the
-<b><a href="../reference/api/org/eclipse/ui/IEditorActionBarContributor.html"> IEditorActionBarContributor</a></b> interface. The contributor is
-separate from the editor itself since any given workbench page can have multiple editors of the same type.
-A single contributor is shared by all the editors of a specific type, rather than
-having each instance of an editor create actions and images.&nbsp;</P>
-<P >
-In <b>ReadmeEditorActionBarContributor</b>, we contribute three actions,
-&quot;Editor Action1,&quot; &quot;Editor Action2,&quot; and &quot;Editor Action3.&quot;&nbsp;&nbsp;
-These are set up in the constructor.</P>
-<pre>
-   public ReadmeEditorActionBarContributor() {
-      	...
-	action1 = new EditorAction(MessageUtil.getString(&quot;Editor_Action1&quot;)); 
-	action1.setToolTipText(MessageUtil.getString(&quot;Readme_Editor_Action1&quot;)); 
-	action1.setDisabledImageDescriptor(ReadmeImages.EDITOR_ACTION1_IMAGE_DISABLE);
-	action1.setImageDescriptor(ReadmeImages.EDITOR_ACTION1_IMAGE_ENABLE);
-	...	
-	action2 = new RetargetAction(IReadmeConstants.RETARGET2, MessageUtil.getString(&quot;Editor_Action2&quot;)); 
-	action2.setToolTipText(MessageUtil.getString(&quot;Readme_Editor_Action2&quot;)); 
-	action2.setDisabledImageDescriptor(ReadmeImages.EDITOR_ACTION2_IMAGE_DISABLE);
-	action2.setImageDescriptor(ReadmeImages.EDITOR_ACTION2_IMAGE_ENABLE);
-	...
-	action3 = new LabelRetargetAction(IReadmeConstants.LABELRETARGET3, MessageUtil.getString(&quot;Editor_Action3&quot;));
-	action3.setDisabledImageDescriptor(ReadmeImages.EDITOR_ACTION3_IMAGE_DISABLE);
-	action3.setImageDescriptor(ReadmeImages.EDITOR_ACTION3_IMAGE_ENABLE);
-	...   
-   }
-</pre>
-<P >
-The names and icons for the actions are set up in the code rather than in the <b>plugin.xml</b>.&nbsp;
-(We'll ignore the differences in the action classes for now until we look at <a href="wrkAdv_retarget_contribute.htm">retargetable
-actions</a>.)&nbsp;&nbsp;</P>
-<P >Note how similar the action information is to the
-<b> viewActions</b> information we saw in the markup
-for the view action.&nbsp; The actions are set up in code since we have to
-manage the sharing of the actions among different instances of the same editor.&nbsp;
-When the actions are created in the constructor, they are independent of any
-particular instance of the editor.</P>
-<P >
- When an editor becomes active and it has actions that need to be installed in the workbench menus and tool bar, the <b>setActiveEditor
-</b>message is sent to the contributor.&nbsp; The contributor connects the editor actions to a specific editor.&nbsp;&nbsp;</P>
-<pre>
-   public void setActiveEditor(IEditorPart editor) {
-      ...
-      action1.setActiveEditor(editor);
-      ...
-   }
-</pre>
-<P >
-As you can see, the actions show up in the workbench menu and tool bar when a readme editor is active. </P>
-
-<img src="images/editormenu.png" alt="Readme entry in workbench menu bar with three editor actions" border="0" >
-
-
-
-<p><img src="images/editortoolbar.png" alt="Workbench toolbar with three readme actions" border="0" ></p>
-<P >
-These menu and tool bar items are only shown when the editor is active. The location for the menu and tool bar items can be specified as described in
-<a HREF="workbench_menupaths.htm" CLASS="XRef">Menu and toolbar paths</a>.</P>
-
-
-
-<H4>
-Editors and content outliners
-</h4>
-<P >
-The readme editor itself, <b>ReadmeEditor</b>, is not very complicated. It extends the
-<b><a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"> TextEditor</a></b> class so that it can contribute a customized content outliner page
-to the outline view when a readme file is being edited. It does not change any behavior inside the text editor.</P>
-<p><img src="images/readmeoutliner.png" alt="" border="0"></p>
-<P >
-Editors often have corresponding content outliners that provide a structured
-view of the editor's contents and assist the user in navigating through the
-contents of the editor.&nbsp; See <a href="editors_workbench_outliner.htm">Content
-outliners</a> for more detail. </P>
-
-
-<P >
-We'll look at the implementation of text editors in <a href="editors_jface.htm">Text
-editors and platform text</a>. </P>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_popupMenus.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_popupMenus.htm
deleted file mode 100644
index 942ba0d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_popupMenus.htm
+++ /dev/null

@@ -1,130 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>org.eclipse.ui.popupMenus</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-org.eclipse.ui.popupMenus</H3>
-
-<P >
-The <b><a href="../reference/extension-points/org_eclipse_ui_popupMenus.html"> org.eclipse.ui.popupMenus</a></b> extension
-point allows a plug-in to contribute to the popup menus of other
-views and editors.</P>
-<P >
-You can contribute an action to a specific popup menu by its id (<b>viewerContribution</b>), or
-by associating it with a particular object type (<b>objectContribution</b>).&nbsp;</P>
-<ul>
-  <li>An <b>objectContribution</b> will cause the menu
-    item to appear in popup menus for views or editors where objects of
-    the specified type are selected.</li>
-  <li>A <b>viewerContribution</b> will cause the menu
-    item to appear in the popup menu of a view or editor specified by id in the
-    markup.&nbsp;&nbsp;</li>
-</ul>
-<P >
-The readme tool defines both. Let's look at the object contribution
-first.&nbsp;&nbsp;</P>
-<pre>
-&lt;extension point = &quot;org.eclipse.ui.popupMenus&quot;&gt;
-     &lt;objectContribution
-        id=&quot;org.eclipse.ui.examples.readmetool&quot;
-        objectClass=&quot;org.eclipse.core.resources.IFile&quot;
-	    nameFilter=&quot;*.readme&quot;&gt;
-	    &lt;action id=&quot;org.eclipse.ui.examples.readmetool.action1&quot;
-	       label=&quot;%PopupMenus.action&quot;
-	       icon=&quot;icons/ctool16/openbrwsr.png&quot;
-	       menubarPath=&quot;additions&quot;
-	       helpContextId=&quot;org.eclipse.ui.examples.readmetool.open_browser_action_context&quot;
-	       class=&quot;org.eclipse.ui.examples.readmetool.PopupMenuActionDelegate&quot;	
-	       enablesFor=&quot;1&quot;&gt;
-	    &lt;/action&gt;
-	 &lt;/objectContribution&gt;
- 	 ...
-</pre><h4>
-   Object contribution
-</h4>
-<P >
-The action &quot;Show Readme Action&quot; is contributed for the object class <a href="../reference/api/org/eclipse/core/resources/IFile.html"><b>IFile</b></a>. This means that any view containing
-<a href="../reference/api/org/eclipse/core/resources/IFile.html"><b>IFile</b></a>
-objects will show the contribution if <a href="../reference/api/org/eclipse/core/resources/IFile.html"><b>IFile</b></a>
-objects are selected. We see that the selection criteria is restricted further with a name filter
-(<b>nameFilter=&quot;*.readme&quot;</b>) and for single selections (<b>enablesFor=&quot;1&quot;</b>). As we've discussed before, the registration of this menu does not run any code from our plug-in until the menu item is actually selected. </P>
-<P >
-When the menu item is selected, the workbench will run the specified class.&nbsp;
-Since the popup is declared as an <b>objectContribution</b>,
-the supplied class must implement <b><a href="../reference/api/org/eclipse/ui/IObjectActionDelegate.html">IObjectActionDelegate</a></b>.&nbsp;</P>
-<P >
-The action is implemented in <b>PopupMenuActionDelegate</b>.&nbsp;&nbsp;</P>
-<pre>
-   public void run(IAction action) {
-      MessageDialog.openInformation(
-         this.part.getSite().getShell(),
-         &quot;Readme Example&quot;,
-         &quot;Popup Menu Action executed&quot;);
-   }
-</pre>
-<P >
-We can see the popup menu contribution when we select a readme file from the resource navigator.</P>
-
-<img src="images/readmepopupmenu.png" alt="" border="0">
-<h4>Viewer contribution</h4>
-<p>
-A viewer contribution is used to contribute to a specific view or editor's popup menu
-by using its id.
-Here is the readme tool's viewer contribution:</p>
-<pre>      ...
-      &lt;viewerContribution
-        id=&quot;org.eclipse.ui.examples.readmetool2&quot;
-        targetID=&quot;org.eclipse.ui.examples.readmetool.outline&quot;&gt;
-	    &lt;action id=&quot;org.eclipse.ui.examples.readmetool.action1&quot;
-	       label=&quot;%PopupMenus.action&quot;
-	       icon=&quot;icons/ctool16/openbrwsr.png&quot;
-	       menubarPath=&quot;additions&quot;
-	       helpContextId=&quot;org.eclipse.ui.examples.readmetool.open_browser_action_context&quot;
-	       class=&quot;org.eclipse.ui.examples.readmetool.ViewActionDelegate&quot;&gt;	
-	    &lt;/action&gt;
-       &lt;/viewerContribution&gt;
-&lt;/extension&gt;</pre>
-<blockquote><i>
-Note:&nbsp; The name <b> viewerContribution</b> is somewhat misleading, as it does not relate to JFace viewers. A better name would
-be <b>popupMenuContribution</b>.</i></blockquote>
-<P >
-When the extension is a <b>viewerContribution</b>, the
-supplied class must implement the
-<b><a href="../reference/api/org/eclipse/ui/IEditorActionDelegate.html"> IEditorActionDelegate</a></b> or
-<b><a href="../reference/api/org/eclipse/ui/IViewActionDelegate.html"> IViewActionDelegate</a></b> interface, depending on whether the
-action is contributed to an editor's or view's popup menu.&nbsp;</P>
-
-
-<P >
-The <b>targetID</b> specifies the view whose popup menu will be altered.&nbsp; In this
-case, we are adding an action to one of the readme tool views, the
-outliner.&nbsp; The action itself is similar to others that we've seen.&nbsp; We specify the <b> id</b>,
-<b>label</b>, and <b>icon</b> of the action, and
-the <b>path</b> within the popup for our contribution.&nbsp; The action will be
-shown only in the readme outline view's popup menu.</P>
-
-
-<P >
-<img src="images/readmeoutlinerpopup.png" alt="" border="0"></P>
-
-
- The interfaces required to contribute a <b>viewerContribution</b>
-to the <b> popupMenus</b> extension
-point are the same as those required by the <b> viewActions</b> and <b> editorActions</b> extension points. If you want to contribute the same action to the popup menu and the local menu of a view or editor, you can use the same class for both extensions.
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_viewActions.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_viewActions.htm
deleted file mode 100644
index fe25711..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_viewActions.htm
+++ /dev/null

@@ -1,92 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>org.eclipse.ui.viewActions</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-org.eclipse.ui.viewActions</H3>
-
-<P >
-It is common for plug-ins to contribute behavior to views that already exist in the workbench. This is done through the
-<b><a href="../reference/extension-points/org_eclipse_ui_viewActions.html"> org.eclipse.ui.viewActions</a></b> 
-extension point. This extension point allows plug-ins to contribute menu items, submenus and tool bar entries to an
-existing view's local
-pull-down menu and local tool bar. </P>
-<P >
-You may have noticed an item in the navigator's local tool bar that becomes
-enabled whenever a readme file is selected. This item also appears in the
-navigator's local
-pull-down menu. These actions appear because the readme tool plug-in contributes
-them using the
-<b> viewActions</b> extension.</P>
-
-<img src="images/readmeviewaction.png" alt="" border="0">
-<P >
-The relevant <b> plugin.xml</b> contribution is below.</P>
-<pre>
-&lt;extension
-    point = &quot;org.eclipse.ui.viewActions&quot;&gt;
-      &lt;viewContribution 
-         id=&quot;org.eclipse.ui.examples.readmetool.vc1&quot; 
-         targetID=&quot;org.eclipse.ui.views.ResourceNavigator&quot;&gt;        
-	   &lt;action id=&quot;org.eclipse.ui.examples.readmetool.va1&quot; 
-              label=&quot;%PopupMenu.ResourceNav.label&quot; 
-	      menubarPath=&quot;additions&quot;
-              toolbarPath=&quot;additions&quot; 
-              icon=&quot;icons/obj16/editor.png&quot; 
-              tooltip=&quot;%PopupMenu.ResourceNav.tooltip&quot; 
-   	      helpContextId=&quot;org.eclipse.ui.examples.readmetool.view_action_context&quot;
-              class=&quot;org.eclipse.ui.examples.readmetool.ViewActionDelegate&quot; 
-              enablesFor=&quot;1&quot;&gt; 
-		&lt;selection class=&quot;org.eclipse.core.resources.IFile&quot; name=&quot;*.readme&quot;/&gt; 
-	   &lt;/action&gt;
-      &lt;/viewContribution&gt;
- &lt;/extension&gt;
-</pre>
-<P >
-A view contribution with a unique id is specified. The view to which we are adding
-the action is specified in the
-<b> targetID</b>. We are contributing to the resource
-navigator's menu.&nbsp; We specify the label and the menu bar and
-tool bar locations for the new action.&nbsp; (For a complete discussion of menu and toolbar locations, see
-<a HREF="workbench_menupaths.htm" CLASS="XRef"> Menu and toolbar paths</a>). </P>
-<P >
-We also specify the conditions under which the action should be enabled. You can see that this action will be enabled when there is one selection
-(<b>enablesFor=&quot;1&quot;</b>) of type
-<b><a href="../reference/api/org/eclipse/core/resources/IFile.html">IFile</a>
-(class=&quot;org.eclipse.core.resources.IFile&quot;)</b>, whose name has
-&quot;<b>.readme</b>&quot; in the file extension (<b>name=&quot;*.readme&quot;</b>). Sure enough, that's exactly what happens when you click around in the resource navigator.&nbsp;&nbsp;</P>
-<P >
-The information in the <b> plugin.xml</b> is all that's needed to add items to menus and tool
-bars since plug-in code will only run when the action is actually selected from the menu or toolbar.
-To provide the action behavior, the implementation class specified in the
-<b> plugin.xml</b> must implement the <b><a href="../reference/api/org/eclipse/ui/IViewActionDelegate.html"> IViewActionDelegate</a></b> interface. </P>
-<P >
-In this example, the readme plug-in supplies <b> ViewActionDelegate</b> to implement the action. If you browse this class you will see that it includes methods for
-remembering its view, handling selection changes, and invoking its action.&nbsp;
-When invoked the action itself simply launches a dialog that announces it was executed.</P>
-<pre>
-public void run(org.eclipse.jface.action.IAction action) {
-	MessageDialog.openInformation(view.getSite().getShell(),
-		MessageUtil.getString(&quot;Readme_Editor&quot;),  
-		MessageUtil.getString(&quot;View_Action_executed&quot;)); 
-}</pre>
-<P >
-Although this action is simple, we can imagine how using selections and more
-functional dialogs could make this action do something more interesting.</P>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_views.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_views.htm
deleted file mode 100644
index be732e7..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_views.htm
+++ /dev/null

@@ -1,150 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>org.eclipse.ui.views</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-org.eclipse.ui.views</H3>
-
-<P >A view is a workbench part that can navigate a hierarchy of information or display properties for an
-object.&nbsp; Only one instance of any given view
-is open in a workbench page.&nbsp; When the user makes selections or other changes in a view,
-those changes are immediately reflected in the workbench. Views are often provided to support a corresponding editor.&nbsp;
-For example, an <b>outline</b> view shows a structured view of the information
-in an editor.&nbsp; A <b>properties</b> view shows the properties of an object
-that is currently being edited.</P>
-
-<P >
-The extension point <b><a href="../reference/extension-points/org_eclipse_ui_views.html">org.eclipse.ui.views</a></b>
-allows plug-ins to add views to the workbench. Plug-ins that contribute a view must register the view in their
-<b> plugin.xml </b> file and provide&nbsp; configuration information about the view, such as its implementation class, the category (or group) of views to which it belongs, and the name and icon that should be used to describe the view in menus and labels.</P>
-<P >
-The interface for views is defined in <b><a href="../reference/api/org/eclipse/ui/IViewPart.html">IViewPart</a></b>, but plug-ins
-can choose to extend the
-<b><a href="../reference/api/org/eclipse/ui/part/ViewPart.html"> ViewPart</a></b> class rather than implement an
-<b><a href="../reference/api/org/eclipse/ui/IViewPart.html"> IViewPart</a></b> from scratch.</P>
-<P >
-We implemented a minimal view extension in the hello world example. Now we'll look at one that is aware of other workbench views and responds to user navigation and selection
-changes in the workbench. First,
-let's take a look at the declaration of the extension in the <b>plugin.xml</b>.</P>
-<pre>&lt;extension 
-   point=&quot;org.eclipse.ui.views&quot;&gt;
-	&lt;category 
-	   id=&quot;org.eclipse.ui.examples.readmetool&quot;
-	   name=&quot;%Views.category&quot;&gt;
-	&lt;/category&gt;
-	&lt;view
- 	   id=&quot;org.eclipse.ui.examples.readmetool.views.SectionsView&quot;
-	   name=&quot;%Views.ReadmeSections&quot;
-	   icon=&quot;icons/view16/sections.png&quot;
-	   category=&quot;org.eclipse.ui.examples.readmetool&quot;
-	   class=&quot;org.eclipse.ui.examples.readmetool.ReadmeSectionsView&quot;&gt;
-	&lt;/view&gt;
-&lt;/extension&gt;
-</pre>
-<P >
-This should look pretty familiar. We see that a new view, <b>ReadmeSectionsView</b>, is contributed to the workbench. The
-<b>view id</b>, <b>name</b>,
-and
-<b> category</b> are specified as we've seen before. An <b> icon</b> is also provided
-for the view, using a path relative to the plug-in's installation directory. </P>
-<P >
-Let's look at the <b>ReadmeSectionsView</b>. You can show any view in the
-workbench by choosing <b>Window-&gt;Show View-&gt;Other... </b> and selecting the view from the <b> Show View</b> list.</P>
-<P >
-When we show the <b>ReadmeSectionsView</b>, a view with a list in it pops up.
-The list is empty unless we click on a file with an extension of <b>.readme</b>, in which case
-the list is populated with sections from the readme file.</P>
-
-<img src="images/readmeview.png" alt="" border="0">
-<P >
-How does the plug-in recognize the readme file and how did it know about selection changes? If we can track down
-the answers to these questions, we are well on our way to understanding how to build integrated workbench plug-ins.</P>
-<P >
-We'll start with the familiar <b>createPartControl</b>
-method.&nbsp; As we saw in the Hello World example, this is where the widgets
-that represent a view are created.&nbsp; We'll ignore some of the code to get
-started.</P>
-<pre>
-   public void createPartControl(Composite parent) {
-      viewer = new ListViewer(parent);
-      ...
-      // add myself as a global selection listener
-      getSite().getPage().addSelectionListener(this);
-
-      // prime the selection
-      selectionChanged(null, getSite().getPage().getSelection());
-   }
-</pre>
-<P >
-The view creates and stores a ListViewer and registers itself as a selection listener
-on its page. It obtains the page from an
-<b><a href="../reference/api/org/eclipse/ui/IViewSite.html">IViewSite</a></b>, which contains information about the view's context, such as its workbench window,
-its containing page, and its plug-in. When we are notified of a selection change, what happens?&nbsp;
-The following code is executed:</P>
-<pre>
-   public void selectionChanged(IWorkbenchPart part, ISelection sel) {
-      //if the selection is a readme file, get its sections.
-      AdaptableList input = ReadmeModelFactory.getInstance().getSections(sel);
-      viewer.setInput(input);
-   }
-</pre>
-<P >
-It looks like the <b> ReadmeModelFactory</b> class is responsible for turning the selection into readme
-sections and these sections are input for
-the viewer that we created in the <b>createPartControl</b>
-method.</P>
-<P >
-But how did the viewer populate its list widgets?&nbsp; For now, let's assume that once the viewer was told its input element, it knew how to populate
-its list widget with the information - it is a ListViewer, after all.&nbsp; If you must know right now what this viewer is all about, go to <a HREF="jface_viewers.htm" CLASS="XRef">Viewers</a>.&nbsp;</P>
-<P >
-We still do not know how readme files are detected or where the file's section
-information comes from.&nbsp; A quick look at the
-<b> ReadmeModelFactory</b> sheds some light.</P>
-<pre>
-   public AdaptableList getSections(ISelection sel) {
-      // If sel is not a structured selection just return.
-      if (!(sel instanceof IStructuredSelection))
-         return null;
-      IStructuredSelection structured = (IStructuredSelection)sel;
-
-      //if the selection is a readme file, get its sections.
-      Object object = structured.getFirstElement();
-      if (object instanceof IFile) {
-         IFile file = (IFile) object;
-         String extension = file.getFileExtension();
-         if (extension != null &amp;&amp; extension.equals(IReadmeConstants.EXTENSION)) {
-            return getSections(file);
-         }
-      }
-
-      //the selected object is not a readme file
-      return null;
-   }
-</pre>
-<P >We check the selection to see if it is a structured (multiple)
-selection.&nbsp; (The concept of a structured selection comes from JFace <a href="jface_viewers.htm">viewers</a>.)&nbsp;
-For the first object in the selection, we check to see whether it is a file (<b><a href="../reference/api/org/eclipse/core/resources/IFile.html">IFile</a></b>)
-resource.&nbsp; If it is, we check its extension to see if it matches the &quot;<b>.readme</b>&quot;
-extension.&nbsp; Once we know we have a readme file, we can use other methods to
-parse the sections.&nbsp;&nbsp; You can browse the rest of <b>ReadmeModelFactory</b>,&nbsp;
-<b>MarkElement</b>, and <b> DefaultSectionsParser</b> for the
-details about the file parsing. </P>
-<P >
-We've covered a lot of common workbench concepts by studying this extension. Now we'll move on to some other workbench extensions and examine how your plug-in can further contribute to the workbench UI. </P>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_guiding.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_guiding.htm
deleted file mode 100644
index ae868d6..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_guiding.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Guiding the user through tasks</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h2>
-Guiding the user through tasks</h2>
-<P>
-Even when the platform UI filters out unneeded functionality, there is still a steep learning
-curve faced by a new user.  The platform UI introduces several mechanisms for helping the user choose what
-task needs to be done and guiding the user through the steps in that task.  These mechanisms are used by
-the workbench itself to help guide Eclipse SDK users through tasks.
-</p>
-<ul>
-<li><b><a href="workbench_advext_cheatsheets.htm">Cheat sheets</a></b> can help guide the user through a series of 
-steps in order to achieve some
-overall goal.  Some steps can be performed by the cheat sheet, and some are described so that the user
-can manually complete the step.</li>
-<li><b><a href="workbench_advext_compositeCheatsheets.htm">Composite cheat sheets</a></b> 
-can guide the user through larger problems by breaking that problem into tasks. 
-Each task is represented by a simple cheat sheet. </li>
-<li><b><a href="workbench_advext_intro.htm">Initial User Experience</a></b> allows plug-ins to define pages that help introduce the product to the end user the first
-time the platform is started.  These pages can reference help content or launch the appropriate cheat sheet
-for a task.</li>
-</ul>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_jobs.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_jobs.htm
deleted file mode 100644
index 2d30cef..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_jobs.htm
+++ /dev/null

@@ -1,267 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Workbench concurrency support</title>
-  <link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-<body style="background-color: rgb(255, 255, 255);">
-<h2>
-Workbench concurrency support</h2>
-<p>
-We've seen that the JFace UI framework provides basic support for
-showing task progress in a dialog (see <a href="jface_operations.htm">Long
-running operations</a> for details). In <a href="runtime_jobs.htm">Concurrency
-infrastructure</a>, we reviewed the platform runtime support for
-concurrency and long running operations. Now we will look at how
-the platform UI enhances this infrastructure in the <b><a href="../reference/api/org/eclipse/ui/progress/package-summary.html">
-org.eclipse.ui.progress</a></b> package. This package supplies the UI
-for showing job progress in the workbench and defines additional
-support for jobs that run in the UI thread.<br>
-</p>
-<p>First, let's look at the different kinds of background operations that may be running
-and how they are shown in the workbench UI:</p>
-<ul>
-  <li>
-    <p><i>User initiated</i> jobs are those that the user has triggered. 
-The workbench will automatically show user jobs in a modal progress
-dialog with a button to allow the user to run the operation in the
-background and continue working. A global preference is used to indicate whether user
-jobs should always run in the background.  User jobs are distinguished as such
-in the Job API using (<a href="../reference/api/org/eclipse/core/runtime/jobs/Job.html#setUser(boolean)">Job#setUser</a>).
-Examples of user jobs include building, checking out a project, synchronizing
-with the repository, exporting a plug-in, and searching. </p>
-  </li>
-  <li>
-    <p><i>Automatically triggered</i> jobs have a meaning for users but are not initiated by the 
-user. These jobs are shown in the progress view and in the
-status line, but a modal progress dialog won't be shown when they are run.  
-Examples include autobuild and scheduled synchronization.</p>
-  </li>
-  <li>
-    <p><i>System operations</i> are not triggered by the user and can be considered a platform
-implementation detail. These jobs are created by setting the system
-flag using(<a href="../reference/api/org/eclipse/core/runtime/jobs/Job.html#setSystem(boolean)">Job#setSystem</a>).
-Examples of system jobs include jobs that lazily populate widgets or compute decorations and annotations for views.
- </p>
-  </li>
-</ul>
-<p><br>
-Given an environment where several things may be happening at the same
-time, a user needs the following:</p>
-<ul>
-  <li>
-    <p>Indication that a long running operation has started.</p>
-    <p><br>
-User jobs are shown to the user in a progress dialog giving immediate
-feedback, whereas automatically triggered jobs are shown in the status
-line and progress view. Jobs that affect a part should
-be <a href="#site_service">scheduled or registered with the part</a>
-so that the workbench can provide hints to the user that something is running
-that affects the part.</p>
-    <p><br>
-    </p>
-  </li>
-  <li>
-    <p>Indication that an operation has ended.</p>
-    <p><br>
-The user can easily know when a user job ends because the progress
-dialog closes. For non-user jobs, there are a couple of feedback mechanisms
-available. If the job is <a href="#site_service">scheduled or
-registered with a part</a> then the part's progress hint will show when
-it is complete. If a job returns an error, an error indicator will
-appear in the bottom right of the status line showing a hint that an
-error has occured.</p>
-    <p><br>
-    </p>
-  </li>
-  <li>
-    <p>Indication of interesting new results, or new information, 
-    without stealing focus by using a dialog.</p>
-    <p><br>
-A user job can directly show the results to the user when the operation
-completes. For non-user jobs, it is recommended to use something other than a
-dialog to show results, so that the user is not interrupted.  For example, a view could be opened
-when the job starts and the results shown in this view without disrupting the
-user's workflow.  In addition, <a href="#job_properties">job properties</a> can be
-added to the job to indicate that it
-should be kept in the progress view and that it provides an action that will show
-the results. In this case, a warning indication will appear in the bottom right
-corner of the status line when a job remains in the progress view and
-has results to show the user.</p>
-    <p><br>
-    </p>
-  </li>
-  <li>
-    <p>A general feeling of being in control of what is running, with
-    the ability to monitor and cancel background operations.</p>
-    <p><br>
-User jobs provide the best control for the user since they are easily
-cancelled and provide strong indication of blocking or conccurent operations running
-via the <b>Details</b> tab of the progress dialog. Note that the enhanced
-progress dialog that provides the <b>Details</b> area is only shown when plug-ins use
-<a
- href="../reference/api/org/eclipse/ui/progress/IProgressService.html#busyCursorWhile(org.eclipse.jface.operation.IRunnableWithProgress)">IProgressService#busyCursorWhile</a>
-or <a
- href="../reference/api/org/eclipse/ui/progress/IProgressService.html#runInUI(org.eclipse.jface.operation.IRunnableContext, org.eclipse.jface.operation.IRunnableWithProgress, org.eclipse.core.runtime.jobs.ISchedulingRule)">IProgressService#runInUI</a>.
-In addition, the progress view provides access to jobs that are running.</p>
-    <p><br>
-    </p>
-  </li>
-  <li>
-    <p>Consistent reporting of progress by all installed plug-ins.</p>
-    <p><br>
-The advantage of using the progress service API is that users get a consistent progress experience. </p>
-    <p><br>
-    </p>
-  </li>
-</ul>
-<h3>Progress service</h3>
-<p>
-The workbench progress service (<a
- href="../reference/api/org/eclipse/ui/progress/IProgressService.html">IProgressService</a>)
-is the primary interface to the workbench progress support. It can be
-obtained from the workbench and then used to show progress
-for both background operations and operations that run in the UI
-thread. The main purpose of this class is to provide one-stop shopping
-for running operations, removing the need for plug-in developers to 
-decide what mechanism should be used for showing progress in a given situation.
-Another advantage is that the progress dialog shown
-with these methods provides good support for indicating when an operation is
-blocked by another and gives the user control to resolve the conflict.
-Where possible, long running operations should be run using
-<a
- href="../reference/api/org/eclipse/ui/progress/IProgressService.html#busyCursorWhile(org.eclipse.jface.operation.IRunnableWithProgress)">IProgressService#busyCursorWhile</a>:
-</p>
-<pre>
-   IProgressService progressService = PlatformUI.getWorkbench().getProgressService();
-   progressService.<b>busyCursorWhile</b>(new IRunnableWithProgress(){
-      public void run(IProgressMonitor monitor) {
-         //do non-UI work
-      }
-   });
-</pre>
-<p>This method will initially put up a busy cursor, and replace it with
-a progress dialog if the operation
-lasts longer than a specified time threshhold. The advantage of this
-method over using a progress dialog is that the progress dialog won't be shown
-if the operation is short
-running . If your operation must
-update the UI, you can always use <a
- href="../reference/api/org/eclipse/swt/widgets/Display.html#asyncExec(java.lang.Runnable)">Display.asyncExec</a>
-or <a
- href="../reference/api/org/eclipse/swt/widgets/Display.html#syncExec(java.lang.Runnable)">Display.syncExec</a>
-to run the code that modifies the UI.</p>
-<p> If an operation must be run in
-its entirety in the UI thread, then <a
- href="../reference/api/org/eclipse/ui/progress/IProgressService.html#runInUI(org.eclipse.jface.operation.IRunnableContext, org.eclipse.jface.operation.IRunnableWithProgress, org.eclipse.core.runtime.jobs.ISchedulingRule)">IProgressService#runInUI</a>
- should be used.  This method will also display a progress
-dialog if the operation is blocked and give the user control.</p>
-<pre>
-   progressService.<b>runInUI</b>(
-      PlatformUI.getWorkbench().getProgressService(),
-      new IRunnableWithProgress() {
-         public void run(IProgressMonitor monitor) {
-            //do UI work
-         }
-      },
-      Platform.getWorkspace().getRoot());
-</pre>
-<p>The third parameter can be null, or a scheduling rule for the
-operation. In this example, we are specifying the workspace root which will
-essentially lock the workspace while this UI operation is run.</p>
-<p>
-You can also register an icon for a job family with the progress service
-so that the progress view can show the icon next to the running
-job. Here is an example that shows how the auto-build job family is associated with its
-icon:</p>
-<pre>
-   IProgressService service = PlatformUI.getWorkbench().getProgressService();
-   ImageDescriptor newImage = IDEInternalWorkbenchImages.getImageDescriptor(
-      IDEInternalWorkbenchImages.IMG_ETOOL_BUILD_EXEC);
-   service.<b>registerIconForFamily</b>(newImage, ResourcesPlugin.FAMILY_MANUAL_BUILD);
-   service.registerIconForFamily(newImage, ResourcesPlugin.FAMILY_AUTO_BUILD);
-</pre>
-<h3><a name="site_service"></a>Showing that a part is busy</h3>
-<p>
-<a
- href="../reference/api/org/eclipse/ui/progress/IWorkbenchSiteProgressService.html"><b>IWorkbenchSiteProgressService</b></a>
-includes API for scheduling jobs that change the appearance of a workbench
-part while the job is running. If your plug-in is running background
-operations that affect the state of a part, you can schedule the job via
-the part and the user will get feedback that the part is busy. Here is
-an example:</p>
-<pre>
-   IWorkbenchSiteProgressService siteService =
-      (IWorkbenchSiteProgressService)view.getSite().getAdapter(IWorkbenchSiteProgressService.class);
-   siteService.<b>schedule</b>(job, 0 /* now */, true /* use the half-busy cursor in the part */);
-</pre>
-<h3><a name="job_properties"></a>Progress Properties for Jobs</h3>
-<p>The workbench defines progress-related properties for jobs in <a
- href="../reference/api/org/eclipse/ui/progress/IProgressConstants.html">IProgressConstants
-</a>.  These can be used to control how a job is shown in the progress
-view. These can be used to tell the progress view to keep (<a
- href="../reference/api/org/eclipse/ui/progress/IProgressConstants.html#KEEP_PROPERTY">IProgressConstants#KEEP_PROPERTY</a>)
-your job in the view after it has finished, or only keep one (<a
- href="../reference/api/org/eclipse/ui/progress/IProgressConstants.html#KEEPONE_PROPERTY">IProgressConstants#KEEPONE_PROPERTY</a>)
-job at a time in the view. You can also associate an action (<a
- href="../reference/api/org/eclipse/ui/progress/IProgressConstants.html#ACTION_PROPERTY">IProgressConstants#ACTION_PROPERTY</a>)
-with a job. When a job has an associated action, the progress view
-shows a hyperlink so that a user can run the action. You can also find
-out if a user job is currently being shown in a progress dialog (<a
- href="../reference/api/org/eclipse/ui/progress/IProgressConstants.html#PROPERTY_IN_DIALOG">IProgressConstants#PROPERTY_IN_DIALOG</a>).
-A hint is provided in the bottom right of the status line when an
-action is available. The following example uses these properties:</p>
-<pre>
-   Job job = new Job("Do Work") {
-      public IStatus run(IProgressMonitor monitor) {
-         // do some work.  
-         // Keep the finished job in the progress view only if it is not running in the progress dialog
-         Boolean inDialog = (Boolean)getProperty(IProgressConstants.PROPERTY_IN_DIALOG);
-         if(!inDialog.booleanValue())
-            <b>setProperty</b>(IProgressConstants.KEEP_PROPERTY, Boolean.TRUE);
-      }
-   };
-   job.<b>setProperty</b>(IProgressConstants.ICON_PROPERTY, Plugin.getImageDescriptor(WORK_IMAGE));
-   IAction gotoAction = new Action("Results") {
-      public void run() {
-         // show the results
-      }
-   };
-   job.<b>setProperty</b>(IProgressConstants.ACTION_PROPERTY, gotoAction);
-   job.setUser(true);
-   job.schedule();
-</pre>
-<h3>Workbench jobs</h3>
-<p>
-Where possible, long running operations should be performed outside of
-the UI thread. However, this cannot always be
-avoided when the operation's purpose is to update the UI. <a
- href="swt_threading.htm">SWT threading issues</a> explains
-how this can be done using the SWT <b><a
- href="../reference/api/org/eclipse/swt/widgets/Display.html"> Display</a></b>.
-The workbench defines a special job, <a
- href="../reference/api/org/eclipse/ui/progress/UIJob.html"><b>UIJob</b></a>,
-whose run method runs inside an SWT <tt>asyncExec</tt>. Subclasses of <a
- href="../reference/api/org/eclipse/ui/progress/UIJob.html"><b>UIJob</b></a>
-should implement the method <b>runInUIThread</b> instead of the <b>run</b>
-method.
-</p>
-<p>
-<a href="../reference/api/org/eclipse/ui/progress/WorkbenchJob.html"><b>WorkbenchJob</b></a>
-extends
-<a href="../reference/api/org/eclipse/ui/progress/UIJob.html"><b>UIJob</b></a>
-so that the job can only be scheduled or run when the workbench is running.
-As always, you should avoid excessive work in the UI thread because the UI will
-not refresh for the duration of the UI Job.
-</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_menupaths.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_menupaths.htm
deleted file mode 100644
index 7629a55..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_menupaths.htm
+++ /dev/null

@@ -1,336 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Menu and toolbar paths
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h2>
-Menu and toolbar paths</h2>
-<P >
-We've seen many action contributions that specify the path for the location of their action. Let's take a close look at what these paths mean.&nbsp;&nbsp;</P>
-
-<h3 >
-Menu paths</h3>
-
-<P >
-We'll look at menu paths first by looking at the workbench <b>Help</b> menu.</P>
-
-<H4>
-Named groups in the workbench</H4>
-<P >
-The locations for inserting new menus and menu items are defined using named groups. You can think of
-a named group as a slot or placeholder that allows you to insert your menu items
-at certain points in a menu bar or pulldown menu.</P>
-<P >
-The workbench defines all of its group slot names in the classes <b><a href="../reference/api/org/eclipse/ui/IWorkbenchActionConstants.html">IWorkbenchActionConstants</a></b>
-and <b><a href="../reference/api/org/eclipse/ui/ide/IIDEActionConstants.html">IIDEActionConstants</a></b>. 
-(Two different classes are used since resource-related menu items are factored out of the generic workbench).
-For each workbench menu, named groups are placed in the menu at locations where it is expected that
-plug-ins will insert new actions.</P>
-<P >
-The following description of the help menu is adapted from the <a href="../reference/api/org/eclipse/ui/IWorkbenchActionConstants.html"><b> IWorkbenchActionConstants</b></a>
-class definition.</P>
-<pre>
-   Standard Help menu actions
-   Start group - HELP_START - &quot;start&quot;
-   End group - HELP_END - &quot;end&quot;
-</pre>
-<P >
-The standard workbench help menu defines a named group called &quot;<b>start</b>,&quot; followed by a named group called &quot;<b>end</b>,&quot;.
-Defining two groups gives plug-ins a little more control over where their contributed
-items will be positioned within the help menu.&nbsp; When you define a menu, you can define as many slots as you like. Adding more slots gives 
-other plug-ins more control over where their contributions appear relative to existing contributions. </P>
-<P >
-Plug-ins that add a menu item to the help menu can use these group names to decide where their
-menu item will go.  For example, the cheatsheet plug-in adds an action
-set containing the &quot;Cheat Sheets...&quot; menu to the workbench.&nbsp; Here's
-the markup from the <b>org.eclipse.ui.cheatsheets</b> plug-in's
-<b>plugin.xml</b>. </P>
-<pre>
-&lt;extension
-	point="org.eclipse.ui.actionSets"&gt;
-	&lt;actionSet
-		label="%CHEAT_SHEETS"
-		visible="true"
-		id="org.eclipse.ui.cheatsheets.actionSet"&gt;
-		&lt;action
-			label="%CHEAT_SHEETS_MENU"
-			class="org.eclipse.ui.internal.cheatsheets.actions.CheatSheetHelpMenuAction"
-			<b>menubarPath="help/helpStart"</b>
-			id="org.eclipse.ui.cheatsheets.actions.CheatSheetHelpMenuAction"&gt;
-		&lt;/action&gt;
-	&lt;/actionSet&gt;
-&lt;/extension&gt;
-</pre>
-<P >
-The new help action will be placed in the help menu, inside the <b>helpStart</b> group.</P>
-
-
-<H4>
-Fully qualified menu paths</H4>
-<P >
- A complete menu path is simply &quot;menu name/group
- name.&quot;&nbsp; Most menu names for the workbench are defined in
-<b><a href="../reference/api/org/eclipse/ui/IWorkbenchActionConstants.html">IWorkbenchActionConstants</a></b>. 
-(Resource-related menu names are defined in <b><a href="../reference/api/org/eclipse/ui/ide/IIDEActionConstants.html">IIDEActionConstants</a></b>.)
-If we look for the name of the help menu in this class, we'll find
-that the fully qualified path name for our help action is
- &quot;<b>help/helpEnd</b>.&quot; </P>
-<P >
-Some menus have nested submenus. This is where longer paths come into play. If the help menu had defined a submenu 
-called &quot;<b>submenu</b>&quot; with a named group called &quot;<b>submenuStart</b>,&quot; 
-then the fully qualified menu path for an action in the new submenu would be 
-&quot;<b>help/submenu/submenuStart</b>.&quot;</P>
-
-
-<H4>
-<a name="workbench_menus_nls">
-Externalizing UI labels</a></H4>
-<p>The example above demonstrates a technique for externalizing strings
-that appear in the UI.&nbsp; Externalized strings are used to make translating the plug-in's UI to
-other languages simpler.&nbsp; We can externalize the strings in our <b>plugin.xml
-</b>files by replacing the string with a key (<b>%CHEAT_SHEETS_MENU</b>) and creating entries in the <b>plugin.properties</b>
-file of the form:</p>
-<pre>
-	CHEAT_SHEETS_MENU = Cheat Sheets...
-</pre>
-<P >
-The <b>plugin.properties</b> file can be
-translated for different languages and the <b>plugin.xml</b>
-will not need to be modified.</P>
-
-
-<H4>
-Adding new menus and groups</H4>
-<P >
-In many of the examples we've seen so far, the actions contributed by the sample plug-ins have been added to existing named groups within menus.</P>
-<P >
-The <b><a href="../reference/extension-points/org_eclipse_ui_actionSets.html">actionSets</a></b>,
-<b><a href="../reference/extension-points/org_eclipse_ui_viewActions.html">viewActions</a></b>,
-<b><a href="../reference/extension-points/org_eclipse_ui_editorActions.html">editorActions</a></b>, and
-<b><a href="../reference/extension-points/org_eclipse_ui_popupMenus.html"> popupMenus</a></b> extension points also allow you to define new menus and groups within your contribution. This means that you can define new submenus or new
-pull-down menus and contribute your actions to these new menus. In this case, the path for your new action will contain the name of your newly defined menu. </P>
-<P>
-We saw this technique when the readme tool defined a new menu for its action
-set.&nbsp; Let's look at the markup one more time now that we've looked at menu
-paths in more detail. </P>
-<pre>
-   &lt;extension point = &quot;org.eclipse.ui.actionSets&quot;&gt;
-   &lt;actionSet id=&quot;org_eclipse_ui_examples_readmetool_actionSet&quot;
-	   label=&quot;%ActionSet.name&quot;
-	   visible=&quot;true&quot;&gt;
-	   &lt;<b>menu id=&quot;org_eclipse_ui_examples_readmetool&quot;</b>
-		   label=&quot;%ActionSet.menu&quot;
-		   <b>path=&quot;window/additions&quot;</b>&gt; 
-		   &lt;separator name=&quot;slot1&quot;/&gt;
-		   &lt;separator name=&quot;slot2&quot;/&gt;
-		   &lt;separator name=&quot;slot3&quot;/&gt;
-	   &lt;/menu&gt;
-	   &lt;action id=&quot;org_eclipse_ui_examples_readmetool_readmeAction&quot;
-		   <b>menubarPath=&quot;window/org_eclipse_ui_examples_readmetool/slot1&quot;</b>
-		   toolbarPath=&quot;readme&quot;
-		   label=&quot;%ReadmeAction.label&quot;
-		   tooltip=&quot;%ReadmeAction.tooltip&quot;
-		   helpContextId=&quot;org.eclipse.ui.examples.readmetool.open_browser_action_context&quot;
-		   icon=&quot;icons/ctool16/openbrwsr.png&quot;
-		   class=&quot;org.eclipse.ui.examples.readmetool.WindowActionDelegate&quot;
-		   enablesFor=&quot;1&quot;&gt;
-		   &lt;selection class=&quot;org.eclipse.core.resources.IFile&quot;
-				name=&quot;*.readme&quot;&gt;
-		   &lt;/selection&gt;
-	   &lt;/action&gt;
-	   ...
-</pre>
-<P >We added a new menu called&nbsp; &quot;<b>org_eclipse_ui_examples_readmetool</b>&quot;
-whose label is defined in by the key &quot;<b>%ActionSet.name</b>&quot; in the
-properties file. Within this menu, we define three named
-groups:&nbsp; &quot;<b>slot1</b>,&quot; &quot;<b>slot2</b>,&quot;
-and &quot;<b>slot3</b>.&quot;&nbsp; We add this new
-menu to the path &quot;<b>window/additions</b>.&quot;</P>
-<P >If we go back to <b><a href="../reference/api/org/eclipse/ui/IWorkbenchActionConstants.html">IWorkbenchActionConstants</a></b>,
-we see this definition of the window menu in the javadoc:</P>
-<pre>
-    * &lt;h3&gt;Standard Window menu actions&lt;/h3&gt;
-    * &lt;ul&gt;
-    * &lt;li&gt;Extra Window-like action group (&lt;code&gt;WINDOW_EXT&lt;/code&gt;)&lt;/li&gt; 
-</pre>
-<P >
-If we look further at the class definition, we will see these related
-definitions: </P>
-
-
-<pre>
-   public static final String MENU_PREFIX = &quot;&quot;;
-   ...
-   public static final String M_WINDOW = MENU_PREFIX+&quot;window&quot;;
-   ...
-   public static final String MB_ADDITIONS = &quot;additions&quot;;  // Group.
-   ...
-   public static final String WINDOW_EXT = MB_ADDITIONS;   // Group.
-</pre>
-
-
-<P >
-From this information, we can piece together the path for adding something to
-the workbench &quot;Window&quot; menu.&nbsp; The menu itself is called &quot;<b>window</b>&quot;
-and it defines one slot called &quot;<b>additions</b>.&quot;&nbsp;
-We use the path &quot;<b>window/additions</b>&quot; to
-add our new menu. </P>
-
-
-<P >
-In the action set declaration, we add an action to our newly defined menu, using
-the path &quot;<b>window/org_eclipse_ui_examples_readmetool/slot1</b>.&quot; </P>
-
-
-<P >
-<img src="images/readmeactionsetmenu.png" alt="" border="0"> </P>
-
-
-<P >Other plug-ins could add to our menu by using this same path (or perhaps one
-of the other slots) to add one of their own menus.&nbsp;&nbsp; </P>
-
-
-<P >In the readme tool example, we use the <b>separator</b> attribute to
-identify the group names.&nbsp; This will cause a separator line to appear
-between these groups when they contain items.&nbsp; We could instead use the <b>groupMarker</b>
-attribute if we want to define a named group without showing any separators in
-the menu to distinguish between the groups. </P>
-
-
-<h3 >Tool bar paths </h3>
-
-
-<p>Tool bar paths work similarly to menu paths.&nbsp;&nbsp;</p>
-
-
-<h4>Named tool bars in the workbench</h4>
-
-
-<p>The workbench tool bar is composed of
-tool bars contributed by different plug-ins, including the workbench
-itself.&nbsp; Within any particular tool bar, there are named groups or slots that can be used for inserting new tool bar items.
-&nbsp;&nbsp;&nbsp;</p>
-<P >
-The following description of the workbench tool bars is adapted from the <a href="../reference/api/org/eclipse/ui/IWorkbenchActionConstants.html"><b> IWorkbenchActionConstants</b></a>
-class definition.</P>
-<pre>// Workbench toolbar ids
-public static final String TOOLBAR_FILE = &quot;org.eclipse.ui.workbench.file&quot;
-public static final String TOOLBAR_NAVIGATE = &quot;org.eclipse.ui.workbench.navigate&quot;; 
-
-// Workbench toolbar group ids.  To add an item at the beginning of the group, 
-// use the GROUP id.  To add an item at the end of the group, use the EXT id.
-public static final String PIN_GROUP = &quot;pin.group&quot;; 
-public static final String HISTORY_GROUP = &quot;history.group&quot;; 
-public static final String NEW_GROUP = &quot;new.group&quot;; 
-public static final String SAVE_GROUP = &quot;save.group&quot;; 
-public static final String BUILD_GROUP = &quot;build.group&quot;; </pre>
-<p>In the simplest case, a plug-in can contribute a tool bar item in its own
-tool bar.&nbsp; For example, the readme tool actions contributed to the menu are
-also given a tool bar path:  </p>
-<pre>
-&lt;action id=&quot;org_eclipse_ui_examples_readmetool_readmeAction&quot;&nbsp;&nbsp;
-   menubarPath=&quot;window/org_eclipse_ui_examples_readmetool/slot1&quot;
-&nbsp;&nbsp; <b>toolbarPath=&quot;readme&quot;
-</b>...</pre>
-<p>Since there is no reference to the workbench tool bar paths or groups, the
-readme actions appear in their own group on the tool bar.&nbsp; Specifying the
-following path would instead place the item in the file tool bar in the save
-group:</p>
-<pre>...
-&lt;action id=&quot;org_eclipse_ui_examples_readmetool_readmeAction&quot;&nbsp;&nbsp;
-   menubarPath=&quot;window/org_eclipse_ui_examples_readmetool/slot1&quot;
-&nbsp;&nbsp; <b>toolbarPath=&quot;org.eclipse.ui.workbench.file/save.group&quot;
-</b>...</pre>
-<p>The paths defined in <a href="../reference/api/org/eclipse/ui/IWorkbenchActionConstants.html"><b> IWorkbenchActionConstants</b></a>
- may be referenced in the tool bar paths of other plug-ins.</p>
-<h4>Adding to action sets of another plug-in</h4>
-<p>Suppose a plug-in wants its tool bar items better integrated with actions
-from a different plug-in?&nbsp; Let's look at how the external
-tools plug-in (<b>org.eclipse.ui.externaltools</b>) integrates its action with the debugger tool bar.&nbsp; The
-debugger (<b>org.eclipse.debug.ui</b>) defines its tool bar actions like this:</p>
-<pre>&lt;extension
-      point=&quot;org.eclipse.ui.actionSets&quot;&gt;
-   &lt;actionSet
-         label=&quot;%LaunchActionSet.label&quot;
-         visible=&quot;false&quot;
-         id=&quot;org.eclipse.debug.ui.launchActionSet&quot;&gt;
-   ...
-   &lt;action
-         <b>toolbarPath=&quot;debug&quot;</b>
-         id=&quot;org.eclipse.debug.internal.ui.actions.RunDropDownAction&quot;
-         hoverIcon=&quot;icons/full/ctool16/run_exc.png&quot;
-         class=&quot;org.eclipse.debug.internal.ui.actions.RunToolbarAction&quot;
-         disabledIcon=&quot;icons/full/dtool16/run_exc.png&quot;
-         icon=&quot;icons/full/etool16/run_exc.png&quot;
-         helpContextId=&quot;run_action_context&quot;
-         label=&quot;%RunDropDownAction.label&quot;
-         pulldown=&quot;true&quot;&gt;
-   &lt;/action&gt;
-   ...</pre>
-<p>Just like the readme tool, the debugger plug-in defines its own tool bar
-path, which means its tool bar items will be inside their own tool bar on the
-workbench.&nbsp; What does the external tools plug-in do?</p>
-<pre>&lt;extension point=&quot;org.eclipse.ui.actionSets&quot;&gt;
-	&lt;actionSet
-		id=&quot;org.eclipse.ui.externaltools.ExternalToolsSet&quot;
-		label=&quot;%ActionSet.externalTools&quot;
-		visible=&quot;true&quot;&gt;
-		...
-		&lt;action
-			id=&quot;org.eclipse.ui.externaltools.ExternalToolMenuDelegateToolbar&quot;
-			definitionId= &quot;org.eclipse.ui.externaltools.ExternalToolMenuDelegateToolbar&quot;
-			label=&quot;%Action.externalTools&quot;
-			<b>toolbarPath=&quot;org.eclipse.debug.ui.launchActionSet/debug&quot;</b>
-			disabledIcon=&quot;icons/full/dtool16/external_tools.png&quot;
-			icon=&quot;icons/full/etool16/external_tools.png&quot;
-			hoverIcon=&quot;icons/full/ctool16/external_tools.png&quot;
-			tooltip=&quot;%Action.externalToolsTip&quot;
-			pulldown=&quot;true&quot;
-			class=&quot;org.eclipse.ui.externaltools.internal.menu.ExternalToolMenuDelegate&quot;&gt;
-		&lt;/action&gt;
-	&lt;/actionSet&gt;
-&lt;/extension&gt;</pre><p>Note the use of the action set ID of the
-debugger in the tool bar path.&nbsp; Using an action set ID in the path denotes
-that the tool bar item should be placed in the tool bar used by the referenced
-action set.&nbsp;  Within a toolbar group, items are ordered by action set id, so
-for our example, the external tools action will appear after the debugger actions.&nbsp;</p>
-<p>When adding to an action set's tool bar, new groups can also be defined.&nbsp;
-If the external tools plug-in defined its <b> toolbarpath</b> as 
-<b>&quot;org.eclipse.debug.ui.launchActionSet/external&quot;</b> a new group would be created 
-for the action on the tool bar.&nbsp;  As with menus, tool bar groups are delineated by separators.&nbsp;</p>
-<h3 >Using paths from another plug-in </h3>
-
-
-<P >In general, it's not good practice to contribute to another plug-in's menu
-or tool bar by deriving the path name from the <b>plugin.xml</b> unless it has
-been marked specifically as being available for clients.&nbsp; It's possible that a future version of the plug-in could change the names of the
-paths.&nbsp; Two common ways to mark your plug-in's action set ids and paths as
-fair game are: </P>
-
-
-<ul>
-  <li>annotate the XML with comments that explicitly mark the menu path or
-    action set as usable by clients</li>
-  <li>define a public interface (much like <b><a href="../reference/api/org/eclipse/ui/IWorkbenchActionConstants.html">IWorkbenchActionConstants</a></b>)
-which specifies exactly which menus, tool bar groups, and slots are considered
-fair game for use by other plug-ins</li>
-</ul>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_menus.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_menus.htm
deleted file mode 100644
index b6988ba..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_menus.htm
+++ /dev/null

@@ -1,131 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Workbench menu contributions
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Workbench menu contributions</H2>
-<P >
-We've seen several different extension points that contribute to various menus and toolbars in the workbench. How do you know which one to use? The following table summarizes the various menu contributions and their use.</P>
-<TABLE BORDER="1" width="671">
-<TR>
-<TH ROWSPAN="1" COLSPAN="1" width="118">
-<P CLASS="CellHeading">
-Extension point name</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1" width="359">
-<P CLASS="CellHeading">
-Location of Actions</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1" width="335">
-<P CLASS="CellHeading">
-Details</P>
-</TH>
-</TR>
-<TR>
-<TD width="118">
-<P CLASS="CellBody">
-<b>
-viewActions</b></P>
-</TD>
-<TD width="359">
-<P CLASS="CellBody">
-Actions appear in a specific view's local toolbar and local pulldown menu.</P>
-</TD>
-<TD width="335">
-<P CLASS="CellBody">
-Contribute an action class that implements <b><a href="../reference/api/org/eclipse/ui/IViewActionDelegate.html">IViewActionDelegate</a></b>. Specify the id of the contribution and the id of the target view that should show the action. The label and image
-dictate the appearance of the action in the UI. The path specifies the location relative to the view's menu and toolbar items.</P>
-</TD>
-</TR>
-<TR>
-<TD width="118">
-<P CLASS="CellBody"><b>editorActions</b></P>
-</TD>
-<TD width="359">
-<P CLASS="CellBody">
-Actions are associated with an editor and appear in the workbench menu and/or tool bar.</P>
-</TD>
-<TD width="335">
-<P CLASS="CellBody">
-Contribute an action class that implements <b><a href="../reference/api/org/eclipse/ui/IEditorActionDelegate.html">IEditorActionDelegate</a></b>. Specify the id of the contribution and the id of the target editor that causes the action to be shown. The label and image specify the appearance of the action in the UI. Separate menu and toolbar paths specify the existence and location of the contribution in the workbench menu and toolbar.</P>
-</TD>
-</TR>
-<TR>
-<TD width="118">
-<P CLASS="CellBody">
-<b>
-popupMenus</b></P>
-</TD>
-<TD width="359">
-<P CLASS="CellBody">
-Actions appear in the popup menu of an editor or view. Actions associated with an object type show up in all popups of views
-and editors that show the object type. Actions associated with a specific popup menu appear only in that popup menu.</P>
-</TD>
-<TD width="335">
-<P CLASS="CellBody">
-<b>
-Object contributions</b> specify the type of object for which the action should appear in a popup menu. The action will be shown in all view
-and editor popups
-that contain the object type.&nbsp; Provide an action class that implements <b><a href="../reference/api/org/eclipse/ui/IObjectActionDelegate.html">IObjectActionDelegate</a></b>.&nbsp;<BR>
-<b>
-Viewer contributions</b> specify the id of the target popup menu in which the menu item should appear.&nbsp;
-Provide an action class that implements <b><a href="../reference/api/org/eclipse/ui/IEditorActionDelegate.html">IEditorActionDelegate</a></b>
-or <b><a href="../reference/api/org/eclipse/ui/IViewActionDelegate.html">IViewActionDelegate</a></b>.&nbsp;</P>
-</TD>
-</TR>
-<TR>
-<TD width="118">
-<P CLASS="CellBody">
-<b>
-actionSets</b></P>
-</TD>
-<TD width="359">
-<P CLASS="CellBody">
-Actions appear in the workbench main menus and toolbar. Actions are grouped into action sets. All actions in an action set will show up in the workbench menus and toolbars according to the user's selection of action sets
-and the current perspective shown in the workbench.&nbsp; May be influenced by
-actionSetPartAssociations (below).</P>
-</TD>
-<TD width="335">
-<P CLASS="CellBody">
-Contribute an action class that implements <b><a href="../reference/api/org/eclipse/ui/IWorkbenchWindowActionDelegate.html"> IWorkbenchWindowActionDelegate</a></b> or
-<b><a href="../reference/api/org/eclipse/ui/IWorkbenchWindowPulldownDelegate.html">IWorkbenchWindowPulldownDelegate</a></b>. Specify the
-<b> name</b> and <b> id</b> of the action set. Enumerate all of the actions that are defined for that action set. For each action, separate menu and toolbar paths specify the existence and location of the contribution in the workbench menu and toolbar.</P>
-</TD>
-</TR>
-<tr>
-<TD width="118">
-<P CLASS="CellBody">
-<b>
-actionSetPartAssociations</b></P>
-</TD>
-<TD width="359">
-<P CLASS="CellBody"> Actions sets are shown only when the specified views or
-editors are active.&nbsp; This is ignored if the user has customized the current
-perspective.</P>
-</TD>
-<TD width="335">
-<P CLASS="CellBody">
-Specify an action set by <b>id</b> and followed by one or more parts (by <b>id</b>)
-that must be active in the current perspective in order to show the action set.</P>
-</TD>
-</tr>
-</TABLE>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_perspectives.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_perspectives.htm
deleted file mode 100644
index 49d549e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_perspectives.htm
+++ /dev/null

@@ -1,176 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Perspectives</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h2>
-Perspectives</h2>
-<P >
-We've already seen some ways the workbench allows the user to control the appearance of plug-in functionality. Views can be hidden or shown using the
-<b>Window &gt;Show View</b> menu. Action sets can be hidden or shown using the <b>Window
-&gt;Customize
-Perspective...</b> menu. These features help the user organize the workbench. </P>
-
-<P >
-<b>
-Perspectives</b> provide an additional layer of organization inside a workbench
-window. Users can switch between perspectives as they move across tasks. A perspective defines
-a collection of views, a layout for the views, and the visible action sets that
-should be used when the user first opens the perspective.</P>
-<P >
-Perspectives are implemented using&nbsp; <b><a href="../reference/api/org/eclipse/ui/IPerspectiveFactory.html">IPerspectiveFactory</a>.&nbsp;
-</b>Implementors of
-<b><a href="../reference/api/org/eclipse/ui/IPerspectiveFactory.html">IPerspectiveFactory</a></b>
-are expected to configure an <b><a href="../reference/api/org/eclipse/ui/IPageLayout.html"> IPageLayout</a></b> with information that describes the
-perspective and its perspective page layout.</P>
-
-
-<h3>
-Workbench part layout</h3>
-<P >
-One of the main jobs of an <b><a href="../reference/api/org/eclipse/ui/IPageLayout.html"> IPageLayout</a></b>
-is to describe the placement of the editor and the views in the workbench window. Note that these layouts are different than the
-<a href="../reference/api/org/eclipse/swt/widgets/Layout.html"><b> Layout</b></a> class in SWT. Although
-<b><a href="../reference/api/org/eclipse/ui/IPageLayout.html"> IPageLayout</a></b>
-and <a href="../reference/api/org/eclipse/swt/widgets/Layout.html"><b> Layout</b></a>
-solve a similar problem (sizing and positioning widgets within a larger area), you do not have to understand SWT layouts in order to supply a
-perspective page layout.</P>
-<P >
-A perspective page layout is initialized with one area for displaying an editor. The perspective factory is responsible for adding additional views relative to the
-editor. Views are added to the layout relative to (top, bottom, left, right) another part. Placeholders (empty space) can also be added for
-items that are not initially shown.</P>
-<P >
-To organize related views and reduce clutter, you can use <a href="../reference/api/org/eclipse/ui/IFolderLayout.html"><b>IFolderLayout</b></a> to group views into tabbed folders. For example, the Resource perspective
-places the resource navigator inside a folder at the top left corner of the
-workbench.&nbsp; Placeholders are commonly used with folder layouts.
-The Resource perspective defines a placeholder for the bookmarks view in the
-same folder as the resource navigator. If the user shows the bookmarks view, it will appear in the same folder with the
-navigator, with a tab for each view.</P>
-<P >
- <b><a href="../reference/api/org/eclipse/ui/IPageLayout.html"> IPageLayout</a></b>
-also allows you to define the available actions and shortcuts inside a
-perspective.&nbsp;&nbsp; </P>
-
-
-
-<ul>
-  <li><b>addActionSet</b> is used to add action sets to a perspective.&nbsp;&nbsp;</li>
-  <li><b>addNewWizardShortcut</b> adds a new entry to the <b>File &gt;New</b> menu for a perspective.</li>
-  <li><b>addShowViewShortcut</b> adds the names of
- views that should appear in the <b>Window &gt;Show View</b>  menu when the
- perspective is active.&nbsp;&nbsp;</li>
-  <li><b>addPerspectiveShortcut</b> adds the names of
- perspectives that should appear in the <b>Window &gt;Open Perspective</b> menu when
- the perspective is active.</li>
-</ul>
-
-
-
-<h3>
-<a name="showin">
-Linking views and editors</a> with &quot;show-in&quot;</h3>
-
-
-
-<p>
-Another valuable service provided by perspectives and the <b><a href="../reference/api/org/eclipse/ui/IPageLayout.html"> IPageLayout</a>
-</b>
-is to aid in navigation between an editor and its related views.&nbsp; We
-typically think of views as helping the user find the objects to work with in
-editors.&nbsp; However, the converse operation is also useful:&nbsp; a user
-working with an object in an editor may need to navigate to that object inside a
-view.&nbsp; This can be accomplished using the workbench <b>Navigate &gt; Show
-In</b> menu.&nbsp; This command allows the user to jump to one of any number of
-related views in the context of the currently edited (or selected) object.&nbsp;
-For example, a user editing a file may want to jump over to that file in the
-resource navigator. </p>
-
-
-
-<p>
-The plug-in architecture of the workbench allows developers to contribute views
-and editors in different plug-ins that are not even aware of each other.&nbsp;
-By implementing support for &quot;show in,&quot; your view or editor can support
-convenient navigation to or from the views and editors contributed by other
-plug-ins.&nbsp; </p>
-
-
-
-<p>
-This navigation allows users to move quickly between views and to easily open a
-view that is not usually shown in a particular perspective.&nbsp; For example, a
-user working in the Java perspective can use <b>Navigate &gt; Show
-In</b>  to view the currently edited Java file in the Navigator view. </p>
-
-
-
-<h4>
-Show-in source</h4>
-<p>If you want to allow users to use <b>Navigate &gt; Show In</b> from your
-editor or view to jump to another view, you must implement <a href="../reference/api/org/eclipse/ui/part/IShowInSource.html"><b>IShowInSource</b></a>.&nbsp;
-Your part can supply its <a href="../reference/api/org/eclipse/ui/part/IShowInSource.html"><b>IShowInSource</b></a>
-directly using protocol (<b>getShowInSource()</b>) or as an adapter.&nbsp; <a href="../reference/api/org/eclipse/ui/part/IShowInSource.html"><b>IShowInSource</b></a>
-allows your part to supply a context (<a href="../reference/api/org/eclipse/ui/part/ShowInContext.html"><b>ShowInContext</b></a>)
-which is used by the target to decide how to show the source.&nbsp; The show in
-context for an editor is typically its input element.&nbsp; For a view, the
-context is typically its selection.&nbsp; Both a selection and an input element
-are provided in a <a href="../reference/api/org/eclipse/ui/part/ShowInContext.html"><b>ShowInContext</b></a>
-to give the target flexibility in determining how to show the source.&nbsp;</p>
-
-
-
-<p>A default context for editors is provided, so that your editor can
-participate in &quot;show-in&quot; without any special coding.&nbsp; For
-editors, the input element and selection are used to create an appropriate
-context.&nbsp;</p>
-
-
-
-<p>For views, <a href="../reference/api/org/eclipse/ui/part/IShowInSource.html"><b>IShowInSource</b></a>
-must be implemented by the view in order to offer <b>Navigate &gt; Show In</b>
-functionality.</p>
-
-
-
-<h4>
-Show-in target</h4>
-
-
-
-<p>You must implement <a href="../reference/api/org/eclipse/ui/part/IShowInTarget.html"><b>IShowInTarget</b></a>
-if you want your view to be a valid target for a &quot;show in&quot;
-operation.&nbsp; The target is responsible for showing a given context in a
-manner appropriate for its presentation.&nbsp; For example, the Navigator view
-expands its tree to select and reveal a resource specified in the
-context.&nbsp;&nbsp;</p>
-<p>A target should check the selection in the <a href="../reference/api/org/eclipse/ui/part/ShowInContext.html"><b>ShowInContext</b></a>
-first in deciding what to show, since this is the more specific
-information.&nbsp; It should show the input element only if no selection is
-indicated.</p>
-<h4>Presenting appropriate targets</h4>
-
-
-
-<p>How is the list of available targets determined?&nbsp; You can specify the
-available targets for your perspective in its <b><a href="../reference/api/org/eclipse/ui/IPageLayout.html"> IPageLayout</a></b>.&nbsp;
-Recall that a &quot;show in&quot; navigation may open a view that is not already
-present in the perspective.&nbsp; Using <b><a href="../reference/api/org/eclipse/ui/IPageLayout.html">IPageLayout</a>.addShowInPart</b>,
-you can specify a valid &quot;show in&quot; target by id.&nbsp; In this way, the
-valid targets can be established without unnecessarily creating any views. </p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_plugin.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_plugin.htm
deleted file mode 100644
index b17d23d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_plugin.htm
+++ /dev/null

@@ -1,81 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-The plug-in class
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-The plug-in class</H2>
-<P >
-So far, we've been looking at the different extensions that are provided by the readme tool. Let's look at the general 
-definition of the readme tool plug-in.</P>
-
-<H3>
-Plug-in definition</H3>
-<P >
-The readme tool plug-in is defined at the top of the <b> plugin.xml</b> file.</P>
-<pre>
-&lt;?xml version="1.0" encoding="UTF-8"?&gt;
-&lt;?eclipse version="3.0"?&gt;
-&lt;plugin
-   id=&quot;org.eclipse.ui.examples.readmetool&quot;
-   name=&quot;%Plugin.name&quot;
-   version=&quot;2.1.0&quot;
-   provider-name=&quot;%Plugin.providerName&quot;
-   class=&quot;org.eclipse.ui.examples.readmetool.ReadmePlugin&quot;&gt;
-
-   &lt;runtime>
-      &lt;library name=&quot;readmetool.jar&quot;/&gt;
-   &lt;/runtime&gt;
-   &lt;requires&gt;
-      &lt;import plugin=&quot;org.eclipse.ui&quot;/&gt;
-      &lt;import plugin=&quot;org.eclipse.core.resources&quot;/&gt;
-      &lt;import plugin=&quot;org.eclipse.core.runtime.compatibility&quot;/&gt;
-      &lt;import plugin=&quot;org.eclipse.ui.views&quot;/&gt;
-      &lt;import plugin=&quot;org.eclipse.ui.ide&quot;/&gt;
-      &lt;import plugin=&quot;org.eclipse.jface.text&quot;/&gt;
-      &lt;import plugin=&quot;org.eclipse.text&quot;/&gt;
-      &lt;import plugin=&quot;org.eclipse.ui.workbench.texteditor&quot;/&gt;
-      &lt;import plugin=&quot;org.eclipse.ui.editors&quot;/&gt;
-   &lt;/requires&gt;
-   ...</pre>
-<P >
-The plug-in definition includes the <b>name</b>, <b>id,</b> <b>version</b>, and <b>provider name</b> of the plug-in. We 
-saw most of these parameters before in our hello world plug-in. The readme tool also defines a specialized plug-in class,
-<b>ReadmePlugin</b>. </P>
-<P >
-The name of the jar file is also provided. File names specified in a <b> plugin.xml</b> file are relative to the
-plug-in's directory, so the readme tool's jar file should be located directly in the plug-in's directory.</P>
-<P >
-The <b>requires</b> element informs the platform of the readme tool's dependencies. 
-The workbench UI plug-ins are listed as required plug-ins, along with the various core, jface, and text plug-ins.  </P>
-
-<H3>
-AbstractUIPlugin</H3>
-<P >
-The<b> ReadmePlugin</b> class represents the readme
-tool plug-in and manages the life cycle of the plug-in.&nbsp; As we saw in the
-Hello World example, you don't have to specify a plug-in class.&nbsp; The
-platform will provide one for you.&nbsp; In this case, our plug-in needs to
-initialize UI related data when it starts up.&nbsp; The platform class <a href="../reference/api/org/eclipse/ui/plugin/AbstractUIPlugin.html"><b>AbstractUIPlugin</b></a>
-provides a structure for managing UI resources and is extended by <b>
-ReadmePlugin</b>.</P>
-<P >
-<a href="../reference/api/org/eclipse/ui/plugin/AbstractUIPlugin.html"><b>AbstractUIPlugin</b></a>
- uses the generic startup and shutdown methods to manage images, dialog settings, and a preference store during the lifetime of the plug-in.&nbsp;
-We'll look at the specifics of the <b> ReadmePlugin</b> class when we work with dialogs and preferences.</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_resources.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_resources.htm
deleted file mode 100644
index cc922bc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_resources.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Workbench resource support</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h2>
-Workbench resource support</h2>
-<P>
-The Eclipse platform is structured so that you can develop a workbench application even if your application
-has nothing to do with the platform resource model.  However, the workbench does provide support for
-working with resources in a separate plug-in, <b>org.eclipse.ui.ide</b>.  This plug-in contains the
-parts of the SDK workbench that focus on IDE building and manipulating the workspace.
-</p>
-<p>
-If your plug-in uses the platform resource model, you may want to take advantage of the resource-oriented
-features in the workbench.  These include resource property pages, resource marker UI, resource filtering, 
-and other utilities.
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_scalability.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_scalability.htm
deleted file mode 100644
index 1ba5895..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_scalability.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Filtering large user interfaces</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h2>
-Filtering large user interfaces</h2>
-<P>
-The rich extensibility mechanisms in the workbench provide many ways for plug-ins to contribute to the platform
-UI.  However, extensibility can introduce its own set of problems.  While allowing for a rich set of features
-contributed by many different developers, it can also create an overwhelming experience for the new user who is
-trying to navigate through vast menus and preferences pages.  As the Eclipse platform matures, the need for
-filtering mechanisms that help reduce the UI clutter and guide the user to their desired tasks has become apparent.
-</P>
-<p>
-The activity and context mechanisms address the problem of too much clutter in the user interface:
-</p>
-<ul>
-<li><b>Activities</b> allow platform integrators to define large-grained groupings of function that are only
-shown when a particular user activity is enabled. Users can explicitly (or implicitly through trigger points)
-enable or disable activities.</li>
-<li><b>Contexts</b> are used to dynamically enable function while the user is performing a specific task.
-They influence what commands are available to the user at any given moment.</li>
-</ul>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_structure.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_structure.htm
deleted file mode 100644
index d166bb0..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_structure.htm
+++ /dev/null

@@ -1,137 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Workbench under the covers
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Workbench under the covers</H2>
-<P >
-The workbench provides an extensive set of classes and interfaces for building complex user interfaces. Fortunately you don't need to understand
-all of them to do something simple. We'll start by looking at some concepts that are exposed in the workbench user interface
-and their corresponding structure under the covers.</P>
-
-<H3>
-Workbench</H3>
-<P >
-We've been using the term <b> workbench</b> loosely to refer to &quot;that window that opens when you start the platform.&quot; Let's drill down a little and look at some of the visual components that make up
-the workbench.</P>
-
-<img src="images/workbench_decomposed.png" alt="Workbench with three views and one editor on a page" border="0">
-<P >
-For the rest of this discussion, when we use the term workbench, we will be referring to the workbench window
-(<b><a href="../reference/api/org/eclipse/ui/IWorkbenchWindow.html">IWorkbenchWindow</a></b>). The workbench window is the top-level window in a workbench. It is the frame that holds the menu bar,
-tool bar, status line, short cut bar, and pages. In general, you don't need to program to the workbench window. You just want to know that it's there.</P>
-<blockquote><i>
-Note:&nbsp; You can open multiple workbench windows; however each workbench window is a self-contained world of editors and views,
-so we'll just focus on a single workbench
-window.</i></blockquote>
-<P >
-From the user's point of view, a workbench contains views and editors. There are a few other classes used to implement the workbench window.&nbsp; </P>
-
-
-
-<H3>
-Page</H3>
-<P >
-Inside the workbench window, you'll find one page (<b><a href="../reference/api/org/eclipse/ui/IWorkbenchPage.html">IWorkbenchPage</a></b>) that in turn contains parts. Pages are an implementation mechanism for grouping parts. You typically don't need to program to the page, but you'll see it in the context of programming and debugging. </P>
-
-
-<h3 >
-Perspectives</h3>
-
-<P >
-Perspectives provide an additional layer of organization inside the workbench
-page.&nbsp; A perspective defines an appropriate collection of views, their
-layout, and applicable actions for a given user task.&nbsp; Users can switch
-between perspectives as they move across tasks.&nbsp;&nbsp; From an
-implementation point of view, the user's active perspective controls which views
-are shown on the workbench page and their positions and sizes.&nbsp; Editors are
-not affected by a change in perspective.</P>
-
-
-<H3>
-<a name="views_and_editors">
-Views and editors</a></H3>
-<P >
-Views and editors are where we move beyond implementation details into some common plug-in programming. When you add a visual component to the workbench, you must decide whether you want to implement a view or
-an editor. How do you decide this?</P>
-<ul>
-  <li>A <b>view</b> is typically used to navigate a hierarchy of information,
-    open an editor, or display properties for the active editor.&nbsp; For
-    example, the <b>navigator</b> view allows you to navigate the workspace
-    hierarchy.&nbsp; The <b>properties</b> and <b>outline</b> views show
-    information about an object in the active editor.&nbsp; Any modifications
-    that can be made in a view (such as changing a property value) are saved
-    immediately.</li>
-  <li>An <b>editor</b> is typically used to edit or browse a document or input
-    object.&nbsp; Modifications made in an editor follow an open-save-close
-    model, much like an external file system editor.&nbsp; The platform text
-    editor and Java editor are examples of workbench editors.</li>
-</ul>
-<P >
-In either case, you will be building your view or editor according to a common lifecycle. </P>
-<ul>
-  <li>
-    
-You implement a <b> createPartControl</b> method to create the SWT widgets that represent your visual component. You must determine which widgets to use and allocate any related UI resources needed to display your view or editor.</li>
-  <li>
-    
-When your view or editor is given focus, you'll receive a <b> setFocus</b> notification so that you can set the focus to the correct widget.</li>
-  <li>
-    
-When the view or editor is closed, you will receive a <b> dispose</b>
- message to signify that the view or editor is being closed.&nbsp; At this point
-the controls allocated in <b>createPartControl</b>
- have already been disposed for you, but you must dispose of any graphics resources (such
-as cursors, icons, or fonts) that you allocated for the view or editor.</li>
-</ul>
-<P >
-Throughout this lifecycle, events will fire from the containing workbench page to notify interested parties about the opening, activation, deactivation, and closing of the
-views and editors.</P>
-<P >
-Seem simple?&nbsp; It can be. That's the beauty of workbench views and editors. They're just widget holders, and can be as simple or complex as you need them to be. We saw the simplest of views earlier when we built a hello world view.
-Let's look at it again now that we've explained more about what's going on.</P>
-<pre>
-   package org.eclipse.examples.helloworld;
-
-   import org.eclipse.swt.widgets.Composite;
-   import org.eclipse.swt.widgets.Label;
-   import org.eclipse.swt.SWT;
-   import org.eclipse.ui.part.ViewPart;
-
-   public class HelloWorldView extends ViewPart {
-      Label label;
-      public HelloWorldView() {
-      }
-      public void createPartControl(Composite parent) {
-         label = new Label(parent, SWT.WRAP);
-         label.setText(&quot;Hello World&quot;);
-      }
-      public void setFocus() {
-         // set focus to my widget.  For a label, this doesn't
-         // make much sense, but for more complex sets of widgets
-         // you would decide which one gets the focus.
-      }
-   }
-</pre>
-<P >
-Notice that we didn't have to implement a <b> dispose()</b> method since we didn't do anything but create a label in the
-<b> createPartControl(parent)</b> method. If we had allocated any UI resources, such as images or fonts, we would have disposed of them here. Since we extended the
-<b><a href="../reference/api/org/eclipse/ui/part/ViewPart.html"> ViewPart</a></b> class, we inherit the &quot;do nothing&quot; implementation of
-<b>dispose()</b>.</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv.htm
deleted file mode 100644
index ac987cc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Advanced workbench concepts
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Advanced workbench concepts</H1>
-<p>
-<a href="workbench.htm">Plugging into the workbench</a> looks at the basic workbench extension points in the
-context of the readme tool example.  However, there are many more extension points available for contributing to the
-workbench.  
-</p>
-<p>The next topics cover additional workbench extensions and concepts that
-you will likely encounter once you've implemented your plug-in and have begun to
-refine its function.  In order to understand the next few topics, you should already be familiar
-with
-</p>
-<ul>
-  <li><a href="workbench.htm">Plugging into the Workbench</a></li>
-  <li><a href="jface.htm">JFace UI framework</a></li>
-  <li><a href="swt.htm">SWT</a></li>
-  <li><a href="resInt.htm">Resources overview</a></li>
-</ul>
-Since the readme tool does not contribute to all of these extension
-points, we will look at example extensions that are implemented by the platform
-workbench, the platform help system, and Java tooling (JDT).
-<p>When using any of these workbench features, it is a good idea to
-keep the rules of engagement for threading in mind.  See 
-<a href="swt_threading.htm#workbench_threads">The workbench and threads</a> for more information.
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_accessibility.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_accessibility.htm
deleted file mode 100644
index 9230731..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_accessibility.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Accessible user interfaces
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Accessible user interfaces</h2>
-<p>The term accessible is used to refer to software that has been designed so
-that people who have disabilities have a successful interaction with it.&nbsp;
-Accessible software takes many different kinds of disabilities into account:</p>
-
-
-<ul>
-  <li>visual - people with color blindness, low vision, or who are completely
-    blind</li>
-  <li>audio - people who are hard of hearing or are completely deaf</li>
-  <li>mobility - people who have physical impairments that limit their movement
-    and fine motor controls</li>
-  <li>cognitive - people who have learning disabilities and may need more
-    consistency or simplicity in their interfaces</li>
-</ul>
-<h3>Assistive technology</h3>
-<p><b>Assistive technology</b> is equipment or software that is used to increase
-the accessibility of existing operating systems and applications.&nbsp; While it
-is beyond the scope of this programmer's guide to cover the broad scope of
-assistive technologies, it is important for you to know that they exist.&nbsp;
-Why?&nbsp; Because simple things you can do when programming your software or
-documentation, such as providing alternate text descriptions for images in your HTML, or
-keyboard equivalents for all of your software actions, can greatly improve the
-effectiveness of assistive technologies that make use of these techniques.</p>
-<h3>Accessibility resources</h3>
-<p>There are some basic coding tips you can use when building plug-in user
-interfaces that will increase the accessibility of your software.&nbsp; See <a href="../reference/misc/ui_accessibility_tips.html">Tips
-for Making User Interfaces More Accessible</a> for more information.</p>
-<p><a href="http://www-3.ibm.com/able/index.html">IBM's Accessibility Center
-Website</a> has many useful resources for accessibility, including <a href="http://www-3.ibm.com/able/guidelines.html">guidelines
-and checklists</a> for developing software and web interfaces.</p>
-<h3>SWT and accessibility</h3>
-<p>Because SWT uses the operating system's native widgets, user interfaces built
-with SWT will inherit any assistive technologies that have been installed on the
-host operating system.&nbsp; SWT implements an interface, <a href="../reference/api/org/eclipse/swt/accessibility/AccessibleListener.html"><b>AccessibleListener</b></a>,
-which provides basic accessibility information, such as descriptions of
-controls, help text, and keyboard shortcuts, to clients.&nbsp; If you are
-developing assistive technologies that need more information or want to improve
-upon the basic accessibiliity of the workbench, you can add your own listeners
-and override the default accessibility behavior in the platform.&nbsp; See the
-package <a href="../reference/api/org/eclipse/swt/accessibility/package-summary.html"><b>org.eclipse.swt.accessibility</b></a>
-for more detail.</p>
-<p>&nbsp;</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_encoding.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_encoding.htm
deleted file mode 100644
index 561973d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_encoding.htm
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Text file encoding
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Text file encoding</h3>
-<p>If your plug-in reads text files, it should honor the <b>text file encoding</b>
-preference in the workbench.&nbsp; </p>
-
-
-<p><img src="images/textencoding.png" alt="" border="0"></p>
-
-
-<p>Text files are encoded differently depending on the platform and the
-locale.&nbsp; Most of the time, using the default text file encoding for the
-locale of the host operating system is good enough.&nbsp; However, a user may
-want to work with text files that originate from another source.&nbsp; Given the
-ability to use the platform in a networked team environment, it's certainly possible
-that users will want to work with text files that use a different encoding
-scheme than their native encoding scheme so that they can easily interchange
-files with another team.</p>
-
-
-<p>For this reason, the workbench defines its own encoding profile that is
-specified by the user in the <b>Preferences</b> dialog.&nbsp; Users may choose
-from the available encoding choices in the <b>General &gt; Editors</b>
-preference page or type in their own encoding.&nbsp; Plug-ins that
-interpret text files, such as editors and builders, should consult the workbench
-encoding preference rather than assume that the installed operating system
-encoding is in use.</p>
-
-
-<p>You can obtain the encoding preference using <b><a href="../reference/api/org/eclipse/core/resources/ResourcesPlugin.html">ResourcesPlugin</a>.getEncoding().&nbsp;
-</b>This encoding should be passed to <b>java.io </b>readers instead of using
-the default system encoding.&nbsp; If you need to track changes to this preference, you can hook a listener on
-the <b><a href="../reference/api/org/eclipse/core/resources/ResourcesPlugin.html">ResourcesPlugin</a>
-</b>preferences and react to changes in <b>ResourcesPlugin.PREF_ENCODING.&nbsp; </b>The
-following example comes from the default text editor: </p>
-
-
-<pre>public void initialize(StatusTextEditor textEditor) {
-	
-	fTextEditor= textEditor;
-	
-	fPropertyChangeListener= new Preferences.IPropertyChangeListener() {
-		public void propertyChange(Preferences.PropertyChangeEvent e) {
-			if (ResourcesPlugin.PREF_ENCODING.equals(e.getProperty()))
-				setEncoding(null, false);
-		}
-	};
-		
-	Preferences p= ResourcesPlugin.getPlugin().getPluginPreferences();
-	p.addPropertyChangeListener(fPropertyChangeListener);
-	
-	fEncodingActionGroup= new EncodingActionGroup(fTextEditor);
-	fEncodingActionGroup.update();
-}</pre>
-<p>Users may also change the encoding for a particular file in the <b>Edit &gt;
-Encoding</b> menu of an editor.&nbsp; If you are manipulating text inside an
-open editor, you should use <b><a href="../reference/api/org/eclipse/ui/editors/text/IEncodingSupport.html">IEncodingSupport</a>.getEncoding()</b>
-instead in order to get the encoding for the particular editor.&nbsp; The
-following example shows how to obtain this information from an editor:</p>
-<pre>IEncodingSupport encodingSupport = (IEncodingSupport) editor.getAdapter(IEncodingSupport.class);
-String encoding = encodingSupport.getEncoding();
-</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings.htm
deleted file mode 100644
index 6d0bd72..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Workbench key bindings
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Workbench key bindings</h2>
-<p>The workbench defines many keyboard accelerators for invoking common actions
-with the keyboard.&nbsp; In early versions of the platform, plug-ins could
-define the accelerator key to be used for their action when the action was
-defined.&nbsp; However, this strategy can cause several problems:</p>
-
-
-<ul>
-  <li>Different plug-ins may define the same accelerator key for actions that are
-    not related.</li>
-  <li>Plug-ins may define different accelerator keys for actions that are
-    semantically the same.</li>
-  <li>Plug-ins may define accelerator keys that later conflict with the workbench
-    (as the workbench is upgraded).</li>
-</ul>
-
-
-<p>In order to alleviate these problems, the platform defines a configurable key
-binding strategy that is extendable by plug-ins.&nbsp; It solves the problems
-listed above and introduces new capabilities:</p>
-
-
-<ul>
-  <li>The user can control which key bindings should be used.</li>
-  <li>Plug-ins can define key bindings that emulate other tools that may be
-    familiar to users of the plug-in.</li>
-  <li>Plug-ins can define contexts for key bindings so that they are only active
-    in certain situations.</li>
-</ul>
-<p>The basic strategy is that plug-ins use <b>commands</b> to define
-semantic actions.&nbsp; Commands are simply declarations of an action and its
-associated category.&nbsp; These commands can then be associated with key
-bindings, actions, and handlers.&nbsp; Commands do not define an implementation
-for the action.&nbsp; When a
-plug-in defines an action for an editor, action set, or view, the action can
-specify that it is an implementation of one of these commands.&nbsp;
-This allows semantically similar actions to be associated with the same command.</p>
-<p>Once a command is defined, a <b>key binding</b> may be defined that
-references the command.&nbsp; The key binding defines the key sequence that
-should be used to invoke the command.&nbsp; A key binding may reference a
-<b>scheme</b> which is used to group key bindings into different named
-schemes that the user may activate via the
-Preferences dialog.</p>
-<p>This is all best understood by walking through the workbench and looking at
-how commands and key bindings are declared.&nbsp; We'll look at all of this from
-the point of view of defining key bindings for existing workbench actions.&nbsp; </p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelConfig.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelConfig.htm
deleted file mode 100644
index c5af62d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelConfig.htm
+++ /dev/null

@@ -1,105 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Schemes
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Schemes</h3>
-
-
-<p><b>Schemes</b> are used to represent a general style or theme of 
-  bindings. For example, the Workbench provides a &quot;Default&quot; scheme and
-  an &quot;Emacs&quot; scheme.&nbsp; Only one scheme is active at any
-  given time.&nbsp; End users control which one 
-  is active using the general <b>Preferences</b> dialog.</p>
-
-
-<p><img src="images/keybindings.png" alt="" border="0"></p>
-
-
-<p>From an implementation point of view, schemes are simply
-named groupings of bindings.&nbsp; A scheme won't
-accomplish anything on its own unless there are bindings associated with
-it.&nbsp;&nbsp;</p>
-
-
-<p>Let's look again at the workbench markup for <b><a href="../reference/extension-points/org_eclipse_ui_bindings.html">org.eclipse.ui.bindings</a>
-</b>to find the binding definitions and how a scheme gets
-associated with a binding.</p>
-
-
-<pre>...
-&lt;key
-       sequence=&quot;Ctrl+S&quot;
-       <b>commandId=&quot;org.eclipse.ui.file.save&quot;</b>
-       <b>schemeId=&quot;org.eclipse.ui.defaultAcceleratorConfiguration&quot;&gt;</b>
-&lt;/key&gt;
-...
-&lt;key
-       sequence=&quot;Ctrl+X Ctrl+S&quot;
-       <b>commandId=&quot;org.eclipse.ui.file.save&quot;</b>
-       <b>schemeId=&quot;org.eclipse.ui.emacsAcceleratorConfiguration&quot;&gt;</b>
-&lt;/key&gt;
-...
-</pre>
-
-
-<p>There are two different key bindings defined for the &quot;org.eclipse.ui.file.save&quot;
-command.&nbsp; Note that each one has a different <b>schemeId</b>
-defined.&nbsp; When the default scheme is active, the &quot;Ctrl+S&quot;
-key binding will invoke the command.&nbsp; When the emacs scheme is
-active, the sequence &quot;Ctrl+X Ctrl+S&quot; will invoke the command. </p>
-
-
-<h4>Defining new schemes</h4>
-
-
-<p>When your plug-in defines a binding, it will most likely assign it to an existing
-scheme.&nbsp; However, your plug-in may want to define a
-completely new style of scheme.&nbsp; If this is the case, you can define
-a new type of scheme inside the <b><a href="../reference/extension-points/org_eclipse_ui_bindings.html">org.eclipse.ui.bindings</a></b>
-definition.&nbsp; The workbench markup that defines the default and emacs key
-configurations are shown below:</p>
-
-
-<pre>...
-&lt;scheme
-       name=&quot;%keyConfiguration.default.name&quot;
-       description=&quot;%keyConfiguration.default.description&quot;
-       <b>id=&quot;org.eclipse.ui.defaultAcceleratorConfiguration&quot;&gt;</b>
-&lt;/scheme&gt;
-&lt;scheme
-       name=&quot;%keyConfiguration.emacs.name&quot;
-       parentId=&quot;org.eclipse.ui.defaultAcceleratorConfiguration&quot;
-       description=&quot;%keyConfiguration.emacs.description&quot;
-       <b>id=&quot;org.eclipse.ui.emacsAcceleratorConfiguration&quot;&gt;</b>
-&lt;/scheme&gt;
-...</pre>
-
-
-<p>Note that the <b>name</b>  defined here is the one used in the preferences page in the list of
-schemes.</p>
-
-
-<h4>Activating a scheme </h4>
-
-
-<p>The user controls the active scheme via the preferences page.&nbsp;
-However, you can define the default active scheme as a part of the 
-"plugin_customization.ini" file.  It is a preference:</p>
-<pre>
-org.eclipse.ui/KEY_CONFIGURATION_ID=org.eclipse.ui.defaultAcceleratorConfiguration
-</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelSet.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelSet.htm
deleted file mode 100644
index c164934..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelSet.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Key bindings
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Key bindings</h3>
-
-
-<p>The association between a command and the key combinations that should
-invoke the command is called a <b>key binding</b>.&nbsp; Plug-ins can define key
-bindings along with commands in the <b><a href="../reference/extension-points/org_eclipse_ui_bindings.html">org.eclipse.ui.bindings</a></b>
-extension point.</p>
-
-
-<pre>...
-&lt;key
-      <b>sequence=&quot;Ctrl+S&quot;</b>
-      <b>commandId=&quot;org.eclipse.ui.file.save&quot;</b>
-      schemeId=&quot;org.eclipse.ui.defaultAcceleratorConfiguration&quot;&gt;
-&lt;/key&gt;
-...</pre>
-
-
-<p>There is our friend <b>org.eclipse.ui.file.save</b>.&nbsp; Recall our
-hypothetical action definition:</p>
-
-<pre>&lt;extension point = &quot;org.eclipse.ui.actionSets&quot;&gt;
-	   &lt;actionSet id=&quot;com.example.actions.actionSet&quot;
-		   label=&quot;Example Actions&quot;
-		   visible=&quot;true&quot;&gt;
-		   &lt;action id=&quot;com.example.actions.action1&quot;
-			   menubarPath=&quot;additions&quot;
-			   label=&quot;Example Save Action&quot;
-			   class=&quot;org.example.actions.ExampleActionDelegate&quot;
-			   <b>definitionID=&quot;org.eclipse.ui.file.save&quot;</b>&gt;
-		   &lt;/action&gt;
-		   ...
-	   &lt;/actionSet&gt;
-&lt;/extension&gt;</pre>
-<p>The <b>sequence</b> attribute for a key binding defines the key
-combination that is used to invoke a command.&nbsp; So, it follows that when our example action set is active, our save action will be invoked
-when the user chooses <b>Ctrl+S</b>.</p>
-
-
-<p> Likewise, when the
-workbench <b>SaveAction</b> is active, the same key combination will invoke it
-instead, since the workbench uses the same command id for its <b>SaveAction</b>.</p>
-
-
-<p>To complete the example, we need to understand what the <b>configuration</b>
-is all about.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_actionDef.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_actionDef.htm
deleted file mode 100644
index 55cdb5a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_actionDef.htm
+++ /dev/null

@@ -1,141 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Commands
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Commands</h3>
-
-
-<p>A <b>command</b> is the declaration of a user action by <b>id</b>.&nbsp;
-Commands are used to declare semantic actions so that action implementations defined
-in action sets and editors can associate themselves with a particular semantic
-command.&nbsp; The separation of the command from the action
-implementation allows multiple plug-ins to define actions that implement the
-same semantic command.&nbsp; The command is what gets associated with a
-particular key binding.</p>
-
-
-<p>The workbench defines many common commands in its <b>plugin.xml</b>
-file, and plug-ins are encouraged to associate their own actions with these
-commands where it makes sense.&nbsp; In this way, semantically similar
-actions implemented in different plug-ins may share the same key binding.</p>
-
-
-<h4>Defining a command</h4>
-
-
-<p>Commands are defined using the <b><a href="../reference/extension-points/org_eclipse_ui_commands.html">org.eclipse.ui.commands</a></b>
-extension point.&nbsp; The following comes from the workbench markup:</p>
-
-
-<pre>
-&lt;extension
-	point=&quot;org.eclipse.ui.commands&quot;&gt;
-	...
-	&lt;command
-		name="%command.save.name"
-		description="%command.save.description"
-		categoryId="org.eclipse.ui.category.file"
-		id="org.eclipse.ui.file.save"&gt;
-	&lt;/command&gt;
-	...
-</pre>
-
-
-<p>The command definition specifies a <b>name</b>, <b>description</b>, and <b>id</b> for
-the action.&nbsp;&nbsp; It also specifies the id of a category for the command, which is
-used to group commands in the preferences dialog.&nbsp; The categories are also
-defined in the <b><a href="../reference/extension-points/org_eclipse_ui_commands.html">org.eclipse.ui.commands</a>
-</b>
-extension point:</p>
-<pre>
-      ...
-      &lt;category
-            name=&quot;%category.file.name&quot;
-            description=&quot;%category.file.description&quot;
-            id=&quot;org.eclipse.ui.category.file&quot;&gt;
-      &lt;/category&gt;
-      ...
-</pre><p>Note that there is no implementation specified for a
-command.&nbsp; A command only becomes concrete when a plug-in
-associates its action with the command id.</p>
-
-
-<h4>Associating an action with a command</h4>
-
-
-<p>Actions can be associated with a command in code or in the <b>plugin.xml
-</b>for action sets.&nbsp;
-Your choice depends on where the action is defined.</p>
-
-
-<p>Actions that are instantiated in code can also be associated with an action
-definition using <a href="../reference/api/org/eclipse/jface/action/IAction.html"><b>IAction</b></a>
-protocol.&nbsp; This is typically done when the action is created.&nbsp; The <b>SaveAction</b>
-uses this technique when it initializes itself. </p>
-
-
-<pre>
-public SaveAction(IWorkbenchWindow window) {
-	...
-	setText...
-	setToolTipText...
-	setImageDescriptor...
-	<b>setActionDefinitionId(&quot;org.eclipse.ui.file.save&quot;)</b>; 
-}
-</pre>
-
-<p>(Note:&nbsp; The method name <b>setActionDefinitionID </b>could more
-appropriately be named <b>setCommandID</b>.&nbsp; The method name reflects the
-original implementation of key bindings and uses outdated terminology.)</p>
-
-
-<p>By invoking <b>setActionDefinitionID</b>, the implementation action (<b>SaveAction</b>) is associated with
-the command id that was used in the command definition markup. It is good practice to define constants for your action definitions so that
-they are easily referenced in code. </p>
-
-<p> If you define an
-action in an action set, then you typically do not need to
-instantiate an action yourself.&nbsp; The workbench will do it for you when the user
-invokes your action from a menu or the keyboard.&nbsp; In this case, you can
-associate your action with a command ID in your&nbsp; XML markup.&nbsp; The
-following shows a hypothetical markup for an action set:</p>
-
-<pre>
-&lt;extension point = &quot;org.eclipse.ui.actionSets&quot;&gt;
-	   &lt;actionSet id=&quot;com.example.actions.actionSet&quot;
-		   label=&quot;Example Actions&quot;
-		   visible=&quot;true&quot;&gt;
-		   &lt;action id=&quot;com.example.actions.action1&quot;
-			   menubarPath=&quot;additions&quot;
-			   label=&quot;Example Save Action&quot;
-			   class=&quot;org.example.actions.ExampleActionDelegate&quot;
-			   <b>definitionID=&quot;org.eclipse.ui.file.save&quot;</b>&gt;
-		   &lt;/action&gt;
-		   ...
-	   &lt;/actionSet&gt;
-   &lt;/extension&gt;</pre>
-<p>The <b>definitionID</b> attribute is used to declare a command ID for the action.</p>
-
-
-<p>Using either technique, associating your action with a command ID causes any key bindings that get defined for the
-command <b>org.eclipse.ui.file.save
-</b>to invoke your action when appropriate.&nbsp; </p>
-
-
-<p>Now let's look at how these key bindings get defined. </p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_contexts.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_contexts.htm
deleted file mode 100644
index 9345a0e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_contexts.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Contexts and key bindings
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Contexts and key bindings</h3>
-
-<p>A <b> context</b> can be specified for a key binding so that the binding is only available when the user is
-working within a specific context.  Contexts are declared in the
-<b><a href="../reference/extension-points/org_eclipse_ui_contexts.html">org.eclipse.ui.contexts</a></b>
-extension point.</p>
-
-<p>A context can be bound to a key binding by specifying the id of the context when the key binding is defined.
-For example, if we only wanted the save command to work while the user is editing text, we could specify
-a context for the key binding:
-</p>
-<pre>&lt;key
-      sequence=&quot;Ctrl+S&quot;
-      commandId=&quot;org.eclipse.ui.file.save&quot;
-      <b>contextId="org.eclipse.ui.textEditorScope"</b>
-      schemeId=&quot;org.eclipse.ui.defaultAcceleratorConfiguration&quot;&gt;
-&lt;/key&gt;
-...
-</pre>
-(See <a href="workbench_advext_contexts.htm">Contexts</a>) for a more detailed discussion
-of contexts and how they are defined.
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerhelp.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerhelp.htm
deleted file mode 100644
index 7ecc8e1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerhelp.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Contributing marker help
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h4>Contributing marker help</h4>
-<p>Now we are ready to look at how to add help to the readme tool's
-markers.&nbsp; Adding marker help is done using the <b><a href="../reference/extension-points/org_eclipse_ui_ide_markerHelp.html">org.eclipse.ui.ide.markerHelp</a></b>
-extension point.&nbsp; This extension point allows plug-ins to associate a help
-context id with a particular type of marker.&nbsp; The marker can be qualified
-by marker type only, or it can be further qualified by the value of one or more of its
-attributes.&nbsp; The readme tool declares several different help contexts:</p>
-<pre>&lt;extension point=&quot;org.eclipse.ui.ide.markerHelp&quot;&gt; 
-   &lt;markerHelp 
-      <b>markerType=&quot;org.eclipse.ui.examples.readmetool.readmemarker&quot; </b>
-      helpContextId=&quot;org.eclipse.ui.examples.readmetool.marker_example1_context&quot;&gt; 
-     <b> &lt;attribute name=&quot;org.eclipse.ui.examples.readmetool.id&quot; value= &quot;1234&quot;/&gt; </b>
-   &lt;/markerHelp&gt; 
-   &lt;markerHelp 
-      markerType=&quot;org.eclipse.ui.examples.readmetool.readmemarker&quot; 
-      helpContextId=&quot;org.eclipse.ui.examples.readmetool.marker_example2_context&quot;&gt; 
-      &lt;attribute name=&quot;org.eclipse.ui.examples.readmetool.level&quot; value= &quot;7&quot;/&gt; 
-   &lt;/markerHelp&gt; 
-   &lt;markerHelp 
-      markerType=&quot;org.eclipse.ui.examples.readmetool.readmemarker&quot; 
-      helpContextId=&quot;org.eclipse.ui.examples.readmetool.marker_example3_context&quot;&gt; 
-      &lt;attribute name=&quot;org.eclipse.ui.examples.readmetool.level&quot; value= &quot;7&quot;/&gt; 
-      &lt;attribute name=&quot;org.eclipse.ui.examples.readmetool.department&quot; value= &quot;infra&quot;/&gt; 
-   &lt;/markerHelp&gt; 
-   ...</pre>
-<p>Each marker help context is defined for the readme marker type.&nbsp;
-However, each help context is associated with a different combination of
-attribute values.&nbsp; The first marker help context will be used for markers
-whose <b>id</b> attribute is set to <b>&quot;1234&quot;</b>.&nbsp; The help
-contexts are defined in the plug-in's <b>HelpContexts.xml </b>file:</p>
-<pre>&lt;context id=&quot;marker_example1_context&quot; &gt;
-	&lt;description&gt;Readme marker example 1 &lt;b&gt;Help&lt;/b&gt; id = 1234 &lt;/description&gt;
-&lt;/context&gt;</pre>
-
-<p>Sure enough, when we select a readme marker with id=&quot;1234&quot; and
-select help using F1, we see our help description. </p>
-<p><img src="images/readmemarkerhelp.png" alt="Tasks list with marker help" border="0" ></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerresolution.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerresolution.htm
deleted file mode 100644
index 5a8cebc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerresolution.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Contributing marker resolution
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h4>Contributing marker resolution</h4>
-<p>Plug-ins can also define marker resolutions, so that their problem markers can
-participate in the workbench <b>Quick Fix</b> feature. Users can select
-a problem marker and choose a <b>Quick Fix</b> from a popup containing the list of supplied
-fixes contributed for the marker.</p>
-
-
-<p><img src="images/markerquickfixmenu.png" alt="Marker quick fix menu" border="0"></p>
-
-
-<p>Marker resolutions are contributed using the <b><a href="../reference/extension-points/org_eclipse_ui_ide_markerResolution.html">org.eclipse.ui.ide.markerResolution</a></b>
-extension point. This extension point allows plug-ins to associate a <b>class</b>
-that implements <b><a href="../reference/api/org/eclipse/ui/IMarkerResolutionGenerator.html">IMarkerResolutionGenerator</a></b>
-with a particular type of marker.&nbsp; The marker can be qualified
-by marker type only, or it can be further qualified by the value of one or more of its
-attributes.  The JDT contributes a marker resolution for Java problems:</p>
-
-
-<pre>
-&lt;extension
-	point="org.eclipse.ui.ide.markerResolution"&gt;
-	&lt;markerResolutionGenerator
-		markerType="org.eclipse.jdt.core.problem"
-		class="org.eclipse.jdt.internal.ui.text.correction.CorrectionMarkerResolutionGenerator"&gt;
-	&lt;/markerResolutionGenerator&gt;
-&lt;/extension&gt;
-</pre>
-
-<p>The marker resolution generator is responsible for returning an array of
-marker resolutions (<a href="../reference/api/org/eclipse/ui/IMarkerResolution.html"><b>IMarkerResolution</b></a>)
-that will be shown in the <b>Quick Fix</b> popup. The resolution will
-be <b>run()</b> if the user selects one of the fixes.</p>
-
-<p><img src="images/markerresolution.png" alt="Marker resolutions" border="0"></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markers.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markers.htm
deleted file mode 100644
index 9eb0ec6..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markers.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Marker help and resolution
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Marker help and resolution</h3>
-<p>In <a href="resAdv_markers.htm">Resource markers</a>, we saw how plug-ins can
-define specialized marker types in order to annotate resources with
-information.&nbsp; The <a href="../samples/org.eclipse.ui.examples.readmetool/doc-html/ui_readmetool_ex.html">readme
-tool</a> example defines its own markers in order to demonstrate two
-marker-related workbench extensions:&nbsp; <b>marker help</b> and <b>marker
-resolutions</b>.&nbsp; The marker definition is in the readme plug-in's manifest
-markup:</p>
-
-
-<pre>&lt;extension id=&quot;readmemarker&quot; point=&quot;org.eclipse.core.resources.markers&quot; name=&quot;%ReadmeMarker.name&quot;&gt;
-	&lt;super type=&quot;org.eclipse.core.resources.taskmarker&quot;/&gt;
-	&lt;super type=&quot;org.eclipse.core.resources.textmarker&quot;/&gt;
-	&lt;persistent value=&quot;true&quot;/&gt;
-	&lt;attribute name=&quot;org.eclipse.ui.examples.readmetool.id&quot;/&gt;
-	&lt;attribute name=&quot;org.eclipse.ui.examples.readmetool.level&quot;/&gt;
-	&lt;attribute name=&quot;org.eclipse.ui.examples.readmetool.department&quot;/&gt;
-	&lt;attribute name=&quot;org.eclipse.ui.examples.readmetool.code&quot;/&gt;
-	&lt;attribute name=&quot;org.eclipse.ui.examples.readmetool.language&quot;/&gt;
-&lt;/extension&gt;   </pre>
-
-
-<p>The tool defines a marker that inherits from the platform's text marker and
-task marker.&nbsp; It also defines named attributes for the marker.&nbsp;&nbsp;
-Marker attributes can be set and queried.</p>
-
-
-<p>Since the new readme marker is a kind of text marker, it
-inherits the text marker attributes.&nbsp; The text marker attributes include
-the character location of the marker.</p>
-
-
-<p>Markers can be added to a <b>.readme</b> file using the readme editor's popup
-menu.&nbsp; (The popup menu actions are added dynamically in <b>ReadmeTextEditor.<font SIZE="2" COLOR="#000000">editorContextMenuAboutToShow(IMenuManager</font>
-</b><font SIZE="2" COLOR="#000000"><b>parentMenu)</b>).&nbsp; Once added,
-the markers appear on the left side of the editor and in the tasks view.</font></p>
-
-
-<p><img src="images/readmemarkermenu.png" alt="Readme editor with readme markers on left side ruler" border="0"></p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget.htm
deleted file mode 100644
index b040756..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget.htm
+++ /dev/null

@@ -1,132 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Retargetable actions
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Retargetable actions</h2>
-<p>It is common for a plug-in's views and editors to implement actions that are
-semantically similar to existing workbench actions, such as clipboard
-cut/copy/paste, view refresh, or properties.&nbsp; The popup menu for views and
-editors can become quite cluttered if every view or editor has to define unique
-actions for these operations and include them in their menus.&nbsp; </p>
-
-
-<p>To solve this problem, the workbench defines <b>retargetable</b> (also called
-<b>global</b>) actions that can be handled by any view or editor.&nbsp; When a
-view or editor is active, its handler will be run when the user chooses the
-action from the workbench menu or toolbar.&nbsp; This allows views and editors
-to share workbench menu space for semantically similar actions. </p>
-
-
-<p><a href="../reference/api/org/eclipse/ui/IWorkbenchActionConstants.html"><b>IWorkbenchActionConstants</b></a>
-documents all of the workbench actions and denotes retargetable actions as
-global.&nbsp; For example, here is the definition of the <b>Properties</b> action.</p>
-
-
-<pre>public static final String PROPERTIES = &quot;properties&quot;; // Global action. </pre>
-
-
-<p>The following table summarizes some of the more common retargetable actions
-that are implemented by views and editors:</p>
-
-
-<table border="1" cellpadding="0" cellspacing="0" width="64%">
-  <tr>
-    <td width="20%">&nbsp;</td>
-    <td width="20%"><b>File menu</b></td>
-    <td width="20%"><b>Edit menu</b></td>
-    <td width="20%"><b>Navigate menu</b></td>
-    <td width="20%"><b>Project menu</b></td>
-  </tr>
-  <tr>
-    <td width="20%"><b>views</b></td>
-    <td width="20%">move<br>
-      rename<br>
-      refresh<br>
-      properties</td>
-    <td width="20%">&nbsp;</td>
-    <td width="20%">go into<br>
-      go to resource<br>
-      sync with editor<br>
-      back<br>
-      forward<br>
-      up<br>
-      next<br>
-      previous</td>
-    <td width="20%">open<br>
-      close<br>
-      build<br>
-      rebuild</td>
-  </tr>
-  <tr>
-    <td width="20%"><b>editors</b></td>
-    <td width="20%">revert<br>
-      print</td>
-    <td width="20%">find</td>
-    <td width="20%">&nbsp;</td>
-    <td width="20%">&nbsp;</td>
-  </tr>
-  <tr>
-    <td width="20%"><b>views and editors</b></td>
-    <td width="20%">&nbsp;</td>
-    <td width="20%">cut<br>
-      copy<br>
-      paste<br>
-      delete<br>
-      select all<br>
-      undo<br>
-      redo</td>
-    <td width="20%">&nbsp;</td>
-    <td width="20%">&nbsp;</td>
-  </tr>
-</table>
-<p>Retargetable actions are created using <b><a href="../reference/api/org/eclipse/ui/actions/RetargetAction.html">RetargetAction</a></b>.&nbsp;
-The following snippet is from <b>WorkbenchActionBuilder</b>.</p>
-
-
-<pre> propertiesAction = createGlobalAction(IWorkbenchActionConstants.PROPERTIES, &quot;file&quot;, false); </pre>
-
-
-<p>The <b> createGlobalAction</b> method shows us exactly how to make a <b><a href="../reference/api/org/eclipse/ui/actions/RetargetAction.html">RetargetAction</a></b>.</p>
-
-
-<pre>private RetargetAction createGlobalAction(String id, String actionDefPrefix, boolean labelRetarget) {
-	RetargetAction action;
-	if (labelRetarget) {
-		action = new LabelRetargetAction(id, WorkbenchMessages.getString(&quot;Workbench.&quot; + id)); 
-	}
-	else {
-		action = new RetargetAction(id, WorkbenchMessages.getString(&quot;Workbench.&quot; + id)); 
-	}
-	...
-	return action;
-}</pre>
-
-<p>When creating a retargetable action, the workbench assigns the id for the
-action and the default label.&nbsp; Note that there are two styles of retarget actions.&nbsp; <b><a href="../reference/api/org/eclipse/ui/actions/RetargetAction.html">RetargetAction</a>
-</b>simply allows a view or editor to reimplement an action.&nbsp; <b><a href="../reference/api/org/eclipse/ui/actions/LabelRetargetAction.html">LabelRetargetAction</a>
-</b>also allows views and editors to reset the label of the action.&nbsp;&nbsp;
-This is useful for making the menu label more specific, such as relabeling an <b>Undo</b>
-action as <b>Undo Typing</b>.&nbsp;&nbsp;</p>
-
-
-<p>Now we know how the retarget actions are defined by the workbench.&nbsp; Let's look
-next at how your view or editor can provide an implementation for a retargetable action.&nbsp;
-This is done by <a href="wrkAdv_retarget_setting.htm">setting a global action
-handler</a>.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute.htm
deleted file mode 100644
index 3d2e20d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Contributing new retargetable actions
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Contributing new retargetable actions</h3>
-<p>The workbench is not the only plug-in that can create retargetable
-actions.&nbsp; Your plug-in can define its own retargetable action, so that
-views and editors within your plug-in can share the same menu actions.&nbsp;
-There are two ways to contribute retargetable actions from your plug-in:</p>
-<ul>
-  <li>An <b>editor</b> can define a retargetable action for which the editor and
-    related views can hook handlers.&nbsp; The action is only available in the
-    menu bar when the editor is open.&nbsp;&nbsp;</li>
-  <li>An <b>action set</b> can define a retargetable action for which editors
-    and views can hook handlers.&nbsp; The action will be visible as long as the
-    action set is visible, but it will only be enabled if the active part has
-    hooked a handler for the action.</li>
-</ul>
-<p>This mechanism is useful for providing tight integration between editors and
-related views.&nbsp; For example, a content outline view can implement a handler
-for an action defined by its associated editor.&nbsp;&nbsp;</p>
-<p>The <a href="../samples/org.eclipse.ui.examples.readmetool/doc-html/ui_readmetool_ex.html">readme
-tool</a> example demonstrates both of these techniques.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute_actionsets.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute_actionsets.htm
deleted file mode 100644
index 9f4cc4f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute_actionsets.htm
+++ /dev/null

@@ -1,119 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Retargetable action set actions
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h4>Retargetable action set actions</h4>
-<p>The <a href="../samples/org.eclipse.ui.examples.readmetool/doc-html/ui_readmetool_ex.html">readme
-tool</a> action set also defines retargetable actions.&nbsp; The action remains
-visible as long as the readme action set is visible, but it is only enabled when
-a view or editor that implements the action is active.&nbsp; When using action
-sets to define retargetable actions, the actions are created in the action set
-markup rather than in code.&nbsp; The following is from the readme tool's action
-set definition:</p>
-<pre>&lt;extension point = &quot;org.eclipse.ui.actionSets&quot;&gt;
-	   &lt;actionSet id=&quot;org_eclipse_ui_examples_readmetool_actionSet&quot;
-		   label=&quot;%ActionSet.name&quot;
-		   visible=&quot;true&quot;&gt;
-...
-&lt;action id=&quot;org_eclipse_ui_examples_readmetool_readmeRetargetAction&quot;
-   menubarPath=&quot;window/org_eclipse_ui_examples_readmetool/slot1&quot;
-   toolbarPath=&quot;readme&quot;
-   label=&quot;%ReadmeRetargetAction.label&quot;
-   tooltip=&quot;%ReadmeRetargetAction.tooltip&quot;
-   helpContextId=&quot;org.eclipse.ui.examples.readmetool.open_browser_action_context&quot;
-   icon=&quot;icons/ctool16/openbrwsr.png&quot;
-   <b>retarget=&quot;true&quot;</b>&gt;
-&lt;/action&gt;
-&lt;action id=&quot;org_eclipse_ui_examples_readmetool_readmeRelabelRetargetAction&quot;
-   menubarPath=&quot;window/org_eclipse_ui_examples_readmetool/slot1&quot;
-   toolbarPath=&quot;readme&quot;
-   label=&quot;%ReadmeRelabelRetargetAction.label&quot;
-   tooltip=&quot;%ReadmeRelabelRetargetAction.tooltip&quot;
-   helpContextId=&quot;org.eclipse.ui.examples.readmetool.open_browser_action_context&quot;
-   icon=&quot;icons/ctool16/openbrwsr.png&quot;
-   <b>retarget=&quot;true&quot;	</b>
-   <b>allowLabelUpdate=&quot;true&quot;</b>&gt;
-&lt;/action&gt;
-...</pre>
-<p>Retargeted actions are specified by using the <b>retarget=&quot;true&quot;</b>
-attribute.&nbsp; This will cause a <b><a href="../reference/api/org/eclipse/ui/actions/RetargetAction.html">RetargetAction</a></b>
-to be created in the action set.&nbsp; Note that the retargetable actions do not specify an implementing
-<b>class</b> since it is up to each view or editor in the plug-in to set up a
-handler that implements each action.&nbsp; If the <b>allowLabelUpdate</b>  is
-true, then a <b><a href="../reference/api/org/eclipse/ui/actions/LabelRetargetAction.html">LabelRetargetAction</a>
-</b>will be created instead.</p>
-<p>The retargeted actions will be visible in the window menu when the readme
-action set is visible.&nbsp; However, they will not be enabled if the readme
-tool's editor or outline view are not active.</p>
-<p><img src="images/readmeactionsetmenu.png" alt="Readme File Editor menu with two grayed items and one enabled item" border="0"></p>
-<p>&nbsp;</p>
-<p>What do the editor and view have to do?&nbsp; Again, the client side is
-similar to registering a handler for the workbench or an editor's retargetable
-action.&nbsp; The action id specified in the markup must be used when
-registering a global action handler.</p>
-<p>The <b>ReadmeEditorActionBarContributor </b>takes care of this for the
-editor.&nbsp; First, it defines the handlers for the actions.</p>
-<pre>public ReadmeEditorActionBarContributor() {
-	...
-	handler4 = new EditorAction(MessageUtil.getString(&quot;Editor_Action4&quot;)); 
-	handler5 = new EditorAction(MessageUtil.getString(&quot;Editor_Action5&quot;)); 
-	handler5.setToolTipText(MessageUtil.getString(&quot;Readme_Editor_Action5&quot;));
-	...
-}</pre>
-<p>The handlers are registered at the same time that the handlers for the editor
-retargetable actions were registered.</p>
-<pre>public void init(IActionBars bars, IWorkbenchPage page) {
-	...
-	bars.setGlobalActionHandler(IReadmeConstants.ACTION_SET_RETARGET4, handler4);
-	bars.setGlobalActionHandler(IReadmeConstants.ACTION_SET_LABELRETARGET5, handler5);
-	...
-}</pre>
-<p>Recall that action bar contributors are shared among different instances of
-the same editor.&nbsp; This means the handlers must be notified if the active
-editor for the <b>ReadmeEditorActionBarContributor </b>changes.</p>
-<pre>public void setActiveEditor(IEditorPart editor) {
-	...
-	handler4.setActiveEditor(editor);
-	handler5.setActiveEditor(editor);
-	...
-}</pre>
-<p>That's it for the editor.&nbsp; We should see these actions enable when the
-editor is activated.</p>
-<p><img src="images/actionseteditorretargets.png" alt="Readme File Editor menu with actions enabled" border="0">&nbsp;</p>
-<p>Note that the label for the first retargetable action (&quot;Editor Action
-4&quot;) was not used since the action set XML markup did not set <b>allowLabelUpdate</b>.</p>
-<p>The <b>ReadmeContentOutlinePage</b>
- defines its handlers in the same place it defined handlers for the editor's
-retargetable actions:</p>
-<pre>public void createControl(Composite parent) {
-	...
-	action = new OutlineAction(MessageUtil.getString(&quot;Outline_Action4&quot;)); 
-	getSite().getActionBars().setGlobalActionHandler(
-		IReadmeConstants.ACTION_SET_RETARGET4, 
-		action);  
-	action = new OutlineAction(MessageUtil.getString(&quot;Outline_Action5&quot;)); 
-	action.setToolTipText(MessageUtil.getString(&quot;Readme_Outline_Action5&quot;)); 
-	getSite().getActionBars().setGlobalActionHandler(
-		IReadmeConstants.ACTION_SET_LABELRETARGET5, 
-		action);  
-}</pre>
-<p>We should see its relabeled action when the content outliner is active.</p>
-<p><img src="images/actionsetoutlineretargets.png" alt="Readme File Editor menu with renamed action" border="0"></p>
-<h4>&nbsp;</h4>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute_editors.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute_editors.htm
deleted file mode 100644
index 6b94d58..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute_editors.htm
+++ /dev/null

@@ -1,132 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Retargetable editor actions
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h4>Retargetable editor actions</h4>
-<p>Recall that the <a href="../samples/org.eclipse.ui.examples.readmetool/doc-html/ui_readmetool_ex.html">readme
-tool</a> defines its own editor which contributes actions
-to the workbench menu bar using its <b>ReadmeEditorActionBarContributor</b>.&nbsp;&nbsp;</p>
-<pre>&lt;extension
-    point = &quot;org.eclipse.ui.editors&quot;&gt;
-	&lt;editor
-  	   id = &quot;org.eclipse.ui.examples.readmetool.ReadmeEditor&quot;
-  	   name=&quot;%Editors.ReadmeEditor&quot;
-      	   icon=&quot;icons/obj16/editor.png&quot;
-      	   class=&quot;org.eclipse.ui.examples.readmetool.ReadmeEditor&quot;
-	   extensions=&quot;readme&quot;
-           <b>contributorClass=&quot;org.eclipse.ui.examples.readmetool.ReadmeEditorActionBarContributor</b>&quot;&gt;
-	&lt;/editor&gt;
-&lt;/extension&gt;</pre>
-<p>Let's look closer at what happens in the contributor class.</p>
-<pre>public ReadmeEditorActionBarContributor() {
-	...
-	action2 = new <b>RetargetAction</b>(<b>IReadmeConstants.RETARGET2</b>, MessageUtil.getString(&quot;Editor_Action2&quot;));
-	action2.setToolTipText(MessageUtil.getString(&quot;Readme_Editor_Action2&quot;));
-	action2.setDisabledImageDescriptor(ReadmeImages.EDITOR_ACTION2_IMAGE_DISABLE);
-	action2.setImageDescriptor(ReadmeImages.EDITOR_ACTION2_IMAGE_ENABLE);
-	...
-	action3 = new <b>LabelRetargetAction</b>(<b>IReadmeConstants.LABELRETARGET3</b>, MessageUtil.getString(&quot;Editor_Action3&quot;));
-	action3.setDisabledImageDescriptor(ReadmeImages.EDITOR_ACTION3_IMAGE_DISABLE);
-	action3.setImageDescriptor(ReadmeImages.EDITOR_ACTION3_IMAGE_ENABLE);
-	...&nbsp;&nbsp;
-	<b>handler2</b> = new EditorAction(MessageUtil.getString(&quot;Editor_Action2&quot;)); 
-	...
-	<b>handler3</b> = new EditorAction(MessageUtil.getString(&quot;Editor_Action3&quot;)); 
-	...</pre>
-<p>When the contributor is created, it creates two retargetable actions (one
-that allows label update and one that does not).&nbsp; Creation of the actions
-uses the same technique that the workbench uses.&nbsp; It also creates two
-handlers that will be used for the actions when the editor is the active
-part.&nbsp;&nbsp;</p>
-<p>But where are the handlers for the actions registered?&nbsp; Setting the
-global handlers is done a little differently when your editor defines the
-retargeted actions.&nbsp; Why?&nbsp; Because your contributor is in charge of
-tracking the active view and hooking different handlers as different views or
-the editor itself becomes active.&nbsp; (The workbench does this for you when
-you set a handler for one of its global actions).&nbsp; Here's how the <b>ReadmeEditorActionBarContributor</b>
-sets things up:</p>
-<pre>public void init(IActionBars bars, IWorkbenchPage page) {
-	super.init(bars, page);
-	bars.setGlobalActionHandler(IReadmeConstants.RETARGET2, handler2);
-	bars.setGlobalActionHandler(IReadmeConstants.LABELRETARGET3, handler3);
-	...</pre>
-<p>First, the contributor registers its handlers for the retargeted
-actions.&nbsp; This ensures that the contributor's actions will be run when the
-editor itself is active.&nbsp; The next step is to register each <b><a href="../reference/api/org/eclipse/ui/actions/RetargetAction.html">RetargetAction</a>
-</b>as a part listener on the page.</p>
-<pre>	...
-	// Hook retarget actions as page listeners
-	page.addPartListener(action2);
-	page.addPartListener(action3);
-	IWorkbenchPart activePart = page.getActivePart();
-	if (activePart != null) {
-		action2.partActivated(activePart);
-		action3.partActivated(activePart);
-	}
-}</pre>
-<p>Adding each <b><a href="../reference/api/org/eclipse/ui/actions/RetargetAction.html">RetargetAction</a>
-</b>as a part listener means that it will be notified when the active part
-changes.&nbsp; The action can get the correct global handler from the newly
-activated part.&nbsp; (See the implementation of <b><a href="../reference/api/org/eclipse/ui/actions/RetargetAction.html">RetargetAction</a>
-</b>for all the details.)&nbsp;&nbsp; Note that to start, the action is seeded
-with the currently active part. </p>
-<p>When the editor contributor is disposed, it should unhook the retargetable
-actions as page listeners.</p>
-<pre>public void dispose() {
-	// Remove retarget actions as page listeners
-	getPage().removePartListener(action2);
-	getPage().removePartListener(action3);
-}</pre>
-<p>Finally, recall that action bar contributors are shared among instances of
-the same editor class.&nbsp; For this reason, the handlers must be notified when
-the active editor changes so that they can connect to the proper editor
-instance.</p>
-<pre>public void setActiveEditor(IEditorPart editor) {
-	...
-	handler2.setActiveEditor(editor);
-	handler3.setActiveEditor(editor);
-	...
-}</pre>
-<p>That completes the setup on the editor side.&nbsp; When the editor is open
-and active, the handlers (and their labels) as defined by the <b>ReadmeEditorActionBarContributor
-</b>will appear in the workbench menu bar.</p>
-<p><img src="images/editorretargets.png" alt="Readme menu with three editor actions in workbench menu bar" border="0"></p>
-<p>Now that the editor's contributions are in place, what does a view do to register a handler?&nbsp; The code on the client side
-is similar to registering a handler for a workbench action, except that the
-action id is the one defined by the plug-in's editor.&nbsp; The <b>ReadmeContentOutlinePage</b>
-registers a handler for these actions.</p>
-<pre>public void createControl(Composite parent) {
-	super.createControl(parent);
-	...
-	getSite().getActionBars().<b>setGlobalActionHandler(
-		IReadmeConstants.RETARGET2, </b>
-		new OutlineAction(MessageUtil.getString(&quot;Outline_Action2&quot;)));  
-
-	OutlineAction action = new OutlineAction(MessageUtil.getString(&quot;Outline_Action3&quot;)); 
-	<b>action.setToolTipText(MessageUtil.getString(&quot;Readme_Outline_Action3&quot;)); </b>
-	getSite().getActionBars().<b>setGlobalActionHandler(
-		IReadmeConstants.LABELRETARGET3, </b>
-		action);  
-	...</pre>
-<p>Note that the outliner sets tool tip text and a label on the second action,
-since it allows relabeling.&nbsp; When the readme outliner view is made active,
-its handlers (and their labels) will now appear in the workbench menu bar.</p>
-<p><img src="images/editoroutlineretargets.png" alt="Readme menu with one renamed editor action" border="0"></p>
-<p>Note that the relabeled action shows the new label.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_setting.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_setting.htm
deleted file mode 100644
index cc1cb61..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_setting.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Setting a global action handler
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Setting a global action handler</h3>
-<p>A plug-in contributes a <a href="wrkAdv_retarget.htm">retargetable action</a>
-for a view or editor part by implementing an <a href="../reference/api/org/eclipse/jface/action/IAction.html"><b>IAction</b></a>
-and registering it as a global action handler with the part's action bars.&nbsp;
-This is usually done at the time that the part creates its actions and
-controls.&nbsp; The name of the retargeted action (as defined in <a href="../reference/api/org/eclipse/ui/IWorkbenchActionConstants.html"><b>IWorkbenchActionConstants</b></a>)
-is used to specify which action the handler is intended for.&nbsp; The following
-shows how the workbench task list registers its handler for the <b>PROPERTIES</b>
-action.</p>
-<pre>public void createPartControl(Composite parent) {
-	...
-	<b>makeActions();</b>
-	...
-
-	// Add global action handlers.
-	...	
-	getViewSite().getActionBars().<b>setGlobalActionHandler(
-		IWorkbenchActionConstants.PROPERTIES,
-		propertiesAction);</b>
-	...</pre>
-<p>The properties action is created in the local method <b>makeActions</b>:</p>
-<pre>void makeActions() {
-	...
-	// properties
-	propertiesAction = new TaskPropertiesAction(this, &quot;properties&quot;); 
-	propertiesAction.setText(TaskListMessages.getString(&quot;Properties.text&quot;)); 
-	propertiesAction.setToolTipText(TaskListMessages.getString(&quot;Properties.tooltip&quot;)); 
-	propertiesAction.setEnabled(false);
-}</pre>
-<p>That's all that is needed.&nbsp; Your action will be run when the user
-chooses the action from the workbench menu bar or tool bar and your view or
-editor is active.&nbsp; The workbench handles the details of ensuring that the
-retargeted action is always associated with the currently active view or editor.
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_singleclick.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_singleclick.htm
deleted file mode 100644
index 2455984..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_singleclick.htm
+++ /dev/null

@@ -1,95 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Honoring single click support
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Honoring single click support</h2>
-<p>The General <b>Preferences</b> allow users to specify whether views should 
-  open their objects on single or double click. </p>
-
-
-<p><img src="images/singleclick.png" alt="General &quot;Open mode&quot; preferences with disclaimer that the preference may not take effect in all views" border="0"></p>
-
-
-<p>Why the disclaimer about this preference not working for all views?&nbsp;
-Because views contributed by plug-ins must explicitly support this preference in
-their implementation.</p>
-
-
-<p>Recall that a view can be implemented by creating SWT controls and writing
-standard SWT code, or by using <a href="jface_viewers.htm"> JFace viewers</a> 
-to handle the low level details.&nbsp; Honoring
-the single click preference can be done at either level.&nbsp; Most views that
-open other objects present them in a structured, list-like view.&nbsp; We'll
-focus on that kind of view for now.&nbsp; If your view displays objects in a
-different manner, you'll likely use the SWT-level concepts to support single
-click.</p>
-
-
-<h3>Single click in JFace viewers</h3>
-
-
-<p>If you are using a <a href="jface_viewers.htm#listviewer">JFace list-oriented
-viewer</a> to present your objects, supporting single click is
-straightforward.&nbsp; Instead of using <b>addDoubleClickListener</b> to trigger
-opening the items in your view, use <b>addOpenListener</b>.&nbsp; The open
-listener honors the current workbench preference, firing the open event when the
-specified mouse event occurs.</p>
-
-
-<p>You may still wish to use <b>addDoubleClickListener</b> for non-open actions,
-such as expanding the items in a tree on double-click.</p>
-
-
-<h3>Single click in SWT controls</h3>
-
-
-<p>JFace provides a utility class, <a href="../reference/api/org/eclipse/jface/util/OpenStrategy.html"><b>OpenStrategy</b></a>, 
-  to handle the logistics of single and double click at the SWT control level.&nbsp; 
-  The <a href="../reference/api/org/eclipse/jface/util/OpenStrategy.html"><b>OpenStrategy</b></a> 
-  is configured by the General <b>Preferences</b> dialog so that it honors the 
-  current workbench open preference. In fact, the JFace viewers use this class 
-  to implement the open listener.&nbsp; </p>
-
-
-<p>You must create an <a href="../reference/api/org/eclipse/jface/util/OpenStrategy.html"><b>OpenStrategy</b></a>
-and associate it with your SWT control.&nbsp; The <a href="../reference/api/org/eclipse/jface/util/OpenStrategy.html"><b>OpenStrategy</b></a>
-will hook the appropriate events and interpret them based on the user
-preferences.&nbsp; Your job is to add an open listener to the strategy that
-implements the code for open.&nbsp; In this way, you are shielded from knowledge
-about which widget event triggered the open event.</p>
-
-
-<pre>OpenStrategy openHandler = new OpenStrategy(control);
-openHandler.addOpenListener(new IOpenEventListener() {
-	public void handleOpen(SelectionEvent e) {
-	// code to handle the open event.
-	...
-	}
-}</pre>
-<p>The other workbench preferences for open (select on hover,
-open using arrow keys) are also handled by <a href="../reference/api/org/eclipse/jface/util/OpenStrategy.html"><b>OpenStrategy</b></a>.&nbsp;
-This means that the &quot;right thing&quot; will happen if you use JFace viewers
-or the <a href="../reference/api/org/eclipse/jface/util/OpenStrategy.html"><b>OpenStrategy</b></a>
-class to implement open behavior.</p>
-<h3>Activating editors on open</h3>
-<p>When handling an open event, you should use <b>OpenStrategy.activateOnOpen() </b>to
-determine whether an opened editor should be activated by default.&nbsp;
-Activating an editor switches the focus from the view to the editor, which can
-be particularly confusing and undesirable in single click mode. </p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_undo.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_undo.htm
deleted file mode 100644
index b3af633..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_undo.htm
+++ /dev/null

@@ -1,340 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Undoable operations
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Undoable operations</h2>
-<p>We've looked at many different ways to contribute actions to the workbench, but we
-haven't focused on the implementation of an action's <tt>run()</tt> method.  The mechanics
-of the method depend on the specific action in question, but structuring the code as an
-<b>undoable operation</b> allows the action to participate in the platform undo and redo
-support.</p>
-<p>
-The platform provides an <b>undoable operations framework</b> in the package
-<b><a href="../reference/api/org/eclipse/core/commands/operations/package-summary.html">org.eclipse.core.commands.operations</a></b>.
-By implementing the code inside a <tt>run()</tt> method to create an
-<a href="../reference/api/org/eclipse/core/commands/operations/IUndoableOperation.html"><b>IUndoableOperation</b></a>,
-the operation can be made available for undo and redo.  Converting an action to use operations is straightforward, 
-apart from implementing the undo and redo behavior itself.</p>
-<h3>Writing an undoable operation</h3>
-<p>
-We'll start by looking at a very simple example.  Recall the simple 
-<b>ViewActionDelegate</b> provided in the readme example plug-in.  When
-invoked, the action simply launches a dialog that announces it was executed.</p>
-<pre>
-public void run(org.eclipse.jface.action.IAction action) {
-	MessageDialog.openInformation(view.getSite().getShell(),
-		MessageUtil.getString(&quot;Readme_Editor&quot;),  
-		MessageUtil.getString(&quot;View_Action_executed&quot;)); 
-}</pre>
-
-Using operations, the run method is responsible for creating an operation that does
-the work formerly done in the run method, and requesting that an <b>operations history</b> 
-execute the operation, so that it can be remembered for undo and redo.
-<pre>
-public void run(org.eclipse.jface.action.IAction action) {
-	IUndoableOperation operation = new ReadmeOperation(
-		view.getSite().getShell()); 
-	...
-	operationHistory.execute(operation, null, null);
-}
-</pre>
-The operation encapsulates the old behavior from the run method, as well as the undo
-and redo for the operation.
-<pre>
-class ReadmeOperation extends AbstractOperation {
-	Shell shell;
-	public ReadmeOperation(Shell shell) {
-		super("Readme Operation");
-		this.shell = shell;
-	}
-	public IStatus execute(IProgressMonitor monitor, IAdaptable info) {
-		MessageDialog.openInformation(shell,
-			MessageUtil.getString(&quot;Readme_Editor&quot;),  
-			MessageUtil.getString(&quot;View_Action_executed&quot;));   
-		return Status.OK_STATUS;
-	}
-	public IStatus undo(IProgressMonitor monitor, IAdaptable info) {
-		MessageDialog.openInformation(shell,
-			MessageUtil.getString(&quot;Readme_Editor&quot;),  
-			&quot;Undoing view action&quot;);   
-		return Status.OK_STATUS;
-	}
-	public IStatus redo(IProgressMonitor monitor, IAdaptable info) {
-		MessageDialog.openInformation(shell,
-			MessageUtil.getString(&quot;Readme_Editor&quot;),  
-			&quot;Redoing view action&quot;);   
-		return Status.OK_STATUS;
-	}
-}
-</pre>
-
-<p>
-For simple actions, it may be possible to move all of the nuts and bolt work into the operation class.
-In this case, it may be appropriate to collapse the former action classes into a single action class
-that is parameterized.  The action would simply execute the supplied operation when it is time to run.
-This is largely an application design decision.  
-</p>
-<p>
-When an action launches a wizard, then the operation is typically created as part of the wizard's 
-<tt>performFinish()</tt> method or a wizard page's <tt>finish()</tt> method.  Converting the <tt>finish</tt> method
-to use operations is similar to converting a <tt>run</tt> method.  The method is responsible for creating
-and executing an operation that does the work previously done inline.
-</p>
-<h3>Operation history</h3>
-<p>
-So far we've used an <b>operations history</b> without really explaining it.
-Let's look again at the code that creates our example operation.</p>
-<pre>
-public void run(org.eclipse.jface.action.IAction action) {
-	IUndoableOperation operation = new ReadmeOperation(
-		view.getSite().getShell()); 
-	...
-	<b>operationHistory.execute(operation, null, null);</b>
-}
-</pre>
-What is the <b>operation history</b> all about?  
-<a href="../reference/api/org/eclipse/core/commands/operations/IOperationHistory.html"><b>IOperationHistory</b></a>
-defines the interface for the object that keeps track of all of the undoable operations.  When an operation history
-executes an operation, it first executes the operation, and then adds it to the undo history.
-Clients that wish to undo and redo operations do so by using 
-<a href="../reference/api/org/eclipse/core/commands/operations/IOperationHistory.html"><b>IOperationHistory</b></a>
-protocol.  
-
-<p>
-The operation history used by an application can be retrieved in several ways.  The simplest way is to use the
-<a href="../reference/api/org/eclipse/core/commands/operations/OperationHistoryFactory.html"><b>OperationHistoryFactory</b></a>.</p>
-<pre>IOperationHistory operationHistory = OperationHistoryFactory.getOperationHistory();
-</pre>
-
-<p>
-The workbench can also be used to retrieve the operations history.  The workbench configures the default
-operation history and also provides protocol to access it.  The following snippet demonstrates how to
-obtain the operation history from the workbench. </p>
-<pre>
-IWorkbench workbench = view.getSite().getWorkbenchWindow().getWorkbench();
-IOperationHistory operationHistory = workbench.getOperationSupport().getOperationHistory();
-</pre>
-Once an operation history is obtained, it can be used to query the undo or redo history, find out which operation
-is the next in line for undo or redo, or to undo or redo particular operations.  Clients can add an
-<a href="../reference/api/org/eclipse/core/commands/operations/IOperationHistoryListener.html"><b>IOperationHistoryListener</b></a>
-in order to receive notifications about changes to the history.  Other protocol allows clients
-to set limits on the history or notify listeners about changes to a particular operation.  Before
-we look at the protocol in detail, we need to understand the <b>undo context</b>.
-
-<h4>Undo contexts</h4>
-<p>
-When an operation is created, it is assigned an <b>undo context</b> that describes the user context in which the original
-operation was performed.  The undo context typically depends on the view or editor that originated the undoable operation.  For
-example, changes made inside an editor are often local to that editor.  In this case, the editor should create its own
-own undo context and assign that context to operations it adds to the history.  In this way, all of the operations performed in the
-editor are considered local and semi-private.  Editors or views that operate on a shared model often use an undo context that is related
-to the model that they are manipulating.  By using a more general undo context, operations performed by one view or editor
-may be available for undo in another view or editor that operates on the same model.</p>
-<p>Undo contexts are relatively simple in behavior; the protocol for
-<a href="../reference/api/org/eclipse/core/commands/operations/IUndoContext.html"><b>IUndoContext</b></a> is fairly
-minimal.  The main role of a context is to "tag" a particular operation as belonging in that undo context, in order to distinguish
-it from operations created in different undo contexts.  This allows the operation history to keep track of the global history of all undoable
-operations that have been executed, while views and editors can filter the history for a specific point of view using the undo context.
-</p>
-<p>
-Undo contexts can be created by the plug-in that is creating the undoable operations, or accessed through API.  For
-example, the workbench provides access to an undo context that can be used for workbench-wide operations.  However they
-are obtained, undo contexts should be assigned when an operation is created.  The following snippet shows how the
-readme plug-in's <b>ViewActionDelegate</b> could assign a workbench-wide context to its operations.
-</p>
-<pre>
-public void run(org.eclipse.jface.action.IAction action) {
-	IUndoableOperation operation = new ReadmeOperation(
-		view.getSite().getShell()); 
-	IWorkbench workbench = view.getSite().getWorkbenchWindow().getWorkbench();
-	IOperationHistory operationHistory = workbench.getOperationSupport().getOperationHistory();
-	IUndoContext undoContext = workbench.getOperationSupport().getUndoContext();
-	operation.addContext(undoContext);
-	operationHistory.execute(operation, null, null);
-}
-</pre>
-<p>
-Why use undo contexts at all?  Why not use separate operation histories for separate views and editors?  Using separate operation
-histories assumes that any particular view or editor maintains its own private undo history, and that undo has no global meaning
-in the application.  This may be appropriate for some applications, and in these cases each view or editor should create its own
-separate undo context.  Other applications may wish to implement a global undo that applies to all user operations, regardless of
-the view or editor where they originated.  In this case, the workbench context should be used by all plug-ins that add operations
-to the history.  </p>
-<p>In more complicated applications, the undo is neither strictly local or strictly global.  Instead, there is some
-cross-over between undo contexts.  This can be achieved by assigning multiple contexts to an operation.  For example, an IDE workbench view may 
-manipulate the entire workspace and consider the workspace its undo context.  An editor that is open on a particular
-resource in the workspace may consider its operations mostly local.  However, operations performed inside the editor may 
-in fact affect both the particular resource and the workspace at large.  (A good example of this case is the JDT refactoring support,
-which allows structural changes to a Java element to occur while editing the source file).  In these cases, it is useful to be able to add both
-undo contexts to the operation so that the undo can be performed from the editor itself, as well as those views that manipulate the
-workspace.
-</p>
-<p>
-Now that we understand what an undo context does, we can look again at the protocol for
-<a href="../reference/api/org/eclipse/core/commands/operations/IOperationHistory.html"><b>IOperationHistory</b></a>.
-The following snippet is used to perform an undo on the some context:</p>
-<pre>IOperationHistory operationHistory = workbench.getOperationSupport().getOperationHistory();
-try {
-	IStatus status = operationHistory.undo(myContext, progressMonitor, someInfo);
-} catch (ExecutionException e) {
-	// handle the exception 
-}
-</pre>
-The history will obtain the most recently performed operation that has the given context and ask it to undo
-itself.  Other protocol can be used to get the entire undo or redo history for a context, or to find the operation
-that will be undone or redone in a partcular context.  The following snippet obtains the label for the operation
-that will be undone in a particular context.
-<pre>
-IOperationHistory operationHistory = workbench.getOperationSupport().getOperationHistory();
-String label = history.getUndoOperation(myContext).getLabel();
-</pre>
-
-<p>
-The global undo context, <b>IOperationHistory.GLOBAL_UNDO_CONTEXT</b>, may be used to refer to the global
-undo history.  That is, to all of the operations in the history regardless of their specific context.  The
-following snippet obtains the global undo history.
-</p>
-<pre>
-IOperationHistory operationHistory = workbench.getOperationSupport().getOperationHistory();
-IUndoableOperation [] undoHistory = operationHistory.getUndoHistory(IOperationHistory.GLOBAL_UNDO_CONTEXT);
-</pre>
-<p>
-Whenever an operation is executed, undone, or redone using operation history protocol, clients can
-provide a progress monitor and any additional UI info that may be needed for performing the operation.
-This information is passed to the operation itself.  In our original
-example, the readme action constructed an operation with a shell parameter that could be used to open
-the dialog.  Instead of storing the shell in the operation, a better approach is to pass parameters
-to the execute, undo, and redo methods that provide any UI information needed to run the operation.  These
-parameters will be passed on to the operation itself.</p>
-<pre>public void run(org.eclipse.jface.action.IAction action) {
-	IUndoableOperation operation = new ReadmeOperation();
-	...
-	<b>operationHistory.execute(operation, null, infoAdapter);</b>
-}
-</pre> 
-The <b>infoAdapter</b> is an <a href="../reference/api/org/eclipse/core/runtime/IAdaptable.html"><b>IAdaptable</b></a>
-that minimally can provide the <a href="../reference/api/org/eclipse/swt/widgets/Shell.html"><b>Shell</b></a> that can
-be used when launching dialogs.  Our example operation would use this parameter as follows:
-<pre>
-public IStatus execute(IProgressMonitor monitor, IAdaptable info) {
-	if (info != null) {
-		Shell shell = (Shell)info.getAdapter(Shell.class);
-		if (shell != null) {
-			MessageDialog.openInformation(shell,
-				MessageUtil.getString(&quot;Readme_Editor&quot;),  
-				MessageUtil.getString(&quot;View_Action_executed&quot;));   
-			return Status.OK_STATUS;
-		}
-	}
-	// do something else...
-}
-</pre> 
-
-<h3>Undo and redo action handlers</h3>
-<p>The platform provides standard undo and redo <a href="wrkAdv_retarget.htm"><b>retargetable action handlers</b></a> 
-that can be configured by views and editors to provide undo and redo support for their particular context.  When the 
-action handler is created, a context is assigned to it so that the operations history is filtered in a way appropriate for
-that particular view.  The action handlers take care of updating the undo and redo labels to show the current
-operation in question, providing the appropriate progress monitor and UI info to the operation history, and
-optionally pruning the history when the current operation is invalid.  An action group that creates the action handlers
-and assigns them to the global undo and redo actions is provided for convenience.</p>
-<pre>new UndoRedoActionGroup(this.getSite(), undoContext, true);
-</pre>
-The last parameter is a boolean indicating whether the undo and redo histories for the specified context should
-be disposed when the operation currently available for undo or redo is not valid.  The setting for this parameter
-is related to the undo context provided and the validation strategy used by operations with that context.
-
-<h3>Application undo models</h3>
-<p>
-Earlier we looked at how undo contexts can be used to implement different kinds of application undo models.
-The ability to assign one or more contexts to operations allows applications to implement undo strategies that
-are strictly local to each view or editor, strictly global across all plug-ins, or some model in between.
-Another design decision involving undo and redo is whether any operation can be undone or redone at any time,
-or whether the model is strictly linear, with only the most recent operation being considered for undo or
-redo.
-</p>
-<p>
-<a href="../reference/api/org/eclipse/core/commands/operations/IOperationHistory.html"><b>IOperationHistory</b></a>
-defines protocol that allows flexible undo models, leaving it up to individual implementations to determine what is allowed.
-The undo and redo protocol we've seen so far assumes that there is only one implied operation available for undo or redo in a particular
-undo context.  Additional protocol is provided to allow clients to execute a specific operation, regardless
-of its position in the history.  The operation history can be configured so that the model appropriate for an
-application can be implemented.  This is done with an interface that is used to pre-approve any undo or redo request
-before the operation is undone or redone.</p>
-<h4>Operation approvers</h4>
-<a href="../reference/api/org/eclipse/core/commands/operations/IOperationApprover.html"><b>IOperationApprover</b></a>
-defines the protocol for approving undo and redo of a particular operation.  An operation approver is installed on an operation history.  Specific
-operation approvers may in turn check all operations for their validity, check operations of only certain contexts,
-or prompt the user when unexpected conditions are found in an operation. 
-The following snippet shows how an application could configure the operation history to enforce a linear undo model for all
-operations.
-<pre>
-IOperationHistory history = OperationHistoryFactory.getOperationHistory();
-
-// set an approver on the history that will disallow any undo that is not the most recent operation
-history.addOperationApprover(new LinearUndoEnforcer());
-
-</pre>
-<p>
-In this case, an operation approver provided by the framework, 
-<a href="../reference/api/org/eclipse/core/commands/operations/LinearUndoEnforcer.html"><b>LinearUndoEnforcer</b></a>,
-is installed on the history to prevent the undo or redo of any operation that is not the most recently done or undone
-operation in all of its undo contexts.</p>
-<p>
-Another operation approver, 
-<a href="../reference/api/org/eclipse/ui/operations/LinearUndoViolationUserApprover.html"><b>LinearUndoViolationUserApprover</b></a>,
-detects the same condition and prompts the user as to whether the operation should be allowed to continue.  This operation
-approver can be installed on a particular workbench part.</p>
-<pre>IOperationHistory history = OperationHistoryFactory.getOperationHistory();
-
-// set an approver on this part that will prompt the user when the operation is not the most recent.
-IOperationApprover approver = new LinearUndoViolationUserApprover(myUndoContext, myWorkbenchPart);
-history.addOperationApprover(approver);
-</pre>
-
-<p>
-Plug-in developers are free to develop and install their own operation approvers for implementing 
-application-specific undo models and approval strategies.
-</p>
-<h3>Undo and the IDE Workbench</h3>
-<p>
-We've seen code snippets that use workbench protocol for accessing the operations history and the workbench undo
-context.  This is achieved using <a href="../reference/api/org/eclipse/ui/operations/IWorkbenchOperationSupport.html"><b>IWorkbenchOperationSupport</b></a>,
-which can be obtained from the workbench.  The notion of a workbench-wide undo context is fairly general.  It is up to the workbench application
-to determine what specific scope is implied by the workbench undo context, and which views or editors use the
-workbench context when providing undo support.
-</p>
-<p>
-In the case of the Eclipse IDE workbench, the workbench undo context should be assigned to any operation that affects the IDE workspace at large.
-This context is used by views that manipulate the workspace, such as the Resource Navigator.  The IDE workbench installs an adapter on
-the workspace for <a href="../reference/api/org/eclipse/core/commands/operations/IUndoContext.html"><b>IUndoContext</b></a> that returns the
-workbench undo context.  This model-based registration allows plug-ins that manipulate the workspace to obtain the appropriate undo context, even if they are headless and
-do not reference any workbench classes.</p>
-<pre>// get the operation history
-IOperationHistory history = OperationHistoryFactory.getOperationHistory();
-
-// obtain the appropriate undo context for my model
-IUndoContext workspaceContext = (IUndoContext)ResourcesPlugin.getWorkspace().getAdapter(IUndoContext.class);
-if (workspaceContext != null) {
-	// create an operation and assign it the context
-}
-
-</pre>
-Other plug-ins are encouraged to use this same technique for registering
-model-based undo contexts.
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_workingsets.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_workingsets.htm
deleted file mode 100644
index b958b3d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_workingsets.htm
+++ /dev/null

@@ -1,89 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Working sets
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Working sets</h2>
-<p>Users often find it necessary to filter views such as the navigator view in
-order to reduce clutter.&nbsp; Plug-ins can assist in filtering using different
-techniques.</p>
-
-
-<ul>
-  <li><a href="workbench_advext_resourceFilters.htm">Resource filters</a>
-    can be used to filter by file name.&nbsp; Plug-ins contribute resource
-    filters that the user can enable using a view's filter selection dialog.</li>
-  <li><b>Working sets</b> can be used to filter resources by only including
-    specified resources.&nbsp; Working sets are selected using the view's
-    working set dialog.</li>
-</ul>
-<p><img src="images/workingset.png" alt="Working set selection dialog" border="0"></p>
-<p>If your plug-in implements a view that shows resources (or objects that are
-adaptable to <a href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a>),
-you should support working sets.&nbsp; <b><a href="../reference/api/org/eclipse/ui/IWorkingSetManager.html">IWorkingSetManager</a>
-</b>provides API for manipulating working sets.&nbsp; You can obtain an <b><a href="../reference/api/org/eclipse/ui/IWorkingSetManager.html">IWorkingSetManager</a>
-</b>using <b><a href="../reference/api/org/eclipse/ui/IWorkbench.html">IWorkbench</a></b>
-API.</p>
-<pre>IWorkingSetManager manager = workbench.getWorkingSetManager();</pre>
-<p><b><a href="../reference/api/org/eclipse/ui/IWorkingSetManager.html">IWorkingSetManager</a>
-</b>allows you to<b> </b>manipulate and create working sets:</p>
-<ul>
-  <li><b>createWorkingSetSelectionDialog</b> - returns a working set dialog that shows the user the current working
-  sets. You can get the selected working sets from the dialog once it is
-  closed.</li>
-  <li><b>createWorkingSetEditWizard</b> - returns a working set edit wizard for editing the specified working
-  set</li>
-  <li><b>getWorkingSets()</b> - returns a list of all defined working sets</li>
-  <li><b>getWorkingSet(String name) </b>- returns a working set specified by
-    name</li>
-</ul>
-<p><b><a href="../reference/api/org/eclipse/ui/IWorkingSetManager.html">IWorkingSetManager</a>
-</b>also provides property change notification as working sets are added,
-removed, or as they change.&nbsp; If your view or editor needs to respond to
-changes in the selected working set, it can add a listener for <b>CHANGE_WORKING_SET_CONTENT_CHANGE.</b></p>
-<h3>Adding new working set types</h3>
-
-
-<p>For many plug-ins, using <b><a href="../reference/api/org/eclipse/ui/IWorkingSetManager.html">IWorkingSetManager</a>
-</b>to provide resource filtering is sufficient.&nbsp; If your plug-in needs to
-define working sets differently, it can register a new type of working set using
-<b><a href="../reference/extension-points/org_eclipse_ui_workingSets.html">org.eclipse.ui.workingSets</a></b>.&nbsp;
-The Java tooling uses this feature to define a Java working set type.&nbsp;
-Working set types are shown when the user decides to add a working set.</p>
-
-
-<p><img src="images/workingSetTypes.png" alt="Working set dialog showing list of available types" border="0"></p>
-
-
-<p>&nbsp;</p>
-
-
-<p>When you define your own type of working set, you can use <b><a href="../reference/api/org/eclipse/ui/IWorkingSet.html">IWorkingSet</a>.getId</b> protocol to ensure that the working set matches the type that you have
-defined.&nbsp; Any working sets that you create programmatically must have
-their id set to the id of a working set page that can display the working
-set elements.&nbsp; This id is used to ensure that the proper working set
-edit page is launched when the user edits the working set.&nbsp; A null
-id indicates that the working set should use the default resource working
-set type.</p>
-
-
-<p>See the
-<b><a href="../reference/extension-points/org_eclipse_ui_workingSets.html">org.eclipse.ui.workingSets</a>
-</b>extension point documentation and <b><a href="../reference/api/org/eclipse/ui/IWorkingSet.html">IWorkingSet</a></b>
-protocol for more detail.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/notices.html b/bundles/org.eclipse.platform.doc.isv/notices.html
deleted file mode 100644
index 03ff544..0000000
--- a/bundles/org.eclipse.platform.doc.isv/notices.html
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <LINK REL="STYLESHEET" HREF="book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Legal Notices</title>
-</head>
-<body>
-
-<h3>
-<a NAME="Notices"></a>Notices</h3>
-<p>
-The material in this guide is Copyright (c) IBM Corporation and others 2000, 2005.
-</p>
-<p>
-<a href="about.html">Terms and conditions regarding the use of this guide.</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/platformOptions.txt b/bundles/org.eclipse.platform.doc.isv/platformOptions.txt
deleted file mode 100644
index 932832a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/platformOptions.txt
+++ /dev/null

@@ -1,290 +0,0 @@
--quiet
--encoding "iso-8859-1"
--charset "iso-8859-1"
-../org.eclipse.osgi/eclipseAdaptor/src/org/eclipse/core/runtime/adaptor/EclipseStarter.java
--sourcepath "
-;../org.apache.lucene/src
-;../org.eclipse.equinox.common/src
-;../org.eclipse.equinox.registry/src
-;../org.eclipse.equinox.preferences/src
-;../org.eclipse.core.jobs/src
-;../org.eclipse.core.contenttype/src
-;../org.eclipse.core.runtime.compatibility/src-runtime
-;../org.eclipse.core.runtime.compatibility/src-model
-;../org.eclipse.core.commands/src
-;../org.eclipse.platform/src
-;../org.eclipse.ant.core/src
-;../org.eclipse.compare/compare
-;../org.eclipse.debug.core/core
-;../org.eclipse.debug.ui/ui
-;../org.eclipse.help/src
-;../org.eclipse.help.base/src
-;../org.eclipse.help.ui/src
-;../org.eclipse.core.runtime/src
-;../org.eclipse.core.resources/src
-;../org.eclipse.pde/src
-;../org.eclipse.jface/src
-;../org.eclipse.jface.text/src
-;../org.eclipse.jface.text/projection
-;../org.eclipse.text/src
-;../org.eclipse.text/projection
-;../org.eclipse.ui/src
-;../org.eclipse.ui.cheatsheets/src
-;../org.eclipse.ui.intro/src
-;../org.eclipse.ui.console/src
-;../org.eclipse.ui.editors/src
-;../org.eclipse.ui.forms/src
-;../org.eclipse.ui.ide/src
-;../org.eclipse.ui.ide/extensions
-;../org.eclipse.ui.views/src
-;../org.eclipse.ui.views.properties.tabbed/src
-;../org.eclipse.ui.workbench/Eclipse UI
-;../org.eclipse.ui.workbench/Eclipse UI Editor Support
-;../org.eclipse.ui.workbench/Eclipse UI Components
-;../org.eclipse.ui.navigator/src
-;../org.eclipse.ui.navigator.resources/src
-;../org.eclipse.ui.workbench.texteditor/src
-;../org.eclipse.swt/Eclipse SWT/win32/
-;../org.eclipse.swt/Eclipse SWT/common/
-;../org.eclipse.swt/Eclipse SWT/common_j2se/
-;../org.eclipse.swt/Eclipse SWT AWT/win32/
-;../org.eclipse.swt/Eclipse SWT AWT/common/
-;../org.eclipse.swt/Eclipse SWT Custom Widgets/common/
-;../org.eclipse.swt/Eclipse SWT Drag and Drop/win32/
-;../org.eclipse.swt/Eclipse SWT Drag and Drop/common/
-;../org.eclipse.swt/Eclipse SWT OLE Win32/win32/
-;../org.eclipse.swt/Eclipse SWT Printing/win32/
-;../org.eclipse.swt/Eclipse SWT Printing/common/
-;../org.eclipse.swt/Eclipse SWT Program/win32/
-;../org.eclipse.swt/Eclipse SWT Program/common/
-;../org.eclipse.swt/Eclipse SWT PI/win32/
-;../org.eclipse.swt/Eclipse SWT PI/common_j2se/
-;../org.eclipse.swt/Eclipse SWT Accessibility/win32/
-;../org.eclipse.swt/Eclipse SWT Accessibility/common/
-;../org.eclipse.swt/Eclipse SWT Browser/win32/
-;../org.eclipse.swt/Eclipse SWT Browser/common/
-;../org.eclipse.team.core/src
-;../org.eclipse.team.ui/src
-;../org.eclipse.update.configurator/src
-;../org.eclipse.update.core/src
-;../org.eclipse.search/search
-;../org.eclipse.search/new search
-;../org.eclipse.core.filebuffers/src
-;../org.eclipse.core.variables/src
-;../org.eclipse.core.expressions/src
-;../org.eclipse.ltk.core.refactoring/src
-;../org.eclipse.ltk.ui.refactoring/src
-;../org.eclipse.osgi/core/adaptor
-;../org.eclipse.osgi/eclipseAdaptor/src
-;../org.eclipse.core.filesystem/src
-;../org.eclipse.swt/Eclipse SWT OpenGL/common
-;../org.eclipse.swt/Eclipse SWT OpenGL/emulated
-;../org.eclipse.swt/Eclipse SWT OpenGL/glx
-;../org.eclipse.swt/Eclipse SWT OpenGL/win32"
--d reference/api
--classpath @rt@
-;../../baseLocation/plugins/com.ibm.icu_3.4.3.jar
-;../org.apache.ant/lib/ant.jar
-;../org.eclipse.osgi/@dot
-;../org.apache.lucene/lucene-1.4.3.jar
-;../org.eclipse.help.appserver/@dot
-;../org.eclipse.update.ui/@dot
-;../org.eclipse.core.filesystem/@dot
-;../org.eclipse.core.jobs/@dot
-;../org.eclipse.core.runtime.compatibility.auth/@dot
-;../org.eclipse.equinox.registry/@dot
-;../org.eclipse.equinox.common/@dot
-;../org.eclipse.equinox.preferences/@dot
-;../org.eclipse.equinox.supplement/@dot
-;../org.eclipse.core.contenttype/@dot
-;../org.eclipse.ui.navigator.resources/@dot
--breakiterator
--use
--splitIndex
--windowtitle "Eclipse Platform API Specification"
--doctitle "Eclipse Platform API Specification"
--header "<b>Eclipse Platform</b><br>Release 3.2"
--bottom '<font size="-1"><p><a href="{@docRoot}/../misc/api-usage-rules.html">Guidelines for using Eclipse APIs</a>.</p><p>Copyright (c) IBM Corp. and others 2000, 2006. All rights reserved.</p></font>'
--link http://java.sun.com/j2se/1.4.2/docs/api
--link http://bundles.osgi.org/javadoc/r4
-
-org.eclipse.ant.core
-org.eclipse.compare
-org.eclipse.compare.contentmergeviewer
-org.eclipse.compare.rangedifferencer
-org.eclipse.compare.structuremergeviewer
-org.eclipse.core.commands
-org.eclipse.core.commands.common
-org.eclipse.core.commands.contexts
-org.eclipse.core.commands.operations
-org.eclipse.core.expressions
-org.eclipse.core.filebuffers
-org.eclipse.core.filebuffers.manipulation
-org.eclipse.core.filesystem
-org.eclipse.core.filesystem.provider
-org.eclipse.core.launcher
-org.eclipse.core.resources
-org.eclipse.core.resources.refresh
-org.eclipse.core.resources.team
-org.eclipse.core.runtime
-org.eclipse.core.runtime.content
-org.eclipse.core.runtime.dynamichelpers
-org.eclipse.core.runtime.jobs
-org.eclipse.core.runtime.model
-org.eclipse.core.runtime.preferences
-org.eclipse.core.variables
-org.eclipse.debug.core
-org.eclipse.debug.core.model
-org.eclipse.debug.core.sourcelookup
-org.eclipse.debug.core.sourcelookup.containers
-org.eclipse.debug.ui
-org.eclipse.debug.ui.actions
-org.eclipse.debug.ui.console
-org.eclipse.debug.ui.memory
-org.eclipse.debug.ui.sourcelookup
-org.eclipse.help
-org.eclipse.help.browser
-org.eclipse.help.ui.browser
-org.eclipse.jface.action
-org.eclipse.jface.bindings
-org.eclipse.jface.bindings.keys
-org.eclipse.jface.bindings.keys.formatting
-org.eclipse.jface.commands
-org.eclipse.jface.contexts
-org.eclipse.jface.dialogs
-org.eclipse.jface.fieldassist
-org.eclipse.jface.operation
-org.eclipse.jface.preference
-org.eclipse.jface.resource
-org.eclipse.jface.contentassist
-org.eclipse.jface.text
-org.eclipse.jface.text.contentassist
-org.eclipse.jface.text.formatter
-org.eclipse.jface.text.hyperlink
-org.eclipse.jface.text.information
-org.eclipse.jface.text.link
-org.eclipse.jface.text.presentation
-org.eclipse.jface.text.projection
-org.eclipse.jface.text.quickassist
-org.eclipse.jface.text.reconciler
-org.eclipse.jface.text.revisions
-org.eclipse.jface.text.rules
-org.eclipse.jface.text.source
-org.eclipse.jface.text.source.projection
-org.eclipse.jface.text.templates
-org.eclipse.jface.text.templates.persistence
-org.eclipse.jface.util
-org.eclipse.jface.viewers
-org.eclipse.jface.window
-org.eclipse.jface.wizard
-
-org.eclipse.ltk.core.refactoring
-org.eclipse.ltk.core.refactoring.participants
-org.eclipse.ltk.ui.refactoring
-
-org.eclipse.osgi.service.datalocation
-org.eclipse.osgi.util
-
-org.eclipse.search.core.text
-org.eclipse.search.ui
-org.eclipse.search.ui.actions
-org.eclipse.search.ui.text
-
-org.eclipse.swt
-org.eclipse.swt.awt
-org.eclipse.swt.accessibility
-org.eclipse.swt.browser
-org.eclipse.swt.custom
-org.eclipse.swt.dnd
-org.eclipse.swt.events
-org.eclipse.swt.graphics
-org.eclipse.swt.layout
-org.eclipse.swt.ole.win32
-org.eclipse.swt.opengl
-org.eclipse.swt.printing
-org.eclipse.swt.program
-org.eclipse.swt.widgets
-
-org.eclipse.team.core
-org.eclipse.team.core.diff
-org.eclipse.team.core.diff.provider
-org.eclipse.team.core.history
-org.eclipse.team.core.history.provider
-org.eclipse.team.core.mapping
-org.eclipse.team.core.mapping.provider
-org.eclipse.team.core.subscribers
-org.eclipse.team.core.synchronize
-org.eclipse.team.core.variants
-org.eclipse.team.ui
-org.eclipse.team.ui.history
-org.eclipse.team.ui.mapping
-org.eclipse.team.ui.synchronize
-
-org.eclipse.text.edits
-org.eclipse.text.undo
-
-org.eclipse.ui
-org.eclipse.ui.about
-org.eclipse.ui.actions
-org.eclipse.ui.activities
-org.eclipse.ui.application
-org.eclipse.ui.branding
-org.eclipse.ui.browser
-org.eclipse.ui.cheatsheets
-org.eclipse.ui.commands
-org.eclipse.ui.console
-org.eclipse.ui.console.actions
-org.eclipse.ui.contentassist
-org.eclipse.ui.contexts
-org.eclipse.ui.dialogs
-org.eclipse.ui.editors.text
-org.eclipse.ui.editors.text.templates
-org.eclipse.ui.fieldassist
-org.eclipse.ui.forms
-org.eclipse.ui.forms.editor
-org.eclipse.ui.forms.events
-org.eclipse.ui.forms.widgets
-org.eclipse.ui.handlers
-org.eclipse.ui.help
-org.eclipse.ui.ide
-org.eclipse.ui.ide.dialogs
-org.eclipse.ui.intro
-org.eclipse.ui.intro.config
-org.eclipse.ui.keys
-org.eclipse.ui.model
-org.eclipse.ui.navigator
-org.eclipse.ui.navigator.resources
-org.eclipse.ui.operations
-org.eclipse.ui.part
-org.eclipse.ui.plugin
-org.eclipse.ui.preferences
-org.eclipse.ui.presentations
-org.eclipse.ui.progress
-org.eclipse.ui.services
-org.eclipse.ui.testing
-org.eclipse.ui.themes
-org.eclipse.ui.texteditor
-org.eclipse.ui.texteditor.link
-org.eclipse.ui.texteditor.quickdiff
-org.eclipse.ui.texteditor.spelling
-org.eclipse.ui.texteditor.templates
-org.eclipse.ui.views
-org.eclipse.ui.views.bookmarkexplorer
-org.eclipse.ui.views.contentoutline
-org.eclipse.ui.views.framelist
-org.eclipse.ui.views.markers
-org.eclipse.ui.views.navigator
-org.eclipse.ui.views.properties
-org.eclipse.ui.views.properties.tabbed
-org.eclipse.ui.views.tasklist
-org.eclipse.ui.wizards
-org.eclipse.ui.wizards.datatransfer
-org.eclipse.ui.wizards.newresource
-
-org.eclipse.update.configurator
-org.eclipse.update.configuration
-org.eclipse.update.core
-org.eclipse.update.core.model
-org.eclipse.update.operations
-org.eclipse.update.search
-org.eclipse.update.standalone

diff --git a/bundles/org.eclipse.platform.doc.isv/plugin.properties b/bundles/org.eclipse.platform.doc.isv/plugin.properties
deleted file mode 100644
index d695256..0000000
--- a/bundles/org.eclipse.platform.doc.isv/plugin.properties
+++ /dev/null

@@ -1,12 +0,0 @@
-###############################################################################
-# Copyright (c) 2000, 2005 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-pluginName = Eclipse Platform Plug-in Developer Guide
-providerName=Eclipse.org

diff --git a/bundles/org.eclipse.platform.doc.isv/plugin.xml b/bundles/org.eclipse.platform.doc.isv/plugin.xml
deleted file mode 100644
index 3e31855..0000000
--- a/bundles/org.eclipse.platform.doc.isv/plugin.xml
+++ /dev/null

@@ -1,94 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?eclipse version="3.0"?>
-<plugin>
-
-<!-- ============================================================================= -->
-<!-- Small library containing a live help action used in doc                             -->
-<!-- ============================================================================= -->
-    
-<!-- ============================================================================= -->
-<!-- Define primary TOC                                                            -->
-<!-- ============================================================================= -->
-   <extension
-         point="org.eclipse.help.toc">
-      <toc
-            file="toc.xml"
-            primary="true">
-      </toc>
-      <index path="index"/>
-   </extension>
-<!-- ============================================================================= -->
-<!-- Define TOCs                                                                   -->
-<!-- ============================================================================= -->
-   <extension
-         point="org.eclipse.help.toc">
-      <toc
-            file="topics_Guide.xml">
-      </toc>
-      <toc
-            file="topics_Reference.xml">
-      </toc>
-      <toc
-            file="topics_Porting.xml">
-      </toc>
-      <toc
-            file="topics_Questions.xml">
-      </toc>
-      <toc
-            file="topics_Samples.xml">
-      </toc>
-   </extension>
-
-<!-- ============================================================================= -->
-<!-- Define Javadoc locations                                                      -->
-<!-- ============================================================================= -->
-   <extension point="org.eclipse.pde.core.javadoc">
-       <javadoc path="reference/api">
-           <plugin id="org.eclipse.ant.core"/>
-           <plugin id="org.eclipse.compare"/>
-           <plugin id="org.eclipse.core.commands"/>
-           <plugin id="org.eclipse.core.contenttype"/>
-           <plugin id="org.eclipse.core.expressions"/>
-           <plugin id="org.eclipse.core.filebuffers"/>
-           <plugin id="org.eclipse.core.filesystem"/>
-           <plugin id="org.eclipse.core.jobs"/>
-           <plugin id="org.eclipse.core.resources"/>
-           <plugin id="org.eclipse.core.runtime"/>
-           <plugin id="org.eclipse.core.variables"/>
-           <plugin id="org.eclipse.debug.core"/>
-           <plugin id="org.eclipse.debug.ui"/>
-           <plugin id="org.eclipse.equinox.common"/>
-           <plugin id="org.eclipse.equinox.preferences"/>
-           <plugin id="org.eclipse.equinox.registry"/>
-           <plugin id="org.eclipse.help"/>
-           <plugin id="org.eclipse.help.base"/>
-           <plugin id="org.eclipse.help.ui"/>
-           <plugin id="org.eclipse.jface"/>
-           <plugin id="org.eclipse.jface.text"/>
-           <plugin id="org.eclipse.ltk.core.refactoring"/>
-           <plugin id="org.eclipse.ltk.ui.refactoring"/>
-           <plugin id="org.eclipse.osgi"/>
-           <plugin id="org.eclipse.search"/>
-           <plugin id="org.eclipse.swt"/>
-           <plugin id="org.eclipse.team.core"/>
-           <plugin id="org.eclipse.team.ui"/>
-           <plugin id="org.eclipse.text"/>
-           <plugin id="org.eclipse.ui.browser"/>
-           <plugin id="org.eclipse.ui.cheatsheets"/>
-           <plugin id="org.eclipse.ui.console"/>
-           <plugin id="org.eclipse.ui.editors"/>
-           <plugin id="org.eclipse.ui.forms"/>
-           <plugin id="org.eclipse.ui.ide"/>
-           <plugin id="org.eclipse.ui.intro"/>
-           <plugin id="org.eclipse.ui.navigator"/>
-           <plugin id="org.eclipse.ui.navigator.resources"/>
-           <plugin id="org.eclipse.ui.views"/>
-           <plugin id="org.eclipse.ui.views.properties.tabbed"/>
-           <plugin id="org.eclipse.ui.workbench"/>
-           <plugin id="org.eclipse.ui.workbench.texteditor"/>
-           <plugin id="org.eclipse.update.configurator"/>
-           <plugin id="org.eclipse.update.core"/>
-       </javadoc>
-   </extension>
-
-</plugin>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/3.0/faq.html b/bundles/org.eclipse.platform.doc.isv/porting/3.0/faq.html
deleted file mode 100644
index a9f7587..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/3.0/faq.html
+++ /dev/null

@@ -1,107 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse 3.0 Plug-in Migration FAQ</title>
-</head>
-
-<body>
-
-<h1>Eclipse 3.0 Plug-in Migration FAQ</h1>
-
-<p><b>Why did Eclipse API change in incompatible ways between 2.1 and 3.0?</b></p>
-<p>Eclipse 3.0 is an evolution of Eclipse 2.1. There were a few areas where we
-could not evolve Eclipse while maintaining perfect compatibility across the
-board. The four main sources of incompatibilities are:</p>
-<ul>
-  <li>The Eclipse 3.0 runtime is now based on OSGi.</li>
-  <li>The Eclipse 3.0 UI workbench is now split into RCP and IDE parts.</li>
-  <li>The Xerces plug-in has been dropped from 3.0.</li>
-  <li>Eclipse 3.0 performs more work in background threads.</li>
-</ul>
-<p>The list of specific <a href="incompatibilities.html"> incompatibilities</a>.</p>
-<p><b>Will a 2.1 plug-in work in Eclipse 3.0?</b></p>
-<p>Yes, except in a few cases. If a plug-in relies only on Eclipse 2.1 APIs, then it will continue to work in
-3.0. The very few exceptions are places in the API where the changes between 2.1
-and 3.0 could not be done in any compatible way; if a plug-in uses one of these, it will not
-work.</p>
-<p><b>My 2.1 plug-in makes use of classes in internal packages. Will it still work in Eclipse 3.0?</b></p>
-<p>If a plug-in relies on internal classes or behavior not specified in
-the Eclipse 2.1 API, it's impossible to make blanket claims one way or the other
-about whether the plug-in might work in 3.0. You'll need to try it.</p>
-<p><b>How do I run my plug-in in Eclipse 3.0 without touching it?</b></p>
-<p>Install your 2.1 plug-in in the eclipse/plugins/ subdirectory of an Eclipse
-3.0-based product and restart Eclipse. Eclipse will recognize that the plug-in
-is an unconverted 2.1 plug-in (by the header on the plugin.xml) and
-automatically make adjustments to compensate for changes to Platform plug-in
-dependencies and renamed Platform extension points.</p>
-<p><b>Will a 2.1 plug-ins need to be changed to compile properly in Eclipse 3.0?</b></p>
-<p>Yes in all cases. There are certain differences between Eclipse 2.1 and 3.0 that
-necessitate changes to all plug-ins going forward. If you have a plug-in written
-for 2.1 and wish to recompile it, it needs to be migrated to 3.0 before it can be developed further
-for 3.0.</p>
-<p><b>How do I migrate my plug-in to Eclipse 3.0?</b></p>
-<p>Once you've loaded (or imported) your plug-in project into an Eclipse 3.0
-workspace, use <b>PDE
-Tools &gt; Migrate to 3.0</b>  (project context menu) to convert the plug-in's manifest to the 3.0
-format and automatically adjust the list of required Platform plug-ins and
-references to Platform extension points that were renamed. In most cases, the code for the
-plug-in should then compile and run successfully. The code for the plug-in
-should then be reviewed to make sure that it is not dependent on one of the
-areas of incompatible API change.</p>
-<p><b>Can I trust that a plug-in will have compile errors or warnings if it relies on API
-that has changed incompatibly?</b></p>
-<p>No. There are some areas of incompatible change that do not get flagged by
-the Java compiler.</p>
-<p><b>Can I safely ignore warnings in the code coming from use of deprecated
-API?</b></p>
-<p>Yes, in the short term. Wherever possible, obsolete APIs are marked as
-deprecated rather than being deleted outright and continue to work (albeit
-possibly only under limited conditions). So while there is usually no urgency to
-get off the deprecated API, the fact that it is now considered obsolete means
-that there is now a better way to do something. Plug-ins should be weaned off
-all usage to deprecated API at the earliest convenience.</p>
-<p><b>Once I migrate my plug-in to Eclipse 3.0, can I still install and run the
-resulting binary plug-in in Eclipse 2.1?</b></p>
-<p>No. This is not supported, and probably wouldn't work due to the renamed
-extension points.</p>
-<p><b>What is the purpose of org.eclipse.core.runtime.compatibility?</b></p>
-<p>The move in 3.0 to an OSGi-base runtime made some of the existing core
-runtime APIs obsolete. Wherever possible, obsolete APIs in the
-org.eclipse.core.runtime.* packages, along with the implementation behind it,
-were moved from the org.eclipse.core.runtime plug-in to a new
-org.eclipse.core.runtime.compatibility plug-in. By default, newly-created
-plug-ins depend on org.eclipse.core.runtime and are expected to use only
-non-deprecated runtime APIs. On the other hand, existing plug-ins migrating from
-2.1 will depend by default on org.eclipse.core.runtime.compatibility and can
-make use of the old APIs as well (the org.eclipse.core.runtime.compatibility
-plug-in re-exports APIs of org.eclipse.core.runtime). While the
-org.eclipse.core.runtime.compatibility plug-in is likely to be included in
-Eclipse IDE configurations, it's dead wood that's unlikely to be included in
-products based on RCP configurations.</p>
-<p><b>What is the purpose of org.eclipse.ui.workbench.compatibility?</b></p>
-<p>org.eclipse.ui.workbench.compatibility is a plug-in fragment that provides
-enhanced binary compatibility for 2.1 plug-ins being run in an Eclipse 3.0-based
-product. In 3.0, six methods with an explicit dependence on IFile or IMarker
-were moved from the org.eclipse.ui.IWorkbenchPage interface in order to cleanly
-separate the workbench from workspace and resources. The
-org.eclipse.ui.workbench.compatibility fragment arranges to add back these
-methods so that existing 2.1 plug-ins can run without modification. Note,
-however, that plug-ins being migrated to 3.0 that reference the moved methods
-will see compile errors that can (only) be resolved by calling the replacement
-methods now located on org.eclipse.ui.ide.IDE.</p>
-<p>The IWorkbenchPage methods in question are: openEditor(IFile),
-openEditor(IFile, String), openEditor(IFile, String, boolean),
-openEditor(IMarker), openEditor(IMarker, boolean), and openSystemEditor(IFile).</p>
-
-
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/3.0/incompatibilities.html b/bundles/org.eclipse.platform.doc.isv/porting/3.0/incompatibilities.html
deleted file mode 100644
index 8945a15..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/3.0/incompatibilities.html
+++ /dev/null

@@ -1,1114 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Incompatibilities between Eclipse 2.1 and 3.0</title>
-</head>
-
-<body>
-
-<h1>Incompatibilities between Eclipse 2.1 and 3.0</h1>
-
-<p> Eclipse changed in
-incompatible ways between 2.1 and 3.0 in ways that affect plug-ins. The
-following entries describe the areas that changed and provide instructions for
-  migrating
-2.1 plug-ins to 3.0. Note that you only need to look here if you are experiencing
-  problems running your 2.1 plug-in on 3.0.</p>
-<ol>
-  <li><a href="#Plug-in manifest version">Plug-in manifest version</a></li>
-  <li><a href="#Restructuring of Platform UI plug-ins">Restructuring of Platform UI plug-ins</a></li>
-  <li><a href="#Restructuring of Platform Core Runtime plug-ins"> Restructuring of Platform Core Runtime plug-ins</a></li>
-  <li><a href="#Removal of Xerces plug-in"> Removal of Xerces plug-in</a></li>
-  <li><a href="#Eclipse 3.0 is more concurrent"> Eclipse 3.0 is more concurrent</a></li>
-  <li><a href="#Opening editors on IFiles"> Opening editors on IFiles</a></li>
-  <li><a href="#Editor goto marker">Editor goto marker</a></li>
-  <li><a href="#Editor launcher">Editor launcher</a></li>
-  <li><a href="#Editor registry">Editor registry</a></li>
-  <li><a href="#Workbench marker help registry"> Workbench marker help registry</a></li>
-  <li><a href="#Text editor document providers"> Text editor document providers</a></li>
-  <li><a href="#Text editors">Text editors</a></li>
-  <li><a href="#Headless annotation support">Headless annotation support</a></li>
-  <li><a href="#Console view">Console view</a></li>
-  <li><a href="#Java breakpoint listeners">Java breakpoint listeners</a></li>
-  <li><a href="#Clipboard access in UI thread"> Clipboard access in UI thread</a></li>
-  <li><a href="#Key down events">Key down events</a></li>
-  <li><a href="#Tab traversal of custom controls"> Tab traversal of custom controls</a></li>
-  <li><a href="#Selection event order in SWT table and tree widgets"> Selection event order in SWT table and tree widgets</a></li>
-  <li><a href="#New severity level in status objects"> New severity level in status objects</a></li>
-  <li><a href="#Build-related resource change notifications"> Build-related resource change notifications</a></li>
-  <li><a href="#Intermediate notifications during workspace operations"> Intermediate notifications during workspace operations</a></li>
-  <li><a href="#URL stream handler extensions"> URL stream handler extensions</a></li>
-  <li><a href="#Class load order">Class load order</a></li>
-  <li><a href="#Class loader protection domain not set"> Class loader protection domain not set</a></li>
-  <li><a href="#PluginModel object casting"> PluginModel object casting</a></li>
-  <li><a href="#ILibrary implementation incomplete"> ILibrary implementation incomplete</a></li>
-  <li><a href="#Invalid assumptions regarding form of URLs"> Invalid assumptions regarding form of URLs</a></li>
-  <li><a href="#BootLoader methods moved/deleted"> BootLoader methods moved/deleted</a></li>
-  <li><a href="#Plug-in export does not include the plug-in's JARs automatically"> Plug-in export does not include the
-    plug-in's JARs automatically</a></li>
-  <li><a href="#Re-exporting runtime API"> Re-exporting runtime API</a></li>
-  <li><a href="#Plug-in parsing methods on Platform"> Plug-in parsing methods on Platform</a></li>
-  <li><a href="#Plug-in libraries supplied by fragments"> Plug-in libraries supplied by fragments</a></li>
-  <li><a href="#Changes to build scripts"> Changes to build scripts</a></li>
-  <li><a href="#Changes to PDE build Ant task"> Changes to PDE build Ant task</a></li>
-  <li><a href="#Changes to eclipse.buildScript Ant task">Changes to
-    eclipse.build Ant task</a></li>
-  <li><a href="#Changes to eclipse.fetch Ant task">Changes to eclipse.fetch Ant
-    task</a></li>
-  <li><a href="#Replacement of install.ini">Replacement of install.ini</a></li>
-</ol>
-<hr>
-<h2><a name="Plug-in manifest version"></a>1. Plug-in manifest version</h2>
-<p>The header of the manifest files for plug-ins (and plug-in fragments) has
-changed to include a new line which identifies the appropriate plug-in manifest
-version. Prior to 3.0, plug-ins did not carry one of these &lt;?eclipse ...?&gt;
-lines; after 3.0, they must always have one. This change is to allow the Eclipse
-runtime to reliably recognize pre-3.0 plug-ins that have not been ported to 3.0,
-so that it can automatically provide greater binary compatibility for such
-plug-ins. This is the general form of the plugin.xml file (fragment.xml is
-similar):</p>
-<p><code>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;<br>
-<u>&lt;?eclipse version=&quot;3.0&quot;?&gt;<br>
-</u>&lt;plugin ...&gt;<br>
-&nbsp;&nbsp;&nbsp; ...<br>
-&lt;/plugin&gt;</code></p>
-<p>Plug-in manifests created by PDE 3.0 automatically have this form. <strong>It
-    is strongly recommended that you use the PDE plug-in migration tool.</strong> It
-    automatically inserts the indicated line into the
-  manifest
-  of 2.1 plug-ins and plug-in
-fragments and addresses many of the other changes described here.</p>
-<p>If you do add this directive to a plugin.xml (manually or using PDE), the
-file must also be updated to explicitly list the plug-ins on which it depends.
-For example, prior to Eclipse 3.0 dependencies on org.eclipse.core.runtime and
-org.eclipse.core.boot were implicit. With 3.0, org.eclipse.core.boot is no
-longer needed and developers must choose org.eclipse.core.runtime or
-org.eclipse.core.runtime.compatibility (or neither) as appropriate.</p>
-<p>Note: This is one of the incompatibilities that does <b>not</b> impact how
-2.1 binary plug-ins are run by Eclipse 3.0.</p>
-<h2><a name="Restructuring of Platform UI plug-ins"></a>2. Restructuring of Platform UI plug-ins</h2>
-<p>The org.eclipse.ui plug-in, which used to be the main Platform UI plug-in,
-now provides just the API and extension points for the generic (i.e.,
-non-IDE-specific) workbench. Optional and IDE-specific API and extension points
-have moved to other plug-ins.</p>
-<p>The impact of this change is two-fold: (1) the moved org.eclipse.ui extension
-points have new extension point ids; and (2) the list of required plug-ins has
-changed.</p>
-<p>The org.eclipse.ui extension points in the following table have moved to
-different plug-ins, causing their extension point ids to change. If an existing
-plug-in contributes an extension to the moved extension points, then the
-reference in the &quot;point&quot; attribute of the &lt;extension&gt; element in
-the plug-in manifest file must be changed to refer to the corresponding new ones
-extension point id. The PDE plug-in migration tool makes these fix-ups.</p>
-<p>Note: This is one of the incompatibilities that does <b>not</b> impact how
-2.1 binary plug-ins are run by Eclipse 3.0. The Eclipse 3.0 runtime automatically detects pre-3.0 plug-ins (by the
-absence of the aforementioned &lt;?eclipse version=&quot;3.0&quot;?&gt; line in the plug-in manifest)
-and automatically compensates for these extension point and plug-in dependency
-changes.</p>
-<table border="1" width="80%">
-  <tr>
-    <td width="50%">
-      <p align="center"><b>Old extension point id</b></p></td>
-    <td width="50%">
-      <p align="center"><b>New extension point id</b></p></td>
-  </tr>
-  <tr>
-    <td width="50%">org.eclipse.ui.markerHelp</td>
-    <td width="50%">org.eclipse.ui.<i>ide</i>.markerHelp</td>
-  </tr>
-  <tr>
-    <td width="50%">org.eclipse.ui.markerImageProviders</td>
-    <td width="50%">org.eclipse.ui.<i>ide</i>.markerImageProviders</td>
-  </tr>
-  <tr>
-    <td width="50%">org.eclipse.ui.markerResolution</td>
-    <td width="50%">org.eclipse.ui.<i>ide</i>.markerResolution</td>
-  </tr>
-  <tr>
-    <td width="50%">org.eclipse.ui.projectNatureImages</td>
-    <td width="50%">org.eclipse.ui.<i>ide</i>.projectNatureImages</td>
-  </tr>
-  <tr>
-    <td width="50%">org.eclipse.ui.resourceFilters</td>
-    <td width="50%">org.eclipse.ui.<i>ide</i>.resourceFilters</td>
-  </tr>
-  <tr>
-    <td width="50%">org.eclipse.ui.markerUpdaters</td>
-    <td width="50%">org.eclipse.ui.<i>editors</i>.markerUpdaters</td>
-  </tr>
-  <tr>
-    <td width="50%">org.eclipse.ui.documentProviders</td>
-    <td width="50%">org.eclipse.ui.<i>editors</i>.documentProviders</td>
-  </tr>
-  <tr>
-    <td width="50%">org.eclipse.ui.workbench.texteditor.<br>
-      markerAnnotationSpecification</td>
-    <td width="50%">org.eclipse.ui.<i>editors</i>.markerAnnotationSpecification</td>
-  </tr>
-</table>
-<p>The following table lists the API packages formerly provided by the
-org.eclipse.ui plug-in that have been moved to different plug-ins. (The names of
-the API packages, classes, fields, and methods did not change.) In some cases,
-the API packages are now split across more than one plug-in. Since the API
-classes visible to any given plug-in are determined by that plug-in's list of
-required plug-ins, these changes may require adjusting
-&quot;&lt;requires&gt;&quot; elements in an existing plug-in's manifest to
-regain access to API class.</p>
-<p>This change only affects plug-ins that depend on the org.eclipse.ui plug-in
-(that is, includes &lt;import plugin=&quot;org.eclipse.ui&quot;/&gt; in the
-&lt;requires&gt; section of the plug-in manifest); all other plug-ins are
-unaffected. If it is affected, you <i>may</i> need to change the &lt;import&gt;
-element, or add additional &lt;import&gt; elements, so that all the API classes
-your plug-in needs are in scope. We strongly recommend that plug-ins only state
-dependencies on the plug-ins that they actually use. Including unnecessary
-dependencies reduces runtime performance because the Java class loader must
-search for classes in all dependents. (The PDE plug-in migration tool will fix
-up the dependencies, and help to determine a minimal set.)</p>
-<table border="1" width="80%">
-  <tr>
-    <td width="33%">
-      <p align="center"><b>API package</b></p></td>
-    <td width="33%">
-      <p align="center"><b>2.1 plug-in</b></p></td>
-    <td width="34%">
-      <p align="center"><b>Corresponding 3.0 plug-in(s)</b></p></td>
-  </tr>
-  <tr>
-    <td width="33%">org.eclipse.jface.text.*</td>
-    <td width="33%">org.eclipse.ui</td>
-    <td width="34%">org.eclipse.jface.text</td>
-  </tr>
-  <tr>
-    <td width="33%">org.eclipse.text.*</td>
-    <td width="33%">org.eclipse.ui</td>
-    <td width="34%">org.eclipse.jface.text</td>
-  </tr>
-  <tr>
-    <td width="33%">org.eclipse.ui</td>
-    <td width="33%">org.eclipse.ui</td>
-    <td width="34%">org.eclipse.ui, org.eclipse.ui.ide</td>
-  </tr>
-  <tr>
-    <td width="33%">org.eclipse.ui.actions</td>
-    <td width="33%">org.eclipse.ui</td>
-    <td width="34%">org.eclipse.ui, org.eclipse.ui.ide</td>
-  </tr>
-  <tr>
-    <td width="33%">org.eclipse.ui.dialogs</td>
-    <td width="33%">org.eclipse.ui</td>
-    <td width="34%">org.eclipse.ui, org.eclipse.ui.ide</td>
-  </tr>
-  <tr>
-    <td width="33%">org.eclipse.ui.editors.*</td>
-    <td width="33%">org.eclipse.ui</td>
-    <td width="34%">org.eclipse.ui.editor</td>
-  </tr>
-  <tr>
-    <td width="33%">org.eclipse.ui.model</td>
-    <td width="33%">org.eclipse.ui</td>
-    <td width="34%">org.eclipse.ui, org.eclipse.ui.ide</td>
-  </tr>
-  <tr>
-    <td width="33%">org.eclipse.ui.part</td>
-    <td width="33%">org.eclipse.ui</td>
-    <td width="34%">org.eclipse.ui, org.eclipse.ui.ide</td>
-  </tr>
-  <tr>
-    <td width="33%">org.eclipse.ui.texteditor</td>
-    <td width="33%">org.eclipse.ui</td>
-    <td width="34%">org.eclipse.ui.workbench.texteditor, org.eclipse.ui.editors</td>
-  </tr>
-  <tr>
-    <td width="33%">org.eclipse.ui.texteditor.*</td>
-    <td width="33%">org.eclipse.ui</td>
-    <td width="34%">org.eclipse.ui.workbench.texteditor</td>
-  </tr>
-  <tr>
-    <td width="33%">org.eclipse.ui.views.bookmarkexplorer</td>
-    <td width="33%">org.eclipse.ui</td>
-    <td width="34%">org.eclipse.ui.ide</td>
-  </tr>
-  <tr>
-    <td width="33%">org.eclipse.ui.views.contentoutline</td>
-    <td width="33%">org.eclipse.ui</td>
-    <td width="34%">org.eclipse.ui.views</td>
-  </tr>
-  <tr>
-    <td width="33%">org.eclipse.ui.views.markers</td>
-    <td width="33%">org.eclipse.ui</td>
-    <td width="34%">org.eclipse.ui.ide</td>
-  </tr>
-  <tr>
-    <td width="33%">org.eclipse.ui.views.navigator</td>
-    <td width="33%">org.eclipse.ui</td>
-    <td width="34%">org.eclipse.ui.ide</td>
-  </tr>
-  <tr>
-    <td width="33%">org.eclipse.ui.views.properties</td>
-    <td width="33%">org.eclipse.ui</td>
-    <td width="34%">org.eclipse.ui.views</td>
-  </tr>
-  <tr>
-    <td width="33%">org.eclipse.ui.views.tasklist</td>
-    <td width="33%">org.eclipse.ui</td>
-    <td width="34%">org.eclipse.ui.ide</td>
-  </tr>
-  <tr>
-    <td width="33%">org.eclipse.ui.wizards.datatransfer</td>
-    <td width="33%">org.eclipse.ui</td>
-    <td width="34%">org.eclipse.ui.ide</td>
-  </tr>
-  <tr>
-    <td width="33%">org.eclipse.ui.wizards.newresource</td>
-    <td width="33%">org.eclipse.ui</td>
-    <td width="34%">org.eclipse.ui.ide</td>
-  </tr>
-</table>
-<h2><a name="Restructuring of Platform Core Runtime plug-ins"></a>3. Restructuring of Platform Core Runtime plug-ins</h2>
-<p>The Eclipse 3.0 Platform Runtime is based on OSGi, necessitating changes to
-the structure of the two Platform Runtime plug-ins, org.eclipse.core.runtime and
-org.eclipse.core.boot.</p>
-<p>A new org.eclipse.core.runtime.compatibility plug-in provides an
-implementation bridge between the old and new APIs, and is the new home for many
-of the obsolete APIs formerly found in org.eclipse.core.runtime and
-org.eclipse.core.boot. Platform Runtime extension points are unaffected by the
-restructuring.</p>
-<p>When migrating the existing plug-in to 3.0, the plug-in's
-manifest needs to be updated to reflect the new structure of the Eclipse
-Platform Runtime plug-ins. The PDE plug-in manifest migration tool will add a
-dependency to org.eclipse.core.runtime.compatibility if required.</p>
-<p>Note also that if you mark you plug-in as 3.0 (using &lt;?eclipse version=&quot;3.0&quot;?&gt;)
-and your plug-in defines a Plugin class, you must either explicitly &lt;import
-plugin=&quot;org.eclipse.core.runtime.compatibility&quot;/&gt; in the plug-in
-manifest or ensure that the Plugin class defines the default constructor.</p>
-<p>Note: This is one of the incompatibilities that does <b>not</b> impact how
-2.1 binary plug-ins are run by Eclipse 3.0. The Eclipse 3.0 runtime automatically detects pre-3.0 plug-ins
-(by the
-absence of the &lt;?eclipse version=&quot;3.0&quot;?&gt; line in the plug-in manifest)
-and automatically compensates for these changes to the Platform Runtime.</p>
-<h2><a name="Removal of Xerces plug-in"></a>4. Removal of Xerces plug-in</h2>
-<p>The org.eclipse.xerces plug-in is no longer necessary and has been deleted.
-XML parsing
-support is built in to J2SE 1.4, and the presence of the Xerces plug-in creates class loader conflicts. The
-javax.xml.parsers, org.w3c.dom.*, and org.xml.sax.*
-API packages formerly provided by the org.eclipse.xerces plug-in are now
-available from the J2SE libraries.</p>
-<p>If your plug-in requires the org.eclipse.xerces plug-in, you must change your plug-in
-manifest to remove this stated dependency. Once that is done, the plug-in's code
-should compile and run without further change.</p>
-<p>A 2.1 binary plug-ins with a stated dependency on the org.eclipse.xerces
-plug-in will be missing a prerequisite when run in a standard Eclipse 3.0
-configuration. The plug-in will not be activated as a consequence.</p>
-<h2><a name="Eclipse 3.0 is more concurrent"></a>5. Eclipse 3.0 is more concurrent</h2>
-<p>Prior to Eclipse 3.0, Eclipse operated mostly in a single thread. Most API
-methods and extension points operated either in the UI thread, or in a thread
-spawned from a progress dialog that blocked the UI thread. Most plug-in writers
-did not have to worry much about thread safety, apart from ensuring that all UI
-activity occurred in the UI thread. In Eclipse 3.0, there is generally much more
-concurrency. Many operations now occur in a background thread, where they may
-run concurrently with other threads, including the UI thread. All plug-ins whose
-code runs in a background thread must now be aware of the thread safety of their
-code.</p>
-<p>In addition to plug-ins that are explicitly running operations in the
-background using the <code>org.eclipse.core.runtime.jobs</code> API, there are
-several platform API facilities and extension points that make use of background
-threads. Plug-ins that hook into these facilities need to ensure that their code
-is thread safe. The following table summarizes the API and extension points that
-run some or all of their code in a background thread in Eclipse 3.0:</p>
-<table border="1" width="80%">
-  <tr>
-    <td width="50%">
-      <p align="center"><b>Extension point or API class</b></p></td>
-    <td width="50%">
-      <p align="center"><b>Notes</b></p></td>
-  </tr>
-  <tr>
-    <td width="50%">org.eclipse.core.runtime.IRegistryChangeListener</td>
-    <td width="50%">New in Eclipse 3.0, runs in background</td>
-  </tr>
-  <tr>
-    <td width="50%">org.eclipse.core.resources.IResourceChangeListener</td>
-    <td width="50%"><code>AUTO_BUILD</code> events now in background</td>
-  </tr>
-  <tr>
-    <td width="50%">org.eclipse.core.resources.builders (ext. point)</td>
-    <td width="50%">Auto-build now in background</td>
-  </tr>
-  <tr>
-    <td width="50%">org.eclipse.core.resources.ISaveParticipant</td>
-    <td width="50%"><code>SNAPSHOT</code> now in background</td>
-  </tr>
-  <tr>
-    <td width="50%">org.eclipse.ui.workbench.texteditor.quickdiffReferenceProvider
-      (ext. point)</td>
-    <td width="50%">New in Eclipse 3.0, runs in background</td>
-  </tr>
-  <tr>
-    <td width="50%">org.eclipse.ui.decorators (ext. point)</td>
-    <td width="50%">Already in background in Eclipse 2.1</td>
-  </tr>
-  <tr>
-    <td width="50%">org.eclipse.ui.startup (ext. point)</td>
-    <td width="50%">Already in background in Eclipse 2.1</td>
-  </tr>
-  <tr>
-    <td width="50%">org.eclipse.team.core.org.eclipse.team.core.repository (ext.
-      point)</td>
-    <td width="50%">Many operations now in background</td>
-  </tr>
-  <tr>
-    <td width="50%">org.eclipse.team.ui.synchronizeParticipants (ext. point)</td>
-    <td width="50%">New in Eclipse 3.0, runs in background</td>
-  </tr>
-  <tr>
-    <td width="50%">org.eclipse.debug.core.launchConfigurationTypes (ext. point)</td>
-    <td width="50%">Now runs in background</td>
-  </tr>
-  <tr>
-    <td width="50%">org.eclipse.jdt.core.IElementChangedListener</td>
-    <td width="50%"><code>ElementChangedEvent.PRE_AUTO_BUILD</code> now runs in background, <code>POST_RECONCILE</code>
-      already ran in the background</td>
-  </tr>
-</table>
-<p>There are various strategies available for making code thread safe. A naive
-solution is to ensure all work occurs in the UI thread, thus ensuring serialized
-execution. This is a common approach for UI plug-ins that are not doing
-CPU-intensive processing. When doing this, be aware of the deadlock risk
-inherent in <code>Display.syncExec</code>. <code>Display.asyncExec</code> is generally
-safer as it does not introduce deadlock risk, at the expense of losing precise
-control over when the code is executed.</p>
-<p>Other techniques for making thread safe code include:</p>
-<ul>
-  <li>Wrapping unsafe code in semaphores or Java monitors. The new concurrency
-    infrastructure includes one such semaphore object: <code>org.eclipse.core.runtime.jobs.ILock</code>.
-    The advantage of <code>ILock</code> over generic locks is that they transfer
-    automatically to the UI thread when doing a <code>syncExec</code>, and there is
-    deadlock detection support built into their implementation that logs and
-    then resolves deadlocks.</li>
-  <li>Message queues. Code can be serialized by forwarding all processing to a
-    message queue that is processed serially in a single thread. One such
-    example is the SWT deferred event queue (<code>Display.asyncExec</code>), which
-    is processed entirely in the UI thread.</li>
-  <li>Immutable objects. Make data structures immutable, and make new copies on
-    modification. This is the approach used to make data structures such as <code>java.lang.String</code>
-    and <code>org.eclipse.core.runtime.IPath</code> thread safe. The advantage of
-    immutable objects is extremely fast read access, at the cost of extra work
-    on modification.</li>
-</ul>
-<h2><a name="Opening editors on IFiles"></a>6. Opening editors on IFiles</h2>
-<p>The following methods were deleted from the org.eclipse.ui.IWorkbenchPage interface.
-IWorkbenchPage is declared in the generic workbench, but the methods are inherently
-resource-specific.</p>
-    <ul>
-      <li>public IEditorPart openEditor(IFile input)</li>
-      <li>public IEditorPart openEditor(IFile input, String editorID)</li>
-      <li>public IEditorPart openEditor(IFile input, String editorID, boolean
-        activate)</li>
-      <li>public IEditorPart openEditor(IMarker marker)</li>
-      <li>public IEditorPart openEditor(IMarker marker, boolean activate)</li>
-      <li>public void openSystemEditor(IFile input)</li>
-    </ul>
-<p>Clients of these IWorkbenchPage.openEditor methods should instead call the
-corresponding public static
-    methods declared in the class org.eclipse.ui.ide.IDE (in the org.eclipse.ui.ide plug-in).</p>
-<p>Clients of these IWorkbenchPage.openSystemEditor(IFile) method should convert the IFile to an
-    IEditorInput using new FileEditorInput(IFile) and then call the
-    openEditor(IEditorInput,String) method. In other words, rewrite
-page.openSystemEditor(file) as page.openEditor(new FileEditorInput(file),
-IEditorRegistry.SYSTEM_EXTERNAL_EDITOR_ID). Note: clients using editor id
-        IEditorRegistry.SYSTEM_EXTERNAL_EDITOR_ID must pass an editor input
-        which implements org.eclipse.ui.IPathEditorInput (which FileEditorInput
-        does).</p>
-Note: This is one of the incompatibilities that does <b>not</b> impact how
-2.1 binary plug-ins are run by Eclipse 3.0. Eclipse 3.0 includes a binary runtime compatibility mechanism that
-    ensures existing 2.1 plug-in binaries using any of the deleted openEditor
-    and openSystemEditor methods continue to work as in 2.1 in spite of this API change.
-(The deleted methods are effectively &quot;added back&quot; by
-    the org.eclipse.ui.workbench.compatibility fragment.)
-<h2><a name="Editor goto marker"></a>7. Editor goto marker</h2>
-<p>The following method was deleted from the org.eclipse.ui.IEditorPart
-interface. IEditorPart is declared in the generic workbench, but the method is inherently
-resource-specific.</p>
-    <ul>
-      <li>public void gotoMarker(IMarker marker)</li>
-    </ul>
-The corresponding methods were also deleted from the classes in the
-org.eclipse.ui.part package that implement IEditorPart, namely EditorPart,
-MultiEditor, MultiPageEditorPart, and MultiPageEditor.&nbsp;
-<p>Clients that call this method should instead test if the editor part
-implements or adapts to org.eclipse.ui.ide.IGotoMarker (in the org.eclipse.ui.ide
-plug-in) and if so, call gotoMarker(IMarker). The IDE class has a convenience
-method for doing so: IDE.gotoMarker(editor, marker);</p>
-Clients that implement an editor that can position itself based on IMarker
-information should implement or adapt to org.eclipse.ui.ide.IGotoMarker.
-<p>Since IGotoMarker's only method is gotoMarker(IMarker) and has the same
-signature and specification as the old IEditorPart.gotoMarker(IMarker), existing
-editor implementations can adapt to this change simply by including IGotoMarker
-in the implements clause of the class definition.</p>
-<p>A 2.1 binary plug-ins with code that calls this method will get an class
-linking error exception when run in a standard Eclipse 3.0
-configuration.</p>
-<h2><a name="Editor launcher"></a>8. Editor launcher</h2>
-<p>The editor launcher interface org.eclipse.ui.IEditorLauncher is implemented by plug-ins that contribute
-    external editors. The following method was removed from this interface. IEditorLauncher
-is declared in the generic workbench, but the method is inherently
-resource-specific.</p>
-    <ul>
-      <li>public void open(IFile file)</li>
-    </ul>
-<p>It was replaced by</p>
-    <ul>
-      <li>public void open(IPath file)</li>
-    </ul>
-Clients that call IEditorLauncher.open(file) should instead call
-IEditorLauncher.open(file.getLocation()). Clients that implement this interface should
-replace (or augment) their implementation
-    of open(IFile) by one for open(IPath).
-<p>A 2.1 binary plug-ins with code that calls this method will get an class
-linking error exception when run in a standard Eclipse 3.0
-configuration.</p>
-<h2><a name="Editor registry"></a>9. Editor registry</h2>
-<p>The following methods were removed from the org.eclipse.ui.IEditorRegistry interface.
-IEditorRegistry is declared in the generic workbench, but the methods are inherently
-resource-specific.</p>
-    <ul>
-      <li>public IEditorDescriptor getDefaultEditor(IFile file)</li>
-      <li>public void setDefaultEditor(IFile file, String editorId)</li>
-      <li>public IEditorDescriptor[] getEditors(IFile file)</li>
-      <li>public ImageDescriptor getImageDescriptor(IFile file)</li>
-    </ul>
-Clients that call getEditors(file) or getImageDescriptor(file) should call the
-    &quot;String&quot; equivalent methods:
-<ul>
-      <li>Rewrite registry.getEditors(file) to be
-        registry.getEditors(file.getName())</li>
-      <li>Rewrite registry.getImageDescriptor(file) to be registry.getImageDescriptor(file.getName())</li>
-</ul>
-Clients that call setDefaultEditor(IFile file, String editorId) and
-    getDefaultEditor(IFile file) should should instead call the corresponding public static
-    methods declared in the class org.eclipse.ui.ide.IDE (in the org.eclipse.ui.ide
-plug-in):
-    <ul>
-      <li>Rewrite registry.getDefaultEditor(file) to be
-        IDE.getDefaultEditor(file)</li>
-      <li>Rewrite registry.setDefaultEditor(file, id) to be IDE.setDefaultEditor(file,
-        id)</li>
-    </ul>
-Also, the API contract for the method IEditorRegistrygetDefaultEditor() was
-changed. This method, which is also now deprecated, and will
-        always return the System External Editor editor descriptor. This change impacts clients that assumed the default editor returned
-        would be a text editor.
-<p>There are new constants that represent the system external editor and system
-    in-place editor identifiers (SYSTEM_EXTERNAL_EDITOR_ID and
-    SYSTEM_INPLACE_EDITOR_ID). These two editors require an editor input that
-    implements or adapts to org.eclipse.ui.IPathEditorInput. Note that the in-place
-    editor descriptor will not exist in Eclipse configurations that do not support in-place
-    editing.</p>
-<h2><a name="Workbench marker help registry"></a>10. Workbench marker help
-registry</h2>
-<p>The following method was deleted from the org.eclipse.ui.IWorkbench interface.
-IWorkbench is declared in the generic workbench, but the method is inherently
-resource-specific.</p>
-    <ul>
-      <li>public IMarkerHelpRegistry getMarkerHelpRegistry()</li>
-    </ul>
-Clients of IWorkbench.getMarkerHelpRegistry() should instead call the public static
-    method org.eclipse.ui.ide.IDE.getMarkerHelpRegistry() (in the org.eclipse.ui.ide plug-in).
-<p>A 2.1 binary plug-ins with code that calls this method will get an exception when run in a standard Eclipse 3.0
-configuration.</p>
-<h2><a name="Text editor document providers"></a>11. Text editor document providers</h2>
-<p>In order to make org.eclipse.ui.texteditor.AbstractTextEditor independent of
-IFile, org.eclipse.ui.texteditor.AbstractDocumentProvider introduces the concept
-    of a document provider operation (DocumentProviderOperation) and a document
-    provider operation runner (IRunnableContext). When requested to perform
-    reset, save, or synchronize, AbstractDocumentProvider creates document
-    provider operations and uses the operation runner to execute them. The
-    runnable context can be provided by subclasses via the getOperationRunner
-    method. Here is a summary of the changes that clients must adapt to:</p>
-<ul>
-  <li>Added protected abstract IRunnableContext getOperationRunner();
-    non-abstract subclasses must implement this method in order to provide their
-    own operation runner.</li>
-  <li>The method resetDocument has been changed to final in order to allow the
-    document provider to wrap the function with a document provider operation.
-    The document provider operation calls the newly introduced doResetDocument
-    method. AbstractDocumentProvider.doResetDocument contains the code that
-    originally resided inside AbstractDocumentProvider.resetDocument. Subclasses
-    must change their implementation of resetDocument to doResetDocument and any
-    contained call of super.resetDocument to super.doResetDocument.</li>
-  <li>The method saveDocument has been changed to final in order to allow the
-    document provider to wrap the function with a document provider operation.
-    The document provider operation calls the newly introduced doSaveDocument
-    method. AbstractDocumentProvider.doSaveDocument contains the code that
-    originally resided inside AbstractDocumentProvider.saveDocument. Subclasses
-    must change their implementation of saveDocument to doSaveDocument and any
-    contained call of super.saveDocument to super.doSaveDocument.</li>
-  <li>The method synchronize has been changed to final in order to allow the
-    document provider to wrap the function with a document provider operation.
-    The document provider operation calls the newly introduced doSynchronize
-    method. AbstractDocumentProvider.doSynchronize contains the code that
-    originally resided inside AbstractDocumentProvider.synchronize. Subclasses
-    must change their implementation of synchronize to doSynchronize and any
-    contained call of super.synchronized to super.doSynchronize.</li>
-</ul>
-<p>The AbstractDocumentProvider subclass org.eclipse.ui.editors.text.StorageDocumentProvider
-implements the getOperationRunner method to always returns null. This means that
-subclasses of StorageDocumentProvider should
-    not be affected by this change.</p>
-<p>The StorageDocumentProvider subclass org.eclipse.ui.editors.text.FileDocumentProvider
-implements the getOperationRunner method that returns an IRunnableContext for executing the given DocumentProviderOperations
-    inside a WorkspaceModifyOperation. Other changes to FileDocumentProvider
-are:</p>
-<ul>
-  <li>resetDocument(Object) has been replaced by
-    doResetDocument(Object,IProgressMonitor).</li>
-  <li> synchronize(Object) has been replaced by
-    doSynchronize(Object,IProgressMonitor).</li>
-</ul>
-<h2><a name="Text editors"></a>12. Text editors</h2>
-<p>Changes to org.eclipse.ui.texteditor.AbstractTextEditor:</p>
-<ul>
-  <li>The method IEditorPart.gotoMarker(IMarker marker) was removed from the
-    IEditorPart interface because it was resource-specific. The default
-    implementation provided by AbstractTextEditor has been removed from
-    AbstractTextEditor and has been moved to AbstractDecoratedTextEditor. Direct
-    subclasses of AbstractTextEditor or StatusTextEditor that want to provide
-    that functionality should follow the migration instructions for
-    IEditorPart [ref Editor goto marker].</li>
-  <li>AbstractTextEditor no longer differentiates between implicit and
-    explicit document providers as the concrete implementation was resource
-    specific. This functionality has been moved to AbstractDecoratedTextEditor. Direct
-    subclasses of AbstractTextEditor or StatusTextEditor must perform the
-    following steps:
-    <ul>
-      <li>Override getDocumentProvider.</li>
-      <li>Override the newly introduced hook method for disposing the document
-        provider (disposeDocumentProvider)</li>
-      <li>Override the newly introduced hook method
-        setDocumentProvider(IEditorInput) that is called while updating the
-        document provider for the new editor input. I.e., that is the method in
-        which you can configure the appropriate implicit document provider for
-        the given editor input.</li>
-    </ul>
-  </li>
-  <li>All internal occurrences of WorkspaceModifyOperation have been removed. The
-    editor now calls the document provider methods directly (see described
-    changes for document providers);
-    <ul>
-      <li>Removed createSaveOperation, changed performSaveOperation to
-        performSave. Subclasses of AbstractTextEditor overriding
-        createSaveOperation or performSaveOperation must now override
-        performSave.</li>
-      <li>Removed createdRevertOperation, changed peformRevertOperation to
-        performRevert. Sunclasses overriding createRevertOperation or
-        performRevertOperation must now override performRevert.</li>
-      <li>The implementation of the method handleEditorInputChanged has been
-        changed to not use WorkbenchModifyingOperation. Subclasses overriding
-        handleEditorInputChange must adapt accordingly. Please use the changes
-        applied to AbstractTextEditor.handleEditorInputChange as the blueprint.</li>
-    </ul>
-  </li>
-  <li>AbstractTextEditor.createActions no longer registers any actions under
-    ITextEditorActionConstants.ADD_TASK and ITextEditorActionConstant.BOOKMARK
-    as those actions are IDE-specific. The registration of these actions has
-    been moved to AbstractDecoratedTextEditor. Direct subclasses of AbstractTextEditor or
-    StatusTextEditor should override the createActions method and add the
-    following lines (accordingly adapted to their circumstances):</li>
-  <li>
-    <pre> ResourceAction action= new AddMarkerAction(TextEditorMessages.getResourceBundle(), &quot;Editor.AddBookmark.&quot;, this, IMarker.BOOKMARK, true); //$NON-NLS-1$
-  action.setHelpContextId(ITextEditorHelpContextIds.BOOKMARK_ACTION);
-  action.setActionDefinitionId(ITextEditorActionDefinitionIds.ADD_BOOKMARK);
-  setAction(IDEActionFactory.BOOKMARK.getId(), action);     </pre>
-    <pre>  action= new AddTaskAction(TextEditorMessages.getResourceBundle(), &quot;Editor.AddTask.&quot;, this); //$NON-NLS-1$
-  action.setHelpContextId(ITextEditorHelpContextIds.ADD_TASK_ACTION);
-  action.setActionDefinitionId(ITextEditorActionDefinitionIds.ADD_TASK);
-  setAction(IDEActionFactory.ADD_TASK.getId(), action);</pre>
-  </li>
-</ul>
-<p>The AbstractTextEditor subclass org.eclipse.ui.texteditor.StatusTextEditor provides the predicate method isErrorStatus(IStatus).
-    Subclasses may override in order to decide whether a given status must
-    considered an error or not.</p>
-<p>Changes to org.eclipse.ui.editors.text.AbstractDecoratedTextEditor:</p>
-<ul>
-  <li>The IEditorPart method gotoMarker(IMarker marker) has been deprecated to
-    allow a future change of its visibility. Clients of this method must follow
-    the migration instructions in the deprecation message.</li>
-  <li>AbstractDecoratedTextEditor returns an adapter for IGotoMarker.</li>
-  <li>AbstractDecoratedTextEditor implements the concept of implicit/explicit document
-    providers previously provided by AbstractTextEditor, as discussed above.</li>
-</ul>
-<h2><a name="Headless annotation support"></a>13. Headless annotation support</h2>
-<p>As part of the introduction of headless annotation support, the following changes to Annotation were made:</p>
-<ul>
-  <li>Removed static Annotation.drawImage methods, use org.eclipse.jface.text.source.ImageUtilities instead.</li>
-  <li>Removed setLayer, getLayer, and paint methods from Annotation, annotations which want to draw
-      themselves should implement IAnnotationPresentation.</li>
-  <li>MarkerAnnotation now directly implements the methods removed from Annotation (setLayer, getLayer, paint).</li>
-  <li>The following classes have been moved from the plug-in org.eclipse.jface.text to the plug-in 
-      org.eclipse.text, the package names remain the same and org.eclipse.jface.text rexports the classes from org.eclipse.jface.text,
-      such that this change is transparent to clients:</li>
-</ul>
-<pre>        org.eclipse.jface.text.source.Annotation 
-        org.eclipse.jface.text.source.AnnotationModel 
-        org.eclipse.jface.text.source.AnnotationModelEvent 
-        org.eclipse.jface.text.source.IAnnotationModel 
-        org.eclipse.jface.text.source.IAnnotationModelListener 
-        org.eclipse.jface.text.source.IAnnotationModelListenerExtension</pre>
-<h2> <a name="Console view"></a>14. Console view</h2>
-<p>Eclipse 3.0 has new generic console support. The generic console is available via the Window
-&gt; Show View &gt; Basic &gt; Console,
-and is used by the Eclipse debug and Ant integration.</p>
-<p>The view id for the console has changed from org.eclipse.debug.ui.ConsoleView
-to org.eclipse.ui.console.ConsoleView. 2.1 plug-ins that programmatically open
-the console will be unsuccessful because that the old view no longer exists.</p>
-<h2><a name="Java breakpoint listeners"></a>15. Java breakpoint listeners</h2>
-<p>In 3.0, the return types for the methods org.eclipse.jdt.debug.core.IJavaBreakpointListener.breakpointHit(IJavaBreakpoint, IJavaThread) and
-installingBreakpoing(IJavaTarget, IJavaBreakpoint, IJavaType) changed from
-boolean to int to allow listeners to vote &quot;don't care&quot;. In releases
-prior to 3.0, listeners could only vote &quot;suspend&quot; or &quot;don't
-suspend&quot; when a breakpoint was hit, and &quot;install&quot; or &quot;don't
-install&quot; when a breakpoint was about to be installed. In 3.0, listeners can
-also vote &quot;don't care&quot; for either of these notifications. This allows
-clients to only make a decisive vote in situations that they care about. For
-&quot;breakpoint hit&quot; notifications, the breakpoint will suspend if any
-listeners vote &quot;suspend&quot;, or all listeners vote &quot;don't
-care&quot;; and it will not suspend if at least one listener votes &quot;don't
-suspend&quot; and no listeners vote &quot;suspend&quot;. Similarly, for
-&quot;breakpoint installing&quot; notifications, the breakpoint will be
-installed if any listeners vote to install, or all listeners vote &quot;don't
-care&quot;; and it will not be installed if at least one listener votes
-&quot;don't install&quot; and no listeners vote &quot;install&quot;. In general,
-implementors should return DONT_CARE unless they have a strong opinion one way
-or the other. It is important to keep in mind, for example, that voting
-&quot;suspend&quot; will override any other listener's vote of &quot;don't
-suspend&quot;.</p>
-<p>The IJavaBreakpointListener interface is implemented by clients that create
-or react to breakpoints in Java code. There are likely few clients beyond JDT
-itself, save the one that reported the problem (<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=37760">bug
-37760</a>) that this change remedies. This is a breaking change for existing
-code that implements the IJavaBreakpointListener interface. This code needs to
-be modified to return an appropriate int value before it will compile or run in
-3.0.</p>
-<h2><a name="Clipboard access in UI thread"></a>16. Clipboard access in UI thread</h2>
-<p>Prior to 3.0, the methods on the SWT class org.eclipse.swt.dnd.Clipboard were tacitly permitted
-to run in threads other than the UI thread. This oversight resulted in failures
-on GTK where the operating system requires that all clipboard interactions be
-performed in the UI thread. The oversight was not revealed earlier because many
-applications are single-threaded and receive most of their testing on Windows.
-In order for the Clipboard API to be sustainable and cross-platform, in 3.0 the
-specification and implementation of all Clipboard API methods have been changed
-to throw an SWT Exception (ERROR_THREAD_INVALID_ACCESS) if invoked from a non-UI
-thread. Clipboard services are commonly provided automatically by Eclipse
-components such as the text editor, which insulate many clients from this
-breaking change. Existing code that does make direct use of Clipboard should
-ensure that the API methods are called on the correct thread, using
-Display.asyncExec or syncExec when appropriate to shift accesses into the UI thread.</p>
-<h2><a name="Key down events"></a>17. Key down events</h2>
-<p>In 3.0, SWT reports key down events before the work is done in the OS. This
-is much earlier than it was prior to 3.0. This change was made to support key
-bindings in Eclipse which necessitates intercepting key events before any widget
-has a chance to process the character. Consequences of this change are visible
-to code that handles low-level org.eclipse.swt.SWT.KeyDown events directly. For example, it
-means that when a listener on a Text widget receives a key down event, the
-widget's content (getText()) will not yet include the key just typed (it would
-have prior to 3.0). The recommended way to get the full text from the widget
-including the current key is to handle the higher-level SWT.Modify or SWT.Verify
-events rather than the low-level SWT.KeyDown event; code that already does it this way
-is unaffected by this change.</p>
-<h2><a name="Tab traversal of custom controls"></a>18. Tab traversal of custom controls</h2>
-<p>Prior to 3.0, when the focus was in the SWT class org.eclipse.swt.widgets.Canvas or one of its subclasses
-(including custom widgets), typing Ctrl+Tab, Shift+Tab, Ctrl+PgUp, or Ctrl+PgDn
-would automatically trigger traversal to the next/previous widget without
-reporting a key event. This behavior was unspecified, and runs counter to the
-rule that Canvases see every key typed in them. The proper way to handle
-traversal is by registering a traverse listener. In order to properly support
-Eclipse key bindings in 3.0, the default behavior was changed so that Canvas now
-sees Ctrl+Tab, Shift+Tab, Ctrl+PgUp, and Ctrl+PgDn key events instead of
-traversing. If you use a raw Canvas or define a subclass of Canvas, ensure that
-that you register a traverse listener.</p>
-<h2><a name="Selection event order in SWT table and tree widgets"></a>19. Selection event order in SWT table and tree widgets</h2>
-<p>Mouse selections of items in the SWT classes org.eclipse.swt.widgets.Table and Tree generate the event
-sequence MouseDown-Selection-MouseUp uniformly in all operating environments.
-Similarly, keyboard selections generate the event sequence
-KeyDown-Selection-KeyUp uniformly in all operating environments. Prior to 3.0,
-the event order was not uniform, with Motif and Photon at variance with the rest
-by always reporting the Selection event first; i.e., Selection-MouseDown-MouseUp
-or Selection-KeyDown-KeyUp. For 3.0, the event order on Motif and Photon has
-been changed to match the others. Existing code that was functioning correctly
-on {Windows, GTK} and on {Motif, Photon} is unlikely to be affected. But it is
-wise to check your code to ensure that it does not rely on an invalid event
-order.</p>
-<h2><a name="New severity level in status objects"></a>20. New severity level in status objects</h2>
-<p><code>org.eclipse.core.runtime.IStatus</code> has a new severity constant, <code>IStatus.CANCEL</code>,
-that can be used to indicate cancelation. Callers of <code>IStatus.getSeverity()</code>
-that rely on the set of possible severities being limited to <code>IStatus.OK</code>,
-<code>INFO</code>, <code>WARNING</code>, and <code>ERROR</code> are affected by this addition. Callers of
-<code>getSeverity</code> should update 
-their code to include the new severity.</p>
-<h2><a name="Build-related resource change notifications"></a>21. Build-related resource change notifications</h2>
-<p>In Eclipse 3.0, workspace auto-builds now occur in a background thread. This
-required an API contract change to <code>org.eclipse.core.resources.IResourceChangeEvent</code>. The contract
-of <code>IResourceChangeEvent</code> previously guaranteed the following ordering of
-events for all workspace changes:</p>
-<ol>
-  <li><code>PRE_DELETE</code> or <code>PRE_CLOSE</code> event notification if applicable</li>
-  <li>Perform the operation</li>
-  <li><code>PRE_AUTO_BUILD</code> event notification</li>
-  <li>If auto-build is on, perform incremental workspace build</li>
-  <li><code>POST_AUTO_BUILD</code> event notification</li>
-  <li><code>POST_CHANGE</code> event notification</li>
-</ol>
-<p>With auto-build now running in the background, there is no longer any
-guarantee about the temporal relationship between the <code>AUTO_BUILD</code> events
-and the <code>POST_CHANGE</code> event. In Eclipse 3.0, steps 3-5 in the above
-structure are removed from the operation. The resulting picture looks like this:</p>
-<ol>
-  <li><code>PRE_DELETE</code> or <code>PRE_CLOSE</code> event notification if applicable</li>
-  <li>Perform the operation</li>
-  <li><code>POST_CHANGE</code> event notification</li>
-</ol>
-<p>Periodically, the platform will perform a background workspace build
-operation. Note that this happens regardless of the whether auto-build is on or
-off. The exact timing of when this build occurs will not be specified. The
-structure of the build operation will look like this:</p>
-<ol>
-  <li><code>PRE_BUILD</code> event notification (<code>PRE_BUILD</code> is the
-    new name for <code>PRE_AUTO_BUILD)</code></li>
-  <li>If auto-build is on, perform incremental workspace build</li>
-  <li><code>POST_BUILD</code> event notification (<code>POST_BUILD</code> is the
-    new name for <code>POST_AUTO_BUILD)</code></li>
-  <li><code>POST_CHANGE</code> event notification</li>
-</ol>
-<p>The reference point for the deltas received by auto-build listeners will be
-different from post-change listeners. Build listeners will receive notification
-of all changes since the end of the last build operation. Post-change listeners
-will receive a delta describing all changes since the last post-change
-notification. This new structure retains three characteristics of resource
-change listeners that have been true since Eclipse 1.0:</p>
-<ul>
-  <li><code>POST_CHANGE</code> listeners receive notification of absolutely all
-    resource changes that occur during the time they are registered. This
-    includes changes made by builders, and changes made by other listeners.</li>
-  <li><code>PRE_AUTO_BUILD</code> listeners receive notification of all resource
-    changes <b>except</b> changes made by builders and resource change
-    listeners.</li>
-  <li><code>POST_AUTO_BUILD</code> listeners receive notification of all resource
-    changes <b>except</b> changes made by other <code>POST_AUTO_BUILD</code>
-    listeners.</li>
-</ul>
-<p>However, there are some important differences with this approach. Prior to
-Eclipse 3.0, auto-build listeners were always called before <code>POST_CHANGE</code>
-listeners. For this reason, the delta received by auto-build listeners was
-always a subset of the delta received by the <code>POST_CHANGE</code> listeners.
-This relationship is now essentially reversed. Auto-build listeners will receive
-a delta that is a super-set of all deltas supplied to <code>POST_CHANGE</code>
-listeners since the end of the last background build. As before, auto-build
-listeners will be allowed to modify the workspace, and post-change listeners
-will not.</p>
-<p>It will no longer be true that upon completion of a workspace changing
-operation, that <code>AUTO_BUILD</code> event listeners will have been notified.
-Client code that registers resource change listeners with <code>IWorkspace.addResourceChangeListener(IResourceChangeListener)</code>
-is unlikely to be affected by this change because <code>AUTO_BUILD</code>
-events were never reported to these listeners. However, clients that use <code>IWorkspace.addResourceChangeListener(IResourceChangeListener,int)</code>
-and specify an event mask that includes <code>AUTO_BUILD</code> events are likely to
-be broken by this change if they make assumptions about when auto-build
-listeners run or what thread they run in. For example, if an auto-build listener
-is updating a domain model to reflect changes to the workspace, then this update
-might not have happened when the workspace changing operation returns. It is
-worth noting that only UI-level code can be affected in this way. Core-level
-code that is called via API may be called within the scope of an <code>IWorkspaceRunnable</code>,
-so it can never be sure about when resource change listeners will be called. The
-suggested fix for this breakage is to use <code>POST_CHANGE</code> instead of build
-listeners if it is necessary to have notification occur before the operation
-completes.</p>
-<h2><a name="Intermediate notifications during workspace operations"></a>22. Intermediate notifications during workspace operations</h2>
-<p>It will no longer be guaranteed that all resource changes that occur during
-the dynamic scope of an <code>IWorkspaceRunnable</code> will be batched in a
-single notification. This mechanism can still be used for batching changes to
-avoid unnecessary builds and notifications, but the Platform may now decide to
-perform notifications during the operation. This API contract change is not
-likely to be a breaking change for existing clients. It is equivalent to the
-Platform deciding to call <code>IWorkspace.checkpoint</code> periodically during
-a long running operations. The reason for this change is that it is now possible
-for multiple threads to be modifying the workspace concurrently. When one thread
-finishes modifying the workspace, a notification is required to prevent
-responsiveness problems, even if the other operation has not yet completed. This
-change also allows users to begin working on a set of resources before the
-operation completes. For example, a user can now begin browsing files in a
-project that is still in the process of being checked out. The new method <code>IWorkspace.run(IWorkspaceRunnable,
-ISchedulingRule, int, IProgressMonitor)</code> has an optional flag, <code>AVOID_UPDATE</code>,
-which operations can use as a hint to the platform to specify whether periodic
-updates are desired.</p>
-<h2><a name="URL stream handler extensions"></a>23. URL stream handler extensions</h2>
-<p><strong>What is affected:</strong> Plug-ins that contribute extensions to the <code>org.eclipse.core.runtime.urlHandlers</code>
-extension point.</p>
-<p><strong>Description:</strong> The contract for the <code>org.eclipse.core.runtime.urlHandlers</code>
-extension point was changed to use the URL Stream Handler service provided by
-OSGi. The OSGi support is superior to the one in Eclipse 2.1, and correctly
-handles dynamic handlers. Because of various design issues with the base Java
-URL handler mechanism, URLStreamHandlers registered with the OSGi handler
-service must implement <code>org.osgi.service.url.URLStreamHandlerService</code>.</p>
-<p><strong>Action required:</strong> Formerly, the handler class had to
-implement <code>java.net.URLStreamHandler</code> and extend the urlHandlers
-extension point. The extension point is no longer supported and the handler must
-be updated to implement <code>org.osgi.service.url.URLStreamHandlerService</code>
-interface. The OSGi framework provides an abstract base class (<code>org.osgi.service.url.AbstractURLStreamHandlerService</code>)
-that can be trivially subclassed to fill this role.</p>
-<p>Instead of registering the handler using an extension point, plug-ins must
-now do so by registering their handler as a service. For example,</p>
-<pre>    Hashtable properties = new Hashtable(1);
-    properties.put(URLConstants.URL_HANDLER_PROTOCOL, new String[] {MyHandler.PROTOCOL});
-    String serviceClass = URLStreamHandlerService.class.getName();
-    context.registerService(serviceClass, new MyHandler(), properties);
-</pre>
-<h2><a name="Class load order"></a>24. Class load order</h2>
-<p><b>What is affected:</b> Plug-ins which supply packages provided which are
-also supplied by other plug-ins. A very limited number of plug-ins are affected
-by this change and some of those affected will actually benefit (see below).</p>
-<p><b>Description:</b> In Eclipse 2.x, class loaders search for classes in the
-following order: consult (1) parent class loader (in practice this is the Java boot
-class loader), then (2) its own classpath contents, and finally (3) all of its prerequisites
-in the order declared. OSGi offers an optimization over this model. In this approach a
-class loader will consult (1)
-parent class loader (again, effectively the Java boot classloader), then either
-(2a) a single
-prerequisite known to contribute classes in the package being queried or (2b) its
-own classpath entries for the desired class.</p>
-<p>The class loader determines whether to consult self or its prerequisites based
-on its imported and required packages. This information is inferred from the
-plug-in content in the case of traditional plug-ins and directly specified in the
-case of plug-ins with explicit OSGi bundle manifest. In either case, it is known <i>a priori</i> which class
-loaders will supply the classes for which packages. This offers performance
-improvements as well as a solution to the vexing problem of multiple
-prerequisites contributing the same classes.</p>
-<p>Take for example the case of Xerces and Xalan, both of which contain various classes
-from org.xml packages. Using the first approach, the Xerces plug-in would see its
-copy of these classes while the Xalan plug-in would see their copy. Since these
-plug-ins need to communicate, ClassCastExceptions occur. Using the second
-approach,
-only one of the two plug-ins contributes the duplicate classes and both plug-ins
-see the same copies.</p>
-<p><b>Action required:</b> The action required depends on the particulars of the
-usecase. Affected developers need to review their classpath and resolve any
-conflicts which may be happening.</p>
-<h2><a name="Class loader protection domain not set"></a>25. Class loader protection domain not set</h2>
-<p><b>What is affected:</b> Plug-ins that expect the protection domain of their
-class loader to be set at all times.</p>
-<p><b>Description:</b> In Eclipse 2.1 plug-in class loaders were
-java.security.SecureClassloaders and, as such, always had a protection domain set. In Eclipse
-3.0, class loaders do not extend SecureClassloader and only set the protection
-domain if Java security is turned on (not the normal case).</p>
-<p><b>Action required:</b> The action required will depend on the scenario in
-which the plug-in is using the protection domain.</p>
-<h2><a name="PluginModel object casting"></a>26. PluginModel object casting</h2>
-<p><b>What is affected:</b> Plug-ins which cast objects of type
-org.eclipse.core.runtime.IPlugin* to org.eclipse.core.runtime.model.Plugin*Model. Even though the relationship between these interfaces and the
-model classes is not specified in the Eclipse 2.1 API, we are explicitly
-calling out this change as we have found instances of plug-ins relying on this
-relationship in the 2.1 implementation.</p>
-<p><b>Description:</b> The Eclipse API provides a series of interfaces (e.g., <code>IPluginDescriptor</code>)
-and so-called &quot;model&quot; classes (e.g., <code>PluginDescriptorModel</code>)
-related to plug-ins and the plug-in registry. In the Eclipse 2.1 implementation
-it happens that the model classes implement the relevant interfaces. In the new
-OSGi-based runtime, the plug-in registry has been significantly reworked to allow for a
-separation between the class loading and prerequisite aspects of plug-ins and the
-extension and extension-point aspects. As such the Eclipse 3.0 runtime is unable
-to maintain the implementation relationship present in 2.1.</p>
-<p><b>Action required:</b>  Plug-ins relying on this non-API
-relationship need to be reworked code according to their usecase. More
-information on this is given in the recommended changes section of this document
-and in the Javadoc for the related classes and methods.</p>
-<h2><a name="ILibrary implementation incomplete"></a>27. ILibrary implementation incomplete</h2>
-<p><b>What is affected:</b> Plug-ins that use <code>org.eclipse.core.runtime.ILibrary</code>.</p>
-<p><b>Description:</b> The new runtime maintains the classpath entries in a
-different and incompatible form from Eclipse. As a result, the compatibility
-layer is unable to correctly model the underlying OSGi structures as ILibrary
-objects. The runtime's compatibility support creates ILibrary objects but must
-assume default values for everything except the library's path.</p>
-<p><b>Action required:</b> Users of ILibrary should consider accessing the
-desired header values (e.g., <code>Bundle-Classpath</code>) from the appropriate
-Bundle (see <code>Bundle.getHeaders()</code>) and using the <code>ManifestElement</code>
-helper class to interpret the entries. See the class Javadoc for more details.</p>
-<h2><a name="Invalid assumptions regarding form of URLs"></a>28 Invalid assumptions regarding form of URLs</h2>
-<p><b>What is affected:</b> Plug-ins that make assumptions regarding their
-installation structure, location and the local file system layout.</p>
-<p><b>Description:</b> Methods such as <code>IPluginDescriptor.getInstallURL()</code>
-return URLs of a particular form. Despite their form being unspecified, various
-plug-ins are making assumptions based on the current implementation. For example, they
-may expect to get a <code>file:</code> URL and use URL.getFile() and use <code>java.io.File</code>
-manipulation on the result. To date, this has been a workable but rather fragile
-approach. For example, if a plug-in is installed on a web server, it is possible
-that an <code>http:</code> URL would be returned. The new Eclipse 3.0 runtime is
-even more flexible and opens more possibilities for execution configurations
-(e.g., maintaining whole plug-ins in JARs rather than exploded in directories).
-That is, while the new OSGi-based runtime does not actually break 2.1 API, it exposes more
-cases where assumptions made in current plug-ins are invalid.</p>
-<p><b>Action required:</b> Plug-in writers should ensure that the information to
-which they need access is available via <code>getResource()</code> (and is on the
-classpath) or use the relevant API for accessing the contents of a plug-in
-(e.g., <code>Bundle.getEntry(String)</code>).</p>
-<h2><a name="BootLoader methods moved/deleted"></a>29. BootLoader methods moved/deleted</h2>
-<p><b>What is affected:</b> Non-plug-in code that calls certain methods from the class
-<code>org.eclipse.core.boot.BootLoader</code>.</p>
-<p><b>Description:</b>  The static methods BootLoader.startup(), shutdown() and run() were
-moved to org.eclipse.core.runtime.adaptor.EclipseStarter, which is part of the OSGi framework.
-This API is the interface between the main() in startup.jar and the OSGi
-framework/Eclipse runtime. The restructuring of the runtime did not permit these methods
-to remain on BootLoader. The old BootLoader class is now located in the runtime compatibility
-layer and is deprecated, and the moved methods are stubbed to do nothing.</p>
-<p>There is no replacement for the old BootLoader.getRunnable() as the runtime can no
-longer support the acquisition of individual applications. Rather, users must indicate the application of interest when they start the platform.</p>
-<p><b>Action required:</b> In general this API is used by very few people (it
-cannot be used from within an Eclipse plug-in). In
-the rare case that it is, the code must be adapted to use the corresponding methods on
-EclipseStarter.</p>
-
-<h2><a name="Plug-in export does not include the plug-in's JARs automatically"></a>30. Plug-in export does not include the
-plug-in's JARs automatically</h2>
-<p><b>What </b><strong> is affected:</strong> All plug-ins.</p>
-<p><strong>Description:</strong> In Eclipse 2.1, a plug-in's bin.includes line 
-  from their build.properties did not have to contain the list of JARs from their 
-  library declaration in the plugin.xml file; these JARs were added for free. 
-  In Eclipse 3.0 the list of files in the bin.includes section of the build.properties 
-  is an exhaustive list and must include all files which plug-in developers intend 
-  to be included in their plug-in when building or exporting.</p>
-<p><strong>Action required:</strong> Ensure that the bin.includes line from the 
-  build.properties file includes all of the JARs listed in your plugin.xml file.</p>
-
-
-<h2><a name="Re-exporting runtime API"></a>31. Re-exporting runtime API</h2>
-<p><b>What is affected:</b> Plug-ins that expose API that includes elements from
-changed runtime API.</p>
-<p><b>Description:</b> Various plug-ins expose API that includes elements from
-the runtime API. With the changes to the Eclipse 3.0 runtime outlined here,
-client plug-ins must re-evaluate their use of runtime API in their API.</p>
-<p><b>Action required:</b> This scenario is quite rare as very little of
-the Eclipse runtime API is changing. Depending on the scenario, clients may have
-to change their API or continue to rely on the the compatibility layer.</p>
-<h2><a name="Plug-in parsing methods on Platform"></a>32. Plug-in parsing methods on Platform</h2>
-<p><b>What is affected:</b> Plug-ins that use <code>org.eclipse.core.runtime.Platform.parsePlugins(...,
-Factory).</code></p>
-<p><b>Description:</b> The method <code>org.eclipse.core.runtime.Platform.parsePlugins(...,
-Factory)</code> has been moved. The API associated with the Factory argument has
-been moved from the org.eclipse.core.runtime plug-in up to the
-org.eclipse.core.runtime.compatibility plug-in (which depends on the runtime
-plug-in). As a result, the parsing method has been moved as well.</p>
-<p><b>Action required:</b> Users of this method should use the same method on
-the class <code>org.eclipse.core.runtime.model.PluginRegistryModel</code>.</p>
-<h2><a name="Plug-in libraries supplied by fragments"></a>33. Plug-in libraries supplied by fragments</h2>
-<p><b>What </b><strong> is affected:</strong> Plug-ins that specify code on their
-classpath but do not supply that code (i.e., the JAR is supplied by a fragment;
-for example, the org.eclipse.swt plug-in).</p>
-<p><strong>Description:</strong> The new runtime must convert plug.xml files to
-manifest.mf files behind the scenes. This is done through a straight mechanical transformation and
-an analysis of the jars listed and supplied by the plug-in. In the case where a
-plug-in specifies a jar on its classpath but does not supply the jar, there is
-no code to analyze and the plug-in convertor cannot generate a correct
-manifest.mf.</p>
-<p><strong>Action required:</strong> Providers of such plug-ins must either
-change to supply the appropriate jar in the plug-in itself or hand
-craft/maintain a META-INF/MANIFEST.MF file for their plug-in. Typically this can
-be done using PDE to get the initial manifest and then adding in the appropriate
-Provide-Package header.</p>
-<h2><a name="Changes to build scripts"></a>34. Changes to build scripts</h2>
-<p><b>What is affected:</b> Scripts (e.g., Ant build.xml
-files) which define classpaths containing runtime-related jars and class
-directories.</p>
-<p><b>Description:</b> The new runtime contains a number of new plug-ins and
-jars. Their introduction was mandated by the refactoring of the runtime into
-configurable pieces. For most runtime situations these changes are transparent.
-However, if you have custom build.xml (or similar) scripts which currently
-compile code against <code>org.eclipse.core.runtime</code>, you will need to update
-them before they will function correctly. A typical script contains a classpath
-entry in a &lt;javac&gt; task that references the <code>org.eclipse.core.runtime</code>
-plug-in as follows:</p>
-<pre>    ../org.eclipse.core.runtime/bin;../org.eclipse.core.runtime/runtime.jar</pre>
-<p>The runtime plug-in continues to contain much of the original runtime code.
-However, various parts of the runtime which are there only for compatibility
-purposes are contained in a compatibility plug-in (<code>org.eclipse.core.runtime.compatibility</code>).
-Most of the new runtime code is contained in a collection of plug-ins (<code>org.eclipse.osgi.*</code>).</p>
-<p><b>Action required:</b> Developers should add the entries below as needed to
-eliminate compilation errors. While the complete set of jars supplied is listed
-below, typical uses require only a subset on the classpath at compile time. As
-usual, the inclusion of the /bin directories is discretionary. The entries are
-given here in logical groupings by supplying plug-in:</p>
-<ul>
-  <li>../org.eclipse.core.runtime.compatibility/bin;../org.eclipse.core.runtime.compatibility/compatibility.jar;</li>
-  <li>../org.eclipse.osgi/bin;../org.eclipse.osgi/osgi.jar;</li>
-  <li>../org.eclipse.update.configurator/bin;../org.eclipse.update.configurator/configurator.jar;</li>
-  <li>../org.eclipse.osgi.util/util.jar;</li>
-</ul>
-<p>In addition the following jars may be required in special cases:</p>
-<ul>
-  <li>../org.eclipse.osgi/core.jar; ../org.eclipse.osgi/resolver.jar; ../org.eclipse.osgi/defaultAdaptor.jar;
-    ../org.eclipse.osgi/eclipseAdaptor.jar; ../org.eclipse.osgi/console.jar</li>
-</ul>
-<p>While updating such scripts, you should also take the opportunity to clean up
-(i.e., remove) references to <code>org.eclipse.core.boot</code>. This plug-in is
-obsolete and longer contains any code. The entries can be left on the classpath
-but they serve no purpose and should be removed. Look to remove:
-</p>
-<pre>    ../org.eclipse.core.boot/bin;../org.eclipse.core.boot/boot.jar</pre>
-<h2><a name="Changes to PDE build Ant task"></a>35. Changes to PDE build Ant task</h2>
-<p><b>What is affected:</b> Scripts (e.g., Ant build.xml
-files) using the eclipse.buildScript task.</p>
-<p><b>Description:</b> PDE Build introduced a new property to the eclipse.buildScript task to control the generation of plug-ins build
-scripts. This was mandated by the introduction of the new OSGi-based runtime.
-</p><p><b>Action required:</b> If you want to use Eclipse 3.0 to build a 2.1 based product, 
-then introduce in eclipse.buildScript the property "buildingOSGi" and set it to false.
-For example: </p><pre>&lt;eclipse.buildScript ... buildingOSGi=&quot;false&quot;/&gt;</pre>	
-
-<h2><a name="Changes to eclipse.buildScript Ant task"></a>36. Changes to
-eclipse.build Ant task</h2>
-<p><b>What is affected:</b> Scripts (e.g., Ant build.xml files) using the
-eclipse.buildScript task.</p>
-<p><b>Description:</b> PDE Build introduced a new property to the
-eclipse.buildScript task to control the generation of plug-ins build scripts.
-This was mandated by the introduction of the new OSGi-based runtime.</p>
-<p><b>Action required:</b> If you want to use Eclipse 3.0 to build a 2.1 based
-product, then introduce in eclipse.buildScript the property &quot;buildingOSGi&quot;
-and set it to false. For example:
-<pre>&lt;eclipse.buildScript ... buildingOSGi=&quot;false&quot;/&gt;</pre></p>
-<h2><a name="Changes to eclipse.fetch Ant task"></a>37. Changes to eclipse.fetch
-Ant task</h2>
-<p><b>What is affected:</b> Scripts (e.g., Ant build.xml files) using the
-eclipse.buildScript task.</p>
-<p><b>Description:</b> PDE Build changed the behavior of the eclipse.fetch task
-to ease building eclipse in an automated build style. The elements style now
-only support one entry at a time and the scriptName is always ignored.</p>
-<p><b>Action required:</b> If you had a list of entries in the
-&quot;elements&quot; tag of an eclipse.fetch call, spread them out over several
-call to eclipse.fetch. If you use to set the scriptName, note that now the
-generated fetch script is always called &quot;fetch_{elementId}&quot;. For
-example:</p>
-<pre>&lt;eclipse.fetch elements=&quot;plugin@org.eclipse.core.runtime, feature@org.eclipse.platform&quot; .../&gt;</pre>
-<p>becomes</p>
-<pre>&lt;eclipse.fetch elements=&quot;plugin@org.eclipse.core.runtime&quot; .../&gt;
-&lt;eclipse.fetch elements=&quot;feature@org.eclipse.platform&quot; .../&gt;</pre>
-
-<h2><a name="Replacement of install.ini"></a>38. Replacement of install.ini</h2>
-<p>The install.ini file is no longer included. In its place is the new
-config.ini file in the configuration sub-directory. Products that used the
-install.ini file to specify a primary feature (e.g., to provide branding
-information) need to make changes to the config.ini file instead. In addition to
-the new filename, the names of the keys have changed.</p>
-<p>The value of the feature.default.id key in 2.1 should be set as the value of
-the new eclipse.product key. The value of the eclipse.application should be set
-to &quot;org.eclipse.ui.ide.workbench&quot;.</p>
-<p>Finally, in 2.1 the image for the splash image was always splash.bmp in the
-branding plug-in's directory. In 3.0 the location of the splash image is
-provided explicitly by the osgi.splashPath key in the config.ini file.</p>
-
-
-
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/3.0/recommended.html b/bundles/org.eclipse.platform.doc.isv/porting/3.0/recommended.html
deleted file mode 100644
index bd47d84..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/3.0/recommended.html
+++ /dev/null

@@ -1,1149 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Changes required when adopting 3.0 mechanisms and APIs</title>
-</head>
-
-<body>
-
-<h2>Changes required when adopting 3.0 mechanisms and APIs</h2>
-<p>This section describes changes that are required if you are trying to change
-  your 2.1 plug-ing to adopt the 3.0 mechanisms and APIs.</p>
-<h3>Getting off of org.eclipse.core.runtime.compatibility</h3>
-<p>The Eclipse 3.0 runtime is significantly different. The underlying implementation
-  is based on the OSGi framework specification. Eclipse 3.0 runtime includes
-  a compatibilty layer
-  (in the org.eclipse.core.runtime.compatibility plug-in) which maintains the
-  2.1 APIs. Plug-in
-  developers interested in additional performance and function should consider
-  adopting the 3.0 APIs and removing their dependence on the compatibility layer.
-Compatibility code shows up in three places:</p>
-<ul>
-  <li>org.eclipse.core.boot - entire plug-in is legacy</li>
-  <li>org.eclipse.core.runtime.compatibility - entire plug-in is legacy</li>
-  <li>org.eclipse.core.runtime - various classes and methods are legacy</li>
-</ul>
-<p>The text below gives more detail on the which classes and methods are present
-  for compatibility purposes as well as guidance on how to update your plug-in.</p>
-<h4>Plug-ins and bundles</h4>
-<p>The Eclipse runtime has been refactored into two parts; classloading and prerequisite
-  management, and extension/extension-point management. This split allows for
-  natural/seamless adoption of the OSGi framework specification for classloading
-  and prerequisite management. This in turn enables a range of new capabilities
-  in the runtime from dynamic plug-in install/update/uninstall to security and
-  increased configurability.</p>
-<p>While we continue to talk about <i>plug-ins</i>, in the new runtime a plug-in
-  is really a <i>bundle</i> plus some extensions and extension-points. The term <i>bundle</i> is
-  defined by the OSGi framework specification and refers to a collection of types
-  and resources and associated inter-bundle prerequisite information. The <i>extension
-  registry</i> is the new form of the plug-in registry  and details only extension
-  and extension-point information. By-in-large the extension registry API is
-  the same as the relevant plug-in
-  registry API (for more information see <a href="#registries">Registries</a>).</p>
-<p>In the Eclipse 2.x runtime, the plug-in object has a number of roles and responsibilities:</p>
-<ul>
-  <li>Lifecycle - The <tt>Plugin</tt> class implements method such as startup()
-    and shutdown(). The runtime uses these methods to signal the plug-in that
-    someone is interested in the function it provides. In response, plug-ins
-    typically do a combination of:
-      <ul>
-        <li>Registration - Hook various event mechanisms (e.g., register listeners)
-          and otherwise make their presence known in the system (e.g., start
-          needed threads). </li>
-        <li>Initialization - Initialize or prime their data structures and load
-          models so they are ready for use.</li>
-      </ul>
-  </li>
-  <li>Plug-in global data/function - While never explicitly put forth for this
-    role, in common practice plug-in classes have become a place to hang data
-    and function which is effectively global to the plug-in itself. In some cases
-    this data/function is API in others it is internal. For example, the UI plug-in
-    exposes as API methods such as <tt>getDialogSettings()</tt> and <tt>getWorkbench()</tt>.</li>
-  <li>Context - The standard <tt>Plugin</tt> class provides access to various
-    runtime-provided function such as preferences and logging.</li>
-</ul>
-<p>In the Eclipse 3.0 runtime picture, these roles and responsibilities are factored
-  into distinct objects.</p>
-<dl>
-    <dt><b>Bundle</b></dt>
-    <dd>Bundles are the OSGi unit of modularity. There is one classloader per
-      bundle and Eclipse-like inter-bundle class loading dependency graphs can
-      be constructed. Bundles have lifecycle for start and stop and the OSGi
-      framework broadcasts bundle related events (e.g., install, resolve, start,
-      stop, uninstall, ...) to interested parties. Unlike the Eclipse <tt>Plugin</tt> class,
-      the OSGi <tt>Bundle</tt> class is not extensible. That is, developers do
-      not have the opportunity to define their own bundle class.</dd>
-    <dt><b>BundleActivator</b></dt>
-    <dd>BundleActivator is an interface defined by the OSGi framework. Each bundle
-      can define a bundle activator class much like a plug-in can define its <tt>Plugin</tt> class.
-      The specified class is instantiated by the framework and used to implement
-      the <tt>start()</tt> and <tt>stop()</tt> lifecycle
-      processing. There is a major difference however in the nature of this lifecycle
-      processing. In Eclipse it is common (though not recommended) to have the <tt>Plugin</tt> classes
-      do both initialization and registration. In OSGi activators must only do
-      registration. Doing large amounts of initialization (or any other work)
-      in <tt>BundleActivator.start()</tt> threatens the liveness of the system.</dd>
-    <dt><b>BundleContext</b></dt>
-    <dd>BundleContexts are the OSGi mechanism for exposing general system function
-      to individual bundles. Each bundle has a unique and <strong>private</strong> instance of
-      BundleContext which they can use to access system function (e.g., getBundles()
-      to discover all bundles in the system).</dd>
-    <dt><b>Plugin</b></dt>
-    <dd>The new <tt>Plugin</tt> is very much like the original Eclipse <tt>Plugin</tt> class
-      with the following exceptions: <tt>Plugin</tt> objects are no longer required
-      or managed by the runtime and various methods have been deprecated. It
-      is essentially a convenience mechanism providing a host of useful function
-      and mechanisms but is no longer absolutely required. Much of the function
-      provided there is also available on the <tt>Platform</tt> class in the
-      runtime.
-            <p><tt>Plugin</tt> also implements <tt>BundleActivator</tt>. This
-              recognizes the convenience of having one central object representing
-              the lifecycle and semantic of a plug-in. Note that this does not
-              however sanction the eager initialization of data structures that
-              is common in plug-ins today. We cannot stress enough that plug-ins
-              can be activated because a somewhat peripheral class was referenced
-              during verification of a class in some other plug-in. That is,
-              just because your plug-in has been activated does not necessarily
-              mean that its function is needed. Note also that you are free to
-              define a different <tt>BundleActivator</tt> class or not have a
-              bundle activator at all.</p>
-    </dd>
-</dl>
-<p>The steps required to port a 2.x <tt>Plugin</tt> class to Eclipse 3.0 depends
-  on what the class is doing. As outlined above, most startup lifecycle work
-  falls into one of the following categories:</p>
-<dl>
-    <dt><b>Initialization</b></dt>
-    <dd>Datastructure and model initialization is quite often done in <tt>Plugin.startup()</tt>.
-      The natural/obvious mapping would be to do this work in a <tt>BundleActivator.start()</tt>,
-      that is to leave the function on <tt>Plugin</tt>. <b> This is strongly
-      discouraged.</b> As with 2.x plug-ins, 3.0 plug-ins/bundles may be started
-      for many different reasons in many different circumstances. <br>
-      An actual example from Eclipse 2.0 days illuminates this case. There was
-      a plug-in which initialized a large model requiring the loading of some
-      11MB of <i>code</i> and many megabytes of data. There were quite common
-      usecases where this plug-in was activated to discover if the project icon
-      presented in the navigator should be decorated with a particular markup.
-      This test did not require any of the initialization done in <tt>startup()</tt> but
-      yet all users, in all usecases had to pay the memory and time penalty for
-      this eager initialization.<br>
-      The alternative approach is to do such initialization in a classic lazy
-      style. For example, rather than having models initialized when the plug-in/bundle
-      is activated, do it when they are actually needed (e.g., in a centralized
-      model accessor method). For many usecases this will amount to nearly the
-      same point in time but for other scenarios this approach will defer initialization
-      (perhaps indefinitely). We recommend taking time while porting 2.1 plug-ins
-      to reconsider the initialization strategy used. </dd>
-    <dt><b>Registration</b></dt>
-    <dd>Plug-in startup is a convenient time to register listeners, services
-      etc. and start background processing threads (e.g., listening on a socket). <tt>Plugin.start()</tt> may
-      be a reasonable place to do this work. It may also make sense to defer
-      until some other trigger (e.g., the use of a particular function or data
-      element).</dd>
-    <dt><b>Plug-in global data</b></dt>
-    <dd>Your <tt>Plugin</tt> class can continue to play this role. The main issue
-      is that <tt>Plugin</tt> objects are no longer globally accessible via a
-      system-managed list. In Eclipse 2.x you could discover any plug-in's <tt>Plugin</tt> object
-      via the plug-in registry. This is no longer possible. In most circumstances
-      this type of access is not required. <tt>Plugins</tt> accessed via the
-      registry are more typically used as generic <tt>Plugins</tt> rather than
-      calling domain-specific methods. The equivalent level of capability can
-      be had by accessing and manipulating the corresponding Bundle objects.</dd>
-</dl>
-<h4><a name="registries"></a>Registries and the plug-in model</h4>
-<p>In the new runtime there is a separation between the information and structures
-  needed to execute a plug-in and that related to a plug-in's extensions and
-  extension points. The former is defined and managed by the OSGi framework specification.
-  The latter are Eclipse-specific concepts and are added by they Eclipse runtime
-  code. Accordingly, the original plug-in registy and related objects have been
-  split into OSGi <i>bundles</i> and the Eclipse <i>extension registry</i>. </p>
-<p>The parts of <tt>IPluginRegistry</tt> dealing with execution specification
-  (e.g., <tt>IPluginDescriptor, ILibrary</tt>, <tt>IPrequisite</tt>) have been
-  deprecated and the remaining parts related to extensions and extension point
-  have been moved to <tt>IExtensionRegistry</tt>. Further, the so-called model
-  objects related to the plug-in registry as a whole are now deprecated. These
-  types were presented and instantiated by the runtime primarily to support tooling
-  such as PDE. Unfortunately, it was frequently the case that the level of information
-  needed exceeded the runtime's capabilities or interests (e.g., remembering
-  line numbers for plugin.xml elements) and in the end, the potential consumers
-  of the runtime's information had to maintain their own structures anyway.</p>
-<p>In the new runtime we have re-evaluated the facilities provided by the runtime
-  and now provide only those which are either essential for runtime execution
-  or are extraordinarily difficult for others to do. As mentioned above, the
-  plug-in registry model objects have been deprecated as has the plug-in parsing
-  API. The new extensions registry maintains the essential extension-related
-  information. A new <i>state</i> (see <tt>org.eclipse.osgi.service.resolver.State</tt> and
-  friends) structure represents and allows the manipulation of the essential
-  execution-related information. </p>
-<h3>NL fragment structure</h3>
-<p>In Eclipse 3.0 the NL fragment structure has been updated to be more consistent.
-  Previously the translations for files like plugin.properties were assumed to
-  be inside of JARs supplied by fragments. Since the original files are found
-  in the root of the relevant host plug-in, a more consistent location would
-  have the translated files located in the root of the NL fragments. For example, </p>
-<pre>  org.eclipse.ui.workbench.nl/
-     fragment.xml
-     plugin_fr.properties
-     plugin_pt_BR.properties
-     ...
-     nl1.jar</pre>
-<p>Note here that the file nl1.jar previously would have contained the translations
-  for plugin.properties. These files are now at the root of the fragment and
-  the JAR contains translations of any translatable resources (i.e., files loaded
-  via the classloader) in the host plug-in. </p>
-<p>Of course, the Eclipse 2.1 NL fragment structure is still supported for 2.1
-  host plug-ins running in Eclipse 3.0. You cannot however use a 2.1 NL fragment
-  on a 3.0 plug-in. The fragment must be updated to the new structure.</p>
-<h3>API changes overview</h3>
-<h4>org.eclipse.core.boot (package org.eclipse.core.boot)</h4>
-<p>The entire org.eclipse.core.boot package has been deprecated. BootLoader has
-  been merged with <tt>org.eclipse.core.runtime.Platform</tt> since
-  it no longer made sense to have a split between boot and runtime. Note that
-  in fact, the org.eclipse.core.boot plug-in has been broken up and all its code
-moved to either the new runtime or the compatibility layer. </p>
-<p><tt>IPlatformConfiguration</tt> has
-    always been a type defined by and for the Eclipse Install/Update component.
-    With the reorganization of the runtime
-    we are able to repatriate this type to its rightful home. This class remains
-    largely unchanged and has been repackaged as <tt>org.eclipse.update.configurator.IPlatformConfiguration</tt>.
-</p>
-<p>IPlatformRunnable has been moved to org.eclipse.core.runtime.IPlatformRunnable. </p>
-<h4>IExtension and IExtensionPoint (package org.eclipse.core.runtime)<br>
-</h4>
-<p>The <code>getDeclaringPlugin()</code> method (on both classes) gives an upward link
-    to the plug-in which declares the extension or extension-point (respectively).
-    The
-          new registry model separates the execution aspects of plug-ins from
-          the extension/extension-point aspects and no longer contains <tt>IPluginDescriptors</tt>.
-          Users of this API should consider the new method <tt>getParentIdentifier()</tt> found
-  on both <tt>IExtension</tt> and <tt>IExtensionPoint</tt>. </p>
-<h4>ILibrary, IPluginDescriptor, IPluginRegistry and IPrerequisite (package org.eclipse.core.runtime)</h4>
-<p> In the original runtime, the plug-in registry maintained a complete picture
-  of the runtime configuration. In Eclipse 3.0 this picture is split over the
-  OSGi framework and the extension registry.  As such, these classes have been
-  deprecated. The deprecation notices contain details of how you should update
-  your code.</p>
-<h4>Platform and Plugin (package org.eclipse.core.runtime)</h4>
-<p>In the new runtime, <tt>Plugin</tt> objects are no longer managed
-by the runtime and so cannot be accessed generically via the Platform. Similarly,
-  the plug-in registry no longer exists or gives access to plug-in descriptors.
-  There are however suitable replacement methods available and detailed in the
-Javadoc of the deprecated methods in these classes.</p>
-<h4>org.eclipse.core.runtime.model (package org.eclipse.core.runtime.model)</h4>
-<p>All types in this package are now deprecated. See the discussion on <a href="#registries">registries</a> for
-  more information.</p>
-<h4>IWorkspaceRunnable and IWorkspace.run (package org.eclipse.core.resources)</h4>
-<p>Clients of the <tt>IWorkspace.run(IWorkspaceRunnable,IProgressMonitor)</tt>
-method should revisit their uses of this method and consider using the richer
-method <tt>IWorkspace.run(IWorkspaceRunnable,ISchedulingRule,int,IProgressMonitor)</tt>.
-The old <tt>IWorkspace.run</tt> method acquires a lock on the entire workspace
-for the duration of the <tt>IWorkspaceRunnable</tt>. This means that an
-operation done with this method will never be able to run concurrently with
-other operations that are changing the workspace. In Eclipse 3.0, many
-long-running operations have been moved into background threads, so the
-likelihood of conflicts between operations is greatly increased. If a modal
-foreground operation is blocked by a long running background operation, the UI
-becomes blocked until the background operation completes, or until one of the
-operations is canceled.</p>
-<p>The suggested solution is to switch all references to old <tt>IWorkspace.run</tt>
-to use the new method with a scheduling rule parameter. The scheduling rule
-should be the most fine-grained rule that encompasses the rules for all changes by that
-operation. If the operation tries to modify resources outside of the scope
-of the scheduling rule, a runtime exception will occur. The precise scheduling rule
-required by a given workspace operation is not specified, and may change depending
-on the installed repository provider on a given project. The factory 
-<code>IResourceRuleFactory</code> should be used to obtain the scheduling
-rule for a resource-changing operation. If desired, a <tt>MultiRule</tt> can be used 
-to specify multiple resource rules, and the <tt>MultiRule.combine</tt> convenience 
-method can be used to combine rules from various resource-changing operations.</p>
-<p>
-If no locking is required, a scheduling rule of <tt>null</tt> can be used. This will
-allow the runnable to modify all resources in the workspace, but will not prevent other
-threads from also modifying the workspace concurrently. For simple changes to 
-the workspace this is often the easiest and most concurrency-friendly solution.
-</p>
-<h4>IWorkbenchPage (package org.eclipse.ui)</h4>
-<ul>
-  <li>The constant EDITOR_ID_ATTR is now deprecated. This is an IMarker
-    attribute name that specifies the preferred editor id to open the IMarker
-    resource with. This constant in now on org.eclipse.ui.ide.IDE class.</li>
-</ul>
-<h4>IEditorDescriptor (package org.eclipse.ui)</h4>
-<ul>
-  <li>There are new API methods to determine whether the editor will open
-    internally to the workbench page (isInternal), in-place to the workbench
-    window (isOpenInPlace), or externally to the workbench (isExternal). While
-    this is not a breaking change, it is a good opportunity for clients that are
-    illegally down-casting IEditorDescriptor to
-    org.eclipse.ui.internal.model.EditorDescriptor to call isInternal to bring
-    there code back into line.</li>
-</ul>
-<h4>ISharedImages (package org.eclipse.ui)</h4>
-<ul>
-  <li>The following fields were removed (deprecated) from this interface because
-    they were IDE-specific:
-    <ul>
-      <li>String IMG_OBJ_PROJECT</li>
-      <li>String IMG_OBJ_PROJECT_CLOSED</li>
-      <li>String IMG_OPEN_MARKER</li>
-      <li>String IMG_OBJS_TASK_TSK</li>
-      <li>String IMG_OBJS_BKMRK_TSK</li>
-    </ul>
-  </li>
-  <li>Existing clients should instead use the fields of the same names declared
-    on IDE.SharedImages in the org.eclipse.ui.ide package of the
-    org.eclipse.ui.ide plug-in.</li>
-</ul>
-<h4>IWorkbenchActionConstants (package org.eclipse.ui)</h4>
-<ul>
-  <li>The following fields were removed (deprecated) from this interface; they
-    are subsumed by the new ActionFactory class:
-    <ul>
-      <li>String ABOUT</li>
-      <li>String BACK</li>
-      <li>String CLOSE</li>
-      <li>String CLOSE_ALL</li>
-      <li>String COPY</li>
-      <li>String CUT</li>
-      <li>String DELETE</li>
-      <li>String EXPORT</li>
-      <li>String FIND</li>
-      <li>String FORWARD</li>
-      <li>String IMPORT</li>
-      <li>String MOVE</li>
-      <li>String NEW</li>
-      <li>String NEXT</li>
-      <li>String PASTE</li>
-      <li>String PREVIOUS</li>
-      <li>String PRINT</li>
-      <li>String PROPERTIES</li>
-      <li>String QUIT</li>
-      <li>String REDO</li>
-      <li>String REFRESH</li>
-      <li>String RENAME</li>
-      <li>String REVERT</li>
-      <li>String SAVE</li>
-      <li>String SAVE_ALL</li>
-      <li>String SAVE_AS</li>
-      <li>String SELECT_ALL</li>
-      <li>String UNDO</li>
-      <li>String UP</li>
-    </ul>
-  </li>
-  <li>Clients should instead call getID() on the fields of the same names
-    declared on ActionFactory in the org.eclipse.ui.actions package (org.eclipse.ui
-    plug-in). For example, change IWorkbenchActionConstants.CUT to
-    ActionFactory.CUT.getId().</li>
-  <li>The following fields were removed (deprecated) from this interface because
-    they were IDE-specific.
-    <ul>
-      <li>String ADD_TASK</li>
-      <li>String BOOKMARK</li>
-      <li>String BUILD</li>
-      <li>String BUILD_PROJECT</li>
-      <li>String CLOSE_PROJECT</li>
-      <li>String FIND</li>
-      <li>String OPEN_PROJECT</li>
-      <li>String REBUILD_ALL</li>
-      <li>String REBUILD_PROJECT</li>
-    </ul>
-  </li>
-  <li>Clients should instead call getID() on the fields of the same names
-    declared on IDEActionFactory in the org.eclipse.ui.ide package (org.eclipse.ui.ide
-    plug-in). For example, change IWorkbenchActionConstants.BUILD to
-    IDEActionFactory.BUILD.getId().</li>
-</ul>
-<h4>IWorkbenchPreferenceConstants (package org.eclipse.ui)</h4>
-<ul>
-  <li>The following fields were removed (deprecated) from this interface because
-    they were IDE-specific:
-    <ul>
-      <li>String PROJECT_OPEN_NEW_PERSPECTIVE</li>
-    </ul>
-  </li>
-  <li>Clients should instead use the fields of the same names declared on
-    IDE.Preferences in the org.eclipse.ui.ide package.</li>
-</ul>
-<h4>IExportWizard (package org.eclipse.ui)</h4>
-<ul>
-  <li>Prior to 3.0, the selection passed to IWorkbenchWizard.init(IWorkbench,
-    IStructuredSelection) for an export wizard was preprocessed. If any of the
-    selections were IResources, or adaptable to IResource, then the selection
-    consisted only of these resources. In 3.0, the generic export wizard does
-    not do any preprocessing.&nbsp;</li>
-  <li>The selection passed to the wizard is generally used to prime the
-    particular wizard page with contextually appropriate values.</li>
-  <li>Client that implement IExportWizard and requires this resource-specific
-    selection transformation should add the following to their init(IWorkbench,
-    IStructuredSelection selection) method to computer <code>filteredSelection</code>
-    from <code>selection</code>:
-    <ul>
-      <li><code>IStructuredSelection filteredSelection = selection;<br>
-        List selectedResources = IDE.computeSelectedResources(currentSelection);<br>
-        if (!selectedResources.isEmpty()) {<br>
-        &nbsp;&nbsp;&nbsp; filteredSelection = new
-        StructuredSelection(selectedResources);<br>
-        }</code></li>
-    </ul>
-  </li>
-</ul>
-<h4>IImportWizard (package org.eclipse.ui)</h4>
-<ul>
-  <li>Prior to 3.0, the selection passed to IWorkbenchWizard.init(IWorkbench,
-    IStructuredSelection) for an import wizard was preprocessed. If any of the
-    selections were IResources, or adaptable to IResource, then the selection
-    consisted only of these resources. In 3.0, the generic import wizard does
-    not do any preprocessing.&nbsp;</li>
-  <li>The selection passed to the wizard is generally used to prime the
-    particular wizard page with contextually appropriate values.</li>
-  <li>Client that implement IImportWizard and requires this resource-specific
-    selection transformation should add the following to their init(IWorkbench,
-    IStructuredSelection selection) method to compute a filtered selection from
-    the selection passed in:
-    <ul>
-      <li><code>IStructuredSelection filteredSelection = selection;<br>
-        List selectedResources = IDE.computeSelectedResources(currentSelection);<br>
-        if (!selectedResources.isEmpty()) {<br>
-        &nbsp;&nbsp;&nbsp; filteredSelection = new
-        StructuredSelection(selectedResources);<br>
-        }</code></li>
-    </ul>
-  </li>
-</ul>
-<h4>INewWizard (package org.eclipse.ui)</h4>
-<ul>
-  <li>Prior to 3.0, the selection passed to IWorkbenchWizard.init(IWorkbench,
-    IStructuredSelection) for a new wizard was preprocessed. If there was no
-    structured selection at the time the wizard was invoked, but the active
-    workbench window had an active editor open on an IFile, then the selection
-    passed in would consist of that IFile. In 3.0, the generic new wizard does
-    not do any preprocessing, and an empty selection will be passed when there
-    is no structured selection.</li>
-  <li>The selection passed to the wizard is generally used to prime the
-    particular wizard page with contextually appropriate values.</li>
-  <li>Client that implement INewWizard and requires this capability should add
-    the following to their init(IWorkbench, IStructuredSelection selection)
-    method to compute a selection from the active editor's input:
-    <pre>if (selection.isEmpty()) {
-   IWorkbenchWindow window = PlatformUI.getWorkbench().getActiveWorkbenchWindow();
-   if (window != null) {
-      IWorkbenchPart part = window.getPartService().getActivePart();
-      if (part instanceof IEditorPart) {
-         IEditorInput input = ((IEditorPart) part).getEditorInput();
-         if (input instanceof IFileEditorInput) {
-            selection = new StructuredSelection(((IFileEditorInput) input).getFile());
-         }
-      }		
-  }
-}</pre>
-  </li>
-</ul>
-<h4>WorkbenchHelp (package org.eclipse.ui.help)</h4>
-<ul>
-  <li>The following WorkbenchHelp method was removed (deprecated) from this
-    class because its result (IHelp) was removed (deprecated):
-    <ul>
-      <li>public static IHelp getHelpSupport()</li>
-    </ul>
-  </li>
-  <li>Clients that called this method to obtain an IHelp should instead call the
-    static methods on HelpSystem or WorkbenchHelp.</li>
-</ul>
-<h4>IHelp (package org.eclipse.help)</h4>
-<ul>
-  <li>This interface has been removed (deprecated). WorkbenchHelp.getHelpsupport()
-    was the only way to get hold of an IHelp object. This method has also been
-    removed (deprecated).</li>
-  <li>The following IHelp methods now appear as static methods on a new
-    HelpSystem class in the same package:
-    <ul>
-      <li>public IToc[] getTocs()</li>
-      <li>public IContext getContext(String contextId)</li>
-    </ul>
-  </li>
-  <li>The rest of the IHelp methods now appear as static method on WorkbenchHelp.</li>
-  <li>This interface was formerly mentioned in the contract for the
-    org.eclipse.help.support extension point. This extension point has been
-    renamed &quot;org.eclipse.ui.helpSupport&quot;, and the contract simplified
-    so that the implementer only needs supply the display methods. For these
-    purposes, IHelp has been replaced by AbstractHelpUI (in the
-    org.eclipse.ui.help package).</li>
-  <li>There should be no clients implementing this interface beyond the Platform
-    which supplied the sole implementation of this interface.</li>
-</ul>
-<h4>ITextEditorActionConstants (package org.eclipse.ui.texteditor)</h4>
-<ul>
-  <li>This interface additionally includes newly defined constants that redefine
-    deprecated constants inherited from org.eclipse.ui.IWorkbenchActionConstants.
-    This change allows clients to free their code from deprecation warnings. The
-    constants ADD_TASK and BOOKMARK have not been redefined as they are IDE
-    specific. When using these two constants in your code, please follow the
-    instructions given in the deprecation message.</li>
-</ul>
-<h4>IAbstractTextEditorHelpContextIds (package org.eclipse.ui.texteditor)</h4>
-<ul>
-  <li>BOOKMARK_ACTION and ADD_TASK_ACTION have been deprecated because they are
-    IDE specific. Use the constants defined in
-    org.eclipse.ui.editors.text.ITextEditorHelpContextIds instead.</li>
-</ul>
-<h4>BasicTextEditorActionContributor (package org.eclipse.ui.texteditor)</h4>
-<ul>
-  <li>BasicTextEditorActionContributor no longer assigns any editor action as
-    global action for org.eclipse.ui.IWorkbenchActionConstants.ADD_TASK and
-    org.eclipse.ui.IWorkbenchActionConstants.BOOKMARK because these actions are
-    IDE specific. This is now done by the
-    org.eclipse.ui.editors.text.TextEditorActionContributor. If your editors are
-    not configured to used TextEditorActionContributor but uses a contributor
-    that is a subclass of BasicTextEditorActionContributor, this contributor has
-    to be extended to also assign global action handlers for ADD_TASK and
-    BOOKMARK. This can be done by adding the following lines to the
-    setActiveEditor method of the editor action contributor:</li>
-  <li>
-    <pre> IActionBars actionBars= getActionBars();
- if (actionBars != null) {
-   actionBars.setGlobalActionHandler(IDEActionFactory.ADD_TASK.getId(), getAction(textEditor, IDEActionFactory.ADD_TASK.getId()));
-   actionBars.setGlobalActionHandler(IDEActionFactory.BOOKMARK.getId(), getAction(textEditor, IDEActionFactory.BOOKMARK.getId()));
- }</pre>
-  </li>
-</ul>
-<h4>TextEditorActionContributor (package org.eclipse.ui.editors.text)</h4>
-<ul>
-  <li>TextEditorActionContributor assigns global action handlers for
-    IWorkbenchActionConstants.ADD_TASK (now IDEActionFactory.ADD_TASK.getId())
-    and IWorkbenchActionConstants.BOOKMARK (now IDEActionFactory.BOOKMARK.getId()).
-    These action handlers have previously been registered by
-    BasicTextEditorActionContributor. See migration notes for
-    BasicTextEditorActionContributor.</li>
-</ul>
-<h4>annotationTypes extension point (plug-in org.eclipse.ui.editors)</h4>
-<p>
-There is now the explicit notion of an annotation type. See Annotation.getType() and Annotation.setType().
-The type of an annotation can change over it's lifetime. A new extension point has been added for the declaration
-of annotation types: "org.eclipse.ui.editors.annotationTypes". An annotation type has a name and can be declared 
-as being a subtype of another declared annotation type. An annotation type declaration may also use the attributes 
-"markerType" and "markerSeverity" in order to specify that markers of a given type and a given severity should be 
-represented in text editors as annotations of a particular annotation type. The attributes "markerType" and 
-"markerSeverity" in the "org.eclipse.ui.editors.markerAnnotationSpecification" should no longer be used. Marker 
-annotation specifications are thus becoming independent from markers and the name thus misleading. However, the 
-name is kept in order to ensure backward compatibility.
-</p><p>
-Instances of subclasses of AbstractMarkerAnnotationModel automatically detect and set the correct  annotation 
-types for annotations they create from markers. In order to programmatically retrieve the annotation type for 
-a given marker or a given pair of markerType and markerSeverity use org.eclipse.ui.texteditor.AnnotationTypeLookup.
-</p><p>
-Access to the hierarchy of annotation types is provided by IAnnotationAccessExtension. For a given annotation type 
-you can get the chain of super types and check whether an annotation type is a subtype of another annotation type.
-DefaultMarkerAnnotationAccess implements this interface.
-</p>
-<h4>markerAnnotationSpecification extension point (plug-in org.eclipse.ui.editors)</h4>
-<p>
-The annotation type is the key with which to find the associated marker annotation specification. As annotation 
-types can extend other annotation types, there is an implicit relation between marker annotation specifications 
-as well. Therefore a marker annotation specification for a given annotation type is completed by the marker 
-annotation specifications given for the super types of the given annotation type. Therefore, marker annotation 
-specification do not have to be complete as this was required before. Marker annotation specifications are 
-retrieved by AnnotationPreferences. By using org.eclipse.ui.texteditor.AnnotationPreferenceLookup, you can retrieve 
-an annotation preference for a given annotation type that transparently performs the completion of the preference 
-along the annotation super type chain.
-</p><p>
-Marker annotation specification has been extended with three additional attributes in order to allow the definition 
-of custom appearances of a given annotation type in the vertical ruler. These attributes are: "icon", "symbolicIcon", 
-and "annotationImageProvider". The value for "icon" is the path to a file containing the icon image. The value of 
-"symbolicIcon" can be one of "error", "warning", "info", "task", "bookmark". The attribute "symbolicIcon" is used 
-to tell the platform that annotation should be depicted with the same images that are used by the platform to 
-present errors, warnings, infos, tasks, and bookmarks respectively. The value of "annotationImageProvider" is a 
-class implementing org.eclipse.ui.texteditor.IAnnotationImageProvider that allows for a full custom annotation 
-presentation.
-</p><p>
-The vertical ruler uses it's associated IAnnotationAccess/IAnnotationAccessExtension to draw annotations. 
-The vertical ruler does not call Annotation.paint any longer. In general, Annotations are no longer supposed 
-to draw themselves. The "paint" and "getLayer" methods have been deprecated in order to make annotation eventually 
-UI independent. DefaultMarkerAnnotationAccess serves as default implementation of IAnnotationAccess/IAnnotationAccessExtension. 
-DefaultMarkerAnnotationAccess implements the following strategy for painting annotations: If an annotation implements 
-IAnnotationPresentation, IAnnotationPresentation.paint is called. If not, the annotation image provider is looked up 
-in the annotation preference. The annotation image provider is only available if specified and if the plug-in defining 
-the enclosing marker annotation specification has already been loaded. If there is an annotation image provider, the 
-call is forwarded to it. If not, the specified "icon" is looked up. "symbolicIcon" is used as the final fallback. For 
-drawing annotations, the annotation presentation layer is relevant. DefaultMarkerAnnotationAccess looks up the presentation 
-layer using the following strategy: If the annotation preference specifies a presentation layer, the specified layer is 
-used. If there is no layer and the annotation implements IAnnotationPresentation, IAnnotationPresentation.getLayer is used 
-otherwise the default presentation layer (which is 0) is returned.
-</p>
-<h4>Migration to annotationTypes extension point (plug-in org.eclipse.ui.editors)</h4>
-<p>
-The following annotation types are declared by the org.eclipse.ui.editors plug-in:
-</p>
-<pre>
-   &lt;extension point="org.eclipse.ui.editors.annotationTypes"&gt;
-      &lt;type
-         name="org.eclipse.ui.workbench.texteditor.error"
-         markerType="org.eclipse.core.resources.problemmarker"
-         markerSeverity="2"&gt;
-      &lt;/type&gt;
-      &lt;type
-         name="org.eclipse.ui.workbench.texteditor.warning"
-         markerType="org.eclipse.core.resources.problemmarker"
-         markerSeverity="1"&gt;
-      &lt;/type&gt;
-      &lt;type
-         name="org.eclipse.ui.workbench.texteditor.info"
-         markerType="org.eclipse.core.resources.problemmarker"
-         markerSeverity="0"&gt;
-      &lt;/type&gt;
-      &lt;type
-         name="org.eclipse.ui.workbench.texteditor.task"
-         markerType="org.eclipse.core.resources.taskmarker"&gt;
-      &lt;/type&gt;
-      &lt;type
-         name="org.eclipse.ui.workbench.texteditor.bookmark"
-         markerType="org.eclipse.core.resources.bookmark"&gt;
-      &lt;/type&gt;
-   &lt;/extension&gt;
-</pre>
-<p>
-The defined markerAnnotationSpecification extension no longer provide "markerType" and "markerSeverity" 
-attributes. They define the "symbolicIcon" attribute with the according value. Thus, MarkerAnnotation.paint 
-and MarkerAnnotation.getLayer are not called any longer, i.e. overriding these methods does not have 
-any effect. Affected clients should implement IAnnotationPresentation.
-</p>
-<h4>ILaunchConfigurationType (package org.eclipse.debug.core)</h4>
-<p>With the introduction of extensible launch modes in 3.0, more than one launch
-delegate can exist for a launch configuration type. Releases prior to 3.0 only
-supported one launch delegate per launch configuration type. The method <code>ILaunchConfigurationType.getDelegate()</code>
-is now deprecated. The method <code>getDelegate(String mode)</code> should be
-used in its place to retrieve the launch delegate for a specific launch mode.
-The deprecated method has been changed to return the launch delegate for the <code>run</code>
-mode.</p>
-<h4>ILaunchConfigurationTab and ILaunchConfigurationTabGroup (package
-org.eclipse.debug.ui)</h4>
-<p>Launch tab groups and launch tabs are no longer notified when a launch
-completes. The method <code>launched(ILaunch)</code> in the interfaces <code>ILaunchConfigurationTab</code>
-and <code>ILaunchConfigurationTabGroup</code> has been deprecated and is no
-longer called. Relying on this method for launch function was always
-problematic, since tabs only exist when launching is performed from the launch
-dialog. Also, with the introduction of background launching, this method can no
-longer be called, as the launch dialog is be closed before the resulting launch
-object exists.</p>
-<h4>ILaunchConfigurationTab and AbstractLaunchConfigurationTab (package
-org.eclipse.debug.ui)</h4>
-<p>Two methods have been added to the <code>ILaunchConfigurationTab</code>
-interface - activated and deactivated. These new life cycle methods are called
-when a tab is entered and exited respectively. Existing implementations of <code>ILaunchConfigurationTab</code>
-that subclass the abstract class provided by the debug plug-in (<code>AbstractLaunchConfigurationTab</code>)
-are binary compatible since the methods are implemented in the abstract class.</p>
-<p>In prior releases, a tab was sent the message <code>initializeFrom</code>
-when it was activated, and <code>performApply</code> when it was deactivated. In
-this way, the launch configuration tab framework provided inter-tab
-communication via a launch configuration (by updating the configuration with
-current attribute values when a tab is exited, and updating the newly entered
-tab). However, since many tabs do not perform inter-tab communication, this can
-be inefficient. As well, there was no way to distinguish between a tab being
-activated, and a tab displaying a selected launch configuration for the first
-time. The newly added methods allow tabs to distinguish between activation and
-initialization, and deactivation and saving current values.</p>
-<p>The default implementation of <code>activated</code>, provided by the
-abstract tab, calls <code>initializeFrom</code>. And, the default implementation
-of <code>deactivated</code> calls <code>performApply</code>. Tabs wishing to
-take advantage of the new API should override these methods as required.
-Generally, for tabs that do not perform inter-tab communication, the recommended
-approach is to re-implement these methods to do nothing.</p>
-<h4>launchConfigurationTabGroup extension point Type (package
-org.eclipse.debug.ui)</h4>
-<p>In prior releases, perspective switching was specified on a launch
-configuration, via the launch configuration attributes <code>ATTR_TARGET_DEBUG_PERSPECTIVE</code>
-and <code>ATTR_TARGET_RUN_PERSPECTIVE</code>. With the addition of extensible
-launch modes in 3.0, this approach no longer scales. Perspective switching is
-now specified on launch configuration type basis, per launch mode that a launch
-configuration type supports. API has been added to <code>DebugUITools</code> to
-set and get the perspective associated with a launch configuration type for a
-specific launch mode.</p>
-<p>An additional, optional, <code>launchMode</code> element has been added to
-the <code>launchConfigurationTabGroup</code> extension point, allowing a
-contributed tab group to specify a default perspective for a launch
-configuration type and mode.</p>
-<p>From the Eclipse user interface, users can edit the perspective associated
-with a launch configuration type by opening the launch configuration dialog, and
-selecting a launch configuration type node in the tree (rather than an
-individual configuration). A tab is displayed allowing the user to set a
-perspective with each supported launch mode.</p>
-<h4>[JDT only] IVMRunner (package org.eclipse.jdt.launching)</h4>
-<p>Two methods have been added to the <code>VMRunnerConfiguration</code> class
-to support the setting and retrieving of environment variables. Implementors of <code>IVMRunner</code>
-should call <code>VMRunnerConfiguration.getEnvironment()</code> and pass that
-environment into the executed JVM. Clients who use <code>DebugPlugin.exec(String[]
-cmdLine, File workingDirectory)</code> can do this by calling <code>DebugPlugin.exec(String[]
-cmdLine, File workingDirectory, String[] envp)</code> instead. Simply passing in
-the result from <code>getEnvironment()</code> is sufficient.</p>
-<h4>[JDT only] VMRunnerConfiguration and Bootstrap Classes (package
-org.eclipse.jdt.launching)</h4>
-<p>In prior releases, the <code>VMRunnerConfiguration</code> had one attribute
-to describe a boot path. The attribute is a collection of <code>Strings</code>
-to be specified in the -<code>Xbootclasspath</code> argument. Three new
-attributes have been added to the VMRunnerConfiguration to support JVMs that
-allow for prepending and appending to the boot path. The new methods/attributes
-added are:</p>
-<ul>
-  <li><code>getPrependBootClassPath()</code> - returns a collection of entries
-    to be prepended to the boot path (the <code>-Xbootclasspath/p</code>
-    argument)</li>
-  <li><code>getMainBootClassPath()</code> - returns a collection of entries to
-    be placed on the boot path (the <code>-Xbootclasspath</code> argument)</li>
-  <li><code>getAppendBootClassPath()</code> - returns a collection of entries to
-    be appended to the boot path (the <code>-Xbootclasspath/a</code> argument)</li>
-</ul>
-<p>The old attribute,<code> getBootClassPath()</code>, still exists and contains
-a complete path equivalent to that of the three new attributes. However, <code>VMRunners</code>
-that support the new boot path options should take advantage of the new
-attributes.</p>
-<h4>[JDT only] Improved support for working copies (package org.eclipse.jdt.core)</h4>
-<p>The Java model working copy facility has been reworked in 3.0 to provide
-greatly increased functionality. Prior to 3.0, the Java model allowed creation
-of individual working copies of compilation units. Changes could be made to the
-working copy and later committed. There was support for limited analysis of a
-working copy in the context of the rest of the Java model. However, there was no
-way these these analyses could ever take into account more than one of the
-working copies at a time.</p>
-<p>The changes in 3.0 make it possible to create and manage sets of working
-copies of compilation units, and to perform analyses in the presence of all
-working copies in a set. For example, it is now possible for a client like JDT
-refactoring to create working copies for one or more compilation units that it
-is considering modifying and then to resolve type references between the working
-copies. Formerly this was only possible after the changes to the compilation
-unit working copies had been committed.</p>
-<p>The Java model API changes in 2 ways to add this improved support:</p>
-<p>(1) The functionality formerly found on <code>IWorkingCopy</code> and
-inherited by <code>ICompilationUnit</code> has been consolidated into <code>ICompilationUnit</code>.
-The <code>IWorkingCopy</code> interface was only used in this one place, and was
-gratuitously more general that in needed to be. This change simplifies the API. <code>IWorkingCopy</code>
-has been deprecated. Other places in the API where <code>IWorkingCopy</code> is
-used as a parameter or result type have been deprecated as well; the replacement
-API methods mention <code>ICompilationUnit</code> instead of <code>IWorkingCopy</code>.</p>
-<p>(2) The interface <code>IBufferFactory</code> has been replaced by <code>WorkingCopyOwner</code>.
-The improved support for working copies requires that there be an object to own
-the working copies. Although <code>IBufferFactory</code> is in the right place,
-the name does not adequately convey how the new working copy mechanism works. <code>WorkingCopyOwner</code>
-is much more suggestive. In addition, <code>WorkingCopyOwner</code> is declared
-as an abstract class, rather than as an interface, to allow the notion of
-working copy owner to evolve in the future. The one method on <code>IBufferFactory</code>
-moves to <code>WorkingCopyOwner</code> unaffected. <code>WorkingCopyOwner</code>
-does not implement <code>IBufferFactory</code> to make it clear that <code>IBufferFactory</code>
-is a thing of the past. <code>IBufferFactory</code> has been deprecated. Other
-places in the API where <code>IBufferFactory</code> appears as a parameter or
-result type have been deprecated as well; the replacement API methods mention <code>WorkingCopyOwner</code>
-instead of <code>IBufferFactory</code>.</p>
-<p>These changes do not break binary compatibility.</p>
-<p>When migrating, all references to the type <code>IWorkingCopy</code> should
-instead reference <code>ICompilationUnit</code>. The sole implementation of <code>IWorkingCopy</code>
-implements <code>ICompilationUnit</code> as well, meaning objects of type <code>IWorkingCopy</code>
-can be safely cast to <code>ICompilationUnit</code>.</p>
-<p>A class that implements <code>IBufferFactory</code> will need to replaced by
-a subclass of <code>WorkingCopyOwner</code>. Although <code>WorkingCopyOwner</code>
-does not implement <code>IBufferFactory</code> itself, it would be possible to
-declare the subclass of <code>WorkingCopyOwner</code> that implements <code>IBufferFactory</code>
-thereby creating a bridge between old and new (<code>IBufferFactory</code>
-declares <code>createBuffer(IOpenable)</code> whereas <code>WorkingCopyOwner</code>
-declares <code>createBuffer(ICompilationUnit)</code>; <code>ICompilationUnit</code>
-extends <code>IOpenable</code>).</p>
-<p>Because the changes involving <code>IWorkingCopy</code> and <code>IBufferFactory</code>
-are interwined, we recommend dealing with both at the same time. The details of
-the deprecations are as follows:</p>
-<ul>
-  <li><code>IWorkingCopy</code> (package <code>org.eclipse.jdt.core</code>)
-    <ul>
-      <li><code>public void commit(boolean, IProgressMonitor)</code> has been
-        deprecated.
-        <ul>
-          <li>The equivalent functionality is now provided on <code>ICompilationUnit</code>
-            directly:
-            <ul>
-              <li><code>public void commitWorkingCopy(boolean, IProgressMonitor)</code></li>
-            </ul>
-          </li>
-          <li>Rewrite <code>wc.commit(b,monitor)</code> as <code>((ICompilationUnit)
-            wc).commitWorkingCopy(b,monitor)</code></li>
-        </ul>
-      </li>
-      <li><code>public void destroy()</code> has been deprecated.
-        <ul>
-          <li>The equivalent functionality is now provided on <code>ICompilationUnit</code>
-            directly:
-            <ul>
-              <li><code>public void discardWorkingCopy(boolean, IProgressMonitor)</code></li>
-            </ul>
-          </li>
-          <li>Rewrite <code>wc.destroy()</code> as <code>((ICompilationUnit)
-            wc).discardWorkingCopy()</code></li>
-        </ul>
-      </li>
-      <li><code>public IJavaElement findSharedWorkingCopy(IBufferFactory)</code>
-        has been deprecated.
-        <ul>
-          <li>The equivalent functionality is now provided on <code>ICompilationUnit</code>
-            directly:
-            <ul>
-              <li><code>public ICompilationUnit findWorkingCopy(WorkingCopyOwner)</code></li>
-            </ul>
-          </li>
-          <li>Note: <code>WorkingCopyOwner</code> substitutes for <code>IBufferFactory.</code></li>
-        </ul>
-      </li>
-      <li><code>public IJavaElement getOriginal(IJavaElement)</code> has been
-        deprecated.
-        <ul>
-          <li>The equivalent functionality is now provided on <code>IJavaElement</code>:
-            <ul>
-              <li><code>public IJavaElement getPrimaryElement()</code></li>
-            </ul>
-          </li>
-        </ul>
-        <ul>
-          <li>Rewrite <code>wc.getOriginal(elt)</code> as <code>elt.getPrimaryElement()</code></li>
-          <li>Note: Unlike <code>IWorkingCopy.getOriginal</code>, <code>IJavaElement.getPrimaryElement</code>
-            does not return <code>null</code> if the receiver is not a working
-            copy.</li>
-        </ul>
-      </li>
-      <li><code>public IJavaElement getOriginalElement()</code> has been
-        deprecated.
-        <ul>
-          <li>The equivalent functionality is now provided on <code>ICompilationUnit</code>
-            directly:
-            <ul>
-              <li><code>public ICompilationUnit getPrimary()</code></li>
-            </ul>
-          </li>
-          <li>Rewrite <code>wc.getOriginalElement()</code> as <code>((ICompilationUnit)
-            wc).getPrimary()</code></li>
-          <li>Note: Unlike <code>IWorkingCopy.getOriginalElement</code>, <code>IWorkingCopy.getPrimary</code>
-            does not return <code>null</code> if the receiver is not a working
-            copy.</li>
-        </ul>
-      </li>
-      <li><code>public IJavaElement[] findElements(IJavaElement)</code> has been
-        deprecated.
-        <ul>
-          <li>The method is now declared on <code>ICompilationUnit</code>
-            directly.</li>
-          <li>Rewrite <code>wc.findElements(elts)</code> as <code>((ICompilationUnit)
-            wc).findElements(elts)</code></li>
-        </ul>
-      </li>
-      <li><code>public IType findPrimaryType()</code> has been deprecated.
-        <ul>
-          <li>The method is now declared on <code>ICompilationUnit</code>
-            directly.</li>
-          <li>Rewrite <code>wc.findPrimaryType()</code> as <code>((ICompilationUnit)
-            wc).findPrimaryType()</code></li>
-        </ul>
-      </li>
-      <li><code>public IJavaElement getSharedWorkingCopy(IProgressMonitor,
-        IBufferFactory, IProblemRequestor)</code> has been deprecated.
-        <ul>
-          <li>The equivalent functionality is now provided on <code>ICompilationUnit</code>
-            directly:
-            <ul>
-              <li><code>public ICompilationUnit getWorkingCopy(WorkingCopyOwner,
-                IProblemRequestor, IProgressMonitor)</code></li>
-            </ul>
-          </li>
-          <li>Note: the parameter order has changed, and <code>WorkingCopyOwner</code>
-            substitutes for <code>IBufferFactory.</code></li>
-        </ul>
-      </li>
-      <li><code>public IJavaElement getWorkingCopy()</code> has been deprecated.
-        <ul>
-          <li>The equivalent functionality is now provided on <code>ICompilationUnit</code>
-            directly:
-            <ul>
-              <li><code>public ICompilationUnit getWorkingCopy(IProgressMonitor)</code></li>
-            </ul>
-          </li>
-          <li>Rewrite <code>wc.getWorkingCopy() </code>as <code>((ICompilationUnit)
-            wc).getWorkingCopy(null)</code></li>
-        </ul>
-      </li>
-      <li><code>public IJavaElement getWorkingCopy(IProgressMonitor,
-        IBufferFactory, IProblemRequestor)</code> has been deprecated.
-        <ul>
-          <li>The equivalent functionality is now provided on <code>ICompilationUnit</code>
-            directly:
-            <ul>
-              <li><code>public ICompilationUnit getWorkingCopy(WorkingCopyOwner,
-                IProblemRequestor, IProgressMonitor)</code></li>
-            </ul>
-          </li>
-          <li>Note: the parameter order has changed, and <code>WorkingCopyOwner</code>
-            substitutes for <code>IBufferFactory.</code></li>
-        </ul>
-      </li>
-      <li><code>public boolean isBasedOn(IResource)</code> has been deprecated.
-        <ul>
-          <li>The equivalent functionality is now provided on <code>ICompilationUnit</code>
-            directly:
-            <ul>
-              <li><code>public boolean hasResourceChanged()</code></li>
-            </ul>
-          </li>
-          <li>Rewrite <code>wc.isBasesOn(res)</code> as <code>((ICompilationUnit)
-            wc).hasResourceChanged()</code></li>
-        </ul>
-      </li>
-      <li><code>public boolean isWorkingCopy()</code> has been deprecated.
-        <ul>
-          <li>The method is now declared on <code>ICompilationUnit</code>
-            directly.</li>
-          <li>Rewrite <code>wc.isWorkingCopy()</code> as <code>((ICompilationUnit)
-            wc).isWorkingCopy()</code></li>
-        </ul>
-      </li>
-      <li><code>public IMarker[]&nbsp; reconcile()</code> has been deprecated.
-        <ul>
-          <li>The equivalent functionality is now provided on <code>ICompilationUnit</code>
-            directly:
-            <ul>
-              <li><code>public void reconcile(boolean,IProgressMonitor)</code></li>
-            </ul>
-          </li>
-          <li>Rewrite <code>wc.reconcile()</code> as <code>((ICompilationUnit)
-            wc).reconcile(false, null)</code></li>
-          <li>Note: The former method always returned <code>null</code>; the
-            replacement method does not return a result.</li>
-        </ul>
-      </li>
-      <li><code>public void reconcile(boolean, IProgressMonitor)</code> has been
-        deprecated.
-        <ul>
-          <li>The method is now declared on <code>ICompilationUnit</code>
-            directly.</li>
-          <li>Rewrite <code>wc.reconcile(b,monitor)</code> as <code>((ICompilationUnit)
-            wc).reconcile(b.monitor)</code></li>
-        </ul>
-      </li>
-      <li><code>public void restore()</code> has been deprecated.
-        <ul>
-          <li>The method is now declared on <code>ICompilationUnit</code>
-            directly.</li>
-          <li>Rewrite <code>wc.restore()</code> as <code>((ICompilationUnit)
-            wc).restore()</code></li>
-        </ul>
-      </li>
-    </ul>
-  </li>
-  <li><code>IType</code> (package <code>org.eclipse.jdt.core</code>)
-    <ul>
-      <li><code>public ITypeHierarchy newSupertypeHierarchy(IWorkingCopy[],
-        IProgressMonitor)</code> has been deprecated.
-        <ul>
-          <li>The replacement method is provided on the same class:
-            <ul>
-              <li><code>public ITypeHierarchy newSupertypeHierarchy(c,
-                IProgressMonitor)</code></li>
-            </ul>
-          </li>
-          <li>Note: The Java language rules for array types preclude casting <code>IWorkingCopy[]</code>
-            to <code>ICompilationUnit[]</code>.</li>
-        </ul>
-      </li>
-      <li><code>public ITypeHierarchy newTypeHierarchy(IWorkingCopy[],
-        IProgressMonitor)</code> has been deprecated.
-        <ul>
-          <li>The replacement method is provided on the same class:
-            <ul>
-              <li><code>public ITypeHierarchy newTypeHierarchy(ICompilationUnit[],
-                IProgressMonitor)</code></li>
-            </ul>
-          </li>
-          <li>Note: The Java language rules for array types preclude casting <code>IWorkingCopy[]</code>
-            to <code>ICompilationUnit[]</code>.</li>
-        </ul>
-      </li>
-    </ul>
-  </li>
-  <li><code>IClassFile</code> (package <code>org.eclipse.jdt.core</code>)
-    <ul>
-      <li><code>public IJavaElement getWorkingCopy(IProgressMonitor,
-        IBufferFactory)</code> has been deprecated.
-        <ul>
-          <li>The replacement method is provided on the same class:
-            <ul>
-              <li><code>public ICompilationUnit getWorkingCopy(WorkingCopyOwner,
-                IProgressMonitor)</code></li>
-            </ul>
-          </li>
-          <li>Note: the parameter order has changed, and <code>WorkingCopyOwner</code>
-            substitutes for <code>IBufferFactory.</code></li>
-        </ul>
-      </li>
-    </ul>
-  </li>
-  <li><code>JavaCore</code> (package <code>org.eclipse.jdt.core</code>)
-    <ul>
-      <li><code>public IWorkingCopy[] getSharedWorkingCopies(IBufferFactory)</code>
-        has been deprecated.
-        <ul>
-          <li>The replacement method is provided on the same class:
-            <ul>
-              <li><code>public ICompilationUnit[]
-                getWorkingCopies(WorkingCopyOwner)</code></li>
-            </ul>
-          </li>
-          <li>Note: <code>WorkingCopyOwner</code> substitutes for <code>IBufferFactory.</code></li>
-          <li>Note: The Java language rules for array types preclude casting <code>ICompilationUnit[]</code>
-            to <code>IWorkingCopy[]</code>.</li>
-        </ul>
-      </li>
-    </ul>
-  </li>
-  <li><code>SearchEngine</code> (package <code>org.eclipse.jdt.core.search</code>)
-    <ul>
-      <li><code>public SearchEngine(IWorkingCopy[])</code> has been deprecated.
-        <ul>
-          <li>The replacement constructor is provided on the same class:
-            <ul>
-              <li><code>public SearchEngine(ICompilationUnit[])</code></li>
-            </ul>
-          </li>
-          <li>Note: The Java language rules for array types preclude casting <code>IWorkingCopy[]</code>
-            to <code>ICompilationUnit[]</code>.</li>
-        </ul>
-      </li>
-    </ul>
-  </li>
-</ul>
-<h4>Restructuring of org.eclipse.help plug-in</h4>
-<p>The org.eclipse.help plug-in, which used to hold APIs and extension points
-for contributing to and extending help system, as well as displaying help, now
-contains just APIs and extension points for contributing and accessing help
-resources. A portion of default help UI implementation contained in that plug-in
-has been moved to a new plug-in org.eclipse.help.base together with APIs for
-extending the implementation. The APIs and extension point for contributing Help
-UI and displaying help have been moved to org.eclipse.ui plug-in. This
-restructuring allows applications greater flexibility with regard to the help
-system; the new structure allows applications based on the generic workbench to
-provide their own Help UI and/or Help implementation, or to omit the help system
-entirely.</p>
-<p>Because the extension points and API packages affected are intended only for
-use by the help system itself, it is unlikely that existing plug-ins are
-affected by this change. They are included here only for the sake of
-completeness:</p>
-<ul>
-  <li>API packages org.eclipse.ui.help.browser and
-    org.eclipse.ui.help.standalone, formerly provided by the org.eclipse.help
-    plug-in, have been moved to the org.eclipse.help.base plug-in.</li>
-  <li>Extension points org.eclipse.help.browser, org.eclipse.help.luceneAnalyzer,
-    and org.eclipse.help.webapp, formerly defined by the org.eclipse.help
-    plug-in, have been moved to the org.eclipse.help.base plug-in, with a
-    corresponding change in extension point id.</li>
-  <li>Extension point org.eclipse.help.support has been replaced by the
-    org.eclipse.ui.helpSupport extension point. The contract for this extension
-    point changed as well (see entry for IHelp).</li>
-</ul>
-<h4>New Search UI API</h4>
-<P>A new API for implmenting custom searches has been added in 3.0. The original API is deprecated in 3.0 and we recommend that cllients port to the new API in the packages org.eclipse.search.ui and org.eclipse.search.ui.text.
-</P>
-<P>Clients will have to create implementations of <CODE>ISearchQuery</CODE>, <CODE>ISearchResult</CODE> and <CODE>ISearchResultPage</CODE>. The <CODE>ISearchResultPage</CODE> implementation must then be contributed into the new <CODE>org.eclipse.search.searchResultViewPages</CODE> extension point. </P>
-<P>Default implementations for <CODE>ISearchResult</CODE> and <CODE>ISearchResultPage</CODE> are provided in the package<CODE>
-org.eclipse.search.ui.text</CODE>.</P>
-
-<h4>null messages in MessageBox and DirectoryDialog (package
-org.eclipse.swt.widgets)</h4>
-<p>Prior to 3.0, calling SWT's DirectoryDialog.setMessage(String string) or
-MessageBox.setMessage(String string) with a null value for string would result
-in a dialog with no text in the title. This behavior was unspecified (passing
-null has never been permitted) and creates problems with getMessage which is not
-permitted to return null. In 3.0, passing null now results in an
-IllegalArgumentException exception being thrown, and the specifications have
-been changed to state this, bringing it into line with the method on their
-superclass Dialog.setMessage. If you use Dialog.setMessage, ensure that that the
-string passed in is never null. Simply pass an empty string if you want a dialog
-with no text in the title.</p>
-<h4>Improving modal progress feedback</h4>
-<p>Supporting concurrent operations requires more sophisticated ways to show
-modal progress. As part of the responsiveness effort additional progress support
-was implemented in the class IProgressService. The existing way to show progress
-with the ProgressMonitorDialog is still working. However, to improve the user
-experience we recommend migrating to the new IProgressService.</p>
-<p>The document <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-core-home/documents/plan_concurrency_modal_progress.html">Showing
-Modal Progress in Eclipse 3.0</a> describes how to migrate to the new
-IProgressService.</p>
-<h4>Debug Action Groups removed</h4>
-<p>The Debug Action Groups extension point
-(org.eclipse.debug.ui.debugActionGroups) has been removed. In Eclipse 3.0, the
-workbench introduced support for Activities via the
-org.eclipse.platform.ui.activities extension point. This support provides
-everything that Debug Action Groups provided and is also easier to use (it
-supports patterns instead of specifying all actions exhaustively) and has a
-programmatic API to support it. Failing to remove references to the old
-extension point won't cause any failures. References to the extension point will
-simply be ignored. Product vendors are encouraged to use the workbench
-Activities support to associate language-specific debugger actions with
-language-specific activities (for example, C++ debugging actions might be
-associated with an activity called &quot;Developing C++&quot;).</p>
-<h4>BreakpointManager can be disabled</h4>
-<p>IBreakpointManager now defines the methods setEnabled(boolean) and
-isEnabled(). When the breakpoint manager is disabled, debuggers should ignore
-all registered breakpoints. The debug platform also provides a new listener
-mechanism, IBreakpointManagerListener which allows clients to register with the
-breakpoint manager to be notified when its enablement changes. The Breakpoints
-view calls this API from a new toggle action that allows the user to &quot;Skip
-All Breakpoints.&quot; Debuggers which do not honor the breakpoint manager's
-enablement will thus appear somewhat broken if the user tries to use this
-feature.</p>
-<h4>[JDT only] Java search participants (package org.eclipse.jdt.core.search)</h4>
-<p>Languages close to Java (such as JSP, SQLJ, JWS, etc.) should be able to
-participate in Java searching. In particular, implementors of such languages
-should be able to:</p>
-<ul>
-  <li>index their source by converting it into Java equivalent source, and
-    feeding it to the Java indexer</li>
-  <li>index their source by parsing it themselves, but record Java index entries</li>
-  <li>locate matches in their source by converting it into Java equivalent
-    source, and feeding it to the Java match locator</li>
-  <li>locate matches in their source by matching themselves, and return Java
-    matches</li>
-</ul>
-<p>Such an implementor is called a search participant. It extends the
-SearchParticipant class. Search participants are passed to search queries (see
-SearchEngine.search(SearchPattern, SearchParticipant[], IJavaSearchScope,
-SearchRequestor, IProgressMonitor)).</p>
-<p>For either indexing or locating matches, a search participant needs to define
-a subclass of SearchDocument that can retrieve the contents of the document by
-overriding either getByteContents() or getCharContents(). An instance of this
-subclass is returned in getDocument(String).</p>
-<p>A search participant wishing to index some document will use
-SearchParticipant.scheduleDocumentIndexing(SearchDocument, IPath) to schedule
-the indexing of the given document in the given index. Once the document is
-ready to be indexed, the underlying framework calls
-SearchParticipant.indexDocument(SearchDocument, IPath). The search participant
-then gets the document's content, parses it and adds index entries using
-SearchDocument.addIndexEntry(char[], char[]).</p>
-<p>Once indexing is done, one can then query the indexes and locate matches
-using SearchEngine.search(SearchPattern, SearchParticipant[], IJavaSearchScope,
-SearchRequestor, IProgressMonitor). This first asks each search participant for
-the indexes needed by this query using
-SearchParticipant.selectIndexes(SearchPattern, IJavaSearchScope). For each index
-entry that matches the given pattern, a search document is created by asking the
-search participant (see getDocument(String)). All these documents are passed to
-the search participant so that it can locate matches using
-locateMatches(SearchDocument[], SearchPattern, IJavaSearchScope, SearchRequestor,
-IProgressMonitor). The search participant notifies the SearchRequestor of search
-matches using acceptSearchMatch(SearchMatch) and passing an instance of a
-subclass of SearchMatch.</p>
-<p>A search participant can delegate part of its work to the default Java search
-participant. An instance of this default participant is obtained using
-SearchEngine.getDefaultSearchParticipant(). For example when asked to locate
-matches, an SQLJ participant can create documents .java documents from its .sqlj
-documents and delegate the work to the default participant passing it the .java
-documents.</p>
-
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/3.1/faq.html b/bundles/org.eclipse.platform.doc.isv/porting/3.1/faq.html
deleted file mode 100644
index 9c1cf09..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/3.1/faq.html
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse 3.1 Plug-in Migration FAQ</title>
-</head>
-
-<body>
-
-<h1>Eclipse 3.1 Plug-in Migration FAQ</h1>
-<ol>
-  <li><a href="#IPreferenceStore">IPreferenceStore has more explicit API</a></li>
-  <li><a href="#IWorkbenchWindow">IWorkbenchWindow#getShell() has more explicit API</a></li>
-</ol>
-<h2> <a name="IPreferenceStore"></a>IPreferenceStore has more explicit API</h2>
-<p>Although the behavior of the IPreferenceStore provided by <code>AbstractUIPlugin#getPreferenceStore() 
-  </code>hasn't changed we have updated the specification of IPreferenceStore 
-  to explicitly define the behavior that we have provided.</p>
-<p><strong>Typing of PropertyChangeEvents</strong></p>
-<p>Any property change event from an IPreferenceStore must have an old and new 
-  value of the same type that is consistent with the setValue call that generated 
-  it. </p>
-<p>For instance if you call<code> IPreferenceStore#setValue(String name, long 
-  value) </code>the values in the PropertyChangeEvent generated from this method 
-  will both be of type <code>java.lang.Long</code>.</p>
-<p><strong>putValue</strong></p>
-<p>Calls to <code>#putValue</code> will not generate a <code>PropertyChangedEvent</code>. 
-  Calls to the various <code>#setValue</code> methods will.</p>
-<p><strong>Relationship between the OSGI Preference and an IPreferenceStore</strong></p>
-<p>The IPreferenceStore provided by <code>AbstractUIPlugin#getPreferenceStore()</code>is 
-  an instance of <code>ScopedPreferenceStore</code> which uses <code>org.osgi.service.prefs.Preferences</code> 
-  as a back end. <code>org.osgi.service.prefs.Preferences</code> propagates change 
-  events as Strings only. </p>
-<p>The <code>ScopedPreferenceStore</code> wrappers those OSGI events generated 
-  by <code>IPreferenceStore#setValue(String name, String value)</code> and one 
-  of it's own <code>PropertyChangeEvents</code> and forwards that event to it's 
-  listeners. For the other implementations of <code>IPreferenceStore#setValue</code> 
-  the <code>ScopedPreferenceStore</code> will create it's own events of the correct 
-  type and not propagate the events from the OSGI preferences.</p>
-<p>Listeners to a <code>ScopedPreferenceStore</code> should be prepared for both 
-  typed and String values in thier change events as it is still possible to get 
-  an event via the OSGI preferences (during a preference import for instance). 
-  OSGI events are always of type <code>java.lang.String.</code></p>
-<h2><a name="IWorkbenchWindow"></a>IWorkbenchWindow#getShell() has more explict API</h2>
-<p>It has always been possible to get a null org.eclipse.swt.widgets.Shell from 
-  the existing IWorkbenchWindows in the Eclipse SDK. We now explictly define the 
-  conditions where this occurs, namely when the shell has not been created or 
-  when the IWorkbenchWindow has been closed.</p>
-
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/3.1/incompatibilities.html b/bundles/org.eclipse.platform.doc.isv/porting/3.1/incompatibilities.html
deleted file mode 100644
index 5387862..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/3.1/incompatibilities.html
+++ /dev/null

@@ -1,347 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Incompatibilities between Eclipse 3.0 and 3.1</title>
-</head>
-
-<body>
-
-<h1>Incompatibilities between Eclipse 3.0 and 3.1</h1>
-
-<p> Eclipse changed in
-incompatible ways between 3.0 and 3.1 in ways that affect plug-ins. The
-following entries describe the areas that changed and provide instructions for
-  migrating 3.0 plug-ins to 3.1. Note that you only need to look here if you are experiencing
-  problems running your 3.0 plug-in on 3.1.</p>
-<ol>
-  <li><a href="#Preference Store">Plug-in Preferences</a></li>
-  <li><a href="#IPath Changes">Changes to IPath constraints</a></li>
-  <li><a href="#Extension Registry">Extension registry</a></li>
-  <li><a href="#Code Formatter Options">Code formatter options</a></li>
-  <li><a href="#AntCorePreferences">API contract changes to AntCorePreferences</a></li>
-  <li><a href="#JFaceLogPolicy">API contract changes to Policy class in JFace</a></li>
-  <li><a href="#NullDefaultPerspective">API contract changes to allow a null default 
-    perspective</a></li>
-  <li><a href="#IViewLayout">API contract changes to IViewLayout</a></li> 
-  <li><a href="#IVMInstall">API contract changes to IVMInstall</a></li> 
-  <li><a href="#SelectionEnabler.SelectionClass">SelectionEnabler.SelectionClass 
-    made package-visible</a></li>
-  <li><a href="#ContributionItem.getParent">ContributionItem.getParent() can return 
-    null</a></li>
-  <li><a href="#IPropertySource.isPropertySet">Changes to isPropertySet(boolean) 
-    in IPropertySource and IPropertySource2</a></li>
-  <li><a href="#handlerSubmission">handlerSubmission element
-    deleted from the org.eclipse.ui.commands extension
-    point</a></li>
-  <li><a href="#teamUI">Static non-final API field GLOBAL_IGNORES_CHANGED 
-  in TeamUI made final</a></li>
-  <li><a href="#FillData">ClassCastException using FillLayout</a></li>
-  <li><a href="#DisposedParent">Creating a widget with a disposed parent</a></li>
-</ol>
-<hr>
-
-<h2><a name="Preference Store"></a>1. Plug-in Preferences</h2>
-  
-<p><strong>What is affected:</strong> Plug-ins who initialize their default plug-in preference values by over-riding <code>Plugin#initializeDefaultPreferences</code> or
-use preference change listeners.</p>
-<p><strong>Description: </strong> In Eclipse 3.1 the <code>org.eclipse.jface.preference.IPreferenceStore</code> 
-  object obtained from <code>org.eclipse.ui.plugin.AbstractUIPlugin#getPreferenceStore</code> 
-  was migrated to live on top of the new 3.0 Eclipse preference framework supplied 
-  by the <code>org.eclipse.core.runtime</code> plug-in. </p>
-  
-  
-<p><strong>Action required: </strong> As a result, clients using the preference 
-  APIs should check for two possible issues: </p>
-<ol>
-  <li>The type of the objects contained in preference change events is not guarenteed; both the old value and
-  new value in events can be null, a <code>String</code>, or a typed object. Therefore to be
-  a good client, preference change listeners should be able to handle all three of these possible situations.</li>
-  <li>If your plug-in uses <code>org.eclipse.ui.plugin.AbstractUIPlugin#initializeDefaultPreferences</code> then
-  you must be sure to include the <code>org.eclipse.core.runtime.compatibility</code> plug-in in your plug-in's list
-  of required plug-ins as this dependancy has been removed from the <code>org.eclipse.ui.workbench</code> 
-    plug-in.</li>
-</ol>
-<p>See the <a href="../../reference/misc/preference_store.html">preference store</a> 
-documentation for more details.
-</p>
-<h2><a name="IPath Changes"></a>2. Changes to IPath constraints</h2>
-<p>
-<b>What is affected:</b> Plug-ins that create, manipulate, or store <tt>IPath</tt> objects.
-</p><p>
-<b>Description:</b> In Eclipse 3.0, <tt>IPath</tt> had a number of restrictions
-on the segments of paths that were more restrictive than the restrictions of the
-underlying operating system. These included:</p>
-<ul>
-<li>Leading and trailing whitespace in path segments were not allowed</li>
-<li>The colon character (':') was reserved as a device separator character</li>
-<li>The backslash character ('\') was reserved as a segment separator character</li>
-</ul>
-<p>These restrictions have been removed in Eclipse 3.1 when the platform's data
-location (workspace) is located on a file system that does not have these restrictions.
-</p><p>
-<b>Action required:</b> In order to enable the proper treatment of the expanded 
-range of paths, all usage of <tt>Path</tt> and <tt>IPath</tt> within plug-ins 
-should be reviewed and updated as described below. Most unmodified plug-ins 
-will continue to behave exactly as in 3.0 on all paths considered legal in 3.0. 
-However, unless these prescribed changes are made, they are likely to fail in 
-cases involving paths considered legal in 3.1 that were illegal in 3.0.</p>
-<p>
-Plug-ins that store string representations of paths in a format that needs to be 
-readable across different platforms should migrate to the new 
-<tt>Path.fromPortableString</tt> factory method. This method produces
-an <tt>IPath</tt> instance from a platform-independent format. This string 
-representation of paths can be created using the <tt>IPath.toPortableString</tt> method.
-Examples of metadata files that are affected include files that are stored inside Eclipse
-workspace projects (.project, .classpath, etc), and all paths stored in the preference
-store (<tt>org.eclipse.core.runtime.preferences.IPreferencesService</tt>).</p> 
-<p>
-Note: <tt>fromPortableString</tt> will correctly read all path strings that were
-created using the Eclipse 3.0 <tt>IPath.toString</tt> method, but not the
-Eclipse 3.1 <tt>toString</tt> method. Thus in most cases no change is required 
-to existing metadata file formats except to begin writing paths with <tt>toPortableString</tt>
-and reading paths with <tt>fromPortableString</tt>.</p>
-<p>
-Plug-ins that were creating paths from hard-coded string literals that assumed 
-':' and '\' had special meaning on all platforms will need to migrate. The easiest
-solution is to restrict string path literals to the subset that is supported
-on all platforms (avoid colon and backslash characters).  Path literals can support
-the complete set of valid Unix paths by using the portable path string format produced
-by <tt>Path.toPortableString</tt>. This format interprets the first single colon (':') 
-as the device separator, slash ('/') as the segment separator, and double colon ("::") 
-as a literal colon character. For example, the code <tt>new Path("c:/temp")</tt>
-will now create a relative path with two segments on Unix platforms.  Similarly,
-<tt>new Path("a\\b")</tt> will now create a path with a single segment
-on Unix platforms, and a path with two segments on Windows.</p>
-<p>
-Plug-ins constructing paths using the <tt>IPath.append(String)</tt> method 
-that assumed ':' and '\' had special meaning on all platforms may need to update their code.
-In Eclipse 3.1, this method uses operating-system specific device and segment
-delimiters to interpret the provided path string.  For example, calling <tt>append("a\\b")</tt>
-on Unix platforms will now append a single segment, whereas on Windows it will
-continue to append two segments.</p>
-<p>
-Any data files read and interpreted by the platform will no longer treat ':' and '\' as 
-special characters on all platforms.  All paths stored in data files that can be
-read on multiple platforms must be in portable form.  For example, paths of
-icon files and other paths in <tt>plugin.xml</tt> must use only '/' as
-the path segment separator.</p>
-<h2><a name="Extension Registry"></a>3. Extension registry</h2>
-
-<p><b>What is affected:</b> Plug-ins that manipulate or retain <code>IExtensionPoint</code>,
-<code>IExtension</code>, and <code>IConfigurationElement </code>objects from the
-Eclipse Platform's plug-in or extension registry.</p>
-<p><b>Description: </b>Prior to 3.0, all objects obtained from the extension
-registry (of the former plug-in registry) were good forever. Changes were made
-in Eclipse 3.0 that allowed plug-ins to be dynamically added or removed without
-having to restart Eclipse. When a plug-in is removed without restarting, its
-entries in the extension registry necessarily become invalid. This means that
-another plug-in holding on to an object obtained previously from the deleted
-plug-in's extension registry entry would be left holding an invalid object. The
-only hint that a client could get would be from listening to <code>IRegistryChangeEvent</code>.
-The problem has existed since Eclipse 3.0, but is rarely encountered in practice
-because it is highly unusual for a plug-in to be removed without restarting
-Eclipse.</p>
-<p>This problem has been addressed in 3.1 by:</p>
-<ul>
-  <li>Existing methods on these <code>IExtensionPoint</code>, <code>IExtension</code>,
-    and <code>IConfigurationElement</code> now specify that <code>InvalidRegistryObjectException</code>
-    will be thrown when the object is invalid. The exception is unchecked so
-    that dynamic unaware clients are not forced to check it.</li>
-  <li>A new <code>isValid()</code> method was added to these interfaces so that
-    a client can determine whether an object is still valid.</li>
-  <li>Recommendations were added to the specs to make it clear that hanging on
-    to objects obtained from the extension registry is not recommended.</li>
-</ul>
-<p><b>Action required:</b> If your plug-in needs to be dynamic-aware (i.e.
-capable of dealing with the on-the-fly addition or removal of plug-ins), the
-code that deals with <code>IExtensionPoint</code>, <code>IExtension</code>, and <code>IConfigurationElement</code>
-object sourced from some other plug-in must be changed to catch <code>IRegistryChangeEvent</code>,
-exactly as if it were a checked exception. Catching the exception (rather than
-an <code>isValid()</code> pre-check) is the only surefire way to deal with the
-case of a plug-in being removed by a concurrent thread (which, if it happens, it
-almost certainly will be).</p>
-
-<h2><a name="Code Formatter Options"></a>4. Code formatter options</h2>
-<p><b>What is affected:</b> Plug-ins that programmatically access the Java code formatter options.</p>
-
-<p><b>Description:</b> In Eclipse 3.0, the values for the code formatter option 
-  <code>org.eclipse.jdt.core.formatter.DefaultCodeFormatterConstants#FORMATTER_TAB_CHAR</code> 
-  could only be <code>TAB</code> or <code>SPACE</code>. The specification made 
-  no explicit mention that the value type was an enumeration that might grow in 
-  future releases. In Eclipse 3.1, a third possible value, <code>MIXED</code>, 
-  was added to address bug <a href="http://bugs.eclipse.org/bugs/show_bug.cgi?id=73104">73104</a>. 
-  The specification has been changed to include this new value, and to allow for 
-  more values being added in the future.</p>
-<p><b>Action required:</b> Clients programmatically reading or setting this code 
-  formatter option should check their code to take account of the new third value, 
-  and to ensure that it is written in a robust way that fails gracefully if it 
-  ever encounters an option value that it did not anticipate.</p>
-  
-<h2><a name="AntCorePreferences"></a>5. API contract changes to AntCorePreferences</h2>
-<p><b>What is affected:</b> Plug-ins that subclass or instantiate <code>org.eclipse.ant.core.AntCorePreferences</code></p>
-
-<p><b>Description:</b> In Eclipse 3.0, the class <code>org.eclipse.ant.core.AntCorePreferences</code> 
-  was not marked that clients may not instantiate or subclass.
-  This was an oversight that has been addressed in Eclipse 3.1 with the class marked as not intended to be subclassed or instantiated.
-  </p>
-<p><b>Action required:</b> Clients programmatically creating an instance of <code>org.eclipse.ant.core.AntCorePreferences</code>
- 	should migrate their code to retrieve the preferences using: <code>org.eclipse.ant.core.AntCorePlugin.getPreferences()</code>.
-	Any subclass will need to be reworked to no longer subclass <code>org.eclipse.ant.core.AntCorePreferences</code>.</p>
-	
-<h2><a name="JFaceLogPolicy"></a>6. API contract changes to Policy class in JFace</h2>
-<p><b>What is affected:</b> RCP applications that override the JFace log set by 
-  the workbench.</p>
-<p><b>Description:</b> In Eclipse 3.0, the workbench set the workbench's log as 
-  the log to use for logging JFace errors, by passing the workbench plug-in's 
-  log directly to <code>org.eclipse.jface.util.Policy.setLog(ILog)</code>. In 
-  3.1, the dependency on <code>ILog</code> has been removed from JFace in order 
-  to enable standalone applications using SWT and JFace outside of the eclipse 
-  runtime. A new interface, <code>ILogger</code>, has been introduced to meet 
-  JFace's needs. The workbench has been changed to provide an <code>ILogger</code> 
-  wrapping the workbench <code>ILog</code>. For further details, see bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=88608">88608</a>.</p>
-<p><b>Action required:</b> Most RCP applications should not need to override the 
-  log set by the workbench, but if they previously called <code>Policy.setLog(ILog)</code>, 
-  they will need to be changed to pass an <code>ILogger</code> instead.</p>
-	
-<h2><a name="NullDefaultPerspective"></a>7. API contract changes to allow a null default 
-  perspective</h2>
-<p><b>What is affected:</b> RCP applications expecting a non-null default perspective.</p>
-<p><b>Description:</b> In order to allow RCP applications to start with an empty 
-  window with no perspectives open (enhancement <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=71150">71150</a>), 
-  <code>WorkbenchAdvisor.getInitialWindowPerspectiveId()</code> and <code>IPerspectiveRegistry.getDefaultPerspective()</code> 
-  have been changed to allow null to be returned. In the IDE, there is always 
-  a default perspective, so <code>IPerspectiveRegistry.getDefaultPerspective()</code> 
-  will not return null. Similarly, if an existing RCP app previously returned 
-  a non-null value from <code>WorkbenchAdvisor.getInitialWindowPerspectiveId()</code>, 
-  then <code>IPerspectiveRegistry.getDefaultPerspective()</code> will still return 
-  a non-null value.</p>
-<p><b>Action required:</b> No action should be required by clients.</p>
-
-<h2><a name="IViewLayout"></a>8. API contract changes to IViewLayout</h2>
-<p><b>What is affected:</b> Plug-ins that implement <code>org.eclipse.ui.IViewLayout.</code></p>
-<p><b>Description:</b> In Eclipse 3.0, the class <code>org.eclipse.ui.IViewLayout</code> 
-  was not marked that clients may not implement. This was an oversight that has 
-  been addressed in Eclipse 3.1 with the class marked as not intended to be implemented 
-  by clients. </p>
-<p><b>Action required:</b> Any implementing classes will need to be reworked to 
-  no longer implement <code>org.eclipse.ui.IViewLayout</code>.</p>
-<h2><a name="IVMInstall"></a>9. API contract changes to IVMInstall</h2>
-<p><b>What is affected:</b> Plug-ins that implement <code>org.eclipse.jdt.launching.IVMInstall.</code></p>
-<p><b>Description:</b> In Eclipse 3.0, the class <code>org.eclipse.jdt.launching.IVMInstall</code> 
-  was not marked that clients may not implement directly. This was an oversight 
-  that has been addressed in Eclipse 3.1 with the class marked as not intended 
-  to be implemented directly by clients. To maintain binary compatibility, we 
-  still allow clients to implement the interface directly, but strongly recommend 
-  that clients subclass <code>org.eclipse.jdt.launching.AbstractVMInstall</code> 
-  instead. Clients that implement <code>IVMInstall</code> should also implement 
-  the new optional interface <code>org.eclipse.jdt.launching.IVMInstall2</code>, 
-  which <code>AbstractVMInstall</code> now implements. It is recommended that 
-  clients implement the new interface, <code>IVMInstall2</code>, to avoid the 
-  problem noted in bug 73493. The recommended migration is to subclass <code>AbstractVMInstall</code>.</p>
-<p><b>Action required:</b> Any implementing classes that do not already subclass 
-  <code>org.eclipse.jdt.launching.AbstractVMInstall</code> should be reworked 
-  to subclass <code>org.eclipse.jdt.launching.AbstractVMInstall.</code></p>
-<h2><a name="SelectionEnabler.SelectionClass"></a>10. SelectionEnabler.SelectionClass 
-  made package-visible</h2>
-<p><b>What is affected:</b> Plug-ins that use <code>org.eclipse.ui.SelectionEnabler.SelectionClass.</code></p>
-<p><b>Description:</b> In Eclipse 3.0, the nested implementation class <code>org.eclipse.ui.SelectionEnabler.SelectionClass</code> 
-  was public, with no restrictions on its usage. This was an oversight that has 
-  been addressed in Eclipse 3.1 with the class being made package-visible. </p>
-<p><b>Action required:</b> Any classes instantiating or extending <code>org.eclipse.ui.SelectionEnabler.SelectionClass</code> 
-  will need to be reworked to no longer refer to this class.</p>
-  
-<h2><a name="ContributionItem.getParent"></a>11. ContributionItem.getParent() 
-  can return null</h2>
-<p><b>What is affected:</b> Plug-ins that call <code>getParent()</code> on a subclass 
-  of <code>org.eclipse.jface.action.ContributionItem.</code></p>
-<p><b>Description:</b> In Eclipse 3.0, method <code>org.eclipse.jface.action.ContributionItem.getParent()</code> 
-  did not specify that it could return null. This was an oversight that has been 
-  addressed in Eclipse 3.1 with Javadoc for the method clarifying when it can 
-  return null. For more details, see bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=92777">92777</a>.</p>
-<p><b>Action required:</b> Any code calling <tt>ContributionItem.getParent()</tt> 
-  must ensure that it can handle a null result.</p>
-
-<h2><a name="IPropertySource.isPropertySet"></a>12. Changes to isPropertySet(boolean) 
-  in IPropertySource and IPropertySource2</h2>
-<p><b>What is affected:</b> Plug-ins that implement <code>org.eclipse.ui.views.properties.IPropertySource</code> 
-  or <code>IPropertySource2.</code></p>
-<p><b>Description:</b> In Eclipse 3.0, the specification for the method <code>org.eclipse.ui.views.properties.IPropertySource.isPropertySet(boolean)</code> 
-  was incorrectly changed to specify that true should be returned if the specified 
-  property did not have a meaningful default value. In previous versions, it specified 
-  that false should be returned in this case. This was an inadvertent breaking 
-  API change, although the implementation worked the same as before if the property 
-  source implemented <code>IPropertySource</code> and not <code>IPropertySource2</code>. 
-  This has been corrected in 3.1, with <code>IPropertySource.isPropertySet(boolean)</code> 
-  being reverted back to its earlier specification (that false should be returned 
-  in this case), and IPropertySource2.isPropertySet(boolean) overriding this to 
-  specify that true should be returned in this case. For more details, see bug 
-  <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=21756 ">21756</a>.</p>
-<p><b>Action required:</b> Any classes implementing IPropertySource or IPropertySource2, 
-  where some of the properties do not have meaningful default values, should be 
-  checked to ensure that they return the appropriate value for isPropertySource(boolean). 
-  Clients should check that the Restore Default Value button in the Properties 
-  view works as expected for their property source.</p>
-
-<h2><a name="handlerSubmission"></a>13. handlerSubmission element
-deleted from the org.eclipse.ui.commands extension point</h2>
-<p><b>What is affected:</b> Plug-ins that used the experimental
-<code>handlerSubmission</code> element introduced into the
-<code>org.eclipse.ui.commands</code> extension point Eclipse 3.0.
-</p>
-<p><b>Description:</b> In Eclipse 3.0, an experimental element was introduced
-into the <code>org.eclipse.ui.commands</code> extension point.  This element was
-intended as a way to register handlers through XML.  Since then, a far superior
-mechanism, the <code>org.eclipse.ui.handlers</code> extension point, has been
-introduced.  Since the element was marked as experimental, it has now been
-removed.</p>
-<p><b>Action required:</b> Any plug-ins defining a
-<code>handlerSubmission</code> element should migrate to the
-<code>org.eclipse.ui.commands</code> extension point.</p>
-  
-<h2><a name="teamUI"></a>14. Static non-final API field GLOBAL_IGNORES_CHANGED 
-  in TeamUI made final</h2>
-<p><b>What is affected:</b> Plug-ins that were setting the GLOBAL_IGNORES_CHANGED 
-  field of TeamUI.</p>
-<p><b>Description:</b> In Eclipse 3.0, the GLOBAL_IGNORES_CHANGED field was added 
-  to the TeamUI class. This field is a constant that is used in a property change 
-  event to indicate that the list of global ignores maintained by the Team plugin 
-  has changed. This field was not marked final in 3.0 but should have been. It 
-  has been made final in 3.1.</p>
-<p><b>Action required:</b> Any plugins that were setting the above field can no 
-  longer do so.</p>
-
-<h2><a name="FillData"></a>15. ClassCastException using FillLayout</h2>
-<p><b>What is affected:</b> Plug-ins that incorrectly use FillLayout.</p>
-<p><b>Description:</b> In Eclipse 3.0, no layout data was associated with 
-the FillLayout and if an application assigned layout data to a child that was 
-managed by a FillLayout, it was ignored. In Eclipse 3.1, support was added to
-FillLayout to cache size information in order to improve resize performance.
-The cached data is stored in a FillData object associated with each child
-managed by the FillLayout.  If an application has incorrectly assigned  
-layout data to a child, a ClassCastException will be thrown when computeSize 
-is called on the parent.</p>
-<p><b>Action required:</b> Find any children in a FillLayout that have layout 
-data assigned and stop assigning the layout data.</p>
-
-<h2><a name="DisposedParent"></a>16. IllegalArgumentException thrown creating a 
-widget with a disposed parent</h2>
-<p><b>What is affected:</b> Plug-ins that catch exceptions while creating widgets.</p>
-<p><b>Description:</b> In Eclipse 3.0, if a widget was created with a disposed 
-parent, no exception was thrown and the widget code failed at a later point or 
-an SWTException with text "Widget Is Disposed" was thrown.  In Eclipse 3.1, 
-if a widget is created with a disposed parent, the constructor will throw an
-IllegalArgumentException with text "Argument not valid".</p>
-<p><b>Action required:</b>Any code that handles the SWTException when creating
-a widget will also need to handle the IllegalArgumentException.</p>
-
-<p>&nbsp;</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/3.1/recommended.html b/bundles/org.eclipse.platform.doc.isv/porting/3.1/recommended.html
deleted file mode 100644
index ce80977..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/3.1/recommended.html
+++ /dev/null

@@ -1,121 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Changes required when adopting 3.1 mechanisms and APIs</title>
-</head>
-
-<body>
-
-<h2>Changes required when adopting 3.1 mechanisms and APIs</h2>
-<p>This section describes changes that are required if you are trying to change
- your 3.0 plug-in to adopt the 3.1 mechanisms and APIs.</p>
-  
-<h3>Platform undo/redo support</h3>
-<p>
-Eclipse 3.1 provides a new infrastructure for defining <b>undoable operations</b> and a shared
-<b>operation history</b> that keeps track of operations that have been executed, undone, and
-redone. The various undo frameworks provided by add-on plug-ins should
-migrated over time to the platform operation support, so that clients of these frameworks 
-can integrate more deeply with the platform and make their undoable operations available
-for undo in other plug-in views and editors.  See the 
-<a href="../../guide/wrkAdv_undo.htm">Undoable operations</a> documentation for basic
-information about adding undo support to a plug-in.  Plug-ins that already define undo support
-or use another framework can be migrated to the new undo support in a staged fashion, as
-described below.</p>
-<h4>Migrating plug-in specific operation (command) classes to IUndoableOperation</h4>
-<p>Plug-ins that already define classes describing their undoable operations should add
-an implementation for the interface <b>IUndoableOperation</b> to their operation/command
-classes.  Plug-ins may still use older frameworks for managing the history (command stack)
-if necessary, but providing an interface for <b>IUndoableOperation</b> allows a plug-in's
-clients to use the same operations in the platform operations history, and to mix and match
-undoable operations from different plug-ins.  This strategy is similar to that used by
-the SDK text editors to migrate to the new operations framework.  If a direct mapping of
-the interface is not possible, wrappers can be used to map <b>IUndoableOperation</b>
-protocol to legacy undo objects.  This strategy is used by the Platform/JDT
-refactoring support.  Migration of the operation/command classes to <b>IUndoableOperation</b>
-is an important step because it allows the undoable operations from different frameworks
-to be utilized by other plug-ins without either plug-in having to migrate completely.</p>
-<h4>Migrating command stacks with IOperationHistory</h4>
-<p>Once undoable operations or commands are expressed in terms of <b>IUndoableOperation</b>, plug-ins 
-that define an undo history (command stack) for keeping track of the undoable and redoable 
-operations can migrate to the platform operations history by defining an <b>IUndoContext</b>
-that represents their undo history.  Undo histories that were previously managed locally 
-can be merged into the common operation history by defining a unique 
-undo context either for each part or for each model object, adding the appropriate undo context to each operation, and
-then adding the operation to the platform operation history.  Undo histories with more 
-global scope can be implemented by defining a unique undo context representing that undo scope,
-assigning that context to each operation, and then adding the operation to the platform
-operation history.  See the 
-<a href="../../guide/wrkAdv_undo.htm">Undoable operations</a> documentation for examples of
-creating undo contexts, assigning them, and adding operations to the platform operation history.
-</p>
-<h4>Defining undoable operations global to the workbench</h4>
-<p>Plug-ins that wish their operations to be undoable from workbench views such as the 
-Navigator or Package Explorer should assign the workbench undo context to their operations.
-See the <a href="../../guide/wrkAdv_undo.htm">Undoable operations</a> documentation for more information
-about this undo context and how it can be retrieved by both workbench and headless plug-ins.
-</p>
-<h3>Platform undo/redo action handlers</h3>
-<p>
-Plug-ins that do not define an undo infrastructure or undoable operations, but wish to 
-provide access to the platform's undo history, should consider retargeting the global 
-undo and redo action handlers with the new common undo and redo action handlers.  The action
-handlers should be assigned an undo context specifying which undo and redo history
-is to be shown.  Plug-ins can use their locally defined undo contexts for showing "part-local"
-undo and redo history.  The workbench undo context can be used for showing workbench-wide
-undo and redo history.  Again, the 
-<a href="../../guide/wrkAdv_undo.htm">Undoable operations</a> documentation 
-has a complete example.</p>
-<h4>Migrating text operation actions to the common action handlers</h4>
-<p>Migrating text editor undo and redo actions is a bit different than simple retargeting
-of the global undo/redo action handlers.  The <b>AbstractTextEditor</b> framework defines 
-common text actions using a parameterized <b>TextOperationAction</b>.  These actions are stored
-locally in the framework and used to dispatch various commands to an editor's text operation
-target.  For text undo to work properly, the text editor framework relies on the presence 
-of text operation actions with the proper id's (<tt>ITextEditorActionConstants.REDO</tt>
-and <tt>ITextEditorActionConstants.UNDO</tt>). 
-</p>
-<p><b>AbstractTextEditor</b> has been migrated so that it creates the common action handlers, while
-still assigning them to the TextOperationAction table with their legacy id's.  In this way, the
-new undo and redo action handlers can be retrieved using the legacy techniques for retrieving
-the action and performing an operation.  Text editors in the <b>AbstractTextEditor</b> hierarchy 
-will inherit this behavior.  </p>
-<p>Editors that do not inherit this behavior from <b>AbstractTextEditor</b> should consider 
-migrating any existing undo and redo actions to use the new handlers.  Editors with
-legacy undo and redo TextOperationActions will still have working local undo support, since 
-the JFace Text undo manager API used by these actions is still supported.  However, the 
-undo and redo action labels will not be consistent with the new Eclipse SDK undo/redo actions, which show 
-the name of the available undo or redo operation.  To create the common undo and redo
-action handlers, the undo context used by the text viewer's undo manager should
-be used when creating the action handlers, and those handlers should be set into the
-editor using the appropriate <tt>ITextEditorActionConstants</tt> id.  See 
-<b><tt>AbstractTextEditor.createUndoRedoActions()</tt></b> and <b><tt>AbstractTextEditor.getUndoContext()</tt></b>
-for a detailed example.  Editors that rely on an <b>EditorActionBarContributor</b> subclass to 
-add to the action bars of their editors can use a similar technique by creating undo and redo action
-handlers and setting them when the active editor is set. </p>
-<h3>Help Enhancements</h3>
-<h4>Information Search</h4>
-<p>Plug-ins that contribute search pages into the <b>Search</b> dialog should 
-consider porting all their information-style searches into federated search 
-engines. Since 3.1, all information-style search is separated from the 
-workbench-artifact search. Information search engines are run in parallel as 
-background jobs and their results collated in the new Help view. See
-<a href="../../guide/help_search.htm">Help Search</a> for more details.</p>
-<h4>Dynamic help</h4>
-<p>The new dynamic help view will work with existing context IDs that are 
-statically associated with widgets in workbench parts and dialogs. However, if 
-you catch help event yourself and show help, dynamic help view will not be able 
-to show anything useful. To fix the problem, you should adapt to the new <code>
-IContextProvider</code> interface as described in
-<a href="../../guide/help_context_dynamic.htm">Dynamic Context Help</a> 
-document.</p>
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/3.2/faq.html b/bundles/org.eclipse.platform.doc.isv/porting/3.2/faq.html
deleted file mode 100644
index d286667..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/3.2/faq.html
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse 3.2 Plug-in Migration FAQ</title>
-</head>
-
-<body>
-
-<h1>Eclipse 3.2 Plug-in Migration FAQ</h1>
-<ol>
-	<li><a href="#legacyActionWithNoLabel">Legacy Action With No Label</a></li>
-</ol>
-<h2><a name="legacyActionWithNoLabel">Legacy Action With No Label</a></h2>
-<p>
-If you are using the action-based extension points, then you may want to specify
-either a <code>definitionId</code> or a non-empty <code>label</code>.  If you
-don't do this, then in the "Uncategorized" category, there may be commands
-called "Legacy Action With No Label".  They will appear in the keys preference
-page.  A warning will be printed to the log.
-</p>
-<p>
-In 3.2, all actions are converted into commands when parsing the registry.  As
-such, actions without a definition id have a command generated for them.  This
-command needs a label, which is typically drawn from the label on the action.
-In the case of actions appearing in the tool bar, sometimes neither a definition
-id nor a label were specified.
-</p>
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/3.2/incompatibilities.html b/bundles/org.eclipse.platform.doc.isv/porting/3.2/incompatibilities.html
deleted file mode 100644
index 8e83df5..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/3.2/incompatibilities.html
+++ /dev/null

@@ -1,209 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Incompatibilities between Eclipse 3.1 and 3.2</title>
-</head>
-
-<body>
-
-<h1>Incompatibilities between Eclipse 3.1 and 3.2</h1>
-
-<p> Eclipse changed in incompatible ways between 3.1 and 3.2 in ways that affect 
-  plug-ins. The following entries describe the areas that changed and provide 
-  instructions for migrating 3.1 plug-ins to 3.2. Note that you only need to look 
-  here if you are experiencing problems running your 3.1 plug-in on 3.2.</p>
-<ol>
-  <li><a href="#NullClassLoaderObject">API contract changes to IJavaReferenceType</a></li>
-  <li><a href="#nonLocalResources">Resources are no longer necessarily in the local file system</a></li>
-  <li><a href="#MultiPageEditorSiteProgress">API changes to MultiPageEditorSite</a></li>
-</ol>
-<hr>
-
-<!-- ############################################## -->
-<h2>1. <a name="NullClassLoaderObject"></a>API contract changes to IJavaReferenceType</h2>
-<p><strong>What is affected:</strong> Clients that call <code>IJavaReferenceType.getClassLoaderObject()</code>.</p>
-<p><strong>Description:</strong> In Eclipse 3.1, the method <code>org.eclipse.jdt.debug.core.IJavaReferenceType.getClassLoaderObject()</code> 
-  was added to <code>IJavaReferenceType</code>. The method was not specified to 
-  return <code>null</code>, but could. In Eclipse 3.2, the specification has been 
-  updated to indicate that <code>null</code> is a valid return value. The behavior 
-  of the method has not changed, but callers should be aware that <code>null</code> 
-  can be returned and should add appropriate checks.</p>
-<p><strong>Action required:</strong> Clients calling <code>IJavaReferenceType.getClassLoaderObject()</code> 
-  should be modified to handle <code>null</code> as a return value.</p>
-
-<!-- ############################################## -->
-<h2>2. <a name="nonLocalResources"></a>Resources are no longer necessarily in the local file system</h2>
-<p><strong>What is affected:</strong>Clients of the <code>IWorkspace</code> API
-that assume resources are stored in the local file system.</p>
-<p><strong>Description:</strong>
-Prior to Eclipse 3.2, each existing <code>IResource</code> had a corresponding
-file or directory in a file system accessible by <code>java.io.File</code>.  In
-Eclipse 3.2, support was added for creating resources whose contents are stored
-in an arbitrary backing file system.  Resources using this support can no longer
-be represented directly as a <tt>java.io.File</tt>.
-</p>
-<p><strong>Action required:</strong>
-The old method <tt>IResource.getLocation()</tt> returns the local file
-system path of a resource.  This method returns null for resources
-that are not stored in the local file system.  Most callers of <tt>getLocation()</tt>
-did so in order to obtain an instance of <tt>java.io.File</tt>, which can
-no longer be used for resources that are not stored in the local file system.
-</p>
-<p>
-The new <tt>org.eclipse.core.filesystem</tt> plugin provides a generic file
-system API that can be used in place of <tt>java.io.File</tt>.  In particular,
-an instance of <tt>org.eclipse.core.filesystem.IFileStore</tt> provides most
-of the same methods that are available on <tt>java.io.File</tt>. The following 
-snippet of code obtains an instance of <tt>IFileStore</tt> for a given resource:
-<pre>
-   IResource resource = ...;//some resource
-   IFileStore store = EFS.getStore(resource.getLocationURI());
-</pre>
-<p>
-The following table provides equivalent methods on <tt>IFileStore</tt>
-for operations usually done with <tt>java.io.File</tt>:
-</p>
-<p>
-<table border=1>
-<th align=left>java.io.File</th><th align=left>IFileStore</th>
-<tr><td>delete</td><td>delete</td></tr>
-<tr><td>getName</td><td>getName</td></tr>
-<tr><td>getParent</td><td>getParent</td></tr>
-<tr><td>list</td><td>childNames</td></tr>
-<tr><td>mkdir</td><td>mkdir(EFS.SHALLOW, null)</td></tr>
-<tr><td>mkdirs</td><td>mkdir(EFS.NONE, null)</td></tr>
-<tr><td>renameTo</td><td>move</td></tr>
-<tr><td>new FileInputStream(file)</td><td>openInputStream</td></tr>
-<tr><td>new FileOutputStream(file)</td><td>openOutputStream</td></tr>
-</table>
-</p>
-<p>
-In the <tt>IFileStore</tt> API, most information about a file is stored in a 
-structure called <tt>IFileInfo</tt>, obtained by calling <tt>IFileStore.fetchInfo()</tt>.
-This design allows for greater optimization over code using <tt>java.io.File</tt>,
-because many attributes about a file can often be obtained with a single file system
-call.  Note that the information in an <tt>IFileInfo</tt> will become stale
-if the underlying file is changed, so instances should only be held onto
-as long as they are needed.  Here are some methods on <tt>java.io.File</tt>
-that have equivalent methods on <tt>IFileInfo</tt>:
-</p>
-<p>
-<table border=1>
-<th align=left>java.io.File</th><th align=left>IFileInfo</th>
-<tr><td>canWrite</td><td>isReadOnly</td></tr>
-<tr><td>exists</td><td>exists</td></tr>
-<tr><td>getName</td><td>getName</td></tr>
-<tr><td>isDirectory</td><td>isDirectory</td></tr>
-<tr><td>isFile</td><td>!isDirectory()</td></tr>
-<tr><td>isHidden</td><td>isHidden</td></tr>
-<tr><td>lastModified</td><td>getLastModified</td></tr>
-<tr><td>length</td><td>getLength</td></tr>
-<tr><td>setLastModified</td><td>setLastModified</td></tr>
-<tr><td>setReadOnly</td><td>setAttribute(EFS.ATTRIBUTE_READ_ONLY, true)</td></tr>
-</table>
-</p>
-<p>
-As a concrete example, code that was previously calling <tt>java.io.File.exists()</tt>
-can now call <tt>IFileStore.fetchInfo().exists()</tt>.  When a <tt>IFileInfo</tt>
-is modified, the result needs to be stored back using the <tt>IFileStore.putInfo</tt>
-method. For example, this snippet flips the read only attribute on a file
-<pre>
-   IFileStore store = ...;//some file store
-   IFileInfo info = store.fetchInfo();
-   boolean readOnly = info.getAttribute(EFS.ATTRIBUTE_READ_ONLY);
-   info.setAttribute(EFS.ATTRIBUTE_READ_ONLY, !readOnly);
-   store.putInfo(info, EFS.SET_ATTRIBUTES, null);
-</pre>
-</p>
-<h4>IProjectDescription.getLocation()</h4>
-<p>
-As with the <tt>getLocation()</tt> method, the project description's location
-may no longer be in the local file system.  The method
-<tt>IProjectDescription.getLocationURI()</tt> can be used to obtain the location
-of a resource in an arbitrary file system.
-</p>
-<h4>Local caching</h4>
-<p>
-Some clients absolutely must have a local representation of a file.  For example,
-they may be launching a native tool against that file, or using non Eclipse-aware
-libraries that can only handle file system resources (such as <tt>java.util.zip.ZipFile</tt>).  
-In these cases, you can ask an IFileStore to return a cached local copy of its contents:
-<pre>
-   IFileStore store = ...;//some file store
-   //see if it can directly be represented as a local file
-   java.io.File local = store.toLocalFile(EFS.NONE, null);
-   //if not, ask for a cached local copy of the file
-   if (local == null)
-      local = store.toLocalFile(EFS.CACHE, null);
-</pre>
-Note that once a cached copy of a file is obtained, it does not remain in sync with 
-the actual file system it came from.  Modifying the cached copy will not cause the 
-underlying file to be modified.
-</p>
-<h4>Graceful failure</h4>
-<p>
-Clients that cannot handle resources outside the local file system may still
-want to adapt their code to fail more gracefully. Clients can check if a resource
-is in the local file system, and either ignore the resource or alert the user when
-they encouter a resource they cannot handle.  To determine if a resource is
-in the local file system, you need to find out its file system <i>scheme</i>. 
-This can be obtained from a resource as follows:
-<pre>
-   IResource resource = ...;//some resource
-   URI uri = resource.getLocationURI();
-   if (uri != null &amp;&amp; EFS.SCHEME_LOCAL.equals(uri.getScheme())) {
-      //file is in local file system
-   } else {
-      //file is not in the local file system
-   }
-</pre>
-If you have an <tt>IFileStore</tt> instance in hand, you can obtain the scheme
-as follows:
-<pre>
-   IFileStore store = ...;//a file store
-   store.getFileSystem().getScheme();
-</pre>
-</p>
-
-<!-- ############################################## -->
-<h2>3. <a name="MultiPageEditorSiteProgress"></a>API changes to MultiPageEditorSite</h2>
-<p><strong>What is affected:</strong> Clients that call <code>MultiPageEditorSite.progressStart()</code> or <code>MultiPageEditorSite.progressEnd()</code>.</p>
-<p><strong>Description:</strong> During Eclipse 3.0 development, these
-  methods were added as part of the progress support work.  Before the 3.0
-  release, the way in which progress was handled was changed, and this method
-  was no longer necessary.  Through programmer error, these public methods were
-  left in for the 3.0 release.  These two methods have never served any function
-  in an Eclipse release, and so have been deleted.
-<p><strong>Action required:</strong> Clients calling 
-  <code>MultiPageEditorSite.progressStart()</code> or 
-  <code>MultiPageEditorSite.progressEnd()</code> should switch to using
-  <code>IWorkbenchSiteProgressService</code> instead.</p>
-
-<!-- ############################################## -->
-
-
-<p>
-<p>
-<p>
-(The following is a template for editing this draft)
-<!-- ############################################## -->
-<h2>4. <a name="anchorNameHere"></a>Title goes here</h2>
-<p><strong>What is affected:</strong> Describe what clients are affected.
-</p>
-<p><strong>Description:</strong> Describe the incompatible changes.
-</p>
-<p><strong>Action required:</strong> Describe the action required.
-</p>
-<!-- ############################################## -->
-  
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/3.2/recommended.html b/bundles/org.eclipse.platform.doc.isv/porting/3.2/recommended.html
deleted file mode 100644
index 900c912..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/3.2/recommended.html
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Changes required when adopting 3.2 mechanisms and APIs</title>
-</head>
-
-<body>
-
-<h2>Changes required when adopting 3.2 mechanisms and APIs</h2>
-<p>This section describes changes that are required if you are trying to change 
-  your 3.1 plug-in to adopt the 3.2 mechanisms and APIs.</p>
-<h3>Launch configurations</h3>
-<h4>Launch configuration resource mapping</h4>
-<p>Eclipse 3.2 provides new infrastructure for associating launch configurations 
-  with resources. This mapping allows the platform to perform resource based filtering 
-  on launch configurations and allows the platform to optionally delete launch 
-  configurations when an associated project is deleted. The launch dialog has 
-  been enhanced to support a set of filters to optionally hide configurations 
-  associated with closed and deleted projects. As well, the launch dialog supports 
-  filtering based on selected working sets in the active workbench window, which 
-  can also be selected in the launch dialog.</p>
-<p>It is a client responsibility to manage the resource mapping for launch configurations. 
-  API has been added to <code>ILaunchConfigurationWorkingCopy</code> to set the 
-  resources associated with a configuration, and API has been added to <code>ILaunchConfiguration</code> 
-  to get the resources associated with a configuration. For example, launch tabs, 
-  launch shortcuts and refactoring participants should be considered when migrating. 
-  Code that creates or modifies launch configurations should also update resource 
-  mappings.</p>
-<h4>Launch configuration migration support</h4>
-<p>Eclipse 3.2 provides new infrastructure for migrating launch configurations 
-  to be compatible with new tooling. For example, in Eclipse 3.2, support has 
-  been added to perform resource based filter on launch configurations. Launch 
-  configurations need to be upgraded to provide resource mappings to leverage 
-  this new feature. Users can manually migrate launch configurations in their 
-  workspace from the <strong>Run/Debug</strong> &gt; <strong>Launching</strong> 
-  &gt; <strong>Launch</strong> <strong>Configurations</strong> preference page, 
-  by pressing the <strong>Migrate</strong> button.</p>
-<p>A new optional migration delegate attribute has been added to the <code>launchConfigurationTypes</code> 
-  extension point, specifying a class that implements the new interface <code>ILaunchConfigurationMigrationDelegate</code>. 
-  A migration delegate is responsible for identifying migration candidates and 
-  migrating them.</p>
-<h3>Launch Modes</h3>
-<p>A new optional attribute has been added to the <code>launchModes</code> extension 
-  point to properly support the externalization of cascade launch menu action 
-  labels. Clients that contribute launch modes should specify the proper label 
-  to use for launch cascade menus such as &quot;Run As&quot;. The new attribute 
-  is named <code>launchAsLabel</code>. Proper labels have been provided by the 
-  platform for run, debug and profile launch modes. For backwards compatibility, 
-  when the new attribute is unspecified for a launch mode, the cascade menu labels 
-  are generated as before, via MessageFormat with &quot;<code>{0} As</code>&quot;. 
-  See related bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=105235">105235</a>.</p>
-  
-<p><em>[No items. See the corresponding section of the <a href="../3.1/recommended.html">3.1 
-  Migration Guide</a> for format.]</em></p>
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_0_porting_guide.html b/bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_0_porting_guide.html
deleted file mode 100644
index f6146a9..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_0_porting_guide.html
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse 3.0 Plug-in Migration Guide</title>
-</head>
-
-<body>
-
-<h1>Eclipse 3.0 Plug-in Migration Guide</h1>
-<p>This guide covers migrating Eclipse 2.1 (or earlier) plug-ins to Eclipse 3.0.</p>
-<p>One of the goals of Eclipse 3.0 was move Eclipse forward while remaining
-compatible with previous versions to the greatest extent possible. That is,
-plug-ins written against the Eclipse 2.1 APIs should continue to work in 3.0 in
-spite of the API changes.</p>
-<p>The key
-kinds of compatibility are API contract compatibility and binary compatibility.
-API contract compatibility means that valid use of 2.1 APIs remains valid for
-3.0, so there is no need to revisit working code. Binary compatibility means that
-the API method signatures, etc. did not change in ways that would cause existing
-compiled (&quot;binary&quot;) code to no longer link and run with the new 3.0 libraries.</p>
-<p>While every effort way made to avoid breakage, there are a few areas of
-incompatibility. This document describes the areas where Eclipse changed in
-incompatible ways between 2.1 and 3.0, and provides instructions for migrating
-2.1 plug-ins to 3.0.</p>
-<ul>
-  <li><a href="3.0/faq.html">Eclipse 3.0 Plug-in Migration FAQ</a></li>
-  <li><a href="3.0/incompatibilities.html">Incompatibilities between
-    Eclipse 2.1 and 3.0</a></li>
-  <li><a href="3.0/recommended.html">Adopting 3.0 mechanisms and API</a></li>
-</ul>
-
-
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_1_porting_guide.html b/bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_1_porting_guide.html
deleted file mode 100644
index b3fd37e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_1_porting_guide.html
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse 3.1 Plug-in Migration Guide</title>
-</head>
-
-<body>
-
-<h1>Eclipse 3.1 Plug-in Migration Guide</h1>
-<p>This guide covers migrating Eclipse 3.0 (or earlier) plug-ins to Eclipse 3.1.</p>
-<p>One of the goals of Eclipse 3.1 was move Eclipse forward while remaining
-compatible with previous versions to the greatest extent possible. That is,
-plug-ins written against the Eclipse 3.0 APIs should continue to work in 3.1 in
-spite of the API changes.</p>
-<p>The key
-kinds of compatibility are API contract compatibility and binary compatibility.
-API contract compatibility means that valid use of 3.0 APIs remains valid for
-3.1, so there is no need to revisit working code. Binary compatibility means that
-the API method signatures, etc. did not change in ways that would cause existing
-compiled (&quot;binary&quot;) code to no longer link and run with the new 3.1 libraries.</p>
-<p>While every effort way made to avoid breakage, there are a few areas of
-incompatibility. This document describes the areas where Eclipse changed in
-incompatible ways between 3.0 and 3.1, and provides instructions for migrating
-3.0 plug-ins to 3.1.</p>
-<ul>
-  <li><a href="3.1/faq.html">Eclipse 3.1 Plug-in Migration FAQ</a></li>
-  <li><a href="3.1/incompatibilities.html">Incompatibilities between
-    Eclipse 3.0 and 3.1</a></li>
-  <li><a href="3.1/recommended.html">Adopting 3.1 mechanisms and API</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_2_porting_guide.html b/bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_2_porting_guide.html
deleted file mode 100644
index e3e43a5..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_2_porting_guide.html
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse 3.2 Plug-in Migration Guide</title>
-</head>
-
-<body>
-
-<h1>Eclipse 3.2 Plug-in Migration Guide</h1>
-<p>This guide covers migrating Eclipse 3.1 (or earlier) plug-ins to Eclipse 3.2.</p>
-<p>One of the goals of Eclipse 3.2 was to move Eclipse forward while remaining compatible 
-  with previous versions to the greatest extent possible. That is, plug-ins written 
-  against the Eclipse 3.1 APIs should continue to work in 3.2 in spite of the 
-  API changes.</p>
-<p>The key kinds of compatibility are API contract compatibility and binary compatibility. 
-  API contract compatibility means that valid use of 3.1 APIs remains valid for 
-  3.2, so there is no need to revisit working code. Binary compatibility means 
-  that the API method signatures, etc. did not change in ways that would cause 
-  existing compiled (&quot;binary&quot;) code to no longer link and run with the 
-  new 3.2 libraries.</p>
-<p>While every effort way made to avoid breakage, there are a few areas of incompatibility. 
-  This document describes the areas where Eclipse changed in incompatible ways 
-  between 3.1 and 3.2, and provides instructions for migrating 3.1 plug-ins to 
-  3.2.</p>
-<ul>
-  <li><a href="3.2/faq.html">Eclipse 3.2 Plug-in Migration FAQ</a></li>
-  <li><a href="3.2/incompatibilities.html">Incompatibilities between Eclipse 3.1 
-    and 3.2</a></li>
-  <li><a href="3.2/recommended.html">Adopting 3.2 mechanisms and API</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/questions/index.html b/bundles/org.eclipse.platform.doc.isv/questions/index.html
deleted file mode 100644
index 5f19919..0000000
--- a/bundles/org.eclipse.platform.doc.isv/questions/index.html
+++ /dev/null

@@ -1,118 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   
-   <LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Platform questions index</title>
-</head>
-<body>
-
-<h1>
-Platform questions index</h1>
-<h3>Getting started</h3>
-<ul>
-  <li><a href="../samples/samples.html">How do I install the examples?</a></li>
-</ul>
-<h3>Core runtime</h3>
-<ul>
-  <li><a href="../guide/arch.htm">What is an extension point?&nbsp; an
-    extension?</a></li>
- <li><a href="../reference/misc/plugin_manifest.html">What is the formal definition
-    for the manifest file?</a></li>
-  <li><a href="../guide/product_def_nl.htm">Where do I put translated files for
-    NLS?</a></li>
-</ul>
-<h3>Resources</h3>
-<ul>
-  <li><a href="../guide/resInt_workspace.htm">What is a workspace?</a>&nbsp;&nbsp;</li>
-  <li><a href="../guide/resInt.htm">What is a resource?</a></li>
-  <li><a href="../guide/resInt_properties.htm">What are resource properties?</a></li>
-  <li><a href="../guide/resAdv_saving.htm">How can I save my plug-in's
-    information when the workspace is saved?</a></li>
-  <li><a href="../guide/resAdv_events.htm">How do I know what changes are being
-    made to resources in the workspace?</a></li>
-  <li><a href="../guide/resAdv_markers.htm">How do I use markers?</a></li>
-  <li><a href="../guide/resAdv_markers.htm#resAdv_markers_extending">How do I
-    define my own marker?</a></li>
-  <li><a href="../guide/resAdv_natures.htm">What is a project nature?</a></li>
-  <li><a href="../guide/resAdv_builders.htm">How do I set up an incremental
-    project builder?</a></li>
-</ul>
-<h3>New file types in the UI</h3>
-<ul>
-  <li><a href="../guide/workbench_basicext_editors.htm">How do I set up an
-    editor for a particular file extension?</a></li>
-  <li><a href="../guide/preferences_prop_contribute.htm">How do I add a properties page for
-    a resource?</a></li>
-  <li><a href="../guide/dialogs_wizards_newWizards.htm">How do I add a new
-    resource wizard to the workbench?</a></li>
-  <li><a href="../guide/workbench_advext_decorators.htm">How do I provide
-    special icons for my new file type?</a></li>
-</ul>
-<h3>Workbench UI</h3>
-<ul>
-  <li><a href="../guide/workbench_structure.htm">What is a view?&nbsp; an
-    editor?&nbsp; a page?</a></li>
-  <li><a href="../guide/workbench_advext_perspectives.htm">What is a
-    perspective?&nbsp; How do I define one?</a></li>
-  <li><a href="../guide/workbench_structure.htm#views_and_editors">When do I
-    want to build a view vs. an editor?</a></li>
-  <li><a href="../guide/editors_workbench_outliner.htm">How do I customize a
-    content outliner for an editor?</a></li>
-  <li><a href="../guide/preferences_prefs.htm">How do I add a page to the
-    preferences dialog?</a></li>
-  <li><a href="../guide/workbench_basicext.htm">Where should I start learning
-    how to extend the workbench UI?</a></li>
-  <li><a href="../reference/extension-points/index.html">What extension points
-    are defined by the workbench UI?</a></li>
-  <li><a href="../guide/workbench_menus.htm">How do I add a menu to the
-    workbench?</a></li>
-  <li><a HREF="../guide/workbench_menupaths.htm">How do I
-    specify menu and toolbar paths?</a></li>
-  <li><a href="../guide/wrkAdv_retarget.htm">How do I implement common actions
-    like cut/copy/paste?</a></li>
-  <li><a href="../guide/jface_resources.htm">How should I manage the icons in my
-    plug-in?</a></li>
-  <li><a href="../guide/dialogs_standard.htm">How do I build an error or message
-    dialog?</a></li>
-  <li><a href="../guide/dialogs_applications.htm">How do I implement a simple
-    dialog of my own?</a></li>
-  <li><a href="../guide/dialogs_settings.htm">How should I remember the user
-    settings in a dialog?</a></li>
-  <li><a href="../guide/jface_viewers.htm">Why would I want a viewer instead of
-    an SWT widget?</a></li>
-  <li><a href="../guide/editors_jface.htm">How should I start learning about the
-    text framework?</a></li>
-  <li><a href="../guide/dialogs_wizards_wizarddialogs.htm">How do I launch a
-    wizard if I'm not adding it as a workbench extension?</a></li>
-  <li><a href="../guide/dialogs_wizards_multipage.htm">How do I build a wizard
-    with multiple pages?</a></li>
-  <li><a href="../guide/swt_widgets_controls.htm">What widgets are available in
-    SWT?</a></li>
-  <li><a href="../guide/swt_layouts.htm">How do I implement an SWT layout?</a></li>
-  <li><a href="http://www.eclipse.org/articles/Article-Writing%20Your%20Own%20Widget/Writing%20Your%20Own%20Widget.htm">How do I implement an
-    SWT native
-    widget?</a></li>
-  <li><a href="../guide/swt_widgets_custom.htm">How do I implement a custom
-    widget in SWT?</a></li>
-  <li><a href="../guide/swt_graphics.htm">How do I draw my own graphics?</a></li>
-</ul>
-<h3>Installation and upgrade</h3>
-<ul>
-  <li><a href="../guide/product_configproduct.htm">How do I configure my own splash
-    screens and product name?</a></li>
-  <li><a href="../guide/product_def_feature.htm">What is a feature?</a></li>
-  <li><a href="../reference/misc/feature_archive.html">How do I package a
-    feature so it will work with the update manager?</a></li>
-  <li><a href="../guide/workbench_advext_intro.htm">How do I configure a custom
-    welcome (intro) page?</a></li>
-  <li><a href="../reference/misc/eclipse-install.html">How do I install an
-    Eclipse based product?</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/.cvsignore b/bundles/org.eclipse.platform.doc.isv/reference/.cvsignore
deleted file mode 100644
index eedd89b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/.cvsignore
+++ /dev/null

@@ -1 +0,0 @@
-api

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/extension-points/index.html b/bundles/org.eclipse.platform.doc.isv/reference/extension-points/index.html
deleted file mode 100644
index 6a20051..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/extension-points/index.html
+++ /dev/null

@@ -1,200 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <title>Platform Extension Points</title>
-<LINK REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-</head>
-<body link="#0000FF" vlink="#800080">
-
-<center>
-<h1>Platform Extension Points
-</h1></center>
-
-The following extension points can be used to extend the capabilities
-of the platform infrastructure:
-<h3><a name="runtime"></a>Platform runtime</h3>
-<ul>
-  <li><a href="org_eclipse_core_runtime_adapters.html">org.eclipse.core.runtime.adapters</a></li>
-  <li><a href="org_eclipse_core_runtime_applications.html">org.eclipse.core.runtime.applications</a></li>
-  <li><a href="org_eclipse_core_runtime_contentTypes.html">org.eclipse.core.runtime.contentTypes</a></li>
-  <li><a href="org_eclipse_core_runtime_preferences.html">org.eclipse.core.runtime.preferences</a></li>
-  <li><a href="org_eclipse_core_runtime_products.html">org.eclipse.core.runtime.products</a></li>
-</ul>
-<h3><a name="workspace"></a>Workspace</h3>
-<ul>
-  <li><a href="org_eclipse_core_resources_builders.html">org.eclipse.core.resources.builders</a>
-  </li>
-   <li><a href="org_eclipse_core_resources_fileModificationValidator.html">org.eclipse.core.resources.fileModificationValidator</a>
-  </li>
-  <li><a href="org_eclipse_core_resources_markers.html">org.eclipse.core.resources.markers</a></li>
-  <li><a href="org_eclipse_core_resources_moveDeleteHook.html">org.eclipse.core.resources.moveDeleteHook</a></li>
-  <li><a href="org_eclipse_core_resources_natures.html">org.eclipse.core.resources.natures</a></li>
-  <li><a href="org_eclipse_core_resources_refreshProviders.html">org.eclipse.core.resources.refreshProviders</a></li>
-  <li><a href="org_eclipse_core_resources_teamHook.html">org.eclipse.core.resources.teamHook</a></li>
-  <li><a href="org_eclipse_core_filesystem_filesystems.html">org.eclipse.core.filesystem.filesystems</a></li>
-</ul>
-
-<h3><a name="text"></a>Platform text</h3>
-<ul>
-	<li><a href="org_eclipse_core_filebuffers_annotationModelCreation.html">org.eclipse.core.filebuffers.annotationModelCreation</a></li>
-	<li><a href="org_eclipse_core_filebuffers_documentCreation.html">org.eclipse.core.filebuffers.documentCreation</a></li>
-	<li><a href="org_eclipse_core_filebuffers_documentSetup.html">org.eclipse.core.filebuffers.documentSetup</a></li>
-	<li><a href="org_eclipse_ui_editors_annotationTypes.html">org.eclipse.ui.editors.annotationTypes</a></li>
-	<li><a href="org_eclipse_ui_editors_documentProviders.html">org.eclipse.ui.editors.documentProviders</a></li>
-	<li><a href="org_eclipse_ui_editors_markerAnnotationSpecification.html">org.eclipse.ui.editors.markerAnnotationSpecification</a></li>
-	<li><a href="org_eclipse_ui_editors_markerUpdaters.html">org.eclipse.ui.editors.markerUpdaters</a></li>
-	<li><a href="org_eclipse_ui_editors_templates.html">org.eclipse.ui.editors.templates</a></li>
-	<li><a href="org_eclipse_ui_workbench_texteditor_quickDiffReferenceProvider.html">org.eclipse.ui.workbench.texteditor.quickDiffReferenceProvider</a></li>
-	<li><a href="org_eclipse_ui_workbench_texteditor_spellingEngine.html">org.eclipse.ui.workbench.texteditor.spellingEngine</a></li>
-</ul>
-
-<h3><a name="workbench"></a>Workbench</h3>
-<ul>
-  <li><a href="org_eclipse_ui_acceleratorConfigurations.html">org.eclipse.ui.acceleratorConfigurations</a></li>
-  <li><a href="org_eclipse_ui_acceleratorScopes.html">org.eclipse.ui.acceleratorScopes</a></li>
-  <li><a href="org_eclipse_ui_acceleratorSets.html">org.eclipse.ui.acceleratorSets</a></li>
-  <li><a href="org_eclipse_ui_actionDefinitions.html">org.eclipse.ui.actionDefinitions</a></li>
-  <li><a href="org_eclipse_ui_actionSetPartAssociations.html">org.eclipse.ui.actionSetPartAssociations</a></li>
-  <li><a href="org_eclipse_ui_actionSets.html">org.eclipse.ui.actionSets</a></li>
-  <li><a href="org_eclipse_ui_activities.html">org.eclipse.ui.activities</a></li>
-  <li><a href="org_eclipse_ui_activitySupport.html">org.eclipse.ui.activitySupport</a></li>
-  <li><a href="org_eclipse_ui_bindings.html">org.eclipse.ui.bindings</a></li>
-  <li><a href="org_eclipse_ui_browserSupport.html">org.eclipse.ui.browserSupport</a></li>
-  <li><a href="org_eclipse_ui_cheatsheets_cheatSheetContent.html">org.eclipse.ui.cheatsheets.cheatSheetContent</a></li>
-  <li><a href="org_eclipse_ui_cheatsheets_cheatSheetItemExtension.html">org.eclipse.ui.cheatsheets.cheatSheetItemExtension</a></li>
-  <li><a href="org_eclipse_ui_commands.html">org.eclipse.ui.commands</a></li>
-  <li><a href="org_eclipse_ui_commandImages.html">org.eclipse.ui.commandImages</a></li>
-  <li><a href="org_eclipse_ui_contexts.html">org.eclipse.ui.contexts</a></li>
-  <li><a href="org_eclipse_ui_decorators.html">org.eclipse.ui.decorators</a></li>
-  <li><a href="org_eclipse_ui_dropActions.html">org.eclipse.ui.dropActions</a></li>
-  <li><a href="org_eclipse_ui_editorActions.html">org.eclipse.ui.editorActions</a></li>
-  <li><a href="org_eclipse_ui_editors.html">org.eclipse.ui.editors</a></li>
-  <li><a href="org_eclipse_ui_elementFactories.html">org.eclipse.ui.elementFactories</a></li>
-  <li><a href="org_eclipse_ui_encodings.html">org.eclipse.ui.encodings</a></li>
-  <li><a href="org_eclipse_ui_exportWizards.html">org.eclipse.ui.exportWizards</a></li>
-  <li><a href="org_eclipse_ui_fontDefinitions.html">org.eclipse.ui.fontDefinitions</a></li>
-  <li><a href="org_eclipse_ui_handlers.html">org.eclipse.ui.handlers</a></li>
-  <li><a href="org_eclipse_ui_helpSupport.html">org.eclipse.ui.helpSupport</a></li>
-  <li><a href="org_eclipse_ui_ide_markerHelp.html">org.eclipse.ui.ide.markerHelp</a></li>
-  <li><a href="org_eclipse_ui_ide_markerImageProviders.html">org.eclipse.ui.ide.markerImageProviders</a></li>
-  <li><a href="org_eclipse_ui_ide_markerResolution.html">org.eclipse.ui.ide.markerResolution</a></li>
-  <li><a href="org_eclipse_ui_ide_markerSupport.html">org.eclipse.ui.ide.markerSupport</a></li>
-  <li><a href="org_eclipse_ui_navigator_linkHelper.html">org.eclipse.ui.navigator.linkHelper</a></li>    
-  <li><a href="org_eclipse_ui_navigator_navigatorContent.html">org.eclipse.ui.navigator.navigatorContent</a></li>  
-  <li><a href="org_eclipse_ui_navigator_viewer.html">org.eclipse.ui.navigator.viewer</a></li>
-  <li><a href="org_eclipse_ui_ide_projectNatureImages.html">org.eclipse.ui.ide.projectNatureImages</a></li>
-  <li><a href="org_eclipse_ui_ide_resourceFilters.html">org.eclipse.ui.ide.resourceFilters</a></li>
-  <li><a href="org_eclipse_ui_importWizards.html">org.eclipse.ui.importWizards</a></li>
-  <li><a href="org_eclipse_ui_intro.html">org.eclipse.ui.intro</a></li>
-  <li><a href="org_eclipse_ui_intro_config.html">org.eclipse.ui.intro.config</a></li>
-  <li><a href="org_eclipse_ui_intro_configExtension.html">org.eclipse.ui.intro.configExtension</a></li>
-  <li><a href="org_eclipse_ui_keywords.html">org.eclipse.ui.keywords</a></li>
-  <li><a href="org_eclipse_ui_menus.html">org.eclipse.ui.menus</a></li>
-  <li><a href="org_eclipse_ui_newWizards.html">org.eclipse.ui.newWizards</a></li>
-  <li><a href="org_eclipse_ui_perspectiveExtensions.html">org.eclipse.ui.perspectiveExtensions</a></li>
-  <li><a href="org_eclipse_ui_perspectives.html">org.eclipse.ui.perspectives</a></li>
-  <li><a href="org_eclipse_ui_popupMenus.html">org.eclipse.ui.popupMenus</a></li>
-  <li><a href="org_eclipse_ui_preferencePages.html">org.eclipse.ui.preferencePages</a></li>
-  <li><a href="org_eclipse_ui_preferenceTransfer.html">org.eclipse.ui.preferenceTransfer</a></li>
-  <li><a href="org_eclipse_ui_presentationFactories.html">org.eclipse.ui.presentationFactories</a></li>
-  <li><a href="org_eclipse_ui_propertyPages.html">org.eclipse.ui.propertyPages</a></li>
-  <li><a href="org_eclipse_ui_startup.html">org.eclipse.ui.startup</a></li>
-  <li><a href="org_eclipse_ui_systemSummarySections.html">org.eclipse.ui.systemSummarySections</a></li>
-  <li><a href="org_eclipse_ui_themes.html">org.eclipse.ui.themes</a></li>
-  <li><a href="org_eclipse_ui_viewActions.html">org.eclipse.ui.viewActions</a></li>
-  <li><a href="org_eclipse_ui_views.html">org.eclipse.ui.views</a></li>
-  <li><a href="org_eclipse_ui_views_properties_tabbed_propertyContributor.html">org.eclipse.ui.views.properties.tabbed.propertyContributor.html</a></li>
-  <li><a href="org_eclipse_ui_views_properties_tabbed_propertySections.html">org.eclipse.ui.views.properties.tabbed.propertySections.html</a></li>
-  <li><a href="org_eclipse_ui_views_properties_tabbed_propertyTabs.html">org.eclipse.ui.views.properties.tabbed.propertyTabs.html</a></li>
-  <li><a href="org_eclipse_ui_workingSets.html">org.eclipse.ui.workingSets</a></li>
-</ul>
-<h3><a name="team"></a>Team</h3>
-<ul>
-  <li><a href="org_eclipse_team_core_fileTypes.html">org.eclipse.team.core.fileTypes</a></li>
-  <li><a href="org_eclipse_team_core_ignore.html">org.eclipse.team.core.ignore</a></li>
-  <li><a href="org_eclipse_team_core_projectSets.html">org.eclipse.team.core.projectSets</a></li>
-  <li><a href="org_eclipse_team_core_repository.html">org.eclipse.team.core.repository</a></li>
-  <li><a href="org_eclipse_team_ui_configurationWizards.html">org.eclipse.team.ui.configurationWizards</a></li>
-  <li><a href="org_eclipse_team_ui_synchronizeParticipants.html">org.eclipse.team.ui.synchronizeParticipants</a></li>
-  <li><a href="org_eclipse_team_ui_synchronizeWizards.html">org.eclipse.team.ui.synchronizeWizards</a></li>
- </ul>
-<h3><a name="debug"></a>Debug</h3>
-<ul>
-  <li><a href="org_eclipse_debug_core_breakpoints.html">org.eclipse.debug.core.breakpoints</a></li>
-  <li><a href="org_eclipse_debug_core_launchConfigurationComparators.html">org.eclipse.debug.core.launchConfigurationComparators</a></li>
-  <li><a href="org_eclipse_debug_core_launchConfigurationTypes.html">org.eclipse.debug.core.launchConfigurationTypes</a></li>
-  <li><a href="org_eclipse_debug_core_launchDelegates.html">org.eclipse.debug.core.launchDelegates</a></li>
-  <li><a href="org_eclipse_debug_core_launchers.html">org.eclipse.debug.core.launchers</a></li>
-  <li><a href="org_eclipse_debug_core_launchModes.html">org.eclipse.debug.core.launchModes</a></li>
-  <li><a href="org_eclipse_debug_core_logicalStructureTypes.html">org.eclipse.debug.core.logicalStructureTypes</a></li>
-  <li><a href="org_eclipse_debug_core_processFactories.html">org.eclipse.debug.core.processFactories</a></li>
-  <li><a href="org_eclipse_debug_core_sourceContainerTypes.html">org.eclipse.debug.core.sourceContainerTypes</a></li>
-  <li><a href="org_eclipse_debug_core_sourceLocators.html">org.eclipse.debug.core.sourceLocators</a></li>
-  <li><a href="org_eclipse_debug_core_sourcePathComputers.html">org.eclipse.debug.core.sourcePathComputers</a></li>
-  <li><a href="org_eclipse_debug_core_statusHandlers.html">org.eclipse.debug.core.statusHandlers</a></li>
-  <li><a href="org_eclipse_debug_core_watchExpressionDelegates.html">org.eclipse.debug.core.watchExpressionDelegates</a></li>
-  <li><a href="org_eclipse_debug_ui_breakpointOrganizers.html">org.eclipse.debug.ui.breakpointOrganizers</a></li>  
-  <li><a href="org_eclipse_debug_ui_consoleColorProviders.html">org.eclipse.debug.ui.consoleColorProviders</a></li>
-  <li><a href="org_eclipse_debug_ui_consoleLineTrackers.html">org.eclipse.debug.ui.consoleLineTrackers</a></li>
-  <li><a href="org_eclipse_debug_ui_contextViewBindings.html">org.eclipse.debug.ui.contextViewBindings</a></li>
-  <li><a href="org_eclipse_debug_ui_debugModelContextBindings.html">org.eclipse.debug.ui.debugModelContextBindings</a></li>
-  <li><a href="org_eclipse_debug_ui_debugModelPresentations.html">org.eclipse.debug.ui.debugModelPresentations</a></li>
-  <li><a href="org_eclipse_debug_ui_launchConfigurationTabGroups.html">org.eclipse.debug.ui.launchConfigurationTabGroups</a></li>
-  <li><a href="org_eclipse_debug_ui_launchConfigurationTypeImages.html">org.eclipse.debug.ui.launchConfigurationTypeImages</a></li>
-  <li><a href="org_eclipse_debug_ui_launchGroups.html">org.eclipse.debug.ui.launchGroups</a></li>
-  <li><a href="org_eclipse_debug_ui_launchShortcuts.html">org.eclipse.debug.ui.launchShortcuts</a></li>
-  <li><a href="org_eclipse_debug_ui_memoryRenderings.html">org.eclipse.debug.ui.memoryRenderings</a></li>    
-  <li><a href="org_eclipse_debug_ui_sourceContainerPresentations.html">org.eclipse.debug.ui.sourceContainerPresentations</a></li>
-  <li><a href="org_eclipse_debug_ui_stringVariablePresentations.html">org.eclipse.debug.ui.stringVariablePresentations</a></li>
-  <li><a href="org_eclipse_debug_ui_variableValueEditors.html">org.eclipse.debug.ui.variableValueEditors</a></li>      
-</ul>
-<h3><a name="console"></a>Console</h3>
-<ul>
-  <li><a href="org_eclipse_ui_console_consoleFactories.html">org.eclipse.ui.console.consoleFactories</a></li>
-  <li><a href="org_eclipse_ui_console_consolePageParticipants.html">org.eclipse.ui.console.consolePageParticipants</a></li>
-  <li><a href="org_eclipse_ui_console_consolePatternMatchListeners.html">org.eclipse.ui.console.consolePatternMatchListeners</a></li>
-</ul>
-<h3><a name="help"></a>Help</h3>
-<ul>
-  <li><a href="org_eclipse_help_contentProducer.html">org.eclipse.help.contentProducer</a></li>
-  <li><a href="org_eclipse_help_contexts.html">org.eclipse.help.contexts</a></li>
-  <li><a href="org_eclipse_help_toc.html">org.eclipse.help.toc</a></li>
-  <li><a href="org_eclipse_help_base_browser.html">org.eclipse.help.base.browser</a></li>
-  <li><a href="org_eclipse_help_base_luceneAnalyzer.html">org.eclipse.help.base.luceneAnalyzer</a></li>
-</ul>
-<h3><a name="other"></a>Other</h3>
-<ul>
-  <li><a href="org_eclipse_ant_core_antProperties.html">org.eclipse.ant.core.antProperties</a></li>
-  <li><a href="org_eclipse_ant_core_antTasks.html">org.eclipse.ant.core.antTasks</a></li>
-  <li><a href="org_eclipse_ant_core_antTypes.html">org.eclipse.ant.core.antTypes</a></li>
-  <li><a href="org_eclipse_ant_core_extraClasspathEntries.html">org.eclipse.ant.core.extraClasspathEntries</a></li>
-  <li><a href="org_eclipse_compare_contentMergeViewers.html">org.eclipse.compare.contentMergeViewers</a></li>
-  <li><a href="org_eclipse_compare_contentViewers.html">org.eclipse.compare.contentViewers</a></li>
-  <li><a href="org_eclipse_compare_streamMergers.html">org.eclipse.compare.streamMergers</a></li>
-  <li><a href="org_eclipse_compare_structureCreators.html">org.eclipse.compare.structureCreators</a></li>
-  <li><a href="org_eclipse_compare_structureMergeViewers.html">org.eclipse.compare.structureMergeViewers</a></li>
-  <li><a href="org_eclipse_core_expressions_propertyTesters.html">org.eclipse.core.expressions.propertyTesters</a></li>
-  <li><a href="org_eclipse_core_variables_dynamicVariables.html">org.eclipse.core.variables.dynamicVariables</a></li>
-  <li><a href="org_eclipse_core_variables_valueVariables.html">org.eclipse.core.variables.valueVariables</a></li>
-  <li><a href="org_eclipse_ltk_core_refactoring_copyParticipants.html">org.eclipse.ltk.core.refactoring.copyParticipants</a></li>
-  <li><a href="org_eclipse_ltk_core_refactoring_createParticipants.html">org.eclipse.ltk.core.refactoring.createParticipants</a></li>
-  <li><a href="org_eclipse_ltk_core_refactoring_deleteParticipants.html">org.eclipse.ltk.core.refactoring.deleteParticipants</a></li>
-  <li><a href="org_eclipse_ltk_core_refactoring_moveParticipants.html">org.eclipse.ltk.core.refactoring.moveParticipants</a></li>
-  <li><a href="org_eclipse_ltk_core_refactoring_renameParticipants.html">org.eclipse.ltk.core.refactoring.renameParticipants</a></li>
-  <li><a href="org_eclipse_ltk_ui_refactoring_changePreviewViewers.html">org.eclipse.ltk.ui.refactoring.changePreviewViewers</a></li>
-  <li><a href="org_eclipse_ltk_ui_refactoring_statusContextViewers.html">org.eclipse.ltk.ui.refactoring.statusContextViewers</a></li>
-  <li><a href="org_eclipse_search_searchPages.html">org.eclipse.search.searchPages</a></li>
-  <li><a href="org_eclipse_search_searchResultSorters.html">org.eclipse.search.searchResultSorters</a></li>
-  <li><a href="org_eclipse_search_searchResultViewPages.html">org.eclipse.search.searchResultViewPages</a></li>
-  <li><a href="org_eclipse_ui_externaltools_configurationDuplicationMaps.html">org.eclipse.ui.externaltools.configurationDuplicationMaps</a></li>
-  <li><a href="org_eclipse_update_core_featureTypes.html">org.eclipse.update.core.featureTypes</a></li>
-  <li><a href="org_eclipse_update_core_installHandlers.html">org.eclipse.update.core.installHandlers</a></li>
-  <li><a href="org_eclipse_update_core_siteTypes.html">org.eclipse.update.core.siteTypes</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/Idea.jpg b/bundles/org.eclipse.platform.doc.isv/reference/misc/Idea.jpg
deleted file mode 100644
index 119ce70..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/Idea.jpg
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/about_customization.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/about_customization.html
deleted file mode 100644
index b098ed9..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/about_customization.html
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>About.ini File Format</title>
-</head>
-
-<body>
-
-<h1>About.ini File Format</h1>
-<p>Last revised March 25, 2003 for Eclipse 2.1</p>
-<p>A feature's &quot;about&quot; information is given by properties in the
-&quot;<code>about.ini</code>&quot; file located within the feature's <i>plug-in</i>.
-This is a <a href="http://java.sun.com/j2se/1.3/docs/api/java/util/Properties.html">java.io.Properties</a>
-format file (ISO 8859-1 character encoding with \u<i>xxxx </i>Unicode escapes),
-with the following keys:</p>
-<ul>
-  <li>&quot;<code>aboutText</code>&quot; - A multi-line text description of the
-    feature containing copyright, license terms, license registration info, etc.
-    URLs found in text are presented as links. Line breaks are indicated by
-    &quot;<code>\n</code>&quot;; lines should be no longer than 75 characters
-    each, and there is a limit of 15 lines. This information is shown in the
-    main &quot;about&quot; dialog (used in conjunction with a half-sized image),
-    and on the secondary &quot;about&quot; dialog describing individuals
-    feature. All features are required to have this property.</li>
-  <li>&quot;<code>windowImage</code>&quot; - A 16x16 pixel color image used to
-    brand windows created by a product. The value of this property is a
-    plug-in-relative path to an image file. This property is only required for
-    primary features; other features may omit it.</li>
-  <li>&quot;<code>featureImage</code>&quot; - A 32x32 pixel color image used as
-    an icon for this feature. The value of this property is a plug-in-relative
-    path to an image file. This image is shown on the &quot;about&quot; dialog
-    describing individual features, and is also used on the main
-    &quot;about&quot; dialog to indicate that the feature is present. This
-    property is optional. Related features supplied by a single provider should
-    contain copies of the identical image file; this allows duplicate images to
-    be eliminated.</li>
-  <li>&quot;<code>aboutImage</code>&quot; - A large color image that appears in
-    the main &quot;about&quot; dialog for a product. The value of this property
-    is a plug-in-relative path to an image file. This property is only required
-    for primary features; other features should omit it. Both graphic-and-text,
-    and graphic only layouts are supported, depending on the size of image
-    provided. A half-size image of up to 250 pixels wide by 330 pixels high is
-    shown on the main &quot;about&quot; dialog with text (&quot;<code>aboutText</code>&quot;
-    property) beside it. A full-size image of up to 500 pixels wide by 330
-    pixels high is shown without text.</li>
-  <li>&quot;<code>welcomePage</code>&quot;&nbsp; - A welcome page. The value of
-    this property is a plug-in-relative path to an XML-format file containing
-    the feature's welcome page. This property is recommended for all major
-    features; other features may omit it.</li>
-  <li>&quot;<code>welcomePerspective</code>&quot;&nbsp; - The preferred
-    perspective in which to show the welcome page. The value of this property is
-    a workbench perspective id. This property is recommended for features with
-    welcome pages that show better in the context of the feature's views and
-    editors. Features that do not have welcome pages, or have no strong opinion
-    where the welcome pages is shown, should omit it.</li>
-  <li>&quot;<code>appName</code>&quot; - A short, non-translatable string used to associate a name
-    with the application on platforms where this makes sense. In operating
-    environments with the Motif window system, the value is used for Motif
-    resource lookup (see xrdb and related). In addition, on the CDE window
-    manager (used on Solaris and AIX), this is the name which shows up under the
-    icon for windows which are minimized to the desktop. This property is
-    required for primary features; other features may omit it.</li>
-  <li>&quot;<code>tipsAndTricksHref</code>&quot;&nbsp; - Tips and tricks section
-    of help documentation. The value of this property is a reference to a help
-    book containing the feature's tips and trick section; for example, <code>tipsAndTricksHref=/org.eclipse.jdt.doc.user/tips/jdt_tips.html</code>.
-    This property is recommended for all major features; other features may omit
-    it.</li>
-</ul>
-
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/api-usage-rules.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/api-usage-rules.html
deleted file mode 100644
index eebf43b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/api-usage-rules.html
+++ /dev/null

@@ -1,339 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Eclipse Platform API - Rules of Engagement</title>
-  
-
-</head>
-<body>
-
-<h1>
-Eclipse platform<br>
-API rules of engagement</h1>
-<i><font size=-1>Version 0.15 - Last revised 12:00 May 30, 2001</font></i>
-<p>Here are the rules of engagement for clients of the Eclipse platform
-API (and other components).</p>
-<h2>
-What it means to be API</h2>
-<p>The Eclipse platform defines API elements for use by its clients, namely
-ISVs writing plug-ins. These plug-ins may in turn define API elements for
-their clients, and so on. API elements are the public face: they carry
-a specification about what they are supposed to do, and about how they
-are intended to be used. API elements are supported: the Eclipse platform
-team will fix implementation bugs where there is a deviation from the specified
-behavior. Since there is often a high cost associated with breaking API
-changes, the Eclipse platform team will also try to evolve API elements
-gracefully through successive major releases.</p>
-<h2>
-How to tell API from non-API</h2>
-<p>By their very nature, API elements are documented and have a specification,
-in contrast to non-API elements which are internal implementation details
-usually without published documentation or specifications. So if you cannot
-find the documentation for something, that's usually a good indicator that
-it's not API.</p>
-<p>To try to draw the line more starkly, the code base for the platform
-is separated into API and non-API packages, with all API elements being
-declared in designated API packages.
-<ul>
-<li>
-<b>API package</b> - a Java package that contains at least one API class
-or API interface. The names of API packages are advertised in the documentation
-for that component; where feasible, all other packages containing only
-implementation details have "internal" in the package name. The names of
-API packages may legitimately appear in client code. For the Eclipse platform
-proper, these are:</li>
-
-</ul><ul>
-<li>
-<tt>org.eclipse.foo.*</tt> - for example, <tt>org.eclipse.swt.widgets</tt>,
-<tt>org.eclipse.ui</tt>,
-or <tt>org.eclipse.core.runtime</tt></li>
-
-<li>
-<tt>org.eclipse.foo.internal.*</tt> - not API; internal implementation
-packages</li>
-
-<li>
-<tt>org.eclipse.foo.examples.*</tt> - not API; these are examples</li>
-
-<li>
-<tt>org.eclipse.foo.tests.*</tt> - not API; these are test suites</li>
-</ul>
-<ul>
-<li>
-<b>API class or interface</b> - a <tt>public</tt> class or interface in
-an API package, or a <tt>public</tt> or <tt>protected</tt> class or interface
-member declared in, or inherited by, some other API class or interface.
-The names of API classes and interfaces may legitimately appear in client
-code.</li>
-
-<li>
-<b>API method or constructor</b> - a <tt>public</tt> or <tt>protected</tt>
-method or constructor either declared in, or inherited by, an API class
-or interface. The names of API methods may legitimately appear in client
-code.</li>
-
-<li>
-<b>API field</b> - a <tt>public</tt> or <tt>protected</tt> field either
-declared in, or inherited by, an API class or interface. The names of API
-fields may legitimately appear in client code.</li>
-</ul>
-Everything else is considered internal implementation detail and off limits
-to all clients. Legitimate client code must never reference the names of
-non-API elements (not even using Java reflection). In some cases, the Java
-language's name accessibility rules are used to disallow illegal references.
-However, there are many cases where this is simply not possible. Observing
-this one simple rule avoids the problem completely:
-<ul>
-<li>
-<b>Stick to officially documented APIs. </b>Only reference packages that
-are documented in the <b><i>published API Javadoc</i></b> for the component.
-Never reference a package belonging to another component that has "internal"
-in its name---these are never API. Never reference a package for which
-there is no published API Javadoc---these are not API either.</li>
-</ul>
-
-<h2>
-General rules</h2>
-The specification of API elements is generated from Javadoc comments in
-the element's Java source code. For some types of elements, the specification
-is in the form of a contract. For example, in the case of methods, the
-contract is between two parties, the caller of the method and the implementor
-of the method. The fundamental ground rule is:
-<ul>
-<li>
-<b>Honor all contracts.</b> The contracts are described in the published
-Javadoc for the API elements you are using.</li>
-</ul>
-The term "must", when used in an API contract, means that it is incumbent
-on the party to ensure that the condition would always be met; any failure
-to do so would be considered a programming error with unspecified (and
-perhaps unpredictable) consequences.
-<ul>
-<li>
-<b>You must honor "must". </b>Pay especially close heed to conditions where
-"must" is used.</li>
-</ul>
-Other common sense rules:
-<ul>
-<li>
-<b>Do not rely on incidental behavior. </b>Incidental behavior is behavior
-observed by experiment or in practice, but which is not guaranteed by any
-API specification.</li>
-
-<li>
-<b>Do not treat null as an object.</b> Null is more the lack of an object.
-Assume everything is non-null unless the API specification says otherwise.</li>
-
-<li>
-<b>Do not try to cheat with Java reflection.</b> Using Java reflection
-to circumvent Java compiler checking buys you nothing more. There are no
-additional API contracts for uses of reflection; reflection simply increases
-the likelihood of relying on unspecified behavior and internal implementation
-detail.</li>
-
-<li>
-<b>Use your own packages. </b>Do not declare code in a package belonging
-to another component. Always declare your own code in your own packages.</li>
-</ul>
-
-<h2>
-Calling public API methods</h2>
-For most clients, the bulk of the Eclipse API takes the form of public
-methods on API interfaces or classes, provided for the client to call when
-appropriate.
-<ul>
-<li>
-<b>Ensure preconditions.</b> Do ensure that an API method's preconditions
-are met before calling the method. Conversely, the caller may safely assume
-that the method's postconditions will have been achieved immediately upon
-return from the call.</li>
-
-<li>
-<b>Null parameters.</b> Do not pass null as a parameter to an API method
-unless the parameter is explicitly documented as allowing null. This is
-perhaps the most frequently made programming error.</li>
-
-<li>
-<b>Restricted callers.</b> Do not call an API method that is documented
-as available only to certain callers unless you're one of them. In some
-situations, methods need to be part of the public API for the benefit of
-a certain class of callers (often internal); calling one of these methods
-at the wrong time has unspecified (and perhaps unpredictable) consequences.</li>
-
-<li>
-<b>Debugging methods.</b> Do not call an API method labelled "for debugging
-purposes only". For example, most <tt>toString()</tt> methods are in this
-category.</li>
-
-<li>
-<b>Parameter capture.</b> Do not pass an array, collection, or other mutable
-object as a parameter to an API method and then modify the object passed
-in. This is just asking for trouble.</li>
-</ul>
-
-<h2>
-Instantiating platform API classes</h2>
-Not all concrete API classes are intended to be instantiated by just anyone.
-API classes have an instantiation contract indicating the terms under which
-instances may be created. The contract may also cover things like residual
-initialization responsibilities (for example, configuring a certain property
-before the instance is fully active) and associated lifecycle responsibilities
-(for example, calling <tt>dispose()</tt> to free up OS resources hung on
-to by the instance). Classes that are designed to be instantiated by clients
-are explicitly flagged in the Javadoc class comment (with words like "Clients
-may instantiate.").
-<ul>
-<li>
-<b>Restricted instantiators.</b> Do not instantiate an API class that is
-documented as available only to certain parties unless you're one of them.
-In some situations, classes need to be part of the public API for the benefit
-of a certain party (often internal); instantiating one of these classes
-incorrectly has unspecified (and perhaps unpredictable) consequences.</li>
-</ul>
-
-<h2>
-Subclassing platform API classes</h2>
-Only a subset of the API classes were designed to be subclassed. API classes
-have a subclass contract indicating the terms under which subclasses may
-be declared. This contract also covers initialization responsibilities
-and lifecycle responsibilities. Classes that are designed to be subclassed
-by clients are explicitly flagged in the Javadoc class comment (with words
-like "Clients may subclass.").
-<ul>
-<li>
-<b>Restricted subclassers.</b> Do not subclass an API class that is not
-intended to be subclassed. Treat these classes as if they had been declared
-final. (These are sometimes referred to as "soft final" classes).</li>
-</ul>
-
-<h2>
-Calling protected API methods</h2>
-Calling inherited protected and public methods from within a subclass is
-generally allowed; however, this often requires more care to correctly
-call than to call public methods from outside the hierarchy.
-<h2>
-Overriding API methods</h2>
-Only a subset of the public and protected API methods were designed to
-be overridden. Each API method has a subclass contract indicating the terms
-under which a subclass may override it. By default, overriding is not permitted.
-It is important to check the subclass contract on the actual method implementation
-being overridden; the terms of subclass contracts are not automatically
-passed along when that method is overridden.
-<ul>
-<li>
-<b>Do not override a public or protected API method unless it is explicitly
-allowed.</b> Unless otherwise indicated, treat all methods as if they had
-been declared final. (These are sometimes known as "soft final" methods).
-If the kind of overriding allowed is:
-
-<ul>
-<li>"<b>implement</b>" - the abstract method declared on the subclass must
-be implemented by a concrete subclass</li>
-<li>"<b>extend</b>" - the method declared on the subclass must invoke the
-method on the superclass (exactly once)</li>
-<li>"<b>re-implement</b>" - the method declared on the subclass must not
-invoke the method on the superclass</li>
-<li>"<b>override</b>" - the method declared on the subclass is free to
-invoke the method on the superclass as it sees fit</li></ul></li>
-
-<li>
-<b>Ensure postconditions. </b>Do ensure that any postconditions specified
-for the API method are met by the implementation upon return.</li>
-
-<li>
-<b>Proactively check preconditions. </b>Do not presume that preconditions
-specified for the API method have necessarily been met upon entry. Although
-the method implementation would be within its rights to not check specified
-preconditions, it is usually a good idea to check preconditions (when feasible
-and reasonably inexpensive) in order to blow the whistle on misbehaving
-callers.</li>
-
-<li>
-<b>Null result. </b>Do not return null as a result from an API method unless
-the result is explicitly documented (on the specifying interface or superclass)
-as allowing null.</li>
-
-<li>
-<b>Return copies. </b>Do not return an irreplaceable array, collection,
-or other mutable object as the result from an API method. Always return
-a copy to avoid trouble from callers that might modify the object.</li>
-</ul>
-
-<h2>
-Implementing platform API interfaces</h2>
-Only a subset of the API interfaces were designed to be implemented by
-clients. API interfaces have a contract indicating the terms under which
-it may be implemented. Interfaces that are designed to be implemented by
-clients are explicitly flagged in the Javadoc class comment (with words
-like "Clients may implement."). A client may declare a subinterface of
-an API interface if and only if they are allowed to implement it.
-<ul>
-<li>
-<b>Restricted implementors.</b> Do not implement an API interface that
-is documented as available only to certain parties unless you're one of
-them. In many situations, interfaces are used to hide internal implementation
-details from view.</li>
-</ul>
-
-<h2>
-Implementing public API methods</h2>
-See "Overriding API methods".
-<h2>
-Accessing fields in API classes and interfaces</h2>
-Clients may read API fields, most of which are final. Certain struct-like
-objects may have non-final public fields, which clients may read and write
-unless otherwise indicated.
-<ul>
-<li>
-<b>Null fields.</b> Do not set an API field to null unless this is explicitly
-allowed.</li>
-</ul>
-
-<h2>
-Casting objects of a known API type</h2>
-An object of a known API type may only be cast to a different API type
-(or conditionally cast using instanceof) if this is explicitly allowed
-in the API.
-<ul>
-<li>
-<b>Cast and instanceof.</b> Do not use instanceof and cast expressions
-to increase what is known about an object beyond what the API supports.
-Improper use exposes incidental implementation details not guaranteed by
-the API.</li>
-</ul>
-And, of course, casting any object to a non-API class or interface is always
-inappropriate.</p>
-<h2>
-Not following the rules</h2>
-<p>Whether done knowingly or unwittingly, there are consequences for transgressing
-the rules. It might be easier for all involved if there were API police
-that would bust you for breaking the rules. However, that is not the case.
-For the most part, API conformance operates as an honor system, with each
-client responsible for knowing the rules and adhering to them.</p>
-<p>The contracts on the API elements delimit the behavior that is supported
-and sustained. As the Eclipse platform matures and evolves, it will be
-the API contracts that guide how this evolution happens. Outside of these
-contracts, everything is unsupported and subject to change, without notice,
-and at any time (even mid-release or between different OS platforms). Client
-code that oversteps the above rules might fail on different versions and
-patch levels of the platform; or when run on different underlying OSes;
-or when run with a different mix of co-resident plug-ins; or when run with
-a different workbench perspective; and so on. Indeed, no one is even particularly
-interested in speculating exactly how any particular transgression might
-come back to bite you. To those who choose to ignore the rules, don't say
-that you weren't warned. And don't expect much more than a sympathetic
-"Told you so."</p>
-<p>On the other hand, client plug-in code that lives by the above rules
-should continue to work across different versions and patch levels of the
-platform, across different underlying OSes, and should peacefully co-exist
-with other plug-ins. If everyone plays by the rules, the Eclipse platform
-will provide a stable and supported base on which to build exciting new
-products.</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/bidi.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/bidi.html
deleted file mode 100644
index 5019512..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/bidi.html
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Bidirectional Support in Eclipse</title>
-</head>
-<BODY BGCOLOR="#ffffff">
-<h1>Bidirectional Support in the Eclipse Workbench</h1>
-<p>As of Eclipse 3.1 RC2 bidirectional support will be complete are supported 
-  in JFace and the Workbench. A bidirectional language is one that can write both 
-  right to left and left to right based on context. Eclipse will recognize Hebrew, 
-  Arabic, Farsi and Urdu as bidirectional by default.</p>
-<h2>Enabling Bidirectional Support in the SDK</h2>
-<p>The orientation of the workbench will be flipped if one of the following ways 
-  (in order of priority)</p>
-<ul>
-  <li><strong>-dir command line parameter</strong>. If the -dir command line option 
-    is used this will be the default orientation. Valid values are -dir rtl or 
-    -dir ltr.</li>
-  <li><strong>system properties</strong>. If the system property eclipse.orientation 
-    is set this will be used. The value is of the same format as -dir.</li>
-  <li><strong>-nl command line parameter</strong>. If the -nl option is used and 
-    the language is Hebrew, Arabic, Farsi or Urdu the orientation will be right 
-    to left, otherwise it will be left to right.</li>
-</ul>
-<p>These values will be used to call org.eclipse.jface.Window#setDefaultOrientation(). 
-  All subclasses of Window and the children of those windows will get the orientation 
-  specified. The default orientation is SWT#NONE.</p>
-<p>Views and editors will by default inherit the window orientation from their 
-  parent. Dialogs should inherit orientation by using the shellStyle of their 
-  parent when setting their own by calling super#getShellStyle.</p>
-<p><img src="bidi.png" alt="bidi image"></p>
-<p><strong>Figure 1 - Screen shot of right to left orientation of the resource 
-  perspective</strong></p>
-<h2>Enabling your plug-in for looking up alternate icons</h2>
-<p>In many cases your icons will not make any sense in right to left mode. In 
-  particular any icon to do with editing will have this issue.To enable lookup 
-  of images in a fragment all you need to do to nl enable $nl$ in your path and 
-  use the Platform bundle support to lookup the icons file.</p>
-<p>For example</p>
-<p>String iconPath = &quot;$nl$/icons/myicon.gif&quot;;</p>
-<p>URL url = Platform.find( Platform.getBundle(MyPluginId), new Path(iconPath));</p>
-<p>Image Descriptor descriptor = ImageDescriptor.createFromURL(url);</p>
-<p>If the icon reference is in your plugin.xml just make sure you have the $nl$ 
-  prefix on your path. If it is an extension point defined by the workbench the 
-  lookup will be handled for you. Just make sure if you create your own extension 
-  point that it loads ImageDescriptors this way.</p>
-<h2>How to choose icons to override</h2>
-<p>There is no hard and fast rules for choosing which icons to override but in 
-  general you should focus on the icons that imply a textual direction with a 
-  horizontal arrow.</p>
-
-
-</BODY></HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/bidi.png b/bundles/org.eclipse.platform.doc.isv/reference/misc/bidi.png
deleted file mode 100644
index 3265a1b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/bidi.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/buddy_loading.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/buddy_loading.html
deleted file mode 100644
index b71a816..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/buddy_loading.html
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Third party libraries and classloading</title>
-</head>
-<body>
-<h1>Third party libraries and classloading</h1>
-Because OSGi makes use of multiple classloaders, the transparent usage of extensible / configurable third party libraries 
-in eclipse requires the usage of an eclipse specific mechanism called "buddy loading". This mechanism allows a 
-bundle to indicate that it needs assistance to load classes or resources when it can not find them 
-among its prerequisites. Note that we call "extensible libraries", libraries that needs to see classes or resources provided
-by user code (for example log4j logger mechanism, hibernate,...).
-<p>
-To indicate its need for buddy loading, a bundle must modify its manifest and add the following header:</p>
-<pre>    Eclipse-BuddyPolicy: &lt;value&gt;
-</pre>
-<p>
-&lt;value&gt; refers to the policy used to look for the classes. Here are the
-supported policies:</p>
-<ul>
-  <li> registered -  indicates that the buddy mechanism will consult bundles
-that have been registered to it. Bundle willing to be registered to a particular
-  bundle add in their manifest: "Eclipse-RegisterBuddy: &lt;bundleSymbolicName&gt;";</li>
-  <li> dependent - indicates that the classes/resources will be looked up
-transitively in all the dependent of the bundle;</li>
-  <li> global - indicates that the classes/resources will be looked up in the
-global pool of exported package;</li>
-  <li> app - indicates that the application classloader will be consulted;</li>
-  <li> ext - indicates that the extensiont classloader will be consulted;</li>
-  <li> boot - indicates that the boot classloader will be consulted.</li>
-</ul>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/bundle_manifest.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/bundle_manifest.html
deleted file mode 100644
index f479daa..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/bundle_manifest.html
+++ /dev/null

@@ -1,269 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005. This page is made available under license. Full for details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>OSGi Bundle Manifest</title>
-</head>
-
-<body lang="EN-US" link=blue vlink=blue style='tab-interval:.5in'>
-
-<div class=Section1>
-
-<h1>OSGi Bundle Manifest Headers</h1>
-
-<p class=MsoNormal><span style='font-size:10.0pt'>Version 3.1 - Last revised June 20, 2005</span></p>
-
-<p>
-A bundle can carry descriptive information about itself in the manifest file 
-named META-INF/MANIFEST.MF.  The OSGi R4 Framework specification defines a set of 
-manifest headers such as Export-Package and Bundle-Classpath, which bundle developers 
-use to supply descriptive information about a bundle.  The Eclipse OSGi Framework 
-implements the complete OSGi R4 Framework specification and all of the Core Framework 
-services. The OSGi R4 Core Framework services include the following:</p>
-<ul>
-  <li>Package Admin Service Specification</li>
-  <li>URL Handlers Service Specification</li>
-  <li>Start Level Service Specification</li>
-  <li>Conditional Permission Admin Specification</li>
-  <li>Permission Admin Service Specification</li>
-</ul>
-  <p> There are a number of optional services defined in the OSGi R4 specification. 
-    The optional services are not included with the Eclipse OSGi Framework implementation. 
-    For information on OSGi R4 manifest headers and services refer to the <a href="http://eclipse.org/osgi/main.html">OSGi 
-    specifications</a>. </p>
-
-<h2>Eclipse Bundle Manifest Headers</h2>
-
-<p>
-The Eclipse OSGi Framework supports a number of additional bundle manifest headers 
-and directives.  A bundle developer may use these additional headers and directives 
-to take advantage of some additional features of the Eclipse OSGi Framework which 
-are not specified as part of a standard OSGi R4 Framework.
-</p>
-<h3>Additional Export-Package Directives</h3>
-
-<p>
-The Eclipse OSGi Framework supports additional directives on the Export-Package 
-header.  These directives are used to specify the access restriction rules of an 
-exported package.  See <a href="runtime-options.html#osgiresolvermode">osgi.resolverMode</a> 
-to configure the Eclipse OSGi Framework to enforce the access restriction rules at 
-runtime.
-</p>
-
-<h4>The x-internal Directive</h4>
-
-<p>
-The x-internal directive can be used in an Export-Package header to specify whether 
-the package is an internal package.  The Plug-in Development Environment will discourage 
-other bundles from using an internal package.  If the x-internal directive is not 
-specified then a default value of 'false' is used.  The x-internal directive must 
-use the following syntax:
-</p>
-
-<pre>
-x-internal ::= ( 'true' | 'false' )
-</pre>
-
-<p>
-The following is an example of the x-internal directive:
-</p>
-
-<pre>
-Export-Package: org.eclipse.foo.internal; x-internal:=true
-</pre>
-
-<h4>The x-friends Directive</h4>
-
-<p>
-The x-friends directive can be used in an Export-Package header to specify a list 
-of bundles which are allowed access to the package.  The Plug-in Development 
-Environment will discourage other bundles from using the package.  The x-friends 
-directive must use the following syntax:
-</p>
-
-<pre>
-x-friends ::= '&quot;' ( target-bundle ) ( ',' target-bundle ) * '&quot;'
-target-bundle ::= a bundle symbolic name
-</pre>
-
-<p>
-The following is an example of the x-friends directive:
-</p>
-
-<pre>
-Export-Package: org.eclipse.foo.formyfriends; x-friends:="org.eclipse.foo.friend1, org.eclipse.foo.friend2"
-</pre>
-
-<p>
-The example specifies that only the bundles org.eclipse.foo.friend1 and 
-org.eclipse.foo.friend2 should be encouraged to use the org.eclipse.foo.formyfriends 
-package.  The x-internal package takes priority over the x-friends directive.  If 
-the x-internal directive specifies 'true' then The Plug-in Development 
-Environment will discourage all bundles from using the package even if they are
-specified as a friend.
-</p>
-
-<h3>The Eclipse-AutoStart Header</h3>
-
-<p>
-The Eclipse-AutoStart header is used to specify if a bundle should be started 
-automatically before the first class or resource is accessed from that bundle. 
-This feature allows Eclipse to activate bundles on demand the first time they are
-needed.  Using this model Eclipse can startup with as few active bundles as 
-possible.  The Eclipse-AutoStart header must use the following syntax:
-</p>
-
-<pre>
-Eclipse-AutoStart ::= ( 'true' | 'false' ) ( ';' 'exceptions' '=' '&quot;' exceptions-list '&quot;' ) ?
-exceptions-list ::= a comma ',' separated list of packages
-</pre>
-
-<p>
-The 'exceptions' attribute is used to specify a list of packages which must not cause
-the bundle to be activated when classes or resources are loaded from them.  
-If the Eclipse-AutoStart header is not defined in the bundle manifest then a default 
-value of 'false' is used.  The following is an example of the Eclipse-AutoStart header:
-</p>
-
-<pre>
-Eclipse-AutoStart: true; exceptions="org.eclipse.foo1, org.eclipse.foo2"
-</pre>
-
-<p>
-The example specifies that this bundle must be activated for any classes or resources 
-that are loaded from this bundle, except the classes and resources in the packages
-'org.eclipse.foo1' and 'org.eclipse.foo2'.
-</p>
-
-<h3>The Eclipse-PlatformFilter Header</h3>
-
-<p>
-The Eclipse-PlatformFilter is used to specify a platform filter for a bundle.  A platform
-filter must evaluate to true in a running platform in order for a bundle to be allowed
-to resolve.  The Eclipse-PlatformFilter header must use the following syntax:
-</p>
-
-<pre>
-Eclipse-PlatformFilter ::= a valid LDAP filter string
-</pre>
-
-<p>
-The Framework supports filtering on the following system properties:
-</p>
-
-<ul type=disc>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-     mso-list:l2 level1 lfo3;tab-stops:list .5in'><b>osgi.nl</b> - the platform 
-     language setting.</li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-     mso-list:l2 level1 lfo3;tab-stops:list .5in'><b>osgi.os</b> - the platform 
-     operating system.</li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-     mso-list:l2 level1 lfo3;tab-stops:list .5in'><b>osgi.arch</b> - the platform 
-     architecture.</li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-     mso-list:l2 level1 lfo3;tab-stops:list .5in'><b>osgi.ws</b> - the platform 
-     windowing system.</li>
-</ul>
-
-<p>
-The following is an example of the Eclipse-PlatformFilter header:
-</p>
-
-<pre>
-Eclipse-PlatformFilter: (&amp; (osgi.ws=win32) (osgi.os=win32) (osgi.arch=x86))
-</pre>
-
-<p>
-This example specifies that this bundle can only be resolved if the platform 
-properties are osgi.ws=win32 and osgi.os=win32 and osgi.arch=x86.  In other words 
-a platform running on an x86 architecture, using a win32 operating system and 
-the win32 windowing system.
-</p>
-
-<h3>The Eclipse-BuddyPolicy Header</h3>
-
-<p>
-The Eclipse-BuddyPolicy header is used to specify the buddy classloading policies for a bundle.
-The Eclipse-BuddyPolicy header must use the following syntax:
-</p>
-
-<pre>
-Eclipse-BuddyPolicy ::= ( policy-name ) ( ',' policy-name ) *
-policy-name ::= ( 'dependent' | 'global' | 'registered' | 
-                  'app' | 'ext' | 'boot' | 'parent' )
-</pre>
-
-<p>
-The following is an example of the Eclipse-BuddyPolicy header:
-</p>
-
-<pre>
-Eclipse-BuddyPolicy: dependent
-</pre>
-
-<h3>The Eclipse-RegisterBuddy Header</h3>
-
-<p>
-The Eclipse-RegisterBuddy header is used to specify a list of bundles for which this bundle is 
-a registered buddy.  The Eclipse-RegisterBuddy header must use the following syntax:
-</p>
-
-<pre>
-Eclipse-RegisterBuddy ::= ( target-bundle ) ( ',' target-bundle ) *
-target-bundle ::= a bundle symbolic name
-</pre>
-
-<p>
-The following is an example of the Eclipse-RegisterBuddy header:
-</p>
-
-<pre>
-Eclipse-RegisterBuddy: org.eclipse.foo.bundle1, org.eclipse.foo.bundle2
-</pre>
-
-<h3>The Eclipse-ExtensibleAPI Header</h3>
-
-<p>
-The Eclipse-ExtensibleAPI is used to specify whether a host bundle allows fragment bundles 
-to add addtional API to the host.  This header should be used if a host bundle wants to allow 
-fragments to add additional packages to the API of the host.  If this header is not 
-specified then a default value of 'false' is used.  The Eclipse-ExtensibleAPI 
-header must use the following syntax:
-</p>
-
-<pre>
-Eclipse-ExtensibleAPI ::= ( 'true' | 'false' )
-</pre>
-
-<p>
-The following is an example of the Eclipse-ExtensibleAPI header:
-</p>
-
-<pre>
-Eclipse-ExtensibleAPI: true
-</pre>
-
-<h3>The Plugin-Class Header</h3>
-
-<p>
-The Plugin-Class header is only used to support plugins developed for the Eclipse 2.1 
-platform.  This header is used to specify a class name that will be used to activate 
-a plugin using the old Eclipse 2.1 activation model.  New bundles developed for the 
-Eclipse 3.0 or greater platform should not use this header.
-The following is an example of the Plugin-Class header:
-</p>
-
-<pre>
-Plugin-Class: org.eclipse.foo.FooPlugin
-</pre>
-
-</div>
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/eclipse-install.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/eclipse-install.html
deleted file mode 100644
index 8e20ef3..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/eclipse-install.html
+++ /dev/null

@@ -1,523 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>How to write an Eclipse installer</title>
-</head>
-
-<body>
-
-<h1>How to write an Eclipse installer</h1>
-<p>Last modified 15:20 Friday June 18, 2004</p>
-<p>Eclipse-based products need to be correctly installed on the end user's
-computer. Special-purpose packaging tools, such as <a href="http://www.installshield.com/">InstallShield</a>
-and <a href="http://www.rpm.org/">RPM</a>, are often used to build executable
-installers that automate installing, updating, and uninstalling. This note
-describes how to write an installer for an Eclipse-based product, and for
-separately-installable extensions to Eclipse-based products.</p>
-<p>We assume that a product development team is responsible for providing the
-raw ingredients that will need to find their way to end users' computers
-packaged as an executable installer. The creation of executable installers is
-scripted, as are the install time actions needed to interact with the end user
-and deposit files on their computer. This note described in detail what these
-installers need to do and how they should work.&nbsp;</p>
-<p>This note should be treated as a recipe for the person responsible for
-writing an installer for an Eclipse-based products. Two good reasons why we
-recommend all installers writers follow our recipe:</p>
-<ul>
-  <li><b>Product and extension interoperability.</b> By behaving in standard
-    ways, an installer for one Eclipse-based product or extension automatically
-    works with products and extensions laid down by other installers. Otherwise
-    the idiosyncrasies of one product's installer would require matching quirks
-    in all extension installers that expected to work with that product.</li>
-  <li><b>Uniformity of install time user interaction.</b> All installers for
-    Eclipse-based products and extension should interact with the user in the
-    same manner. There is nothing to having gratuitous variety in this matter.</li>
-</ul>
-
-<h2>Product installer creation script</h2>
-
-<p>A product installer should be self-contained - the kind of thing that could
-be distributed on a CD and installed on any machine with a suitable operating
-system.</p>
-<p>Eclipse requires a Java2 Java Runtime Environment (JRE) to run Java code.
-JREs are licensed software, obtained from Java vendors. With a license to
-redistribute a JRE from a JRE vendor, a company can include a JRE with its
-product, and install it on the end user's computer at the same time as the
-product. The alternative is to require that a JRE be pre-installed on the end
-user's computer, and associated with at product install time. One way or the
-other, an Eclipse-based product requires a suitable JRE, and the product
-installer must play a role in either installing a JRE or locating and linking to
-a pre-existing JRE.&nbsp;</p>
-<p>Assume that a JRE is to be installed with the product. A directory containing
-the JRE is one input to the installer creation script. Denote this directory
-&lt;<i>JRE</i>&gt;. This directory must have a standard JRE directory structure,
-with the Java executable is located at <code>jre/bin/java.exe</code> and the class
-library at <code>jre/lib/rt.jar</code> below the &lt;<i>JRE</i>&gt; directory.
-For reference, the skeletal structure of this directory looks like:</p>
-<p><code>&lt;<i>JRE</i>&gt;/<br>
-&nbsp; jre/<br>
-&nbsp;&nbsp;&nbsp; bin/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; java.exe<br>
-&nbsp;&nbsp;&nbsp; lib/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; rt.jar
-</code></p>
-<p>There are additional files (and subdirectories) in these directories; we've
-only shown a sample to give the general structure. Italicized names in italics
-are product-specific.</p>
-<p>The second input to the installer creation script is a directory, &lt;<code><i>product
-head</i></code>&gt;,
-containing the product-specific executable launcher and any files unrelated to
-Eclipse. For reference, the skeletal
-structure of this directory would look like (italics indicate file names that
-will vary from product to product):</p>
-<p><code>&lt;<i>product head</i>&gt;/<br>
-<i>&nbsp; acmeproduct.exe<br>
-</i>
-<br>
-</code>The third input to the installer creation script is a directory, &lt;<code><i>product
-body</i></code>&gt;,
-containing the features and plug-ins developed for the product. For reference, the skeletal
-structure of this directory would look like:</p>
-<p><code>&lt;<i>product body</i>&gt;/<br>
-&nbsp; eclipse/<br>
-&nbsp;&nbsp;&nbsp; features/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <i>com.example.acme.acmefeature</i>_<i>1.0.0</i>/<br>
-&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; feature.xml<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <i>com.example.acme.otherfeature</i>_<i>1.0.0</i>/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; feature.xml<br>
-&nbsp;&nbsp;&nbsp; plugins/<br>
-</code>&nbsp; <code>&nbsp;&nbsp;&nbsp;&nbsp; <i>com.example.acme.acmefeature</i>_<i>1.0.0</i>/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; plugin.xml<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; about.ini<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; about.properties<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; about.mappings<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; plugin_customization.ini<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; splash.bmp<br>
-</code>&nbsp; <code>&nbsp;&nbsp;&nbsp;&nbsp; <i>com.example.acme.otherfeature</i>_<i>1.0.0</i>/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; plugin.xml<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; about.ini<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; about.properties<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; about.mappings<br>
-</code>&nbsp; <code>&nbsp;&nbsp;&nbsp;&nbsp; <i>com.example.acme.myplugin</i>_<i>1.0.0</i>/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; plugin.xml<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <i>myplugin</i>.jar<br>
-</code>&nbsp; <code>&nbsp;&nbsp;&nbsp;&nbsp; <i>com.example.acme.otherplugin</i>_<i>1.0.0</i>/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; plugin.xml<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <i>otherplugin</i>.jar
-</code></p>
-<p>The fourth input to the installer creation script is a directory, &lt;<code><i>platform</i></code>&gt;,
-containing the features and plug-ins for the Eclipse platform itself and any third-party tools being included.
-This directory also includes the standard Eclipse executable launcher, <code>eclipse.exe</code>,
-(named <code>eclipse</code> on Unix operating environment), its companion <code>startup.jar</code>, and any other Eclipse platform files
-required to be at the root of the install. For reference, the skeletal
-structure of this directory would look like:</p>
-<p><code>
-&lt;<i>platform</i>&gt;<br>
-&nbsp; eclipse/<br>
-&nbsp; &nbsp; eclipse.exe<br>
-&nbsp;&nbsp;&nbsp; startup.jar<br>
-&nbsp;&nbsp;&nbsp; features/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; org.eclipse.platform_2.0.0/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; org.eclipse.platform.win32_2.0.0/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; org.eclipse.jdt_2.0.0/<br>
-&nbsp; &nbsp;&nbsp;&nbsp; org.eclipse.pde_2.0.0/<br>
-&nbsp;&nbsp;&nbsp; plugins/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; org.eclipse.platform_2.0.0/<br>
-&nbsp; &nbsp;&nbsp;&nbsp; org.eclipse.core.runtime_2.0.0/<br>
-&nbsp;&nbsp;&nbsp; &nbsp; org.eclipse.core.boot_2.0.0/<br>
-&nbsp; &nbsp;&nbsp;&nbsp; org.eclipse.core.resources_2.0.0/<br>
-&nbsp;&nbsp;&nbsp; &nbsp; org.eclipse.ui_2.0.0/<br>
-&nbsp; &nbsp;&nbsp;&nbsp; org.eclipse.jdt_2.0.0/<br>
-&nbsp;&nbsp;&nbsp; &nbsp; org.eclipse.jdt.core_2.0.0/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; org.eclipse.jdt.ui_2.0.0/<br>
-&nbsp; &nbsp;&nbsp;&nbsp; org.eclipse.pde_2.0.0/<br>
-&nbsp;&nbsp;&nbsp; &nbsp; org.eclipse.pde.core_2.0.0/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; org.eclipse.pde.ui_2.0.0/<br>
-&nbsp; &nbsp;&nbsp;&nbsp; (more org.eclipse.* plug-in directories)<br>
-<br>
-</code>The exact contents of the &lt;<i><code>JRE</code></i>&gt;, &lt;<i><code>product
-head</code></i>&gt;, &lt;<i><code>product body</code></i>&gt;,
-and &lt;<code><i>platform</i></code>&gt; input directories determine what files
-will eventually be installed on the end user's computer.</p>
-<p>The final inputs to the installer creation script are the id and version
-strings for the product's primary feature; e.g., &quot;<code><i>com.example.acme.acmefeature&quot;</i></code>,
-and &quot;<code><i>1.0.0</i></code>&quot;;
-and the name of the product executable; e.g., &quot;<code><i>acmeproduct</i></code><code>.exe</code>&quot;.
-For products that do not require their own product executable, this would be the
-path of the standard Eclipse executable launcher &quot;<code>eclipse/eclipse.exe</code>&quot;.
-These strings have special significance to the installer, appearing in file and
-directory names, and in the contents of marker files created at install time.</p>
-<p>At install time, the installer should behave in the standard manner (further
-details follow the list of steps):</p>
-<ol>
-  <li>warn user to exit all programs</li>
-  <li>introduce the product to be installed</li>
-  <li>if appropriate, ask the user for the name of the registered owner and for
-    the license key</li>
-  <li>display the product's licensing agreement and ask the user to accept</li>
-  <li>recommend a location on the disk to install the product (but allow user to
-    override this default)</li>
-  <li>check that a product or extension is not already stored at the specified
-    location</li>
-  <li>ask user to confirm all details of the install</li>
-  <li>create marker file to mark root of product install</li>
-  <li>copy files to disk&nbsp; (see below)</li>
-  <li>if appropriate, insert name of registered owner and license key into the &quot;about
-    &quot; description</li>
-  <li>create a desktop shortcut to run the product executable</li>
-  <li>create an appropriate entry to allow the user to uninstall the product</li>
-  <li>launch the product executable with -initialize option to perform all
-    first-time processing</li>
-  <li>offer to show the product release notes (&quot;readme&quot; file)</li>
-</ol>
-<p>If the location specified in step 5 is &lt;<code><i>install</i></code>&gt;,
-the installer copies all the files in the &lt;<i><code>JRE</code></i>&gt;, <code>&lt;<i>platform</i>&gt;, </code> &lt;<i><code>product</code></i>&gt;,&nbsp;
-and <code>&lt;<i>product plug-ins</i>&gt;</code> directories into &lt;<code><i>install</i></code>&gt;.</p>
-<table border="1" width="50%">
-  <tr>
-    <td width="50%">Input file</td>
-    <td width="50%">Installed file</td>
-  </tr>
-  <tr>
-    <td width="50%"><code>&lt;<i>JRE</i>&gt;/*</code></td>
-    <td width="50%"><code>&lt;<i>install</i>&gt;/eclipse/*</code></td>
-  </tr>
-  <tr>
-    <td width="50%"><code>&lt;<i>product head</i>&gt;/*</code></td>
-    <td width="50%"><code>&lt;<i>install</i>&gt;/*</code></td>
-  </tr>
-  <tr>
-    <td width="50%"><code>&lt;<i>product body</i>&gt;/*</code></td>
-    <td width="50%"><code>&lt;<i>install</i>&gt;/*</code></td>
-  </tr>
-  <tr>
-    <td width="50%"><code>&lt;<i>platform</i>&gt;/*</code></td>
-    <td width="50%"><code>&lt;<i>install</i>&gt;/*</code></td>
-  </tr>
-</table>
-<p>The marker file created in step 8 is <code>&lt;<i>install</i>&gt;/eclipse/.eclipseproduct</code>
- is used to mark a directory into which an Eclipse-based product has been
-installed, primarily for extension installers to locate. This marker file is a <a href="http://java.sun.com/j2se/1.3/docs/api/java/util/Properties.html">java.io.Properties</a>
-format file (ISO 8859-1 character encoding with &quot;\&quot; escaping) and
-contains the following information that identifies the product to the user and distinguishes
-one Eclipse-based product from one another:</p>
-<blockquote>
-<p><code>name=<i>Acme Visual Tools Pro</i><br>
-id=<i>com.example.acme.acmefeature<br>
-</i>version=<i>1.0.0</i></code></p>
-</blockquote>
-<p>The values of the &quot;id&quot; and &quot;version&quot; property are inputs
-to the installer creation script; the name of the product is presumably known
-and hard-wired. (Products would not ordinarily access this marker file; only
-product and extension installers write or read it.)</p>
-<p>Step 6 requires checking for an existing <code>&lt;<i>install</i>&gt;/eclipse/.eclipseproduct</code>
-or <code>&lt;<i>install</i>&gt;/eclipse/.eclipseextension</code> file. A
-product cannot be installed in exactly the same place as another product or extension.</p>
-<p>After installing all files, the top-level structure of the install directory
-would contain the following files and subdirectories (and perhaps others):</p>
-<p><code>&lt;<i>install</i>&gt;/<br>
-&nbsp; <i>acmeproduct</i>.exe<br>
-&nbsp; eclipse/<br>
-&nbsp;&nbsp;&nbsp; .eclipseproduct<br>
-&nbsp; &nbsp; eclipse.exe<br>
-&nbsp; &nbsp; startup.jar<br>
-&nbsp;&nbsp;&nbsp; features/<br>
-&nbsp;&nbsp;&nbsp; plugins/<br>
-&nbsp;&nbsp;&nbsp; jre/<br>
-<br>
-</code>If a product installer solicits license information from the user, such as
-the name of the registered owner and the license key, this information should
-make it into the product &quot;about&quot; dialog (step 10).</p>
-<p>This is done by recording the user responses in the &quot;<code>about.mapping</code>&quot;
-file in the primary feature's plug-in. For example, at <code>&lt;<i>install</i>&gt;/plugins/<i>com.example.acme.acmefeature</i>_<i>1.0.0</i>/about.mapping</code>.
-The &quot;<code>about.mapping</code>&quot; file may be pre-existing in the &lt;<i><code>product
-head</code></i>&gt;
-input, or may need to be created by the installer at install time.
-The keys are numbers; the value of the &quot;<i>n</i>&quot; key is substituted
-for the substring &quot;<code>{<i>n</i>}</code>&quot; in the &quot;<code>aboutText</code>&quot; property.
-For example, if a license key was field number 0, an &quot;<code>about.mapping</code>&quot;
-file containing a line like &quot;<code>0=T42-24T-ME4U-U4ME</code>&quot; should
-be created.</p>
-<p>N.B.
-The &quot;<code>about.mapping</code>&quot; file is a&nbsp; <a href="http://java.sun.com/j2se/1.3/docs/api/java/util/Properties.html">java.io.Properties</a>
-format file (ISO 8859-1 character encoding with "\" escaping).
-When the native character encoding at install time is different from ISO 8859-1,
-the installer is responsible for converting the native character encoding to
-Unicode and for adding &quot;\&quot; escapes where required. Escaping is required
-when the strings contain special characters (such as &quot;\&quot;) or non-Latin characters. For example, field number 1 containing the first 3 letters of the Greek
-alphabet would be written &quot;<code>1=\u03B1\u03B2\u03B3</code>&quot;.</p>
-<p>At step 12, the product installer launches the product executable,<code>&nbsp;&lt;<i>install</i>&gt;/<i>acmeproduct</i>.exe</code>,
-with the special -initialize option [exact details TBD]. This causes the Eclipse platform to quietly
-perform all time-consuming first-time processing and cache the results, so that
-when the user starts the product it comes up promptly in an open-for-business
-state.</p>
-<h3>Uninstaller behavior</h3>
-<p>At uninstall time, the uninstaller should behave in the standard manner:</p>
-<ol>
-  <li>warn user to exit all programs, especially the product being uninstalled</li>
-  <li>ask user to confirm that the product is to be uninstalled</li>
-  <li>remove all installed files from the &lt;<i><code>install</code></i>&gt;
-    directory, and <b>all</b> files in &lt;<i><code>install</code></i>&gt;<code>/eclipse/features</code>
-    and &lt;<i><code>install</code></i>&gt;<code>/eclipse/plugins</code> including ones put there by parties other than
-    this installer (e.g., by the Eclipse update manager)</li>
-  <li>remove desktop shortcut for the product executable</li>
-  <li>remove entry for product uninstaller</li>
-  <li>inform user of any files that were not removed</li>
-</ol>
-<p>When the product is uninstalled, files deposited at
-install time should be deleted, along with updated features and plug-ins created
-by the Eclipse update manager. <b>Important:</b> At uninstall time, there may be
-other directories and files in the <code>&lt;<i>install</i>&gt;</code>
-directory, notably <code>&lt;<i>install</i>&gt;/eclipse/workspace/</code>,
-<code>&lt;<i>install</i>&gt;/eclipse/links/</code>, and <code>&lt;<i>install</i>&gt;/eclipse/configuration/</code>,
-that contain important data
-which must be retained when the product is uninstalled. The user must be able to
-uninstall and reinstall a product at the same location without losing important
-data.</p>
-<h3>Installer behavior when product already installed</h3>
-<p>When the product is already installed on the user's computer, the installer
-should allow a service update or version upgrade to be applied to the installed
-product.</p>
-<p>At install time, the installer should behave in the standard manner:</p>
-<ol>
-  <li>warn user to exit all programs, especially the product being updated</li>
-  <li>locate the installed product to be updated, if necessary by searching the
-    disk for an existing product install or by allowing the user to locate it</li>
-  <li> determine where this installer is a compatible update</li>
-  <li>if appropriate, ask the user for the name of the registered owner and for
-    the license key</li>
-  <li>display the product's updated licensing agreement and ask the user to accept</li>
-  <li>ask user to confirm all details of the update</li>
-  <li>update files to disk&nbsp; (see below)</li>
-  <li>if required, alter the desktop shortcut to run the product executable</li>
-  <li>should add modified or newly added files to the list of ones to be removed at uninstall
-    time (where feasible)</li>
-  <li>offer to show the product release notes (&quot;readme&quot; file)</li>
-</ol>
-<p>In step 2, an installed product can be recognized by the presence of an &quot;<code>eclipse</code>&quot;
-directory immediately containing a file named &quot;<code>.eclipseproduct</code>&quot;.
-The parent of the &quot;<code>eclipse</code>&quot; directory is a product's install
-directory; i.e., <code>&lt;<i>install</i>&gt;/eclipse/.eclipseproduct</code>.
-The information contained within this marker file should be shown to the user for
-confirmation that the correct product is being updated (there may be several
-Eclipse-based product on the user's computer).</p>
-<p>The installer should perform compatibility checks in step 3 by simple pattern
-matching against subdirectories in the <code>&lt;<i>install</i>&gt;/eclipse/features</code>
-directory. For example, the presence of a folder matching &quot;<code><i>com.example.acme.otherfeature</i>_<i>1.0.1</i></code>&quot;
-would ensure that a certain service update had been applied to the installed
-product.</p>
-<p>For step 7, the installer may delete or replace any of the files that it
-originally installed, and add more files. <b>Important:</b> Several files and directories,
-including <code>&lt;<i>install</i>&gt;/eclipse/workspace/</code>, <code>&lt;<i>install</i>&gt;/eclipse/configuration</code>,
-may be co-located with the install and contain important data files
-which need to be retained
-when the product is upgraded.&nbsp;</p>
-<p>In upgrade situations, there is a good chance that most of the files below <code>&lt;<i>install</i>&gt;/eclipse/plugins/</code>
-are the same (likewise for <code>&lt;<i>install</i>&gt;/eclipse/features/</code>).
-There is significant opportunity for optimization in <code>&lt;<i>install</i>&gt;/eclipse/plugins/</code>
-since the sub-directory name, which embeds the plug-in (or fragment) version
-number, changes if and only iff any of the files below it change. In other
-words, there is no need to touch any files in <code>&lt;<i>install</i>&gt;/eclipse/plugins/org.eclipse.ui_2.0.0</code>/
-if this sub-directory should also exist after the upgrade; if any of the plug-in's
-files were to change, the plug-in's version number is revised, causing the files
-for the upgraded plug-in to be installed in a parallel directory <code>&lt;<i>install</i>&gt;/eclipse/plugins/org.eclipse.ui_2.0.1</code>/.&nbsp;</p>
-<h3>Associating a JRE installed elsewhere</h3>
-<p>The JRE is expected to be located at <code>&lt;<i>install</i>&gt;/eclipse/jre/bin/javaw.exe</code>.
-If it is located elsewhere, the absolute path should be specified using the <code>-vm</code>
-option on the command line; e.g.,<code>   -vm C:\j2jre1.3.0\jre\bin\javaw.exe</code>.
-In which case, the installer should add this option to the command line of the desktop shortcut
-it creates.</p>
-<h2>Extension installer creation script</h2>
-
-<p>By extension we mean a separately installable set of features and their plug-ins that
-can be associated with, and used from, one ore more Eclipse-based products installed on the
-same computer. In contrast to a product, an extension is not self-contained; an extension does not include
-a product executable, the Eclipse platform, a JRE.</p>
-<p>Without loss of generality, assume that an extension consists of a single
-feature. The first input to the installer creation script is a directory, &lt;<code><i>extension</i></code>&gt;,
-containing its feature and plug-ins. We are assuming that an extension has no
-files that are related to Eclipse; if it did, they would go in <code>&lt;<i>extension</i>&gt;/</code>,
-and not in <code>&lt;<i>extension</i>&gt;/eclipse/</code>. For reference, the skeletal
-structure of this directory would look like:</p>
-<p><code>&lt;<i>extension</i>&gt;/<br>
-&nbsp; eclipse/<br>
-&nbsp; &nbsp; features/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <i>com.example.wiley.anvilfeature</i>_<i>1.0.0</i>/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; feature.xml<br>
-&nbsp; &nbsp; plugins/<br>
-</code>&nbsp; <code>&nbsp;&nbsp;&nbsp;&nbsp; <i>com.example.wiley.anvilfeature</i>_<i>1.0.0</i>/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; plugin.xml<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; about.ini<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; about.properties<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; about.mappings<br>
-</code>&nbsp; <code>&nbsp;&nbsp;&nbsp;&nbsp; <i>com.example.wiley.mainplugin</i>_<i>1.0.0</i>/<br>
-</code>&nbsp; <code>&nbsp;&nbsp;&nbsp;&nbsp; <i>com.example.wiley.otherplugin</i>_<i>1.0.0</i>/
-</code></p>
-<p>The exact contents of the &lt;<i><code>extension</code></i>&gt; input
-directory determines what files
-will eventually be installed on the end user's computer.</p>
-<p>The final inputs to the installer creation script are the id and version
-strings for the extension's feature; e.g., &quot;<i><code>com.example.wiley.anvil</code></i>&quot;
-and &quot;<code><i>1.0.0</i></code>&quot;. These strings have special
-significance to the installer, appearing in file and directory names, and in the
-contents of marker files created at install time.</p>
-<p>An extension installer is similar to a product installer in most respects.
-The areas where it differs are highlighted below:</p>
-<p>At install time, the installer behaves in the standard manner:</p>
-<ol>
-  <li>warn user to exit all programs</li>
-  <li>introduce the extension to be installed</li>
-  <li>if appropriate, ask the user for the name of the registered owner and for
-    the license key</li>
-  <li>display the extension's licensing agreement and ask the user to accept</li>
-  <li>recommend a location on the disk to install the extension (but allow user to
-    override this default)</li>
-  <li>check that a product or a different extension is not already stored at the specified
-    location</li>
-  <li> ask user which product(s) to are to use this extension (search disk;
-    browse; or skip)
-  </li>
-  <li>optionally, determine if extension is compatible with selected products</li>
-  <li>ask user to confirm all details of the install</li>
-  <li>create marker file to mark root of extension install</li>
-  <li>copy files to disk&nbsp; (see below)</li>
-  <li>insert name of registered owner and license key into the &quot;about
-    &quot; description</li>
-  <li>create an appropriate entry to allow the user to uninstall the extension</li>
-  <li>write link file in each of the selected products to associate extension
-    with product</li>
-  <li>offer to show the extension release notes (&quot;readme&quot; file)</li>
-</ol>
-<p>If the location specified in step 5 is &lt;<code><i>install</i></code>&gt;,
-the installer copies all the files in the <code>&lt;<i>extension</i>&gt; </code>directory
-into &lt;<code><i>install</i></code>&gt; in step 11.</p>
-<table border="1" width="50%">
-  <tr>
-    <td width="50%">Input file</td>
-    <td width="50%">Installed file</td>
-  </tr>
-  <tr>
-    <td width="50%"><code>&lt;<i>extension</i>&gt;/*</code></td>
-    <td width="50%"><code>&lt;<i>install</i>&gt;/*</code></td>
-  </tr>
-</table>
-<p>For step 7, any Eclipse product might be a candidate. Eclipse-based product
-can be recognized by the presence of a <code>&lt;<i>product install</i>&gt;/eclipse/.eclipseproduct</code>
-file; the user should be able to request a limited disk search for installed
-products (a &quot;search for installed products&quot; button), or would navigate
-to a directory containing a product (i.e., a &quot;browse&quot; button).</p>
-<p>The installer should perform compatibility checks in step 8 by simple pattern
-matching against subdirectories in the <code>&lt;<i>product install</i>&gt;/eclipse/features</code>
-directory. For example, the presence of a folder matching &quot;<code>org.eclipse.jdt_2.*</code>&quot;
-means that JDT is included in the installed product.&nbsp;</p>
-<p>The marker file created in step 10 is <code>&lt;<i>install</i>&gt;/eclipse/.eclipseextension</code>
- is used to mark a directory into which an Eclipse-based extension has been
-installed, primarily for extension installers to locate
-(analogous to a product's <code>.eclipseproduct</code> marker file). This
-marker file is a <a href="http://java.sun.com/j2se/1.3/docs/api/java/util/Properties.html">java.io.Properties</a>
-format file (ISO 8859-1 character encoding with &quot;\&quot; escaping) and
-contains the following information that identifies the extension to the user and distinguishes
-one Eclipse-based extension from one another:</p>
-<blockquote>
-<p><code>name=<i>Wiley Anvil Enterprise Edition</i><br>
-id=<i>com.example.wiley.anvilfeature<br>
-</i>version=<i>1.0.0</i></code></p>
-</blockquote>
-<p>The values of the &quot;id&quot; and &quot;version&quot; property are inputs
-to the installer creation script; the name of the extension is presumably known
-and hard-wired. (Products would not ordinarily access this marker file; only
-product and extension installers write or read it.)</p>
-<p>After installing all files, the top-level structure of the install directory
-would contain the following files and subdirectories:</p>
-<p><code>&lt;<i>install</i>&gt;/<br>
-&nbsp; eclipse/<br>
-&nbsp; &nbsp; .eclipseextension<br>
-&nbsp;&nbsp;&nbsp; features/<br>
-&nbsp;&nbsp;&nbsp; plugins/</code></p>
-<p>The only significant difference from a product installer is that an extension
-installer also creates link files in other Eclipse-based products already
-installed on the user's computer. (This saves the user from having to manually
-associate the new extension from within each product using the Eclipse update
-manager.)&nbsp;</p>
-<p>The link file created in step 14 is <code>&lt;<i>product install</i>&gt;/eclipse/links/<i>com.example.wiley.anvilfeature.</i>link</code>;
-that is, the file has the same name of as the extension's feature directory less
-the version number suffix. A link file is a <a href="http://java.sun.com/j2se/1.3/docs/api/java/util/Properties.html">java.io.Properties</a>
-format file (ISO 8859-1 character encoding with "\" escaping).
-The key is &quot;path&quot; and the value is the absolute path of the installed
-extension, <code>&lt;<i>install</i>&gt;</code>; e.g., an entry might looks like &quot;<code>path=C:\\Program
- Files\\Wiley\\Anvil</code>&quot;<code>.</code> The installer is responsible for converting
-from native character
-encoding to Unicode and adding &quot;\&quot; escapes where required. Escaping is
-usually required since <code>&lt;<i>install</i>&gt;</code>
- typically contains special characters (such as &quot;\&quot;)
-and may mention directories with non-Latin characters in their names. The product reads
-link files when it starts up. The installer keeps a record of any link
-files it creates so that they can be located when the extension is updated or
-uninstalled.</p>
-<h3>Uninstaller behavior</h3>
-<p>At un install time, the un installer should behave in the standard manner:</p>
-<ol>
-  <li>warn user to exit all programs, especially products using the extension
-    being uninstalled</li>
-  <li>ask user to confirm that the extension is to be un installed</li>
-  <li>remove all installed files from the &lt;<i><code>install</code></i>&gt;
-    directory, and <b>all</b> files in &lt;<i><code>install</code></i>&gt;<code>/eclipse/features</code>
-    and &lt;<i><code>install</code></i>&gt;<code>/eclipse/plugins</code> including ones put there by parties other than
-    this installer (e.g., by the Eclipse update manager)</li>
-  <li>if feasible, remove the link file from any products to which it had been
-    added&nbsp;</li>
-  <li>remove entry for extension uninstaller</li>
-  <li>inform user of any files that were not removed</li>
-</ol>
-<p>When an extension is uninstalled, all plug-in and feature files should be deleted; there are no
-important data files to be kept in these subdirectories. This allows the user to uninstall an extension
-completely, including any updates applied by the Eclipse update manager.</p>
-<h3>Installer behavior when extension already installed</h3>
-<p>When the extension is already installed on the user's computer, the installer
-should allow a service update or version upgrade to be applied to the installed
-extension.</p>
-<p>At install time, the installer should behave in the standard manner:</p>
-<ol>
-  <li>warn user to exit all programs, especially products using the extension
-    being updated</li>
-  <li>locate the installed extension to be updated, if necessary by searching
-    the disk for an existing extension install or by allowing the user to locate
-    it</li>
-  <li> determine where this installer is a compatible update</li>
-  <li>if appropriate, ask the user for the name of the registered owner and for
-    the license key</li>
-  <li>display the product's updated licensing agreement and ask the user to accept</li>
-  <li>ask user to confirm all details of the update</li>
-  <li>update files on disk&nbsp; (see below)</li>
-  <li>should add modified or newly added files to the list of ones to be removed at uninstall
-    time (where feasible)</li>
-  <li>offer to show the extension release notes (&quot;readme&quot; file)</li>
-</ol>
-<p>In step 2, an installed extension can be recognized by the presence of an &quot;<code>eclipse</code>&quot;
-directory immediately containing a file named &quot;<code>.eclipseextension</code>&quot;.
-The parent of the &quot;<code>eclipse</code>&quot; directory is an extension's install
-directory; i.e., <code>&lt;<i>install</i>&gt;/eclipse/.eclipseextension</code>.
-The information contained within this marker file should be shown to the user for
-confirmation that the correct extension is being updated (there may be several
-Eclipse-based extension on the user's computer).</p>
-<p>For step 7, the installer should not delete or overwrite any of the files
-that it originally installed; rather, it should only add the files for new
-versions of features and plug-in, and possibly rewrite the marker file <code>&lt;<i>install</i>&gt;/eclipse/.eclipseextension</code>. Leaving the old versions around gives the user
-the option to back out of the update. As with upgrading a product install, there
-is no need to touch any files in <code>&lt;<i>install</i>&gt;/eclipse/plugins/<i>com.example.wiley.otherplugin</i>_<i>1.0.0</i></code>/
-if this sub-directory should also exist after the upgrade; if any of the plug-in's
-files were to change, the plug-in's version number is revised, causing the files
-for the upgraded plug-in to be installed in a parallel directory <code>&lt;<i>install</i>&gt;/eclipse/plugins/<i>com.example.wiley.otherplugin</i>_<i>1.0.1</i></code>/.&nbsp;</p>
-
-
-
-</body>
-
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/eclipsestarter.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/eclipsestarter.html
deleted file mode 100644
index a30a21b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/eclipsestarter.html
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Starting Eclipse from Java</title>
-</head>
-
-<body>
-
-<h1>Starting Eclipse from Java</h1>
-<p>Last modified 09:00 Wednesday June 23, 2004</p>
-<p>
-The Eclipse Platform makes heavy use of Java class loaders for loading plug-ins. Even the Eclipse Runtime itself 
-and the OSGi framework need to be loaded by special class loaders. Client programs, such as a Java main program
-or a servlet, cannot directly reference any part of Eclipse directly. Instead, a client must use 
-the <b>EclipseStarter</b> class in <b>org.eclipse.core.runtime.adaptor</b> to start the platform, 
-invoking functionality defined in plug-ins, and shutting down the platform when done. 
-</p>
-<p>
-Clients that do not need to access any particular function, but just need to start the platform, can use
-<tt>org.eclipse.core.launcher.Main.run()</tt> in <tt>startup.jar</tt>.  However, clients that need to invoke specific function should use
-<b>EclipseStarter</b>.  See the javadoc inside this class for details.
-</p>  
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/feature_archive.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/feature_archive.html
deleted file mode 100644
index 1f344b5..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/feature_archive.html
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Feature Archives</title>
-</head>
-<body>
-
-<h1>
-Feature Archives</h1>
-<p>The feature packaging information is placed into a separate Java .jar.
-Standard Java jar facilities are used for constructing feature archives.
-Feature archives reference separately packaged plug-in archives (see next
-section) and non-plug-in files.</p><p>Features are identified using a structured identifier based on the provider
-internet domain name. For example, organization eclipse.org produces
-feature org.eclipse.jdt. The character set used for feature identifiers
-is as specified for plug-in identifiers (see <a href="plugin_manifest.html">Plug-in
-Manifest</a>).</p>
-<p>The recommended convention for naming the feature archives is
-<br><tt>&lt;id>_&lt;version>.jar</tt> </p>
-<p>Where <tt>&lt;id></tt> is the feature identifier and <tt>&lt;version></tt>
-is the full version identifier contained in the respective feature.xml.
-Note that this is a recommended convention that minimizes chance of collisions,
-but is not required by the Eclipse architecture. For example, the following
-are valid feature archive names</p>
-<p><tt>org.eclipse.jdt_2.0.0.jar</tt>
-<br><tt>org.eclipse.pde_2.0.jar</tt>
-<br><tt>my_feature.jar</tt></p>
-<p>Internally, each feature archive is packaged relative to its feature
-directory (but not including the directory path element). The archive has
-the following structure	</p>
-<p><tt>feature.xml</tt>
-<br><tt>feature&lt;_locale>.properties (see "Translated Feature Information")</tt>
-<br><tt>other feature files and subdirectories (TBD)</tt>
-<br><tt>META-INF/</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; Java jar manifest and security files</tt>
-</p>
-Note that feature archives do not contain their constituent plug-ins and fragments.
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/feature_manifest.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/feature_manifest.html
deleted file mode 100644
index 866fb1d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/feature_manifest.html
+++ /dev/null

@@ -1,536 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Feature Manifest</title>
-</head>
-<body>
-
-<h1>
-Eclipse platform feature manifest</h1>
-<p class=MsoNormal><span style='font-size:10.0pt'>Version 3.0 - Last revised June 22, 2004</span></p>
-
-<p>The feature manifest format is defined by the following dtd:</p>
-<p><tt>&lt;?xml encoding="ISO-8859-1"?></tt></p>
-<p><tt>&lt;!ELEMENT feature (install-handler? | description? | copyright? |
-license? | url? | includes* | requires? | plugin* | data*)></tt>
-<br><tt>&lt;!ATTLIST feature</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; version&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; provider-name CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; image&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; os&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; arch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; ws&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; nl&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; colocation-affinity</tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; primary&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-(true | false) "false"<br>
-&nbsp;&nbsp;&nbsp; exclusive&nbsp;&nbsp;&nbsp;&nbsp; (true | false)
-&quot;false&quot;<br>
-&nbsp;&nbsp;&nbsp; plugin&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA
-#IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; application&nbsp;&nbsp; CDATA #IMPLIED</tt>
-<br><tt>></tt></p>
-<p><tt>&lt;!ELEMENT install-handler EMPTY></tt>
-<br><tt>&lt;!ATTLIST install-handler</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; library&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; handler&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>></tt></p>
-<p><tt>&lt;!ELEMENT description (#PCDATA)></tt>
-<br><tt>&lt;!ATTLIST description</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>></tt></p>
-<p><tt>&lt;!ELEMENT copyright (#PCDATA)></tt>
-<br><tt>&lt;!ATTLIST copyright</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>></tt></p>
-<p><tt>&lt;!ELEMENT license (#PCDATA)></tt>
-<br><tt>&lt;!ATTLIST license</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>></tt></p>
-<p><tt>&lt;!ELEMENT url (update?, discovery*)></tt></p>
-<p><tt>&lt;!ELEMENT update EMPTY></tt>
-<br><tt>&lt;!ATTLIST update</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>></tt></p>
-<p><tt>&lt;!ELEMENT discovery EMPTY></tt>
-<br><tt>&lt;!ATTLIST discovery<br>
-&nbsp;&nbsp;&nbsp; type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-(web | update) &quot;update&quot;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>></tt></p>
-<p><tt>&lt;!ELEMENT includes EMPTY></tt>
-<br><tt>&lt;!ATTLIST includes</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; version&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED<br>
-&nbsp;&nbsp;&nbsp;
-name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED<br>
-&nbsp;&nbsp;&nbsp;
-optional&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (true | false)
-&quot;false&quot;<br>
-&nbsp;&nbsp;&nbsp; search-location&nbsp;&nbsp; (root | self | both)
-&quot;root&quot;</tt><br><tt>&nbsp;&nbsp;&nbsp; os&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; arch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; ws&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; nl&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA #IMPLIED</tt> <tt><br>
-></tt></p>
-<p><tt>&lt;!ELEMENT requires (import+)></tt></p>
-<p><tt>&lt;!ELEMENT import EMPTY></tt>
-<br><tt>&lt;!ATTLIST import</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; plugin&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED<br>
-&nbsp;&nbsp;&nbsp; feature&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; version&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; match&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-(perfect | equivalent | compatible | greaterOrEqual) "compatible"<br>
-&nbsp;&nbsp;&nbsp; patch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (true |
-false) &quot;false&quot;</tt>
-<br><tt>></tt></p>
-<p><tt>&lt;!ELEMENT plugin EMPTY></tt>
-<br><tt>&lt;!ATTLIST plugin</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; version&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; fragment&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (true
-| false) "false"</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; os&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; arch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; ws&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; nl&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; download-size CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; install-size&nbsp; CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; unpack&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (true |
-false) &quot;true&quot;</tt>
-<br><tt>></tt></p>
-<p><tt>&lt;!ELEMENT data EMPTY></tt>
-<br><tt>&lt;!ATTLIST data</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; os&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; arch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; ws&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; nl&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; download-size CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; install-size&nbsp; CDATA #IMPLIED</tt>
-<br><tt>></tt></p>
-<p>The element and attribute definitions are as follows:
-<ul>
-
-<li>&lt;feature&gt; - defines the feature
-<ul>
-<li>id - required feature identifier (eg. com.xyz.myfeature)</li>
-<li>version - required component version (eg. 1.0.3)</li>
-<li>label - optional displayable label (name). Intended to be translated.</li>
-<li>provider-name - optional display label identifying the organization providing
-this component. Intended to be translated.</li>
-<li>image - optional image to use when displaying information about the feature.&nbsp;
-Specified relative to the feature.xml.</li>
-<li>os - optional operating system specification. A comma-separated list of
-operating system designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this feature should only be installed on one of the specified
-OS systems. If this attribute is not specified, the feature can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of feature regardless of this setting).</li>
-<li>arch - optional machine architecture specification. A comma-separated list
-of architecture designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this feature should only be installed on one of the specified
-systems. If this attribute is not specified, the feature can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of feature regardless of this setting).</li>
-<li>ws - optional windowing system specification. A comma-separated list of
-window system designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this feature should only be installed on one of the specified
-WS's. If this attribute is not specified, the feature can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of feature regardless of this setting).</li>
-<li>nl - optional locale specification. A comma-separated list of locale designators
-defined by Java. Indicates this feature should only be installed on a system
-running with a compatible locale (using Java locale-matching rules). If
-this attribute is not specified, the feature can be installed on all systems
-(language-neutral implementation). This information is used as a hint by
-the installation and update support (user can force installation of feature
-regardless of this setting).</li>
-<li>colocation-affinity - optional reference to another feature identifier
-used to select the default installation location for this feature. When
-this feature is being installed as a new feature (no other versions of
-it are installed), an attempt is made to install this feature in the same
-installation location as the referenced feature.</li>
-<li>primary - optional indication specifying whether this feature can be used
-as a primary feature. Default if <i>false</i>
-(not a primary feature).</li>
-<li>application - optional identifier of the Eclipse application that is to
-be used during startup when the declaring feature is the primary feature. The application identifier must represent a valid application
-registered in the <tt>org.eclipse.core.runtime.applications</tt> extension
-point. Default is <tt>org.eclipse.ui.ide.workbench</tt>.</li>
-<li> plugin - optional identifier that represents the id of the plug-in 
-listed in the feature that is used to carry branding information for 
-the feature (images, translations, splash screens in case of primary feature 
-etc.). If not specified, the assumption will be made the attribution plug-in 
-has the same id as the feature.</li>
-<li>exclusive  - optional flag that, if &quot;true&quot;, indicates that
-the feature cannot be installed in a group with other features.</li>
-</ul>
-</li>
-
-<li>&lt;install-handler&gt;
-<ul>
-<li>library - optional .jar library containing the install handler classes.
-If specified, the referenced .jar must be contained in the feature archive.
-It is specified as a path within the feature archive, relative to the feature.xml
-entry. If not specified, the feature archive itself is used to load the
-install handler classes. This attribute is only interpreted if <i>class</i>
-attribute is also specified</li>
-<li>handler - optional identifier of the install handler. The value is interpreted
-depending on the value of the <i>library</i> attribute. If <i>library</i>
-is specified,&nbsp; the value is interpreted as a fully qualified name
-of a class contained in the specified <i>library</i>. If <i>library</i>
-is not specified, the value is is interpreted as an extension identifier
-of an extension registered in the <i>org.eclipse.update.installHandlers</i>
-extension point. In either case, the resulting class must implement the
-<i>IInstallHandler</i>
-interface. The class is dynamically loaded and called at specific points
-during feature processing. When the handler is specified as a class, it has visibility to the API classes
-from the org.eclipse.update.core plug-in, and Eclipse plug-ins required by this 
-plug-in; otherwise, when is specified as extension, it has access to all the 
-classes as the plug-in defining the extension.</li>
-</ul>
-</li>
-
-<li>&lt;description&gt; - brief component description as simple text. Intended
-to be translated.
-<ul>
-<li>url - optional URL for the full description as HTML. The URL can be specified
-as absolute of relative. If relative, it is assumed to be relative to (and
-packaged in) the feature archive. Note, that for NL handling the URL value
-should be separated to allow alternate URLs to be specified for each national
-language.</li>
-</ul>
-</li>
-
-<li>&lt;copyright&gt; - feature copyright as simple text. Intended to be translated.
-<ul>
-<li>url - optional URL for the full description as HTML. The URL can be specified
-as absolute of relative. If relative, it is assumed to be relative to (and
-packaged in) the feature archive. Note, that for NL handling the URL value
-should be separated to allow alternate URLs to be specified for each national
-language.</li>
-</ul>
-</li>
-
-<li>&lt;license&gt; - feature "click-through" license as simple text. Intended
-to be translated. It is displayed in a standard dialog with [Accept] [Reject]
-actions during the download/ installation process. Note, that click-through
-license must be specified for any feature that will be selected for installation
-or update using the Eclipse update manager. When using nested features,
-only the nesting parent (i.e. the feature selected for installation or update)
-must have click-through license text defined. The license text is required
-even if the optional <i>url</i> attribute is specified.
-<ul>
-<li>url - optional URL for the full description as HTML. The URL can be specified
-as absolute of relative. If relative, it is assumed to be relative to (and
-packaged in) the feature archive. Note, that for NL handling the URL value
-should be separated to allow alternate URLs to be specified for each national
-language. Note, that the "content" of this URL is <b>not</b> what is presented
-as the click-through license during installation processing. The click-through
-license is the actual value of the <i>&lt;license></i> element (eg. <tt>&lt;license>click
-through text&lt;/license></tt>)</li>
-</ul>
-</li>
-
-<li>&lt;url&gt; - optional URL specifying site(s) contain feature updates, or new features
-<ul>
-<li>&lt;update&gt; - URL to go to for updates to this feature
-<ul>
-<li>url - actual URL</li>
-<li>label - displayable label (name) for the referenced site</li>
-</ul>
-</li>
-<li>&lt;discovery&gt; - URL to go to for new features. In general, a provider
-can use this element to reference its own site(s), or site(s) of partners
-that offer complementary features. Eclipse uses this element simply as
-a way to distribute new site URLs to the clients. Sites that belong to root
-features (at the top of the hierarchy) typically appear in &quot;Sites to
-Visit&quot; in Update Manager.
-<ul>
-<li>url - actual URL</li>
-<li>label - displayable label (name) for the referenced site</li>
-<li>type (new in 2.1) - by default, discovery sites are assumed to be update sites
-(&quot;update&quot;). By setting the value of this attribute to &quot;web&quot;,
-it is possible to indicate to Eclipse that the URL should be treated as a
-regular Web hyperlink that can be directly displayed in a suitable browser.</li>
-</ul>
-</li>
-</ul>
-</li>
-
-<li>&lt;includes&gt; - optional reference to a nested feature that is considered
-to be part of this feature. Nested features must be located on the same
-update site as this feature
-<ul>
-<li>id - required nested feature identifier. If the feature is a patch (see the 
-&lt;requires&gt; section below), this must be the id of another patch.</li>
-<li>version - required nested feature version</li>
-<li>optional - it is possible to include a feature as optional when
-this attribute is &quot;true&quot;. Users are allowed to not install optional
-features, disable them if they are installed, and install them later. A missing
-optional feature is not treated as an error.</li>
-<li>name - if an optional feature is missing, Eclipse cannot render its
-name properly. This attribute can be used as a 'place holder' to allow Eclipse
-to render the name of the optional feature when it is not installed.</li>
-<li>search-location - an included feature can be updated by patches. 
-By default, search location is &quot;root&quot;
-which means that URL specified in the &quot;update&quot; element within the
-&quot;url&quot; element of the parent will be considered. If an included feature
-has its own &quot;update&quot; element defined, it will be ignored by default.
-If the parent feature wants to allow the child to be updated from its own
-location, it can set this attribute to &quot;both&quot; or &quot;self&quot;.</li>
-<li>os - optional operating system specification. A comma-separated list of
-operating system designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this entry should only be installed on one of the specified OS
-systems. If this attribute is not specified, the entry can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of entry regardless of this setting).</li>
-<li>arch - optional machine architecture specification. A comma-separated list
-of architecture designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this feature should only be installed on one of the specified
-systems. If this attribute is not specified, the feature can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of feature regardless of this setting).</li>
-<li>ws - optional windowing system specification. A comma-separated list of
-window system designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this entry should only be installed on one of the specified WS's.
-If this attribute is not specified, the entry can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of entry regardless of this setting).</li>
-<li>nl - optional locale specification. A comma-separated list of locale designators
-defined by Java. Indicates this entry should only be installed on a system
-running with a compatible locale (using Java locale-matching rules). If
-this attribute is not specified, the entry can be installed on all systems
-(language-neutral implementation). This information is used as a hint by
-the installation and update support (user can force installation of entry
-regardless of this setting).</li>
-</ul>
-</li>
-
-<li>&lt;requires&gt; - optional feature dependency information. Is expressed in
-terms of plug-in dependencies. If specified, is enforced by the installation
-and update support at the time of installation
-<ul>
-<li>&lt;import&gt; - dependency entry. Specification and processing is a subset
-of the &lt;import&gt; specification in plugin.xml
-<ul>
-<li>plugin - identifier of dependent plug-in, if plug-in is used to express dependency</li>
-<li>feature (new in 2.1) - identifier of dependent feature, if feature is used to
-express dependency. <b>Either plugin or feature attribute must be set, but not
-both. </b>If &quot;patch&quot; is &quot;true&quot;, feature attribute must be
-used.</li>
-<li>version - optional plug-in version specification. If &quot;patch&quot; is
-&quot;true&quot;, version must be set.</li>
-<li>match - optional matching rule. Valid values and processing are as follows:
-<ul>
-<li>if version attribute is not specifies, the match attribute (if specified) is ignored.</li>
-<li><b><i>perfect</i></b> - dependent plug-in version must match exactly the
-specified version. If &quot;patch&quot; is &quot;true&quot;, &quot;perfect&quot;
-is assumed and other values cannot be set.</li>
-<li><b><i>equivalent</i></b> - dependent plug-in version must be at least at
-the version specified, or at a higher service level (major and minor version
-levels must equal the specified version).</li>
-<li><b><i>compatible</i></b> - dependent plug-in version must be at least at
-the version specified, or at a higher service level or minor level (major
-version level must equal the specified version).</li>
-<li><b><i>greaterOrEqual</i></b> - dependent plug-in version must be at least
-at the version specified, or at a higher service, minor or major level.</li>
-</ul>
-</li>
-<li>patch - if &quot;true&quot;, this constraint declares the enclosing
-feature to be a patch for the referenced feature. Certain rules must be followed
-when this attribute is set:
-<ul>
-  <li>feature attribute must be used to identifier of feature being patched</li>
-  <li>version attribute must be set</li>
-  <li>match attribute should not be set and &quot;perfect&quot; value will be
-    assumed.</li>
-  <li>if other features are &lt;include&gt;'ed, they must also be patches.</li>
-</ul>
-A patch is a special feature that carries newer versions of plug-ins for
- the feature it is patching.  It does not replace the feature.  A patch can also
- carry other patches by inclusion.</li>
-</ul>
-</li>
-</ul>
-</li>
-
-<li>&lt;plugin&gt; - identifies referenced plug-in
-<ul>
-<li>id - required plug-in identifier (from plugin.xml)</li>
-<li>version - required plug-in version (from plugin.xml)</li>
-<li>fragment - optional specification indicating if this entry is a plug-in fragment. Default is "false"</li>
-<li>os - optional operating system specification. A comma-separated list of
-operating system designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this entry should only be installed on one of the specified os
-systems. If this attribute is not specified, the entry can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of entry regardless of this setting).</li>
-<li>arch - optional machine architecture specification. A comma-separated list
-of architecture designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this feature should only be installed on one of the specified
-systems. If this attribute is not specified, the feature can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of feature regardless of this setting).</li>
-<li>ws - optional windowing system specification. A comma-separated list of
-window system designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this entry should only be installed on one of the specified WS's.
-If this attribute is not specified, the entry can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of entry regardless of this setting).</li>
-<li>nl - optional locale specification. A comma-separated list of locale designators
-defined by Java. Indicates this entry should only be installed on a system
-running with a compatible locale (using Java locale-matching rules). If
-this attribute is not specified, the entry can be installed on all systems
-(language-neutral implementation). This information is used as a hint by
-the installation and update support (user can force installation of entry
-regardless of this setting).</li>
-<li>download-size - optional hint supplied by the feature packager, indicating
-the download size in KBytes of the referenced plug-in archive. If not specified,
-the download size is not known (<b>Implementation Note:</b> the implementation
-needs to distinguish between "not known" and 0 size)</li>
-<li>install-size - optional hint supplied by the feature packager, indicating
-the install size in KBytes of the referenced plug-in archive. If not specified,
-the install size is not known (<b>Implementation Note:</b> the implementation
-needs to distinguish between "not known" and 0 size)</li>
-<li>unpack (new in 3.0) - optional specification supplied by the feature packager,
-indicating that plugin is capable of running from a jar, and contents of plug-in
-jar should not be unpacked into a directory.  Default is "true".
-(<b>Implementation Note:</b> partial plug-ins - delivered in a feature specifying
-<tt>org.eclipse.update.core.DeltaInstallHandler</tt> as an install handler should
-not set unpack to &quot;false&quot;)</li>
-</ul>
-</li>
-
-<li>&lt;data&gt; - identifies non-plugin data that is part of the feature
-<ul>
-<li>id - required data identifier in the form of a relative path.</li>
-<li>os - optional operating system specification. A comma-separated list of
-operating system designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this entry should only be installed on one of the specified OS's.
-If this attribute is not specified, the entry can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of entry regardless of this setting).</li>
-<li>arch - optional machine architecture specification. A comma-separated list
-of architecture designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this feature should only be installed on one of the specified
-systems. If this attribute is not specified, the feature can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of feature regardless of this setting).</li>
-<li>ws - optional windowing system specification. A comma-separated list of
-window system designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this entry should only be installed on one of the specified WS's
-If this attribute is not specified, the entry can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of entry regardless of this setting).</li>
-<li>nl - optional locale specification. A comma-separated list of locale designators
-defined by Java. Indicates this entry should only be installed on a system
-running with a compatible locale (using Java locale-matching rules). If
-this attribute is not specified, the entry can be installed on all systems
-(language-neutral implementation). This information is used as a hint by
-the installation and update support (user can force installation of entry
-regardless of this setting).</li>
-<li>download-size - optional hint supplied by the feature packager, indicating
-the download size in KBytes of the referenced data archive. If not specified,
-the download size is not known (<b>Implementation Note:</b> the implementation
-needs to distinguish between "not known" and 0 size)</li>
-<li>install-size - optional hint supplied by the feature packager, indicating
-the install size in KBytes of the referenced data archive. If not specified,
-the install size is not known (<b>Implementation Note:</b> the implementation
-needs to distinguish between "not known" and 0 size)</li>
-</ul>
-</li>
-</ul></p>
-<p>When interacting with
-the update site, the feature implementation maps the <tt>&lt;plugin></tt>
-and <tt>&lt;data></tt> elements into path identifiers used by the site
-to determine the actual files to download and install. The default feature
-implementation supplied by Eclipse constructs the path identifiers as follows:</p>
-<ul>
-<li>
-<tt>&lt;plugin></tt> element results in a path entry in the form "<tt>plugins/&lt;pluginId>_&lt;pluginVersion>.jar</tt>"
-(for example, "<tt>plugins/org.eclipse.core.boot_2.0.0.jar</tt>")</li>
-
-<li>
-<tt>&lt;data></tt> element results in a path entry in the form "<tt>features/&lt;featureId>_&lt;featureVersion>/&lt;dataId></tt>"
-(for example, "f<tt>eatures/com.xyz.tools_1.0.3/examples.zip</tt>")</li>
-</ul>
-<p>Note, that in general the feature.xml&nbsp; manifest documents should specify
-UTF-8 encoding. For example:</p>
-<pre>&lt;?xml version="1.0" encoding="UTF-8"?></pre>
-<p>Translatable text contained in the feature.xml can be separated into
-feature&lt;_locale>.properties files using Java property bundle conventions.
-Note that the translated strings are used at installation time (i.e. do
-not employ the plug-in fragment runtime mechanism).&nbsp;
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/help_infocenter.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/help_infocenter.html
deleted file mode 100644
index 2f316ef..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/help_infocenter.html
+++ /dev/null

@@ -1,196 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-   <head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-      <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-      <meta name="Author" content="eclipse.org">
-      <title>
-         Infocenter
-      </title>
-  <link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   </head>
-<body>
-
-<h1>Installing the help system as an infocenter</h1>
-
-<p>You can allow your users to access the help system over the Internet or an 
-intranet, by installing the infocenter and the documentation 
-plug-ins on   a server. Clients view help by navigating 
-to a URL, and the help system is shown in their web browser. The infocenter help 
-system can be used both for client applications and for web applications, either 
-of which can have their help accessed remotely. All features of help system except infopops and 
-active help are supported. </p>
-<P>The infocenter help system allows passing number of options that can
-be used to customize various aspects of the infocenter. The following
-options are supported:</P>
-<UL>
-	<LI><B>-eclipsehome</B> <I>eclipseInstallPath</I> - specifies Eclipse
-	installation directory. This directory is a parent to "plugins" directory
-	and eclipse executable.  The option must be provided, when current directory
-	from which infocenter is launched, is
-	not the same as Eclipse installation directory.</LI>
-
-	<LI><B>-data</B> <I>instanceArea</I> - specifies a path that Eclipse
-	can use to write instance data.  The value can be an absolute path of
-	a directory, or a path relative to Eclipse installation directory.
-	The option must be provided when Eclipse is installed in the read only
-	location, or has been customized to override osgi.instance.area or
-	osgi.instance.area.default properties. </LI>
-
-	<LI><B>-host</B> <I>helpServerHost</I> - specifies host name of the
-	interface that help server will use. It overrides host name specified in
-	the application server plugin preferences.</LI>
-
-	<LI><B>-port</B> <I>helpServerPort</I> - specifies port number that
-	help server will use. It overrides port number specified in the
-	application server plugin preferences.</LI>
-
-  <li><b>-locales</b> <I>localeList</I> - specifies a list of locales that infocenter
-   will recognize and provide a customized content for.
-   If the option is not specified, infocenter will build navigation, and index documents
-   for each preferred locale of the browsers accessing the infocenter.
-   When the option is present, locales from browser requests will be matched with locales in the list.
-   If browser preferred locale does not exist in the list, but its language part does, it will be used.
-   Subsequently, additional browser locales in decreased order of preference will be matched against
-   the list.  If none of the browser locales (or its language part) matches any locale on the list,
-   the client will be served content in the default locale - server locale or locale passed with -nl option.
-   For example using options <pre>-nl en -locales de en es fr it ja ko pt_BR zh_CN zh_TW</pre>
-   will cause infocenter operating in 10 locales.  All other locales will receive content for en locale.</li>
-
-	<LI><B>-dir ltr</B> or <B>-dir rtl</B> - forces left-to-right or right-to-left
-	  rendering direction of help UI in the browser for all languages. By default
-	  direction is determined based on the browser locale.</LI>
-
-	<LI><B>-noexec</B> - indicates that Eclipse executable
-	should not be used.  You may need to use this option when running
-	on a platform for which Eclipse executable is not available.</LI>
-
-	<LI>Additionally, most <A
-		href="../../../org.eclipse.platform.doc.user/tasks/running_eclipse.htm">options
-	accepted by Eclipse executable</A> can be passed. They are especially
-	useful during debugging and for applying customization to Eclipse.
-	For example, passing options
-	<PRE><EM><SPAN style="font-style: normal">-vmargs -Xmx256M</SPAN></EM> </PRE>
-	increases memory available to the infocenter and will allow serving a larger book collection.</LI>
-</UL>
-<H2><B>Installation/packaging</B></H2>
-<P>These steps are for the help system integrator and are not meant to
-address all the possible scenarios. It is assumed that all your
-documentation is delivered as Eclipse plug-ins and, in general, you are
-familiar with the eclipse help system.</P>
-<OL>
-	<LI>Download the Eclipse Platform Runtime Binary
-	driver from <A target="_blank" href="http://www.eclipse.org/downloads/">www.eclipse.org</A>.</LI>
-	<LI>Install (unzip) the driver in a directory, <VAR>d:\myApp</VAR>. This will create an eclipse sub-directory,
-	d:\myApp\eclipse that contains the code required for the Eclipse
-	platform (which includes the help system).</LI>
-</OL>
-<H2><B>How to start or stop infocenter from command line</B></H2>
-<P>The org.eclipse.help.standalone.Infocenter class has a main method that you
-can use to launch infocenter from a command line. The command line
-arguments syntax is:</P>
-<PRE><EM><SPAN style="font-style: normal">-command start | shutdown | [-eclipsehome eclipseInstallPath] [-data instanceArea] [-host helpServerHost] [-locales localeList] [-port helpServerPort] [-dir rtl] [-noexec] [platform options] [-vmargs JavaVMarguments]</SPAN></EM></PRE>
-<P>To start an infocenter on port 8081 issue a start command by running</P>
-<PRE>java -classpath d:\myApp\eclipse\plugins\org.eclipse.help.base_3.1.0.jar org.eclipse.help.standalone.Infocenter -command start -eclipsehome d:\myApp\eclipse -port 8081</PRE>
-<P>To shut the infocenter down issue a shutdown command by running</P>
-
-<PRE>java -classpath d:\myApp\eclipse\plugins\org.eclipse.help.base_3.1.0.jar org.eclipse.help.standalone.Infocenter -command shutdown -eclipsehome d:\myApp\eclipse</PRE>
-<h2>Using the infocenter</h2>
-<p>Start the web server. Point a web browser to the path &quot;help&quot; web 
-application running on a port specified when starting the infocenter.&nbsp; On the machine the infocenter is installed, this would be 
-http://localhost:8081/help/. </p>
-<H2><B>How to start or stop infocenter from Java</B></H2>
-<P>When including infocenter as part of another application, it may be more convenient to start it and stop using Java APIs instead of using system commands. Follow the steps if it is the case:</P>
-<OL>
-	<LI>Make sure <EM><SPAN style="font-style: normal">d:\myApp\eclipse\plugins\org.eclipse.help.base_3.1.0.jar</SPAN></EM>
-	is on your app classpath. The class you use to start, and shut
-	down the infocenter isorg.eclipse.help.standalone.Infocenter.</LI>
-	<LI>Create an array of String containing options that you want to pass
-	to the infocenter. Typically, the eclipsehome and port options are needed. <PRE><EM><SPAN
-		style="font-style: normal">String[] options = new String[] { &quot;-eclipsehome&quot;, &quot;d:\\myApp\\eclipse&quot; , &quot;-port&quot;, &quot;8081&quot; };</SPAN></EM> </PRE></LI>
-	<LI>In your application, create an instance of the Help class by
-	passing the options.<PRE><EM><SPAN style="font-style: normal">Infocenter infocenter = new Help(options);</SPAN></EM> </PRE>
-	</LI>
-	<LI>To start the help system: <PRE><EM><SPAN style="font-style: normal">helpSystem.start();</SPAN></EM></PRE>
-	</LI>
-	<LI>
-	<P>To shut the infocenter down:</P>
-	<PRE><EM><SPAN style="font-style: normal">helpSystem.shutdown();</SPAN></EM> </PRE></LI>
-</OL>
-<H2>Making infocenter available on the web</H2>
-<p>Eclipse contains a complete infocenter and does not require other server software to run.
-However, in unsecure environment like Internet, it is recommended infocenter is not
-accessed directly by clients, but is made available through an HTTP server or an application
-server. Most servers come with modules or servlets for delegating certain request to other
-web resources. For example, one may configure a proxy module of Apache HTTP Server
-to redirect requests made to <I>http://mycompany.com/myproduct/infocenter</I> to
-<I>http://internalserver:8081/help</I> that runs an infocenter. Adding the  lines
-</p>
-<pre>LoadModule proxy_module modules/ApacheModuleProxy.dll
-ProxyPass /myproduct/infocenter http://internalserver:8081/help
-ProxyPassReverse /myproduct/infocenter http://internalserver:8081/help
-</pre>
-<p>to conf/httpd.conf file of Apache server running mycompany web site accomplishes this.
-</p>
-<p>Some versions of Apache HTTP server, may contain AddDefaultCharset directive enabled in configuration file.
-Remove the directive or replace with</p>
-<pre>AddDefaultCharset Off</pre>
-<p>to have browsers display documents using correct character set.
-</p>
-
-<H2>Running multiple instance of infocenter</H2>
-<P>Multiple instances of infocenter can be run on a machine from one installation.
-Each started instance must use its own port and be provided with a workspace,
-hence <code>-port</code> and <code>-data</code> options must be specified.
-The instances can serve documentation from different set of plug-ins, by providing
-a valid platform configuration with <code>-configuration</code> option.
-</P>
-<P>If <code>-configuration</code> is not used and configuration directory is shared
-among multiple infocenter instances, with overlapping set of locales, it must be ensured
-that all search indexes are created by one infocenter instance before another instance is started.
-Indexes are saved in the configuration directory, and write access is not synchronized
-across infocenter processes.
-</P>
-
-<H2>[Optional] Installing a minimal set of plug-ins</H2>
- <p>The infocenter does not require the entire &nbsp;Eclipse Platform package.
-It is possible to run the infocenter with the following plug-ins (located
-in the&nbsp; eclipse\plugins directory):<br>
-</p>
-<p><code>
-org.apache.lucene<br>
-org.eclipse.core.runtime<br>
-org.eclipse.help<br>
-org.eclipse.help.appserver<br>
-org.eclipse.help.base<br>
-org.eclipse.help.webapp<br>
-org.eclipse.osgi<br>
-org.eclipse.tomcat<br>
-org.eclipse.update.configurator<br>
-</code>
-</p>
-<p>
-Some documentation plug-ins may have dependencies on other plug-ins,
-usually by specifying required plug-ins in their plugin.xml.
-The dependent plug-ins need to be installed on the infocenter as well.
-Additionally, plug-ins that were designed for earlier than 3.0 version of Eclipse
-implicitly require an <code>org.eclipse.core.runtime.compatibility</code>
-being present plug-in to work.
-</p>
-<p>
-Infocenter plug-ins can be updated without restarting the infocenter, using
-commands explained in <a href="help_infocenter_update.html">
-Updating a running infocenter from command line</a> topic.  To use this
-functionality, the minimal set of plug-ins must include
- <code>org.eclipse.update.core</code> plug-in.
-</p>
-
-<p>See <a href="help_preferences.html">Help System Preferences</a> for more
-information on customizing help system.</p>
-
-
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/help_infocenter_update.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/help_infocenter_update.html
deleted file mode 100644
index 96558f4..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/help_infocenter_update.html
+++ /dev/null

@@ -1,111 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Updating a running infocenter from command line</title>
-</head>
-<body>
-
-<h1>Updating a running infocenter from command line</h1>
-In addition to the start and shutdown commands supported by the infocenter and documented in
-<a href="help_infocenter.html">Installing the help system as an infocenter</a>
-, infocenter supports set of command
-for invoking update manager operations in running eclipse.
-You can install, update, enable, disable features, or list installed features,
-or features available on an update site, or adding an extension site to the running
-infocenter.  In effect, you can change set of running documentation plug-ins without
- a need for shutting the infocenter down or restarting it.
-<br>
- <br>
-Start infocenter as explained in
-<a href="help_infocenter.html">Installing the help system as an infocenter</a>.
-  If you are running minimal set of plug-ins, add org.eclipse.update.core plug-in to the list of plug-ins before launching infocenter using the start command.<br>
-Launch infocenter update commands as follows, where [ ] means optional argument and arguments in italics must be provided by the user.<br>
-After performing updates as needed, apply the changes by issuing the apply command
- as the last step.  It reflects the changes in the current session.
- If you do not call apply command, the changes will take
-effect the next time infocenter is started.<br>
-	<br>
-<b>Installing a feature from a remote site</b>:<br>
- java -cp plugins/org.eclipse.help.base_3.1.0.jar org.eclipse.help.standalone.Infocenter<br>
- &nbsp;&nbsp;&nbsp; -command install <br>
- &nbsp;&nbsp;&nbsp; -featureId <i>feature_id </i><br>
- &nbsp;&nbsp;&nbsp; -version <i>version </i><br>
- &nbsp;&nbsp;&nbsp; -from <i>remote_site_url</i> <br>
- &nbsp;&nbsp;&nbsp; [-to <i>target_site_dir</i>] <br>
-<p>
-	<b>Example:</b> <code>java -cp plugins/org.eclipse.help.base_3.1.0.jar org.eclipse.help.standalone.Infocenter -command install  -from http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/optionalSite/ -featureId com.example.root -version 1.0.0</code>
-	</p>
- <br>
-<b>Updating an existing feature or all features</b>:<br>
- java -cp plugins/org.eclipse.help.base_3.1.0.jar org.eclipse.help.standalone.Infocenter<br>
- &nbsp;&nbsp;&nbsp; -command update<br>
- &nbsp;&nbsp;&nbsp; [-featureId <i>feature_id </i>]<br>
-  &nbsp;&nbsp;&nbsp; [-version <i>version </i>]<br>
-<br>
-<b>Enabling (configuring) a specified feature:</b><br>
- java -cp plugins/org.eclipse.help.base_3.1.0.jar org.eclipse.help.standalone.Infocenter<br>
- &nbsp;&nbsp;&nbsp; -command enable<br>
- &nbsp;&nbsp;&nbsp; -featureId <i>feature_id </i><br>
- &nbsp;&nbsp;&nbsp; -version <i>version </i><br>
- &nbsp;&nbsp;&nbsp; [-to <i>target_site_dir</i>] <br>
-<br>
-<b>Disabling (unconfiguring) a specified feature:</b><br>
- java -cp plugins/org.eclipse.help.base_3.1.0.jar org.eclipse.help.standalone.Infocenter<br>
- &nbsp;&nbsp;&nbsp; -command disable<br>
- &nbsp;&nbsp;&nbsp; -featureId <i>feature_id </i><br>
- &nbsp;&nbsp;&nbsp; -version <i>version </i><br>
- &nbsp;&nbsp;&nbsp; [-to <i>target_site_dir</i>] <br>
-<br>
-<b>Uninstalling a specified feature:</b><br>
- java -cp plugins/org.eclipse.help.base_3.1.0.jar org.eclipse.help.standalone.Infocenter<br>
- &nbsp;&nbsp;&nbsp; -command uninstall<br>
- &nbsp;&nbsp;&nbsp; -featureId <i>feature_id </i><br>
- &nbsp;&nbsp;&nbsp; -version <i>version </i><br>
- &nbsp;&nbsp;&nbsp; [-to <i>target_site_dir</i>] <br>
-<br>
-In all the above commands where the -to target_site_dir is specified, corresponding
-configured target site at given directory will be used. If it is not specified,
-then the default local product site is used.<br>
-<br>
-If you only need to verify if the operation would succeed, in the above commands, (i.e. it satisfies the constraints), without actually performing it,
-then add <b><em>-verifyOnly=true</em></b> to the list of arguments.<br>
-
-<br><b>Searching a remote site, listing all available features for install:</b><br>
- java -cp plugins/org.eclipse.help.base_3.1.0.jar org.eclipse.help.standalone.Infocenter<br>
- &nbsp;&nbsp;&nbsp; -command search<br>
- &nbsp;&nbsp;&nbsp; -from <i>remote_site_url</i> <br>
-
-<br><b>Listing installed features:</b><br>
- java -cp plugins/org.eclipse.help.base_3.1.0.jar org.eclipse.help.standalone.Infocenter<br>
- &nbsp;&nbsp;&nbsp; -command listFeatures<br>
- &nbsp;&nbsp;&nbsp; -from <i>local_site_dir</i> <br>
- <br>
- The features are listed as:
- <br>
- <code>
- Site: <em>site url </em><br>
-  &nbsp;&nbsp;Feature: <em>id version</em>  enabled (or disabled)
- </code>
- <br>
-
-<br><b>Adding a local site with more features:</b><br>
- java -cp plugins/org.eclipse.help.base_3.1.0.jar org.eclipse.help.standalone.Infocenter<br>
- &nbsp;&nbsp;&nbsp; -command addSite<br>
- &nbsp;&nbsp;&nbsp; -from <i>local_site_dir</i> <br>
-
-<br><b>Removing a local site:</b><br>
- java -cp plugins/org.eclipse.help.base_3.1.0.jar org.eclipse.help.standalone.Infocenter<br>
- &nbsp;&nbsp;&nbsp; -command removeSite<br>
- &nbsp;&nbsp;&nbsp; -to <i>local_site_dir</i> <br>
- 
-<br><b>Applying the changes:</b><br>
- java -cp plugins/org.eclipse.help.base_3.1.0.jar org.eclipse.help.standalone.Infocenter<br>
- &nbsp;&nbsp;&nbsp; -command apply<br> 
-<br>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/help_preferences.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/help_preferences.html
deleted file mode 100644
index 2eee515..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/help_preferences.html
+++ /dev/null

@@ -1,382 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>Help System Preferences</title>
-</head>
-<body>
-<h1>Help System Preferences</h1>
-<p>The Eclipse help system can be configured and branded to suit your
-product by
-specifying custom defaults for number of help preferences.<br>
-</p>
-<p>The Help system itself is divided up into a number of separate
-plug-ins.
-These tables shows available preferences, and which plug-in
-defines them.&nbsp; Consult <a href="../../guide/product_configproduct.htm">Customizing
-a product</a> on how to override some of these preferences.<br>
-&nbsp;
-</p>
-<h2>
-org.eclipse.help plug-in:<br>
-</h2>
-<table border="1">
-  <tbody>
-    <tr>
-      <td style="font-weight: bold;">Preference key</td>
-      <td style="font-weight: bold;">Usage<br>
-      </td>
-      <td style="font-weight: bold;">Default</td>
-    </tr>
-    <tr>
-      <td><code>baseTOCS</code> </td>
-      <td>Toc ordering. Ordered list of help TOC's (books) or TOC
-categories as they would appear on the bookshelf. All the other TOCS and categories
-will follow these. Non-present TOCs or categories on this list will be ignored. For TOCs, use
-the location of the TOC as /pluginId/path/to/toc.xml. For categories, use the category
-id.</td>
-      <td><code>/org.eclipse.platform.doc.user/toc.xml,<br>
-/org.eclipse.jdt.doc.user/toc.xml,<br>
-/org.eclipse.platform.doc.isv/toc.xml,<br>
-/org.eclipse.jdt.doc.isv/toc.xml,<br>
-/org.eclipse.pde.doc.user/toc.xml</code></td>
-    </tr>
-    <tr>
-      <td><code>ignoredTOCS</code> </td>
-      <td>Disabling TOCs. List of help TOCs (books) or TOC categories that
-will be ignored by the help system.  The disabled TOCs/categories will not
-appear in the list of books, cannot be linked. Topics defined by disabled TOCs
-will not be available from search.
-Non-present TOCs or categories in this list will be ignored. For TOCs, use the
-location of the TOC as /pluginId/path/to/toc.xml. For categories, use the
-category id.</td>
-      <td><br>
-      </td>
-    </tr>
-  </tbody>
-</table>
-<h2>
-org.eclipse.help.base plug-in:<br>
-</h2>
-<table border="1">
-  <tbody>
-    <tr>
-      <td style="font-weight: bold;">Preference key</td>
-      <td style="font-weight: bold;">Usage<br>
-      </td>
-      <td style="font-weight: bold;">Default</td>
-    </tr>
-    <tr>
-      <td><code>banner</code></td>
-      <td>Location of the banner page to display in the top frame<br>
-Example: <code>banner=/org.eclipse.help.webapp/advanced/banner.html</code></td>
-      <td><br>
-      </td>
-    </tr>
-    <tr>
-      <td><code>banner_height</code></td>
-      <td>Height of the banner frame<br>
-Example: <code>banner_height=60</code></td>
-      <td><br>
-      </td>
-    </tr>
-    <tr>
-      <td><code>help_home</code></td>
-      <td>The page to show in the content area when opening help.
-Specify your html page as <code>/pluginId/path/to/home.html</code>.</td>
-      <td><code>/org.eclipse.help.base/doc/help_home.html</code></td>
-    </tr>
-    <tr>
-      <td><code>linksView</code></td>
-      <td>Set to <code>true</code> or <code>false</code> to control the visibility
-of the
-related links view.<br>
-Note: this option has no effect in the infocenter.</td>
-      <td><code>true</code></td>
-    </tr>
-    <tr>
-      <td><code>bookmarksView</code></td>
-      <td>Set to <code>true</code> or <code>false</code> to control the visibility
-of the
-bookmarks view.<br>
-Note: this option has no effect in the infocenter.</td>
-      <td><code>true</code></td>
-    </tr>
-    <tr>
-      <td><code>windowTitlePrefix</code></td>
-      <td>Set to <code>true</code> or <code>false</code> to control the title of
-the browser
-window. If <code>true</code>, the
-title will have a form "Help - <code>&lt;PRODUCT_NAME&gt;</code>",
-otherwise the title will be
-"<code>&lt;PRODUCT_NAME&gt;</code>",
-where <code>&lt;PRODUCT_NAME&gt;</code>
-is the name of
-Eclipse product set in the primary feature.</td>
-      <td><code>true</code></td>
-    </tr>
-    <tr>
-      <td><code>loadBookAtOnceLimit</code></td>
-      <td>The maximum number of topics a book can have, for the
-navigation to be loaded by the browser as one document. Navigation for
-larger books is loaded dynamically, few levels at a time. More topics
-are downloaded as necessary, when branches are expanded.</td>
-      <td><code>1000</code></td>
-    </tr>
-    <tr>
-      <td><code>dynamicLoadDepthsHint</code></td>
-      <td>Suggested number of
-levels in topic navigation downloaded to the browser for large books.
-The value needs to be greater than <code>0</code>. The actual number of levels
-can
-differ for wide tree if suggested number of levels contains large
-number of topics.<br>
-      </td>
-      <td><code>3</code></td>
-    </tr>
-    <tr>
-      <td><code>imagesDirectory</code></td>
-      <td>Directory containing images used in the help view. Images
-must have the same name as those in the org.eclipse.help.webapp
-plug-in.
-Use the <code>/pluginID/directory</code>
-format.</td>
-      <td><code>images</code></td>
-    </tr>
-    <tr>
-      <td><code>advanced.toolbarBackground</code></td>
-      <td>CSS background for toolbars. Value is used in browsers
-that display advanced help UI.</td>
-      <td><code>ButtonFace</code></td>
-    </tr>
-    <tr>
-      <td><code>advanced.viewBackground</code></td>
-      <td>CSS background for navigation views. Value is used in
-browsers that display advanced help UI.</td>
-      <td><code>Window</code></td>
-    </tr>
-    <tr>
-      <td><code>advanced.toolbarFont</code></td>
-      <td>CSS font for toolbars. Value is used in browsers that
-display advanced help UI.</td>
-      <td><code>icon</code></td>
-    </tr>
-    <tr>
-      <td><code>advanced.viewFont</code></td>
-      <td>CSS font for navigation views. Value is used in browsers
-that display advanced help UI.</td>
-      <td><code>icon</code></td>
-    </tr>
-    <tr>
-      <td><code>basic.toolbarBackground</code></td>
-      <td>Background color for toolbars. Value is used in browsers
-displaying basic help UI.</td>
-      <td><code>#D4D0C8</code></td>
-    </tr>
-    <tr>
-      <td><code>basic.viewBackground</code></td>
-      <td>Background color for navigation views. Value is used in
-browsers displaying basic help UI.</td>
-      <td><code>#FFFFFF</code></td>
-    </tr>
-    <tr>
-      <td><code>locales</code></td>
-      <td>List of locales that infocenter will recognize and
-provide a customized content for; if locales (or languages) accepted by
-client browser are not matched with any locales in this list, the
-browser will be served content for default locale - the server locale,
-or locale specified by eclipse <code>-nl</code>
-command line option; if list is not
-specified, the browser will be served contents for its preferred
-locale; note: not providing this option may result in a large
-memory and disk space requirements as navigations and indexes will be
-created for each distinct preferred locale among browsers accessing the
-infocenter.<br>
-Example: <code>locales=en ja zh_CN
-zh_TW</code></td>
-      <td><br>
-      </td>
-    </tr>
-    <tr>
-      <td><code>productIndex</code></td>
-      <td>If per-product, pre-built documentation index is provided with the
-product, the ID of the plug-in delivering the index must be specified
-to the help system here.</td>
-      <td><br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;"><code>always_external_browser</code><br>
-      </td>
-      <td style="vertical-align: top;">Use embedded when possible (on
-Windows or Linux), or always external.&nbsp; Setting to true will force
-use of external browser.&nbsp; Option has no effect if embedded browser
-is not available on a given platform.<br>
-      </td>
-      <td style="vertical-align: top;"><code>false</code><br>
-      </td>
-    </tr>
-    <tr>
-      <td><code>default_browser</code></td>
-      <td><p>Default external browser.&nbsp; ID of one of the external
-  web browsers contributed to org.eclipse.help.base.browser extension
-  point that help system will use. The browser's adapter <code>available()</code>
-  method must return true on the current system.</p>
-      <p>This preference controls external browsers in stand-alone help mode.
-      In the workbench mode, help uses browsers provided by workbench browser
-        support.</p></td>
-      <td>default dynamically set based on the browser available on a
-given system<br>
-      </td>
-    </tr>
-    <tr>
-      <td><code>custom_browser_path</code></td>
-      <td><p>Executable path for custom browser</p>
-      <p>This preference controls external browsers in stand-alone help mode.
-        In the workbench mode, help uses browsers provided by workbench browser
-      support.</p></td>
-      <td><code>C:\Program Files\Internet Explorer\IEXPLORE.EXE" %1</code> - on
-Windows,<br>
-      <code>"konqueror %1"</code> - on
-Linux<br>
-      <code>"mozilla %1"</code> - on
-other platforms
-      </td>
-    </tr>
-    <tr>
-      <td><code>showDisabledActivityTopics</code></td>
-      <td>Help system filters topics from disabled
-capabilities.&nbsp; This option controls this behavior and existence
-of&nbsp; Show All Topics button.<br>
-Accepted values: <code>never</code>, <code>off</code>, <code>on</code>, <code>always</code><br>
-&nbsp;<code>never</code> - topic from
-disabled capabilities are not shown<br>
-&nbsp;<code>off</code> - user can
-choose to show all topics, disabled topics
-initially hidden<br>
-&nbsp;<code>on</code> - user can choose
-to show all topics, all topics initially
-shown<br>
-&nbsp;<code>always</code> - topic from
-disabled capabilities are shown (filtering
-disabled)</td>
-      <td><code>off</code></td>
-    </tr>
-    <tr>
-      <td><code>activeHelp</code></td>
-      <td>Allows enabling and disabling execution of active help.
-The option has no effect in the infocenter setup, where active help is
-disabled.<br>
-Accepted values:<br>
-&nbsp;<code>true</code> - default
-active help actions enabled<br>
-&nbsp;<code>false</code> - active help
-framework disabled</td>
-      <td><code>true</code></td>
-    </tr>
-    <tr>
-      <td><code>window_infopop</code></td>
-      <td>Allows enabling the old-style infopops when help key is pressed in 
-		workbench windows. If false, the new dynamic help view will open 
-		instead.</td>
-      <td><code>false</code></td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;"><code>
-		dialog_infopop</code><br>
-      </td>
-      <td style="vertical-align: top;">Allows enabling the old-style infopops 
-		when help key is pressed in dialogs. If false, the new dynamic help 
-		window will open instead.<br>
-      </td>
-      <td style="vertical-align: middle;"><code>false</code><br>
-      </td>
-    </tr>
-  </tbody>
-</table>
-<h2>
-org.eclipse.help.appserver plug-in:<br>
-</h2>
-<table border="1">
-  <tbody>
-    <tr>
-      <td style="font-weight: bold;">Preference key</td>
-      <td style="font-weight: bold;">Usage<br>
-      </td>
-      <td style="font-weight: bold;">Default</td>
-    </tr>
-    <tr>
-      <td><code>port</code></td>
-      <td>The port number on which the sever listens for http
-requests. If port is not given, an arbitrary
-port is picked by the system.</td>
-      <td>&nbsp;</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;"><code>host</code><br>
-      </td>
-      <td style="vertical-align: top;"><p>The host address or name to use
-  for connecting to the server. The default is nothing, and eclipse will
-  pick up an available local address.</p>
-        <p>Products using help in local mode (workbench or stand-alone, not infocenter),
-          can set this preference to &quot;<code>127.0.0.1</code>&quot; to
-          ensure help server is not exposed to other users on the network.<br>
-        </p></td>
-      <td style="vertical-align: top;"><br>
-      </td>
-    </tr>
-  </tbody>
-</table>
-<h2>
-org.eclipse.tomcat plug-in:<br>
-</h2>
-<table border="1">
-  <tbody>
-    <tr>
-      <td style="font-weight: bold;">Preference key</td>
-      <td style="font-weight: bold;">Usage<br>
-      </td>
-      <td style="font-weight: bold;">Default</td>
-    </tr>
-    <tr>
-      <td><code>acceptCount</code></td>
-      <td>The maximum queue length for incoming connection requests
-when all possible request processing threads are in use. Any requests
-received when the queue is full will be refused.</td>
-      <td><code>100</code></td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;"><code>maxProcessors</code><br>
-      </td>
-      <td style="vertical-align: top;">The maximum number of request
-processing threads to be created by this Connector, which therefore
-determines the maximum number of simultaneous requests that can be
-handled.<br>
-      </td>
-      <td style="vertical-align: top;"><code>75</code><br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;"><code>minProcessors</code><br>
-      </td>
-      <td style="vertical-align: top;">The number of request processing
-threads that will be created when this Connector is first started. This
-attribute should be set to a value smaller than that set for
-maxProcessors.<br>
-      </td>
-      <td style="vertical-align: top;"><code>5</code><br>
-      </td>
-    </tr>
-  </tbody>
-</table>
-<br>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/help_product_index.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/help_product_index.html
deleted file mode 100644
index 16dcd99..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/help_product_index.html
+++ /dev/null

@@ -1,85 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-                           
-  <meta http-equiv="Content-Type"
- content="text/html; charset=iso-8859-1">
-                           
-  <meta name="Author" content="eclipse.org">
-  <title>Pre-built documentation index</title>
-                                                
-  <link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1"
- type="text/css">
-</head>
-<body>
-<h1>Pre-built documentation index</h1>
-<p>When user searches help contents of a product, the search is performed
-within a documentation index. &nbsp;By default, this index &nbsp;is created
-on the first invocation of help search, but can be pre-built and delivered
-to the user with each plug-in, since 3.1, or as a complete index for a product. &nbsp;This
-prevents
-indexing
-from
-occurring
-on
-the user machine and lets the user obtain first search results faster.</p>
-<h2><b>Building a documentation index for a plug-in.</b></h2>
-<p>To build an index follow the steps:</p>
-<ul>
-  <li>add an <code>index</code> element to the <code>org.eclipse.help.toc
-      extension</code> in a documentation plug-in, to specify directory where
-      index will exist,</li>
-  <li>create an index for a desired locale by running the <code>help.buildHelpIndex</code> ANT
-    task for each plug-in and fragment with documentation.<br>
-</li>
-</ul>
-<h2><b>Building an index for a product</b></h2>
-<p>Per-product index is a one aggregate index of all documentation in the product.
-  It should be used in scenarios in which the set of documentation plug-ins is
-  not changing. For example an info-center installation will benefit
-  from per-product
-  index.</p>
-<p>To build an index follow the steps:<br>
-</p>
-<ul>
-  <li>build a product, including all documentation plug-ins,</li>
-  <li>create an index for a desired locale by running this command:     
-                          
-    <pre>eclipse -nosplash -application org.eclipse.help.base.indexTool -vmargs -DindexOutput=<i>outputDirectory</i> -DindexLocale=<i>locale</i></pre>
-from the directory containing the product. &nbsp;The following arguments
-need to be set :<br>
-    <b>outputDirectory</b> - specifies path of the directory where the index
-is to be saved<br>
-    <b>locale</b> - specifies locale for which the index will be built<br>
-  </li>
-</ul>
-<p>For example, running<br>
-</p>
-<pre>eclipse -nosplash -application org.eclipse.help.base.indexTool -vmargs -DindexOutput=d:/build/com.my.plugin -DindexLocale=en</pre>
-<p>will result in file <b>doc_index.zip</b> being saved in the <b>nl/en</b>
-directory that will be created under <b>d:/build/com.my.plugin</b>. &nbsp;The
-zip will contain index of contents of documents that are available to users
-when they run the product in the <b>en</b> locale.<br>
-</p>
-<h2><b>Packaging and Installation of the product's pre-built index</b> </h2>
-Pre-built indices, the <b>doc_index.zip</b> files, need to be packaged as
-a plug-in. &nbsp; You can choose to use a plug-in associated with the primary
-feature, or choose to package the index for each language into separate fragments.<br>
-<br>
-For example, if product's documentation is available in three languages, say
-English, German and Simplified Chinese, a plug-in com.my.plugin can have the following structure:<br>
-<pre>com.my.plugin/<br>              plugin.xml<br>              nl/<br>                 de/<br>                    doc_index.zip<br>                 en/<br>                    doc_index.zip<br>                 zh/<br>                    CN/<br>                       doc_index.zip<br>              other files of this plugin</pre>
-<br>
- The ID of the plug-in needs to be specified as a <b>productIndex</b> preference
-for org.eclipse.help.base plug-in.&nbsp;For plug-in in the above example, the
-plugin_customization.ini
-file needs to contain the entry<br>
-<pre>org.eclipse.help.base/productIndex=com.my.plugin<br></pre>
-
-<br>
-<br>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/help_standalone.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/help_standalone.html
deleted file mode 100644
index bc73736..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/help_standalone.html
+++ /dev/null

@@ -1,161 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-   <head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-      <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-      <meta name="Author" content="eclipse.org">
-      <title>
-         Installing Standalone Help
-      </title>
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   </head>
-<body>
-
-<h1>Installing the stand-alone help system</h1>
-<p>If you are creating an application that is not based on 
-the Eclipse framework, you can still use the Eclipse help system. Your 
-application can package and install the stand-alone help system, a very small 
-version of Eclipse that has  everything except the help system stripped out 
-of it. Then, your application can make API calls from its Help menu, or from UI 
-objects, to launch the help browser. The stand-alone help system has all the 
-features of the integrated help system, except infopops and active help. When an application is not Java based, or help is required when the application is not running, it is possible to use stand-alone help from a system shell, a shell script or a desktop shortcut and provide command line options instead of calling Java APIs.</p>
-<P>The stand-alone help system allows passing number of options that can be used to customize various aspects of the help system. The following options are supported:</P><UL>
-	<LI><B>-eclipsehome</B> <I>eclipseInstallPath</I> - specifies Eclipse
-	installation directory. This directory is a parent to "plugins" directory
-	and eclipse executable.  The option must be provided, when current directory
-	from which infocenter is launched, is
-	not the same as Eclipse installation directory.</LI>
-	<LI><B>-host</B> <I>helpServerHost</I> - specifies host name of the
-	interface that help server will use. It overrides host name specified
-	the application server plugin preferences.</LI>
-
-	<LI><B>-data</B> <I>instanceArea</I> - specifies a path that Eclipse
-	can use to write instance data.  The value can be an absolute path of
-	a directory, or a path relative to Eclipse installation directory.
-	The option must be provided when Eclipse is installed in the read only
-	location, or has been customized to override osgi.instance.area or
-	osgi.instance.area.default properties. </LI>
-
-	<LI><B>-port</B> <I>helpServerPort</I> - specifies port number that
-	help server will use. It overrides port number specified the
-	application server plugin preferences.</LI>
-
-	<LI><B>-dir ltr </B> or<B> -dir rtl</B> - sets left-to right or right-to-left
-	  rendering direction of help UI in the browser.</LI>
-
-	<LI>Additionally, most <A
-		href="../../../org.eclipse.platform.doc.user/tasks/running_eclipse.htm">options
-	accepted by Eclipse executable</A> can be passed. They are especially useful during debugging and for applying customization to Eclipse.
-	For example, passing an option
-	<PRE><EM><SPAN style="font-style: normal">-nl fr_FR</SPAN></EM> </PRE>
-	will start help system in French language instead of a language specified by the machine's locale.</LI>
-
-</UL>
-<h2><b>Installation/packaging</b> </h2>
-These steps are for the help system 
-  integrator and are not meant to address all the possible scenarios. It is 
-  assumed   that 
-  all your documentation is delivered as Eclipse plug-ins and, in general, you are 
-  familiar with the eclipse help system.
-<ol>
-  <li>Download the Eclipse Platform Runtime Binary driver from
-  <a target="_blank" href="http://www.eclipse.org/downloads/">www.eclipse.org</a>.</li>
-  <li>Install (unzip) the driver under your application directory, for 
-  example, <var>d:\myApp</var>. This will create an eclipse sub-directory, d:\myApp\eclipse that 
-  contains the code required for the Eclipse platform (which includes the help 
-  system). </li>
-</ol>
-<h2><b>How to call the help classes from Java</b></h2>
-<ol>
-  <li>Make sure <em><span style="font-style: normal">d:\myApp\eclipse\plugins\org.eclipse.help.base_3.1.0.jar</span></em> is 
-  on your app classpath. The class you use to start, launch, and shut down the help system is 
-  org.eclipse.help.standalone.Help. </li>
-  <li>Create an array of String containing options that you want to pass to help system support. Typically, the eclipsehome option is needed.
-  <PRE><EM><SPAN style="font-style: normal">String[] options = new String[] { &quot;-eclipsehome&quot;, &quot;d:\\myApp\\eclipse&quot; };</SPAN></EM> </PRE></li>
-	<LI>In your application, create an instance of the Help class by
-	passing the options. This object should be held onto until
-	the end of your application.<PRE><EM><SPAN style="font-style: normal">Help helpSystem = new Help(options);</SPAN></EM> </PRE>
-	</LI>
-	<li>To start the help system:
-  <pre><em><span style="font-style: normal">helpSystem.start();</span></em> </pre>
-  </li>
-  <li>To invoke help when needed:
-  <pre><em><span style="font-style: normal">helpSystem.displayHelp();</span></em> </pre>
-  <p>You can also call help on specific primary TOC files or topics:</p>
-  <pre>helpSystem.displayHelp(&quot;/com.mycompany.mytool.doc/toc.xml&quot;);
-helpSystem.displayHelp(&quot;/com.mycompany.mytool.doc/tasks/task1.htm&quot;);</pre>
-  </li>
-  <li>To launch context sensitive help, call 
-  helpSystem.displayContext(contextId, x, y) where contextId is a fully 
-  qualified context id. The screen coordinates, x and y, are not currently used.
-  </li>
-	<LI>
-	<P>At the end of your application, to shutdown the help system:</P>
-	<PRE><EM><SPAN style="font-style: normal">helpSystem.shutdown();</SPAN></EM> </PRE></LI>
-</ol>
-<h2><b>How to call the help from command line</b> </h2>
-<p>The org.eclipse.help.standalone.Help class has a  main method that you 
-can use to launch stand-alone help from a command 
-line. The command line arguments syntax is:</p>
-<pre><em><span style="font-style: normal">-command start | shutdown | (displayHelp [href]) [-eclipsehome eclipseInstallPath] [-data instanceArea] [-host helpServerHost] [-port helpServerPort] [-dir rtl] [platform options] [-vmargs JavaVMarguments]</span></em></pre>
-<P>A simple way to display help is to invoke</P>
-<pre>java -classpath d:\myApp\eclipse\plugins\org.eclipse.help.base_3.1.0.jar org.eclipse.help.standalone.Help -command displayHelp</pre><P>from within d:\myApp\eclipse directory. To display specific TOC file or topic use</P>
-
-<PRE>java -classpath d:\myApp\eclipse\plugins\org.eclipse.help.base_3.1.0.jar org.eclipse.help.standalone.Help -command displayHelp /com.mycompany.mytool.doc/tasks/task1.htm</PRE>
-<P>The calls above to display help will cause help system to start, display help, and keep running to allow a user to continue browsing  help after the command is executed. To control the life cycle of the help system, use start and shutdown commands, in addition to the displayHelp command. For example, you may call</P>
-<PRE>java -classpath d:\myApp\eclipse\plugins\org.eclipse.help.base_3.1.0.jar org.eclipse.help.standalone.Help -command start</PRE>
-
-
-<H2>[Optional] Installing a minimal set of plug-ins</H2>
- <p>The stand-alone help does not require the entire &nbsp;Eclipse Platform package.
-It is possible to run the stand-alone help with the following plug-ins (located
-in the&nbsp; eclipse\plugins directory):<br>
-</p>
-<p><code>
-org.apache.lucene<br>
-org.eclipse.core.runtime<br>
-org.eclipse.help<br>
-org.eclipse.help.appserver<br>
-org.eclipse.help.base<br>
-org.eclipse.help.webapp<br>
-org.eclipse.osgi<br>
-org.eclipse.tomcat<br>
-org.eclipse.update.configurator<br>
-</code>
-</p>
-
-<p>
-On Windows and Linux, the following plugins and fragments 
-are required on top of the minimal configuration to provide robust browser support
-(an SWT-embedded Internet Explorer on Windows and Mozilla on Linux or stand-alone
- system browser on Windows).</p>
-<p><code> 
-org.eclipse.core.expressions<br>
-org.eclipse.help.ui<br>
-org.eclipse.jface<br>
-org.eclipse.swt<br>
-org.eclipse.swt.win32 or org.eclipse.swt.gtk<br>
-org.eclipse.ui<br>
-org.eclipse.ui.workbench<br>
-</code>
-</p>
-<p>
-Some documentation plug-ins may have dependencies on other plug-ins,
-usually by specifying required plug-ins in their plugin.xml.
-The dependent plug-ins need to be installed on the infocenter as well.
-Additionally, plug-ins that were designed for earlier than 3.0 version of Eclipse
-implicitly require an <code>org.eclipse.core.runtime.compatibility</code>
-being present plug-in to work.
-</p>
-
-<p>See <a href="help_preferences.html">Help System Preferences</a> for more
-information on customizing help system.</p>
-
-<A href="../../../org.eclipse.help.base/preferences.ini">
-org.eclipse.help.base preferences</A>
-
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/index.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/index.html
deleted file mode 100644
index cc41b7c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/index.html
+++ /dev/null

@@ -1,70 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Eclipse Platform Release Notes</title>
-</head>
-<body>
-
-<h1>
-Other Reference Information</h1>
-The following specifications, white papers, and design notes describe various
-aspects of the Eclipse Platform.
-<h2>Basic platform information</h2>
-<ul>
-  <li> <a href="runtime-options.html">Runtime options</a></li>
-  <li> <a href="eclipsestarter.html">Starting Eclipse from Java</a></li>
-  <li> <a href="api-usage-rules.html">API Rules of Engagement</a></li>
-  <li> <a href="naming.html">Naming Conventions</a></li>
-  <li> <a href="terminology.html">Glossary of terms</a></li>
-  <li> <a href="overview-platform.html">Map of Platform Plug-ins</a></li>
-  <li> <a href="plugin_manifest.html">Plug-in Manifest</a></li>
-  <li> <a href="project_description_file.html">Project Description File</a></li>
-  <li> <a href="bundle_manifest.html">OSGi Bundle Manifest</a></li>
-  <li> <a href="message_bundles.html">Message Bundles in Eclipse 3.1</a></li>
-  <li> <a href="multi_user_installs.html">Multi-user Installs</a></li>
-</ul>
-<h2>User interface information</h2>
-<ul>
-<li>
-<a href="ui_accessibility_tips.html">Tips for making user interfaces accessible</a></li>
-
-</ul>
-<h2>Help information</h2>
-<ul>
-<li>
-<a href="help_product_index.html">Pre-built documentation index</a></li>
-
-<li>
-<a href="help_standalone.html">Installing the stand-alone help system</a></li>
-
-<li>
-<a href="help_infocenter.html">Installing the help system as an infocenter</a></li>
-
-<li>
-<a href="help_preferences.html">Help system preferences</a></li>
-
-</ul>
-<h2>Product install and configuration information</h2>
-<ul>
-  <li> <a href="eclipse-install.html">How to write an Eclipse Installer</a></li>
-  <li> <a href="about_customization.html">About.ini File Format</a></li>
-  <li> <a href="plugin_archive.html">Plug-in archives</a></li>
-  <li> <a href="feature_manifest.html">Feature manifest</a></li>
-  <li> <a href="feature_archive.html">Feature archives</a></li>
-  <li> <a href="update_platform_xml.html">The platform.xml File</a></li>
-  <li> <a href="update_sitemap.html">Update server site map</a></li>
-  <li> <a href="update_policy.html">Update policy control</a></li>
-  <li> <a href="update_standalone.html">Running update manager from command line</a></li>
-</ul>
-<h2><a href="http://www.eclipse.org/articles/index.html">Eclipse.org articles
-index</a></h2>
-<p>The eclipse corner site contains technical articles about many topics of
-interest.&nbsp; Check the index regularly for the latest technical information
-regarding Eclipse.</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/message_bundles.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/message_bundles.html
deleted file mode 100644
index a7bb829..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/message_bundles.html
+++ /dev/null

@@ -1,99 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Message Bundles</title>
-</head>
-
-<body>
-<h1>Message Bundles In Eclipse 3.1</h1>
-<h2>Description </h2>
-<p>Standard Java ResourceBundles have quite inefficient space characteristics. 
-  Since a running Eclipse tends to have many externalized messages we have implemented 
-  a new message bundle system to be used in Eclipse. The mechanism is quite simple 
-  and completely generic - it can be used anywhere.</p>
-<h3>Summary of the new approach:</h3>
-<ul>
-  <li><code> messages.properties </code>- this file is same as before except all 
-    keys need to be valid Java identifiers.</li>
-  <li> Each message file has a corresponding Java class.</li>
-  <li> Each key/value pair in the file has a <code>public static String</code> 
-    field whose name is the same as the message key.</li>
-  <li> When message bundles are loaded, the values of the fields are set to be 
-    the values from the <code>messages.properties </code>files.</li>
-  <li> The message properties files are purged from memory. </li>
-</ul>
-<h3>When creating a new message:</h3>
-<ul>
-  <li> Create a field in your <code>Messages.java </code>file.</li>
-  <li> Create a key/value pair in your <code>messages.properties </code>file where 
-    the key name matches the field name,</li>
-  <li> To reference the message, simply reference the field (e.g. <code>Messages.my_key</code>) 
-    rather than the standard lookup.</li>
-</ul>
-<h2>Example Files:</h2>
-<h3>Client Code</h3>
-<h4>Old Code: </h4>
-<pre><code>public class MyClass {
-  public void myMethod() {
-    String message;
-    ...
-    // no args
-    message = Messages.getString(&quot;key.one&quot;); //$NON-NLS-1$
-    ...
-    // bind one arg
-    message = MessageFormat.format(Messages.getString(&quot;key.two&quot;), new Object[] {&quot;example usage&quot;}); //$NON-NLS-1$ //$NON-NLS-2$
-    ...
-  }
-}</code></pre>
-<h4>New Code:</h4>
-<pre><code>public class MyClass {
-  public void myMethod() {
-    String message;
-    ...
-    // no args
-    message = Messages.key_one;
-    ...
-    // bind one arg
-    message = NLS.bind(Messages.key_two, &quot;example usage&quot;); //$NON-NLS-1$
-    ...
-  }
-}</code></pre>
-<h3>Messages.java</h3>
-<h4>Old Code:</h4>
-<pre><code>public class Messages {
-  private static final String BUNDLE_NAME = &quot;org.eclipse.core.utils.messages&quot;; //$NON-NLS-1$
-  private static final ResourceBundle bundle = ResourceBundle.getBundle(BUNDLE_NAME);
-   
-  public static String getString(String key) {
-    try {
-      return bundle.getString(key);
-    } catch (MissingResourceException e) {
-      return key;
-    }
-  }
-}</code></pre>
-<h4>New Code:</h4>
-<pre><code>import org.eclipse.osgi.util.NLS;</code></pre>
-<pre><code>public class Messages extends NLS {
-  private static final String BUNDLE_NAME = &quot;org.eclipse.core.utils.messages&quot;; //$NON-NLS-1$
-   
-  public static String key_one;
-  public static String key_two;
-  ...
-  static {
-    NLS.initializeMessages(BUNDLE_NAME, Messages.class);
-  }
-}</code></pre>
-<h3> messages.properties</h3>
-<h4> Old Code:</h4>
-<pre>key.one = Hello world.
-key.two = This is an {0} of binding with one argument.</pre>
-<h4>New Code:</h4>
-<pre>key_one = Hello world.
-key_two = This is an {0} of binding with one argument.</pre>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/multi_user_installs.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/multi_user_installs.html
deleted file mode 100644
index ccee5cc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/multi_user_installs.html
+++ /dev/null

@@ -1,140 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Eclipse Multi-user Installs</title>
-</head>
-<body text="#000000" bgcolor="#ffffff">
-<h1>Eclipse multi-user installs</h1>
-<p> 
-  Eclipse provides a number of strategies for supporting multi-user installs. 
-  Each strategy satisfies a specific scenario. This document covers these strategies, 
-  describing when each one should be used. The intended readers are product engineers 
-  configuring an Eclipse-based product for distribution, system administrators 
-  setting up Eclipse-based products to be used through a network and developers 
-  interested in creating plug-ins that are good citizens in such setups.</p>
-<p>Last Modified: June 17th, 2005</p>
-<h2>Basic concepts</h2>
-<h3>Locations</h3>
-<p>As described in the <a href="runtime-options.html#locations">Eclipse Runtime 
-  options</a> article, there are three different locations that are important 
-  in the context of deploying Eclipse in a multi-user setup:</p>
-<ul>
-  <li> <strong>install area</strong> - the location where the Eclipse Platform 
-    is installed. This location can be read-only, since neither the Eclipse runtime 
-    nor plug-ins are supposed to write there. However, in a single user scenario, 
-    the configuration area, which is typically writable, defaults to a directory 
-    called &quot;configuration&quot; stored under the install area.</li>
-  <li> <strong>configuration area</strong> - the location where Eclipse stores 
-    essential runtime metadata (such as information about the set of plug-ins 
-    installed and the dependencies between them) and cached data in general. Eclipse 
-    cannot run without a configuration area. Plug-ins may choose to store data 
-    here that should be available regardless the workspace in use (for instance, 
-    help index files). User settings shared across workspaces are also stored 
-    under this location.</li>
-  <li><strong>instance area</strong> - the location where user files are stored, 
-    commonly called the <em>workspace</em>. It is optional, however most Eclipse-based 
-    products require an instance area to work. The instance area cannot be shared, 
-    although a single user might maintain multiple instance areas. Inside the 
-    instance area there is a special directory called .metadata, where plug-ins 
-    store their own workspace-specific metadata and user settings.</li>
-</ul>
-<h3>Configuration initialization</h3>
-<p>Before Eclipse has been run for the first time, the configuration area is basically 
-  an empty directory. This location is gradually populated by the Eclipse runtime, 
-  and other plug-ins, across Eclipse sessions. Most of the metadata kept by the 
-  Eclipse runtime (e.g. plug-in dependencies, the extension registry) is written 
-  during the shutdown of the first session. If no changes are made to the set 
-  of installed plug-ins, no data has to be written during subsequent sessions. 
-  We say the configuration is <em>initialized</em>. When the configuration is 
-  in this state, it is even possible to make the configuration area read-only. 
-  Making the configuration area read-only is useful in scenarios such as shared 
-  configurations (more on this later).</p>
-<p>The <code>-initialize</code> command-line option allows one to initialize the 
-  configuration area without requiring an Eclipse application to run. The initialization 
-  procedure forces the creation of any metadata that is written out to the configuration 
-  location during the first Eclipse session. However, there are other files kept 
-  in the configuration area that are created only when needed. Examples are:</p>
-<ul>
-  <li>Help indexes - only created for the first time the Eclipse Help system is 
-    opened. After it is created, provided the user locale does not change, no 
-    files are ever written again.</li>
-  <li>files extracted out of plug-in JARs - plug-ins shipped as JARs often need 
-    to access embedded files as plain files on the file system. For that, plug-ins 
-    call the Eclipse Runtime API <code><a href="../api/org/eclipse/core/runtime/Platform.html#asLocalURL(java.net.URL)">
-	Platform.asLocalURL(URL)</a></code>. The result is that 
-    if the URL refers to a file inside a JAR, that file will be extracted to the 
-    file system under the configuration area. Once a file is extracted, subsequent 
-    calls to <code>Platform.asLocalURL()</code> will be able to find it, so no additional extractions 
-    will occur <em>for that file</em>. A similar (actually, the original) scenario 
-    where <code>Platform.asLocalURL</code> is used that has the same consequences relates to 
-    making sure remote contents (for instance, a file accessible via a http URL) 
-    are available locally.</li>
-</ul>
-<p>For these cases (and others that 3rd-party plug-ins might introduce), the initialization 
-  procedure is not sufficient to fully initialize the configuration area. There 
-  will still be need to write to the configuration area although this need tends 
-  to disappear as all the execution paths in the application that cause files 
-  to be created in the configuration area are visited. Only after that it can 
-  be said the configuration area is fully initialized and no write access to it 
-  will ever be required in order for Eclipse to run.</p>
-<h2>Scenario #1 - private install</h2>
-<p>This is actually a single-user scenario. The Eclipse install is used by a single 
-  user, and the user has full access privileges to it. The configuration area 
-  location defaults to the configuration directory under the install location.</p>
-<p>The procedure to set up this scenario requires just making sure the user has 
-  full rights to the install location.</p>
-<h2>Scenario #2 - shared install</h2>
-<p>In this scenario, a single install area is shared by many users. The &quot;configuration&quot; 
-  directory under the install area is home only to the config.ini as shipped with 
-  the product (it is not initialized). Every user has their own local standalone 
-  configuration location.</p>
-<p>The set up for this scenario requires making the install area read-only for 
-  regular users. When users start Eclipse, this causes the configuration area 
-  to automatically default to a directory under the user home dir. If this measure 
-  is not taken, all users will end up using the same location for their configuration 
-  area, which is not supported.</p>
-<h2>Scenario #3 - shared configuration</h2>
-<p>Here users share not only an install area but also a master configuration area. 
-  Users still have, by default, their own private writable configuration areas. 
-  A user's private configuration area is cascaded to the master configuration 
-  and will not contain any interesting data if the master configuration has been 
-  fully initialized and no changes to the set of plug-ins to be installed has 
-  occurred.</p>
-<p>In this scenario, the system administrator initializes the master configuration 
-  (typically under the install location), and ensures the whole install and configuration 
-  areas are read-only to users. When users run the Eclipse-based product from 
-  the shared install location, since they do not have write access privileges 
-  to the configuration area under the install area, a local configuration area 
-  will be automatically computed and initialized.</p>
-<p>The more fully initialized the shared configuration is, the less need there 
-  is for files to be created under the local configuration.</p>
-<h3>Setting the private configuration area location</h3>
-<p>The default location for a private configuration area is:</p>
-<p><code>&lt;user-home-dir&gt;/.eclipse/&lt;product-id&gt;_&lt;product-version&gt;/configuration</code></p>
-<p>The user home dir is determined by the <code>user.home</code> Java system property. 
-  The product id and version are obtained from the product marker file <code>.eclipseproduct</code> 
-  under the Eclipse install.</p>
-<p>A non-default configuration area can be defined by setting the <a href="runtime-options.html#osgiconfigurationarea"><code>osgi.configuration.area</code></a> 
-  system property. This property can be set by the end user, but it is more convenient 
-  to set it either in the <a href="runtime-options.html#launcher">launcher .ini 
-  file</a> or the in the config.ini file at the base configuration location.</p>
-<h3>Updating</h3>
-<h4>Shared configuration</h4>
-<p>Plug-ins can be installed in/removed from the shared configuration. Users will 
-  catch up with those changes the next time Eclipse runs. It is necessary to make 
-  sure users having the shared configuration as their master configuration are 
-  not running Eclipse.</p>
-<h4>Private configuration</h4>
-<p>Users can modify their local configuration areas by installing additional plug-ins. 
-  This does not cause any changes to the shared configuration, so other users 
-  will not see the changes. Note that plug-ins configured at the shared configuration 
-  <em>cannot</em> be removed. If they are, they will be reinstalled the next time 
-  the platform starts.</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/naming.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/naming.html
deleted file mode 100644
index 9d5950e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/naming.html
+++ /dev/null

@@ -1,217 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Eclipse Platform - Naming Conventions</title>
-</head>
-<body>
-
-<h1>
-Eclipse Platform<br>
-Naming Conventions</h1>
-<font size=-1>Last revised June 24, 2002 - version for Eclipse project R2.0</font>
-<p>Naming conventions and guidelines for the Eclipse Platform:
-<ul>
-<li>
-<a href="#Java Packages">Java packages</a></li>
-
-<li>
-<a href="#Classes and Interfaces">Classes and interfaces</a></li>
-
-<li>
-<a href="#Methods">Methods</a></li>
-
-<li>
-<a href="#Variables">Variables</a></li>
-
-<li>
-<a href="#Plug-ins">Plug-ins and extension points</a></li>
-</ul>
-
-<h2>
-<a NAME="Java Packages"></a><b>Java Packages</b></h2>
-The Eclipse Platform consists of a collection of Java packages. The package
-namespace is managed in conformance with <a href="http://java.sun.com/docs/codeconv/html/CodeConventions.doc8.html#367">Sun's
-package naming guidelines</a>; subpackages should not be created without
-prior approval from the owner of the package sub-tree. The packages for
-the Eclipse platform are all subpackages <b><tt>org.eclipse</tt></b>. The
-first package name component after <b><tt>org.eclipse</tt></b> is called
-the <i>major </i>package name. The following major packages of <b><tt>org.eclipse</tt></b>
-are assigned in the Eclipse 2.0 release:
-<blockquote><b><tt>org.eclipse.ant[.*]</tt> </b>- Ant support
-<br><b><tt>org.eclipse.compare[.*]</tt></b> - Compare support
-<br><b><tt>org.eclipse.core[.*]</tt> </b>- Platform core
-<br><b><tt>org.eclipse.debug[.*]</tt> </b>- Debug
-<br><b><tt>org.eclipse.help[.*]</tt></b> - Help support
-<br><b><tt>org.eclipse.jdi[.*]</tt> </b>- Eclipse implementation of Java
-Debug Interface (JDI)
-<br><b><tt>org.eclipse.jdt[.*]</tt> </b>- Java development tools
-<br><b><tt>org.eclipse.jface[.*]</tt> </b>- JFace
-<br><b><tt>org.eclipse.pde[.*]</tt></b> - Plug-in Development Environment
-<br><b><tt>org.eclipse.search[.*]</tt></b> - Search support
-<br><b><tt>org.eclipse.swt[.*]</tt> </b>- Standard Widget Toolkit
-<br><b><tt>org.eclipse.team[.*]</tt> </b>- Team support and Version and
-  Configuration Management
-<br><b><tt>org.eclipse.tomcat[.*]</tt> </b>- Apache tomcat support
-<br><b><tt>org.eclipse.ui[.*]</tt></b> - Workbench
-<br><b><tt>org.eclipse.update[.*]</tt></b> - Update/install
-<br><b><tt>org.eclipse.webdav[.*]</tt> </b>- WebDAV support</blockquote>
-The following package name segments are reserved:
-<blockquote><b><tt>internal</tt></b> - indicates an internal implementation
-package that contains no API
-<br><b><tt>tests</tt></b> - indicates a non-API package that contains only
-test suites
-<br><b><tt>examples</tt></b> - indicates a non-API package that contains
-only examples</blockquote>
-These name are used as qualifiers, and must only appear following the major
-package name. For example,
-<blockquote><b><tt>org.eclipse.core.internal.resources</tt></b> - Correct
-usage
-<br><b><tt>org.eclipse.internal.core.resources</tt></b> - Incorrect. <b><tt>internal</tt></b>
-precedes major package name.
-<br><b><tt>org.eclipse.core.resources.internal</tt></b> - Incorrect. <b><tt>internal</tt></b>
-does not immediately follow major package name.</blockquote>
-Aside on how the Eclipse Platform is structured: The Eclipse Platform is
-divided up into <i>Core </i>and <i>UI</i>. Anything classified as Core
-is independent of the window system; applications and plug-ins that depend
-on the Core and not on the UI can run headless. The distinction between
-Core and UI does not align with the distinction between API and non-API;
-both Core and UI contain API. The UI portion of the Eclipse Platform is
-known as the Workbench. The Workbench is a high-level UI framework for
-building products with sophisticated UIs built from pluggable components.
-The Workbench is built atop JFace, SWT, and the Platform Core. SWT (Standard
-Widget Toolkit) is a low-level, OS-platform-independent means of talking
-to the native window system. JFace is a mid-level UI framework useful for
-building complex UI pieces such as property viewers. SWT and JFace are
-UI by definition. The Java tooling is a Java IDE built atop the workbench.
-End aside.</p>
-<p><b>API Packages</b>&nbsp; API packages are ones that contain classes
-and interfaces that must be made available to ISVs. The names of API packages
-need to make sense to the ISV. The number of different packages that the
-ISV needs to remember should be small, since a profusion of API packages
-can make it difficult for ISVs to know which packages they need to import.
-Within an API package, all public classes and interfaces are considered
-API. The names of API packages should not contain <b><tt>internal</tt></b>,
-<b><tt>tests</tt></b>,
-or <b><tt>examples</tt></b> to avoid confusion with the scheme for naming
-non-API packages.</p>
-<p><b>Internal Implementation Packages</b>&nbsp; All packages that are
-part of the platform implementation but contain no API that should be exposed
-to ISVs are considered internal implementation packages. All implementation
-packages should be flagged as <b><tt>internal</tt></b>, with the tag occurring
-just after the major package name. ISVs will be told that all packages
-marked <b><tt>internal</tt></b> are out of bounds. (A simple text search
-for "<tt>.internal.</tt>" detects suspicious reference in source files;
-likewise, "/<tt>internal/</tt>" is suspicious in .class files).</p>
-<p><b>Test Suite Packages</b>&nbsp; All packages containing test suites
-should be flagged as <b><tt>tests</tt></b>, with the tag occurring just
-after the major package name. Fully automated tests are the norm; so, for
-example,
-<tt>org.eclipse.core.tests.resources</tt> would contain automated
-tests for API in <tt>org.eclipse.core.resources</tt>. Interactive tests
-(ones requiring a hands-on tester) should be flagged with <b><tt>interactive</tt></b>
-as the <i>last</i> package name segment; so, for example, <tt>org.eclipse.core.tests.resources.interactive</tt>
-would contain the corresponding interactive tests.</p>
-<p><b>Examples Packages</b>&nbsp; All packages containing examples that
-ship to ISVs should be flagged as <b><tt>examples</tt></b>, with the tag
-occurring just after the major package name. For example,
-<tt>org.eclipse.swt.examples</tt>
-would contain examples for how to use the SWT API.</p>
-<p>Additional rules:
-<ul>
-<li>
-Package names should contain only lowercase ASCII alphanumerics, and avoid
-underscore <tt>_</tt> or dollar sign <tt>$</tt> characters.</li>
-</ul></p>
-
-<h2>
-<a NAME="Classes and Interfaces"></a><b>Classes and Interfaces</b></h2>
-<p><a href="http://java.sun.com/docs/codeconv/index.html">Sun's naming guidelines</a>
-states</p>
-<blockquote>Class names should be nouns, in mixed case with the first letter
-of each internal word capitalized. Try to keep your class names simple
-and descriptive. Use whole words - avoid acronyms and abbreviations (unless
-the abbreviation is much more widely used than the long form, such as URL
-or HTML).<br>&nbsp;
-<br>Examples:
-<br><tt>&nbsp;&nbsp;&nbsp; class Raster;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; class ImageSprite;</tt> <br>&nbsp;
-<br>Interface names should be capitalized like class names.</blockquote>
-<p>For interface names, we follow the "I"-for-interface convention: all interface
-names are prefixed with an "<tt>I</tt>". For example, "<tt>IWorkspace</tt>"
-or "<tt>IIndex</tt>". This convention aids code readability by making interface
-names more readily recognizable. (Microsoft COM interfaces subscribe to
-this convention).</p>
-<p>Additional rules:
-<ul>
-<li>
-The names of exception classes (subclasses of <tt>Exception</tt>) should
-follow the common practice of ending in "<tt>Exception</tt>".</li>
-</ul></p>
-
-<h2>
-<a NAME="Methods"></a><b>Methods</b></h2>
-<p><a href="http://java.sun.com/docs/codeconv/index.html">Sun's naming guidelines</a>
-states</p>
-<blockquote>Methods should be verbs, in mixed case with the first letter
-lowercase, with the first letter of each internal word capitalized.<br>&nbsp;
-<br>Examples:
-<br><tt>&nbsp;&nbsp;&nbsp; run();</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; runFast();</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; getBackground();</tt></blockquote>
-Additional rules:
-<ul>
-<li>
-The named of methods should follow common practice for naming getters (<tt>get<i>X</i>()</tt>),
-setters (<tt>set<i>X</i>()</tt>), and predicates (<tt>is<i>X</i>()</tt>,
-<tt>has<i>X</i>()</tt>).</li>
-</ul>
-
-<h2>
-<a NAME="Variables"></a><b>Variables</b></h2>
-<p><a href="http://java.sun.com/docs/codeconv/index.html">Sun's naming guidelines</a>
-states</p>
-<blockquote>Except for variables, all instance, class, and class constants
-are in mixed case with a lowercase first letter. Internal words start with
-capital letters. Variable names should not start with underscore <tt>_</tt>
-or dollar sign <tt>$ </tt>characters, even though both are allowed.<br>&nbsp;
-<br>Variable names should be short yet meaningful. The choice of a variable
-name should be mnemonic - that is, designed to indicate to the casual observer
-the intent of its use. One-character variable names should be avoided except
-for temporary "throwaway" variables. Common names for temporary variables
-are <tt>i</tt>, <tt>j</tt>, <tt>k</tt>, <tt>m</tt>, and <tt>n</tt> for
-integers; <tt>c</tt>, <tt>d</tt>, and <tt>e</tt> for characters.<br>&nbsp;
-<br>Examples:
-<br><tt>&nbsp;&nbsp;&nbsp; int i;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; char c;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; float myWidth;</tt></blockquote>
-<p>(Note: we are no longer following the convention that prefixes non-constant
-field names with "<tt>f</tt>", such as "<tt>fWidget</tt>".)</p>
-<h2>
-<a NAME="Constants"></a><b>Constants</b></h2>
-<p><a href="http://java.sun.com/docs/codeconv/index.html">Sun's naming guidelines</a>
-states</p>
-<blockquote>The names of variables declared class constants and of ANSI
-constants should be all uppercase with words separated by underscores (&quot;_&quot;).<br>&nbsp;
-<br>Examples:
-<br><tt>&nbsp;&nbsp;&nbsp; static final int MIN_WIDTH = 4;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; static final int MAX_WIDTH = 999;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; static final int GET_THE_CPU = 1;</tt></blockquote>
-
-<h2>
-<a NAME="Plug-ins"></a><b>Plug-ins and Extension Points</b></h2>
-<p>All plug-ins, including the ones that are part of the Eclipse Platform,
-like the Resources and Workbench plug-ins, must have unique identifiers
-following the same naming pattern as Java packages. For example, workbench
-plug-ins are named <b><tt>org.eclipse.ui[.*]</tt></b>.</p>
-<p>The plug-in namespace is managed hierarchically; do not create plug-in
-without prior approval from the owner of the enclosing namespace.</p>
-<p>Extension points that expect multiple extensions should have plural
-names. For example, "<tt>builders</tt>" rather than "<tt>builder</tt>".
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/overview-platform.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/overview-platform.html
deleted file mode 100644
index b4b0649..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/overview-platform.html
+++ /dev/null

@@ -1,414 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html>
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Map of Platform Plug-ins</title>
-</head>
-
-<body>
-
-<h1>Eclipse Platform<br>
-Map of Platform Plug-ins</h1>
-<p>The Eclipse Platform provides basic support for plug-ins, resources, and the
-workbench.</p>
-<p>The Eclipse Platform itself is divided up into a number of separate plug-ins.
-The following table shows which API packages are found in which plug-ins as of
-Eclipse 3.1. This table is useful for
-determining which plug-ins a given plug-in should include as prerequisites.</p>
-<center>
-<table border="1" width="80%">
-  <tr>
-    <td><b>API Package</b></td>
-    <td><b>Required plug-in id</b></td>
-    <td>Notes</td>
-  </tr>
-  <tr>
-    <td><tt>org.apache.tools.ant[.*]<br>
-   org.apache.tools.bzip2<br>
-   org.apache.tools.mail<br>
-   org.apache.tools.tar<br>
-   org.apache.tools.zip</tt></td>
-    <td><tt>org.apache.ant</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.apache.lucene[.*]</tt></td>
-    <td><tt>org.apache.lucene</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ant.core</tt></td>
-    <td><tt>org.eclipse.ant.core</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.compare<br>
-    org.eclipse.compare.contentmergeviewer<br>
-    org.eclipse.compare.rangedifferencer<br>
-    org.eclipse.compare.structuremergeviewer</tt></td>
-    <td><tt>org.eclipse.compare</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.core.commands<br>
-    org.eclipse.core.commands.common<br>
-    org.eclipse.core.commands.contexts<br>
-    org.eclipse.core.commands.operations</tt></td>
-    <td><tt>org.eclipse.core.commands</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.core.expressions</tt></td>
-    <td><tt>org.eclipse.core.expressions</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.core.filebuffers<br>
-    org.eclipse.core.filebuffers.manipulation</tt></td>
-    <td><tt>org.eclipse.core.filebuffers</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.core.resources<br>
-    org.eclipse.core.resources.refresh<br>
-    org.eclipse.core.resources.team</tt></td>
-    <td><tt>org.eclipse.core.resources</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt> org.eclipse.core.runtime<br>
-    org.eclipse.core.runtime.content<br>
-    org.eclipse.core.runtime.dynamichelpers<br>
-    org.eclipse.core.runtime.jobs<br>
-    org.eclipse.core.runtime.preferences<br>
-    org.eclipse.osgi[.*]<br>
-    org.osgi[.*]</tt></td>
-    <td><tt>org.eclipse.core.runtime</tt></td>
-    <td>[<a href="#Note 1">1</a>]</td>
-  </tr>
-  <tr>
-    <td><tt><i>org.eclipse.core.boot (obsolete)<br>
-      org.eclipse.core.runtime.model (obsolete)</i></tt></td>
-    <td><tt>org.eclipse.core.runtime.compatibility</tt></td>
-    <td>[<a href="#Note 2">2</a>]</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.core.variables</tt></td>
-    <td><tt>org.eclipse.core.variables</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.debug.core<br>
-    org.eclipse.debug.core.model<br>
-    org.eclipse.debug.core.sourcelookup<br>
-    org.eclipse.debug.core.sourcelookup.containers</tt></td>
-    <td><tt>org.eclipse.debug.core</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt> org.eclipse.debug.ui<br>
-    org.eclipse.debug.ui.actions<br>
-    org.eclipse.debug.ui.console<br>
-    org.eclipse.debug.ui.memory<br>
-    org.eclipse.debug.ui.sourcelookup</tt></td>
-    <td><tt>org.eclipse.debug.ui</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.help</tt></td>
-    <td><tt>org.eclipse.help</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.help.browser<br>
-     org.eclipse.help.search<br>
-     org.eclipse.help.standalone</tt></td>
-    <td><tt>org.eclipse.help.base</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.help.ui<br>
-    org.eclipse.help.ui.browser</tt></td>
-    <td><tt>org.eclipse.help.ui</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.jface<br>
-    org.eclipse.jface.action<br>
-    org.eclipse.jface.action.images<br>
-    org.eclipse.jface.bindings<br>
-    org.eclipse.jface.bindings.keys<br>
-    org.eclipse.jface.bindings.keys.formatting<br>
-    org.eclipse.jface.commands<br>
-    org.eclipse.jface.contexts<br>
-    org.eclipse.jface.dialogs<br>
-    org.eclipse.jface.dialogs.images<br>
-    org.eclipse.jface.images<br>
-    org.eclipse.jface.operation<br>
-    org.eclipse.jface.preference<br>
-    org.eclipse.jface.preference.images<br>
-    org.eclipse.jface.resource<br>
-    org.eclipse.jface.util<br>
-    org.eclipse.jface.viewers<br>
-    org.eclipse.jface.viewers.deferred<br>
-    org.eclipse.jface.window<br>
-    org.eclipse.jface.wizard<br>
-    org.eclipse.jface.wizard.images</tt></td>
-    <td><tt>org.eclipse.ui</tt></td>
-    <td>[<a href="#Note 3">3</a>]</td>
-  </tr>
-  <tr>
-    <td><tt> org.eclipse.jface.contentassist<br>
-    org.eclipse.jface.contentassist.images<br>
-    org.eclipse.jface.text (split)<br>
-    org.eclipse.jface.text.contentassist<br>
-    org.eclipse.jface.text.formatter<br>
-    org.eclipse.jface.text.hyperlink<br>
-    org.eclipse.jface.text.information<br>
-    org.eclipse.jface.text.link (split)<br>
-    org.eclipse.jface.text.presentation<br>
-    org.eclipse.jface.text.quickassist<br>
-    org.eclipse.jface.text.reconciler<br>
-    org.eclipse.jface.text.revisions<br>
-    org.eclipse.jface.text.rules<br>
-    org.eclipse.jface.text.source (split)<br>
-    org.eclipse.jface.text.source.projection<br>
-    org.eclipse.jface.text.source.projection.images<br>
-    org.eclipse.jface.text.templates (split)<br>
-    org.eclipse.jface.text.templates.persistence</tt></td>
-    <td><tt>org.eclipse.jface.text</tt></td>
-    <td>[<a href="#Note 4">4</a>]</td>
-  </tr>
-  <tr>
-    <td><tt> org.eclipse.jface.text (split)<br>
-    org.eclipse.jface.text.link (split)<br>
-    org.eclipse.jface.text.projection<br>
-    org.eclipse.jface.text.source (split)<br>
-    org.eclipse.jface.text.templates (split)<br>
-    org.eclipse.text.edits<br>
-    org.eclipse.text.undo</tt></td>
-    <td><tt>org.eclipse.text</tt></td>
-    <td>[<a href="#Note 4">4</a>]</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ltk.core.refactoring<br>
-    org.eclipse.ltk.core.refactoring.participants</tt></td>
-    <td><tt>org.eclipse.ltk.core.refactoring</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ltk.ui.refactoring</tt></td>
-    <td><tt>org.eclipse.ltk.ui.refactoring</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.search.core.text<br>
-	org.eclipse.search.ui<br>
-	org.eclipse.search.ui.actions<br>
-    org.eclipse.search.ui.text</tt></td>
-    <td><tt>org.eclipse.search</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.swt<br>
-    org.eclipse.swt.accessibility<br>
-    org.eclipse.swt.awt<br>
-    org.eclipse.swt.browser<br>
-    org.eclipse.swt.custom<br>
-    org.eclipse.swt.dnd<br>
-    org.eclipse.swt.events<br>
-    org.eclipse.swt.graphics<br>
-    org.eclipse.swt.layout<br>
-    org.eclipse.swt.printing<br>
-    org.eclipse.swt.program<br>
-    org.eclipse.swt.widgets</tt></td>
-    <td><tt>org.eclipse.ui</tt></td>
-    <td>[<a href="#Note 5">5</a>]</td>
-  </tr>
-  <tr>
-    <td><tt> org.eclipse.swt.ole.win32</tt></td>
-    <td><tt>org.eclipse.swt.win32.win32.x86</tt></td>
-    <td>[<a href="#Note 9">9</a>]</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.team.core<br>
-    org.eclipse.team.core.subscribers<br>
-    org.eclipse.team.core.synchronize<br>
-    org.eclipse.team.core.variants</tt></td>
-    <td><tt>org.eclipse.team.core</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.team.ui<br>
-    org.eclipse.team.ui.synchronize</tt></td>
-    <td><tt>org.eclipse.team.ui</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui.browser</tt></td>
-    <td><tt>org.eclipse.ui.browser</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui.cheatsheets</tt></td>
-    <td><tt>org.eclipse.ui.cheatsheets</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui.console<br>
-    org.eclipse.ui.console.actions</tt></td>
-    <td><tt>org.eclipse.ui.console</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui.editors.text<br>
-      org.eclipse.ui.editors.text.templates<br>
-      org.eclipse.ui.texteditor (split)</tt></td>
-    <td><tt>org.eclipse.ui.editors</tt></td>
-    <td>[<a href="#Note 6">6</a>]</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui.forms<br>
-    org.eclipse.ui.forms.editor<br>
-    org.eclipse.ui.forms.events<br>
-    org.eclipse.ui.forms.widgets</tt></td>
-    <td><tt>org.eclipse.ui.forms</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui.navigator</tt></td>
-    <td><tt>org.eclipse.ui.navigator</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui.navigator.resources</tt></td>
-    <td><tt>org.eclipse.ui.navigator.resources</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui (split)<br>
-    org.eclipse.ui.about<br>
-    org.eclipse.ui.actions (split)<br>
-    org.eclipse.ui.activities<br>
-    org.eclipse.ui.application<br>
-    org.eclipse.ui.branding<br>
-    org.eclipse.ui.browser<br>
-    org.eclipse.ui.commands<br>
-    org.eclipse.ui.contexts<br>
-    org.eclipse.ui.dialogs (split)<br>
-    org.eclipse.ui.fieldassist<br>
-    org.eclipse.ui.handlers<br>
-    org.eclipse.ui.help<br>
-    org.eclipse.ui.intro<br>
-    org.eclipse.ui.keys<br>
-    org.eclipse.ui.model (split)<br>
-    org.eclipse.ui.operations<br>
-    org.eclipse.ui.part (split)<br>
-    org.eclipse.ui.plugin<br>
-    org.eclipse.ui.preferences<br>
-    org.eclipse.ui.presentations<br>
-    org.eclipse.ui.progress<br>
-    org.eclipse.ui.services<br>
-    org.eclipse.ui.testing<br>
-    org.eclipse.ui.themes<br>
-    org.eclipse.ui.views<br>
-    org.eclipse.ui.wizards</tt></td>
-    <td><tt>org.eclipse.ui</tt></td>
-    <td>[<a href="#Note 7">7</a>,<a href="#Note 8">8</a>]</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui (split)<br>
-    org.eclipse.ui.actions (split)<br>
-    org.eclipse.ui.dialogs (split)<br>
-    org.eclipse.ui.ide<br>
-    org.eclipse.ui.ide.dialogs<br>
-    org.eclipse.ui.model (split)<br>
-    org.eclipse.ui.part (split)<br>
-    org.eclipse.ui.views.bookmarkexplorer<br>
-    org.eclipse.ui.views.framelist<br>
-    org.eclipse.ui.views.markers<br>
-    org.eclipse.ui.views.navigator<br>
-    org.eclipse.ui.views.properties<br>
-    org.eclipse.ui.views.tasklist<br>
-    org.eclipse.ui.wizards.datatransfer<br>
-    org.eclipse.ui.wizards.newresource</tt></td>
-    <td><tt>org.eclipse.ui.ide</tt></td>
-    <td>[<a href="#Note 8">8</a>]</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui.intro.config</tt></td>
-    <td><tt>org.eclipse.ui.intro</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui.views.contentoutline<br>
-      org.eclipse.ui.views.properties</tt></td>
-    <td><tt>org.eclipse.ui.views</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui.contentassist<br>
-      org.eclipse.ui.texteditor (split)<br>
-      org.eclipse.ui.texteditor.link<br>
-      org.eclipse.ui.texteditor.quickdiff<br>
-      org.eclipse.ui.texteditor.spelling<br>
-      org.eclipse.ui.texteditor.templates</tt></td>
-    <td><tt>org.eclipse.ui.workbench.texteditor</tt></td>
-    <td>[<a href="#Note 6">6</a>]</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.update.configurator</tt></td>
-    <td><tt>org.eclipse.update.configurator</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.update.configuration<br>
-    org.eclipse.update.core<br>
-    org.eclipse.update.core.model<br>
-    org.eclipse.update.operations<br>
-    org.eclipse.update.search<br>
-    org.eclipse.update.standalone</tt></td>
-    <td><tt>org.eclipse.update.core</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.update.ui</tt></td>
-    <td><tt>org.eclipse.update.ui</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-</table>
-</center>
-<p><a name="Note 1">Note 1</a>: Plug-ins needing access to the
-Eclipse runtime API must list <tt>org.eclipse.core.runtime</tt> (or <tt>org.eclipse.core.runtime.compatibility</tt>)
-as a prerequisite plug-in. <tt>org.eclipse.core.runtime</tt> re-exports API from
-the OSGi-specific plug-ins (e.g., <tt>org.eclipse.osgi</tt>). The OSGi plug-ins should never be explicitly listed as prerequisites.</p>
-<p><a name="Note 2">Note 2</a>: These pre-3.0 API packages are obsolete and have been moved to the <tt>org.eclipse.core.runtime.compatibility</tt> 
-plug-in.</p><p><a name="Note 3">Note 3</a>: Plug-ins needing access to the JFace API must list <tt>org.eclipse.ui</tt> as a prerequisite plug-in.
-<tt>org.eclipse.ui</tt> re-exports API from the JFace plug-in. The <tt>org.eclipse.jface
-</tt>plug-in should never be explicitly listed as a prerequisite.</p><p><a name="Note 4">Note
-4</a>: Some
-of the JFace text packages are split between the <tt>org.eclipse.jface.text</tt>
-and the <tt>org.eclipse.text</tt> plug-ins.</p>
-<p><a name="Note 5">Note 5</a>: Plug-ins needing access to the SWT API must list <tt>org.eclipse.ui</tt> as a prerequisite plug-in.
-<tt>org.eclipse.ui</tt> re-exports API from the SWT plug-in. The <tt>org.eclipse.swt
-</tt>plug-in should never be explicitly listed as a prerequisite.</p>
-<p><a name="Note 6">Note 6</a>: The <tt>
-      org.eclipse.ui.texteditor</tt> package is split between the <tt>org.eclipse.ui.editors</tt>
-and the <tt>org.eclipse.ui.workbench.texteditor</tt> plug-ins.</p>
-<p><a name="Note 7">Note 7</a>: Plug-ins needing access to the Workbench UI API must list <tt>org.eclipse.ui</tt> as a prerequisite plug-in.
-<tt>org.eclipse.ui</tt> re-exports API from the <tt>org.eclipse.ui.workbench</tt> plug-in.
-The <tt>org.eclipse.ui.workbench </tt>plug-in should never be explicitly listed as
-a prerequisite.</p>
-<p><a name="Note 8">Note 8</a>: Some of the UI packages are split between the <tt>org.eclipse.ui</tt>
-and the <tt>org.eclipse.ui.ide</tt> plug-ins.</p>
-<p><a name="Note 9">Note 9</a>: The plug-in <tt>org.eclipse.swt.win32.win32.x86</tt> is available on Win32/x86 platforms only.</p>
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_archive.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_archive.html
deleted file mode 100644
index e6cc5a3..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_archive.html
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Plugin-in Archives</title>
-</head>
-<body>
-
-<h1>
-Plug-in Archives</h1>
-Plug-ins and plug-in fragments are individually packaged as separate Java
-.jars. Standard Java jar facilities are used for constructing plug-in archives.
-There is no distinction made between a plug-in archive containing a plug-in
-and one containing a plug-in fragment.
-<p>The recommended convention for naming the plug-in archives is
-<br><tt>&lt;id>_&lt;version>.jar</tt></p>
-<p>Where <tt>&lt;id></tt> is the plug-in or fragment identifier and <tt>&lt;version></tt>
-is the full version identifier contained in the respective plugin.xml or
-fragment.xml. Note that this is a recommended convention that minimizes
-chance of collisions, but is not required by the Eclipse architecture.
-For example, the following are valid plug-in archive names:</p>
-<p><tt>org.eclipse.platform_1.0.3.jar</tt>
-<br><tt>org.eclipse.ui.nl_2.0.jar</tt>
-<br><tt>my_plugin.jar</tt></p>
-<p>Internally, each plug-in archive packages all the relevant plug-in or
-fragment files relative to its plug-in or fragment directory (but not including
-the directory path element). The archive has the following structure </p>
-<p><tt>plugin.xml *OR* fragment.xml</tt>
-<br><tt>other plug-in or fragment files and subdirectories</tt>
-<br><tt>META-INF/</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; Java jar manifest and security files</tt>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_dtd.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_dtd.html
deleted file mode 100644
index 6912c3a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_dtd.html
+++ /dev/null

@@ -1,81 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
-
-<title>Plug-in manifest dtd</title>
-</head>
-
-<body lang="EN-US" style='tab-interval:.5in'>
-
-<pre>&lt;?xml encoding=&quot;US-ASCII&quot;?&gt;
-
-&lt;!ELEMENT plugin (requires?, runtime?, extension-point*, extension*)&gt;
-&lt;!ATTLIST plugin
- name                CDATA #REQUIRED
- id                  CDATA #REQUIRED
- version             CDATA #REQUIRED
- provider-name       CDATA #IMPLIED
- class               CDATA #IMPLIED
-&gt;
-
-&lt;!ELEMENT fragment (requires?, runtime?, extension-point*, extension*)&gt;
-&lt;!ATTLIST fragment
- name                CDATA #REQUIRED
- id                  CDATA #REQUIRED
- version             CDATA #REQUIRED
- provider-name       CDATA #IMPLIED
- plugin-id           CDATA #REQUIRED
- plugin-version      CDATA #REQUIRED
- match               (perfect | equivalent | compatible | greaterOrEqual) &quot;compatible&quot;
-&gt;
-
-&lt;!ELEMENT requires (import+)&gt;
-&lt;!ELEMENT import EMPTY&gt;
-&lt;!ATTLIST import
- plugin              CDATA #REQUIRED
- version             CDATA #IMPLIED
- match               (perfect | equivalent | compatible | greaterOrEqual) &quot;compatible&quot;
- export              (true | false) &quot;false&quot;
- optional            (true | false) &quot;false&quot;
-&gt;
-
-&lt;!ELEMENT runtime library+)&gt;
-
-&lt;!ELEMENT library (export*, packages?)&gt;
-&lt;!ATTLIST library
- name                CDATA #REQUIRED
- type                (code | resource) &quot;code&quot;
-&gt;
-
-&lt;!ELEMENT export EMPTY&gt;
-&lt;!ATTLIST export
- name                CDATA #REQUIRED
-&gt;
-
-&lt;!ELEMENT packages EMPTY&gt;
-&lt;!ATTLIST packages
- prefixes            CDATA #REQUIRED
-&gt;
-
-&lt;!ELEMENT extension-point EMPTY&gt;
-&lt;!ATTLIST extension-point
- name                CDATA #REQUIRED
- id                  CDATA #REQUIRED
- schema              CDATA #IMPLIED
-&gt;
-
-&lt;!ELEMENT extension ANY&gt;
-&lt;!ATTLIST extension
- point               CDATA #REQUIRED
- name                CDATA #IMPLIED
- id                  CDATA #IMPLIED
-&gt;
-</pre>
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_manifest.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_manifest.html
deleted file mode 100644
index a54669e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_manifest.html
+++ /dev/null

@@ -1,321 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Plug-in manifest</title>
-</head>
-
-<body>
-
-<h1>Eclipse platform plug-in manifest</h1>
-
-<p><span style='font-size:10.0pt'>Version 3.0 - Last revised June 24, 2004</span></p>
-
-<p>The manifest markup definitions below make use of various naming tokens and
-identifiers. To eliminate ambiguity, here are some production rules for these [are
-referenced in text below]. In general, all identifiers are case-sensitive. </p>
-
-<pre>SimpleToken := sequence of characters from ('a-z','A-Z','0-9','_')
-ComposedToken := SimpleToken | (SimpleToken '.' ComposedToken)
-JavaClassName := ComposedToken
-PlugInId := ComposedToken
-PlugInPrereq := PlugInId | 'export' PlugInId
-ExtensionId := SimpleToken
-ExtensionPointId := SimpleToken
-ExtensionPointReference := ExtensionPointID | (PlugInId '.' ExtensionPointId)</pre>
-
-<p>The remainder of this section describes the plugin.xml file structure as a series
-of DTD fragments. File <a href="plugin_dtd.html">plugin.dtd</a> presents the DTD
-definition in its entirety. </p>
-
-<pre>&lt;?xml encoding=&quot;US-ASCII&quot;?&gt;
-&lt;!ELEMENT plugin (requires?, runtime?, extension-point*, extension*)&gt;
-&lt;!ATTLIST plugin
-  name                CDATA #REQUIRED
-  id                  CDATA #REQUIRED
-  version             CDATA #REQUIRED 
-  provider-name       CDATA #IMPLIED
-  class               CDATA #IMPLIED 
-&gt;</pre>
-
-<p>The &lt;plugin&gt; element defines the body of the manifest. It optionally contains
-definitions for the plug-in runtime, definitions of other plug-ins required by
-this one, declarations of any new extension points being introduced by the
-plug-in, as well as configuration of functional extensions (configured into
-extension points defined by other plug-ins, or introduced by this plug-in).
-&lt;plugin&gt; attributes are as follows: </p>
-
-<ul>
- <li><b>name</b> - user displayable (translatable) name for the plug-in</li>
- <li><b>id</b> - unique identifier for the plug-in.
- <ul>
-  <li>To minimize potential for naming collisions, the identifier should be derived
-      from the internet domain id of the supplying provider (reversing the domain name
-      tokens and appending additional name tokens separated by dot [.]). For example,
-      provider ibm.com could define plug-in identifier com.ibm.db2</li>
-  <li>[production rule: PlugInId]</li>
- </ul></li>
- <li><b>version</b> - plug-in
-     version number. See org.eclipse.core.runtime.PluginVersionIdentifier for
-     details. Plug-in version format is <b>major.minor.service.qualifier</b>.
-     Change in the major component is interpreted as an incompatible version
-     change. Change in the minor component is interpreted as a compatible
-     version change. Change in the service component is interpreted as <i>cumulative</i>
-     service applied to the minor version. Change in the qualifier component is interpreted as
-     different source code control version of the same component.</li>
- <li><b>provider-name</b> - user-displayable name of the provider supplying the plug-in.</li>
- <li><b>class</b> - name of the
-     plug-in class for this plug-in. The class must be a subclass of
-     org.eclipse.core.runtime.Plugin.</li>
-</ul>
-
-<p>The XML DTD construction rule <tt><i>element*</i></tt> means zero
-or more occurrences of the element; <tt><i>element?</i></tt> means zero or
-one occurrence of the element; and <tt><i>element+</i></tt> (used below) means one or more
-occurrences of the element. Based on the &lt;plugin&gt; definition above, this
-means, for example, that a plug-in containing only a run-time definition and no
-extension point declarations or extension configurations is valid (for example,
-common libraries that other plug-ins depend on). Similarly, a plug-in
-containing only extension configurations and no runtime or extension points of
-its own is also valid (for example, configuring classes delivered in other
-plug-ins into extension points declared in other plug-ins). </p>
-
-<p>The &lt;requires&gt; section of the manifest declares any dependencies on other plug-ins.</p>
-
-<pre>&lt;!ELEMENT requires (import+)&gt;
-&lt;!ELEMENT import EMPTY&gt;
-&lt;!ATTLIST import
- plugin               CDATA #REQUIRED
- version              CDATA #IMPLIED
- match                (perfect | equivalent | compatible | greaterOrEqual) &quot;compatible&quot;
- export               (true | false) &quot;false&quot;
- optional             (true | false) &quot;false&quot;
-&gt;</pre>
-
-<p>Each dependency is specified using an &lt;import&gt; element. It contains the
-following attributes: </p>
-
-<ul>
- <li><b>plugin</b> - identifier of the required plug-in</li>
- <li><b>version</b> - optional version specification</li>
- <li><b>match</b> - version
-     matching rule. Ignored if version attribute is not specified. Determines
-     whether the dependency is satisfied only with a plug-in that has this exact
-     specified version, with a plug-in
-     that has a service or qualifier more recent than this one, with any
-     compatible version (including a more recent minor version of the plug-in)
-     or with any more recent version of this plug-in</li>
- <li><b>export</b> - specifies
-     whether the dependent plug-in classes are made visible (are (re)exported)
-     to users of this plug-in. By default, dependent classes are not exported
-     (are not made visible)</li>
- <li><b>optional</b> - specifies
-     whether or not this dependency will be strictly enforced. If set to &lt;true&gt; and this
-     dependency cannot be satisfied, the dependency will be ignored</li>
-</ul>
-
-<p><a name=runtime></a>The &lt;runtime&gt; section of the manifest contains a
-definition of one or more libraries that make up the plug-in runtime. The
-referenced libraries are used by the platform execution mechanisms (the plug-in
-class loader) to load and execute the correct code required by the plug-in. </p>
-
-<pre>&lt;!ELEMENT runtime (library+)&gt;
-&lt;!ELEMENT library (export*, packages?)&gt;
-&lt;!ATTLIST library
-  name               CDATA #REQUIRED
-  type               (code | resource) &quot;code&quot;
-&gt;
-&lt;!ELEMENT export EMPTY&gt;
-&lt;!ATTLIST export
-  name               CDATA #REQUIRED
-&gt;
-&lt;!ELEMENT packages EMPTY&gt;
-&lt;!ATTLIST packages
-  prefixes           CDATA #REQUIRED
-&gt;</pre>
-
-<p>The &lt;runtime&gt; element has no attributes. </p>
-
-<p>The &lt;library&gt; elements collectively define the plug-in runtime. At least one
-&lt;library&gt; must be specified. Each &lt;library&gt; element has the
-following attributes: </p>
-
-<ul>
- <li><b>name</b> - string
-     reference to a library file or directory containing classes (relative to
-     the plug-in install directory). Directory references must contain trailing
-     file separator.</li>
- <li><b>type</b> - specifies
-     whether this library contains executable code (&lt;code&gt;) or just
-     resources.<span style="mso-spacerun: yes">  </span>If the library is
-     of type &lt;code&gt; accessing anything in this library will cause activation of
-     the plug-in.<span style="mso-spacerun: yes">  </span>Accessing a
-     &lt;resource&gt; will not cause plug-in activation (a potential for significant
-     performance improvement).<span style="mso-spacerun: yes">  </span>It
-     should be noted that specifying a library of type &lt;code&gt; allows it to
-     contain both code and resources.<span style="mso-spacerun: yes"> 
-     </span>But specifying a library of type &lt;resource&gt; assumes it will only be
-     used for resources.</li>
-</ul>
-
-<p>Each &lt;library&gt; element can specify which portion of the library should be
-exported. The export rules are specified as a set of export masks. By default
-(no export rules specified), the library is considered to be private. Each export mask
-is specified using the <b>name</b> attribute, which can have the following values:
-</p>
-<ul>
-  <li><b>*</b> - indicates all contents of library are exported (public)</li>
-  <li><b>package.name.*</b> - indicates
-      all classes in the specified package are exported. The matching rules are
-      the same as in the Java import statement.</li>
- <li><b>package.name.ClassName</b> - fully qualified java class name</li>
-</ul>
-<p>
-<b>Eclipse 2.1 plug-ins only:</b>  Each library can also specify the package prefixes. These are used to enhance 
-  the classloading performance for the plug-in and/or fragment. If the &lt;packages&gt; 
-  element is not specified, then by default the classloading enhancements are 
-  not used. The &lt;packages&gt; element has the following attribute:</p>
-<ul>
- <li><b>prefixes</b> - a comma-separated
-	 list of package prefixes for the runtime library</li>
-</ul>
-
-<p>The platform's architecture is based on the notion of configurable extension
-points. The platform itself predefines a set of extension points that cover the
-task of extending the platform and desktop (for example, adding menu actions,
-contributing embedded editor). In addition to the predefined extension points,
-each supplied plug-in can declare additional extension points. By declaring an
-extension point the plug-in is essentially advertising the ability to configure
-the plug-in function with externally supplied extensions. For example, the Page
-Builder plug-in may declare an extension point for adding new Design Time
-Controls (DTCs) into its builder palette. This means that the Page Builder has
-defined an architecture for what it means to be a DTC and has implemented the
-code that looks for DTC extensions that have been configured into the extension
-points. </p>
-
-<pre>&lt;!ELEMENT extension-point EMPTY&gt;  
-&lt;!ATTLIST extension-point 
-  name               CDATA #REQUIRED 
-  id                 CDATA #REQUIRED    
-  schema             CDATA #IMPLIED 
-&gt;</pre>
-
-<p>The &lt;extension-point&gt; element has the following attributes:</p>
-
-<ul>
- <li><b>name</b> - user-displayable (translatable) name for the extension point</li>
- <li><b>id</b> - simple id token,
-     unique within this plug-in. The token cannot contain dot (.) or
-     whitespace.
- <ul>
-  <li>[production rule: ExtensionPointId]</li>
- </ul>
- </li>
- <li><b>schema</b> - schema
-     specification for this extension point. The exact details are being
-     defined as part of the Plug-In Development Environment (PDE). The schema
-     is currently not used at runtime. The reference is a file name relative to
-     the plug-in installation location.</li>
-</ul>
-
-<p>Actual extensions are configured into extension points (predefined, or newly declared
-in this plug-in) in the &lt;extension&gt; section. The configuration
-information is specified as well-formed XML contained between the &lt;extension&gt;
-and &lt;/extension&gt; tags. The platform does not specify the actual form of
-the configuration markup (other than requiring it to be well-formed XML). The
-markup is defined by the supplier of the plug-in that declared the extension
-point. The platform does not actually interpret the configuration markup. It
-simply passes the configuration information to the plug-in as part of the
-extension point processing (at the time the extension point logic queries all
-of its configured extensions). </p>
-
-<pre>&lt;!ELEMENT extension ANY&gt; 
-&lt;!ATTLIST extension 
-  point              CDATA #REQUIRED 
-  id                 CDATA #IMPLIED 
-  name               CDATA #IMPLIED 
-&gt;</pre>
-
-<p>The &lt;extension&gt; element has the following attributes: </p>
-<ul>
- <li><b>point</b> - reference to
-     an extension point being configured. The extension point can be one
-     defined in this plug-in or another plug-in
- <ul>
-  <li>[production rule: ExtensionPointReference]</li>
- </ul>
- </li>
- <li><b>id</b> - optional
-     identifier for this extension point configuration instance. This is used
-     by extension points that need to uniquely identify (rather than just
-     enumerate) the specific configured extensions. The identifier is specified
-     as a simple token unique within the definition of the declaring plug-in.
-     When used globally, the extension identifier is qualified by the plug-in
-     identifier
- <ul>
-  <li>[production rule: ExtensionId]</li>
- </ul>
- </li>
- <li><b>name</b> - user-displayable (translatable) name for the extension</li>
-</ul>
-
-<p><b>Important:</b>
-The content of the &lt;extension&gt; element is declared using the <tt>ANY</tt> rule. 
-This means that any well-formed XML can be specified within the extension
-configuration section (between &lt;extension&gt; and &lt;/extension&gt; tags). </p>
-
-<p>Fragments are used to increase the scope of a plug-in.
-An example would be to incorporate data such as messages or labels in another language.</p>
-<pre>&lt;?xml encoding=&quot;US-ASCII&quot;?&gt; 
-&lt;!ELEMENT fragment (requires?, runtime?, extension-point*, extension*)&gt;
-&lt;!ATTLIST fragment
-  name                CDATA #REQUIRED
-  id                  CDATA #REQUIRED
-  version             CDATA #REQUIRED
-  provider-name       CDATA #IMPLIED
-  plugin-id           CDATA #REQUIRED
-  plugin-version      CDATA #REQUIRED
-  match               (perfect | equivalent | compatible | greaterOrEqual) &quot;compatible&quot;
-&gt;</pre>
-<p>Each fragment must be associated with a specific plug-in.  
-The associated plug-in is identified with &lt;plugin-id&gt;, &lt;plugin-version&gt; and optionally, &lt;match&gt;.
-Note that if this specification matches more than one plug-in, the matching plug-in with the highest version number will be used.
-</p>
-<p>The &lt;requires&gt;, &lt;runtime&gt;, &lt;extension-point&gt;, and &lt;extension&gt; components of a fragment will be logically added to the matching plug-in.
-</p>
-<p>&lt;fragment&gt; attributes are as follows: </p>
-
-<ul>
- <li><b>name</b> - user displayable (translatable) name for the fragment</li>
- <li><b>id</b> - unique identifier for the fragment.
- <ul>
-  <li>To minimize potential
-      for naming collisions, the identifier should be derived from the id of
-      the associated plug-in in addition to something which identifies the
-      scope of this fragment. For example, org.eclipse.core.runtime.nl1 
-      could define a natural language fragment
-      for the org.eclipse.core.runtime plug-in</li>
-  <li>[production rule: PlugInId]</li>
- </ul>
- </li>
- <li><b>version</b> - fragment
-     version number. See org.eclipse.core.runtime.PluginVersionIdentifier for
-     details. Fragment version format is the same as plug-in version format.</li>
- <li><b>provider-name</b> - user-displayable name of the provider
-     supplying the fragment.</li>
- <li><b>plugin-id</b> - matches the id of the associated plug-in</li>
- <li><b>plugin-version</b> - matches the version of the associated plug-in</li>
- <li><b>match</b> - the matching rule used to find an
-     associated plug-in using &lt;plugin-id&gt; and &lt;plugin-version&gt;. See
-     the definition of &lt;match&gt; in the &lt;requires&gt; clause for
-     complete details.</li>
-</ul>
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/preference_store.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/preference_store.html
deleted file mode 100644
index 07241ab..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/preference_store.html
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>JFace preference stores</title>
-</head>
-<BODY BGCOLOR="#ffffff">
-<h1>JFace Preference Stores</h1>
-<p>As of release 3.1 the <a href="../api/org/eclipse/jface/preference/IPreferenceStore.html"><strong>org.eclipse.jface.preference.IPreferenceStore</strong></a> 
-  that is returned from AbstractUIPlugin#getPreferenceStore will be an instance 
-  of <strong><a href="../api/org/eclipse/ui/preferences/ScopedPreferenceStore.html">org.eclipse.ui.preferences.ScopedPreferenceStore</a></strong>. 
-  The ScopedPreferenceStore uses the new core runtime API to manage preferences. 
-  In 3.0 it used the compatibility layer to interface with an instance of <strong><a href="../api/org/eclipse/core/runtime/Preferences.html">org.eclipse.core.runtime.Preferences</a></strong>.</p>
-<p>In 3.1 we have disambiguated IPreferenceStore to be more specific about the 
-  types of the values sent in preference changed events. The IPreferenceStore 
-  from AbstractUIPlugin#getPreferenceStore has the same behavior as before - all 
-  that has changed is that it has been specified more clearly.</p>
-<p><strong>Typing:</strong> <strong><a href="../api/org/eclipse/jface/util/IPropertyChangeListener.html">org.eclipse.jface.util.IPropertyChangeListener</a></strong> 
-  added to an IPreferenceStore can potentially get two types of old and new values 
-  - typed or String representations. Any event generated by a call to a typed 
-  IPreferenceStore API (such as <code>setValue(String key, boolean value)</code> 
-  will generate a typed event. However it is also possible that events will be 
-  propagated from the core runtime preferences which generate an un typed event 
-  (for instance on a preference import). Property listeners need to be prepared 
-  for both. Note also that typed events will not be propagating primitive types 
-  so a call to <code>setValue(String key, boolean value)</code> will result in 
-  an event where the oldValue and newValue are Booleans.</p>
-<p><strong>putValue</strong>: IPreferenceStore.putValue(String key, String value) 
-  will not generate a change event. This API is meant to be used for private preferences 
-  that no listener would want to react to.</p>
-<p><strong>initializeDefaultPreferences</strong>. This API was deprecated in Eclipse 
-  3.0 as it is only fired if the compatibility layer is used. As most plug-ins 
-  rely on AbstractUIPlugin#getPreferenceStore to get their preference store this 
-  was being fired on plug-in start-up previously. If your plug-in does not access 
-  the compatibility layer itself then this method may not be fired. It is recommended 
-  that you create a <a href="../api/org/eclipse/core/runtime/preferences/AbstractPreferenceInitializer.html"><strong>org.eclipse.core.runtime.preferences.AbstractPreferenceInitializer</strong></a> 
-  to handle your preference initialization.</p>
-
-</BODY></HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/project_description_file.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/project_description_file.html
deleted file mode 100644
index fd75725..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/project_description_file.html
+++ /dev/null

@@ -1,165 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-  <link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-  <title>Project description file</title>
-</head>
-<body link="#0000FF" vlink="#800080">
-
-<h1 align="left">
-The project description file</h1>
-<b><i>Description:</i></b> When a project is created in the workspace,
-a project description file is automatically generated that describes the
-project.&nbsp; The purpose of this file is to make the project self-describing,
-so that a project that is zipped up or released to a server can be correctly
-recreated in another workspace.&nbsp; This file is always called ".project",
-and is located as a direct member of the project's content area.&nbsp;
-The name of the file is exposed through the static field <tt>DESCRIPTION_FILE_NAME</tt>
-on <tt>org.eclipse.core.resources.IProjectDescription.</tt>
-
-<p>The name, location, and content of this file are part of the workspace
-API.&nbsp; This means they are guaranteed not to change in a way that would
-break existing users of the file.&nbsp; However, the right to add additional
-elements and attributes to the markup is reserved for possible future additions
-to the file.&nbsp; For this reason, clients that read the description file
-contents should tolerate unknown elements and attributes.
-</p>
-
-<p>Clients that modify, delete, or replace the project description file
-do so at their own risk.&nbsp; Projects with invalid or missing description
-files will not be generally usable.&nbsp; If a project with an invalid
-description file is discovered on workspace startup, the project is closed,
-and it will not be possible to open it until the project description file
-has been repaired.&nbsp; The workspace will not generally attempt to automatically
-repair a missing or invalid description file.&nbsp; One exception is that
-missing project description files will be regenerated during workspace
-save and on calls to <tt>IProject.setDescription</tt>.
-</p>
-
-<p>Modifications to the project description file have mostly the same effect
-as changing the project description via <tt>IProject.setDescription</tt>.&nbsp;
-One exception is that adding or removing project natures will not trigger
-the corresponding nature's configure or deconfigure method.&nbsp; Another
-exception is that changes to the project name are ignored.
-</p>
-
-<p>If a new project is created at a location that contains an existing
-project description file, the contents of that description file will be
-honoured as the project description.&nbsp; One exception is that the project
-name in the file will be ignored if it does not match the name of the project
-being created.&nbsp; If the description file on disk is invalid, the project
-creation will fail.
-</p>
-
-<br>&nbsp;
-<p><b><i>Configuration Markup:</i></b></p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT projectDescription (name, comment, projects,
-buildSpec, natures, linkedResources)></tt></p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT name EMPTY></tt></p>
-<ul>
-<li>
-<b>name </b>- the name of the project.&nbsp; Ignored if it does match the
-name of the project using this description.&nbsp; Corresponds to <tt>IProjectDescription.getName()</tt>.</li>
-</ul>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT comment EMPTY></tt>
-<ul>
-<li>
-<b>comment</b> - a comment for the project.&nbsp; The comment can have
-arbitrary contents that are not interpreted by the project or workspace.&nbsp;
-Corresponds to <tt>IProjectDescription.getComment()</tt>.</li>
-</ul>
-<tt>&nbsp;&nbsp; &lt;!ELEMENT projects (project)*></tt>
-<br><tt>&nbsp;&nbsp; &lt;!ELEMENT project EMPTY></tt>
-<ul>
-<li>
-<b>projects</b> - the names of the projects that are referenced by this
-project.&nbsp; Corresponds to <tt>IProjectDescription.getReferencedProjects().</tt></li>
-</ul></p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT buildSpec (buildCommand)*></tt></p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT buildCommand (name, arguments)></tt> </p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT name EMPTY></tt> </p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT arguments (dictionary?)></tt></p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT dictionary (key, value)*></tt></p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT key EMPTY></tt></p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT value EMPTY></tt></p>
-<ul>
-<li><b>buildSpec</b> - the ordered list of build commands for this project.&nbsp;
-Corresponds to <tt>IProjectDescription.getBuildSpec().</tt></li>
-<li><b>buildCommand </b>- a single build commands for this project.&nbsp; Corresponds
-to <tt>org.eclipse.core.resources.ICommand.</tt></li>
-<li><b>name</b> - the symbolic name of an incremental project builder.&nbsp;
-Corresponds to <tt>ICommand.getBuilderName().</tt></li>
-<li><b>arguments</b> - optional arguments that may be passed to the project
-builder.&nbsp; Corresponds to <tt>ICommand.getArguments()</tt>.</li>
-<li><b>dictionary</b> - a list of &lt;key, value> pairs in the argument list.&nbsp;
-Analagous to <tt>java.util.Map.</tt></li>
-</ul>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT natures (nature)*></tt></p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT nature EMPTY></tt></p>
-<ul>
-<li>
-<b>natures </b>- the names of the natures that are on this project.&nbsp;
-Corresponds to <tt>IProjectDescription.getNatureIds().</tt></li>
-<li><b>nature </b>- the name of a single natures on this project.</li>
-</ul>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT linkedResources (link)*></tt></p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT link (name, type, location)></tt></p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT name EMPTY></tt> </p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT type EMPTY></tt> </p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT location EMPTY></tt></p>
-
-<ul>
-<li><b>linkedResources</b> - the list of linked resources for this project.</li>
-<li><b>link</b> - the definition of a single linked resource.</li>
-<li><b>name</b> - the name of the linked resource as it appears in the workspace.</li>
-<li><b>type</b> - the resource type.  Value values are: &quot;1&quot; for a file,
-or &quot;2&quot; for a folder.</li>
-<li><b>location</b> - the file system path of the target of the linked resource.  Either an
-absolute path, or a relative path whose first segment is the name of a workspace
-path variable.</li>
-</ul>
-
-<b><i>Examples: </i></b>The following is a sample project description file.&nbsp;
-The project has a single nature and builder configured, and some project
-references.
-<p><tt>&lt;?xml version="1.0" encoding="UTF-8"?></tt>
-<br><tt>&lt;projectDescription></tt>
-<br><tt>&nbsp;&nbsp;&nbsp; &lt;name>WinterProject&lt;/name></tt>
-<br><tt>&nbsp;&nbsp;&nbsp; &lt;comment>This is a cool project.&lt;/comment></tt>
-<br><tt>&nbsp;&nbsp;&nbsp; &lt;projects></tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;project>org.seasons.sdt&lt;/project></tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;project>CoolStuff&lt;/project></tt>
-<br><tt>&nbsp;&nbsp;&nbsp; &lt;/projects></tt>
-<br><tt>&nbsp;&nbsp;&nbsp; &lt;buildSpec></tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;buildCommand></tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-&lt;name>org.seasons.sdt.seasonBuilder&lt;/name></tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-&lt;arguments></tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-&lt;dictionary></tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-&lt;key>climate&lt;/key></tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-&lt;value>cold&lt;/value></tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-&lt;/dictionary></tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-&lt;/arguments></tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/buildCommand></tt>
-<br><tt>&nbsp;&nbsp;&nbsp; &lt;/buildSpec></tt>
-<br><tt>&nbsp;&nbsp;&nbsp; &lt;natures></tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;nature>org.seasons.sdt.seasonNature&lt;/nature></tt>
-<br><tt>&nbsp;&nbsp;&nbsp; &lt;/natures></tt>
-<br><tt>&lt;/projectDescription></tt>
-<br></p>
-<p><b><i>API Information:</i></b> The contents of the project description
-file map to the <tt>org.eclipse.core.resources.IProjectDescription</tt>
-interface. The project description file can be overwritten by the method
-<tt>IProject.setDescription()</tt>.</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html
deleted file mode 100644
index cd218b9..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html
+++ /dev/null

@@ -1,669 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Eclipse runtime options</title>
-</head>
-
-<body>
-
-<h1>The Eclipse runtime options</h1>
-<p>Version 3.1 - Last revised June 15, 2005</p>
-<p>The Eclipse platform is highly configurable. Configuration input takes the
-  form of command line arguments and System property settings. In many cases
-  the command line arguments are simply short cuts for setting the related System
-  properties. In fact, there are many more System property settings than command
-line arguments. </p>
-<h2><a name="commandline"></a>Command line arguments </h2>
-<p>Listed below are the command line arguments processed by various parts of
-  the Eclipse runtime. Many of these values can also be specified using System
-  properties either on the command line using -D VM arguments, by specifying
-  their values in a config.ini file or by using a &lt;launcher&gt;.ini file.
-  Using the two latter techniques it is possible to customize your Eclipse without
-  using command line arguments at all.</p>
-<p>For each argument in the list, its corresponding System property key is given
-  (in {}). Also given is the Eclipse runtime layer in which the command line
-  argument is processed (in ()). This is useful for people replacing parts of
-  the runtime to suit special needs.</p>
-<dl>
-  <dt>-application &lt;id&gt; (Runtime)</dt>
-  <dd>equivalent to setting  <a href="#eclipseapplication">eclipse.application</a>
-    to &lt;id&gt;</dd>
-  <dt>-arch &lt;architecture&gt; (OSGi) </dt>
-  <dd>equivalent to setting <a href="#osgiarch">osgi.arch</a> to &lt;architecture&gt;</dd>
-  <dt>-clean (OSGi) </dt>
-  <dd>equivalent to setting <a href="#osgiclean">osgi.clean</a> to &quot;true&quot;</dd>
-  <dt>-configuration &lt;location&gt;   (Main)</dt>
-  <dd>equivalent to setting <a href="#osgiconfigurationarea">osgi.configuration.area</a>
-    to &lt;location&gt;</dd>
-  <dt>-console [port] (OSGi) </dt>
-  <dd>equivalent to setting <a href="#osgiconsole">osgi.console</a> to [port]
-    or the empty string if the default port is to be used (i.e., when the port
-    is not specified)</dd>
-  <dt>-consoleLog (Runtime)</dt>
-  <dd>equivalent to setting <a href="#eclipseconsolelog">eclipse.consoleLog</a> to
-    &quot;true&quot;</dd>
-  <dt>-data &lt;location&gt;    (OSGi)<br>
-  </dt>
-  <dd>equivalent to setting <a href="#osgiinstancearea">osgi.instance.area</a>
-    to &lt;location&gt;</dd>
-  <dt>-debug [options file] (OSGi)</dt>
-  <dd> equivalent to setting <a href="#osgidebug">osgi.debug</a> to [options
-    file] or the empty string to simply enable debug (i.e., if the options file
-    location is not specified)</dd>
-  <dt>-dev [entries] (OSGi)</dt>
-  <dd>equivalent to setting <a href="#osgidev">osgi.dev</a> to [entries] or
-    the empty string to simply enable dev mode (i.e., if entries are not specified)</dd>
-  <dt>-endSplash &lt;command&gt; (Main)</dt>
-  <dd>specifies the command to use to take down the splash screen. Typically
-    supplied by the Eclipse executable.</dd>
-  <dt>-feature &lt;feature id&gt;    (Runtime)</dt>
-  <dd>equivalent to setting  <a href="#eclipseproduct">eclipse.product</a>
-    to &lt;feature id&gt;</dd>
-  <dt>-framework &lt;location&gt; (Main) </dt>
-  <dd>equivalent to setting  <a href="#o.pngramework">osgi.framework</a> to
-    &lt;location&gt;</dd>
-  <dt>-initialize (Main)</dt>
-  <dd>initializes the configuration being run. All runtime related data structures
-    and caches are refreshed. Any user/plug-in defined configuration data is
-    not purged. No application is run, any product specifications are ignored
-    and no UI is presented (e.g., the splash screen is not drawn)</dd>
-  <dt>-install &lt;location&gt; (Main)</dt>
-  <dd>equivalent to setting  <a href="#osgiinstallarea">osgi.install.area</a> to
-    &lt;location&gt;</dd>
-  <dt>-keyring &lt;location&gt; (Runtime)</dt>
-  <dd>the location of the authorization database on disk. This argument has to
-    be used together with the -password argument. </dd>
-  <dt>-name &lt;string&gt; <em>NEW</em></dt>
-  <dd>The name to be displayed in task bar item when the application starts up. When not set, the name is the name of the executable.</dd>
-  <dt>-nl &lt;locale&gt; (OSGi)</dt>
-  <dd>equivalent to setting <a href="#osginl">osgi.nl</a> to &lt;locale&gt;</dd>
-  <dt>-noExit (OSGi)</dt>
-  <dd>equivalent to setting <a href="#osginoshutdown">osgi.noShutdown</a> to &quot;true&quot;</dd>
-  <dt>-noLazyRegistryCacheLoading (Runtime) </dt>
-  <dd>equivalent to setting <a href="#eclipsenolazyregistrycacheloading">eclipse.noLazyRegistryCacheLoading</a>
-    to &quot;true&quot;</dd>
-  <dt>-noRegistryCache
-    (Runtime) </dt>
-  <dd>equivalent to setting  <a href="#eclipsenoregistrycache">eclipse.noRegistryCache</a>
-  to &quot;true&quot;</dd>
-  <dt>-noSplash (Executable, Main)</dt>
-  <dd>controls whether or not the splash screen is shown</dd>
-  <dt>-os &lt;operating system&gt; (OSGi) </dt>
-  <dd>equivalent to setting  <a href="#osgios">osgi.os</a> to &lt;operating system&gt;</dd>
-  <dt>-password &lt;password&gt; (Runtime) </dt>
-  <dd>the password for the authorization database </dd>
-  <dt> -pluginCustomization &lt;location&gt; (Runtime) </dt>
-  <dd>equivalent to setting <a href="#eclipseplugincustomization">eclipse.pluginCustomization</a> to
-  &lt;location&gt;</dd>
-  <dt> -product &lt;id&gt; (OSGi) </dt>
-  <dd>equivalent to setting  <a href="#eclipseproduct">eclipse.product</a> to
-  &lt;id&gt;</dd>
-  <dt>-showSplash &lt;command&gt; (Main)</dt>
-  <dd>specifies the command to use to show the splash screen. Typically supplied
-    by the Eclipse executable.</dd>
-  <dt>-startup &lt;location&gt; (Executable) <em>NEW</em></dt>
-  <dd>The location of jar used to startup eclipse. The jar referred to must have the Main-Class attribute set. 
-  If this parameter is not set, the startup.jar located in the same folder than the executable is used.</dd>
-  <dt>-user &lt;location&gt; (OSGi) </dt>
-  <dd>equivalent to setting <a href="#osgiuserarea">osgi.user.area</a> to &lt;location&gt;</dd>
-  <dt>-vm &lt;path to java executable&gt;    (Executable, Main) </dt>
-  <dd>when passed to the Eclipse executable, this option is used to locate the
-    Java VM to use to run Eclipse. It must be the full file system path to an
-    appropriate Java executable. If not specified, the Eclipse executable uses
-    a search
-    algorithm to locate a suitable VM. In any event, the executable then passes
-    the path to the actual VM used to Java Main using the -vm argument. Java
-    Main then stores this value in <a href="#eclipsevm">eclipse.vm</a>.</dd>
-  <dt>-vmargs [vmargs*] (Executable,
-    Main) </dt>
-  <dd>when passed to the Eclipse, this option is used to customize the operation
-    of the Java VM to use to run Eclipse. If
-    specified, this option must come at the end of the command line. Even if
-    not specified on the executable command line, the executable will automatically
-    add the relevant arguments (including the class being launched) to the command
-    line passed into Java using the -vmargs argument.
-    Java Main then stores this value in <a href="#eclipsevmargs">eclipse.vmargs</a>.</dd>
-  <dt>-ws &lt;window system&gt; (OSGi) </dt>
-  <dd>equivalent to setting  <a href="#osgiws">osgi.ws</a> to &lt;window system&gt;</dd>
-</dl>
-<h3>Obsolete command line arguments </h3>
-<p>The following command line arguments are no longer relevant or have been superceded
-  and are consumed by the runtime and not passed on to the application being
-  run to maintain backward compatibility. .</p>
-<dl>
-  <dt> -boot</dt>
-  <dd>see -configuration</dd>
-  <dt>-classLoaderProperties</dt>
-  <dd>no longer relevant</dd>
-  <dt>-firstUse</dt>
-  <dd>no longer relevant</dd>
-  <dt>-newUpdates</dt>
-  <dd>no longer relevant</dd>
-  <dt>-noPackagePrefixes</dt>
-  <dd>no longer relevant</dd>
-  <dt>-noUpdate</dt>
-  <dd>no longer relevant</dd>
-  <dt>-plugins</dt>
-  <dd>no longer relevant</dd>
-  <dt>-update</dt>
-  <dd>no longer relevant</dd>
-</dl>
-<h3>Others</h3>
-<p>The following command line arguments are defined by various Eclipse plug-ins
-  and are only supported if the defining plug-in is installed, resolved and activated.</p>
-<dl>
-  <dt>-noVersionCheck (workbench)</dt>
-  <dd>&lt;description&gt;</dd>
-  <dt>-perspective (workbench)</dt>
-  <dd>&lt;description&gt;</dd>
-  <dt>-refresh (org.eclipse.core.resources)</dt>
-  <dd>&lt;description&gt;</dd>
-  <dt>-showLocation (org.eclipse.ui.ide.workbench)</dt>
-  <dd>&lt;description&gt;</dd>
-  <dt>-allowDeadlock</dt>
-  <dd>&lt;description&gt;</dd>
-</dl>
-<h2>System properties</h2>
-<p>The following System properties are used by the Eclipse runtime. Note that
-  those starting with &quot;osgi&quot; are specific to the OSGi framework implementation
-  while those starting with &quot;eclipse&quot; are particular to the Eclipse
-  runtime layered on top of the OSGi framework. </p>
-<p>Many of these properties have command line equivalents (see the <a href="#commandline">command
-    line arguments</a> section and the value in braces {}). Users are free to
-    use either command line or property settings to specify a value. Properties
-    can
-    be set
-  in
-  the
-  following
-  ways:</p>
-<ul>
-  <li>use -DpropName=propValue as a VM argument to the Java VM</li>
-  <li>set the desired property in the config.ini file in the appropriate configuration
-    area</li>
-</ul>
-<dl>
-  <dt><a name="eclipseapplication" id="eclipseapplication"></a>eclipse.application {-application}</dt>
-  <dd>the identifier of the application to run. The value given here overrides
-    any application defined by the product (see <a href="#eclipseproduct">eclipse.product</a>) being run</dd>
-  <dt><a name="eclipsecommands" id="eclipsecommands"></a>eclipse.commands</dt>
-  <dd>a new-line separated list of all command-line arguments passed in when launching 
-    Eclipse </dd>
-  <dt><a name="eclipseconsolelog" id="eclipseconsolelog"></a>eclipse.consoleLog</dt>
-  <dd>if &quot;true&quot;, any log output is also sent to Java's System.out (typically
-    back to the command shell if any). Handy when combined with -debug </dd>
-  <dt><a name="eclipsedebugstartuptime" id="eclipsedebugstartuptime"></a>eclipse.debug.startupTime</dt>
-  <dd>the time in milliseconds when the Java VM for this session was started</dd>
-  <dt><a name="eclipseexitcode" id="eclipseexitcode"></a>eclipse.exitcode</dt>
-  <dd>&lt;description&gt;</dd>
-  <dt><a name="eclipseexitdata" id="eclipseexitdata"></a>eclipse.exitdata</dt>
-  <dd>&lt;description&gt;</dd>
-  <dt><a name="eclipselogbackupmax" id="eclipselogbackupmax"></a>eclipse.log.backup.max</dt>
-  <dd>the max number of backup log files to allow.  The oldest backup log file will be deleted
-     after the max number of backup log files is reached as a result of rotating the log file.
-     The default value is &quot;10&quot;.  A negative or zero value will cause the default
-     value to be used.</dd>
-  <dt><a name="eclipselogsizemax" id="eclipselogsizemax"></a>eclipse.log.size.max</dt>
-  <dd>the max size in Kb that the log file is allowed to grow.  The log file is rotated when
-     the file size exceeds the max size.  The default value is &quot;1000&quot;.
-     A negative value will cause the default value to be used.  A zero value indicates
-     no max log size.</dd>
-  <dt><a name="eclipsenoextensionmunging" id="eclipsenoextensionmunging"></a>eclipse.noExtensionMunging</dt>
-  <dd>if &quot;true&quot;, legacy registry extension are left as-is. By default such extensions
-    are updated to use the new extension point ids found in Eclipse 3.0.</dd>
-  <dt><a name="eclipsenolazyregistrycacheloading" id="eclipsenolazyregistrycacheloading"></a>eclipse.noLazyRegistryCacheLoading {-noLazyRegistryCacheLoading}</dt>
-  <dd>if &quot;true&quot;, the platform's plug-in registry cache loading optimization is
-      deactivated. By default, configuration elements are loaded from the registry
-      cache (when available)
-      only on demand, reducing memory footprint. This option forces the registry
-  cache to be fully loaded at startup. </dd>
-  <dt><a name="eclipsenoregistrycache" id="eclipsenoregistrycache"></a>eclipse.noRegistryCache {-noRegistryCache}</dt>
-  <dd>if &quot;true&quot;, the internal extension registry cache is neither read or written</dd>
-  <dt><a name="eclipseplugincustomization" id="eclipseplugincustomization"></a>eclipse.pluginCustomization {-pluginCustomization}</dt>
-  <dd>the file system location of a properties file containing default settings
-      for plug-in preferences. These default settings override default settings
-      specified in the primary feature. Relative paths are interpreted relative
-  to the current working directory for eclipse itself.</dd>
-  <dt><a name="eclipseproduct" id="eclipseproduct"></a>eclipse.product {-product}</dt>
-  <dd>the identifier of the product being run. This controls various branding
-  information and what application is used.</dd>
-  <dt><a name="eclipsestarttime" id="eclipsestarttime"></a>eclipse.startTime</dt>
-  <dd>This property is set at the time eclipse is started.  The value of this property a string 
-      representation of the value returned by System.currentTimeMillis().  This value is not
-      intended to be set by users.</dd>
-  <dt><a name="eclipsevm" id="eclipsevm"></a>eclipse.vm {-vm}</dt>
-  <dd>the path to the Java executable used to run Eclipse. This information is
-  used to construct relaunch command lines.</dd>
-  <dt><a name="eclipsevmargs" id="eclipsevmargs"></a>eclipse.vmargs {-vmargs}</dt>
-  <dd>lists the VM arguments used to run Eclipse. This
-      information is used to construct relaunch command
-  lines.</dd>
-  <dt><a name="osgiadaptor"></a>osgi.adaptor</dt>
-  <dd>the class name of the OSGi framework adaptor to use.</dd>
-  <dt><a name="osgiarch"></a>osgi.arch {-arch}</dt>
-  <dd>see -arch</dd>
-  <dt><a name="osgibaseconfigurationarea"></a>osgi.baseConfiguration.area</dt>
-  <dd>specifies a base configuration that is used when 
-      <a href="#osgiconfigurationarea">osgi.configuration.area</a> is not specified.</dd>
-  <dt><a name="osgibundles"></a>osgi.bundles</dt>
-  <dd>The comma-separated list of bundles which are automatically installed
-    and optionally started
-     once the system is up and running. Each entry is of the form:<br>
-	 <pre>    &lt;URL | simple bundle location&gt;[@ [&lt;start-level&gt;] [&quot;:start&quot;]]</pre>
-     If the start-level (&gt;0 integer) is omitted then the framework will use the
-     default start level for the bundle. If the &quot;start&quot; tag is added
-     then the bundle will be marked as started after being installed.
-     Simple bundle locations are interepreted as relative to the framework's
-    parent directory.
-     The start-level indicates the OSGi start level at which the bundle should
-  run. If this value is not set, the system computes an appropriate default.  </dd>
-  <dt><a name="osgiclean"></a>osgi.clean</dt>
-  <dd>if set to &quot;true&quot;, any cached data used by the OSGi framework and eclipse runtime 
-will be wiped clean.  This will clean the caches used to store bundle 
-dependency resolution and eclipse extension registry data.  Using this option 
-will force eclipse to reinitialize these caches.</dd>
-  <dt><a name="osgiconfigurationcascaded"></a>osgi.configuration.cascaded</dt>
-  <dd>if set to &quot;true&quot;, this configuration is cascaded to a parent
-    configuration.  The parent configuration is specified by the <a href="#osgisharedconfigurationarea">osgi.sharedConfiguration.area</a>. 
-    See the section on <a href="#locations">locations</a> for more details.</dd>
-  <dt><a name="osgiconfigurationarea"></a>osgi.configuration.area {-configuration}</dt>
-  <dd>the configuration location for this run of the platform. The configuration
-    determines what plug-ins will run as well as various other system settings.
-    See the section on <a href="#locations">locations</a>  for
-    more details.</dd>
-  <dt><a name="osgiconfigurationareadefault" id="osgiconfigurationareadefault"></a>osgi.configuration.area.default</dt>
-  <dd>the default configuration location for this run of the platform. The configuration
-    determines what plug-ins will run as well as various other system settings.
-    This value (i.e., the default setting) is only used if no value for the osgi.configuration.area
-    is set. See the section on <a href="#locations">locations</a>  for
-    more details.</dd>
-  <dt><a name="osgiconsole"></a>osgi.console {-console} </dt>
-  <dd>if set to a non-null value, the OSGi console (if installed) is enabled.
-    If the value is a suitable integer, it is interpreted as the port on which
-    the console listens and directs its output
-    to the
-    given port.
-Handy for investigating
-  the state of the system.   </dd>
-  <dt><a name="osgiconsoleclass"></a>osgi.console.class</dt>
-  <dd>the class name of the console to run if requested</dd>
-  <dt><a name="osgidebug"></a>osgi.debug {-debug}</dt>
-  <dd>if set to a non-null value, the platform is put in debug mode. If the value
-    is a string it is interpreted as the location of the
-    .options file. This file indicates what debug
-    points are
-    available
-    for a plug-in and whether or not they are enabled. If a location is not specified,
-  the platform searches for the .options file under the install directory.</dd>
-  <dt><a name="osgidev"></a>osgi.dev {-dev}</dt>
-  <dd>if set to the empty string, dev mode is simply turned on. This property
-    may also be set to a comma-separated class path entries
-    which are added to
-    the class
-    path of each
-    plug-in or a URL to a Java properties file containing custom classpath additions
-    for a set of plug-ins. For each plug-in requiring a customized dev time classpath
-    the file will contain an entry of the form<br>
-<pre>    &lt;plug-in id&gt;=&lt;comma separated list of classpath entries to add&gt;</pre>
-    where plug-in id &quot;*&quot; matches any plug-in not otherwise mentioned.</dd>
-  <dt><a name="o.pngramework"></a>osgi.framework</dt>
-  <dd>the URL location of the OSGi framework. Useful if the Eclipse install
-  is disjoint. See the section on <a href="#locations">locations</a> for more details. </dd>
-  <dt><a name="o.pngrameworkclasspath"></a>osgi.frameworkClassPath</dt>
-  <dd>a comma separated list of classpath entries for the OSGi framework implementation.
-    Relative locations are interpreted as relateve to the framework location
-    (see <a href="#o.pngramework">osgi.framework</a>)</dd>
-  <dt><a name="osgiframeworkextensions"></a>osgi.framework.extensions</dt>
-  <dd>a comma-separated list of framework extensions.  Each entry is of the form:<br>
-	 <pre>    &lt;URL | simple bundle location&gt;</pre>
-      If a simple bundle location is specified (not a URL) then a search is done in parent directory of the 
-      org.eclipse.osgi bundle.  Framework extensions may be used to run Eclipse with a different
-      framework adaptor.  The framework extension may contain an eclipse.properties file to set 
-      system properties.  For example, a framework extension that provides a framework adaptor 
-      implementation can specify what the adaptor class is by setting the 
-      <a href="#osgiadaptor">osgi.adaptor</a> property.</dd>
-  <dt><a name="osgiframeworkshape"></a>osgi.framework.shape</dt>
-  <dd>set to the shape of the Eclipse OSGi Framework implementation.  This property is set when
-  the Eclipse platform is started and is not intended by be set by the user.  The value
-  &quot;jar&quot; indicates that the Eclipse OSGi Framework is contained in a single jar.
-  The value &quot;folder&quot; indicates that the Eclipse OSGi Framework is contained in a 
-  directory.</dd>
-  <dt><a name="osgijavaprofile"></a>osgi.java.profile</dt>
-  <dd>a URL to the JRE profile file to use.  A JRE profile contains values for the properties
-     org.osgi.framework.system.packages and org.osgi.framework.bootdelegation.  If 
-     the osgi.java.profile is not set then a profile is selected based on the 
-     java.specification.version value of the running JRE.</dd>
-  <dt><a name="osgijavaprofilebootdelegation"></a>osgi.java.profile.bootdelegation</dt>
-  <dd>
-    a java profile <a href="#osgijavaprofile">osgi.java.profile</a> may contain a 
-    &quot;org.osgi.framework.bootdelegation&quot; property.  This value may be used to set the system 
-	property &quot;org.osgi.framework.bootdelegation&quot;.  The osgi.java.profile.bootdelegation 
-	indicates the policy for bootdelegation to be used.  The following values are valid 
-	(default is ignore):
-    <ul type=disc>
-      <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-          mso-list:l2 level1 lfo3;tab-stops:list .5in'><b>ignore</b> - indicates that
-          the &quot;org.osgi.framework.bootdelegation&quot; value in the java profile should be ingored.  
-          The system property &quot;org.osgi.framework.bootdelegation&quot; will be used to 
-          determine which packages should be delegated to boot.
-      </li>
-      <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-          mso-list:l2 level1 lfo3;tab-stops:list .5in'><b>override</b> - 
-          indicates that the &quot;org.osgi.framework.bootdelegation&quot; in the java profile should 
-          override the system property &quot;org.osgi.framework.bootdelegation&quot;.
-      </li>
-      <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-          mso-list:l2 level1 lfo3;tab-stops:list .5in'><b>none</b> - 
-          indicates that the &quot;org.osgi.framework.bootdelegation&quot; in the java profile AND 
-          the system properties should be ignored.  This is the most strict option.  
-          Running with this option causes the framework to use the OSGi R4 strict boot 
-          delegation model.
-      </li>
-    </ul>
-  </dd>
-  <dt><a name="osgiinstallarea" id="osgiinstallarea"></a>osgi.install.area {-install}</dt>
-  <dd>the install location of the platform. This setting indicates the location
-    of the basic Eclipse plug-ins and is useful if the Eclipse install is disjoint.
-  See the section on <a href="#locations">locations</a> for more details. </dd>
-  <dt><a name="osgiinstancearea"></a>osgi.instance.area {-data}</dt>
-  <dd>the instance data location for this session. Plug-ins use this location
-    to store their data. For example, the Resources plug-in uses this as the
-    default location for projects (aka the workspace). See the section on <a href="#locations">locations</a> for
-    more details.</dd>
-  <dt><a name="osgiinstanceareadefault" id="osgiinstanceareadefault"></a>osgi.instance.area.default</dt>
-  <dd>the default instance data location for this session. Plug-ins use this
-    location to store their data. For example, the Resources plug-in uses this
-    as the
-    default location for projects (aka the workspace). This value (i.e., the
-    default setting) is only used if no value for the osgi.instance.area
-    is set. See the section on <a href="#locations">locations</a> for
-    more details.</dd>
-  <dt><a name="osgilocking"></a>osgi.locking</dt>
-  <dd>the locking type to use for this run of the platform.  The valid locking types
-  are &quot;java.io&quot;, &quot;java.nio&quot;, and &quot;none&quot;.  The default value is
-  &quot;java.nio&quot; unless the JRE does not support &quot;java.nio&quot; then &quot;java.io&quot;
-  is the default.</dd>
-  <dt><a name="osgimanifestcache"></a>osgi.manifest.cache</dt>
-  <dd>the location where generated manifests are discovered and generated. The
-    default is in the configuration area but the manifest cache can be stored
-    separately.</dd>
-  <dt><a name="osginl"></a>osgi.nl {-nl}</dt>
-  <dd>the name of the locale on which Eclipse platform will run. NL values should
-    follow the standard Java locale naming conventions.</dd>
-  <dt><a name="osginoshutdown"></a>osgi.noShutdown {-noExit}</dt>
-  <dd>if &quot;true&quot;, the VM will not exit after the eclipse application has ended.  This
-      is useful for examining the OSGi framework after the eclipse application has ended.</dd>
-  <dt><a name="osgios"></a>osgi.os {-os}</dt>
-  <dd>the operating system value. The value should be one of the Eclipse processor
-    architecture names known to Eclipse (e.g., x86, sparc, ...).</dd>
-  <dt><a name="osgiparentclassloader"></a>osgi.parentClassloader</dt>
-  <dd>the classloader type to use as the parent classloader for all bundles installed
-  in the Framework.  The valid types are the following:
-    <ul type=disc>
-      <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-          mso-list:l2 level1 lfo3;tab-stops:list .5in'><b>app</b> - the application classloader.</li>
-      <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-     mso-list:l2 level1 lfo3;tab-stops:list .5in'><b>boot</b> - the boot classloader.</li>
-      <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-     mso-list:l2 level1 lfo3;tab-stops:list .5in'><b>ext</b> - the extension classloader.</li>
-      <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-     mso-list:l2 level1 lfo3;tab-stops:list .5in'><b>fwk</b> - the framework classloader.</li>
-    </ul>
-  </dd>
-  <dt><a name="osgirequiredjavaversion"></a>osgi.requiredJavaVersion</dt>
-  <dd>The minimum java version that is required to launch Eclipse.  The default value is
-      &quot;1.4.1&quot;.</dd>
-  <dt><a name="osgiresolvermode"></a>osgi.resolverMode</dt>
-  <dd>the mode used to resolve bundles installed in the Framework.  A value of 
-      &quot;strict&quot; puts the resolver in strict mode.  The default resolver
-      mode is not strict.  When the resolver is in strict mode the Framework will 
-      enforce access restriction rules when loading classes and resources from 
-      exported packages which specify the x-internal or x-friends directives.</dd>
-  <dt><a name="osgisharedconfigurationarea"></a>osgi.sharedConfiguration.area</dt>
-  <dd>the shared configuration location for this run of the platform.  If the
-  <a href="#osgiconfigurationcascaded">osgi.configuration.cascaded</a> property is set
-  to &quot;true&quot; then shared configuration area is used as the parent configuration.</dd>
-  <dt><a name="osgisplashlocation"></a>osgi.splashLocation</dt>
-  <dd>the absolute URL location of the splash screen (.bmp file) to to show while
-    starting Eclipse. This property overrides any value set in <a href="#osgisplashpath">osgi.splashPath</a>.</dd>
-  <dt><a name="osgisplashpath"></a>osgi.splashPath</dt>
-  <dd>a comma separated list of URLs to search for a file called splash.bmp.
-  This property is overriden by any value set in <a href="#osgisplashlocation">osgi.splashLocation</a>.</dd>
-  <dt><a name="osgisyspath"></a>osgi.syspath</dt>
-  <dd>set to the path where the eclipse OSGi Framework (org.eclipse.osgi) implementation 
-  is located.  For example, &quot;&lt;eclipse install path&gt;/eclipse/plugins&quot;.
-  This property is set when the Eclipse platform is started and is not intended by be 
-  set by the user.</dd>
-  <dt><a name="osgiuserarea"></a>osgi.user.area {-user}</dt>
-  <dd>the location of the user area. The user area contains data (e.g., preferences)
-    specific to the OS user and independent of any Eclipse install, configuration
-    or instance. See the section on <a href="#locations">locations</a> for more
-    details.</dd>
-  <dt><a name="osgiuserareadefault" id="osgiuserareadefault"></a>osgi.user.area.default</dt>
-  <dd>the default location of the user area. The user area contains data (e.g.,
-    preferences) specific to the OS user and independent of any Eclipse install,
-    configuration
-    or instance. This value (i.e., the default setting) is only used if no value
-    for the osgi.user.area is set. See the section on <a href="#locations">locations</a> for
-    more details.</dd>
-  <dt><a name="osgiws"></a>osgi.ws {-ws}</dt>
-  <dd>the window system value. The value should be one of the Eclipse window
-    system names known to Eclipse (e.g., win32, motif, ...).</dd>
-</dl>
-<h2><a name="locations"></a>Locations
-</h2>
-<p>The Eclipse runtime defines a number of <i>locations</i> which give plug-in
-  developers context for reading/storing data and Eclipse users a control over
-  the scope of data sharing and visibility. Eclipse defines the following notions
-  of location:</p>
-<dl>
-    <dt>User (-user) {<a href="#osgiuserarea">osgi.user.area</a>} [@none, @noDefault, @user.home, @user.dir,
-      filepath, url]</dt>
-    <dd>User locations are specific to, go figure, users. Typically the user
-      location is based on the value of the Java <code>user.home</code> system
-      property but this can be overridden. Information such as user scoped preferences
-      and login information may be found in the user location.</dd>
-    <dt>Install (-install) {osgi.install.area} [@user.home, @user.dir, filepath,
-      url]</dt>
-    <dd>An install location is where Eclipse itself is installed. In practice
-      this location is the directory (typically &quot;eclipse&quot;) which is
-      the parent of the startup.jar or eclipse.exe being run. This location should
-      be considered read-only to normal users as an install may be shared by
-      many users. It is possible to set the install location and decouple startup.jar
-      from the rest of Eclipse.</dd>
-    <dt>Configuration (-configuration) {osgi.configuration.area} [@none, @noDefault,
-      @user.home, @user.dir, filepath, url]</dt>
-    <dd>Configuration locations contain files which identify and manage the (sub)set
-      of an install to run. As such, there may be many configurations per install.
-      Installs may come with a default configuration area but typical startup
-      scenarios involve the runtime attempting to find a more writable configuration
-      location. </dd>
-    <dt>Instance (-data) {osgi.instance.area} [@none, @noDefault, @user.home,
-      @user.dir, filepath, url]</dt>
-    <dd>Instance locations contain user-defined data artifacts. For example,
-      the Resources plug-in uses the instance area as the workspace location
-      and thus the default home for projects. Other plugins are free to write
-      whatever files they like in this location.</dd>
-</dl>
-<p>While users can set any of these locations, Eclipse will compute reasonable
-  defaults if values are not given. The most common usecase for setting location
-  is the instance area or, in the IDE context, the workspace. To run the default
-  Eclipse configuration on a specific data set you can specify:</p>
-<pre>    eclipse -data c:\mydata</pre>
-<h3>More detail</h3>
-<p>Locations are URLs. For simplicity, file paths are also accepted and automatically
-  converted to file: URLs. For better control and convenience, there are also
-  a number of predefined symbolic locations which can be used. Note that not
-  all combinations of location type and symbolic value are valid. A table below
-  details which combinations are possible. Since the default case is for all
-  locations to be set, valid and writable, some plug-ins may fail in other setups
-  even if they are listed as possible. For example, it is unreasonable to expect
-  a plugin focused on user data (e.g., the Eclipse Resources plug-in) to do much
-  if the instance area is not defined. It is up to plug-in developers to choose
-  the setups they support and design their function accordingly.</p>
-<dl>
-    <dt>@none</dt>
-    <dd>Indicates that the corresponding location should never be set either
-      explicitly or to its default value. For example, an RCP style application
-      which has no user data may use osgi.instance.area=@none to prevent
-      extraneous files being written to disk. @none must not be followed by any
-      additional path segments.</dd>
-    <dt>@noDefault</dt>
-    <dd>Forces a location to be undefined or explicitly defined (i.e., Eclipse
-      will not automatically compute a default value). This is useful where you
-      want to allow for data in the corresponding location but the Eclipse default
-      value is not appropriate. @noDefault must not be followed by any
-      additional path segments.</dd>
-    <dt>@user.home</dt>
-    <dd>Directs Eclipse to compute a location value relative to the user's home
-      directory. @user.home can be followed
-      by additional path segments. In all cases, the string &quot;@user.home&quot; is
-      simply replaced with the value of the Java &quot;user.home&quot; System
-      property. For example, setting<br>
-      &nbsp;&nbsp;&nbsp;&nbsp;osgi.instance.area=@user.home/myWorkspace<br>
-      results in a value of
-      <br>
-      &nbsp;&nbsp;&nbsp;&nbsp;file:/users/bob/myWorkspace</dd>
-    <dt>@user.dir</dt>
-    <dd>Directs Eclipse to compute a location value relative to the current working
-      directory. @user.dir can be followed
-      by additional path segments. In all cases, the string &quot;@user.dir&quot; is
-      simply replaced with the value of the Java &quot;user.dir&quot; System
-      property. For example, setting<br>
-&nbsp;&nbsp;&nbsp;&nbsp;osgi.instance.area=@user.dir/myWorkspace<br>
-results in a value of <br>
-&nbsp;&nbsp;&nbsp;&nbsp;file:/usr/share/eclipse/myWorkspace</dd>
-</dl>
-<table width="100%" border="0" bgcolor="#FFFFFF">
-  <tr bgcolor="#CCCCCC">
-    <td width="10%">location/value</td>
-    <td width="17%"><div align="center">supports default</div></td>
-    <td width="17%"><div align="center">file/URL</div>
-    </td>
-    <td width="17%"><div align="center">@none</div>
-    </td>
-    <td width="17%"><div align="center">@noDefault</div>
-    </td>
-    <td width="17%"><div align="center">@user.home</div>
-    </td>
-    <td width="17%"><div align="center">@user.dir</div>
-    </td>
-  </tr>
-  <tr>
-    <td bgcolor="#CCCCCC"><div align="center">instance</div>
-    </td>
-    <td><div align="center">yes</div></td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes (default)</div>
-    </td>
-  </tr>
-  <tr>
-    <td bgcolor="#CCCCCC"><div align="center">configuration</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes*</div>
-    </td>
-    <td><div align="center">yes*</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-  </tr>
-  <tr>
-    <td bgcolor="#CCCCCC"><div align="center">install</div>
-    </td>
-    <td><div align="center">no</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">no</div>
-    </td>
-    <td><div align="center">no</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-  </tr>
-  <tr>
-    <td bgcolor="#CCCCCC"><div align="center">user</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-  </tr>
-</table>
-<p>* indicates that this setup is technically possible but pragmatically quite
-  difficult to manage. In particular, without a configuration location the Eclipse
-  runtime may only get as far as starting the OSGi framework.</p>
-
-<h3>Read-only Locations</h3>
-
-<p>
-A location may be specified as a read-only location by appending &quot;.readOnly&quot; 
-to the location property and setting it to the value &quot;true&quot;.  The following properties
-can be used to specify their corresponding locations as read-only:</p>
-    <ul type=disc>
-      <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-          mso-list:l2 level1 lfo3;tab-stops:list .5in'>
-          osgi.configuration.area.readOnly <a href="#osgiconfigurationarea">osgi.configuration.area</a>
-      </li>
-      <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-          mso-list:l2 level1 lfo3;tab-stops:list .5in'>
-          osgi.sharedConfiguration.area.readOnly <a href="#osgisharedconfigurationarea">osgi.sharedConfiguration.area</a>
-      </li>
-      <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-          mso-list:l2 level1 lfo3;tab-stops:list .5in'>
-          osgi.instance.area.readOnly <a href="#osgiinstancearea">osgi.instance.area</a>
-      </li>
-      <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-          mso-list:l2 level1 lfo3;tab-stops:list .5in'>
-          osgi.user.area.readOnly <a href="#osgiuserarea">osgi.user.area</a>
-      </li>
-    </ul>
-
-<h2><a name="launcher"></a>Launcher ini file</h2>
-<p>
-The eclipse.exe and more generally executables for RCP applications now read their parameters from an associated 
-ini file. This file offers a platform independent way to pass in arguments that previously had to be specified directly on
-the command line such as vm or vm arguments. Although all parameters can be specified in this file, it recommend for maintainability
-and consistency across various installations to only specifiy the vm location and the vm arguments in this ini file and use the config.ini
-file for others.</p>
-
-<h3>File format</h3>
-<p>This file must be named after the executable name (for example, eclipse.exe will read eclipse.ini, whereas launcher.exe will read launcher.ini) and every parameter
-must be specified on a new line in the file. Here is an example of such a file specifying the vm location and some parameters:</p>
-<pre>-vm
-c:/myVm/java.exe
--vmargs
--Dms40M
-</pre>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/terminology.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/terminology.html
deleted file mode 100644
index 8a269b4..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/terminology.html
+++ /dev/null

@@ -1,102 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Glossary of terms</title>
-
-
-</head>
-<body>
-
-<h1>
-Glossary of terms</h1>
-It can be confusing when one person refers to the same thing with different
-terms, and downright misleading if they refer to different things using
-the same term. That's why it's important to choose the right words when
-referring to things in comments, code, and documentation.
-<p><b>Eclipse</b>
-<blockquote>Eclipse is the name for the overall project supporting the
-construction of integrated tools for developing applications. It represents
-a collection of related <a href="http://www.eclipse.org/projects/main.html">projects</a>
-that include the <a href="#Platform"> Eclipse Platform,</a> the <a href="#JDT"> Java development tools
-  (JDT)</a>, and
-the <a href="#PDE"> Plug-in Development Environment (PDE)</a>.</blockquote>
-<a NAME="Eclipse Platform"></a><b>Eclipse Platform</b>
-<blockquote>Eclipse Platform is the name for&nbsp; the core frameworks
-and services upon which plug-in extensions are created. It provides the
-runtime in which plug-ins are loaded and run. In order to use the term
-with the right degree of (im)precision, it is useful to know some things
-about the Platform. First off, the Eclipse Platform itself is not really
-a true product that would ship by itself. The Platform's direct consumers
-are tool builders, or ISVs, since they add the value to the Eclipse Platform
-that makes it useful to people.
-<br>
-The Eclipse Platform is divided up into <i>Core </i>and <i>UI</i>.
-Anything classified as "UI" needs a window system, whereas things classified
-as "Core" can run "headless". The UI portion of the Eclipse Platform is
-known as the <a href="#Workbench">Workbench</a>. The core portion of the
-Eclipse Platform is simply called the <a href="#Core">Platform Core</a>,
-or Core.
-<br>
-So the Eclipse Platform is just the nucleus around which tool builders
-build tool plug-ins.
-</blockquote>
-<b>Eclipse SDK</b>
-<blockquote>The Eclipse SDK is the <a href="#Eclipse Platform">Eclipse
-Platform</a>, <a href="#JDT">JDT</a>, and <a href="#PDE">PDE</a>.
-In addition to the Platform, the SDK provides the development tools required
-to, among other things, enable Eclipse to be a development environment
-for itself.</blockquote></p>
-<p><a NAME="Platform"></a><b>Platform - </b>Short for "<a href="#Eclipse Platform">Eclipse
-Platform</a>".</p>
-<p><a NAME="Workbench"></a><b>Workbench</b> - Short for "Eclipse Platform
-UI".
-<blockquote>The Workbench is a high-level UI framework for building products
-with sophisticated UIs built from pluggable components. The Workbench is
-built atop <a href="#JFace">JFace</a>, <a href="#SWT">SWT</a>, and the
-<a href="#Core">Platform
-Core</a>.</blockquote>
-<a NAME="Core"></a><b>Core</b> - Short for "Eclipse Platform Core".
-<blockquote>All the UI-free infrastructure of the <a href="#Eclipse Platform">Eclipse
-Platform</a>. The major divisions are: platform runtime and plug-in management,
-workspaces and resource management, and version and configuration management.</blockquote>
-<a NAME="Runtime"></a><b>Runtime</b> - Short for "Eclipse Platform Core
-Runtime".
-<blockquote>The lowest level part of the <a href="#Core">Platform Core</a>,
-responsible for the plug-in registry and plug-ins. Note that the Platform
-Core Runtime does not include workspaces and resources (they're in the
-Resources plug-in).</blockquote>
-<a NAME="Workspace"></a><b>Workspace</b>
-<blockquote>A workspace is the general umbrella for managing resources
-in the Eclipse Platform. Note that workspaces and resources are an optional
-part of the Platform; some configurations of the Platform will not have
-a workspace.</blockquote>
-<a NAME="UI"></a><b>UI</b> - Short for "Eclipse Platform UI".
-<blockquote>All-inclusive term for the UI portion of the <a href="#Eclipse Platform">Eclipse
-Platform</a>.</blockquote>
-<a NAME="JFace"></a><b>JFace</b>
-<blockquote>JFace is the mid-level UI framework useful for building complex
-UI pieces such as property viewers. JFace works in conjunction with <a href="#SWT">SWT</a>.</blockquote>
-<a NAME="SWT"></a><b>SWT</b>
-<blockquote>SWT (Standard Widget Toolkit) is a small, fast widget toolkit
-with a portable API and a native implementation. So far, SWT has been ported
-to Windows, Linux (GTK and Motif window systems), AIX (Motif), Solaris (Motif),
-  HP-UX (Motif), QNX (Photon) and Mac OS X (Carbon).</blockquote>
-
-<a name="JDT"><b>JDT</b>
-</a>
-<blockquote>Java development tools (n.b. &quot;development tools&quot; in
-  lowercase, for legal reasons) adds Java program development capability to the
-  Eclipse Platform.</blockquote>
-
-<a name="PDE"><b>PDE</b>
-</a>
-<blockquote>The Plug-in Development Environment adds specialized tools for
-  developing Eclipse plug-ins.</blockquote>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/ui_accessibility_tips.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/ui_accessibility_tips.html
deleted file mode 100644
index b4e932c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/ui_accessibility_tips.html
+++ /dev/null

@@ -1,104 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Tips For making user interfaces accessible</title>
-</head>
-<body>
-<h1>Tips for making user interfaces accessible </h1>
-<p>Below is a series of tips for making something usable to the IAccessibility
-interface provided by Windows. </p>
-<dl>
-<dt><b>Use Groups instead of Labels.</b></dt>
-<dd>If you use a Label to title a group of related widgets remove the label and
-  replace their parent composite with a Group whose text is the same as the
-  title Label. <br>&nbsp;</dd>
-  
-<dt><b>Avoid intermediate Composites.</b></dt>
-<dd>IAccessibility tools will read as far up the parent hierarchy of a widget
-  with focus as there are widgets to read. Be sure there are no widgets without
-  text anywhere in the tree.<br>&nbsp;</dd>
-  
-<dt><b>Use read-only Texts instead of Labels.</b></dt>
-<dd>A text can be accessed using the keyboard and should be used if you want
-  the information in a label to be accessible to keyboard navigation. Please
-  note that a label beside a text will be treated as a title and so if you have
-  a title:value pair you wish to show it is only required that you make the
-  value widget a Text.<br>&nbsp;</dd>
-
-<dt><b>Read and understand the IBM checklist.</b></dt>
-<dd>IBM provides a useful checklist for good accessibility at <a href="http://www.ibm.com/able/guidelines/software/accesssoftware.html">
-http://www.ibm.com/able/guidelines/software/accesssoftware.html</a><br>&nbsp;</dd>
-
-<dt><b>Assign mnemonics to all menus and menu items.</b></dt>
-<dd>Ensure they are unique within a given menu. If a menu
-  is dynamically composed from multiple plugins, it may be better to not assign
-  mnemonics since conflicts cannot be avoided in general (e.g. the <b>File &gt; New</b>
-  list, or <b>Window &gt; Show View</b> list)<br>&nbsp;</dd>
-
-<dt><b>Assign mnemonics to all labels of controls in
-dialogs / preference pages / property pages (e.g. buttons, checkboxes, radio
-buttons, etc)</b></dt>
-<dd>Ensure they are unique within the dialog. Be careful to
-avoid collisions with the default buttons (e.g. Restore &amp;Defaults,
-&amp;Apply in preference pages; &amp;Next, &amp;Back, &amp;Finish in wizards).
-Do not assign mnemonics to OK and Cancel buttons. If you make OK the default
-button of the shell, and Cancel is equivalent to closing the shell, then Enter
-and Esc map to these by default. Generally doing something with Esc or Enter is
-a bad idea.<br>&nbsp;</dd>
-
-<dt><b>Ensure that controls that do not have labels are preceded by a label.</b></dt>
-<dd>If a control does not have its own label (e.g. a text field), use a preceding label
-ending with ':' and assign a mnemonic to it. Screen readers like JAWS will read this label 
-when the control has focus (see <b>Window &gt; Preferences &gt; General</b>)<br>&nbsp;</dd>
-  
-<dt><b>Avoid extra freestanding labels.</b></dt>
-<dd>You cannot navigate to freestanding labels with the keyboard and screen readers
-like JAWS skip these since they do not take focus<br>&nbsp;</dd>
-
-<dt><b>Do not assign mnemonics to controls in the main window.</b></dt>
-<dd>Do not put mnemonics on controls in the main window (other than main
-menus and main menu items), even if it looks like a dialog (e.g. the form editors in
-org.eclipse.ui.forms) as these will usually conflict with menu mnemonics<br>&nbsp;</dd>
-
-<dt><b>Assign shortcut keys for frequently used functions (and <em>only</em> frequently used functions).</b></dt>
-<dd>There are currently only two ways to hook shortcut keys in SWT:
-<ul>
-    <li>by setting an accelerator on a menu item in the
-      main menu bar (they are ignored in context menus) -- JFace actions have
-      support for this</li>
-    <li>by hooking a key listener on a particular control
-      (e.g. in the implementation of a view or editor)</li>
-</ul>
-Consult the table of Eclipse SDK shortcut keys, available within Eclipse from the <b>General &gt; Keys</b>
-preference page, to avoid collision.<br>&nbsp;</dd>
-
-<dt><b>Avoid Alt+{key}, Ctrl+Alt+{key} and Ctrl+Space+{key} combinations.</b></dt>
-<dd><ul>
-<li>Alt+{key} combinations may conflict with menu mnemonics</li>
-<li>Ctrl+Alt+{key} combinations can conflict with entering special characters on international keyboards (alt Gr = Ctrl+Alt)</li>
-<li>Ctrl+Space+{key} combinations can conflict with Ctrl-Space, used for mode switching in Asian languages.</li>
-</ul></dd>
-
-<dt><b>Try to save navigation context.</b></dt>
-<dd>For example, in <b>Window &gt; Preferences</b>, we now remember
-which page you had selected last. This avoids having to navigate through the
-list each time<br>&nbsp;</dd>
-
-<dt><b>Assign a specific person on the team to be responsible for accessibility on your project.</b></dt>
-<dd>Everything that is important needs an advocate. Make sure that everyone on the team knows
-that good accessibility is crucial, and is willing to give the person their full cooperation.<br>&nbsp;</dd>
-
-<dt><b>Test for accessibility.</b></dt>
-<dd>Have your team hold an occasional &quot;unplug your mouse day&quot; where they
-try to use the product using keyboard only. If you are developing on Window, get a copy of
-<a href="http://www.freedomscientific.com/">JAWS<font size="-1"><sup>TM</sup></font></a>
-and ensure that your UI is usable with it<br>&nbsp;</dd>
-</dl>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/update_platform_xml.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/update_platform_xml.html
deleted file mode 100644
index 89558fb..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/update_platform_xml.html
+++ /dev/null

@@ -1,98 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>The platform.xml file</title>
-</head>
-<body>
-<h1>The platform.xml file</h1>
-<h3><strong>Since: </strong></h3>
-<p>3.0</p>
-<h3>Description:</h3>
-<p>The primary update manager configuration information is maintained by the platform.xml 
-  file located in the configuration directory (usually, eclipse/configuration/org.eclipse.update/platform.xml). 
-  This file format is internal and can change any time, but, in practice, it should 
-  not change much, if at all.</p>
-<p>As some people would like to take advantage of shipping an eclipse based product 
-  with a pre-defined installation configuration, this document provides some syntax 
-  and semantics info for this configuration file.</p>
-<p>Given that the platform.xml originated from the old platform.cfg and installConfig*.xml 
-  file, there are still some deprecated elements/attributes that will not be mentioned 
-  in this doc, as well as some relatively convoluted way of specifying the configuration 
-  info. If platform.xml is to become API, then some re-work is needed (both syntax 
-  and semantics).</p>
-<h3>Configuration Markup:</h3>
-<p class=code id=dtd>&lt;!ELEMENT <a name="e.extension">extension</a> EMPTY&gt;</p>
-<p class=code id=dtd>&lt;!ATTLIST extension</p>
-<p class=code id=dtdAttlist>point&nbsp;CDATA #REQUIRED</p><p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED</p><p class=code id=dtdAttlist>name&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
-
-<ul class=ConfigMarkup id=attlistDesc>
-</ul>
-<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.config">config</a> EMPTY&gt;</p>
-<p class=code id=dtd>&lt;!ATTLIST config</p>
-<p class=code id=dtdAttlist>version&nbsp;&nbsp;&nbsp;CDATA #IMPLIED</p><p class=code id=dtdAttlist>date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED</p>
-<p class=code id=dtdAttlist>transient&nbsp;(true | false) &quot;false&quot;</p>
-<p class=code id=dtdAttlist>shared_ur&nbsp;CDATA #IMPLIED&gt;</p>
-
-<p class=ConfigMarkup id=elementDesc> describes the current install configuration.</p>
-<br>
-<ul class=ConfigMarkup id=attlistDesc>
-<li><b>version</b> - this attribute may be used to indentify the version of the configuration specification</li>
-<li><b>date</b> - this is an internal attribute that is generated by the update configurator code. If you manually create or modify the platform.xml file then remove this attribute, and let the update code add it when it first runs. In this scenario, update will not try to reconcile the platform.xml with what is on the disk, it takes the platform.xml as is, and slaps the date attribute.</li>
-<li><b>transient</b> - a transient configuration is not modified by the update code, it is just read and used to configure the plugins to run. Its main point is to avoid doing any reconciliation with what's on the disk. This flag is a bit of a hack for PDE to run self hosting without having features in the workspace, and it is better if it is left set to false.</li>
-
-<li><b>shared_ur</b> - points to the shared configuration location. This is particularly useful on unix/linux, when the admin sets up a shared installation and each user's configuration consists of the shared installation data (as pointed at by this attribute) and any local changes.</li>
-</ul>
-<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.site">site</a> EMPTY&gt;</p>
-<p class=code id=dtd>&lt;!ATTLIST site</p>
-<p class=code id=dtdAttlist>url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED</p><p class=code id=dtdAttlist>enabled&nbsp;&nbsp;&nbsp;&nbsp;(true | false) </p><p class=code id=dtdAttlist>updateable&nbsp;(true | false) </p><p class=code id=dtdAttlist>policy&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(USER-EXCLUDE|USER-INCLUDE|MANAGED-ONLY) </p><p class=code id=dtdAttlist>linkfile&nbsp;&nbsp;&nbsp;CDATA #IMPLIED</p><p class=code id=dtdAttlist>list&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
-
-<p class=ConfigMarkup id=elementDesc>
-defines an installation location, which is a location that contains features and plugins.</p>
-<br>
-<ul class=ConfigMarkup id=attlistDesc>
-<li><b>url</b> - location of this installation site. The url is absolute, but there is a special url for the base location (where eclipse.exe is located), of the form platform:/base/</li>
-<li><b>enabled</b> - a boolean value that defines whether the plugins and features from this location will be considered at runtime.</li>
-<li><b>updateable</b> - defines whether any update/install/enable/uninstall/etc. operations can be performed on features on this site.</li>
-
-  <li><b>policy</b> - defines the way the &quot;list&quot; attribute is interpreted: 
-    <br>
-    USER-EXCLUDE: all the plugins from the site are run, except those listed in 
-    the &quot;list&quot; attribute. This is what's currently used by the update 
-    code. <br>
-    USER-INCLUDE: only the plugins listed by the &quot;list&quot; attribute are 
-    run. This is what PDE generated configurations use. <br>
-    MANAGED-ONLY: only plugins from the features define by this site (see the &lt;feature&gt; element) are run (new in 3.1)</li>
-<li><b>linkfile</b> - if this site has been contributed from a .link file, then this attribute points to that file.</li>
-  <li><b>list</b> - lists the plugins to be included or excluded (see the &quot;policy&quot; 
-    attribute) at runtime.</li>
-
-</ul>
-<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.feature">feature</a> EMPTY&gt;</p>
-<p class=code id=dtd>&lt;!ATTLIST feature</p>
-<p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED</p><p class=code id=dtdAttlist>version&nbsp;CDATA #REQUIRED</p><p class=code id=dtdAttlist>url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED&gt;</p>
-
-<p class=ConfigMarkup id=elementDesc> defines a feature installed on this site.</p>
-<br>
-<ul class=ConfigMarkup id=attlistDesc>
-<li><b>id</b> - the feature id</li>
-<li><b>version</b> - the feature version</li>
-<li><b>url</b> - the feature location, relative to the site. By default, the url is of the form features/some_feature_id_version.</li>
-</ul>
-
-<br>
-<h4 class=CaptionFigColumn id=header>Example: </h4>
-<div class="e"> 
-  <pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;<br>&lt;config date=&quot;1119300698390&quot; transient=&quot;false&quot; version=&quot;3.0&quot;&gt;<br>  &lt;site enabled=&quot;true&quot; policy=&quot;USER-EXCLUDE&quot; updateable=&quot;true&quot; url=&quot;platform:/base/&quot;&gt;<br>    &lt;feature id=&quot;org.eclipse.platform&quot; url=&quot;features/org.eclipse.platform_3.1.0/&quot; version=&quot;3.1.0&quot;&gt;
-    &lt;/feature&gt;<br>    &lt;feature id=&quot;org.eclipse.platform.source&quot; url=&quot;features/org.eclipse.platform.source_3.1.0/&quot; version=&quot;3.1.0&quot;&gt;
-    &lt;/feature&gt;<br>    &lt;feature id=&quot;org.eclipse.rcp&quot; url=&quot;features/org.eclipse.rcp_3.1.0/&quot; version=&quot;3.1.0&quot;&gt;
-    &lt;/feature&gt;<br>    &lt;feature id=&quot;org.eclipse.jdt&quot; url=&quot;features/org.eclipse.jdt_3.1.0/&quot; version=&quot;3.1.0&quot;&gt;<br>    &lt;/feature&gt;<br>    &lt;feature id=&quot;org.eclipse.jdt.source&quot; url=&quot;features/org.eclipse.jdt.source_3.1.0/&quot; version=&quot;3.1.0&quot;&gt;<br>    &lt;/feature&gt;<br>    &lt;feature id=&quot;org.eclipse.pde&quot; url=&quot;features/org.eclipse.pde_3.1.0/&quot; version=&quot;3.1.0&quot;&gt;<br>    &lt;/feature&gt;<br>    &lt;feature id=&quot;org.eclipse.sdk&quot; url=&quot;features/org.eclipse.sdk_3.1.0/&quot; version=&quot;3.1.0&quot;&gt;<br>    &lt;/feature&gt;<br>    &lt;feature id=&quot;org.eclipse.pde.source&quot; url=&quot;features/org.eclipse.pde.source_3.1.0/&quot; version=&quot;3.1.0&quot;&gt;<br>    &lt;/feature&gt;<br>    &lt;feature id=&quot;org.eclipse.rcp.source&quot; url=&quot;features/org.eclipse.rcp.source_3.1.0/&quot; version=&quot;3.1.0&quot;&gt;<br>    &lt;/feature&gt;<br>  &lt;/site&gt;<br>  &lt;site enabled=&quot;true&quot; policy=&quot;USER-EXCLUDE&quot; updateable=&quot;true&quot; url=&quot;file:/d:/extensions/org.eclipse.core.tools/eclipse/&quot;&gt;
-  &lt;/site&gt;<br>&lt;/config&gt;
-</pre>
-</div>
-
-</body></html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/update_policy.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/update_policy.html
deleted file mode 100644
index ea712ac..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/update_policy.html
+++ /dev/null

@@ -1,153 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Eclipse update policy control</title>
-</HEAD>
-
-<BODY>
-
-<h1>Eclipse Update Policy Control</h1>
-
-<p>Eclipse Update allows users to search for updates to the currently installed 
-features. For each installed feature, Update uses the embedded URL to 
-connect to the remote server and search for new versions. If there are updates, 
-Eclipse allows users to initiate the install procedure. After downloading, 
-installing and restarting the platform, new feature version is ready for use.</p>
-<p>In companies with many users of the same Eclipse-based product (typically a 
-commercial one), several problems can arise from this model:</p>
-<ol>
-  <li>Updates for very large products (e.g. 500+ plug-ins) are also large. 
-  I/T support teams may not like the idea of hundreds of developers individually 
-  downloading 500MEG updates to their individual machines. In addition to the 
-  bandwidth hit, such a large download request may fail, leading to repeated 
-  attempts and increased developers' downtime.</li>
-  <li>Some companies explicitly don't want the developers downloading updates 
-  directly from the Internet. For example, they can set up a local support team 
-  that may not be ready to handle requests related to the version of the product
-    already available from the provider's update site. They may want to restrict updates and 
-  fixes to the internally approved list. Ideally, they would do that by setting 
-  up 'proxy' update sites on the LAN (behind the firewall).</li>
-  <li>Once updates are set in the proxy sites as above, administrators need a 
-  way of letting users know that updates are available.</li>
-</ol>
-<h2>2. Update policy to the rescue</h2>
-
-<h3>2.1 Support for creating local (proxy) update sites</h3>
-<p>First step for a product administrator would be to set up a local Eclipse 
-update site on a server connected to the company's LAN (behind the firewall). 
-The update site would be a subset of the product's update site on the Internet 
-because it would contain only features and plug-ins related to the updates that 
-the company wants applied at the moment. Technically, this site would be a 
-regular Eclipse update site with site.xml, feature and plug-in archives.</p>
-<p>Administrators would construct this site in two ways:</p>
-<ol>
-  <li>Product support teams would make a zip file of the update site readily 
-  available for this particular purpose. Administrators would simply need to 
-  download the zip file from the product support web page using the tool of 
-  their choice and unzip it in the local server. This approach is useful for 
-  very large zip files that require modern restartable downloading managers 
-  (those that can pick up where they left off in case of the connection 
-  problems).</li>
-  <li>Eclipse Update provides a tool to mirror remote update sites 
-  entirely or allow administrators to select updates and fixes to download.
-  This mirroring capability would be fully automated and would greatly simplify administrator's task 
-  but it relies on Update network connection support.</li>
-</ol>
-<h3>2.2 Common update policy control</h3>
-<p>Since features have the update site URL embedded in the manifest, they are unaware of the local 
-update sites set up by the administrators. It is therefore important to provide <b>
-redirection capability</b>. This and other update policy settings can be set for
-an Eclipse product by creating an update policy file and configuring Update to 
-use that file when searching.</p>
-<p>The file in question uses XML format and can have any name. The file can be set in <b>
-Preferences&gt;Install/Update</b> in the <b>Update Policy</b> field. The text field 
-is empty by default: users may set the URL of the update policy file. The file 
-is managed by the local administrator and is shared for all the product 
-installations. Sharing can be achieved in two ways:</p>
-<ul>
-  <li>If users install the product: users are told to open the preference page 
-  and enter the provided URL</li>
-  <li>If administrators install the product: administrators edit the file 'plugin_customization.ini' 
-  in the primary product feature and set the default value of the 'updatePolicyURL' 
-  property as follows:
-  <blockquote><pre>
-org.eclipse.update.core/updatePolicyURL = &lt;URL value&gt;</pre></blockquote>
-  This will cause all the installations to have this file set by default.</li>
-</ul>
-<p>The policy file must conform to the following DTD:</p>
-<blockquote><pre>&lt;?xml encoding=&quot;ISO-8859-1&quot;?&gt;
-
-&lt;!ELEMENT update-policy (url-map)*&gt;
-&lt;!ATTLIST update-policy
-&gt;
-
-&lt;!ELEMENT url-map EMPTY&gt;
-	pattern	CDATA #REQUIRED
-	url	CDATA #REQUIRED
-&gt;
-</pre></blockquote>
-
-<h4>url-map</h4>
-<ul>
-  <li><b>pattern</b> - a string that represents prefix of a feature ID (up to
-    and including a complete ID). A value of "*" matches all the features.</li>
-  <li><b>url</b> - a URL of the alternative update site that should be used if
-    the feature ID begins with the pattern. If the string is empty, features matching 
-    pattern will not be updateable.</li>
-</ul>
-<p>This element is used to override Update URLs embedded in feature manifests. When
-looking for new updates, Eclipse search will check the update policy (if 
-present) and check if <b>url-map</b> for the matching feature prefix is 
-specified. If a match is found, the mapped URL will be used <b> instead</b> of the 
-embedded one. This way, administrators can configure Eclipse products to search 
-for updates in the local server behind the firewall. Meanwhile, third-party
-features installed by Eclipse Update will continue to be updated using the
-default mechanism because they will not find matches in the policy.</p>
-<p>Several <b>url-map</b> elements may exist in the file. Feature prefixes can be 
-chosen to be less or more specific. For example, to redirect all Eclipse 
-updates, the pattern attribute would be <code>&quot;org.eclipse&quot;</code>. Similarly, it is 
-possible to use a complete feature ID as a pattern if redirection is required on 
-a per-feature basis.</p>
-<p>Patterns in the file may be chosen to progressively narrow the potential
-matches. This may result in multiple matches for a given feature. In this case,
-the <b>match with a longest pattern</b> will be used. For
-example:</p>
-<blockquote>
-<pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
-&lt;update-policy&gt;
-	&lt;url-map pattern=&quot;org.eclipse&quot; url=&quot;URL1&quot;/&gt;
-	&lt;url-map pattern=&quot;org.eclipse.jdt&quot; url=&quot;URL2&quot;/&gt;
-&lt;/update-policy&gt;</pre>
-</blockquote>
-<p>In the case above, all Eclipse features will be updated from URL1, except <code>org.eclipse.jdt</code> that will use URL2.</p>
-<p>Update policy files do not contain translatable strings and therefore do not
-require special NL handling. In general, the files should use UTF-8 encoding.</p>
-<h3>2.3 Automatic discovery of updates</h3>
-<p>Automatic updates will allow Eclipse to run update search on a 
-specified schedule (on each startup (the default), once a day, once a week 
-etc.). </p>
-<h2>3. Summary </h2>
-<p>Here is the complete sequence of steps that comprise the solution:</p>
-<ol>
-  <li>Administrator allocates a server on the company LAN for hosting local 
-  product updates. Initially it contains no update sites. The machine must have
-    an HTTP server running.</li>
-  <li>Administrator sets up an update policy file on that server and instructs 
-  all users to set the update policy preference the provided URL.</li>
-  <li>As the product provider ships updates and fixes on their update sites,
-    administrator downloads supported updates onto the local server.</li>
-  <li>Automatic update executed at the scheduled frequency when the client's
-    product is up picks up the local 
-  updates and notifies the user</li>
-  <li>User chooses to install the discovered updates</li>
-</ol>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/update_sitemap.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/update_sitemap.html
deleted file mode 100644
index 442751f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/update_sitemap.html
+++ /dev/null

@@ -1,264 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta name="Author" content="Lab User">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Update server site map</title>
-</head>
-<body>
-
-<h1>
-Update server site map</h1>
-The default Eclipse update server is any URL-accessible server. The default
-implementation assumes a fixed-layout server. The content of the server
-(in terms of available features and plug-ins) is described in a site map
-file, <i>site.xml</i>. This file can be manually maintained, or can be
-dynamically computed by the server.
-<h3>
-Site Map</h3>
-The update server URL can be specified as a full URL to the site map file,
-or a URL of a directory path containing the site map file (similar to index.html
-processing). The site map site.xml format is defined by the following dtd:
-<p><tt>&lt;?xml encoding="ISO-8859-1"?></tt></p>
-<p><tt>&lt;!ELEMENT site (description?, feature*, archive*, category-def*)></tt>
-<br><tt>&lt;!ATTLIST site</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; mirrorsURL&nbsp;&nbsp;&nbsp; CDATA #IMPLIED</tt>
-<br><tt>></tt></p>
-<p><tt>&lt;!ELEMENT description (#PCDATA)></tt>
-<br><tt>&lt;!ATTLIST description</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>></tt></p>
-<p><tt>&lt;!ELEMENT feature (category*)></tt>
-<br><tt>&lt;!ATTLIST feature</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; version&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt> <tt>&nbsp;&nbsp;&nbsp;  </tt>
-<br><tt>&nbsp;&nbsp;&nbsp; patch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-(false | true) false</tt> <tt>&nbsp;</tt></p><p><tt>&nbsp;&nbsp;&nbsp; os&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; nl&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; arch&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; ws &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt>
-<br><tt>></tt></p>
-<p><tt>&lt;!ELEMENT archive EMPTY></tt>
-<br><tt>&lt;!ATTLIST archive</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; path&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt>
-<br><tt>></tt></p>
-<p><tt>&lt;!ELEMENT category EMPTY></tt>
-<br><tt>&lt;!ATTLIST category</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt>
-<br><tt>></tt></p>
-<p><tt>&lt;!ELEMENT category-def (description?)></tt>
-<br><tt>&lt;!ATTLIST category-def</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt>
-<br><tt>></tt></p>
-<p>The element and attribute definitions are as follows:</p>
-<ul>
-
-<li>&lt;site&gt; - defines the site map
-<ul>
-<li>type - optional site type specification. The value refers to a type string
-registered via the install framework extension
-point. If not specified, the type is assumed to be the default Eclipse
-site type (as specified in this document).</li>
-<li>url - optional URL defining the update site baseline URL (used to determine
-individual &lt;feature> and &lt;archive> location).&nbsp; Can be relative
-or absolute. If relative, is relative to site.xml. If not specified, the
-default is the URL location of the site.xml file.</li>
-<li>mirrorsURL - optional URL pointing to a file that contains update site mirror 
-definitions. This URL can be absolute or relative to this site. The mirrors file 
-is described later in this document.</li>
-</ul>
-</li>
-
-<li>&lt;description&gt; - brief description as simple text. Intended to be translated.
-<ul>
-<li>url - optional URL for the full description as HTML. The URL can be specified
-as absolute of relative. If relative, the URL is relative to site.xml.
-<br>Note, that for NL handling the URL value should be separated to allow
-alternate URLs to be specified for each national language.</li>
-</ul>
-</li>
-
-<li>&lt;feature&gt; - identifies referenced feature archive
-<ul>
-<li>type - optional feature type specification. The value refers to a type
-string registered via the install framework extension
-point. If not specified, the type is assumed to be the default feature
-type for the site. If the site type is the default Eclipse site type, the
-default feature type is the packaged feature type (as specified in this
-document).</li>
-<li>id - optional feature identifier. The information is used as a performance
-optimization to speed up searches for features. Must match the identifier
-specified in the feature.xml of the referenced archive (the url attribute).
-If specified, the version attribute must also be specified.</li>
-<li>version - optional feature version. The information is used as a performance
-optimization to speed up searches for features. Must match the version
-specified in the feature.xml of the referenced archive (the url attribute).
-If specified, the id attribute must also be specified.</li>
-<li>url - required URL reference to the feature archive. Can be relative or
-absolute. If relative, it is relative to the location of the site.xml file.
-<b>Note</b>:
-the default site implementation allows features to be accessed without
-being explicitly declared using a &lt;feature> entry. By default, an undeclared
-features reference is interpreted as "features/&lt;id>_&lt;version>.jar".
-<b>Note</b>: for better lookup performance, always define the id and version 
-attributes.</li>
-<li>patch - optional attribute to denote that this is a patch (special type of 
-feature).
-<b>Note</b>: for better lookup performance, always define this attribute.</li>
-<li>os - optional operating system specification. A comma-separated list of
-operating system 
-designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>. Indicates this feature should only be 
-installed on one of the specified OS's. If this attribute is not 
-specified, the feature can be installed on all systems (portable 
-implementation). This information is used as a hint by the installation and 
-update support (user can force installation of feature regardless of this 
-setting). </li>
-<li>arch - optional machine architecture specification. A comma-separated list of 
-architecture designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>. Indicates this feature should only be 
-installed on one of the specified systems. If this attribute is not specified, 
-the feature can be installed on all systems (portable implementation). This 
-information is used as a hint by the installation and update support (user can 
-force installation of feature regardless of this setting). </li>
-<li>ws - optional windowing system specification. A comma-separated list of
-window system 
-designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>. Indicates this feature should only be 
-installed on one of the specified WS's. If this attribute is not 
-specified, the feature can be installed on all systems (portable 
-implementation). This information is used as a hint by the installation and 
-update support (user can force installation of feature regardless of this 
-setting). </li>
-<li>nl - optional locale specification. A comma-separated list of locale designators 
-defined by Java. Indicates this feature should only be installed on a system 
-running with a compatible locale (using Java locale-matching rules). If this 
-attribute is not specified, the feature can be installed on all systems 
-(language-neutral implementation). This information is used as a hint by the 
-installation and update support (user can force installation of feature 
-regardless of this setting).</li>
-</ul>
-</li>
-
-<li>&lt;archive&gt; - identifies referenced "storage" archive (the actual files
-referenced via the <tt>&lt;plugin></tt> or <tt>&lt;data></tt> elements
-in the feature manifest). The site simply manages archives as a path-to-URL
-map. The default Eclipse site implementation does not require the &lt;archive>
-section to be included in the site map (site.xml). Any archive reference
-not explicitly defined as part of an &lt;archive> section is assumed to
-be mapped to a url in the form "&lt;archivePath>" relative to the location
-of the site.xml file.
-<ul>
-<li>path - required archive path identifier. This is a string that is determined
-by the feature referencing
-this archive and is not otherwise interpreted by the site (other than as
-a lookup token).</li>
-<li>url - required URL reference to the archive. Can be relative or absolute.
-If relative, it is relative to the location of the site.xml file.</li>
-</ul>
-</li>
-
-<li>&lt;category-def&gt; - an optional definition of a category that can be used
-by installation and update support to hierarchicaly organize features
-<ul>
-<li>name - category name. Is specified as a path of name tokens separated by /</li>
-<li>label - displayable label. Intended to be translated.</li>
-</ul>
-</li>
-
-<li>&lt;category&gt; - actual category specification for a feature entry
-<ul>
-<li>name - category name</li>
-</ul>
-</li>
-</ul>
-
-<p>Note, that in general the feature.xml manifest documents should specify
-UTF-8 encoding. For example:</p>
-<p><tt>&lt;?xml version="1.0" encoding="UTF-8"?></tt></p>
-<p>Translatable text contained in the site.xml can be separated into site&lt;_locale>.properties
-files using Java property bundle conventions. Note that the translated
-strings are used at installation time (ie. do not employ the plug-in fragment
-runtime mechanism). The property bundles are located relative to the site.xml
-location.</p>
-<h3>Default Site Layout</h3>
-<p><tt>&lt;site root>/</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; site.xml</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; features/</tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; feature archives&nbsp;&nbsp;
-(eg. org.eclipse.javatools_1.0.1.jar)</tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;featureId>_&lt;featureVersion>/&nbsp;&nbsp;&nbsp;
-(optional)</tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-non-plug-in files for feature</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; plugins/</tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; plug-in archives&nbsp;&nbsp;&nbsp;
-(eg. org.eclipse.ui_1.0.3.jar)</tt></p>
-<h3>
-Mirrors File</h3>
-<p>The update mirrors file (the one pointed at by the mirrorsURL attribute of 
-&lt;site&gt;) contains definition for update site mirrors. It format is defined by the following dtd:
-</p>
-<p><tt>&lt;?xml encoding="ISO-8859-1"?></tt></p>
-<p><tt>&lt;!ELEMENT mirrors (mirror*))></tt>
-<br>&nbsp;</p><p><tt>&lt;!ELEMENT mirror EMPTY&gt;</tt>
-<br><tt>&lt;!ATTLIST mirror</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt> <tt>&nbsp;&nbsp;&nbsp;  </tt>
-<br><tt>&nbsp;&nbsp;&nbsp; label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA #REQUIRED</tt>
-<br><tt>></tt></p>
-<ul>
-<li>&lt;mirrors&gt; - defines the available update site mirrors</li>
-<li>&lt;mirror&gt; - defines a mirror site
-<ul>
-<li>url - the URL of the mirror site</li>
-<li>label - displayable label. Intended to be translated.</li>
-</ul>
-</li>
-</ul>
-
-<h3>Controlling Access</h3>
-<p>The default Eclipse site implementation provides support for http access
-with basic user authentication (userid and password).</p>
-<p>Custom access control mechanisms can be added to base Eclipse in one
-of 2 ways:</p>
-<ul>
-<li>
-by supplying server-side logic on the update server (eg. implementing servlets
-that compute the site.xml map, and control access to individual archives
-based on some user criteria)</li>
-
-<li>
-by supplying a custom concrete implementation of the site object (installed
-on the client machine, update server specified <tt>&lt;site type=""></tt>).
-The custom concrete site implementation, together with any server-side
-logic support the required control mechanisms.</li>
-</ul>
-<p>Eclipse provides an example demonstrating an implementation of an access
-mechanism based on feature key files.
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/update_standalone.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/update_standalone.html
deleted file mode 100644
index da62124..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/update_standalone.html
+++ /dev/null

@@ -1,131 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Running update manager from command line</title>
-</head>
-<body>
-
-<h1>Running update manager from command line</h1>
-In addition to the install wizard and configuration dialog, it is possible to perform
-update manager operations by running eclipse in a command line mode. You can install, update, enable, disable features,
-or list installed features, or features available on an update site, or adding an extension product site to the local install, etc.
-<br>
-You can also, mirror chosen features from an update site to a local update site location.<br>
- <br>
-Launch eclipse as follows, where [ ] means optional argument and arguments in italics must be provided by the user.<br>
-	<br>
-<b>Installing a feature from a remote site</b>:<br>
- java -cp startup.jar org.eclipse.core.launcher.Main <br>
- &nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate<br>
- &nbsp;&nbsp;&nbsp; -command install <br>
- &nbsp;&nbsp;&nbsp; -featureId <i>feature_id </i><br>
- &nbsp;&nbsp;&nbsp; -version <i>version </i><br>
- &nbsp;&nbsp;&nbsp; -from <i>remote_site_url</i> <br>
- &nbsp;&nbsp;&nbsp; [-to <i>target_site_dir</i>] <br>
-<p>
-	<b>Example:</b> <code>java -cp startup.jar org.eclipse.core.launcher.Main -application org.eclipse.update.core.standaloneUpdate -command install  -from http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/optionalSite/ -featureId com.example.root -version 1.0.0</code>
-	</p>
- <br>
-<b>Updating an existing feature or all features</b>:<br>
- java -cp startup.jar org.eclipse.core.launcher.Main <br>
- &nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate<br>
- &nbsp;&nbsp;&nbsp; -command update<br>
- &nbsp;&nbsp;&nbsp; [-featureId <i>feature_id </i>]<br>
-  &nbsp;&nbsp;&nbsp; [-version <i>version </i>]<br>
-<br>
-<b>Enabling (configuring) a specified feature:</b><br>
- java -cp startup.jar org.eclipse.core.launcher.Main <br>
- &nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate<br>
- &nbsp;&nbsp;&nbsp; -command enable<br>
- &nbsp;&nbsp;&nbsp; -featureId <i>feature_id </i><br>
- &nbsp;&nbsp;&nbsp; -version <i>version </i><br>
- &nbsp;&nbsp;&nbsp; [-to <i>target_site_dir</i>] <br>
-<br>
-<b>Disabling (unconfiguring) a specified feature:</b><br>
- java -cp startup.jar org.eclipse.core.launcher.Main <br>
- &nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate<br>
- &nbsp;&nbsp;&nbsp; -command disable<br>
- &nbsp;&nbsp;&nbsp; -featureId <i>feature_id </i><br>
- &nbsp;&nbsp;&nbsp; -version <i>version </i><br>
- &nbsp;&nbsp;&nbsp; [-to <i>target_site_dir</i>] <br>
-<br>
-<b>Uninstalling a specified feature:</b><br>
- java -cp startup.jar org.eclipse.core.launcher.Main <br>
- &nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate<br>
- &nbsp;&nbsp;&nbsp; -command uninstall<br>
- &nbsp;&nbsp;&nbsp; -featureId <i>feature_id </i><br>
- &nbsp;&nbsp;&nbsp; -version <i>version </i><br>
- &nbsp;&nbsp;&nbsp; [-to <i>target_site_dir</i>] <br>
-<br>
-In all the above commands where the -to target_site_dir is specified, corresponding
-configured target site at given directory will be used. If it is not specified,
-then the default local product site is used.<br>
-<br>
-If you only need to verify if the operation would succeed, in the above commands, (i.e. it satisfies the constraints), without actually performing it,
-then add <b><em>-verifyOnly=true</em></b> to the list of arguments.<br>
-
-<br><b>Searching a remote site, listing all available features for install:</b><br>
- java -cp startup.jar org.eclipse.core.launcher.Main <br>
- &nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate<br>
- &nbsp;&nbsp;&nbsp; -command search<br>
- &nbsp;&nbsp;&nbsp; -from <i>remote_site_url</i> <br>
-
-<br><b>Listing installed features:</b><br>
- java -cp startup.jar org.eclipse.core.launcher.Main <br>
- &nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate<br>
- &nbsp;&nbsp;&nbsp; -command listFeatures<br>
- &nbsp;&nbsp;&nbsp; -from <i>local_site_dir</i> <br>
- <br>
- The features are listed as:
- <br>
- <code>
- Site: <em>site url </em><br>
-  &nbsp;&nbsp;Feature: <em>id version</em>  enabled (or disabled)
- </code>
- <br>
-
-<br><b>Adding a local site with more features:</b><br>
- java -cp startup.jar org.eclipse.core.launcher.Main <br>
- &nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate<br>
- &nbsp;&nbsp;&nbsp; -command addSite<br>
- &nbsp;&nbsp;&nbsp; -from <i>local_site_dir</i> <br>
-
-<br><b>Removing a local site:</b><br>
- java -cp startup.jar org.eclipse.core.launcher.Main <br>
- &nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate<br>
- &nbsp;&nbsp;&nbsp; -command removeSite<br>
- &nbsp;&nbsp;&nbsp; -to <i>local_site_dir</i> <br>
- 
-<br>
-<b>Mirroring feature(s) from a remote site:</b><br>
- java -cp startup.jar org.eclipse.core.launcher.Main <br>
- &nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate<br>
- &nbsp;&nbsp;&nbsp; -command mirror<br>
- &nbsp;&nbsp;&nbsp; -from <i>remote_site_url</i> <br>
- &nbsp;&nbsp;&nbsp; -to <i>target_site_dir</i><br>
- &nbsp;&nbsp;&nbsp; [-featureId <i>feature_id</i>]<br>
- &nbsp;&nbsp;&nbsp; [-version <i>version</i>]<br>
- &nbsp;&nbsp;&nbsp; [-mirrorURL <i>mirror_site_url</i>]<br>
-<br>
-If -mirrorURL is specified, an update policy will be generated in
-&lt;target_site_dir&gt;/policy.xml file.  The resulting policy.xml
-maps all features from the mirror site to the specified URL.
-The policy.xml can be used as is, or its fragments
-can be included into custom designed policy file.
-<br>
-<br>
-The return code for each command is either 0 (success) or 1 (failure).<br>
-<br>
-Additionally, most <A
-	href="../../../org.eclipse.platform.doc.user/tasks/running_eclipse.htm">options
-	accepted by Eclipse executable</A> can be passed. They are especially
-	useful during debugging and for specifying target environment for installed features.
-	For example, passing option
-	<code>-data some_path</code> will set the workspace to some_path.<br>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/web_triggered_updates.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/web_triggered_updates.html
deleted file mode 100644
index 81ec765..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/web_triggered_updates.html
+++ /dev/null

@@ -1,168 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta name="Author" content="Lab User">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Web-triggered updates</title>
-</head>
-<body>
-
-<h1>
-Web-triggered updates</h1>
-<p>Eclipse update manager can be used to render and browse Eclipse update sites
-in a predictable manner. An update site can contain categories shown in the tree
-view, and these categories in turn contain features. Features can be inspect in
-the Preview view inside update manager. If a feature is a valid install
-candidate, it will contain a button &quot;Install Now&quot; that will launch
-Eclipse install wizard. Upon completion of the install task, the feature will be
-part of the product.</p>
-<p>This standard way of presenting features for installation is not the only
-way. Providers can take over presentation, registration, search and other tasks
-from update manager and return control only when it is time to actually install
-a feature into an Eclipse product.</p>
-<p>Update manager is capable of running a servlet that can accept requests from
-Web pages. This capability is not automatic: it must be activated in <b>Preferences&gt;Install/Update&gt;Web-triggered
-Updates</b> page. When <b>OK</b> is pressed, update manager will activate the
-application server that can handle incoming requests. After that, all URLs
-opened from within Update Manager will be encoded with the callback URL
-information. If the initial URL is a regular Web page, the encoded URL will have
-the query part that adds the callback URL to use to call Eclipse:</p>
-<blockquote>
-  <div align="left">
-    <pre align="left">http://acme.com/myApplication.html</pre>
-  </div>
-</blockquote>
-<p align="left">becomes</p>
-<blockquote>
-  <div align="left">
-    <pre align="left">http://acme.com/myApplication.html?updateURL=&lt;localhost&gt;:&lt;localport&gt;?org.eclipse.update/install</pre>
-  </div>
-</blockquote>
-<p align="left">where 'localhost' is the address of the Eclipse server running
-on your local machine, local port is selected dynamically when the server is
-started, and the query is the Eclipse Web application name and the name of the
-servlet that handles the request.</p>
-<p align="left">If the original URL is already a query:</p>
-<blockquote>
-  <div align="left">
-    <pre align="left">http://acme.com/myApplication/myServlet?arg1=value1&amp;arg2=value2</pre>
-  </div>
-</blockquote>
-<p align="left">the encoding will simply add our information as another
-parameter:</p>
-<blockquote>
-  <div align="left">
-    <pre align="left">http://acme.com/myApplication/myServlet?arg1=value1&amp;arg2=value2&amp;updateURL=&lt;localhost&gt;:&lt;localport&gt;?org.eclipse.update/install</pre>
-  </div>
-</blockquote>
-<p align="left">The encoding is ignored by normal web pages and queries and does
-not cause any problems nor it affects the presentation. It simply adds
-information that can be used by a page that knows about it.</p>
-<p align="left">Since a Web page must be launched from update manager, site
-bookmarks in Updates view can be created as Web bookmarks. Update manager treats
-these bookmarks accordingly and when you double-click on one, it will open the
-URL in a browser (if embedded browser is available on the version of operating
-and windowing system, it will open directly inside update manager; otherwise, it
-will open in the resident browser window).</p>
-<h3 align="left">Tasks that can be performed in a Web page</h3>
-<p align="left">Providers can set up their Update web pages any way they want:
-they can use elaborate Web applications backed by databases, or use simple,
-static HTML. Using more complex architecture allows providers to offer more
-value to users. Complex searches for new features, updates and e-fixes, rich
-visual presentations of selected features, articles on their functionality,
-various useful links, 'most popular features' votes are just some of the
-possibilities. In addition, providers can enable authentication to restrict
-access to some of the features, require user registration etc.</p>
-<h3 align="left">Calling Eclipse from a Web page</h3>
-<p align="left">There are many different ways to extract the encoded
-information. A very simple one is to use Java Script function as shown below:</p>
-<blockquote>
-  <pre align="left">&lt;SCRIPT LANGUAGE=&quot;JavaScript&quot;&gt;
-
-function getArgs() {
-   var args = new Object();
-   var query = location.search.substring(1);
-   var pairs = query.split(&quot;&amp;&quot;);
-   for (var i=0; i&lt;pairs.length; i++) {
-      var pos = pairs[i].indexOf('=');
-      if (pos == -1) continue;
-      var argname = pairs[i].substring(0, pos);
-      var value = pairs[i].substring(pos+1);
-      args[argname] = unescape(value);
-   }
-   return args;
-}
-&lt;/SCRIPT&gt;</pre>
-</blockquote>
-<p align="left">The function above parses the URL of the current page and
-returns query arguments as an array.</p>
-<p align="left">The role of the callback URL is to allow Web pages to return
-control back to Eclipse. Once user selected a feature to install, it must return
-back to Eclipse to complete it. The role of Web-triggered update is not to make
-update sites obsolete: they are still needed, but in this scenario they are used
-simply as a location where features are physically stored. Web page must at some
-point call back into Eclipse and pass the update site URL, as well as the
-selected feature ID and version. This information is encoded by using the
-original callback URL and adding the arguments, thus forming a query.</p>
-<p>The arguments for the callback query are:</p>
-<ul>
-  <li><b>server</b> - expects a URL of the Eclipse Update site (the one with
-    site.xml) where feature and plug-in archives are placed. This URL can be the
-    same as the web site, or can be a completely different server (you probably
-    had experience with download sites in which the actual data servers are
-    different from the front end and use different protocols, e.g. FTP).</li>
-  <li><b>feature</b> - expects a string in the form &lt;id&gt;_&lt;version&gt;
-    where 'id' is the feature identifier and 'version' is its version. These
-    values will be used to locate the feature on the update server.</li>
-  <li><b>backURL</b> - passes the URL of the page itself that will be used in
-    Eclipse servlet to feed the 'Go Back' links (those that will get you back to
-    this page)</li>
-</ul>
-<p align="left">Calling back to Eclipse should be done when users finished all
-their selections in the Web page and all that is left is to press some kind of
-'Download' button or hyperlink. A simple implementation of this capability would
-be:</p>
-<div align="left">
-  <blockquote>
-    <pre align="left">&lt;input type=&quot;button&quot; 	name=&quot;Download&quot; value=&quot;Download&quot; 
-			onClick=&quot;javascript:download('com.example.root', '1.0.0')&quot;&gt;</pre>
-  </blockquote>
-</div>
-<p>In the code above, feature Id and versions are hard-coded in the button tag.</p>
-<p>The download function can be implemented as follows:</p>
-<blockquote>
-  <pre>function download(id, version) {
-   var args = getArgs();
-   if (args.updateURL) {
-      var updateURL = args.updateURL;
-      var callback = updateURL+&quot;?server=
-      &quot;+escape(&quot;<a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-update-home/optionalSite/index.html">http://acme.com/updateSite</a>/&quot;)+
-      &quot;&amp;feature=&quot;+escape(id+'_'+version)+&quot;&amp;backURL=&quot;+escape(location);
-      location = callback;
-   }
-}</pre>
-</blockquote>
-<p>In the JavaScript function above, the callback URL that was encoded in the
-page URL from the beginning is used to form the query. Once the query is
-created, the browser is asked to open it. This step will cause the browser to
-call Eclipse servlet, which will process the query, connect to the provider
-update site (in this case &quot;http://acme.com/updateSite/&quot;) and locate
-the feature with the provided id and version. If everything goes well, Eclipse
-window will be brought to the top and the familiar install wizard will open. At
-that point, you will be back in Eclipse and can finish the installation as
-usual.</p>
-<p>It is important to point out that having encoded callback URL is crucial for
-the whole mechanism. If the page that contains the 'download' link or button is
-several levels deep in the web site map, the root web page (the one launched
-from update manager) has to ensure the callback URL passed down to all pages
-opened from within that page. It can be done in various ways (direct encoding in
-the page, saving a transient cookie, storing it in a servlet that serves the
-pages from the site etc.).</p>
-<p>&nbsp;</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/win_only.png b/bundles/org.eclipse.platform.doc.isv/reference/misc/win_only.png
deleted file mode 100644
index 7523f99..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/win_only.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/samples/samples.html b/bundles/org.eclipse.platform.doc.isv/samples/samples.html
deleted file mode 100644
index f3c7980..0000000
--- a/bundles/org.eclipse.platform.doc.isv/samples/samples.html
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <title>Installation of Examples</title>
-   <LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-</head>
-<body>
-
-<h1>
-<b>Installing the examples</b></h1>
-
-<h3>
- Installing examples via the Update Manager</h3>
-
-<p>
-The Eclipse SDK examples are found on the Eclipse project update site at <a href="http://update.eclipse.org/updates">http://update.eclipse.org/updates</a>.
-To locate and install them into a product:</p>
-
-<ol>
-  <li>Open the main update manager by clicking <b>Help &gt; Software Updates &gt; Find 
-  and Install</b>. This opens the Install Wizard.</li>
-  <li> Select &quot;Search for new features&quot; and click <b>Next</b>.</li>
-  <li> In the sites to search page, add an update site by clicking on <b>Add 
-  Update Site </b>button: In the Add Update Site dialog that opens, give the site
-    the name 
-    &quot;Eclipse.org&quot; and URL
-	&quot;<a href="http://update.eclipse.org/updates">http://update.eclipse.org/updates</a>&quot;. 
-  Note: this step is not needed if the site is already there.</li>
-  <li>Click <b>Next</b> and wait for the search results to return all the 
-  features found on that site.</li>
-  <li>Select the SDK Examples feature and click <b>Next</b>. </li>
-  <li>Accept the license and click <b>Next</b>.</li>
-  <li> Select the directory into which the example feature is to be installed and hit <b>Next</b>.</li>
-  <li> <p>Click <b>Install</b> to allow the downloading and installing
-    to proceed.</p></li>
-  <li> Click <b>Yes</b> when asked to exit and restart the workbench for the
-    changes to take effect. The examples are now installed in the workbench. 
-  Note: you can also click on <b>Apply Now</b> to dynamically install the 
-  examples into the current configuration.</li>
-</ol>
-
-<h3>
- Installing examples manually</h3>
-To install the examples without the Update Manager, download the appropriate Eclipse SDK Example zip file from the
-Eclipse project web site at <a href="http://www.eclipse.org/downloads">http://www.eclipse.org/downloads</a>.
-<p>
-The workbench should not be running while the examples are being&nbsp;
-installed.&nbsp; Extract the contents of the zip file to the root directory&nbsp;
-of your Eclipse installation.&nbsp;</p>
-<p> For example, if you installed the Eclipse
-Project SDK on <b> d:\eclipse-sdk\</b> then extract the contents of the examples
-zip file to <b>d:\eclipse-sdk\</b> (the
-subdirectories named <b>eclipse</b> should line up).</p>
-<p>Start the workbench.&nbsp;The workbench will report that updates have been
-detected; accept them. The examples are now installed in the workbench.</p>
-
-<p>You can verify that examples have been installed by looking for <b>File &gt;
-New &gt; Example...</b> in the workbench menu bar.</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/schema.css b/bundles/org.eclipse.platform.doc.isv/schema.css
deleted file mode 100644
index 4efbf26..0000000
--- a/bundles/org.eclipse.platform.doc.isv/schema.css
+++ /dev/null

@@ -1,66 +0,0 @@
-H6.CaptionFigColumn#header {

-	font-size:16px; 

-	display:inline

-}

-

-P.Note#copyright {

-	font-size: smaller; 

-	font-style: normal;

-	color: #336699; 

-	display:inline;

-	margin-top: 3.000000pt;

-	margin-bottom: 11.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 0.000000pt;

-}

-

-P.Code#dtd {

-	color: #800000; 

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 10.000000pt;

-}

-

-P.Code#dtdAttlist {

-	color: #800000; 

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 20.000000pt;

-}

-

-P.Code#tag {

-	color: #000080; 

-	display:inline;

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 0.000000pt;

-}

-

-P.Code#cstring {

-	color: #008000; 

-	display:inline;

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 0.000000pt;	

-}

-

-.ConfigMarkup#elementDesc {

-	color: black;

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 10.000000pt;

-}

-

-.ConfigMarkup#attlistDesc {

-	color: black;

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 32.000000pt;

-}

-


diff --git a/bundles/org.eclipse.platform.doc.isv/src/org/eclipse/platform/doc/isv/activeHelp/ActiveHelpOpenDialogAction.java b/bundles/org.eclipse.platform.doc.isv/src/org/eclipse/platform/doc/isv/activeHelp/ActiveHelpOpenDialogAction.java
deleted file mode 100644
index 504a59e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/src/org/eclipse/platform/doc/isv/activeHelp/ActiveHelpOpenDialogAction.java
+++ /dev/null

@@ -1,55 +0,0 @@
-/*******************************************************************************
- * Copyright (c) 2002, 2005 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- *     IBM Corporation - initial API and implementation
- *******************************************************************************/
-package org.eclipse.platform.doc.isv.activeHelp;
-
-import org.eclipse.help.ILiveHelpAction;
-import org.eclipse.jface.dialogs.MessageDialog;
-import org.eclipse.swt.widgets.Display;
-import org.eclipse.swt.widgets.Shell;
-import org.eclipse.ui.IWorkbenchWindow;
-import org.eclipse.ui.PlatformUI;
-
-/**
- * Sample Active Help action.  This is the source code for the sample
- * active help action that is shown in the Platform Plug-in Developer Guide
- * in the Programmer's Guide.  This class is marked public because
- * it must be called from the active help servlet.  However, this class
- * is not intended to be used as API and should not be called by clients.
- */
-public class ActiveHelpOpenDialogAction implements ILiveHelpAction {
-
-     public void setInitializationString(String data) {
-          // ignore the data.  We do not use any javascript parameters.
-     }
-
-     public void run() {
-          // Active help does not run on the UI thread, so we must use syncExec
-          Display.getDefault().syncExec(new Runnable() {
-               public void run() {
-                    IWorkbenchWindow window =
-                         PlatformUI.getWorkbench().getActiveWorkbenchWindow();
-                    if (window != null) {
-                         // Bring the Workbench window to the top of other windows;
-                         // On some Windows systems, it will only flash the Workbench
-                         // icon on the task bar
-                         Shell shell = window.getShell();
-                         shell.setMinimized(false);
-                         shell.forceActive();
-                         // Open a message dialog
-                         MessageDialog.openInformation(
-                              window.getShell(),
-                              "Hello World.", //$NON-NLS-1$
-                              "Hello World."); //$NON-NLS-1$
-                    }
-               }
-          });
-     }
-}

diff --git a/bundles/org.eclipse.platform.doc.isv/toc.xml b/bundles/org.eclipse.platform.doc.isv/toc.xml
deleted file mode 100644
index 347e8ce..0000000
--- a/bundles/org.eclipse.platform.doc.isv/toc.xml
+++ /dev/null

@@ -1,24 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define the top level topics                                                   -->
-<!-- ============================================================================= -->
-
-<toc label="Platform Plug-in Developer Guide">
-	<topic label="Programmer&apos;s Guide">
-		<link toc="topics_Guide.xml" />
-	</topic>
-	<topic label="Reference">
-		<link toc="topics_Reference.xml" />
-	</topic>
-	<topic label="3.2 Plug-in Migration Guide">
-		<link toc="topics_Porting.xml"/>
-	</topic>
-	<topic label="Examples Guide">
-		<link toc="topics_Samples.xml" />
-	</topic>
-	<topic label="Questions Index" href="questions/index.html">
-		<link toc="topics_Questions.xml" />
-	</topic>
-	<topic label="Legal" href="notices.html"/>
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/topics_Guide.xml b/bundles/org.eclipse.platform.doc.isv/topics_Guide.xml
deleted file mode 100644
index 609a427..0000000
--- a/bundles/org.eclipse.platform.doc.isv/topics_Guide.xml
+++ /dev/null

@@ -1,338 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define topics for the main guide                                              -->
-<!-- ============================================================================= -->
-<toc label="Guide">
-	<topic label="Welcome to Eclipse" href="guide/int.htm">
-		<topic label="Who needs a platform?" href="guide/int_who.htm" />
-		<topic label="The holy grail" href="guide/int_goal.htm" />
-		<topic label="What is Eclipse?" href="guide/int_eclipse.htm" />
-		<topic label="Go to eclipse.org" href="http://www.eclipse.org" />
-	</topic>
-
-	<topic label="Platform architecture" href="guide/arch.htm">
-		<topic label="Platform SDK roadmap" href="guide/arch_struct.htm" />
-	</topic>
-
-	<topic label="Simple plug-in example" href="guide/firstplugin.htm">
-		<topic label="A minimal plug-in" href="guide/firstplugin_minimal.htm" />
-		<topic label="Creating the plug-in project" href="guide/firstplugin_create.htm" />
-		<topic label="The Hello World view" href="guide/firstplugin_view.htm" />
-		<topic label="The Hello World manifests" href="guide/firstplugin_manifest.htm" />
-		<topic label="Running the plug-in" href="guide/firstplugin_run.htm" />
-		<topic label="Beyond the basics" href="guide/firstplugin_btb.htm" />
-	</topic>
-
-	<topic label="Runtime overview"  href="guide/runtime.htm">
-		<topic label="The runtime plug-in model" href="guide/runtime_model.htm">
-			<topic label="Plug-ins and bundles" href="guide/runtime_model_bundles.htm"/>
-			<topic label="Extension points and the registry" href="guide/runtime_registry.htm"/>
-		</topic>
-		<topic label="Runtime preferences" href="guide/runtime_preferences.htm"/>
-		<topic label="Content types" href="guide/runtime_content.htm">
-			<topic label="Using content types" href="guide/runtime_content_using.htm"/>
-			<topic label="Contributing content types" href="guide/runtime_content_contributing.htm"/>		
-		</topic>
-		<topic label="Concurrency infrastructure" href="guide/runtime_jobs.htm">
-			<topic label="Reporting progress" href="guide/runtime_jobs_progress.htm"/>
-			<topic label="Job scheduling" href="guide/runtime_jobs_scheduling.htm"/>
-			<topic label="Scheduling rules" href="guide/runtime_jobs_rules.htm"/>
-			<topic label="Locks" href="guide/runtime_jobs_locks.htm"/>
-		</topic>
-	</topic>
-
-	<topic label="Plugging into the workbench"  href="guide/workbench.htm">
-		<topic label="Workbench under the covers" href="guide/workbench_structure.htm" />
-		<topic label="Basic workbench extension points" href="guide/workbench_basicext.htm" >
-			<topic label="org.eclipse.ui.views" href="guide/workbench_basicext_views.htm" />
-			<topic label="org.eclipse.ui.viewActions" href="guide/workbench_basicext_viewActions.htm" />
-			<topic label="org.eclipse.ui.editors" href="guide/workbench_basicext_editors.htm" />
-			<topic label="org.eclipse.ui.editorActions" href="guide/workbench_basicext_editorActions.htm" />
-			<topic label="org.eclipse.ui.popupMenus" href="guide/workbench_basicext_popupMenus.htm" />
-			<topic label="org.eclipse.ui.actionSets" href="guide/workbench_basicext_actionSets.htm" />
-		</topic>
-		<topic label="The plug-in class" href="guide/workbench_plugin.htm" />
-		<topic label="Preference pages" href="guide/preferences_prefs.htm">
-			<topic label="Contributing a preference page" href="guide/preferences_prefs_contribute.htm" />
-			<topic label="Implementing a preference page" href="guide/preferences_prefs_implement.htm" />
-			<topic label="Field editors" href="guide/preferences_prefs_fieldeditors.htm" />
-		</topic>
-	</topic>
-
-	<topic label="Dialogs and wizards"  href="guide/dialogs.htm">
-		<topic label="Standard dialogs" href="guide/dialogs_standard.htm" />
-		<topic label="Application dialogs" href="guide/dialogs_applications.htm" />
-		<topic label="Dialog settings" href="guide/dialogs_settings.htm" />
-		<topic label="Wizards" href="guide/dialogs_wizards.htm" />
-		<topic label="Workbench wizard extension points" href="guide/dialogs_wizards_extensions.htm" >
-			<topic label="org.eclipse.ui.newWizards" href="guide/dialogs_wizards_newWizards.htm" />
-			<topic label="org.eclipse.ui.importWizards" href="guide/dialogs_wizards_importWizards.htm" />
-			<topic label="org.eclipse.ui.exportWizards" href="guide/dialogs_wizards_exportWizards.htm" />
-		</topic>
-		<topic label="Wizard dialogs" href="guide/dialogs_wizards_wizarddialogs.htm" />
-		<topic label="Multi-page wizards" href="guide/dialogs_wizards_multipage.htm" />
-	</topic>
-	
-	<topic label="JFace UI framework" href="guide/jface.htm">
-		<topic label="Viewers" href="guide/jface_viewers.htm" />
-		<topic label="Actions and contributions" href="guide/jface_actions.htm" />
-		<topic label="User interface resources" href="guide/jface_resources.htm" />
-		<topic label="Long-running operations" href="guide/jface_operations.htm" />
-	</topic>
-
-	<topic label="Standard Widget Toolkit" href="guide/swt.htm">
-		<topic label="Widgets" href="guide/swt_widgets.htm" >
-			<topic label="Controls" href="guide/swt_widgets_controls.htm" />
-			<topic label="Events" href="guide/swt_widgets_events.htm" />
-			<topic label="Custom widgets" href="guide/swt_widgets_custom.htm" />
-		</topic>
-		<topic label="Layouts" href="guide/swt_layouts.htm" >
-			<topic label="Custom Layouts" href="guide/swt_layouts_custom.htm" />
-		</topic>
-		<topic label="Threading issues " href="guide/swt_threading.htm" />
-		<topic label="Error handling" href="guide/swt_error.htm" />
-		<topic label="Graphics" href="guide/swt_graphics.htm" />
-	</topic>
-	
-	<topic label="UI Forms" href="guide/forms.htm">
-       <topic label="Controls" href="guide/forms_controls.htm">
- 		   <topic label="Form" href="guide/forms_controls_form.htm"/>
-		   <topic label="Hyperlink" href="guide/forms_controls_link.htm"/>
-		   <topic label="Section" href="guide/forms_controls_section.htm"/>
-		   <topic label="FormText" href="guide/forms_controls_text.htm">
-   		      <topic label="XML Markup" href="guide/forms_controls_text_markup.htm"/>
-   		   </topic>
-	   </topic>
-	   <topic label="Layouts" href="guide/forms_layouts.htm">
-	      <topic label="TableWrapLayout" href="guide/forms_layouts_table.htm"/>
-	      <topic label="ColumnLayout" href="guide/forms_layouts_column.htm"/>
-	   </topic>
-	   <topic label="Advanced Topics">
-	      <topic label="Color and font management" href="guide/forms_colors.htm"/>
-	      <topic label="Managed forms" href="guide/forms_managed.htm"/>
-	      <topic label="Master/Details block" href="guide/forms_master_details.htm"/>
-	   </topic>
-	   <topic label="Multi-page form editors" href="guide/forms_editors.htm"/>
-	</topic>
-	
-	<topic label="Resources overview"  href="guide/resInt.htm">
-		<topic label="Resources and the workspace" href="guide/resInt_workspace.htm" />
-		<topic label="Resources and the local file system" href="guide/resInt_filesystem.htm" />
-		<topic label="Resource properties" href="guide/resInt_properties.htm" />
-		<topic label="Project-scoped preferences" href="guide/resInt_preferences.htm" />
-		<topic label="File encoding and content types" href="guide/resInt_content.htm" />
-		<topic label="Linked resources" href="guide/resInt_linked.htm" />
-		<topic label="Resource markers" href="guide/resAdv_markers.htm" />
-		<topic label="Modifying the workspace" href="guide/resAdv_modify.htm" >
-			<topic label="Batching resource changes" href="guide/resAdv_batching.htm" />
-			<topic label="Tracking resource changes" href="guide/resAdv_events.htm" />
-			<topic label="Concurrency and the workspace" href="guide/resAdv_concurrency.htm" />
-		</topic>
-		<topic label="Incremental project builders" href="guide/resAdv_builders.htm" />
-		<topic label="Derived resources" href="guide/resAdv_derived.htm" />
-		<topic label="Workspace save participation" href="guide/resAdv_saving.htm" />
-		<topic label="Project natures" href="guide/resAdv_natures.htm" />
-		<topic label="Resource modification hooks" href="guide/resAdv_hooks.htm" />
-		<topic label="Refresh providers" href="guide/resAdv_refresh.htm" />
-	</topic>
-
-	<topic label="Advanced Workbench Concepts" href="guide/wrkAdv.htm">
-		<topic label="Workbench menu contributions" href="guide/workbench_menus.htm" />
-		<topic label="Menu and toolbar paths" href="guide/workbench_menupaths.htm" />
-		<topic label="Action set part associations" href="guide/workbench_basicext_actionSetPartAssociations.htm" />
-		<topic label="Boolean expressions and action filters" href="guide/workbench_actionfilters.htm" />
-		<topic label="Retargetable actions" href="guide/wrkAdv_retarget.htm" >
-			<topic label="Setting a global action handler" href="guide/wrkAdv_retarget_setting.htm" />
-			<topic label="Contributing new retargetable actions" href="guide/wrkAdv_retarget_contribute.htm" >
-				<topic label="Retargetable editor actions" href="guide/wrkAdv_retarget_contribute_editors.htm" />
-				<topic label="Retargetable action set actions" href="guide/wrkAdv_retarget_contribute_actionsets.htm" />
-			</topic>
-		</topic>
-		<topic label="Undoable operations" href="guide/wrkAdv_undo.htm" />
-		<topic label="Perspectives" href="guide/workbench_perspectives.htm" >
-			<topic label="org.eclipse.ui.perspectives" href="guide/workbench_advext_perspectives.htm" />
-			<topic label="org.eclipse.ui.perspectiveExtensions" href="guide/workbench_advext_perspectiveExtension.htm" />
-		</topic>
-		<topic label="Decorators" href="guide/workbench_advext_decorators.htm" />
-		<topic label="Workbench key bindings" href="guide/wrkAdv_keyBindings.htm" >
-			<topic label="Commands" href="guide/wrkAdv_keyBindings_actionDef.htm" />
-			<topic label="Bindings" href="guide/wrkAdv_keyBindings_accelSet.htm" />
-			<topic label="Schemes" href="guide/wrkAdv_keyBindings_accelConfig.htm" />
-			<topic label="Contexts and key bindings" href="guide/wrkAdv_keyBindings_contexts.htm" />
-		</topic>
-		<topic label="Element factories" href="guide/workbench_advext_elementFactories.htm" />
-		<topic label="Accessible user interfaces" href="guide/wrkAdv_accessibility.htm" />
-		<topic label="Honoring single click support" href="guide/wrkAdv_singleclick.htm" />
-		<topic label="Working sets" href="guide/wrkAdv_workingsets.htm" />
-		<topic label="Filtering large user interfaces" href="guide/workbench_scalability.htm" >
-			<topic label="Activities" href="guide/workbench_advext_activities.htm" />
-			<topic label="Contexts" href="guide/workbench_advext_contexts.htm" />
-		</topic>
-		<topic label="Workbench concurrency support" href="guide/workbench_jobs.htm" />
-		<topic label="Workbench resource support" href="guide/workbench_resources.htm" >
-			<topic label="Contributing a property page" href="guide/preferences_prop_contribute.htm" />
-			<topic label="Implementing a property page" href="guide/preferences_prop_implement.htm" />
-			<topic label="Marker help and resolution" href="guide/wrkAdv_markers.htm" >
-				<topic label="Contributing marker help" href="guide/wrkAdv_markerhelp.htm" />
-				<topic label="Contributing marker resolution" href="guide/wrkAdv_markerresolution.htm" />
-			</topic>
-			<topic label="Contributing resource filters" href="guide/workbench_advext_resourceFilters.htm" />
-			<topic label="Text file encoding" href="guide/wrkAdv_encoding.htm" />	
-		</topic>
-	</topic>
-	
-	<topic label="Editors" href="guide/editors.htm">
-		<topic label="Workbench editors" href="guide/editors_workbench.htm" />
-		<topic label="Text editors and platform text" href="guide/editors_jface.htm" />
-		<topic label="Documents and partitions" href="guide/editors_documents.htm" />
-		<topic label="Source viewers and annotations" href="guide/editors_annotations.htm" />
-		<topic label="Configuring a source viewer" href="guide/editors_sourceviewers.htm" />
-		<topic label="Text and ruler hover" href="guide/editors_hover.htm" />
-		<topic label="Syntax coloring" href="guide/editors_highlighting.htm" />
-		<topic label="Content assist" href="guide/editors_contentassist.htm" />
-		<topic label="Registering editor actions" href="guide/editors_actions.htm" />
-		<topic label="Other text editor responsibilities" href="guide/editors_utilities.htm" />
-		<topic label="Content outliners" href="guide/editors_workbench_outliner.htm" />
-	</topic>
-	
-	<topic label="Search support" href="guide/search.htm">
-		<topic label="Contributing a search page" href="guide/search_page.htm" />
-		<topic label="Contributing a search result page" href="guide/search_result.htm" />
-	</topic>
-	
-	<topic label="Compare support" href="guide/compare.htm">
-		<topic label="Merging multiple streams" href="guide/compare_streammerger.htm" />
-		<topic label="Implementing a content viewer" href="guide/compare_contentviewer.htm" />
-		<topic label="Implementing a structure viewer" href="guide/compare_structureviewer.htm" />
-		<topic label="Advanced compare techniques" href="guide/compare_beyond.htm" />
-	</topic>
-	
-	<topic label="Team support" href="guide/team.htm">
-		<topic label="Repository providers" href="guide/team_provider_repository.htm" />
-		<topic label="Resource management" href="guide/team_resources.htm" />
-		<topic label="Synchronization Support" href="guide/team_synchronize.htm" >
-			<topic label="Local History Synchronization Example" href="guide/team_synchronize_localhistory_example.htm" />
-			<topic label="Beyond the basics" href="guide/team_synchronize_beyond_basics.htm" />
-		</topic>
-		<topic label="Rich Team Integration" href="guide/team_howto.htm" >
-			<topic label="Adding team actions" href="guide/team_ui_actions.htm" />
-			<topic label="Team decorators" href="guide/team_ui_decorators.htm" />
-			<topic label="Adding preferences and properties" href="guide/team_ui_prefs.htm" />
-		</topic>
-	</topic>
-	
-	<topic label="Program debug and launch support" href="guide/debug.htm">
-		<topic label="Launching a program" href="guide/debug_launch.htm" >
-			<topic label="Adding launchers to the platform" href="guide/debug_launch_adding.htm" >
-				<topic label="Obtaining a program's source code" href="guide/debug_launch_sourcelocators.htm" />
-				<topic label="Comparing launch configurations" href="guide/debug_launch_comparators.htm" />
-				<topic label="Process factories" href="guide/debug_launch_processfactories.htm" />
-				<topic label="Launching Java applications" href="guide/debug_launch_java.htm" />		
-			</topic>
-			<topic label="Handling errors from a launched program" href="guide/debug_launch_status.htm" />		
-			<topic label="Launch configuration dialog" href="guide/debug_launch_ui.htm" />
-			<topic label="Launch configuration type images" href="guide/debug_launch_uiimages.htm" />
-			<topic label="Launch shortcuts" href="guide/debug_launch_uishortcuts.htm" />
-		</topic>
-		<topic label="Debugging a program" href="guide/debug_debug.htm" >
-			<topic label="Platform debug model" href="guide/debug_model.htm" />
-			<topic label="Breakpoints" href="guide/debug_breakpoints.htm" />
-			<topic label="Expressions" href="guide/debug_expressions.htm" />
-			<topic label="Debug model presentation" href="guide/debug_presentation.htm" />
-			<topic label="Debug UI utility classes" href="guide/debug_ui.htm" />
-		</topic>
-	</topic>
-	
-	<topic label="Platform Ant support" href="guide/ant.htm">
-		<topic label="Running Ant buildfiles programmatically" href="guide/ant_running_buildfiles_programmatically.htm" />
-		<topic label="Ant tasks provided by the platform" href="guide/ant_eclipse_tasks.htm" />
-		<topic label="Contributing tasks and types" href="guide/ant_contributing_task.htm" />
-		<topic label="Developing Ant tasks and types within Eclipse" href="guide/ant_developing.htm" />
-		<topic label="Expanding the Ant classpath" href="guide/ant_expanding_classpath.htm" />
-	</topic>
-	
-	<topic label="User Assistance support" href="guide/ua.htm">
-		<topic label="Welcome" href="guide/ua_intro.htm" >
-			<topic label="Defining an intro part" href="guide/ua_intro_defining.htm" />
-			<topic label="Contributing a HelloWorld Intro Part" href="guide/ua_intro_hello_world.htm" />
-			<topic label="Using the CustomizableIntroPart" href="guide/ua_intro_cust_intro_part.htm" >
-				<topic label="Defining an intro config" href="guide/ua_intro_defining_config.htm" />
-				<topic label="Defining intro content" href="guide/ua_intro_define_content.htm" />
-				<topic label="Using XHTML as intro content" href="guide/ua_intro_xhtml.htm" />
-				<topic label="Displaying static HTML content in the CustomizableIntroPart" href="guide/ua_intro_cust_static.htm" />
-				<topic label="Extending an intro config" href="guide/ua_intro_extending.htm" >
-					<topic label="Extending the content of an intro config" href="guide/ua_intro_extending_content.htm" />
-					<topic label="Contributing a standby content part" href="guide/ua_intro_ext_standbypart.htm" />
-					<topic label="Defining a custom IntroURL action" href="guide/ua_intro_ext_custom_url.htm" />
-				</topic>
-			</topic>
-		</topic>
-		<topic label="Help" href="guide/ua_help.htm">
-			<topic label="Help content" href="guide/ua_help_content.htm" >
-				<topic label="Table of contents (toc) files" href="guide/ua_help_content_toc.htm" />
-				<topic label="Help server and file locations" href="guide/ua_help_content_files.htm" />
-				<topic label="Completing the plug-in manifest" href="guide/ua_help_content_manifest.htm" />
-				<topic label="Building nested documentation structures" href="guide/ua_help_content_nested.htm" />
-				<topic label="Contributing XHTML help documents" href="guide/ua_help_content_xhtml.htm" />
-				<topic label="Active help" href="guide/ua_help_content_active.htm" >
-					<topic label="Writing the help action" href="guide/ua_help_content_active_action.htm" />
-					<topic label="Invoking the action from HTML" href="guide/ua_help_content_active_invoke.htm" />
-					<topic label="Tips for debugging active help" href="guide/ua_help_content_active_debug.htm" />
-				</topic>
-				<topic label="Embedding commands in help" href="guide/ua_help_content_command.htm" >
-					<topic label="Authoring a command link" href="guide/ua_help_content_command_authoring.htm" />
-				</topic>
-			</topic>
-			<topic label="Context-sensitive help" href="guide/ua_help_context.htm" >
-				<topic label="Declaring a context id" href="guide/ua_help_context_id.htm" />
-				<topic label="Describing and packaging context-sensitive help" href="guide/ua_help_context_xml.htm" />
-				<topic label="Creating contexts dynamically" href="guide/ua_help_context_dynamic.htm"/>
-				<topic label="Infopops" href="guide/ua_help_context_infopops.htm"/>
-			</topic>
-			<topic label="Federated information search" href="guide/ua_help_search.htm">
-			   <topic label="Plugging in new engine types" href="guide/ua_help_search_types.htm"/>		
-			</topic>
-		</topic>
-		<topic label="Cheat sheets" href="guide/ua_cheatsheet.htm" >
-			<topic label="Simple cheat sheets" href="guide/ua_cheatsheet_simple.htm" />
-			<topic label="Composite cheat sheets" href="guide/ua_cheatsheet_composite.htm">		    
-			    <topic label="Composite cheatsheet content file definition" href="guide/ua_cheatsheet_composite_content.htm" />
-			</topic>
-		</topic>
-		<topic label="Dynamic content" href="guide/ua_dynamic.htm">
-			<topic label="Filters" href="guide/ua_dynamic_filters.htm" />
-			<topic label="Includes" href="guide/ua_dynamic_includes.htm" />
-			<topic label="Anchors" href="guide/ua_dynamic_anchors.htm" />
-		</topic>
-	</topic>
-
-	<topic label="Packaging and delivering Eclipse based products" href="guide/product.htm">
-		<topic label="Defining a Product" href="guide/product_def.htm" >
-			<topic label="The products extension point" href="guide/product_def_extpt.htm" />
-			<topic label="Customizing a product" href="guide/product_configproduct.htm" />
-			<topic label="Products as primary features" href="guide/product_def_primary.htm" />
-			<topic label="Customizing a primary feature" href="guide/product_configfeature.htm" />
-		</topic>
-		<topic label="Features" href="guide/product_def_feature.htm" />
-		<topic label="Plug-ins and fragments" href="guide/product_def_plugins.htm" />
-		<topic label="Locale specific files" href="guide/product_def_nl.htm" />
-		<topic label="Product installation guidelines" href="guide/product_config_install.htm" />
-		<topic label="Product extensions" href="guide/product_extension.htm" />
-		<topic label="Updating a product or extension" href="guide/product_update.htm" />
-		<topic label="Deploying eclipse based application with Java Web Start" href="guide/java_web_start.htm"/>
-	</topic>
-	
-	<topic label="Building a Rich Client Platform application" href="guide/rcp.htm">
-		<topic label="The browser example" href="guide/rcp_browser.htm" />
-		<topic label="Defining a rich client application" href="guide/rcp_define.htm" />
-		<topic label="Customizing the workbench" href="guide/rcp_advisor.htm" />
-		<topic label="Making UI contributions" href="guide/rcp_extensions.htm" >
-			<topic label="Adding the perspective" href="guide/rcp_perspective.htm" />
-			<topic label="Adding views" href="guide/rcp_view.htm" />
-			<topic label="Defining the actions" href="guide/rcp_actions.htm" />
-		</topic>
-	</topic>			
-	
-
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/topics_Porting.xml b/bundles/org.eclipse.platform.doc.isv/topics_Porting.xml
deleted file mode 100644
index 5637c2f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/topics_Porting.xml
+++ /dev/null

@@ -1,28 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define topics for the porting guide index                                     -->
-<!-- ============================================================================= -->
-<toc label="Migration">
-	<topic label="Migrating to Eclipse 3.2 from 3.1">
-		<topic label="Introduction"
-		       href="porting/eclipse_3_2_porting_guide.html"/>
-		<topic label="FAQ" href="porting/3.2/faq.html" />
-		<topic label="Incompatibilities" href="porting/3.2/incompatibilities.html" />
-		<topic label="Adopting 3.2 Mechanisms and API" href="porting/3.2/recommended.html" />
-	</topic>
-	<topic label="Migrating to Eclipse 3.1 from 3.0">
-		<topic label="Introduction"
-		       href="porting/eclipse_3_1_porting_guide.html"/>
-		<topic label="FAQ" href="porting/3.1/faq.html" />
-		<topic label="Incompatibilities" href="porting/3.1/incompatibilities.html" />
-		<topic label="Adopting 3.1 Mechanisms and API" href="porting/3.1/recommended.html" />
-	</topic>
-	<topic label="Migrating to Eclipse 3.0 from 2.1">
-		<topic label="Introduction"
-		       href="porting/eclipse_3_0_porting_guide.html"/>
-		<topic label="FAQ" href="porting/3.0/faq.html" />
-		<topic label="Incompatibilities" href="porting/3.0/incompatibilities.html" />
-		<topic label="Adopting 3.0 Mechanisms and API" href="porting/3.0/recommended.html" />
-	</topic>
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/topics_Questions.xml b/bundles/org.eclipse.platform.doc.isv/topics_Questions.xml
deleted file mode 100644
index ad5a504..0000000
--- a/bundles/org.eclipse.platform.doc.isv/topics_Questions.xml
+++ /dev/null

@@ -1,7 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define topics for the questions index                                         -->
-<!-- ============================================================================= -->
-<toc label="Questions">
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/topics_Reference.xml b/bundles/org.eclipse.platform.doc.isv/topics_Reference.xml
deleted file mode 100644
index e138399..0000000
--- a/bundles/org.eclipse.platform.doc.isv/topics_Reference.xml
+++ /dev/null

@@ -1,358 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define topics for the references                                              -->
-<!-- ============================================================================= -->
-<toc label="Reference">
-
-	<topic label="API Reference" href="reference/api/overview-summary.html">
-      <topic label="org.eclipse.ant.core" href="reference/api/org/eclipse/ant/core/package-summary.html"/>
-      <topic label="org.eclipse.compare" href="reference/api/org/eclipse/compare/package-summary.html"/>
-      <topic label="org.eclipse.compare.contentmergeviewer" href="reference/api/org/eclipse/compare/contentmergeviewer/package-summary.html"/>
-      <topic label="org.eclipse.compare.rangedifferencer" href="reference/api/org/eclipse/compare/rangedifferencer/package-summary.html"/>
-      <topic label="org.eclipse.compare.structuremergeviewer" href="reference/api/org/eclipse/compare/structuremergeviewer/package-summary.html"/>
-      <topic label="org.eclipse.core.commands" href="reference/api/org/eclipse/core/commands/package-summary.html"/>
-      <topic label="org.eclipse.core.commands.common" href="reference/api/org/eclipse/core/commands/common/package-summary.html"/>
-      <topic label="org.eclipse.core.commands.contexts" href="reference/api/org/eclipse/core/commands/contexts/package-summary.html"/>
-      <topic label="org.eclipse.core.commands.operations" href="reference/api/org/eclipse/core/commands/operations/package-summary.html"/>
-      <topic label="org.eclipse.core.expressions" href="reference/api/org/eclipse/core/expressions/package-summary.html"/>
-      <topic label="org.eclipse.core.filebuffers" href="reference/api/org/eclipse/core/filebuffers/package-summary.html"/>
-      <topic label="org.eclipse.core.filebuffers.manipulation" href="reference/api/org/eclipse/core/filebuffers/manipulation/package-summary.html"/>
-      <topic label="org.eclipse.core.filesystem" href="reference/api/org/eclipse/core/filesystem/package-summary.html"/>
-      <topic label="org.eclipse.core.filesystem.provider" href="reference/api/org/eclipse/core/filesystem/provider/package-summary.html"/>
-      <topic label="org.eclipse.core.launcher" href="reference/api/org/eclipse/core/launcher/package-summary.html"/>
-      <topic label="org.eclipse.core.resources" href="reference/api/org/eclipse/core/resources/package-summary.html"/>
-      <topic label="org.eclipse.core.resources.refresh" href="reference/api/org/eclipse/core/resources/refresh/package-summary.html"/>
-      <topic label="org.eclipse.core.resources.team" href="reference/api/org/eclipse/core/resources/team/package-summary.html"/>
-      <topic label="org.eclipse.core.runtime" href="reference/api/org/eclipse/core/runtime/package-summary.html"/>
-      <topic label="org.eclipse.core.runtime.adaptor" href="reference/api/org/eclipse/core/runtime/adaptor/package-summary.html"/>
-      <topic label="org.eclipse.core.runtime.content" href="reference/api/org/eclipse/core/runtime/content/package-summary.html"/>
-	  <topic label="org.eclipse.core.runtime.dynamichelpers" href="reference/api/org/eclipse/core/runtime/dynamichelpers/package-summary.html"/>
-      <topic label="org.eclipse.core.runtime.jobs" href="reference/api/org/eclipse/core/runtime/jobs/package-summary.html"/>
-      <topic label="org.eclipse.core.runtime.model" href="reference/api/org/eclipse/core/runtime/model/package-summary.html"/>
-      <topic label="org.eclipse.core.runtime.preferences" href="reference/api/org/eclipse/core/runtime/preferences/package-summary.html"/>
-      <topic label="org.eclipse.core.variables" href="reference/api/org/eclipse/core/variables/package-summary.html"/>
-      <topic label="org.eclipse.debug.core" href="reference/api/org/eclipse/debug/core/package-summary.html"/>
-      <topic label="org.eclipse.debug.core.model" href="reference/api/org/eclipse/debug/core/model/package-summary.html"/>
-      <topic label="org.eclipse.debug.core.sourcelookup" href="reference/api/org/eclipse/debug/core/sourcelookup/package-summary.html"/>
-      <topic label="org.eclipse.debug.core.sourcelookup.containers" href="reference/api/org/eclipse/debug/core/sourcelookup/containers/package-summary.html"/>
-      <topic label="org.eclipse.debug.ui" href="reference/api/org/eclipse/debug/ui/package-summary.html"/>
-      <topic label="org.eclipse.debug.ui.actions" href="reference/api/org/eclipse/debug/ui/actions/package-summary.html"/>
-      <topic label="org.eclipse.debug.ui.console" href="reference/api/org/eclipse/debug/ui/console/package-summary.html"/>
-      <topic label="org.eclipse.debug.ui.memory" href="reference/api/org/eclipse/debug/ui/memory/package-summary.html"/>
-      <topic label="org.eclipse.debug.ui.sourcelookup" href="reference/api/org/eclipse/debug/ui/sourcelookup/package-summary.html"/>
-      <topic label="org.eclipse.help" href="reference/api/org/eclipse/help/package-summary.html"/>
-      <topic label="org.eclipse.help.browser" href="reference/api/org/eclipse/help/browser/package-summary.html"/>
-      <topic label="org.eclipse.help.ui.browser" href="reference/api/org/eclipse/help/ui/browser/package-summary.html"/>
-      <topic label="org.eclipse.jface.action" href="reference/api/org/eclipse/jface/action/package-summary.html"/>
-      <topic label="org.eclipse.jface.bindings" href="reference/api/org/eclipse/jface/bindings/package-summary.html"/>
-      <topic label="org.eclipse.jface.bindings.keys" href="reference/api/org/eclipse/jface/bindings/keys/package-summary.html"/>
-      <topic label="org.eclipse.jface.bindings.keys.formatting" href="reference/api/org/eclipse/jface/bindings/keys/formatting/package-summary.html"/>
-      <topic label="org.eclipse.jface.commands" href="reference/api/org/eclipse/jface/commands/package-summary.html"/>
-      <topic label="org.eclipse.jface.contentassist" href="reference/api/org/eclipse/jface/contentassist/package-summary.html"/>
-      <topic label="org.eclipse.jface.contexts" href="reference/api/org/eclipse/jface/contexts/package-summary.html"/>
-      <topic label="org.eclipse.jface.dialogs" href="reference/api/org/eclipse/jface/dialogs/package-summary.html"/>
-      <topic label="org.eclipse.jface.operation" href="reference/api/org/eclipse/jface/operation/package-summary.html"/>
-      <topic label="org.eclipse.jface.preference" href="reference/api/org/eclipse/jface/preference/package-summary.html"/>
-      <topic label="org.eclipse.jface.resource" href="reference/api/org/eclipse/jface/resource/package-summary.html"/>
-      <topic label="org.eclipse.jface.text" href="reference/api/org/eclipse/jface/text/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.contentassist" href="reference/api/org/eclipse/jface/text/contentassist/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.formatter" href="reference/api/org/eclipse/jface/text/formatter/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.hyperlink" href="reference/api/org/eclipse/jface/text/hyperlink/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.information" href="reference/api/org/eclipse/jface/text/information/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.link" href="reference/api/org/eclipse/jface/text/link/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.presentation" href="reference/api/org/eclipse/jface/text/presentation/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.projection" href="reference/api/org/eclipse/jface/text/projection/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.quickassist" href="reference/api/org/eclipse/jface/text/quickassist/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.reconciler" href="reference/api/org/eclipse/jface/text/reconciler/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.revisions" href="reference/api/org/eclipse/jface/text/revisions/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.rules" href="reference/api/org/eclipse/jface/text/rules/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.source" href="reference/api/org/eclipse/jface/text/source/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.source.projection" href="reference/api/org/eclipse/jface/text/source/projection/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.templates" href="reference/api/org/eclipse/jface/text/templates/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.templates.persistence" href="reference/api/org/eclipse/jface/text/templates/persistence/package-summary.html"/>
-      <topic label="org.eclipse.jface.util" href="reference/api/org/eclipse/jface/util/package-summary.html"/>
-      <topic label="org.eclipse.jface.viewers" href="reference/api/org/eclipse/jface/viewers/package-summary.html"/>
-      <topic label="org.eclipse.jface.window" href="reference/api/org/eclipse/jface/window/package-summary.html"/>
-      <topic label="org.eclipse.jface.wizard" href="reference/api/org/eclipse/jface/wizard/package-summary.html"/>
-      <topic label="org.eclipse.ltk.core.refactoring" href="reference/api/org/eclipse/ltk/core/refactoring/package-summary.html"/>
-      <topic label="org.eclipse.ltk.core.refactoring.participants" href="reference/api/org/eclipse/ltk/core/refactoring/participants/package-summary.html"/>
-      <topic label="org.eclipse.ltk.ui.refactoring" href="reference/api/org/eclipse/ltk/ui/refactoring/package-summary.html"/>
-      <topic label="org.eclipse.osgi.service.datalocation" href="reference/api/org/eclipse/osgi/service/datalocation/package-summary.html"/>
-      <topic label="org.eclipse.osgi.util" href="reference/api/org/eclipse/osgi/util/package-summary.html"/>
-      <topic label="org.eclipse.search.ui" href="reference/api/org/eclipse/search/core/text/package-summary.html"/>
-      <topic label="org.eclipse.search.ui" href="reference/api/org/eclipse/search/ui/package-summary.html"/>
-      <topic label="org.eclipse.search.ui" href="reference/api/org/eclipse/search/ui/actions/package-summary.html"/>
-      <topic label="org.eclipse.search.ui.text" href="reference/api/org/eclipse/search/ui/text/package-summary.html"/>
-      <topic label="org.eclipse.swt" href="reference/api/org/eclipse/swt/package-summary.html"/>
-      <topic label="org.eclipse.swt.accessibility" href="reference/api/org/eclipse/swt/accessibility/package-summary.html"/>
-      <topic label="org.eclipse.swt.awt" href="reference/api/org/eclipse/swt/awt/package-summary.html"/>
-      <topic label="org.eclipse.swt.browser" href="reference/api/org/eclipse/swt/browser/package-summary.html"/>
-      <topic label="org.eclipse.swt.custom" href="reference/api/org/eclipse/swt/custom/package-summary.html"/>
-      <topic label="org.eclipse.swt.dnd" href="reference/api/org/eclipse/swt/dnd/package-summary.html"/>
-      <topic label="org.eclipse.swt.events" href="reference/api/org/eclipse/swt/events/package-summary.html"/>
-      <topic label="org.eclipse.swt.graphics" href="reference/api/org/eclipse/swt/graphics/package-summary.html"/>
-      <topic label="org.eclipse.swt.layout" href="reference/api/org/eclipse/swt/layout/package-summary.html"/>
-      <topic label="org.eclipse.swt.ole.win32" href="reference/api/org/eclipse/swt/ole/win32/package-summary.html"/>
-      <topic label="org.eclipse.swt.opengl" href="reference/api/org/eclipse/swt/opengl/package-summary.html"/>
-      <topic label="org.eclipse.swt.printing" href="reference/api/org/eclipse/swt/printing/package-summary.html"/>
-      <topic label="org.eclipse.swt.program" href="reference/api/org/eclipse/swt/program/package-summary.html"/>
-      <topic label="org.eclipse.swt.widgets" href="reference/api/org/eclipse/swt/widgets/package-summary.html"/>
-      <topic label="org.eclipse.team.core" href="reference/api/org/eclipse/team/core/package-summary.html"/>
-      <topic label="org.eclipse.team.core.subscribers" href="reference/api/org/eclipse/team/core/subscribers/package-summary.html"/>
-      <topic label="org.eclipse.team.core.synchronize" href="reference/api/org/eclipse/team/core/synchronize/package-summary.html"/>
-      <topic label="org.eclipse.team.core.variants" href="reference/api/org/eclipse/team/core/variants/package-summary.html"/>
-      <topic label="org.eclipse.team.ui" href="reference/api/org/eclipse/team/ui/package-summary.html"/>
-      <topic label="org.eclipse.team.ui.synchronize" href="reference/api/org/eclipse/team/ui/synchronize/package-summary.html"/>
-      <topic label="org.eclipse.text.edits" href="reference/api/org/eclipse/text/edits/package-summary.html"/>
-      <topic label="org.eclipse.text.undo" href="reference/api/org/eclipse/text/undo/package-summary.html"/>
-      <topic label="org.eclipse.ui" href="reference/api/org/eclipse/ui/package-summary.html"/>
-      <topic label="org.eclipse.ui.about" href="reference/api/org/eclipse/ui/about/package-summary.html"/>
-      <topic label="org.eclipse.ui.actions" href="reference/api/org/eclipse/ui/actions/package-summary.html"/>
-      <topic label="org.eclipse.ui.activities" href="reference/api/org/eclipse/ui/activities/package-summary.html"/>
-      <topic label="org.eclipse.ui.application" href="reference/api/org/eclipse/ui/application/package-summary.html"/>
-      <topic label="org.eclipse.ui.branding" href="reference/api/org/eclipse/ui/branding/package-summary.html"/>
-      <topic label="org.eclipse.ui.browser" href="reference/api/org/eclipse/ui/browser/package-summary.html"/>
-      <topic label="org.eclipse.ui.cheatsheets" href="reference/api/org/eclipse/ui/cheatsheets/package-summary.html"/>
-      <topic label="org.eclipse.ui.commands" href="reference/api/org/eclipse/ui/commands/package-summary.html"/>
-      <topic label="org.eclipse.ui.console" href="reference/api/org/eclipse/ui/console/package-summary.html"/>
-      <topic label="org.eclipse.ui.console.actions" href="reference/api/org/eclipse/ui/console/actions/package-summary.html"/>
-      <topic label="org.eclipse.ui.contentassist" href="reference/api/org/eclipse/ui/contentassist/package-summary.html"/>
-      <topic label="org.eclipse.ui.contexts" href="reference/api/org/eclipse/ui/contexts/package-summary.html"/>
-      <topic label="org.eclipse.ui.dialogs" href="reference/api/org/eclipse/ui/dialogs/package-summary.html"/>
-      <topic label="org.eclipse.ui.editors.text" href="reference/api/org/eclipse/ui/editors/text/package-summary.html"/>
-      <topic label="org.eclipse.ui.editors.text.templates" href="reference/api/org/eclipse/ui/editors/text/templates/package-summary.html"/>
-      <topic label="org.eclipse.ui.fieldassist" href="reference/api/org/eclipse/ui/fieldassist/package-summary.html"/>
-      <topic label="org.eclipse.ui.forms" href="reference/api/org/eclipse/ui/forms/package-summary.html"/>
-      <topic label="org.eclipse.ui.forms.editor" href="reference/api/org/eclipse/ui/forms/editor/package-summary.html"/>
-      <topic label="org.eclipse.ui.forms.events" href="reference/api/org/eclipse/ui/forms/events/package-summary.html"/>
-      <topic label="org.eclipse.ui.forms.widgets" href="reference/api/org/eclipse/ui/forms/widgets/package-summary.html"/>
-      <topic label="org.eclipse.ui.handlers" href="reference/api/org/eclipse/ui/handlers/package-summary.html"/>
-      <topic label="org.eclipse.ui.help" href="reference/api/org/eclipse/ui/help/package-summary.html"/>
-      <topic label="org.eclipse.ui.ide" href="reference/api/org/eclipse/ui/ide/package-summary.html"/>
-      <topic label="org.eclipse.ui.ide.dialogs" href="reference/api/org/eclipse/ui/ide/dialogs/package-summary.html"/>
-      <topic label="org.eclipse.ui.intro" href="reference/api/org/eclipse/ui/intro/package-summary.html"/>
-      <topic label="org.eclipse.ui.intro.config" href="reference/api/org/eclipse/ui/intro/config/package-summary.html"/>
-      <topic label="org.eclipse.ui.keys" href="reference/api/org/eclipse/ui/keys/package-summary.html"/>
-      <topic label="org.eclipse.ui.model" href="reference/api/org/eclipse/ui/model/package-summary.html"/>
-      <topic label="org.eclipse.ui.navigator" href="reference/api/org/eclipse/ui/navigator/package-summary.html"/>      
-	  <topic label="org.eclipse.ui.navigator.resources" href="reference/api/org/eclipse/ui/navigator/resources/package-summary.html"/>            
-      <topic label="org.eclipse.ui.operations" href="reference/api/org/eclipse/ui/operations/package-summary.html"/>
-      <topic label="org.eclipse.ui.part" href="reference/api/org/eclipse/ui/part/package-summary.html"/>
-      <topic label="org.eclipse.ui.plugin" href="reference/api/org/eclipse/ui/plugin/package-summary.html"/>
-      <topic label="org.eclipse.ui.preferences" href="reference/api/org/eclipse/ui/preferences/package-summary.html"/>
-      <topic label="org.eclipse.ui.presentations" href="reference/api/org/eclipse/ui/presentations/package-summary.html"/>
-      <topic label="org.eclipse.ui.progress" href="reference/api/org/eclipse/ui/progress/package-summary.html"/>
-      <topic label="org.eclipse.ui.services" href="reference/api/org/eclipse/ui/services/package-summary.html"/>
-      <topic label="org.eclipse.ui.testing" href="reference/api/org/eclipse/ui/testing/package-summary.html"/>
-      <topic label="org.eclipse.ui.themes" href="reference/api/org/eclipse/ui/themes/package-summary.html"/>
-      <topic label="org.eclipse.ui.texteditor" href="reference/api/org/eclipse/ui/texteditor/package-summary.html"/>
-      <topic label="org.eclipse.ui.texteditor.link" href="reference/api/org/eclipse/ui/texteditor/link/package-summary.html"/>
-      <topic label="org.eclipse.ui.texteditor.quickdiff" href="reference/api/org/eclipse/ui/texteditor/quickdiff/package-summary.html"/>
-      <topic label="org.eclipse.ui.texteditor.templates" href="reference/api/org/eclipse/ui/texteditor/templates/package-summary.html"/>
-      <topic label="org.eclipse.ui.texteditor.spelling" href="reference/api/org/eclipse/ui/texteditor/spelling/package-summary.html"/>
-      <topic label="org.eclipse.ui.views" href="reference/api/org/eclipse/ui/views/package-summary.html"/>
-      <topic label="org.eclipse.ui.views.bookmarkexplorer" href="reference/api/org/eclipse/ui/views/bookmarkexplorer/package-summary.html"/>
-      <topic label="org.eclipse.ui.views.contentoutline" href="reference/api/org/eclipse/ui/views/contentoutline/package-summary.html"/>
-      <topic label="org.eclipse.ui.views.framelist" href="reference/api/org/eclipse/ui/views/framelist/package-summary.html"/>
-      <topic label="org.eclipse.ui.views.markers" href="reference/api/org/eclipse/ui/views/markers/package-summary.html"/>
-      <topic label="org.eclipse.ui.views.navigator" href="reference/api/org/eclipse/ui/views/navigator/package-summary.html"/>
-      <topic label="org.eclipse.ui.views.properties" href="reference/api/org/eclipse/ui/views/properties/package-summary.html"/>
-      <topic label="org.eclipse.ui.views.properties.tabbed" href="reference/api/org/eclipse/ui/views/properties/tabbed/package-summary.html"/>
-      <topic label="org.eclipse.ui.views.tasklist" href="reference/api/org/eclipse/ui/views/tasklist/package-summary.html"/>
-      <topic label="org.eclipse.ui.wizards" href="reference/api/org/eclipse/ui/wizards/package-summary.html"/>
-      <topic label="org.eclipse.ui.wizards.datatransfer" href="reference/api/org/eclipse/ui/wizards/datatransfer/package-summary.html"/>
-      <topic label="org.eclipse.ui.wizards.newresource" href="reference/api/org/eclipse/ui/wizards/newresource/package-summary.html"/>
-      <topic label="org.eclipse.update.configurator" href="reference/api/org/eclipse/update/configurator/package-summary.html"/>
-      <topic label="org.eclipse.update.configuration" href="reference/api/org/eclipse/update/configuration/package-summary.html"/>
-      <topic label="org.eclipse.update.core" href="reference/api/org/eclipse/update/core/package-summary.html"/>
-      <topic label="org.eclipse.update.core.model" href="reference/api/org/eclipse/update/core/model/package-summary.html"/>
-      <topic label="org.eclipse.update.operations" href="reference/api/org/eclipse/update/operations/package-summary.html"/>
-      <topic label="org.eclipse.update.search" href="reference/api/org/eclipse/update/search/package-summary.html"/>
-      <topic label="org.eclipse.update.standalone" href="reference/api/org/eclipse/update/standalone/package-summary.html"/>
-    </topic>
-
-	<topic label="Extension Points Reference" href="reference/extension-points/index.html">
-       <topic label="org.eclipse.ant.core.antProperties" href="reference/extension-points/org_eclipse_ant_core_antProperties.html"/>
-       <topic label="org.eclipse.ant.core.antTasks" href="reference/extension-points/org_eclipse_ant_core_antTasks.html"/>
-       <topic label="org.eclipse.ant.core.antTypes" href="reference/extension-points/org_eclipse_ant_core_antTypes.html"/>
-       <topic label="org.eclipse.ant.core.extraClasspathEntries" href="reference/extension-points/org_eclipse_ant_core_extraClasspathEntries.html"/>
-       <topic label="org.eclipse.compare.contentMergeViewers" href="reference/extension-points/org_eclipse_compare_contentMergeViewers.html"/>
-       <topic label="org.eclipse.compare.contentViewers" href="reference/extension-points/org_eclipse_compare_contentViewers.html"/>
-       <topic label="org.eclipse.compare.streamMergers" href="reference/extension-points/org_eclipse_compare_streamMergers.html"/>
-       <topic label="org.eclipse.compare.structureCreators" href="reference/extension-points/org_eclipse_compare_structureCreators.html"/>
-       <topic label="org.eclipse.compare.structureMergeViewers" href="reference/extension-points/org_eclipse_compare_structureMergeViewers.html"/>
-       <topic label="org.eclipse.core.expressions.propertyTesters" href="reference/extension-points/org_eclipse_core_expressions_propertyTesters.html"/>
-       <topic label="org.eclipse.core.filebuffers.annotationModelCreation" href="reference/extension-points/org_eclipse_core_filebuffers_annotationModelCreation.html"/>
-       <topic label="org.eclipse.core.filebuffers.documentCreation" href="reference/extension-points/org_eclipse_core_filebuffers_documentCreation.html"/>
-       <topic label="org.eclipse.core.filebuffers.documentSetup" href="reference/extension-points/org_eclipse_core_filebuffers_documentSetup.html"/>
-       <topic label="org.eclipse.core.filesystem.filesystems" href="reference/extension-points/org_eclipse_core_filesystem_filesystems.html"/>
-       <topic label="org.eclipse.core.resources.builders" href="reference/extension-points/org_eclipse_core_resources_builders.html"/>
-       <topic label="org.eclipse.core.resources.fileModificationValidator" href="reference/extension-points/org_eclipse_core_resources_fileModificationValidator.html"/>
-       <topic label="org.eclipse.core.resources.markers" href="reference/extension-points/org_eclipse_core_resources_markers.html"/>
-       <topic label="org.eclipse.core.resources.moveDeleteHook" href="reference/extension-points/org_eclipse_core_resources_moveDeleteHook.html"/>
-       <topic label="org.eclipse.core.resources.natures" href="reference/extension-points/org_eclipse_core_resources_natures.html"/>
-       <topic label="org.eclipse.core.resources.refreshProviders" href="reference/extension-points/org_eclipse_core_resources_refreshProviders.html"/>
-       <topic label="org.eclipse.core.resources.teamHook" href="reference/extension-points/org_eclipse_core_resources_teamHook.html"/>
-       <topic label="org.eclipse.core.runtime.adapters" href="reference/extension-points/org_eclipse_core_runtime_adapters.html"/>
-       <topic label="org.eclipse.core.runtime.applications" href="reference/extension-points/org_eclipse_core_runtime_applications.html"/>
-       <topic label="org.eclipse.core.runtime.contentTypes" href="reference/extension-points/org_eclipse_core_runtime_contentTypes.html"/>
-       <topic label="org.eclipse.core.runtime.preferences" href="reference/extension-points/org_eclipse_core_runtime_preferences.html"/>
-       <topic label="org.eclipse.core.runtime.products" href="reference/extension-points/org_eclipse_core_runtime_products.html"/>
-       <topic label="org.eclipse.core.variables.dynamicVariables" href="reference/extension-points/org_eclipse_core_variables_dynamicVariables.html"/>
-       <topic label="org.eclipse.core.variables.valueVariables" href="reference/extension-points/org_eclipse_core_variables_valueVariables.html"/>
-       <topic label="org.eclipse.debug.core.breakpoints" href="reference/extension-points/org_eclipse_debug_core_breakpoints.html"/>
-       <topic label="org.eclipse.debug.core.launchConfigurationComparators" href="reference/extension-points/org_eclipse_debug_core_launchConfigurationComparators.html"/>
-       <topic label="org.eclipse.debug.core.launchConfigurationTypes" href="reference/extension-points/org_eclipse_debug_core_launchConfigurationTypes.html"/>
-       <topic label="org.eclipse.debug.core.launchDelegates" href="reference/extension-points/org_eclipse_debug_core_launchDelegates.html"/>
-       <topic label="org.eclipse.debug.core.launchers" href="reference/extension-points/org_eclipse_debug_core_launchers.html"/>
-       <topic label="org.eclipse.debug.core.launchModes" href="reference/extension-points/org_eclipse_debug_core_launchModes.html"/>
-       <topic label="org.eclipse.debug.core.logicalStructureTypes" href="reference/extension-points/org_eclipse_debug_core_logicalStructureTypes.html"/>
-       <topic label="org.eclipse.debug.core.processFactories" href="reference/extension-points/org_eclipse_debug_core_processFactories.html"/>
-       <topic label="org.eclipse.debug.core.sourceContainerTypes" href="reference/extension-points/org_eclipse_debug_core_sourceContainerTypes.html"/>
-       <topic label="org.eclipse.debug.core.sourceLocators" href="reference/extension-points/org_eclipse_debug_core_sourceLocators.html"/>
-       <topic label="org.eclipse.debug.core.sourcePathComputers" href="reference/extension-points/org_eclipse_debug_core_sourcePathComputers.html"/>
-       <topic label="org.eclipse.debug.core.statusHandlers" href="reference/extension-points/org_eclipse_debug_core_statusHandlers.html"/>
-       <topic label="org.eclipse.debug.core.watchExpressionDelegates" href="reference/extension-points/org_eclipse_debug_core_watchExpressionDelegates.html"/>
-       <topic label="org.eclipse.debug.ui.breakpointOrganizers" href="reference/extension-points/org_eclipse_debug_ui_breakpointOrganizers.html"/>
-       <topic label="org.eclipse.debug.ui.consoleColorProviders" href="reference/extension-points/org_eclipse_debug_ui_consoleColorProviders.html"/>
-       <topic label="org.eclipse.debug.ui.consoleLineTrackers" href="reference/extension-points/org_eclipse_debug_ui_consoleLineTrackers.html"/>
-       <topic label="org.eclipse.debug.ui.contextViewBindings" href="reference/extension-points/org_eclipse_debug_ui_contextViewBindings.html"/>
-       <topic label="org.eclipse.debug.ui.debugModelContextBindings" href="reference/extension-points/org_eclipse_debug_ui_debugModelContextBindings.html"/>
-       <topic label="org.eclipse.debug.ui.debugModelPresentations" href="reference/extension-points/org_eclipse_debug_ui_debugModelPresentations.html"/>
-       <topic label="org.eclipse.debug.ui.launchConfigurationTabGroups" href="reference/extension-points/org_eclipse_debug_ui_launchConfigurationTabGroups.html"/>
-       <topic label="org.eclipse.debug.ui.launchConfigurationTypeImages" href="reference/extension-points/org_eclipse_debug_ui_launchConfigurationTypeImages.html"/>
-       <topic label="org.eclipse.debug.ui.launchGroups" href="reference/extension-points/org_eclipse_debug_ui_launchGroups.html"/>
-       <topic label="org.eclipse.debug.ui.launchShortcuts" href="reference/extension-points/org_eclipse_debug_ui_launchShortcuts.html"/>
-       <topic label="org.eclipse.debug.ui.memoryRenderings" href="reference/extension-points/org_eclipse_debug_ui_memoryRenderings.html"/>
-       <topic label="org.eclipse.debug.ui.sourceContainerPresentations" href="reference/extension-points/org_eclipse_debug_ui_sourceContainerPresentations.html"/>
-       <topic label="org.eclipse.debug.ui.stringVariablePresentations" href="reference/extension-points/org_eclipse_debug_ui_stringVariablePresentations.html"/>
-       <topic label="org.eclipse.debug.ui.variableValueEditors" href="reference/extension-points/org_eclipse_debug_ui_variableValueEditors.html"/>
-       <topic label="org.eclipse.help.contentProducer" href="reference/extension-points/org_eclipse_help_contentProducer.html"/>
-       <topic label="org.eclipse.help.contexts" href="reference/extension-points/org_eclipse_help_contexts.html"/>
-       <topic label="org.eclipse.help.toc" href="reference/extension-points/org_eclipse_help_toc.html"/>
-       <topic label="org.eclipse.help.base.browser" href="reference/extension-points/org_eclipse_help_base_browser.html"/>
-       <topic label="org.eclipse.help.base.luceneAnalyzer" href="reference/extension-points/org_eclipse_help_base_luceneAnalyzer.html"/>
-       <topic label="org.eclipse.ltk.core.refactoring.copyParticipants" href="reference/extension-points/org_eclipse_ltk_core_refactoring_copyParticipants.html"/>
-       <topic label="org.eclipse.ltk.core.refactoring.createParticipants" href="reference/extension-points/org_eclipse_ltk_core_refactoring_createParticipants.html"/>
-       <topic label="org.eclipse.ltk.core.refactoring.deleteParticipants" href="reference/extension-points/org_eclipse_ltk_core_refactoring_deleteParticipants.html"/>
-       <topic label="org.eclipse.ltk.core.refactoring.moveParticipants" href="reference/extension-points/org_eclipse_ltk_core_refactoring_moveParticipants.html"/>
-       <topic label="org.eclipse.ltk.core.refactoring.renameParticipants" href="reference/extension-points/org_eclipse_ltk_core_refactoring_renameParticipants.html"/>
-       <topic label="org.eclipse.ltk.ui.refactoring.changePreviewViewers" href="reference/extension-points/org_eclipse_ltk_ui_refactoring_changePreviewViewers.html"/>
-       <topic label="org.eclipse.ltk.ui.refactoring.statusContextViewers" href="reference/extension-points/org_eclipse_ltk_ui_refactoring_statusContextViewers.html"/>
-       <topic label="org.eclipse.search.searchPages" href="reference/extension-points/org_eclipse_search_searchPages.html"/>
-       <topic label="org.eclipse.search.searchResultSorters" href="reference/extension-points/org_eclipse_search_searchResultSorters.html"/>
-       <topic label="org.eclipse.search.searchResultViewPages" href="reference/extension-points/org_eclipse_search_searchResultViewPages.html"/>
-       <topic label="org.eclipse.team.core.fileTypes" href="reference/extension-points/org_eclipse_team_core_fileTypes.html"/>
-       <topic label="org.eclipse.team.core.ignore" href="reference/extension-points/org_eclipse_team_core_ignore.html"/>
-       <topic label="org.eclipse.team.core.projectSets" href="reference/extension-points/org_eclipse_team_core_projectSets.html"/>
-       <topic label="org.eclipse.team.core.repository" href="reference/extension-points/org_eclipse_team_core_repository.html"/>
-       <topic label="org.eclipse.team.ui.configurationWizards" href="reference/extension-points/org_eclipse_team_ui_configurationWizards.html"/>
-       <topic label="org.eclipse.team.ui.synchronizeParticipants" href="reference/extension-points/org_eclipse_team_ui_synchronizeParticipants.html"/>
-       <topic label="org.eclipse.team.ui.synchronizeWizards" href="reference/extension-points/org_eclipse_team_ui_synchronizeWizards.html"/>
-       <topic label="org.eclipse.ui.acceleratorConfigurations" href="reference/extension-points/org_eclipse_ui_acceleratorConfigurations.html"/>
-       <topic label="org.eclipse.ui.acceleratorScopes" href="reference/extension-points/org_eclipse_ui_acceleratorScopes.html"/>
-       <topic label="org.eclipse.ui.acceleratorSets" href="reference/extension-points/org_eclipse_ui_acceleratorSets.html"/>
-       <topic label="org.eclipse.ui.actionDefinitions" href="reference/extension-points/org_eclipse_ui_actionDefinitions.html"/>
-       <topic label="org.eclipse.ui.actionSetPartAssociations" href="reference/extension-points/org_eclipse_ui_actionSetPartAssociations.html"/>
-       <topic label="org.eclipse.ui.actionSets" href="reference/extension-points/org_eclipse_ui_actionSets.html"/>
-       <topic label="org.eclipse.ui.activities" href="reference/extension-points/org_eclipse_ui_activities.html"/>
-	    <topic label="org.eclipse.ui.activitySupport" href="reference/extension-points/org_eclipse_ui_activitySupport.html"/>
-		 <topic label="org.eclipse.ui.bindings" href="reference/extension-points/org_eclipse_ui_bindings.html"/>
-		 <topic label="org.eclipse.ui.browserSupport" href="reference/extension-points/org_eclipse_ui_browserSupport.html"/>
-       <topic label="org.eclipse.ui.cheatsheets.cheatSheetContent" href="reference/extension-points/org_eclipse_ui_cheatsheets_cheatSheetContent.html"/>
-       <topic label="org.eclipse.ui.cheatsheets.cheatSheetItemExtension" href="reference/extension-points/org_eclipse_ui_cheatsheets_cheatSheetItemExtension.html"/>
-       <topic label="org.eclipse.ui.commands" href="reference/extension-points/org_eclipse_ui_commands.html"/>
-       <topic label="org.eclipse.ui.commandImages" href="reference/extension-points/org_eclipse_ui_commandImages.html"/>
-       <topic label="org.eclipse.ui.console.consoleFactories" href="reference/extension-points/org_eclipse_ui_console_consoleFactories.html"/>
-       <topic label="org.eclipse.ui.console.consolePageParticipants" href="reference/extension-points/org_eclipse_ui_console_consolePageParticipants.html"/>
-       <topic label="org.eclipse.ui.console.consolePatternMatchListeners" href="reference/extension-points/org_eclipse_ui_console_consolePatternMatchListeners.html"/>
-	    <topic label="org.eclipse.ui.contexts" href="reference/extension-points/org_eclipse_ui_contexts.html"/>
-       <topic label="org.eclipse.ui.decorators" href="reference/extension-points/org_eclipse_ui_decorators.html"/>
-       <topic label="org.eclipse.ui.dropActions" href="reference/extension-points/org_eclipse_ui_dropActions.html"/>
-       <topic label="org.eclipse.ui.editorActions" href="reference/extension-points/org_eclipse_ui_editorActions.html"/>
-       <topic label="org.eclipse.ui.editors" href="reference/extension-points/org_eclipse_ui_editors.html"/>
-       <topic label="org.eclipse.ui.editors.annotationTypes" href="reference/extension-points/org_eclipse_ui_editors_annotationTypes.html"/>
-       <topic label="org.eclipse.ui.editors.documentProviders" href="reference/extension-points/org_eclipse_ui_editors_documentProviders.html"/>
-       <topic label="org.eclipse.ui.editors.markerAnnotationSpecification" href="reference/extension-points/org_eclipse_ui_editors_markerAnnotationSpecification.html"/>
-       <topic label="org.eclipse.ui.editors.markerUpdaters" href="reference/extension-points/org_eclipse_ui_editors_markerUpdaters.html"/>
-       <topic label="org.eclipse.ui.editors.templates" href="reference/extension-points/org_eclipse_ui_editors_templates.html"/>
-       <topic label="org.eclipse.ui.elementFactories" href="reference/extension-points/org_eclipse_ui_elementFactories.html"/>
-	    <topic label="org.eclipse.ui.encodings" href="reference/extension-points/org_eclipse_ui_encodings.html"/>
-       <topic label="org.eclipse.ui.exportWizards" href="reference/extension-points/org_eclipse_ui_exportWizards.html"/>
-       <topic label="org.eclipse.ui.externaltools.configurationDuplicationMaps" href="reference/extension-points/org_eclipse_ui_externaltools_configurationDuplicationMaps.html"/>
-       <topic label="org.eclipse.ui.fontDefinitions" href="reference/extension-points/org_eclipse_ui_fontDefinitions.html"/>
-	    <topic label="org.eclipse.ui.handlers" href="reference/extension-points/org_eclipse_ui_handlers.html"/>
-       <topic label="org.eclipse.ui.helpSupport" href="reference/extension-points/org_eclipse_ui_helpSupport.html"/>
-       <topic label="org.eclipse.ui.ide.markerHelp" href="reference/extension-points/org_eclipse_ui_ide_markerHelp.html"/>
-       <topic label="org.eclipse.ui.ide.markerImageProviders" href="reference/extension-points/org_eclipse_ui_ide_markerImageProviders.html"/>
-       <topic label="org.eclipse.ui.ide.markerResolution" href="reference/extension-points/org_eclipse_ui_ide_markerResolution.html"/>
-        <topic label="org.eclipse.ui.ide.markerSupport" href="reference/extension-points/org_eclipse_ui_ide_markerSupport.html"/>
-       <topic label="org.eclipse.ui.ide.projectNatureImages" href="reference/extension-points/org_eclipse_ui_ide_projectNatureImages.html"/>
-       <topic label="org.eclipse.ui.ide.resourceFilters" href="reference/extension-points/org_eclipse_ui_ide_resourceFilters.html"/>
-       <topic label="org.eclipse.ui.importWizards" href="reference/extension-points/org_eclipse_ui_importWizards.html"/>
-       <topic label="org.eclipse.ui.intro" href="reference/extension-points/org_eclipse_ui_intro.html"/>
-       <topic label="org.eclipse.ui.intro.config" href="reference/extension-points/org_eclipse_ui_intro_config.html"/>
-       <topic label="org.eclipse.ui.intro.configExtension" href="reference/extension-points/org_eclipse_ui_intro_configExtension.html"/>
-	    <topic label="org.eclipse.ui.keywords" href="reference/extension-points/org_eclipse_ui_keywords.html"/>	    
-       <topic label="org.eclipse.ui.menus" href="reference/extension-points/org_eclipse_ui_menus.html"/>
-       <topic label="org.eclipse.ui.navigator.linkHelper" href="reference/extension-points/org_eclipse_ui_navigator_linkHelper.html"/>
-	   <topic label="org.eclipse.ui.navigator.navigatorContent" href="reference/extension-points/org_eclipse_ui_navigator_navigatorContent.html"/>
-	   <topic label="org.eclipse.ui.navigator.viewer" href="reference/extension-points/org_eclipse_ui_navigator_viewer.html"/>
-       <topic label="org.eclipse.ui.newWizards" href="reference/extension-points/org_eclipse_ui_newWizards.html"/>
-       <topic label="org.eclipse.ui.perspectiveExtensions" href="reference/extension-points/org_eclipse_ui_perspectiveExtensions.html"/>
-       <topic label="org.eclipse.ui.perspectives" href="reference/extension-points/org_eclipse_ui_perspectives.html"/>
-       <topic label="org.eclipse.ui.popupMenus" href="reference/extension-points/org_eclipse_ui_popupMenus.html"/>
-       <topic label="org.eclipse.ui.preferencePages" href="reference/extension-points/org_eclipse_ui_preferencePages.html"/>
-       <topic label="org.eclipse.ui.preferenceTransfer" href="reference/extension-points/org_eclipse_ui_preferenceTransfer.html"/>
-       <topic label="org.eclipse.ui.presentationFactories" href="reference/extension-points/org_eclipse_ui_presentationFactories.html"/>
-       <topic label="org.eclipse.ui.propertyPages" href="reference/extension-points/org_eclipse_ui_propertyPages.html"/>
-       <topic label="org.eclipse.ui.startup" href="reference/extension-points/org_eclipse_ui_startup.html"/>
-       <topic label="org.eclipse.ui.systemSummarySections" href="reference/extension-points/org_eclipse_ui_systemSummarySections.html"/>
-       <topic label="org.eclipse.ui.themes" href="reference/extension-points/org_eclipse_ui_themes.html"/>
-       <topic label="org.eclipse.ui.viewActions" href="reference/extension-points/org_eclipse_ui_viewActions.html"/>
-       <topic label="org.eclipse.ui.views" href="reference/extension-points/org_eclipse_ui_views.html"/>
-       <topic label="org.eclipse.ui.views.properties.tabbed.propertyContributor" href="reference/extension-points/org_eclipse_ui_views_properties_tabbed_propertyContributor.html"/>
-       <topic label="org.eclipse.ui.views.properties.tabbed.propertySections" href="reference/extension-points/org_eclipse_ui_views_properties_tabbed_propertySections.html"/>
-       <topic label="org.eclipse.ui.views.properties.tabbed.propertyTabs" href="reference/extension-points/org_eclipse_ui_views_properties_tabbed_propertyTabs.html"/>
-       <topic label="org.eclipse.ui.workbench.texteditor.quickDiffReferenceProvider" href="reference/extension-points/org_eclipse_ui_workbench_texteditor_quickDiffReferenceProvider.html"/>
-       <topic label="org.eclipse.ui.workbench.texteditor.spellingEngine" href="reference/extension-points/org_eclipse_ui_workbench_texteditor_spellingEngine.html"/>
-       <topic label="org.eclipse.ui.workingSets" href="reference/extension-points/org_eclipse_ui_workingSets.html"/>
-       <topic label="org.eclipse.update.core.featureTypes" href="reference/extension-points/org_eclipse_update_core_featureTypes.html"/>
-       <topic label="org.eclipse.update.core.installHandlers" href="reference/extension-points/org_eclipse_update_core_installHandlers.html"/>
-       <topic label="org.eclipse.update.core.siteTypes" href="reference/extension-points/org_eclipse_update_core_siteTypes.html"/>
-    </topic>
-
-	<topic label="OSGi API Reference" href="http://bundles.osgi.org/javadoc/r4"/>
-
-	<topic label="Other reference information" href="reference/misc/index.html">
-		<topic label ="Bidirectional Support" href="reference/misc/bidi.html"/>
-      	<topic label="Runtime options" href="reference/misc/runtime-options.html"/>
-      	<topic label="Eclipse Multi-user Installs" href="reference/misc/multi_user_installs.html"/>		
-      	<topic label="Starting Eclipse from Java" href="reference/misc/eclipsestarter.html"/>
-      	<topic label="API rules of engagement" href="reference/misc/api-usage-rules.html"/>
-      	<topic label="Naming Conventions" href="reference/misc/naming.html"/>
-      	<topic label="Glossary of Terms" href="reference/misc/terminology.html"/>
-      	<topic label="Map of Platform Plug-ins" href="reference/misc/overview-platform.html"/>
-      	<topic label="Plug-in Manifest " href="reference/misc/plugin_manifest.html"/>
-       	<topic label="OSGi Bundle Manifest" href="reference/misc/bundle_manifest.html"/>
-		<topic label="Preference Stores" href="reference/misc/preference_store.html"/>
-		<topic label="Message Bundles" href="reference/misc/message_bundles.html"/>
-     	<topic label="Project Description File" href="reference/misc/project_description_file.html"/>
-      	<topic label="Tips for making user interfaces accessible" href="reference/misc/ui_accessibility_tips.html"/>
-      	<topic label="Pre-built documentation index" href="reference/misc/help_product_index.html"/>
-      	<topic label="Installing the stand-alone help system" href="reference/misc/help_standalone.html"/>
-      	<topic label="Installing the help system as an infocenter" href="reference/misc/help_infocenter.html"/>
-      	<topic label="Help System Preferences" href="reference/misc/help_preferences.html"/>
-       	<topic label="How to write an Eclipse Installer" href="reference/misc/eclipse-install.html"/>
-       	<topic label="About.ini file format" href="reference/misc/about_customization.html"/>
-       	<topic label="Plug-in archives" href="reference/misc/plugin_archive.html"/>
-       	<topic label="Feature manifest" href="reference/misc/feature_manifest.html"/>
-       	<topic label="Feature archives" href="reference/misc/feature_archive.html"/>
-       	<topic label="Update server site map" href="reference/misc/update_sitemap.html"/>
-       	<topic label="Update policy control" href="reference/misc/update_policy.html"/>
-       	<topic label="The platform.xml file" href="reference/misc/update_platform_xml.html"/>
-       	<topic label="Running update manager from command line" href="reference/misc/update_standalone.html"/>
-       	<topic label="Third party libraries and classloading" href="reference/misc/buddy_loading.html"/>
-   	</topic>
-</toc>

diff --git a/bundles/org.eclipse.platform.doc.isv/topics_Samples.xml b/bundles/org.eclipse.platform.doc.isv/topics_Samples.xml
deleted file mode 100644
index 1ef0d91..0000000
--- a/bundles/org.eclipse.platform.doc.isv/topics_Samples.xml
+++ /dev/null

@@ -1,53 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define topics for the samples                                                 -->
-<!-- ============================================================================= -->
-<toc label="Examples" >
-   <topic label="Installing the examples" href="samples/samples.html" />
-   <topic label="Standard Widget Toolkit">
-      <topic label="Using the SWT example launcher" href="samples/org.eclipse.swt.examples.launcher/doc-html/swt_launcher_ex.html" />
-      <topic label="Running and browsing the SWT examples manually" href="samples/org.eclipse.swt.examples/doc-html/swt_manual_setup.html" />
-      <topic label="Stand-alone examples" >
-        <topic label="Address book" href="samples/org.eclipse.swt.examples/doc-html/swt_addressbook_ex.html" />
-        <topic label="Clipboard" href="samples/org.eclipse.swt.examples/doc-html/swt_clipboard_ex.html" />
-        <topic label="File viewer" href="samples/org.eclipse.swt.examples/doc-html/swt_fileviewer_ex.html"/>
-        <topic label="Hello world" href="samples/org.eclipse.swt.examples/doc-html/swt_helloworld_ex.html"/>
-        <topic label="Hover help" href="samples/org.eclipse.swt.examples/doc-html/swt_hoverhelp_ex.html"/>
-        <topic label="Image analyzer" href="samples/org.eclipse.swt.examples/doc-html/swt_imageanalyzer_ex.html"/>
-        <topic label="Java syntax viewer" href="samples/org.eclipse.swt.examples/doc-html/swt_javaviewer_ex.html"/>
-        <topic label="Text editor" href="samples/org.eclipse.swt.examples/doc-html/swt_texteditor_ex.html"/>
-      </topic>
-      <topic label="Workbench views" >
-        <topic label="Browser" href="samples/org.eclipse.swt.examples.browser/doc-html/swt_browser_ex.html"/>
-        <topic label="Controls" href="samples/org.eclipse.swt.examples.controls/doc-html/swt_controls_ex.html"/>
-        <topic label="Custom Controls" href="samples/org.eclipse.swt.examples.controls/doc-html/swt_customcontrols_ex.html"/>
-        <topic label="Layout" href="samples/org.eclipse.swt.examples.layouts/doc-html/swt_layout_ex.html"/>
-        <topic label="OLE" href="samples/org.eclipse.swt.examples.ole.win32/doc-html/swt_ole_ex.html" />
-        <topic label="Paint" href="samples/org.eclipse.swt.examples.paint/doc-html/swt_paint_ex.html"/>
-      </topic>
-   </topic>
-
-   <topic label="Workbench">
-      <topic label="Field assist example" href="samples/org.eclipse.ui.examples.fieldassist/doc-html/ui_fieldassist_ex.html" />
-      <topic label="Java editor" href="samples/org.eclipse.ui.examples.javaeditor/doc-html/ui_javaeditor_ex.html" />
-      <topic label="Template editor" href="samples/org.eclipse.ui.examples.javaeditor/doc-html/ui_templateeditor_ex.html" />
-      <topic label="Multi page editor" href="samples/org.eclipse.ui.examples.multipageeditor/doc-html/ui_multipageeditor_ex.html" />
-      <topic label="Property sheet" href="samples/org.eclipse.ui.examples.propertysheet/doc-html/ui_propertysheet_ex.html" />
-      <topic label="Readme tool" href="samples/org.eclipse.ui.examples.readmetool/doc-html/ui_readmetool_ex.html" />
-      <topic label="Undo example" href="samples/org.eclipse.ui.examples.undo/doc-html/ui_undo_ex.html" />
-   </topic>
-
-   <topic label="Help" href="samples/org.eclipse.help.examples.ex1/doc-html/help_ex.html" />
- 
-   <topic label="Team">
-      <topic label="Repository Providers" href="samples/org.eclipse.team.examples.filesystem/doc-html/team_filesystem_ex.html" />
-      <topic label="Synchronize Participants" href="samples/org.eclipse.team.examples.filesystem/doc-html/team_localhistory_ex.html" />
-   </topic>
-     
-   <topic label="Compare">
-   	  <topic label="Structured Compare" href="samples/org.eclipse.compare.examples/doc-html/ui_structurecreator_ex.html" />
-   	  <topic label="XML Compare" href="samples/org.eclipse.compare.examples.xml/doc-html/ui_xmlcompare_ex.html" />
-   </topic>
-   
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/workbench.png b/bundles/org.eclipse.platform.doc.isv/workbench.png
deleted file mode 100644
index c3f7d3f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/workbench.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/.project b/bundles/org.eclipse.platform.doc.user/.project
deleted file mode 100644
index 24f4a52..0000000
--- a/bundles/org.eclipse.platform.doc.user/.project
+++ /dev/null

@@ -1,17 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
-	<name>org.eclipse.platform.doc.user</name>
-	<comment></comment>
-	<projects>
-	</projects>
-	<buildSpec>
-		<buildCommand>
-			<name>org.eclipse.pde.ManifestBuilder</name>
-			<arguments>
-			</arguments>
-		</buildCommand>
-	</buildSpec>
-	<natures>
-		<nature>org.eclipse.pde.PluginNature</nature>
-	</natures>
-</projectDescription>

diff --git a/bundles/org.eclipse.platform.doc.user/.settings/org.eclipse.pde.prefs b/bundles/org.eclipse.platform.doc.user/.settings/org.eclipse.pde.prefs
deleted file mode 100644
index f7c96b7..0000000
--- a/bundles/org.eclipse.platform.doc.user/.settings/org.eclipse.pde.prefs
+++ /dev/null

@@ -1,12 +0,0 @@
-#Tue May 03 09:54:45 EDT 2005
-compilers.p.deprecated=1
-compilers.p.no-required-att=0
-compilers.p.not-externalized-att=1
-compilers.p.unknown-attribute=0
-compilers.p.unknown-class=0
-compilers.p.unknown-element=1
-compilers.p.unknown-resource=1
-compilers.p.unresolved-ex-points=0
-compilers.p.unresolved-import=0
-compilers.use-project=true
-eclipse.preferences.version=1

diff --git a/bundles/org.eclipse.platform.doc.user/META-INF/MANIFEST.MF b/bundles/org.eclipse.platform.doc.user/META-INF/MANIFEST.MF
deleted file mode 100644
index 8ce6269..0000000
--- a/bundles/org.eclipse.platform.doc.user/META-INF/MANIFEST.MF
+++ /dev/null

@@ -1,9 +0,0 @@
-Manifest-Version: 1.0
-Bundle-ManifestVersion: 2
-Bundle-Name: %pluginName
-Bundle-SymbolicName: org.eclipse.platform.doc.user; singleton:=true
-Bundle-Version: 3.2.0.qualifier
-Bundle-Vendor: %providerName
-Bundle-Localization: plugin
-Eclipse-LazyStart: true
-Require-Bundle: org.eclipse.help

diff --git a/bundles/org.eclipse.platform.doc.user/about.html b/bundles/org.eclipse.platform.doc.user/about.html
deleted file mode 100644
index 59d06ea..0000000
--- a/bundles/org.eclipse.platform.doc.user/about.html
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
-<title>About</title>
-</head>
-<body lang="EN-US">
-<h2>About This Content</h2>
- 
-<p>February 24, 2005</p>	
-<h3>License</h3>
-
-<p>The Eclipse Foundation makes available all content in this plug-in (&quot;Content&quot;).  Unless otherwise indicated below, the Content is provided to you under the terms and conditions of the
-Eclipse Public License Version 1.0 (&quot;EPL&quot;).  A copy of the EPL is available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
-For purposes of the EPL, &quot;Program&quot; will mean the Content.</p>
-
-<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is being redistributed by another party (&quot;Redistributor&quot;) and different terms and conditions may
-apply to your use of any object code in the Content.  Check the Redistributor's license that was provided with the Content.  If no such license exists, contact the Redistributor.  Unless otherwise
-indicated below, the terms and conditions of the EPL still apply to any source code in the Content.</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/book.css b/bundles/org.eclipse.platform.doc.user/book.css
deleted file mode 100644
index a4eedda..0000000
--- a/bundles/org.eclipse.platform.doc.user/book.css
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/build.properties b/bundles/org.eclipse.platform.doc.user/build.properties
deleted file mode 100644
index b862b18..0000000
--- a/bundles/org.eclipse.platform.doc.user/build.properties
+++ /dev/null

@@ -1,22 +0,0 @@
-###############################################################################
-# Copyright (c) 2000, 2004 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-# 
-# Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-customBuildCallbacks=customBuildCallbacks.xml
-
-
-bin.includes = META-INF/,\
-               plugin.properties,\
-               *.xml, *.zip,*.html,*.htm,*.png,book.css,index/,concepts/, gettingStarted/, images/,\
-               reference/, tasks/, tips/, whatsNew/
-               
-               
-bin.excludes = build.properties,\
-			   build.xml,\
-			   customBuildCallbacks.xml

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/accessibility/accessmain.htm b/bundles/org.eclipse.platform.doc.user/concepts/accessibility/accessmain.htm
deleted file mode 100644
index a96bf49..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/accessibility/accessmain.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<html>
-
- <head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<LINK REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css"> 
- <meta name="keyword" content="shortcut key, accelerator key, hot key, hotkey">
- <meta name="keyword" content="shortcut keys, accelerator keys, hot keys, hotkeys">
- <meta name="keyword" content="accessibility, disability, special needs">
- <meta name="keyword" content="accessible, disabilities, special need">
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
- <title>Accessibility features for Eclipse</title>
- <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
- <body>
-
- <h1>Accessibility features in Eclipse</h1>
- <p>
- Accessibility features help people with a physical disability, such as 
- restricted mobility or limited vision, or those with special needs to use 
- software products successfully. These are the major accessibility features in
- Eclipse:</p>
- <ul>
-   <li>Eclipse uses Microsoft Active 
-   Accessibility (MSAA) APIs to render user interface elements accessible to 
-   assistive technology.</li>
-   <li>You can operate all features using the keyboard instead of the mouse. See 
-   the related task. </li>
-   <li>You can use screen-reader software such as Freedom Scientific's JAWS <sup>TM</sup>
-    and a digital speech synthesizer to hear what is displayed on the 
-   screen. You can also use voice recognition software,
-   such as IBM ViaVoice <sup>TM</sup> to enter data and to navigate the user 
-   interface.</li>
-   <li>You can magnify what is displayed on your screen in the graphical views.
-   </li>
-   <li>Fonts and colors defined by Eclipse can be set using the
-   <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.ColorsAndFonts)")'>
-   <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-   <strong>General &gt; Appearance &gt; Colors and Fonts</strong></a>
-   preference page. See the related link.
-   </li>
- </ul>
- <p><strong>Note: </strong>The Accessibility features mentioned in 
- this document apply to the Windows operating system.
- </p>
- <p><img src="../../images/ngrelt.png" alt="Related tasks" border="0" ><a href="navigation.htm"><br>
- Navigating the user interface using the keyboard</a></p>
- <p><img src="../../images/ngrelr.png" alt="Related references" border="0" ><br>
- <a href="keyboardshortcuts.htm">Keys</a><br>
-  <a href="fontsandcolors.htm">Font and color settings in Eclipse</a></p>
-
- 
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/accessibility/colordialog.htm b/bundles/org.eclipse.platform.doc.user/concepts/accessibility/colordialog.htm
deleted file mode 100644
index cb6e4c6..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/accessibility/colordialog.htm
+++ /dev/null

@@ -1,535 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <LINK REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css"> 
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-  <title>Color Dialog Mappings Table</title>
-</head>
-
-<body>
-<h1>Windows Color Dialog Reference</h1>
-<p>Below are the tables that show the colors of the fonts in the matrix of the 
-  Windows color dialog and the color settings that each of these correspond to.</p>
-<h2>Windows Color Dialog Color Matrix</h2>
-<table border="1">
-  <col >
-  <col span=2 >
-  <col  span=5 >
-  <tr bordercolor="#000000" > 
-    <td > <div align="center">salmon</div></td>
-    <td> <div align="center">pale yellow</div></td>
-    <td > <div align="center">pale green</div></td>
-    <td > <div align="center">spring green</div></td>
-    <td> <div align="center">pale turquoise</div></td>
-    <td > <div align="center">deep sky blue</div></td>
-    <td> <div align="center">pale rose</div></td>
-    <td > <div align="center">pink</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="center">red</div></td>
-    <td > <div align="center">yellow</div></td>
-    <td > <div align="center">apple green</div></td>
-    <td > <div align="center">light green</div></td>
-    <td > <div align="center">aqua</div></td>
-    <td > <div align="center">turquoise</div></td>
-    <td > <div align="center">pale slate blue</div></td>
-    <td > <div align="center">magenta</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="center">chocolate</div></td>
-    <td > <div align="center">pumpkin</div></td>
-    <td > <div align="center">lime</div></td>
-    <td > <div align="center">teal</div></td>
-    <td > <div align="center">dark turquoise</div></td>
-    <td > <div align="center">medium slate blue</div></td>
-    <td > <div align="center">maroon</div></td>
-    <td > <div align="center">rose</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="center">dark red</div></td>
-    <td > <div align="center">dark orange</div></td>
-    <td > <div align="center">green</div></td>
-    <td > <div align="center">sea green</div></td>
-    <td > <div align="center">blue</div></td>
-    <td > <div align="center">medium blue</div></td>
-    <td > <div align="center">purple</div></td>
-    <td > <div align="center">blueviolet</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="center">dark brown</div></td>
-    <td > <div align="center">saddle brown</div></td>
-    <td > <div align="center">dark forest green</div></td>
-    <td > <div align="center">dark teal</div></td>
-    <td > <div align="center">navy </div></td>
-    <td > <div align="center">midnight blue</div></td>
-    <td > <div align="center">dark purple</div></td>
-    <td > <div align="center">dark blueviolet</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="center">black</div></td>
-    <td > <div align="center">olive</div></td>
-    <td > <div align="center">dark olive</div></td>
-    <td > <div align="center">grey</div></td>
-    <td > <div align="center">light teal</div></td>
-    <td > <div align="center">light grey</div></td>
-    <td > <div align="center">dark purple</div></td>
-    <td > <div align="center">white</div></td>
-  </tr>
-</table>
-<h2>Settings for Default Colors in the Windows Color Dialog</h2>
-<p></p>
-<table border="1">
-  <col >
-  <col span=2 >
-  <col  span=5 >
-  <tr bordercolor="#000000"  > 
-    <td width="95"  > <div align="left"><strong>Color</strong></div></td>
-    <td width="22" > <div align="right"><strong>Hue</strong></div></td>
-    <td width="58" > <div align="right"><strong>Saturation</strong></div></td>
-    <td width="63" > <div align="right"><strong>Lumination</strong></div></td>
-    <td width="21" > <div align="right"><strong>Red</strong></div></td>
-    <td width="37"  x:str="Green "> <div align="right"><strong>Green </strong></div></td>
-    <td width="26" > <div align="right"><strong>Blue</strong></div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">apple green</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">aqua</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">255</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">black</div></td>
-    <td  > <div align="right">160</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">blue</div></td>
-    <td  > <div align="right">160</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">255</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">blueviolet</div></td>
-    <td  > <div align="right">180</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">255</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">chocolate</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">80</div></td>
-    <td  > <div align="right">90</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">64</div></td>
-    <td  > <div align="right">64</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">dark blueviolet</div></td>
-    <td  > <div align="right">180</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">64</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">dark brown</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">30</div></td>
-    <td  > <div align="right">64</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">dark forest green</div></td>
-    <td  > <div align="right">80</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">30</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">64</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">dark olive</div></td>
-    <td  > <div align="right">40</div></td>
-    <td  > <div align="right">80</div></td>
-    <td  > <div align="right">90</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">64</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">dark orange</div></td>
-    <td  > <div align="right">20</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">dark purple</div></td>
-    <td  > <div align="right">200</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">30</div></td>
-    <td  > <div align="right">64</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">64</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">dark purple</div></td>
-    <td  > <div align="right">200</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">30</div></td>
-    <td  > <div align="right">64</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">64</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">dark red</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">dark teal</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">30</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">64</div></td>
-    <td  > <div align="right">64</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">dark turquoise</div></td>
-    <td  > <div align="right">140</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">64</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">deep sky blue</div></td>
-    <td  > <div align="right">140</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">255</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">green</div></td>
-    <td  > <div align="right">80</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">grey</div></td>
-    <td  > <div align="right">160</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">light green</div></td>
-    <td  > <div align="right">90</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">64</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">light grey</div></td>
-    <td  > <div align="right">160</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">181</div></td>
-    <td  > <div align="right">192</div></td>
-    <td  > <div align="right">192</div></td>
-    <td  > <div align="right">192</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">light teal</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">80</div></td>
-    <td  > <div align="right">90</div></td>
-    <td  > <div align="right">64</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">lime</div></td>
-    <td  > <div align="right">80</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">magenta</div></td>
-    <td  > <div align="right">200</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">255</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">maroon</div></td>
-    <td  > <div align="right">220</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">64</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">medium blue</div></td>
-    <td  > <div align="right">160</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">75</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">160</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">medium slate blu<span style='display:
-  none'>e</span></div></td>
-    <td  > <div align="right">160</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">180</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">255</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">midnight blue</div></td>
-    <td  > <div align="right">160</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">30</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">64</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td   x:str="navy "> <div align="left">navy </div></td>
-    <td  > <div align="right">160</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">olive</div></td>
-    <td  > <div align="right">40</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">pale green</div></td>
-    <td  > <div align="right">80</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">180</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">pale rose</div></td>
-    <td  > <div align="right">220</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">180</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">192</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">pale slate blue</div></td>
-    <td  > <div align="right">160</div></td>
-    <td  > <div align="right">81</div></td>
-    <td  > <div align="right">151</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">192</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">pale turquoise</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">180</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">255</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">pale yellow</div></td>
-    <td  > <div align="right">40</div></td>
-    <td > <div align="right">240</div></td>
-    <td  > <div align="right">180</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">pink</div></td>
-    <td  > <div align="right">200</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">180</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">255</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">pumpkin</div></td>
-    <td  > <div align="right">13</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">150</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">64</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">purple</div></td>
-    <td  > <div align="right">200</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">red</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">rose</div></td>
-    <td  > <div align="right">220</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">saddle brown</div></td>
-    <td  > <div align="right">20</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">64</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">salmon</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">180</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">sea green</div></td>
-    <td  > <div align="right">100</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">64</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">spring green</div></td>
-    <td  > <div align="right">100</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">teal</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">turquoise</div></td>
-    <td  > <div align="right">133</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">90</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">192</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">white</div></td>
-    <td  > <div align="right">160</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">255</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">yellow</div></td>
-    <td  > <div align="right">40</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-</table>
-
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/accessibility/fontsandcolors.htm b/bundles/org.eclipse.platform.doc.user/concepts/accessibility/fontsandcolors.htm
deleted file mode 100644
index 53ec6fa..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/accessibility/fontsandcolors.htm
+++ /dev/null

@@ -1,131 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <LINK REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css"> 
-  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-  <title>Fonts and colors in Eclipse</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body>
-
-<h1>Fonts and colors in Eclipse</h1>
-<p>Eclipse uses the fonts and colors provided by the operating system as much 
-  as possible. On Windows the platform color and font settings are found on the 
-  <b>Properties &gt; Colors and Fonts</b> page. The font used by most widgets 
-  in Eclipse is the one set in the Message Box settings of the properties. However, 
-  operating systems do not provide enough colors to handle all of the extra information 
-  that colors and fonts provide in Eclipse.&nbsp;</p>
-<h2>Fonts</h2>
-
-<p>There are 4 main fonts in use by the Eclipse platform. They are: </p>
-
-<dl>
-  <dt><em>Banner Font</em></dt>
-  <dd>Used in PDE editors, welcome pages and in the title area of many wizards. 
-    For instance the New Project wizard uses this font for the top title,</dd>
-  <dt><em>Header Font</em></dt>
-  <dd>Used as a section heading. For instance the Welcome page for the Eclipse 
-    Platform uses this font for the top title,</dd>
-  <dt><em>Text Font</em></dt>
-  <dd>Used in text editors.</dd>
-  <dt><em>Dialog Font</em></dt>
-  <dd>Used in dialogs.</dd>
-</dl>
-<p>These fonts can be set via the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.ColorsAndFonts)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General &gt; Appearance &gt; Colors and Fonts</b></a> preference page. 
-  As well as these 4 fonts there are several other secondary font settings. These 
-  default to the text font. They can be found on the Colors and Fonts preference 
-  page:</p>
-<ul>
-  <li><b>Compare Text Font</b></li>
-  <li><b>Console Text Font</b></li>
-  <li><b>CVS Console Font</b></li>
-  <li><b>Debug Console Font</b></li>
-  <li><b>Detail Pane Text Font</b></li>
-  <li><b>Java Compare Text Font</b></li>
-  <li><b>Java Editor Text Font</b></li>
-  <li><b>Memory Views Table Font</b></li>
-  <li><b>Part Title Font</b> (optional: used by some presentations)</li>
-  <li><b>View Message Font</b> (optional: used by some presentations)</li>
-</ul>
-<h2>Colors</h2>
-<p>Eclipse uses colors as an information enhancement in many places. Whenever
-possible the operating system color settings are used, but in cases where the
-operating system settings are not enough, Eclipse defines other colors. All of
-these colors can be adjusted via the following preference pages:</p>
-<ul>
-  <li><b><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.ColorsAndFonts)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General &gt; Appearance &gt; Colors and Fonts</b></a> &gt; Basic </b> (Error text, hyperlink 
-    text, active hyperlink text)</li>
-  <li><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.search.preferences.SearchPreferencePage)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General &gt; Search</b></a> (Foreground for potential matches)</li>
-  <li><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.ConsolePreferencePage)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Run/Debug &gt; Console</b></a> (Standard Out, Standard Error, Standard In)</li>
-  <li><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.DebugPreferencePage)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Run/Debug</b></a> (Variable Views changed value, Memory View unbuffered lines)</li>
-  <li><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ant.ui.AntPreferencePage)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Ant</b></a> (Error, Warning, Information, Verbose, Debug)</li>
-  <li><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.JavaEditorPreferencePage)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Java &gt; Editor</b></a> (Line number, matching brackets, current line, 
-    print, find scope, hyperlink, selection foreground, selection background)</li>
-  <li><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.JavaEditorColoringPreferencePage)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Java &gt; Editor &gt; Syntax Coloring</b></a> (Javadoc HTML tags, 
-    Javadoc keywords, Javadoc links, Javadoc others, keyword 'return', keywords 
-    excluding 'return', Method names, Multi line comment, Operators and brackets, 
-    Others, Single-line comment, Strings, Task Tags)</li>
-  <li><b>Java &gt; Editor &gt; Code Assist</b> (completion proposal background, 
-    completion proposal foreground, method parameter background, method parameter 
-    foreground, completion overwrite background, completion overwrite foreground)</li>
-  <li><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.pde.ui.EditorPreferencePage)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Plug-in Development &gt; Editors</b></a> (Text, Processing instructions, 
-    Constant strings, Tags, Comments)</li>
-  <li><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.ConsolePreferences)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Team &gt; CVS &gt; Console</b></a> (Command line, Message, Error)</li>
-</ul>
-<h2><img src="../../images/win_only.png" alt="Windows only" border="0" >Accessibility 
-  and the Windows Color Dialog</h2>
-<p>For color selection, Eclipse uses a dialog provided by the operating system. 
-  On windows, the color selection dialog does not respond properly to assistive 
-  technology. When you first get into the dialog, focus is on one of the basic 
-  colors, but the dialog provides no indication of this through assistive technology. 
-  You can select colors in Eclipse with this dialog in the following way:</p>
-<ol>
-  <li> Select to customize the color of something in Eclipse, for example the 
-    color of Error Text in your Workbench Colors and Fonts Basic preferences.</li>
-  <li> In the color selection dialog, tab twice to go from the Basic Color matrix 
-    to the Define Custom Colors button and press Enter.</li>
-  <li> You can now enter the basic colors using an HSL or RGB specification according 
-    to the following definitions. See the<a href="colordialog.htm"> Windows Color 
-    Dialog Reference</a> for a tables and values for these colors.<br>
-  </li>
-</ol>
-<p><img src="../../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-<a href="accessmain.htm">Accessibility Features in Eclipse</a><br>
-<a href="navigation.htm">Navigating the user interface by using the keyboard</a>
-</p>
-
-<p><img src="../../images/ngrelr.png" alt="Related references" border="0" ><br>
-<a href="keyboardshortcuts.htm">Keys</a><br>
-<a href="colordialog.htm"> Windows Color 
-    Dialog Reference</a> 
-</p>
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/accessibility/keyboardshortcuts.htm b/bundles/org.eclipse.platform.doc.user/concepts/accessibility/keyboardshortcuts.htm
deleted file mode 100644
index 16e9ace..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/accessibility/keyboardshortcuts.htm
+++ /dev/null

@@ -1,187 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-	<LINK REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css"> 
-	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-	<title>Keys</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-<body>
-<h1>Keys</h1>
-<p>
-The function of the keyboard can be extensively customized in Eclipse. Within
-Eclipse, key strokes and key sequences are assigned to invoke particular
-commands. 
-</p>
-<h2>Key Strokes, Key Sequences, and Key Bindings</h2>
-<p>
-A 'key stroke' is the pressing of a key on the keyboard, while optionally holding down one 
-or more of these modifier keys: <code>Ctrl</code>, <code>Alt</code> (<code>Option</code> on the Macintosh), <code>Shift</code>, or 
-<code>Command</code> (only on the Macintosh.) For example, holding down <code>Ctrl</code> then 
-pressing <code>A</code> produces the key stroke <code>Ctrl+A</code>. The pressing of the modifier keys themselves
-do not constitute key strokes.
-</p>
-<p>
-A 'key sequence' is one or more key strokes. Traditionally, Emacs assigned two or three key stroke key sequences to particular 
-commands. For example, the normal key sequence assigned to <code>Close All</code> in emacs is <code>Ctrl+X Ctrl+C</code>. 
-To enter this key sequence, one presses the key stroke <code>Ctrl+X</code> followed by the key stroke <code>Ctrl+C</code>.
-While Eclipse supports key sequences of arbitrary lengths, it is recommended
-that keyboard shortcuts be four key strokes in length (or less).
-</p>
-<p>
-A 'key binding' is the assignment of a key sequence to a command.
-</p>
-<h2>Schemes</h2>
-<p>
-A 'scheme' is a set of bindings. Eclipse includes two schemes:
-</p>
-<ul>
-<li>Default</li>
-<li>Emacs (extends Default)</li>
-</ul>
-<p>
-The <em>Default</em> scheme contains a general set of bindings, in many cases recognizable to 
-users as traditional key sequences. For instance, <code>Ctrl+A</code> is assigned to <code>Select All</code>, 
-and <code>Ctrl+S</code> is assigned to <code>Save</code>.
-</p>
-<p>
-The <em>Emacs</em> scheme contains a set of key bindings familiar to users of Emacs.
-For instance, <code>Ctrl+X H</code> is assigned to <code>Select All</code>, and <code>Ctrl+X S</code> is assigned to <code>Save</code>.
-</p>
-<p>
-It is important to understand why the <em>Emacs</em> scheme says that it 'extends Default'. The <em>Emacs</em> scheme
-is not a complete set of bindings like the <em>Default</em> scheme. Rather, it borrows from the <em>Default</em>
-scheme where possible, only defining explicit Emacs-style bindings where they vary from the
-<em>Default</em> scheme. Generally, only well known commands like <code>Select All</code>, <code>Save</code>, etc. have specific Emacs key sequences associated with them. 
-</p>
-<p>
-The user decides which scheme they are most comfortable using by changing the 'Scheme' setting on the
-keys preference page. If the user chooses the <em>Default</em> scheme, all <em>Emacs</em> bindings are ignored. If the user chooses
-the <em>Emacs</em> scheme, explicit Emacs-style key sequence assignments take precedence over any conflicting assignments in the <em>Default</em> scheme.
-</p>
-<h2>Contexts</h2>
-<p>
-Key bindings can vary based on the current context of Eclipse. 
-</p>
-<p> Sometimes the active part might be a Java file editor, for instance, where 
-  a different set of key sequence assignments may be more appropriate than if 
-  the active part was an html file editor. As a specific example, typically <code>Ctrl+B</code> 
-  is assigned to <code>Build</code> in a context such as Java file editing, while 
-  <code>Ctrl+B</code> is assigned to <code>Make Text Bold</code> in a context 
-  such as HTML file editing. This context is usually determined by the active
-  part, but it can be influenced by the active window or dialog as well. If the
-  active part does not choose a particular context, the workbench will set the 
-  active context to <em>In Windows</em>.</p>
-<p>Eclipse includes nine different contexts. They are: </p>
-<ul>
-  <li>In Dialogs and Windows</li>
-  <li>In Windows (extends In Dialogs and Windows)</li>
-  <li>In Dialogs (extends In Dialogs and Windows)</li>
-  <li>Editing Text (extends In Windows)</li>
-  <li>Editing Java Source (extends Editing Text)</li>
-  <li>Debugging (extends In Windows)</li>
-  <li>Debugging Java (extends Debugging)</li>
-  <li>In Console</li>
-  <li>Editing Ant buildfiles<br>
-    <br>
-  </li>
-</ul>
-<p> Much like configurations, contexts can extend other contexts. For example, 
-  the <em>Editing Java Source</em> context borrows key bindings from the <em>Editing Text</em> 
-  context, which in turn borrows key bindings from the <em>In Windows</em> context. 
-</p>
-<p>Note: It is not recommended to promote a key binding to a context which it
-extends.  For example, it is not recommended to move an <em>Editing Text</em> key
-binding to the <em>In Dialogs and Windows</em> context.  This may have unexpected
-results.</p>
-<p>It is possible for some key bindings to work in dialogs.  Those key bindings
-are assigned to the <em>In Dialogs and Windows</em> context.  One example of such a
-key binding is the key binding for "cut".  It is possible to change these key
-bindings.  For example, it is possible to have Ctrl+X as cut in dialogs, but
-Ctrl+W as cut in windows.</p>
-<h2>Platform and Locale</h2>
-<p>
-Key bindings also vary by platform and locale. On the Macintosh platform, <code>Command+S</code> is assigned to <code>Save</code>, instead of the usual <code>Ctrl+S</code>. On Chinese locales (zh), <code>Alt+/</code> is assigned to <code>Content Assist</code>, instead of the usual <code>Ctrl+Space</code>.
-</p>
-<p>
-The current platform and locale is determined when Eclipse starts, and does not vary over the course of an Eclipse instance.
-</p>
-<h2>Customizing Key bindings</h2>
-<p> With multi-stroke key sequences, schemes, and contexts, there are a 
-  lot of things to keep in mind when customizing key bindings. To make things 
-  easier, all key customization is done on the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Keys)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General &gt; Keys</b></a> preference page.
-</p>
-<p> <img src="../../images/keys1.png" alt="Keys preference page showing Emacs as the active configuration and the Close command selected" > 
-</p>
-<p>
-In this example, we have chosen to select <em>Emacs</em> as the scheme, 
-and have selected the command <code>Close</code> from the list of commands. Information 
-on this command, along with its current key bindings, is shown. </p> 
-<p> Notice that <code>Close</code> has three key sequences assigned to it: <code>Ctrl+F4</code>  and <code>Ctrl+W</code>
-  in the <em>Default</em> scheme and <code>Ctrl+X K</code> in the <em>Emacs</em> 
-  scheme. Both are assigned in the <em>In Windows</em> context. Thus, if the 
-  user sets the scheme to <em>Default</em>, <code>Ctrl+F4</code> and <code>Ctrl+W</code>
-  will be assigned to <code>Close</code> while <code>Ctrl+X K</code> will not. 
-  If the user sets the scheme to <em>Emacs</em>, however, <code>Ctrl+X 
-  K</code> will be assigned to <code>Close</code>. As well, because the <em>Emacs</em> 
-  scheme also borrows key bindings from the <em>Default</em> scheme, 
-  <code>Ctrl+F4</code> and <code>Ctrl+W</code> will also be assigned to <code>Close</code> provided that 
-  these key binding have not been assigned to another command in the <em>Emacs</em> 
-  scheme.  In this example, "Ctrl+W" is bound to <code>Cut</code> in the Emacs
-  scheme.</p>
-<p> Below the list of key sequences assigned to <code>Close</code>, there is a 
-  place to add or remove key bindings. By default, it selects the context as <em>In Windows</em>.</p> 
-<p> We type in the key sequence <code>Ctrl+W</code>, and the 'Add' button becomes 
-  enabled. Also, a list of all the commands to which the key sequence <code>Ctrl+W</code> 
-  is already assigned is show below the Add button. We can see that <code>Ctrl+W</code> 
-  is currently assigned to the command <code>Cut</code> in the <em>In Windows and Dialogs</em> 
-  context. We click the 'Add' button to assign <code>Ctrl+W</code> to <code>Close</code>. </p>
- <h2>The Dynamic Nature of Key bindings</h2>
-<p>
-Key bindings are provided by plug-ins, and in Eclipse, plug-ins can be added or removed. This can cause key bindings declared by these plug-ins to be added or removed. Eclipse stores custom key bindings in a way to This compensate for this. Consider the example above where <code>Ctrl+Alt+W</code> was assigned to <code>Cut</code> in the <em>Emacs</em> scheme. Consider the user installs a new plug-in which assigns <code>Ctrl+Alt+W</code> to a particular command. Eclipse will preserve the user's assignment to <code>Cut</code>.
-</p>
-<h2>Conflict Resolution</h2>
-<p> There are only a finite number of simple, common key strokes available to 
-  assign to a multitude of commands. We have seen that scheme, context, 
-  platform, and locale all partition key sequence assignments into domains where 
-  they don't conflict with one another. Consider the case for <code>Ctrl+B</code> 
-  above if contexts did not exist. One plug-in would assign <code>Ctrl+B</code> 
-  to <code>Build</code>, the other plug-in would assign <code>Ctrl+B</code> to 
-  <code>Make Bold Text</code>. How would Eclipse properly resolve this conflict? 
-</p>
-<p> Though conflicts are drastically reduced by employing the above mechanisms, 
-  they can still occur. Two plug-ins, independent of one another, could assign 
-  the same key sequence to different commands with the same context, scheme, 
-  platform, and locale. Consider if a plug-in assigned <code>Ctrl+F4</code> in 
-  the <em>In Windows</em> context and <em>Default</em> scheme to one of its 
-  commands. This directly conflicts with Eclipse assigning <code>Ctrl+F4</code> 
-  to the close command in the same context and scheme. </p>
-<p>
-This is a conflict. It wouldn't be proper to invoke both commands, nor would it be proper to simply choose one of the two commands to receive the key stroke. The only proper thing to do is to ignore both key bindings, making <code>Ctrl+F4</code> effectively useless in this context and scheme.
-</p>
-<p> These types of conflicts can be resolved by the user explicitly assigning 
-  the key sequence to one of the commands. </p>
-<p>
-Another type of conflict can be caused by multiple-key stroke key sequences. For example, in the <em>Emacs</em> scheme, there are many multiple-key stroke key sequences beginning with the key stroke <code>Ctrl+X</code>. <code>Ctrl+X K</code> is assigned to <code>Close</code>. <code>Ctrl+X H</code> is assigned to <code>Select All</code>.
-</p>
-<p>
-As previously mentioned, the <em>Emacs</em> scheme borrows key bindings from the <em>Default</em> scheme. In the default scheme, <code>Ctrl+X</code> is assigned to <code>Cut</code>. Though the <em>Emacs</em> scheme doesn't explicitly redefine <code>Ctrl+X</code>, pressing <code>Ctrl+X</code> is required as part of many of its key bindings. In the <em>Emacs</em> scheme, when one presses <code>Ctrl+X</code>, one is half way to entering one of many possible assigned key sequences. One would not expect the <code>Cut</code> action to be invoked at this time.
-</p>
-<p>
-For this type of conflict, the rule is that the <code>Ctrl+X</code> key sequence assigned to <code>Cut</code> would be ignored. Otherwise, it would not be possible to complete many of the key bindings in the <em>Emacs</em> configuration. 
-</p>
-<p><img src="../../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="accessmain.htm">Accessibility Features in Eclipse</a><br>
-<a href="../../tasks/tkeybindings.htm">Changing the key bindings</a><br>
-<a href="../chelpsys.htm">Online help system</a></p>
-<p><img src="../../images/ngrelr.png" alt="Related references" ><br>
-  <a href="fontsandcolors.htm">Font and color settings in Eclipse</a></p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/accessibility/navigation.htm b/bundles/org.eclipse.platform.doc.user/concepts/accessibility/navigation.htm
deleted file mode 100644
index 1c79dfb..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/accessibility/navigation.htm
+++ /dev/null

@@ -1,110 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
- <LINK REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css"> 
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
- <title>Navigating the user interface using the keyboard</title>
-</head>
-
- <body>
-
- <h1>Navigating the user interface using the keyboard</h1>
- <p>The user interface is navigable using the keyboard. The Tab key is used to
- iterate through the controls in a particular scope (for example, a dialog or a view and
- its related icons). To navigate to the main controls for the Workbench window
- or to tab out of views that use the Tab key (such as editors) use Ctrl+Tab.</p>
- <h2>Menus</h2>
- <p>Most menus are assigned mnemonics for each entry which allow you to
- select them by typing the underlined letter instead of the mouse. You can also
- select an item by moving through the menus and sub-menus with the arrow keys. </p>
- <p>The various menus available can be accessed using the keyboard in the
- following ways: </p>
- <ul>
-  <li>F10 accesses the menus on the main menu bar.</li>
-  <li>Shift+F10 pops up the context menu for the current view. (Note: this
-  shortcut is actually dependent on your window manager, but for most people it
-  should be Shift+F10.)</li>
-  <li>Ctrl+F10 will open the pull down menu for the current view if there is
-    one.  For editors, Ctrl+F10 will open the menu for the marker bar on the left of the
-    editor area.</li>
-  <li>Alt+mnemonic will activate the Workbench menu for a particular entry
-    (e.g., Alt+W will bring down the <u>W</u>indow menu).</li>
-  <li>Microsoft Windows only: Pressing Alt will give focus to the menu
-  bar.</li>
- </ul>
- <h2>Controls</h2>
- <p>Mnemonics are assigned to most control labels (e.g., buttons, checkboxes,
- radio buttons, etc.) in dialog boxes, preference pages, and property pages. To
- access the control associated with a label, use the Alt key along with the
- letter that is underlined in the label.</p>
- <h2>Navigation Context</h2>
- <p>Navigation context is saved for the packages, navigator views, Workbench preferences and properties dialogs. The expanded state of the tree in
- the packages and resource views are saved between Workbench sessions. The
- selected page for the preferences and properties dialog is saved between
- invocations of the dialog but are not saved between workbench invocations. </p>
- <h2>Cycling Editors, Views and Perspectives </h2>
- <p>To switch between editors, views and perspectives, the workbench provides a cycling
- function that is invoked by Ctrl and a function key. All of these cycling
- functions recall the last thing selected to allow for rapid cycling back and
- forth between two items. The cycling functions are </p>
- <ul>
-  <li>Ctrl+F6 - Cycle to Editor</li>
-  <li>Ctrl+F7 - Cycle to View</li>
-  <li>Ctrl+F8 - Cycle to Perspective</li>
- </ul>
- <p>Also, Ctrl+E can be used to activate the editor drop-down, and Ctrl+PageUp
- and Ctrl+PageDown can be used for switching between the open editors.</p>
- <h2>Accelerators </h2>
- 
-<p>Many of the actions in Eclipse have an accelerator assigned to them. For additional 
-  information on accelerators, see <a href="keyboardshortcuts.htm">Keys</a>. </p>
- <h2>Help system</h2>
- <p>You can navigate the help system by keyboard using the following key 
- combinations:</p>
- <ul>
-   <li>Pressing Tab inside a frame (page) takes you to the next link, button or 
-   topic node. </li>
-   <li>To expand/collapse a tree node, press Right/Left arrows. </li>
-   <li>To move to the next topic node, press Down arrow or Tab </li>
-   <li>To move to the previous topic node, press Up arrow or Shift+Tab </li>
-   <li>To display selected topic, press Enter. </li>
-   <li>To scroll all the way up or down press Home or End. </li>
-   <li>To go back press Alt+Left arrow; to go forward press Alt+Right arrow.
-   </li>
-   <li>To go to the next frame, or toolbar press Ctrl+Tab
-     (Ctrl+F6, if using Mozilla, or Mozilla based browser).</li>
-   <li>To move to previous frame, press Shift+Ctrl+Tab.
-     (Shift-Ctrl+F6, if using Mozilla, or Mozilla based browser).</li>
-
-   <li>To move to the frame displaying topic content press Alt+K (when using
-     embedded help browser on Windows, or Internet Explorer).</li>
-   <li>To move to Contents tab, press Alt+C</li>
-   <li>To move to Search Results tab, press Alt+R</li>
-   <li>To move between tabs, press Right/Left arrows.</li>
-   <li>To switch view, select a tab and press Enter.</li>
-   <li>To switch and move to a view, select a tab and press Up arrow.</li>
-   <li>To move to the search entry field, press Alt+S</li>
-   <li>To print the current page or active frame, press Ctrl+P. </li>
-   <li>To find a string in the current page or active frame, press Ctrl+F
-     (when using embedded help browser on Windows, or Internet Explorer). </li>
- </ul>
-<p>Most labels of controls
-on help system pop-up dialogs have mnemonics are assigned to them. To access
-  the control associated with a label, use the Alt key along with the letter
-  that
- is underlined.</p>
-
-<p><img src="../../images/ngrelc.png" alt="Related concepts" border="0" ><br>
-  <a href="accessmain.htm">Accessibility features in Eclipse</a><br>
- <a href="../../tasks/tkeybindings.htm">Changing the key bindings</a><br>
- <a href="keyboardshortcuts.htm">Keys</a> <br>
-<a href="../chelpsys.htm">Online help system</a></p>
- <p><img src="../../images/ngrelr.png" alt="Related references" border="0" ><br>
-  <a href="fontsandcolors.htm">Font and color settings in Eclipse</a></p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/cbookmrk.htm b/bundles/org.eclipse.platform.doc.user/concepts/cbookmrk.htm
deleted file mode 100644
index bfa4b85..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/cbookmrk.htm
+++ /dev/null

@@ -1,48 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Bookmarks</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
- Bookmarks </H1>
-<P CLASS="Para">You can place an &quot;anchor&quot; either on a resource within
-the Workbench, or at a specific line within a file, by creating a bookmark. Then
-you can use the Bookmarks view to return to those files quickly.</P>
-<P CLASS="Para">The Bookmarks&nbsp; view (<b>Window &gt; Show View &gt;
-Bookmarks</b>) displays all bookmarks&nbsp;that you have created.&nbsp;</P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="ctskview.htm">Tasks view</a></p>
-
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-81b.htm">Creating a bookmark for an entire file</a><a href="../tasks/tasks-81.htm"><br>
-Creating a bookmark within a file</a><a href="../tasks/tasks-82.htm"><br>
-Deleting a bookmark<br>
-</a><a href="../tasks/tasks-77.htm">Adding line items in the Tasks view</a><a href="../tasks/tasks-77b.htm"><br>
-Associating a task with an editable resource</a></p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="concepts-11.htm">Markers</a><br>
-<a href="ctskview.htm">Tasks view</a><br>
-<a href="cprbview.htm">Problems view</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-28.htm">Bookmarks view</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/cdecorations.htm b/bundles/org.eclipse.platform.doc.user/concepts/cdecorations.htm
deleted file mode 100644
index 9de9eaa..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/cdecorations.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Label decorations</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
- Label decorations </H1>
-<P CLASS="Para">Label decorations are used to show extra information about an
-item by modifying its label or icon. They can be used to obtain information
-about the state of an item without having to look at its properties in the
-Properties view or open its Properties dialog.</P>
-<P CLASS="Para">A number of label decorators may be available. To control which 
-  decorators are visible, go to the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Decorators)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General &gt; Appearance &gt; Label Decorations</b></a> preference page.
-  This preference page provides a selectable 
-  list and description of the available decorations.</P>
-<P CLASS="Para">The following is the Navigator view showing resources with CVS
-decorations:</P>
-<P CLASS="Para"><img src="../images/Image273_nav-decorators.png" alt="Navigator view with CVS decorators on" border="0" ></P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/chelpsys.htm b/bundles/org.eclipse.platform.doc.user/concepts/chelpsys.htm
deleted file mode 100644
index 9899685..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/chelpsys.htm
+++ /dev/null

@@ -1,87 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Help system</title>
-</head>
-
-<body>
-
-<h1>Help system</h1>
-
-<p>The online help system lets you 
-browse, search, and print system documentation. The documentation is organized
-  into sets of  information that are analogous to books. The help system also
-  supplies a text
-search capabilities for finding the information you need by keyword and
-context-sensitive help for finding information to describe the particular
-function you are working with.</p>
-<p>You can interact with help system in the workbench using Help view, or in
-  external help browser window.</p>
-<h2>The help browser</h2>
-
-<p>When you first open the help browser by selecting <b>Help &gt; Help Contents</b> 
-in the Workbench, the first view shown in the help window is called Contents.
-   Contents displays 
-various groupings of documentation for the product. Click on 
-one of the links to expand the navigation tree for that set of documentation.
-Browse the tree and click on topics to display them.</p>
-
-<h2>Search</h2>
-<p>If you want to find a particular piece of information in the online help, use
-Search. The help system will search the entire information set, or only a part
-of it, to find topics that meet the criteria you specify.</p>
-
-<h2>The Help view</h2>
-
-<p>You can open a Help view by The Help view
-  by selecting <b>Help &gt; Dynamic Help</b> or by selecting <b>Help &gt; Search </b>
-in the Workbench., A help view will open turning to the Related Topics or to the
-Search page. You can use links at the bottom of the help view to turn to other
-pages. Browse topics and click on links to display them.</p>
-
-<h2>Context-sensitive help</h2>
-
-<p>If you are working through a task and encounter part of the interface that
-you do not understand, use context-sensitive help.. Bring focus to the
-  interface widget in
-question by clicking on it or using the Tab key, and then press <code>F1</code>
-(<code>Ctrl+F1</code> on GTK+, and <code>Help</code> key on Carbon). A Help view
-will display description of the widget in focus, and list related topics. Leave
-the Help view open to see information on other interface elements when you focus
-on them.</p>
-<p>When working in a dialog, like wizards, or preferences, and request context-sensitive
-  help, a help view will be shown in a small window adjacent to the dialog.</p>
-<p>An alternative way of presenting context-sensitive information are infopops.
-  You can use help preference page to choose to use infopops instead of Help
-  view for displaying context-sensitive help. If configured, a context help key,
-  such as <code>F1</code>, will open an infopop that will provide you with information
-  about the interface and, if appropriate, links
-  to more
-  information.</p>
-<p>Note: On the some installation of KDE, Ctrl+F1 is the key binding for "Switch
-to Desktop 1".  To make context-sensitive help work with GTK+ on KDE, then that
-binding must be removed.  Try using the "KDE Default for 4 Modifier Keys" key
-binding scheme.</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt=
-"Related concepts"><br>
-<a href="chelpview.htm">Help View</a></p>
-<p>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/taccess.htm">Accessing and navigating online help</a><br>
-<a href="../tasks/tsearch.htm">Searching online help</a><br>
-<a href="../tasks/tf1help.htm">Accessing context-sensitive help</a><br>
-</p>
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/chelpview.htm b/bundles/org.eclipse.platform.doc.user/concepts/chelpview.htm
deleted file mode 100644
index a3daf9a..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/chelpview.htm
+++ /dev/null

@@ -1,214 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta name="copyright" content=
-"Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content=
-"text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
-type="text/css">
-<title>Help view</title>
-</head>
-
-<body bgcolor="#ffffff">
-<h1>Help view</h1>
-
-<p class="Intro">The Help view provides user assistance inside the
-Workbench. The view consists of four pages providing user
-assistance. Each page presents help topics in a slightly different
-fashion. Hyper links at the bottom of the help view allow switching
-among pages, and clicking any topic will display its contents.</p>
-
-<h2>Related Topics</h2>
-
-<p class="Para"><img src="../images/helpview-related.png" alt=
-"Picture of Help view turned to related topics page. List of topics related to some workbench part is displayed."
- border="0"></p>
-
-<p class="Para">The Related Topics page shows description and help
-topics related to the current workbench context. The topics include
-context help, as well as the result of a local help search on the
-current context, presented in "Dynamic Help" section of the page.
-For example, if the currently active workbench part is 'Package
-Explorer' inside the Java perspective, local help will find and
-present topics describing "Package Explorer view" or "Java
-perspective". The Related Topics page tracks changes in the
-workbench and continuously updates displayed information.</p>
-
-<h2>All Topics</h2>
-
-<p class="Para"><img src="../images/helpview-all.png" alt=
-"Picture of Help view turned to all topics page. Page contains a navigation tree of all help topics."
- border="0"></p>
-
-<p class="Para">The All Topics page shows the Table of Contents. It
-is a hierarchy of all help topics arranged in a tree The tree
-branches can be expanded to browse topics that can be displayed
-using a single mouse click.</p>
-
-<h2>Search</h2>
-
-<p class="Para"><img src="../images/helpview-search.png" alt=
-"Picture of Help view turned to search page. Search exprssion entry field, and search results topic list."
- border="0"></p>
-
-<p class="Para">The Search page allows locating local topics,
-remote documents, and other documents given a search query. Links
-to search hits are displayed along with a summary of topic
-contents. Search scope controls a subset of documentation being
-searched. Multiple search scopes can be configured, each defining a
-custom set of resources from among local documentation, additional
-local search engines or remote engines on the web.</p>
-
-<h2>Bookmarks</h2>
-
-<p class="Para"><img src="../images/helpview-bookmarks.png" alt=
-"Picture of Help view turned to the bookmarks page. Page contains a bookmark to one of the topics."
- border="0"></p>
-
-<p class="Para">The Bookmarks shows topics marked as personal
-bookmarks.</p>
-
-<h2>Toolbar</h2>
-
-<p>The toolbar of the Help view contains the following buttons. The
-available buttons depends on the currently displayed page.</p>
-
-<dl>
-<dt>Back</dt>
-
-<dd>Displays the page or the topic that was displayed immediately
-prior to the current display.</dd>
-
-<dt>Forward</dt>
-
-<dd>Displays the page or the topic was displayed immediately after
-the current display.</dd>
-
-<dt>Collapse All</dt>
-
-<dd>Collapses the tree expansion state of all topics on the
-page.</dd>
-
-<dt>Show All Topics</dt>
-
-<dd>When filtering of workbench elements is enabled, the buttons
-enables displaying topics for disabled elements.</dd>
-
-<dt>Show Result Categories</dt>
-
-<dd>Switches between sorting search results by relevance and by
-logical containers for example books.</dd>
-
-<dt>Show Result Descriptions</dt>
-
-<dd>Displays short description of each search hit, when
-available.</dd>
-
-<dt>Menu</dt>
-
-<dd>Provides menu items that allow you switching help view
-pages.</dd>
-</dl>
-
-<h2>Icons</h2>
-
-<p class="Para">The following icons can appear in the Help
-view.</p>
-
-<table border="1" cellspacing="0">
-<thead>
-<tr>
-<th rowspan="1" colspan="1">
-<p class="Para">Icon</p>
-</th>
-<th rowspan="1" colspan="1">
-<p class="Para">Description</p>
-</th>
-</tr>
-</thead>
-
-<tbody>
-<tr>
-<td rowspan="1" colspan="1" valign="top" align="left"><img src=
-"../images/toc_closed.png" alt="Open project icon" border="0"></td>
-<td rowspan="1" colspan="1" valign="top" align="left">Book
-(closed)</td>
-</tr>
-
-<tr>
-<td rowspan="1" colspan="1" valign="top" align="left"><img src=
-"../images/toc_open.png" alt="Folder icon" border="0"></td>
-<td rowspan="1" colspan="1" valign="top" align="left">Book
-(closed)</td>
-</tr>
-
-<tr>
-<td colspan="1" valign="top" align="left"><img src=
-"../images/container_obj.png" alt="File icon" border="0"></td>
-<td colspan="1" valign="top" align="left">Topic (container)</td>
-</tr>
-
-<tr>
-<td colspan="1" valign="top" align="left"><img src=
-"../images/topic_small.png" alt="File icon" border="0"></td>
-<td colspan="1" valign="top" align="left">Topic</td>
-</tr>
-
-<tr>
-<td colspan="1" valign="top" align="left"><img src=
-"../images/slocalhelp_obj.png" alt="File icon" border="0"></td>
-<td colspan="1" valign="top" align="left">Search of local help</td>
-</tr>
-
-<tr>
-<td colspan="1" valign="top" align="left"><img src=
-"../images/sinfocenter_obj.png" alt="File icon" border="0"></td>
-<td colspan="1" valign="top" align="left">Search of remote
-info-center</td>
-</tr>
-
-<tr>
-<td colspan="1" valign="top" align="left"><img src=
-"../images/sweb_obj.png" alt="File icon" border="0"></td>
-<td colspan="1" valign="top" align="left">Search of web engine</td>
-</tr>
-
-<tr>
-<td colspan="1" valign="top" align="left"><img src=
-"../images/openseparate_co.png" alt="File icon" border="0"></td>
-<td colspan="1" valign="top" align="left">Open link in a help
-window</td>
-</tr>
-
-<tr>
-<td colspan="1" valign="top" align="left"><img src=
-"../images/addbkmrk_co.png" alt="File icon" border="0"></td>
-<td colspan="1" valign="top" align="left">Bookmark document</td>
-</tr>
-
-<tr>
-<td colspan="1" valign="top" align="left"><img src=
-"../images/bookmark_obj.png" alt="File icon" border="0"></td>
-<td colspan="1" valign="top" align="left">Bookmarked document</td>
-</tr>
-</tbody>
-</table>
-
-<p><img border="0" src="../images/ngrelc.png" alt=
-"Related concepts"><br>
-<a href="concepts-5.htm">Views</a></p>
-
-<p><img border="0" src="../images/ngrelt.png" alt=
-"Related tasks"><br>
-<a href="../tasks/tasks-3.htm">Opening views</a><br>
-<a href="../tasks/tasks-3e.htm">Moving and docking views</a><br>
-<a href="../tasks/tasks-9b.htm">Creating fast views</a></p>
-
-<p><img border="0" src="../images/ngrelr.png" alt=
-"Related reference"><br>
-<a href="../reference/ref-34.htm">Help window</a></p>
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/cnav.htm b/bundles/org.eclipse.platform.doc.user/concepts/cnav.htm
deleted file mode 100644
index cabccf1..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/cnav.htm
+++ /dev/null

@@ -1,113 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Navigator view</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>
-Navigator view</H1>
-<P CLASS="Intro">
-
-The Navigator view provides a hierarchical view of the resources in the Workbench.
-From here, you can open files for editing or select resources for operations such
-as exporting.</p>
-<P CLASS="Para">
-<img src="../images/Image241_nav_view.png" alt="Picture of Navigator view showing a simple hierarchy (project, folders, files)" border="0"></P>
-<P CLASS="Para">
-Right-click on any resource in the Navigator view to open a pop-up menu that
-allows you to perform operations such as copying, moving, creating new
-resources, comparing resources with each other, or performing team
-operations. To see a description of what each menu item does, move selection
-highlight to that menu item and press the context-sensitive help key (e.g., F1
-on Microsoft Windows).</P>
-<P CLASS="Para">
-By default, the Navigator view is included in the Resources perspective. To add it
-to the current perspective, click
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.ResourceNavigator)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Navigator</b></a>.</P>
-<h2>
-Toolbar</h2>
-<P>
-The toolbar of the Navigator view contains the following buttons:</P>
-<dl>
-  <dt>Back</dt>
-  <dd>Displays the hierarchy that was displayed immediately prior to the current display.</dd>
-  <dt>Forward</dt>
-  <dd>Displays the hierarchy that was displayed immediately after the current
-    display.</dd>
-  <dt>Up</dt>
-  <dd>Displays the hierarchy of the parent of the
-current highest level resource.</dd>
-  <dt>Collapse All</dt>
-  <dd>Collapses the tree expansion state of all resources in the view.</dd>
-  <dt>Link with Editor</dt>
-  <dd>Toggles whether the Navigator view selection is linked to the active editor.
-  When this option is selected, changing the active editor will automatically update the 
-  Navigator selection to the resource being edited.</dd>
-  <dt>Menu</dt>
-  <dd>Provides menu items that allow you to sort or filter the contents of the
-  Navigator view as well as select a working set.</dd>
-</dl>
-<h2>
-Icons</h2>
-<p CLASS="Para">The following icons can appear in the Navigator view.</p>
-<table BORDER="1" cellspacing="0">
-    <thead>
-    <tr>
-      <th ROWSPAN="1" COLSPAN="1">
-        <p CLASS="Para">Icon</p>
-      </th>
-      <th ROWSPAN="1" COLSPAN="1">
-        <p CLASS="Para">Description</p>
-      </th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td ROWSPAN="1" COLSPAN="1" valign="top" align="left"><img src="../images/ref-10.png"  alt="Open project icon" border="0"></td>
-      <td ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-        Project (open)      </td>
-    </tr>
-    <tr>
-      <td ROWSPAN="1" COLSPAN="1" valign="top" align="left"><img src="../images/ref-12.png"  alt="Folder icon" border="0"></td>
-      <td ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-       Folder
-      </td>
-    </tr>
-    <tr>
-      <td COLSPAN="1" valign="top" align="left"><img src="../images/ref-15.png"  alt="File icon" border="0"></td>
-      <td COLSPAN="1" valign="top" align="left"> File</td>
-    </tr>
-  </tbody>
-</table>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="concepts-12.htm">Resources</a><br>
-<a href="concepts-5.htm">Views</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-46bg.htm">Narrowing the scope of the Navigator view</a><br>
-<a href="../tasks/tasks-48.htm">Sorting resources in the Navigator view</a><br>
-<a href="../tasks/tasks-48b.htm">Showing or hiding files in the Navigator view</a><br>
-<a href="../tasks/tasks-3.htm">Opening views</a><br>
-<a href="../tasks/tasks-3e.htm">Moving and docking views</a><br>
-<a href="../tasks/tasks-9b.htm">Creating fast views</a>
-</p>
-<P><IMG border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-27.htm">Navigator view</a>
-</P>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-11.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-11.htm
deleted file mode 100644
index d7f48bd..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-11.htm
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Markers</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Markers</H1>
-<p CLASS="Head">Markers are objects that may be associated with Workbench resources.&nbsp; 
-  There are many uses of markers in the Workbench.&nbsp; The three main uses of 
-  markers in the Workbench are:</p>
-<ul>
-  <li>Tasks</li>
-  <li>Problems</li>
-  <li>Bookmarks</li>
-</ul>
-<p CLASS="Head">Markers are shown in a marker view (Tasks, Problems or Bookmark 
-  view) or on the marker bar in the editor area.</p>
-<p CLASS="Head">The following sections give more detail on each of these marker 
-  types. </p>
-<DIV CLASS="Subtopic">
-<h2>
-Tasks</h2>
-  <P CLASS="Para"> A task marker represents a work item. There are two kinds of 
-    tasks: </P>
-<UL CLASS="UnorderedList">
-    <LI CLASS="Item"> Automatically-generated information associated with the 
-      resource</LI>
-    <LI CLASS="Item"> User specified tasks that may or may not be associated with 
-      a resource</LI>
-</UL>
-  <p>Both of these task types appear in the Tasks view.</p>
-<h2>
-Problems</h2>
-  <P CLASS="Para" Label=Type> Problem markers represent invalid states and are 
-    categorized as follows..</P>
-</DIV>
-<ul>
-  <li> 
-    <DIV CLASS="Subtopic"> <strong>Errors</strong>: Error markers are often used 
-      to indicate the source location of syntax or compilation errors.</DIV>
-  </li>
-  <li> 
-    <DIV CLASS="Subtopic"> <strong>Warnings</strong>: Warning markers indicate 
-      the source location of, for example, compilation warnings.</DIV>
-  </li>
-  <li> 
-    <DIV CLASS="Subtopic"> <strong>Information</strong>: Information markers indicate 
-      the source location of information only tasks.</DIV>
-  </li>
-</ul>
-<p>Problems are shown in the Problems view. </p>
-<h2>
-Bookmarks</h2>
-<P CLASS="Para" Label=Type> Bookmarks place an anchor either at a specific line 
-  in a resource or on the resource itself. They are shown in the Bookmarks view.</P>
-
-<P CLASS="Para" Label=Type>
-<img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="cbookmrk.htm">Bookmarks</a><br>
-<a href="ctskview.htm">Tasks view</a><br>
-  <a href="cprbview.htm">Problems view</a></P>
-
-<P CLASS="Para" Label=Type>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-81.htm">Creating a bookmark within a file</a><br>
-<a href="../tasks/tasks-81b.htm">Creating a bookmark for an entire file</a></P>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-12.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-12.htm
deleted file mode 100644
index b0305fd..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-12.htm
+++ /dev/null

@@ -1,76 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Resources</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Resources</H1>
-<p CLASS="Head"> <i>Resources</i> is a collective term for the projects, folders, 
-  and files that exist in the Workbench. The navigation views provide a hierarchical 
-  view of resources and allows you to open them for editing. Other tools may display 
-  and handle these resources differently.&nbsp;</p>
-<p CLASS="Head">There are three basic types of resources that exist in the
-Workbench:</p>
-<dl>
-  <dt>Files</dt>
-  <dd>Comparable to files as you see them in the file system.&nbsp;</dd>
-  <dt>Folders</dt>
-  <dd>Comparable to directories on a file system.&nbsp; In the Workbench,
-    folders are contained in projects or other folders. Folders can contain
-    files and other folders.</dd>
-  <dt>Projects</dt>
-  <dd>Contain folders and files. Projects are used for builds, version
-    management, sharing, and resource organization. Like folders, projects map
-    to directories in the file system. (When you create a project, you specify a
-    location for it in the file system.)</dd>
-
-  <dd>A project is either open or closed. When a project is closed, it cannot be
-    changed in the Workbench.&nbsp; The resources of a closed project will not
-    appear in the Workbench, but the resources still reside on the local file
-    system.&nbsp; Closed projects require less memory.&nbsp; Since they are not
-    examined during builds, closing a project can improve build time.</dd><dd>When a project is open, the structure of the project can be changed and
-    you will see the contents.&nbsp;</dd>
-</dl>
-<p>
-Folders and files directly below projects can be linked to locations in the file system
-outside of the project's location.  These special folders and files are called 
-<a href="concepts-13.htm">linked resources</a>.
-</p>
-<p>Different tools that plug into the Workbench use their own specialized types
-of projects, folders, and files.&nbsp;</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="concepts-2.htm">Workbench</a><br>
-<a href="cnav.htm">Navigator view</a><br>
-<a href="concepts-17.htm">Resource hierarchies</a><br>
-<a href="concepts-13.htm">Linked resources</a><br>
-<a href="concepts-22.htm">Builds</a>
-</p>
-
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-53.htm">Importing resources into the Workbench</a><br>
-<a href="../tasks/tasks-42.htm">Creating a project</a><br>
-<a href="../tasks/tasks-43.htm">Creating a folder</a><br>
-<a href="../tasks/tasks-44.htm">Creating a file</a><br>
-<a href="../tasks/tasks-45.htm">Creating linked resources</a><br>
-<a href="../tasks/tasks-47.htm">Closing projects</a><br>
-<a href="../tasks/tasks-49.htm">Viewing resource properties</a><br>
-<a href="../tasks/tasks-46ag.htm">Finding a resource quickly</a><br>
-<a href="../tasks/tasks-63cg.htm">Copying resources</a><br>
-<a href="../tasks/tasks-63.htm">Moving resources</a><br>
-<a href="../tasks/tasks-68.htm">Comparing resources</a><br>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-13.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-13.htm
deleted file mode 100644
index b7be756..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-13.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Linked resources</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Linked resources</H1>
-<p>
-Linked resources are files and folders that are stored in locations 
-in the file system outside of the project's location.  These special resources can be
-used to add files and folders to your project that for some reason must be stored in a 
-certain place outside of your project.  For example, a linked folder can be used
-to store build output separately from your source files.
-</p>
-<p>
-You can even use linked resources to overlap other resources in the workspace, so
-resources from one project can appear in another project.
-If you do want to have overlapping resources in your workspace, do so with caution.
-Keep in mind that this means changing a resource in one place will cause simultaneous 
-changes in the duplicate resource.  Deleting one duplicate resource will delete both!
-</p>
-<p>
-Special rules apply when manipulating linked resources.  Since they must be located
-directly below a project, you cannot copy or move linked resources into other folders.
-Deleting a linked resource will <em>not</em> cause the corresponding resource
-in the file system to be deleted.  However, deleting child resources of linked folders
-<em>will</em> cause them to be removed from the file system.
-</p>
-<p>
-Some plug-ins built on top of the Eclipse platform are not compatible with linked resources.
-If this is the case, you can completely disable the linked resource feature to prevent them
-from being created in your workspace.  Linked resources can be disabled from the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.LinkedResources)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>General &gt; Workspace &gt; Linked Resources</b></a> preference page.
-Certain types of projects or team repository providers may also disallow linked resources
-from being created in some projects.</p>
-<p>
-
-<img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="concepts-2.htm">Workbench</a><br>
-<a href="cnav.htm">Navigator view</a><br>
-<a href="concepts-12.htm">Resources</a><br>
-<a href="concepts-17.htm">Resource hierarchies</a><br>
-</p>
-
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-45.htm">Creating linked resources</a><br>
-<a href="../tasks/tasks-67.htm">Deleting resources</a><br>
-<a href="../tasks/tasks-49.htm">Viewing resource properties</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br>
-  <a href="../reference/ref-14b.htm">Linked resources</a> 
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-17.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-17.htm
deleted file mode 100644
index c14110c..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-17.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Resource hierarchies</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Resource hierarchies</H1>
-<p CLASS="Head">Resources are stored and displayed in the Workbench in
-hierarchies.&nbsp; Described below are the terms used when referring to
-resources that are stored and displayed in a hierarchical structure.</p>
-<dl>
-  <dt>Root</dt>
-  <dd>The top level of the Workbench contents (in the file system).</dd>
-  <dt>Parent resource</dt>
-  <dd>Any resource that contains another resource. Only projects and folders can be parent resources.</dd>
-  <dt>Child resource</dt>
-  <dd>Any resource that is contained within another resource. Only files and folders can be child resources.</dd>
-</dl>
-<P>Resource hierarchies are displayed in the Navigator view, which is one of the
-default views in the Resource perspective.
-</P>
-
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><a href="cnav.htm"><br>
-</a><a href="concepts-12.htm">Resources
-</a><a href="cnav.htm"><br>
-Navigator view</a></p>
-
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-46ag.htm">
-Finding a resource quickly</a><a href="../tasks/tasks-46bg.htm"><br>
-Narrowing the scope of the Navigator view</a><a href="../tasks/tasks-48.htm"><br>
-Sorting resources in the Navigator view</a><a href="../tasks/tasks-48b.htm"><br>
-Showing or hiding files in the Navigator view</a></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-17a.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-17a.htm
deleted file mode 100644
index c8e4144..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-17a.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Local history</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Local history</H1>
-<p>A local edit history of a file is maintained when you create or modify a
-file. Each time you edit and save the file,&nbsp; a copy is saved so that you can replace the current
-file with a previous edit or even restore a deleted file.&nbsp; You can also
-compare the contents of all the local edits.&nbsp; Each edit in the local
-history is uniquely represented by the date and time the file was
-saved.&nbsp;&nbsp;</p>
-<p>Only files have local history; projects and folders do not.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="concepts-27.htm">Versions</a></p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-70.htm">Comparing resources with local history</a><br>
-<a href="../tasks/tasks-87.htm">Replacing a resource with local history</a><br>
-<a href="../tasks/tasks-87b.htm">Restoring deleted resources from local history</a><br>
-<a href="../tasks/tasks-88.htm">Setting local history preferences<br></a><br>
-<a href="../tasks/tasks-100.htm">Creating a version of a project</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-18.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-18.htm
deleted file mode 100644
index 04eda7d..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-18.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Toolbars in the Workbench</title>
-<meta name="keyword" content="shortcut bar">
-<meta name="keyword" content="fast view">
-</HEAD>
-
-<BODY>
-
-<H1 CLASS="Head">Toolbars </H1>
-
-<p CLASS="Para" Label="Type">There are four kinds of toolbars in the Workbench.</p>
-
-
-<p CLASS="Para" Label="Type">The <i> main toolbar</i>, sometimes called the Workbench toolbar,
-is displayed at the top of
-the Workbench window directly beneath the menu bar. The contents of this toolbar change based on the active perspective. Items in the toolbar
-might be enabled or disabled based on
-the state of either the active view or editor. Sections of the main toolbar can be rearranged using the mouse.
-</p>
-
-
-<p CLASS="Para" Label="Type">There are also individual <i>view toolbars</i>,
-which appear in the title
-bar of a view. Actions in a view's toolbar apply only to the view in which
-they appear. Some view toolbars include a <b>Menu</b> button, shown as an
-inverted triangle, that contain actions for that view.</p>
-<p CLASS="Head">A third type of toolbar is the perspective switcher.  The
-perspective switcher allows quick access to perspectives that are currently
-open.  It also has a button that can open new perspectives.  The perspective
-switcher is normally located in the top-right, next to the main toolbar.
-However, it is also possible to position it below the main toolbar
-("top-left"), or to position it vertically on the left-hand side of the
-workbench ("left").  The name of the perspectives is shown by default, but
-it is possible to hide the text and show only the icons.  To reposition the
-perspective or hide the text, right-click on it and choose the appropriate
-item from the context menu.</p>
-<p CLASS="Head">Finally, the fast view bar is a toolbar that contains icons representing 
-  the current set of fast views. A fast view is a shortcut to a view that is frequently 
-  used; see the section on fast views for more information. The fast view bar 
-  appears in the bottom left corner of the workbench by default. However, it is 
-  possible to position it on the left or right as well.</p>
-<p CLASS="Head">In all cases, you can find out what toolbar buttons do by moving
-your mouse pointer over the button and reading the tooltip that opens. See the
-list of related reference topics below for a table of all toolbar buttons.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="concepts-2.htm">Workbench<br>
-</a><a href="concepts-5.htm">Views</a>
-<a href="concepts-2.htm"><br>
-</a><a href="concepts-4.htm">Perspectives<br>
-</a><a href="concepts-21.htm">Fast views</a></p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-<a href="../tasks/tasks-9b.htm"><br>Creating fast views</a>
-<a href="../tasks/ttoolbars.htm"><br>Rearranging the main toolbar</a>
-</p>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-68.htm">Toolbar buttons</a></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-2.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-2.htm
deleted file mode 100644
index ea53750..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-2.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>The Workbench</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Workbench</H1>
-<P>The term <i>Workbench</i> refers to the desktop development environment. 
-The Workbench aims to achieve seamless tool integration and controlled openness by providing a common paradigm for the creation, management, and navigation of workspace resources.</P>
-
-
-<P>
-Each Workbench window contains one or more
-perspectives.&nbsp; Perspectives contain views and editors and control
-what appears in certain menus and tool bars.&nbsp; More than one Workbench window can exist
-on the desktop at any given time.</P>
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><a href="concepts-25.htm"><br>
-Features<br>
-</a><a href="concepts-12.htm">Resources</a><a href="concepts-4.htm"><br>
-Perspectives</a><a href="concepts-5.htm"><br>
-Views<br>
-</a><a href="concepts-6.htm">Editors<br>
-</a><a href="concepts-27c.htm">CVS Repositories</a></P>
-
-
-<P><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><a href="../tasks/tasks-34.htm"><br>
-Installing new features with the update manager</a><a href="../tasks/tasks-9f.htm"><br>
-Opening perspectives<br>
-</a><a href="../tasks/tasks-3.htm">Opening views</a><br>
-<a href="../tasks/tasks-28.htm">Switching between perspectives</a><br>
-<a href="../tasks/tasks-9k.htm">Configuring perspectives</a></P>
-
-
-<P><img border="0" src="../images/ngrelr.png" alt="Related reference" ><a href="../reference/ref-68.htm"><br>
-Toolbar buttons</a></P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-21.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-21.htm
deleted file mode 100644
index 3fb5702..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-21.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Fast views</title>
-<meta name="keyword" content="shortcut bar">
-
-</HEAD>
-<body>
-<H1 CLASS="Head">
-Fast views</H1>
-<P CLASS="Para" Label=Type>
-   Fast views are hidden views that can be quickly opened and closed. They work
-   like other views except they do not take up space in your Workbench window.&nbsp;</P>
-<P CLASS="Para" Label=Type> Fast views are represented by toolbar buttons on the 
-  <i>fast view bar</i>, which is the horizontal toolbar initially on the bottom 
-  left of the Workbench window. When you click the toolbar button for a fast view, 
-  that view opens temporarily in the current perspective. As soon as you click 
-  outside that view, it is hidden again. The fast view bar can also be docked 
-  on the right and left side of the Workbench window.</P>
-<P CLASS="Para" Label=Type>
-You can create a new fast view by dragging any open view to the
-shortcut bar or by selecting <b>Fast View</b> from the menu that opens when you
-click the icon at the left end of the view's title bar.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="concepts-2.htm">Workbench</a><a href="concepts-18.htm"><br>
-Toolbars</a></P>
-
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-9b.htm">Creating fast views</a><a href="../tasks/tasks-3e.htm"><br>
-Moving and docking views</a><br>
-<a href="../tasks/tasks-3i.htm">Maximizing a view or editor</a></P>
-
-
-</body>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-22.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-22.htm
deleted file mode 100644
index 091128f..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-22.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Builds</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Builds</H1>
-<p CLASS="Head">
-A <i>build</i> is a process that derives new resources from existing ones, updates existing resources, or both.&nbsp;</p>
-<p CLASS="Head">
-In the Workbench,&nbsp;different <i>builders</i> are invoked for different types
-of projects. For example, when a build is triggered for a Java project, a Java
-builder converts each Java source file (.java files) into one or more executable class files
-(.class files). Builders usually enforce the constraints of some
-domain. For example, a Web link builder could update links to files
-whose name/location changes.</p>
-
-<p CLASS="Para" Label="Type">There are two kinds of builds:&nbsp;</p>
-<ul>
-  <li>
-    <p CLASS="Para" Label="Type">An <i>incremental build</i> leverages a
-    previously built state and applies the transforms of the configured builders
-    to the resources that have changed since the previous state was computed
-    (that is, since the last build).</p></li>
-  <li>
-    <p CLASS="Para" Label="Type">A clean build discards any problems and 
-    previously built state.  The next build after a clean will transform all resources according to
-    the domain rules of the configured builders.</p></li>
-</ul>
-<p>Incremental and clean builds can be done over a specific set of projects or
-the workspace as a whole.&nbsp;Specific files and folders cannot be built. There are two ways that builds can be performed:</p>
-<ul>
-  <li> Automatic builds are performed as resources are saved. Automatic builds 
-    are always incremental and always operate over the entire workspace. You can 
-    configure your preferences
-    (<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workspace)")'>
-    <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-    <b>Window &gt; Preferences &gt; General &gt; Workspace</b></a>) to 
-    perform builds automatically on resource modification.&nbsp;</li>
-  <li>
-Manual builds are initiated when you explicitly select a menu item or press the
-equivalent shortcut key. Manual builds can be either clean or incremental and can operate over collections of projects 
-or the entire workspace.</li>
-</ul>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br><a href="concepts-exttools.htm">External tools</a>
-</p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-<br><a href="../tasks/tasks-73.htm">Building resources</a>
-<br><a href="../tasks/tasks-75.htm">Performing builds manually</a>
-<br><a href="../tasks/tasks-16.htm">Performing builds automatically</a>
-<br><a href="../tasks/tasks-17.htm">Saving resources automatically before a manual build</a><a href="../tasks/tasks-14.htm"><br>
-Changing build order</a></p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-25.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-25.htm
deleted file mode 100644
index b0fe9e9..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-25.htm
+++ /dev/null

@@ -1,84 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Features</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head" dir="ltr">
-Features</H1>
-
-<p>On disk, an Eclipse based product is structured as a collection of <em>plug-ins</em>.
-Each plug-in contains the code that provides some of the product's
-functionality. The code and other files for a plug-in are installed on the local
-computer, and get activated automatically as required. A product's plug-ins are
-grouped together into features. A <em>feature</em> is the smallest unit of separately downloadable and installable
-functionality. (The notion of a feature was new for Eclipse 2.0; it replaced the similar
-notion of component in Eclipse 1.0.) </p>
-<p>The fundamentally modular nature of the Eclipse platform makes it easy 
-to install additional features and plug-ins into an Eclipse based
-product, and to update the product's existing features and plug-ins. You 
-can do this either by using traditional native installers running separately from Eclipse,
-or by using the Eclipse platform's own update manager. The Eclipse <em>update
-manager</em> can be used to discover, download, and install updated features and
-plug-ins from special web based Eclipse update sites.</p>
-<p>The basic underlying mechanism of the update manager is simple: the files for a feature or
-plug-in are always stored in a sub-directory whose name includes a version
-identifier (e.g., &quot;2.0.0&quot;). Different versions of a feature or plug-in
-are always given different version identifiers, thereby ensuring that 
-multiple versions of the same feature or plug-in can co-exist on
-disk. This means that installing or updating features and plug-ins requires
-adding more files, but never requires deleting or overwriting existing files.
-Once the files are installed on the local computer, the new feature and plug-in
-versions are available to be configured. The same installed base of files is
-therefore capable of supporting many different <em>configurations</em>
-simultaneously; installing and upgrading an existing product is reduced to
-formulating a configuration that is incrementally newer than the current one. Important
-configurations can be saved and restored to active service in the
-event of an unsuccessful upgrade.</p>
-
-<p>Large Eclipse based products can organize their features into trees starting
-from the root feature that represents the entire product. This root feature then
-includes smaller units of functionality all the way down to leaf features that
-list one or more plug-ins and fragments. The capability to group feature
-hierarchically allows products to be stacked using a 'Russian doll' approach - a
-large product can build on top of a smaller one by including it and adding more
-features.</p>
-
-<p>Some included features may be useful add-ons but not vital to the proper
-functioning of the overall product. Feature providers can elect to mark them as <b>optional</b>.
-When installing optional features, users are provided with a choice of whether
-they want them or not. If not installed right away, optional features can be
-added at a later date.</p>
-
-<p>The <b>About</b> option on the <b>Help</b> menu provides information about installed features and plug-ins. 
-The <b>Software Updates</b> submenu on the <b>Help</b> menu groups together items for updating existing features, and 
-for finding, downloading, and installing new features.
-</p>
-
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="concepts-2.htm">Workbench</a></P>
-
-<P>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-<br><a href="../tasks/tasks-33.htm">Inspecting the current configuration</a>
-<br><a href="../tasks/tasks-34.htm">Installing new features with the update manager</a>
-<br><a href="../tasks/tasks-35.htm">Configuration operations</a>
-<br>
-  <a href="../tasks/tasks-36.htm">Updating features with the update manager</a> 
-  <br>
-  <a href="../tasks/tasks-37.htm">Update policy</a>
-<br><a href="../tasks/tasks-38.htm">Restoring a saved configuration</a>
-</P>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-26.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-26.htm
deleted file mode 100644
index 44de9cf..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-26.htm
+++ /dev/null

@@ -1,198 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-             
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-             
-  <meta http-equiv="Content-Style-Type" content="text/css">
-              
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>Team programming with CVS</title>
-                       
-  <meta name="keyword" content="team">
-</head>
-  <body style="background-color: rgb(255,255,255);">
-       
-<h1 class="Head">Team programming with CVS</h1>
-       
-<p class="Para">In the Concurrent Versions System (CVS) team programming environment,
-   team members do all of their work in their own Workbenches, isolated from
-others.    Eventually they will want to share their work. They do this via
-a CVS Repository.</p>
-       
-<h2 class="Para">Branches</h2>
-       
-<p class="Para">CVS uses a branch model to support multiple courses of work 
- that    are somewhat isolated from each other but still highly interdependent. 
- Branches    are where a development team shares and integrates ongoing work. 
- A branch can    be thought of as a shared workspace that is updated by team 
- members as they    make changes to the project. This model allows individuals 
- to work on a CVS    team project, share their work with others as changes 
- are made, and access the    work of others as the project evolves. A special 
- branch, referred to as HEAD,    represents the main course of work in the 
-repository (HEAD is often referred    to as the trunk).</p>
-       
-<h2 class="Para">Sharing work</h2>
-       
-<div class="Topic">      
-<p class="Para">As team members produce new work, they share this work by 
- <i>committing</i>      those changes to the branch. Similarly, when they 
-wish to get the latest available      work, they <i>update</i> their local 
-workspaces to the changes on the branch.&nbsp;      Thus the branch is constantly 
-changing, moving forward as team members submit      new work.</p>
-         
-<p class="Para">The branch effectively represents the current state of the 
- project.      At any point a team member can update their workspaces from the branch and know
- they are up      to date.</p>
-         
-<div class="Figure">        
-<div> <img src="../images/ref-9.png"
- alt="Interaction with Branches and Workbenches" >
-        </div>
-      </div>
-         
-<div class="XRefList">   </div>
-    </div>
-       
-<div class="Topic">      
-<h2>Optimistic team model</h2>
-         
-<p class="Para">CVS provides two important features required for working in
-     a team:</p>
-         
-<ul>
-        <li>                      
-    <p class="Para">A history of the work submitted by the team     </p>
-     </li>
-     <li>                      
-    <p class="Para">A way to coordinate and integrate this work   </p>
-     </li>
-     
-</ul>
-         
-<p class="Para">Maintaining history is important so that one can compare the
-     current work against previous drafts, revert to older work that is better, and
-so on.      Coordinating the work is critical so that there exists one definition
-of the      current project state, containing the integrated work of the
-team. This coordination      is provided via the branch model.</p>
-         
-<p class="Para">An optimistic model is one where any member of the team can 
-      make changes to any resource he or she has access to.&nbsp; Because 
-two team      members can commit to the branch changes to the same resource, 
- conflicts      can occur and must be dealt with. This model is termed <i>
-   optimistic</i> because      it is assumed that conflicts are rare.</p>
-         
-<h2>Recommended work flow</h2>
-         
-<p class="Para">Usually resources do not exist in isolation, they typically
-    contain implicit or explicit dependencies on other resources.&nbsp; For
-    example, Web pages have links to other Web pages, and source code has
-  references to artifacts described in other source code resources.&nbsp; 
- No   resource is an island.</p>
-         
-<p class="Para">As resources are committed to the branch, these dependencies 
-      can be affected. Ensuring the integrity of the dependencies is important 
- because      the branch represents the current project state: at any point 
- a team member      could take the branch contents as a basis for new work.</p>
-         
-<p class="Para">The ideal work flow therefore is one in which the branch integrity
-     is preserved. </p>
-
-<a name="IdealWorkFlow">
-<h3 class="Para">Ideal flow enumerated</h3>
-</a>
-
-<p class="Para">The ideal work flow proceeds as follows:</p>
-         
-<ol>
-        <li>                      
-    <p class="Para">Start fresh. Before starting work, update the resources
-    in the workspace with 
- the          current branch state. If you are sure that you have no local 
- work that          you care about, the fastest way to get caught up is to 
- select the projects          you are interested in from the branch (or HEAD) 
- and select <b>Checkout</b> (or <b>Replace with &gt; Latest from Repository</b>
- if the projects already exist locally). This will overwrite your 
-local resources with those from          the branch.          </p>
-     </li>
-     <li>                      
-    <p class="Para">Make changes. Work locally in your Workbench, creating 
- new       resources, modifying existing ones, saving locally as you go. 
-   </p>
-     </li>
-     <li>                      
-    <p class="Para">Synchronize. When you are ready to commit your work, synchronize
-         with the repository.        </p>
-                 
-    <ol type="a">
-            <li>                                      
-        <p class="Para">Update. Examine incoming changes and add them to your
-             local Workbench. This allows you to determine if there are changes
-             which might affect the integrity of what you are about to commit.
-             Resolve conflicts. Retest, run integrity checkers (for example,
-check              for broken hypertext links, ensure your code compiles,
-and so on).                  </p>
-         </li>
-         <li>                                      
-        <p class="Para">Commit. Now that you are confident that your changes 
-              are well integrated with the latest branch contents, commit 
- your              changes to the branch. To be prudent, you may repeat the 
- previous              step if there are new incoming changes.           
-    </p>
-         </li>
-                 
-    </ol>
-        </li>
-         
-</ol>
-         
-<p class="Para">Of course this is an <i>ideal</i> workflow. Under certain 
- conditions      you may be confident that the incoming changes do not affect 
- you and choose      to commit without updating. However, in general team 
-members should make an      effort to follow a flow similar to the above in
-order to ensure that the branch      integrity is not accidentally compromised.&nbsp;
-    </p>
-     
-<p class="Para">You can find more information on CVS at <a
- href="https://www.cvshome.org" class="URL" target="_blank">https://www.cvshome.org.</a>
-    </p>
-   </div>
-        
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br><a href="concepts-27c.htm">CVS Repositories</a>
-<br><a href="concepts-27b.htm">Branches</a>
-<br><a href="concepts-27.htm">Versions</a>
-<br><a href="concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-         
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-   <a href="../tasks/tasks-92.htm"><br>
-    Creating a CVS repository location</a><a
- href="../tasks/tasks-96.htm"><br>
-    Checking out a project from a CVS repository</a>&nbsp;<a
- href="../tasks/tasks-103.htm"><br>
-    Replacing resources in the Workbench</a><a
- href="../tasks/tasks-117.htm"><br>
-    Sharing a new project using CVS</a><a href="../tasks/tasks-115.htm"><br>
-    Synchronizing with the repository</a><a
- href="../tasks/tasks-113.htm"><br>
-    Updating</a><a href="../tasks/tasks-113b.htm"><br>
-    Resolving conflicts </a><a href="../tasks/tasks-100b.htm"><br>
-    Merging from a branch</a><a href="../tasks/tasks-114.htm"><br>
-    Committing</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- >
- <br><a href="../reference/ref-47.htm">CVS</a>
-</p>
-           
-
-        
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-27.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-27.htm
deleted file mode 100644
index cdec6f0..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-27.htm
+++ /dev/null

@@ -1,81 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-     
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-     
-  <meta http-equiv="Content-Style-Type" content="text/css">
-      
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>Versions</title>
-         
-  <meta name="keyword" content="team">
-</head>
-  <body style="background-color: rgb(255,255,255);">
-   
-<h1 class="Head"> Versions</h1>
-   
-<p class="Para"> Resources are versioned in order to capture a snapshot 
-  of the current state of the resources at one specific point in time. Resources
-   in CVS are versioned by tagging them with a version label. When a resource
-is    versioned, it means that a non-modifiable copy of it can be retrieved
-from the    repository. </p>
-   
-<p class="Intro">Versioning a project saves the line up of all resource versions 
-   in the project. Resources other than projects (files and folders) 
-can    be versioned.&nbsp; However, it is more common to version entire projects 
-together    as the resources contained in a project are often highly interdependent. 
-Projects    can be versioned from the workspace or from the branch (including HEAD) in the 
-CVS Repositories    view. The difference between these two approaches is in
-deciding which child    resource versions should be part of the project version.
- </p>
- 
-<p class="Para"> When tagging a project as a version from the <i>Workbench</i>,    the base revisions of the files in the Workbench are tagged as belonging 
-to    that version.&nbsp; This is the preferred method of versioning a project 
-because    you know exactly which file revisions will be in the version.&nbsp;This 
-operation    is allowed if you have outgoing changes or uncommitted changes. 
-Uncommitted    changes are simply ignored and resources with outgoing changes 
-can still have    their base revisions be part of the version.&nbsp; Versioning 
-a project with    uncommitted or outgoing changes is handy if you have to 
-split the project at    the point where you started making changes to the 
-resources and commit the resources    to another branch.</p>
-   
-<p class="Para"> When tagging a project as a version from a <i>branch</i>
-  in the    CVS Repositories view, you are versioning whatever the latest 
-resource versions    are in the branch at that moment in time.&nbsp; You should
-not version your    projects from the branch if you do not know what is committed
-in the branch.    For this reason, versioning from the Workbench is often
-preferable.</p>
-     
-<p class="Para"> <img border="0" src="../images/ngrelc.png"
- alt="Related concepts" >
-  <br>
- <a href="concepts-27c.htm">CVS Repositories</a> <br>
- <a href="concepts-27b.htm">Branches</a> <br>
- <a href="concepts-17a.htm">Local history</a> <br>
- <a href="concepts-12.htm">Resources</a> </p>
-    
-<p class="Para"> <img border="0" src="../images/ngrelt.png"
- alt="Related tasks" >
-  <br>
- <a href="../tasks/tasks-100.htm">Creating a version of a project</a> <br>
- <a href="../tasks/tasks-118.htm">Versioning projects in the repository</a>
-  <br>
- <a href="../tasks/tasks-107b.htm">Enabling the CVS resource decorations</a><BR>
-  <a href="../tasks/tasks-105c.htm">Moving version tags</a><br>
-  </p>
-    
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- >
-  <br>
- <a href="../reference/ref-47.htm">CVS</a> </p>
-    
-
-     
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-27b.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-27b.htm
deleted file mode 100644
index 6b19d78..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-27b.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Branches</title>
-<meta name="keyword" content="team">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>Branches</H1>
-
-<p>In CVS, teams share and integrate their ongoing work in <i>branches</i>. Think 
-  of a branch as a shared work area that can be updated at any time by team members. 
-  In this way, individuals can work on a team project, share their work with others 
-  on the team, and access the work of others during all stages of the project. 
-  The branch effectively represents the current shared state of the project. 
-</p>
-<p>Resources can be changed in the Workbench without affecting the branch. 
-  Individuals must explicitly provide their changed resources to the branch.
-</p>
-<p>Every CVS repository has at least one branch, referred to as HEAD. Under 
-  certain conditions, more than one branch may exist in a repository. For 
-  example, one branch may be for ongoing work, and another branch may be for maintenance 
-  work.&nbsp; </p>
-<p>As you make changes locally in your Workbench, you are working alone. When you are ready to make your local resource changes 
-  available to other team members, you'll need to <i>commit</i> your work to 
-  the branch. All such changes are classified as outgoing changes when you do a synchronization. 
-</p>
-  
-<p>Ideally, you should update your local workspace with any changes others have 
-  made in a branch before committing to it. This ensures that you have the very 
-  latest work from the other team members. After you have updated from the branch, 
-  merged any conflicting changes in your local Workbench, and tested your changes 
-  locally, you can more easily commit your Workbench's changes to the branch.</p>
-
-  
-<p>When you commit changes to the branch, your changes are copied from your local 
-  Workbench to the branch. As a result, these changes are then seen as incoming 
-  changes when other developers update from the branch later.</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br><a href="concepts-26.htm">Team programming with CVS</a>
-<br><a href="concepts-27c.htm">CVS Repositories</a>
-<br><a href="concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><a href="../tasks/tasks-92.htm"><br>
-  </a><a href="../tasks/tasks-96.htm"> Checking out a project from a CVS repository</a>&nbsp;<a href="../tasks/tasks-117.htm"><br>
-  Sharing a new project using CVS</a><a href="../tasks/tasks-100a.htm"><br>
-Branching</a><a href="../tasks/tasks-115.htm"><br>
-Synchronizing with the repository</a><a href="../tasks/tasks-113.htm"><br>
-Updating</a>
-<br><a href="../tasks/tasks-114.htm">Committing</a>
-<br><a href="../tasks/tasks-113b.htm">Resolving conflicts </a>
-</p>
-
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="../reference/ref-47.htm">CVS</a>
-<br><a href="../reference/ref-32.htm">CVS Repositories view</a>
-</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-27c.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-27c.htm
deleted file mode 100644
index 2433e6c..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-27c.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
- 
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
- 
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>CVS Repositories</title>
-  
-  <meta name="keyword" content="team">
-</head>
-  <body bgcolor="#ffffff">
- 
-<h1 class="Head">CVS Repositories</h1>
- 
-<p class="Intro"> </p>
-<p class="Para"> A Concurrent Versions System (CVS) repository is a persistent
-   data store that coordinates multi-user access to projects and their contents.
-   Projects in a repository can be of two forms: immutable (a project version)
-   or modifiable (a project in a branch). Communication between the repository
-   and Workbench clients is possible over local or wide area networks.&nbsp;
-Currently    the Workbench supports two internal authentication protocols
-for CVS: pserver    and ssh. Authentication protocols provided by external
-tools can also be used    by CVS.</p>
- 
-<div class="Topic"> 
-<p class="Para"> You can find more information on CVS at <a
- href="https://www.cvshome.org" class="URL" target="_blank">https://www.cvshome.org.</a></p>
- </div>
-   
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"
- >
-<br>
- <a href="concepts-26.htm">Team programming with CVS</a> <a
- href="concepts-27b.htm"><br>
- Branches</a><a href="concepts-27.htm"><br>
- Versions<br>
- </a><a href="concepts-17a.htm">Local history</a></p>
-   
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"
- >
- <br>
-<a href="../tasks/tasks-92.htm">Creating a CVS repository location</a> </p>
-   
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- >
-<br><a href="../reference/ref-47.htm"> CVS</a> <br>
-<a href="../reference/ref-32.htm">CVS Repositories view</a> </p>
-  
-
-  
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-29.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-29.htm
deleted file mode 100644
index a62f8a5..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-29.htm
+++ /dev/null

@@ -1,87 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-         
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-         
-  <meta http-equiv="Content-Style-Type" content="text/css">
-          
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>Three way comparisons</title>
-    
-</head>
-  <body style="background-color: rgb(255,255,255);">
-     
-<h1 class="Head"> Three way comparisons </h1>
-     
-<p class="Para"> Three way comparisons show the differences between three different 
-  versions of a resource.&nbsp;This feature is most useful when merging resources 
-  or when there is a conflict during synchronization.&nbsp;Conflicts occur when 
-  two developers add a version from the same branch to their Workbench, then each 
-  developer modifies it, then one developer attempts to commit the resource after 
-  the other developer has already committed it.&nbsp; </p>
-     
-<p class="Para"> When this situation arises, you can view the differences between 
-  three resource versions: the resource in the Workbench, the version of the resource 
-  that is committed in the branch, and the <i> common ancestor</i> from which the 
-  two conflicting versions are based.&nbsp;&nbsp;If a common ancestor cannot 
-  be determined, for example because a resource with the same name and path was 
-  created and committed by two different developers, the comparison becomes a 
-  two-way comparison. </p>
-<h2>Interpreting compare results</h2>
-<p>The Synchronize view allows you to view the differences between two or three 
-  files. If a common ancestor is available, the sync view performs a three way 
-  comparison. It is possible that a common ancestor for two conflicting resource 
-  versions cannot be determined, (e.g. a resource with the same name and path 
-  is created and committed by two different developers). In this case the compare 
-  becomes a regular two way compare.&nbsp;&nbsp;</p>
-<p class="Para">In a three way compare the Workbench shows you: </p>
-<ul class="UnorderedList">
-  <li class="Item"> what has been changed in the first child in comparison to 
-    the common ancestor.&nbsp;</li>
-  <li class="Item"> what has been changed in the second child in comparison to 
-    the common ancestor.</li>
-</ul>
-
-<p class="Para"> In the picture below, the common ancestor is displayed in the top pane of the text 
-  compare pane.&nbsp; The differences that you see 
-  highlighted are what has changed in the Workbench resource as compared to the 
-  common ancestor, and what has been changed in the branch resource as compared 
-  to the common ancestor. The sections that differ in all three files are highlighted 
-  as differences.&nbsp;Conflicts are shown in red, incoming changes in blue, and 
-  outgoing changes in gray. </p>
-  
-<p class="Para"> <img src="../images/Image49_3_way_compare.png" alt="Synchronize View with 3 way compare" border="0" >
-   </p>
-       
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"
- >
-<br><a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a></p>
-       
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"
- >
-  <a href="../tasks/tasks-92.htm"><br>
-   </a><a href="../tasks/tasks-68.htm">Comparing resources</a> <a
- href="../tasks/tasks-115.htm"><br>
-   Synchronizing with a repository<br>
-  </a><a href="../tasks/tasks-68dg.htm">Merging changes in the compare editor</a><a
- href="../tasks/tasks-113.htm"><br>
-   </a><a href="../tasks/tasks-113b.htm"> Resolving conflicts</a><a
- href="../tasks/tasks-68b.htm"><br>
-   Setting preferences for comparing files</a>&nbsp;<a
- href="../tasks/tasks-101.htm"><br>
-   Comparing resources with repository versions</a> </p>
-       
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="../reference/ref-25.htm">Compare editor</a>
-<br><a href="../reference/ref-33.htm">CVS Synchronize view</a>
-</p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-30.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-30.htm
deleted file mode 100644
index 1ac346a..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-30.htm
+++ /dev/null

@@ -1,77 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-     
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-     
-  <meta http-equiv="Content-Style-Type" content="text/css">
-      
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>Synchronizing with a CVS repository</title>
-   
-</head>
- <body style="background-color: rgb(255,255,255);">
-   
-<h1 class="Head"> Synchronizing with a CVS repository</h1>
-   
-<p class="Para"> In the CVS team programming environment, there are    two
-distinct processes involved in synchronizing resources: <i>updating</i> 
-   with the latest changes from a branch and <i>committing</i> to the branch.&nbsp;</p>
-   
-<p class="Para">When you make changes in the Workbench, the resources   
-are saved locally.&nbsp; Eventually you will want to commit your changes
-to the branch so others can have access to them.&nbsp; Meanwhile, others
-may have committed changes to the branch.&nbsp; You will want to update
-your Workbench resources with their changes.</p>
-   
-<p class="Para"><b>Important!</b>: It is preferable to update <i> before</i>
-    committing, in case there are conflicts with the resources in your Workbench
-   and the resources currently in the branch.&nbsp;&nbsp;</p>
-   
-<p>The synchronize view contains filters to control whether you want to view only 
-  i<i>ncoming changes</i> or <i>outgoing changes</i>. Incoming changes come from 
-  the branch. If accepted, they will update the Workbench resource to the latest 
-  version currently committed into the branch. Outgoing changes come from the 
-  Workbench. If committed, they will change the branch resources to match those 
-  currently present in the Workbench. </p>
-     
-<p>Regardless of which mode (filter) you select, the Synchronize view always 
-shows    you conflicts that arise when you have locally modified a resource 
-for which    a more recent version is available in the branch. In this 
-situation you    can choose to do one of three things: update the resource 
-from the branch, commit    your version of the resource to the branch, or 
-merge your work with the changes    in the branch resource. Typically 
-you will want to merge, as the other    two options will result in loss of 
-work. </p>
-     
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"
- >
- <br>
-  <a href="concepts-26.htm">Team programming with CVS</a>
-  <a href="concepts-27b.htm"><br>Branches</a>
-</p>
-     
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"
- >
- <a href="../tasks/tasks-115.htm"><br>
-  Synchronizing with the repository</a><a href="../tasks/tasks-113.htm"><br>
-Updating</a><a href="../tasks/tasks-113b.htm"><br>
-  Resolving conflicts</a><a href="../tasks/tasks-100b.htm"><br>
-  Merging from a branch</a><a href="../tasks/tasks-114.htm"><br>
-Committing</a> </p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="../reference/ref-47.htm">CVS</a>
-<br><a href="../reference/ref-33.htm">CVS Synchronize view</a>
-</p>
-   
-
-
-     
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-4.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-4.htm
deleted file mode 100644
index 21d6b23..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-4.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Perspectives</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Perspectives</H1>
-<p CLASS="Para" Label="Type">Each Workbench window contains one or more
-perspectives. A perspective defines the initial set and layout of views
-in the Workbench window. Within the window, each perspective shares the same set
-of editors. Each perspective provides a set of functionality aimed
-at accomplishing a specific type of task or works with specific types of
-resources.&nbsp;For example, the Java perspective combines views that you would
-commonly use while editing Java source files, while the Debug perspective
-contains the views that you would use while debugging Java programs. As you work
-in the Workbench, you will probably switch perspectives frequently.</p>
-<P CLASS="Para" Label=Type>Perspectives control what appears in certain menus
-and toolbars. They define visible <i> action sets</i>, which you
-can change to customize a perspective. You can save a perspective that you
-build in this manner, making your own custom perspective that you can open again
-later.&nbsp;&nbsp;</p>
-<P CLASS="Para" Label=Type>You can use the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Perspectives)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>General &gt; Perspectives</b></a>
-preference page to open perspectives 
-in the same window or in a new window.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="concepts-2.htm">Workbench</a><br>
-<a href="concepts-6.htm">Editors</a><br>
-<a href="concepts-5.htm">Views</a></p>
-<P CLASS="Para" Label=Type><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><a href="../tasks/tasks-9f.htm"><br>
-Opening perspectives<br>
-</a><a href="../tasks/tasks-3.htm">Opening views</a><br>
-<a href="../tasks/tasks-24.htm">Changing where perspectives open<br></a>
-<a href="../tasks/tasks-31.htm">Specifying the default perspective</a><br>
-<a href="../tasks/tasks-28.htm">Switching between perspectives</a><br>
-<a href="../tasks/tasks-9k.htm">Configuring perspectives</a><br>
-  <a href="../tasks/tasks-9i.htm">Saving a user defined perspective</a><a href="../tasks/tasks-9j.htm"><br>
-Resetting perspectives</a></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-5.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-5.htm
deleted file mode 100644
index 3211465..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-5.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Views</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Views</H1>
-<P CLASS="Para" Label=Type> Views support editors and provide alternative presentations 
-  as well as ways to navigate the information in your Workbench.&nbsp; For example, 
-  the Navigator and other navigation views display projects and other resources that you are working 
-  with.</P>
-<P CLASS="Para" Label=Type>
- Views also have their own menus. To open the menu for a view, click the icon at the left
-end of the view's title bar. Some views also have their own toolbars. The actions represented by buttons on view
-toolbars only affect the items within that view.&nbsp;</P>
-<P CLASS="Para" Label=Type>
-A view might appear by itself, or stacked with other
-views in a tabbed notebook.&nbsp;You can change the layout of a perspective by
-opening and closing views and by docking them in different
-positions in the Workbench window.&nbsp; </P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="concepts-4.htm">Perspectives</a><br>
-<a href="concepts-21.htm">Fast views</a><br>
-<a href="concepts-6.htm">Editors</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-3.htm">Opening views</a><br>
-<a href="../tasks/tasks-3e.htm">Moving and docking views</a><br>
-<a href="../tasks/tasks-9b.htm">Creating fast views</a><br>
-<a href="../tasks/tasks-3i.htm">Maximizing a view or editor</a><br>
-  <a href="../tasks/tasks-9i.htm">Saving a user defined perspective</a><br>
-<a href="../tasks/tasks-9j.htm">Resetting perspectives</a>
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-6.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-6.htm
deleted file mode 100644
index aebc0fe..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-6.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Editors and the editor area</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Editors</H1>
-<P CLASS="Para" Label=Type>
-Most perspectives in the Workbench are comprised of an editor area and one or more
-views. </P>
-<P CLASS="Para" Label=Type>You can associate different editors with different
-types of files. For example, when you open a file for editing by double-clicking
-it in one of the navigation views, the associated editor opens in the Workbench.
-If there is no
-associated editor for a resource, the Workbench attempts to launch an <i>external
-editor</i>  outside the Workbench. (On Windows, the Workbench will first
-attempt to launch the editor in place as an OLE document. This type
-of editor is referred to as an <i>embedded editor</i>. For example, if you have a
-.doc file in the Workbench and Microsoft Word is registered as the editor for .doc
-files in your operating system, then opening the file will launch Word as an OLE document within the Workbench editor
-area. The Workbench menu bar and toolbar will be updated with options for
-Microsoft Word.)&nbsp; </P>
-<P CLASS="Para" Label=Type>Any number of editors can be open at once, but only
-one can be active at a time. The main menu bar and toolbar for the
-Workbench window contain operations that are applicable to the active
-editor.&nbsp; </P>
-<P CLASS="Para" Label=Type>Tabs in the editor area indicate the names of
-resources that are currently open for editing. An asterisk (*) indicates that an editor has unsaved
-changes.&nbsp;&nbsp; </P>
-<P CLASS="Para" Label=Type>By default, editors are stacked in the editor area,
-but you can choose to tile them in order to view source files simultaneously.</P>
-<P CLASS="Para" Label=Type>
-Here is an example of a text editor in the Workbench:</P>
-<P CLASS="Para" Label=Type> 
-<img src="../images/Image5_text_editor.png" alt="Text editor" border="0"> </P>
-<P>&nbsp;The gray border at the left margin of the editor area may contain
-icons that flag errors, warnings, or problems detected by the system. Icons also
-appear if you have created bookmarks, added breakpoints for debugging, or
-recorded notes in the Tasks view. You can view details for any icons in the left
-margin of the editor by moving the mouse cursor over them.
-</P>
-
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><a href="concepts-2.htm"><br>
-Workbench<br>
-</a><a href="concepts-6a.htm">External editors</a><a href="cbookmrk.htm"><br>
-Bookmarks</a><a href="ctskview.htm"><br>
-Tasks view<br>
-</a><a href="cnav.htm">
-Navigator view</a></p>
-
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-46.htm">Opening files for editing</a><br>
-<a href="../tasks/tasks-51.htm">Associating editors with file types</a><br>
-<a href="../tasks/tasks-52.htm">Editing files outside the Workbench</a></p>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-6a.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-6a.htm
deleted file mode 100644
index b0a28ca..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-6a.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>External editors</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-External editors</H1>
-<P CLASS="Para" Label=Type>Sometimes you may need to use an external program to
-edit a file in the Workbench. This can occur, for example, when the Workbench
-has no editor for that file type.</P>
-<P CLASS="Para" Label=Type>The external program will be used if that program is
-registered as the system default editor for that file type and no other editor
-is registered for that file type in the Workbench. For example, on most systems the default
-&quot;editor&quot; for HTML files is a Web browser. If there is no other editor
-associated with .htm and .html files in the Workbench, then opening an HTML file from the
-Workbench would cause the file to be opened in a separate browser session.</P>
-<P CLASS="Para" Label=Type><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><a href="concepts-2.htm"><br>
-</a><a href="concepts-6.htm">
-Editors</a></P>
-<P CLASS="Para" Label=Type>&nbsp;<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-46.htm">Opening files for editing</a><br>
-<a href="../tasks/tasks-51.htm">Associating editors with file types</a><br>
-<a href="../tasks/tasks-52.htm">Editing files outside the Workbench</a></P>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-activites.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-activites.htm
deleted file mode 100644
index b98aec3..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-activites.htm
+++ /dev/null

@@ -1,30 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Activities</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Activities</h2>
-<P CLASS="Para">Activities, also referred to as Capabilities, are plug-ins logically 
-  grouped to provide functionality and improve scalability. Welcome page selections 
-  determine what activities are enabled, but activities can also later be enabled 
-  or disabled using the preference page. When an activity is enabled, the actions 
-  associated with that activity are available to the user, however once an activity 
-  is disabled those actions are no longer visible in menus, wizards and so on. 
-  Should the user attempt to employ an action that has been disabled a prompt 
-  will appear confirming the enablement of the action, thus providing new functions 
-  to the Workbench as they are required by the user. </P>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-  <a href="../tasks/tasks-activites.htm">Activities Example</a><br>
-</P>
-<p> <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-  <a href="../reference/ref-activitiespref.htm">Capabilities</a></P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-antsupport.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-antsupport.htm
deleted file mode 100644
index 7dfa3b4..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-antsupport.htm
+++ /dev/null

@@ -1,61 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Ant support</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Ant support</H1>
-<P CLASS="Para">
-Apache Ant is an open source, Java-based build tool. &nbsp;See <a href="http://ant.apache.org" target="_blank">http://ant.apache.org</a>
-for more details.  </P>
-<P CLASS="Para">
-The Ant support allows you to create and run Ant buildfiles from the Workbench.&nbsp;
-These Ant buildfiles can operate on resources in the file system as well as
-resources in the workspace. 
-</P>
-<P CLASS="Para">
-Output from an Ant buildfile is displayed in the console view in the same hierarchical
-format seen when running Ant from the command line. Ant tasks (for example "[mkdir]")
-are hyperlinked to the associated Ant buildfile, and javac error reports are hyperlinked
-to the associated Java source file and line number.
-</P>
-<P CLASS="Para">
-You can add classes to the Ant classpath and add Ant tasks and types from the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ant.ui.AntRuntimePreferencePage)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Ant &gt; Runtime</b></a> preference page.
-</P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-22.htm">Builds</a><br>
-<a href="../concepts/concepts-exttools.htm">External tools</a>
-</p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-ant-running.htm">Running Ant buildfiles</a><br>
-<a href="../tasks/tasks-ant-classpath.htm">Modifying the Ant classpath</a><br>
-<a href="../tasks/tasks-ant-addtasksandtypes.htm">Adding new Ant tasks and types</a><br>
-<a href="../tasks/tasks-ant-version.htm">Using a different version of Ant</a><br>
-<a href="../tasks/antRunner.htm">antRunner application entry point</a>
-</p>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-antprefs.htm">Ant preferences</a><br>
-<a href="../reference/ref-anteditorprefs.htm">Ant editor preferences</a><br>
-<a href="../reference/ref-antruntimeprefs.htm">Ant runtime preferences</a><br>
-<a href="../reference/ref-antview.htm">Ant view</a><br>
-<a href="../reference/ref-anteditor.htm">Ant editor</a><br>
-<a href="../reference/ref-anticons.htm">External Tools and Ant icons</a>
-</p>
-
-
-</BODY>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-cvs-watch.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-cvs-watch.htm
deleted file mode 100644
index c07e0fc..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-cvs-watch.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-     
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-     
-  <meta http-equiv="Content-Style-Type" content="text/css">
-      
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>CVS Watch/Edit</title>
-   
-</head>
- <body style="background-color: rgb(255,255,255);">
-<h1 class="Head"> Watch/Edit</h1>
-   
-<p class="Para"> CVS provides a notification scheme which allows a group of developers 
-  to know if somebody is working on a given file. This facility is known as <em>watches</em>. 
-  By setting a <em>watch</em> on a file, you can have CVS notify you via email 
-  if someone else starts to <em>edit</em> this file. This mechanism is notification 
-  based only; the file is not locked in any way on the server, and several people 
-  are allowed to edit the same file at the same time.</p>
-<p class="Para">In addition to watch list notification, <em>edit</em> on its own 
-  is useful for discovering if others are also editing that file. This is because 
-  when you edit a file, you will be informed if someone else is already editing 
-  it. </p>
-<p class="Para">Normally with CVS clients, an explicit <em>edit</em> would need 
-  to be issued by the user. With Team CVS support however, an <em>edit</em> is 
-  automatically issued by the client when you start to modify a file. In addition, 
-  when <em>editing</em> a file, Team CVS provides you with the list of people 
-  already editing a file. This allows you to find out who is working on a file 
-  before you start to edit it.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"
- >
- <br>
-  <a href="concepts-26.htm">Team programming with CVS</a> </p>
-     
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"
- > <a href="../tasks/tasks-cvs-watch.htm"><br>
-  Finding out who's working on what: watch/edit</a></p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br>
-  <a href="../reference/ref-47.htm">CVS</a> </p>
-   
-
-     
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-exttools.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-exttools.htm
deleted file mode 100644
index 5495a4f..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-exttools.htm
+++ /dev/null

@@ -1,228 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta http-equiv="Content-Style-Type" content="text/css">
-   <meta name="Author" content="OTI Employee">
-   <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-   <title>External tools</title>
-<link REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-</head>
-<body bgcolor="#FFFFFF">
-
-<h1>
-External tools</h1>
-
-<p>External tools allow you to configure and run programs,
-batch files, Ant buildfiles, and others using the Workbench. You can save
-these external tool configurations and run them at a later time.</p>
-
-<p>Output from external tools is displayed in the console
-view.</p>
-
-<p>You can add external tools as part of the build process
-for a project. These external tools will run in the specified order every
-time a project is built.</p>
-
-<p>The following variables are available when you configure
-an external tool. These variables are automatically expanded each time
-the external tool is run.</p>
-
-<blockquote>
-<p><b>${workspace_loc}</b> - The absolute path on the system's
-hard drive to Eclipse's workspace directory.</p>
-
-<p><b>${workspace_loc:<i>&lt;resource path></i>}</b> - The
-absolute path on the system's hard drive to the specified resource. The
-<i>&lt;resource
-path></i> is the full path of the resource relative to the workspace root.
-For example ${workspace_loc:/MyProject/MyFile.txt}. Note that the expanded
-result of this variable is not the same as ${workspace_loc}/MyProject/MyFile.txt
-if the project's contents directory for MyProject is outside the workspace
-directory.</p>
-
-<p><b>${project_loc}</b> - The absolute path on the system's
-hard drive to the currently selected resource's project or to the project
-being built if the external tool is run as part of a build.</p>
-
-<p><b>${project_loc:<i>&lt;resource path></i>}</b> - The
-absolute path on the system's hard drive to the specified resource's project.
-The
-<i>&lt;resource path></i> is the full path of the resource relative
-to the workspace root. For example ${workspace_loc:/MyProject/MyFile.txt}.
-Note that the expanded result of this variable is not the same as ${workspace_loc}/MyProject
-if the project's contents directory for MyProject is outside the workspace
-directory.</p>
-
-<p><b>${container_loc}</b> - The absolute path on the system's
-hard drive to the currently selected resource's parent (either a folder
-or project).</p>
-
-
-<p><b>${container_loc:<i>&lt;resource path></i>}</b> - The
-absolute path on the system's hard drive to the specified resource's parent
-(either a folder or project). The <i>&lt;resource path></i> is the full
-path of the resource relative to the workspace root. For example:${workspace_loc:/MyProject/MyFolder/MyFile.txt}.
-Note that the expanded result of this variable is not the same as ${workspace_loc}/MyProject/MyFolder
-if the project's contents directory for MyProject is outside the workspace
-directory.</p>
-
-<p><b>${resource_loc}</b> - The absolute path on the system's
-hard drive to the currently selected resource.</p>
-
-<p><b>${resource_loc:<i>&lt;resource path></i>}</b> - The
-absolute path on the system's hard drive to the specified resource. The
-<i>&lt;resource
-path></i> is the full path of the resource relative to the workspace root.
-For example ${workspace_loc:/MyProject/MyFile.txt}. Note that the expanded
-result of this variable is not the same as ${workspace_loc}/MyProject/MyFile.txt
-if the project's contents directory for MyProject is outside the workspace
-directory.</p>
-
-<p><b>${project_path}</b> - The full path, relative to the
-workspace root, of the currently selected resource's project or of the
-project being built if the external tool is run as part of a build.</p>
-
-<p><b>${container_path}</b> - The full path, relative to the
-workspace root, of the currently selected resource's parent (either a folder
-or project).</p>
-
-<p><b>${resource_path}</b> - The full path, relative to the
-workspace root, of the currently selected resource.</p>
-
-<p><b>${project_name}</b> - The name of the currently selected
-resource's project or of the project being built if the external tool is
-run as part of a build.</p>
-
-<p><b>${container_name}</b> - The name of the currently selected
-resource's parent (either a folder or project).</p>
-
-<p><b>${resource_name}</b> - The name of the currently selected
-resource.</p>
-
-<p><b>${build_type}</b> - The kind of build when the external
-tool is run as part of a build. The value can be one of "full", "incremental",
-or "auto". If the external tool is run outside of a build, the value is
-then "none".</p></blockquote>
-
-<p>Lets assume your Eclipse workspace directory is c:\eclipse\workspace
-and you have two projects, MyProject1 and MyProject2. The first project,
-MyProject1, is located inside the workspace directory, the second project,
-MyProject2, is located outside the workspace directory at c:\projects\MyProject2.
-Lets look at how the variable examples below will be expanded when an
-external tool is run, if the resource /MyProject2/MyFolder/MyFile.txt is
-selected.
-<br>&nbsp;
-<br>&nbsp;
-<center><table BORDER WIDTH="80%" >
-<tr>
-<td>
-<center><b>Variable Examples</b></center>
-</td>
-
-<td>
-<center><b>Expanded Results</b></center>
-</td>
-</tr>
-
-<tr>
-<td>${workspace_loc}</td>
-
-<td>c:\eclipse\workspace</td>
-</tr>
-
-<tr>
-<td>${workspace_loc:/MyProject1/MyFile.txt}</td>
-
-<td>c:\eclipse\workspace\MyProject\MyFile.txt</td>
-</tr>
-
-<tr>
-<td>${workspace_loc:/MyProject2/MyFile.txt}</td>
-
-<td>c:\projects\MyProject2\MyFile.txt</td>
-</tr>
-
-<tr>
-<td>${project_loc}</td>
-
-<td>c:\projects\MyProject2</td>
-</tr>
-
-<tr>
-<td>${project_loc:/MyProject1/MyFile.txt}</td>
-
-<td>c:\eclipse\workspace\MyProject</td>
-</tr>
-
-<tr>
-<td>${container_loc}</td>
-
-<td>c:\projects\MyProject2\MyFolder</td>
-</tr>
-
-<tr>
-<td>${resource_loc}</td>
-
-<td>c:\projects\MyProject2\MyFile.txt</td>
-</tr>
-
-<tr>
-<td>${project_path}</td>
-
-<td>/MyProject2</td>
-</tr>
-
-<tr>
-<td>${container_path}</td>
-
-<td>/MyProject2/MyFolder</td>
-</tr>
-
-<tr>
-<td>${resource_path}</td>
-
-<td>/MyProject2/MyFolder/MyFile.txt</td>
-</tr>
-
-<tr>
-<td>${project_name}</td>
-
-<td>MyProject2</td>
-</tr>
-
-<tr>
-<td>${container_name}</td>
-
-<td>MyFolder</td>
-</tr>
-
-<tr>
-<td>${resource_name}</td>
-
-<td>MyFile.txt</td>
-</tr>
-
-<tr>
-<td>${build_type}</td>
-
-<td>none</td>
-</tr>
-</table></center>
-</p>
-
-<p><br><img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-<br><a href="concepts-antsupport.htm">Ant support</a>
-<br><a href="concepts-22.htm">Builds</a></p>
-<p><img src="../images/ngrelr.png" alt="Related reference" BORDER=0 >
-<br><a href="../reference/ref-exttoolsprefs.htm">External Tools preferences</a><br>
-<a href="../reference/ref-anticons.htm">External Tools and Ant icons</a></p>
-<p><img src="../images/ngrelt.png" alt="Related tasks" BORDER=0 >
-<br><a href="../tasks/tasks-exttools-running.htm">Running external tools</a>
-<br><a href="../tasks/tasks-ant-running.htm">Running Ant buildfiles</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/coutline.htm b/bundles/org.eclipse.platform.doc.user/concepts/coutline.htm
deleted file mode 100644
index e8acefc..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/coutline.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Outline view</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY>
-<H1 CLASS="Head">
-Outline view</H1>
-
-<P>The Outline view displays an outline of a structured file that is currently 
-  open in the editor area, and lists structural elements.&nbsp;The contents of 
-  the Outline view are editor specific. In the example below, which is for a Java 
-  source file, the structural elements are classes, fields, and methods. The contents 
-  of the toolbar are also editor specific. </p>
-
-<P><img src="../images/ref-8.png" alt="Picture of Outline view showing structure for a Java file" border="0" > 
-</p>
-<p>
-  To add the Outline view to the current perspective, click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.ContentOutline)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Window &gt; Show View &gt; Other... &gt; General &gt; Outline</b></a>.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="concepts-5.htm">Views</a><br>
-<a href="concepts-4.htm">Perspectives</a><br>
-<a href="concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-3.htm">Opening views</a><br>
-<a href="../tasks/tasks-3e.htm">Moving and docking views</a><br>
-<a href="../tasks/tasks-9b.htm">Creating fast views</a>
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/cpathvars.htm b/bundles/org.eclipse.platform.doc.user/concepts/cpathvars.htm
deleted file mode 100644
index dbafac8..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/cpathvars.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Path variables</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Path variables</H1>
-<p>
-Path variables specify locations on the file system. The location of linked resources
-may be specified relative to these path variables. They allow you to avoid references to 
-a fixed location on your file system.
-</p>
-<p>
-By using a path variable, you can share projects containing linked resources with
-team members without requiring the exact same directory structure as on your file 
-system.
-</p>
-<p>
-You can load a project that uses path variables even if you do not currently have all 
-the path variables defined in your workspace. A linked resource that uses a missing path
-variable is flagged using a special decorator icon. In addition, the
-<b>File &gt; Properties &gt; Info</b> 
-property page and the Properties view
-(<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.PropertySheet)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Properties</b></a>)
-for a linked resource indicate the 
-variable and whether it is defined or not. A path variable can also specify a 
-location that does not currently exist on the file system. Linked resources that use such
-a path variable are indicated using the same decorator icon mentioned above.
-</p>
-<p>
-You can create new path variables and edit and remove existing path variables on the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.LinkedResources)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>General &gt; Workspace &gt; Linked Resources</b></a> preference page.
-</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="concepts-13.htm">Linked resources</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-45.htm">Creating linked resources</a><br>
-<a href="../tasks/tasks-49.htm">Viewing resource properties</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br>
-  <a href="../reference/ref-14b.htm">Linked resources</a> </p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/cprbview.htm b/bundles/org.eclipse.platform.doc.user/concepts/cprbview.htm
deleted file mode 100644
index b210050..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/cprbview.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Problems view (concept)</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body>
-
-<H1 CLASS="Head">Problems view</H1>
-<P CLASS="Para"> As you work with resources in the workbench, various builders 
-  may automatically log problems, errors, or warnings in the Problems view. For 
-  example, when you save a Java source file that contains syntax errors, those 
-  will be logged in the Problems view. When you double-click the icon for a problem, 
-  error, or warning, the editor for the associated resource automatically opens 
-  to the relevant line of code.&nbsp;</P>
-<p><img src="../images/prob.png" alt="Picture of the Problems view with two warnings added to it." border="0" ></p>
-<p CLASS="Head"> The first column of the Problems view displays an icon that denotes 
-  the type of line item. Click on the item to open the file in an editor, the 
-  line containing the problem will be highlighted. </p>
-<p CLASS="Head">You can filter line items in the Problems view, to view only warnings 
-  and errors associated with a particular resource or group of resources.</p><p><img src="../images/prbfil.png" alt="Picture of the Filters options." border="0" ></p>
-<p CLASS="Head">
-  To add the Problems view to the current perspective, click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.ProblemView)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Window &gt; Show View &gt; Other... &gt; General &gt; Problems</b></a>.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-  <a href="concepts-11.htm">Markers</a><br>
-  <a href="cbookmrk.htm">Bookmarks</a><br>
-  <a href="ctskview.htm">Tasks view</a><br>
-</p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-3.htm">Opening views</a><br>
-<a href="../tasks/tasks-3e.htm">Moving and docking views</a><br>
-<a href="../tasks/tquickfix.htm">Automatically fixing problems</a><br>
-</p>
-
-
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/cpropview.htm b/bundles/org.eclipse.platform.doc.user/concepts/cpropview.htm
deleted file mode 100644
index 052ad99..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/cpropview.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Properties view</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Properties view</H1>
-<P CLASS="Para">
-The properties view displays property names and values for a selected item such
-as a resource.
-Here is an example:</P>
-<P CLASS="Para">
-<img src="../images/Image240_props_view.png" alt="Picture of a Properties sheet with 3 columns, including a column for property and a column for value." border="0" ></P>
-<P CLASS="Para">Toolbar buttons allow you to toggle to display
-properties by category or to filter advanced properties. Another
-toolbar button allows you to restore the selected property to its default value.</P>
-<P>To see more detailed information about a resource than the Properties view
-gives you, right-click the resource name in one of the navigation views and select
-Properties from the pop-up menu.
-</P>
-<p>
-  To add the Properties view to the current perspective, click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.PropertySheet)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Window &gt; Show View &gt; Other... &gt; General &gt; Properties</b></a>.
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/csearchview.htm b/bundles/org.eclipse.platform.doc.user/concepts/csearchview.htm
deleted file mode 100644
index b289efe..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/csearchview.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"><title>Search view</title></head><body>
-<h1>
-Search view</h1>
-
-<p>
-This view displays the results of a search.&nbsp;&nbsp;</p>
-
-<p>
-Text searches will only search for expressions in files with extensions (file
-types) specified in the search dialog.</p>
-
-<p>
-Here is what the Search view looks like:</p>
-<p>
-<img src="../images/Image237_search_view.png" alt="Search View" border="0" ></p>
-<h2>
-Toolbar</h2>
-<p>The toolbar in the Search view contains the following buttons:</p>
-<dl>
-	<dt>Show Next Match</dt>
-		<dd>This command highlights the next match of the search expression in the editor area, opening the file if required.</dd>
-	<dt>Show Previous Match</dt>
-		<dd>This command highlights the previous match of the search expression in the editor area, opening the file if required.</dd>
-	<dt>Remove Selected Matches</dt>
-		<dd>Removes all highlighted matches from the search results.</dd>
-	<dt>Search</dt>
-		<dd>This command opens the Search dialog.</dd>
-	<dt>Previous Search Results</dt>
-		<dd>This command allows you to browse previously conducted searches and repeat a previous search.&nbsp; You can select a previous search from the drop-down menu or clear the search history.</dd>
-</dl>
-
-<p><br>
-<img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<a href="concepts-12.htm"><br>Resources</a>&nbsp;
-<br>
-<a href="concepts-5.htm">Views</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-84.htm">Searching for text within a file</a><br>
-<a href="../tasks/tasks-84b.htm">Searching for files</a>
-<br>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br><a href="../reference/ref-26.htm">Search view</a><br><a href="../reference/ref-45.htm">File search</a><br></p>
-
-
-
-</body></html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/ctskview.htm b/bundles/org.eclipse.platform.doc.user/concepts/ctskview.htm
deleted file mode 100644
index f6d64eb..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/ctskview.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Tasks view (concept)</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body>
-
-<H1 CLASS="Head">
-Tasks view</H1>
-<P CLASS="Para"> You can assign tasks within your project by right clicking marker 
-  bar's context menu and selecting <strong>Add Task</strong> or you can add items 
-  within the Tasks view by selecting <strong>Add Task </strong><img src="../images/addtask.png" alt="Picture of the Tasks view with two dummy tasks added to it." border="0" >. 
-  For example, if you would like to record reminders to follow up on something 
-  later, add it to the tasks view. When you add a task, you have the option of 
-  associating it with a resource so that you can use the Tasks view to quickly 
-  open that resource for editing.</P>
-<p><img src="../images/Image243_tasks_view.png" alt="Picture of the Add Task icon" border="0" ></p>
-<p CLASS="Head"> The first column of the Tasks view displays an icon that denotes 
-  the type of line item. You can sort and filter line items in the task view, 
-  to view only high-priority tasks or tasks associated with a particular resource 
-  or group of resources.&nbsp;</p>
-<p CLASS="Head"> By default, the Tasks view is included in the Resource perspective. 
-  To add it to the current perspective, click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.TaskList)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Window &gt; Show View &gt; Other... &gt; General &gt; Tasks</b></a>.</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="concepts-11.htm">Markers</a><br>
-<a href="cbookmrk.htm">Bookmarks</a><br>
-<a href="cprbview.htm">Problems view</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-3.htm">Opening views</a><br>
-<a href="../tasks/tasks-3e.htm">Moving and docking views</a><br>
-<a href="../tasks/tasks-77.htm">Adding line items in the Tasks view</a><br>
-<a href="../tasks/tasks-77b.htm">Associating a task with a resource</a><br>
-<a href="../tasks/tasks-79.htm">Filtering the Tasks view</a><br>
-<a href="../tasks/tasks-78.htm">Deleting tasks</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-31.htm">Tasks view</a>
-</p>
-
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/cworkset.htm b/bundles/org.eclipse.platform.doc.user/concepts/cworkset.htm
deleted file mode 100644
index 554d0bf..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/cworkset.htm
+++ /dev/null

@@ -1,97 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working sets</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Working sets</H1>
-<P CLASS="Para" Label=Type>
-Working sets group elements for display in views or for operations on a set 
-of elements. </P>
-
-<P CLASS="Para" Label=Type> The navigation views use working sets to restrict 
-  the set of resources that are displayed. If a working set is selected in the 
-  navigator, only resources, children of resources, and parents of resources contained 
-  in the working set are shown. </P>
-
-<P CLASS="Para" Label=Type> Working sets may be used in the task view to limit 
-  the display of tasks in a similar fashion as the navigation views. </P>
-
-<P CLASS="Para" Label=Type>
-When using the Workbench search facility, working sets may be used to restrict 
-the set of elements that are searched. </P>
-
-<P CLASS="Para" Label=Type>
-Different views provide different means to specify a working set. However, they 
-typically use the following working set selection dialog to manage existing working 
-sets and to create new working sets.
-</P>
-
-<P CLASS="Para" Label=Type>
-&nbsp;
-<img src="../images/Image87_workset_sel.png" alt="Picture of working set selection dialog" border="0" >
-</P>
-
-<P CLASS="Para" Label=Type>&nbsp;
-
-</P>
-
-<P CLASS="Para" Label=Type>
-When you create a new working set you may be able to choose from different types
-of working sets. In the example below you can create a resource working set, a
-Java working set or a help working set.
-</P>
-
-<P CLASS="Para" Label=Type>
-&nbsp;
-<img src="../images/Image88_workset_new_type.png" alt="Picture of type selection page of new working set wizard" border="0" >
-</P>
-
-<P CLASS="Para" Label=Type>&nbsp;
-
-</P>
-
-<P CLASS="Para" Label=Type>
-If you create a new resource working set you will be able to select the working 
-set resources as shown below. The same wizard is used to edit an existing working
-set. Different types of working sets provide different kinds of working set 
-editing wizards.
-</P>
-
-<P CLASS="Para" Label=Type>
-&nbsp;
-<img src="../images/Image89_workset_new_res.png" alt="Picture of edit page of working set wizard" border="0" >
-</P>
-
-<P CLASS="Para" Label=Type>&nbsp;
-
-</P>
-
-<DIV CLASS="Note">
-  <P CLASS="Para" Label=Type> <strong>Note:</strong> Newly created resources are 
-    not automatically included in the active working set. They are implicitly 
-    included in a working set if they are children of an existing working set 
-    element. If you want to include other resources after you have created them 
-    you have to explicitly add them to the working set. </P>
-</DIV>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="cnav.htm">Navigator view</a><br>
-<a href="ctskview.htm">Tasks view</a><br>
-</p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks." ><br>
-<a href="../tasks/tasks-84.htm">Searching for text within a file</a><br>
-<a href="../tasks/tasks-48b.htm">Showing or hiding resources in the Navigator view</a><br>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/no_help_exists.htm b/bundles/org.eclipse.platform.doc.user/concepts/no_help_exists.htm
deleted file mode 100644
index 28fb7f9..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/no_help_exists.htm
+++ /dev/null

@@ -1,20 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE> No Help Exists</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-No Help Exists</H1>
-<p CLASS="Head">There are no available help topics associated with this
-item.&nbsp;&nbsp;&nbsp;</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/contexts_AntUI.xml b/bundles/org.eclipse.platform.doc.user/contexts_AntUI.xml
deleted file mode 100644
index 82277b6..0000000
--- a/bundles/org.eclipse.platform.doc.user/contexts_AntUI.xml
+++ /dev/null

@@ -1,189 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-
-  <context id="remove_all_action_context">
-    <description>This command removes all buildfiles from the Ant view.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="search_for_buildfiles_action_context">
-    <description>This command searches for buildfiles and adds them to the Ant view.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="edit_launch_configuration_action_context">
-    <description>This command opens a dialog to edit a launch configuration associated with the selected buildfile.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="run_target_action_context">
-    <description>This command executes the selected target or the default target of the selected buildfile.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="remove_project_action_context">
-    <description>This command removes the selected buildfiles from the Ant view.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-  
-  <context id="refresh_buildfile_action_context">
- 	<description>This command refreshes the selected buildfiles in the Ant view. All buildfiles are refreshed if the Ant view has no selection.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-  
-  <context id="add_buildfile_action_context">
-    <description>This command prompts you to select a buildfile in the workspace to be added to the view.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="add_task_dialog_context">
-    <description>This dialog allows you to define an Ant task for Ant builds. You must set the name, location and classfile.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-  
-  <context id="edit_task_dialog_context">
-    <description>This dialog allows you to edit an exisitng Ant task defined for Ant builds.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-  
-  <context id="add_type_dialog_context">
-    <description>This dialog allows you to define an Ant type for Ant builds. You must set the name, location and classfile.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-  
-  <context id="edit_type_dialog_context">
-    <description>This dialog allows you to edit an existing Ant type defined for Ant builds.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="add_property_dialog_context">
-    <description>This dialog allows you to define an Ant property used in an Ant build.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-  
-  <context id="edit_property_dialog_context">
-    <description>This dialog allows you to edit an existing Ant property.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="search_for_buildfiles_dialog_context">
-    <description>This dialog allows you to search for buildfiles within the workspace.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="target_order_dialog_context">
-    <description>This dialog allows you to specify the order in which the selected Ant targets will be run. This ordering does not override the dependencies specified in your buildfile.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_preference_page_context">
-    <description>On this page, you can configure Ant preferences.</description>
-   	<topic label="Preferences - Ant" href="reference/ref-antprefs.htm"/>    
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_runtime_preference_page_context">
-    <description>On this page, you can configure the runtime environment of Ant.</description>
-    <topic label="Preferences - Ant Runtime" href="reference/ref-antruntimeprefs.htm"/>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_editor_preference_page_context">
-    <description>On this page, you can configure Ant editor preferences.</description>
-    <topic label="Preferences - Ant Editor" href="reference/ref-anteditorprefs.htm"/>
-    <topic label="Ant Editor" href="reference/ref-anteditor.htm"/> 
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_types_page_context">
-    <description>On this page, you can add or edit custom Ant types, specified within a Java class file, to be used when running Ant buildfiles.</description>
-    <topic label="Preferences - Ant Runtime" href="reference/ref-antruntimeprefs.htm"/>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_classpath_page_context">
-    <description>On this page, you can configure the Ant runtime classpath.</description>
-    <topic label="Preferences - Ant Runtime" href="reference/ref-antruntimeprefs.htm"/>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_properties_page_context">
-    <description>On this page, you can configure the properties available to Ant.</description>
-    <topic label="Preferences - Ant Runtime" href="reference/ref-antruntimeprefs.htm"/>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_tasks_page_context">
-    <description>On this page, you can add or edit custom Ant tasks, specified within a Java class file, to be used when running Ant buildfiles.</description>
-    <topic label="Preferences - Ant Runtime" href="reference/ref-antruntimeprefs.htm"/>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_view_context">
-    <description>This view allows you to view your Ant buildfiles in one place and quickly execute a target or the default target of a buildfile.</description>
-    <topic label="Ant View" href="reference/ref-antview.htm"/>
-    <topic label="Ant Editor" href="reference/ref-anteditor.htm"/> 
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-  
-  <context id="ant_editor_context">
-    <description>The Ant editor provides you with Ant buildfile specific text editing support.</description>
-    <topic label="Ant Editor" href="reference/ref-anteditor.htm"/> 
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_main_tab_context">
-    <description>This tab allows you to configure the buildfile location and other attributes of this launch configuration.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_targets_tab_context">
-    <description>This tab allows you to configure which targets will be executed by this launch configuration.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_properties_tab_context">
-    <description>This tab allows you to configure the properties that will be passed in to Ant when this launch configuration is executed.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_classpath_tab_context">
-    <description>This tab allows you to configure the runtime classpath that will be used when this launch configuration is executed.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-  
-   <context id="ant_jre_tab_context">
-    <description>This tab allows you to configure the JRE used for the Ant build.  By default Ant runs in a separate Java virtual machine (JVM) from Eclipse. You can specify the build to occur in the same JRE as Eclipse.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-</contexts>

diff --git a/bundles/org.eclipse.platform.doc.user/contexts_Compare.xml b/bundles/org.eclipse.platform.doc.user/contexts_Compare.xml
deleted file mode 100644
index 435941b..0000000
--- a/bundles/org.eclipse.platform.doc.user/contexts_Compare.xml
+++ /dev/null

@@ -1,99 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-
-<!-- Compare plugin -->
-
-	<context id="compare_editor_context">
-		<description>Compare and merge files and folders in a Compare Editor.</description>
- 		<topic label="Compare editor" href="reference/ref-25.htm"/>
- 		<topic label="Comparing Resources" href="tasks/tasks-68.htm"/>
- 		<topic label="Understanding the comparison" href="tasks/tasks-68bg.htm"/>
- 		<topic label="Merging changes in the Compare editor" href="tasks/tasks-68dg.htm"/>
- 		<topic label="Three way comparisons" href="concepts/concepts-29.htm"/>
-	</context>
-
-	<context id="patch_input_wizard_page_context">
-		<description>This wizard helps you applying a patch to files and folders in your workspace. On the first page you can select the file or folders on which to apply the patch and whether the patch is loaded from an external file or from the clipboard.</description>
- 		<topic label="Working with patches" href="tasks/tasks-68c.htm"/>
-	</context>
-
-	<context id="patch_preview_wizard_page_context">
-		<description>On this page you can see how well the patch matches with your workspace. You can adjust some parameters to influence the matching.</description>
- 		<topic label="Working with patches" href="tasks/tasks-68c.htm"/>
-	</context>
-
-	<context id="compare_dialog_context">
-		<description>A dialog displaying the results of comparing files.</description>
- 		<topic label="Comparing Resources" href="tasks/tasks-68.htm"/>
- 		<topic label="Understanding the comparison" href="tasks/tasks-68bg.htm"/>
-	</context>
-	
-	<context id="add_from_history_dialog_context">
-		<description>A dialog that lets you restore deleted files from the local history.</description>
- 		<topic label="Restoring deleted resources from the local history" href="tasks/tasks-87b.htm"/>
- 		<topic label="Local history" href="concepts/concepts-17a.htm"/>
- 		<topic label="Working with local history" href="tasks/tasks-1f.htm"/>
- 		<topic label="Local history" href="reference/ref-6a.htm"/>
-	</context>
-	
-	<context id="compare_with_edition_dialog_context">
-		<description>A dialog that lets you compare files with entries from the local history.</description>
- 		<topic label="Comparing resources with the local history" href="tasks/tasks-70.htm"/>
- 		<topic label="Local history" href="concepts/concepts-17a.htm"/>
- 		<topic label="Working with local history" href="tasks/tasks-1f.htm"/>
- 		<topic label="Local history" href="reference/ref-6a.htm"/>
-	</context>
-	
-	<context id="replace_with_edition_dialog_context">
-		<description>A dialog that lets you replace files with entries from the local history.</description>
- 		<topic label="Replacing a resource with local history" href="tasks/tasks-87.htm"/>
- 		<topic label="Local history" href="concepts/concepts-17a.htm"/>
- 		<topic label="Working with local history" href="tasks/tasks-1f.htm"/>
- 		<topic label="Local history" href="reference/ref-6a.htm"/>
-	</context>
-	
-	
-		
-	<context id="text_merge_view_context">
-		<description>This editor provides support for comparing and merging text files.</description>
-	</context>
-		
-	<context id="image_compare_view_context">
-		<description>This view shows two images side-by-side.</description>
-	</context>
-
-	<context id="binary_compare_view_context">
-		<description>This view shows the first position where two files differ.</description>
-	</context>
-		
-
-	<context id="global_next_diff_action_context">
-		<description>Goto next difference globally.</description>
-	</context>
-	
-	<context id="global_previous_diff_action_context">
-		<description>Goto previous difference globally.</description>
-	</context>
-	
-	<context id="next_diff_action_context">
-		<description>Goto next difference.</description>
-	</context>
-	
-	<context id="previous_diff_action_context">
-		<description>Goto previous difference.</description>
-	</context>
-	
-	<context id="ignore_whitespace_action_context">
-		<description>Ignore whitespace.</description>
-	</context>
-
-	
-  	<context id="compare_preference_page_context" >
-		<description>This preference page is used to set preferences for the compare, merge, and patch functionality in the workbench.</description>
- 		<topic label="Setting preferences for comparing files" href="tasks/tasks-68b.htm"/>
- 		<topic label="Preferences - Compare/Patch" href="reference/ref-11.htm"/>
-   		<topic label="Comparing Resources" href="reference/ref-25.htm"/>
-	</context>
-
-</contexts>

diff --git a/bundles/org.eclipse.platform.doc.user/contexts_ExternalTools.xml b/bundles/org.eclipse.platform.doc.user/contexts_ExternalTools.xml
deleted file mode 100644
index e272963..0000000
--- a/bundles/org.eclipse.platform.doc.user/contexts_ExternalTools.xml
+++ /dev/null

@@ -1,33 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-  <context id="file_selection_dialog_context">
-    <description>This dialog allows you to select a file in the workspace.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="preference_page_context">
-    <description>On this page, you can configure External Tool preferences.</description>
-   	<topic label="Preferences - External Tools" href="reference/ref-exttoolsprefs.htm"/>    
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="builder_property_page_context">
-    <description>On this page, you can configure the External Tool builders that are run when this project is built.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="builders_tab_context">
-    <description>This tab allows you to configure when this project builder will be executed.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="program_main_tab_context">
-    <description>This tab allows you to configure the program location and other attributes of this launch configuration.</description>
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-</contexts>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/contexts_Help.xml b/bundles/org.eclipse.platform.doc.user/contexts_Help.xml
deleted file mode 100644
index a7df39d..0000000
--- a/bundles/org.eclipse.platform.doc.user/contexts_Help.xml
+++ /dev/null

@@ -1,41 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-
-<contexts>
-
-<!-- F1 on F1 -->
-   <context  id="f1Shell" >
-      <description>Context-sensitive &quot;infopop&quot; help is provided for many interfaces, including views, wizards, fields, checkboxes, buttons, and menu items. To access this help, bring focus to the item by clicking it or using the tab key, and then press F1.
-
-Some infopops include links to topics within the online help where you can find more information about the item.
-
-This infopop opened because you pressed F1 while an infopop was already open.</description>
-   </context>
-
-<!-- Preference page for help browsers -->
-   <context  id="prefPageBrowsers" >
-      <description>Allows selecting a web browser.  The selected web browser will be the default browser used to display help contents.</description>
-	  <topic label="Preferences Dialog" href="/org.eclipse.platform.doc.user/reference/ref-72.htm"/>
-   </context>
-
-<!-- Path to custom browser on preference page for help browsers -->
-   <context  id="prefPageCustomBrowserPath" >
-      <description>When custom web browser is selected from the list, specify path to the browser program that launches the browser.  If the program is available on your system path, you may specify only the program name.
-
-If the program does not accept URL as its last parameter, you may use %1 string to denote the position of the URL parameter in the command.</description>
-      <topic label="Preferences Dialog" href="/org.eclipse.platform.doc.user/reference/ref-72.htm"/>
-   </context>
-
-<!-- Application server preference page -->
-   <context  id="prefPageAppServer" >
-      <description>These settings allow you to override the network interface address and port number that the internal <b>application server</b> will use.  Change the settings when the port it is trying to use is taken, or when your IP address has changed.
-
-To automatically determine the interface address, leave the host field <b>blank</b>.
-
-To use port dynamically assigned by the system, specify <b>0</b> in the port field.
-
-Under normal circumstances, use the <b>Default</b> settings.</description>
-      <topic label="Preferences Dialog" href="/org.eclipse.platform.doc.user/reference/ref-72.htm"/>
-   </context>
-
-</contexts>

diff --git a/bundles/org.eclipse.platform.doc.user/contexts_Search.xml b/bundles/org.eclipse.platform.doc.user/contexts_Search.xml
deleted file mode 100644
index 2f42319..0000000
--- a/bundles/org.eclipse.platform.doc.user/contexts_Search.xml
+++ /dev/null

@@ -1,56 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-
-<!-- Search plugin -->
-   <context  id="search_dialog_context" >
-      <description>You can search the workbench for resources matching the indicated conditions.</description>
- 	<topic label="Text searching" href="tasks/tasks-84.htm"/>
- 	<topic label="File searching" href="tasks/tasks-84b.htm"/>
-   	<topic label="File search" href="reference/ref-45.htm"/>
-   </context>
-
-   <context  id="text_search_page_context" >
-      <description>Type a file pattern and/or expression for which you want to search the workbench. You can use the indicated wildcards and/or search only the specific file types as needed.</description>
- 	<topic label="Text searching" href="tasks/tasks-84.htm"/>
- 	<topic label="File searching" href="tasks/tasks-84b.htm"/>
-   	<topic label="File search" href="reference/ref-45.htm"/>
-   	<topic label="Available Regular Expressions" href="http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html" />
-   </context>
-
-   <context  id="replace_dialog_context" >
-      <description>Replace matches in the search results view with a replacment string.</description>
-   	<topic label="About Regular Expressions" href="http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html" />
-   </context>
- 
-   <context  id="search_view_context" >
-      <description>This view displays the results of recent searches.</description>
- 	<topic label="Search view" href="reference/ref-26.htm"/>
- 	<topic label="File search" href="reference/ref-45.htm"/>
-   </context>
-   
-   <context  id="new_search_view_context" >
-      <description>This view displays the results of recent searches.</description>
- 	<topic label="File search" href="reference/ref-45.htm"/>
-   </context>
-
-   <context  id="search_preference_page_context" >
-      <description>This page displays the search preferences.</description>
- 	<topic label="Search preferences" href="reference/ref-search.htm"/>
- 	<topic label="Search view" href="reference/ref-26.htm"/>
- 	<topic label="File search" href="reference/ref-45.htm"/>
-   </context>
-
-   <context  id="open_search_dialog_action_context" >
-      <description>This command opens the search dialog.</description>
-   </context>
-
-   <context  id="file_search_action_context" >
-      <description>This command opens the file search dialog.</description>
- 	<topic label="Text searching" href="tasks/tasks-84.htm"/>
- 	<topic label="File searching" href="tasks/tasks-84b.htm"/>
-   	<topic label="File search" href="reference/ref-45.htm"/>
-
-   </context>
-
-</contexts>

diff --git a/bundles/org.eclipse.platform.doc.user/contexts_Team.xml b/bundles/org.eclipse.platform.doc.user/contexts_Team.xml
deleted file mode 100644
index 5d12444..0000000
--- a/bundles/org.eclipse.platform.doc.user/contexts_Team.xml
+++ /dev/null

@@ -1,158 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-
-	<!-- ********************************** -->
- 	<!-- Dialogs							-->
- 	<!-- ********************************** -->
- 	
- 	<context id="sync_view_preference_dialog_context">
-      <description>This dialog allows you set configure the active synchronization in the Synchronize View.</description>
-   	</context>
-   	
-   	<context id="configre_refresh_schedule_dialog_context">
-      <description>This dialog allows you to configure the active synchronization to be automatically refreshed at a specified interval.</description>
-   	</context>
-   	
-	<!-- ********************************** -->
- 	<!-- Wizard Pages 						-->
- 	<!-- ********************************** -->
- 	
- 	<context id="share_project_page_context">
-      <description>This page helps you select what type of target site you wish to connect the project to.</description>
-   	</context>
-   	
-   	<context id="import_project_set_page_context">
-      <description>This page helps you import a project set from a file on the file system. A project set is a lightweight description of a set of shared projects. It can be used to reconstruct a lineup of shared projects that you have in your workspace.</description>
-   	</context>
-	
-	<context id="export_project_set_page_context">
-      <description>This page helps you export a project set to a file which can be shared with other team members. A project set is a lightweight description of a set of shared projects. It can be used to reconstruct a lineup of shared projects that you have in your workspace.</description>
-   	</context>
-   	
-    <context id="sync_resource_selection_page_context">
-      <description>This page allows you to choose the resources that are to be synchronized.</description>
-   	</context>
-   	
-   	<context id="refresh_wizard_selection_page_context">
-      <description>This page allows you to choose the type of synchronization you want to create.</description>
-   	</context>
-	
-	
- 	<!-- ********************************** -->
- 	<!-- Preference Pages 					-->
- 	<!-- ********************************** -->
- 	
- 	<context id="ignore_preference_page_context" >
-      <description>You may wish to exclude certain resources from version control. Resources whose names match any enabled pattern will not be released. The wildcard characters '*' and '?' are permitted. These settings will not affect resources already under version control.</description>
-      <topic label="Creating a global ignore pattern" href="tasks/tasks-100d1.htm"/>
-   	</context>
-
- 	<context id="sync_preference_page_context" >
-      <description>This page allows you to configure various aspects of the Synchronize View.</description>
-      <topic label="CVS Synchronize view" href="reference/ref-33.htm"/>
-   	</context>
-
- 	<context id="file_type_preference_page_context" >
-      <description>This page allows you to associate a file extension with its content type (ASCII or binary). These setting are used by repository providers, such as CVS</description>
-      <topic label="Setting the content type of a file extension" href="tasks/tasks-team-1.htm"/>
-   	</context>
-   	   	  	
-   	<!-- ********************************** -->
- 	<!-- TargetMenuActions 					-->
- 	<!-- ********************************** -->
-	
-	<context id="target_get_action_context">
-   		<description>Downloads the selected resources from the site into your workspace.</description>
-   	</context>
-
- 	<context id="target_put_action_context">
-   		<description>Uploads the selected resources from your workspace to the site.</description>
-   	</context>
-   	
-   	<context id="target_synchronize_action_context">
-   		<description>Show any differences between the local and remote site state of the selected resources in the Synchronize view.</description>
-   	</context>
-   	
-   	<context id="target_getas_action_context">
-   		<description>Downloads the selected resources from the site into your workspace. You may specify the local name of the resources.</description>
-   	</context>
-   	
-   	<context id="target_getasproject_action_context">
-   		<description>Downloads the selected resources from the site into your workspace. A project is created in the workspace for each of the selected items.</description>
-   	</context>
-   	
-   	<context id="target_disconnect_action_context">
-   		<description>Discards the selected target sites from the list of remembered sites.</description>
-   	</context>
-   	
-   	<!-- ********************************** -->
- 	<!-- TargetCatchupReleaseViewer			-->
- 	<!-- ********************************** -->
-	
-	<context id="target_catchup_release_viewer_context">
-   		<description>This view shows incoming, outgoing and conflicting changes.</description>
-   	</context>
-   	
-   	<!-- ********************************** -->
- 	<!-- TargetActions						-->
- 	<!-- ********************************** -->
-   	
-   	<context id="sync_get_action_context">
-   		<description>Downloads the selected resources from the site into your workspace.</description>
-   	</context>
-   	
-   	<context id="sync_put_action_context">
-   		<description>Uploads the selected resources from your workspace to the site.</description>
-   	</context>
-   	
-   	<!-- ********************************** -->
- 	<!-- Views					            -->
- 	<!-- ********************************** -->
- 	
- 	<context id="site_explorer_view_context">
-      <description>The Site Explorer view allows you to browse of the contents of known target sites and download remote resources into the local workspace.</description>
-   	</context>
-
- 	<context id="sync_view_context">
-      <description>The Synchronize view allows the synchronization of the local contents of the workspace with a remote repository or target.</description>
-      <topic label="CVS Synchronize view" href="reference/ref-33.htm"/>
-   	</context>
-   	   	
-   	<!-- ********************************** -->
- 	<!-- SiteExplorerViewActions		    -->
- 	<!-- ********************************** -->
- 	
- 	<context id="add_site_action_context">
-      <description>Creates a new target site to which you can upload or download resources.</description>
-   	</context>
-   	
-   	<context id="new_folder_action_context">
-      <description>Creates a new folder on the target site.</description>
-   	</context>
-   	
-   	<!-- ********************************** -->
- 	<!-- SyncViewActions				    -->
- 	<!-- ********************************** -->
- 	
- 	<context id="refresh_action_context">
-      <description>Refreshes the contents of the view.</description>
-   	</context>
-
-   	<context id="open_action_context">
-      <description>Show the comparison of the local and remote contents of the file in the comparison viewer.</description>
-   	</context>
-   	 	
-   	<context id="expandall_action_context">
-      <description>Fully expands all selected items.</description>
-   	</context>
-   	
-   	<context  id="remove_action_context">
-      <description>Removes the selected items from the Synchronize view.</description>
-   	</context>
-   	
-   	<context  id="navigator_show_action_context">
-      <description>Selects and reveals the selected items in the Navigator view.</description>
-   	</context>
- 
-</contexts>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/contexts_Team_CVS.xml b/bundles/org.eclipse.platform.doc.user/contexts_Team_CVS.xml
deleted file mode 100644
index f789d87..0000000
--- a/bundles/org.eclipse.platform.doc.user/contexts_Team_CVS.xml
+++ /dev/null

@@ -1,709 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-   
-	<!-- ********************************** -->
- 	<!-- TagSelectionDialog 				-->
- 	<!-- ********************************** -->
-	
-	<context id="replace_tag_selection_dialog_context">
-   		<description>You have chosen to replace the selected resources with a branch or version tag. This dialog allows you to select the tag which is to be used for this operation. The selected resources will be replaced with those tagged with the selected tag. If the desired tag does not appear in the list of Versions or Branches, perform a "Refresh from Repository" or a "Configure Tags" to automatically or manually find the tags that exist in the repository. Disabling the "Recurse into sub-folders" option will restrict the operation to selected folders and their direct children and selected files only.</description>
-   		<topic label="Replacing resources in the workbench" href="tasks/tasks-103.htm" />
-   	</context>
-   	
-   	<context id="compare_tag_selection_dialog_context">
-   		<description>You have chosen to compare the selected resources with a branch or version tag. This dialog allows you to select the tag which is to be used for this operation. The selected resources will be compared with those tagged with the selected tag. If the desired tag does not appear in the list of Versions or Branches, perform a "Refresh from Repository" or a "Configure Tags" to automatically or manually find the tags that exist in the repository.</description>
-        <topic label="Comparing resources with repository versions" href="tasks/tasks-101.htm" />
-   	</context>
-   	
-   	<context id="tag_remote_with_existing_dialog_context">
-   		<description>You have chosen to tag the selected resources with an existing branch or version tag. This dialog allows the user to select the tag which is to be used for this operation. If the tag already exists on another revision of any of the selected resources, it will be moved to the revision in the selection. If the desired tag does not appear in the list of Versions or Branches, perform a "Refresh from Repository" or a "Configure Tags" to automatically or manually find the tags that exist in the repository. Disabling the "Recurse into sub-folders" option will restrict the operation to selected folders and their direct children and selected files only.</description>
-        <topic label="Moving version tags" href="tasks/tasks-105c.htm" />
-   	</context>
-   	
-   	<!-- ********************************** -->
- 	<!-- TagAsVersionDialog 				-->
- 	<!-- ********************************** -->
- 	
- 	<context id="tag_as_version_dialog_context">
-   		<description>This dialog allows you to create a version. Enter the version name to be used to tag to the selected resources.</description>
-   		<topic label="Creating a version of a project" href="tasks/tasks-100.htm" />
-   	</context>
-   	
-   	<!-- ********************************** -->
- 	<!-- WizardPages 						-->
- 	<!-- ********************************** -->
- 	
- 	<context id="sharing_autoconnect_page_context">
-   		<description>The local project has CVS information associated with it but is not registered as a CVS project. This page shows the CVS information associated with the local project. Clicking "Finish" will register this project as a CVS project and enable the use of CVS menu commands. If "Validate Connection on Finish" is enabled, a connection will be attempted to the server.</description>
-		<topic label="Project checked out with another CVS tool" href="tasks/tasks-117a.htm" />
-   	</context>
-   	
-   	<context id="sharing_select_repository_page_context">
-   		<description>Either choose the repository you want from the list of existing repositories or indicate that a new repository location is to be created.</description>
- 		<topic label="Sharing a new project using CVS" href="tasks/tasks-117.htm" />
-   	</context>
-
- 	<context id="sharing_new_repository_page_context">
-   		<description>Enter the information that identifies the repository you would like to connect with and the user and connection information required to access this repository.</description>
-   		<topic label="New Repository Location Wizard" href="reference/ref-40.htm"/>
-		<topic label="CVS Repositories" href="concepts/concepts-27c.htm"/>
-		<topic label="Creating a CVS repository location" href="tasks/tasks-92.htm"/>
-	   	<topic label="Discarding a CVS repository location" href="tasks/tasks-94.htm"/>
-   	</context>
-
- 	<context id="sharing_module_page_context">
-   		<description>Specify the remote module with which the local project is shared. You can either choose to use the project name as the name that will be given to the remote module, to specify a custom module path or to select an existing module. In the first two cases, the name is relative to the repository root directory and, if the remote module does not exist, it is created.</description>
-		<topic label="Sharing a new project using CVS" href="tasks/tasks-117.htm" />
-   	</context>
-
- 	<context id="sharing_tag_selection_page_context">
-   		<description>The project being shared already exists remotely. This page allows the you to select the branch with which the project is to be shared. If the desired branch is not HEAD and does not appear in the list of Branches, perform a "Refresh from Repository" or a "Configure Tags" to automatically or manually find the tags that exist in the repository.</description>
-		<topic label="Sharing a new project using CVS" href="tasks/tasks-117.htm" />
-   	</context>
-   	
- 	<context id="sharing_sync_page_context">
-   		<description>Inspect the resources being shared and decide which resources should be shared and which should be ignored. Clicking "Finish" will provide an option to commit all outgoing changes.</description>
-		<topic label="Sharing a new project using CVS" href="tasks/tasks-117.htm" />
-   	</context>
-
- 	<context id="patch_selection_page_context">
-   		<description>This wizard allows you to generate a patch of any local changes that can be reapplied at a later time. This page allows you to specify the location where you would like the patch to be saved.</description>
- 		<topic label="Working with patches" href="tasks/tasks-68c.htm" />
-   	</context>
-
- 	<context id="patch_options_page_context">
-   		<description>This wizard page allows you to customize the format of patch that will be generated.</description>
-   		<topic label="Working with patches" href="tasks/tasks-68c.htm" />
-   	</context>
-
- 	<context id="keyword_substitution_page_context">
-   		<description>This dialog lets you change the keyword substitution mode associated with one or more files.</description>
-		<topic label="Setting the CVS keyword substitution mode" href="tasks/tasks-cvs-11.htm" />
-   	</context>
-  
-   	<context id="merge_wizard_page_context">
-   		<description>This dialog allows you to merge the changes from another branch or version into the files in your local workspace.</description>
-		<topic label="Merging from a branch" href="tasks/tasks-100b.htm" />
-   		<topic label="Merge Wizard" href="reference/ref-41a.htm"/> 
-   	</context>
-   	
- 	<context id="merge_start_page_context">
-   		<description>Select a version of the project that will be the starting (base) point of the merge operation. If the tag is not available try refreshing from the repository or configuring tags.</description>
-		<topic label="Merging from a branch" href="tasks/tasks-100b.htm" />
-   		<topic label="Merge Wizard" href="reference/ref-41a.htm"/> 
-   	</context>
-   	
- 	<context id="merge_end_page_context">
-   		<description>Select either a version or branch that will act as the end point of the merge.</description>
-		<topic label="Merging from a branch" href="tasks/tasks-100b.htm" />
-   		<topic label="Merge Wizard" href="reference/ref-41a.htm"/> 
-   	</context>
-   	
-   	<context id="checkout_module_selection_context">
-   		<description>Specify one or more remote modules to be checked out. You can either type in the module path or choose one or more existing modules to be checked out. The existing modules are not fetched until the option to select an existing module is enabled.</description>
-		<topic label="Checking out a project from a CVS repository" href="tasks/tasks-96.htm" />
-   	</context>
-   	
-   	<context id="checkout_configuration_context">
-   		<description>Specify how the selected modules are to be checkout out. For a one or more selected modules, you have the option to check out as projects or as folders in an already existing project or folder. For a single selection that has no .project file in the remote module, you will also have the option of configuring the project using the New Project wizard.</description>
-		<topic label="Checking out a project from a CVS repository" href="tasks/tasks-96.htm" />
-   	</context>
-   	
-   	<context id="checkout_location_selection_context">
-   		<description>Specify the project location in the local file system. For a single project, the location is the location of the project directory. For multiple projects, the location is the location of the parent directory for the projects.</description>
-		<topic label="Checking out a project from a CVS repository" href="tasks/tasks-96.htm" />
-   	</context>
-   	
-   	<context id="checkout_tag_selection_page_context">
-   		<description>Specify the tag to be used for the modules being checked out.</description>
-   		<topic label="Checking out a project from a CVS repository" href="tasks/tasks-96.htm" />
-   	</context>
-   	
-   	<context id="update_tag_selection_page_context">
-   		<description>This dialog allows you to select a branch or version tag and update the workspace to that tag while keeping any local changes.</description>
-   		<topic label="Replacing resources in the workbench" href="tasks/tasks-103.htm" />
-   	</context>
-   	
-   	<context id="checkout_into_resource_selection_page_context">
-   		<description>Select the parent folder under which the selected modules should be created. When checking out a single moduel, you can also specify the name of the folder to be created.</description>
-   		<topic label="Checking out a folder into an existing project" href="tasks/tasks-96b.htm"/> 
-   	</context>
-   	
-   	<context id="restore_from_repository_file_selection_page_context">
-   		<description>Browse files that have been deleted from the repository and check the revision of each file to be restored to the local workspace.</description>
-		<topic label="Restoring deleted files from the repository" href="tasks/tasks-105a.htm" />
-   	</context>
-   	
-   	<context id="working_set_folder_selection_page_context">
-        <description>Select the folders you wish to add to the working set as projects.</description>
-        <topic label="Discovering branch and version tags" href="tasks/tasks-110.htm" />
-    </context>
-    
-    <context id="commit_comment_page_context">
-       <description>Enter a comment to describe the contents of this commit.</description>
-       <topic label="Committing" href="tasks/tasks-114.htm"/>
-    </context>
-    
-    <context id="commit_file_types_page_context">
-       <description>The type of the listed file names or extensions are not known. Assign a type to thee files so the contents can be properly committed to the repository.</description>
-       <topic label="Committing" href="tasks/tasks-114.htm"/>
-    </context>
-    
-   	<!-- ********************************** -->
- 	<!-- TeamMenuActions 					-->
- 	<!-- ********************************** -->
-	
-	<context  id="manage_action_context" >
-      <description>These commands allow you to perform version/configuration management operations.</description>
-	</context>
-  
-	<context id="team_synchronize_action_context">
-   		<description>Shows any differences between the local and remote state of the selected resources in the Synchronize view.</description>
-   		<topic label="Sharing a new project using CVS" href="tasks/tasks-117.htm"/>
- 		<topic label="Synchronizing with the repository" href="tasks/tasks-115.htm"/>
-	 	<topic label="Updating" href="tasks/tasks-113.htm"/>
-	 	<topic label="Committing" href="tasks/tasks-114.htm"/>
-   	</context>
-   	
-   	<context id="team_synchronize_outgoing_action_context">
-  		<description>Shows any differences between the local and remote state of any selected resources that have outgoing changes in the Synchronize View.</description>
-		<topic label="Synchronizing with the repository" href="tasks/tasks-115.htm"/>
-	 	<topic label="Committing" href="tasks/tasks-114.htm"/>
-   	</context>
-
- 	<context id="team_commit_action_context">
-    		<description>Commits any outgoing changes in the selected resources to the server.</description>
-   		<topic label="Committing" href="tasks/tasks-114.htm"/>
-   	</context>
-
- 	<context id="team_update_action_context">
-   		<description>Updates the selected resources with any remote changes.</description>
-   		<topic label="Updating" href="tasks/tasks-113.htm"/>
-   	</context>
-   	
-   	<context id="team_switch_action_context">
-   		<description>Switch the selected resources to another branch or version while keeping any local changes.</description>
-   		<topic label="Replacing resources in the workbench" href="tasks/tasks-103.htm" />
-   	</context>
-
- 	<context id="team_create_patch_action_context">
-   		<description>Creates a patch that, when applied to the same base as the local resources, will duplicate the selected resources.</description>
-   		<topic label="Working with patches" href="tasks/tasks-68c.htm"/>
-   	</context>
-
- 	<context id="team_tag_as_version_action_context">
-   		<description>Tags the selected resources in the repository with a version name provided by the user.</description>
-   		<topic label="Creating a version of a project" href="tasks/tasks-100.htm"/>
-   		<topic label="Versioning projects in the repository" href="tasks/tasks-118.htm"/>
-   	</context>
-
- 	<context id="team_branch_action_context">
-   		<description>Creates a branch using the selected resources as the base and optionally updates the local resources to be on the new branch.</description>
-   		<topic label="CVS" href="reference/ref-47.htm"/>
- 		<topic label="Branching" href="tasks/tasks-100a.htm"/>
-   	</context>
-
- 	<context id="team_merge_action_context">
-   		<description>Merges the changes from one branch into another.</description>
-   		<topic label="CVS" href="reference/ref-47.htm"/>
-   	</context>
-
- 	<context id="team_set_keyword_mode_action_context">
-   		<description>Sets the keyword substitution mode of the selected resources.</description>
-   		<topic label="Setting the content type of a file extension" href="tasks/tasks-team-1.htm"/>
-   	</context>
-
- 	<context id="team_disconnect_action_context">
-   		<description>Disconnects the project from CVS control and optionally deletes the CVS folders.</description>
-		<topic label="Discarding a CVS repository location" href="tasks/tasks-94.htm"/>
-   	</context>
-
- 	<context id="team_add_action_context">
-   		<description>Adds the selected resources to CVS control so they can be committed and shared.</description>
-   	</context>
-
- 	<context id="team_ignore_action_context">
-   		<description>Ignores the selected resources so that they will not be considered for version control.</description>
-   	</context>
-
-   	<context id="team_restore_from_repository_action_context">
-   		<description>Load the contents of files that have been deleted from the repository so they can be restored.</description>
-   	</context>
-   		
-   	<!-- ********************************** -->
- 	<!-- Other Menu Actions 				-->
- 	<!-- ********************************** -->
-	
-	<context id="compare_with_tag_action_context">
-   		<description>Compares the selected resources with the corresponding remote resources tagged with a user specified version or branch tag.</description>
-   		<topic label="Comparing resources" href="tasks/tasks-68.htm"/>
-	 	<topic label="Comparing resources with repository versions" href="tasks/tasks-101.htm"/>
-   	</context>
-   	
-   	<context id="compare_with_latest_action_context">
-   		<description>Compares the selected resources with the corresponding remote resources with the same tag or on the same branch.</description>
-   	</context>
-
-   	<context id="compare_with_revision_action_context">
-   		<description>Compares the selected file with a user specified revision of the file.</description>
-   		<topic label="Comparing resources" href="tasks/tasks-68.htm"/>
-	 	<topic label="Comparing resources with repository versions" href="tasks/tasks-101.htm"/>
-   	</context>
-   	
- 	<context id="replace_with_tag_action_context">
-   		<description>Replaces the selected resources with the corresponding remote resources tagged with a user specified version or branch tag.</description>
-	 	<topic label="Replacing resources in the workbench" href="tasks/tasks-103.htm"/>
-   	</context>
-   	
-   	 <context id="replace_with_latest_action_context">
-   		<description>Replaces the selected resources with the corresponding remote resources with the same tag or on the same branch.</description>
-   	</context>
-    
-   	<context id="replace_with_revision_action_context">
-   		<description>Replaces the selected file with a user specified revision of the file.</description>
-   		<topic label="Navigator View" href="reference/ref-27.htm"/>
-	 	<topic label="Replacing resources in the workbench" href="tasks/tasks-103.htm"/>
-   	</context>
-   	
-   	<context id="checkout_into_action_context">
-   		<description>Checks out the selected folder into an existing project.</description>
-   		<topic label="Checking out a folder into an existing project" href="tasks/tasks-96b.htm"/>
-   	</context>
-   	
-   	<context id="checkout_as_action_context">
-   		<description>Checks out the selected folder into a user configured project. This new project can have a different name from the default one.</description>
-   	</context>
-   	
-   	<context id="checkout_as_project_action_context">
-   		<description>Checks out the selected folders into projects that corresponds to the name of each remote folder.</description>
-   		<topic label="Checking out a project from a CVS repository" href="tasks/tasks-96.htm"/>
-   	</context>
-
-   	<context id="checkout_module_action_context">
-   		<description>Checks out the selected modules into the local workspace.</description>
-   	</context>
-   	   	
-   	<context id="open_remote_file_action_context">
-   		<description>Opens the contents of the selected remote file in an editor.</description>
-   	</context>
-
- 	<context id="show_in_history_action_context">
-   		<description>Displays the revision history of the selected local or remote file in the history view.</description>
-   		<topic label="Viewing a File's Revision History" href="tasks/tasks-119.htm"/>
-   	</context>
-
-    <context id="confirm_merge_action_context">
-   		<description>Marked the selected resources as merged. This will change the base of the local resource to match that of the conflicting incoming change so the changes in the local resource can be committed. Only do this after you have manually accepted any incoming changes that should be preserved.</description>
-   		<topic label="Updating" href="tasks/tasks-113.htm"/>
-   	</context>
-   	
-    <context id="select_new_action_context">
-   		<description>Select all resources that are new and have not yet been added to CVS control.</description>
-   	</context>
-   	
- 	<context id="compare_remote_resources_action_context">
-   		<description>Compares the two selected remote resources with each other.</description>
-   		<topic label="Comparing resources" href="tasks/tasks-68.htm"/>
-	 	<topic label="Comparing resources with repository versions" href="tasks/tasks-101.htm"/>
-   	</context>
-   	
-   	<context id="compare_remote_with_tag_action_context">
-   		<description>Compares the selected resource with another branch or version of the same resource.</description>
-   	</context>
-   	
-   	<context id="copy_repository_name_action_context">
-   		<description>Copies the name of the selected repository location to the clipboard.</description>
-   	</context>
-   	
-   	<context id="remove_root_action_context">
-   		<description>Removes the selected repository locations from the Repositories View.</description>
-   	</context>
-   	
-   	<context id="add_to_branch_context">
-   		<description>Adds the selected project to the branch list in this view. This operation only adds the project to the branch in the view and does not affect the repository itself.</description>
-   	</context>
-   	
-   	<context id="move_remote_tag_action_context">
-   		<description>Tags the selected resources with an existing user specified tag, moving the tag if required.</description>
-   	</context>
-   	
-   	<context id="tag_remote_action_context">
-   		<description>Tags the selected resources with a user specified tag.</description>
-   	</context>
-
-   	<context id="show_comment_in_history_action_context">
-   		<description>Shows the complete multi-line comment of the selected entry in a separate text pane.</description>
-   		<topic label="CVS Resource History view " href="reference/ref-32a.htm"/>
-   	</context>
-   	
-   	<context id="show_tag_in_history_action_context">
-   		<description>Shows the complete list of tags for the selected entry in a separate list pane.</description>
-   		<topic label="CVS Resource History view " href="reference/ref-32a.htm"/>
-   	</context>
-   	
-   	<context id="tag_with_existing_action_context">
-   		<description>Tags the selected resources with an existing user specified tag, moving the tag if required.</description>
-   	</context>
-   	
-   	<context id="select_working_set_action_context">
-   		<description>This filter removes all root folders from the view whose name does not match a project in the selected working set.</description>
-   	</context>
-   	
-   	<context id="deselect_working_set_action_context">
-   		<description>This action removes the currently installed working set filter.</description>
-   	</context>
-   	
-    <context id="edit_working_set_action_context">
-   		<description>This action edits the currently installed working set filter.</description>
-   	</context>
-   	
- 	<!-- ********************************** -->
- 	<!-- TagConfiguration 					-->
- 	<!-- ********************************** -->
-	
-	<context id="refresh_tags_action_context">
-   		<description>Refresh the branch and version tags displayed in this view by contacting the server</description>
-   		<topic label="Discovering branch and version tags" href="tasks/tasks-110.htm"/>
-   	</context>
-   	
-	<context id="refresh_remote_project_selection_page_context">
-   		<description>Refresh the branch and version tags for the checked folders by contacting the server</description>
-   		<topic label="Discovering branch and version tags" href="tasks/tasks-110.htm"/>
-   	</context>
-   	
-	<context  id="tag_configuration_overview" >
-   		<description>Configure the branch and version tags that are shown in the workbench. By browsing remote CVS files for tags you can selectively choose, from the list of tags on each file, which tags should be remembered and which should not. You can also select the files that will be automatically examined for tags.</description>
-   		<topic label="Discovering branch and version tags" href="tasks/tasks-110.htm"/>
-   	</context>
-   
-    <context  id="tag_configuration_refreshlist" >
-      <description>This lists the files that are automatically examined for tags. By default, the .project file	is examined. But in some cases other files may have a more complete tag history and should be examined instead.</description>
-      <topic label="Discovering branch and version tags" href="tasks/tasks-110.htm"/>
-   	</context>
-   
-   	<context  id="tag_configuration_refreshaction" >
-      <description>This will fetch branch and version tags from the files that have been configured to be automatically searched for tags. If tags that you expected to see do not appear, try changing the list of files to examined via the tag configuration dialog.</description>
-      <topic label="Discovering branch and version tags" href="tasks/tasks-110.htm"/>
-   	</context>
-
- 	<!-- ********************************** -->
- 	<!-- Watch/Edit							-->
- 	<!-- ********************************** -->
- 	
- 	<context  id="team_edit_action_context" >
-      <description>Notify the server that you wish to edit this file.</description>
-   	</context>
-   	
-   	<context  id="team_unedit_action_context" >
-      <description>Notify the server that you are no longer editing this file and revert the contents to that of the base revision from which it was derived.</description>
-   	</context>
-   	
-   	<context  id="team_show_editors_action_context" >
-      <description>Show all editors of the selected resource and any of its children in the CVS Editors view.</description>
-   	</context>
-   	
-   	<context  id="cvs_editors_view_context" >
-      <description>This view shows all registered editors of one or more files.</description>
-   	</context>
-   	
-   	<context  id="editors_dialog_context" >
-      <description>This dialog shows all registered editors of the file that you are requesting to edit.</description>
-   	</context>
-   	
-   	<context  id="watch_edit_preference_page_context" >
-      <description>This page supports the configuration of CVS watch/edit. Enabling the use of watch/edit will result in all files being checked out read-only from the server. Editing a file will make the file writtable and send an edit notification to the server.</description>
-   	</context>
-   	
- 	<!-- ********************************** -->
- 	<!-- Dialogs					        -->
- 	<!-- ********************************** -->
- 	
- 	<context id="release_comment_dialog_context">
-       <description>Enter a comment to describe the contents of this commit.</description>
-    </context>
-   	<context id="user_validation_dialog_context">
-      <description>In this dialog, enter the appropriate information to log in to the repository.</description> 
-    </context>
-    <context id="tag_local_as_version_dialog_context">
-      <description>Enter the name of the version tag to be applied to the revisions that exist locally.</description>
-    </context>
-    <context id="branch_dialog_context">
-		<description>This dialog lets you specify the name of the branch you want to create and optionally lets you start working in the branch by updating the tag of the local resources to be the newly created branch tag.</description>
-    </context>
-    <context id="add_to_cvsignore_context">
-    	<description>In this dialog choose how to add the selected resources to the .cvsignore files. For each resource to be ignored, a .cvsignore file will created in its parent directory containing the pattern specified in the dialog. This will not affect resources already under version control.</description>
-    </context>
-    <context id="add_to_version_control_dialog_context">
-    	<description>Select which new resources should be added to version control before the commit. Any resources listed in this dialog which are not added first will not be committed to the server.</description>
-    </context>
-    <context id="disconnect_action_context">
-    	<description>This dialog allows you to disconnect the project from CVS control. Keeping the CVS meta information allows the project to be easily re-shared or used with other CVS tools.</description>
-    </context>
-    <context id="history_filter_dialog_context">
-        <description>This dialog allows you to specify filters that reduce the number of entries displayed in the History View. </description>
-    </context>
-    <context id="date_tag_dialog_context">
-        <description>This dialog allows you to specify a date tag which can be used to retrieve the resources that were in the repository at that time.</description>
-    </context>
-    <context id="keyboard_interactive_dialog_context">
-        <description>This dialog allows you to perform keyboard-interactive authentication for a CVS connection.</description>
-    </context>
-    <context id="replace_overwrite_dialog_context">
-        <description>There are modified resources in the selection and these local changes will be overwritten by the replace operation and lost. This dialog allows you to decide whether to continue.</description>
-    </context>
-    <context id="tag_uncommmited_dialog_context">
-        <description>There are modified resources in the selection and these changes will not be included in the version created by the tag operation. This dialog allows you to decide whether to continue.</description>
-    </context>
-        <context id="commit_set_dialog_context">
-        <description>This dialog allows you to create or edit the name and comment for a CVS change set.</description>
-    </context>
-    
- 	<!-- ********************************** -->
- 	<!-- Preference Pages 					-->
- 	<!-- ********************************** -->
- 	
- 	<context  id="prune_empty_directories_pref" >
-      <description>Enables pruning of empty directories on update and in the synchronization view. Although pruned directories aren't shown in the workbench there is actually still an empty directory in the repository.</description>
-   	</context>
-   	
-   	<context  id="quietness_level_pref" >
-      <description>Sets the amount of status information CVS prints for a command. In "Somewhat quiet" mode the printing of unimportant informational messages is suppressed. The consideration of what is important depends on each command. In "Very quiet" mode all output except what is absolutely necessary to complete the command is suppressed. In "Very Quiet" mode, some CVS servers may not communicate important information about errors that have occurred. You may want to consider using "Somewhat quiet" mode instead.</description>
-   	</context>
-   	
-  	<context  id="compression_level_pref" >
-      <description>Sets the compression level on communications with the server if it is supported by the server. Level 1 is minimal compression (slower communication but less CPU needed) and level 9 is maximum compression (faster communication but more CPU needed).</description>
-   	</context>
-
-	<context  id="default_keywordmode_pref" >
-      <description>Sets the default keyword substitution mode to use for ASCII files.</description>
-      <topic label="Setting the CVS keyword substitution mode" href="tasks/tasks-cvs-11.htm"/>
-   	</context>
-   	
-	<context  id="comms_timeout_pref" >
-      <description>Sets the amount of time in seconds to wait before timing out from a connection to the CVS server.</description>
-   	</context>
-   	
-   	<context  id="consider_content_pref" >
-      <description>Sets the default compare method for comparing and synchronizing CVS resources. By default timestamps are used to compare CVS files, and this is by far the fastest method. However, in some cases a more accurate comparison can be achieved by comparing file content. This setting can be toggled from within a compare editor or the synchronization view.</description>
-   	</context>
-   	
-	<context  id="replace_deletion_of_unmanaged_pref" >
-      <description>Allows resources not under CVS control to be deleted when replacing with resources from the repository.</description>
-   	</context>
-   	
-    <context  id="save_dirty_editors_pref" >
-      <description>Configures what happens when there are open editors with unsaved changes when a CVS operation is performed.</description>
-   	</context>
-   	
-   	<context  id="debug_protocol_pref" >
-      <description>Enabling this options will output the CVS communications trace to the console if eclipse was started with the -consolelog and -debug flags the java executable (as opposed to javaw).</description>
-   	</context>
-   	
-   	<context  id="treat_new_files_as_binary_pref" >
-      <description>Sets whether all new files are to be treated as binary. If disabled, the Team file content type preferences are used to determine the file type.</description>
-      <topic label="Setting the content type of a file extension" href="tasks/tasks-team-1.htm"/>
-   	</context>
-   	
-   	<context  id="determine_server_version" >
-      <description>Sets whether the server version should be queried on the first connection to determine compatibility.</description>
-   	</context>
-
-   	<context  id="confirm_move_tag" >
-      <description>Sets whether the user is prompted for confirmation when they perform a tag operation that requests an existing tag be moved.</description>
-   	</context>
-   	
-   	<context  id="line_end_pref" >
-      <description>Sets whether the line endings for text files should be translated to the platform line ending or left alone when files are downloaded from the server.</description>
-   	</context>
-   	
-   	<context  id="auto_refresh_tag" >
-      <description>Sets whether the tags are automatically refreshed from the repository when comparing or replacing tags from another branch or version.</description>
-   	</context>
-
-   	<context  id="change_perspective_on_show_annotations" >
-      <description>Configure how the target perspective is opened when showing annotations.</description>
-   	</context>
-   	
-   	<context  id="show_annotations_perspective" >
-      <description>Set the perspective to be opened when showing annotations.</description>
-   	</context>
-   	
-   <context  id="allow_empty_commit_comment" >
-      <description>When enabled, empty commit comments will be allowed without prompting. When disabled, you will be prompted to confirm the use of an empty commit comment.</description>
-   	</context>
-   	
-   	<context  id="console_preference_page_context" >
-      <description>This page supports the configuration of the CVS console. Properties that can be set are outpu colors and text font. The console can also be configured to open automatically when there is output.</description>
-   	</context>
-
-   	<context  id="ext_preference_page_context" >
-      <description>This page supports the configuration of the EXT connection parameters.</description>
-      <topic label="CVS" href="reference/ref-47.htm"/>
-      <topic label="CVS" href="reference/ref-19cvs.htm"></topic>
-   	</context>
-   	
-   	<context id="ext_preference_rsh_context">
-		<description>This program will be called to connect to the remote CVS server. The RSH command is invoked with following calling pattern: &lt;CVS_RSH&gt; &lt;Parameters&gt; &lt;CVS_SERVER&gt;</description> 
-	</context>
-	
-	<context id="ext_preference_param_context">
-		<description>The default parameter pattern is {host} -l {user}. It can be tailored using {host}, {user}, {password} and {port}.</description>
-	</context>
-	
-	<context id="ext_preference_server_context">
-		<description>This is the name of the remote CVS server program. Change this setting only if the remote CVS server name is different than the default</description>
-	</context>
-
-   	<context  id="decorators_preference_page_context" >
-      <description>This page supports the configuration of the CVS label and icons decorations.</description>
-      <topic label="CVS" href="reference/ref-19cvs.htm"></topic>
-      <topic label="Enabling the CVS resource decorations" href="tasks/tasks-107b.htm"/>
-   	</context>
-   	
-   	<context  id="password_management_preference_page_context" >
-      <description>This page allows you to view which repository locations have authentication information cached and allows you to purge this information.</description>
-		<topic label="CVS" href="reference/ref-19cvs.htm"></topic>
-   	</context>
-   	
-    <context  id="cvs_compare_preference_page_context" >
-      <description>This page allows you to configure various aspects of CVS synchronizations and comparisons.</description>
-      <topic label="CVS Synchronize view" href="reference/ref-33.htm"/>
-   	</context>
-   	
-   	<context  id="general_preference_page_context" >
-      <description>This page allows you to configure various aspects of CVS.</description>
-   	</context>
-   	
-   	<context  id="ssh2_preference_page_context" >
-      <description>This page allows you to configure the extssh (SSH2) connection method.</description>
-   	</context>
-   	   	   	   	
-   	<!-- ********************************** -->
- 	<!-- Views					            -->
- 	<!-- ********************************** -->
- 	
- 	<context  id="console_view_context" >
-      <description>This view shows the output of CVS operations.</description>
-      <topic label="Team programming with CVS" href="concepts/concepts-26.htm"/>
-   	</context>
-   	<context  id="repositories_view_context" >
-      <description>This view allows the browsing of the contents of known CVS repositories and the checkout of modules into the local workspace as projects.</description>
-		<topic label="CVS Repositories View " href="reference/ref-32.htm"/>
-		<topic label="Refreshing the CVS Repositories view" href="tasks/tasks-93.htm"/>
-   	</context>
-   	<context  id="resource_history_view_context" >
-      <description>This view shows the revision history of a file under CVS control.</description>
-      <topic label="CVS Resource History view " href="reference/ref-32a.htm"/>
-      <topic label="Viewing a File's Revision History" href="tasks/tasks-119.htm"/>
-   	</context>
-   	<context  id="catchup_release_viewer_context" >
-      <description>This view shows the incoming, outgoing and conflicting changes.</description>
-      <topic label="CVS Synchronize view" href="reference/ref-33.htm"/>
-		<topic label="Synchronizing with the repository" href="tasks/tasks-115.htm"/>
-   	</context>
-   	<context  id="compare_revision_view_context" >
-      <description>This view allows the comparison of the local copy of a file with the revisions from the repository. Actions available for a revision are "Get Contents" and "Get Revision". Although both replace the local file with the contents of the remote revision, "Get Revision" will make the local file "sticky". This means that changes to the file cannot be committed back to the repository.</description>
-   	</context>
-    <context  id="annotate_view_context" >
-      <description>This view shows the user and revision annotations for a file in the CVS repository.</description>
-   	</context>
-   	
-   	
-   	<!-- ********************************** -->
- 	<!-- Actions					        -->
- 	<!-- ********************************** -->
- 	
- 	<context  id="get_file_revision_action_context" >
-      <description>Loads the revision of the file into the workspace. The file will be "sticky" and the user will be unable to commit changes to the repository.</description>
-   	</context>
- 	<context  id="get_file_contents_action_context" >
-      <description>Loads the contents of the file into the workspace. The base revision of the local file will not change and the file will become dirty. Perform this action if you wish to revert to the contents of an older revision of the file.</description>
-   	</context>
-   	<context  id="get_annotate_action_context" >
-      <description>Perform the CVS annotate command on the selected resource.  This command displays the resource with the contributor and revision noted for each line.</description>
-   	</context>
-   	<context  id="new_repository_location_action_context" >
-      <description>Creates a new CVS repository location and adds it to the CVS Repositories view.</description>
-      <topic label="Create a Repository Location" href="tasks/tasks-92.htm"/>
-   	</context>
-   	<context  id="new_dev_eclipse repository_location_action_context" >
-      <description>Creates a new CVS repository location for dev.eclipse.org and adds it to the CVS Repositories view.</description>
-      <topic label="Create a Repository Location" href="tasks/tasks-92.htm"/>
-   	</context>
-   	<context  id="show_remote_folders_action_context" >
-      <description>Toggles the CVS Repositories view to show folders.</description>
-      <topic label="CVS Repositories View " href="reference/ref-32.htm"/>
-   	</context>
-   	<context  id="show_remote_modules_action_context" >
-      <description>Toggles the CVS Repositories view to show modules defined in the CVSROOT/modules file.</description>
-      <topic label="CVS Repositories View " href="reference/ref-32.htm"/>
-   	</context>
-   		
-   	<!-- ********************************** -->
- 	<!-- Sync Actions					    -->
- 	<!-- ********************************** -->
- 	
-   	<context id="sync_commit_action_context" >
-      <description>Commits the selected outgoing changes to the CVS repository. Conflicting changes are not committed; to commit them you must use the "Override and Commit" action.</description>
-   	</context>
-   	
-   	<context id="sync_forced_commit_action_context">
-      <description>Commits the selected conflicting and incoming changes to the CVS repository. Non-conflicting outgoing changes are not committed; to commit them you must use the "Commit" action.</description>
-   	</context>
-	
-	<context id="sync_update_action_context">
-      <description>Gets the selected incoming changes from the CVS repository. Conflicting changes are not updated; to update them you must use the "Override and Update" action.</description>
-   	</context>
-	
-	<context id="sync_forced_update_action_context">
-      <description>Gets the selected conflicting and outgoing changes from the CVS repository. Non-conflicting incoming changes are not updated; to update them you must use the "Update" action. If some of the selected resources are auto-mergeable (i.e. they have no line-based conflicts) then you have the option of either performing an auto-merge or replacing with the remote content.</description>
-   	</context>
-	
-	<context id="sync_add_action_context">
-      <description>Adds the selected resources to CVS control.</description>
-   	</context>
-	
-	<context id="sync_ignore_action_context">
-      <description>Adds the selected resources to the appropriate .cvsignore file. These resources will no longer be considered for repository operations.</description>
-   	</context>
-	
-	<context id="merge_update_action_context">
-      <description>Gets the selected incoming changes from the CVS repository. Conflicting changes are not updated; to update them you must use the "Override and Update" action.</description>
-   	</context>
-	
-	<context id="merge_forced_update_action_context">
-      <description>Gets the selected conflicting changes from the CVS repository. Non-conflicting incoming changes are not updated; to update them you must use the "Update" action. If some of the selected resources are auto-mergeable (i.e. they have no line-based conflicts) then you have the option of either performing an auto-merge or replacing with the remote content.</description>
-   	</context>
-	
-	<context id="merge_update_with_joinaction_context">
-      <description>Gets the selected conflicting changes from the CVS repository. Non-conflicting incoming changes are not updated; to update them you must use the "Update" action. When performing a merge, it is difficult to detect if conflicts are auto-mergeable (i.e. they have no line-based conflicts). If you believe the file is auto-mergeable, you may use this action. You will then have the option of either performing an auto-merge or replacing with the remote content.</description>
-   	</context>
-
-   	<!-- ********************************** -->
- 	<!-- Properties pages				    -->
- 	<!-- ********************************** -->
- 	
-   	<context id="repository_location_property_page_context" >
-      <description>This page shows the properties of a repository location and allows the modification of the connection method, user name and password. If properties are changed on this page, they are changed for all projects shared with this location.</description>
-      <topic label="Changing the properties of a CVS Repository Location" href="tasks/tasks-95.htm"/>
-   	</context>
-   	
-   	<context id="repository_encoding_property_page_context" >
-      <description>This page allows you to set the file system encoding used by the server hosting the repository. Setting this properly will ensure that file names and commit messages are translated properly. This setting has no effect on file contents.</description>
-   	</context>
-
-   	<context id="project_property_page_context" >
-      <description>This page shows the CVS properties of the project. The project's CVS sharing information can be changed to another compatible repository location.</description>
-      <topic label="Changing the sharing of a Project" href="tasks/tasks-117b.htm"/>
-   	</context>
-   	
-   	<context id="folder_property_page_context" >
-      <description>This page shows the CVS properties of the folder.</description>
-   	</context>
-   	
-   	<context id="file_property_page_context" >
-      <description>This page shows the CVS properties of the file.</description>
-   	</context>
-   		
-</contexts>

diff --git a/bundles/org.eclipse.platform.doc.user/contexts_Update.xml b/bundles/org.eclipse.platform.doc.user/contexts_Update.xml
deleted file mode 100644
index b86f8d7..0000000
--- a/bundles/org.eclipse.platform.doc.user/contexts_Update.xml
+++ /dev/null

@@ -1,185 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-
-<contexts>
-   
-   <!-- Context IDs added in the  code, ID is class name, where context ID is set -->
-   
-   <context  id="ConfigurationView" >
-      <description>This dialog can be used to work with installed features. By default, it only shows the features that are currently enabled. On the dialog toolbar, turn on the "Show disabled features" filter so you can see the disabled features as well.</description>
-      <topic label="Inspecting the configuration" href="tasks/tasks-33.htm"/>
-      <topic label="Enable, disable, uninstall a feature" href="tasks/tasks-35.htm"/>
-   </context>
-     
-   <context  id="ReviewPage" >
-      <description>Results of the feature searches are shown on this page. Select features you want to install.</description>
-   </context>
-   
-   
-   <context  id="CofigurationView_showUnconfFeaturesAction" >
-      <description>Show disabled features.</description>
-   </context>
-   
-   <context  id="CofigurationView_revertAction" >
-      <description>Restore your configuration to match the selected history.</description>
-   </context>
-   
-   <context  id="CofigurationView_showStatusAction" >
-      <description>Show the current configuration status for the selected feature.</description>
-   </context>
-   
-   <context  id="CofigurationView_preserveAction" >
-      <description>Save the selected configuration in the <b>Saved Configurations</b> folder.</description>
-   </context>
-   
-   <context  id="CofigurationView_removePreservedAction" >
-      <description>Delete the selected configuration from the <b>Saved Configurations</b> folder.</description>
-   </context>
-   
-   <context  id="CofigurationView_unlinkAction" >
-      <description>Unlink the selected site from the configuration.</description>
-   </context>
-   
-   <context  id="CofigurationView_propertiesAction" >
-      <description>Display properties for the selection.</description>
-   </context>
-   
-   <context  id="UpdatesView_newAction" >
-      <description>Create a new site bookmark.</description>
-   </context>
-   
-   <context  id="UpdatesView_newFolderAction" >
-      <description>Create a new folder in the Feature Updates View. Folders can be used to organize site bookmarks and search queries.</description>
-   </context>
-   
-   <context  id="UpdatesView_newSearchAction" >
-      <description>Create a new search query.</description>
-   </context>
-   
-   <context  id="UpdatesView_newLocalAction" >
-      <description>Create a site bookmark for the selected local site.</description>
-   </context>
-   
-   <context  id="UpdatesView_deleteAction" >
-      <description>Delete the selected item.</description>
-   </context>
-   
-   <context  id="UpdatesView_refreshAction" >
-      <description>Refresh the selected item.</description>
-   </context>
-   
-   <context  id="UpdatesView_fileFilterAction" >
-      <description>Select to show individual files in <b>My Computer</b>. Deselect to show only local sites and directories.</description>
-   </context>
-   
-   <context  id="UpdatesView_filterEnvironmentAction" >
-      <description>Select to show only features matching current environment. Deselect to show all available features (features not matching current environment cannot be installed).</description>
-   </context>
-   
-   <context  id="UpdatesView_showCategoriesAction" >
-      <description>Select to see features organized into site categories. Deselect to see all features as a list.</description>
-   </context>
-   
-   <context  id="UpdatesView_linkExtensionAction" >
-      <description>Link the selected site into the configuration.</description>
-   </context>
-   
-   <context  id="DetailsView_homeAction" >
-      <description>Display the Update Manager Welcome page.</description>
-   </context>
-   
-   <context  id="DetailsView_backAction" >
-      <description>Go back to the previous details page.</description>
-   </context>
-   
-   <context  id="DetailsView_forwardAction" >
-      <description>Go forward to the next details page.</description>
-   </context>
-   
-   <context  id="MainPreferencePage" >
-      <description>Set Update Manager preferences - <b>number of histories</b> to maintain before deleting; scoping of <b>new updates</b> search to service updates only, or compatible minor release updates; <b>update policy</b> to alternate update sites; <b>proxy</b> settings</description>
-      <topic label="Update policy control"  href="tasks/tasks-37.htm"/>
-   </context>
-
-      
-   <context  id="LicensePage2" >
-      <description>You must view the presented license agreement(s) and either accept or reject.</description>
-   </context>
-   
-   <context  id="ModeSelectionPage" >
-      <description>Select whether you want to search for available updates to installed features, or to search for any features found on selected update sites</description>   
-      <topic label="Installing features with the update manager" href="tasks/tasks-34.htm"/>
-      <topic label="Updating features with the update manager" href="tasks/tasks-36.htm"/>   
-   </context>
-   
-   <context  id="SitePage" >
-      <description>Add, remove or edit an update site bookmark. 
-Select the site(s) to search for features and patches.
-
-<b>Remote site</b>: the url to a web site containing features
-<b>Local site</b>: a site that is on the current machine
-<b>Archive site</b>: a local site packaged as a ZIP or JAR file
-
-You can turn on or off searching for features that don't match the environment (OS, locale, etc.)
-	</description>
-   </context>
-   
-   <context  id="NewUpdatesWizardPage" >
-      <description>Select one or more of the available updates to install.</description>
-   </context>
-   
-   <context  id="MultiTargetPage2" >
-      <description>For each feature to be installed, select an installation location from the presented choices, or add a new one. Due to co-location constraints, you may not be able to define a new location for some features.</description>
-   </context>
-   
-   <context id="OptionalFeaturesPage">
-   	  <description>Choose which optional features that are included in the main feature will be installed.</description>
-   </context>
-   
-   <context id="MultiOptionalFeaturesPage2">
-   	  <description>Choose which optional features that are included in the main features will be installed.</description>
-   </context>
-   
-   <context  id="JarVerificationPage" >
-      <description>You must accept or reject the certificate of the JAR file</description>
-   </context>
-   
-   <context  id="UserValidationDialog" >
-      <description>Enter user information.</description>
-   </context>
-   
-   <context id="MultiReviewPage2">
-      <description>Select the features you want to install. If there are errors, press <b>Error Details</b> and try fixing them by selecting or unselecting the appropriate features.</description>
-     <topic label="Installing features with the update manager" href="tasks/tasks-34.htm"/>
-   </context>
-
-   
-   <context  id="InstallableSiteForm" >
-      <description>Displays details about local site that is part of the configuration.</description>          
-   </context>
-   
-   
-   <context  id="SiteForm" >
-      <description>Displays current installation configuration details.</description> 
-      <topic label="Inspecting the configuration" href="tasks/tasks-33.htm"/>
-      <topic label="Enable, disable, uninstall a feature" href="tasks/tasks-35.htm"/>       
-   </context>
-   
-   <context  id="UnknownObjectForm" >
-      <description>Displays when an unknown object or no object has been selected in the active part.</description>
-   </context>
-   
-   
-   <context id ="SiteBookmarkPropertyPage">
-      <description>Change properties of the bookmark object.</description>
-   </context>
-   
-   <context id ="NamedObjectPropertyPage">
-      <description>Change the name of the selected object.</description>
-   </context>
-   
-   <context id ="ConfigurationPropertyPage">
-      <description>Change the name of the selected configuration.</description>
-   </context>
-   
-</contexts>

diff --git a/bundles/org.eclipse.platform.doc.user/contexts_Workbench.xml b/bundles/org.eclipse.platform.doc.user/contexts_Workbench.xml
deleted file mode 100644
index e87da2d..0000000
--- a/bundles/org.eclipse.platform.doc.user/contexts_Workbench.xml
+++ /dev/null

@@ -1,1202 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-    <!-- Actions -->
-    
-    <context id="missing">
-        <description>The context help for this user interface element could not be found.</description>
-    </context>
-    <context id="dock_on_perspective_action_context">
-        <description>This docks the perspective bar in different locations.</description>
-        <topic label="Perspectives" href="concepts/concepts-4.htm"/>
-        <topic label="Perspective Bar" href="reference/ref-3.htm"/>
-    </context>
-    <context id="show_text_perspective_action_context">
-        <description>This toggles whether text is shown for items on the perspective bar.</description>
-        <topic label="Perspectives" href="concepts/concepts-4.htm"/>
-        <topic label="Perspective Bar" href="reference/ref-3.htm"/>
-    </context>
-    
-    <context id="add_bookmark_action_context">
-        <description><b>Bookmarks</b> place an &quot;anchor&quot; at a specific line in a workbench resource.</description>
-        <topic label="Adding a Bookmark" href="tasks/tasks-81.htm"/>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="add_task_action_context">
-        <description><b>Tasks</b> place an &quot;anchor&quot; at a specific line in a workbench resource.</description>
-        <topic label="Adding a Task" href="tasks/tasks-77b.htm"/>
-        <topic label="Tasks View" href="concepts/ctskview.htm"/>
-    </context>
-    <context id="incremental_build_action_context">
-        <description>An <b>incremental build</b> compiles only the resources in the selected project that have been modified since the last build.</description>
-        <topic label="Navigator View - Rebuild All" href="reference/ref-27.htm"/>
-        <topic label="Builds" href="concepts/concepts-22.htm"/>
-        <topic label="Building Resources" href="tasks/tasks-73.htm"/>
-    </context>
-    <context id="full_build_action_context">
-        <description>A <b>full build</b> compiles the resources in the selected project from scratch. This kind of build is only performed when a manual build is done.</description>
-        <topic label="Navigator View - Rebuild All" href="reference/ref-27.htm"/>
-        <topic label="Builds" href="concepts/concepts-22.htm"/>
-        <topic label="Building Resources" href="tasks/tasks-73.htm"/>
-    </context>
-    <context id="global_incremental_build_action_context">
-        <description>An incremental build compiles only the resources that have been modified since the last build.</description>
-        <topic label="Builds" href="concepts/concepts-22.htm"/>
-        <topic label="Building Resources" href="tasks/tasks-73.htm"/>
-    </context>
-    <context id="global_full_build_action_context">
-        <description>A <b>full build</b> compiles the entire workbench from scratch. This kind of build is only performed when a manual build is done.</description>
-        <topic label="Builds" href="concepts/concepts-22.htm"/>
-        <topic label="Building Resources" href="tasks/tasks-73.htm"/>
-    </context>
-    <context id="close_resource_action_context">
-        <description>This closes the selected resource.</description>
-        <topic label="Closing Resources" href="tasks/tasks-47.htm"/>
-        <topic label="Navigator View - Close" href="reference/ref-27.htm"/>
-    </context>
-    <context id="open_resource_action_context">
-        <description>This opens the selected resource.</description>
-        <topic label="Opening Resources" href="tasks/tasks-46.htm"/>
-        <topic label="Navigator View - Open" href="reference/ref-27.htm"/>
-    </context>
-    <context id="open_file_action_context">
-        <description>This causes the selected resource to open in the editor area or in the specified external editor.</description>
-        <topic label="Navigator View - Open With..." href="reference/ref-27.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="open_system_editor_action_context">
-        <description>This causes the selected resource to open in the default system editor for this file type.</description>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-        <topic label="Editing a File Externally" href="tasks/tasks-52.htm"/>
-    </context>
-    <context id="refresh_action_context">
-        <description>This refreshes the contents and display of the view.</description>
-        <topic label="Navigator View - Refresh" href="reference/ref-27.htm"/>
-    </context>
-    <context id="move_resource_action_context">
-        <description>This command allows you to move a resource from one location to another.</description>
-        <topic label="Moving Resources" href="tasks/tasks-63.htm"/>
-        <topic label="Navigator View - Move" href="reference/ref-27.htm"/>
-    </context>
-    <context id="copy_resource_action_context">
-        <description>This command allows you to copy a resource from one location to another.</description>
-        <topic label="Navigator View - Copy" href="reference/ref-27.htm"/>
-    </context>
-    <context id="move_project_action_context">
-        <description>This command allows you to move a project from one location to another.</description>
-        <topic label="Moving Resources" href="tasks/tasks-63.htm"/>
-        <topic label="Navigator View - Move" href="reference/ref-27.htm"/>
-    </context>
-    <context id="copy_project_action_context">
-        <description>This command allows you to copy a project from one location to another.</description>
-        <topic label="Navigator View - Copy" href="reference/ref-27.htm"/>
-    </context>
-    <context id="rename_resource_action_context">
-        <description>This command allows you to supply a new name for the selected resource.</description>
-        <topic label="Renaming Resources" href="tasks/tasks-66.htm"/>
-        <topic label="Navigator View - Rename" href="reference/ref-27.htm"/>
-    </context>
-    <context id="delete_resource_action_context">
-        <description>This command allows you to delete the selected resource.</description>
-        <topic label="Deleting Resources" href="tasks/tasks-67.htm"/>
-        <topic label="Navigator View - Delete" href="reference/ref-27.htm"/>
-    </context>
-    <context id="delete_retarget_action_context">
-        <description>This command deletes the selected resource or element.</description>
-        <topic label="Deleting Resources" href="tasks/tasks-67.htm"/>
-        <topic label="Navigator View - Delete" href="reference/ref-27.htm"/>
-    </context>
-    <context id="property_dialog_action_context">
-        <description>This command displays the various properties of the selected resource.</description>
-        <topic label="Viewing Resource Properties" href="tasks/tasks-49.htm"/>
-        <topic label="Navigator View - Properties" href="reference/ref-27.htm"/>
-    </context>
-    <context id="project_property_dialog_action_context">
-        <description>This command displays the various properties of the project for the selected resource.</description>
-        <topic label="Project Menu - Properties" href="reference/ref-59.htm"/>
-        <topic label="Viewing Resource Properties" href="tasks/tasks-49.htm"/>
-    </context>
-    <context id="create_folder_action_context">
-        <description>This command allows you to create a new folder container.</description>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-        <topic label="Creating Resources - Folders" href="tasks/tasks-43.htm"/>
-        <topic label="New Folder Wizard" href="reference/ref-38.htm"/>
-    </context>
-    <context id="create_file_action_context">
-        <description>This command allows you to create a new file.</description>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-        <topic label="Creating Resources - Files" href="tasks/tasks-44.htm"/>
-        <topic label="New File Wizard" href="reference/ref-39.htm"/>
-    </context>
-    <context id="new_action_context">
-        <description>This command allows you to create a new item such as a resource.</description>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-        <topic label="Workbench New Wizards" href="reference/ref-37.htm"/>
-    </context>
-    <context id="import_action_context">
-        <description>This command allows you to import resources.</description>
-        <topic label="Importing" href="tasks/tasks-53.htm"/>
-        <topic label="Importing from a Directory" href="tasks/tasks-55.htm"/>
-        <topic label="Importing from a Zip File" href="tasks/tasks-55bg.htm"/>
-        <topic label="File Menu - Import" href="reference/ref-56.htm"/>
-    </context>
-    <context id="export_action_context">
-        <description>This command allows you to export resources.</description>
-        <topic label="Exporting" href="tasks/tasks-57.htm"/>
-        <topic label="Exporting to the File System" href="tasks/tasks-59.htm"/>
-        <topic label="Exporting to a Zip File" href="tasks/tasks-59ag.htm"/>
-        <topic label="File Menu - Export" href="reference/ref-56.htm"/>
-    </context>
-    <context id="scrub_local_action_context">
-        <description>The workbench is preparing for a build.</description>
-        <topic label="Builds" href="concepts/concepts-22.htm"/>
-    </context>
-    <context id="set_page_action_context">
-        <description>This command refreshes the workbench display.</description>
-        <topic label="Navigator View - Refresh" href="reference/ref-27.htm"/>
-    </context>
-    <context id="save_perspective_action_context">
-        <description>This menu option allows you to save the current perspective as a defined perspective.</description>
-        <topic label="Perspectives" href="concepts/concepts-4.htm"/>
-        <topic label="Saving Perspectives" href="tasks/tasks-9i.htm"/>
-        <topic label="Window Menu - Save Perspective As" href="reference/ref-60.htm"/>
-    </context>
-    <context id="save_as_action_context">
-        <description>This command allows you to save the resource being edited to another workbench location.</description>
-        <topic label="File Menu - Save As" href="reference/ref-56.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="save_all_action_context">
-        <description>This command allows you to save all open resources in the editor area at once.</description>
-        <topic label="File Menu - Save All" href="reference/ref-56.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="save_action_context">
-        <description>This command saves the resource that is currently active in the editor area.</description>
-        <topic label="File Menu - Save" href="reference/ref-56.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="about_action_context">
-        <description>This command displays product information.</description>
-        <topic label="Help Menu - About" href="reference/ref-61.htm"/>
-    </context>
-    <context id="close_all_action_context">
-        <description>This command closes all editors that are currently open in the editor area.</description>
-        <topic label="File Menu - Close All" href="reference/ref-56.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="close_page_action_context">
-        <description>This command closes the active perspective.</description>
-        <topic label="Perspectives - Concept" href="concepts/concepts-4.htm"/>
-        <topic label="Window Menu - Close Perspective" href="reference/ref-60.htm"/>
-        <topic label="Perspectives - Reference" href="reference/ref-6.htm"/>
-    </context>
-    <context id="close_part_action_context">
-        <description>This command closes the currently-active editor.</description>
-        <topic label="File Menu - Close" href="reference/ref-56.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="edit_action_sets_action_context">
-        <description>This command allows you to customize the action sets available in the workbench menu bar and toolbar.</description>
-        <topic label="Configuring Perspectives" href="tasks/tasks-9k.htm"/>
-        <topic label="Window Menu - Customize Perspective" href="reference/ref-60.htm"/>
-    </context>
-    <context id="edit_perspectives_action_context">
-        <description>This command allows you to delete or reset defined perspectives or to define the default perspective.</description>
-        <topic label="Perspectives - Concept" href="concepts/concepts-4.htm"/>
-        <topic label="Changing Where Perspectives Open" href="tasks/tasks-24.htm"/>
-        <topic label="Perspectives - Reference" href="reference/ref-6.htm"/>
-    </context>
-    <context id="close_all_pages_action_context">
-        <description>This closes all the perspectives that are currently open.</description>
-        <topic label="Perspectives - Concept" href="concepts/concepts-4.htm"/>
-        <topic label="Window Menu - Close All Perspectives" href="reference/ref-60.htm"/>
-    </context>
-    <context id="open_new_page_action_context">
-        <description>This opens a new page.</description>
-        <topic label="Perspectives - Concept" href="concepts/concepts-4.htm"/>
-        <topic label="New Perspectives" href="tasks/tasks-9f.htm"/>
-        <topic label="Window Menu - Open Perspective" href="reference/ref-60.htm"/>
-    </context>
-    <context id="open_preferences_action_context">
-        <description>This opens the preferences dialog.</description>
-        <topic label="Workbench - Preferences" href="reference/ref-10.htm"/>
-    </context>
-    <context id="open_new_window_action_context">
-        <description>This opens a new window.</description>
-        <topic label="Opening perspectives" href="tasks/tasks-9f.htm"/>
-        <topic label="Changing Where Perspectives Open" href="tasks/tasks-24.htm"/>
-        <topic label="Workbench" href="concepts/concepts-2.htm"/>
-        <topic label="Perspectives" href="concepts/concepts-4.htm"/>
-    </context>
-    <context id="open_new_action_context">
-        <description>This opens a new perspective.</description>
-        <topic label="Perspectives - Concept" href="concepts/concepts-4.htm"/>
-        <topic label="Opening New Perspectives" href="tasks/tasks-24.htm"/>
-        <topic label="Window Menu - Open Perspective" href="reference/ref-60.htm"/>
-    </context>
-    <context id="next_page_action_context">
-        <description>This will show the next open perspective.</description>
-        <topic label="Perspectives - Concept" href="concepts/concepts-4.htm"/>
-        <topic label="Changing Where Perspectives Open" href="tasks/tasks-24.htm"/>
-    </context>
-    <context id="quick_start_action_context">
-        <description>This will open the welcome editor.</description>
-        <topic label="Help Menu - Welcome" href="reference/ref-61.htm"/>
-    </context>
-    <context id="tips_and_tricks_action_context">
-        <description>This will open the tips and tricks help page.</description>
-        <topic label="Help Menu - Tips and Tricks" href="reference/ref-61.htm"/>
-    </context>
-    <context id="quit_action_context">
-        <description>This will save the workspace and exit.</description>
-        <topic label="File Menu - Exit" href="reference/ref-56.htm"/>
-    </context>
-    <context id="reset_perspective_action_context">
-        <description>This will reset the perspective to its original (default) layout.</description>
-        <topic label="Perspectives" href="concepts/concepts-4.htm"/>
-        <topic label="Reset Perspectives" href="tasks/tasks-9j.htm"/>
-        <topic label="Window Menu - Reset Perspective" href="reference/ref-60.htm"/>
-    </context>    
-    <context id="target_editors_visibility_action_context">
-        <description>This allows you to hide or show the editor area.  You can increase the area other views have to display themselves when you hide the editor area.</description>
-        <topic label="Window Menu - Show/Hide Editors" href="reference/ref-60.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="switch_to_perspective_action_context">
-        <description>This opens a new perspective, to be selected by the user.</description>
-        <topic label="Perspectives - Concept" href="concepts/concepts-4.htm"/>
-        <topic label="Switching Between Perspectives" href="tasks/tasks-28.htm"/>
-        <topic label="Window Menu - Open Perspective" href="reference/ref-60.htm"/>
-        <topic label="Perspectives - Reference" href="reference/ref-6.htm"/>
-    </context>
-    <context id="show_view_action_context">
-        <description>This will show a view, to be selected by the user.</description>
-        <topic label="Displaying Views" href="tasks/tasks-3.htm"/>
-        <topic label="Window Menu - Show View" href="reference/ref-60.htm"/>
-    </context>
-    <context id="show_view_other_action_context">
-        <description>Opens a dialog to select a view to show.</description>
-        <topic label="Displaying Views" href="tasks/tasks-3.htm"/>
-        <topic label="Window Menu - Show View" href="reference/ref-60.htm"/>
-    </context>
-    <context id="open_perspective_action_context">
-        <description>Opens the selected perspective.</description>
-        <topic label="Opening Perspectives" href="tasks/tasks-9f.htm"/>
-        <topic label="Window Menu - Open Perspective" href="reference/ref-60.htm"/>
-    </context>
-    <context id="open_perspective_other_action_context">
-        <description>Opens a dialog to select a perspective to open.</description>
-        <topic label="Opening Perspectives" href="tasks/tasks-9f.htm"/>
-        <topic label="Window Menu - Open Perspective" href="reference/ref-60.htm"/>
-    </context>
-    <context id="remove_bookmark_action_context">
-        <description>Remove a bookmark.</description>
-        <topic label="Deleting a Bookmark" href="tasks/tasks-82.htm"/>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="open_bookmark_action_context">
-        <description>Open resource in which a bookmark resides.</description>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="select_all_bookmark_action_context">
-        <description>Select all bookmarks.</description>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="filter_selection_action_context">
-        <description>This command allows filtering of the types shown in the resource navigator.</description>
-        <topic label="Navigator View - Filters" href="reference/ref-27.htm"/>
-    </context>
-    <context id="goto_resource_action_context">
-        <description>Go to the selected resource.</description>
-        <topic label="Navigator View - Go To" href="reference/ref-27.htm"/>
-    </context>
-    <context id="resource_navigator_move_action_context">
-        <description>Move the selected resource to another location.</description>
-        <topic label="Moving Resources" href="tasks/tasks-63.htm"/>
-        <topic label="Navigator View - Move" href="reference/ref-27.htm"/>
-    </context>
-    <context id="resource_navigator_rename_action_context">
-        <description>Rename the selected resource.</description>
-        <topic label="Renaming Resources" href="tasks/tasks-66.htm"/>
-        <topic label="Navigator View - Rename" href="reference/ref-27.htm"/>
-    </context>
-    <context id="show_in_navigator_action_context">
-        <description>Show the selected resource in the Navigator view.</description>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-        <topic label="Navigator View" href="reference/ref-27.htm"/>
-    </context>
-    <context id="sort_view_action_context">
-        <description>This command changes the sort order of the types shown in the resource navigator.</description>
-        <topic label="Sorting Resources" href="tasks/tasks-48.htm"/>
-        <topic label="Navigator View - Sort" href="reference/ref-27.htm"/>
-    </context>
-    <context id="properties_categories_action_context">
-        <description>Show property values grouped according to category.</description>
-        <topic label="Properties View" href="concepts/cpropview.htm"/>
-    </context>
-    <context id="properties_defaults_action_context">
-        <description>Sets the value of the selected property to its default value.</description>
-        <topic label="Properties View" href="concepts/cpropview.htm"/>
-    </context>
-    <context id="properties_filter_action_context">
-        <description>Filter properties.</description>
-        <topic label="Properties View" href="concepts/cpropview.htm"/>
-    </context>
-    <context id="purge_completed_task_action_context">
-        <description>Remove all completed tasks from the list.</description>
-        <topic label="Deleting Tasks" href="tasks/tasks-78.htm"/>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="new_task_action_context">
-        <description>Create a new task.</description>
-        <topic label="Adding an Unassociated Task" href="tasks/tasks-77.htm"/>
-        <topic label="Adding an Associated Task" href="tasks/tasks-77b.htm"/>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="remove_task_action_context">
-        <description>Remove a task from this list.</description>
-        <topic label="Deleting Tasks" href="tasks/tasks-78.htm"/>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="goto_task_action_context">
-        <description>Opens the resource associated with a task.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="undo_action_context">
-        <description>Undo the previous edit.</description>
-        <topic label="Edit Menu - Undo" href="reference/ref-57.htm"/>
-    </context>
-    <context id="redo_action_context">
-        <description>Redo the previous edit.</description>
-        <topic label="Edit Menu - Redo" href="reference/ref-57.htm"/>
-    </context>
-    <context id="cut_action_context">
-        <description>Cut the selected text to the clipboard.</description>
-        <topic label="Edit Menu - Cut" href="reference/ref-57.htm"/>
-    </context>
-    <context id="copy_action_context">
-        <description>Copy the selection to the clipboard.</description>
-        <topic label="Edit Menu - Copy" href="reference/ref-57.htm"/>
-    </context>
-    <context id="paste_action_context">
-        <description>Paste the contents of the clipboard at the current cursor position.</description>
-        <topic label="Edit Menu - Paste" href="reference/ref-57.htm"/>
-    </context>
-    <context id="delete_action_context">
-        <description>Delete the selection.</description>
-        <topic label="Edit Menu - Delete" href="reference/ref-57.htm"/>
-    </context>
-    <context id="selectAll_action_context">
-        <description>Select all contents of the file.</description>
-        <topic label="Edit Menu - Select All" href="reference/ref-57.htm"/>
-    </context>
-    <context id="ShiftLeft_action_context">
-        <description>Shift selected text to the left, reducing the indentation.</description>
-    </context>
-    <context id="ShiftRight_action_context">
-        <description>Shift selected text to the right, increasing the indentation.</description>
-    </context>
-    <context id="find_action_context">
-        <description>This will bring up a dialog to specify text to search for in the editor.</description>
-        <topic label="Edit Menu - Find/Replace" href="reference/ref-57.htm"/>
-    </context>
-    <context id="bookmark_action_context">
-        <description>Add a bookmark on this resource.</description>
-        <topic label="Edit Menu - Add Bookmark" href="reference/ref-57.htm"/>
-    </context>
-    <context id="addTask_action_context">
-        <description>Add a task associated with this resource.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="revert_action_context">
-        <description>Revert to saved contents.</description>
-    </context>
-    <context id="GotoLine_action_context">
-        <description>Place cursor position at beginning of a specified line.</description>
-    </context>
-    <context id="open_workspace_file_action_context">
-        <description>Opens an editor on a specified resource.</description>
-        <topic label="Navigate Menu - Open Resource" href="reference/ref-58.htm"/>
-    </context>
-    <context id="print_action_context">
-        <description>This command prints the resource that is currently active in the editor area.</description>
-    </context>
-    <context id="select_working_set_action_context">
-        <description>Selects a working set from the list to be the active one.</description>
-    </context>
-    <context id="clear_working_set_action_context">
-        <description>Deselects the active working set.</description>
-    </context>
-    <context id="edit_working_set_action_context">
-        <description>Edits the contents of the active working set.</description>
-    </context>
-    <context id="show_in_action_context">
-        <description>Shows the current selection in the specified view.</description>
-    </context>
-    <context id="navigation_history_forward">
-        <description>Moves forward in the navigation history.</description>
-        <topic label="Navigate Menu - Forward" href="reference/ref-58.htm"/>
-    </context>
-    <context id="navigation_history_backward">
-        <description>Moves backward in the navigation history.</description>
-        <topic label="Navigate Menu - Back" href="reference/ref-58.htm"/>
-    </context>
-    <!-- Dialogs -->
-    <context id="about_dialog_context">
-        <description>This dialog displays product information.</description>
-        <topic label="Help Menu - About" href="reference/ref-61.htm"/>
-    </context>
-    <context id="action_set_selection_dialog_context">
-        <description>Each perspective includes a predefined set of actions that are accessible from the menu bar and workbench toolbar. Related actions are grouped into action sets.</description>
-        <topic label="Configuring Perspectives" href="tasks/tasks-9k.htm"/>
-        <topic label="Window Menu - Customize Perspective" href="reference/ref-60.htm"/>
-    </context>
-    <context id="editor_selection_dialog_context">
-        <description>In this dialog, you can associate various embedded and external editors with the various types of workbench resources.</description>
-        <topic label="Preferences - File Associations" href="reference/ref-13.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="file_extension_dialog_context">
-        <description>In this dialog, indicate the extension for the file type you wish to identify.</description>
-        <topic label="Preferences - File Associations" href="reference/ref-13.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="preference_dialog_context">
-        <description>This dialog allows you to set your workbench preferences.</description>
-        <topic label="Preferences Dialog" href="reference/ref-72.htm"/>
-    </context>
-    <context id="property_dialog_context">
-        <description>This dialog allows you to view or change the properties of the selected resource.</description>
-        <topic label="Navigator View - Properties Page" href="reference/ref-27.htm"/>
-        <topic label="Resource Properties" href="tasks/tasks-49.htm"/>
-    </context>
-    <context id="save_perspective_dialog_context">
-        <description>Dialog to save a perspective specified by the user.</description>
-        <topic label="Perspectives" href="concepts/concepts-4.htm"/>
-        <topic label="Saving Perspectives" href="tasks/tasks-9i.htm"/>
-    </context>
-    <context id="select_perspective_dialog_context">
-        <description>Dialog to select a perspective.</description>
-        <topic label="Perspectives - Concept" href="concepts/concepts-4.htm"/>
-        <topic label="Saving Perspectives" href="tasks/tasks-9i.htm"/>
-        <topic label="Window Menu" href="reference/ref-60.htm"/>
-    </context>
-    <context id="project_location_selection_dialog_context">
-        <description>Dialog to select the location of a project.</description>
-    </context>
-    <context id="show_view_dialog_context">
-        <description>Dialog to select a view to show.</description>
-        <topic label="Displaying Views" href="tasks/tasks-3.htm"/>
-    </context>
-    <context id="save_as_dialog_context">
-        <description>Dialog to specify the name and location of the a resource to save.</description>
-    </context>
-    <context id="type_filtering_dialog_context">
-        <description>Use this dialog to filter file types.</description>
-        <topic label="Export Wizard" href="reference/ref-71.htm"/>
-        <topic label="Import Wizard" href="reference/ref-70.htm"/>
-    </context>
-    <context id="container_selection_dialog_context">
-        <description>Dialog to select a folder.</description>
-    </context>
-    <context id="file_selection_dialog_context">
-        <description>Dialog to select a file.</description>
-    </context>
-    <context id="list_selection_dialog_context">
-        <description>Dialog to select an item from a list.</description>
-    </context>
-    <context id="yes_no_cancel_list_selection_dialog_context">
-        <description>Dialog to accept, reject, or cancel a selection from a list.</description>
-    </context>
-    <context id="resource_selection_dialog_context">
-        <description>Dialog to select a resource.</description>
-    </context>
-    <context id="goto_resource_dialog_context">
-        <description>Dialog to select a resource to find in the workspace.</description>
-    </context>
-    <context id="task_filters_dialog_context">
-        <description>Dialog that allows you to show or hide tasks based on certain criteria.</description>
-        <topic label="Filtering Your Task List" href="tasks/tasks-79.htm"/>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="find_replace_dialog_context">
-        <description>Dialog to find and replace specified text.</description>
-		<topic label="Available Regular Expressions" href="http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html" />
-    </context>
-    <context id="goto_line_dialog_context">
-        <description>Dialog to specify a line at which to place the cursor.</description>
-    </context>
-    <!-- Editors -->
-    <context id="welcome_editor_context">
-        <description>A quick, simple guide to introduce new users to some basic tasks.</description>
-        <topic label="Help Menu" href="reference/ref-61.htm"/>
-    </context>
-    <context id="text_editor_context">
-        <description>A text editor is used to edit files.</description>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="system_summary_editor_context">
-        <description>Shows the product configuration details.</description>
-    </context>
-    <!-- Preference pages -->
-    <context id="file_editors_preference_page_context">
-        <description>On this preferences page, you can associate various embedded and external editors with the various types of workbench resources.</description>
-        <topic label="Preferences - File Associations" href="reference/ref-13.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="build_order_preference_page_context">
-        <description>Allows you to change the order that projects in the workspace are built.</description>
-        <topic label="Changing the Build Order" href="tasks/tasks-14.htm"/>
-    </context>
-    <context id="file_states_preference_page_context">
-        <description>This preference page is used to configure the local file history for the workbench.</description>
-        <topic label="Local History" href="concepts/concepts-17a.htm"/>
-        <topic label="Preferences - Local History" href="reference/ref-14.htm"/>
-        <topic label="Navigator - Local History" href="reference/ref-27.htm"/>
-    </context>
-    <context id="perspectives_preference_page_context">
-        <description>Allows you to set the state of existing perspectives.</description>
-        <topic label="Preferences - Perspectives" href="reference/ref-15.htm"/>
-        <topic label="Perspectives" href="concepts/concepts-4.htm"/>
-    </context>
-    <context id="views_preference_page_context">
-        <description>This preference page is used to set preferences for the look and layout of views in the workbench.</description>
-        <topic label="Preferences - Appearance" href="reference/ref-16.htm"/>
-        <topic label="Views" href="concepts/concepts-5.htm"/>
-    </context>
-    <context id="workspace_preference_page_context">
-        <description>This preference page is used to set the IDE-specific preferences settings related in workspace.</description>
-        <topic label="Preferences - Workspace" href="reference/ref-9.htm"/>
-    </context>    
-    <context id="workbench_preference_page_context">
-        <description>Allows you to set general workbench preferences.</description>
-        <topic label="Preferences - General" href="reference/ref-10.htm"/>
-    </context>
-    <context id="font_preference_page_context">
-        <description>This preference page is used to set the fonts used within the workbench.</description>
-        <topic label="Preferences - Colors and Fonts" href="reference/ref-fonts.htm"/>
-    </context>
-    <context id="keys_preference_page_context">
-        <description>This preference page is used to set the key bindings used within the workbench.</description>
-        <topic label="Preferences - Keys" href="concepts/accessibility/keyboardshortcuts.htm"/>
-    </context>
-    <context id="workbench_editor_preference_page_context">
-        <description>This preference page is used to set preferences for the editor area in the workbench.</description>
-        <topic label="Preferences - Editors" href="reference/ref-texteditorprefs.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="compare_viewers_preference_page_context">
-        <description>This preference page is used to set preferences for compare viewers in the workbench.</description>
-        <topic label="Preferences - Compare" href="reference/ref-11.htm"/>
-        <topic label="Comparing Resources" href="reference/ref-25.htm"/>
-    </context>
-	<context id="capabilities_preference_page_context">
-		<description>This preference page is used to set preferences relating to workbench capabilities.</description>
-		<topic label="Preferences - Capabilities" href="reference/ref-activitiespref.htm"/>
-	</context>
-    <context id="content_types_preference_page_context">
-        <description>This preference page is used to set preferences relating to resource content types.</description>
-        <topic label="Preferences - Content Types" href="reference/ref-content-type.htm"/>
-        <topic label="Preferences - File Associations" href="reference/ref-13.htm"/> 
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-    </context>
-    <!-- Property pages -->
-    <context id="project_reference_property_page_context">
-        <description>Allows you to set referenced projects.</description>
-        <topic label="Navigator View - Properties Page" href="reference/ref-27.htm"/>
-        <topic label="Viewing Resource Properties" href="tasks/tasks-49.htm"/>
-    </context>
-    <context id="resource_info_property_page_context">
-        <description>Allows you to view information about the selected resource.</description>
-        <topic label="Navigator View - Properties Page" href="reference/ref-27.htm"/>
-        <topic label="Viewing Resource Properties" href="tasks/tasks-49.htm"/>
-    </context>
-    <!-- Views -->
-    <context id="bookmark_view_context">
-        <description>View to show all bookmarks.</description>
-        <topic label="Views" href="concepts/concepts-5.htm"/>
-        <topic label="Bookmarks View" href="reference/ref-28.htm"/>
-    </context>
-    <context id="content_outline_context">
-        <description>View to show the outline (if applicable) of a resource being edited.</description>
-        <topic label="Views" href="concepts/concepts-5.htm"/>
-        <topic label="Outline View" href="concepts/coutline.htm"/>
-    </context>
-    <context id="resource_view_context">
-        <description>This view shows all resources in the workspace.</description>
-        <topic label="Views" href="concepts/concepts-5.htm"/>
-        <topic label="Navigator View" href="reference/ref-27.htm"/>
-    </context>
-    <context id="property_sheet_view_context">
-        <description>This view shows the properties of a selected resource.</description>
-        <topic label="Views" href="concepts/concepts-5.htm"/>
-        <topic label="Properties View" href="concepts/cpropview.htm"/>
-    </context>
-    <context id="task_list_view_context">
-        <description>This view shows build problems and tasks (reminders) that are either user-created or are automatically generated during building.</description>
-        <topic label="Views" href="concepts/concepts-5.htm"/>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <!-- Property sheet -->
-    <context id="property_sheet_page_help_context">
-        <description>The Properties view displays the properties of the selected resource.</description>
-        <topic label="Views" href="concepts/concepts-5.htm"/>
-        <topic label="Properties View" href="concepts/cpropview.htm"/>
-    </context>
-    <!-- Windows -->
-    <context id="detached_window_context">
-        <description>Views can be undocked from a workbench window and can exist in floating windows on the desktop.</description>
-        <topic label="Docking Views" href="tasks/tasks-3e.htm"/>
-        <topic label="Workbench Window Layout" href="reference/ref-23.htm"/>
-        <topic label="Views" href="concepts/concepts-5.htm"/>
-    </context>
-    <context id="workbench_window_context">
-        <description>Each workbench window contains one or more perspectives, which are made up of various views and editors.</description>
-        <topic label="Workbench" href="concepts/concepts-2.htm"/>
-        <topic label="Perspectives" href="concepts/concepts-4.htm"/>
-        <topic label="Workbench Management" href="tasks/tasks-1.htm"/>
-    </context>
-    <!-- Wizard pages -->
-    <context id="new_project_wizard_page_context">
-        <description>This wizard helps you create a new project in the workbench.</description>
-        <topic label="New Project Wizard" href="reference/ref-37.htm"/>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-        <topic label="Creating Resources - Projects" href="tasks/tasks-42.htm"/>
-    </context>
-    <context id="new_project_reference_wizard_page_context">
-        <description>This wizard page allows you to select other projects which this project will reference.</description>
-        <topic label="Select Referenced Projects Page" href="reference/ref-37.htm"/>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-    </context>
-    <context id="new_folder_wizard_page_context">
-        <description>Wizard to guide you through creation of a new folder resource.</description>
-        <topic label="New Folder Wizard" href="reference/ref-38.htm"/>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-        <topic label="Creating Resources - Folders" href="tasks/tasks-43.htm"/>
-    </context>
-    <context id="new_file_wizard_page_context">
-        <description>Wizard to guide you through creation of a new file resource.</description>
-        <topic label="New File Wizard" href="reference/ref-39.htm"/>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-        <topic label="Creating Resources - Files" href="tasks/tasks-44.htm"/>
-    </context>
-    <context id="new_wizard_selection_wizard_page_context">
-        <description>Choose the type of resource you would like to create.</description>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-    </context>
-    <context id="export_wizard_selection_wizard_page_context">
-        <description>Choose the type of export you would like to do.</description>
-        <topic label="Using the Export Wizard" href="reference/ref-71.htm"/>
-        <topic label="Exporting resources" href="tasks/tasks-57.htm"/>
-        <topic label="Exporting to the File System" href="tasks/tasks-59.htm"/>
-        <topic label="Exporting to a Zip File" href="tasks/tasks-59ag.htm"/>
-    </context>
-    <context id="import_wizard_selection_wizard_page_context">
-        <description>Choose the type of import you would like to do.</description>
-        <topic label="Using the Import Wizard" href="reference/ref-70.htm"/>
-        <topic label="Importing resources with the Import Wizard" href="tasks/tasks-55.htm"/>
-    </context>
-    <context id="file_system_export_wizard_page">
-        <description>This page helps you provide all the information required to export resources to the file system.</description>
-        <topic label="Using the Export Wizard" href="tasks/tasks-59.htm"/>
-        <topic label="Export Wizard" href="reference/ref-71.htm"/>
-    </context>
-    <context id="file_system_import_wizard_page">
-        <description>This page helps you provide all the information required to import files from the file system.</description>
-        <topic label="Importing from File System" href="tasks/tasks-55.htm"/>
-        <topic label="Import Wizard" href="reference/ref-70.htm"/>
-    </context>
-    <context id="zip_file_export_wizard_page">
-        <description>This page helps you provide all the information required to export resources from the workspace to an archive file.</description>
-        <topic label="Exporting to a Zip File" href="tasks/tasks-59ag.htm"/>
-        <topic label="Export Wizard" href="reference/ref-71.htm"/>
-    </context>
-    <context id="zip_file_import_wizard_page">
-        <description>This page helps you provide all the information required to import files from an archive file into the workspace.</description>
-        <topic label="Importing from a Zip File" href="tasks/tasks-55bg.htm"/>
-        <topic label="Import Wizard" href="reference/ref-70.htm"/>
-    </context>
-    <!-- Wizards -->
-    <context id="new_wizard_context">
-        <description>These wizards allow you to create new resources and/or elements</description>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-    </context>
-    <context id="new_wizard_shortcut_context">
-        <description>Opens a creation wizard.</description>
-    </context>
-    <context id="new_file_wizard_context">
-        <description>Wizard to assist in creating a new file resource.</description>
-        <topic label="New File Wizard" href="reference/ref-39.htm"/>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-        <topic label="Creating Resources - Files" href="tasks/tasks-44.htm"/>
-    </context>
-    <context id="new_folder_wizard_context">
-        <description>Wizard to assist in creating a new folder resource.</description>
-        <topic label="New Folder Wizard" href="reference/ref-38.htm"/>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-        <topic label="Creating Resources - Folders" href="tasks/tasks-43.htm"/>
-    </context>
-    <context id="new_project_wizard_context">
-        <description>Wizard to assist in creating a new project.</description>
-        <topic label="New Project Wizard" href="reference/ref-37.htm"/>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-        <topic label="Creating Resources - Projects" href="tasks/tasks-42.htm"/>
-    </context>
-    <context id="import_wizard_context">
-        <description>Wizard to assist in importing resources.</description>
-        <topic label="Using the Import Wizard" href="tasks/tasks-55.htm"/>
-    </context>
-    <context id="export_wizard_context">
-        <description>Wizard to assist in exporting resources.</description>
-        <topic label="Exporting files" href="tasks/tasks-57.htm"/>
-        <topic label="Exporting to the File System" href="tasks/tasks-59.htm"/>
-        <topic label="Exporting to a Zip File" href="tasks/tasks-59ag.htm"/>
-        <topic label="Export Wizard" href="reference/ref-71.htm"/>
-    </context>
-    <!-- terminal reference commented out in org.eclipse.ui.internal.WorkbenchActionBuilder, line 301 
-  <context id="close_all_saved_action_context">
-    <description></description>
-  </context>
-  -->
-    <context id="show_view_menu_action_context">
-        <description>Displays the menu for the active view.</description>
-    </context>
-    <context id="workbench_editors_action_context">
-        <description>Displays the Switch to Editors dialog.</description>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <!-- terminal reference in org.eclipse.ui.internal.IHelpContextIds, line 77
-  <context id="new_wizard_shortcut_action_context">
-    <description></description>
-  </context>
-  -->
-    <context id="text_cut_action_context">
-        <description>Cut the selected text to the clipboard.</description>
-        <topic label="Edit Menu - Cut" href="reference/ref-57.htm"/>
-    </context>
-    <context id="text_copy_action_context">
-        <description>Copy the selection to the clipboard.</description>
-        <topic label="Edit Menu - Copy" href="reference/ref-57.htm"/>
-    </context>
-    <context id="text_paste_action_context">
-        <description>Paste the contents of the clipboard at the current cursor position.</description>
-        <topic label="Edit Menu - Paste" href="reference/ref-57.htm"/>
-    </context>
-    <context id="text_select_all_action_context">
-        <description>Select all contents.</description>
-        <topic label="Edit Menu - Select All" href="reference/ref-57.htm"/>
-    </context>
-    <context id="text_delete_action_context">
-        <description>Delete the selection.</description>
-        <topic label="Edit Menu - Delete" href="reference/ref-57.htm"/>
-    </context>
-    <context id="cell_cut_action_context">
-        <description>Cut the selected text to the clipboard.</description>
-        <topic label="Edit Menu - Cut" href="reference/ref-57.htm"/>
-    </context>
-    <context id="cell_copy_action_context">
-        <description>Copy the selection to the clipboard.</description>
-        <topic label="Edit Menu - Copy" href="reference/ref-57.htm"/>
-    </context>
-    <context id="cell_paste_action_context">
-        <description>Paste the contents of the clipboard at the current cursor position.</description>
-        <topic label="Edit Menu - Paste" href="reference/ref-57.htm"/>
-    </context>
-    <context id="cell_delete_action_context">
-        <description>Delete the selection.</description>
-        <topic label="Edit Menu - Delete" href="reference/ref-57.htm"/>
-    </context>
-    <context id="cell_find_action_context">
-        <description>This will bring up a dialog to specify text to search for in the editor.</description>
-        <topic label="Edit Menu - Find/Replace" href="reference/ref-57.htm"/>
-    </context>
-    <context id="cell_select_all_action_context">
-        <description>Select all contents.</description>
-        <topic label="Edit Menu - Select All" href="reference/ref-57.htm"/>
-    </context>
-    <context id="cell_undo_action_context">
-        <description>Undo the previous edit.</description>
-        <topic label="Edit Menu - Undo" href="reference/ref-57.htm"/>
-    </context>
-    <context id="cell_redo_action_context">
-        <description>Redo the previous edit.</description>
-        <topic label="Edit Menu - Redo" href="reference/ref-57.htm"/>
-    </context>
-    <context id="working_set_selection_dialog_context">
-        <description>This dialog allows you to add, remove, or configure working sets for use within the workbench.  A working set is a subset of the workspace.</description>
-    </context>
-    <context id="delete_project_dialog_context">
-        <description>This dialog asks you to confirm whether or not you wish to delete the selected project, and if so, whether you wish to also delete the underlying project files on the local file system corresponding to your project.</description>
-    </context>
-    <context id="filter_dialog_context">
-        <description>This dialog allows you to select filters to isolate specific elements of the workspace only.</description>
-    </context>
-    <context id="marker_resolution_selection_dialog_context">
-        <description>This dialog allows you to select from a list of possible resolutions.</description>
-    </context>
-    <context id="workbench_editors_dialog">
-        <description>This dialog displays all open editors, allowing you to conveniently choose those you wish to close or save.</description>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="welcome_page_selection_dialog">
-        <description>This dialog allows you to one of the set of available welcome pages. Welcome pages can help you get started using particular parts of the workbench.</description>
-    </context>
-    <context id="decorators_preference_page_context">
-        <description>This page allows you to specify which decorators you would like to be displayed on items within the workbench. Decorators give you more information about an item, at the expense of visual clutter.</description>
-        <topic label="Preferences - Label decorations" href="reference/ref-decorations.htm"/>
-    </context>
-    <context id="startup_preference_page_context">
-        <description>This page shows you all of the plug-ins that are activated when the workbench starts.</description>
-        <topic label="Preferences - Startup" href="reference/ref-startup.htm"/>
-    </context>
-    <context id="working_set_new_wizard_context">
-        <description>This wizard will guide you through the process of creating a working set.</description>
-    </context>
-    <context id="working_set_edit_wizard_context">
-        <description>This wizard will guide you through the process of editing a working set.</description>
-    </context>
-    <context id="filters_action_context">
-        <description>Displays a dialog to allow you to select filters to isolate specific elements of the workspace only.</description>
-    </context>
-    <context id="mark_completed_action_context">
-        <description>Marks the currently selected task as &apos;complete&apos;.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="resolve_marker_action_context">
-        <description>Displays a dialog to allow you to select from a list of possible resolutions.</description>
-    </context>
-    <context id="select_all_tasks_action_context">
-        <description>Selects all tasks in the task view.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_properties_action_context">
-        <description>Displays a dialog to allow you to set properties for the selected task.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="back_action_context">
-        <description>Move back one frame.</description>
-        <topic label="Navigator View" href="concepts/cnav.htm"/>
-    </context>
-    <context id="forward_action_context">
-        <description>Move forward one frame.</description>
-        <topic label="Navigator View" href="concepts/cnav.htm"/>
-    </context>
-    <context id="go_into_action_context">
-        <description>Drill down into selected element</description>
-        <topic label="Navigator View" href="concepts/cnav.htm"/>
-    </context>
-    <context id="up_action_context">
-        <description>Move up one frame.</description>
-        <topic label="Navigator View" href="concepts/cnav.htm"/>
-    </context>
-    <context id="lock_toolbar_action_context">
-        <description>Locks the toolbars within the workbench.</description>
-    </context>
-    <context id="about_plugins_dialog_context">
-        <description>This dialog shows details about all installed plug-ins.</description>
-    </context>
-    <context id="about_features_plugins_dialog_context">
-        <description>This dialog shows details about all plug-ins within a particular feature.</description>
-    </context>
-    <context id="about_features_dialog_context">
-        <description>This dialog shows details about all installed features.</description>
-    </context>
-    <context id="working_set_resource_page">
-        <description>This page allows you to choose the resources that will be part of your working set.</description>
-    </context>
-    <context id="working_set_type_page">
-        <description>This page allows you to select the type of working set you want to create.</description>
-    </context>
-    <context id="copy_bookmark_action_context">
-        <description>Copies the selected bookmark to the clipboard.</description>
-        <topic label="Edit Menu - Copy" href="reference/ref-57.htm"/>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="paste_bookmark_action_context">
-        <description>Pastes the bookmark(s) on the clipboard.</description>
-        <topic label="Edit Menu - Paste" href="reference/ref-57.htm"/>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="bookmark_properties_action_context">
-        <description>Displays a dialog to allow you to set properties for the selected bookmark.</description>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="bookmark_sort_ascending_action_context">
-        <description>Sorts bookmarks in ascending order.</description>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="bookmark_sort_descending_action_context">
-        <description>Sorts bookmarks in descending order.</description>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="bookmark_sort_description_action_context">
-        <description>Sorts bookmarks by description.</description>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="bookmark_sort_resource_action_context">
-        <description>Sorts bookmarks by resource.</description>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="bookmark_sort_folder_action_context">
-        <description>Sorts bookmarks by folder.</description>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="bookmark_sort_location_action_context">
-        <description>Sorts bookmarks by location.</description>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="bookmark_sort_creation_time_action_context">
-        <description>Sorts bookmarks by creation time.</description>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="resource_navigator_copy_action_context">
-        <description>Copies the selected resource to the clipboard.</description>
-        <topic label="Edit Menu - Copy" href="reference/ref-57.htm"/>
-        <topic label="Navigator View" href="concepts/cnav.htm"/>
-    </context>
-    <context id="resource_navigator_paste_action_context">
-        <description>Pastes the resource on the clipboard to the location of the currently selected resource.</description>
-        <topic label="Edit Menu - Paste" href="reference/ref-57.htm"/>
-        <topic label="Navigator View" href="concepts/cnav.htm"/>
-    </context>
-    <context id="properties_copy_action_context">
-        <description>Copies the selected property to the clipboard.</description>
-        <topic label="Edit Menu - Copy" href="reference/ref-57.htm"/>
-    </context>
-    <context id="copy_task_action_context">
-        <description>Copies the selected task to the clipboard.</description>
-        <topic label="Edit Menu - Copy" href="reference/ref-57.htm"/>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="paste_task_action_context">
-        <description>Paste the contents of the clipboard at the current cursor position.</description>
-        <topic label="Edit Menu - Paste" href="reference/ref-57.htm"/>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_properties_dialog_context">
-        <description>This dialog allows you to set properties for the selected task.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_sort_type_action_context">
-        <description>Sorts tasks by type.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_sort_completed_action_context">
-        <description>Sorts tasks by completion.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_sort_priority_action_context">
-        <description>Sorts tasks by priority.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_sort_description_action_context">
-        <description>Sorts tasks by description.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_sort_resource_action_context">
-        <description>Sorts tasks by resource.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_sort_folder_action_context">
-        <description>Sorts tasks by folder.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_sort_location_action_context">
-        <description>Sorts tasks by location.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_sort_creation_time_action_context">
-        <description> Sorts tasks by creation time.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_sort_ascending_action_context">
-        <description>Sorts tasks in ascending order.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_sort_descending_action_context">
-        <description>Sorts tasks in descending order.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="show_part_pane_menu_action_context">
-        <description>Opens the system menu of the active view or editor.</description>
-    </context>
-    <context id="cycle_part_forward_action_context">
-        <description>Displays a menu which allows you navigate forward through the currently open views.</description>
-    </context>
-    <context id="cycle_part_backward_action_context">
-        <description>Displays a menu which allows you navigate backward through the currently open views.</description>
-    </context>
-    <context id="cycle_editor_forward_action_context">
-        <description>Displays a menu which allows you navigate forward through the currently open editors.</description>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="cycle_editor_backward_action_context">
-        <description>Displays a menu which allows you navigate backward through the currently open editors.</description>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="cycle_perspective_forward_action_context">
-        <description>Displays a menu which allows you navigate forward through the currently open perspectives.</description>
-        <topic label="Perspectives" href="concepts/concepts-4.htm"/>
-    </context>
-    <context id="cycle_perspective_backward_action_context">
-        <description>Displays a menu which allows you navigate backward through the currently open perspectives.</description>
-        <topic label="Perspectives" href="concepts/concepts-4.htm"/>
-    </context>
-    <context id="activate_editor_action_context">
-        <description>Activates the editor pane.</description>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <!-- part of project capability support. currently unused.
-  <context id="project_capability_property_page_context">
-    <description></description>
-  </context>
-
-  <context id="new_project_capability_wizard_page_context">
-    <description></description>
-  </context>
-
-  <context id="new_project_review_wizard_page_context">
-    <description></description>
-  </context>
-
-  <context id="new_project_configure_wizard_page_context">
-    <description></description>
-  </context>
-
-  <context id="show_project_perspective_dialog_context">
-    <description></description>
-  </context>
-
-  <context id="update_capability_wizard_context">
-    <description></description>
-  </context>
-  -->
-
-    <!--new context ids-->
-    <context id="goto_last_edit_position_action_context">
-        <description>This command navigates back to the last edit location.</description>
-    </context>
-    
-    <context id="goto_next_annotation_action_context">
-        <description>Selects the next annotation in the resource that is currently active in the editor area.</description>
-    </context>
-
-    <context id="goto_previous_annotation_action_context">
-        <description>Selects the previous annotation in the resource that is currently active in the editor area.</description>
-    </context>
-    
-    <context id="ConvertLineDelimitersToMAC_action_context">
-        <description>This command converts the file to use classic MacOS line delimiters (CR).</description>
-    </context>
-    <context id="ConvertLineDelimitersToUNIX_action_context">
-        <description>This command converts the file to use Unix/MacOS X line delimiters (LF).</description>
-    </context>
-    <context id="ConvertLineDelimitersToWindows_action_context">
-        <description>This command converts the file to use Windows line delimiters (CRLF).</description>
-    </context>
-    <context id="FindIncrementalReverse_action_context">
-        <description>This command enters the incremental find previous mode or goes to the previous match if already in incremental mode. Esc quits the incremental find mode.</description>
-    </context>
-    <context id="DeleteLineToBeginning_action_context">
-        <description>This command deletes the text form the current caret position to the beginning of the line.</description>
-    </context>
-    <context id="DeleteLineToEnd_action_context">
-        <description>This command deletes the text from the current caret position to the end of the line.</description>
-    </context>
-    <context id="SetMark_action_context">
-        <description>This command sets a mark in the editor.</description>
-    </context>
-    <context id="FindNext_action_context">
-        <description>This command finds the next match in the editor.</description>
-    </context>
-    <context id="CutLine_action_context">
-        <description>This command cuts the whole line to the clipboard.</description>
-    </context>
-    <context id="DeleteLine_action_context">
-        <description>This command deletes the whole line.</description>
-    </context>
-    <context id="CutLineToEnd_action_context">
-        <description>This command cuts the text from the current caret position to the end of the line to the clipboard.</description>
-    </context>
-    <context id="ClearMark_action_context">
-        <description>This command clears the previously set mark in the editor.</description>
-    </context>
-    <context id="SwapMark_action_context">
-        <description>Swaps the current curet position with the previously set mark.</description>
-    </context>
-    <context id="FindIncremental_action_context">
-        <description>This command enters the incremental find mode or goes to the next match if already in incremental mode. Esc quits the incremental find mode.</description>
-    </context>
-    <context id="FindPrevious_action_context">
-        <description>This command finds the previous match in the editor.</description>
-    </context>
-    <context id="CutLineToBeginning_action_context">
-        <description>This command cuts the text from the current caret position to the beginning of the line to the clipboard.</description>
-    </context>
-    <context id="US-ASCII_action_context">
-        <description>This command sets the encoding to US-ASCII.</description>
-    </context>
-    <context id="ISO-8859-1_action_context">
-        <description>This command sets the encoding to ISO-8859-1.</description>
-    </context>
-    <context id="UTF-8_action_context">
-        <description>This command sets the encoding to UTF-8.</description>
-    </context>
-    <context id="UTF-16BE_action_context">
-        <description>This command sets the encoding to UTF-16 (big-endian).</description>
-    </context>
-    <context id="UTF-16LE_action_context">
-        <description>This command sets the encoding to UTF-16 (little-endian).</description>
-    </context>
-    <context id="UTF-16_action_context">
-        <description>This command sets the encoding to UTF-16.</description>
-    </context>
-    <context id="System_action_context">
-        <description>This command sets the encoding to the current system encoding.</description>
-    </context>
-    <context id="Default_action_context">
-        <description>This command sets the encoding to the default encoding.</description>
-    </context>
-    <context id="Custom_action_context">
-        <description>This command allows to set a custom encoding.</description>
-    </context>
-    <context id="text_editor_preference_page_context">
-        <description>This preference page is used to set preferences for the text editor.</description>
-        <topic label="Preferences - Text Editor" href="reference/ref-texteditorprefs.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="quick_assist_action_context">
-        <description>This command provides quick assists and quick fixes.</description>
-    </context>
-	 <context id="responsive_ui_context">
-        <description>This view displays the current state of background processes.</description>
-        <topic label="Responsive UI" href="gettingStarted/qs-responsiveUI.htm"/>
-    </context>
-     <context id="tips_and_tricks_page_selection_dialog">
-        <description>This dialog allows you to open a feature specific tips and tricks page.</description>
-        <topic label="Help Menu - Tips and Tricks" href="reference/ref-61.htm"/>
-    </context>
-	<!-- Help Menu: Help Contents -->
-    <context  id="help_contents_action_context" >
-        <description>This command displays the help view. The help view contains help books, topics, and information related to the workbench and installed components.</description>
-        <topic label="Online Help System" href="/org.eclipse.platform.doc.user/concepts/chelpsys.htm"/>
-        <topic label="Help Menu - Help Contents" href="/org.eclipse.platform.doc.user/reference/ref-61.htm"/>
-    </context>
-    <context  id="help_search_action_context" >
-        <description>This command displays the help view opened on the search page.</description>
-        <topic label="Searching online help" href="/org.eclipse.platform.doc.user/tasks/tsearch.htm"/>
-        <topic label="Help Menu - Search" href="/org.eclipse.platform.doc.user/reference/ref-61.htm"/>
-    </context>
-   <!-- Browser support: Help Contents -->
-    <context id="browser_preference_page_context">
-        <description>This preference page is used to set preferences for launching Web browsers from the workbench.</description>
-    </context>
-    <context id="browser_preference_page_dialog_context">
-        <description>This dialog allows you to modify the properties of an externally launched browser.</description>
-    </context>
-    <context id="browser_context">
-        <description>This view allows you to display Web pages.</description>
-    </context>
-</contexts>

diff --git a/bundles/org.eclipse.platform.doc.user/cpy.png b/bundles/org.eclipse.platform.doc.user/cpy.png
deleted file mode 100644
index a0f8775..0000000
--- a/bundles/org.eclipse.platform.doc.user/cpy.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/customBuildCallbacks.xml b/bundles/org.eclipse.platform.doc.user/customBuildCallbacks.xml
deleted file mode 100644
index 1f2afe4..0000000
--- a/bundles/org.eclipse.platform.doc.user/customBuildCallbacks.xml
+++ /dev/null

@@ -1,139 +0,0 @@
-<!-- ===================================================================== -->
-<!-- Custom targets called from a project's generated build.xml            -->
-<!-- Set customBuildCallbacks=<path/to/this/file> in your build.properties.-->
-<!-- ===================================================================== -->
-<project name="Build specific targets and properties" default="noDefault">
-
-	<!-- ===================================================================== -->
-	<!-- Default target                                                        -->
-	<!-- ===================================================================== -->
-	<target name="noDefault">
-		<echo message="This file must be called with explicit targets" />
-	</target>
-	
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the target build.jars                              -->
-	<!-- Available parameters :                                                -->
-	<!--   build.result.folder - folder to contain the build results           -->
-	<!-- ===================================================================== -->
-	<target name="pre.build.jars">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target build.jars                               -->
-	<!-- Available parameters :                                                -->
-	<!--   build.result.folder - folder to contain the build results           -->
-	<!-- ===================================================================== -->
-	<target name="post.build.jars">
-		<antcall target="build.index"/>		
-	</target>
-	
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the target build.sources                           -->
-	<!-- Available parameters :                                                -->
-	<!--   build.result.folder - folder to contain the build results           -->
-	<!-- ===================================================================== -->
-	<target name="pre.build.sources">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target build.sources                            -->
-	<!-- Available parameters :                                                -->
-	<!--   build.result.folder - folder to contain the build results           -->
-	<!-- ===================================================================== -->
-	<target name="post.build.sources">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the compilation target <name>                      -->
-	<!-- Substitute "name" with the name of the compilation target, eg @dot    -->
-	<!-- Available parameters :                                                -->
-	<!--   source.foldern : n = 1 ... N, the source folders                    -->
-	<!--   target.folder  : where the results of the compilation go            -->
-	<!--   <name>.classpath : name = name of the compilation target. A         -->
-	<!--                      reference to the classpath structure.            -->
-	<!-- ===================================================================== -->
-	<target name="pre.name">
-	</target>
-
-	<target name="pre.@dot">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the compilation target <name>                       -->
-	<!-- Substitute "name" with the name of the compilation target, eg @dot    -->
-	<!-- Available parameters :                                                -->
-	<!--   jar.location - the location of the compilation results              -->
-	<!--   <name>.classpath : name = name of the compilation target. A         -->
-	<!--                      reference to the classpath structure.            -->
-	<!-- ===================================================================== -->
-	<target name="post.name">
-	</target>
-
-	<target name="post.@dot">
-	</target>
-	
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target gather.bin.parts                         -->
-	<!-- Available parameters :                                                -->
-	<!--   base.dir - root of the project                                      -->
-	<!--   build.result.folder - folder containing the build results           -->
-	<!--   target.folder - destination folder                                  -->
-	<!-- ===================================================================== -->
-	<target name="post.gather.bin.parts">
-	</target>
-
-	<target name="build.index" description="Builds search index for the plug-in: org.eclipse.platform.doc.user." if="eclipse.running">
-		<help.buildHelpIndex manifest="plugin.xml" destination="."/>
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the target gather.sources                          -->
-	<!-- Available parameters :                                                -->
-	<!--   destination.temp.folder - destination folder                        -->
-	<!-- ===================================================================== -->
-	<target name="pre.gather.sources">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target gather.sources                           -->
-	<!-- Available parameters :                                                -->
-	<!--   destination.temp.folder - destination folder                        -->
-	<!-- ===================================================================== -->
-	<target name="post.gather.sources">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the target gather.logs                             -->
-	<!-- Available parameters :                                                -->
-	<!--   destination.temp.folder - destination folder                        -->
-	<!-- ===================================================================== -->
-	<target name="pre.gather.logs">        
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target gather.logs                              -->
-	<!-- Available parameters :                                                -->
-	<!--   destination.temp.folder - destination folder                        -->
-	<!-- ===================================================================== -->
-	<target name="post.gather.logs">       
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the target clean                                   -->
-	<!-- Available parameters :                                                -->
-	<!--   destination.temp.folder - destination folder                        -->
-	<!-- ===================================================================== -->
-	<target name="pre.clean">              
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target clean                                    -->
-	<!-- Available parameters :                                                -->
-	<!--   plugin.destination - final destination of the build                 -->
-	<!--   build.result.folder - results of the compilation                    -->
-	<!--   temp.folder - temporary folder                                      -->
-	<!-- ===================================================================== -->
-	<target name="post.clean">             
-	</target>
-</project>

diff --git a/bundles/org.eclipse.platform.doc.user/doc.html b/bundles/org.eclipse.platform.doc.user/doc.html
deleted file mode 100644
index 16a09a4..0000000
--- a/bundles/org.eclipse.platform.doc.user/doc.html
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-
-<title>Documentation Images</title>
-</head>
-<body lang="EN-US">
-<h2>Documentation Images</h2>
- 
-<p>Many of the images found in the Eclipse documentation have been taken using 
-  the Windows XP Manifest, giving them the default Windows XP look. The Windows 
-  XP Manifest affects the look and feel of the Eclipse platform, rounding out 
-  otherwise blunt edges of boxes and buttons, as can be seen in the following 
-  examples.</p>
-<p>Screenshot of the Help Preferences page without the Windows XP Manifest.</p>
-<p><img src="images/help_no_manifest.png" alt="Help Preference Page without the Manifest" border="0"></p>
-<p>Screenshot of Help Preferences page with the Windows XP Manifest.</p>
-<p> <img src="images/help_manifest.png" alt="Help Preference Page with the Manifest" border="0"></p>
-<p>If you would like to use the Windows XP Manifest on your installation simply 
-  place the javaw.exe.manifest file in the same directory as your java.exe executable. 
-  The javaw.exe.manifest file can be found in org.eclipse.swt.win32.win32.x86_3.1.0.jar.<br>
-</p>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/gs_htmldoc_book.book b/bundles/org.eclipse.platform.doc.user/gettingStarted/gs_htmldoc_book.book
deleted file mode 100644
index 6c53646..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/gs_htmldoc_book.book
+++ /dev/null

@@ -1,100 +0,0 @@
-#HTMLDOC 1.8.23

--t pdf13 -f test.pdf --book --toclevels 3 --no-numbered --toctitle "Table of Contents" --no-title --linkstyle underline --size Universal --left 1.00in --right 0.50in --top 0.50in --bottom 0.50in --header .t. --footer h.1 --nup 1 --tocheader .t. --tocfooter ..i --portrait --color --no-pscommands --no-xrxcomments --compression=5 --jpeg=0 --fontsize 11.0 --fontspacing 1.2 --headingfont Helvetica --bodyfont Times --headfootsize 11.0 --headfootfont Helvetica --charset iso-8859-1 --links --no-embedfonts --pagemode outline --pagelayout single --firstpage p1 --pageeffect none --pageduration 10 --effectduration 1.0 --no-encryption --permissions all  --owner-password ""  --user-password "" --browserwidth 680

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-01.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-02a.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-02b.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-02d.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-02e.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-07a.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-07b.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-07c.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-07d.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-10b.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-12.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-12b.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-12c.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-12d.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-13.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-24a.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-24c.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-31a.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-31b.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-31c.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-32.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-34a.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-34b.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-34c.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-34d.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-35.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-35b.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-35c.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-35d.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-36.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-36a.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-36b.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-37-2b.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-37-2d.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-37-2d2.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-37-2f.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-37-3b.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-37-3c.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-37-3e.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-37-3f.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-39.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-39c.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-39d.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-39e.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-39f.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-39g.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-40.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-40a.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-40b.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-43.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-43b.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-43c.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-43e.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-43f.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-52.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-52c.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-52d.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-52e.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-55.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-55b.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-60_team.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-60a_setup.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-61c_offline.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-61d_repoloca.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-61d_repolocb.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-61e_whatisloc.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-61f_syncproject.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-62b_sync.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-62c_releasing.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-64a_another.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-64b_fredadd.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-64b_fredmod.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_mod.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_sync2.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_sync3_rel.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_sync_view.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-70_replace.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-74_review.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-74_version.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-80_ant.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-81_basics.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-82_create.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-83_edit.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-84_run_ant.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-85_ant_configs.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-85a_ant_view.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-86_use_cases.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-87_plugin_deploy.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-88_create_plugin.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-89_generate_buildxml.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-90_build_jar.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-91_build_options.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-92_project_builders.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-93_project_builder.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-94_run_pj.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-95_external_tools.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-96_non_ant_pjs.htm

-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-97_standalone_ets.htm


diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/intro/overview.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/intro/overview.htm
deleted file mode 100644
index 157b2b0..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/intro/overview.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Eclipse Platform</title>
-
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-<script type="text/javaScript">
-	function openRelatedLink(rel) {
-		var href = '/org.eclipse.platform.doc.user/'+rel;
-		if (self.name=="ContentViewFrame") {
-			showTopicInContents(href);
-			window.location = '../../'+rel;
-		}
-		else {
-			window.location = 'http://org.eclipse.ui.intro/showHelpTopic?id='+href;
-		}
-	}
-</script>
-</head>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Eclipse Platform</h1>
-
-<p>The Eclipse platform itself is structured as subsystems which are implemented 
-in one or more plug-ins.&nbsp; The subsystems are built on top of a small runtime 
-engine. The figure below depicts a simplified view. </p>
-<p align="center">
-<img alt="Platform runtime base with groups of plug-ins adding function" src="../../images/arch-npi.jpg" border="0" width="312" height="312">
-</p>
-<h2>Workbench</h2>
-<P>The term <i>Workbench</i> refers to the desktop development environment. 
-The Workbench aims to achieve seamless tool integration and controlled openness by providing a common paradigm for the creation, management, and navigation of workspace resources.</P>
-
-
-<P>
-Each Workbench window contains one or more
-perspectives.&nbsp; Perspectives contain views and editors and control
-what appears in certain menus and tool bars.&nbsp; More than one Workbench window can exist
-on the desktop at any given time.</P>
-<P>
-<img border="0" src="../../images/ngrelc.png" alt="Related concepts" width="159" height="27" ><br>
-<a href="javaScript:openRelatedLink('concepts/concepts-25.htm')">Features</a><br>
-<a href="javaScript:openRelatedLink('concepts/concepts-12.htm')">Resources</a><br>
-<a href="javaScript:openRelatedLink('concepts/concepts-4.htm')">Perspectives</a><br>
-<a href="javaScript:openRelatedLink('concepts/concepts-5.htm')">Views</a><br>
-<a href="javaScript:openRelatedLink('concepts/concepts-6.htm')">Editors</a><br>
-<a href="javaScript:openRelatedLink('concepts/concepts-27c.htm')">CVS Repositories</a>
-</P>
-<P>
-<img border="0" src="../../images/ngrelt.png" alt="Related tasks" width="159" height="27"><br>
-<a href="javaScript:openRelatedLink('tasks/tasks-34.htm')">Installing new features with the update manager</a><br>
-<a href="javaScript:openRelatedLink('tasks/tasks-9f.htm')">Opening perspectives</a><br>
-<a href="javaScript:openRelatedLink('tasks/tasks-3.htm')">Opening views</a><br>
-<a href="javaScript:openRelatedLink('tasks/tasks-28.htm')">Switching between perspectives</a><br>
-<a href="javaScript:openRelatedLink('tasks/tasks-9k.htm')">Configuring perspectives</a>
-</P>
-<P>
-<img border="0" src="../../images/ngrelr.png" alt="Related reference" width="159" height="27" ><br>
-<a href="javaScript:openRelatedLink('reference/ref-68.htm')">Toolbar buttons</a></P>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/no_help_exists.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/no_help_exists.htm
deleted file mode 100644
index 8860eeb..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/no_help_exists.htm
+++ /dev/null

@@ -1,21 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE> No Help Exists</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-No Help Exists</H1>
-<p CLASS="Head">There are no available help topics associated with this
-item.&nbsp;&nbsp;&nbsp;</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-01.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-01.htm
deleted file mode 100644
index 8eaeccb..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-01.htm
+++ /dev/null

@@ -1,24 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Basic tutorial</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Basic tutorial</H1>
-<P>This tutorial provides a step by step walk-through of the
-Workbench.&nbsp;<br>
-</P>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02a.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02a.htm
deleted file mode 100644
index e14a86c..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02a.htm
+++ /dev/null

@@ -1,48 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>The Workbench</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h2>
-The Workbench</h2>
-<P CLASS="Para"> When the Workbench is launched the first thing you see is a 
-  dialog that allows you to select where the workspace should be located. The
-  workspace is the directory where your work will be stored. For now, just
-  click OK to pick the default location. (You can also check the checkbox
-  to prevent this question from being asked again.)</p>
- <p>After the workspace location is chosen, a single Workbench window is displayed. 
-  A Workbench window offers one or more perspectives. A perspective contains 
-  editors and views, such as the Navigator. Multiple Workbench windows can be 
-  opened simultaneously. Initially, in the first Workbench window that is opened,
-  the Resource perspective is displayed, with only the Welcome view visible. 
-  Click the arrow labeled <b>Workbench</b> in the Welcome view to cause the other
-  views in the perspective to become visible.</P>
-<p>(You can get the Welcome view back at any time by selecting
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.help.quickStartAction")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Help &gt; Welcome</b></a>.)</p>
-<p>A shortcut bar appears in the top right corner of the window. This allows the user 
-  to open new perspectives and switch between ones already open. The name of the 
-  active perspective is shown in the title of the window and its item in the shortcut 
-  bar is highlighted.</p>
-<p>The title bar of the Workbench window indicates which perspective is active. 
-  In this example, the Resource perspective is in use. The Navigator, Tasks, and 
-  Outline views are open along with an editor. <br>
-</p>
-<P CLASS="Para"><img src="../images/Image1.png" alt="Workbench" border="0"></P>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02b.htm
deleted file mode 100644
index d3f6def..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02b.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Editors and views</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Editors and views</h2>
-<P CLASS="Intro">Prior to commencing the Workbench tutorials found in this section, 
-  it is important to first be familiar with the various elements of the Workbench. 
-  A Workbench consists of:</p> 
-<ul>
-  <li>
-    perspectives</li>
-  <li>
-    views</li>
-  <li>
-    editors</li>
-</ul>
-<p CLASS="Intro">A perspective is a group of views and editors in 
-the Workbench window. One or more perspectives can exist in a single Workbench 
-window. Each perspective contains one or more views and editors. Within a
-window, each perspective may have a different set of views but all perspectives
-share the same set of editors.</p>
-<p CLASS="Intro">A view is a visual component within the Workbench. It is typically 
-  used to navigate a hierarchy of information (such as the resources in the Workbench), 
-  open an editor, or display properties for the active editor. Modifications made 
-  in a view are saved immediately. Normally, only one instance of a particular type of view 
-  may exist within a Workbench window.&nbsp; </p>
-<p CLASS="Intro">An editor is also a visual component within the Workbench. It is typically used to edit or browse a
-resource.  Modifications made in an editor follow an open-save-close lifecycle model.
-Multiple instances of an editor type may exist within a Workbench window.&nbsp;
-</p>
-<p CLASS="Intro">Some features are common to both views and editors. We use the 
-  term &quot;part&quot; to mean either a view or an editor. Parts can be active 
-  or inactive, but only one part can be active at any one time.&nbsp; The active 
-  part is the one whose title bar is highlighted. The active part is the target 
-  for common operations like cut, copy and paste. The active part also determines 
-  the contents of the status line. If an editor tab is not highlighted it indicates 
-  the editor is not active, however views may show information based on the last 
-  active editor.&nbsp;&nbsp;</p>
-<p CLASS="Intro">In the image below, the Navigator view is active. </p>
-<p CLASS="Intro"><img src="../images/Image2_active_view.png"  alt="Workbench" border="0"></p>
-<P CLASS="Intro">Clicking on the Outline view causes the Outline's title bar to 
-  become highlighted and the Navigator's title bar to no longer be highlighted, 
-  as shown below. The Outline view is now active. </p>
-<P CLASS="Intro"><img src="../images/Image2_active_editor.png"  alt="Welcome page selected" border="0">
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02d.xhtml b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02d.xhtml
deleted file mode 100644
index 329ce1f..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02d.xhtml
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." />
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css" />
-<title>Editors</title>
-
-</head>
-<body bgcolor="#ffffff">
-<h3>
-Editors</h3>
-<p class="Para"> Depending on the type of file that is being edited, the appropriate 
-  editor is displayed in the editor area. For example, if a .TXT file is being 
-  edited, a text editor is displayed in the editor area. The figure below shows 
-  an editor open on the file sample.txt. The name of the file appears in the tab 
-  of the editor. If an asterisk (*) appears at the left side of the tab this indicates 
-  that the editor has unsaved changes. If an attempt is made to close the editor 
-  or exit the Workbench with unsaved changes a prompt to save the editor's changes 
-  will appear.</p>
-<p><img src="../images/Image5_text_editor.png" alt="Eclipse Workbench, one editor" border="0" />
-</p>
-
-
-<p class="Para">When an editor is active the Workbench menu bar and toolbar contain 
-  operations applicable to the editor. When a view becomes active, the editor 
-  operations are disabled. However, certain operations may be appropriate 
-  in the context of a view and will remain enabled.</p>
-
-
-<p class="Para"> The editors can be stacked in the editor area and individual 
-  editors can be activated by clicking the tab for the editor. Editors can also 
-  be tiled side-by-side in the editor area so their content can be viewed simultaneously. 
-  In the figure below, editors for sample.txt and otherFile.txt have been placed 
-  one above the other. Instructions will be given later in this tutorial explaining 
-  how to rearrange views and editors.</p>
-<p><img src="../images/Image6_two_editors.png" alt="Eclipse Workbench, two editors" border="0" /> 
-</p>
-
-
-<p>If a resource that does not have an associated editor is opened, the Workbench 
-  will attempt to launch an external editor registered with the platform. These 
-  external editors are not tightly integrated with the Workbench and are not embedded 
-  into the Workbench's editor area. </p>
-<p>Also, the editors can be cycled through using the back and forward arrow buttons 
-  in the toolbar and by using the Ctrl+F6 accelerator. The arrow buttons move 
-  through the last mouse selection points and permits moving through several points 
-  in a file before moving to another one. Ctrl+F6 pops up a list of currently 
-  selected editors, by default, the editor used before the current one is selected.
-  (On the Macintosh, the accelerator is Command+F6.)</p>
-<p filter="ws=win32"><img src="../images/win_only.png" alt="Windows only" border="0" />
-  On Windows the Workbench will also attempt to launch the editor in-place as an 
-  OLE document editor. For example, editing a DOC file will cause Microsoft Word 
-  to be opened in-place within the Workbench if Microsoft Word is installed on 
-  the machine. If Microsoft Word has not been installed, Word Pad will open instead.</p>
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02e.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02e.htm
deleted file mode 100644
index 04cb4e3..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02e.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Views</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h3>
-Views</h3>
-<P CLASS="Para">Views support editors and provide alternative presentations or 
-  navigations of the information in the Workbench.&nbsp; For example:</P>
-<UL CLASS="UnorderedList">
-<LI CLASS="Item">
-The Bookmarks view displays all bookmarks in the Workbench along with the names
-of the files with which the bookmarks are associated.</LI>
-  <LI CLASS="Item"> The Navigator view displays the projects and other resources.</LI>
-</UL>
-<P CLASS="Para">
-A view might appear by itself or stacked with other views in a tabbed notebook.&nbsp;&nbsp;</P>
-<blockquote>
-  <blockquote>
-<P CLASS="Para" align="center">
-<img src="../images/Image3_single.png"  alt="Task View" border="0"></P>
-  </blockquote>
-</blockquote>
-<P CLASS="Para"> To activate a view that is part of a tabbed notebook simply click 
-  its tab. The Workbench provides a number of quick and easy ways to configure 
-  an environment, including whether the tabs are at the bottom or top of the notebooks.&nbsp;</P>
-<P CLASS="Para" align="center">
-<img src="../images/Image3_tabbed.png" alt="Two views with tabs, navigator view active" border="0"></P>
-<P CLASS="Para">Views have two menus, the first, which is accessed by right clicking on the
-  view's tab, allows the view to be manipulated in much the 
-  same manner as the menu associated with the Workbench window.</P>
-<P CLASS="Para" align="center"><img src="../images/Image8_view.png" alt="Navigator view menu, top left" border="0"></P>
-<P CLASS="Para">The second menu, called the "view pull-down menu", is accessed by clicking the down arrow <img src="../images/Image9_viewdownarrow.png" alt="View down arrow" border="0" >. 
-  The view pull-down menu typically contains operations that apply to the entire 
-  contents of the view, but not to a specific item shown in the view. Operations 
-  for sorting and filtering are commonly found on the view pull-down.&nbsp;</P>
-<P CLASS="Para" align="center"><img src="../images/Image7_view_pulldown.png" alt="Navigator view menu, arrow pulldown" border="0"></P>
-<P CLASS="Para">&nbsp;</P>
-<P CLASS="Para"> Customizing the Workbench is a good opportunity to use the <b>Window 
-  &gt; Reset Perspective</b> menu operation. The reset operation restores the 
-  layout to its original state.</P>
-<P CLASS="Para"> A view can be displayed by selecting it from the <b>Window &gt; 
-  Show View</b> menu. A perspective determines which views may be required and 
-  displays these on the <b>Show View</b> submenu. Additional views are available 
-  by choosing
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Other...</b></a>
-  at the bottom of the <b>Show View</b> submenu. This 
-  is just one of the many features that provide for the creation of a custom work 
-  environment. </P>
-<P CLASS="Para">&nbsp;</P>
-<P CLASS="Para" align="center">
-<img src="../images/Image4_showview.png" alt="Show View menu" border="0"></P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07a.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07a.htm
deleted file mode 100644
index fd1a5f3..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07a.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>A simple project</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2> A simple project</h2>
-<P CLASS="Para"> Now that the basic elements of the Workbench have been explained, 
-  here are some instructions for creating a simple project. New projects, folders, 
-  and files can be created using several different approaches. In this section 
-  resources will be created using three different approaches:</P>
-<ol>
-  <li><b>File</b> menu</li>
-  <li>Navigation view context menu</li>
-  <li>New Wizard button</li>
-</ol>
-<P>A project can be created using the <b>File</b> menu. Once the project has been 
-  created a folder and file can be created as well. </P>
-
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07b.htm
deleted file mode 100644
index 6df92c2..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07b.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Using the File menu</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Using the File menu</h3>
-<P CLASS="Para">
-You can create new resources by using the <b>File &gt; New</b> menu on the Workbench menu bar.
-Start by creating a simple project as follows:</P>
-<ol>
-  <li>
-<P CLASS="Para">
-From the menu bar, select <b>File &gt; New &gt; Project...</b></P>
-<P CLASS="Para">
-<img src="../images/Image11_new_wizard.png"  alt="New Project Wizard" border="0"></P>
-  </li>
-  <li>
-    <P CLASS="Para"> In the New Project wizard, select <b>Simple</b> <strong>&gt;</strong> 
-      <b>Project</b> then click <b>Next</b>.</P>
-  </li>
-  <li>
-    <P CLASS="Para"> In the <b> Project name </b> field, type your name as the 
-      name of your new project. Do not use spaces or special characters in the 
-      project name (for example, &quot;JaneQuser&quot;).</P>
-  </li>
-  <li>
-<P CLASS="Para">
-Leave the box checked to use the default location for your new project. Click
-<b>Finish</b> when you are done.</P>
-<P CLASS="Para">
-<img src="../images/Image12_new_project_wizard.png"  alt="New Project Wizard" border="0"></P>
-<P CLASS="Para">&nbsp;
-</P>
-  </li>
-</ol>
-<P>If you sneak a peek at the navigation view, you will see that it now contains 
-  the simple project we just created.&nbsp; </P>
-
-
-<P align="center"><img src="../images/Image13_project_in_nav.png" alt="Navigator view" border="0">
-</P>
-
-
-<P>Create a second project called JaneQuser2 using the same steps, but instead 
-  of clicking <b>Finish</b>, click <b>Next</b>. At this point you can specify 
-  other projects that project JaneQuser2 depends on. Since we want to create two 
-  independent projects we will not select any of the projects in the <b>Project 
-  References </b> table. Click <b>Finish</b> to create your second simple project. 
-</P>
-
-
-<P align="center"><img src="../images/Image15_project_depend.png" alt="New Project Wizard" border="0">
-</P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07c.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07c.htm
deleted file mode 100644
index 2942fb2..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07c.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Using the popup</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Using the popup</h3>
-<P CLASS="Para">
-Now that we have our project we will create a folder. We will create
-our folder using the Navigator view's popup menu.</P>
-<ol>
-  <li> 
-    <P CLASS="Para"> Activate the Navigator view and select the project JaneQuser 
-      (the first project we created in the Navigator view). From the view's popup 
-      menu choose <b>New &gt; Folder</b>.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the New Folder wizard, your project name appears by default 
-      in the <b>Enter or select the parent folder </b> field. This is because 
-      we chose to create the new folder from your project's context menu.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the <b> Folder name</b> field, type a unique name for 
-      your new folder (for example, using your first and last names in the title). 
-      Do not use spaces or special characters in the folder name (for example, 
-      &quot;JanesFolder&quot;).</P>
-    <P CLASS="Para"> <img src="../images/Image14_new_folder_wizard.png"  alt="New Folder Wizard" border="0"></P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Click <b>Finish</b> when you are done. The Navigator view 
-      will update to show your newly created folder.</P>
-  </li>
-</ol>
-<P><strong>Note:</strong> There is now also an <b>Advanced</b> button. This button 
-  when selected allows you to enter a location outside of a project's hierarchy 
-  as the location for one of its folders. This is called a linked folder.</P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07d.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07d.htm
deleted file mode 100644
index 456af12..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07d.htm
+++ /dev/null

@@ -1,117 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Using the New button</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Using the New button</h3>
-<P CLASS="Para">We have seen how to create resources using <b>File &gt; New</b> 
-  and <b>New</b> from the context menu of one of the navigation views. We will 
-  now create a file for our project using the third alternative, the toolbar <b>New</b> 
-  button.</P>
-<ol>
-  <li> 
-    <P CLASS="Para">Select the folder JanesFolder in one of the navigation views.</P>
-  </li>
-  <li> 
-    <P CLASS="Para">In the Workbench window's toolbar, activate the drop-down 
-      menu on the New Wizard button <img src="../images/Image15_new_button.png" alt="New Wizard Button" border="0"> 
-      and select <b>File</b>. To activate the drop-down menu simply click on the 
-      down arrow.</P>
-    <P CLASS="Para"> <img src="../images/Image16_new_pulldown.png" alt="New Wizard Pulldown" border="0"></P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the New File wizard, your folder's name and path already 
-      appear by default in the <b> Enter or select the parent folder </b> field. 
-      This is because you chose to create the new file while this folder was selected 
-      in one of the navigation views and the view was active.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the <b> File name</b> field, type a unique name for a 
-      new text file, including the .txt file extension. Do not use spaces or special 
-      characters in this file name (for example, &quot;JanesFile.txt&quot;).</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Click <b>Finish</b> when you are done.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> The Workbench has an editor capable of editing text files. 
-      A text editor is automatically opened on the newly created file.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the text editor, type in the following five lines:</P>
-    <blockquote> 
-      <P CLASS="Para"><i>This is a sample text file.<br>
-        There is not much else<br>
-        we can really say about it other<br>
-        than it has five lines of<br>
-        text that are rather dull.</i></P>
-    </blockquote>
-    <P CLASS="Para">Notice that the editor tab has an asterisk (*) at the left 
-      of the filename. The asterisk indicates that the editor has unsaved changes.</P>
-    <blockquote> 
-      <P CLASS="Para"><img src="../images/Image17b_unsaved_changes.png" alt="Editor Unsaved Changes" border="0"></P>
-    </blockquote>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the Workbench window's toolbar, click the Save button 
-      <img src="../images/Image17_save_button.png"  alt="Save Button" border="0"> 
-      to save your work.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In one of the navigation views ensure your folder is still 
-      selected and the navigation view is active.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Click <strong>New Wizard </strong>in the Workbench toolbar. 
-      Previously we clicked on the drop-down arrow of the New button. Here we 
-      clicked on the button itself which has the same effect as choosing <b>File 
-      &gt; New &gt; Other...</b></P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the New wizard, select <b>Simple</b> <strong>&gt;</strong> 
-      <b>File</b>. Then click <b>Next</b>.&nbsp;</P>
-  </li>
-  <li> <P CLASS="Para"> Once again, your folder's name and path appears by default in the <b> Enter 
-    or select the parent folder </b> field.&nbsp;</P></li>
-  <li>
-    <P CLASS="Para"> In the <b>File name</b> field, type a unique name for an 
-      .ini file. Do not use any spaces or special characters in the file name 
-      (for example, &quot;JanesINIFile.ini&quot;). Click Finish when you are done.&nbsp;</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Since the Workbench does not have any editors registered 
-      for .ini files, it may launch an external editor on the file if one is registered 
-      with the operating system. For the moment, close the editor. </P>
-  </li>
-</ol>
-<P>Now that we have created our resources, one of the navigation views shows our two projects, 
-  the folder and its two files. To the right of one of the navigation views is the text 
-  editor open on the first file we created (JanesFile.txt). To proceed with the 
-  following example create a second file (JanesFile2.txt). </P>
-
-
-<P><img src="../images/Image18_created_resources.png" alt="Eclipse Workbench" border="0">
-</P>
-
-
-<P>Click the new JanesFile2.txt editor tab. Now select the file JanesINIFile.ini 
-  in one of the navigation views. Then select <b>Link with Editor</b> on one of 
-  the navigation views. Lastly, click on the editor tab for JanesFile.txt. Notice 
-  how the navigation view updated itself to select the file you are currently 
-  editing (JanesFile.txt). If you don't like this automatic update you can easily 
-  turn it off by deselecting <b>Link with Editor</b>.</P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-10b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-10b.htm
deleted file mode 100644
index 18a3069..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-10b.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Closing an editor</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h2>
-Closing an editor</h2>
-<P CLASS="Para"> Now that there are a couple of editors open, here's how to close 
-  them.&nbsp;</P>
-<ol>
-  <li>
-<P CLASS="Para">
-Select the JanesFile.txt editor tab.&nbsp;</P>
-  </li>
-  <li>
-<p CLASS="Para">
-In the text area add a 6th line of text:</p>
-<blockquote>
-  <p CLASS="Para">This is a 6th line</p>
-</blockquote>
-  </li>
-  <li>
-    <P CLASS="Para"> To close the editor, choose one of the following options:</P>
-<ul>
-  <li>
-    <p CLASS="Para">
-    Click the close button (&quot;X&quot;)
-    <img src="../images/Image19_close_on_tab.png"  alt="Editor Tab" border="0">
-    in the tab of the editor.</p>
-  </li>
-  <li>
-        <p CLASS="Para"> Select <b>File &gt; Close</b> from the menu bar.</p></li>
-</ul>
-  </li>
-  <li>
-    <P CLASS="Para"> Note the prompt to save the file before the editor is closed.</P>
-  </li>
-  <li>
-    <P CLASS="Para"> Click OK to save any changes and close the editor.</P>
-  </li>
-</ol>
-<P>If the editor was closed using <b>File &gt; Close</b>, notice that the option 
-  <b>File &gt; Close All</b> was also displayed. This is a quick way to close 
-  all of the open editors. If <b>File &gt; Close All</b> is chosen, a prompt will 
-  appear to choose which editors with unsaved changes should be saved. </P>
-
-<P>The preference to close editors automatically can be found in the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Editors)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General &gt; Editors</b></a> preference page. The number of editors that 
-  can be opened prior to editors being reused and what should occur when all editors 
-  have unsaved changes can be configured there.</P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12.htm
deleted file mode 100644
index 9866655..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Navigating resources</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Navigating resources </h2>
-<P CLASS="Para"> This section will work with the Navigator and Tasks views.&nbsp; 
-  These views are initially part of the resource perspective. To experiment with 
-  other views, they can be displayed by using the <b>Window &gt; Show View</b> 
-  menu.</P>
-<P CLASS="Para">
-One important view to become familiar with is one of the navigation views, which displays information 
-about the contents of the Workbench and how the resources relate to each other in a hierarchy.</P>
-<P CLASS="Para">
-In the Workbench, all resources reside in projects. Projects can contain folders and/or individual
-files.&nbsp;&nbsp;</P>
-<blockquote>
-  <blockquote>
-<P CLASS="Para" align="center">
-<img src="../images/Image20_nav_with_resources.png"  alt="Navigator View" border="0"></P>
-  </blockquote>
-</blockquote>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12b.htm
deleted file mode 100644
index d0a8dea..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12b.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Opening resources in the Navigator</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h3>
-Opening resources in the Navigator </h3>
-<P CLASS="Para">Using the Navigator there are several ways to open an
-editor.&nbsp;</P>
-<ol>
-  <li> 
-    <P CLASS="Para">In one of the navigation views select the file JanesFile.txt</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> To open an editor on the file choose one of the following 
-      approaches:</P>
-    <ul>
-      <li><p>To edit a resource using the default editor for that resource, either 
-        double click on the resource (in one of the navigation views), or select 
-        the resource and choose <b>Open</b> from its popup menu.&nbsp; 
-        </p></li>
-      <li><p>To use a specific editor to edit the resource, start by selecting the 
-        resource in one of the navigation views, and choose the <b>Open With</b> 
-        option from the popup menu. 
-        </p> </li>
-    </ul>
-    <p CLASS="Para">The Workbench remembers the last editor that was used for 
-      editing a specific file. This makes it easier to use the same editor down 
-      the road.</p>
-  </li>
-</ol>
-<P CLASS="Para"> The default editors can be configured using the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.FileEditors)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>General &gt; Editors &gt; File Associations</b></a> preference page.
-</P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12c.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12c.htm
deleted file mode 100644
index 99b3f7f..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12c.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Go To</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Go
-To</h3>
-<P CLASS="Para"> The Go To operation makes it easy to jump to a specific resource 
-  in the navigation views.&nbsp;</P>
-<ol>
-  <li> 
-    <P CLASS="Para"> Select one of the navigation views. Its title bar will be 
-      highlighted (according to the operating system's color scheme).</P>
-  </li>
-  <li> 
-    <P CLASS="Para">From the menu bar choose <b>Navigate &gt; Go To &gt; Resource...</b>.</P>
-  </li>
-  <li> 
-    <P CLASS="Para">In the Go To Resource dialog type &quot;JanesF&quot; into 
-      the <b>Pattern </b>field at the top of the dialog.</P>
-    <P CLASS="Para">As the filename is typed, the dialog filters the set of possible 
-      matches based on what has been entered so far.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Select JanesFile.txt from the <b>Matching Resources</b> field 
-      and click OK or simply press Enter. </P>
-  </li>
-  <li> 
-    <p CLASS="Para"> The navigation view will select the file JanesFile.txt.</p>
-  </li>
-</ol>
-<P align="center"><img src="../images/Image30_goto_resource.png"  alt="Goto Resource popup" border="0">
-</P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12d.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12d.htm
deleted file mode 100644
index 49e55b0..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12d.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Go Into</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3> Go Into&nbsp;</h3>
-<P CLASS="Para"> The navigation view shows all of the resources in the Workbench. 
-  Select a project or folder, choose to &quot;Go Into it&quot; and hide all other 
-  resources as demonstrated with the JaneQuser project.</P>
-<ol>
-  <li>
-    <P CLASS="Para"> Select the Navigator view. Its title bar will be highlighted 
-      (according to the operating system's color scheme).</P>
-  </li>
-  <li>
-<p CLASS="Para">
-Select the JaneQuser project.</p>
-  </li>
-  <li>
-<P CLASS="Para">
-Choose <b>Go Into</b> from the popup menu.</P>
-  </li>
-  <li>
-    <p CLASS="Para">The Navigator now shows only the contents of the JaneQuser 
-      project. The title of the Navigator shows the name of the resource that 
-      is currently displayed.</p>
-<p CLASS="Para"><img src="../images/Image31_go_into.png"  alt="Navigator view" border="0"></p></li>
-  <li>
-    <P CLASS="Para">The back, forward and up buttons <img src="../images/Image33_into_buttons.png"  alt="into buttons" border="0"> 
-      can be used to move between showing all resources and showing only the JaneQuser 
-      project. </P>
-<P CLASS="Para">Click the back button to show all of the
-resources.&nbsp; </P>
-  </li>
-</ol>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-13.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-13.htm
deleted file mode 100644
index 7ce9fed..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-13.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Files</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Files</h2>
-<p CLASS="Para">The projects, folders and files that you create with the Workbench are
-  all stored under a single directory that represents your workspace. The location of
-  the workspace was set in the dialog that first opens when you start the Workbench.</p>
-<p>If you have forgotten where that location is, you can find it by selecting
-  <b>File > Switch Workspace...</b>. The workspace directory will be displayed in
-  the dialog that appears.
-  <b>IMPORTANT:</b> After recording this location, hit <b>Cancel</b> to close the dialog,
-  or the Workbench will exit and re-open on whatever workspace was selected.</p>
-<p CLASS="Para">All of the projects, folders and files that you create with the 
-  Workbench are stored as normal directories and files on the machine. This allows
-  the use of other tools when working with the files. 
-  Those tools can be completely oblivious to the Workbench. A later section will 
-  look at how to work with external editors that are not integrated into the Workbench.</p>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-24a.xhtml b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-24a.xhtml
deleted file mode 100644
index 4739ac4..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-24a.xhtml
+++ /dev/null

@@ -1,101 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-	<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." />
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css" />
-<title>Exporting files</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body bgcolor="#ffffff">
-<h1>
-Exporting files </h1>
-<p class="Para">Files can be exported from the Workbench either by:</p>
-<ul>
-  <li> Dragging and dropping to the file system (Windows and Linux GTK only), or</li>
-  <li filter="ws=win32"> <img align="texttop" border="0" src="../images/win_only.png" alt="Windows only" />
-    Copying and pasting to the file system, or</li>
-  <li> Using the
-  <a class="command-link" href="javascript:executeCommand(&quot;org.eclipse.ui.file.export&quot;)">
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Export wizard</b></a>.</li>
-</ul>
-<h2>
-Drag and drop or copy and paste</h2>
-<p class="Para" filter="ws=win32"> <img align="texttop" border="0" src="../images/win_only.png" alt="Windows only" /> 
-  The operating system's file system explorer can be used to export a copy of 
-  a folder or file from the Workbench to the file system.</p>
-<ol>
-  <li> 
-    <p class="Para"> Open the operating system's file system explorer.</p>
-  </li>
-  <li> 
-    <p class="Para"> Drag the file JanesFile.txt from one of the navigation view 
-      to the file system explorer.</p>
-  </li>
-  <li> 
-    <p class="Para">Depending on where you are dragging to, you may need to hold 
-      down the Ctrl or Shift key while dragging to ensure the file is copied. 
-      Look for a small plus sign on the drag cursor to know whether the file is 
-      being copied or moved. </p>
-  </li>
-  <li filter="ws=win32"> 
-    <p class="Para"> The export can also be achieved by selecting the file in 
-      the Navigator and choosing <b>Edit &gt; Copy</b>, then</p> 
-    <p class="Para">pasting it in the file system explorer.</p> </li>
-</ol>
-<h2>
- Export wizard</h2>
-<p class="Para"> The Export wizard can be used to export from the Workbench to 
-  the file system.</p>
-<ol>
-  <li> 
-    <p class="Para"> Select the project JaneQuser in the navigation view. </p>
-  </li>
-  <li> 
-    <p class="Para"> From the popup menu, select <b>Export</b>.</p>
-  </li>
-  <li> 
-    <p class="Para"> In the Export wizard, select <b>File system</b>, then click 
-      <b>Next</b>.</p>
-    <p class="Para"> <img src="../images/Image42_export.png" alt="Export Wizard. Select an export destination." border="0" /></p>
-  </li>
-  <li> 
-    <p class="Para">Expand JaneQuser project, and click on JanesFolder. In the 
-      right pane ensure that only JanesINIFile.ini is selected. Notice the 
-      folder and project in the left pane now have a grayed checkbox indicating 
-      that some, but not all, of their contents will be exported.</p>
-    <p class="Para">The <b>Select Types</b> button can be used to filter the types 
-      of resources to export.</p>
-    <p class="Para"><strong>Note:</strong> To export JanesINIFile.ini only, simply 
-      select it in the navigation view and choose <b>File &gt; Export</b>. The 
-      Export wizard will automatically ensure it is the only file selected for 
-      export. </p>
-    <p class="Para"> <img src="../images/Image43_export_tree.png" alt="Export Wizard. Enter a destination directory." border="0" /></p>
-  </li>
-  <li> 
-    <p class="Para"> In the <b> To directory</b> field, type or browse to select 
-      a location in the file system for the exported resources to reside.</p>
-    <p class="Para"> If the name of a directory that does not exist is entered 
-      the Export wizard will offer to create it once <b>Finish</b> is selected.</p>
-  </li>
-  <li> 
-    <p class="Para"> In the <b>Options</b> area, options are given to:</p>
-    <ul class="UnorderedList">
-      <li class="Item"> Overwrite existing resources without warning </li>
-      <li class="Item"> Create directory structure for files or Create only selected 
-        directories</li>
-    </ul>
-  </li>
-  <li> 
-    <p class="Para"> Click <b>Finish</b> when done.</p>
-  </li>
-</ol>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-24c.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-24c.htm
deleted file mode 100644
index 51d0979..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-24c.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Export wizard</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
- Export wizard</h3>
-<P CLASS="Para"> The Export wizard can be used to export from the Workbench to 
-  the file system.</P>
-<ol>
-  <li> 
-    <P CLASS="Para"> Select the project JaneQuser in the Navigator. </P>
-  </li>
-  <li> 
-    <P CLASS="Para"> From the popup menu, select <b>Export</b>.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the Export wizard, select <b>File system</b>, then click 
-      <b>Next</b>.</P>
-    <P CLASS="Para"> <img src="../images/Image42_export.png"  alt="Export Wizard. Select an export destination." border="0"></P>
-  </li>
-  <li> 
-    <p class="Para">Expand JaneQuser project, and click on JanesFolder. In the 
-      right pane ensure that only JanesINIFile.ini is selected.&nbsp; Notice the 
-      folder and project in the left pane now have a grayed checkbox indicating 
-      that some, but not all, of their contents will be exported.</p>
-    <p class="Para">The <b>Select Types</b> button can be used to filter the types 
-      of resources to export.</p>
-    <p class="Para"><strong>Note:</strong> To export JanesINIFile.ini only, simply 
-      select it in the Navigator and choose <b>File &gt; Export</b>. The Export 
-      wizard will automatically ensure it is the only file selected for export. 
-    </p>
-	<p class="Para"> <img src="../images/Image43_export_tree.png"  alt="Export Wizard. Enter a destination directory." border="0"></p>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the <b> To directory</b> field, type or browse to select 
-      a location in the file system for the exported resources to reside.</P>
-    <P CLASS="Para"> If the name of a directory that does not exist is entered 
-      the Export wizard will offer to create it once <b>Finish</b> is selected.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the <b>Options</b> area, options are given to:</P>
-    <UL CLASS="UnorderedList">
-      <LI CLASS="Item"> Overwrite existing resources without warning </LI>
-      <LI CLASS="Item"> Create directory structure for files or Create only selected 
-        directories</LI>
-    </UL>
-  </li>
-  <li> 
-    <P CLASS="Para"> Click <b>Finish</b> when done.</P>
-  </li>
-</ol>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31a.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31a.htm
deleted file mode 100644
index fb4bab9..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31a.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Importing files</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h2>
-Importing files </h2>
-<P CLASS="Para"> Files can be imported into the Workbench either by :</P>
-<ul>
-  <li>
-    dragging and dropping from the file system, or</li>
-  <li>
-    copying and pasting from the file system, or</li>
-  <li>
-     Using the
-     <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import")'>
-     <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-     <b>Import wizard</b></a>.</li>
-</ul>
-<p>Using drag and drop or copy/paste to import files relies on operating system support
-  that is not necessarily available on all platforms. If the platform you are using
-  does not have this support, you can always use the Import wizard.</p>
-<p CLASS="Para"> In this section the two files that were just exported will be 
-  imported and placed into the second project JaneQuser2. <br>
-</p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31b.htm
deleted file mode 100644
index 354128e..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31b.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Drag and drop or copy and paste</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Drag and drop or copy and paste</h3>
-<P CLASS="Para"> 
-  On some platforms, for example on the Macintosh and Microsoft Windows,
-  the operating system's file system browser can be used to copy folders and files 
-  from the file system into the Workbench.</P>
-<P CLASS="Para"> <strong>Note: </strong>The resource(s) must be dragged to the 
-  exact location in the hierarchy of one of the navigation views where the resources 
-  are to reside; they cannot be simply dragged and dropped onto a blank area in 
-  the navigation view.</P>
-<ol>
-  <li> 
-    <P CLASS="Para"> Open the operating system's file system explorer.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Locate the file JanesFile.txt that was recently exported 
-      and drag it to a specific location in one of the navigation views in the 
-      Workbench.&nbsp;&nbsp;</P>
-    <P CLASS="Para">When dragging resources into one of the navigation views, 
-      the project/folder that the resource is being dropped into will be selected.</P>
-    <blockquote> 
-      <blockquote> 
-        <P CLASS="Para"> <img src="../images/Image37drop.png"  alt="Navigator view" border="0"></P>
-      </blockquote>
-    </blockquote>
-    <P CLASS="Para"> Drag the file over JaneQuser2 and release the mouse button.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Notice that the file is copied into the Workbench and placed 
-      into JaneQuser2.</P>
-  </li>
-  <li>This can also be achieved by copying the file in the file system explorer, 
-    then selecting the destination in the navigation view and choosing <b>Edit 
-    &gt; Paste</b>. </li>
-</ol>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31c.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31c.htm
deleted file mode 100644
index 8a21403..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31c.htm
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Import wizard</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Import wizard</h3>
-<P CLASS="Para"> The Import wizard can be used to copy resources into the Workbench.</P>
-<ol>
-  <li> 
-    <p CLASS="Para"> Select the project JaneQuser.</p>
-  </li>
-  <li> 
-    <P CLASS="Para"> Select <b>Import</b> from the popup.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the Import wizard, select <b>File system</b>, then click 
-      <b>Next</b>.</P>
-    <P CLASS="Para"> <img src="../images/Image38_import.png"  alt="Import Wizard. Import resources from the local file system." border="0"></P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the <b>From directory</b> field, type or browse to select 
-      the directory containing the file JanesINIFile.ini that was recently exported.</P>
-    <P CLASS="Para">Recent directories that have been imported from are shown 
-      on the <b>From directory</b> field's combo box.</P>
-    <blockquote> 
-      <P CLASS="Para">&nbsp;<img src="../images/Image41_import_combo.png"  alt="Import Wizard. From directory field." border="0"></P>
-    </blockquote>
-  </li>
-  <li> 
-    <P CLASS="Para">In the right pane check the file JanesINIFile.ini&nbsp;&nbsp;</P>
-    <P CLASS="Para"> Checking a folder in the left pane will import its entire 
-      contents into the Workbench. A grayed checkbox (as shown below) indicates 
-      that only some of the files in the folder will be imported into the Workbench.</P>
-    <P CLASS="Para">The <b>Filter Types</b> button can be used to filter the types 
-      of files that will be imported.</P>
-    <P CLASS="Para"><img src="../images/Image39_import_tree.png"  alt="Import Wizard. Filter types." border="0"></P>
-  </li>
-  <li> 
-    <P CLASS="Para"> The <b>Into folder</b> field should already be filled in 
-      with the name of the project (JaneQuser).&nbsp; </P>
-  </li>
-  <li> 
-    <P CLASS="Para">The destination project or folder can be changed by clicking 
-      <b>Browse</b>; </P>
-    <P CLASS="Para">Click the <b>Browse</b> button and choose the second project 
-      JaneQuser2.&nbsp; </P>
-    <blockquote> 
-      <blockquote> 
-        <P CLASS="Para"> <img src="../images/Image40_import_target.png"  alt="Import Wizard. Select a folder to import into." border="0"></P>
-      </blockquote>
-    </blockquote>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the <b>Options</b> area, options are given to: </P>
-    <UL CLASS="UnorderedList">
-      <LI CLASS="Item"> Overwrite existing resources without warning </LI>
-      <LI CLASS="Item"> Create complete folder structure or Create selected folders 
-        only</LI>
-    </UL>
-  </li>
-  <li> 
-    <P CLASS="Para"> Click <b>Finish</b> when done. The file JaneINIFile.ini is 
-      now shown in the one of the navigation views in the project JaneQuser2.</P>
-  </li>
-</ol>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-32.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-32.htm
deleted file mode 100644
index 6a307db..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-32.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Deleting resources</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Deleting resources</h2>
-<P CLASS="Para">Now that a few files have been imported into the second project 
-  (JaneQuser2), here are instructions on how to delete the project.&nbsp;</P>
-<ol>
-  <li> 
-    <P CLASS="Para">Select project JaneQuser2 in one of the navigation views.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> To delete the project do one of the following:</P>
-    <ul>
-      <li> From the project's pop-up menu choose <b>Delete</b> </li>
-      <li>Press the DEL key </li>
-      <li>Choose <b>Edit &gt; Delete</b> from the pull-down menu</li>
-    </ul>
-  </li>
-  <li> 
-    <P CLASS="Para"> A prompt will ask for confirmation of the deletion and also 
-      what type of deletion should be performed.</P>
-    <P CLASS="Para"> It is possible to:</P>
-    <ul>
-      <li> 
-        <p CLASS="Para">Delete the contents of the project from the file system</p>
-      </li>
-      <li> 
-        <p CLASS="Para">Delete the project from the workspace but keep its contents 
-          in the file system</p>
-      </li>
-      <li>Accept the default (do not delete contents) and click <b>Yes</b>.</li>
-    </ul>
-  </li>
-</ol>
-<p><strong>Note:</strong> This is only an option for projects. Files and folders 
-  are always deleted from the file system when deleted.</p>
-<P> The same steps work for any resource shown in the navigation view. <br>
-</P>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34a.xhtml b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34a.xhtml
deleted file mode 100644
index 56b25eb..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34a.xhtml
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." />
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css" />
-<title>Working with other editors</title>
-
-</head>
-<body bgcolor="#ffffff">
-<h2>
-Working with other editors</h2>
-<p class="Para"> Instructions have been given explaining how to import and export 
-  resources from the Workbench. This section will look at how to edit Workbench 
-  resources using the following three approaches:</p>
-<ul>
-  <li>
-    External editors launched by the Workbench</li>
-  <li filter="ws=win32">
-    Embedded OLE documents <img src="../images/win_only.png" alt="Windows only" border="0" /></li>
-  <li>
-    External editors launched without the Workbench's knowledge</li>
-</ul>
-<p class="Para">Before continuing, take a moment and confirm that the Navigator 
-  contains the following resources:</p>
-<blockquote>
-  <blockquote>
-    <p class="Para" align="center"><img src="../images/Image44_confirm_state.png" alt="Navigator view" border="0" /></p>
-  </blockquote>
-</blockquote>
-
-
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34b.xhtml b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34b.xhtml
deleted file mode 100644
index 08ac4bc..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34b.xhtml
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." />
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css" />
-<title>External editors</title>
-
-</head>
-<body bgcolor="#ffffff">
-<h3>
-External editors</h3>
-<p class="Para">When opening a resource the Workbench first consults its list 
-  of registered editors. If no registered editors are found for the resource the 
-  Workbench checks with the underlying operating system to determine if it has 
-  any editors registered for the particular file type. If an editor is located, 
-  the Workbench will automatically launch that editor. This type of editor is 
-  referred to as an external editor because it does not show up as an editor tab 
-  in the Workbench.</p>
-<ol>
-  <li>
-<p class="Para">Select the file JanesINIFile.ini.</p>
-  </li>
-  <li>
-<p class="Para">
-Double-click the file in one of the navigation views to launch the external editor.</p>
-    <p class="Para"> If an editor for INI files is not registered with the underlying 
-      operating system the Workbench will attempt to use its own default text 
-      editor. If this happens, to see an external editor, import another file 
-      (see previous sections) that is associated with a third party editor. Double 
-      click again on this new file and the selected editor will open in its own 
-      window.</p>
-<p class="Para" filter="ws=win32"><img src="../images/win_only.png" alt="Windows only" border="0" /><br />
-      The Workbench supports OLE document editors, and some editors provide OLE 
-      document support allowing it to be opened in its own window, or embedded 
-      inside another window like the Workbench. This will be discussed in more 
-      detail in the next section.</p>
-  </li>
-</ol>
-
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34c.xhtml b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34c.xhtml
deleted file mode 100644
index 4e2c8dd..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34c.xhtml
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." />
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css" />
-<title>Embedded editors</title>
-
-</head>
-<body bgcolor="#ffffff">
-<h3>
-Embedded editors</h3>
-<p class="Para"> <img src="../images/win_only.png" alt="Windows only" border="0" />The 
-  Workbench supports OLE document editors.</p>
-<p class="Para"><img src="../images/Image619_ole.png" alt="OLE document editor." border="0" /></p>
-<ol>
-  <li> 
-    <p class="Para"> Select JanesFolder in the navigation view.</p>
-  </li>
-  <li>Create the file Jane.doc. </li>
-  <li> 
-    <p class="Para">Notice how the Workbench automatically opens the OLE document 
-      editor in place and integrates its pull-down menu options into the menu 
-      bar. There should also be an editor tab for Jane.doc.</p>
-  </li>
-  <li> 
-    <p class="Para"> Make a change to the file.</p>
-  </li>
-  <li> 
-    <p class="Para"> Close the editor by clicking the X on the editor tab; when 
-      prompted, save its contents.</p>
-  </li>
-  <li> 
-    <p class="Para"> Reopen the file by double-clicking it in the navigation view.</p>
-  </li>
-</ol>
-
-
-
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34d.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34d.htm
deleted file mode 100644
index 8f9cf28..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34d.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Editing files outside the Workbench</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Editing files outside the Workbench</h3>
-<P CLASS="Para"> In a previous section an external editor was launched on the 
-  file JanesINIFile.ini by double clicking on it in the Navigator. The same external 
-  editor can also be used by launching it outside of the Workbench.&nbsp;</P>
-<ol>
-  <li> 
-    <P CLASS="Para"> Close any editors that are open on JanesINIFile.ini.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the file system explorer, navigate to the directory where 
-      the Workbench was installed and go into the workspace sub-directory.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Edit the file JanesINIFile.ini and save it . Do not use the 
-      Workbench's Navigator to open the editor.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Return to the Workbench and in the Navigator view, select 
-      the project JaneQuser.&nbsp;</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Choose <b>Refresh</b> from the project's context menu. This 
-      instructs the Workbench to look for any changes to the project that have 
-      been made in the local file system by external tools.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Select the file JanesINIFile.ini.</P>
-  </li>
-  <li> 
-    <p CLASS="Para"> For a little variety choose <b>Open With &gt; Text Editor</b> 
-      from the file's popup menu.</p>
-  </li>
-  <li> 
-    <P CLASS="Para"> Observe that the Workbench's own default text editor is opened.&nbsp;</P>
-    <P CLASS="Para"> In the default text editor verify that the externally made 
-      changes are reflected in the Workbench.</P>
-  </li>
-</ol>
-<P>The Workbench stores all of its resources in the local file system. This means 
-  the system file explorer can be used to copy files from the Workbench's workspace 
-  area even when the Workbench is not running. Resources can also be copied into 
-  the workspace directory. Use Refresh to update the Workbench with any changes 
-  made outside the Workbench.&nbsp; &nbsp; </P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35.htm
deleted file mode 100644
index 08b54d4..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Copying, renaming and moving</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>
-Copying, renaming and moving</h1>
-<P CLASS="Para">Workbench resources can be copied, moved and renamed using popup 
-  menu operations in one of the navigation views. In this section several of the 
-  files that have been created will be copied and renamed.&nbsp;</P>
-<P CLASS="Para">Prior to copying files, some setup is required:</P>
-<p CLASS="Head"><b><a name="Setup">Setup</a></b></p>
-<ol>
-  <li> 
-    <p CLASS="Head">In one of the navigation views, delete the file JanesWordDoc.doc. 
-      The navigation view should look like this:</p>
-    <blockquote> 
-      <P CLASS="Para"> <img src="../images/Image44_confirm_state.png" alt="Navigator view" border="0"></P>
-    </blockquote>
-    <p CLASS="Head">&nbsp;</p>
-  </li>
-  <li> 
-    <P CLASS="Para">Double click on JanesFile.txt and ensure that it contains 
-      the following text.</P>
-    <blockquote> 
-      <P><i>This is a sample text file<br>
-        There is not much else<br>
-        we can really say about it other<br>
-        than it has five lines of<br>
-        text that are rather dull.</i></P>
-    </blockquote>
-  </li>
-  <li> 
-    <p CLASS="Head">Close the editor on JanesFile.txt.</p>
-  </li>
-  <li> 
-    <p CLASS="Para"> Select the project JaneQuser. Using the project's pop-up 
-      menu create a folder named JanesOtherFolder.</p>
-    <blockquote> 
-      <p CLASS="Para"><img src="../images/Image45_setup.png" alt="Navigator view" border="0"></p>
-    </blockquote>
-  </li>
-</ol>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35b.htm
deleted file mode 100644
index fa0f893..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35b.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Copying</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Copying</h3>
-<p CLASS="Head">You can copy JanesFile.txt to the new folder (JanesOtherFolder) using
-  the following steps. </p>
-<ol>
-  <li> 
-    <p CLASS="Head"> Ensure that the setup described in the introduction to this 
-      <a href="qs-35.htm#setup">section</a> has been performed.</p>
-  </li>
-  <li> 
-    <p CLASS="Para"> In one of the navigation views, select JanesFile.txt.</p>
-  </li>
-  <li> 
-    <P CLASS="Para"> From the file's context menu, select <b>Copy</b> (or Ctrl+C)</P>
-  </li>
-  <li>In one of the navigation views, select JanesOtherFolder as the destination.</li>
-  <li> 
-    <p CLASS="Head"> From the folder's context menu, select <b>Paste</b> (or Ctrl+V).</p>
-  </li>
-</ol>
-<P>As an alternative to copying files using the copy operation, it is also possible 
-  to copy files by holding down the Ctrl key while dragging a file from one folder 
-  to another folder. (On the Macintosh, the Option key is used for this.)</P>
-<p>Once the file has been copied it can be renamed.</p>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35c.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35c.htm
deleted file mode 100644
index 815aa67..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35c.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Renaming</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Renaming</h3>
-<p CLASS="Head">Now that JanesFile.txt has been copied from JanesFolder to JanesOtherFolder 
-  it is ready to be renamed as something else.&nbsp;</p>
-<ol>
-  <li>
-    <p CLASS="Head">In one of the navigation views, select JanesFile.txt in JanesOtherFolder.</p>
-  </li>
-  <li>
-<P CLASS="Para">
-From the file's context menu, select <b>Rename</b>.</P>
-  </li>
-  <li>
-    <p CLASS="Para">The navigation view overlays the file's name with a text field.&nbsp;&nbsp;Type 
-      in JanesText.txt and press Enter.</p>
-<DIV CLASS="Note">
-<P CLASS="Para">&nbsp;
-</P>
-<blockquote>
-  <P CLASS="Para">
-<img src="../images/Image48_rename.png"  alt="Navigator view" border="0"></P>
-</blockquote>
-      <P CLASS="Para">To halt the renaming of a resource, Escape can be pressed 
-        to dismiss the text field.</P>
-</DIV>
-  </li>
-</ol>
-<P>Copy and rename works on folders as well.&nbsp; </P>
-
-
-<ol>
-  <li> 
-    <P CLASS="Para"> In one of the navigation views, select the folder JanesOtherFolder.</P>
-  </li>
-  <li> 
-    <p CLASS="Para"> From the folder's context menu choose <b>Rename</b>.</p>
-  </li>
-  <li>Once again the navigation view overlays the folder name with an entry field 
-    to allow the typing in of a new name. Change the folder name to be JanesSecondFolder.</li>
-  <li>Rename the folder back to its original name (JanesOtherFolder).</li>
-</ol>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35d.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35d.htm
deleted file mode 100644
index c74cf0a..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35d.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Moving</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Moving</h3>
-<p CLASS="Head">Having copied and renamed several of the resources, now it's time 
-  to move some resources around. JanesOtherFolder and its file will be moved to 
-  be a sub-folder of the original folder JanesFolder.</p>
-<ol>
-  <li>In the Navigator view, select JanesOtherFolder. </li>
-  <li>From the file's context menu, select <b>Move</b>.</li>
-  <li><p>In the Folder Selection dialog choose JanesFolder and click <b>OK</b>.</p>
-    <blockquote> 
-      <p CLASS="Para"><img src="../images/Image48_move.png"  alt="Folder dialog" border="0"></p>
-</blockquote>
-  </li>
-  <li>In the Navigator JanesFolder now contains JanesOtherFolder. Expand
-JanesOtherFolder and confirm that it contains JanesText.txt.
-<blockquote>
-  <p><img src="../images/Image48_rename_done.png"  alt="Navigator view" border="0"></p>
-</blockquote>
-  </li>
-</ol>
-
-
-<P>As an alternative to moving files using the move operation, it is also possible 
-  to move files by dragging a file from one folder to another folder. Remember 
-  that to copy files from one folder to the other, Ctrl needs to be held down 
-  while performing the drag and drop operation. (On the Macintosh, the Option 
-  key is used for this.) </P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36.htm
deleted file mode 100644
index 5eb83fa..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"><title>Searching</title></head>
-<body>
-
-<h2>Searching</h2>
-
-<p>Text strings and files can be searched for in the Workbench.&nbsp;In this section, 
-  <strong>Search </strong><img src="../images/Image50_search.png"  alt="Search button" border="0"> 
-  will be used to perform a text search across the resources that are shown in 
-  the navigation view. Instruction will also be given on how to use the Search 
-  view to work with the results.</p>
-
-
-
-
-</body></html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36a.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36a.htm
deleted file mode 100644
index fac0348..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36a.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Starting a search</title>
-
-</HEAD>
-<body>
-<h3>Starting a search</h3>
-
-<p>Text strings can be searched for in the Workbench as follows:</p>
-
-<ol>
-  <li>In the Workbench toolbar, click the search button <img src="../images/Image50_search.png"  alt="Search button" border="0">.</li>
-  <li>In the <b>Containing text</b> field, type in: <i>it</i> <br>
-    The combo box for the <b>Containing text</b> field also displays a list of 
-    recently performed searches to select from.<br>
-    <img src="../images/Image51_search_it.png"  alt="Search dialog" border="0"></li>
-  <li> The <b>Case sensitive</b> checkbox can be selected or deselected depending 
-    on whether or not a case sensitive or insensitive search is to be performed.
-    You can also select the <b>Regular expression</b> checkbox to enable more powerful searching
-    capabilities. To see what is available in regular expression mode, you can hit
-    Ctrl-Space over the text field to get content assistance that lists the possibilities.
-    For this example, just check the <b>Case sensitive</b> box to search for lowercase 
-    &quot;<i>it</i>&quot;.</li>
-  <li> The kinds of files to include in the search can be specified in the <b>File 
-    name patterns</b> field. Click <b>Choose...</b> to open the Select Types dialog. 
-    This dialog provides a quick way to select from a list of registered extensions. 
-    <blockquote><img src="../images/Image51_choose_ext.png" alt="Type Selection Dialog" border="0"></blockquote>
-    For the moment, the search will be confined to .txt files. Ensure *.txt is 
-    checked and click <b>OK</b>.</li>
-  <li>In the <b>Scope</b> field, specify the files and folders to include in the 
-    search. The choices are: the entire workspace, the currently selected resources 
-    in the Workbench, or a working set which is a named, customized group of files 
-    and folders. Leave the scope as workspace.</li>
-  <li> Use the <b>Customize</b> button to choose what kinds of searches are available 
-    in the dialog. This setting may be left unchanged.</li>
-  <li>Click <b>Search</b>. At this point, the Search view will be made visible, 
-    and it will begin to fill in with the results of the search. The stop button 
-    in the Search view can be clicked to cancel the search while it is in progress. 
-  </li>
-  <li>Observe that the Search view displays: 
-    <blockquote> <img src="../images/Image51_search_view.png" alt="Search view" border="0"></blockquote>
-  </li>
-</ol>
-
-<p> The next section will describe how to work with the Search view.</p>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36b.htm
deleted file mode 100644
index f35ce1d..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36b.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-	<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-	<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-
-	<title>The Search view</title>
-</head>
-
-<body>
-
-<h3>The Search view&nbsp;</h3>
-
-<p>Now that the search for &quot;it&quot; has been completed, the Search view 
-  is visible. The title of the Search view shows that four matches were found.&nbsp;</p>
-<blockquote> 
-  <p> <img src="../images/Image51_search_view.png"  alt="Search view. Four occurrences of the word it found in the Workspace." border="0">&nbsp;&nbsp;</p>
-</blockquote>
-<p CLASS="Head"> Within the Search view two files are shown and within each file 
-  there were 2 matches found.&nbsp; </p>
-    <ol>
-  <li>Click the Show Next Match button <img src="../images/Image51_search_next.png"  alt="Show next match button" border="0">to 
-    navigate to the first match of the search expression (&quot;it&quot;). <br>
-    Notice that the file JanesFile.txt is automatically selected and opened in 
-    the editor area. <br>
-    Click Show Next Match button two more times. Once again the Search view automatically 
-    opens the file (JanesText.txt).</li>
-  <li>It is sometimes useful to remove uninteresting matches from the search results. 
-    The Search view's popup menu allows you to do this using <b>Remove Selected 
-    Matches</b> which removes any selected file entries (and all matches in them) 
-    from the Search view. Note that this <strong>only</strong> removes the entries 
-    in the Search view, it does <strong>not</strong> effect the files themselves. 
-    Select JanesFile.txt and choose <b>Remove Selected Matches</b> from the popup 
-    menu. The Search view now shows only the matches for JanesText.txt 
-    <blockquote><img src="../images/Image51_search_reduced.png"  alt="Search view. One occurrence in Workspace." border="0"></blockquote>
-  </li>
-  <li>Perform a second search for &quot;that&quot; by clicking on the Search button 
-    <img src="../images/Image50_search.png"  alt="Search button" border="0"> in 
-    the Workbench's toolbar.</li>
-  <li><p>The Search view updates to show the results of the new search. <br>
-    Use the drop down button on the Search view's toolbar to move back and forth 
-    between the two search results. 
-    <blockquote><img src="../images/Image51_search_switching.png"  alt="Search view. Drop down button." border="0"></blockquote></p>
-  </li>
-  <li>In the drop down button choose &quot;it&quot; - 1 Occurrence. The Search 
-    view switches back to show the original search. On the context menu choose 
-    <b>Search Again</b> to repeat the initial search. Notice that once again there 
-    are four matches.</li>
-</ol>
-
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2b.htm
deleted file mode 100644
index c9c08ab..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2b.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Tasks and markers</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Tasks and markers</h2>
-<P CLASS="Para"> There are various types of markers including bookmarks, task 
-  markers, debugging breakpoints and problems. This section will focus on tasks 
-  and the Tasks view.</P>
-<P CLASS="Para"> The Tasks view displays all the tasks in the Workbench. 
-  The view displays tasks associated with specific files, specific lines in specific 
-  files, as well as generic tasks that are not associated with any specific file.</P>
-<P CLASS="Para">
-In the figure below &quot;sample task&quot; is a generic task not associated
-with any specific resource. The second task (&quot;add sixth line to the
-text&quot;) is associated with the file JanesFile.txt.</P>
-<P>&nbsp;<img src="../images/Image21_task_view.png" alt="Task view" border="0">
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2d.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2d.htm
deleted file mode 100644
index c05be66..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2d.htm
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Unassociated tasks</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Unassociated
-tasks</h3>
-<P CLASS="Para">
-Unassociated tasks are not associated with any specific resource. To create an 
-unassociated task: </P>
-<ol>
-  <li> 
-    <P CLASS="Para"> In the Tasks view, click the New Task button <img src="../images/Image52_new_task.png" alt="New task button" border="0" >. 
-      A new task dialog appears. </P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Type a brief description for the task and press Enter. To 
-      cancel the dialog while entering the description press Escape . The new 
-      task appears in the Tasks view.</P>
-    <p CLASS="Para"><img src="../images/Image53_newtask.png" alt="Tasks view" border="0" ></p></li>
-</ol>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2d2.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2d2.htm
deleted file mode 100644
index d1a8d24..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2d2.htm
+++ /dev/null

@@ -1,84 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Associated tasks</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Associated tasks</h3>
-<P CLASS="Para"> Associated tasks are associated with a specific location in a 
-  resource. To associate a task with the&nbsp;JanesFile.txt:</P>
-<ol>
-  <li> 
-    <P CLASS="Para"> Open a text file (JanesFile.txt) by double clicking on it 
-      in one of the navigation views.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the editor area directly to the left of any line in the 
-      text editor, access the context menu from the marker bar. The marker bar 
-      is the vertical bar to the left of the main text area.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> From the marker bar's context menu, select <b>Add Task</b>.</P>
-    <P CLASS="Para"> The marker bar displays any marker including bookmarks, task 
-      markers (for associated tasks), and/or debugging breakpoints. Various markers 
-      can be associated with specific lines in a file by accessing the context 
-      menu from the marker bar directly to the left of that line.</P>
-    <P CLASS="Para"> <img src="../images/Image53_marker1.png"  alt="Marker bar menu" border="0"></P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the <b>Description</b> field, type a brief description 
-      for the task that will be associated with that line in the text file.</P>
-    <blockquote> 
-      <P CLASS="Para"> <img src="../images/Image53_add_task_dlg.png"  alt="Add Task dialog" border="0"></P>
-    </blockquote>
-  </li>
-  <li> 
-    <P CLASS="Para"> Click <b>OK</b> when done.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Notice that a new task marker appears in the marker bar, 
-      directly to the left of the line where the task was added. Also, notice 
-      that the new task appears in the Tasks view.</P>
-    <P CLASS="Para"> <img src="../images/Image53_task_updated.png"  alt="Tasks view" border="0"></P>
-  </li>
-  <li> 
-    <P CLASS="Para"> After the new task has been added, click in the editor on 
-      the first line or any other line above the line with which the new task 
-      is associated.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Add several lines of text to the file at this point.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Notice that as lines of text are added above it, the task 
-      marker moves down in the marker bar in order to remain with the associated 
-      line in the file. The line number in the Tasks view is updated when the 
-      file is saved.&nbsp;</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the Tasks view, access the context menu for the task that 
-      was just created.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Select <b>Mark Completed</b>. </P>
-  </li>
-  <li>Now select <b>Delete Completed Tasks</b> from the marker's context menu.</li>
-  <li> 
-    <P CLASS="Para"> Notice that the task marker disappears from the marker bar 
-      and the task is removed from the Tasks view.</P>
-  </li>
-</ol>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2f.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2f.htm
deleted file mode 100644
index 6942ce7..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2f.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Opening files</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Opening
-files</h3>
-<P CLASS="Para">
-The Tasks view provides two approaches for opening the file associated with a
-task:</P>
-<ul>
-  <li> Select the task, and from the context menu choose <b>Go To</b></li>
-  <li>
-    Double click on the task</li>
-</ul>
-<p CLASS="Para">In both cases the file's editor is opened and the line with which the selected task is associated is highlighted.
-<br>
-</p>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3b.htm
deleted file mode 100644
index 9b30c48..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3b.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Bookmarks</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Bookmarks</h2>
-<P CLASS="Para"> Bookmarks are a simple way to navigate to resources that are 
-  used frequently. This section will look at setting and removing bookmarks and 
-  viewing them in the Bookmarks view.</P>
-<P CLASS="Para"> The Bookmarks&nbsp;view displays all bookmarks&nbsp;in the Workbench. 
-  To show the Bookmarks view select <b>Window &gt; Show View &gt; Bookmarks</b> 
-  while in the Resource perspective.</P>
-<blockquote>
-  <P>&nbsp;<img src="../images/Image54_bookmark1.png" alt="Bookmarks view" border="0" >
-</P>
-
-
-</blockquote>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3c.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3c.htm
deleted file mode 100644
index aa938f5..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3c.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Adding and viewing bookmarks</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Adding and viewing bookmarks</h3>
-<p CLASS="Head">The Workbench allows the bookmarking of individual files or locations 
-  within a file. This section will demonstrate how to set several bookmarks and 
-  how to view them using the Bookmarks view.</p>
-<ol>
-  <li>
-<p CLASS="Head">From the menu bar, select <b>Window &gt; Show View &gt; Bookmarks</b>. The
-Bookmarks view appears in the Workbench.&nbsp;</p>
-  </li>
-  <li>
-    <P CLASS="Para"> Edit the file JanesFile.txt.</P>
-  </li>
-  <li>
-    <P CLASS="Para"> Position the cursor over the editor's marker bar next to 
-      any line in the file. Then, from the context menu on the marker bar, select 
-      <b>Add Bookmark</b>.</P>
-<blockquote>
-<P CLASS="Para">
-<img src="../images/Image54_bookmark_menu.png"  alt="Bookmark Menu" border="0"></P>
-</blockquote>
-<P CLASS="Para">When the Add Bookmark dialog opens type in a description for 
-this bookmark. Type in &quot;My Bookmark&quot;.</P>
-  </li>
-  <li>
-<P CLASS="Para">
-Notice that a new bookmark appears in the marker bar.</P>
-<blockquote>
-<P CLASS="Para">
-<img src="../images/Image54_bookmark_added.png" alt="Editor with bookmark" border="0" >&nbsp;</P>
-</blockquote>
-<P CLASS="Para">
-The new bookmark also appears in the Bookmarks view.</P>
-<blockquote>
-<P CLASS="Para">
-<img src="../images/Image54_bookmark_added2.png" alt="Bookmark view" border="0" ></P>
-</blockquote>
-  </li>
-  <li>
-    <P CLASS="Para"> In one of the navigation views select the file JanesText.txt. From 
-      the main Workbench menu select <strong>Edit &gt; </strong><b>Add Bookmark</b>.</P>
-<P CLASS="Para">
-This will bookmark the file using the filename to describe the bookmark. Observe the Bookmarks view now contains two
-bookmarks.</P>
-<blockquote>
-<P CLASS="Para">
-<img src="../images/Image54_bookmark_two.png" alt="Bookmark view" border="0" ></P>
-</blockquote>
-  </li>
-</ol>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3e.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3e.htm
deleted file mode 100644
index bb76e48..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3e.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Using bookmarks</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Using bookmarks</h3>
-<p CLASS="Head"> Now that some bookmarks have been created, instructions will 
-  be given on how to get to the files associated with the bookmarks.</p>
-<ol>
-  <li> 
-    <P CLASS="Para"> Close all of the files in the editor area.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the Bookmarks view, double-click on the first bookmark 
-      that was created (My Bookmark).</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Notice that a file editor opens displaying the file with 
-      which the bookmark is associated and that the line associated with the bookmark 
-      is highlighted.<br> 
-	  <strong>Note:</strong> The Bookmarks view supports an additional 
-      way to open the file associated with a selected bookmark, simply select 
-      <b>Go To </b>from the bookmark's context menu.<b> </b></P>
-  </li>
-</ol>
-<p CLASS="Head"> In the Bookmarks view, select the associated file in the Navigator. 
-</p>
-<ol>
-  <li>In the Bookmarks view, select My Bookmark.</li>
-  <li>From the bookmark's context menu choose <b>Show in Navigator</b>. </li>
-  <li>
-    <P CLASS="Para"> Notice that the Navigator view is now visible and the file 
-      JanesFile.txt is automatically selected. JanesFile.txt is the file My Bookmark 
-      was associated with.</P>
-  </li>
-</ol>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3f.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3f.htm
deleted file mode 100644
index e118d64..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3f.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Removing bookmarks</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Removing bookmarks</h3>
-<p CLASS="Head">This section will demonstrate how to remove the bookmarks that 
-  have been created.</p>
-<ol>
-  <li> 
-    <P CLASS="Para"> In the Bookmarks view, select JanesFile.txt (the second bookmark 
-      we created) and do one of the following:</P>
-    <ul>
-      <li> Click the Delete button <img src="../images/Image54_bookmark_del1.png" alt="Bookmark delete button" border="0" > 
-        on the view's toolbar. </li>
-      <li> From the bookmark's context menu choose delete.</li>
-      <li> Hit the Delete key on the keyboard.</li>
-    </ul>
-    <P CLASS="Para"> Notice that the bookmark is removed from the Bookmarks view.</P>
-    <blockquote> 
-      <P CLASS="Para"> <img src="../images/Image54_bookmark_oneleft.png" alt="Bookmark view" border="0" ></P>
-    </blockquote>
-  </li>
-  <li>There should be one remaining bookmark. This bookmark is associated with 
-    a line in the file JanesFile.txt. There are two other approaches to removing 
-    this bookmark. 
-    <ul>
-      <li>Use <b>Remove Bookmark</b> in the marker bar of the JanesFile.txt editor. 
-        Remember, <b>Add Bookmark</b> was used <b></b>in the marker bar when the 
-        bookmark was first created.<br>
-        <img src="../images/Image54_bookmark_remove2.png" alt="Bookmark menu" border="0" ></li>
-      <li>Delete the bookmark (as was done above) by using <b>Delete</b> from 
-        the bookmark's popup menu in the Bookmarks view.</li>
-    </ul>
-    <p>Here is the second approach.&nbsp;</p>
-  </li>
-  <li> 
-    <P CLASS="Para">Ensure there is an editor open on JanesFile.txt.&nbsp;</P>
-    <P CLASS="Para">Although the editor doesn't actually need to be open, the 
-      editor update will be viewable as the bookmark is deleted.</P>
-  </li>
-  <li> 
-    <p CLASS="Head">In the Bookmarks view, select JanesFile.txt (the remaining 
-      bookmark). Click the Delete button <img src="../images/Image54_bookmark_del1.png" alt="Bookmark delete button" border="0" > 
-      on the view's toolbar. Notice that the bookmark is removed from the Bookmarks 
-      view and the JanesFile.txt editor.&nbsp; </p>
-  </li>
-</ol>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39.htm
deleted file mode 100644
index ec0c809..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Rearranging views and editors</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Rearranging views and editors</h2>
-<P CLASS="Para">This section will explain how to rearrange editors and views to 
-  customize the layout of the Workbench.</P>
-<P CLASS="Para"><b>Setup</b></P>
-<P CLASS="Para">Before rearranging the Workbench, a little housekeeping is required.</P>
-<ol>
-  <li>
-<P CLASS="Para">Start by choosing <b>Window &gt; Reset Perspective</b> and selecting <b>OK</b>. This will reset the
-current perspective to its original views and layout.</P>
-  </li>
-  <li>
-    <P CLASS="Para"> Ensure there are editors open for JanesFile.txt and JanesText.txt. 
-      Close any other editors.</P>
-  </li>
-</ol>
-<P>The Workbench should now look like this:&nbsp;&nbsp;&nbsp; </P>
-
-
-<P>&nbsp;<img src="../images/Image55_reset.png" alt="Workbench after reset" border="0">
-</P>
-
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39c.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39c.htm
deleted file mode 100644
index 90eff0e..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39c.htm
+++ /dev/null

@@ -1,86 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Drop cursors</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Drop cursors</h3>
-<P CLASS="Para"> Drop cursors indicate where it is possible to dock views in the 
-  Workbench window. Several different drop cursors may be displayed when rearranging 
-  views.</P>
-<TABLE BORDER="1" cellspacing="0">
-<THEAD>
-</THEAD>
-<TBODY>
-<TR>
-<TD height="38" valign="top" align="left">
-<P CLASS="Para">
-<img src="../images/drop_top_source.png" alt="Up arrow" border="0" >
-</P>
-</TD>
-      <TD height="38" valign="top" align="left"> <P CLASS="Para"> Dock above: 
-          If the mouse button is released when a dock above cursor is displayed, 
-          the view will appear above the view underneath the cursor.</P>
-</TD>
-</TR>
-<TR>
-<TD height="38" valign="top" align="left">
-<P CLASS="Para">
-<img src="../images/drop_bottom_source.png" alt="Down arrow" border="0" >
-</P>
-</TD>
-      <TD height="38" valign="top" align="left"> <p CLASS="Para"> Dock below: 
-          If the mouse button is released when a dock below cursor is displayed, 
-          the view will appear below the view underneath the cursor.</p></TD>
-</TR>
-<TR>
-<TD height="38" valign="top" align="left">
-<P CLASS="Para"><img src="../images/drop_right_source.png" alt="Right arrow" border="0" >
-</P>
-</TD>
-      <TD height="38" valign="top" align="left"> <p CLASS="Para"> Dock to the right: 
-          If the mouse button is released when a dock to the right cursor is displayed, 
-          the view will appear to the right of the view underneath the cursor.</p> 
-      </TD>
-</TR>
-<TR>
-<TD height="38" valign="top" align="left">
-<img src="../images/drop_left_source.png" alt="Left arrow" border="0" >
-</TD>
-      <TD height="38" valign="top" align="left"> Dock to the left: If the mouse button 
-        is released when a dock to the left cursor is displayed, the view will 
-        appear to the left of the view underneath the cursor. </TD>
-</TR>
-<TR>
-<TD height="38" valign="top" align="left">
-<img src="../images/drop_stack.png" alt="Stack icon" border="0" >
-</TD>
-      <TD height="38" valign="top" align="left"> Stack: If the mouse button is 
-        released when a stack cursor is displayed, the view will appear as a tab 
-        in the same pane as the view underneath the cursor. </TD>
-</TR>
-<TR>
-<TD height="38" valign="top" align="left">
-<img src="../images/drop_invalid_source.png" alt="Restricted icon" border="0" >
-</TD>
-      <TD height="38" valign="top" align="left"> Restricted: If the mouse button 
-        is released when a restricted cursor is displayed, the view will not dock 
-        there. For example, a view cannot be docked in the editor area. </TD>
-</TR>
-</TBODY>
-</TABLE>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39d.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39d.htm
deleted file mode 100644
index 94b612a..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39d.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Rearranging views</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Rearranging views</h3>
-<p CLASS="Head"> The position of the Navigator view in the Workbench window can 
-  be changed.</p>
-<ol>
-  <li> 
-    <p CLASS="Head"> Click in the title bar of the Navigator view and drag the 
-      view across the Workbench window. Do not release the mouse button yet.</p>
-  </li>
-  <li> 
-    <p CLASS="Head"> While still dragging the view around on top of the Workbench 
-      window, note that various drop cursors appear. These drop cursors (see previous 
-      section) indicate where the view will dock in relation to the view or editor 
-      area underneath the cursor when the mouse button is released. Notice also that
-      a rectangular highlight is drawn that provides additional feedback on where the
-      view will dock.</p>
-  </li>
-  <li> 
-    <P CLASS="Para"> Dock the view in any position in the Workbench window, and 
-      view the results of this action. </P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Click and drag the view's title bar to re-dock the view in 
-      another position in the Workbench window. Observe the results of this action. 
-    </P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Finally, drag the Navigator view over the Outline view. A 
-      stack cursor will be displayed. If the mouse button is released the Navigator 
-      will be stacked with the Outline view into a tabbed notebook.&nbsp;&nbsp; 
-    </P>
-  </li>
-</ol>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39e.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39e.htm
deleted file mode 100644
index f77f2ff..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39e.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Tiling editors</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Tiling editors</h3>
-<P CLASS="Para"> The Workbench allows for the creation of two or more sets of 
-  editors in the editor area. The editor area can also be resized but views cannot 
-  be dragged into the editor area.</P>
-<ol>
-  <li> 
-    <P CLASS="Para"> Open at least two editors in the editor area by double-clicking 
-      editable files in one of the navigation views.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Click and drag one of the editor's tabs out of the editor 
-      area. Do not release the mouse button.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Notice that the restricted cursor displays if an attempt 
-      is made to drop the editor either on top of any view or outside the Workbench 
-      window.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Still holding down the mouse button, drag the editor over 
-      the editor area and move the cursor along all four edges as well as in the 
-      middle of the editor area, on top of another open editor. Notice that along 
-      the edges of the editor area the directional arrow drop cursors appear, 
-      and in the middle of the editor area the stack drop cursor appears.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Dock the editor on a directional arrow drop cursor so that 
-      two editors appear in the editor area.&nbsp;</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Notice that each editor can also be resized as well as the 
-      entire editor area to accommodate the editors and views as necessary.</P>
-  </li>
-  <li> 
-    <p CLASS="Para"> It is important to observe the color of an editor tab (in 
-      the figure below there are two groups, one above the other)</p> 
-    <p CLASS="Para"><b>blue</b> - indicates that the editor is currently active</p>
-    <p CLASS="Para"><b>default </b>(gray on Windows XP) - indicates that the editor 
-      was the last active editor. If there is an active view, it will be the editor 
-      that the active view is currently working with. This is important when working 
-      with views like the Outline and Properties that work closely with the editor.</p></li>
-  <li> 
-    <P CLASS="Para"> Drag and dock the editor somewhere else in the editor area, 
-      noting the behavior that results from docking on each kind of drop cursor. 
-      Continue to experiment with docking and resizing editors and views until 
-      the Workbench has been arranged to satisfaction. The figure below illustrates 
-      the layout if one editor is dragged and dropped below another.</P>
-  </li>
-</ol>
-<P>&nbsp;<img src="../images/Image57_two_editors.png" alt="Two editors" border="0"><br>
-</P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39f.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39f.htm
deleted file mode 100644
index 735fce4..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39f.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Rearranging tabbed views</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Rearranging tabbed views</h3>
-<P CLASS="Para">In addition to dragging and dropping views on the Workbench the 
-  order of views can also be rearranged within a tabbed notebook.</P>
-<ol>
-  <li> 
-    <P CLASS="Para"> Choose <b>Window &gt; Reset Perspective</b> to reset the 
-      Resource perspective back to its original layout.&nbsp;</P>
-  </li>
-  <li> 
-    <P CLASS="Para">Click on the Outline title bar and drag it on top of one of 
-      the navigation views. The Outline will now be stacked on top of one of the 
-      navigation views.&nbsp;</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Click the tab of the navigation views and drag it to the 
-      right of the Outline tab.</P>
-    <P CLASS="Para"><img src="../images/Image60_tabs.png" alt="tabs" border="0" ></P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Once the cursor is to the right of the Outline tab and the 
-      cursor is a stack cursor release the mouse button.</P>
-    <P CLASS="Para">Observe the Navigator tab is now to the right of the Outline 
-      tab.</P>
-    <P CLASS="Para"><img src="../images/Image60_tabs2.png" alt="tabs" border="0" ></P>
-  </li>
-</ol>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39g.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39g.htm
deleted file mode 100644
index a9eafa8..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39g.htm
+++ /dev/null

@@ -1,30 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Maximizing</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Maximizing</h3>
-<P CLASS="Para">Sometimes it is useful to be able to maximize a view or editor. Maximizing both views and editors is easy.</P>
-<ul>
-  <li> To maximize a view, either double click on its tab or choose <b>Maximize</b> 
-    from the tab's popup menu.</li>
-  <li>
-    To maximize an editor double click on the editor tab or choose <b>Maximize</b> 
-    from the tab's popup menu.</li>
-</ul>
-<p CLASS="Para">Restoring a view to its original size is done in a similar
-manner (double click or choose <b>Restore</b> from the menu).</p>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40.htm
deleted file mode 100644
index e73658f..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Fast views</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Fast views</h2>
-<p CLASS="Head">Fast views are hidden views, which can be quickly made visible. 
-  They work the same as normal views, only when they are hidden they do not take 
-  up screen space on the Workbench window.&nbsp;</p>
-
-
-<P> This section we will explain how to convert the Navigator view into a fast 
-  view. </P>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40a.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40a.htm
deleted file mode 100644
index 16d05cb..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40a.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating fast views</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Creating fast views</h3>
-<p CLASS="Head">Fast views are hidden views, which can be quickly made visible. 
-  These instructions commence by creating a fast view from one of the navigation views 
-  and then explain how to use the view once it is a fast view.&nbsp;</p>
-<p CLASS="Head">There are two ways to create a fast view</p>
-<ul>
-  <li> Using drag and drop.</li>
-  <li> Using a menu operation available from the view System menu.</li>
-</ul>
-<p CLASS="Head">Create a fast view using drag and drop as follows.</p>
-<ol>
-  <li>
-    <P CLASS="Para"> In the Navigator view click on the title bar and drag it 
-      to the shortcut bar at the bottom left of the window.&nbsp;</P>
-  </li>
-  <li>
-    <P CLASS="Para"> Once over the shortcut bar, the cursor will change to a &quot;fast view&quot; 
-      cursor. Release the mouse button to drop the Navigator onto the shortcut 
-      bar. </P>
-<P CLASS="Para">The shortcut bar now includes a button for the Navigator fast view </P>
-<blockquote>
-<P CLASS="Para"><img src="../images/Image60_fast_view1.png" alt="Fast view" border="0" ></P>
-</blockquote>
-  </li>
-</ol>
-<P>To create a fast view using the second approach, start by popping up the context 
-  menu over the Navigator view's tab. From this menu, 
-  select <b>Fast View</b>. </P>
-
-
-<blockquote> 
-  <P><img src="../images/Image61_fast_options.png" alt="Navigator view menu" border="0"> 
-  </P>
-
-
-</blockquote>
-
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40b.htm
deleted file mode 100644
index 01bdac8..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40b.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working with fast views</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Working with fast views</h3>
-<p CLASS="Head">The Navigator has now been converted into a fast view. This section 
-  will demonstrate what can now be done with it.</p>
-<p CLASS="Head">Confirm that the shortcut bar at the bottom left of the window 
-  still has the Navigator view and looks like this:</p>
-<blockquote>
-  <p CLASS="Head"><img src="../images/Image60_fast_view1.png" alt="Fast view on shortcut bar" border="0" ></p>
-</blockquote>
-<ol>
-  <li> 
-    <P CLASS="Para">In the shortcut bar click on the Navigator fast view button.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Observe the Navigator view slides out from the left side of the window.&nbsp; 
-    </P>
-    <P CLASS="Para"> <img src="../images/Image61_nav_fast.png" alt="Navigator view" border="0" ></P>
-  </li>
-  <li> 
-    <p CLASS="Head">The Navigator fast view can be used as it would be normally.&nbsp;&nbsp;To 
-      resize a fast view, move the mouse to the right edge of the fast view where 
-      the cursor will change to a double-headed arrow. Then hold the left mouse 
-      button down as the mouse is moved. </p>
-  </li>
-  <li> 
-    <P CLASS="Para"> To hide the fast view simply click on another view or editor 
-      or click on the <b>Minimize</b> button on the fast view's toolbar </P>
-    <P CLASS="Para"> <img src="../images/Image61_fast_minimize.png" alt="Minimize fast icon" border="0" > 
-    </P>
-    <P CLASS="Para">&nbsp; </P>
-    <P CLASS="Para"><b>Note:</b> If a file is opened from the a navigation view 
-      fast view, the fast view will automatically hide itself to allow the file 
-      to be worked with.</P>
-  </li>
-</ol>
-<P>To convert a fast view back to a regular view either: </P>
-<ul>
-  <li>Choose <b>Fast View</b> from the context menu of the icon in the top left 
-    corner of the view. </li>
-  <li>Drag the fast view icon from the tool bar, and drop it somewhere in the 
-    Workbench window. </li>
-</ul>
-
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43.htm
deleted file mode 100644
index 04848ec..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Perspectives</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Perspectives</h2>
-<p class="Para" Type Label>A perspective defines the initial set and layout of
-views in the Workbench window. One or more perspectives can exist in a single
-Workbench window.&nbsp;&nbsp;</p>
-<p class="Para" Type Label>Perspectives can be opened in one of two ways:</p>
-<ul>
-  <li><p>In the same (existing) Workbench window.</p> </li>
-  <li><p>In a new Workbench window.</p></li> 
-</ul>
-<p class="Para" Type Label>Perspectives define visible action sets, which can 
-  be changed to customize a perspective. A perspective that is built in this manner 
-  can be saved, creating a custom perspective that can be opened again later.&nbsp;&nbsp;&nbsp;</p>
-<P CLASS="Para"> The Workbench window displays one or more perspectives. Each 
-  product determines initially what default perspective is displayed, in this 
-  example it is the Resource perspective. A perspective consists of views such 
-  as the Navigator as well as editors for working with resources. More than one 
-  Workbench window can be open at any given time.&nbsp; </P>
-<P CLASS="Para"> So far, only the Resource perspective (shown below) has been 
-  used in this tutorial. This section will explore how to open and work with other 
-  perspectives. </P>
-<P CLASS="Para"> A perspective provides a set of functionality aimed at accomplishing 
-  a specific type of task, or working with a specific type of resource.&nbsp;&nbsp; 
-</P>
-<P CLASS="Para">
-<img src="../images/Image1.png" alt="Eclipse Workbench" border="0" > </P>
-<P>&nbsp;</P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43b.htm
deleted file mode 100644
index 80b8fb0..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43b.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>New perspectives</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-New perspectives</h3>
-<p CLASS="Head">There are several ways to open a new perspective within
-this Workbench window:</p>
-<ul>
-  <li>
-    Using the Open Perspective button 
-    <img src="../images/Image70_shortcut2.png" alt="Open Perspectives" border="0" >
-    on the shortcut bar.</li>
-  <li>
-    Choosing a perspective from the <b>Window &gt; Open Perspective</b> menu.&nbsp;</li>
-</ul>
-<p>To open one by using the shortcut bar button:</p>
-<ol>
-  <li> 
-    <p CLASS="Para">Click on the Open Perspective button <img src="../images/Image70_shortcut2.png" alt="Open Perspectives" border="0" >.&nbsp;</p>
-  </li>
-  <li> 
-    <p CLASS="Head">A menu appears showing the same choices as shown on the <b>Window 
-      &gt; Open Perspective</b> menu. Choose <b>Other</b> from the menu.</p>
-    <blockquote> 
-      <p CLASS="Head"> <img src="../images/Image70_shortcut3.png" alt="Open Perspective Menu" border="0" ></p>
-    </blockquote>
-  </li>
-  <li> 
-    <p CLASS="Para">In the Select Perspective dialog choose <b>Debug</b> and click 
-      <b>OK</b>.</p>
-    <blockquote> 
-      <p CLASS="Para"> <img src="../images/Image70_select_pers.png" alt="Select Perspective" border="0" ></p></blockquote>
-    <p CLASS="Para">The Debug perspective is displayed.&nbsp;&nbsp;</p>
-  </li>
-  <li> 
-    <p CLASS="Para">There are several other interesting things to take note of.</p>
-    <ul>
-      <li> 
-        <p CLASS="Para">The title of the window now indicates that the Debug perspective 
-          is in use.</p></li>
-      <li> 
-        <p CLASS="Para">The shortcut bar contains several perspectives, the original 
-          Resource perspective, the new Debug perspective and a few others.&nbsp;The 
-          Debug perspective button is pressed in, indicating that it is the current 
-          perspective.</p></li>
-      <li> 
-        <p CLASS="Para">To display the full name of the perspective right click 
-          the perspective bar and check <strong>Show Text</strong>.<br>
-          <img src="../images/Image70_shortcut4.png" alt="Debug Perspective" border="0" ></p></li>
-    </ul>
-  </li>
-  <li> 
-    <p CLASS="Para">In the shortcut bar, click on the Resource perspective button. 
-      The Resource perspective is once again the current perspective. Notice that 
-      the set of views is different for each of the perspectives.&nbsp;</p>
-  </li>
-</ol>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43c.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43c.htm
deleted file mode 100644
index 268e127..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43c.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>New windows</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-New windows</h3>
-<p CLASS="Head">As well as opening a perspective inside the current Workbench 
-  window, new perspectives can also be opened in their own window.</p>
-<p CLASS="Head">By default, new perspectives are opened in the current window. 
-  This default behavior can be configured using <b>Window &gt; Preferences &gt; 
-  General &gt; Perspectives</b>.</p>
-<blockquote> 
-  <P>&nbsp;<img src="../images/Image71_pers_pref.png" alt="Perspective preferences"> 
-  </P>
-
-
-</blockquote>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43e.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43e.htm
deleted file mode 100644
index 0e2162d..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43e.htm
+++ /dev/null

@@ -1,88 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Saving perspectives</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Saving
-perspectives</h3>
-<P CLASS="Para">This tutorial has demonstrated how to add new views to the perspective, 
-  rearrange the views and convert views into fast views. The Workbench also allows 
-  this layout to be saved for future use.</P>
-<ol>
-  <li> 
-    <p CLASS="Para">In the shortcut bar click on the Resource perspective.&nbsp;The 
-      Resource perspective is now active.</p>
-  </li>
-  <li> 
-    <p CLASS="Para">Drag the Outline view and stack it with one of the navigation 
-      views.</p></li>
-  <li> 
-    <p CLASS="Para">Choose <b>Window &gt; Save Perspective As...</b></p>
-  </li>
-  <li> 
-    <p CLASS="Para">The Save Perspective As dialog allows for an existing perspective 
-      to be redefined or for a new perspective to be created.</p> 
-    <p CLASS="Para">Click <b>OK</b> to update the Resource perspective and <b>Yes</b> 
-      to the subsequent confirmation dialog. The new perspective layout will be 
-      used if the perspective is reset or if a new one is opened.</p>
-    <blockquote> 
-      <p CLASS="Para"><img src="../images/Image71_pers_save.png" alt="Saving Perspective" border="0" ></p>
-    </blockquote>
-  </li>
-  <li> 
-    <P CLASS="Para">In the Resource perspective move the Outline view so that 
-      it is now stacked with the Tasks view.</P>
-  </li>
-  <li> 
-    <p CLASS="Para">Choose <b>Window &gt; Reset Perspective</b>. Notice the Outline 
-      view is stacked with the navigation view. Originally when the Workbench 
-      was first started it was below the navigation view, but because the perspective 
-      was saved with the navigation view and Outline stacked, it now considers 
-      this its initial layout.&nbsp;&nbsp;</p>
-  </li>
-  <li> 
-    <P CLASS="Para">Choose <b>Window &gt; New Window</b> to open a second window 
-      showing the resource perspective. Observe that it uses the newly saved layout.&nbsp;</P>
-  </li>
-  <li> 
-    <P CLASS="Para">Close the second window.</P>
-  </li>
-</ol>
-<p CLASS="Para">While the Resource perspective has been changed, there is a way 
-  to get back the original layout. To reset the Resource perspective to its original 
-  layout:</p>
-<ol>
-  <li> 
-    <p CLASS="Para">Choose <b>Window &gt; Preferences</b>.</p>
-  </li>
-  <li> 
-    <p CLASS="Para">Expand <b>General</b> and select <b>Perspectives</b>.</p>
-  </li>
-  <li> 
-    <p CLASS="Para">Select <b>Resource (default) &gt; Make Default</b> and then 
-      click <b>OK</b>.</p> 
-    <blockquote> 
-      <p CLASS="Para"><img src="../images/Image71_pers_reset.png" alt="Reset Perspective" border="0"></p></blockquote>
-  </li>
-  <li> 
-    <p CLASS="Para">Any changes to the saved state of the perspective has now 
-      been undone. To update the current copy of the Resource perspective that 
-      is being worked with, also choose <b>Window &gt; Reset Perspective</b> from 
-      the Workbench's menu bar.&nbsp;</p>
-  </li>
-</ol>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43f.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43f.htm
deleted file mode 100644
index 540ff11..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43f.htm
+++ /dev/null

@@ -1,61 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Configuring perspectives</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Configuring
-perspectives</h3>
-<p CLASS="Para">In addition to configuring the layout of a perspective you can 
-  also control several other key aspects of a perspective. These include:</p>
-<ul>
-  <li> The <b>New</b> menu.</li>
-  <li> The <b>Window &gt; Open Perspective</b> menu.</li>
-  <li> The <b>Window &gt; Show View</b> menu.</li>
-  <li> Action sets that show up on the toolbar.</li>
-</ul>
-<p CLASS="Para">Try customizing one of these items.&nbsp;</p>
-<ol>
-  <li>
-        <p CLASS="Para">In the shortcut bar click on the Resource perspective.&nbsp;</p>
-      </li>
-  <li>
-        <p CLASS="Para">Select <b>Window &gt; Customize Perspective...</b></p></li>
-  <li>
-        
-    <p CLASS="Para">Select the <strong>Commands</strong> tab.&nbsp;</p>
-      </li>
-  <li>Check <b>Launch</b> and click <b>OK</b>.
-        <blockquote>
-          <p>
-          <img src="../images/Image71_pers_customize.png" alt="Customizing Perspective" border="0" ></p>
-        </blockquote>
-      </li>
-  <li>Observe that the toolbar now
-        includes buttons for debug/run launching.
-        
-    <blockquote> 
-      <p> <img src="../images/Image71_pers_rundebug.png" alt="Customized Perspective" border="0" ></p>
-        </blockquote>
-      </li>
-  <li>
-        
-    <p CLASS="Para">After experimenting with the other options on the Customize 
-      Perspective dialog, choose <b>Window &gt; Reset Perspective</b> to return 
-      the perspective to its original state.&nbsp; </p>
-      </li>
-</ol>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52.htm
deleted file mode 100644
index 4eb1af2..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Comparing</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Comparing</h2>
-<P CLASS="Para"> The Workbench allows for the comparison of multiple resources 
-  and for the presentation of the results in a special compare editor. </P>
-<P CLASS="Para"><b>Setup</b> </P>
-<P CLASS="Para">Before commencing with compare a few files must be created. This 
-  will also be a good time to recap some of the basic features that have already 
-  been introduced.</P>
-<ol>
-  <li> 
-    <p CLASS="Para">Start by selecting all of the projects in one of the navigation 
-      views and deleting them by using <b>Delete</b> on the pop-up menu.</p>
-  </li>
-  <li> 
-    <p CLASS="Para">Create a new simple project using <b>File &gt; New &gt; Project</b>. 
-      Be sure to give the project a distinct name by typing unique name as the 
-      name of the new project (for example, &quot;JaneQUserCompare&quot;). Do 
-      not use spaces or special characters in the project name.</p></li>
-  <li> 
-    <p CLASS="Para">Use the project's pop-up menu to create a file called file1.txt.</p>
-    <p CLASS="Para">In the editor for file1.txt type the following lines of text 
-      and save the file:</p>
-    <blockquote> 
-      <p CLASS="Para"><i>This is line 1.<br>
-        This is line 2.<br>
-        This is line 3.<br>
-        This is line 4.<br>
-        This is line 5.</i></p>
-    </blockquote>
-  </li>
-  <li> 
-    <p CLASS="Para">In one of the navigation views select file1.txt and use Ctrl+C 
-      to copy the file.</p></li>
-  <li> 
-    <p CLASS="Para">Use Ctrl+V (Paste) to create the copy. In the name conflict 
-      dialog which appears, rename the file to file2.txt.</p></li>
-</ol>
-<p>(On the Mac, use Command+C and Command+V.)</p>
-<P>There are now two identical files, file1.txt and file2.txt. </P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52c.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52c.htm
deleted file mode 100644
index 0340111..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52c.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Simple compare</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Simple compare</h3>
-<p CLASS="Head"> In one of the navigation views select file1.txt and file2.txt 
-  choose <b>Compare With &gt; Each Other</b> from the context menu.&nbsp;</p>
-<p CLASS="Head"> A dialog will appear indicating that the two files are the same.&nbsp;</p>
-<p CLASS="Head"><img src="../images/Image80_compare.png" alt="Compare popup" border="0" ></p>
-<p CLASS="Head">Edit file1.txt as follows:</p>
-<ul>
-  <li>
-    delete&nbsp; line 1&nbsp; &quot;<i>This is line 1.&quot;</i></li>
-  <li>
-    change line 3 to be &quot;This is a much better line
-    3.&quot;</li>
-  <li>
-    insert a line 4a (before line 5) that reads &quot;This is
-    line 4a and it is new&quot; </li>
-</ul>
-<p CLASS="Head">The file (file1.txt) should now read as follows:&nbsp; </p>
-<blockquote>
-  <p><i>This is line 2.<br>
-  This is a much better line 3.<br>
-  This is line 4.<br>
-  This is line 4a and it is new<br>
-  This is line 5.</i></p>
-</blockquote>
-<p>Save the contents of the file by choosing <b>File &gt; Save</b> (or pressing
-Ctrl+S).</p>
-<p>To compare the files, once again select file1.txt and file2.txt and choose 
-  <b>Compare With &gt; Each Other</b> in the navigation view context menu.</p>
-<p>A special compare editor opens. The next section will explain how to use this 
-  compare editor.</p>
-<blockquote> 
-  <P><img src="../images/Image80_compare_editor.png" alt="Compare Editor" border="0" > 
-  </P>
-
-
-</blockquote>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52d.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52d.htm
deleted file mode 100644
index e529475..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52d.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Understanding the comparison</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Understanding the comparison</h3>
-<p CLASS="Head">Comparing file1.txt and file2.txt resulted in the following
-compare editor. The left side shows the contents of file1.txt and the right side
-shows the contents of file2.txt. The lines connecting the left and right panes
-indicate the differences between the files.</p>
-<p CLASS="Head">If more room is needed to look at the comparison, the editor tab 
-  can be double clicked to maximize the editor.&nbsp;</p>
-<p CLASS="Head">
-<img src="../images/Image80_compare_editor2.png" alt="Compare editor" border="0" >&nbsp;&nbsp;</p>
-<p CLASS="Head"> The numbered changes on the left side of the difference editor 
-  are as follows:</p>
-<ul>
-  <li> Starting with the top line (in the left pane) the difference bar (in the 
-    area of the blue circle) indicates something is missing from the very top 
-    of the left file. Follow the difference band (see #1) to the right file. It 
-    contains &quot;This is line 1&quot; .</li>
-  <li> The next line &quot;This is line 2.&quot; is white indicating it matches 
-    the right file.</li>
-  <li> Moving onto the next line (colored in the background color), see that the 
-    left file and right file have different contents for this line (see #2).</li>
-  <li> The next line (This is line 4) is once again in white, so it can be skipped.</li>
-  <li> The next line exists in the left file&nbsp; but since it is in the background 
-    color its difference bar can be followed to the right (see #3) and notice 
-    that the right file does not contain the line (see red circle).</li>
-</ul>
-<p CLASS="Head">Initially the compare editor might seem a bit daunting but when 
-  simply working down the left side and focusing on the items marked as gray, 
-  and those items missing from the left side, it turns out not to be as tricky 
-  as it first seems.</p> 
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52e.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52e.htm
deleted file mode 100644
index 7a3b1d9..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52e.htm
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working with the comparison</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Working with the comparison</h3>
-<p CLASS="Head">Comparing file1.txt and file2.txt resulted in the following compare 
-  editor. This section demonstrates how to use the compare editor to resolve the 
-  differences between the two files.</p>
-<p>
-<img src="../images/Image80_compare_editor.png" alt="Compare editor" border="0" ></p>
-<p>There are two parts to the compare editor's local toolbar. Move to the next 
-  or previous change using the right group of local toolbar buttons.&nbsp;</p>
-<blockquote>
-<p>
-<img src="../images/Image80_compare_editor3.png" alt="Compare buttons" border="0" ></p>
-</blockquote>
-<ol>
-  <li>Click the Select Next Change button&nbsp; 
-  <img src="../images/Image80_compare_editor_next.png" alt="Compare editor next button" border="0" >.
-        Observe how it selects the next difference.</li>
-  <li>
-        <p CLASS="Para">Click Select Next
-        Change button a second time to go to the next change.&nbsp;</p>
-      </li>
-  <li>
-        <p CLASS="Para">Click the Select Previous Change
-        button.</p>
-      </li>
-</ol>
-<p>To merge changes from the left file to the right file and vice versa use the 
-  left group of local toolbar buttons. There are four types of merges that can 
-  be performed:</p>
-<ul>
-  <li>Copy whole document from left to right.&nbsp;</li>
-  <li>Copy whole document from right to left.</li>
-  <li>Copy current change from left to right.</li>
-  <li>Copy current change from right to left.</li>
-</ul>
-<p> Typically the copy whole document actions are used when the entire file on 
-  either the left or right can just be replaced by the contents of the other file.</p>
-<p> The Copy current change buttons allow a single change to be merged.&nbsp;&nbsp;</p>
-<ol>
-  <li>
-        <p CLASS="Para">Ensure that the second difference is selected (as shown
-        below):</p>
-        <p CLASS="Para">
-        <img src="../images/Image80_compare_change2.png" alt="Compare editor" border="0" ></p>
-        </li>
-  <li>
-        
-    <p CLASS="Para">Click&nbsp;<strong>Copy Current Change from Right to Left 
-      </strong><img src="../images/Image80_compare_rl.png" alt="Compare editor right to left button" border="0" >. 
-      Observe that the selected text from the right file is copied to the left 
-      file.</p> 
-    <p CLASS="Para"><img src="../images/Image80_compare_after.png" alt="Compare editor" border="0" ></p>
-      </li>
-  <li>
-        
-    <p CLASS="Para">Close the compare editor and choose <b>Yes</b> to save the 
-      changes. Alternatively, save the changes by choosing <b>File &gt; Save</b> 
-      (Ctrl+S).&nbsp;</p>
-      </li>
-</ol>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-55.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-55.htm
deleted file mode 100644
index 8ead832..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-55.htm
+++ /dev/null

@@ -1,72 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Local history</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Local history</h2>
-<P CLASS="Para"> Every time an editable file is saved in the Workbench, the Workbench 
-  updates the local history of that file and logs the changes that have been made. 
-  The local history of a file can then be accessed and a previously saved copy 
-  of the file can be reverted to, as long as the desired state is recent enough 
-  in the save history.</P>
-<ol>
-  <li>
-<P CLASS="Para">
-Create a new file named sampleFile.txt.</P>
-  </li>
-  <li>
-<P CLASS="Para">
-In the editor for sampleFile.txt modify the resource by adding the line
-&quot;change1&quot; and saving the file.</P>
-  </li>
-  <li>Repeat this by entering a new line &quot;change2&quot; and saving it again.
-  </li>
-  <li>Add
-a third line &quot;change3&quot; and save it again. </li>
-  <li>
-<P CLASS="Para">
-From the resource's context menu in one of the navigation views, select <b>Replace With &gt; Local History</b>.</P>
-  </li>
-  <li>
-<P CLASS="Para">The Replace from Local History dialog opens and shows the 
-previous local history&nbsp; of the file.</P>
-<P CLASS="Para">&nbsp;<img src="../images/Image81_local.png" alt="Local history" border="0" ></P>
-    <P CLASS="Para">The left pane of the dialog contains the Workbench's copy 
-      of the file. The figure above shows that the Workbench contains the copy 
-      with all 3 lines - the same copy that is currently shown in the editor area 
-      of the Workbench.&nbsp;<br>
-&nbsp;</P>
-<P CLASS="Para">The first item in the local history (see above) contains the
-last saved copy of the file. This is the one with only two lines of text. The
-final entry in the tree is the first copy of the file.<br>
-&nbsp;</P>
-    <P CLASS="Para">The bottom area of the dialog displays the differences between 
-      the Workbench file and the specific copy of the file selected in the local 
-      history.&nbsp;&nbsp;</P>
-  </li>
-  <li>Select the first item (shown above) in the local history. The right pane should
-show one line of text.&nbsp; </li>
-  <li>
-<P CLASS="Para">Click <b>Replace</b>. This replaces the Workbench's copy of
-sampleFile.txt with the chosen local history item.</P>
-  </li>
-  <li>
-<P CLASS="Para">Observe that the sampleFile.txt editor now contains two
-lines.&nbsp;</P>
-  </li>
-</ol>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-55b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-55b.htm
deleted file mode 100644
index a6d2244..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-55b.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Exiting the Workbench</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Exiting the Workbench</h2>
-<P CLASS="Para"> Each time the Workbench is exited, the Workbench is automatically 
-  saved, including all open perspectives and windows. The next time the Workbench 
-  is reopened, it will appear exactly as it was when it was last closed.</P>
-<p> To exit the Workbench, select <b>File &gt; Exit</b> from the menu bar or close 
-  the workbench with the window close button (x). When the latter option is used 
-  a prompt will ask if the user really wishes to exit the workbench. </p>
-<p><strong>Note: </strong>This dialog also presents an option to turn off the 
-  prompting. To turn it back on, select <strong>Window &gt; Preferences</strong> 
-  from the main Workbench menu bar, in the Preferences Dialog select <strong>General 
-  &gt; Startup and Shutdown</strong> and check Confirm exit when closing last 
-  window.</p>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-60_team.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-60_team.htm
deleted file mode 100644
index ae8bb25..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-60_team.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Team CVS tutorial</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Team CVS tutorial</H1>
-<P>This chapter will explain how to use the CVS team capabilities built into the 
-  Workbench. The steps in this chapter are team oriented; it will be difficult 
-  to complete these tutorials if others are not simultaneously working through 
-  this chapter. </P>
-
-
-<P>Instructions will be given explaining how to work on a project and then commit 
-  changes to the repository for others on the team to use. By continuing to work 
-  on the project alongside other users, this section will demonstrate how to commit 
-  resources that other users may be simultaneously working on, and how to update 
-  a workspace with changes others make in the project. </P>
-<P>Remember, before getting started, entice at least one coworker into working 
-  through these steps as well. </P>
-
-
-<UL CLASS="UnorderedList">
-
-</UL>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-60a_setup.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-60a_setup.htm
deleted file mode 100644
index 8d303d1..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-60a_setup.htm
+++ /dev/null

@@ -1,27 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Setting up a CVS repository</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2> Setting up a CVS repository</h2>
-<P CLASS="Para">
-A repository is a persistent store that coordinates multi-user access to the
-resources being developed by a team. The Workbench comes with CVS support
-built-in. The CVS server is available at <a href="https://www.cvshome.org" target="_blank">https://www.cvshome.org</a>.&nbsp;</P>
-<P CLASS="Para"> Refer to this site for information on how to install and configure 
-  a CVS repository including user access and passwords.</P>
-<p>In order to continue with this tutorial, access to a CVS repository is required.</p>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61c_offline.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61c_offline.htm
deleted file mode 100644
index e2ff132..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61c_offline.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Starting offline</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h2>Starting offline</h2>
-  
-<P CLASS="Para">The team CVS tutorial will start by working offline and creating 
-  a simple project. Once the project is created, instructions will be given explaining 
-  how to commit it to the repository.&nbsp;</P>
-<ol>
-  <li> 
-    <P CLASS="Para">Create a new &quot;Simple&quot; project using <b>File &gt; 
-      New &gt; Project</b>. Use a unique name as the project name (e.g. JanesTeamProject).&nbsp; 
-    </P>
-  </li>
-  <li>Create a folder named folder1. </li>
-  <li>Create two text files (.txt) in folder1 called&nbsp; file1.txt and file2.txt. 
-    Their contents should be as follows: 
-    <p>file1.txt</p>
-    <blockquote> 
-      <p><i>This is the contents<br>
-        of file 1.</i></p>
-    </blockquote>
-    <p>file2.txt</p>
-    <blockquote> 
-      <p><i>File2 is a small file&nbsp;&nbsp;<br>
-        with simple text.</i></p>
-    </blockquote>
-    <p>The navigation view should now appear as follows:</p>
-    <blockquote> 
-      <p> <img src="../images/Image82_nav.png" alt="Navigator view" border="0"></p>
-    </blockquote>
-  </li>
-</ol>
-
-
-<P>The project can be continued within this mode but unless the project is committed 
-  into the repository, others on the team will be unable to work on the project 
-  as well. </P>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61d_repoloca.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61d_repoloca.htm
deleted file mode 100644
index 9269c31..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61d_repoloca.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Sharing the project</title>
-</head>
-<body bgcolor="#ffffff">
-<h2> Sharing the project</h2>
-<div class="Subtopic">Now that a project has been created in the
-workspace you can make it available to other Team members. To do this
-the following steps will have to occur:<br>
-<br>
-<ol>
-  <li>Create a CVS location identifying the team's shared CVS
-repository.<br>
-    <br>
-  </li>
-  <li>Share the project with the CVS location and commit the changes.<br>
-  </li>
-</ol>
-</div>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61d_repolocb.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61d_repolocb.htm
deleted file mode 100644
index 13164ee..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61d_repolocb.htm
+++ /dev/null

@@ -1,102 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Specifying a repository location</title>
-</head>
-<body bgcolor="#ffffff">
-<h3>
-Specifying a repository location</h3>
-<p class="Head">Before it is possible to share the project with other
-users an available repository must first be specified.</p>
-<ol>
-  <li>Open the CVS Repository Exploring perspective. The top left view
-shows all of the CVS repositories that are currently being worked with.
-As can be seen, the view is empty, meaning a repository still needs to
-be specified.<br>
-    <br>
-  </li>
-  <li>In the context menu of the CVS Repositories view choose <b>New
-&gt;&nbsp;Repository Location</b>.
-    <blockquote>
-      <blockquote>
-        <p> <img  border="0"
- alt="CVS Repositories view" src="../images/Image82_repo_new.png"></p>
-      </blockquote>
-    </blockquote>
-  </li>
-  <li>In the CVS Repository Location wizard, the location of the
-repository and the login information needs to be filled in. Assistance
-from a repository administrator may be required in order to fill in the
-necessary information.
-    <blockquote>
-      <p> <img  border="0"
- alt="Add CVS Repository dialog" src="../images/Image82_repo_new3.png"></p>
-    </blockquote>
-  </li>
-  <li>
-    <p class="Para"> In the <b> Host </b> field, type the address of
-the host (for example, "teamsamples.com").<br>
-    <br>
-    </p>
-  </li>
-  <li>
-    <p class="Para"> In the <b> Repository path </b> field, type the
-path for the repository at the host address (for example,
-"/home/cvsroot/repositoryName").<br>
-    <br>
-    </p>
-  </li>
-  <li>
-    <p class="Para">In the <b> User </b> field, type the user name
-under which to connect.<br>
-    <br>
-    </p>
-  </li>
-  <li>
-    <p class="Para">In the <b>Password</b> field, type the password.<br>
-    <br>
-    </p>
-  </li>
-  <li>
-    <p class="Para"> In the <b> Connection type </b> field, select
-the type of CVS connection for the repository (The default is pserver).<br>
-    <br>
-    </p>
-  </li>
-  <li>
-    <p class="Para"> Leave<b> Use Default Port</b> enabled. <br>
-    <br>
-    </p>
-  </li>
-  <li>By default the <b>Validate Connection on Finish<b> option </b></b>is
-checked. <br>
-    <br>
-  </li>
-  <li>
-    <p class="Para"> Click <b>Finish</b> when done.</p>
-    <p class="Para"> Since <b>Validate location on finish </b>was
-checked,<b> </b>the wizard will now attempt to validate the
-information by connecting to the repository. In doing so it may prompt
-for a password. <strong>Note: </strong>The repository connection is
-only used to validate the information.<br>
-    <br>
-    </p>
-  </li>
-  <li>
-    <p class="Para">Observe that the CVS Repositories view now shows
-the new repository location.</p>
-    <p class="Para"> <img  border="0"
- alt="CVS Repositories view" src="../images/Image82_repo_view1.png"></p>
-  </li>
-</ol>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61e_whatisloc.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61e_whatisloc.htm
deleted file mode 100644
index b003295..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61e_whatisloc.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Repository locations</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Repository locations</h3>
-<DIV CLASS="Subtopic">
-
-  <p CLASS="Para">Now that a new repository location has been added to the CVS 
-    Repositories view, the following will explain what a repository location is 
-    or, more importantly, what it isn't.</p>
-  <p CLASS="Para">A repository location is not an actual live connection. Instead, 
-    it is a description of where the repository is located. At a later time, when 
-    instructions are given explaining how to commit work to the repository or 
-    update with work done by others, the Workbench will create a connection based 
-    on this location information. Connections will be opened and closed as required 
-    when performing CVS team operations, and those connections will be based on 
-    the information provided in the repository location. </p>
-  <p CLASS="Para">When disconnected from the network the CVS Repositories view 
-    continues to display the list of known repository locations. In addition, 
-    the projects themselves will still know the repository location they are associated 
-    with.</p> 
-</DIV>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61f_syncproject.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61f_syncproject.htm
deleted file mode 100644
index fbd5304..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61f_syncproject.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Sharing a project</title>
-</head>
-<body bgcolor="#ffffff">
-<h3> Sharing a project</h3>
-<p class="Para"> Now that a project has been created and a repository
-location has been specified, the project can be made available to other
-team members.</p>
-<ol>
-  <li>
-    <p class="Para"> In one of the navigation views select the project
-JanesTeamProject.</p>
-  </li>
-  <li>
-    <p class="Para">From the project's context menu choose <b>Team
-&gt; Share Project</b>. If more than one repository provider is
-installed, select <strong>CVS </strong>and select <strong>Next</strong>.</p>
-  </li>
-  <li>
-    <p class="Para"> In the sharing wizard page, select the location
-that was previously created.</p>
-    <blockquote>
-      <p><img  border="0"
- alt="Set Project Sharing" src="../images/Image82_repo_sync1.png"></p>
-    </blockquote>
-  </li>
-  <li>The next page will ask you the module name to create on the
-server. Simply use the default value and use the name of the project
-you are sharing. Click <span style="font-weight: bold;">Next</span>.<br>
-    <br>
-    <div style="text-align: left; margin-left: 40px;"><img src="../images/Image82_repo_sync2.png">
-<br>
-    </div>
-    <br>
-  </li>
-  <li>The next page will allow you to see the files that are going to
-be shared with your team. The arrows with the plus sign show that the
-files are new outgoing additions. They have never existed on the server
-yet. <br>
-    <br>
-    <div style="margin-left: 40px;"><img src="../images/Image82_repo_team.png">
-</div>
-  </li>
-  <li>Press <span style="font-weight: bold;">Finish</span> and you will be prompted 
-    to commit the files. Enter a commit comment to describe the commit you are 
-    making. You can enter anything you like. Press <strong>Finish</strong> when 
-    you are done and the files will be committed.<br>
-  </li>
-  <li>Now you have shared the project and all the files have been
-committed to the CVS repository. Others can now see your files!<br>
-  </li>
-</ol>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-62b_sync.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-62b_sync.htm
deleted file mode 100644
index 7f49933..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-62b_sync.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Synchronize view</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Synchronize view</h3>
-<P>The Synchronize view provides a single place where both the changes that have 
-  been made locally, and changes others have made and committed to the repository 
-  can be viewed. In addition to providing a combined <i>local + remote</i> resource 
-  tree, it allows changes to be made in the repository (commit), and allows the 
-  user to access the changes others have made (update). </P>
-
-<P>When looking at the Synchronize view in more detail the first thing to notice 
-  is that the title of the view indicates that the &quot;Outgoing Mode&quot; is 
-  active and the Outgoing Mode button (see A) is pressed in. Changes that have 
-  been made locally can be committed to the repository using Outgoing Mode. By 
-  default, if the Repository is synchronized with and the repository has no changes, 
-  outgoing mode is automatically displayed to allow the user to quickly commit 
-  changes. </P>
-<blockquote>
-  <P><img src="../images/Image82_repo_syncview.png" alt="Synchronize - Release Mode" border="0" > 
-  </P>
-
-
-</blockquote>
-<P CLASS="Para">&nbsp;</P>
-
-<P>In &quot;Outgoing Mode&quot; the top area (#1) shows all of the resources that
-need to be committed.
-</P>
-
-
-<P>The bottom area (#2 and #3) is the text compare area that was introduced in 
-  the basic tutorial. By double-clicking on a resource in the <b>Structured Compare</b> 
-  list the lower area displays the differences between what is in the Workbench 
-  (#2) versus what is currently in the repository (#3). </P>
-
-
-<P>Switch between outgoing mode and other synchronization modes with Toolbar buttons 
-  (A). </P>
-
-
-<p>Merge changes between a file and the repository copy of the file with the lower 
-  toolbar (B).</p>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-62c_releasing.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-62c_releasing.htm
deleted file mode 100644
index 5afa6b2..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-62c_releasing.htm
+++ /dev/null

@@ -1,73 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Committing</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Committing</h3>
-<P>Now that the Synchronize view has been described here's how files can be committed 
-  to the repository. </P>
-
-
-<ol>
-  <li> 
-    <P CLASS="Para"> In the <b>Structure Compare</b> list select file1.txt</P>
-    . 
-    <blockquote> 
-      <P CLASS="Para"> <img src="../images/Image82_repo_release.png" alt="Structure Compare" border="0" ></P>
-    </blockquote>
-  </li>
-  <li> 
-    <P CLASS="Para"> Pop-up the menu and choose <b>Commit</b>. Click <b>OK</b> 
-      when asked to add and to supply a commit comment.</P>
-  </li>
-  <li>Observe that file1.txt is no longer in the list. 
-    <blockquote> 
-      <p><img src="../images/Image82_repo_release2.png" alt="Structure Compare" border="0" ></p>
-    </blockquote>
-    <p>In addition to committing individual resources the project can also be 
-      selected and all of the changes in the project can be committed.</p>
-  </li>
-  <li>Select JanesTeamProject. </li>
-  <li>Choose <b>Commit</b> from the project's context menu and type in &quot;my 
-    first project&quot; when prompted for a commit comment. 
-    <p>Observe that the remaining resources in the project are committed and the 
-      structure compare list is now empty.&nbsp;</p>
-  </li>
-  <li>Click on the Resource perspective button in the shortcut bar (at the far 
-    left of the window). 
-    <blockquote> 
-      <blockquote> 
-        <p><img src="../images/Image82_repo_res.png" alt="Resource Perspective" border="0" ></p>
-      </blockquote>
-    </blockquote>
-  </li>
-  <li>In the navigator create a third file called file3.txt with the following 
-    contents: 
-    <blockquote> 
-      <p><i>This is the brief contents<br>
-        of file 3.</i></p>
-    </blockquote>
-  </li>
-  <li>Select the project (JanesTeamProject) and choose <b>Team &gt; Synchronize 
-    with Repository</b> again from the context menu. 
-    <p>When the Synchronize view opens, there is only one change, the new file3.txt.</p>
-    <blockquote> 
-      <p><img src="../images/Image82_repo_rel5.png" alt="Outgoing mode" border="0" ></p>
-    </blockquote>
-  </li>
-  <li>Select file3.txt, and choose <b>Commit</b> from the context menu. </li>
-</ol>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64a_another.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64a_another.htm
deleted file mode 100644
index 8591836..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64a_another.htm
+++ /dev/null

@@ -1,61 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>Working with another user</title>
-</head>
-<body bgcolor="#ffffff">
-<h2>
-Working with another user</h2>
-<p>Instructions were given explaining how to create a project and
-commit it to the repository. First a repository location was specified.
-Next the project was shared with that location and the HEAD branch and
-the resources were added then committed. </p>
-<p>The repository currently contains the project and the two files
-that were committed (file1.txt and file2.txt). </p>
-<p>It's time to find that coworker (let's call him Fred) to work
-through some steps with you (for the remainder your name is Jane). This
-section will demonstrate how two
-people can work on the same project and simultaneously commit changes
-to the repository. Specifically, the following actions will be taken: </p>
-<ul>
-  <li>Fred will import the project to his Workbench</li>
-  <li>Fred will make changes to file1.txt and file2.txt.</li>
-  <li>You will update these new changes and also add a new file called
-file3.txt.</li>
-  <li>Fred will make more changes to some files while you change the
-same files. Fred will release his changes first.<br>
-  </li>
-  <li>You will have to resolve the conflicts between files that you
-both changed.&nbsp;</li>
-</ul>
-Here is some terminology commonly used to describe changes:<br>
-<table border="0" cellspacing="0" cellpadding="3" width="568">
-  <tbody>
-    <tr>
-      <td valign="top" width="71" align="left"> <b>incoming</b> </td>
-      <td valign="top" width="481" align="left">Changes that are in the
-repository, which you have not yet updated to. </td>
-    </tr>
-    <tr>
-      <td valign="top" width="71" align="left"> <b>outgoing</b> </td>
-      <td valign="top" width="481" align="left">Changes that you are
-committing. </td>
-    </tr>
-    <tr>
-      <td valign="top" width="71" align="left"> <b>conflict</b> </td>
-      <td valign="top" width="481" align="left">Both you and the
-repository have modifications to the same resource. </td>
-    </tr>
-  </tbody>
-</table>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64b_fredadd.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64b_fredadd.htm
deleted file mode 100644
index d6494c8..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64b_fredadd.htm
+++ /dev/null

@@ -1,75 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>Checking out a project</title>
-</head>
-<body bgcolor="#ffffff">
-<h3> Checking out a project</h3>
-<p class="Para">Coworker Fred has several tasks in front of him:&nbsp;</p>
-<ul>
-  <li>Fred will import the project that Jane committed to the CVS
-repository into his Workbench.</li>
-  <li>Fred will make changes to file1.txt and file2.txt.</li>
-  <li>Fred will synchronize and commit his outgoing changes to the two
-files.</li>
-</ul>
-<p>Fred's first step is to import the project into his workspace as
-follows:</p>
-<ol>
-  <li>Run the import wizard via the <span style="font-weight: bold;">File
-&gt; Import</span> menu item.<br>
-    <br>
-    <div style="margin-left: 40px;"><img src="../images/Image82_import_project_fred.png" alt="Screenshot of Import type selection">
-<br>
-    </div>
-    <br>
-  </li>
-  <li>Select the <span style="font-weight: bold;">Checkout Projects
-from CVS</span> item and press <span style="font-weight: bold;">Next</span>.<br>
-    <br>
-  </li>
-  <li>Create a repository location as described when Jane <a
- href="qs-61d_repolocb.htm">created a repository</a>.<br>
-    <br>
-  </li>
-  <li>On the next page select the "Use an existing module" radio button
-and wait while the repository is contacted.<br>
-    <br>
-    <div style="margin-left: 40px;"><img src="../images/Image82_import2_project_fred.png" alt="Screenshot of CVS module selection page">
-<br>
-    <br>
-    </div>
-  </li>
-  <li>From the list of available projects, select <span
- style="font-weight: bold;">JanesTeamProject </span>and press <span
- style="font-weight: bold;">Finish</span>. A progress dialog will
-appear showing the progress of the import operation.<br>
-    <br>
-    <div style="margin-left: 40px;"><img src="../images/Image82_import3_project_fred.png" alt="Screenshot of progress dialog">
-<br>
-    <br>
-    </div>
-  </li>
-  <li>Open one of the navigation views and observe&nbsp;that it now includes
-the project <span style="font-weight: bold;">JanesTeamProject</span>.
-Notice that there are CVS decorators indicating the file revisions, the
-repository name, and the file types.<br>
-    <br>
-    <div style="margin-left: 40px;"><img src="../images/Image82_import4_project_fred.png" alt="Screenshot of Fred's Navigator after checkout">
-<br>
-    </div>
-    <br>
-    <br>
-  </li>
-</ol>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64b_fredmod.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64b_fredmod.htm
deleted file mode 100644
index e41e594..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64b_fredmod.htm
+++ /dev/null

@@ -1,87 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Another user making changes</title>
-</head>
-<body bgcolor="#ffffff">
-<h3>
-Another user making changes</h3>
-<p class="Para">Now that Fred has the project in his Workbench he needs
-to modify several of the files and synchronize with the repository in
-order to commit them.</p>
-<ul>
-  <li>Fred will make changes to file1.txt and file2.txt</li>
-  <li>Fred will synchronize and commit his outgoing changes to the two files.</li>
-</ul>
-<p class="Para">Fred should proceed as follows:</p>
-<ol>
-  <li>Modify file1.txt as follows
-    <p>Original contents:</p>
-    <blockquote>
-      <p><i>This is the contents<br>
-of file 1.</i></p>
-    </blockquote>
-    <p>New contents (changes shown in bold):</p>
-    <blockquote>
-      <p><i>This is the contents<br>
-      <b>Fred-update&nbsp; </b><br>
-of file 1.</i></p>
-    </blockquote>
-  </li>
-  <li>Modify file2.txt as follows
-    <p>Original contents:</p>
-    <blockquote>
-      <p><i>File2 is a small file<br>
-with simple text.</i></p>
-    </blockquote>
-    <p>New contents (changes shown in bold):</p>
-    <blockquote>
-      <p><i>File2 is a (<b>Fred was here) </b>small file<br>
-with simple text. </i></p>
-    </blockquote>
-  </li>
-  <li>Observe that the Navigator updates the CVS state of a resource.
-Notice
-that the two files which Fred has changed are preceded by "&gt;".
-    <blockquote>
-      <p class="Para"><img src="../images/Image83_fred_verson.png" alt="Navigator View">
-&nbsp;</p>
-    </blockquote>
-  </li>
-  <li>To commit his changes to the repository Fred can either:
-    <ul>
-      <li>Select the two files and choose <b>Team &gt; Synchronize
-with Repository</b> or,</li>
-      <li>Select the project and choose <b>Team &gt; Synchronize with
-Repository</b></li>
-    </ul>
-    <p>Often choosing the project is the easiest thing to do. Let's do
-that. Select the project and choose <b>Team &gt; Synchronize with
-Repository</b> from its context menu. When you are asked to switch to
-the Team Synchronizing perspective select <span
- style="font-weight: bold;">Yes</span>.<br>
-    <br>
-    <img src="../images/Image83_fred_verson2.png">
-<br>
-    <br>
-    </p>
-  </li>
-  <li>When the Synchronize View opens Fred can browse the changes he
-made and at the end should commit his changes to
-file1.txt and file2.txt by selecting JanesTeamProject in the
-Synchronize View and from the context menu select <span
- style="font-weight: bold;">Commit</span>. You will have to enter a
-commit comment before committing the changes.<br>
-  </li>
-</ol>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_mod.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_mod.htm
deleted file mode 100644
index 54eb3a8..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_mod.htm
+++ /dev/null

@@ -1,94 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Making our own changes</title>
-</head>
-<body bgcolor="#ffffff">
-<h3>
-Making our own changes</h3>
-<p class="Para">Fred has made several changes to file1.txt and
-file2.txt and committed them to the repository. In this section
-additional changes will be made and then synchronized with the
-repository. When synchronizing, expect to see the changes made in this
-section along with changes that have been made by Fred.</p>
-<ol>
-  <li>Add file3.txt as follows 
-    <p>New contents:(changes shown in bold)</p>
-    <blockquote> 
-      <p><i>This is the brief contents<br>
-        of file<b> </b>3</i></p>
-    </blockquote>
-  </li>
-  <li>Observe that the Navigator displays the CVS state of a resources. Notice 
-    that the new file added by Jane is preceded by "&gt;". 
-    <blockquote> 
-      <p class="Para"><img src="../images/Image83_jane1.png" alt="Navigator View">
-</p>
-    </blockquote>
-  </li>
-  <li> 
-    <p class="Para">Select the project <span style="font-weight: bold;">JanesTeamProject</span> 
-      and from the project's context menu, select <b>Team &gt; Synchronize with 
-      Repository</b>. When asked to switch perspective select <span
- style="font-weight: bold;">Yes</span>. The Team Synchronizing perspective will 
-      open and you will see the files you have changed appear in the Synchronize 
-      View. Double click on file1.txt and you should see a compare editor open:</p>
-	  <p class="Para"><img src="../images/Image83_jane-sync.png"></p>
-  </li>
-  <li>There are a couple of other things worth observing. First, the icon next 
-    to file1.txt (in the structured compare area) indicates that file1.txt has 
-    an incoming change. This means a change was released to the server which you 
-    need to take. Looking at file1.txt we can see the text that Fred has added 
-    to the file. Also, notice at the bottom of the window, in the status line, 
-    there are arrows with numbers beside them. These show the number of files 
-    you have incoming, outgoing, and in conflict. The first number beside a file 
-    is the revision you have in the workspace, and the other is the revision on 
-    the server when you last synchronized.<br>
-    <br>
-  </li>
-  <li>Normally you should update the changes made by others, then test your workspace 
-    with the changes, then commit your changes once you are sure that the new 
-    changes by others didn't break anything in your workspace. <br>
-    <br>
-  </li>
-  <li>Before deciding to accept Fred's changes you may want to find out why he 
-    made the changes. Select file1.txt and from the context menu select <span style="font-weight: bold;">Show 
-    in Resource History</span>.<br>
-    <br>
-    <img src="../images/Image83_jane-history.png" > <br>
-    <br>
-  </li>
-  <li>The row starting with a <span style="font-weight: bold;">*</span> indicates 
-    that this is the current revision loaded. In this case you can see the comment 
-    made by Fred when he released revision 1.2. <br>
-    <span style="font-weight: bold;">Trick</span>: You can select the 'link with 
-    editor' toolbar button in the history view to have the history automatically 
-    update when a new editor is opened. This allows for quick browsing of comments.<br>
-    <br>
-  </li>
-  <li>To update simply select <span style="font-weight: bold;">JanesTeamProject</span> 
-    in the Synchronize View and from the context menu select <span
- style="font-weight: bold;">Update</span>.<br>
-    <br>
-  </li>
-  <li>The Synchronize View will update to reflect the fact that file1.txt and 
-    file2.txt are no longer out-of-sync with the repository. You should only have 
-    file3.txt visible now.<br>
-    <br>
-  </li>
-  <li>Next you can commit file3.txt.<br>
-    <p><br>
-    </p>
-  </li>
-</ol>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_sync2.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_sync2.htm
deleted file mode 100644
index 5cbe444..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_sync2.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Updating</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3> Updating</h3>
-<p CLASS="Para"> The Synchronize view will be used to update the local resource 
-  to the latest contents in the repository and to commit any changes.</p>
-<p CLASS="Para">&nbsp;</p>
-<ol>
-  <li>Confirm that the Synchronize view is in Incoming Mode (#1). If it is not 
-    then press the Incoming Mode button on the local toolbar (#2). 
-    <p><img src="../images/Image83_jane5a.png" alt="Incoming mode" border="0" ></p>
-  </li>
-  <li>Open file1.txt (the incoming change) by double-clicking. The comparison 
-    viewer shows that&nbsp;the repository copy of file1.txt has a new line inserted 
-    (Fred-update). 
-    <p><img src="../images/Image83_jane4.png" alt="Text Compare" border="0" ></p></li>
-  <li> 
-    <p CLASS="Para"> From the context menu of file1.txt choose <b>Update</b>. 
-      This will cause the Workbench to be updated with the repository copy of 
-      file1.txt. </p>
-  </li>
-  <li>Select file2.txt. The comparison viewer shows that&nbsp;the repository copy 
-    of file1.txt and the local copy of file1.txt have both had the exact same 
-    line modified.&nbsp; 
-    <p><img src="../images/Image83_jane6a.png" alt="Text Compare" border="0" ></p></li>
-  <li>If the change seems suspicious, find out some more information about it. 
-    To do this, first figure out who made the change and why. 
-    <p>In the Structure compare pane of the Synchronize view select file2.txt 
-      and choose <b>Show in Resource History</b> from the context menu.</p>
-    <p><img src="../images/Image84_reshist.png" alt="Resource History" border="0" ></p>
-  </li>
-  <li>In the Resource History view (see above) there is a * next to version 1.1. 
-    This indicates 1.1 is currently in the Workbench. It also shows that the repository 
-    contains 1.2 of file2.txt.&nbsp;The author of 1.2 is Fred. Looks like it's 
-    time to ask Fred why he was changing file2.txt.&nbsp; 
-    <p>If Fred had entered a meaningful description when releasing his changes, 
-      these descriptions would have appeared in the comment field of the Resource 
-      History view thereby providing some insight into the intent of the change.</p> 
-  </li>
-  <li>The four copy buttons can now be used to help merge in conflicting changes 
-    made to the repository. 
-    <p> For now assume that Fred's change turns out to be the right one.</p> 
-    <p>Select file2.txt and choose <b>Override and Update</b> from the context 
-      menu. When asked to confirm the replacement choose <b>Yes</b>.</p> </li>
-  <li>The Update mode no longer has any remaining incoming or conflicting changes.&nbsp; 
-    <p>The status bar shows that there is still one remaining outgoing change 
-      to deal with.</p>
-    <blockquote> 
-      <p><img src="../images/Image84_status.png" alt="Status bar" border="0" ></p>
-    </blockquote>
-  </li>
-</ol>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_sync3_rel.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_sync3_rel.htm
deleted file mode 100644
index 3c1b30f..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_sync3_rel.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Committing</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3> Committing</h3>
-<p CLASS="Para"> The Outgoing Mode of the Synchronize view will now be used to 
-  commit the one remaining outgoing change.&nbsp;</p>
-<ol>
-  <li>Place the Synchronize view into outgoing mode by clicking on the Outgoing 
-    Mode button (#1) and confirming that the title of the view now indicates Outgoing 
-    Mode (#2). 
-    <p><img src="../images/Image84_relmode.png" alt="Outgoing mode" border="0" ></p>
-      </li>
-  <li>Open file3.txt (the outgoing change) by double-clicking.&nbsp; </li>
-  <li>The comparison viewer shows that&nbsp;the local copy of file3.txt has a 
-    change to the second line.&nbsp; The repository copy is shown in the right 
-    pane. 
-    <p><img src="../images/Image84_jane.png" alt="Text compare" border="0" ></p></li>
-  <li>From the context menu of file3.txt choose <b>Commit</b>. 
-      Be sure to enter a meaningful description when prompted for one.&nbsp; 
-    <p>The Workbench copy is now committed into the repository.</p>
-    </li>
-  <li>
-    <p CLASS="Para"> At this point Fred may want to synchronize with the repository 
-      to update his workspace with the changes just committed.</p>
-  </li>
-</ol>
-<P>By making simultaneous changes to the same project you have successfully collaborated 
-  with Fred. The Synchronize view and CVS Resource History view allowed you to 
-  determine the specific changes each user was making and to quickly stay on top 
-  of the ongoing changes being committed into the repository. </P>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_sync_view.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_sync_view.htm
deleted file mode 100644
index b976c81..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_sync_view.htm
+++ /dev/null

@@ -1,100 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Working with conflicting changes</title>
-</head>
-<body style="background-color: rgb(255, 255, 255);">
-<h3>Working with conflicting changes<br>
-</h3>
-<p class="Para">There are cases where two users are editing the same files and 
-  when the second to commit to the repository tries to commit their changes, the 
-  repository won't allow the commit to succeed because of the conflict. Let's 
-  simulate this by making Fred and Jane change the same files.<br>
-</p>
-<ol>
-  <li>In Fred's workspace open one of the navigation views and edit file1.txt. Make
-the text the following:<br>
-    <br style="font-style: italic;">
-    <span style="font-style: italic;">Fred line 1</span><br
- style="font-style: italic;">
-    <span style="font-style: italic;">This is the contents</span><br
- style="font-style: italic;">
-    <span style="font-style: italic;">Fred-update</span><br
- style="font-style: italic;">
-    <span style="font-style: italic;">of file 1.<br>
-    <br>
-    </span></li>
-  <li><span style="font-style: italic;"><span
- style="font-style: italic;"></span></span>Fred will also change
-file2.txt with the following change:<br>
-    <br>
-    <span style="font-style: italic;">File2 is a (Fred was here again)
-small file</span><br style="font-style: italic;">
-    <span style="font-style: italic;">with simple text.</span><br>
-    <br>
-  </li>
-  <li>Fred committed his changes to the repository.<br>
-    <br>
-  </li>
-  <li>Next, at the same time Jane was making changes to file1.txt. She
-added the following line to the end of the file:<br>
-    <br>
-    <span style="font-style: italic;">This is the contents</span><br
- style="font-style: italic;">
-    <span style="font-style: italic;">Fred-update</span><br
- style="font-style: italic;">
-    <span style="font-style: italic;">of file 1.</span><br
- style="font-style: italic;">
-    <span style="font-style: italic;">Jane was at the end<br>
-    <br>
-    </span></li>
-  <li>And finally, Jane changed file2.txt to the following:<br>
-    <br>
-    <span style="font-style: italic;">File2 is a (Jane was here) small
-file</span><br style="font-style: italic;">
-    <span style="font-style: italic;">with simple text.<br>
-    <br>
-    </span></li>
-  <li>When Jane was finished making changes she synchronized the
-project and found the following appear in the Synchronize View:<br>
-    <br>
-    <img src="../images/Image83_jane3_conflict.png">
-<br>
-    <br>
-  </li>
-  <li>Both file1.txt and file2.txt show with a red icon indicating that they have 
-    conflicting changes. You can't commit the files until the conflicts are resolved. 
-    Click on file1.txt and notice that Fred and Jane made changes to two different 
-    parts of the file. In this case, Jane can simply update the file and the lines 
-    added by Fred will be merged into Jane's local file. Select file1.txt and 
-    from the context menu select <strong>Update</strong>.<br>
-    <br>
-  </li>
-  <li>Next, double on file2.txt to see the conflict. In this case you can see 
-    that both Jane and Fred changed the same line. For this type of conflicting 
-    change a regular update can't resolve the conflict. Here you have three options 
-    (with the command to use in brackets): accept the changes from Fred (<span style="font-weight: bold;">Override 
-    and Update</span>), ignore Fred's changes (<span style="font-weight: bold;">Mark 
-    as Merged</span>), or manually merge the files within the compare editor.<br>
-    <br>
-    <img src="../images/Image83_jane3_conflict2.png">
-<br>
-    <br>
-  </li>
-  <li>For this example, let's say Jane updated file1.txt and selected
-override and update for file2.txt. After the operations are run the
-conflicts turn into outgoing changes. Jane can review the changes and
-commit them.<br>
-  </li>
-</ol>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-70_replace.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-70_replace.htm
deleted file mode 100644
index 7fc298e..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-70_replace.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Replacing</title>
-</head>
-<body bgcolor="#ffffff">
-<h3> Replacing</h3>
-<p class="Head">Suppose after further reflection, it becomes apparent
-that the revision of file1.txt that was just received is incorrect and
-an earlier revision is required. A Workbench resource can be replaced
-with an earlier revision of the resource from the repository. To roll
-back to an earlier revision:</p>
-<ol>
-  <li> 
-    <p class="Head"> In one of the navigation views select the file1.txt.<br>
-      <br>
-    </p>
-  </li>
-  <li> 
-    <p class="Para"> From the file's context menu, select <b>Replace With &gt; 
-      Revision.<br>
-      <br>
-      </b></p>
-  </li>
-  <li> 
-    <p class="Para"> In the replace with revision Compare editor that opens, choose 
-      the original (bottom) revision and, from the pop-up menu choose <b>Get Contents</b>.<br>
-      <br>
-    </p>
-  </li>
-  <li> 
-    <p>Observe that the navigation view updates to show the CVS state of a resource. 
-      Notice that the modified file is preceded by "&gt;" (see #1) indicating 
-      that file1.txt has changed (by replacing it with the earlier version). <br>
-      <br>
-    </p>
-    <p><img src="../images/Image84_replace2.png"  alt="File selection"> <br>
-      <br>
-    </p>
-  </li>
-  <li>Now assume that this older revision is not as good as it initially seemed 
-    and in fact the revision in the repository is better after all.&nbsp; 
-    <p>Instead of choosing <b>Team &gt; Synchronize with Repository</b>, choose 
-      <b>Replace With &gt; Latest from Repository.</b></p>
-    <p>Observe that file1.txt is updated to be the contents from the repository, 
-      and that the leading indicator "&gt;" has been removed since it is now the 
-      same revision as the repository. </p>
-  </li>
-</ol>
-<p>Now that how to synchronize with the repository, replace with a revision or 
-  replace with the latest from the repository has been explained, these revisions/versions 
-  can also be compared with in a similar manner by choosing the <b>Compare With</b> 
-  menu operation from a resource's context menu in the navigation view. </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-74_review.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-74_review.htm
deleted file mode 100644
index 8a6c319..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-74_review.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>A quick review</title>
-</head>
-<body bgcolor="#ffffff">
-<h3>
-A quick review</h3>
-<p class="Para"> Here are some of the more important but subtle issues
-associated with working in a repository . </p>
-<ul>
-  <li>The project was tagged as a version by versioning the project as
-it appeared in the Workbench. For this reason it is important to
-synchronize the project with the repository (that is the HEAD or the
-branch that is being worked in) prior to versioning it. Otherwise
-another user may have committed interesting changes to the project
-which have yet to be updated in the Workbench. By proceeding to version
-the project without updating, it will be versioned without these
-changes.&nbsp;</li>
-  <li>The repository contains all projects in the repository.
-Individual users pick which projects they are interested in and check
-them out into the workspace. From that point on they are synchronizing
-those projects (only) with respect to the repository.</li>
-  <li>The repository represents a large in-progress collection of all
-known projects. From the repository's perspective, everything in HEAD
-or on a branch is always open for change.</li>
-  <li>The act of versioning a project effectively snapshots it and
-places it into the Versions section of the repository, however the
-repository branches are still open for change.</li>
-  <li>It is important to first update to changes made to the
-repository, retest with those changes and the soon to be committed
-changes and then commit the changes.&nbsp; By first taking the latest
-changes in the branch, and retesting, it helps to ensure that the
-changes about to be committed will actually work with the current state
-of the branch.</li>
-  <li>Each project is associated with a specific repository. Different
-projects can be associated with different repositories that may be on
-completely different servers.&nbsp; </li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-74_version.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-74_version.htm
deleted file mode 100644
index ea0c154..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-74_version.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Versioning a project</title>
-</head>
-<body bgcolor="#ffffff">
-<h3> Versioning a project</h3>
-<p class="Para"> Now that the project is complete it is time to version
-it. While committing the file resources the repository automatically
-assigned them version numbers, or to be more accurate "revision
-numbers". As the files were committed the only information supplied was
-a commit comment.&nbsp;</p>
-<p class="Para">To version a project proceed as follows:</p>
-<ol>
-  <li> 
-    <p class="Para">Select the project <span style="font-weight: bold;">JanesTeamProject</span>.</p>
-  </li>
-  <li>In one of the navigation views select <b>Team &gt; Tag as Version...</b></li>
-  <li>When the Tag Resources dialog opens enter the version name A1 and click 
-    <b>OK</b>.</li>
-  <li>Select the CVS Repositories view.</li>
-  <li>Expand <b>Versions</b>, and <span style="font-weight: bold;">JanesTeamProject</span>. 
-    Observe that under JanesTeamProject there is now a version of this project 
-    whose version number is A1. Looking closely at the contents of folder1 note 
-    that the version numbers of the individual files match the version numbers 
-    in the Workbench. 
-    <p>&nbsp;</p>
-  </li>
-</ol>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-80_ant.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-80_ant.htm
deleted file mode 100644
index 2f46ece..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-80_ant.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Ant &amp; external tools tutorial</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Ant &amp; external tools tutorial</H1>
-<P CLASS="Para">This chapter covers Eclipse's external tools framework, and its 
-  integration with <a href="http://ant.apache.org/">Ant</a>, the build tool from 
-  the <a href="http://www.apache.org/">Apache Software Foundation</a>. For more 
-  information on Ant, see the <a href="http://ant.apache.org/manual/index.html">Apache 
-  Ant manual</a> for documentation. This chapter assumes a basic knowledge of 
-  Ant.</P>
-
-
-<P CLASS="Para">This chapter is split into three main sections. First, the basics 
-  of working with Ant buildfiles in Eclipse are covered. Next, several Eclipse 
-  use cases will be worked through, in which Ant buildfiles can make life a little 
-  easier. Finally, the entire external tools framework and how to use non-Ant 
-  tools is considered.</P>
-
-
-<UL CLASS="UnorderedList">
-
-</UL>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-81_basics.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-81_basics.htm
deleted file mode 100644
index 864a479..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-81_basics.htm
+++ /dev/null

@@ -1,23 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Eclipse Ant basics</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Eclipse Ant basics</h2>
-  
-<P CLASS="Para">This section covers the basics of working with Ant buildfiles 
-  in Eclipse. Creating, editing, configuring and reusing Ant buildfiles will all 
-  be discussed in this section.</P>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-82_create.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-82_create.htm
deleted file mode 100644
index d68cf8f..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-82_create.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating Ant buildfiles</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Creating Ant buildfiles</h3>
-  
-<P CLASS="Para"> Ant buildfiles are just text files, so the most straightforward 
-  way to create an Ant buildfile in Eclipse is:</P>
-<ol>
-  <li><b>File &gt; New &gt; File</b>.</li>
-  <li>Enter any name for the file, but make sure it has a .xml extension.</li>
-  <li>Click <b>Finish</b>.</li>
-</ol>
-<p>As long as the file has a .xml extension, Eclipse will consider it to be a 
-  possible Ant buildfile, and will enable Ant-related actions when it is selected.
-  Until a file has ant buildfile content, you will need to open it using <b>Open With &gt; Ant Editor</b>.</p>
-<p>As will be demonstrated in a later section, an Ant buildfile can be created 
-  for an Eclipse plug-in that contains predefined targets that are useful for deploying 
-  the plug-in.</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-83_edit.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-83_edit.htm
deleted file mode 100644
index 87efba7..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-83_edit.htm
+++ /dev/null

@@ -1,96 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Editing Ant buildfiles</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Editing Ant buildfiles</h3>
-<P CLASS="Para">Because Ant buildfiles are simple text files, any text editor 
-  can be used to edit them. But there are several advantages to using the Eclipse 
-  Ant editor, including syntax coloring, content assist, navigation, occurrence marking and an outline view. To 
-  get familiar with the Eclipse Ant editor, create a simple Ant buildfile using 
-  this editor.</P>
-<ol>
-  <li>Create an Ant buildfile called HelloWorld.xml.</li>
-  <li>Open the Ant editor on the file by selecting <b>Open With &gt; Ant Editor</b> 
-    from the file's context menu. <br>
-    <strong>Note:</strong> The default editor for a .xml file is a simple text 
-    editor until it has buildfile content, but this can be changed in the <b>Window &gt; Preferences &gt; General 
-    &gt; File Associations</b>. </li>
-  <li>Enter the following content in the editor: <br>
-    <br>
-    <p> &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;</p>
-    
-    <p>&lt;project name=&quot;Hello World&quot; default=&quot;Hello&quot; basedir=&quot;.&quot;&gt;</p>
-    <blockquote> 
-      &lt;property name=&quot;HelloText&quot; value=&quot;Hello&quot;/&gt;
-      <p>&lt;target name=&quot;Hello&quot;&gt;</p>
-      <blockquote> 
-        &lt;echo&gt;${HelloText}&lt;/echo&gt;
-      </blockquote>
-    </blockquote>
-    <blockquote> 
-      &lt;/target&gt;
-    </blockquote>
-    <p>&lt;/project&gt; </p>
-   
-    <p><img src="../images/first_anteditor.png" alt="HelloWorld.xml file content" border="0" ></p>
-  </li>
-  <li>Notice the syntax coloring for property values.</li>
-  <li>Begin to enter a second target by typing '&lt;tar', then hit <strong>Ctrl-Space</strong>
-    to activate content assist. A list of valid completions is presented. Select the &lt;target&gt; completion and 
-    notice that the editor inserts both the opening and closing tags and leaves 
-    the cursor positioned to enter attributes for this tag.</li>
-  <li>Name this target 'World'.</li>
-  <li>Enter an 'echo' task for this target similar to that for the Hello target, 
-    but change the text to '${WorldText}'.</li> 
-    <li>Add a dependency on the 'World' target from the 'Hello' target. Place the cursor after the definition of the name attribute, hit <strong>Ctrl-Space</strong>
-    and select the depends attribute completion. Hit <strong>Ctrl-Space</strong> again to get the completion for the other target 'World' in the buildfile.</li>
-    <li>Save the buildfile contents.</li>
-    <li>The full content will now be:
-    <br>
-    <p> &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;</p>
-    <br>
-    <p>&lt;project name=&quot;Hello World&quot; default=&quot;Hello&quot; basedir=&quot;.&quot;&gt;</p>
-    <blockquote> 
-      &lt;property name=&quot;HelloText&quot; value=&quot;Hello&quot;/&gt;<br>
-      &lt;property name=&quot;WorldText&quot; value=&quot;World&quot;/&gt;
-      <p>&lt;target name=&quot;Hello&quot;&gt;</p>
-      <blockquote> 
-        &lt;echo&gt;${HelloText}&lt;/echo&gt;<br>
-      </blockquote>
-      <p>&lt;/target&gt;</p>
-    </blockquote>
-     <blockquote> 
-      <p>&lt;target name=&quot;World&quot;&gt;</p>
-      <blockquote> 
-        &lt;echo&gt;${WorldText}&lt;/echo&gt;<br>
-      </blockquote>
-      <p>&lt;/target&gt;</p>
-    </blockquote>
-    <p>&lt;/project&gt; </p></li>
-  <li>Save the changes to HelloWorld.xml.</li>
-  <li>Make the Outline view visible and notice that there are entries for each 
-    property and each target. In addition, each task under a target has an entry.<br>
-    <img src="../images/outline_hello.png" alt="Outline view for an Ant buildfile" border="0" ></li>
-  <li>Clicking on an entry in the Outline view will scroll the editor to that 
-    entry. In addition, when the Outline view has focus, typing a character will 
-    move the selection in the Outline view to the next visible entry beginning 
-    with that character.</li>
-  <li>Position the cursor just past the end of one of the '&lt;target&gt;' tags, 
-    type '&lt;tar', then hit Ctrl-Space to activate content assist. Notice that 
-    now the only valid completion is the 'tar' tag. This is because the Ant editor 
-    knows that nested targets are not allowed.
-    <img src="../images/Image602_tar_assist.png" alt="Code assist in Ant editor" border="0"> 
-  </li>
-  <li>Close the editor and do not save changes.</li>
-</ol>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-84_run_ant.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-84_run_ant.htm
deleted file mode 100644
index 5a14500..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-84_run_ant.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Running Ant buildfiles</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Running Ant buildfiles</h3>
-  
-<P CLASS="Para">Any file with a .xml extension can be run as an Ant buildfile. 
-  Of course, not all such files really are Ant buildfiles, but no harm is done 
-  if an attempt is made to mistakenly run a non-Ant .xml file as an Ant buildfile.</P>
-<P CLASS="Para">In this section, the basic mechanisms for running Ant buildfiles 
-  in Eclipse will be covered, using the HelloWorld.xml file created in the last 
-  section.</P>
-<ol>
-  <li>Select HelloWorld.xml in one of the navigation views and choose <b>Run As 
-    &gt; Ant Build... </b> from its context menu.</li>
-  <li>A launch configuration dialog is opened on a launch configuration for this Ant buildfile.
-    <p><img src="../images/ant_run_dialog.png"  alt="Run Ant dialog" border="0"></p>
-  </li>
-  <li>This dialog allows the configuration of many aspects of the way an Ant 
-    buildfile is run, but for now concentrate on the <b>Targets</b> tab which 
-    allows the selection of which Ant targets to run and their order. Select both 
-    targets and leave the order as the default. </li>
-  <li>Click <b>Run</b>.</li>
-  <li>The Ant buildfile is run, and the output is sent to the Console view.</li>
-</ol>
-<p>Fortunately, if the buildfile is run so that the Hello target is executed first 
-  and other times so that the World target is first, the dialog does not need 
-  to be brought up each time nor does the ordering need to be changed.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-85_ant_configs.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-85_ant_configs.htm
deleted file mode 100644
index 7e28ee0..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-85_ant_configs.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Saving &amp; Reusing Ant options</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Saving &amp; Reusing Ant options</h3>
-  
-<P CLASS="Para">When we ran the HelloWorld.xml Ant buildfile in the last section, 
-  the choice of targets, along with all other options in the Run Ant dialog were 
-  saved in an entity called a 'launch configuration'. Launch configurations contain 
-  all details necessary to run a single Ant buildfile in a particular way. It is 
-  perfectly valid to have multiple launch configurations associated with a single 
-  Ant buildfile. So, in addition to the launch configuration that was created in 
-  the last step, specifying that our HelloWorld.xml buildfile should execute the 
-  targets Hello &amp; World in that order, we could create a second launch configuration 
-  for this same buildfile specifying the same targets but in the reverse order. So 
-  far so good. But the really nice thing about launch configurations is that now 
-  you can quickly run your Ant buildfile in either configuration by simply specifying 
-  the corresponding launch configuration.</P>
-<ol>
-  <li>From the Workbench toolbar, select <b>Run &gt; External Tools &gt; External Tools...</b>.</li>
-  <li>The External Tools dialog opens and presents a choice of launch configurations 
-    to view and edit. The launch configuration we created when we ran the HelloWorld.xml 
-    buildfile is selected in the tree at the left, and the tabs on the right show 
-    the options for this launch configuration.<br>
-    <img src="../images/et_dialog.png" alt="External tools dialog" border="0" > 
-  </li>
-  <li>At the top of the dialog, change the Name to 'Hello World' and <b>Apply</b> 
-    the change.</li>
-  <li>In the tree at left, bring up on the context menu on the selected launch 
-    configuration and choose <b>Duplicate</b>. A copy of the launch configuration 
-    for the Hello World buildfile is created, '(1)' is appended to the name, and 
-    the new launch configuration is selected in the tree.</li>
-  <li>Rename the new configuration to 'World Hello'.</li>
-  <li>In the <b>Targets</b> tab, click the <b>Order...</b> button, change the 
-    order of the targets so that the World target executes first, and <b>Apply</b> 
-    the change.</li>
-  <li>Click <b>Run</b>.</li>
-  <li>As before, the HelloWorld.xml buildfile runs and sends its output to the 
-    Console view. This time however, because the targets were reversed, the output 
-    is reversed as well.</li>
-  <li>Go back to the External Tools drop down in the toolbar. <br>
-    <img src="../images/et_dropdown.png" alt="External tools drop-down menu" border="0" ><br>
-    Notice now that there are two entries in the history, one for Hello World 
-    and one for World Hello. In order to rerun the Ant buildfile so that it outputs 
-    Hello World, just select this launch configuration in the history. To rerun 
-    the launch configuration that outputs World Hello, select this configuration 
-    in the history.<br>
-    <strong>Note</strong>: The history is ordered so that the most frequently 
-    run configurations are at the top of the dropdown.</li>
-</ol>
-<p>This concludes our quick look at the basics of Ant integration in Eclipse. 
-  In the next chapters, we consider several real-world use cases for running Ant 
-  buildfiles inside Eclipse.</p>
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-85a_ant_view.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-85a_ant_view.htm
deleted file mode 100644
index b066cec..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-85a_ant_view.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Using the Ant view</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Using the Ant view</h3>
-  
-<P CLASS="Para">Eclipse provides a standard view, the Ant view, that lets you 
-  work with your Ant buildfiles. This view is tree-structured, showing Ant buildfiles 
-  as top-level entries and targets &amp; internal targets as children. The main 
-  advantage of this view is that you can work with all of your Ant buildfiles 
-  in one place, as opposed to hunting them down in one of the navigation views.</P>
-<ol>
-  <li>Open the Ant view from the workbench menu by selecting <b>Window &gt; Show 
-    View &gt; Ant</b>.</li>
-  <li>By default, the Ant view is empty. There are three ways to add Ant buildfiles 
-    to this view: 
-    <ul>
-      <li>Click <strong>Add Buildfile<img src="../images/image618-add-ant.png" alt="Ant view" border="0" ></strong>. 
-        This brings up a dialog in which you explicitly select those Ant buildfiles 
-        you want to add</li>
-      <li>Click <strong>Add Buildfiles with Search<img src="../images/image618-add-ant-search.png" alt="Ant view" border="0" ></strong>. 
-        This brings up a search dialog in which you can specify a filename pattern 
-        for your Ant buildfiles and search within the entire workspace or a specified 
-        working set.<br></li>
-        <li>Drag and drop buildfiles from other views to the Ant view.<br>
-        <br>
-        Once added to the Ant view, Ant buildfile entries remain in the view across 
-        workbench invocations until explicitly removed or the associated project is closed.</li>
-    </ul>
-  </li>
-  <li>Click <strong>Add Buildfiles with Search</strong>. Suppose you only remember 
-    that the buildfile you want to work with starts with 'H'. Enter 'H*.xml' for 
-    the buildfile name. Make sure Workspace is selected for the scope, then click 
-    Search. The HelloWorld.xml file is found and placed in the Ant view.</li>
-  <li>Expand the top-level entry to see the default target Hello, and the internal 
-    target World.<br>
-    <img src="../images/ant_view.png" alt="Ant view" border="0" > 
-  </li>
-  <li>Select the World internal target and click <strong>Run the Selected Target <img src="../images/image618-ant-run.png" alt="Ant view" border="0" ></strong>. 
-    Notice that just the World target gets executed. </li>
-  <li>Select the top-level HelloWorld buildfile and click <strong>Run the Default 
-    Target of the Selected Buildfile <img src="../images/image618-ant-run.png" alt="Ant view" border="0" ></strong>. Notice that just the default target, 
-    Hello, gets executed.</li>
-  <li>To edit your buildfile, bring up the context menu on the HelloWorld file 
-    and select <b>Open With &gt; Ant Editor</b>.</li>
-  <li>To edit the default launch configuration, select <strong>Run As > Ant Build...</strong> from 
-    the context menu.</li>
-  <li>The Run Ant launch configuration dialog appears. Here you can modify the way in which the buildfile 
-    is run from the Ant view.</li>
-  <li>Select the HelloWorld file, then click the Remove button. The buildfile 
-    is removed from the view.<br>
-    <strong>Note</strong>: This does not delete the file from the workspace.</li>
-</ol>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-86_use_cases.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-86_use_cases.htm
deleted file mode 100644
index f01141a..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-86_use_cases.htm
+++ /dev/null

@@ -1,27 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Use cases for Ant in Eclipse</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Use cases for Ant in Eclipse</h2>
-  
-<P CLASS="Para">Now that we've seen how to work with Ant buildfiles in Eclipse, 
-  let's look at two ways that Ant buildfiles can be useful in Eclipse.</P>
-<ul>
-  <li>Deploying Eclipse plug-ins</li>
-  <li>Building projects</li>
-</ul>
-<p>We'll start by using an Ant buildfile to handle various aspects of deploying 
-  Eclipse plug-ins.</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-87_plugin_deploy.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-87_plugin_deploy.htm
deleted file mode 100644
index 1a6ab69..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-87_plugin_deploy.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Deploying Eclipse plug-ins</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Deploying Eclipse plug-ins</h3>
-  
-<P CLASS="Para">The first use of Ant within Eclipse discussed here will be as 
-  a plug-in deployment tool. When developing Eclipse plug-ins, it's frequently 
-  handy to build the jar files for your plug-in and test them as part of an Eclipse 
-  install. The Ant buildfile we'll look at in the next section will do this and 
-  much more.</P>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-88_create_plugin.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-88_create_plugin.htm
deleted file mode 100644
index 34224cf..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-88_create_plugin.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating a HelloWorld plug-in</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Creating a HelloWorld plug-in</h3>
-<P CLASS="Para">To work through this example, we need to create a simple 'Hello 
-  World' Eclipse plug-in. Creating Eclipse plug-ins is covered in more detail elsewhere 
-  in this documentation, so we will just create a simple HelloWorld plug-in as 
-  follows:</P>
-<ol>
-  <li> 
-    <P CLASS="Para">Create a new plug-in project by menuing to <b>File &gt; New &gt; Other...</b></P>
-  </li>
-  <li>Select <b>Plug-in Development</b> in the left pane, and <b>Plug-in Project</b> in 
-    the right and click <b>Next</b>.</li>
-  <li>Enter a name for your project, then click <b>Next</b>. </li>
-  <li>On the next page, accept all defaults and click <b>Next</b>.</li>
-  <li>Make sure <b>Create a plug-in project using one of the templates </b>is 
-    selected, then select <b>Hello, World</b> from the list below and click <b>Next</b>.</li>
-  <li>Accept all the defaults on this page and click <b>Finish</b>.</li>
-</ol>
-<p>Now that we have a plug-in project, we can create a build.xml file for it to 
-  manage plug-in deployment.</p>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-89_generate_buildxml.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-89_generate_buildxml.htm
deleted file mode 100644
index d404d62..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-89_generate_buildxml.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Generating the build.xml file</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Generating the build.xml file</h3>
-  
-<P CLASS="Para">Open one of the navigation views and locate your new plug-in project.</P>
-<ol>
-  <li>Select the file 'plugin.xml' underneath your new project and right-click 
-    <b>PDE Tools &gt; Create Ant Build File</b>.</li>
-  <li>A new file, 'build.xml' will be created underneath your project.</li>
-  <li>Open the Ant editor on the build.xml file by double clicking it in one of 
-    the navigation views. Notice that for this file, the Ant editor is the default 
-    editor. This is because by default, there is a file association in the general 
-    preferences associating files named 'build.xml' with the Ant editor. <br>
-    <img src="../images/Image607_buildxml.png" alt="default build.xml file" border="0" ></li>
-</ol>
-<p>The build.xml file is a default Ant buildfile with many targets useful for deploying 
-  your plug-in. For example, there are individual targets to build all necessary 
-  jars for your plug-in, create a .zip file containing everything in your plug-in, 
-  cleanup any .zip files that may have been created and so on. </p>
-<p>Now that we have the build.xml file, we will use it to build a .jar file for 
-  our plug-in.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-90_build_jar.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-90_build_jar.htm
deleted file mode 100644
index 6ef824d..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-90_build_jar.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Building a .jar file for the plug-in</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Building a .jar file for the plug-in</h3>
-  
-<P CLASS="Para">Now we are ready to use the build.xml Ant buildfile that was created 
-  in the last section:</P>
-<ol>
-  <li>Select the build.xml file in one of the navigation views and choose <b>Run 
-    &gt; External Tools </b> from the context menu.</li>
-  <li>In the dialog, the Targets tab should be visible. Make sure that 'build.jars' 
-    is the only item in the list selected.</li>
-  <li>Switch to the <b>Refresh</b> tab. The options on this tab control if and 
-    how the workspace looks for new, changed and deleted resources after the buildfile 
-    finishes execution. Because refreshing can be an expensive operation, you 
-    should refresh the smallest subset of the workspace necessary for your buildfile.</li>
-  <li>Check <b>Refresh resources upon completion</b>, then select <b>The project 
-    containing the selected resource</b>.<br>
-    <img src="../images/Image606_refresh_tab.png" alt="Refresh tab in Run Ant dialog" border="0" > 
-  </li>
-  <li>Click <b>Run</b>.</li>
-  <li>The Ant buildfile runs, executing the build.jars target. Output from the 
-    buildfile is visible in the Console view.</li>
-  <li>When the buildfile finishes, notice that there is a new .jar file under 
-    your project containing the two class files that comprise your plug-in. If 
-    we had chosen not to refresh the project, the .jar file would still have been 
-    created, but we would not see it in one of the navigation views.</li>
-</ol>
-<p>We've run the default target for the build.xml Ant buildfile, but there are many 
-  other targets and options to be explored.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-91_build_options.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-91_build_options.htm
deleted file mode 100644
index d16b6bc..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-91_build_options.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>More plug-in deployment options</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>More plug-in deployment options</h3>
-  
-<P CLASS="Para">Now that we've run the default target for our build.xml buildfile, 
-  it's time to explore some more options. </P>
-<P CLASS="Para">As can be seen in the Outline view, the default build.xml Ant 
-  buildfile has a number of targets.<br>
-  <img src="../images/Image608_buildxml_outline.png" alt="Outline view of default build.xml file" border="0" > 
-</P>
-<P CLASS="Para">Solid green circles denote targets, while internal targets are 
-  represented by hollow green circles. The following are the useful top-level 
-  targets:</P>
-<ul>
-  <li><b>build.update.jar</b> This target builds jars for the plug-in, then zips 
-    them into a form suitable for use with the Eclipse Update Manager.</li>
-  <li><b>HelloWorldPlugin.jar</b> This target does the work of the building jars 
-    for the plug-in.</li>
-  <li><b>build.jars</b> This is the default target we ran in the last section. 
-    It defers to the HelloWorldPlugin.jar target to do its work.</li>
-  <li><b>clean</b> This target deletes all zips, jars and temporary directories 
-    that may have been created by other targets in this buildfile.</li>
-  <li><b>zip.plugin</b> This target builds executable and source jars, then zips 
-    everything into a single archive.</li>
-</ul>
-<p>Remember that this build.xml file is simply the <i>default</i> deployment buildfile 
-  for an Eclipse plug-in. There will be times when you will want/have to modify 
-  this buildfile to handle your particular projects. For example, if you have a directory 
-  that contains resources necessary for your plug-in, you will want to update 
-  the build.xml file to include this directory in the jars and zips it creates.</p>
-<p>This completes our look at using Ant buildfiles to deploy Eclipse plug-ins. The 
-  key points to remember are that you can easily create a default deployment buildfile 
-  for a plug-in that contains many useful targets, and that while this default 
-  buildfile is useful, you may have to modify it to suit your needs.</p>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-92_project_builders.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-92_project_builders.htm
deleted file mode 100644
index ef29067..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-92_project_builders.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Ant buildfiles as project builders</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Ant buildfiles as project builders</h3>
-  
-<P CLASS="Para">Our second practical example of using Ant buildfiles in Eclipse 
-  is a 'project builder'. This is an Ant buildfile that has been designated to 
-  run whenever a project is built. The uses for such a buildfile are many:</P>
-<ul>
-  <li>Generate a .jar file containing class files from your project</li>
-  <li>Perform some type of pre or post build processing on source or binary files 
-    in your project. For example: 
-    <ul>
-      <li>Pre-processing source files to instrument them for performance analysis</li>
-      <li>Obfuscating binary files to prevent reverse engineering</li>
-    </ul>
-  </li>
-  <li>Copy class files to some location (for instance, on a network)</li>
-</ul>
-<p>For this example, we will create an Ant buildfile that creates a .jar archive 
-  of the class files in a project. Note that this is similar to the example in 
-  the last chapter, in which we used an Ant buildfile to generate .jar files for 
-  an Eclipse plug-in. This example differs in that it works for any Eclipse project, 
-  whether or not it is also an Eclipse plug-in. </p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-93_project_builder.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-93_project_builder.htm
deleted file mode 100644
index 8288aba..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-93_project_builder.htm
+++ /dev/null

@@ -1,85 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating a project builder Ant buildfile</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Creating a project builder Ant buildfile</h3>
-<P CLASS="Para">To see how project builders work, we will create a simple project 
-  with a single source file and an Ant buildfile that jars up the single class file. 
-  Though this example uses Java, it should be noted that project builders are 
-  available for all projects, Java or otherwise.</P>
-<ol>
-  <li>Create a Java project named 'HW'.</li>
-  <li>Create a Java source file named 'HelloWorld' with a main method.</li>
-  <li>Put a single 'System.out.println()' statement in the main method, and make 
-    it print a greeting of your choice.</li>
-  <li>Save changes.</li>
-  <li>Create a file named 'projectBuilder.xml', open the Ant editor on it, enter 
-    the following content, and save changes.<br>
-  </li>
-  <p><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt;<br>
-  &lt;project name="HW.makejar" default="makejar" basedir="."&gt; 
-  <blockquote>&lt;target name ="makejar" description="Create a jar for the HW 
-    project"&gt;</blockquote>
-  <blockquote> 
-    <blockquote>&lt;jar jarfile="HelloWorld.jar" includes="*.class" basedir="."/&gt;</blockquote>
-  </blockquote>
-  <blockquote>&lt;/target&gt;</blockquote>
-  &lt;/project&gt; </code></p> 
-  <li>In one of the navigation views, select the HW project and choose <b>Properties</b> 
-    from its context menu.</li>
-  <li>In the project properties dialog, select <b>Builders</b>, then click <b>New...</b>. 
-  </li>
-  <li>In the <strong>Choose configuration type</strong> dialog, select <strong>Ant 
-    build</strong>, and click <b>OK</b>. </li>
-  <li>The <strong>External Tools</strong> dialog appears. Set the name to 'Makejar'. 
-    In the Main tab, click the <strong>Buildfile</strong> <b>Browse Workspace...</b> 
-    and set the <b>Location</b> to be the projectBuilder.xml buildfile created 
-    above. Then click the <strong>Base Directory</strong> <b>Browse Workspace...</b> 
-    and set the Base Directory to be the HW project.<br>
-    <img src="../images/Image611_et_main_tab.png" alt="Main tab of External tools dialog" border="0" > 
-  </li>
-  <li>In the <b>Refresh</b> tab, we want to be sure that when our HelloWorld.jar 
-    is created, we see it in Eclipse. By default, no refreshing is done when a 
-    project builder finishes running, so check <b>Refresh resource upon completion</b>, 
-    then select <b>The project containing the selected resource</b> in the list 
-    of scope variables. Because refreshing can be expensive, you should in general 
-    refresh the smallest entity that contains all resources that will be affected 
-    by your buildfile. <br>
-    <img src="../images/Image612_et_refresh_tab.png" alt="Refresh tab of External tools dialog" border="0" > 
-  </li>
-  <li>In the <b>Targets</b> tab, the default target should be selected.</li>
-  <li>In the <b>Build Options</b> tab, you can specify when this project builder 
-    is executed. By default, this is set to <strong>After a &quot;Clean&quot; 
-    </strong>and <strong>During Manual Builds</strong>. Running your project builder 
-    during auto builds is possible, though not recommended because of performance 
-    concerns.<br>
-    <img src="../images/Image610_et_options_tab.png" alt="Build options tab of External tools dialog" border="0" > 
-  </li>
-  <li>Apply the changes and click <b>OK</b>.</li>
-  <li>Back in the project properties dialog, you will now see a project builder 
-    named 'Makejar' that is set to run after the default Java Builder. Click <b>OK</b> 
-    to save the project builder and close the dialog. <strong><br>
-    Note: </strong>You can change the order so that your Ant buildfile runs before 
-    the Java builder, though that wouldn't make sense in this example. <br>
-    <img src="../images/Image613_project_properties.png" alt="Project properties dialog" border="0" > 
-  </li>
-</ol>
-<p>The Java Builder runs the internal Eclipse Java compiler which in 
-  turn is responsible for indexing your source so that searching, refactoring and 
-  many other features are available. Thus it is not possible to replace the internal 
-  Eclipse Java compiler by using a project builder. You can disable the Java Builder and you can control 
-  when the Java Builder runs with respect to the project builders that you define.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-94_run_pj.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-94_run_pj.htm
deleted file mode 100644
index b38f121..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-94_run_pj.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Executing project builders</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Executing project builders</h3>
-  
-<P CLASS="Para">The whole point of project builders is that they are not explicitly 
-  run by the user, but instead are run any time a qualifying build takes place 
-  for the project that owns the buildfile. Remember that the builders are triggered as indicated
-  on the <strong>Build Options</strong> tab in the External Tools dialog and can be 
-  any combination of after a clean, during a manual build or during auto builds. Let's see how this works.</P>
-<ol>
-  <li>Select the HW project in one of the navigation views. In the workbench menu 
-    bar, choose <b>Project &gt; Clean...</b> Select <b>Clean selected projects</b> 
-    and click <b>Ok</b></li>
-  <li>The project is rebuilt and the projectBuilder.xml buildfile is run. Notice 
-    the output from this buildfile in the Console view. </li>
-  <li>Make sure the Autobuild preference is turned on, then make some trivial 
-    change to HelloWorld.java and save the change. The save triggers an auto build, 
-    but the auto build does not trigger the project builder. </li>
-  <li>Suppose we don't want to see the buildfile output every time it runs. Go 
-    back to the External Tools Builders page of the project properties dialog 
-    on HW. Select the Makejar entry and click <b>Edit...</b>. On the <b>Main</b> 
-    tab, uncheck the <b>Capture Output</b> option, apply the change and exit back 
-    to the workbench. </li>
-</ol>
-<P CLASS="Para">This concludes our look at Ant buildfiles as project builders 
-  in Eclipse. It's worth repeating that though this example used a Java project, 
-  project builders are not tied to Java, and may be used for any type of project. 
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-95_external_tools.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-95_external_tools.htm
deleted file mode 100644
index d9c23e0..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-95_external_tools.htm
+++ /dev/null

@@ -1,30 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>External tools</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>External tools</h2>
-  
-<P CLASS="Para">Up to this point in the tutorial, we've discussed Ant as if it 
-  were the only type of external tool available for use in Eclipse. The fact is 
-  that Eclipse's external tools framework handles two broad classes of external 
-  tools:</P>
-<ul>
-  <li>Ant buildfiles</li>
-  <li>Everything else</li>
-</ul>
-<P CLASS="Para"> In this section, we look at ways to set up and use non-Ant external 
-  tools. </P>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-96_non_ant_pjs.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-96_non_ant_pjs.htm
deleted file mode 100644
index dd878ed..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-96_non_ant_pjs.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Non-Ant project builders</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Non-Ant project builders</h3>
-  
-<P CLASS="Para"> When we worked through our project builder example, you may have 
-  noticed that when we created our project builder Ant buildfile, we had a choice 
-  of external tool type:<br>
-  <img src="../images/Image614_et_type_dialog.png" alt="Choice of external tool type dialog" border="0" > </P>
-<P CLASS="Para">The <b>Program</b> option is essentially a catch-all, allowing you 
-  to define an external tool for any executable file that is accessible on your 
-  local or network file system. Suppose that instead of Ant, you prefer to use 
-  your own shell scripts or Windows .bat files to jar up and deploy your Eclipse 
-  projects. You would then create a Program external tool that specified where 
-  and how to execute your script. </P>
-<ol>
-  <li>Create a script that performs your preferred deployment steps.</li>
-  <li>Select the project that you wish to build in one of the navigation views, 
-    and choose <b>Properties</b> from the context menu.</li>
-  <li>Select <b>Builders</b>, click <b>New...</b>, select <b>Program</b> and click 
-    <b>OK</b>.</li>
-  <li>The External Tools dialog appears, configured for Program type tools.</li>
-  <li>Enter the location of your script, its working directory, and any required 
-    arguments. <br>
-    <img src="../images/Image615_program_builder.png" alt="External tools dialog for program type tools" border="0" > 
-  </li>
-  <li>In this case, the script is a Windows .bat file, but it could be a Linux 
-    shell script, a Perl script or just about anything else that can be executed 
-    on your system. </li>
-  <li>The <b>Refresh</b> and <b>Build Options</b> tabs are identical to the tabs 
-    we saw for Ant project builders. In particular, the <b>Build Options</b> tab 
-    allows us to control what types of builds trigger our project builder buildfile.</li>
-  <li>Apply the changes, and click <b>OK</b>.</li>
-  <li>As with Ant project builders, we can control the ordering of this project 
-    builder with respect to other project builders (such as the default Java Builder 
-    for Java projects).</li>
-  <li>Rebuild your project. This will trigger your script to execute. Any output 
-    it generates will be sent to the Console view.</li>
-</ol>
-<p>Ant is a popular tool for configuring and deploying projects. But if you prefer 
-  some other tool, or prefer to do it yourself, you can set up a Program external 
-  tool project builder. This allows you customize the deployment of your project 
-  as you see fit, while keeping the convenience of automatically running your 
-  script every time your project is built.</p>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-97_standalone_ets.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-97_standalone_ets.htm
deleted file mode 100644
index ad1c1b0..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-97_standalone_ets.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Stand-alone external tools</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Stand-alone external tools</h3>
-  
-<P CLASS="Para">For the ultimate in external tool flexibility, create a 'stand-alone' 
-  external tool launch configuration. This is similar to the project builder launch 
-  configurations discussed in the last section, except that it need have nothing 
-  to do with project building, and you can explicitly run it whenever you choose. 
-  Suppose you wanted to have a way to quickly see the contents of a .jar file 
-  in your workspace using the jar utility. </P>
-<ol>
-  <li>Select some .jar file in your workspace.</li>
-  <li>Select <b>Run &gt; External Tools &gt; External Tools...</b> from the workbench 
-    toolbar.<br>
-    <img src="../images/Image616_et_dropdown.png" alt="External tools drop-down menu" border="0" > 
-  </li>
-  <li>Select <b>Program</b> in the tree, then click <b>New</b>.<br>
-    <img src="../images/Image617_jar_inspector.png" alt="External tools dialog for jar inspector script" border="0" > 
-  </li>
-  <li>Name the launch configuration 'jar inspector'.</li>
-  <li>Use the first <b>Browse File System...</b> button to locate the jar executable.</li>
-  <li>In the <b>Arguments</b> field, type '-tvf' and a space, then click <b>Variables...</b>.</li>
-  <li>In the Select Variable dialog, you will see a number of variables you can 
-    pass as arguments to the program specified in Location. Select <b>resource_loc</b> 
-    and click <b>OK</b>. </li>
-  <li>When this buildfile is run, the absolute path of the resource selected in 
-    the workbench will be passed to the jar utility in the position specified. 
-  </li>
-  <li>Click <b>Run</b>.</li>
-  <li>Notice that the buildfile sends the jar utility output to the Console view.</li>
-  <li>Select a different .jar file in your workspace.</li>
-  <li>Click the External Tools button in the toolbar. Notice the contents of this 
-    jar are sent to the Console view as well. Now you have a quick and easy way 
-    to see the output of the jar utility for any .jar file in your workspace.</li>
-</ol>
-<p>This example has only scratched the surface of what you can do with external 
-  tools. The important things to remember are that you can create an external 
-  tool for anything you can run on your system, and that you can pass arguments 
-  to the external tool related to the current workbench selection. In many cases, 
-  this allows you to loosely integrate tools that do not have corresponding Eclipse 
-  plug-ins. </p>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-content.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-content.htm
deleted file mode 100644
index 4f7ef84..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-content.htm
+++ /dev/null

@@ -1,157 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Content Sensitive Object Contributions</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Content Sensitive Object Contributions</h2>
-<p>Previously, the context menus of some applications were limited by the exclusion 
-  of certain menu options. This was based on the known peripheral information, 
-  such as the number of selected resources, the physical name of the file, the 
-  type of resource, and so on. In some instances, a restricted amount of information 
-  was known about the contents of a resource and this significantly reduced unusable 
-  menu options. Such information, could be of great use in an XML file as there 
-  are numerous situations in which an action is applicable for one type of XML 
-  file but not another, such as XML files that contain Ant scripts. The action 
-  <strong>Run Ant...</strong>, while logical in its context menu, is not an action 
-  that is applicable to an XML file that is used to define a plug-in.</p>
-<p> With the addition of the extension point, org.eclipse.core.runtime.contentTypes, 
-  Eclipse now provides a 'content type', allowing plug-ins to contribute to the 
-  Platform content type catalog, further, classes called Content Type Describers 
-  are also available. For developers providing their own content types, there 
-  are two customizable, built-in content type describers available: BinarySignatureDescriber 
-  (for binary content types) and XMLRootElementContentDescriber (for text, XML 
-  based content types). Additionally, plug-in providers may create their own content 
-  describers, for detailed information see, the Platform Plug-in Developer Guide 
-  (Programmer's Guide &gt; Runtime overview &gt; Content types).</p>
-<h3>XMLRootElementContentDescriber</h3>
-<p>It is now possible to define object contributions specific to an XML file with 
-  a given top level tag or that specifies a given DTD. To do this, define an extension 
-  to the org.eclipse.core.runtime.contentTypes extension point with a describer 
-  class of XMLRootElementContentDescriber and parameters indicating the top level 
-  tag name or the dtd name as follows:</p>
-<PRE>   &lt;extension
-       point="org.eclipse.core.runtime.contentTypes"&gt;
-       &lt;content-type
-           id=&lt;id&gt;
-           name=&lt;name&gt; 	
-           base-type="org.eclipse.core.runtime.xml"&gt;
-           &lt;describer class="org.eclipse.core.runtime.content.XMLRootElementContentDescriber"&gt;
-               &lt;parameter name="element" value=<EM>tagValue</EM> /&gt;
-           &lt;/describer&gt;
-       &lt;/content-type&gt;
-   &lt;/extension&gt;</PRE>or <PRE>   &lt;extension
-       point="org.eclipse.core.runtime.contentTypes"&gt;
-       &lt;content-type
-           id=&lt;id&gt;
-           name=&lt;name&gt; 	
-           base-type="org.eclipse.core.runtime.xml"&gt;
-           &lt;describer class="org.eclipse.core.runtime.content.XMLRootElementContentDescriber"&gt;
-               &lt;parameter name="dtd" value=<EM>dtdValue</EM> /&gt;
-           &lt;/describer&gt;
-       &lt;/content-type&gt;
-    &lt;/extension&gt;</PRE>
-<BLOCKQUOTE>where tagValue represents the name of the top level tag to match and
-  <p>dtdValue represents the name of the DTD as seen in the XML file.</p>
-</BLOCKQUOTE>
-  <p>Consider the following object contribution in a plugin.xml file:</p>
-  <p></p>
-
-<PRE>   &lt;extension
-       point="org.eclipse.core.runtime.contentTypes"&gt;
-       &lt;content-type 
-           id="topElementContentType"
-           name="Tests top-level element recognition" 	
-           base-type="org.eclipse.core.runtime.xml"
-           priority="high"&gt;
-           &lt;describer class="org.eclipse.core.runtime.content.XMLRootElementContentDescriber"&gt;
-               &lt;parameter name="element" value="myTag" /&gt;
-           &lt;/describer&gt;
-       &lt;/content-type&gt;
-   &lt;/extension&gt;
-
-   &lt;extension
-       point="org.eclipse.core.runtime.contentTypes"&gt;
-       &lt;content-type 
-           id="dtdContentType"
-           name="Tests dtd element recognition" 	
-           base-type="org.eclipse.core.runtime.xml"
-           priority="high"&gt;
-           &lt;describer class="org.eclipse.core.runtime.content.XMLRootElementContentDescriber"&gt;
-               &lt;parameter name="dtd" value="myDTD.xml" /&gt;
-           &lt;/describer&gt;
-       &lt;/content-type&gt;
-   &lt;/extension&gt;
-</PRE><PRE>   &lt;extension point="org.eclipse.ui.popupMenus"&gt;
-       &lt;objectContribution
-           id="org.eclipse.ui.examples.objectContributions"
-           objectClass="org.eclipse.core.resources.IFile"
-           nameFilter="*.xml"&gt;
-           &lt;visibility&gt;
-               &lt;or&gt;
-                   &lt;objectState
-                       name="contentTypeId"
-                       value="org.eclipse.ui.examples.topElementContentType"/&gt;
-                   &lt;objectState
-                       name="contentTypeId"
-                       value="org.eclipse.ui.examples.dtdContentType"/&gt;
-               &lt;/or&gt;
-           &lt;/visibility&gt;
-           &lt;action id="org.eclipse.ui.examples.objectContributions.action1"
-               label="%PopupMenus.action"
-               icon="icons/ctool16/openbrwsr.png"
-               menubarPath="additions"
-               class="org.eclipse.ui.examples.objectContributions.PopupMenuActionDelegate"
-               enablesFor="1"&gt;
-           &lt;/action&gt;
-       &lt;/objectContribution&gt;
-   &lt;/extension&gt;</PRE>
-<P>This will make action1 visible for any IFile with a name matching *.xml 
-provided it contains myTag as the top level XML tag or it uses the DTD called 
-myDTD.xml. So the following XML files will match:</P>
-<BLOCKQUOTE>
-  <PRE>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
-&lt;myTag
-  id="org.eclipse.ui.workbench"
-  name="%pluginName"
-  version="3.0.0"
-  provider-name="%providerName"
-  class="org.eclipse.ui.internal.WorkbenchPlugin"&gt;
-&lt;/myTag&gt;</PRE>
-</BLOCKQUOTE>
-<p>or</p>
-<BLOCKQUOTE>
-  <PRE>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
-&lt;!DOCTYPE Book SYSTEM "myDTD.xml"&gt;
-&lt;fragment
-   id="org.eclipse.ui.workbench"
-   name="%pluginName"
-	version="3.0.0"
-	provider-name="%providerName"
-	class="org.eclipse.ui.internal.WorkbenchPlugin"&gt;
-	&lt;runtime&gt;
-	   &lt;library name="workbench.jar"&gt;
-	      &lt;export name="*"/&gt;
-		  &lt;packages prefixes="org.eclipse.ui, org.eclipse.jface"/&gt;
-	   &lt;/library&gt;
-	&lt;/runtime&gt;
-&lt;/fragment&gt;
-</PRE>
-</BLOCKQUOTE>
-<H3>BinarySignatureDescriber</H3>
-<p>The BinarySignatureDescriber is a content describer that detects a specified 
-  binary 'signature' at a given offset within a file. This describer is used in 
-  the same fashion as the XMLRootElementContentDescriber with the exception that 
-  it takes parameters "signature", "offset" and "required" instead of "element" 
-  or "dtd". The Javadoc for BinarySignatureDescriber provides complete details 
-  on this content describer's class usage. </p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-responsiveUI.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-responsiveUI.htm
deleted file mode 100644
index 7b80f23..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-responsiveUI.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Responsive UI</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1> Responsive UI</h1>
-<P CLASS="Para">By default all Eclipse operations run in the user interface thread. 
-  Employing the Responsive UI, which allows the threading of sequential code, 
-  will enable you to continue working elsewhere in Eclipse. Without the Responsive 
-  UI support you would be locked out of performing any other actions when met 
-  with a slow operation.</P>
-<P CLASS="Para">While some operations automatically run in the background (such 
-  as auto build), in many cases a dialog will be displayed providing you with 
-  the option to run an operation in the background. For example, building a project 
-  manually can sometimes take more than a few minutes, during which time you may 
-  wish to continue to use other functions in Eclipse.</p> 
-<P CLASS="Para"><img src="../images/res.png" alt="Image of the Build All Menu Item." border="0" > </p>
-<p>While the project is being built, select <strong>Run in Background </strong>from 
-  the <strong>Building Workspace</strong> dialog and the Responsive UI will allow 
-  you to carry on with other tasks in Eclipse.</p>
-<p><img src="../images/res_build.png" alt="Image of the Building Workspace window" border="0" ></p>
-<p>For information on the status of the action and additional operations that 
-  are currently running, click <strong>Details</strong>.</p>
-<p><img src="../images/res_details.png" alt="Image of the Building Workspace window with the Details displayed" border="0" ></p>
-<p>The <strong>Details </strong>panel displays the status information of the operation 
-  at hand as well as any additional operations that may be running simultaneously.</P>
-<p><img src="../images/res_otherjobs.png" alt="Image of the Building Workspace window with the Details showing simultaneous operations" border="0" ></P>
-<p>The Progress Information dialog also indicates when one operation is being 
-  blocked by another. </P>
-<p><img src="../images/res_blocked.png" alt="Image of Progress Information view with an operation that is waiting for another to complete." border="0" ></P>
-<p>To have operations running in the background set as the default, select <strong>Window 
-  &gt; Preferences &gt; General </strong> and check <strong>Always run in background.</strong> 
-</P>
-<p><img src="../images/res_pref.png" alt="Image of Workbench Preferences Window" border="0"></P>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs_activites.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs_activites.htm
deleted file mode 100644
index 1ecdaed..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs_activites.htm
+++ /dev/null

@@ -1,92 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css"><title>Activities Editor</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Activities Editor</h2>
-<P CLASS="Para">To launch the activities editor:</P>
-<ol>
-  <li>Download the activities editor zip file, extract the contents into the Eclipse 
-    plug-in directory and start Eclipse. </li>
-  <li>From the main menu bar, select <strong>File &gt; New &gt; Activity Binding</strong>. 
-    <blockquote> 
-      <p><img src="../images/activity_menu.png" alt="Image of a new activity being opened from the menu bar." border="0" ></p>
-      <p><strong>Notes:</strong></p>
-    </blockquote>
-  </li>
-  <ul>
-    <li>To create a new activities.xml file, select <strong>File &gt; New &gt; 
-      File</strong>. </li>
-    <li>Once an activities.xml file has been created, double-clicking it will 
-      launch the tool. </li>
-    <li>If the Activity Binding menu item or Eclipse icon is not visible, the 
-      activity editor can be added to the perspective by selecting <strong>Window 
-      &gt; Customize Perspective</strong> and checking the Activity Binding command 
-      group within the Commands tab. </li>
-  </ul>
-</ol>
-<p><strong>Supported Operations</strong></P>
-<table width="75%" border="1">
-  <tr> 
-    <td width="48%"><strong>Operation</strong></td>
-    <td width="52%"><strong>Instructions</strong></td>
-  </tr>
-  <tr> 
-    <td> <p>Add a selected plug-in to a selected activity in the categories, activities, 
-        and plug-ins and fragments viewer.</p></td>
-    <td>Click &quot;&gt;&gt;&quot; or select &quot;Add&quot; from the menu accessed 
-      by right clicking in the plug-ins and fragments viewer. </td>
-  </tr>
-  <tr> 
-    <td> Delete a selected category and/or activity in the categories, activities, 
-      and plug-ins and fragments viewer.</td>
-    <td>Select &quot;Delete&quot; from the menu accessed by right clicking in 
-      the viewer.</td>
-  </tr>
-  <tr> 
-    <td> Remove selected categories and/or activities, and selected plug-ins from 
-      the categories, activities, and plug-ins and fragments viewer.</td>
-    <td>Select &quot;Remove/Delete&quot; from the menu accessed by right clicking 
-      in the viewer.</td>
-  </tr>
-  <tr> 
-    <td> Remove selected plug-ins from the categories, activities, and plug-ins 
-      and fragments viewer and return them to the plug-ins and fragments viewer.</td>
-    <td>Click &quot;&lt;&lt;&quot; or select &quot;Remove&quot; from the menu 
-      accessed by right clicking in the categories, activities, and plug-ins and 
-      fragments viewer. </td>
-  </tr>
-  <tr> 
-    <td>Create a category in the categories, activities, and plug-ins and fragments 
-      viewer.</td>
-    <td>Click &quot;New Category&quot; or select &quot;New Category&quot; from 
-      the menu by right clicking in the viewer. </td>
-  </tr>
-  <tr> 
-    <td height="69">Create an activity in the selected category in the categories, 
-      activities, and plug-ins and fragments viewer.</td>
-    <td>Click &quot;New Activity&quot; or select &quot;New Activity&quot; from 
-      the menu by right clicking in the viewer. </td>
-  </tr>
-  <tr> 
-    <td>
-<p>Edit the description field for the categories and activities.</P>
-      </td>
-    <td>Edit the descriptions page as required. </td>
-  </tr>
-</table>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-  <a href="../tasks/concepts-activites.htm">Activities</a></p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-  <a href="../tasks/tasks-activites.htm">Activities Example</a></p> 
-<p> <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-  <a href="../reference/ref-activites.htm">Activities Editor Pages</a></P>
-  
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image1.png b/bundles/org.eclipse.platform.doc.user/images/Image1.png
deleted file mode 100644
index 503bd51..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image11_new_wizard.png b/bundles/org.eclipse.platform.doc.user/images/Image11_new_wizard.png
deleted file mode 100644
index 6288428..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image11_new_wizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image12_new_project_wizard.png b/bundles/org.eclipse.platform.doc.user/images/Image12_new_project_wizard.png
deleted file mode 100644
index 03ab9f3..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image12_new_project_wizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image13_project_in_nav.png b/bundles/org.eclipse.platform.doc.user/images/Image13_project_in_nav.png
deleted file mode 100644
index b92a81f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image13_project_in_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image14_new_folder_wizard.png b/bundles/org.eclipse.platform.doc.user/images/Image14_new_folder_wizard.png
deleted file mode 100644
index 41e4eb5..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image14_new_folder_wizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image15_new_button.png b/bundles/org.eclipse.platform.doc.user/images/Image15_new_button.png
deleted file mode 100644
index 5d54b6a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image15_new_button.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image15_project_depend.png b/bundles/org.eclipse.platform.doc.user/images/Image15_project_depend.png
deleted file mode 100644
index 065c390..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image15_project_depend.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image16_new_pulldown.png b/bundles/org.eclipse.platform.doc.user/images/Image16_new_pulldown.png
deleted file mode 100644
index 885ef16..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image16_new_pulldown.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image17_save_button.png b/bundles/org.eclipse.platform.doc.user/images/Image17_save_button.png
deleted file mode 100644
index 8934246..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image17_save_button.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image17b_unsaved_changes.png b/bundles/org.eclipse.platform.doc.user/images/Image17b_unsaved_changes.png
deleted file mode 100644
index dd11deea..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image17b_unsaved_changes.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image18_created_resources.png b/bundles/org.eclipse.platform.doc.user/images/Image18_created_resources.png
deleted file mode 100644
index 395f235..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image18_created_resources.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image19_close_on_tab.png b/bundles/org.eclipse.platform.doc.user/images/Image19_close_on_tab.png
deleted file mode 100644
index a277176..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image19_close_on_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image201_filetype.png b/bundles/org.eclipse.platform.doc.user/images/Image201_filetype.png
deleted file mode 100644
index d17f47b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image201_filetype.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image202_editorsel.png b/bundles/org.eclipse.platform.doc.user/images/Image202_editorsel.png
deleted file mode 100644
index 77fb42e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image202_editorsel.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image203_actionset.png b/bundles/org.eclipse.platform.doc.user/images/Image203_actionset.png
deleted file mode 100644
index 126b242..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image203_actionset.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image206_persp_saveas.png b/bundles/org.eclipse.platform.doc.user/images/Image206_persp_saveas.png
deleted file mode 100644
index 92e7e2b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image206_persp_saveas.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image207_persp_sel.png b/bundles/org.eclipse.platform.doc.user/images/Image207_persp_sel.png
deleted file mode 100644
index 70a539b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image207_persp_sel.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image208_view_sel.png b/bundles/org.eclipse.platform.doc.user/images/Image208_view_sel.png
deleted file mode 100644
index bf2e509..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image208_view_sel.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image209_workspace.png b/bundles/org.eclipse.platform.doc.user/images/Image209_workspace.png
deleted file mode 100644
index 1bb614e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image209_workspace.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image20_nav_with_resources.png b/bundles/org.eclipse.platform.doc.user/images/Image20_nav_with_resources.png
deleted file mode 100644
index edb3c51..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image20_nav_with_resources.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image210_filefilter.png b/bundles/org.eclipse.platform.doc.user/images/Image210_filefilter.png
deleted file mode 100644
index 6f0e7ba..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image210_filefilter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image211_fastview.png b/bundles/org.eclipse.platform.doc.user/images/Image211_fastview.png
deleted file mode 100644
index 1a39fd3..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image211_fastview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image211_perspective.png b/bundles/org.eclipse.platform.doc.user/images/Image211_perspective.png
deleted file mode 100644
index 4794b0c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image211_perspective.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image214_toobar_rsrc.png b/bundles/org.eclipse.platform.doc.user/images/Image214_toobar_rsrc.png
deleted file mode 100644
index 14481b6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image214_toobar_rsrc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image215_toolbar_view.png b/bundles/org.eclipse.platform.doc.user/images/Image215_toolbar_view.png
deleted file mode 100644
index 744007e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image215_toolbar_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image216_history_view.png b/bundles/org.eclipse.platform.doc.user/images/Image216_history_view.png
deleted file mode 100644
index 051977d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image216_history_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image217_pref_wb.png b/bundles/org.eclipse.platform.doc.user/images/Image217_pref_wb.png
deleted file mode 100644
index 75c580c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image217_pref_wb.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image218_pref_app.png b/bundles/org.eclipse.platform.doc.user/images/Image218_pref_app.png
deleted file mode 100644
index ddcefd5..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image218_pref_app.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image219_pref_cv.png b/bundles/org.eclipse.platform.doc.user/images/Image219_pref_cv.png
deleted file mode 100644
index 07a7e85..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image219_pref_cv.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image21_task_view.png b/bundles/org.eclipse.platform.doc.user/images/Image21_task_view.png
deleted file mode 100644
index e20ba36..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image21_task_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image220_pref_dte.png b/bundles/org.eclipse.platform.doc.user/images/Image220_pref_dte.png
deleted file mode 100644
index 6cb2e86..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image220_pref_dte.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image221_pref_fe.png b/bundles/org.eclipse.platform.doc.user/images/Image221_pref_fe.png
deleted file mode 100644
index e087ea1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image221_pref_fe.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image222_pref_lh.png b/bundles/org.eclipse.platform.doc.user/images/Image222_pref_lh.png
deleted file mode 100644
index 558facc..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image222_pref_lh.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image223_pref_persp.png b/bundles/org.eclipse.platform.doc.user/images/Image223_pref_persp.png
deleted file mode 100644
index 7087d52..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image223_pref_persp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image224_pref_build.png b/bundles/org.eclipse.platform.doc.user/images/Image224_pref_build.png
deleted file mode 100644
index ab78b90..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image224_pref_build.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image225_pref_help.png b/bundles/org.eclipse.platform.doc.user/images/Image225_pref_help.png
deleted file mode 100644
index b1cd054..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image225_pref_help.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image229_editor_popup.png b/bundles/org.eclipse.platform.doc.user/images/Image229_editor_popup.png
deleted file mode 100644
index 09193e1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image229_editor_popup.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image229_view_popup.png b/bundles/org.eclipse.platform.doc.user/images/Image229_view_popup.png
deleted file mode 100644
index e28c5bb..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image229_view_popup.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image230_editor_area.png b/bundles/org.eclipse.platform.doc.user/images/Image230_editor_area.png
deleted file mode 100644
index 0495666..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image230_editor_area.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image231_marker_bar.png b/bundles/org.eclipse.platform.doc.user/images/Image231_marker_bar.png
deleted file mode 100644
index e91e19c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image231_marker_bar.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image232_marker_context.png b/bundles/org.eclipse.platform.doc.user/images/Image232_marker_context.png
deleted file mode 100644
index eb7664c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image232_marker_context.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image237_search_view.png b/bundles/org.eclipse.platform.doc.user/images/Image237_search_view.png
deleted file mode 100644
index 0ea0e48..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image237_search_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image239_help_view.png b/bundles/org.eclipse.platform.doc.user/images/Image239_help_view.png
deleted file mode 100644
index 1ae007c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image239_help_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image240_props_view.png b/bundles/org.eclipse.platform.doc.user/images/Image240_props_view.png
deleted file mode 100644
index 5fa5eef..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image240_props_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image241_nav_view.png b/bundles/org.eclipse.platform.doc.user/images/Image241_nav_view.png
deleted file mode 100644
index 805ff99..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image241_nav_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image242_repo_view.png b/bundles/org.eclipse.platform.doc.user/images/Image242_repo_view.png
deleted file mode 100644
index 3b44388..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image242_repo_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image243_tasks_view.png b/bundles/org.eclipse.platform.doc.user/images/Image243_tasks_view.png
deleted file mode 100644
index 4242dba..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image243_tasks_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image244_bmark_view.png b/bundles/org.eclipse.platform.doc.user/images/Image244_bmark_view.png
deleted file mode 100644
index c5230ad..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image244_bmark_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image245_sync_view.png b/bundles/org.eclipse.platform.doc.user/images/Image245_sync_view.png
deleted file mode 100644
index 412d68d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image245_sync_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image246_file_wiz.png b/bundles/org.eclipse.platform.doc.user/images/Image246_file_wiz.png
deleted file mode 100644
index 1cc5d93..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image246_file_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image247_projsel_wiz.png b/bundles/org.eclipse.platform.doc.user/images/Image247_projsel_wiz.png
deleted file mode 100644
index 6ba4e4f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image247_projsel_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image248_folder_wiz.png b/bundles/org.eclipse.platform.doc.user/images/Image248_folder_wiz.png
deleted file mode 100644
index bfb370f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image248_folder_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image249_repo_wiz.png b/bundles/org.eclipse.platform.doc.user/images/Image249_repo_wiz.png
deleted file mode 100644
index d80f849..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image249_repo_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image251_proj_wiz.png b/bundles/org.eclipse.platform.doc.user/images/Image251_proj_wiz.png
deleted file mode 100644
index b538fb3..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image251_proj_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image252_projref_page.png b/bundles/org.eclipse.platform.doc.user/images/Image252_projref_page.png
deleted file mode 100644
index c9526e9..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image252_projref_page.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image258_perps_custom.png b/bundles/org.eclipse.platform.doc.user/images/Image258_perps_custom.png
deleted file mode 100644
index cca53ff..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image258_perps_custom.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image261_import_sel.png b/bundles/org.eclipse.platform.doc.user/images/Image261_import_sel.png
deleted file mode 100644
index 530321c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image261_import_sel.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image262_import_file.png b/bundles/org.eclipse.platform.doc.user/images/Image262_import_file.png
deleted file mode 100644
index e462c51..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image262_import_file.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image262_import_preferences.png b/bundles/org.eclipse.platform.doc.user/images/Image262_import_preferences.png
deleted file mode 100644
index ad52dd2..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image262_import_preferences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image263_import_cvs.png b/bundles/org.eclipse.platform.doc.user/images/Image263_import_cvs.png
deleted file mode 100644
index 86bd74e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image263_import_cvs.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image263_import_zip.png b/bundles/org.eclipse.platform.doc.user/images/Image263_import_zip.png
deleted file mode 100644
index 122afcd..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image263_import_zip.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image264_existing_project.png b/bundles/org.eclipse.platform.doc.user/images/Image264_existing_project.png
deleted file mode 100644
index 2a27223..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image264_existing_project.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image264_export_sel.png b/bundles/org.eclipse.platform.doc.user/images/Image264_export_sel.png
deleted file mode 100644
index 5a2b9e1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image264_export_sel.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image264_external_feature.png b/bundles/org.eclipse.platform.doc.user/images/Image264_external_feature.png
deleted file mode 100644
index 8ebed95..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image264_external_feature.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image264_plugins_fragments.png b/bundles/org.eclipse.platform.doc.user/images/Image264_plugins_fragments.png
deleted file mode 100644
index fd9aac7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image264_plugins_fragments.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image265_export_file.png b/bundles/org.eclipse.platform.doc.user/images/Image265_export_file.png
deleted file mode 100644
index 3ffb778..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image265_export_file.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image265_team_project.png b/bundles/org.eclipse.platform.doc.user/images/Image265_team_project.png
deleted file mode 100644
index 830a2ff..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image265_team_project.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image266_export_ant.png b/bundles/org.eclipse.platform.doc.user/images/Image266_export_ant.png
deleted file mode 100644
index 4904ecf..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image266_export_ant.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image266_export_feature.png b/bundles/org.eclipse.platform.doc.user/images/Image266_export_feature.png
deleted file mode 100644
index 524298a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image266_export_feature.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image266_export_javadoc.png b/bundles/org.eclipse.platform.doc.user/images/Image266_export_javadoc.png
deleted file mode 100644
index 37b809c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image266_export_javadoc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image266_export_plugins.png b/bundles/org.eclipse.platform.doc.user/images/Image266_export_plugins.png
deleted file mode 100644
index 5c046f6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image266_export_plugins.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image266_export_preferences.png b/bundles/org.eclipse.platform.doc.user/images/Image266_export_preferences.png
deleted file mode 100644
index 240821b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image266_export_preferences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image266_export_product.png b/bundles/org.eclipse.platform.doc.user/images/Image266_export_product.png
deleted file mode 100644
index 952c372..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image266_export_product.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image266_export_zip.png b/bundles/org.eclipse.platform.doc.user/images/Image266_export_zip.png
deleted file mode 100644
index 89f2160..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image266_export_zip.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image267_export_jar.png b/bundles/org.eclipse.platform.doc.user/images/Image267_export_jar.png
deleted file mode 100644
index 47928f2..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image267_export_jar.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image268_export_team.png b/bundles/org.eclipse.platform.doc.user/images/Image268_export_team.png
deleted file mode 100644
index 6ebd8d0..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image268_export_team.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image269_merge_init.png b/bundles/org.eclipse.platform.doc.user/images/Image269_merge_init.png
deleted file mode 100644
index 1a26c08..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image269_merge_init.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image273_local_hist.png b/bundles/org.eclipse.platform.doc.user/images/Image273_local_hist.png
deleted file mode 100644
index a996edb..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image273_local_hist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image273_nav-decorators.png b/bundles/org.eclipse.platform.doc.user/images/Image273_nav-decorators.png
deleted file mode 100644
index dfc64da..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image273_nav-decorators.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image274_fonts_preference.png b/bundles/org.eclipse.platform.doc.user/images/Image274_fonts_preference.png
deleted file mode 100644
index fdde10d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image274_fonts_preference.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image274_fonts_preference2.png b/bundles/org.eclipse.platform.doc.user/images/Image274_fonts_preference2.png
deleted file mode 100644
index 204f353..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image274_fonts_preference2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image275_startup_preference.png b/bundles/org.eclipse.platform.doc.user/images/Image275_startup_preference.png
deleted file mode 100644
index 3cdfe8c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image275_startup_preference.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image276_search_preference.png b/bundles/org.eclipse.platform.doc.user/images/Image276_search_preference.png
deleted file mode 100644
index 5897c79..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image276_search_preference.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image2_active_editor.png b/bundles/org.eclipse.platform.doc.user/images/Image2_active_editor.png
deleted file mode 100644
index eda53de..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image2_active_editor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image2_active_view.png b/bundles/org.eclipse.platform.doc.user/images/Image2_active_view.png
deleted file mode 100644
index 461c734..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image2_active_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image30_goto_resource.png b/bundles/org.eclipse.platform.doc.user/images/Image30_goto_resource.png
deleted file mode 100644
index 2d1bb90..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image30_goto_resource.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image31_go_into.png b/bundles/org.eclipse.platform.doc.user/images/Image31_go_into.png
deleted file mode 100644
index 3d8690c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image31_go_into.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image33_into_buttons.png b/bundles/org.eclipse.platform.doc.user/images/Image33_into_buttons.png
deleted file mode 100644
index 531e7d9..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image33_into_buttons.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image35umd_extprevu.png b/bundles/org.eclipse.platform.doc.user/images/Image35umd_extprevu.png
deleted file mode 100644
index c922641..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image35umd_extprevu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image36_linkedresources.png b/bundles/org.eclipse.platform.doc.user/images/Image36_linkedresources.png
deleted file mode 100644
index d069ca3..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image36_linkedresources.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image37drop.png b/bundles/org.eclipse.platform.doc.user/images/Image37drop.png
deleted file mode 100644
index ee2143d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image37drop.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image38_import.png b/bundles/org.eclipse.platform.doc.user/images/Image38_import.png
deleted file mode 100644
index 7546818..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image38_import.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image39_import_tree.png b/bundles/org.eclipse.platform.doc.user/images/Image39_import_tree.png
deleted file mode 100644
index 37b01c9..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image39_import_tree.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image3_single.png b/bundles/org.eclipse.platform.doc.user/images/Image3_single.png
deleted file mode 100644
index 77db27a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image3_single.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image3_tabbed.png b/bundles/org.eclipse.platform.doc.user/images/Image3_tabbed.png
deleted file mode 100644
index 8101bc8..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image3_tabbed.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image400_filterbutton.png b/bundles/org.eclipse.platform.doc.user/images/Image400_filterbutton.png
deleted file mode 100644
index 379cc4d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image400_filterbutton.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image40_import_target.png b/bundles/org.eclipse.platform.doc.user/images/Image40_import_target.png
deleted file mode 100644
index 8a8e5f6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image40_import_target.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image41_import_combo.png b/bundles/org.eclipse.platform.doc.user/images/Image41_import_combo.png
deleted file mode 100644
index 1241b52..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image41_import_combo.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image42_export.png b/bundles/org.eclipse.platform.doc.user/images/Image42_export.png
deleted file mode 100644
index 8b180ba..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image42_export.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image43_export_tree.png b/bundles/org.eclipse.platform.doc.user/images/Image43_export_tree.png
deleted file mode 100644
index d4c173e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image43_export_tree.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image44_confirm_state.png b/bundles/org.eclipse.platform.doc.user/images/Image44_confirm_state.png
deleted file mode 100644
index 1b67fa1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image44_confirm_state.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image45_file_search.png b/bundles/org.eclipse.platform.doc.user/images/Image45_file_search.png
deleted file mode 100644
index 5bac86d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image45_file_search.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image45_setup.png b/bundles/org.eclipse.platform.doc.user/images/Image45_setup.png
deleted file mode 100644
index 6569d69..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image45_setup.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image48_move.png b/bundles/org.eclipse.platform.doc.user/images/Image48_move.png
deleted file mode 100644
index 11b7b82..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image48_move.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image48_rename.png b/bundles/org.eclipse.platform.doc.user/images/Image48_rename.png
deleted file mode 100644
index 1b0a8c5..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image48_rename.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image48_rename_done.png b/bundles/org.eclipse.platform.doc.user/images/Image48_rename_done.png
deleted file mode 100644
index f1d4d4e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image48_rename_done.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image49_3_way_compare.png b/bundles/org.eclipse.platform.doc.user/images/Image49_3_way_compare.png
deleted file mode 100644
index 840e2c2..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image49_3_way_compare.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image4_showview.png b/bundles/org.eclipse.platform.doc.user/images/Image4_showview.png
deleted file mode 100644
index a6dffa1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image4_showview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image50_search.png b/bundles/org.eclipse.platform.doc.user/images/Image50_search.png
deleted file mode 100644
index 44519f5..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image50_search.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image51_choose_ext.png b/bundles/org.eclipse.platform.doc.user/images/Image51_choose_ext.png
deleted file mode 100644
index 083d71b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image51_choose_ext.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image51_search_hover.png b/bundles/org.eclipse.platform.doc.user/images/Image51_search_hover.png
deleted file mode 100644
index 9aa8d36..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image51_search_hover.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image51_search_it.png b/bundles/org.eclipse.platform.doc.user/images/Image51_search_it.png
deleted file mode 100644
index 7a98ad0..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image51_search_it.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image51_search_next.png b/bundles/org.eclipse.platform.doc.user/images/Image51_search_next.png
deleted file mode 100644
index a98a55e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image51_search_next.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image51_search_progress.png b/bundles/org.eclipse.platform.doc.user/images/Image51_search_progress.png
deleted file mode 100644
index 5e1a586..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image51_search_progress.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image51_search_reduced.png b/bundles/org.eclipse.platform.doc.user/images/Image51_search_reduced.png
deleted file mode 100644
index 6bb05d2..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image51_search_reduced.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image51_search_switching.png b/bundles/org.eclipse.platform.doc.user/images/Image51_search_switching.png
deleted file mode 100644
index 2fbe452..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image51_search_switching.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image51_search_view.png b/bundles/org.eclipse.platform.doc.user/images/Image51_search_view.png
deleted file mode 100644
index dd4ae2e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image51_search_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image52_new_task.png b/bundles/org.eclipse.platform.doc.user/images/Image52_new_task.png
deleted file mode 100644
index 9bdec36..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image52_new_task.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image53_add_task_dlg.png b/bundles/org.eclipse.platform.doc.user/images/Image53_add_task_dlg.png
deleted file mode 100644
index e2bf81f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image53_add_task_dlg.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image53_marker1.png b/bundles/org.eclipse.platform.doc.user/images/Image53_marker1.png
deleted file mode 100644
index f1eef68..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image53_marker1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image53_newtask.png b/bundles/org.eclipse.platform.doc.user/images/Image53_newtask.png
deleted file mode 100644
index bfd2538..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image53_newtask.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image53_task_updated.png b/bundles/org.eclipse.platform.doc.user/images/Image53_task_updated.png
deleted file mode 100644
index 9c58073..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image53_task_updated.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark1.png b/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark1.png
deleted file mode 100644
index 2a4cde3..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_added.png b/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_added.png
deleted file mode 100644
index d82061a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_added.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_added2.png b/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_added2.png
deleted file mode 100644
index 6a83d63..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_added2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_del1.png b/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_del1.png
deleted file mode 100644
index 1314da7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_del1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_goto.png b/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_goto.png
deleted file mode 100644
index 282bbe3..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_goto.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_menu.png b/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_menu.png
deleted file mode 100644
index d12b430..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_oneleft.png b/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_oneleft.png
deleted file mode 100644
index 933fc7d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_oneleft.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_remove2.png b/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_remove2.png
deleted file mode 100644
index 376d1fb..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_remove2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_two.png b/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_two.png
deleted file mode 100644
index 4e4d8d2..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_two.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image55_reset.png b/bundles/org.eclipse.platform.doc.user/images/Image55_reset.png
deleted file mode 100644
index bdcea27..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image55_reset.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image57_two_editors.png b/bundles/org.eclipse.platform.doc.user/images/Image57_two_editors.png
deleted file mode 100644
index 4236063..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image57_two_editors.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image5_text_editor.png b/bundles/org.eclipse.platform.doc.user/images/Image5_text_editor.png
deleted file mode 100644
index d5b5809..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image5_text_editor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image602_tar_assist.png b/bundles/org.eclipse.platform.doc.user/images/Image602_tar_assist.png
deleted file mode 100644
index 0129c29..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image602_tar_assist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image603_run_dialog.png b/bundles/org.eclipse.platform.doc.user/images/Image603_run_dialog.png
deleted file mode 100644
index 6830bd5..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image603_run_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image606_refresh_tab.png b/bundles/org.eclipse.platform.doc.user/images/Image606_refresh_tab.png
deleted file mode 100644
index 53dc913..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image606_refresh_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image607_buildxml.png b/bundles/org.eclipse.platform.doc.user/images/Image607_buildxml.png
deleted file mode 100644
index 8cc6564..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image607_buildxml.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image608_buildxml_outline.png b/bundles/org.eclipse.platform.doc.user/images/Image608_buildxml_outline.png
deleted file mode 100644
index f17a81e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image608_buildxml_outline.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image609_project_builder.png b/bundles/org.eclipse.platform.doc.user/images/Image609_project_builder.png
deleted file mode 100644
index 59aaad7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image609_project_builder.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image60_fast_view1.png b/bundles/org.eclipse.platform.doc.user/images/Image60_fast_view1.png
deleted file mode 100644
index 1fb3993..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image60_fast_view1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image60_switch_editor.png b/bundles/org.eclipse.platform.doc.user/images/Image60_switch_editor.png
deleted file mode 100644
index 16ff32d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image60_switch_editor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image60_tabs.png b/bundles/org.eclipse.platform.doc.user/images/Image60_tabs.png
deleted file mode 100644
index 7b05619..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image60_tabs.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image60_tabs2.png b/bundles/org.eclipse.platform.doc.user/images/Image60_tabs2.png
deleted file mode 100644
index 9428f2d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image60_tabs2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image610_et_options_tab.png b/bundles/org.eclipse.platform.doc.user/images/Image610_et_options_tab.png
deleted file mode 100644
index 5bcc754..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image610_et_options_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image611_et_main_tab.png b/bundles/org.eclipse.platform.doc.user/images/Image611_et_main_tab.png
deleted file mode 100644
index a5b85c6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image611_et_main_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image612_et_refresh_tab.png b/bundles/org.eclipse.platform.doc.user/images/Image612_et_refresh_tab.png
deleted file mode 100644
index 953cb2c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image612_et_refresh_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image613_project_properties.png b/bundles/org.eclipse.platform.doc.user/images/Image613_project_properties.png
deleted file mode 100644
index 49f4fe2..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image613_project_properties.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image614_et_type_dialog.png b/bundles/org.eclipse.platform.doc.user/images/Image614_et_type_dialog.png
deleted file mode 100644
index dcb4dcd..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image614_et_type_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image615_program_builder.png b/bundles/org.eclipse.platform.doc.user/images/Image615_program_builder.png
deleted file mode 100644
index 92e3196..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image615_program_builder.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image616_et_dropdown.png b/bundles/org.eclipse.platform.doc.user/images/Image616_et_dropdown.png
deleted file mode 100644
index 1e531e2..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image616_et_dropdown.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image617_jar_inspector.png b/bundles/org.eclipse.platform.doc.user/images/Image617_jar_inspector.png
deleted file mode 100644
index deec202..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image617_jar_inspector.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image619_ole.png b/bundles/org.eclipse.platform.doc.user/images/Image619_ole.png
deleted file mode 100644
index be3e8f4..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image619_ole.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image61_fast_minimize.png b/bundles/org.eclipse.platform.doc.user/images/Image61_fast_minimize.png
deleted file mode 100644
index e06d005..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image61_fast_minimize.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image61_fast_options.png b/bundles/org.eclipse.platform.doc.user/images/Image61_fast_options.png
deleted file mode 100644
index e2b8740..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image61_fast_options.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image61_fast_restore.png b/bundles/org.eclipse.platform.doc.user/images/Image61_fast_restore.png
deleted file mode 100644
index b08bdfd..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image61_fast_restore.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image61_nav_fast.png b/bundles/org.eclipse.platform.doc.user/images/Image61_nav_fast.png
deleted file mode 100644
index dd15861..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image61_nav_fast.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image6_two_editors.png b/bundles/org.eclipse.platform.doc.user/images/Image6_two_editors.png
deleted file mode 100644
index 9f61ef6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image6_two_editors.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image70_select_pers.png b/bundles/org.eclipse.platform.doc.user/images/Image70_select_pers.png
deleted file mode 100644
index 67032d0..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image70_select_pers.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image70_shortcut1.png b/bundles/org.eclipse.platform.doc.user/images/Image70_shortcut1.png
deleted file mode 100644
index a25018f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image70_shortcut1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image70_shortcut2.png b/bundles/org.eclipse.platform.doc.user/images/Image70_shortcut2.png
deleted file mode 100644
index 95cdae6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image70_shortcut2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image70_shortcut3.png b/bundles/org.eclipse.platform.doc.user/images/Image70_shortcut3.png
deleted file mode 100644
index 97cbdfd..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image70_shortcut3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image70_shortcut4.png b/bundles/org.eclipse.platform.doc.user/images/Image70_shortcut4.png
deleted file mode 100644
index 8f99392..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image70_shortcut4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image71_pers_customize.png b/bundles/org.eclipse.platform.doc.user/images/Image71_pers_customize.png
deleted file mode 100644
index 796027b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image71_pers_customize.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image71_pers_pref.png b/bundles/org.eclipse.platform.doc.user/images/Image71_pers_pref.png
deleted file mode 100644
index f152084..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image71_pers_pref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image71_pers_reset.png b/bundles/org.eclipse.platform.doc.user/images/Image71_pers_reset.png
deleted file mode 100644
index ad294bc..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image71_pers_reset.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image71_pers_rundebug.png b/bundles/org.eclipse.platform.doc.user/images/Image71_pers_rundebug.png
deleted file mode 100644
index 7b977b6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image71_pers_rundebug.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image71_pers_save.png b/bundles/org.eclipse.platform.doc.user/images/Image71_pers_save.png
deleted file mode 100644
index f34e33b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image71_pers_save.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image7_view_pulldown.png b/bundles/org.eclipse.platform.doc.user/images/Image7_view_pulldown.png
deleted file mode 100644
index 7a8c9a2..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image7_view_pulldown.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image80_compare.png b/bundles/org.eclipse.platform.doc.user/images/Image80_compare.png
deleted file mode 100644
index f093767..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image80_compare.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_after.png b/bundles/org.eclipse.platform.doc.user/images/Image80_compare_after.png
deleted file mode 100644
index d831e30..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_after.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_change2.png b/bundles/org.eclipse.platform.doc.user/images/Image80_compare_change2.png
deleted file mode 100644
index 0a57fe8..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_change2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor.png b/bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor.png
deleted file mode 100644
index 48bf5e7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor2.png b/bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor2.png
deleted file mode 100644
index 2194263..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor3.png b/bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor3.png
deleted file mode 100644
index 670bb1e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor_next.png b/bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor_next.png
deleted file mode 100644
index b01051a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor_next.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_rl.png b/bundles/org.eclipse.platform.doc.user/images/Image80_compare_rl.png
deleted file mode 100644
index 0143879..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_rl.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image81_local.png b/bundles/org.eclipse.platform.doc.user/images/Image81_local.png
deleted file mode 100644
index ab8569d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image81_local.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_import2_project_fred.png b/bundles/org.eclipse.platform.doc.user/images/Image82_import2_project_fred.png
deleted file mode 100644
index ce16e7b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_import2_project_fred.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_import3_project_fred.png b/bundles/org.eclipse.platform.doc.user/images/Image82_import3_project_fred.png
deleted file mode 100644
index 9a50921..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_import3_project_fred.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_import4_project_fred.png b/bundles/org.eclipse.platform.doc.user/images/Image82_import4_project_fred.png
deleted file mode 100644
index 04e59a4..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_import4_project_fred.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_import_project_fred.png b/bundles/org.eclipse.platform.doc.user/images/Image82_import_project_fred.png
deleted file mode 100644
index e9fefd0..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_import_project_fred.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_nav.png b/bundles/org.eclipse.platform.doc.user/images/Image82_nav.png
deleted file mode 100644
index 23dc0ec..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_new.png b/bundles/org.eclipse.platform.doc.user/images/Image82_repo_new.png
deleted file mode 100644
index f6a6ae8..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_new.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_new3.png b/bundles/org.eclipse.platform.doc.user/images/Image82_repo_new3.png
deleted file mode 100644
index c64f5f4..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_new3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_rel5.png b/bundles/org.eclipse.platform.doc.user/images/Image82_repo_rel5.png
deleted file mode 100644
index cb93dc7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_rel5.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_release.png b/bundles/org.eclipse.platform.doc.user/images/Image82_repo_release.png
deleted file mode 100644
index 4ce603f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_release.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_release2.png b/bundles/org.eclipse.platform.doc.user/images/Image82_repo_release2.png
deleted file mode 100644
index 7645723..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_release2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_res.png b/bundles/org.eclipse.platform.doc.user/images/Image82_repo_res.png
deleted file mode 100644
index 696d417..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_res.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_sync1.png b/bundles/org.eclipse.platform.doc.user/images/Image82_repo_sync1.png
deleted file mode 100644
index 2938fd5..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_sync1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_sync2.png b/bundles/org.eclipse.platform.doc.user/images/Image82_repo_sync2.png
deleted file mode 100644
index 8019822..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_sync2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_syncview.png b/bundles/org.eclipse.platform.doc.user/images/Image82_repo_syncview.png
deleted file mode 100644
index 9c9a7bd..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_syncview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_team.png b/bundles/org.eclipse.platform.doc.user/images/Image82_repo_team.png
deleted file mode 100644
index 629184a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_team.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_view1.png b/bundles/org.eclipse.platform.doc.user/images/Image82_repo_view1.png
deleted file mode 100644
index a9717bf..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_view1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_cvs_savedpasswords.png b/bundles/org.eclipse.platform.doc.user/images/Image83_cvs_savedpasswords.png
deleted file mode 100644
index 05954e4..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_cvs_savedpasswords.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_fred1.png b/bundles/org.eclipse.platform.doc.user/images/Image83_fred1.png
deleted file mode 100644
index d654f6a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_fred1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_fred2.png b/bundles/org.eclipse.platform.doc.user/images/Image83_fred2.png
deleted file mode 100644
index 8c7ed3b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_fred2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_fred3_add.png b/bundles/org.eclipse.platform.doc.user/images/Image83_fred3_add.png
deleted file mode 100644
index 7328917..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_fred3_add.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_fred_verson.png b/bundles/org.eclipse.platform.doc.user/images/Image83_fred_verson.png
deleted file mode 100644
index 6589ffa..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_fred_verson.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_fred_verson2.png b/bundles/org.eclipse.platform.doc.user/images/Image83_fred_verson2.png
deleted file mode 100644
index 4051596..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_fred_verson2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_jane-history.png b/bundles/org.eclipse.platform.doc.user/images/Image83_jane-history.png
deleted file mode 100644
index 1a6d791..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_jane-history.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_jane-sync.png b/bundles/org.eclipse.platform.doc.user/images/Image83_jane-sync.png
deleted file mode 100644
index 1c365e6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_jane-sync.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_jane1.png b/bundles/org.eclipse.platform.doc.user/images/Image83_jane1.png
deleted file mode 100644
index 95cde15..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_jane1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_jane2b.png b/bundles/org.eclipse.platform.doc.user/images/Image83_jane2b.png
deleted file mode 100644
index 9ef61c3..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_jane2b.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_jane3_conflict.png b/bundles/org.eclipse.platform.doc.user/images/Image83_jane3_conflict.png
deleted file mode 100644
index 4a6ce4b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_jane3_conflict.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_jane3_conflict2.png b/bundles/org.eclipse.platform.doc.user/images/Image83_jane3_conflict2.png
deleted file mode 100644
index 35eaf3a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_jane3_conflict2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_jane3_status.png b/bundles/org.eclipse.platform.doc.user/images/Image83_jane3_status.png
deleted file mode 100644
index d61d0bb..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_jane3_status.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_jane4.png b/bundles/org.eclipse.platform.doc.user/images/Image83_jane4.png
deleted file mode 100644
index d4b41e8..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_jane4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_jane5a.png b/bundles/org.eclipse.platform.doc.user/images/Image83_jane5a.png
deleted file mode 100644
index d07f2b6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_jane5a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_jane6a.png b/bundles/org.eclipse.platform.doc.user/images/Image83_jane6a.png
deleted file mode 100644
index 30e96b7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_jane6a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image84_decorator_preferenc.png b/bundles/org.eclipse.platform.doc.user/images/Image84_decorator_preferenc.png
deleted file mode 100644
index 1d73585..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image84_decorator_preferenc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image84_decorator_preference.png b/bundles/org.eclipse.platform.doc.user/images/Image84_decorator_preference.png
deleted file mode 100644
index 75d78be..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image84_decorator_preference.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image84_jane.png b/bundles/org.eclipse.platform.doc.user/images/Image84_jane.png
deleted file mode 100644
index 7a27b6a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image84_jane.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image84_relmode.png b/bundles/org.eclipse.platform.doc.user/images/Image84_relmode.png
deleted file mode 100644
index 738c206..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image84_relmode.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image84_replace2.png b/bundles/org.eclipse.platform.doc.user/images/Image84_replace2.png
deleted file mode 100644
index 1806784..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image84_replace2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image84_reshist.png b/bundles/org.eclipse.platform.doc.user/images/Image84_reshist.png
deleted file mode 100644
index d93c972..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image84_reshist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image84_status.png b/bundles/org.eclipse.platform.doc.user/images/Image84_status.png
deleted file mode 100644
index 247f107..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image84_status.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image85_version2.png b/bundles/org.eclipse.platform.doc.user/images/Image85_version2.png
deleted file mode 100644
index 299f12d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image85_version2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image87_workset_sel.png b/bundles/org.eclipse.platform.doc.user/images/Image87_workset_sel.png
deleted file mode 100644
index c0b22d5..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image87_workset_sel.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image88_workset_new_type.png b/bundles/org.eclipse.platform.doc.user/images/Image88_workset_new_type.png
deleted file mode 100644
index dbf1d01..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image88_workset_new_type.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image89_workset_new_res.png b/bundles/org.eclipse.platform.doc.user/images/Image89_workset_new_res.png
deleted file mode 100644
index 6273446..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image89_workset_new_res.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image8_view.png b/bundles/org.eclipse.platform.doc.user/images/Image8_view.png
deleted file mode 100644
index b21f503..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image8_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image90_locked_toolbar.png b/bundles/org.eclipse.platform.doc.user/images/Image90_locked_toolbar.png
deleted file mode 100644
index 02d9421..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image90_locked_toolbar.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image90_unlocked_toolbar.png b/bundles/org.eclipse.platform.doc.user/images/Image90_unlocked_toolbar.png
deleted file mode 100644
index 334538b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image90_unlocked_toolbar.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_1.png b/bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_1.png
deleted file mode 100644
index bb584e6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_2.png b/bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_2.png
deleted file mode 100644
index 3432671..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_3.png b/bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_3.png
deleted file mode 100644
index 931cb20..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image9_viewdownarrow.png b/bundles/org.eclipse.platform.doc.user/images/Image9_viewdownarrow.png
deleted file mode 100644
index cb0d2c6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image9_viewdownarrow.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image_auto_up.png b/bundles/org.eclipse.platform.doc.user/images/Image_auto_up.png
deleted file mode 100644
index ab7fa24..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image_auto_up.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image_filecon_pref.png b/bundles/org.eclipse.platform.doc.user/images/Image_filecon_pref.png
deleted file mode 100644
index 1d109c9..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image_filecon_pref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image_ignore_pref.png b/bundles/org.eclipse.platform.doc.user/images/Image_ignore_pref.png
deleted file mode 100644
index a9fa2d9..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image_ignore_pref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image_pref_inup.png b/bundles/org.eclipse.platform.doc.user/images/Image_pref_inup.png
deleted file mode 100644
index 6275a8d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image_pref_inup.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image_team_pref.png b/bundles/org.eclipse.platform.doc.user/images/Image_team_pref.png
deleted file mode 100644
index c006658..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image_team_pref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/accessibility_new_project.png b/bundles/org.eclipse.platform.doc.user/images/accessibility_new_project.png
deleted file mode 100644
index a863bf7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/accessibility_new_project.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/activity_menu.png b/bundles/org.eclipse.platform.doc.user/images/activity_menu.png
deleted file mode 100644
index 753d399..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/activity_menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/activity_toolbar.png b/bundles/org.eclipse.platform.doc.user/images/activity_toolbar.png
deleted file mode 100644
index 3070bdb..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/activity_toolbar.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/addbkmrk_co.png b/bundles/org.eclipse.platform.doc.user/images/addbkmrk_co.png
deleted file mode 100644
index 73580b2..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/addbkmrk_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/addbkmrk_tsk.png b/bundles/org.eclipse.platform.doc.user/images/addbkmrk_tsk.png
deleted file mode 100644
index fbb4cea..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/addbkmrk_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/addtask.png b/bundles/org.eclipse.platform.doc.user/images/addtask.png
deleted file mode 100644
index 8d42cbf..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/addtask.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/alpha_mode.png b/bundles/org.eclipse.platform.doc.user/images/alpha_mode.png
deleted file mode 100644
index 585fd8a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/alpha_mode.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/annotations-preferences.png b/bundles/org.eclipse.platform.doc.user/images/annotations-preferences.png
deleted file mode 100644
index bd96253..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/annotations-preferences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ant-view.png b/bundles/org.eclipse.platform.doc.user/images/ant-view.png
deleted file mode 100644
index baf86f1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ant-view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ant_code_assist.png b/bundles/org.eclipse.platform.doc.user/images/ant_code_assist.png
deleted file mode 100644
index 466f492..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ant_code_assist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ant_editor_appearance.png b/bundles/org.eclipse.platform.doc.user/images/ant_editor_appearance.png
deleted file mode 100644
index 7761036..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ant_editor_appearance.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ant_editor_folding.png b/bundles/org.eclipse.platform.doc.user/images/ant_editor_folding.png
deleted file mode 100644
index 36d2171..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ant_editor_folding.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ant_editor_problems.png b/bundles/org.eclipse.platform.doc.user/images/ant_editor_problems.png
deleted file mode 100644
index bd1d77e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ant_editor_problems.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ant_editor_syntax.png b/bundles/org.eclipse.platform.doc.user/images/ant_editor_syntax.png
deleted file mode 100644
index 2992a49..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ant_editor_syntax.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ant_formatter.png b/bundles/org.eclipse.platform.doc.user/images/ant_formatter.png
deleted file mode 100644
index 0f61905..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ant_formatter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ant_prefs.png b/bundles/org.eclipse.platform.doc.user/images/ant_prefs.png
deleted file mode 100644
index ebbe3e5..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ant_prefs.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ant_run_dialog.png b/bundles/org.eclipse.platform.doc.user/images/ant_run_dialog.png
deleted file mode 100644
index de5a01f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ant_run_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ant_runtime_properties.png b/bundles/org.eclipse.platform.doc.user/images/ant_runtime_properties.png
deleted file mode 100644
index 551cd46..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ant_runtime_properties.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ant_templates.png b/bundles/org.eclipse.platform.doc.user/images/ant_templates.png
deleted file mode 100644
index 60699a7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ant_templates.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ant_view.png b/bundles/org.eclipse.platform.doc.user/images/ant_view.png
deleted file mode 100644
index e9008e3..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ant_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/arch-npi.jpg b/bundles/org.eclipse.platform.doc.user/images/arch-npi.jpg
deleted file mode 100644
index 99e4170..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/arch-npi.jpg
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/backward_nav.png b/bundles/org.eclipse.platform.doc.user/images/backward_nav.png
deleted file mode 100644
index 8b022d1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/backward_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/bookmark_obj.png b/bundles/org.eclipse.platform.doc.user/images/bookmark_obj.png
deleted file mode 100644
index 42d2478..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/bookmark_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/build_exec.png b/bundles/org.eclipse.platform.doc.user/images/build_exec.png
deleted file mode 100644
index fdf4f82..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/build_exec.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cap-conf.png b/bundles/org.eclipse.platform.doc.user/images/cap-conf.png
deleted file mode 100644
index 98fce3a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cap-conf.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cap-pref-advanced.png b/bundles/org.eclipse.platform.doc.user/images/cap-pref-advanced.png
deleted file mode 100644
index 96d0330..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cap-pref-advanced.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cap-pref.png b/bundles/org.eclipse.platform.doc.user/images/cap-pref.png
deleted file mode 100644
index d28b42a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cap-pref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/capabilities.png b/bundles/org.eclipse.platform.doc.user/images/capabilities.png
deleted file mode 100644
index ef4ec8a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/capabilities.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/change.png b/bundles/org.eclipse.platform.doc.user/images/change.png
deleted file mode 100644
index 1a5a79d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/change.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cheatsheet_composite_running.png b/bundles/org.eclipse.platform.doc.user/images/cheatsheet_composite_running.png
deleted file mode 100644
index c96332f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cheatsheet_composite_running.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cheatsheet_composite_start.png b/bundles/org.eclipse.platform.doc.user/images/cheatsheet_composite_start.png
deleted file mode 100644
index ac96cf6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cheatsheet_composite_start.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/close_view.png b/bundles/org.eclipse.platform.doc.user/images/close_view.png
deleted file mode 100644
index f69be2f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/close_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/compare-editor.png b/bundles/org.eclipse.platform.doc.user/images/compare-editor.png
deleted file mode 100644
index 8ff1157..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/compare-editor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/confadd_ov.png b/bundles/org.eclipse.platform.doc.user/images/confadd_ov.png
deleted file mode 100644
index c5d4b6d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/confadd_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/confauto_ov.png b/bundles/org.eclipse.platform.doc.user/images/confauto_ov.png
deleted file mode 100644
index 03a4e30..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/confauto_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/confchg_ov.png b/bundles/org.eclipse.platform.doc.user/images/confchg_ov.png
deleted file mode 100644
index 806aad1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/confchg_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/confdel_ov.png b/bundles/org.eclipse.platform.doc.user/images/confdel_ov.png
deleted file mode 100644
index 8cfd1c1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/confdel_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/container_obj.png b/bundles/org.eclipse.platform.doc.user/images/container_obj.png
deleted file mode 100644
index d092562..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/container_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/content_type.png b/bundles/org.eclipse.platform.doc.user/images/content_type.png
deleted file mode 100644
index 5f79d56..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/content_type.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/contenttype-pref-charset.png b/bundles/org.eclipse.platform.doc.user/images/contenttype-pref-charset.png
deleted file mode 100644
index ba2020f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/contenttype-pref-charset.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/copy_edit.png b/bundles/org.eclipse.platform.doc.user/images/copy_edit.png
deleted file mode 100644
index a3d7188..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/copy_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cut_edit.png b/bundles/org.eclipse.platform.doc.user/images/cut_edit.png
deleted file mode 100644
index 3d32818..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cut_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-checkout1.png b/bundles/org.eclipse.platform.doc.user/images/cvs-checkout1.png
deleted file mode 100644
index ec54a4c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-checkout1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-checkout2.png b/bundles/org.eclipse.platform.doc.user/images/cvs-checkout2.png
deleted file mode 100644
index db1aab4..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-checkout2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-checkout3.png b/bundles/org.eclipse.platform.doc.user/images/cvs-checkout3.png
deleted file mode 100644
index 71fbb5f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-checkout3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-checkout4.png b/bundles/org.eclipse.platform.doc.user/images/cvs-checkout4.png
deleted file mode 100644
index e22e287..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-checkout4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-checkout5.png b/bundles/org.eclipse.platform.doc.user/images/cvs-checkout5.png
deleted file mode 100644
index d73e60f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-checkout5.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-connection.png b/bundles/org.eclipse.platform.doc.user/images/cvs-connection.png
deleted file mode 100644
index 7440ab7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-connection.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-console-prefs.png b/bundles/org.eclipse.platform.doc.user/images/cvs-console-prefs.png
deleted file mode 100644
index 11afd80..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-console-prefs.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-console.png b/bundles/org.eclipse.platform.doc.user/images/cvs-console.png
deleted file mode 100644
index d560816..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-console.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-decoration-general.png b/bundles/org.eclipse.platform.doc.user/images/cvs-decoration-general.png
deleted file mode 100644
index 8e226a7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-decoration-general.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-decoration-icon.png b/bundles/org.eclipse.platform.doc.user/images/cvs-decoration-icon.png
deleted file mode 100644
index 80a5d8b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-decoration-icon.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-decoration-text.png b/bundles/org.eclipse.platform.doc.user/images/cvs-decoration-text.png
deleted file mode 100644
index d775f79..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-decoration-text.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-ext.png b/bundles/org.eclipse.platform.doc.user/images/cvs-ext.png
deleted file mode 100644
index 5da1b35..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-ext.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-files.png b/bundles/org.eclipse.platform.doc.user/images/cvs-files.png
deleted file mode 100644
index d102801..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-files.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-general.png b/bundles/org.eclipse.platform.doc.user/images/cvs-general.png
deleted file mode 100644
index 8a7e5c5..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-general.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-merge-sync.png b/bundles/org.eclipse.platform.doc.user/images/cvs-merge-sync.png
deleted file mode 100644
index b4235fb..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-merge-sync.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-password.png b/bundles/org.eclipse.platform.doc.user/images/cvs-password.png
deleted file mode 100644
index cb96c5f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-password.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-prompting.png b/bundles/org.eclipse.platform.doc.user/images/cvs-prompting.png
deleted file mode 100644
index eda9079..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-prompting.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-share1.png b/bundles/org.eclipse.platform.doc.user/images/cvs-share1.png
deleted file mode 100644
index 298374d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-share1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-share2.png b/bundles/org.eclipse.platform.doc.user/images/cvs-share2.png
deleted file mode 100644
index 7ba1004..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-share2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-share3.png b/bundles/org.eclipse.platform.doc.user/images/cvs-share3.png
deleted file mode 100644
index a1f590f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-share3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-share4.png b/bundles/org.eclipse.platform.doc.user/images/cvs-share4.png
deleted file mode 100644
index 266144a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-share4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-ssh2-general.png b/bundles/org.eclipse.platform.doc.user/images/cvs-ssh2-general.png
deleted file mode 100644
index 7dad67a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-ssh2-general.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-ssh2-hosts.png b/bundles/org.eclipse.platform.doc.user/images/cvs-ssh2-hosts.png
deleted file mode 100644
index 6628900..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-ssh2-hosts.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-ssh2-key.png b/bundles/org.eclipse.platform.doc.user/images/cvs-ssh2-key.png
deleted file mode 100644
index eff0499..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-ssh2-key.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-ssh2-proxy.png b/bundles/org.eclipse.platform.doc.user/images/cvs-ssh2-proxy.png
deleted file mode 100644
index a86f74c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-ssh2-proxy.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-sync-compare.png b/bundles/org.eclipse.platform.doc.user/images/cvs-sync-compare.png
deleted file mode 100644
index 0c87739..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-sync-compare.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-watch-edit.png b/bundles/org.eclipse.platform.doc.user/images/cvs-watch-edit.png
deleted file mode 100644
index 9c493c9..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-watch-edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs_folder_rep.png b/bundles/org.eclipse.platform.doc.user/images/cvs_folder_rep.png
deleted file mode 100644
index a01ac81..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs_folder_rep.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs_module_rep.png b/bundles/org.eclipse.platform.doc.user/images/cvs_module_rep.png
deleted file mode 100644
index 235ec1e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs_module_rep.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs_synch.png b/bundles/org.eclipse.platform.doc.user/images/cvs_synch.png
deleted file mode 100644
index f446782..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs_synch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/debug_exec.png b/bundles/org.eclipse.platform.doc.user/images/debug_exec.png
deleted file mode 100644
index c76ecad..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/debug_exec.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/defaults_ps.png b/bundles/org.eclipse.platform.doc.user/images/defaults_ps.png
deleted file mode 100644
index 6fc29e6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/defaults_ps.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/delete_edit.png b/bundles/org.eclipse.platform.doc.user/images/delete_edit.png
deleted file mode 100644
index e93c632..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/delete_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/description.png b/bundles/org.eclipse.platform.doc.user/images/description.png
deleted file mode 100644
index bfff890..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/description.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/dirty_ov.png b/bundles/org.eclipse.platform.doc.user/images/dirty_ov.png
deleted file mode 100644
index 253d03d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/dirty_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/drop_bottom_source.png b/bundles/org.eclipse.platform.doc.user/images/drop_bottom_source.png
deleted file mode 100644
index aaa56d1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/drop_bottom_source.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/drop_invalid_source.png b/bundles/org.eclipse.platform.doc.user/images/drop_invalid_source.png
deleted file mode 100644
index 66e2b7a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/drop_invalid_source.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/drop_left_source.png b/bundles/org.eclipse.platform.doc.user/images/drop_left_source.png
deleted file mode 100644
index d009b50..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/drop_left_source.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/drop_offscreen.png b/bundles/org.eclipse.platform.doc.user/images/drop_offscreen.png
deleted file mode 100644
index 1c834f0..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/drop_offscreen.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/drop_right_source.png b/bundles/org.eclipse.platform.doc.user/images/drop_right_source.png
deleted file mode 100644
index 36ccf37..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/drop_right_source.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/drop_stack.png b/bundles/org.eclipse.platform.doc.user/images/drop_stack.png
deleted file mode 100644
index 813c553..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/drop_stack.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/drop_top_source.png b/bundles/org.eclipse.platform.doc.user/images/drop_top_source.png
deleted file mode 100644
index 49b9743..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/drop_top_source.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/e_maximize.png b/bundles/org.eclipse.platform.doc.user/images/e_maximize.png
deleted file mode 100644
index ee67ced..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/e_maximize.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/e_restore.png b/bundles/org.eclipse.platform.doc.user/images/e_restore.png
deleted file mode 100644
index b29a407..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/e_restore.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/e_show_all.png b/bundles/org.eclipse.platform.doc.user/images/e_show_all.png
deleted file mode 100644
index bd8803a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/e_show_all.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/e_synch_nav.png b/bundles/org.eclipse.platform.doc.user/images/e_synch_nav.png
deleted file mode 100644
index 9f7da5c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/e_synch_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/e_synch_toc_nav.png b/bundles/org.eclipse.platform.doc.user/images/e_synch_toc_nav.png
deleted file mode 100644
index ed24449..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/e_synch_toc_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/edited_ov.png b/bundles/org.eclipse.platform.doc.user/images/edited_ov.png
deleted file mode 100644
index fd40606..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/edited_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/et_dialog.png b/bundles/org.eclipse.platform.doc.user/images/et_dialog.png
deleted file mode 100644
index 5971985..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/et_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/et_dropdown.png b/bundles/org.eclipse.platform.doc.user/images/et_dropdown.png
deleted file mode 100644
index 5b6c135..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/et_dropdown.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/export_wiz.png b/bundles/org.eclipse.platform.doc.user/images/export_wiz.png
deleted file mode 100644
index f83ccda..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/export_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/external_tools.png b/bundles/org.eclipse.platform.doc.user/images/external_tools.png
deleted file mode 100644
index 5dfe6da..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/external_tools.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/external_tools_prefs.png b/bundles/org.eclipse.platform.doc.user/images/external_tools_prefs.png
deleted file mode 100644
index 0e6e020..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/external_tools_prefs.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/filter_ps.png b/bundles/org.eclipse.platform.doc.user/images/filter_ps.png
deleted file mode 100644
index ace1090..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/filter_ps.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/first_anteditor.png b/bundles/org.eclipse.platform.doc.user/images/first_anteditor.png
deleted file mode 100644
index cd849ca..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/first_anteditor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/forward_nav.png b/bundles/org.eclipse.platform.doc.user/images/forward_nav.png
deleted file mode 100644
index a6afdee..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/forward_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/gotoobj_tsk.png b/bundles/org.eclipse.platform.doc.user/images/gotoobj_tsk.png
deleted file mode 100644
index cc5e088..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/gotoobj_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_manifest.png b/bundles/org.eclipse.platform.doc.user/images/help_manifest.png
deleted file mode 100644
index b08a755..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_manifest.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_no_manifest.png b/bundles/org.eclipse.platform.doc.user/images/help_no_manifest.png
deleted file mode 100644
index 62e2c19..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_no_manifest.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_search_w.png b/bundles/org.eclipse.platform.doc.user/images/help_search_w.png
deleted file mode 100644
index c03e6a8..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_search_w.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/helpview-all.png b/bundles/org.eclipse.platform.doc.user/images/helpview-all.png
deleted file mode 100644
index a4ab9bd..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/helpview-all.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/helpview-bookmarks.png b/bundles/org.eclipse.platform.doc.user/images/helpview-bookmarks.png
deleted file mode 100644
index 056ca45..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/helpview-bookmarks.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/helpview-related.png b/bundles/org.eclipse.platform.doc.user/images/helpview-related.png
deleted file mode 100644
index 835cfaf..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/helpview-related.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/helpview-search.png b/bundles/org.eclipse.platform.doc.user/images/helpview-search.png
deleted file mode 100644
index e568877..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/helpview-search.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/home_nav.png b/bundles/org.eclipse.platform.doc.user/images/home_nav.png
deleted file mode 100644
index f06b685..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/home_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image618-add-ant-search.png b/bundles/org.eclipse.platform.doc.user/images/image618-add-ant-search.png
deleted file mode 100644
index 4ec3223..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image618-add-ant-search.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image618-add-ant.png b/bundles/org.eclipse.platform.doc.user/images/image618-add-ant.png
deleted file mode 100644
index e81a32c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image618-add-ant.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image618-ant-run.png b/bundles/org.eclipse.platform.doc.user/images/image618-ant-run.png
deleted file mode 100644
index c560bfb..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image618-ant-run.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-begin.png b/bundles/org.eclipse.platform.doc.user/images/image92-begin.png
deleted file mode 100644
index 6762771..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-begin.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-check.png b/bundles/org.eclipse.platform.doc.user/images/image92-check.png
deleted file mode 100644
index 867806f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-check.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-close.png b/bundles/org.eclipse.platform.doc.user/images/image92-close.png
deleted file mode 100644
index e97c452..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-close.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-collapse.png b/bundles/org.eclipse.platform.doc.user/images/image92-collapse.png
deleted file mode 100644
index a57ea8b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-collapse.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-complete.png b/bundles/org.eclipse.platform.doc.user/images/image92-complete.png
deleted file mode 100644
index cdaf558..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-complete.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-expand.png b/bundles/org.eclipse.platform.doc.user/images/image92-expand.png
deleted file mode 100644
index 8cb2274..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-expand.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-help.png b/bundles/org.eclipse.platform.doc.user/images/image92-help.png
deleted file mode 100644
index 787e064..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-help.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-hide.png b/bundles/org.eclipse.platform.doc.user/images/image92-hide.png
deleted file mode 100644
index f16ba73..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-hide.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-opencheat.png b/bundles/org.eclipse.platform.doc.user/images/image92-opencheat.png
deleted file mode 100644
index 9335d5c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-opencheat.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-perform.png b/bundles/org.eclipse.platform.doc.user/images/image92-perform.png
deleted file mode 100644
index 93e8f53..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-perform.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-redo.png b/bundles/org.eclipse.platform.doc.user/images/image92-redo.png
deleted file mode 100644
index c958d59..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-redo.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-restart.png b/bundles/org.eclipse.platform.doc.user/images/image92-restart.png
deleted file mode 100644
index d12507e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-restart.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-save.png b/bundles/org.eclipse.platform.doc.user/images/image92-save.png
deleted file mode 100644
index 61e5d54..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-save.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-select.png b/bundles/org.eclipse.platform.doc.user/images/image92-select.png
deleted file mode 100644
index 3c6c587..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-select.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-skip-mark.png b/bundles/org.eclipse.platform.doc.user/images/image92-skip-mark.png
deleted file mode 100644
index 73b7743..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-skip-mark.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-skip.png b/bundles/org.eclipse.platform.doc.user/images/image92-skip.png
deleted file mode 100644
index 0575d4d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-skip.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-tutorial.png b/bundles/org.eclipse.platform.doc.user/images/image92-tutorial.png
deleted file mode 100644
index 04a710f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-tutorial.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/import_wiz.png b/bundles/org.eclipse.platform.doc.user/images/import_wiz.png
deleted file mode 100644
index f65ecb2..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/import_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/keys1.png b/bundles/org.eclipse.platform.doc.user/images/keys1.png
deleted file mode 100644
index 62b74d3..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/keys1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/keys2.png b/bundles/org.eclipse.platform.doc.user/images/keys2.png
deleted file mode 100644
index 2acf4f1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/keys2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/keys6.png b/bundles/org.eclipse.platform.doc.user/images/keys6.png
deleted file mode 100644
index d2253a3..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/keys6.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/last_edit_pos.png b/bundles/org.eclipse.platform.doc.user/images/last_edit_pos.png
deleted file mode 100644
index 11391fc..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/last_edit_pos.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/mark_occurrences.png b/bundles/org.eclipse.platform.doc.user/images/mark_occurrences.png
deleted file mode 100644
index e4cb1d0..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/mark_occurrences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/max.png b/bundles/org.eclipse.platform.doc.user/images/max.png
deleted file mode 100644
index 3f57933..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/max.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/merged_ov.png b/bundles/org.eclipse.platform.doc.user/images/merged_ov.png
deleted file mode 100644
index b00a69b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/merged_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/minus.png b/bundles/org.eclipse.platform.doc.user/images/minus.png
deleted file mode 100644
index 9506d78..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/minus.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/new_persp.png b/bundles/org.eclipse.platform.doc.user/images/new_persp.png
deleted file mode 100644
index 18f50e0..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/new_persp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/new_wiz.png b/bundles/org.eclipse.platform.doc.user/images/new_wiz.png
deleted file mode 100644
index 80b3a54..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/new_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/newfile_wiz.png b/bundles/org.eclipse.platform.doc.user/images/newfile_wiz.png
deleted file mode 100644
index 356239b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/newfile_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/newfolder_wiz.png b/bundles/org.eclipse.platform.doc.user/images/newfolder_wiz.png
deleted file mode 100644
index 86a4f30..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/newfolder_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/newprj_wiz.png b/bundles/org.eclipse.platform.doc.user/images/newprj_wiz.png
deleted file mode 100644
index bbee775..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/newprj_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/next_nav.png b/bundles/org.eclipse.platform.doc.user/images/next_nav.png
deleted file mode 100644
index 0328357..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/next_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ngback.png b/bundles/org.eclipse.platform.doc.user/images/ngback.png
deleted file mode 100644
index 9e63522..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ngback.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ngnext.png b/bundles/org.eclipse.platform.doc.user/images/ngnext.png
deleted file mode 100644
index b250a0d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ngnext.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ngrelc.png b/bundles/org.eclipse.platform.doc.user/images/ngrelc.png
deleted file mode 100644
index 161e3aa..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ngrelc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ngrelr.png b/bundles/org.eclipse.platform.doc.user/images/ngrelr.png
deleted file mode 100644
index 4726f8c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ngrelr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ngrelt.png b/bundles/org.eclipse.platform.doc.user/images/ngrelt.png
deleted file mode 100644
index 74bee2b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ngrelt.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/no_remotedir_ov.png b/bundles/org.eclipse.platform.doc.user/images/no_remotedir_ov.png
deleted file mode 100644
index 2aa0e84..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/no_remotedir_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/open_persp.png b/bundles/org.eclipse.platform.doc.user/images/open_persp.png
deleted file mode 100644
index 47616cd..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/open_persp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/openseparate_co.png b/bundles/org.eclipse.platform.doc.user/images/openseparate_co.png
deleted file mode 100644
index 49a30bf..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/openseparate_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/add_co.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/add_co.png
deleted file mode 100644
index 01d1608..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/add_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/ant_targets.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/ant_targets.png
deleted file mode 100644
index 7d42ca5..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/ant_targets.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/properties.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/properties.png
deleted file mode 100644
index dedd6f7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/properties.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/refresh.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/refresh.png
deleted file mode 100644
index a3884fb..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/refresh.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/removeAll_co.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/removeAll_co.png
deleted file mode 100644
index ea14834..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/removeAll_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/remove_co.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/remove_co.png
deleted file mode 100644
index 8308efe..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/remove_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/run_tool.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/run_tool.png
deleted file mode 100644
index 5bd0e13..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/run_tool.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/search.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/search.png
deleted file mode 100644
index c549447..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/search.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/ctool16/external_tools.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/ctool16/external_tools.png
deleted file mode 100644
index 5dfe6da..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/ctool16/external_tools.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/cview16/ant_view.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/cview16/ant_view.png
deleted file mode 100644
index f304510..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/cview16/ant_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant.png
deleted file mode 100644
index cf88df0..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant_buildfile.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant_buildfile.png
deleted file mode 100644
index 653215a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant_buildfile.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant_target_err.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant_target_err.png
deleted file mode 100644
index e66c98e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant_target_err.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/build_tab.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/build_tab.png
deleted file mode 100644
index c87f431..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/build_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/classpath.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/classpath.png
deleted file mode 100644
index 0b5d271..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/classpath.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/defaulttarget_obj.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/defaulttarget_obj.png
deleted file mode 100644
index 1e3df57..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/defaulttarget_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/import_obj.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/import_obj.png
deleted file mode 100644
index 5bf4a40..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/import_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/invalid_build_tool.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/invalid_build_tool.png
deleted file mode 100644
index 0e02f53..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/invalid_build_tool.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/jar_l_obj.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/jar_l_obj.png
deleted file mode 100644
index 281b5e8..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/jar_l_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/macrodef_obj.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/macrodef_obj.png
deleted file mode 100644
index 365cfbb..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/macrodef_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/main_tab.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/main_tab.png
deleted file mode 100644
index 2cbe988..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/main_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/prop_ps.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/prop_ps.png
deleted file mode 100644
index dedd6f7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/prop_ps.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/property_obj.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/property_obj.png
deleted file mode 100644
index 7841e76..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/property_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/targetinternal_obj.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/targetinternal_obj.png
deleted file mode 100644
index 4e10cf4..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/targetinternal_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/targetpublic_obj.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/targetpublic_obj.png
deleted file mode 100644
index 705a33e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/targetpublic_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/task_obj.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/task_obj.png
deleted file mode 100644
index 0a915c6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/task_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/type.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/type.png
deleted file mode 100644
index 9fd1b3f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/type.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/outline_hello.png b/bundles/org.eclipse.platform.doc.user/images/outline_hello.png
deleted file mode 100644
index 725f311..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/outline_hello.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/paste_edit.png b/bundles/org.eclipse.platform.doc.user/images/paste_edit.png
deleted file mode 100644
index b66e9dd..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/paste_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/performanceview.png b/bundles/org.eclipse.platform.doc.user/images/performanceview.png
deleted file mode 100644
index a489782..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/performanceview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/pin_editor.png b/bundles/org.eclipse.platform.doc.user/images/pin_editor.png
deleted file mode 100644
index 903588d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/pin_editor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/pin_view.png b/bundles/org.eclipse.platform.doc.user/images/pin_view.png
deleted file mode 100644
index d2913c2..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/pin_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/prbfil.png b/bundles/org.eclipse.platform.doc.user/images/prbfil.png
deleted file mode 100644
index 56b8a0c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/prbfil.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/pref_helpserver.png b/bundles/org.eclipse.platform.doc.user/images/pref_helpserver.png
deleted file mode 100644
index 8b4963d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/pref_helpserver.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/prev_nav.png b/bundles/org.eclipse.platform.doc.user/images/prev_nav.png
deleted file mode 100644
index 830c2c9..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/prev_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/print_edit.png b/bundles/org.eclipse.platform.doc.user/images/print_edit.png
deleted file mode 100644
index 1d46567..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/print_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/printer.png b/bundles/org.eclipse.platform.doc.user/images/printer.png
deleted file mode 100644
index 7a11f9c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/printer.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/prob.png b/bundles/org.eclipse.platform.doc.user/images/prob.png
deleted file mode 100644
index c95d01f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/prob.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/question_ov.png b/bundles/org.eclipse.platform.doc.user/images/question_ov.png
deleted file mode 100644
index 921a272..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/question_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/r_inadd_ov.png b/bundles/org.eclipse.platform.doc.user/images/r_inadd_ov.png
deleted file mode 100644
index c69417d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/r_inadd_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/r_inchg_ov.png b/bundles/org.eclipse.platform.doc.user/images/r_inchg_ov.png
deleted file mode 100644
index 995e896..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/r_inchg_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/r_indel_ov.png b/bundles/org.eclipse.platform.doc.user/images/r_indel_ov.png
deleted file mode 100644
index 050859a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/r_indel_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/r_outadd_ov.png b/bundles/org.eclipse.platform.doc.user/images/r_outadd_ov.png
deleted file mode 100644
index 2a919c8..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/r_outadd_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/r_outchg_ov.png b/bundles/org.eclipse.platform.doc.user/images/r_outchg_ov.png
deleted file mode 100644
index 2a126be..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/r_outchg_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/r_outdel_ov.png b/bundles/org.eclipse.platform.doc.user/images/r_outdel_ov.png
deleted file mode 100644
index 8ea3b58..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/r_outdel_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/redo_edit.png b/bundles/org.eclipse.platform.doc.user/images/redo_edit.png
deleted file mode 100644
index 4442683..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/redo_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-1.png b/bundles/org.eclipse.platform.doc.user/images/ref-1.png
deleted file mode 100644
index 666a5ec..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-10.png b/bundles/org.eclipse.platform.doc.user/images/ref-10.png
deleted file mode 100644
index 0430baa..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-10.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-11.png b/bundles/org.eclipse.platform.doc.user/images/ref-11.png
deleted file mode 100644
index fddcb8c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-11.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-12.png b/bundles/org.eclipse.platform.doc.user/images/ref-12.png
deleted file mode 100644
index 835714b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-12.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-15.png b/bundles/org.eclipse.platform.doc.user/images/ref-15.png
deleted file mode 100644
index 0c63917..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-15.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-16.png b/bundles/org.eclipse.platform.doc.user/images/ref-16.png
deleted file mode 100644
index 7be849e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-16.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-17.png b/bundles/org.eclipse.platform.doc.user/images/ref-17.png
deleted file mode 100644
index 60c9c4b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-17.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-18.png b/bundles/org.eclipse.platform.doc.user/images/ref-18.png
deleted file mode 100644
index bd6fce8..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-18.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-2.png b/bundles/org.eclipse.platform.doc.user/images/ref-2.png
deleted file mode 100644
index bf3dd39..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-20.png b/bundles/org.eclipse.platform.doc.user/images/ref-20.png
deleted file mode 100644
index 6cb6b84..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-20.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-21.png b/bundles/org.eclipse.platform.doc.user/images/ref-21.png
deleted file mode 100644
index de00eec..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-21.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-22.png b/bundles/org.eclipse.platform.doc.user/images/ref-22.png
deleted file mode 100644
index 68759f9..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-22.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-23.png b/bundles/org.eclipse.platform.doc.user/images/ref-23.png
deleted file mode 100644
index 0a2fa7f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-23.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-24.png b/bundles/org.eclipse.platform.doc.user/images/ref-24.png
deleted file mode 100644
index 77a4a7e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-24.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-25.png b/bundles/org.eclipse.platform.doc.user/images/ref-25.png
deleted file mode 100644
index 28d36eb..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-25.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-27.png b/bundles/org.eclipse.platform.doc.user/images/ref-27.png
deleted file mode 100644
index 5d7b932..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-27.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-3.png b/bundles/org.eclipse.platform.doc.user/images/ref-3.png
deleted file mode 100644
index 67389bf..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-4.png b/bundles/org.eclipse.platform.doc.user/images/ref-4.png
deleted file mode 100644
index 7655e93..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-5.png b/bundles/org.eclipse.platform.doc.user/images/ref-5.png
deleted file mode 100644
index dfa9678..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-5.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-50.png b/bundles/org.eclipse.platform.doc.user/images/ref-50.png
deleted file mode 100644
index 9126bcf..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-50.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-52.png b/bundles/org.eclipse.platform.doc.user/images/ref-52.png
deleted file mode 100644
index 497459a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-52.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-7.png b/bundles/org.eclipse.platform.doc.user/images/ref-7.png
deleted file mode 100644
index 2efb270..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-7.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-79.png b/bundles/org.eclipse.platform.doc.user/images/ref-79.png
deleted file mode 100644
index 4d4b6e1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-79.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-8.png b/bundles/org.eclipse.platform.doc.user/images/ref-8.png
deleted file mode 100644
index 7ab4f6e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-8.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-81.png b/bundles/org.eclipse.platform.doc.user/images/ref-81.png
deleted file mode 100644
index f25c89d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-81.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-9.png b/bundles/org.eclipse.platform.doc.user/images/ref-9.png
deleted file mode 100644
index 2bb8b3d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-9.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-accessibility.png b/bundles/org.eclipse.platform.doc.user/images/ref-accessibility.png
deleted file mode 100644
index fd58dc2..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-accessibility.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-annotationspref.png b/bundles/org.eclipse.platform.doc.user/images/ref-annotationspref.png
deleted file mode 100644
index 952e06c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-annotationspref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-quickdiffpref.png b/bundles/org.eclipse.platform.doc.user/images/ref-quickdiffpref.png
deleted file mode 100644
index 3208f84..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-quickdiffpref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-spellingpref.png b/bundles/org.eclipse.platform.doc.user/images/ref-spellingpref.png
deleted file mode 100644
index 5f3dda9..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-spellingpref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-texteditorpref.png b/bundles/org.eclipse.platform.doc.user/images/ref-texteditorpref.png
deleted file mode 100644
index 4d00095..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-texteditorpref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-webbrowserpref.png b/bundles/org.eclipse.platform.doc.user/images/ref-webbrowserpref.png
deleted file mode 100644
index 65ad108..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-webbrowserpref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/refresh_nav.png b/bundles/org.eclipse.platform.doc.user/images/refresh_nav.png
deleted file mode 100644
index e920f9b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/refresh_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/res.png b/bundles/org.eclipse.platform.doc.user/images/res.png
deleted file mode 100644
index 8327b7f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/res.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/res_blocked.png b/bundles/org.eclipse.platform.doc.user/images/res_blocked.png
deleted file mode 100644
index 82b7a72..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/res_blocked.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/res_build.png b/bundles/org.eclipse.platform.doc.user/images/res_build.png
deleted file mode 100644
index e901cc6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/res_build.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/res_details.png b/bundles/org.eclipse.platform.doc.user/images/res_details.png
deleted file mode 100644
index ea023b0..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/res_details.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/res_otherjobs.png b/bundles/org.eclipse.platform.doc.user/images/res_otherjobs.png
deleted file mode 100644
index ed05cfa..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/res_otherjobs.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/res_pref.png b/bundles/org.eclipse.platform.doc.user/images/res_pref.png
deleted file mode 100644
index 0ad2537..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/res_pref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/run_exec.png b/bundles/org.eclipse.platform.doc.user/images/run_exec.png
deleted file mode 100644
index 5bd0e13..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/run_exec.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/save_edit.png b/bundles/org.eclipse.platform.doc.user/images/save_edit.png
deleted file mode 100644
index 5f0fb5b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/save_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/saveall_edit.png b/bundles/org.eclipse.platform.doc.user/images/saveall_edit.png
deleted file mode 100644
index eeea6be..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/saveall_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/saveas_edit.png b/bundles/org.eclipse.platform.doc.user/images/saveas_edit.png
deleted file mode 100644
index 5c364cf..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/saveas_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/search_src.png b/bundles/org.eclipse.platform.doc.user/images/search_src.png
deleted file mode 100644
index c549447..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/search_src.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/searchm_obj.png b/bundles/org.eclipse.platform.doc.user/images/searchm_obj.png
deleted file mode 100644
index 5a2a75a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/searchm_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/segment_edit.png b/bundles/org.eclipse.platform.doc.user/images/segment_edit.png
deleted file mode 100644
index aa0dc0b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/segment_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/sinfocenter_obj.png b/bundles/org.eclipse.platform.doc.user/images/sinfocenter_obj.png
deleted file mode 100644
index 54c089d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/sinfocenter_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/slocalhelp_obj.png b/bundles/org.eclipse.platform.doc.user/images/slocalhelp_obj.png
deleted file mode 100644
index a32d1a7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/slocalhelp_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/stop_nav.png b/bundles/org.eclipse.platform.doc.user/images/stop_nav.png
deleted file mode 100644
index c42305a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/stop_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/sweb_obj.png b/bundles/org.eclipse.platform.doc.user/images/sweb_obj.png
deleted file mode 100644
index 5017276..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/sweb_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/synced.png b/bundles/org.eclipse.platform.doc.user/images/synced.png
deleted file mode 100644
index b2e9aa4..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/synced.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/synch_participants.png b/bundles/org.eclipse.platform.doc.user/images/synch_participants.png
deleted file mode 100644
index 6cf2deb..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/synch_participants.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/tasks-1.png b/bundles/org.eclipse.platform.doc.user/images/tasks-1.png
deleted file mode 100644
index 666a5ec..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/tasks-1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/tasks-3.png b/bundles/org.eclipse.platform.doc.user/images/tasks-3.png
deleted file mode 100644
index 67389bf..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/tasks-3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/tasks-7.png b/bundles/org.eclipse.platform.doc.user/images/tasks-7.png
deleted file mode 100644
index 83d3692..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/tasks-7.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/tasks-96b-module_rep.png b/bundles/org.eclipse.platform.doc.user/images/tasks-96b-module_rep.png
deleted file mode 100644
index 6a2bfa8..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/tasks-96b-module_rep.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/team-file-content.png b/bundles/org.eclipse.platform.doc.user/images/team-file-content.png
deleted file mode 100644
index 0eedb7a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/team-file-content.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/team-ignore.png b/bundles/org.eclipse.platform.doc.user/images/team-ignore.png
deleted file mode 100644
index 2bf4716..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/team-ignore.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/team-prefs.png b/bundles/org.eclipse.platform.doc.user/images/team-prefs.png
deleted file mode 100644
index 7a6600c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/team-prefs.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/team_contents_icon.png b/bundles/org.eclipse.platform.doc.user/images/team_contents_icon.png
deleted file mode 100644
index e27b59d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/team_contents_icon.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/toc_closed.png b/bundles/org.eclipse.platform.doc.user/images/toc_closed.png
deleted file mode 100644
index 3f1da0f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/toc_closed.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/toc_open.png b/bundles/org.eclipse.platform.doc.user/images/toc_open.png
deleted file mode 100644
index ac3129c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/toc_open.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/topic_small.png b/bundles/org.eclipse.platform.doc.user/images/topic_small.png
deleted file mode 100644
index b790314..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/topic_small.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/tree_mode.png b/bundles/org.eclipse.platform.doc.user/images/tree_mode.png
deleted file mode 100644
index e72e897..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/tree_mode.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/undo_edit.png b/bundles/org.eclipse.platform.doc.user/images/undo_edit.png
deleted file mode 100644
index adbf2e1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/undo_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/up_nav.png b/bundles/org.eclipse.platform.doc.user/images/up_nav.png
deleted file mode 100644
index d7c890c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/up_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/version_controlled.png b/bundles/org.eclipse.platform.doc.user/images/version_controlled.png
deleted file mode 100644
index ed401bd..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/version_controlled.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/view_menu.png b/bundles/org.eclipse.platform.doc.user/images/view_menu.png
deleted file mode 100644
index 3fae7f5..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/view_menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/viewer.png b/bundles/org.eclipse.platform.doc.user/images/viewer.png
deleted file mode 100644
index e93d5b6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/viewer.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/win_only.png b/bundles/org.eclipse.platform.doc.user/images/win_only.png
deleted file mode 100644
index 7523f99..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/win_only.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/xml.png b/bundles/org.eclipse.platform.doc.user/images/xml.png
deleted file mode 100644
index 2460b22..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/xml.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/no_help_exists.htm b/bundles/org.eclipse.platform.doc.user/no_help_exists.htm
deleted file mode 100644
index 07ccd50..0000000
--- a/bundles/org.eclipse.platform.doc.user/no_help_exists.htm
+++ /dev/null

@@ -1,21 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE> No Help Exists</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-No Help Exists</H1>
-<p CLASS="Head">There are no available help topics associated with this
-item.&nbsp;&nbsp;&nbsp;</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/notices.html b/bundles/org.eclipse.platform.doc.user/notices.html
deleted file mode 100644
index 03ff544..0000000
--- a/bundles/org.eclipse.platform.doc.user/notices.html
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <LINK REL="STYLESHEET" HREF="book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Legal Notices</title>
-</head>
-<body>
-
-<h3>
-<a NAME="Notices"></a>Notices</h3>
-<p>
-The material in this guide is Copyright (c) IBM Corporation and others 2000, 2005.
-</p>
-<p>
-<a href="about.html">Terms and conditions regarding the use of this guide.</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/plugin.properties b/bundles/org.eclipse.platform.doc.user/plugin.properties
deleted file mode 100644
index bb84e10..0000000
--- a/bundles/org.eclipse.platform.doc.user/plugin.properties
+++ /dev/null

@@ -1,12 +0,0 @@
-###############################################################################
-# Copyright (c) 2000, 2004 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-# 
-# Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-pluginName=Eclipse Workbench User Guide
-providerName=Eclipse.org

diff --git a/bundles/org.eclipse.platform.doc.user/plugin.xml b/bundles/org.eclipse.platform.doc.user/plugin.xml
deleted file mode 100644
index b85f7d3..0000000
--- a/bundles/org.eclipse.platform.doc.user/plugin.xml
+++ /dev/null

@@ -1,102 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?eclipse version="3.0"?>
-
-<!-- ===================================================== -->
-<!-- Declare the documentation for the Platform User Guide  -->
-<!-- We will declare only one infoset (book)               -->
-<!-- ===================================================== -->
-
-<plugin>
-
-
-<!-- ============================================================================= -->
-<!-- Define primary TOC                                                            -->
-<!-- ============================================================================= -->
-
-   <extension point="org.eclipse.help.toc">
-       <toc file="toc.xml" primary="true" />
-       <index path="index"/>
-   </extension>
-
-<!-- ============================================================================= -->
-<!-- Define TOCs                                                                   -->
-<!-- ============================================================================= -->
-
-   <extension point="org.eclipse.help.toc">
-       <toc file="topics_GettingStarted.xml" />
-       <toc file="topics_Concepts.xml" />
-       <toc file="topics_Tasks.xml" />
-       <toc file="topics_Reference.xml" />
-   </extension>
-
-<!-- ============================================================================= -->
-<!-- F1 context files                                                              -->
-<!-- ============================================================================= -->
-
-   <extension point="org.eclipse.help.contexts"> 
-       <contexts file="contexts_Workbench.xml" plugin="org.eclipse.ui"/> 
-   </extension>
-   
-    <extension point="org.eclipse.help.contexts"> 
-       <contexts file="contexts_Workbench.xml" plugin="org.eclipse.ui.ide"/> 
-   </extension>
-
-   <extension point="org.eclipse.help.contexts"> 
-       <contexts file="contexts_Workbench.xml" plugin="org.eclipse.ui.workbench.texteditor"/> 
-   </extension>
-
-   <extension point="org.eclipse.help.contexts"> 
-       <contexts file="contexts_Workbench.xml" plugin="org.eclipse.ui.editors"/> 
-   </extension>
-   
-   <extension point="org.eclipse.help.contexts">
-   		<contexts file="contexts_ExternalTools.xml" plugin="org.eclipse.ui.externaltools"/>
-   </extension>
-
-   <extension point="org.eclipse.help.contexts"> 
-       <contexts file="contexts_Workbench.xml" plugin="org.eclipse.ui.browser"/> 
-   </extension>
-
-   <extension point="org.eclipse.help.contexts">
-   		<contexts file="contexts_AntUI.xml" plugin="org.eclipse.ant.ui"/>
-   </extension>
-
-   <extension point="org.eclipse.help.contexts"> 
-       <contexts file="contexts_Team.xml" plugin="org.eclipse.team.ui"/> 
-   </extension>
-
-   <extension point="org.eclipse.help.contexts"> 
-       <contexts file="contexts_Team_CVS.xml" plugin="org.eclipse.team.cvs.ui"/> 
-   </extension>
-
-	<extension point="org.eclipse.help.contexts"> 
-		<contexts file="contexts_Compare.xml" plugin="org.eclipse.compare"/> 
-	</extension>
-   
-   <extension point="org.eclipse.help.contexts"> 
-      <contexts file="contexts_Search.xml" plugin="org.eclipse.search"/> 
-   </extension>
-   
-	<extension point="org.eclipse.help.contexts"> 
-		<contexts file="contexts_Update.xml"  plugin="org.eclipse.update.ui"/> 
-	</extension>
-
-	<extension point="org.eclipse.help.contexts"> 
-		<contexts file="contexts_Help.xml"  plugin="org.eclipse.help.ui"/> 
-	</extension>
-
-<!-- ============================================================================= -->
-<!-- Dynamic Content                                                               -->
-<!-- ============================================================================= -->
-
-    <extension
-          point="org.eclipse.help.contentProducer">
-       <binding producerId="org.eclipse.help.dynamic"/>
-    </extension>
-    
-    <extension
-          point="org.eclipse.help.base.luceneSearchParticipants">
-       <binding participantId="org.eclipse.help.base.xhtml"/>
-    </extension>
-
-</plugin>

diff --git a/bundles/org.eclipse.platform.doc.user/quickstart.htm b/bundles/org.eclipse.platform.doc.user/quickstart.htm
deleted file mode 100644
index 7601965..0000000
--- a/bundles/org.eclipse.platform.doc.user/quickstart.htm
+++ /dev/null

@@ -1,359 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title> Quick Start Guide</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Quick Start Guide</H1>
-<P>This tutorial introduces you to the Workbench, providing a brief overview of 
-  the steps required to create simple applications. More extensive explanations, 
-  including images, are available in the Workbench User Guide.</P>
-<P><strong>Workbench Quick Start</strong></P>
-<table width="75%" border="1">
-  <tr> 
-    <td width="32%"><strong>Task</strong></td>
-    <td width="68%"><strong>Description</strong></td>
-  </tr>
-  <tr> 
-    <td><p>Create a Simple Project</p>
-      <p>&nbsp;</p>
-      <p>&nbsp;</p></td>
-    <td><ol>
-        <li>Select <strong>File &gt; New &gt; Project...</strong>.</li>
-        <li>In the New Project wizard, select <strong>Simple &gt; Project </strong>then 
-          click <strong>Next</strong>. </li>
-        <li>In the <strong>Project name </strong>field type a name for your new 
-          project.</li>
-        <li> 
-          <p>Specify a location for the project or use the default. </p>
-        </li>
-        <li> 
-          <p>Click <strong>Finish</strong>.</p>
-        </li>
-      </ol></td>
-  </tr>
-  <tr> 
-    <td><p>Create a Folder</p>
-      <p>&nbsp;</p>
-      <p>&nbsp;</p></td>
-    <td> <ol>
-        <li>Ensure one or more projects exist.</li>
-        <li>Select <strong>File &gt; New &gt; Folder</strong>.</li>
-        <li>In the <strong>Folder name </strong>field of the New Folder wizard, 
-          type a name for your new folder.</li>
-        <li>Click <strong>Finish</strong>.</li>
-      </ol></td>
-  </tr>
-  <tr> 
-    <td><p>Create a File</p>
-      <p>&nbsp;</p></td>
-    <td><ol>
-        <li>Ensure one or more projects exist.</li>
-        <li>Select <strong>File &gt; New &gt; File</strong>.</li>
-        <li>In the <strong>File name </strong>field of the New Folder wizard, 
-          type a name for your new folder.</li>
-        <li>Click <strong>Finish</strong>.</li>
-      </ol></td>
-  </tr>
-  <tr> 
-    <td><p>Import Resources</p>
-      <p>&nbsp;</p>
-      <p>&nbsp;</p></td>
-    <td><ol>
-        <li>Select <strong>File &gt; Import</strong>.</li>
-        <li>Select an import source.</li>
-        <li>Click <strong>Next</strong>.</li>
-        <li>Select the import location containing the resource by following the 
-          steps indicated in the applicable wizard.</li>
-        <li>Click <strong>Finish</strong>.</li>
-      </ol></td>
-  </tr>
-  <tr> 
-    <td><p>Export Resources</p>
-      <p>&nbsp;</p>
-      <p>&nbsp;</p></td>
-    <td><ol>
-        <li>Select <strong>File &gt; Export</strong>.</li>
-        <li>Select an export destination.</li>
-        <li>Click <strong>Next</strong>.</li>
-        <li> Select the export destination by following the steps indicated in 
-          the applicable wizard.</li>
-        <li>Click <strong>Finish</strong>.</li>
-      </ol></td>
-  </tr>
-  <tr> 
-    <td>Create a Java Project: JUnit example</td>
-    <td><ol>
-        <li>To download the JUnit source code, visit http://www.eclipse.org/downloads/ 
-          and locate the Eclipse release that you are working with. </li>
-        <li>Scroll down to the Example Plug-ins section and download the examples 
-          archive. </li>
-        <li> Extract the contents of the Zip file to a directory. </li>
-        <li>Return to Eclipse and select <strong>File &gt; New &gt; Project...</strong>.</li>
-        <li> Select <strong>Java Project </strong>then click <strong>Next</strong>. 
-        </li>
-        <li>In the <strong>Project name</strong> field type <strong>JUnit</strong>.</li>
-        <li>Click <strong>Finish</strong>.</li>
-        <li>In the Package Explorer, make sure that the JUnit project is selected. 
-        </li>
-        <li>Select the menu item <strong>File &gt; Import...</strong>. </li>
-        <li>Select Zip file, then click <strong>Next</strong>.</li>
-        <li> Click <strong>Browse </strong>next to the Zip file field and browse 
-          to select &lt;ExamplesDownloadPath&gt;eclipse/plugins/org.eclipse.jdt.ui.examples.projects_3.0.0/archive/junit/junit381src.jar.</li>
-        <li> 
-          <p>In the Import wizard, below the hierarchy list click <strong>Select 
-            All</strong>. </p>
-        </li>
-        <li> 
-          <p>Once the JUnit project appears in the destination <strong>Folder 
-            </strong>field click <strong>Finish</strong>. </p>
-        </li>
-        <li> 
-          <p>In the import progress indicator, notice that the imported resources 
-            are compiled as they are imported into the workbench. This is because 
-            the <strong>Build automatically </strong>option is checked on the 
-            Workbench preferences page. You will be prompted to overwrite the 
-            .classpath and .project files in the JUnit project. This is because 
-            the .classpath resource was created for you when you created the JUnit 
-            project. It is safe to overwrite these files. <br>
-            In the Package Explorer view, expand the JUnit project to view the 
-            JUnit packages. </p>
-        </li>
-      </ol></td>
-  </tr>
-  <tr> 
-    <td>Create a Java Class: JUnit Example</td>
-    <td> <ol>
-        <li> In the Package Explorer view, right-click the JUnit project, select 
-          <strong>New &gt; Package</strong>.</li>
-        <li> In the <strong>Name</strong> field, type <strong>test</strong> as 
-          the name for the new package. </li>
-        <li>Click<strong> Finish</strong>. </li>
-        <li>In the Package Explorer view, select the new test package and click 
-          <strong>New Java Class </strong>in the toolbar. Make sure that <strong>JUnit</strong> 
-          appears in the Source Folder field and that <strong>test</strong> appears 
-          in the Package field.</li>
-        <li> In the Name field, type <strong>MyTestCase</strong>.</li>
-        <li>Next to the <strong>Superclass </strong>field, click <strong>Browse</strong>. 
-        </li>
-        <li>In the <strong>Choose a type </strong>field in the Superclass Selection 
-          dialog, type <strong>Test </strong>to narrow the list of available superclasses. 
-        </li>
-        <li>Select the <strong>TestCase</strong> class and click <strong>OK</strong>. 
-        </li>
-        <li>Select the checkbox for <strong>Constructors from superclass</strong>. 
-        </li>
-        <li> Click <strong>Finish</strong>.</li>
-        <li>The new file is opened in the editor. In the Outline view select the 
-          new class <strong>MyTestCase</strong>. Open the context menu and select 
-          <strong>Source &gt; Override/Implement Methods...</strong>.</li>
-        <li>In the Override Methods dialog, check <strong>setUp()</strong> and 
-          <strong>tearDown()</strong> and click <strong>OK.</strong> </li>
-        <li>Change the body of <strong>setUp()</strong> to container= new Vector();.</li>
-        <li><strong> container </strong>and <strong>Vector </strong>are underlined 
-          with a problem highlight line as they cannot be resolved. A light bulb 
-          appears on the marker bar. Set the cursor inside Vector and press Ctrl+1 
-          (or use <strong>Edit &gt; Quick Fix from the menu bar</strong>). Choose 
-          <strong>Import 'Vector' (java.util)</strong>.This adds the missing import 
-          declaration. </li>
-        <li>Set the cursor inside <strong>container </strong>and press Ctrl+1. 
-          Choose <strong>Create field 'container' </strong>to add the new field. 
-        </li>
-        <li>In the Outline view, select the class <strong>MyTestCase</strong>. 
-          Open the context menu and select <strong>Source &gt; Generate Getter 
-          and Setter...</strong>.</li>
-        <li> The Generate Getter and Setter dialog suggests that you create the 
-          methods getContainer and setContainer. Select both and click <strong>OK</strong>. 
-          A getter and setter method for the field container are added.</li>
-        <li>Save the file.</li>
-        <li> The formatting of generated code can be configured in <strong>Window 
-          &gt; Preferences &gt; Java &gt; Code Style &gt; Code Formatter</strong>. 
-          If you use a prefix or suffix for field names, you can specify this 
-          in <strong>Window &gt; Preferences &gt; Java &gt; Code Style &gt; Fields</strong> 
-          so that generated getters and setters will suggest method names without 
-          the prefix or suffix. </li>
-      </ol></td>
-  </tr>
-  <tr> 
-    <td> 
-      <p>&nbsp;</p>
-      <p>Launch a Java Program: JUnit Example</p></td>
-    <td>
-<ol>
-        <li>In the Package Explorer view, <strong>find junit.textui.TestRunner.java</strong> 
-          and double-click it to open it in an editor. </li>
-        <li><em>In the Outline view, notice that the TestRunner class has an icon 
-          which indicates that the class defines a main method.</em></li>
-        <li>Right-click <strong>TestRunner.java </strong>in the Package Explorer 
-          and select <strong>Run &gt; Java Application</strong>.</li>
-        <li>Select <strong>Run &gt; Run...</strong>. The Launch Configurations 
-          dialog opens with the TestRunner launch configuration selected. </li>
-        <li> In the Launch Configurations dialog select the <strong>Arguments 
-          </strong>tab and type <strong>junit.samples.VectorTest</strong> in the 
-          Program arguments area. </li>
-        <li>Click <strong>Run</strong>. This time the program runs correctly, 
-          indicating the number of tests that were run. </li>
-        <li>Switch to the Debug perspective. In the Debug view, notice that a 
-          process for the last program launch was registered when the program 
-          was run.</li>
-        <li>Click <strong>Run </strong>in the workbench toolbar. This list contains 
-          the previously launched programs. These programs can be relaunched by 
-          selecting them in the history list. </li>
-        <li>From the context menu in the Debug view (or the equivalent toolbar 
-          button), select <strong>Remove All Terminated</strong> to clear the 
-          view of terminated launch processes. </li>
-      </ol></td>
-  </tr>
-  <tr> 
-    <td> 
-      <p>Create a </p>
-      <p>Plug-in</p></td>
-    <td>
-<ol>
-        <li>Select <strong>File &gt; New &gt; Project</strong>.</li>
-        <li>Select <strong>Plug-in Project</strong> and click <strong>Next</strong>.</li>
-        <li>In the <strong>Project name</strong> field, type a name for your project 
-          and click <strong>Next</strong>.</li>
-        <li>In the <strong>Plug-in Content </strong>page, set the data with which 
-          the plugin.xml file will be initialized, including the plug-in ID, version 
-          and name.</li>
-        <li>Select an available template and click <strong>Next</strong>.</li>
-        <li>Customize the sample extension and click <strong>Finish</strong>. 
-        </li>
-      </ol>
-      </td>
-  </tr>
-  <tr> 
-    <td>Launch an Eclipse runtime workbench instance to test a plug-in</td>
-    <td>
-<ol>
-        <li>Select <strong>Run &gt; Run...</strong>. </li>
-        <li>In the Launch Configuration dialog, type a name for your configuration 
-          in the <strong>Name</strong> field.</li>
-        <li>In the <strong>Workspace data </strong>field, click <strong>Browse</strong> 
-          to define the workspace that will be used by the run-time workbench. 
-          The location of this runtime workspace must be different from the workspace 
-          of your host instance.</li>
-        <li>In the <strong>Run an application</strong> field select the default 
-          Eclipse application <strong>org.eclipse.ui.ide.workbench</strong>.</li>
-        <li>Click <strong>Run.</strong></li>
-      </ol>
-      <p>A second workbench instance will appear whose constituent plug-ins are 
-        the workspace plug-ins and the plug-ins selected on the Target Platform 
-        preference page. You can test your runtime workbench using the JRE of 
-        your choice and does not have to be the same one against which your plug-ins 
-        compile in the workspace. You can also specify any VM arguments that are 
-        appropriate for your testing. </p>
-      </td>
-  </tr>
-  <tr> 
-    <td>Automatically performing builds </td>
-    <td> <ol>
-        <li>Select <strong>Window &gt; Preferences</strong>.</li>
-        <li>Select the <strong>General </strong>category in the left pane.</li>
-        <li> Select <strong>Build automatically</strong>. </li>
-        <li>Click <strong>OK</strong>. </li>
-      </ol></td>
-  </tr>
-  <tr> 
-    <td>Manually performing builds </td>
-    <td><ol>
-        <li>In the Navigator view of the Resource perspective, select one or more 
-          projects. </li>
-        <li>Right-click and select the option <strong>Build Project </strong>from 
-          the pop-up menu. </li>
-      </ol></td>
-  </tr>
-</table>
-<P><strong>CVS Quick Start</strong></P>
-<P><strong>Note:</strong> A CVS server must already be configured on the host 
-  machine to create a valid repository location in the Workbench.</P>
-<table width="75%" border="1">
-  <tr> 
-    <td width="32%"><strong>Task</strong></td>
-    <td width="68%"><strong>Description</strong></td>
-  </tr>
-  <tr> 
-    <td> <p>Creating a CVS repository location</p>
-      <p>&nbsp;</p></td>
-    <td><ol>
-        <li>Select <strong>Window &gt; Show View &gt; Other... </strong> </li>
-        <li>Select <strong>CVS &gt; CVS</strong> <strong>Repositories</strong>.</li>
-        <li>Click <strong>Add CVS Repository</strong>.</li>
-        <li>Enter the information required to identify and connect to the repository 
-          location.</li>
-        <li>Click <strong>Finish</strong>. </li>
-      </ol></td>
-  </tr>
-  <tr> 
-    <td>Connecting and configuring CVS with SSH</td>
-    <td><ol>
-        <li>Select <strong>Window &gt; Preferences</strong>.</li>
-        <li>Select <strong>Team &gt; CVS &gt; SSH2 Connection Method</strong>.</li>
-        <li>Select the <strong>General </strong>tab, click <strong>Add Private 
-          Key</strong> and add your private key to the list.</li>
-        <li>Provide a password for your private key and save it on your computer.</li>
-      </ol>
-      <p>If you do not have a key pair:</p>
-      <p></p>
-      <ol>
-        <li>Select <strong>Window &gt; Preferences</strong>.</li>
-        <li>Select <strong>Team &gt; CVS &gt; SSH2 Connection Method</strong>.</li>
-        <li>Select the <strong>Key Management</strong> tab.</li>
-        <li>If your server supports version 1 of the protocol, select <strong>Generate 
-          RSA key</strong>, for version 2 select <strong>Generate DSA key</strong>. 
-          A public key and private key will be generated. The public key will 
-          be shown in the read-only text area. </li>
-        <li>Copy the public key to your server. If your server is running an OpenSSH 
-          server, click <strong>Export via sftp</strong>. Otherwise copy and paste 
-          the public key into your remote ~/.ssh/authorized_keys file.</li>
-      </ol></td>
-  </tr>
-  <tr> 
-    <td>Checking out a project from a CVS repository</td>
-    <td> <ol>
-        <li>Switch to the CVS Repository Exploring perspective. </li>
-        <li> In the CVS Repositories view, expand the repository location.</li>
-        <li>Expand HEAD and select the folders that you want to add as projects 
-          to the Workbench. </li>
-        <li>Select one of the following from the menu for the selected folders: 
-          <ul>
-            <li><strong>Check Out</strong> to check out each of the selected folders 
-              as a project in the local workspace with the same name as the folder 
-              in the repository.</li>
-            <li><strong> Check Out As... </strong>to check out the selected folders 
-              into a custom configured project in the local workspace. </li>
-          </ul>
-        </li>
-      </ol></td>
-  </tr>
-  <tr> 
-    <td>Synchronizing with the Repository and Updating or Committing changes</td>
-    <td><ol>
-        <li>In the Navigator view, select the resources that you want to synchronize.</li>
-        <li> Right click and select <strong>Team &gt; Synchronize with Repository</strong>. 
-        </li>
-        <li>In the Synchronize view, right-click the resource and select one of 
-          the following: 
-          <ul>
-            <li><strong>Commit</strong>, if you want to override the existing 
-              CVS version of the resource and save your version to the repository.</li>
-            <li><strong>Update</strong>, if you want to update your workspace 
-              with the version stored within the repository.
-            </li>
-          </ul>
-        </li>
-      </ol></td>
-  </tr>
-</table>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/no_help_exists.htm b/bundles/org.eclipse.platform.doc.user/reference/no_help_exists.htm
deleted file mode 100644
index 8860eeb..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/no_help_exists.htm
+++ /dev/null

@@ -1,21 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE> No Help Exists</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-No Help Exists</H1>
-<p CLASS="Head">There are no available help topics associated with this
-item.&nbsp;&nbsp;&nbsp;</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-10.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-10.htm
deleted file mode 100644
index 8bf7b5b..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-10.htm
+++ /dev/null

@@ -1,77 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta http-equiv="Content-Style-Type" content="text/css">
-   <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-   <title>General</title>
-<link REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-</head>
-<body bgcolor="#FFFFFF">
-<h1 CLASS="Head">General</h1>
-
-<div CLASS="Intro">General settings for the Workbench.  The term <i>Workbench</i> refers to the desktop development
-environment.</div>
-
-
-<p CLASS="Para" Label="Type">Each Workbench window contains one or more
-perspectives.&nbsp; Perspectives contain views and editors and control
-what appears in certain menus and tool bars.&nbsp; More than one Workbench
-window can exist on the desktop at any given time.</p>
-
-<p CLASS="Para">The following preferences can be changed on the General page. </p>
-<table width="75%" border="1">
-  <tr> 
-    <td><strong>Option</strong></td>
-    <td><strong>Description</strong></td>
-    <td><strong>Default</strong></td>
-  </tr>
-  <tr> 
-    <td>Always run in background</td>
-    <td>If this option is turned on, then the Workbench will perform certain actions 
-      in the background without disturbing the user.<br></td>
-    <td>Off<br></td>
-  </tr>
-  <tr> 
-    <td>Keep next/previous part dialog open </td>
-    <td>If this option is turned on then the editor and view cycle dialogs will 
-      remain open when their activation key is let go. Normally the dialog closes 
-      as soon as the key combination is release.</td>
-    <td>Off </td>
-  </tr>
-  <tr> 
-    <td>Open mode...</td>
-    <td><div CLASS="Para">You can select one of the following methods for opening 
-        resources:</div>
-      <div CLASS="Para"></div>
-      &nbsp; <ul>
-        <li CLASS="Item"> Double click - Single clicking on a resource will select 
-          it and double clicking on it will open it in an editor.</li>
-        <li CLASS="Item"> Single click (Select on hover) - Hovering the mouse 
-          cursor over the resource will select it and clicking on it once will 
-          open it in an editor.</li>
-        <li CLASS="Item"> Single click (Open when using arrow keys) - Selecting 
-          a resource with the arrow keys will open it in an editor.
-         <p CLASS="Para"><strong>Note:</strong> Depending on which view has focus, 
-          selecting and opening a resource may have different behavior. </p></li>
-      </ul></td>
-    <td>Double click</td>
-  </tr>
-</table>
-<table width="75%" border="1">
-  <tr> 
-
-  </tr>
-</table>
-<p>Here is what the General preferences page looks like:</p> 
-<p><img src="../images/Image217_pref_wb.png" alt="Preference dialog"></p>
-
-<P><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-23.htm">Workbench Window Layout</a>
-</P>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-11.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-11.htm
deleted file mode 100644
index 1250a9c..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-11.htm
+++ /dev/null

@@ -1,145 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta http-equiv="Content-Style-Type" content="text/css">
-   <title>Compare/Patch</title>
-<link REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-</head>
-<body bgcolor="#FFFFFF">
-
-<h1 CLASS="Head">
-Compare/Patch</h1>
-
-<div CLASS="Para"></div>
-
-<div CLASS="Para">The following preferences can be changed on the Compare/Patch
-page.</div>
-
-<h2>General options</h2>
-<table border="1" cellspacing="0" style="width: 100%;">
-  <caption>
-  </caption>
-  <thead>
-  </thead>
-  <tbody>
-  </tbody>
-  <tbody>
-    <tr> 
-      <th width="25%"> <div class="Para">Option</div></th>
-      <th> <div class="Para">Description</div></th>
-      <th> <div class="Para">Default</div></th>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Open structure 
-          compare automatically<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para"> 
-          <div CLASS="Para">This option controls whether a structure compare is 
-            automatically performed whenever a content compare is done. Turn this 
-            option off if you don't want to see the structural differences.</div>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">On</div></td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Show additional compare information 
-        in the status line </td>
-      <td style="vertical-align: top;">If this option is on, additional information 
-        about a change is shown in<br>
-        the status line. Turn this option on if you are interested in additional 
-        information about a change.<br> </td>
-      <td style="vertical-align: top;">Off<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Ignore white space<br> </td>
-      <td style="vertical-align: top;">This option controls whether or not whitespace 
-        change are shown in the compare viewer. Turn this option on if you want 
-        to see changes in whitespace.<br> </td>
-      <td style="vertical-align: top;">Off<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Automatically save dirty options 
-        before patching</td>
-      <td style="vertical-align: top;">This option controls whether any unsaved 
-        changes are automatically saved before a patch is applied. Turn this option 
-        on if you want to save changes automatically.<br> </td>
-      <td style="vertical-align: top;">Off<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Filtered Members</td>
-      <td style="vertical-align: top;"><p>This option allows you to filter members 
-          that should be excluded from 'Compare With Each Other'. </p>
-        <p><strong>Note: </strong>The names in the list must be separated by a 
-          comma.<br>
-        </p></td>
-      <td style="vertical-align: top;"><br> </td>
-    </tr>
-  </tbody>
-</table>
-<h2>Text Compare options</h2>
-<table border="1" cellspacing="0" style="width: 100%;">
-  <caption>
-  </caption>
-  <thead>
-  </thead>
-  <tbody>
-  </tbody>
-  <tbody>
-    <tr> 
-      <th width="25%"> <div class="Para">Option</div></th>
-      <th> <div class="Para">Description</div></th>
-      <th> <div class="Para">Default</div></th>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Synchronize 
-          scrolling between panes in compare viewers<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">
-          <div CLASS="Para">The two comparison viewers will "lock scroll" along 
-            with one another in order to keep identical and corresponding portions 
-            of the code in each pane side-by-side. Turn this option off if you 
-            do not want the compare viewers to lock scroll.</div>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">On</div></td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Initially show ancestor pane</td>
-      <td style="vertical-align: top;">Sometimes you want to compare two versions 
-        of a resource with the previous version from which they were both derived. 
-        This is called their <i>common ancestor</i>, and it appears in its own 
-        comparison pane during a three way compare. Turn this option on if you 
-        want the ancestor pane to always appear at the start of a comparison.<br> </td>
-      <td style="vertical-align: top;">Off<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Show pseudo conflicts<br> </td>
-      <td style="vertical-align: top;">Displays pseudo conflicts, which occur 
-        when two developers make the same change (for example, both add or remove 
-        the exact same line of code or comment). Turn this option on if you want 
-        pseudo conflicts to appear in compare browsers.<br> </td>
-      <td style="vertical-align: top;">Off<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Connect ranges with single 
-        line</td>
-      <td style="vertical-align: top;">Controls whether differing ranges are visually 
-        connected by a single line or a range delimited by two lines.<br> </td>
-      <td style="vertical-align: top;">On<br> </td>
-    </tr>
-  </tbody>
-</table>
-
-
-<p>Here is what the Compare preference page looks like:</p>
-<p><img src="../images/Image219_pref_cv.png" alt="Compare preference page" border="0" ></p>
-
-<P><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-25.htm">Compare Editor</a>
-<br><a href="ref-33.htm">CVS Synchronization View</a>
-</P>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-12.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-12.htm
deleted file mode 100644
index ddada6d..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-12.htm
+++ /dev/null

@@ -1,97 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Editors</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Editors</H1>
-<P CLASS="Para">
-The following preferences can be changed on the Editors page.</P>
-<TABLE BORDER="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Option</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Description</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Default</P></TH>
-    </TR>
-  </THEAD>
-  <TBODY>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">Size 
-          of recently opened files list</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          For each file that is opened in an editor, it is stored in a list of 
-          recently used files. This option controls the number of files which 
-          is displayed in this list in the File menu. </P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">4</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">Show 
-          multiple editor tabs</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">Specifies 
-          whether you wish to show multiple editor tabs. If off, then editor workbooks 
-          have one large tab and all non-visible editors are accessible only from 
-          the chevron.</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">On</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">Close 
-          editors automatically</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          This option is used to specify whether or not to re-use editors in the 
-          Workbench. If turned on, then you may specify the number of editors 
-          to use before they are recycled (Default is 8). You can also specify 
-          if a prompt dialog should be opened or if a new editor should be opened 
-          when all editors are dirty. Once it is turned on, the Pin Editor action 
-          is added to the toolbar and editor tab menu. Pinned editors are not 
-          recycled. </P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">Off</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">Text 
-          file encoding</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Use this option to specify the encoding to use when saving text files 
-          in editors. </P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">Default 
-          (CP1252)</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">Text 
-          File line delimiter</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Use this option to specify the line delimiter to use for new text files. 
-          <strong>Note:</strong> This will generally not effect the file line 
-          delimiter for<br>
-          existing files.</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">Default 
-        </P></TD>
-    </TR>
-  </TBODY>
-</TABLE>
-<P>&nbsp;
-</P>
-
-
-<P>Here is what the Editors preference page looks like:&nbsp;
-</P>
-
-
-<P><img src="../images/Image220_pref_dte.png" alt="Editors Preference Page" border="0" >
-</P>
-
-<P><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-24.htm">Editor Area</a>
-</P>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-13.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-13.htm
deleted file mode 100644
index 6cc18cf..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-13.htm
+++ /dev/null

@@ -1,77 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>File Associations</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-File Associations</H1>
-<P CLASS="Intro">
-On the File Associations preference page, you can add or remove file
-types recognized by the Workbench.&nbsp; You can also associate
-editors with file types in the file types list.</p>
-<DIV CLASS="Topic">
-<h2>
-File types list</h2>
-<UL CLASS="UnorderedList">
-    <LI CLASS="Item"> <strong>Add...</strong>:&nbsp; Adds a new file or file type 
-      (extension) to the predefined list. In the resulting New File Type dialog, 
-      type the name of a file or a file extension. If you are adding a file extension, 
-      you must type either a dot or a &quot;*.&quot; before the file type (e.g., 
-      &quot;.xml&quot; or &quot;*.xml&quot; as opposed to simply &quot;xml&quot;).</LI>
-    <LI CLASS="Item"><strong> Remove</strong>:&nbsp; Removes the selected file 
-      type from the list</LI>
-</UL>
-<p>Dialog to create a new file type:</p>
-<p><img src="../images/Image201_filetype.png" alt="New file type dialog" border="0" ></p>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Associated editors list</h2>
-  <UL CLASS="UnorderedList">
-    <LI CLASS="Item"> <strong>Add...</strong>:&nbsp; Adds a new editor to the 
-      list of editors associated with the file type selected above. In the resulting 
-      Editor Selection dialog, you can choose an editor to launch either inside 
-      the Workbench (internal) or outside the Workbench (external); click <b>Browse</b> 
-      to locate an editor yourself if the editor you want is not displayed in 
-      the list.</LI>
-    <LI CLASS="Item"> <strong>Remove</strong>:&nbsp; Removes the association between 
-      an editor and the file type selected above.<strong> Note:</strong> Any editor 
-      that is bound by content type may not be removed from this list. Currently, 
-      there is no mechanism available to remove these editors.</LI>
-    <LI CLASS="Item"> <strong>Default</strong>:&nbsp; Sets the selected editor 
-      as the default editor for the file type selected above. The editor moves 
-      to the top of the Associated Editors list to indicate that it is the default 
-      editor for that file type.</LI>
-  </UL>
-</DIV>
-<P>Dialog to create a new file association:
-</P>
-
-
-<P><img src="../images/Image202_editorsel.png" alt="Editor Selection dialog" border="0" >
-</P>
-
-
-<P>&nbsp;
-</P>
-
-
-<P>Here is what the File Associations preference page looks like:&nbsp;
-</P>
-
-
-<P><img src="../images/Image221_pref_fe.png" alt="File associations preference page" border="0" >
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-14.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-14.htm
deleted file mode 100644
index c8a2545..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-14.htm
+++ /dev/null

@@ -1,97 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Local History</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Local History</H1>
-<P CLASS="Intro"> The following preferences can be changed on the Local History 
-  page.</p>
-<TABLE BORDER="1" cellspacing="0">
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para"> Days to keep files</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Indicates for how many days you want to maintain changes in the local history.
-History state older than this value will be lost.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-7 days</P>
-</TD>
-</TR>
-<TR>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Maximum entries per File</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Indicates how many history states per file you want to maintain in the local
-history.&nbsp;If you exceed this value, you will lose older history to make room
-for new history.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-50 entries</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para"> Maximum file size (MB)</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Indicates the maximum size of individual states in the history store.&nbsp; If a
-file is over this size, it will not be stored.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-1 MB</P>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-
-
-<P>&nbsp;Here is what the Local History preference page looks like:&nbsp;
-</P>
-
-
-<P><img src="../images/Image222_pref_lh.png" alt="Local history preference page" border="0"> 
-</P>
-
-<P><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-6a.htm">Local History</a>
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-14b.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-14b.htm
deleted file mode 100644
index faa8bbf..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-14b.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Linked Resources</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Linked Resources</H1>
-<P CLASS="Intro">
-
-This preference page is used when working with 
-<a href="../concepts/concepts-13.htm">linked resources</a>. The preference 
-<b>Enable linked resources</b> is used to globally enable or disable the linked resource
-feature for the entire workspace.  By default, linked resources are enabled. If you
-disable linked resources, then you will not be able to create any new linked resources,
-or import existing projects that contain linked resources.
-</P>
-<P CLASS="Para">
-Not all versions of the workbench support linked resources and recognize them as such. 
-You may not want to use linked resources if you plan to share your workspace data with 
-other users. Disable this preference if they will not be able to work with linked resources.
-
-</P>
-<P CLASS="Para"> The remainder of this page is for defining <a href="../concepts/cpathvars.htm">path 
-  variables</a> that are used when creating linked resources. Use the <b>New</b> 
-  button to define new variables, the <b>Edit</b> button to change the value of 
-  an existing variable, and the <b>Remove</b> button to get rid of an existing 
-  variable. Note if you change a path variable that is currently in use, you will 
-  need to perform a local refresh on those projects to &quot;discover&quot; what 
-  is different in the file system. You can refresh a resource by opening the one 
-  of the navigation views' context menu for that resource and selecting <b>Refresh</b>. 
-  It is not recommended that you remove a path variable that is currently in use. 
-</P>
-
-
-<P>&nbsp;Here is what the Linked Resources preference page looks like:&nbsp;
-</P>
-
-
-<P><img src="../images/Image36_linkedresources.png" alt="Linked resources preference page" border="0">
-</P>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br><a href="../concepts/concepts-13.htm">Linked resources</a>
-<br><a href="../concepts/cpathvars.htm">Path variables</a>
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-15.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-15.htm
deleted file mode 100644
index e666e75..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-15.htm
+++ /dev/null

@@ -1,178 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Perspectives</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Perspectives</H1>
-<P CLASS="Para">
-On the
-Perspectives preference page, you can manage the various perspectives defined in the Workbench.&nbsp;&nbsp;</P>
-
-
-<TABLE BORDER="1" cellspacing="0">
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Open a new perspective
-</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Use this option to set what happens when you open a new perspective. Do you want the perspective opened within
-the current Workbench window or opened in a new window?
-</P>
-</TD>
-<TD>
-In the same window
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Open a new view
-</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Use this option to specify what happens when a new view is opened. It is either
-opened to its default position within the current perspective or it is opened as a fast view
-and docked to the side of the current perspective.
-</P>
-</TD>
-<TD>
-Within the perspective
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-New project options
-</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Use this option to specify the perspective behavior when a new project is created. You can set it
-to switch the current perspective to be the one associated with the project type and 
-open the perspective in the same Workbench window as the current one, switch the perspective and
-open it in a new Workbench window, or not to switch perspectives at all.
-</P>
-</TD>
-<TD>
-Open perspective in the same window
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-
-
-<h2>Available Perspectives Options:</h2>
-<TABLE BORDER="1" cellspacing="0">
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Make Default</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Sets the selected perspective as the default perspective.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Resource</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Reset</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Resets the definition of the selected perspective to the default configuration. This option is only applicable 
-to built-in perspectives that have been overwritten using Window > Save Perspective As...</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-n/a</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Delete</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Deletes the selected perspective. This option is only applicable to user-defined
-perspectives (built-in perspectives can not be deleted).</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-n/a</P>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-<P>&nbsp;
-</P>
-
-
-<P>&nbsp;Here is what the Perspectives preferences page looks like:&nbsp;
-</P>
-
-
-<P><img src="../images/Image223_pref_persp.png" alt="Perspectives Preference Page" border="0">
-</P>
-
-<P><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-6.htm">Perspectives</a>
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-16.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-16.htm
deleted file mode 100644
index acbba02..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-16.htm
+++ /dev/null

@@ -1,82 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Appearance</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Appearance</H1>
-<P CLASS="Para"> The following preferences can be changed on the Appearance page.</P>
-<table width="80%" border="1">
-  <tr> 
-    <td width="19%"><strong>Option</strong></td>
-    <td width="60%"><strong>Description</strong></td>
-    <td width="21%"><strong>Default</strong></td>
-  </tr>
-  <tr> 
-    <td>Editor tab positions </td>
-    <td>Specify either top or bottom to indicate where you want tabs for stacked 
-      editors to appear.</td>
-    <td>Top</td>
-  </tr>
-  <tr> 
-    <td>View tab positions </td>
-    <td>Specify either top or bottom to indicate where you want tabs for stacked 
-      views to appear.</td>
-    <td>Top</td>
-  </tr>
-  <tr> 
-    <td>Perspective switcher positions</td>
-    <td><P CLASS="Para">Specify the location of the perspective switcher bar</p></td>
-    <td>Top right</td>
-  </tr>
-  <tr> 
-    <td>Current presentation</td>
-    <td>Specify the currently active presentation (look and feel).</td>
-    <td>Default (current)</td>
-  </tr>
-  <tr> 
-    <td>Current theme</td>
-    <td>Specify the currently active theme (color and font set).</td>
-    <td>Default (current)</td>
-  </tr>
-  <tr> 
-    <td>Show text on perspective bar</td>
-    <td>Specify whether labels should be shown in the perspective bar as well 
-      as icons. 
-      <p></p></td>
-    <td>Enabled</td>
-  </tr>
-  <tr> 
-    <td>Show traditional style tabs</td>
-    <td>Specify whether traditional (square) tabs should be used in place of the 
-      curved tabs</td>
-    <td>Disabled</td>
-  </tr>
-  <tr> 
-    <td>Enable animations </td>
-    <td>Enable/disable the feature where views animate to their location when 
-      closed or<br>
-      opened</td>
-    <td>Enabled</td>
-  </tr>
-</table>
-<P CLASS="Para">&nbsp;</P>
-<P>Here is what the Appearance preferences page looks like:&nbsp;
-</P>
-
-
-<P><img src="../images/Image218_pref_app.png" alt="Appearance Preference Page" border="0">
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-17.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-17.htm
deleted file mode 100644
index 998798b..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-17.htm
+++ /dev/null

@@ -1,84 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Build Order</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Build Order</H1>
-<P CLASS="Para">
-Often the order in which projects are built is important.&nbsp; For
-example, if one project requires the Java classes which were defined in another
-project, the first project must be built after its prerequisite classes have
-been built.&nbsp; The Workbench allows users to explicitly define the order in
-which projects are built. Alternatively, users can let the platform compute the
-build order by interpreting project references as prerequisite relationships.
-The build order is applied for both building the entire workspace or for a group
-of projects.&nbsp;</P>
-<P CLASS="Para">You can change this order on the Build Order preferences page.&nbsp;</P>
-<TABLE BORDER="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Option</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Description</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Default</P></TH>
-    </TR>
-  </THEAD>
-  <TBODY>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Use default builder order</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          This<b></b> option allows the platform to computes the build ordering. 
-          Turning off this option enables access to the projects list, the ordering 
-          of which can be manipulated. </P></TD>
-      <TD>On</TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Project build order</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">This 
-          option allows you to select projects and use the <b>Up</b> and <b>Down</b> 
-          buttons to change the build order. Add and remove projects in the build 
-          order using the <b>Add Project</b> and <b>Remove Project</b> buttons. 
-          Projects removed from the build order <i>will</i> be built, but they 
-          will be built after all projects in the build order are built.</P></TD>
-      <TD>&nbsp; </TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Max iterations when building with cycles</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">This 
-          preference allows you to deal with build orders that contain cycles. 
-          Ideally, you should avoid cyclic references between projects. Projects 
-          with cycles really logically belong to a single project, and so they 
-          should be collapsed into a single project if possible. However, if you 
-          absolutely must have cycles, it may take several iterations of the build 
-          order to correctly build everything. Changing this preference will alter 
-          the maximum number of times the workbench will attempt to iterate over 
-          the build order before giving up.</P></TD>
-      <TD> 10</TD>
-    </TR>
-  </TBODY>
-</TABLE>
-<P CLASS="Para">Here is what the Build Order preference page looks like:&nbsp; 
-</P>
-<P><img src="../images/Image224_pref_build.png" alt="Build order preference page" border="0"> 
-</P>
-
-<P><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-5.htm">Builds</a>
-<br><a href="ref-59.htm">Project menu</a>
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-18.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-18.htm
deleted file mode 100644
index 11f9c3e..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-18.htm
+++ /dev/null

@@ -1,89 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Help</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Help</H1>
-<P CLASS="Para">
-On the Help preferences page, you can indicate how to display help information.</P>
-<TABLE BORDER="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Option</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Description</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Default</P></TH>
-    </TR>
-    <TR> 
-      <TH align="left"> <span style="font-weight: 400">Use external browsers</span></TH>
-      <TH align="left"> <span style="font-weight: 400">If embedded web browser 
-        is supported on your system, help window uses an embedded help browser
-        to display help contents, whenever possible, and this option is available.
-        Select it, to force help to use external browsers.  Use &quot;Web
-        Browser&quot; preference page to select browser to use.</span> </TH>
-      <TH align="left"> <span style="font-weight: 400">Off</span></TH>
-    </TR>
-    <TR> 
-      <TH align="left"> <span style="font-weight: 400">Open window context help 
-        </span></TH>
-      <TH align="left"><span style="font-weight: 400">This option allows you to 
-        determine whether the window context help will be opened in a dynamic 
-        help view or in an infopop.</span></TH>
-      <TH align="left"> <span style="font-weight: 400">in a dynamic help view 
-        </span></TH>
-    </TR>
-    <TR> 
-      <TH align="left"> <span style="font-weight: 400">Open dialog context help</span></TH>
-      <TH align="left"><span style="font-weight: 400">This option allows you to 
-        determine whether the dialog context help will be opened in a dynamic 
-        help section of help view or in an infopop.</span></TH>
-      <TH align="left"> <span style="font-weight: 400">in a dynamic help window</span></TH>
-    </TR>
-    <TR> 
-      <TH align="left"> <span style="font-weight: 400">Help view document open 
-        mode </span></TH>
-      <TH align="left"><span style="font-weight: 400">This option allows you to 
-        determine whether the documents selected in the help view will be opened
-        in place or in the editor area.</span></TH>
-      <TH align="left"> <span style="font-weight: 400">Open in place </span></TH>
-    </TR>
-  </THEAD>
-  <TBODY>
-  </TBODY>
-</TABLE>
-
-
-<P>Here is what the Help preferences page looks like:&nbsp;&nbsp;
-</P>
-
-
-<P>
-<img src="../images/Image225_pref_help.png" alt="Help Preference Page" border="0">
-</P>
-
-<p>
-<b>Note:</b>  Selection performed on this page can affect how the help view is presented.  If the selected browser is not fully compatible with Internet Explorer or Mozilla, or has JavaScript disabled, the help view shown in the browser might be a simplified version.
-</p>
-
-<p>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tchgbrws.htm">Changing the browser used by the help system</a></p>
-
-<p>
-<img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-34.htm">Help View</a>
-<br><a href="ref-42.htm">Web Browser</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-19.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-19.htm
deleted file mode 100644
index 026329e..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-19.htm
+++ /dev/null

@@ -1,77 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Team</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Team</H1>
-<P CLASS="Para"> The <strong>Team</strong> preferences page contains options which 
-  affect the version management Team support.</P>
-<TABLE BORDER="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Option</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Description</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Default</P></TH>
-    </TR>
-    <TR> 
-      <TD COLSPAN="1" valign="top" align="left">Show all synchronization information 
-        in a resource's text label</TD>
-      <TD COLSPAN="1" valign="top" align="left">Use this option to have the synchronization 
-        state of a resource displayed as text in the resource's label. By default, 
-        only an icon decorator is used to identify a resource's synchronization 
-        state.</TD>
-      <TD COLSPAN="1" valign="top" align="left">Off</TD>
-    </TR>
-  </THEAD>
-  <TBODY>
-    <TR> 
-      <TD COLSPAN="1" valign="top" align="left">Choose the default Synchronize 
-        View layout</TD>
-      <TD COLSPAN="1" valign="top" align="left">Use this option to configure the 
-        default layout used when a synchronization is first added to the Synchronize 
-        view. The layout can be subsequently changed in the view drop down menu.</TD>
-      <TD COLSPAN="1" valign="top" align="left">Compressed Folders</TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Open the associated perspective when a synchronize operation completes</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">Use 
-          this option to configure what happens when a synchronization operation 
-          is run. The options are:</P>
-        <ul>
-          <li><strong class="Para">Always</strong>: always switch perspectives</li>
-          <li><strong class="Para">Never</strong>: never switch perspectives</li>
-          <li><strong class="Para">Prompt</strong>: prompt to switch perspectives</li>
-        </ul></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Always</P></TD>
-    </TR>
-    <TR> 
-      <TD COLSPAN="1" valign="top" align="left">Perspectives</TD>
-      <TD COLSPAN="1" valign="top" align="left">Use this option to configure which 
-        perspective is to be shown when a synchronize operation is run.</TD>
-      <TD COLSPAN="1" valign="top" align="left">Team Synchronizing perspective</TD>
-    </TR>
-  </TBODY>
-</TABLE>
-<P>Here is what the Team preference page looks like:&nbsp;&nbsp; </P>
-<P> </P>
-<img src="../images/Image_team_pref.png" alt="Team Preference Page" border="0">
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- > <br>
-  <a href="ref-33.htm">CVS Synchronize view</a> </p>
-<p><a href="ref-6.htm">Perspectives</a> </p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-console.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-console.htm
deleted file mode 100644
index e275515..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-console.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-
-<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<META http-equiv="Content-Style-Type" content="text/css"><LINK rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<TITLE>CVS Console</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff">
-<H1 class="Head">CVS Console</H1>
-<P class="Para">The following preferences can be changed on the CVS Console preference 
-  page.</P>
-<TABLE width="100%" border="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH> <P class="Para">Option</P></TH>
-      <TH> <P class="Para">Description</P></TH>
-      <TH>Default</TH>
-    </TR>
-  </THEAD>
-  <TR> 
-    <TD valign="top" align="left">Fixed width</TD>
-    <TD valign="top" align="left">Use this option to fix the width of console 
-      lines. Enabling this option allows the width to be specified. The default 
-      width is 80.</TD>
-    <TD valign="top" align="left">Disabled</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Limit console output</TD>
-    <TD valign="top" align="left">Use this option to limit the number of characters 
-      to be buffered by the console. The default buffer size is 500000.</TD>
-    <TD valign="top" align="left">Enabled</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Show CVS output in Console view</TD>
-    <TD valign="top" align="left">Use this option to show the output of CVS commands 
-      in the Console view. Enabling this option may show useful information but 
-      will slow down command operation.</TD>
-    <TD valign="top" align="left">Disabled</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Console text color settings</TD>
-    <TD valign="top" align="left">Use these options to change the colors for the 
-      text shown in CVS Console. 
-      <UL>
-        <LI>Command line text <I>(black)</I></li>
-        <LI>Message text <I>(blue)</I></li> 
-        <LI>Error text <I>(red)</I></LI>
-      </UL></TD>
-    <TD valign="top" align="left">&nbsp;</TD>
-  </TR>
-</TABLE>
-<p>Here is what the preference page looks like:</p>
-<p><img src="../images/cvs-console-prefs.png"></p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-decorations.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-decorations.htm
deleted file mode 100644
index 036dcae..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-decorations.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-
-<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<META http-equiv="Content-Style-Type" content="text/css"><LINK rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<TITLE>CVS Labels Decorations</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff">
-<H1 class="Head">CVS Label Decorations</H1>
-<P class="Para">The following preferences can be changed on the CVS Label Decorations 
-  preference page.</P>
-<TABLE width="100%" border="1" cellspacing="0">
-  <TR> 
-    <TD valign="top" align="left">General </TD>
-    <TD valign="top" align="left"> Use the options on this page to configure general 
-      preferences about the decorators: 
-      <ul>
-        <li><STRONG>Compute deep outgoing state for folders: </STRONG>Use this 
-          option to configure if the outgoing indicators on folders should be 
-          calculated. Disabling this option improves the performance of the decorators 
-          because calculating the dirty state for folders requires computing the 
-          dirty state for all child resources. (<EM>enabled by default</EM>)</li>
-        <li><strong>Enable font and color decorations: </strong>Use this option 
-          to enable font and color decorations. The colors and fonts used for 
-          outgoing changes, ignored resources, etc. can be configured on the <strong>General 
-          &gt; Appearance &gt;Colors and Fonts</strong> preference page</li>
-      </ul></TD>
-  </TR>
-  <TR> 
-    <TD valign="center" align="left">Text </TD>
-    <TD valign="top" align="left"> Use the options on this page to configure how 
-      CVS information will be added to text labels.</TD>
-  </TR>
-  <TR> 
-    <TD valign="center" align="left">Icons </TD>
-    <TD valign="top" align="left">Use the options on this page to configure the 
-      which icons can be used as overlays to show CVS specific information in 
-      views. </TD>
-  </TR>
-</TABLE>
-<p>This is what the General tab group of the CVS Label Decorations preference 
-  page looks like:</p>
-<p><img src="../images/cvs-decoration-general.png"></p>
-<p>This is what the Text tab group of the CVS Label Decorations preference page 
-  looks like:</p>
-<p><img src="../images/cvs-decoration-text.png"></p>
-<p>This is what the Icons tab group of the CVS Label Decorations preference page 
-  looks like:</p>
-<p><img src="../images/cvs-decoration-icon.png" width="580" height="489"></p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-ext.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-ext.htm
deleted file mode 100644
index 612db01..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-ext.htm
+++ /dev/null

@@ -1,61 +0,0 @@
-
-<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<META http-equiv="Content-Style-Type" content="text/css"><LINK rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<TITLE>CVS Ext Connection Method</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff">
-<H1 class="Head">CVS Ext Connection Method</H1>
-<P class="Para">The following preferences can be changed on the CVS Ext Connection 
-  Method preference page.</P>
-<TABLE border="1" cellspacing="0">
-  <TR> 
-    <TD width="150" align="left" valign="top">Use external program vs. Use internal 
-      connection method </TD>
-    <TD width="650" align="left" valign="top">This page allows you to configure 
-      the ext connection method to use an external program or another connection 
-      method to to connect to a server. The later option is provided to allow 
-      custom connection method such as extssh to remain compatible with external 
-      CVS client tools.</TD>
-    <TD width="65" valign="top">Use external program</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">CVS_RSH </TD>
-    <TD valign="top" align="left"> Use this option to configure the program that 
-      will be called to connect to the remote CVS server. The RSH command is invoked 
-      with following calling pattern: 
-      <P><EM>CVS_RSH Parameters CVS_SERVER</EM></P></TD>
-    <TD valign="top">ssh </TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Parameters </TD>
-    <TD valign="top" align="left"> Use this option to configure the parameters 
-      passed to the CVS_RSH program. The default parameter pattern is {host} -l 
-      {user}. It can be tailored using the {host}, {user}, {password} and {port} 
-      variables.</TD>
-    <TD valign="top">{host} -l {user} </TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">CVS_SERVER </TD>
-    <TD valign="top" align="left">Use this option to configure the name of the 
-      remote CVS server program to run. Change this setting only if the remote 
-      CVS server binary name is different than the default. </TD>
-    <TD valign="top">cvs </TD>
-  </TR>
-  <TR>
-    <TD valign="top" align="left">Connection type</TD>
-    <TD valign="top" align="left">Use this option to set the connection method 
-      to be used for repository locations that use the ext connection method, 
-      if the option to use another connection method is enabled.</TD>
-    <TD>&nbsp;</TD>
-  </TR>
-</TABLE>
-<p>Here is what the preference page looks like:</p>
-<p><img src="../images/cvs-ext.png"></p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-password.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-password.htm
deleted file mode 100644
index c84e3bc..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-password.htm
+++ /dev/null

@@ -1,20 +0,0 @@
-
-<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<META http-equiv="Content-Style-Type" content="text/css"><LINK rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<TITLE>CVS Password Management</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff">
-<H1 class="Head">CVS Password Management</H1>
-<p>This preference page allows you to see which repository locations have passwords 
-  cached in the keyring file and also allows you to purge those passwords.Only 
-  those passwords that you have explicitly indicated should be saved will appear 
-  in the list. Here is what the preference page looks like:</p>
-<p><img src="../images/cvs-password.png"></p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-ssh2.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-ssh2.htm
deleted file mode 100644
index 94cd2c4..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-ssh2.htm
+++ /dev/null

@@ -1,48 +0,0 @@
-
-<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<META http-equiv="Content-Style-Type" content="text/css"><LINK rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<TITLE>CVS SSH2 Connection Method</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff">
-<H1 class="Head">CVS SSH2 Connection Method</H1>
-<P class="Para">The preferences on the CVS SSH2 Connection Method preference page 
-  are divided into 4 groups.</P>
-<TABLE width="100%" border="1" cellspacing="0">
-  <TR> 
-    <TD width="17%" align="left" valign="center">General</TD>
-    <TD width="83%" align="left" valign="center"> Use the options in this tab 
-      group to configure where the ssh key directory is and what keys are to be 
-      sent to a server when connecting.</TD>
-  </TR>
-  <TR> 
-    <TD valign="center" align="left">Proxy</TD>
-    <TD valign="top" align="left">Use the options in this tab group to configure 
-      an HTTP or SOCKS5 proxy.</TD>
-  </TR>
-  <TR> 
-    <TD valign="center" align="left">Key Management</TD>
-    <TD valign="top" align="left"> Use the options in this tab group to create, 
-      manage and export keys.</TD>
-  </TR>
-  <TR>
-    <TD valign="center" align="left">Known Hosts</TD>
-    <TD valign="top" align="left">Use the options in this tab group to manage 
-      the keys for the known hosts.</TD>
-  </TR>
-</TABLE>
-<p>Here's what the General tab of the CVS SSH2 preference page looks like:</p>
-<p><img src="../images/cvs-ssh2-general.png"></p>
-<p>Here's what the Proxy tab of the CVS SSH2 preference page looks like:</p>
-<p><img src="../images/cvs-ssh2-proxy.png"></p>
-<p>Here's what the Key Management tab of the CVS SSH2 preference page looks like:</p>
-<p><img src="../images/cvs-ssh2-key.png"></p>
-<p>Here's what the Known Hosts tab of the CVS SSH2 preference page looks like:</p>
-<p><img src="../images/cvs-ssh2-hosts.png"></p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-sync.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-sync.htm
deleted file mode 100644
index 97061c1..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-sync.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-
-<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<META http-equiv="Content-Style-Type" content="text/css"><LINK rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<TITLE>CVS Synchronize/Compare</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff">
-<H1 class="Head">CVS Synchronize/Compare</H1>
-<P class="Para">The following preferences can be changed on the CVS Synchronize/Compare 
-  preference page.</P>
-<TABLE width="100%" border="1" cellspacing="0">
-<THEAD>
-    <TR> 
-      <TH width="164"> <P class="Para">Option</P></TH>
-      <TH width="490"> <P class="Para">Description</P></TH>
-      <TH width="152"> <P class="Para">Default</P></TH>
-    </TR>
-  </THEAD>
-  <TR> 
-    <TD width="21%" align="left" valign="top">Consider file contents in comparisons</TD>
-    <TD width="58%" align="left" valign="top"> Use this option to compare contents 
-      for changed files found when comparing CVS resources. Usually, time stamps 
-      are used to compare CVS files, and this is by far the fastest method. However, 
-      in some cases a more accurate comparison can be achieved by comparing file 
-      content. Disabling this option will speed up comparisons but may result 
-      in compare entries whose contents are the same. This option only applies 
-      to comparisons and merges but not Workspace synchronizations.</TD>
-    <TD width="21%" align="left" valign="top">Enabled</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Show revision comparisons in dialog</TD>
-    <TD valign="top" align="left">Use this this option to show revision comparisons 
-      in a dialog instead of a compare editor.</TD>
-    <TD valign="top" align="left" >Disabled</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Show the file author in compare editors</TD>
-    <TD valign="top" align="left"> Use this option to show the author of file 
-      revisions when shown in compare editors and dialogs.</TD>
-    <TD valign="top" align="left">Disabled</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Enable change set grouping in CVS synchronizations</TD>
-    <TD valign="top" align="left">Use the option to have change sets enabled by 
-      default in those CVS synchronizations that support them.</TD>
-    <TD valign="top" align="left">Disabled</TD>
-  </TR>
-</TABLE>
-<p>Here is what the preference page looks like:</p>
-<p><img src="../images/cvs-sync-compare.png"></p>
-<P><IMG height="27" alt="Related reference" src="../images/ngrelr.png" width="159" border="0"><BR>
-<A href="ref-19.htm">Team</A><br>
-<a href="ref-33.htm">CVS Workspace Synchronization</a><br>
-<a href="ref-33a.htm">CVS Merge Synchronization</a></P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-watch-edit.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-watch-edit.htm
deleted file mode 100644
index a8eb815..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-watch-edit.htm
+++ /dev/null

@@ -1,78 +0,0 @@
-
-<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<META http-equiv="Content-Style-Type" content="text/css"><LINK rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<TITLE>CVS Watch/Edit</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff">
-<H1 class="Head">CVS Watch/Edit</H1>
-<P class="Para">The following preferences can be changed on the CVS Watch/Edit 
-  preference page.</P>
-<TABLE border="1" cellspacing="0">
-<THEAD>
-    <TR> 
-      <TH width="164"> <P class="Para">Option</P></TH>
-      <TH width="490"> <P class="Para">Description</P></TH>
-      <TH width="152"> <P class="Para">Default</P></TH>
-    </TR>
-  </THEAD>
-  <TR> 
-    <TD valign="top" align="left">Configure projects to use Watch/edit on checkout</TD>
-    <TD valign="top" align="left"> Use this option to indicate that files checked 
-      out out from the repository should be made read-only.</TD>
-    <TD valign="top" align="left">Disabled</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">When read-only files are modified in an editor</TD>
-    <TD valign="top" align="left"> Use this option to configure what occurs when 
-      a read-only file is modified in an open editor or by another tool. The options 
-      are: 
-      <ul>
-        <li><strong>Send a cvs edit notification to the server: </strong>Issues 
-          a cvs edit notification to the server before making the file writable. 
-          If other editors exist on the file, the user will be prompted and may 
-          continue or cancel.</li>
-        <li><strong>Send a cvs edit notification to the server in the background: 
-          </strong>Issues a cvs edit notification to the server in the background 
-          after making the file writable. This allows the user to keep typing 
-          uninterrupted while the edit notification is sent to the server.</li>
-        <li><strong>Edit the file without informing the server: </strong>Makes 
-          the file read-only without notifying the server.</li>
-      </ul></TD>
-    <TD valign="top" align="left">Send a cvs edit notification to the server in 
-      the background</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Before a CVS edit notification is sent to the 
-      server </TD>
-    <TD valign="top" align="left">Use this option to configure what occurs when 
-      a read-only file is modified in an open editor or by another tool and the 
-      <strong>Send a cvs edit notification to the server</strong> is enabled. 
-      The options are: <ul>
-        <li><strong>Always Prompt: </strong>Always prompt the user for confirmation</li>
-        <li><strong>Only prompt if there are other editors: </strong>Shows the 
-          user the list of current editors and allows the user to confirm or cancel 
-          the edit.</li>
-        <li><strong>Never Prompt: </strong>Send the edit notification without 
-          prompting</li>
-      </ul></TD>
-    <TD valign="top" align="left">Only prompt if there are editors</TD>
-  </TR>
-</TABLE>
-<p>Here is what the preference page looks like:</p>
-<p><img src="../images/cvs-watch-edit.png"></p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" > <br>
-  <a href="../concepts/concepts-cvs-watch.htm">Watch/Edit</a></p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"
- > <a href="../tasks/tasks-cvs-watch.htm"><br>
-  Finding out who's working on what: watch/edit</a></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs.htm
deleted file mode 100644
index 44360c8..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs.htm
+++ /dev/null

@@ -1,224 +0,0 @@
-
-<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<META http-equiv="Content-Style-Type" content="text/css"><LINK rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<TITLE>CVS</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff">
-<H1 class="Head">CVS</H1>
-<p class="Head">The following sections describe the preferences available in the 
-  tab groups of the CVS preferences page.</p>
-<h2 class="Para">General</h2>
-<p>On the General tab group of the CVS preference page you can customize several 
-  aspects of the CVS Plug-in.</p>
-<TABLE border="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH> <P class="Para">Option</P></TH>
-      <TH> <P class="Para">Description</P></TH>
-      <TH> <P class="Para">Default</P></TH>
-    </TR>
-  </THEAD>
-  <TR> 
-    <TD valign="top" align="left">Validate server version compatibility on first 
-      connection </TD>
-    <TD valign="top" align="left">Use this option to enable a query of the CVS 
-      server version on the first connection to determine server compatibility. 
-      The server version will be output to the console and if an incompatibility 
-      is detected a warning message will be logged when connecting. </TD>
-    <TD>Enabled </TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Confirm move tag on tag operation</TD>
-    <TD valign="top" align="left">Use this option to be prompted when the Move 
-      tag option is chosen when tagging.</TD>
-    <TD>Enabled</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Display detailed protocol output to stdout</TD>
-    <TD valign="top" align="left">Use this option to display the communication 
-      trace between the Workbench and a CVS server.</TD>
-    <TD>Disabled</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Refresh tags when comparing or replacing tags</TD>
-    <TD valign="top" align="left">Use this option to have the Compare with and 
-      Replace With tag dialogs automatically refresh the known tags by contacting 
-      the server.</TD>
-    <TD>Disabled</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Automatically share projects containing CVS 
-      meta information </TD>
-    <TD valign="top" align="left">Use this option to have any imported project 
-      that was checked out from CVS using a different CVS tool automatically shared 
-      with CVS. </TD>
-    <TD>Enabled</TD>
-  </TR>
-  <TR>
-    <TD valign="top" align="left">Maximum number of files displayed when committing</TD>
-    <TD valign="top" align="left">Use this option to limit the number of files 
-      that get displayed in the commit dialog.</TD>
-    <TD>1000</TD>
-  </TR>
-</TABLE>
-<p>This is what the General tab group of the CVS preference page looks like:</p>
-<p><img src="../images/cvs-general.png"></p>
-<h2><strong>Files and Folders</strong></h2>
-<p>On the File and Folders tab group of the CVS preference page you can customize 
-  several aspects of the CVS Plug-in.</p>
-<TABLE border="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH> <P class="Para">Option</P></TH>
-      <TH> <P class="Para">Description</P></TH>
-      <TH> <P class="Para">Default</P></TH>
-    </TR>
-  </THEAD>
-  <TR> 
-    <TD valign="top" align="left">Treat all new files as binary </TD>
-    <TD valign="top" align="left">Use this option to override the file content 
-      settings and treat all new files as binary. </TD>
-    <TD>Disabled </TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Convert text files to use platform line ending</TD>
-    <TD valign="top" align="left">Use the option to convert the line endings of 
-      text files to the line ending used by the platform. This option can be disabled 
-      if you are checking out resources to a *nix drive that is mounted on a Windows 
-      machine. </TD>
-    <TD>Enabled</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left"> Prune empty directories</TD>
-    <TD valign="top" align="left"> Use this option to specify the pruning of empty 
-      directories on update and in the synchronization view. Although pruned directories 
-      aren't shown in the workbench there is actually still an empty directory 
-      in the repository. This is helpful because CVS doesn't provide a client 
-      with the ability to remove directories from the server.</TD>
-    <TD>Enabled </TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Delete unmanaged resources on replace </TD>
-    <TD valign="top" align="left">Use this option to allows resources not under 
-      CVS control to be deleted when replacing with resources from the repository. 
-    </TD>
-    <TD>Enabled </TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Default text mode</TD>
-    <TD valign="top" align="left">Use this option to set the default keyword substitution 
-      for text files. </TD>
-    <TD>ASCII with keyword expansion -kkv </TD>
-  </TR>
-</TABLE>
-<p>This is what the File and Folders tab group of the CVS preference page looks 
-  like:</p>
-<p><img src="../images/cvs-files.png"></p>
-<h2>Connection</h2>
-<p>On the Connections tab group of the CVS preference page you can customize several 
-  aspects of the CVS Plug-in.</p>
-<TABLE border="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH> <P class="Para">Option</P></TH>
-      <TH> <P class="Para">Description</P></TH>
-      <TH> <P class="Para">Default</P></TH>
-    </TR>
-  </THEAD>
-  <TR> 
-    <TD valign="top" align="left">Communication timeout </TD>
-    <TD valign="top" align="left">Use this option to configure the amount of time 
-      in seconds to wait before timing out from a connection to the CVS server. 
-    </TD>
-    <TD>60 seconds </TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Quietness level </TD>
-    <TD valign="top" align="left">Sets the amount of status information CVS prints 
-      for a command. In <STRONG>Somewhat quiet</STRONG> mode the printing of unimportant 
-      informational messages is suppressed. The consideration of what is important 
-      depends on each command. In <STRONG>Very quiet</STRONG> mode all output 
-      except what is absolutely necessary to complete the command is suppressed. 
-      In <STRONG>Very Quiet</STRONG> mode, some CVS servers may not communicate 
-      important information about errors that have occurred. You may want to consider 
-      using <STRONG>Somewhat quiet</STRONG> mode instead. </TD>
-    <TD>Verbose </TD>
-  </TR>
-  <TR>
-    <TD valign="top" align="left">Compression</TD>
-    <TD valign="top" align="left">Use this option to set the compression level 
-      used when sending files between the client and server.</TD>
-    <TD>0</TD>
-  </TR>
-</TABLE>
-<p>This is what the Connection tab group of the CVS preference page looks like:</p>
-<p><img src="../images/cvs-connection.png"></p>
-<h2>Prompting</h2>
-<p>On the Prompting tab group of the CVS preference page you can customize several 
-  aspects of the CVS Plug-in.</p>
-<TABLE border="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH> <P class="Para">Option</P></TH>
-      <TH> <P class="Para">Description</P></TH>
-      <TH> <P class="Para">Default</P></TH>
-    </TR>
-  </THEAD>
-    <TR> 
-      <TD valign="top" align="left">Allow empty commit comments</TD>
-      <TD valign="top" align="left"><p>Use the option to configure what happens 
-          if a commit comment is not provided when committing.</p>
-        <ul>
-          <li><STRONG>Yes: </STRONG>Allow the commit to occur without a comment.</li>
-          <li><strong>No: </strong>Do not allow the commit to proceed until a 
-            comment is provided.</li>
-          <li><STRONG>Prompt: </STRONG>Ask the user whether they want to allow 
-            the commit to proceed without a comment.</li>
-        </ul></TD>
-      <TD valign="top" align="left">Prompt</TD>
-    </TR>
-  <TR> 
-    <TD valign="top" align="left">Automatically save dirty editors before CVS 
-      operations </TD>
-    <TD valign="top" align="left"> Use this option to configure what happens when 
-      there are open editors with unsaved changes when a CVS operation is performed. 
-      Options are: 
-      <ul>
-        <li><STRONG>Yes: </STRONG>Automatically save unsaved changes in open editors 
-          before each CVS operation.</li>
-        <li><strong>No: </strong>Continue CVS operations even if there are unsaved 
-          changes in open editors.</li>
-        <li><STRONG>Prompt: </STRONG>Ask the user what to do with unsaved changes 
-          in open editors.</li>
-      </ul></TD>
-    <TD valign="top" align="left">Prompt </TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Open perspective after a 'Show Annotations' 
-      operation </TD>
-    <TD valign="top" align="left"><p>Use this option to configure whether another 
-        perspective is opened when the Show Annotations operation is run.</p>
-      <ul>
-        <li><STRONG>Yes: </STRONG>Open the perspective chosen in the Default perspective 
-          for 'Show Annotations' preference.</li>
-        <li><strong>No:</strong>Do not open another perspective.</li>
-        <li><STRONG>Prompt: </STRONG>Ask the user whether they want to open the 
-          perspective chosen in the Default perspective for 'Show Annotations' 
-          preference or remain in the current perspective.</li>
-      </ul></TD>
-    <TD valign="top" align="left">Prompt</TD>
-  </TR>
-</TABLE>
-<p>This is what the Prompting tab group of the CVS preference page looks like:</p>
-<p><img src="../images/cvs-prompting.png"></p>
-<P><IMG height="27" alt="Related reference" src="../images/ngrelr.png" width="159" border="0"><BR>
-  <A href="ref-6.htm">Perspectives</A></P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-2.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-2.htm
deleted file mode 100644
index b35fa9b..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-2.htm
+++ /dev/null

@@ -1,70 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Workbench toolbar</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Workbench toolbar </H1>
-<P CLASS="Intro">The Workbench toolbar is displayed
-at the top of the Workbench window, directly underneath the menu bar.&nbsp; The
-contents of the toolbar change based on the active editor.&nbsp; Actions in the
-toolbar may apply to particular views, so these actions may be enabled or
-disabled based on the state of the currently active view or editor.</p>
-<P CLASS="Para">
-Here is an example of the toolbar in the Resource perspective:</P>
-<P CLASS="Para">
-<img src="../images/Image214_toobar_rsrc.png" alt="Workbench toolbar" border="0" ></P>
-<DIV CLASS="XRefList">
-
-<h2>
-New Wizard</h2>
-<P CLASS="Para">
-This command brings up a dialog where you can choose
-the type of resource to create.</P>
-
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Save The Open Editor Contents</h2>
-<P CLASS="Para">
-This command saves the file currently displayed in the editor area.</P>
-</DIV>
-<DIV CLASS="Topic"> 
-  <h2> Print</h2>
-  <P CLASS="Para"> This command opens a dialog which allows you to specify where 
-    you would like to print the contents of the file currently being displayed 
-    in the editor.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Search</h2>
-<P CLASS="Para">
-This command opens the search dialog, which allows you to search the
-workspace for
-specified text.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-External Tools</h2>
-  <P CLASS="Para"> This command presents a drop-down menu which allows you to run 
-    or configure external tools. <br>
-  </P>
-</DIV>
-
-<P><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-3.htm">Shortcut Bar</a>
-<br><a href="ref-4.htm">View Toolbars</a>
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-20-fileContent.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-20-fileContent.htm
deleted file mode 100644
index 67f75df..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-20-fileContent.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Team File Content</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Team File Content</H1>
-<P CLASS="Intro"> On the Team&gt;File Content preference page, you can associate 
-  file names or extensions with the type of data the file contains. The two choices 
-  for file content type are ASCII and Binary. Repository providers such as CVS 
-  can then use this information to provide content type appropriate behavior. 
-  For example, for ASCII files, CVS ensures that line terminators conform to those 
-  of the OS platform.</p> 
-<P CLASS="Intro">Entries are added to the File Content page in two ways. The first 
-  is through contributions from workbench plug-ins. Tools integrated into the 
-  workbench provide the workbench with the file content types for file extensions 
-  specific to the tool. The workbench itself also defines the file content type 
-  for file extensions that are common and appear frequently in the workbench (e.g. 
-  html,.png, etc.).</p> 
-<P CLASS="Intro">The second method is for users to add file content types explicitly 
-  on the File Content preference page. To do so, the user can simply click on 
-  the <strong>Add Extension</strong> button and enter an extension or click on 
-  the <strong>Add Name</strong> button and add a name.. Following this, they can 
-  toggle the type associated with the name or extension by selecting the entry 
-  for the extension in the table and clicking <strong>Change</strong>. Entries 
-  can be removed from the list by selecting them and clicking <strong>Remove</strong>. 
-  Only those entries that were manually added can be removed. Entries contributed 
-  through the plug-in manifest can only be changed.</p> 
-<P CLASS="Intro">Here is what the Team File Content preference pages looks like:</p>
-<P CLASS="Intro"><img src="../images/team-file-content.png"></p>
-<p>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-cvs-11.htm">Setting the CVS keyword substitution mode</a>
-</p>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-20.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-20.htm
deleted file mode 100644
index 05489a8..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-20.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Ignored Resources</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Team Ignored Resources</H1>
-<P CLASS="Intro"> On the <strong>Team&gt;Ignored Resources</strong> preference 
-  page, you can specify file name patterns to exclude from the version control 
-  management system. There is a list of file patterns against which resources 
-  will be matched before they are considered as version control candidates.&nbsp; 
-  These patterns may contain the wildcard characters "*" and "?".&nbsp; This pattern 
-  "*" represents any sequence of zero or more characters.&nbsp; This pattern "?" 
-  represents any one character.&nbsp; For example, you can specify a pattern of 
-  "*~", which would match any temporary files that end with "~".&nbsp;&nbsp; Any 
-  file or directory that matches any one of the patterns will be ignored during&nbsp; 
-  update or commit operations.</p> 
-<P CLASS="Para"> To add a file type to the ignore list, simply click <strong>Add 
-  Pattern</strong>. In the dialog, enter a file type (e.g. *.class). To remove 
-  a file type from the ignore list, simply select the file type in the ignore 
-  list and click <strong>Remove</strong>.&nbsp;</P>
-<P CLASS="Para"> You can temporarily disable ignoring the file pattern by de-selecting 
-  it from the list. You do not have to remove the specified file pattern from 
-  the list to temporarily disable it.</P>
-<P>Here is what the Ignored Resources preference page looks like:&nbsp;&nbsp; 
-</P>
-<P> </P>
-<img src="../images/Image_ignore_pref.png" alt="Ignored Resources Preference Page" border="0">
-<P CLASS="Para">&nbsp;</P>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- >
-  <br>
-     <a href="ref-48a.htm">Ignoring Resources from Version Control</a>
-   </p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-21.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-21.htm
deleted file mode 100644
index ec7dee4..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-21.htm
+++ /dev/null

@@ -1,94 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Install/Update</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Install/Update</H1>
-<P CLASS="Intro"> The following preferences can be changed on the Install/Update 
-  page:</p> 
-<TABLE BORDER="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Option</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Description</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Default</P></TH>
-    </TR>
-  </THEAD>
-  <TBODY>
-    <tr> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Maximum number of 'History' configurations</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Maximum number of configurations you want maintained in the configuration 
-          history. These configurations are maintained to allow you to revert 
-          to a previous configuration of installed feature versions.</p></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          100</P></TD>
-    </tr>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Check digital signatures of downloaded archives</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          This option will check for digital signatures of downloaded archives.</p></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          On</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Valid updates</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Assuming that feature versions use the form 'major.minor.service', you 
-          can select what update level you want to choose from: 
-        <dl>
-          <dt>equivalent</dt> 
-          <dd>Only service updates will be displayed.</dd>
-          <dt>compatible</dt>
-          <dd>Service updates and minor updates will be displayed.</dd>
-        </dl></p></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          equivalent </P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Update Policy</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          The update policy URL that controls the redirection of update sites 
-          within an organization.</p></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          No policy</P></TD>
-    </TR>
-    <TR> 
-      <TD COLSPAN="1" valign="top" align="left"> Proxy settings</TD>
-      <TD COLSPAN="1" valign="top" align="left"> Allows connection to the remote 
-        server from behind the firewall. When enabled, proxy host address (required) 
-        and port number (optional) can be specified.</TD>
-      <TD COLSPAN="1" valign="top" align="left"> No proxy</TD>
-    </TR>
-  </TBODY>
-</TABLE>
-
-
-<p>Here is what the Install/Update preference page looks like:&nbsp;&nbsp; </p>
-<P> </P><img src="../images/Image_pref_inup.png" alt="Install/Update Preference Page" border="0">
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-<br><a HREF="../tasks/tasks-36.htm">Updating Eclipse with the update manager</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a HREF="ref-61.htm">Help Menu</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-21a.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-21a.htm
deleted file mode 100644
index 96b47c4..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-21a.htm
+++ /dev/null

@@ -1,78 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Automatic updates</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Automatic Updates</H1>
-<P CLASS="Intro"> The following preferences can be changed on the Automatic Updates 
-  page:</p> 
-<TABLE BORDER="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Option</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Description</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Default</P></TH>
-    </TR>
-  </THEAD>
-  <TBODY>
-    <tr> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Automatically find new updates and notify me</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          When selected, Update manager will automatically search for update, 
-          as defined&nbsp; by the update schedule</p></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Off</P></TD>
-    </tr>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Update Schedule</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Look for updates on each startup, or once a day or some day a week, 
-          at a predefined time.</p></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          on startup</P></TD>
-    </TR>
-    <TR> 
-      <TD height="23" COLSPAN="1" ROWSPAN="1" align="left" valign="top"> <P CLASS="Para"> 
-          Download Options</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          This option allows you to choose between having Eclipse search for updates 
-          and notifying you of them once they are available or having Eclipse 
-          automatically download new updates and asking you to install them.</p>
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          on startup</P></TD>
-    </TR>
-  </TBODY>
-</TABLE>
-
-
-<P>Here is what the Automatic Updates preference page looks like:&nbsp;&nbsp; 
-</P>
-<P> </P>
-<img src="../images/Image_auto_up.png" alt="Automatic Update Preference Page" border="0">
-<P>&nbsp; </P>
-
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-<br><a HREF="../tasks/tasks-36.htm">Updating Eclipse with the update manager</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a HREF="ref-61.htm">Help Menu</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-22.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-22.htm
deleted file mode 100644
index 6245655..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-22.htm
+++ /dev/null

@@ -1,76 +0,0 @@
-<!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en"><html><head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta http-equiv="Content-Style-Type" content="text/css"><title>Annotations preference page</title>
-   
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"></head><body bgcolor="#ffffff">
-
-<h1 class="Head">Annotations preference page</h1>
-<div class="Para">
-  <p>The following preferences can be changed on the Annotations preference page.</p>
-</div>
-
-<table border="1" cellspacing="0" style="width: 100%;">
-  <caption>
-  </caption>
-  <thead>
-  </thead>
-  <tbody>
-  </tbody>
-  <tbody>
-    <tr> 
-      <th style="width: 25%;"> <div class="Para">Option</div></th>
-      <th> <div class="Para">Description</div></th>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> Show in Text as </td>
-      <td align="left" valign="top">This option controls whether the selected 
-        annotation type is shown in the text. The corresponding text will be underlined 
-        with squiggles or highlighted.<br> </td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Show in Overview 
-          ruler&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
-        </div></td>
-      <td align="left" valign="top"> This option controls whether the overview 
-        ruler on the right side of the text editor is shown.</td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top"> <div class="Para">Show in Vertical ruler&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-          <br>
-        </div></td>
-      <td align="left" valign="top"> This option controls whether the selected 
-        annotation type is shown in the vertical ruler.</td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Color</div></td>
-      <td align="left" valign="top"> <div class="Para">This option controls the 
-          color for the selected annotation type.<br>
-        </div></td>
-    </tr>
-  </tbody>
-</table>
-
-<table border="1" cellspacing="0" style="width: 100%;">
-  <caption>
-  </caption>
-  <thead>
-  </thead>
-  <tbody>
-  </tbody>
-  <tbody>
-  
-  </tbody>
-</table>
-<p></p>
-<p>Here is what the Annotations preference page looks like: </p>
-<p><img src="../images/ref-annotationspref.png" alt="Image of the Annotations preference page"><br>
-</p>
-<p>&nbsp;<br>
-
-</p>
-
-
-</body></html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-23.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-23.htm
deleted file mode 100644
index 514c3b2..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-23.htm
+++ /dev/null

@@ -1,249 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Workbench window layout</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Workbench window layout</H1>
-<P CLASS="Para">
-You can rearrange the layout of Workbench windows as follows:</P>
-<UL CLASS="UnorderedList">
-<LI CLASS="Item">
-Drag views to different positions within the Workbench window.</LI>
-<LI CLASS="Item">
-Drag views to the shortcut bar to create a fast view.</LI>
-<LI CLASS="Item">
-Drag editors such that they are simultaneously visible beside, above, or below
-another editor.</LI>
-<LI CLASS="Item">
-Resize views and editors by dragging the sashes which separate them.</LI>
-</UL>
-<DIV CLASS="Topic">
-<h2>
-Drop cursors</h2>
-<P CLASS="Para">
-<i>Drop cursors</i> indicate where a view will dock when you release your mouse
-button. This indication is relative to the view or editor area underneath the cursor. </P>
-<TABLE BORDER="1" width="669" cellspacing="0">
-<CAPTION>
-Drop Cursors</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1" width="54">
-<P CLASS="Para">
-Cursor</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1" width="113">
-<P CLASS="Para">
-Name</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1" width="480">
-<P CLASS="Para">
-Description</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" width="54">
-<P CLASS="Para">&nbsp;
-</P>
-<img src="../images/ref-1.png"  align="BASELINE" alt="Up arrow">
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="113">
-<P CLASS="Para">
-Dock above</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="480">
-<P CLASS="Para">
-The view will appear above the view underneath the cursor.</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" width="54">
-<P CLASS="Para">&nbsp;
-</P>
-<img src="../images/ref-2.png"  align="BASELINE" alt="Down arrow">
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="113">
-<P CLASS="Para">
-Dock below</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="480">
-<P CLASS="Para">
-The view will appear below the view underneath the cursor.</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" width="54">
-<P CLASS="Para">&nbsp;
-</P>
-<img src="../images/ref-3.png"  align="BASELINE" alt="Right arrow">
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="113">
-<P CLASS="Para">
-Dock to the right</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="480">
-<P CLASS="Para">
-The view will appear to the right of the view underneath the cursor.</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" width="54">
-<P CLASS="Para">&nbsp;
-</P>
-<img src="../images/ref-4.png"  align="BASELINE" alt="Left arrow">
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="113">
-<P CLASS="Para">
-Dock to the left</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="480">
-<P CLASS="Para">
-The view will appear to the left of the view underneath the cursor. </P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" width="54">
-<P CLASS="Para">&nbsp;
-</P>
-<img src="../images/ref-5.png"  align="BASELINE" alt="Stack">
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="113">
-<P CLASS="Para">
-Stack</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="480">
-<P CLASS="Para">
-The view will appear as a tab in the same pane as the view underneath the cursor. </P>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-</DIV>
-<DIV CLASS="Topic">
-<DIV CLASS="Subtopic">
-<H2>
-Fast views</H2>
-<P CLASS="Para">
-From a view's title bar context menu, you can select Fast View to minimize the view
-as a&nbsp; button on the shortcut bar.</P>
-<P CLASS="Para">
-If a view is minimized in this way, you can click its
-button on the shortcut bar to bring it up in a fast view. To revert the fast
-view back to a docked view again, select the <i>Fast View</i> button on its title
-bar.</P>
-<A HREF="ref-3.htm" CLASS="XRef">See Shortcut Bar</A></DIV>
-<DIV CLASS="Subtopic">
-<H2 CLASS="Head">
-Double-Click</H2>
-    <P CLASS="Para"> Double-clicking a view or editor's title bar maximizes the 
-      part in the Workbench window.</P>
-  </DIV>
-  <DIV CLASS="Subtopic">
-<H2 CLASS="Head"> Title bar context menu and fast view toolbars</H2>
-    <P CLASS="Para"> From the context menu of a view or editor's title bar, you 
-      can select how you want the view to appear within the Workbench window.</P>
-    <TABLE BORDER="1" cellspacing="0">
-      <CAPTION>
-      View and editor title bar context menu options 
-      </CAPTION>
-      <THEAD>
-        <TR> 
-          <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> <A NAME="pgfId-1096571">O</A>ption</P></TH>
-          <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Description</P></TH>
-        </TR>
-      </THEAD>
-      <TBODY>
-        <TR> 
-          <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-              Restore</P></TD>
-          <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-              Restores the view to its originating (non-maximized/non-minimized) 
-              size and position within the Workbench.</P></TD>
-        </TR>
-        <TR> 
-          <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-              Fast View<BR>
-              (views only)</P></TD>
-          <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-              Minimizes the view and places a button for it in the shortcut bar.</p>
-            <P CLASS="Para"> This option, when used in a fast view, will restore 
-              the view to its originating (docked) position in the Workbench.</P>
-            <P CLASS="Para"> <A HREF="ref-3.htm" CLASS="XRef">See Shortcut Bar</A> </p>
-          </TD>
-        </TR>
-        <TR> 
-          <TD COLSPAN="1" valign="top" align="left">Restore</TD>
-          <TD COLSPAN="1" valign="top" align="left">Restores the view or editor 
-            to its originating (non-maximized/non-minimized) size and position 
-            within the Workbench.</TD>
-        </TR>
-        <TR> 
-          <TD COLSPAN="1" valign="top" align="left">Move</TD>
-          <TD COLSPAN="1" valign="top" align="left">Move the part or part group.</TD>
-        </TR>
-        <TR> 
-          <TD COLSPAN="1" valign="top" align="left">Size</TD>
-          <TD COLSPAN="1" valign="top" align="left">Change the size of the part 
-            in the direction specified.</TD>
-        </TR>
-        <TR> 
-          <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-              Maximize</P></TD>
-          <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-              Maximizes the part in the Workbench window.</P></TD>
-        </TR>
-        <TR> 
-          <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-              Minimize</P></TD>
-          <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-              Minimizes the part in the Workbench window.</P></TD>
-        </TR>
-        <TR> 
-          <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-              Close</P></TD>
-          <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-              Closes the part.&nbsp;&nbsp;</P></TD>
-        </TR>
-        <TR> 
-          <TD COLSPAN="1" valign="top" align="left"><p>Close Others</p>
-            <p>(editors only)</p></TD>
-          <TD COLSPAN="1" valign="top" align="left">Closes all editors except 
-            the current editor.</TD>
-        </TR>
-        <TR> 
-          <TD COLSPAN="1" valign="top" align="left"><p>Close All </p>
-            <p>(editors only)</p></TD>
-          <TD COLSPAN="1" valign="top" align="left">Closes all editors.</TD>
-        </TR>
-      </TBODY>
-    </TABLE>
-</DIV>
-</DIV>
-<P>Here is what a view's context menu looks like:
-</P>
-
-
-<P><img src="../images/Image229_view_popup.png" alt="View's context menu" border="1" >
-</P>
-<P>Here is what an editor's context menu looks like:
-</P>
-
-
-<P><img src="../images/Image229_editor_popup.png" alt="Editor's context menu" border="1" >
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-24.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-24.htm
deleted file mode 100644
index a1bbc29..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-24.htm
+++ /dev/null

@@ -1,90 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Editor area</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Editor area</H1>
-<P CLASS="Intro">
-
-The editor area is where you modify the contents of files in the Workbench.</p>
-<P CLASS="Para">
-Here is what the editor area looks like when multiple files are open and a text
-file is being edited:</P>
-<P CLASS="Para">
-<img src="../images/Image230_editor_area.png" alt="Editor Area" border="0" ></P>
-<DIV CLASS="Topic" style="width: 559; height: 402"> 
-  <h2>
-Marker bar</h2>
-<P CLASS="Para">
-The marker bar is the vertical bar located at the left of the editor area.&nbsp;&nbsp;</P>
-<P CLASS="Para">
-Here is what the marker bar looks like:</P>
-  <P CLASS="Para"> <img src="../images/Image231_marker_bar.png" alt="Marker Bar" border="0" ></P>
-<h2>Markers</h2>
-<P CLASS="Para">
-Markers are displayed in the marker bar, to the left of the text editor.</P>
-<P CLASS="Para">
-Depending on the type of file displayed in the editor area, three kinds of markers
-may be displayed:</P>
-<UL CLASS="UnorderedList">
-<LI CLASS="Item">
-Bookmarks </LI>
-<LI CLASS="Item">
-Task markers (for associated tasks) </LI>
-<LI CLASS="Item">
-Debugging breakpoints </LI>
-</UL>
-<P CLASS="Para">
-You can create and associate a marker with a specific line in a file by accessing the context menu from the marker bar,
-which is directly to the left of that line. </P>
-<P CLASS="Para">
-Here is what the context menu of the marker bar looks like: </P>
-<P CLASS="Para">
-<img src="../images/Image232_marker_context.png" alt="Marker Bar Menu" border="1" > </P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Types of editors</h2>
-<P CLASS="Para">
-The Workbench uses three types of editors:</P>
-<UL CLASS="UnorderedList">
-<LI CLASS="Item">
-Internal: These editors are launched inside the editor area in the Workbench window.</LI>
-<LI CLASS="Item">
-External: You can go outside the Workbench in the file system, edit a Workbench file outside the Workbench, and save the edited file. For example, 
-imagine that you add an SGML file to the Workbench. Later, you go into the file system and open the 
-file in an SGML editor, then save the file. The edited SGML file is still represented in the Workbench, even 
-though you did not edit the file in the Workbench. If you associate a file type with an external editor in 
-the Workbench
-(<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.FileEditors)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>General &gt; Editors &gt; File Associations</b></a>
-preference page), then the Workbench
-will launch this external editor.</LI>
-<LI CLASS="Item">
-ActiveX: On Microsoft Windows platforms, the Workbench makes use of ActiveX controls for applications that allow for them. For example, Microsoft Word supports being embedded as an OLE
-document. Thus if you have a <i>.doc</i> file in the Workbench, and Word is registered as the editor for
-<i>.doc </i>files in your operating system, then opening the file will launch Word as an OLE document within the Workbench editor area. Notice how OLE documents also add such features as menus
-and toolbar buttons.</LI>
-</UL>
-<p>The following illustrates Microsoft Word embedded as an OLE document:</p>
-<DIV CLASS="Figure">
-    <DIV> <IMG SRC="../images/ref-7.png"  alt="Workbench with OLE Editor" > 
-    </DIV>
-</DIV>
-</DIV>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-25.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-25.htm
deleted file mode 100644
index 7b11c23..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-25.htm
+++ /dev/null

@@ -1,101 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-             
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-             
-  <meta http-equiv="Content-Style-Type" content="text/css">
-              
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>Compare editor</title>
-</head>
-  <body bgcolor="#ffffff">
-       
-<h1 class="Head"> Compare editor</h1>
-       
-<p class="Para"> You can view the differences between two files by comparing 
- them.    You can compare different files, you can compare versions in 
- the Workbench    with versions in the repository, or with the local edit history.&nbsp;
- In some    cases you can compare three files (when a common ancestor exists).
- </p>
-       
-<p class="Para"> After a comparison is carried out, the compare editor opens 
- in    the editor area. In the compare editor, you can&nbsp; browse through 
- all the    differences and copy highlighted differences between the compared 
- resources.    You can save changes to resources that are made in the comparison 
- editor. </p>
-       
-<p class="Para">Here is how the compare editor looks when you open it from a CVS 
-Workspace synchronization..</p>
-       
-<p class="Para"><img
- src="../images/compare-editor.png"
- alt=" Picture of 3-paned editor. Top pane compares project structure; bottom 2 panes (side by side) compare lines of source."  border="0" align="top"> 
-</p>
-       
-<div class="Topic">    
-<div class="Subtopic">    
-<h2>Toolbar</h2>
-       
-<p>The toolbar of the Compare editor includes the following buttons:</p>
-           
-<dl>
-  <dt>Control Visibility of Ancestor Pane</dt>
-  <dd>There are two conditions under which a three way compare will occur, 
-          both when using the Team version management support: when comparing 
- a          file that is in conflict, and when comparing a file being merged 
- from          a branch. In both cases, the system will determine a common 
- ancestor in          the repository to compare the conflict or merge against. 
- This button determines          the visibility of the third editor. By default, 
- the ancestor pane is not          visible.</dd>
-  <dt>Perform Three way/Two way Compare</dt>
-  <dd>The compare editor can be toggled between performing a three way compare 
-          or a two way compare which ignores the common ancestor.</dd>
-  <dt>Copy All from Left to Right</dt>
-  <dd>Copies the entire contents of the file in the left pane into the file 
-          in the right pane, making the contents of the two files identical.&nbsp;</dd>
-  <dt>Copy All Non-Conflicting Changes from Right to Left</dt>
-  <dd>Copies all the non-conflicting changes from the right pane into the left
-  pane. Conflicting changes must be copied individually.</dd>
-  <dt>Copy Current Change from Left to Right</dt>
-  <dd>Merges changes in two files by copying the highlighted change in the 
-          left pane into the highlighted fragment on the right.&nbsp; This 
- will          overwrite the highlighted fragment in the right pane.</dd>
-  <dt>Copy Current Change from Right to Left</dt>
-  <dd>Does the opposite of the one just described.</dd>
-  <dt>Select Next Difference</dt>
-  <dd>Highlights the next difference that is found between the compared resources.</dd>
-  <dt>Select Previous Difference</dt>
-  <dd>Highlights the previous difference that is found between the compared 
-          resources.</dd>
-</dl>
-           
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"
- >
-   <br>
-          <a href="../concepts/concepts-30.htm">Synchronizing with a CVS
-repository</a>        <br>
-   <a href="../concepts/concepts-29.htm">Three way comparisons</a></p>
-         
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"
- >
-   <br>
-    <a href="../tasks/tasks-68.htm">Comparing resources</a><br>
-    <a href="../tasks/tasks-115.htm">Synchronizing with the repository</a><br>
-    <a href="../tasks/tasks-68dg.htm">Merging changes in the compare editor</a><br>
-    <a href="../tasks/tasks-113b.htm">Resolving conflicts</a><br>
-    <a href="../tasks/tasks-68b.htm">Setting preferences for comparing files</a><br>
-    <a href="../tasks/tasks-101.htm">Comparing resources with repository
-versions</a>    </p>
-      </div>
-    </div>
-        
-
-        
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-26.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-26.htm
deleted file mode 100644
index 9fc4e65..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-26.htm
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"><title>Search view</title></head><body bgcolor="#ffffff">
-
-<h1>Search view</h1>
-
-<p>
-This view displays the results of a search.&nbsp;&nbsp;</p>
-
-<p>
-Text searches will only search for expressions in files with extensions (file
-types) specified in the search dialog.</p>
-
-<p>
-Here is what the Search view looks like:</p>
-
-<p>
-<img src="../images/Image237_search_view.png" alt="Search View" border="0" ></p>
-
-<dl>
-<dt>Show Next Match</dt>
-<dd>
-This command highlights the next match of the search
-expression in the editor area, opening the file if required.</dd>
-
-<dt>Show Previous Match</dt>
-<dd>
-This command highlights the previous match of the
-search expression in the editor area, opening the file if required.</dd>
-
-
-<dt>Remove Selected Matches</dt>
-<dd>Removes all highlighted matches from the search results.</dd>
-
-<dt>Remove All Matches</dt>
-<dd>Remove all matches from the search results.</dd>
-
-<dt>Expand All</dt>
-<dd>Expand all matches in the hierarchical view.</dd>
-
-<dt>Collapse All</dt>
-<dd>Collapse all matches in the hierarchical view.</dd>
-
-<dt>Cancel Current Search</dt>
-<dd>Cancel a search that is running.</dd>
-
-
-<dt>Previous Search Results</dt>
-<dd>
-This command allows you to browse previously
-conducted searches and repeat a previous search.&nbsp; You can select a previous
-search from the drop-down menu or clear the search history.</dd>
-
-</dl>
-
-<p><img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-<br>
-<a href="../concepts/csearchview.htm">Search view</a><br>
-</p>
-
-<p><img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-<br>
-<a href="../tasks/tasks-84b.htm">Searching for files</a><br>
-<a href="../tasks/tasks-84.htm">Searching for text within a file</a><br>
-</p>
-
-<p><img src="../images/ngrelr.png" alt="Related reference" border="0" >
-<br>
-<a href="ref-45.htm">File search</a><br>
-</p>
-
-
-
-</body></html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-27.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-27.htm
deleted file mode 100644
index fb39b06..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-27.htm
+++ /dev/null

@@ -1,267 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Navigator view</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>
-Navigator view</H1>
-<P CLASS="Intro">
-
-This view provides a hierarchical view of the resources in the Workbench.</p>
-<P CLASS="Para">
-Here is what the Navigator view looks like:</P>
-<P CLASS="Para">
-<img src="../images/Image241_nav_view.png" alt="Navigator View" border="0" ></P>
-<p CLASS="Head">
-To add the Navigator view to the current perspective, click
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.ResourceNavigator)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Navigator</b></a>.
-</p>
-<P CLASS="Para">&nbsp;
-</P>
-<h2>Toolbar</h2>
-<DIV CLASS="Topic">
-<h3>
-Back</h3>
-<P CLASS="Para">
-This command displays the hierarchy that was displayed immediately prior to the current display.&nbsp;
-For example, if you Go Into a resource, then the Back command in the resulting display returns the view to the same hierarchy from which you activated the
-<i> Go Into</i> command. The hover help for this button tells you where it will
-take you. This command is similar to the Back button in a web browser.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h3>
-Forward</h3>
-<P CLASS="Para">
-This command displays the hierarchy that was displayed immediately after the current display.&nbsp;
-For example, if you've just selected the Back command, then selecting the Forward command in the resulting display returns the view to the same hierarchy from which you activated the Back command.&nbsp;The
-hover help for this button tells you where it will take you.
-This command is similar to the Forward button in a web browser.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h3>Up</h3>
-<P CLASS="Para">
-This command displays the hierarchy of the parent of the
-current highest level resource. The hover help for this button tells you where
-it will take you.</P>
-</DIV>
-<H3>Collapse All</H3>
-<P>This command collapses the tree expansion state of all resources in the
-view.</P>
-<H3>Link with Editor</H3>
-<P>This command toggles whether the Navigator view selection is linked to
-the active editor. When this option is selected, changing the active editor
-will automatically update the Navigator selection to the resource being
-edited.</P>
-<P><BR>
-</P>
-<H2>Menus</H2>
-<P>Click the black upside-down triangle icon to
-open a menu of items specific to the Navigator view. Right-click inside
-the view to open a context menu.&nbsp;</P>
-<H3>Select Working Set</H3>
-<P>Opens the <B>Select Working Set</B> dialog to allow selecting a working set for the Navigator view.</P>
-<H3>Deselect Working Set</H3>
-<P>Deselects the current working set. </P>
-<H3>Edit Active Working Set</H3>
-<P>Opens the <B>Edit Working Set</B> dialog to allow changing the current working set.</P>
-<DIV CLASS="Topic">
-<h3>
-Sort</h3>
-<P CLASS="Para">
-This command sorts the resources in the Navigator view according to the selected schema:</P>
-<UL CLASS="UnorderedList">
-<LI CLASS="Item">
-<b>
-By Name</b>:&nbsp; Resources are sorted alphabetically, according to the full name
-of the resource (e.g., A.TXT, then B.DOC, then C.HTML, etc.)</LI>
-<LI CLASS="Item">
-<b>By Type</b>:&nbsp; Resources are sorted alphabetically by file type/extension (e.g.,
-all DOC files, then all HTML files, then all TXT files, etc.).</LI>
-</UL>
-</DIV>
-<DIV CLASS="Topic">
-<h3>
-Filters</h3>
-<P CLASS="Para">
-This command allows you to select filters to apply to the view so that you can show or hide various resources as needed.&nbsp;
-File types selected in the list will not be shown in the Navigator.&nbsp; Here
-is what the file filters dialog looks like:</P>
-<P CLASS="Para">
-<img src="../images/Image210_filefilter.png" alt="Filters dialog" border="0" ></P>
-</DIV>
-<H3>Link with Editor</H3>
-<P>See the toolbar item description above.</P>
-<P><BR>
-In addition to these menu items, the Navigator view menu shows a list of
-recently used working sets that have been selected in the view.</P>
-<P><BR>
-</P>
-<h2>Context menu</h2>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">
-New</H3>
-<P CLASS="Para">
-This command allows you to create a new resource in the Workbench. Select the
-type of resource to create from the submenu.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">
-Go Into</H3>
-<P CLASS="Para">
-This command displays a new hierarchy in the Navigator view, with the children
-of the selected resource as its contents.&nbsp; For example if you Go Into a
-project, the Navigator will be refocused on the immediate files and folders of
-the project.</P>
-</DIV>
-<DIV CLASS="Topic">
-
-<h3 CLASS="Head">Open</H3>
-<P CLASS="Para">This command opens the selected resource.&nbsp; If the resource is a file that is associated with an editor, then the Workbench launches the associated internal, external, or ActiveX editor and opens the file in that editor.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">Open With</H3>
-<P CLASS="Para">
-This command allows you to open an editor other than the default editor for the selected resource.&nbsp;
-Specify the editor with which to open the resource by selecting an editor from the submenu.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">
-Copy</H3>
-<P CLASS="Para">This command copies the selected resource to the clipboard.</P>
-</DIV>
-<H3>Paste</H3>
-<P>This command pastes resources on the clipboard into the selected project
-or folder. If a resource is selected the resources on the clipboard are
-pasted as siblings of the selected resource.</P>
-<h3 CLASS="Head">
-Delete</H3>
-<P CLASS="Para">This command deletes the selected resource from the workspace.</P>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">Move</H3>
-<P CLASS="Para">
-This command moves the selected resource to another location.
-A dialog will appear, prompting for the destination location to which the resource
-will be moved.&nbsp;&nbsp;</P>
-</DIV>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">
-Rename</H3>
-<P CLASS="Para">
-This command allows you to specify a new name for the selected resource.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">
-Import</H3>
-<P CLASS="Para">
-This command opens the import wizard and allows you to select resources
-to import into the Workbench.
-</P>
-</DIV>
-
-<DIV CLASS="Topic">
-<h3 CLASS="Head">
-Export</H3>
-<P CLASS="Para">
-This command opens the export wizard and allows you to export resources
-to an external location.
-</P>
-</DIV>
-
-<h3 CLASS="Head">
-Refresh</H3>
-<P CLASS="Para">This command refreshes the Workbench's view of the selected resource and
-its children. For example, this is used when you create a new file for
-an existing project outside the Workbench and want the file to appear in
-the Navigator view.</P>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">Close Project</H3>
-<P CLASS="Para">The close project command is visible when an open project is selected.
-This command closes the selected project.</P>
-</DIV>
-<H3>Open Project</H3>
-<P>The open project command is visible when a closed project is selected.
-This command opens the selected project.</P>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">
-Team</H3>
-  <p CLASS="Head"> Menu items in the Team submenu are related to version control 
-    management and are determined by the version control management system that 
-    is associated with the project. Eclipse provides the special menu item<b> 
-    Share Project...</b> for projects that are not under version control management. 
-    This command will present a wizard that allows the user to choose to share 
-    the project with any version control management systems that has been added 
-    to Eclipse. Eclipse ships with support for CVS.</p>
-  </DIV>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">Compare With</H3>
-
-<P CLASS="Para">
-Commands on the Compare With submenu allow you to do one of the following
-types of compares: </P>
-  <UL CLASS="UnorderedList">
-    <LI CLASS="Item"> Compare two or three selected resources with each other</LI>
-    <LI CLASS="Item"> Compare the selected resource with remote versions (if the 
-      project is associated with a version control management system).</LI>
-    <LI CLASS="Item"> Compare the selected resource with a local history state</LI>
-  </UL>
-
-<P CLASS="Para">After you select the type of compare you want to do, you will 
-      either see a compare editor or a compare dialog. In the compare editor, 
-      you can browse and copy various changes between the compared resources.&nbsp; 
-      In the compare dialog, you can only browse through the changes.&nbsp;&nbsp;</P>
-
-</DIV>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">
-Replace With</h3>
-  <P CLASS="Para"> Commands on the Replace With submenu allow you to replace the 
-    selected resource with another state from the local history. If the project 
-    is under version control management, there may be additional items supplied 
-    by the version control management system as well.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">
-Properties</H3>
-  <P CLASS="Para"> This command displays the properties of the selected resource. 
-    The kinds of properties that are displayed depend on what type of resource 
-    is selected. Resource properties may include (but are not limited to):</P>
-  <UL CLASS="UnorderedList">
-    <LI CLASS="Item">Path relative to the project in which it is held</LI>
-    <LI CLASS="Item">Type of resource</LI>
-    <LI CLASS="Item">Absolute file system path, or name of path variable when using linked resources</LI>
-    <LI CLASS="Item">Resolved path variable when using a path variable for a linked resource</LI>
-    <LI CLASS="Item">Size of resource</LI>
-    <LI CLASS="Item">Last modified date</LI>
-    <LI CLASS="Item">Read-only status</LI>
-    <LI CLASS="Item">Derived resource status</LI>
-    <LI CLASS="Item">Execution arguments, if it is an executable resource</LI>
-    <LI CLASS="Item">Program launchers, if it is launchable</LI>
-    <LI CLASS="Item">Project dependencies, if any</LI>
-  </UL>
-</DIV>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br><a href="../concepts/concepts-26.htm">Team programming with CVS</a>
-<br><A HREF="../concepts/concepts-29.htm">Three-way compare</A>
-<br><a href="../concepts/concepts-13.htm">Linked resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="ref-25.htm">Compare editor</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-28.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-28.htm
deleted file mode 100644
index de95a13..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-28.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Bookmarks view</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Bookmarks view</H1>
-<P CLASS="Para">
-The Bookmarks view displays user defined bookmarks.</P>
-<P CLASS="Para">
-<img align="texttop" border="0" src="../images/Image244_bmark_view.png" alt="Bookmarks view" ></P>
-<p CLASS="Head">
-To add the Bookmarks view to the current perspective, click
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.BookmarkView)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Bookmarks</b></a>.
-</p>
-<DIV CLASS="Subtopic">
-<P CLASS="Para">
-The Description column contains a description of the bookmark.&nbsp;
-You can edit the description by selecting <b>Properties</b> from the context menu.</P>
-</DIV>
-<DIV CLASS="Subtopic">
-<P CLASS="Para">
-The Resource and In Folder columns provide the name and location of the resource
-associated with each bookmark.</P>
-</DIV>
-<P CLASS="Para">
-The Location column indicates the line number of the bookmark within its associated resource.</P>
-<h2>Toolbar</h2>
-<p>The toolbar of the Bookmarks view includes the following buttons.</p>
-<dl>
-  <dt>Delete</dt>
-  <dd>Delete the selected bookmark.</dd>
-  <dt>Go to</dt>
-  <dd>Open the bookmark's resource and navigate to the bookmarked region.</dd>
-</dl>
-<h2>Menus</h2>
-<p>Click the icon at the left end of the view's title bar to open a menu of items
-generic to all views. Click the black upside-down triangle icon to open a menu of items
-specific to the Bookmarks view. Right-click inside the view to open a context menu.&nbsp;</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-81b.htm">Creating a bookmark for an entire file</a><br><a href="../tasks/tasks-81.htm">
-Creating a bookmark within a file</a><br><a href="../tasks/tasks-82.htm">
-Deleting a Bookmark</a><br></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-29.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-29.htm
deleted file mode 100644
index 8cfd440..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-29.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Properties view</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Properties view</H1>
-<P CLASS="Para">
-This view displays property names and basic properties of a selected resource.
-Here is an example:</P>
-<P CLASS="Para">
-<img src="../images/Image240_props_view.png" alt="Properties view" border="0" ></P>
-<P CLASS="Para">Toolbar buttons allow you to toggle whether to display
-properties by category and whether to filter advanced properties. Another
-toolbar button allows you to restore the selected property to its default value.</P>
-<P>To see more detailed information about a resource than the Properties view
-gives you, right-click the resource name in one of the navigation views and select
-Properties from the pop-up menu.
-</P>
-<p CLASS="Head">
-To add the Properties view to the current perspective, click
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.PropertySheet)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Properties</b></a>.
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-3.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-3.htm
deleted file mode 100644
index edceba8..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-3.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Perspective bar</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Perspective Bar</H1>
-<P CLASS="Intro">
-The perspective bar allows quick access to perspectives that are currently open, as well
-as providing an easy way to open a new perspective.&nbsp; The perspective bar may be docked in three different positions.  It may be docked in the upper right corner (the default position), the upper left corner (under the main toolbar) and to the far left.</p>
-<P CLASS="Para">
-Here is an example of what the perspective bar looks like:&nbsp;</P>
-<P CLASS="Para">
-<img src="../images/Image211_perspective.png" alt="Perspective Bar" border="0"></P>
-<DIV CLASS="Topic">
-<h3>
-Open Perspective</h3>
-<P CLASS="Para">
-This command opens a new perspective which is
-selected by the user from a drop-down menu.&nbsp; All of the perspectives that are open within a single Workbench window are
-shown on the shortcut bar.</P>
-</DIV>
-<DIV CLASS="Topic"> 
-  <h3>Perspective Buttons</h3>
-  <P CLASS="Para"> These buttons provide a quick way to switch to one of the open 
-    perspectives in the current Workbench window.&nbsp; </P>
-  <P CLASS="Para"></P>
-  <h3>Available Perspectives</h3>
-  <p>There are several available perspectives, while one is set as a default, 
-    others can be manually added to the perspective bar. To add new perspectives 
-    to your workspace, click <strong>Open Perspective</strong> <img src="../images/open_persp.png" alt="Open Perspective Icon" border="0" >, 
-    select <strong>Other</strong> and choose from the following
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective")'>
-    <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-    available perspectives</a>:</p>
-</DIV>
-<ul>
-  <li>CVS Repository Exploring;</li>
-  <li>Debug;</li>
-  <li>Java;</li>
-  <li>Java Browsing;</li>
-  <li>Java Type Hierarchy;</li>
-  <li>Plug-in Development;</li>
-  <li>Resource;</li>
-  <li>Team Synchronizing.</li>
-</ul>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" > <br>
-  <a href="ref-6.htm">Perspectives</a> <br>
-  <a href="ref-4.htm">View Toolbars</a> <br>
-  <a href="ref-2.htm">Workbench Toolbar</a> <br>
-  <a href="ref-23.htm">Workbench Window Layout</a> </p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-30.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-30.htm
deleted file mode 100644
index 4f694c0..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-30.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Outline view</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<body>
-<H1 CLASS="Head">
-Outline view</H1>
-
-<P>This view displays an outline of a structured file
-that is currently open in the editor area, and&nbsp; lists structural
-elements.&nbsp;The contents of the outline view are editor-specific. In the
-example below, which is for a Java source file, the structural elements are classes, variables, and methods.
-The contents of the toolbar are also editor-specific.
-</p>
-
-<P><img src="../images/ref-8.png" alt="Picture of Outline view showing structure for a Java file" border="0" >
-</p>
-<p CLASS="Head">
-To add the Outline view to the current perspective, click
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.ContentOutline)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Outline</b></a>.
-</p>
-</body>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-30a.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-30a.htm
deleted file mode 100644
index e584615..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-30a.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>CVS views</title>
-
-</HEAD>
-<body>
-<H1 CLASS="Head">
-CVS views</H1>
-
-<P>There are several CVS specific views, the CVS Repositories view, the CVS Resource 
-History view, the CVS Console view and the Synchronize view.
-</p>
-<P>  See Team Support in the
-Reference section for details on these views.
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- >
-  <br>
-     <a href="ref-32.htm">CVS Repositories view</a><br>
-     <a href="ref-32a.htm">CVS Resource History View</a><br>
-     <a href="ref-32b.htm">CVS Console view</a><br>
-     <a href="ref-33.htm">Synchronize view</a>
-     
-   </p>
-</body>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-31.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-31.htm
deleted file mode 100644
index 9526133..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-31.htm
+++ /dev/null

@@ -1,101 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Tasks view (reference)</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Tasks view</H1>
-<P CLASS="Para"> The Tasks view displays tasks that you add manually. You can 
-  associate a task with a resource in the Workbench, but this is not required.</P>
-<p><img src="../images/Image243_tasks_view.png" alt="Picture of the Tasks view with two dummy tasks added to it." border="0"></p>
-<p CLASS="Head">
-By default, the Tasks view is included in the Resources perspective. To add it
-to the current perspective, click
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.TaskList)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Tasks</b></a>.
-</p>
-<p CLASS="Head">
-The following icons are used by the Tasks view:</p>
-<table border="1" cellspacing="0" cellpadding="5" summary="Icon table">
-  <tr> 
-    <th valign="top" align="center">Icon</th>
-    <th valign="top" align="left">Description</th>
-  </tr>
-  <tr> 
-    <td valign="top" align="center"><img src="../images/ref-21.png" alt=" High priority task item" border="0" ></td>
-    <td valign="top" align="left"> High priority task</td>
-  </tr>
-  <tr> 
-    <td valign="top" align="center"><img src="../images/ref-23.png" alt=" Low priority task icon" border="0"></td>
-    <td valign="top" align="left"> Low priority task </td>
-  </tr>
-  <tr> 
-    <td valign="top" align="center"><img src="../images/ref-25.png"  alt="Completed task icon" border="0"></td>
-    <td valign="top" align="left"> Completed task </td>
-  </tr>
-    <tr> 
-    <td valign="top" align="center"><img src="../images/addtask.png" alt="Add task" border="0" ></td>
-    <td valign="top" align="left"> Add task</td>
-  </tr>
-  <tr> 
-    <td valign="top" align="center"><img src="../images/delete_edit.png" alt="Delete" border="0"></td>
-    <td valign="top" align="left"> Delete</td>
-  </tr>
-  <tr> 
-    <td valign="top" align="center"><img src="../images/filter_ps.png" alt="Filter" border="0" ></td>
-    <td valign="top" align="left"> Filter</td>
-  </tr>
-
-</table>
-
-<p CLASS="Head"> The first column indicates whether the task is completed. Completed 
-  tasks are flagged with a check mark, which you add manually.</p>
-<p CLASS="Head"> The second column indicates whether the task is high, normal, 
-  or low priority.&nbsp;</p>
-<DIV CLASS="Subtopic">
-<P CLASS="Para">
-The Description column contains a description of the line item.&nbsp;
-You can edit the description of user-defined tasks by selecting <b>Properties</b> from the context menu.</P>
-</DIV>
-<DIV CLASS="Subtopic">
-<P CLASS="Para">
-The Resource and In Folder columns provide the name and location of the resource
-associated with each line item.</P>
-</DIV>
-<P CLASS="Para">
-The Location column indicates the line number of the line item within its associated resource.</P>
-<h2>Toolbar</h2>
-<p>The toolbar of the Tasks view includes the following buttons.</p>
-<dl>
-  <dt>Add task</dt>
-  <dd>Manually add a &quot;to do&quot; item to the Tasks view.</dd>
-  <dt>Delete</dt>
-  <dd>Delete the selected line item.</dd>
-  <dt>Filter</dt>
-  <dd>Filter the view according to the type of item.</dd>
-</dl>
-<h2>Menus</h2>
-<p>Click the icon at the left end of the view's title bar to open a menu of items 
-  generic to all views. Click the upside-down triangle icon to open a menu of 
-  items specific to the Tasks view. Right-click inside the view to open a context 
-  menu.&nbsp;</p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-77.htm">Adding line items in the Tasks view</a>
-<a href="../tasks/tasks-77b.htm"><br>Associating a task with a resource</a>
-<a href="../tasks/tasks-78.htm"><br>Deleting tasks</a>
-<a href="../tasks/tasks-79.htm"><br>Filtering the task view</a></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-31a.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-31a.htm
deleted file mode 100644
index b41323a..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-31a.htm
+++ /dev/null

@@ -1,90 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Problems view (reference)</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Problems view</H1>
-<P CLASS="Para"> The Problems view displays system-generated errors, warnings, 
-  or information associated with a resource. These are typically produced by builders. 
-  For example, if you save a Java source file that contains syntax errors, the 
-  errors will automatically be logged in this view.</P>
-<p><img src="../images/prob.png" alt="Picture of the Problems view with two warnings added to it." border="0" ></p>
-<p CLASS="Head"> By default, the Problems view is included in the Resources perspective. 
-  To add it to the current perspective, click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.ProblemView)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Window &gt; Show View &gt; Other... &gt; General &gt; Problems</b></a>.
-</p>
-<p CLASS="Head"> The following icons are used by the Problems view:</p>
-<table border="1" cellspacing="0" cellpadding="5" summary="Icon table">
-  <tr>
-    <th valign="top" align="center">Icon</th>
-    <th valign="top" align="left">Description</th>
-  </tr>
-  <tr>
-    <td valign="top" align="center"><img src="../images/ref-20.png" alt=" Information icon" border="0" ></td>
-    <td valign="top" align="left">
-      Information&nbsp;    </td>
-  </tr>
-  <tr>
-    <td valign="top" align="center"><img src="../images/ref-22.png" alt="Warning icon" border="0"></td>
-    <td valign="top" align="left">
-      Warning    </td>
-  </tr>
-  <tr>
-    <td valign="top" align="center"><img src="../images/ref-24.png" alt="Error icon" border="0"></td>
-    <td valign="top" align="left">
-      Error    </td>
-  </tr>
-  <tr> 
-    <td valign="top" align="center"><img src="../images/delete_edit.png" alt="Delete" border="0"></td>
-    <td valign="top" align="left"> Delete</td>
-  </tr>
-  <tr> 
-    <td valign="top" align="center"><img src="../images/filter_ps.png" alt="Filter" border="0" ></td>
-    <td valign="top" align="left"> Filter</td>
-  </tr>
-</table>
-
-<p CLASS="Head"> The first column indicates whether the line item is a task or 
-  a compiler generated error, warning or info.</p>
-<DIV CLASS="Subtopic">
-<P CLASS="Para">
-The Description column contains a description of the line item.&nbsp;
-You can edit the description of user-defined tasks by selecting <b>Properties</b> from the context menu.</P>
-</DIV>
-<DIV CLASS="Subtopic">
-<P CLASS="Para">
-The Resource and In Folder columns provide the name and location of the resource
-associated with each line item.</P>
-</DIV>
-<P CLASS="Para">
-The Location column indicates the line number of the line item within its associated resource.</P>
-<h2>Toolbar</h2>
-<p>The toolbar of the Problems view includes the following buttons.</p>
-<dl>
-  <dt>Delete</dt>
-  <dd>Delete the selected line item.</dd>
-  <dt>Filter</dt>
-  <dd>Filter the view according to the type of item.</dd>
-</dl>
-<h2>Menus</h2>
-<p>Click the icon at the left end of the view's title bar to open a menu of items 
-  generic to all views. Click the upside-down triangle icon to open a menu of 
-  items specific to the Problems view. Right-click inside the view to open a context 
-  menu.&nbsp;</p>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-32.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-32.htm
deleted file mode 100644
index ebedafa..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-32.htm
+++ /dev/null

@@ -1,220 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-         
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-         
-  <meta http-equiv="Content-Style-Type" content="text/css">
-          
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>CVS Repositories view</title>
-    
-</head>
- <body bgcolor="#ffffff">
-     
-<h1> CVS Repositories view</h1>
-     
-<p class="Para">The CVS Repositories view, which is part of the CVS Repository
-    Exploring perspective, shows the CVS repository locations that you have
- added    to your Workbench.&nbsp;Expanding a location reveals the main trunk
- (HEAD),    project versions and branches in that repository. You can further
- expand the    project versions and branches to reveal the folders and files
- contained within    them. </p>
-     
-<p>The pop-up menu for this view also allows you to specify new repository
- locations.    Use the CVS Repositories view to check out resources from
- the repository    to the Workbench, configure the branches and versions
-shown  by the view, view    resource history, and compare resource versions.
-</p>
-     
-<p class="Para"> Here is what the CVS Repositories view looks like:</p>
-     
-<p class="Para"> <img
- src="../images/Image242_repo_view.png" alt="CVS Repositories View"  border="0" align="top"> 
-</p>
-     
-     
-  
-<p>There are two types of folders displayed in the repositories view. For the 
-  most part, they can be treated in the same fashion. That is, they can be checked 
-  out from the Repositories view, etc. However, there are some cases where modules 
-  cannot be expanded in the Repositories view even though they can still be checked 
-  out. </p>
-<table width="75%" border="1">
-  <tr>
-    <td width="9%" align="center"><img src="../images/cvs_folder_rep.png"></td>
-    <td width="91%">A CVS module that maps to a folder on the CVS server.</td>
-  </tr>
-  <tr>
-    <td align="center"><img src="../images/cvs_module_rep.png"></td>
-    <td>A CVS module defined in the CVSROOT/modules file of the repository.</td>
-  </tr>
-</table>
-<p>Like other views in the Workbench, the CVS Repositories view has its own toolbar. 
-  Toolbar buttons are provided for refreshing the view, navigating and creating 
-  new repository locations. The toolbar also contains a drop-down menu that allows 
-  the user to filter the view by working set.</p>
-       
-<h2>Toolbar</h2>
-
-<div class="Topic"> 
-<h3>Go Home</h3>  
-<p class="Para">This command redraws the view, showing the repository locations as the roots 
-displayed by the view.</p>
-</div>
-     
-<div class="Topic">     
-<h3> Go Back</h3> 
-<p class="Para"> This command redraws the view, showing the roots that
- where displayed immediately prior to the previous issued Go Into command.</p>
-</div>
-     
-<div class="Topic">     
-<h3> Go Into</h3>  
-<p class="Para"> This command redraws the view, making the children of the  selected entry 
-the roots displayed by the view.</p>
-</div>
-     
-<div class="Topic">     
-<h3> Refresh View</h3>
-<p class="Para"> This command refreshes the contents of the Repositories view.</p>
-</div>
-     
-<div class="Topic">     
-<h3>Collapse All</h3>
-  <p class="Para"> This command collapses all expanded entries in the Repositories 
-    view.</p>
-</div>
-
-<div class="Topic">     
-<h3>Add CVS Repository</h3>
-  <p class="Para"> This command brings up the wizard to help you specify a new repository 
-  location.</p>
-</div>
-
-<h3 class="Para">Drop-Down Menu</h3>
-<p class="Para">The drop down menu in the title bar allows the repositories view 
-  to be filtered by a working set.</p>
-     
-<h2 class="Para">Context menu </h2>
-     
-<p class="Para">From the context menu of the Repositories view you can  perform
-a number    of interesting operations.</p>
-     
-<h3>  New &gt; Repository Location&nbsp;</h3>
-     
-<p class="Para">This command brings up the wizard to help you specify a new repository 
-  location (same as Add CVS Repository toolbar item).</p>
-  
-  <h3>  New &gt; Date Tag</h3>
-     
-<p class="Para">This command, available on the repository location and Date category 
-  entries, brings up the dialog which allows the specification of a date tag that 
-  is to be added to the Date category of the location entry in the Repositories 
-  view.</p>
-
-<h3>Check Out</h3>
-<p>This command checks the selected CVS modules out into projects in the Workbench 
-  with the same names as the remote modules (for remote modules that are folders 
-  on the server) or into projects with the name specified with the module (if 
-  the module is defined in the CVSROOT/modules file on the server).</p>
-     
-<h3>Check Out As...</h3>
-<p>This command open the Check Out wizard in order to allow the configuration of how the selected remote modules
-are checked out into the Workbench.</p>
-
-<h3>Tag as Version...</h3>  
-<p> This command versions the selected resource based on the current branch
- contents.</p>
-     
-<h3>Tag with Existing...</h3>  
-<p> This command versions the selected resource based on the current branch
- contents,    moving the tag from previously tagged resources if required.</p>
-
-<h3> Compare</h3>   
-<p class="Para">This command will compare two selected resources.</p>
-
-<h3>Compare With...</h3>
-<p class="Para">This command will compare the selected folder with a branch or 
-version of the same folder.</p>
-  
-<h3>Configure Branches and Versions</h3>
-<p class="Para"> This command brings up the wizard to help you discover the branch 
-  and version tags that exist in the repository for the selected folder so they 
-  can be added to the repositories view to allow the resources that have these 
-  tags can be browsed.</p>
-
-<h3>Refresh Branches and Versions</h3>
-<p class="Para"> This command, available on repository location entries, allows 
-  you to refresh the list of known branches and versions that are displayed in 
-  the repositories view for selected projects. This operation makes use of the 
-  defined auto-refresh files for each project. If the operation fails for a particular 
-  project, use Configure Branches and Versions on the project to select one or 
-  more appropriate refresh files.</p>
-  
-<h3>Add to Branch List...</h3>
-<p> This command adds the selected project to the list of projects that are displayed 
-  under the specified branch in the repositories view. This command only modifies 
-  the repositories view and does not effect the repository in any way. If you 
-  want to add the project to a branch, you can perform a <strong>Tag with Existing</strong> 
-  after performing this operation.</p>
-  
-<h3> Open</h3>
-<p> This command opens the selected file in an editor.&nbsp; Since file revisions
-    in the repository are immutable, the editor opens in a read-only state,
- so it    is not modifiable.&nbsp; </p>
-
-<h3> Show Annotation</h3>   
-<p> This command shows the contents of file with annotations identifying the author
-of each line of code in the file.</p>
-   
-<h3> Show in Resource History</h3>   
-<p> This command shows the revision history of the selected file in the CVS
- Resource    History view.</p>
-     
-
-<h3>Properties</h3>   
-<p> Available on repository location entries, this command allows the modification 
-  of any of the properties of the location. It also allows the assignment of a 
-  display name and a server encoding which is used to translate file paths and 
-  commit comments between the client and server (but does not affect file contents).</p>
-
-      
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"
- >
-  <br>
-     <a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-     <a href="../concepts/concepts-27c.htm">CVS Repositories</a><br>
-     <a href="../concepts/concepts-27b.htm">Branches</a><br>
-     <a href="../concepts/concepts-27.htm">Versions</a><br>
-     <a href="../concepts/concepts-17a.htm">Local history</a></p>
-     
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"
- >
-  <br>
-     <a href="../tasks/tasks-92.htm">Creating a CVS repository location</a><br>
-     <a href="../tasks/tasks-94.htm">Discarding a CVS repository location</a><br>
-     <a href="../tasks/tasks-93.htm">Refreshing the CVS repositories view</a><br>
-     <a href="../tasks/tasks-95.htm">Changing the properties of a CVS Repository Location</a><br>
-     <a href="../tasks/tasks-96.htm">Checking out a project from a CVS repository</a><br>
-     <a href="../tasks/tasks-103.htm">Replacing resources in the Workbench</a><br>
-     <a href="../tasks/tasks-117.htm">Sharing a new project using CVS</a><br>
-     <a href="../tasks/tasks-119.htm">Viewing a file's revision history</a>
-   </p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- >
-  <br>
-     <a href="ref-47.htm">CVS</a><br>
-     <a href="ref-32a.htm">CVS Resource History View</a>
-   </p>
-          
-
-      
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-32a.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-32a.htm
deleted file mode 100644
index 281151f..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-32a.htm
+++ /dev/null

@@ -1,142 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-     
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-     
-  <meta http-equiv="Content-Style-Type" content="text/css">
-      
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>CVS Resource History View</title>
-   
-</head>
- <body style="background-color: rgb(255,255,255);">
-   
-<h1 class="Head"> CVS Resource History view</h1>
-    
-<p class="Intro"> This view provides a list of all the revisions of a resource 
-   in the repository. From this view you can compare two revisions, replace 
-(get    sticky) or revert (get contents) the corresponding workspace file 
-to the revision,    or open an editor on a revision. </p>
- 
-<p class="Para">Here is what the CVS Resource History View looks like:</p>
-   
-<p class="Para"><img
- src="../images/Image216_history_view.png"
- alt="CVS Resource History View"  border="0" align="top"> </p>
-
-<h2>Columns</h2>
-<p class="Para">For each resource, the following is displayed in the table:</p>
-   
-<div class="Topic">    
-<h3> Revision</h3>
-<p class="Para"> This column displays the revision number in the history.&nbsp; </p>
-</div>
-   
-<div class="Topic">    
-<h3>Tags</h3>   
-<p class="Para">The tags that are associated with the revision. Selecting 
-a      revision line will list the tags in the lower left pane of the view.</p>
-</div>
-   
-<div class="Topic">  
-<h3> Date</h3>   
-<p class="Para"> This column displays the creation date and time of the revision 
-     in the history.</p>
-</div>
-   
-<div class="Topic">       
-<h3> Author</h3>
-<p class="Para"> This column displays the name of the person who created and
-authored the version.</p>
-</div>
-   
-<div class="Topic">  
-<h3> Comment</h3>   
-<p class="Para"> This column displays the comment (if any) supplied for this 
-     revision at the time it was committed. Selecting a revision line will 
-show      the complete comment in the lower right pane of the view.</p>
-</div>
-
-<h2>Toolbar</h2>
-
-<div class="Topic"> 
-<h3>Refresh View</h3>  
-<p class="Para">This command refreshes the contents of the view, 
-fetching the latest history information for the resource from the server.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Link with Editor</h3>  
-<p class="Para">When enabled, the view will display the history for the resource 
-of the active editor.</p>
-</div> 
-
-<div class="Topic"> 
-<h3>Filter History</h3>  
-<p class="Para">This command will open a dialog that allows the specification of view filters.
-The resource history can be filtered by author, comment or date.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Drop Down Menu</h3>  
-<p class="Para">The drop down menu in the toolbar allows the comment and tag panes to be hidden or shown.</p>
-</div> 
-
-<h2 class="Para">Context menu </h2>
-     
-<p class="Para">From the context menu of the CVS Resource History view you can  perform
-a number of interesting operations.</p>
-     
-<h3>Get Contents</h3>   
-<p class="Para">This command will load the contents of the selected revision
-into the local copy of the file whose history
-is displayed in the view. The local file can then be committed to make
-the contents of latest revision in HEAD (or a branch) match the contents of
-the selected revision.</p>
-
-<h3>Get Sticky Revision</h3>   
-<p class="Para">This command will load the the selected revision over the local 
-  file whose history is being displayed. This operation is rarely needed and is 
-  mainly used to change the tag on one or more resources. The loaded revision 
-  cannot be subsequently committed but can be tagged.</p>
-
-<h3>Tag with Existing...</h3>   
-<p class="Para">This command allows an existing tag to be moved to the
-selected file revision.</p>
-
-<h3> Show Annotation</h3>   
-<p> This command shows the contents of file with annotations identifying the author
-of each line of code in the file.</p>
-
-<h3>Compare</h3>   
-<p> This command opens an editor comparing the contents of the two selected revisions.</p>
-
-<h3>Open</h3>   
-<p> This command opens an editor displaying the contents of the selected file revision.</p>
-
-<h3>Refresh View</h3>   
-<p> This command refreshes the contents of the view.</p>
-
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- >
- <br>
-    <a href="ref-32.htm">CVS Repositories view</a>  </p>
-    
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"
- >
-  <br>
- <a href="../concepts/concepts-12.htm">Resources</a> <br>
- <a href="../concepts/concepts-27c.htm">CVS Repositories</a> <br>
- <a href="../concepts/concepts-17a.htm">Local history</a> </p>
-    
-
-    
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-32b.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-32b.htm
deleted file mode 100644
index 7a2cb0f..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-32b.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-     
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-     
-  <meta http-equiv="Content-Style-Type" content="text/css">
-      
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>CVS Console</title>
-   
-</head>
- <body style="background-color: rgb(255,255,255);">
-   
-<h1 class="Head"> CVS Console</h1>
-    
-<p class="Intro">The CVS Console is shown in the Workbench Console view. The CVS 
-  entry in this view shows the output from CVS commands. This output is similar 
-  to that of the CVS command line client. If an error occurs during a CVS operation 
-  opening the console can help troubleshoot the cause of the error.</p>
- 
-<p class="Para">Here is what the CVS Console in the Console view looks like:</p>
-<p class="Para"><img src="../images/cvs-console.png" alt="Console View" ></p>
-   
-<div class="Topic">
-<img border="0" src="../images/ngrelr.png" alt="Related reference"
- > <br>
-    <a href="ref-32.htm">CVS Repositories view</a>
-</div>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"
- >
-  <br>
- <a href="../concepts/concepts-12.htm">Resources</a> <br>
- <a href="../concepts/concepts-27c.htm">CVS Repositories</a> <br>
- <a href="../concepts/concepts-17a.htm">Local history</a> </p>
-    
-
-    
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-33.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-33.htm
deleted file mode 100644
index fae5afb..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-33.htm
+++ /dev/null

@@ -1,346 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-     
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-     
-  <meta http-equiv="Content-Style-Type" content="text/css">
-      
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>CVS Workspace Synchronization</title>
-   
-</head>
- <body style="background-color: rgb(255,255,255);">
-<h1>CVS Workspace Synchronization</h1>
-<p class="Para">CVS workspace synchronizations launched using the <b>Team &gt; Synchronize</b>
-menu command or the <b>Synchronize</b> toolbar command in the Team Perspective will appear
-in the Synchronize view. This view allows you to inspect the differences between the local 
-Workbench resources and their remote counterparts as well as
-update resources in the Workbench 
-and commit resources from the Workbench to a repository.</p>
-   
-<p class="Para"> Here is what the CVS Workspace Synchronization in the Synchronize view looks like:</p>
-   
-<p class="Para"> <img align="top" border="0"
- src="../images/Image245_sync_view.png" alt="CVS Workspace Synchronization" >
- </p>
-
-<h2>Features</h2>
-
-The following is a brief summary of some of the features of the synchronize view.
-
-
-<h3 class="Para">Synchronization state</h3>
-  <p class="Para">The synchronize view shows the synchronization 
-    state of resources in your workspace compared to those in the repository. 
-    This state is shown by using icons and can also be configured to show the 
-    state as text appended to the resource name. A description of the icons is 
-    shown in the table below:</p>
-  <table width="100%" border="1">
-    <tr> 
-      <td width="9%" align="center"><img src="../images/r_inadd_ov.png" alt="Incoming addition icon" ></td>
-      <td width="91%">An incoming addition means that a resource has been added 
-        to the repository. <strong>Updating</strong> will transfer the resource 
-        to your workspace.</td>
-    </tr>
-    <tr> 
-      <td align="center"><img src="../images/r_inchg_ov.png" alt="Incoming change icon" ></td>
-      <td>An incoming change means that the file has changed in the repository. 
-        <strong>Updating</strong> will transfer the new file revision to your 
-        workspace.</td>
-    </tr>
-    <tr> 
-      <td align="center"><img src="../images/r_indel_ov.png" alt="Incoming deletion icon" ></td>
-      <td>An incoming deletion means that a resource was deleted from the server. 
-        <strong>Updating</strong> will delete your local resource.</td>
-    </tr>
-    <tr> 
-      <td align="center"><img src="../images/r_outadd_ov.png" alt="Outgoing addition icon" ></td>
-      <td>An outgoing addition means that the file was added to your workspace 
-        and is not yet in the repository. <strong>Adding</strong> then <strong>Committing</strong> 
-        will transfer the new file to the repository.</td>
-    </tr>
-    <tr> 
-      <td align="center"><img src="../images/r_outchg_ov.png" alt="Outgoing change icon" ></td>
-      <td>An outgoing change means that the file was change locally. <strong>Committing</strong> 
-        the file will transfer the changes to the repository and create a new 
-        revision of the file.</td>
-    </tr>
-    <tr> 
-      <td align="center"><img src="../images/r_outdel_ov.png" alt="Outgoing deletion icon" ></td>
-      <td>An outgoing deletion is a resource that has been deleted locally. <strong>Committing 
-        </strong>these resources will cause the remote resource to be deleted. 
-        <strong>Note</strong>: in CVS directories are never really deleted from 
-        the repository. Instead, files are deleted and empty directories are pruned 
-        from your workspace. </td>
-    </tr>
-    <tr> 
-      <td align="center"><img src="../images/confadd_ov.png" alt="Conflicting addition icon" ></td>
-      <td>A conflicting additions means that the resource has been added locally 
-        and remotely.</td>
-    </tr>
-    <tr> 
-      <td align="center"><img src="../images/confchg_ov.png" alt="Conflicting change icon" ></td>
-      
-    <td>A conflicting change means that the file has been changed locally and 
-      remotely. A manual or automatic merge will be required by the user. Also, 
-      any entries in the view that contain children that are conflicts will also 
-      be decorated with the conflict icon. This is done to make conflicts easy 
-      to find. </td>
-    </tr>
-    <tr> 
-      <td align="center"><img src="../images/confdel_ov.png" alt="Conflicting deletion icon" ></td>
-      <td>A conflicting deletion means that the resource was deleted locally and 
-        remotely. </td>
-    </tr>
-  </table>
-
-
-
-<h3>Mode</h3>
-
-<p>The Synchronize view can be filtered using modes using either the toolbar actions or
-the menu items in the view's drop down menu. 
-Modes can be used to show only incoming, outgoing or conflicting changes.
-The advantages to modes are: </p>
-<ul>
-  <li>
-    They support and encourage the <a href="../concepts/concepts-26.htm#IdealWorkFlow"> ideal work flow.</a></li>
-  <li>
-    They reduce the amount of information you are faced with at any one time.</li>
-    <li> They provide a degree of safety restricting you to those operations appropriate 
-      to that mode. For example, you can't accidentally commit a conflict when 
-      in incoming mode.</li>
-</ul>
-     
-  <p class="Para"> <b>Important</b>: It is preferable to update resources in the 
-    Workbench first, resolve any conflicts that exist by merging, then commit 
-    Workbench resources to the repository.</p>
-    
-<h3>Layout</h3>
-<p> There are three options for Synchronize view layout for CVS: Flat, Tree and 
-  Compressed Folders.</p> 
-<ul>
-  <li>Flat layout shows all the out-of-sync resources as top level items.</li>
-  <li>Tree layout shows the resource hierarchy as it is shown in the Resource 
-    Navigator.</li>
-  <li>Compress Folders shows changes grouped by project and then by folder. This 
-    results in a hierarchy that is at most three levels deep with folder paths 
-    being compressed into a single level (similar to a Java package).</li>
-</ul>
-
-<h3>Navigation</h3>
-
-The Synchronize view provides toolbar actions for navigating through the changes in the view.
-This actions not only navigate between files but also go from change to change within a file.
-
-<h3>Update and Commit Operations</h3>
-
-<p> There are several flavors of update and commit operations available in the 
-  Synchronize view. You can perform the standard update and commit operation on 
-  all visible applicable changes or a selected subset. You can also choose to 
-  override and update, thus ignoring any local changes, or override and commit, 
-  thus making the remote resource match the contents of the local resource. You 
-  can also choose to clean the timestamps for files that have been modified locally 
-  (perhaps by an external build tool) but whose contents match that of the server.</p> 
-<h3>Conflict Handling</h3>
-
-<p> When dealing with conflicts, you can first perform an update and any conflicting 
-  changes The update operation will correctly update conflicts that are auto-mergeable 
-  (i.e. files content changes do not overlap) but will skip files that contain 
-  changes that overlap. Alternatively, conflicts can be handled using a Compare 
-  editor. A Compare editor can be opened by double-clicking (or single-clicking 
-  if you have change your open strategy in the preferences) on the conflict or 
-  by choosing <b>Open in Compare Editor</b> from the context menu. The Compare 
-  editor allows you to manually resolve the conflicts in the file. Once completed, 
-  perform a <b>Mark as Merged</b> on the conflict to indicate that you are done. 
-  This will change the conflict into an outgoing change.</p> 
-<h3>Problem Markers</h3>
-
-<p>
-The Synchronize view will show <i>error</i> or <i>warning</i> problem markers on any change that appears
-in the view or any folder or project that appears in the view that contains a resource that has such a problem
-marker. This is done to prevent resources with problems from getting committed to the repository.</p>
-
-<h2>Toolbar</h2>
-
-<div class="Topic"> 
-<h3>Synchronize</h3>  
-  <p class="Para">This command allows you to repeat the current synchronization 
-    which refetches the remote state of the resources. The drop down of the toolbar 
-    item allows you to select other existing synchronizations or create new ones 
-    using the <b>Synchronize...</b> menu command.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Pin Current Synchronization</h3>  
-<p class="Para">This command allows you to pin or unpin the current synchronization.
-Pinned synchronizations will not be replaced by the next synchronization of the same type
-while unpinned synchronizations will be replaced.
-This allows you to keep a synchronization around for easy access. Such a synchronization 
-will automatically update when changes to Workbench resources take place and can be configured
-to perform scheduled refreshes in order to keep up-to-date with the remote state of the resources. </p>
-</div>
-
-<div class="Topic"> 
-<h3>Go to Next Difference</h3>  
-<p class="Para">This command will go to the next difference displayed by the view. All the
-differences within a single file will be visited before opening the next file in the view.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Go to Previous Difference</h3>  
-<p class="Para">This command will go to the previous difference displayed by the view. All the
-differences within a single file will be visited before opening the previous file in the view.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Collapse All</h3>  
-<p class="Para">Collapse all the expanded entries in the view.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Incoming Mode</h3>  
-<p class="Para">In this mode, only resources which have been changed in the repository 
-       since they were last loaded or synchronized with those in the Workbench 
-       (incoming changes) are visible.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Outgoing Mode</h3>  
-<p class="Para">In this mode, only resources which have been modified in the Workbench 
-       (outgoing changes) are visible.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Incoming/Outgoing Mode</h3>  
-<p class="Para"> In this mode both incoming and outgoing changes are shown, and you can 
-      both update and commit. The advantage to using this dual mode is 
-      you can do either task as you choose. The disadvantage is that performing 
-      a simultaneous bi-directional merge is often complicated.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Conflicts Mode</h3>  
-  <p class="Para"> In this mode only conflicts (resources modified both in the Workbench 
-    and in the repository) are shown.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Update All Incoming Changes</h3>  
-  <p class="Para">This command updates all the incoming changes visible in the view. 
-    The command will also update conflicts that are auto-mergeable but will skip 
-    files whose contents contain conflicts.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Commit All Outgoing Changes</h3>  
-  <p class="Para">This command commits all the outgoing changes visible in the view. 
-    Conflicts are not included in the commit.</p>
-</div>
-
-<div class="Topic"> 
-  <h3>Change Sets</h3>
-  <p>Change sets can be enabled in incoming mode and outgoing mode.</p>
-  <ul>
-    <li>In incoming mode, Change Sets shows incoming changes grouped by commit 
-      comment which is handy for seeing who released what and why.</li>
-    <li>In outgoing mode, the user can create Change Sets for grouping related 
-      changes together. Grouping is performed using various commands in the context 
-      menu. </li>
-  </ul>
-<h3>Drop Down Menu</h3>  
-  <p class="Para">The drop down menu allows you to remove the current or all synchronizations, 
-    change the mode or layout, configure the current synchronization to perform 
-    scheduled refreshes as well as set other view preferences.</p>
-</div>
-
-<h2 class="Para">Context menu </h2>
-     
-<p class="Para">From the context menu of the Synchronize view you can  perform
-a number    of interesting operations.</p>
-     
-<h3>Open in Compare Editor</h3>
-<p class="Para">This command open the selected change in a Compare editor which allows 
-you to inspect the changes within the file.</p>
-
-<h3>Open</h3>
-<p class="Para">This command open the local resource for the selected change in 
-the default Workbench editor for the file type.</p>
-
-<h3>Open With</h3>
-<p class="Para">This command allows you to open the local resource for the selected 
-  change in the a Workbench editor.</p>
-
-<h3>Synchronize</h3>
-<p class="Para">This command refreshed the remote state of the selected resources.</p>
-
-<h3>Remove From View</h3>
-<p class="Para">This command removes the selected resources from the view. The
-resources will only reappear if the state of the removed resources changes or the 
-Workbench is restarted.</p>
-
-<h3>Update</h3>
-<p class="Para">This command updates the selected resources. Conflicts can be 
-  included in an update but only auto-mergeable conflicts will be updated. Non-mergeable 
-  conflicts will be skipped and should be merged manually using a compare editor.</p>
-
-<h3>Commit</h3>
-<p class="Para">This command commits the selected resources. Only outgoing 
-changes can be committed.</p>
-
-<h3>Override and Update</h3>
-<p class="Para">This command operates on conflicts and outgoing changes
-and replaces the local contents of those resources with the contents 
-from the server.</p>
-
-<h3>Override and Commit</h3>
-<p class="Para">This command operates on conflicts and incoming changes
-and overwrites the server contents with the contents from their local
-counterparts.</p>
-
-<h3>Mark as Merged</h3>
-<p class="Para">This command adjusts the CVS timestamps of conflicting changes
-so they become outgoing changes. This command should be performed after
-conflicts are merged manually using a compare editor.</p>
-
-<h3>Clean Timestamps</h3>
-<p class="Para">This command adjusts the timestamps of outgoing changes whose 
-  contents already match the contents of the corresponding resource on the server 
-  so that the file is no longer an outgoing change. This is useful in situations 
-  where build tools regenerate files whose contents have not changed.</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"
- >
- <br>
-    <a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-    <a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
- &nbsp;   </p>
-   
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"
- >
- <a href="../tasks/tasks-115.htm"><br>
-    Synchronizing with the repository</a><a
- href="../tasks/tasks-113.htm"><br>
-    Updating</a><a href="../tasks/tasks-113b.htm"><br>
-    Resolving conflicts</a><a href="../tasks/tasks-100b.htm"><br>
-    Merging from a branch</a><a href="../tasks/tasks-114.htm"><br>
-Committing</a><a href="../tasks/tasks-68.htm"><br>
-    </a> <a href="../tasks/tasks-68.htm">Comparing resources<br>
-    </a> <a href="../tasks/tasks-68dg.htm">Merging changes in the compare 
-editor</a></p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- >
- <br><a href="../reference/ref-47.htm">CVS</a>
- <br><a href="ref-25.htm">Compare editor</a>  </p>
-
-
-   
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-33a.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-33a.htm
deleted file mode 100644
index 42796b0..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-33a.htm
+++ /dev/null

@@ -1,181 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-     
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-     
-  <meta http-equiv="Content-Style-Type" content="text/css">
-      
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>CVS Merge Synchronization</title>
-   
-</head>
- <body style="background-color: rgb(255,255,255);">
-<h1>CVS Merge Synchronization</h1>
-<p class="Para">CVS Merge synchronizations launched using the <b>Team &gt; Merge</b> 
-  menu command will appear in the Synchronize view. This view allows you to inspect 
-  the differences between the local Workbench resources and their remote counterparts 
-  that are being merged and allows you to update the local resources. Committing 
-  is not supported when merging.</p>
-   
-<p class="Para"> Here is what the CVS Merge Synchronization in the Synchronize view looks like:</p>
-   
-<p class="Para"> <img src="../images/cvs-merge-sync.png"  align="top" border="0" alt="CVS Merge Synchronization">
-
- </p>
-
-<h2>Features</h2>
-
-<p class="Para"> 
-The features of the CVS Merge Synchronization are similar to those of the 
-<a href="ref-33.htm">CVS Workspace Synchronization</a> with the following
-differences.
-</p>
-
-<ul>
-<li><b>Modes:</b>
-When merging, only incoming and conflicting changes are possible. 
-As such, only the Incoming Mode and Conflicts mode are supported.</li>
-
-  <li><b>Operations:</b> Only updating is supported when merging.</li>
-  <li><b>Ongoing merges:</b> In order to compensate for the poor ongoing merge 
-support of CVS, a CVS Merge Synchronization can be pinned and kept indefinitely.
-The timestamps of merged changes are recorded and, on refresh, only new changes since the last
-merge are shown in the view.</li>
-</ul>
-
-<h2>Toolbar</h2>
-
-<div class="Topic"> 
-<h3>Synchronize</h3>  
-  <p class="Para">This command allows you to repeat the current synchronization 
-    which refetches the remote state of the resources. The drop down of the toolbar 
-    item allows you to select other existing synchronizations or create new ones 
-    using the <b>Synchronize...</b> menu command.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Pin Current Synchronization</h3>  
-  <p class="Para">This command allows you to pin or unpin the current synchronization. 
-    Pinned synchronizations will not be replaced by the next synchronization of 
-    the same type while unpinned synchronizations will be replaced. This allows 
-    you to keep a synchronization around for easy access. Such a synchronization 
-    will automatically update when changes to Workbench resources take place and 
-    can be configured to perform scheduled refreshes in order to keep up-to-date 
-    with the remote state of the resources. This is especially handy for ongoing 
-    merges from a more stable branch (e.g. HEAD) into a development branch.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Go to Next Difference</h3>  
-<p class="Para">This command will go to the next difference displayed by the view. All the
-differences within a single file will be visited before opening the next file in the view.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Go to Previous Difference</h3>  
-<p class="Para">This command will go to the previous difference displayed by the view. All the
-differences within a single file will be visited before opening the previous file in the view.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Collapse All</h3>  
-<p class="Para">Collapse all the expanded entries in the view.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Incoming Mode</h3>  
-<p class="Para">In this mode, all resources which have been changed in the branch
-being merged are visible.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Conflicts Mode</h3>  
-<p class="Para"> In this mode only conflicts (resources modified both in the Workbench 
-and in the branch being merged) are shown.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Update All Incoming Changes</h3>  
-  <p class="Para">This command updates all the incoming changes visible in the view. 
-    The command will also update conflicts that are auto-mergeable but will skip 
-    files whose contents contain conflicts.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Drop Down Menu</h3>  
-  <p class="Para">The drop down menu allows you to remove the current or all synchronizations, 
-    change the mode or layout, configure the current synchronization to perform 
-    scheduled refreshes as well as set other view preferences.</p>
-</div>
-
-<h2 class="Para">Context menu </h2>
-     
-<p class="Para">From the context menu of the Synchronize view you can  perform
-a number of interesting operations.</p>
-     
-<h3>Open in Compare Editor</h3>
-<p class="Para">This command open the selected change in a Compare editor which allows 
-you to inspect the changes within the file.</p>
-
-<h3>Open</h3>
-<p class="Para">This command open the local resource for the selected change in 
-the default Workbench editor for the file type.</p>
-
-<h3>Open With</h3>
-<p class="Para">This command allows you to open the local resource for the selected 
-  change in the a Workbench editor.</p>
-
-<h3>Synchronize</h3>
-<p class="Para">This command refreshed the remote state of the selected resources.</p>
-
-<h3>Remove From View</h3>
-<p class="Para">This command removes the selected resources from the view. The
-resources will only reappear if the state of the removed resources changes or the 
-Workbench is restarted.</p>
-
-<h3>Update</h3>
-<p class="Para">This command updates the selected resources. Conflicts can be 
-  included in an update but only auto-mergeable conflicts will be updated. Non-mergeable 
-  conflicts will be skipped and should be merged manually using a compare editor.</p>
-
-<h3>Override and Update</h3>
-<p class="Para">This command operates on conflicts and outgoing changes
-and replaces the local contents of those resources with the contents 
-from the server.</p>
-
-<h3>Mark as Merged</h3>
-<p class="Para">This command removes the change from the view. This command should be performed after
-conflicts are merged manually using a compare editor. The change will only reappear
-if the view is refreshed and new changes are found in the branch being merged.</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"
- >
- <br><a href="../concepts/concepts-26.htm">Team programming with CVS</a>
- </p>
-   
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"
- >
-<br><a href="../tasks/tasks-113b.htm">Resolving conflicts</a><br>
-<a href="../tasks/tasks-100b.htm">Merging from a branch</a><br>
-<a href="../tasks/tasks-68.htm">Comparing resources</a><br>
-<a href="../tasks/tasks-68dg.htm">Merging changes in the compare editor</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- >
- <br><a href="../reference/ref-47.htm">CVS</a>
- <br><a href="ref-41a.htm">Merge wizard</a>
- <br><a href="ref-33.htm">CVS Workspace Synchronization</a>
- <br><a href="ref-25.htm">Compare editor</a>
- </p>
-
-
-   
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-34.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-34.htm
deleted file mode 100644
index 286e0f8..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-34.htm
+++ /dev/null

@@ -1,90 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Help window</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Help window</H1>
-<P CLASS="Para">
-This window displays help on using the Workbench.&nbsp;If you are reading this
-document, you've probably found this view already.</P>
-<P CLASS="Para">
-Here is what the Help view looks like, when using embedded browser:</P>
-<P CLASS="Para">
-<img src="../images/Image239_help_view.png" alt="Help Window" border="0" ></P>
-<P CLASS="Para">&nbsp;
-</P>
-<h2>
-Table of Contents (Bookshelf)</h2>
-<p>This list contains all the available sets of information (or books). Click a book 
-to see its topics tree.</p>
-<h2>
-Contents Tab&nbsp;</h2>
-<P CLASS="Para">
-This tab displays an outline of the available Help topics
-for the selected book.</P>
-<DIV CLASS="Subtopic">
-<h2>
-Search Results Tab</h2>
-<p>
-If you run a search of the documentation, the results list will be displayed on 
-this tab.</p>
-<h2>Links Tab</h2>
-<p>If you invoke the context
-sensitive (F1) help, all the related links for that context are displayed in a
-list on this tab.</p>
-<h2>Bookmarks Tab</h2>
-<p>This list displays topics that were bookmarked using Bookmark Document button.</p>
-<h2>Search</h2>
-<p>Type a search query in the field and click Go. Click Advanced Search to enter 
-a longer query or to filter the results by available books.</p>
-</DIV>
-<h2>
-Search scope</h2>
-<P>
-Click the link to change the documentation set to be searched.</P>
-<h2>
-Go
-Back</h2>
-<P>
-Click this button to display the previously displayed
-page.</P>
-<h2>
-Go
-Forward</h2>
-<P>
-You can use this button if you have just used the Go Back button. Click it to display a&nbsp;previously displayed page.</P>
-<h2>
-Refresh / Show Current Topic and Show in Table of Contents</h2>
-<P>Click one of these buttons to match the navigation tree up to the topic currently 
-shown in the content frame.</P>
-<h2>
-Bookmark Document</h2>
-<P>
-This button adds the currently displayed document to the Bookmarks view.</p>
-<h2>
-Print Page</h2>
-<P>
-This command prints the currently displayed topic.</P>
-<h2>
-Maximize and Restore</h2>
-<P>
-The Maximize buttons cause navigation or content frame to be maximized.
-When a frame is maximized the Restore button is available than can be used to restore the frame to its original size.</P>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a HREF="ref-43.htm">Workbench User Guide</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-35.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-35.htm
deleted file mode 100644
index 9819f26..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-35.htm
+++ /dev/null

@@ -1,78 +0,0 @@
-<!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en"><html><head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta http-equiv="Content-Style-Type" content="text/css"><title>Quick Diff Preference Page</title>
-   
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"></head><body bgcolor="#ffffff">
-
-<h1 class="Head">Quick Diff Preference Page</h1>
-<div class="Para"></div>
-
-<div class="Para">
-  <p>The following preferences can be changed on the Quick Diff preference page.</p>
-</div>
-<table border="1" cellspacing="0" style="width: 100%;">
-  <caption>
-  </caption>
-  <thead>
-  </thead>
-  <tbody>
-  </tbody>
-  <tbody>
-    <tr> 
-      <th width="25%"> <div class="Para">Option</div></th>
-      <th> <div class="Para">Description</div></th>
-      <th> <div class="Para">Default</div></th>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Enable quick 
-          diff<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option will enable 
-          or disable the quick diff option.</div></td>
-      <td align="left" valign="top"> <div class="Para">On</div></td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Show differences in overview 
-        ruler<br> </td>
-      <td style="vertical-align: top;"><br>
-        This option will show differences in the overview ruler.</td>
-      <td style="vertical-align: top;">Off<br> </td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Colors - Changes<br>
-        </div></td>
-      <td align="left" valign="top">This option controls the color of changes. 
-      </td>
-      <td align="left" valign="top">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Colors - Additions<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option controls the 
-          color of additions. <br>
-        </div></td>
-      <td align="left" valign="top"> <br> </td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Colors - Deletions<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option controls the 
-          color of deletions. </div></td>
-      <td align="left" valign="top"> <div class="Para"></div></td>
-    </tr>
-  </tbody>
-</table>
-
-<p></p>
-<p>Here is what the Quick Diff preference page looks like: </p>
-<p><img src="../images/ref-quickdiffpref.png" alt="Image of the Quick Diff preference page"><br>
-</p>
-<p>&nbsp;<br>
-
-</p>
-
-
-</body></html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-36.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-36.htm
deleted file mode 100644
index 8215f30..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-36.htm
+++ /dev/null

@@ -1,82 +0,0 @@
-<!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en"><html><head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta http-equiv="Content-Style-Type" content="text/css"><title>Spelling preference page</title>
-   
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"></head><body bgcolor="#ffffff">
-<h1 class="Head">Spelling Preference Page</h1>
-<div class="Para">
-  <p>The following preferences can be changed on the Spelling preference page.</p>
-</div>
-<table border="1" cellspacing="0" style="width: 100%;">
-  <caption>
-  </caption>
-  <thead>
-  </thead>
-  <tbody>
-  </tbody>
-  <tbody>
-    <tr> 
-      <th width="25%"> <div class="Para">Option</div></th>
-      <th> <div class="Para">Description</div></th>
-      <th> <div class="Para">Default</div></th>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Enable spell 
-          checking<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option enables spell 
-          checking. </div></td>
-      <td align="left" valign="top"> <div class="Para">Off</div></td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Ignore words with digits <br> 
-      </td>
-      <td style="vertical-align: top;">This option ignores words with digits when 
-        performing spell checking.<br> </td>
-      <td style="vertical-align: top;">Off<br> </td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Ignore mixed 
-          case words <br>
-        </div></td>
-      <td align="left" valign="top">This option ignores mixed case words when 
-        performing spell checking. </td>
-      <td align="left" valign="top"> Off<br> </td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Ignore sentence 
-          capitalization<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option ignores sentence 
-          capitalization when performing spell checking. <br>
-        </div></td>
-      <td align="left" valign="top"> Off<br> </td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Ignore upper 
-          case words<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option ignores upper 
-          case words when performing spell checking. </div></td>
-      <td align="left" valign="top"> <div class="Para">Off</div></td>
-    </tr>
-    <tr>
-      <td align="left" valign="top"> <div class="Para">Ignore internet addresses<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option ignores internet 
-          addresses when performing spell checking. </div></td>
-      <td style="vertical-align: top;"><br>
-        Off </td>
-    </tr>
-  </tbody>
-</table>
-
-<p></p>
-<p>Here is what the Spelling preference page looks like: </p>
-<p><img src="../images/ref-spellingpref.png" alt="Image of the Spelling preference page"><br>
-  &nbsp;<br>
-</p>
-</body></html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-37.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-37.htm
deleted file mode 100644
index a230dc2..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-37.htm
+++ /dev/null

@@ -1,120 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta http-equiv="Content-Style-Type" content="text/css">
-   <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-   <title>New Project wizard</title>
-<link REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-</head>
-<body bgcolor="#FFFFFF">
-
-<h1 CLASS="Head">
-New Project wizard</h1>
-
-<div CLASS="Intro">This wizard helps you create a new project in the Workbench.</div>
-
-
-<p CLASS="Para">When you first bring up the New Project wizard, you need
-to select the type of project you want to create.&nbsp; Select the Simple
-type if you want to create a generic project.</p>
-
-<p CLASS="Para"><img src="../images/Image247_projsel_wiz.png" alt="New project wizard" border="0" ></p> 
-<div CLASS="Topic">
-<h2>
-Create a New Project Resource Page</h2>
-When you select Next, you will be presented with the New Project Resource
-Page, containing the following edit fields:
-<br>&nbsp;
-<table BORDER CELLSPACING=0 >
-<tr>
-<th>
-<div CLASS="Para">Field</div>
-</th>
-
-<th>
-<div CLASS="Para">Description</div>
-</th>
-
-<th>
-<div CLASS="Para">Default</div>
-</th>
-</tr>
-
-<tr>
-<td ALIGN=LEFT VALIGN=TOP>
-<div CLASS="Para">Project Name</div>
-</td>
-
-<td ALIGN=LEFT VALIGN=TOP>
-<div CLASS="Para">The name of the new project to be created.</div>
-</td>
-
-<td ALIGN=LEFT VALIGN=TOP>
-<div CLASS="Para">&lt;blank></div>
-</td>
-</tr>
-
-<tr>
-<td ALIGN=LEFT VALIGN=TOP>
-<div CLASS="Para">Location</div>
-</td>
-
-<td ALIGN=LEFT VALIGN=TOP>
-<div CLASS="Para">The location in the file system where the project will
-be created. De-select "Use default location" to specify a location other
-than the default.&nbsp; You can type the new location or browse to select
-a file system location for the new project.</div>
-</td>
-
-<td ALIGN=LEFT VALIGN=TOP>
-<div CLASS="Para">The workspace root directory</div>
-</td>
-</tr>
-</table>
-
-
-  <p CLASS="Para">After you indicate a name and location for the project, you 
-    can either click <strong>Finish </strong>to create the project, or you can 
-    click <strong>Next </strong>to set up project dependencies on the Select Referenced 
-    Projects page.</p> 
-  <p CLASS="Para">Here is what the New Project Resource page looks like:</p>
-
-  <p CLASS="Para"><img src="../images/Image251_proj_wiz.png" alt="New project name and location page" border="0" ></p></div>
-
-<div CLASS="Topic">
-<h2>
-Select Referenced Projects page</h2>
-
-<div CLASS="Para">In the Referenced Projects list, you can set project
-dependencies for the new project. In the list of other projects in the
-Workbench, you can select one or more projects on which you want the new
-project to depend.&nbsp; Initially, no projects will be selected.</div>
-
-
-  <p CLASS="Para">Click <strong>Finish</strong> when you are done to create the 
-    new project in the Workbench.</p> 
-  <p CLASS="Para">Here is what the Select Referenced Projects page looks
-like:</p>
-
-  <p CLASS="Para"><img src="../images/Image252_projref_page.png" alt="Project references page" border="0" ></p></div>
-
-<div CLASS="Topic">
-<h2>
-New Project perspective options</h2>
-
-  <div CLASS="Para">On the preferences page (<strong>Window > Preferences > General 
-    > Perspectives</strong>), you can change the way that new projects are initially 
-    displayed. For details on how to change this option see <a href="ref-10.htm">Workbench</a>.</div>
-</div>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-27.htm">Navigator View</a>
-</p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-38.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-38.htm
deleted file mode 100644
index fc1116d..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-38.htm
+++ /dev/null

@@ -1,94 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>New Folder wizard</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-New Folder wizard</H1>
-<P CLASS="Para">
-This wizard helps you create a new folder in the Workbench.</P>
-<P CLASS="Para">
-Here is what the New Folder wizard looks like:</P>
-<P CLASS="Para"> <img src="../images/Image248_folder_wiz.png" alt="New folder wizard" border="0" ></P>
-<P CLASS="Para">&nbsp;
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-New Folder Fields</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Field</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Enter or select the parent folder</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The resource in which the new folder will be created. Type or navigate the list to
-select the resource.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The resource that was selected when you chose to create the new folder</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Folder name</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The name for the new folder.&nbsp;</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;blank&gt;</P>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-<H2>Advanced</H2>
-<P>The <B>Advanced</B> button reveals or hides a section of the wizard used to create a linked folder. Check the <B>Link to folder in the file system</B> checkbox if you want the new folder to reference a folder in the file
-system. Use the field below the checkbox to enter a folder path or the
-name of a path variable. Use the <B>Browse...</B> button to browse for a folder in the file system. Use the <B>Variables...</B> button if you want to use a path variable to reference a file system folder.</P>
-
-<P><IMG border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br><A href="../concepts/concepts-13.htm">Linked resources</A>
-<br><A href="../concepts/cpathvars.htm">Path variables</A>
-</P>
-
-<P><img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-<br><a href="../tasks/tasks-43.htm">Creating a folder</a>
-<br><a href="../tasks/tasks-45.htm">Creating linked resources</a>
-</P>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-27.htm">Navigator View</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-39.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-39.htm
deleted file mode 100644
index 5dabf37..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-39.htm
+++ /dev/null

@@ -1,96 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>New File wizard</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-New File wizard</H1>
-<P CLASS="Para">
-This wizard helps you create a new file in the Workbench.</P>
-<P CLASS="Para">
-Here is what the New File wizard looks like:</P>
-<P CLASS="Para"> <img src="../images/Image246_file_wiz.png" alt="New file dialog" border="0" ></P>
-<P CLASS="Para">&nbsp;
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-New File Fields</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Field</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Enter or select the parent folder</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The resource in which the new file will be created. Type or browse the list to select the resource.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The resource that was selected when you invoked the New File wizard.</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">File name</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The name for the new file, including the file extension.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;blank&gt;</P>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-<H2>Advanced</H2>
-<P>The <B>Advanced</B> button reveals or hides a section of the wizard used to create a linked
-file. Check the <B>Link to file in the file system</B> checkbox if you want the new file to reference a file in the file system.
-Use the field below the checkbox to enter a file path or the name of a
-path variable. Use the <B>Browse...</B> button to browse for a file in the file system. Use the <B>Variables...</B> button if you want to use a path variable to reference a file system file.</P>
-
-<P><IMG border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br>
-<A href="../concepts/concepts-13.htm">Linked resources</A>
-<br>
-<A href="../concepts/cpathvars.htm">Path variables</A>
-</P>
-
-<P><img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-<br><a href="../tasks/tasks-44.htm">Creating a file</a>
-<br><a href="../tasks/tasks-45.htm">Creating linked resources</a>
-</P>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-27.htm">Navigator View</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-39a.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-39a.htm
deleted file mode 100644
index c49c84e..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-39a.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>CVS Wizards</title>
-
-</HEAD>
-<body>
-<H1 CLASS="Head">
-CVS Wizards</H1>
-
-<P>There are several CVS specific wizards. These include the Import CVS Project 
-  wizard (which is also available from the New Project wizard) and the New CVS 
-  Repository Location wizard. There are also wizards for several CVS operations, 
-  such as committing and merging.</p>
-<P>  See Team Support in the
-Reference section for details on these wizards.
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- >
-  <br>
-  <a href="ref-40a.htm">CVS Checkout wizard</a><br>
-     <a href="ref-40.htm">New CVS Repository Location wizard</a><br>
-     <a href="ref-41a.htm">Merge wizard</a>
-     
-   </p>
-</body>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-3a.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-3a.htm
deleted file mode 100644
index bc76b13..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-3a.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Fast View bar</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Fast View Bar</H1>
-<P class="Intro"> The fast view bar is the place where fast views are docked. 
-  It may be docked in three locations. It may be docked on the left, bottom (default) 
-  and right. </p>
-<p>Here is an example of what some fast view bars look like:&nbsp;</P> 
-<P CLASS="Para">
-<img src="../images/Image211_fastview.png" alt="Fast View Bar" border="0"></P>
-
-<DIV CLASS="Topic">
-<h3>
-View Buttons</h3>
-<P CLASS="Para">
-These buttons provide a quick way to display the
-fast views in the current perspective.&nbsp; Fast views are essentially
-minimized views that have been dragged onto the shortcut bar.&nbsp; Fast views
-pop up when selected, and revert
-back to their minimized state when the user clicks outside of the view and may be oriented either horizontally or vertically according to their configuration.&nbsp; 
-To convert a fast view back into a normal view, click on the <i>Fast View</i> action
-in the view's menu or drag it back to the workbench.&nbsp;</P>
-</DIV>
-
-<P><img border="0" src="../images/ngrelr.png" alt="Related reference" > <br>
-  <a href="ref-4.htm">View Toolbars</a> <br>
-  <a href="ref-23.htm">Workbench Window Layout</a>
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-4.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-4.htm
deleted file mode 100644
index a28f29d..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-4.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>View toolbars</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-View toolbars</H1>
-<P CLASS="Para">
-View toolbars contain actions that apply only to the particular view in which they appear.&nbsp;
-The view toolbar also contains a context menu that contains other actions for that view.
-This menu is opened by clicking on the
-downwards pointing triangle.&nbsp;If there is enough space, view toolbars are in the view tab area.  Otherwise they appear in the view.</P>
-<P CLASS="Para">
-Here is an example of the view toolbar for the Properties view:</P>
-<P CLASS="Para">
-<img src="../images/Image215_toolbar_view.png" alt="Properties View Tool Bar" border="0" ></P>
-
-<h2>
-Title Bar</h2>
-<P CLASS="Para">
-View title bars contain the view name, its icon, and
-the view toolbar. </P>
-
-<P><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-3.htm">Shortcut Bar</a>
-<br><a href="ref-2.htm">Workbench Toolbar</a>
-<br><a href="ref-23.htm">Workbench Window Layout</a>
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-40.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-40.htm
deleted file mode 100644
index 6ca5a87..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-40.htm
+++ /dev/null

@@ -1,152 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-     
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-     
-  <meta http-equiv="Content-Style-Type" content="text/css">
-      
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>Add CVS Repository wizard</title>
-   
-</head>
- <body style="background-color: rgb(255,255,255);">
-   
-<h1 class="Head">Add CVS Repository wizard</h1>
-   
-<p class="Para"> This wizard helps you create a repository location.</p>
-   
-<p class="Para"> Here is what the New CVS Repository Location wizard looks 
-like:</p>
-   
-<p class="Para"> <img align="top" border="0"
- src="../images/Image249_repo_wiz.png" alt="Repositories View" >
- </p>
-   
-<div class="Topic">  
-<h2 class="Head">Fields</h2>
-   
-<p class="Head"> The following are the editable fields for a new CVS repository 
-location:</p>
-     
-<table border="1" cellspacing="0" cellpadding="3">
-      <thead>      <tr>
-         <th rowspan="1" colspan="1">               
-    <p class="Para"> Option</p>
-        </th>
-        <th rowspan="1" colspan="1">               
-    <p class="Para"> Description</p>
-        </th>
-        <th rowspan="1" colspan="1">               
-    <p class="Para"> Default</p>
-        </th>
-      </tr>
-      </thead> <tbody>
-       <tr>
-         <td rowspan="1" colspan="1" valign="top" align="left">         
-       Host
-        </td>
-        <td rowspan="1" colspan="1" valign="top" align="left">           
-     	The address of the host (e.g., "hostmachine.com").
-        </td>
-        <td rowspan="1" colspan="1" valign="top" align="left">           
-      &lt;blank&gt;
-        </td>
-      </tr>
-      <tr>
-         <td rowspan="1" colspan="1" valign="top" align="left">         
-       Repository Path
-        </td>
-        <td rowspan="1" colspan="1" valign="top" align="left">           
-     	The path to the repository on the host (e.g., "/x/y/z",&nbsp; 
-           "d:/myrepo").
-        </td>
-        <td rowspan="1" colspan="1" valign="top" align="left">           
-     	&lt;blank&gt;
-        </td>
-      </tr>
-      <tr>
-         <td rowspan="1" colspan="1" valign="top" align="left">         
-       	User Name
-        </td>
-        <td rowspan="1" colspan="1" valign="top" align="left">           
-		The user name under which you want to connect to the 
-           server.
-        </td>
-        <td rowspan="1" colspan="1" valign="top" align="left">           
-	    &lt;blank&gt;
-        </td>
-      </tr>
-      <tr>
-        <td colspan="1" valign="top" align="left">Password</td>
-        <td colspan="1" valign="top" align="left">The password required for 
-the          above user name to access the above host.</td>
-        <td colspan="1" valign="top" align="left">&nbsp;</td>
-      </tr>
-      <tr>
-         <td rowspan="1" colspan="1" valign="top" align="left">         
-		 Connection Type
-        </td>
-        <td rowspan="1" colspan="1" valign="top" align="left">           
-		The type of CVS connection for the repository, either 
-           "pserver", "extssh" or "ext".
-        </td>
-        <td rowspan="1" colspan="1" valign="top" align="left">           
-		pserver
-        </td>
-      </tr>
-      <tr>
-         <td colspan="1" valign="top" align="left">Port</td>
-        <td colspan="1" valign="top" align="left">Option to use a custom
-port for          the connection.</td>
-        <td colspan="1" valign="top" align="left">Use Default Port</td>
-      </tr>
-      <tr>
-         <td rowspan="1" colspan="1" valign="top" align="left">         
-		Validate connection on finish
-        </td>
-        <td rowspan="1" colspan="1" valign="top" align="left">           
-     
-    Check this option if you want to attempt a connection 
-           to the host upon completion of the wizard to validate that the 
-entered            information is correct.&nbsp; If this option is not enabled, 
-you will            not know whether the information entered is correct until 
-you try to            access the contents of a repository for the first time. 
-        </td>
-        <td rowspan="1" colspan="1" valign="top" align="left">           
-     
-      <p class="Para">On</p>
-        </td>
-      </tr>
-         
-       <tr>
-         <td rowspan="1" colspan="1" valign="top" align="left">         
-       	Save Password
-        </td>
-        <td rowspan="1" colspan="1" valign="top" align="left"> Check this option 
-          if you want the password in the Workbench keyring file. The file is 
-          stored on your local harddrive and is obfuscated but not strongly encrypted. 
-          Only do this if your password is not sensitive or you are sure that 
-          no one can access the keyring file on your local disk. </td>
-        <td rowspan="1" colspan="1" valign="top" align="left">           
-     
-      <p class="Para">Off</p>
-        </td>
-      </tr>
-      
-  </tbody>     
-</table>
-    <img border="0" src="../images/ngrelr.png" alt="Related reference"
- >
- <br>
-    <a href="ref-32.htm">CVS Repositories View</a> </div>
-    
-
-    
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-40a.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-40a.htm
deleted file mode 100644
index ea09137..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-40a.htm
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-     
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-     
-  <meta http-equiv="Content-Style-Type" content="text/css">
-      
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>CVS Checkout wizard</title>
-   
-</head>
- <body style="background-color: rgb(255,255,255);">
-   
-<h1 class="Head">CVS Checkout wizard</h1>
-   
-<p class="Para"> This wizard helps you check out one or more projects from a CVS repository.
-It is available from the Import menu, the New &gt; Project menu and the toolbar of the CVS
-Repository Exploring perspective. It is also opened when performing a Checkout As from the
-CVS Repositories view.</p>
-   
-<p class="Para">The first page of the checkout wizard allows you to choose an existing repository
-location or create a new one. If you choose to create a new location, the page from the 
-<a href="ref-40.htm">New Repository Location wizard</a> is shown.</p>
-   
-<p class="Para"> <img align="top" border="0"
- src="../images/cvs-checkout1.png" alt="CVS Checkout wizard" >
-</p>
-
-<p class="Para"> After a repository location is selected, you can now choose one 
-  or more modules to check out. You can either enter a module path or select one 
-  or more from the list of existing modules. A dot (.) can be entered to checkout 
-  the entire contents of the repository for those rare cases where the repository 
-  represents a single project. </p>
-
-<p class="Para"> <img align="top" border="0"
- src="../images/cvs-checkout2.png" alt="CVS Checkout wizard" >
-</p>
-
-<p class="Para"> Once one or more modules are selected, you can choose to check 
-  out one or more selected modules as a new projects or into an existing project 
-  or folder. If one module is selected and it does not contain a .project file 
-  (the Workbench project configuration file), you will also have the option to 
-  configure the project using the new project wizard (in order to make the project 
-  a Java project, for instance). </p>
-
-<p class="Para"> <img align="top" border="0"
- src="../images/cvs-checkout3.png" alt="CVS Checkout wizard" >
-</p> 
-
-<p class="Para">
-For a single project, you can configure the location of the project to be either
-the default location or a custom location outside the workspace. For multiple
-projects, you can configure the parent folder where all the projects should be
-located.
-</p>
-
-<p class="Para"> <img align="top" border="0"
- src="../images/cvs-checkout4.png" alt="CVS Checkout wizard" >
-</p> 
-
-<p class="Para">
-Finally, you can choose the tag to be used for the check out.
-</p>
-
-<p class="Para"> <img align="top" border="0"
- src="../images/cvs-checkout5.png" alt="CVS Checkout wizard" >
-</p> 
-   
-<img border="0" src="../images/ngrelr.png" alt="Related reference">
- <br><a href="ref-32.htm">CVS Repositories View</a>
- <br><a href="ref-40.htm">Add CVS Repository wizard</a> 
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-40b.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-40b.htm
deleted file mode 100644
index 775551a..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-40b.htm
+++ /dev/null

@@ -1,75 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-     
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-     
-  <meta http-equiv="Content-Style-Type" content="text/css">
-      
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>CVS Sharing wizard</title>
-   
-</head>
- <body style="background-color: rgb(255,255,255);">
-   
-<h1 class="Head">CVS Sharing wizard</h1>
-   
-<p class="Para"> This wizard helps you share a project with others using a CVS 
-  repository. It is available from the <strong>Team &gt; Share Project </strong>menu 
-  command of views that display resources such as one of the navigation views 
-  and the Java Packages Explorer.</p>
-   
-<p class="Para">The first page of the Sharing wizard allows you to choose the type of
-repository you would like to share you project with. If the repository type
-you wish to share with is not listed, you can click the Show All Wizards checkbox
-to see repository types that are installed but not enabled.</p>
-   
-<p class="Para"> <img align="top" border="0"
- src="../images/cvs-share1.png" alt="Sharing wizard" >
-</p>
-
-<p class="Para">
-Selecting CVS will bring you to the CVS Sharing wizard. On the first page of the
-CVS wizard, you can select the repository you wish to share with. If the repository
-is not in the list, you can select to create a new repository.
-If you choose to create a new location, the page from the 
-<a href="ref-40.htm">New Repository Location wizard</a> is shown.
-</p>
-
-<p class="Para"> <img align="top" border="0"
- src="../images/cvs-share2.png" alt="CVS Sharing wizard" >
-</p>
-
-<p class="Para">
-After you have selected the repository, you must indicate the name of the module
-that will be used to share the project. You can choose to use the same name
-as the local project or you can type in a path containing one or more folder segments
-indicating the remote module. There is also an option to reconnect the local project to an existing
-module.
-</p>
-
-<p class="Para"> <img align="top" border="0"
- src="../images/cvs-share3.png" alt="CVS Sharing wizard" >
-</p>
-
-<p class="Para"> The final page of the CVS Sharing wizard allows you to decide 
-  which resources to commit and which to ignore. There are toolbar items for changing 
-  the layout of the view and for committing and ignoring resources. If there are 
-  resources left in the view when Finish is pressed, you will be prompted to commit 
-  the remaining resources in the background (if the <em>Launch the Commit Wizard</em> 
-  option is enabled) which will allow you to return to work while the commit takes 
-  place. </p>
-
-<p class="Para"> <img align="top" border="0"
- src="../images/cvs-share4.png" alt="CVS Sharing wizard" >
-</p>
-
-<img border="0" src="../images/ngrelr.png" alt="Related reference">
- <br><a href="ref-40.htm">Add CVS Repository wizard</a>    
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-41a.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-41a.htm
deleted file mode 100644
index 0bea249..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-41a.htm
+++ /dev/null

@@ -1,75 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Merge wizard</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Merge wizard</H1>
-<P CLASS="Intro"> This wizard helps you merge changes between two states of a 
-  project into your workspace. Often the Merge Wizard is used to move changes 
-  from one branch into another, for example after splitting a branch to work on 
-  a bug fix. The merge operation takes changes between two points in a branch, 
-  the <b> start point</b> and the <b> end point</b>, and merges them into your 
-  workspace. Typically the start point will be the root of a branch (version tag) 
-  and the end point can either be the tip (latest and best) of the branch 
-  or another version tag.<br>
-  <br>
-  It is very important to understand that the destination of the merge is always 
-  the project in your workspace. After the merge has been completed you can test the 
-  changes locally and then commit them to the new branch (usually HEAD).</p>
-<P CLASS="Intro">To start a merge, select a project (or one or more resources), 
-  and select <b>Team &gt; Merge...</b> from the pop-up menu. The following dialog 
-  will appear.</p>
-<P><img src="../images/Image269_merge_init.png" alt="Merge dialog initial state" border="0" > 
-</P>
-
-
-<p>First, you should choose the end tag of the merge. This is the branch or version 
-  being merged into the workspace. Choose a version when you want to merge the 
-  differences between two versions of a project into your workspace. Choose a 
-  branch if you want to merge the changes made in the branch into your local workspace.</p>
-<p>The wizard will try to pick an appropriate tag for the start tag or base tag. 
-  If one cannot be determined, you should enter it manually. If there is no start 
-  tag, you can choose to merge without a preview, in which case a start tag is 
-  not required but the merge will happen directly into the workspace. The drawback 
-  of this is that CVS uses a text base markup to identify conflicts and this is 
-  cumbersome to work with.</p>
-
-
-<P>If the merge preview option is selected, after the finish button is pressed, 
-  the changes between the start point and end point are calculated and displayed 
-  as a <a href="ref-33a.htm">CVS Merge Synchronization</a> in the Synchronize 
-  view. Depending on the size of the project you are merging, this may take some 
-  time but can be run in the background. In the Synchronize view you can update 
-  or merge changes into your Workbench.</P>
-
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br><a href="../concepts/concepts-26.htm">Team programming with CVS</a>
-<br><a href="../concepts/concepts-27b.htm">Branches</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-<br><a href="../tasks/tasks-100a.htm">Branching</a>
-<br><a href="../tasks/tasks-100b.htm">Merging from a branch</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- >
- <br><a href="../reference/ref-47.htm">CVS</a>
-  <br><a href="ref-33a.htm">CVS Merge Synchronization</a>  
- <br><a href="ref-25.htm">Compare editor</a>  
- </p>
-    
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-42.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-42.htm
deleted file mode 100644
index b0c8e52..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-42.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en"><html><head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta http-equiv="Content-Style-Type" content="text/css"><title>Web Browser preference page</title>
-   
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"></head><body bgcolor="#ffffff">
-
-<h1 class="Head">Web Browser Preference Page</h1>
-<div class="Para"> 
-  <p>The following preferences can be changed on the Web Browser preference page.</p>
-</div>
-
-<table border="1" cellspacing="0" style="width: 100%;">
-  <caption>
-  </caption>
-  <thead>
-  </thead>
-  <tbody>
-  </tbody>
-  <tbody>
-    <tr> 
-      <th width="25%"> <div class="Para">Option</div></th>
-      <th> <div class="Para">Description</div></th>
-      <th> <div class="Para">Default</div></th>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Use internal 
-          Web browser<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option enables you 
-          to use an internal Web browser. </div></td>
-      <td align="left" valign="top"> <div class="Para">On</div></td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top"> <div class="Para">Use external Web browser<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option enables you 
-          to use an external Web browser. Select the required browser from the 
-          list of available external web browsers.</div></td>
-      <td style="vertical-align: top;">Off<br> </td>
-    </tr>
-  </tbody>
-</table>
-<p></p>
-<p>Here is what the Web Browser preference page looks like: </p>
-<p><img src="../images/ref-webbrowserpref.png" alt="Image of the Web Browser preference page"><br>
-</p>
-<p>&nbsp;<br>
-
-</p>
-
-
-</body></html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-43.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-43.htm
deleted file mode 100644
index c4d5c51..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-43.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Workbench User Guide</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Workbench User Guide</H1>
-<P CLASS="Para">
-The Help view displays help related to using the Workbench.&nbsp; See <a href="ref-34.htm">Help
-window</a> on how to navigate through the contents of the Help view.&nbsp;&nbsp;</P>
-<P CLASS="Para">If you select Workbench User Guide in the list of books displayed
-  in the Help window, you will see help topics related to using the Workbench
-  in the
-Contents tab.&nbsp; The Workbench User Guide is broken down into four main
-sections, described below.</P>
-<DIV CLASS="Topic">
-
-<DIV CLASS="Subtopic">
-<H2 CLASS="Head">
-Getting started</H2>
-<P CLASS="Para">
-This section contains tutorials that will help you
-when you start using the Workbench.</P>
-</DIV>
-<DIV CLASS="Subtopic">
-<H2 CLASS="Head">
-Concepts</H2>
-<P CLASS="Para">
-Concepts are high level descriptions of the schema
-and functions of the Workbench.&nbsp; This section helps provide a general
-understanding of how the Workbench functions.&nbsp; For example, the Concepts section includes a discussion of what perspectives and views are and how they relate to one another.</P>
-</DIV>
-<DIV CLASS="Subtopic">
-<H2 CLASS="Head">
-Tasks</H2>
-<P CLASS="Para">
-Task descriptions are step by step instructions for
-performing specific actions and tasks in the Workbench. For example, the Tasks section contains step by step instructions for
-creating a repository location, and for importing a file from the file system into the Workbench.</P>
-</DIV>
-<DIV CLASS="Subtopic">
-<H2 CLASS="Head">
-Reference</H2>
-<P CLASS="Para">
-Reference materials are helpful resources that will assist you while you are using the Workbench. This includes descriptions of various wizards, dialogs, and fields as well as Workbench resources such as specific views and perspectives.</P>
-<P CLASS="Para">
-The Reference section also includes a glossary of terms that you might find useful while using the Workbench.</P>
-</DIV>
-</DIV>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-45.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-45.htm
deleted file mode 100644
index dd2ccff..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-45.htm
+++ /dev/null

@@ -1,75 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"><title>File search</title></head>
-
-<body>
-
-<h1>File search</h1>
-
-<p>
-In the Search Dialog, the File Search tab allows you to search for files or text in the Workbench.
-You can bring up the Search Dialog by clicking on the Search toolbar button.</p>
-
-<p>
-<img src="../images/Image45_file_search.png"  alt="File search dialog" border="0"></p>
-
-<h2>Containing text</h2>
-<p>Type the expression for which you wish to do the text search. Leave this field empty to search for files.&nbsp;</p>
-
-<p>From the drop-down menu, you can choose to repeat or
-modify a recent search.</p>
-
-<h3>Wildcards</h3>
-<p>The available wildcards for search expressions are displayed in the search dialog:</p>
-
-<ul>
-	<li>"*" matches any set of characters, including the empty string</li>
-	<li>"?" matches for any character</li>
-	<li> "\" is the escape for a literal; if you want to search for an asterisk, question mark, or backslash character, type a backslash before it to indicate that you are not using these characters as wildcards (e.g., "\*", "\?", or "\\")</li>
-</ul>
-
-<h2>File name patterns</h2>
-<p>In this field, enter all the file name patterns for the files to find or search
-through for the specified expression.<br>
-</p>
-
-<h3>Wildcards</h3>
-<p>The available wildcards for file name patterns are displayed in the search dialog:</p>
-<ul>
-	<li>"*" matches any set of characters, including the empty string</li>
-	<li>"?" matches for any character</li>
-</ul>
-
-<h2>Case sensitive</h2>
-<p>Turn this option on if you want the text search to be case sensitive.</p>
-
-<h2>Scope</h2>
-<p>Choose the scope of your search. You can either search the whole workspace,
-pre-defined working sets, previously selected resources or projects enclosing
-the selected resources.</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br>
-<a href="../concepts/csearchview.htm">Search view</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-<br>
-<a href="../tasks/tasks-84b.htm">Searching for files</a><br>
-<a href="../tasks/tasks-84.htm">Searching for text within a file</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br>
-<a href="ref-26.htm">Search view</a><br>
-</p>
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-47.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-47.htm
deleted file mode 100644
index 0efd454..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-47.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>CVS</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> CVS </H1>
-<DIV CLASS="Topic"> 
-  <P CLASS="Para"> The Workbench is shipped with a built in client for the Concurrent 
-    Versions System (CVS). With this client you can access CVS repositories.</P>
-  <P CLASS="Para"> You can find more information on CVS at&nbsp; <a href="https://www.cvshome.org" target="_blank">https://www.cvshome.org</a>.</P>
-  <P CLASS="Para">You can also visit the <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/docs/online/cvs_features2.0/cvs-faq.html" target="_blank">Eclipse 
-    CVS FAQ</a>.</P>
-</DIV>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-48a.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-48a.htm
deleted file mode 100644
index afdfcb4..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-48a.htm
+++ /dev/null

@@ -1,72 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Ignoring resources from version control</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Ignoring resources from version control</H1>
-<P CLASS="Para" Label=Type>When synchronizing resources, it is possible that there 
-  are some resources that you do not want to commit to the repository. There 
-  are two ignore facilities provided, allowing the user to specify which resources 
-  should be excluded from update and commit operations.</P>
-<P CLASS="Para" Label=Type>The first is a global ignore facility, provided by the
-Workbench. The second is the CVS ignore facility, which reads the contents of a
-special file .<i>cvsignore</i> to determine what to ignore.</P>
-<h2 Label=Type>Why ignore files when synchronizing?</h2>
-<P Label=Type>There are many files that a user may not want to commit to the repository.&nbsp;
-For example, external editors may create temporary files in your project. Compilation of .java files creates .class files, and
-likewise many build operations result in binary files. These files, when taken together, may
-be quite large. In addition, they may be re-generated whenever a build is performed,
-resulting in many&nbsp; outgoing changes.  Typically these are not files that one wants to share with other members of a team or persist in the repository.&nbsp;&nbsp;</P>
-<DIV CLASS="Subtopic">
-<h2>
-Global ignore facility</h2>
-<p CLASS="Head">A global ignore facility is provided by the Workbench via the
-Team preference page.
-There is a list of file patterns against which resources will be matched before they are
-considered as version control candidates.&nbsp;
-These patterns may contain the wildcard characters "*" and "?".&nbsp; "*"
-represents any sequence of zero or more characters.&nbsp; "?" represents any one
-character.&nbsp; For example, you can specify a pattern of "*~", which would match
-any temporary files that end with "~".&nbsp;&nbsp; Any file or directory that matches any one of the
-patterns will be ignored during&nbsp; update or commit operations.&nbsp; When
-you specify a file pattern to ignore, you can temporarily disable ignoring the
-file pattern by de-selecting it from the list; you do not have to remove the
-specified file pattern from the list.<br>
-<br>
-The patterns in the global ignore facility are matched against resource names during a
-synchronize operation.&nbsp; It is important to note that the path leading up to the resource name is not
-included in the matching.&nbsp; For example, for the file &quot;/path/to/file.txt&quot;, only the string
-&quot;file.txt&quot; is matched against the patterns.&nbsp; This facility is not intended for specifying fully-qualified
-path names but for specifying globally-applicable patterns.<br>
-</p>
-<h2>CVS ignore facility</h2>
-  <p CLASS="Head">The Eclipse CVS client recognizes a file named &quot;.cvsignore&quot; 
-    in each directory of a project.&nbsp; This is a standard CVS facility and 
-    many existing CVS projects may contain this file.<br>
-    <br>
-    This text file consists of a list of files, directories, or patterns.&nbsp; 
-    In a similar way to the global ignore facility, the wildcards "*" and "?" 
-    may be present in any entry in the .cvsignore file.&nbsp; Any file or sub-directory 
-    <b> in the current directory</b> that matches any one of the patterns will 
-    be ignored.&nbsp; It is important to note that the semantics of this file 
-    differs from that of the global ignore facility in that it applies only to 
-    files and&nbsp; directories in the same directory as the .cvsignore file itself.&nbsp; 
-    A project may contain one .cvsignore file in each directory.&nbsp; For more 
-    information, please visit&nbsp; <a href="https://www.cvshome.org" target="_blank">https://www.cvshome.org</a>.</p>
-  <p CLASS="Head">Resources that have not been added to CVS control can be ignored 
-    by selecting <b>Team &gt; Add to .cvsignore</b> from the pop-up menu of the 
-    resource in one of the navigation views. This menu option is also available 
-    in the Synchronize view.</p>
-</DIV>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-5.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-5.htm
deleted file mode 100644
index 48e5a54..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-5.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Builds</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-
-<h1 class="Head">Builds</h1>
-<p class="Para">Builders create or modify workspace resources,
-usually based on the existence and state of other resources. They are a powerful
-mechanism for enforcing the constraints of some domain. For example, a Java
-builder converts Java source files (.java files) into executable class files
-(.class files), a web link builder updates links to files whose name/location
-have changed, etc.&nbsp; As resources are created and modified, builders are run
-and the constraints are maintained. This transform need not be one to one. For
-example, a single .java file can produce several .class files.&nbsp;</p>
-<h2>Auto-build vs. Manual Build</h2>
-<p class="Intro">There are two distinct user work modes with respect to
-building: relying on Auto-build, or user initiated manual building.</p>
-<p class="Intro">Users who do not need fine-grained control over when builds
-occur may simply choose to turn on auto-building.&nbsp; With auto-building on,
-builds occur after every set of resource changes (e.g., saving a file, importing
-a ZIP, ...).&nbsp; Auto-building is efficient because the amount of work done is
-proportional to the amount of change done.&nbsp; The benefit of auto-building is
-that your derived resources (e.g., Java .class files) are always up to date.
-Auto-building is turned on/off via the <b>Build automatically</b> option on the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workspace)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>General &gt; Workspace</b></a> preference page.</p>
-<p class="Intro">Users needing more control over when builds occur can turn off
-auto-building and manually invoke builds.&nbsp;This is sometimes desirable in
-cases where, for example, you know building is of no value until you finish a
-large set of changes. In this case there is no benefit to paying the cost of
-auto-building. Builds can be invoked manually in numerous ways, for example, by
-selecting <b>Build Project</b> from a project's context menu.</p>
-<p class="Intro">The disadvantage of manual building is that the problems that
-were generated to indicate build errors quickly become out of date until you
-build. In addition, it is very important that you remember to manually build
-before relying on build output (e.g. before running your Java program).</p>
-<h2>Building and Cleaning</h2>
-<p class="Intro">Builds work incrementally based on a previous built state. They
-will apply the transforms of the configured builders only on the resources that have 
-changed since that previous state was computed (i.e., since the last build).
-Auto-building always uses incremental building for efficiency.</p>
-<p class="Intro">A clean build (<b>Project &gt; Clean</b>) discards any existing
-built state.  The next build after a clean will transform all resources according the 
-domain rules of the configured builders.</p>
-<p class="Intro">Depending on the user's needs, build and clean can
-be done over a specific set of projects or the workspace as a whole.&nbsp;Specific
-files and folders cannot be built separately.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-56.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-56.htm
deleted file mode 100644
index 2daad82..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-56.htm
+++ /dev/null

@@ -1,120 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>File menu</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">File menu</H1>
-<P CLASS="Para">
-This menu allows you to create, save, close, print, import, and export Workbench resources and exit the Workbench itself.</P>
-<DIV CLASS="Topic">
-<h2>New</h2>
-<P CLASS="Para">
-This command creates new resources.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Open File</h2>
-<P CLASS="Para">
-This command allows you to open files that do not reside in the workspace in the text editor.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Close</h2>
-<P CLASS="Para">
-This command closes the active editor.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Close All</h2>
-<P CLASS="Para">
-This command closes all open editors.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Save</h2>
-<P CLASS="Para">
-This command allows you to save the contents of the
-active editor.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Save As</h2>
-<P CLASS="Para">
-This command allows you to save the contents of the
-active editor under another file name or location.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Save All</h2>
-<P CLASS="Para">
-This command saves the contents of all open editors.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Revert</h2>
-<P CLASS="Para">
-This command replaces the contents of the active editor with the previously saved contents.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Move</h2>
-<P CLASS="Para">
-This command moves the currently selected resources to a different location.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Rename</h2>
-<P CLASS="Para">
-This command changes the name of the currently selected resource.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Refresh</h2>
-<P CLASS="Para">
-This command refreshes the resource with the contents in the file system.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Convert Line Delimiters To</h2>
-<P CLASS="Para">
-These commands alter the line delimiters for the selected files in the active part.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Print</h2>
-<P CLASS="Para">
-This command prints the contents of the active editor.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Switch workspace</h2>
-<P CLASS="Para">
-This command allows you to switch to a different workspace.  This will restart the workbench.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Import</h2>
-<P CLASS="Para">
-This option launches the import wizard, which allows you to add resources
-to the Workbench.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Export</h2>
-<P CLASS="Para">
-This option launches the export wizard, which allows you to export resources from the Workbench.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Properties</h2>
-<P CLASS="Para">
-This command opens the properties dialog for the currently selected resource.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Recent file list</h2>
-<P CLASS="Para">
-A list of the most recently accessed files in the Workbench is maintained at the bottom of the File menu.&nbsp;
-Any of these files can be opened from the File menu by simply selecting the file name.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Exit</h2>
-<P CLASS="Para">
-This command closes and exits the Workbench.</P>
-</DIV>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-57.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-57.htm
deleted file mode 100644
index 2ea539e..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-57.htm
+++ /dev/null

@@ -1,119 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Edit menu</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h1 class="Head">Edit menu</h1>
-<p class="Intro"><a name="pgfId-1010738"></a>This menu helps you manipulate
-resources in the editor area.</p>
-<div class="Topic">
-  <a name="elementId-1010741"></a><a name="pgfId-1010746"></a>
-  <h2>Undo</h2>
-  <p class="Para"><a name="pgfId-1010752"></a>This command reverses your most
-  recent editing action.</p>
-</div>
-<div class="Topic">
-  <a name="elementId-1007106"></a><a name="pgfId-1010758"></a>
-  <h2>Redo</h2>
-  <p class="Para"><a name="pgfId-1007117"></a>This command re-applies the editing
-  action that has most recently been reversed by the Undo action.</p>
-</div>
-<div class="Topic">
-  <a name="elementId-1007120"></a><a name="pgfId-1007125"></a>
-  <h2>Cut</h2>
-  <p class="Para"><a name="pgfId-1007131"></a>This command removes the selection
-  and places it on the clipboard.</p>
-</div>
-<div class="Topic">
-  <a name="elementId-1007134"></a><a name="pgfId-1007139"></a>
-  <h2>Copy</h2>
-  <p class="Para"><a name="pgfId-1007145"></a>This command places a copy of the
-  selection on the clipboard.</p>
-</div>
-<div class="Topic">
-  <a name="elementId-1007148"></a><a name="pgfId-1007153"></a>
-  <h2>Paste</h2>
-  <p class="Para"><a name="pgfId-1007159"></a>This command places the text or
-  object on the clipboard at the current cursor location in the currently active
-  view or editor.</p>
-</div>
-<div class="Topic">
-  <a name="elementId-1007162"></a><a name="pgfId-1007167"></a>
-  <h2>Delete</h2>
-  <p class="Para"><a name="pgfId-1007173"></a>This command removes the current
-  selection.</p>
-</div>
-<div class="Topic">
-  <a name="elementId-1007176"></a><a name="pgfId-1007181"></a>
-  <h2>Select All</h2>
-  <p class="Para"><a name="pgfId-1007187"></a>This command selects all text or
-  objects in the currently active view or editor.</p>
-</div>
-<div class="Topic">
-  <a name="elementId-1007190"></a><a name="pgfId-1007195"></a>
-  <h2>Find/Replace</h2>
-  <p class="Para"><a name="pgfId-1007201"></a>This command allows you to search
-  for an expression in the active editor, and optionally replace the expression with a new expression.</p>
-</div>
-<DIV CLASS="Topic">
-<h2>Find Next</h2>
-<P CLASS="Para">
-This command allows you to search for the next occurrence of the current selection, or
-for the next occurrence of the most recent expression found using the Find/Replace action.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Find Previous</h2>
-<P CLASS="Para">
-This command allows you to search for the previous occurrence of the current selection, or
-for the previous occurrence of the most recent expression found using the Find/Replace action.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Incremental Find Next</h2>
-<P CLASS="Para">
-This command allows you to search for expressions in the active editor.  As you type the search
-expression, it will incrementally jump to the next exact match in the active editor.  While in this
-mode, the up and down cursor keys can be used to navigate between matches, and the search
-can be cancelled by pressing left or right cursor keys, the enter key, or the escape key.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Incremental Find Previous</h2>
-<P CLASS="Para">
-This command allows you to search for expressions in the active editor.  As you type the search
-expression, it will incrementally jump to the previous exact match in the active editor.  While in this
-mode, the up and down cursor keys can be used to navigate between matches, and the search
-can be cancelled by pressing left or right cursor keys, the enter key, or the escape key.</P>
-</DIV>
-<div class="Topic">
-  <a name="elementId-1007218"></a><a name="pgfId-1007223"></a>
-  <h2>Add Bookmark</h2>
-  <p class="Para"><a name="pgfId-1007230"></a>This command adds a bookmark in
-  the active file on the line where the cursor is currently displayed.</p>
-</div>
-<DIV CLASS="Topic">
-<h2>Add Task</h2>
-<P CLASS="Para">
-This command adds a task in the active file on the line where the cursor is currently displayed.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Word Completion</h2>
-<P CLASS="Para">
-This action will attempt to complete the word currently being entered in the active editor.
-</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Set Encoding</h2>
-<P CLASS="Para">
-This action launches a dialog that allows you to change the file encoding used to read and write the file in the active editor.</P>
-</DIV>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-58.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-58.htm
deleted file mode 100644
index e075fa2..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-58.htm
+++ /dev/null

@@ -1,104 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Navigate menu</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>
-Navigate menu
-</h1>
-<P CLASS="Intro">
-This menu allows you to locate and navigate through resources and other artifacts displayed in the Workbench.</p>
-<DIV CLASS="Topic">
-<h2>
-Go Into</h2>
-<P CLASS="Para">
-This command refocuses the active view so that the current selection is at the root.  This allows web 
-browser style navigation within hierarchies of artifacts.
-</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2 CLASS="Head">
-Go To</H2>
-
-<UL CLASS="UnorderedList">
-<LI CLASS="Item">
-<b>Back</b>:&nbsp; This command displays the hierarchy that was displayed immediately prior to the current display.&nbsp; For example, if
-you Go Into a resource, then the Back command in the resulting display returns the view to the same hierarchy from which you activated the Go Into command.&nbsp; This command is similar to the Back button in an HTML browser.</LI>
-<LI CLASS="Item">
-<b>Forward</b>:&nbsp; This command displays the hierarchy that was displayed immediately after the current display.&nbsp; For example, if you've just selected the Back command, then selecting the Forward command in the resulting display returns the view to the same hierarchy from which you activated the Back command.&nbsp; This command is similar to the Forward button in an HTML browser.</LI>
-<LI CLASS="Item">
-<b>Up one level</b>:&nbsp; This command displays the hierarchy of the parent of the current highest-level resource.</LI>
-  <LI CLASS="Item"><B>Resource</B>: This command allows you to navigate quickly to a resource. For more information
-  see the links to related tasks below.</LI>
-</UL>
-</DIV>
-<DIV CLASS="Topic">
-<H2>Open Resource</H2>
-<P>This command displays a dialog that lets you select any resource in the
-workspace to open it in an editor. For more information see the links
-to related tasks below.</P>
-</DIV>
-<DIV CLASS="Topic">
-<H2>Show In</H2>
-<P>This sub-menu is used to find and select the currently selected resource in another view.
-If an editor is active, these commands are used to select the resource currently being edited
-in another view.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Next</h2>
-<P CLASS="Para">
-This command navigates to the next item in a list or table in the active view.  For example, when the search results view
-is active, this navigates to the next search result.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Previous</h2>
-<P CLASS="Para">
-This command navigates to the previous item in a list or table in the active view.  For example, when the search results view
-is active, this navigates to the previous search result.</P>
-</DIV>
-
-<DIV CLASS="Topic">
-<h2>Last Edit Position</h2>
-<P CLASS="Para">
-This command allows you to jump the last edit position.</P>
-</DIV>
-
-<DIV CLASS="Topic">
-<h2>Go to Line</h2>
-<P CLASS="Para">
-This command allows you to jump to a specific line in the active editor.</P>
-</DIV>
-
-<DIV CLASS="Topic">
-<h2>
-Back</h2>
-<P CLASS="Para">
-This command navigates to the previous resource that was viewed in an editor.
-Analogous to the <b>Back</b> button on a web browser.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Forward</h2>
-<P CLASS="Para">
-This command navigates to undo the effect of the previous
-<b>Back</b> command.  Analogous to the <b>Forward</b> button on a web browser.</P>
-</DIV>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-46ag.htm">Finding a resource quickly</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-59.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-59.htm
deleted file mode 100644
index 967cb73..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-59.htm
+++ /dev/null

@@ -1,88 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Project menu</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Project menu</H1>
-<P CLASS="Para">
-The Project menu allows you to perform actions (builds or compilations) on projects in the Workbench.</P>
-<DIV CLASS="Topic">
-<h2>
-Open Project</h2>
-<P CLASS="Para">
-This command opens the currently selected project or projects.  The selected projects must currently 
-be closed for this command to be available.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Close Project</h2>
-<P CLASS="Para">
-This command closes the currently selected project or projects.  The selected projects must be
-currently open for this command to be available.  Closing a project will remove all of that project's
-state from memory, but the contents on disk are left untouched.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Build All</h2>
-<P CLASS="Para">
-This command performs an incremental build on all projects in the Workbench. That is, it builds 
-(compiles) all resources in the Workbench that are affected by any resource changes since the 
-last incremental build.  This command is only available if auto-build is turned off.  Auto-build is turned
-off via the <strong>Build Automatically</strong> menu option or from the <b>General &gt; Workspace</b> preference page.
-</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Build Project</h2>
-<P CLASS="Para">
-This command performs an incremental build on the currently selected project. That is, it builds 
-(compiles) all resources in the project that are affected by any resource changes since the 
-last build.  This command is only available if auto-build is turned off.  Auto-build is turned
-off via the <strong>Build Automatically</strong> menu option or from the <b>General &gt; Workspace</b> preference page.
-</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Build Working Set</h2>
-<P CLASS="Para">
-This menu allows you to performs an incremental build on a working set. That is, it builds 
-(compiles) all resources in the working set that are affected by any resource changes since the 
-last build.  This command is only available if auto-build is turned off.  Auto-build is turned
-off via the <strong>Build Automatically</strong> menu option or from the <b>General &gt; Workspace</b> preference page.
-</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Clean</h2>
-<P CLASS="Para">
-This command discards all previous build results.  If autobuild is on, then this invokes a full build.
-</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Build Automatically</h2>
-<P CLASS="Para">
-This command allows you to toggle the auto build preference.  The auto-build preference is also located on the <b>General &gt; Workspace</b> preference page.
-</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Properties</h2>
-<P CLASS="Para">
-This command opens a dialog showing the properties of the selected project or of the project that contains the
-selected resource.</P>
-</DIV>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-6.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-6.htm
deleted file mode 100644
index d1f95d8..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-6.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Perspectives</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Perspectives</H1>
-
-<P CLASS="Intro">
-A perspective defines the initial set and layout of views in the Workbench
-window. One or more perspectives can exist in a single Workbench window.</p>
-<p CLASS="Para" Label=Type>Perspectives can be opened either in the same 
-(existing) Workbench window, hiding the current perspective, or in a new 
-Workbench window</p>
-<p CLASS="Para" Label=Type>Perspectives define visible action sets, which you
-can change to customize a perspective.&nbsp; You can save a perspective that you
-build in this manner, making your own custom perspective that you can open again
-later.&nbsp;&nbsp;</p>
-<P CLASS="Para">
-The Workbench defines the <i>Resource</i> perspective by default. This 
-perspective shows views relevant to resource management.
-</P>
-
-<P><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-60.htm">Window Menu</a>
-<br><a href="ref-24.htm">Editor Area</a>
-<br><a href="ref-27.htm">Navigator View</a>
-<br><a href="ref-30.htm">Outline View</a>
-<br><a href="ref-31.htm">Tasks View</a>
-</P>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-60.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-60.htm
deleted file mode 100644
index eb334f9..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-60.htm
+++ /dev/null

@@ -1,149 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Window menu</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Window menu</H1>
-<P CLASS="Intro">
-This menu allows you to display, hide, and otherwise manipulate the various views, perspectives, and actions in the Workbench.</p>
-
-<DIV CLASS="Topic">
-<h2>
-New Window</h2>
-<P CLASS="Para">
-This command opens a new Workbench window with the same perspective as the current perspective.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-New Editor</h2>
-<P CLASS="Para">
-This command opens an editor based on the currently active editor.  It will have the same editor type and input as the original.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Open Perspective</h2>
-<P CLASS="Para">
-This command opens a new perspective in this Workbench window.
-This preference can be changed on the <b>General &gt; Perspectives</b>
-preference page. All of the perspectives that are open within the Workbench window are
-shown on the shortcut bar.</P>
-<P CLASS="Para">
-The perspectives you will likely want to open are
-listed first.&nbsp;This list is dependent on the current perspective. From the <b>Other...</b> submenu you can open any perspective.</P>
-<P CLASS="Para"><img src="../images/Image207_persp_sel.png" alt="Select Perspective dialog" border="0" ></P>
-<P CLASS="Para">&nbsp;</P>
-</DIV>
-
-<DIV CLASS="Topic">
-<h2>
-Show View</h2>
-<P CLASS="Para">
-This command displays the selected view in the
-current perspective.&nbsp; You can configure how views are opened on the <b>General &gt; 
-Perspectives</b> preference page. Views you are likely to want to open are listed
-first.&nbsp;This list is dependent on the current perspective. From the <b>Other...</b> submenu you can open any view.&nbsp; The views
-are sorted into categories in the Show View dialog.</P>
-<P CLASS="Para"><img src="../images/Image208_view_sel.png" alt="Show View Dialog" border="0" ></P>
-</DIV>
-
-<DIV CLASS="Topic">
-  <h2> Customize Perspective</h2>
-</DIV>
-<DIV CLASS="Topic">
-  <P CLASS="Para"> Each perspective includes a predefined set of actions that are 
-    accessible from the menu bar and Workbench toolbar.&nbsp;</P>
-<P CLASS="Para"><img src="../images/Image258_perps_custom.png" alt="Customize Perspective Dialog" border="0" > 
-  </P>
-</DIV>
-
-<DIV CLASS="Topic">
-<h2>
-Save Perspective As</h2>
-<P CLASS="Para">
-This command allows you to save the current perspective,
-creating your own custom perspective.&nbsp; You can open more perspectives of
-this type using the <b>Window &gt; Open Perspective &gt; Other</b> menu item once you have
-saved a perspective.&nbsp;</P>
-  <P CLASS="Para"> <img src="../images/Image206_persp_saveas.png" alt="Save Perspective As dialog" border="0" >x</P>
-</DIV>
-
-<DIV CLASS="Topic">
-<h2>
-Reset Perspective</h2>
-<P CLASS="Para">
-This command changes the layout of the current perspective to its original
-configuration.</P>
-</DIV>
-
-<DIV CLASS="Topic">
-<h2>
-Close Perspective</h2>
-<P CLASS="Para">
-This command closes the active perspective.</P>
-</DIV>
-
-<DIV CLASS="Topic">
-<h2>
-Close All Perspectives</h2>
-<P CLASS="Para">
-This command closes all open perspectives in the
-Workbench window.</P>
-</DIV>
-
-<DIV CLASS="Topic"> 
-  <h2> Navigation</h2>
-<P CLASS="Para">
-This submenu contains shortcut keys for navigating between the views, perspectives, and editors in the Workbench window.</P>
-  <UL CLASS="UnorderedList">
-    <LI CLASS="Item"> <b>Show System Menu</b>:&nbsp; Shows the menu that is used 
-      for resizing, closing or pinning the current view or editor.</LI>
-    <LI CLASS="Item"> <b>Show View Menu</b>:&nbsp; Shows the drop down menu that 
-      is available in the toolbar of the active view.</LI>
-    <LI CLASS="Item"> <strong>Maximize active view or editor: </strong>Causes 
-      the active part to take up the entire screen, or if it already is, returns 
-      it to its previous state. </LI>
-    <LI><b>Activate Editor</b>:&nbsp; Makes the current editor active.</LI>
-    <LI CLASS="Item"> <b>Next Editor</b>:&nbsp; Activates the next open editor 
-      in the list of most recently used editors.</LI>
-    <LI CLASS="Item"> <b>Previous Editor</b>:&nbsp; Activates the previous open 
-      editor in the list of most recently used editors.</LI>
-    <LI CLASS="Item"> <strong>Switch to editor:</strong> Shows a dialog that allows 
-      switching to opened editors. Shows a dialog that allows switching to opened 
-      editors. </LI>
-    <LI><b>Next View</b>:&nbsp; Activates the next open view in the list of most 
-      recently used views.</LI>
-    <LI CLASS="Item"> <b>Previous View</b>:&nbsp; Activates the previous open 
-      view in the list of most recently used editors.</LI>
-    <LI CLASS="Item"> <b>Next Perspective</b>:&nbsp; Activates the next open perspective 
-      in the list of most recently used perspectives.</LI>
-    <LI CLASS="Item"> <b>Previous Perspective</b>:&nbsp; Activates the previous 
-      open perspective in the list of most recently used perspectives.</LI>
-  </UL>
-</DIV>
-<DIV CLASS="Topic"></DIV>
-<DIV CLASS="Topic">
-<h2>
-Preferences</h2>
-<P CLASS="Para">
-This command allows you to indicate your preferences for using the Workbench.&nbsp;  There
-are a wide variety of preferences for configuring the appearance of the Workbench and its views, 
-and for customizing the behavior of all tools that are installed in the Workbench.
-</P>
-<DIV CLASS="XRefList">
-</DIV>
-</DIV>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-61.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-61.htm
deleted file mode 100644
index 60a23b0..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-61.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Help menu</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>
-Help menu</h1>
-<P CLASS="Para">
-This menu provides help on using the Workbench.</P>
- <h2 CLASS="Head"> Welcome</h2>
-<p CLASS="Head">
-This command will open the welcome content.</p>
-<DIV CLASS="Topic">
-<h2 CLASS="Head">
-Help Contents</h2>
-<P CLASS="Para">
-This command displays the help contents in a help window or external browser.
-The help contents contains help books, topics, and information related to the Workbench and installed
-features.</P>
-<h2 CLASS="Head">
-Search</h2>
-<P CLASS="Para">
-This command displays the help view opened on the Search page.</P>
-<h2 CLASS="Head">
-Dynamic Help</h2>
-<P CLASS="Para">
-This command displays the help view opened to Related Topics page.</P>
-<h2 CLASS="Head"> Key Assist ...</h2>
-  <p CLASS="Head"> This command will display a list of key bindings</p>
-  <h2 CLASS="Head"> Tips and Tricks ...</h2>
-<p CLASS="Head">
-This command will open a list of interesting productivity features that you may not have discovered.</p>
-<h2 CLASS="Head"> Cheat Sheets ...</h2>
-  <p CLASS="Head"> This command will open the cheat sheet selection dialog.</p>
-<h2 CLASS="Head">
-<a NAME="SoftwareUpdates"></a>Software Updates</h2>
-<P CLASS="Para">
-This group of commands allows you to update your product and to download and
-install new features.</P>
-<h2 CLASS="Head">
-About</h2>
-<P CLASS="Para">
-This command displays information about the product, installed features, and
-available plug-ins.</P>
-</DIV>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-65.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-65.htm
deleted file mode 100644
index e474c86..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-65.htm
+++ /dev/null

@@ -1,73 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Navigator view icons</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Navigator view icons</H1>
-<P CLASS="Para"> The following icons can appear in the navigation views:</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-Navigator view icons</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Icon</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<IMG SRC="../images/ref-10.png" ALIGN="BASELINE"  alt="Open Project icon">
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Project (open)</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<IMG SRC="../images/ref-12.png" ALIGN="BASELINE"  alt="Folder icon">
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Folder (open)</P>
-</TD>
-</TR>
-<TR>
-<TD COLSPAN="1" valign="top" align="left">
-<IMG SRC="../images/ref-11.png" ALIGN="BASELINE"  alt="Closed Project icon">
-</TD>
-<TD COLSPAN="1" valign="top" align="left">
-Project (closed)
-</TD>
-</TR>
-<TR>
-<TD COLSPAN="1" valign="top" align="left">
-<IMG SRC="../images/ref-15.png" ALIGN="BASELINE"  alt="File Icon">
-</TD>
-<TD COLSPAN="1" valign="top" align="left">
-Generic File
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-66.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-66.htm
deleted file mode 100644
index 9841b6f..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-66.htm
+++ /dev/null

@@ -1,103 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Editor area marker bar</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Editor area marker bar</H1>
-<P CLASS="Para">
-The following markers can appear in the marker bar (to the left of the editor area):</P>
-<TABLE BORDER="1" width="209" cellspacing="0">
-<CAPTION>
-Marker Bar Markers</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1" width="40">
-<P CLASS="Para">
-Icon</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1" width="169">
-<P CLASS="Para">
-Description</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" width="40">
-<img src="../images/ref-16.png"  align="BASELINE" alt="Bookmark Icon">
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="169">
-<P CLASS="Para">
-Bookmark</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" width="40">
-<img src="../images/ref-17.png"  align="BASELINE" alt="Breakpoint Icon">
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="169">
-<P CLASS="Para">
-Breakpoint</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" width="40">
-<img src="../images/ref-18.png"  align="BASELINE" alt="Task marker icon">
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="169">
-<P CLASS="Para">
-Task marker</P>
-</TD>
-</TR>
-<TR>
-      <TD ROWSPAN="1" COLSPAN="1" width="40"> 
-        <IMG SRC="../images/searchm_obj.png"  alt="Search result icon" width="16" height="16" ALIGN="BASELINE" > 
-      </TD>
-<TD ROWSPAN="1" COLSPAN="1" width="169">
-<P CLASS="Para">
-Search result</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" width="40">
-<IMG SRC="../images/ref-24.png" ALIGN="BASELINE"  alt="Error marker icon" >
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="169">
-<P CLASS="Para">
-Error marker</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" width="40">
-<img src="../images/ref-22.png"  align="BASELINE" alt="Warning marker icon">
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="169">
-<P CLASS="Para">
-Warning marker</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" width="40">
-<img src="../images/ref-20.png"  align="BASELINE" alt="Information marker icon">
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="169">
-<P CLASS="Para">
-Information marker</P>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-67.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-67.htm
deleted file mode 100644
index 853dad6..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-67.htm
+++ /dev/null

@@ -1,74 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Tasks view</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Tasks view</H1>
-<P CLASS="Para">
-The following markers can appear in the Tasks view:</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-Tasks View Icons</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Icon</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Icon</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<IMG SRC="../images/ref-21.png" ALIGN="BASELINE"  alt="High priority task">
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-High priority task</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<IMG SRC="../images/ref-23.png" ALIGN="BASELINE"  alt="Low priority task">
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Low priority task</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<img src="../images/ref-25.png"  align="BASELINE" alt="Completed task">
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Completed task</P>
-</TD>
-</TR>
-
-</TBODY>
-</TABLE>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-68.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-68.htm
deleted file mode 100644
index 7a1cb75..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-68.htm
+++ /dev/null

@@ -1,243 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Toolbar buttons</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Toolbar buttons</H1>
-<P CLASS="Para">
-The following buttons may appear in the Workbench toolbar, toolbars for views, and the shortcut bar:</P>
-<TABLE BORDER="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Button</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Description</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Button</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Description</P></TH>
-    </TR>
-  </THEAD>
-  <TBODY>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/new_persp.png" ALIGN="BASELINE"  alt = "New perspective image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Open a new perspective</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/save_edit.png" ALIGN="BASELINE"  alt = "Save edit image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Save the active editor contents</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/saveall_edit.png" ALIGN="BASELINE"  alt = "Save all image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Save the contents of all editors</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/saveas_edit.png" ALIGN="BASELINE"  alt = "Save as image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Save editor contents under a new name or location</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/search_src.png" ALIGN="BASELINE"  alt = "Open search dialog image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Opens the search dialog</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/print_edit.png" ALIGN="BASELINE"  alt = "Print editor image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Print editor contents</P></TD>
-    </TR>
-    <TR> 
-      <TD height="40" COLSPAN="1" ROWSPAN="1" align="left" valign="top"> <IMG SRC="../images/new_wiz.png" ALIGN="BASELINE"  alt = "New wizard image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">Open 
-          a resource creation wizard</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/newfile_wiz.png" ALIGN="BASELINE"  alt = "New file image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Open a file creation wizard</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/newfolder_wiz.png" ALIGN="BASELINE"  alt = "New folder image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Open a folder creation wizard</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/newprj_wiz.png" ALIGN="BASELINE"  alt = "New project image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Open a project creation wizard</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/import_wiz.png" ALIGN="BASELINE"  alt = "Import wizard image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Open the import wizard</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/export_wiz.png" ALIGN="BASELINE"  alt = "Export wizard image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Open the export wizard</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/build_exec.png" ALIGN="BASELINE"  alt = "Build image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">Run 
-          incremental build</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/run_exec.png" ALIGN="BASELINE"  alt = "Run image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Run a program</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/debug_exec.png" ALIGN="BASELINE"  alt = "Debug image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Debug a program</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/external_tools.png" ALIGN="BASELINE"  alt = "Run external tool" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Run an external tool or Ant</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/cut_edit.png" ALIGN="BASELINE"  alt = "Cut image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Cut selection to clipboard</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/copy_edit.png" ALIGN="BASELINE"  alt = "Copy image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Copy selection to clipboard</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/paste_edit.png" ALIGN="BASELINE"  alt = "Paste image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Paste selection from clipboard</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/undo_edit.png" ALIGN="BASELINE"  alt = "Undo edit image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Undo most recent edit</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/redo_edit.png" ALIGN="BASELINE"  alt = "Redo edit image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Redo most recent undone edit</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/next_nav.png" ALIGN="BASELINE"  alt = "Navigate next image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Navigate to next item in a list</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/prev_nav.png" ALIGN="BASELINE"  alt = "Navigate previous image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Navigate to previous item in a list</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/forward_nav.png" ALIGN="BASELINE"  alt = "Navigate forwards image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Navigate forwards</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/backward_nav.png" ALIGN="BASELINE"  alt = "Navigate backwards image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Navigate backwards</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/up_nav.png" ALIGN="BASELINE"  alt = "Navigate up image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Navigate up one level</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"><IMG SRC="../images/addbkmrk_tsk.png" ALIGN="BASELINE"  alt = "Add bookmark or task image" ></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">Add bookmark or task</TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/view_menu.png" ALIGN="BASELINE"  alt = "View menu image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Open a view's drop down menu</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <img src="../images/close_view.png"  align="BASELINE" alt="Close view image" height="16"> 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Close view or editor</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/pin_editor.png" ALIGN="BASELINE"  alt = "Pin editor image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Pin editor to prevent automatic reuse</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/filter_ps.png" ALIGN="BASELINE"  alt = "Filter tasks or properties" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Filter tasks or properties</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/gotoobj_tsk.png" ALIGN="BASELINE"  alt = "Goto object image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Go to a task, problem, or bookmark in the editor</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/defaults_ps.png" ALIGN="BASELINE"  alt = "Restore defaults image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Restore default properties</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/tree_mode.png" ALIGN="BASELINE"  alt = "Tree mode image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Show items as a tree</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/refresh_nav.png" ALIGN="BASELINE"  alt = "Refresh image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Refresh view contents</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/alpha_mode.png" ALIGN="BASELINE"  alt = "Alphabetical order image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Sort list in alphabetical order</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/stop_nav.png" ALIGN="BASELINE"  alt = "Cancel operation image" > 
-      </TD>
-      <td>Cancel a long running operation</td>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/delete_edit.png" ALIGN="BASELINE"  alt = "Delete image" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Delete selected item or content</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/last_edit_pos.png" ALIGN="BASELINE"  alt = "Last edit location" > 
-      </TD>
-      <td>Last edit location</td>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/mark_occurrences.png" ALIGN="BASELINE"  alt = "Toggle Mark Occurrences" > 
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Toggle Mark Occurrences</P></TD>
-    </TR>
-  <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <IMG SRC="../images/segment_edit.png" ALIGN="BASELINE"  alt = "Show source of selected element only" > 
-      </TD>
-      <td>Show source of selected element only</td>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">  </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"></TD>
-    </TR>
-    
-  </TBODY>
-</TABLE>
-<P>&nbsp;<br>
-<img border="0" src="../images/ngrelc.png" alt="Related concepts" ><a href="../concepts/concepts-18.htm"><br>
-Toolbars</a>
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-6a.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-6a.htm
deleted file mode 100644
index c21aa4e..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-6a.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Local history</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Local history</H1>
-<p>Local history of a file is maintained when you create or modify a file. Each time you edit and save
-a file,&nbsp;a copy of it is saved. This allows you to compare
-your current file state to a previous state, or replace the file with a previous
-state.&nbsp;Each state in the local
-history is identified by the date and time the file was
-saved.&nbsp;&nbsp;</p>
-<p>Neither projects nor folders have local history.</p>
-<p>Here is a look at what the local history of a Workbench file might look
-like:</p>
-<p><img src="../images/Image273_local_hist.png" alt="Local history dialog" border="0" ></p>
-<P>To view the local history of a file, choose Team &gt; Compare with &gt; Local History... from the pop-up
-menu.&nbsp;You can select different local states in the list, which are compared against the
-current file. You can also revert to the local history when you select a file and
-select the Team &gt; Replace With &gt; Local History... menu item.&nbsp;&nbsp;
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-7.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-7.htm
deleted file mode 100644
index 6396abe..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-7.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en"><html><head>

-

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-

-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

-   <meta http-equiv="Content-Style-Type" content="text/css"><title>Accessibility preference page</title>

-   

-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"></head><body bgcolor="#ffffff">

-

-<h1 class="Head">Accessibility Preference Page</h1>

-<div class="Para"></div>

-

-<div class="Para">

-  <p>The following preferences can be changed on the Accessibility page.</p>

-

-</div>

-

-<table width="75%" border="1" cellspacing="0" style="width: 100%;">

-  <caption>

-  </caption>

-  <thead>

-  </thead>

-  <tbody>

-  </tbody>

-  <tbody>

-    <tr> 

-      <th width="25%"> <div class="Para">Option</div></th>

-      <th> <div class="Para">Description</div></th>

-      <th> <div class="Para">Default</div></th>

-    </tr>

-    <tr> 

-      <td align="left" valign="top" width="25%"> <div class="Para">Use custom 

-          caret <br>

-        </div></td>

-      <td align="left" valign="top"> <div class="Para">This option replaces the 

-          original caret with a custom caret and shows a different caret for Overwrite 

-          and Insert mode.<br>

-        </div></td>

-      <td align="left" valign="top"> <div class="Para">On</div></td>

-    </tr>

-    <tr> 

-      <td style="vertical-align: top; width: 25%;">Enable thick caret</td>

-      <td style="vertical-align: top;"> This option replaces the original caret 

-        with a more visible, thicker caret.<br> </td>

-      <td style="vertical-align: top;">On<br> </td>

-    </tr>

-    <tr> 

-      <td align="left" valign="top" width="25%"> <div class="Para">Use characters 

-          to show changes on line number bar<br>

-        </div></td>

-      <td align="left" valign="top">Quick Diff shows the changes in a vertical 

-        ruler using colors. Color blind persons can enable this option to show 

-        the differences with different characters in the line<br>

-        number ruler.<br> </td>

-      <td align="left" valign="top"> Off<br> </td>

-    </tr>

-  </tbody>

-</table>

-

-<p></p>

-

-<p>Here is what the Accessibility preference page looks like: </p>

-<p><img src="../images/ref-accessibility.png" alt="Accessibility preference page"><br>

-

-

-</p>

-<p>

-</p>

-</body></html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-70.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-70.htm
deleted file mode 100644
index 143ae9c..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-70.htm
+++ /dev/null

@@ -1,865 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Import wizard</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Import wizard</H1>
-<P CLASS="Para">
-This wizard helps you import resources into the Workbench.</P>
-<P CLASS="Para">
-When the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Import wizard</b></a>
-first comes up, you must choose what type of import to
-do:</P><img src="../images/Image261_import_sel.png" alt="Import wizard" border="0">
-<P CLASS="Para"> </P>
-
-<DIV CLASS="Topic">
-  <h2> Archive File</h2>
-  <p CLASS="Head"> If you choose this option, you will import files from an archive 
-    file.</p>
-  <P>&nbsp;<img src="../images/Image263_import_zip.png" alt="Archive file import wizard page" border="0" > 
-  </P>
-<P>&nbsp;
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-    Import - Archive File Options 
-    </CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para"> Archive File</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The file from which to import.&nbsp; Type in the full path or Browse to select
-the path on the file system.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;blank&gt;</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Filter Types...</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Dialog to select which file types to import.&nbsp; Use this to restrict the
-import to only certain file types.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Check off all resources for import</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Deselect All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Uncheck all resources.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-<TD COLSPAN="1">
-Folder
-</TD>
-<TD COLSPAN="1">
-The folder into which the resources will be imported.&nbsp; Type the path or
-Browse to select a path in the Workbench.
-</TD>
-<TD COLSPAN="1">
-The folder holding the selected resource
-</TD>
-</TR>
-<TR>
-<TD COLSPAN="1">
-Overwrite existing resources without warning
-</TD>
-<TD COLSPAN="1">
-Determines whether importing a resource should silently overwrite a resource
-which already exists in the Workbench. If this option is off, you will be
-prompted before a given resource is overwritten, in which case you can either
-overwrite the resource, skip it, or cancel the import.
-</TD>
-<TD COLSPAN="1">
-Off
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-</DIV>
-
-<DIV CLASS="Topic">
-  <h2>Checkout projects from CVS</h2>
-  <p CLASS="Head">Import a project from a CVS Repository.</p>
-  <P>&nbsp;<img src="../images/Image263_import_cvs.png" alt="CVS project import wizard page" width="399" height="413" border="0" > 
-  </P>
-<P>&nbsp;
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-    Import - Checkout projects from CVS Options 
-    </CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Create a new repository location</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Go to the <a href="ref-40.htm">New CVS Repository Location
-wizard</a>.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&lt;disabled&gt;</P>
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Use existing repository location</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Use a previously datafilled CVS location.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>enabled</i></P>
-</TD>
-</TR>
-
-</TBODY>
-</TABLE>
-</DIV>
-
-<DIV CLASS="Topic">
-<h2>
-Existing Project into Workspace</h2>
-<p CLASS="Head">
-Imports a project into this workspace that was previously located in this workspace, or
-that currently exists in another workspace.</p>
-  <P>&nbsp;<img src="../images/Image264_existing_project.png" alt="Existing project import wizard page"  border="0" > 
-  </P>
-<P>&nbsp;
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-Import - Existing Project Options</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select root directory</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Root directory in the File System to start
-scanning for projects to import. Type in the full path or Browse to
-select the path on the file system.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;blank&gt;</P>
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select archive file</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Archive file to scan for projects to import.
-Type in the full path or Browse to select the archive on the file system.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;disabled&gt;</P>
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Check all of the projects that were found for import.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Deselect All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Uncheck all projects.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Refresh</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Rescan the selected source for projects to import.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</TR>
-
-</TBODY>
-</TABLE>
-</DIV>
-
-
-<DIV CLASS="Topic">
-<h2>
-External Features</h2>
-<p CLASS="Head">
-Create projects from external features. Note that this wizard should only 
-be used for feature-based launching.</p>
-
-<P>&nbsp;<img src="../images/Image264_external_feature.png" 
-     alt="External Feature import wizard page" width="427" height="323"  border="0" > 
-  </P>
-<P>&nbsp;
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-Import - External Feature Options</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Choose from features in the target platform</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Scan the target platform for external features to import.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;checked&gt;</P>
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Feature Location</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The install location to search for features.  It defaults to the target
-platform.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;disabled&gt;</P>
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Import as binary project</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Import the feature as a binary project.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;checked&gt;</P>
-</TD>
-</TR>
-
-
-
-</TBODY>
-</TABLE>
-</DIV>
-
-
-
-<DIV CLASS="Topic">
-<h2>
-External Plug-ins and Fragments</h2>
-<p CLASS="Head">
-Create projects from external plug-ins and fragments.</p>
-
-<!-- PWDOC need new screenshot of import  plug-ins and fragments wizard -->
-  <P>&nbsp;<img src="../images/Image264_plugins_fragments.png" 
-     alt="External Plug-ins and Fragments import wizard page" width="566" height="565" border="0" > 
-  </P>
-<P>&nbsp;
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-Import - External Plug-ins and Fragments Options</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-
-<tr>
-<td rowspan="1" colspan="3" valign="top" align="left">
-<P CLASS="Para"><b>Import From (category)</b></P>
-</td>
-</tr>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Target Platform</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The target platform (as specified in the Preferences).</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;checked&gt;</P>
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Plug-in Location</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The install location to search for plug-ins and fragments.  It defaults to 
-the target platform.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;disabled&gt;</P>
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Source Code Locations</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Locations to be searched for library JARs source attachments.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Environment Variables</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Variables in library paths are resolved as specified in the
-Preferences.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</TR>
-
-<tr>
-<td rowspan="1" colspan="3" valign="top" align="left">
-<P CLASS="Para"><b>Import As (category)</b></P>
-</td>
-</tr>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Binary projects</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para"> &nbsp;Import into the workspace but do not expand contents</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Binary projects with linked content</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para"> &nbsp;Only link to the external files</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;checked&gt;</P>
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Projects with source folders</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para"> &nbsp;Extract the contents to source files</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</TR>
-
-
-</TBODY>
-</TABLE>
-</DIV>
-
-
-<DIV CLASS="Topic">
-<h2>
-File System</h2>
-<p CLASS="Head">
-If you choose this option, you will import files from the file system.</p>
-  <p CLASS="Head"> <img src="../images/Image262_import_file.png" alt="Import file system page" border="0" ></p>
-<p CLASS="Head">&nbsp;
-</p>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-Import - File System Options</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Directory</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The directory from which to import files.&nbsp; Select a previous path from the
-drop down combo or Browse to select the path in the file system.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;blank&gt;</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Filter Types</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Dialog to select which file types to import.&nbsp; Use this to
-restrict the import to only certain file types.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Check off all files and folders for import.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Deselect All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Uncheck all resources.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-<TD COLSPAN="1">
-Folder
-</TD>
-<TD COLSPAN="1">
-The folder into which the resources will be imported.&nbsp; Type the path or
-Browse to select a path in the Workbench.
-</TD>
-<TD COLSPAN="1">
-The folder holding the selected resource&nbsp;
-</TD>
-</TR>
-<TR>
-<TD COLSPAN="1">
-Overwrite existing resources without warning
-</TD>
-<TD COLSPAN="1">
-Determines whether importing a resource should silently overwrite a resource
-which already exists in the Workbench. If this option is off, you will be
-prompted before a given resource is overwritten, in which case you can either
-overwrite the resource, skip it, or cancel the import.
-</TD>
-<TD COLSPAN="1">
-Off
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create complete folder structure</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create hierarchy (folder) structure in the Workbench to accommodate the
-resources being imported, and all parent folders of those resources in the file system. </P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Off</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create selected folders only</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create hierarchy (folder) structure in the Workbench to accommodate the
-resources being imported. </P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">On</P>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-</DIV>
-
-
-<DIV CLASS="Topic">
-<h2>
-Preferences</h2>
-<p CLASS="Head">
-Import preferences from the local file system.</p>
-<!-- PWDOC need a new screenshot for the Import preferences wizard -->
-  <p CLASS="Head"> <img src="../images/Image262_import_preferences.png" 
-   alt="Import Preferences wizard page" width="431" height="491" border="0" ></p>
-<p CLASS="Head">&nbsp;
-</p>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-Import - Preferences Options</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-From preference file</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The file from which to import preferences.&nbsp; Select a previous file from the
-drop down combo or Browse to select the file in the file system.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;blank&gt;</P>
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Import All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Import all of the preferences.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;checked&gt;</P>
-</TD>
-</TR>
-
-<TR>
-<TD COLSPAN="1">
-<P CLASS="Para">
-Choose specific preferences to import</P>
-</TD>
-<TD COLSPAN="1">
-<P CLASS="Para">
-Choose from the preferences contained in the file, like CVS connection 
-preferences or JRE preferences.</P>
-</TD>
-<TD COLSPAN="1">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</TR>
-
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Check off all files and folders for import.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Deselect All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Uncheck all resources.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-
-
-</TBODY>
-</TABLE>
-</DIV>
-
-
-<DIV CLASS="Topic">
-<h2>
-Team Project Set</h2>
-<p CLASS="Head">
-Imports a description of the repository and version control information for a set of projects.
-This allows you to synchronize correctly with the appropriate project state in your repository.
-</p>
-  <P>&nbsp;<img src="../images/Image265_team_project.png" alt="Team project set import wizard page" border="0" > 
-  </P>
-<P>&nbsp;
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-Import - Team Project Options</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-File name</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The name of the team project set export file</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;blank&gt;</P>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-</DIV>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-71.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-71.htm
deleted file mode 100644
index adc1159..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-71.htm
+++ /dev/null

@@ -1,1431 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Export wizard</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Export wizard</H1>
-<P CLASS="Para">
-This wizard help you export resources from the Workbench.</P>
-<P CLASS="Para">
-When the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Export wizard</b></a>
-first comes up, you must choose what type of export to
-do:</P>
-<P CLASS="Para"> <img src="../images/Image264_export_sel.png" alt="Export selection page" border="0"></P>
-
-
-<DIV CLASS="Topic">
-  <h2>Ant Buildfiles</h2>
-  <p CLASS="Head">Generates Ant buildfiles based on the configuration 
-     of the Java projects.</p>
-     <P>&nbsp;<img src="../images/Image266_export_ant.png" 
-     alt="ant buildfile export"  border="0"> </P>
-<P>&nbsp;
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-    Export - Ant Buildfiles Options 
-    </CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select the projects to use to generate the buildfiles</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The project (and resources within that project) to use to generate the 
-buildfiles.&nbsp;</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Java projects selected.</P>
-</TD>
-</tr>
-
-
-</TBODY>
-</TABLE>
-</DIV> 
-<DIV CLASS="Topic">
-  <h2> Archive File</h2>
-  <p CLASS="Head"> If you choose this option, you will export files to an archive 
-    file.</p>
-  <P>&nbsp;<img src="../images/Image266_export_zip.png" alt="ZIP file export" border="0"> 
-  </P>
-<P>&nbsp;
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-    Export - Archive File Options 
-    </CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select resources to export</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The project (and resources within that project) to export to an archive.&nbsp;</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The project holding the selected resource</P>
-</TD>
-</tr>
-<TR>
-<TD COLSPAN="1">
-<P CLASS="Para">
-Select Types...</P>
-</TD>
-<TD COLSPAN="1">
-<P CLASS="Para"> Dialog to select which file types to export.&nbsp; Use this to 
-            restrict the export to only certain file types.</P>
-</TD>
-<TD COLSPAN="1">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Check off all resources for export.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Deselect All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Uncheck all resources.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-        <TD COLSPAN="1"> Archive File </TD>
-<TD COLSPAN="1">
-The path and name of an archive file into which the resources will be exported.&nbsp; Type the path,
-select a previous path from the drop down list, or Browse to select a path and file name on the file system.
-</TD>
-        <TD COLSPAN="1"> The archive file of the previous export, or &lt;blank&gt;. 
-        </TD>
-</TR>
-<TR>
-<TD COLSPAN="1">
-Compress the contents of the file
-</TD>
-<TD COLSPAN="1">
-Compresses the contents (resources selected to be exported) in the archive that
-is created.
-</TD>
-<TD COLSPAN="1">
-On
-</TD>
-</TR>
-<TR>
-<TD COLSPAN="1">
-Overwrite existing file without warning
-</TD>
-<TD COLSPAN="1">
-If the specified archive already exists in the file system, you will be prompted
-to overwrite the file.&nbsp; If you do not want to be prompted turn this option
-on.
-</TD>
-<TD COLSPAN="1">
-Off
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create directory structure for files</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create hierarchy (folder) structure in the file system as it exists in the Workbench. </P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Off</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create only selected directories</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create hierarchy (folder) structure in the file system only for selected folders. </P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">On</P>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-</DIV>
-
-
-<DIV CLASS="Topic"> 
-  <h2>Deployable Features</h2>
-  <p CLASS="Head">Export the selected features in a form suitable for 
-     deploying in an Eclipse product.</p>
-     
-  <P>&nbsp;<img src="../images/Image266_export_feature.png" 
-    alt="Deployable feature export"  border="0"> </P>
-<P>&nbsp;
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-    Export - Deployable Feature Options 
-    </CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Available Features</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The features in your workspace available for export.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Features selected.</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select all of the features listed.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Deselect All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Clear all of the features listed.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Working Set</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select a defined working set of features.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</tr>
-
-<tr>
-<td rowspan="1" colspan="3" valign="top" align="left">
-<P CLASS="Para"><b>Export Destination </b></P>
-</td>
-</tr>
-
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Archive File</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Export to this archive file.  Type the file, select a previous export file
-from the drop down list, or Browse to select a file.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;blank&gt;</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Directory</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Export to this directory on the file system.
-Type the path, select a previous export path
-from the drop down list, or Browse to select a path.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;disabled&gt;</P>
-</TD>
-</tr>
-
-<tr>
-<td rowspan="1" colspan="3" valign="top" align="left">
-<P CLASS="Para"><b>Compiler Options </b></P>
-</td>
-</tr>
-
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Source Compatibility</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The Java source compatibility level.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;1.3&gt;</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Generated .class files compatibility</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The Java binary compatibility level.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;1.2&gt;</P>
-</TD>
-</tr>
-
-<tr>
-<td rowspan="1" colspan="3" valign="top" align="left">
-<P CLASS="Para"><b>Export Options </b></P>
-</td>
-</tr>
-
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Include source code</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Include the source code in the deployed feature.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;unchecked&gt;</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Package features as individual JAR archives</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Package features and plug-ins as individual JAR archives.  This is required
-for JNLP and update sites.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;unchecked&gt;</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Save as Ant script</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Generate an ant script to allow command line builds.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;unchecked&gt;</P>
-</TD>
-</tr>
-
-</TBODY>
-</TABLE>
-</DIV> 
-<DIV CLASS="Topic"> 
-  <h2>Deployable Plug-ins and Fragments</h2>
-  <p CLASS="Head">Export the selected plug-ins and/or fragments in a 
-  form suitable for deploying in an Eclipse product.</p>
-     
-  <P>&nbsp;<img src="../images/Image266_export_feature.png" 
-    alt="Deployable Plug-ins export"  border="0"> </P>
-<P>&nbsp;
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-    Export - Deployable Plug-ins and Fragments Options 
-    </CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Available Plug-ins and Fragments</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The plug-ins and fragments in your workspace available for export.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Plug-ins selected.</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select all of the plug-ins listed.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Deselect All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Clear all of the plug-ins listed.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Working Set</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select a defined working set of plug-ins.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</tr>
-
-<tr>
-<td rowspan="1" colspan="3" valign="top" align="left">
-<P CLASS="Para"><b>Export Destination </b></P>
-</td>
-</tr>
-
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Archive File</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Export to this archive file.  Type the file, select a previous export file
-from the drop down list, or Browse to select a file.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;blank&gt;</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Directory</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Export to this directory on the file system.
-Type the path, select a previous export path
-from the drop down list, or Browse to select a path.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;disabled&gt;</P>
-</TD>
-</tr>
-
-<tr>
-<td rowspan="1" colspan="3" valign="top" align="left">
-<P CLASS="Para"><b>Compiler Options </b></P>
-</td>
-</tr>
-
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Source Compatibility</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The Java source compatibility level.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;1.3&gt;</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Generated .class files compatibility</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The Java binary compatibility level.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;1.2&gt;</P>
-</TD>
-</tr>
-
-<tr>
-<td rowspan="1" colspan="3" valign="top" align="left">
-<P CLASS="Para"><b>Export Options </b></P>
-</td>
-</tr>
-
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Include source code</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Include the source code in the deployed feature.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;unchecked&gt;</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Package plug-ins as individual JAR archives</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Package plug-ins and fragments as individual JAR archives.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;unchecked&gt;</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Save as Ant script</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Generate an ant script to allow command line builds.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;unchecked&gt;</P>
-</TD>
-</tr>
-
-</TBODY>
-</TABLE>
-</DIV> 
-<DIV CLASS="Topic"> 
-  <h2>Eclipse Product</h2>
-  <p CLASS="Head">Export an Eclipse product.</p>
-     
-  <P>&nbsp;<img src="../images/Image266_export_product.png" 
-    alt="Eclipse product export" border="0"> </P>
-<P>&nbsp;
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-    Export - Eclipse Product Options 
-    </CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-
-<tr>
-<td rowspan="1" colspan="3" valign="top" align="left">
-<P CLASS="Para"><b>Product Configuration </b></P>
-</td>
-</tr>
-
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Configuration</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The configuration to create the product. Type the configuration, 
-select a previous configuration from the drop down list, or Browse to 
-select a configuration.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;blank&gt;</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Root directory</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;  </P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<b>eclipse</b></P>
-</TD>
-</tr>
-
-<tr>
-<td rowspan="1" colspan="3" valign="top" align="left">
-<P CLASS="Para"><b>Synchronization </b></P>
-</td>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Synchronize before exporting</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Synchronization of the product configuration with the product's
-defining plug-in ensures that the plug-in does not contain stale
-data.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;checked&gt;</P>
-</TD>
-</tr>
-
-<tr>
-<td rowspan="1" colspan="3" valign="top" align="left">
-<P CLASS="Para"><b>Export Destination </b></P>
-</td>
-</tr>
-
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Archive File</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Export to this archive file.  Type the file, select a previous export file
-from the drop down list, or Browse to select a file.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;blank&gt;</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Directory</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Export to this directory on the file system.
-Type the path, select a previous export path
-from the drop down list, or Browse to select a path.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;disabled&gt;</P>
-</TD>
-</tr>
-
-<tr>
-<td rowspan="1" colspan="3" valign="top" align="left">
-<P CLASS="Para"><b>Compiler Options </b></P>
-</td>
-</tr>
-
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Source Compatibility</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The Java source compatibility level.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;1.3&gt;</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Generated .class files compatibility</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The Java binary compatibility level.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;1.2&gt;</P>
-</TD>
-</tr>
-
-<tr>
-<td rowspan="1" colspan="3" valign="top" align="left">
-<P CLASS="Para"><b>Export Options </b></P>
-</td>
-</tr>
-
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Include source code</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Include the source code.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;unchecked&gt;</P>
-</TD>
-</tr>
-
-
-</TBODY>
-</TABLE>
-</DIV> 
-<DIV CLASS="Topic">
-<h2>
-File System</h2>
-<p CLASS="Head">
-If you choose this option, you will export files to the file system.</p>
-  <p CLASS="Head"> <img src="../images/Image265_export_file.png" alt="Export file system" border="0" ></p>
-<p CLASS="Head">&nbsp;
-</p>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-Export - File System Options</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select resources to export</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The project (and resources within that project) to export to the file
-system.&nbsp;</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The project holding the selected resource</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select Types...</P>
-</TD>
-        <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">Dialog 
-            to select which file types to export.&nbsp; Use this to restrict the 
-            export to only certain file types.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Checks off all resources for export.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Deselect All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Uncheck all resources.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-<TD COLSPAN="1">
-Directory
-</TD>
-<TD COLSPAN="1">
-The directory on the file system into which the resources will be exported.&nbsp; Type the path,
-select a previous export path from the drop down list, or Browse to select a path.
-</TD>
-<TD COLSPAN="1">
-The directory of the last export, or &lt;blank&gt;
-</TD>
-</TR>
-<TR>
-<TD COLSPAN="1">
-Overwrite existing files without warning
-</TD>
-<TD COLSPAN="1">
-Determines whether exporting a resource should silently overwrite a resource
-which already exists in the file system. If this option is off, you will be
-prompted before a given file is overwritten, in which case you can either
-overwrite the file, skip it, or cancel the export.
-</TD>
-<TD COLSPAN="1">
-Off
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create directory structure for files</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create hierarchy (folder) structure in the file system as it exists in the Workbench. </P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Off</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create only selected directories</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create hierarchy (folder) structure in the file system only for selected folders. </P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">On</P>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-</DIV>
-
-
-
-<DIV CLASS="Topic">
-<h2>
-Jar File</h2>
-<p CLASS="Head">
-If you choose this option, you will export files to an JAR file.</p>
-  <p CLASS="Head"> <img src="../images/Image267_export_jar.png" alt="Export JAR page" border="0" ></p>
-<p CLASS="Head">&nbsp;
-</p>
-
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-Export - JAR File Options</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select packages to export</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The project (and packages within that project) to export to a JAR file.&nbsp;</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The project holding the selected resource</P>
-</TD>
-</tr>
-<TR>
-<TD COLSPAN="1">
-<P CLASS="Para">
-Export generated class files and resources</P>
-</TD>
-<TD COLSPAN="1">
-<P CLASS="Para">
-Export the generated bytecodes (.class files) and resource files contained
-in the selected packages and projects.</P>
-</TD>
-<TD COLSPAN="1">
-<P CLASS="Para">
-On</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Export java source files and resources</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Export the java source files (.java) and resource files
-contained in the selected packages and projects.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Off</P>
-</TD>
-</TR>
-<TR>
-<TD COLSPAN="1">
-Jar File
-</TD>
-<TD COLSPAN="1">
-The path and name of a JAR file into which the resources will be exported.&nbsp; Type the path or
-Browse to select a path and file name on the file system.
-</TD>
-<TD COLSPAN="1">
-The JAR file of the previous export, or &lt;blank&gt;.
-</TD>
-</TR>
-<tr>
-<TD COLSPAN="1">
-Compress the contents of the JAR file
-</TD>
-<TD COLSPAN="1">
-Compresses the contents (resources selected to be exported) in the JAR file that
-is created.
-</TD>
-<TD COLSPAN="1">
-On
-</TD>
-</tr>
-<tr>
-<TD COLSPAN="1">
-Overwrite existing files without warning
-</TD>
-<TD COLSPAN="1">
-<p>If the specified JAR file already exists on the file system, you will be
-prompted to overwrite the file.&nbsp; If you do not want to be prompted turn
-this option on.</p>
-</TD>
-<TD COLSPAN="1">
-Off
-</TD>
-</tr>
-</TBODY>
-</TABLE>
-</DIV>
-
-
-
-<DIV CLASS="Topic"> 
-  <h2>Javadoc</h2>
-  <p CLASS="Head">Generate Javadocs</p>
-    
-  <P>&nbsp;<img src="../images/Image266_export_javadoc.png" 
-    alt="Generate Javadoc export"  border="0"> </P>
-<P>&nbsp;
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-    Export - Generate Javadoc Options 
-    </CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select types for which Javadoc will be generated</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-In the list, check or clear the boxes to specify exactly the types that you 
-want to export to the JAR file. This list is initialized by the workbench 
-selection. Only one project can be selected at once as only one project's 
-classpath can be used at a time when running the Javadoc tool.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create Javadoc for members with visibility</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para"></p><ul>
-<li><b>Private</b>: All members will be documented</li>
-<li><b>Package</b>: Only members with default, protected or public visibility 
-will be documented</li>
-<li><b>Protected</b>: Only members with protected or public visibility will 
-be documented</li>
-<li><b>Public</b>: Only members with public visibility will be documented (default)</li>
-</ul><p></p>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Use Standard Doclet</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Start the Javadoc command with the standard doclet (default)</p>
-<ul>
-<li><b>Destination</b>: select the destination to which the standard doclet 
-will write the generated documentation. The destination is a doclet specific 
-argument, and therefore not enabled when using a custom doclet.</li>
-</ul>
-<p></P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Use Custom Doclet</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
- Use a custom doclet to generate documentation</p>
- <ul>
-<li><b>Doclet name</b>: Qualified type name of the doclet</li>
-<li><b>Doclet class path</b>: Classpath needed by the doclet class</li>
-</ul>
-<p></P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</tr>
-
-
-</TBODY>
-</TABLE>
-</DIV> 
-<DIV CLASS="Topic"> 
-  <h2>Preferences</h2>
-  <p CLASS="Head">Export preferences to the local file system.</p>
-     <P>&nbsp;<img src="../images/Image266_export_preferences.png" 
-     alt="Preferences export wizard" width="470" height="550" border="0"> </P>
-<P>&nbsp;
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-    Export - Preference Options 
-    </CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Export All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Export all of the preferences in this session.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;checked&gt;</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Choose specific preferences to export</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select preferences from this session to export, like
-CVS repository preferences.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;disabled&gt;</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select all of the available preferences.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Deselect All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Clear all of the available preferences.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-To preference file</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-A file on the file system to store the preferences.
-Type the file, select a previous export file
-from the drop down list, or Browse to select a file.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;blank&gt;</P>
-</TD>
-</tr>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Overwrite existing files without warning</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Overwrite a pre-existing file.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;unchecked&gt;</P>
-</TD>
-</tr>
-
-
-</TBODY>
-</TABLE>
-</DIV> 
-<DIV CLASS="Topic">
-<h2>
-Team Project Set</h2>
-<p CLASS="Head">
-Exports a description of the repository and version control information for a set of projects.
-This allows you to synchronize those projects correctly in a different workspace.
-</p>
-  <p CLASS="Head"> <img src="../images/Image268_export_team.png" alt="Export team project set page" border="0" ></p>
-<p CLASS="Head">&nbsp;
-</p>
-
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-Export - Team Project Set Options</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select projects</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The project(s) to export to the team project set file.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The selected projects</P>
-</TD>
-</TR>
-<TR>
-<TD COLSPAN="1">
-<P CLASS="Para">
-File name</P>
-</TD>
-<TD COLSPAN="1">
-<P CLASS="Para">
-The path and name of the file to export to.</P>
-</TD>
-<TD COLSPAN="1">
-<P CLASS="Para">
-&lt;blank&gt;</P>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-</DIV>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-72.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-72.htm
deleted file mode 100644
index b15346f..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-72.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta http-equiv="Content-Style-Type" content="text/css">
-   <title>Preferences</title>
-<link REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body bgcolor="#FFFFFF">
-
-<h1 CLASS="Head">
-Preferences</h1>
-
-<p CLASS="Para">The Preferences dialog is the dialog used to set user preferences. 
-  The Preferences dialog pages can be searched using the filter function. To filter 
-  by matching the page title, simply type the name of the page you are seeking 
-  and the available pages will be presented below. The filter also searches on 
-  keywords such as appearance and java. The history controls allow you to navigate 
-  through previously viewed pages. To step back or forward several pages at a 
-  time, click the drop down arrow and a list of the most recently viewed preference 
-  pages will appear.</p> 
-<p CLASS="Para">The Preferences dialog can be found from the main workbench <b>Window</b> 
-  menu under
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workbench)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Window &gt; Preferences</b></a>.
-  Preference pages contributed by plug-ins 
-  will be found in this dialog.</p> 
-<p CLASS="Para">Here is what the preferences dialog looks like:</p> 
-<p><img src="../images/Image217_pref_wb.png" alt="Preference dialog" border="0" ></p>
-
-<P><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-23.htm">Workbench window layout</a>
-</P>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-8.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-8.htm
deleted file mode 100644
index ba8b6af..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-8.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Crash recovery</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Crash recovery</H1>
-<P CLASS="Intro">
-
-The Workbench periodically saves a snapshot in order to reduce the risk of
-losing data due to crashes.</p>
-<UL CLASS="UnorderedList">
-<LI CLASS="Item">
-Saved data is never lost as it is written to disk immediately (upon save). </LI>
-<LI CLASS="Item">
-Unsaved data in open editors may be lost, depending on the editor implementation.  </LI>
-<LI CLASS="Item">
-Bookmarks and tasks might be lost.  </LI>
-<LI CLASS="Item">
-If a crash occurs during CVS synchronization, the Workbench may be out of sync.
-You can check by performing the synchronize operation again. </LI>
-<LI CLASS="Item">
-Previously-created projects are never lost.</LI>
-</UL>
-<p>Developers of plug-ins can also choose to participate in this lifecycle and save
-the state of their plug-ins.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-9.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-9.htm
deleted file mode 100644
index 27d3955..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-9.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">

-<html>

-<head>

-

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-

-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

-   <meta http-equiv="Content-Style-Type" content="text/css">

-   <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">

-   <title>Workspace</title>

-<link REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

-</head>

-<body bgcolor="#FFFFFF">

-

-<h1 CLASS="Head"> Workspace</h1>

-<p CLASS="Head">On the <strong>Workspace</strong> preference page, you can manage 

-  various IDE-specific workspace preferences settings in the Workbench. </p>

-

-<p CLASS="Para">The following preferences can be accessed on the Workspace page 

-  by selecting <strong>Window &gt; Preferences &gt; General &gt; Workspace</strong>. 

-  <br>

-</p>

-<table width="75%" border="1">

-  <tr> 

-    <td><strong>Option</strong></td>

-    <td><strong>Description</strong></td>

-    <td><strong>Default</strong></td>

-  </tr>

-  <tr> 

-    <td>Build automatically</td>

-    <td>If this option is turned on, then the Workbench will perform an automatic 

-      build whenever a modified resource is saved.</td>

-    <td>On</td>

-  </tr>

-  <tr> 

-    <td>Save automatically before build</td>

-    <td>If this option is selected, when a manual build is performed the Workbench 

-      will automatically save all resources that have been modified since the 

-      last build was performed.<br></td>

-    <td>Off<br></td>

-  </tr>

-  <tr> 

-    <td>Workspace save interval (in minutes) </td>

-    <td>This number indicates how often the state of the workspace is automatically 

-      saved to disk.</td>

-    <td>5</td>

-  </tr>

-  <tr> 

-    <td>Refresh automatically</td>

-    <td><p>If this option is turned on then the workspace resources will be synchronized 

-        with their corresponding resources in the file system automatically.</p>

-      <p><strong>Note</strong>: This can potentially be a lengthy operation depending 

-        on the number of resources you have in your workspace. </p></td>

-    <td>Off </td>

-  </tr>

-</table>

-<p>Here is what the <strong>Workspace</strong> preferences page looks like:</p> 

-<p><img src="../images/Image209_workspace.png" alt="Preference dialog" border="0" ></p>

-

-

-</body>

-</html>


diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-activites.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-activites.htm
deleted file mode 100644
index dd7aa8c..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-activites.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Activities Editor Pages</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Activities Editor Pages</h2>
-<P CLASS="Para">The activities editor consists of three pages, the Viewers Page, 
-  the Descriptions Page and the &quot;activities.xml&quot; Page.</P>
-<P CLASS="Para"> <strong>Viewers Page</strong></P>
-<P CLASS="Para">The viewers page has two separate viewers, one viewer is for the 
-  plug-ins and fragments, and the other viewer is for the categories and activities, 
-  as well as plug-ins and fragments. </P>
-<P CLASS="Para">The first viewer displays all the plug-ins and fragments located 
-  in Eclipse's workspace directory. The second viewer displays the categories, 
-  the activities bound to categories and the plug-ins bound to activities. The 
-  latter items are also initially read from Eclipse's workspace directory. <br>
-</P>
-<p><img src="../images/viewer.png" alt="Image of Viewers page" border="0" ></p>
-<p><strong>Descriptions Page</strong></p>
-<p> Categories and activities are defined by mandatory IDs, names and optional 
-  descriptions. The descriptions page has two viewers, one which allows for the 
-  modification of categories' descriptions and the other of activities' descriptions. 
-</p>
-<p>The first viewer displays the categories, their respective ID, name and the 
-  editable description field. The second viewer shows the same information for 
-  the current activities. When the editor switches to another page, the descriptions 
-  are then updated in the &quot;activities.xml&quot; file. <br>
-</p>
-<p><img src="../images/description.png" alt="Image of Descriptions page" border="0" ></p>
-
-<p><strong>&quot;activities.xml&quot; Page</strong></p>
-<p> When the &quot;activities.xml&quot; page tab is clicked it updates automatically. 
-  The file will contain the category, activity, and binding definitions represented 
-  in the viewers' page. </p>
-<p><img src="../images/xml.png" alt="Image of activities.xml page" border="0" ></p>
-
-<p><strong>Generated Format </strong> </p>
-<p>Activity pattern bindings are created when plug-ins are added to an activity. 
-  The patterns follow a syntax similar to the following example: &quot;org\.eclipse\.pde/.*&quot; 
-  for the plug-in &quot;org.eclipse.pde&quot;. If all the plug-ins starting with 
-  &quot;org.eclipse.pde&quot; have been added to the same activity, the individual 
-  plug-ins patterns are replaced with &quot;org\.eclipse\.pde\..*/.*&quot;. Similarly, 
-  on removal of a plug-in from an activity where the latter pattern is defined, 
-  the pattern will be replaced by the patterns of the plug-ins remaining in that 
-  activity. The activity editor will read activity pattern bindings on start up 
-  from defined &quot;org.eclipse.activities&quot; extensions defined in other 
-  plug-ins if and only if they follow the syntax described above.</P>
-<p>A unique ID is generated when an activity is created. The ID has the following 
-  format: &quot;activityName&quot; + Activity, where the activity name has been 
-  stripped from spaces, and converted to lower case. A unique ID is generated 
-  when a category is created. The ID will have the following format: &quot;categoryName&quot; 
-  + Category, where the category name has been stripped from spaces, and converted 
-  to lower case. </P>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-  <a href="../concepts/concepts-activites.htm">Activities</a></p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-  <a href="../tasks/tasks-activites.htm">Activities Example</a></p> 
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-activitiespref.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-activitiespref.htm
deleted file mode 100644
index 8afc0b5..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-activitiespref.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Capabilities</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Capabilities</h2>
-<P CLASS="Para">The Capabilities preference page allows you to enable or disable 
-  various product components such as Java development and plug-in development. By 
-  default, the page only shows general categories of behavior.  If you would like
-  configure fine-grained capabilities you should use the &quot;Advanced&quot; dialog.</P>
-<P CLASS="Para"><strong>Note:</strong> Some capability selections have dependencies 
-  on other capabilities, disabling a required capability while leaving dependant 
-  capabilities enabled will only result in them becoming re-enabled. This is the 
-  case when deselecting Java Development and Core Team Support.</P>
-<P CLASS="Para">Here is what the Capabilities preference page looks like: </P>
-
-<p><img src="../images/cap-pref.png" alt="Image of Capabilities Preference page" border="0" ></p>
-
-<P CLASS="Para">The advanced dialog appears as follows:</P>
-<p><img src="../images/cap-pref-advanced.png" alt="Image of advanced Capabilities Preference page dialog"></p>
-
-<p>When attempting to enable an action after its capability has been disabled 
-  or has yet to be enabled in the preferences page, the following <strong>Confirm 
-  Enablement </strong>prompt will appear verifying that you do indeed want to 
-  enable the required capability. Click <strong>Details</strong> to display a 
-  description of the capability.</p>
-  
-<p><img src="../images/cap-conf.png" alt="Image of Confirm Enablement prompt" border="0" ></p>
-
-<P CLASS="Para"><strong>Note:</strong> This dialog only appears if the 
-  "Prompt when enabling capabilities" preference has not been disabled.</P>
-  
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-antcodeassist.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-antcodeassist.htm
deleted file mode 100644
index a4f93cf..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-antcodeassist.htm
+++ /dev/null

@@ -1,95 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Ant Code Assist</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Ant Code Assist</H1>
-<div class="Para">
-  <p>The following preferences can be changed on the Ant Code Assist preference 
-    page.</p>
-</div>
-<table border="1" cellspacing="0" style="width: 100%;">
-  <caption>
-  </caption>
-  <thead>
-  </thead>
-  <tbody>
-  </tbody>
-  <tbody>
-    <tr> 
-      <th width="25%"> <div class="Para">Option</div></th>
-      <th> <div class="Para">Description</div></th>
-      <th> <div class="Para">Default</div></th>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Insert single 
-          proposals automatically<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option allows you 
-          to automatically insert single proposals. </div></td>
-      <td align="left" valign="top"> <div class="Para">On</div></td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Provide proposals for user 
-        defined tasks (may lock referenced JAR files)<br> </td>
-      <td style="vertical-align: top;">This option allows you to provide proposals 
-        for user defined tasks. <br> </td>
-      <td style="vertical-align: top;">On<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Enable auto activation</td>
-      <td style="vertical-align: top;">This option enables and disables auto activation.<br> 
-      </td>
-      <td style="vertical-align: top;">On<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Auto activation delay<br> </td>
-      <td style="vertical-align: top;">This option allows you to set the auto 
-        activation delay.<br> </td>
-      <td style="vertical-align: top;">500<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Auto activation triggers<br> 
-      </td>
-      <td style="vertical-align: top;">This option allows you to set the auto 
-        activation triggers.<br> </td>
-      <td style="vertical-align: top;">&lt;${<br> </td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Code assist 
-          color options<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option allows you 
-          to set the color for the completion proposal background and foreground.<br>
-        </div></td>
-      <td align="left" valign="top"> <br> </td>
-    </tr>
-  </tbody>
-</table>
-
-<P CLASS="Para">Here is what the Ant Code Assist preference page looks like.</P>
-<P CLASS="Para">
-<img src="../images/ant_code_assist.png" alt="Ant Code Assist preference page" border="0"></P>
-
-<P CLASS="Para"> <img border="0" src="../images/ngrelc.png" alt="Related concepts" > 
-  <br>
-  <a href="../concepts/concepts-antsupport.htm">Ant support</a> </P>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="ref-anteditor.htm">Ant Editor</a><br>
-<a href="../reference/ref-antprefs.htm">Ant preferences</a><br>
-<a href="../reference/ref-antruntimeprefs.htm">Ant runtime preferences</a>
-
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-anteditor.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-anteditor.htm
deleted file mode 100644
index c889a28..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-anteditor.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-         
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-         
-  <meta http-equiv="Content-Style-Type" content="text/css">
-          
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>Ant editor</title>
-    
-</head>
- <body bgcolor="#ffffff">
-     
-<h1> Ant editor</h1>
-     
-<p class="Para">The Ant editor provides specialized features for editor Ant buildfiles. 
-Associated with the editor is a Ant buildfile specific Outline view which shows the structure of the Ant build file. 
-It is updated as the user edits the buildfile</p>
-
-The editor includes the following features:
-
-<ul>
-      <li>Syntax highlighting</li>
-
-      <li>Content/code assist (including Ant specific templates)</li>
-
-      <li>Annotations</li>
-    </ul>
-
-    
-<p>The most common way to invoke the Ant editor is to open an Ant buildfile from 
-  one of the navigation views or Package explorer using pop-up menus or by clicking 
-  the file (single or double-click depending on the user preferences).</p>
-     
-        
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"
- >
-  <br>
-     <a href="../concepts/concepts-antsupport.htm">Ant support</a><br>
-     <a href="../concepts/concepts-exttools.htm">External tools</a></p>
-     
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"
- ><br>
-<a href="../tasks/tasks-ant-running.htm">Running Ant buildfiles</a><br>
-<a href="../tasks/tasks-ant-classpath.htm">Modifying the Ant classpath</a><br>
-<a href="../tasks/tasks-ant-addtasksandtypes.htm">Adding new Ant tasks and types</a><br>
-<a href="../tasks/tasks-ant-version.htm">Using a different version of Ant</a></p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- >
-  <br>
-     <a href="ref-anteditorprefs.htm">Ant editor preferences</a><br>
-     <a href="ref-anticons.htm">External Tools and Ant icons</a>
-   </p>
-          
-
-      
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-anteditorprefs.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-anteditorprefs.htm
deleted file mode 100644
index 66acae1..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-anteditorprefs.htm
+++ /dev/null

@@ -1,101 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Ant Editor</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Ant Editor</H1>
-<div class="Para">The following preferences can be changed on the Ant Editor page.</div>
-<h2>Appearance options</h2>
-<table border="1" cellspacing="0" style="width: 100%;">
-  <caption>
-  </caption>
-  <thead>
-  </thead>
-  <tbody>
-  </tbody>
-  <tbody>
-    <tr> 
-      <th width="25%"> <div class="Para">Option</div></th>
-      <th> <div class="Para">Description</div></th>
-      <th> <div class="Para">Default</div></th>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Mark occurrences 
-          of the selected element in the current buildfile<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option allows you 
-          to select elements and mark occurrences in the current buildfile. </div></td>
-      <td align="left" valign="top"> <div class="Para">Off</div></td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Keep marks when selection changes<br> 
-      </td>
-      <td style="vertical-align: top;">This option allows you to keep marks when 
-        the selection changes. <br> </td>
-      <td style="vertical-align: top;">On<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Insert spaces for tabs when 
-        typing<br> </td>
-      <td style="vertical-align: top;">This option controls whether a tab is replaced 
-        with spaces when typed in the Ant editor.<br> </td>
-      <td style="vertical-align: top;">Off<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Show affordance in hover on 
-        how to make it sticky</td>
-      <td style="vertical-align: top;">This option controls whether or not the 
-        hover will display affordance on to make it sticky.<br> </td>
-      <td style="vertical-align: top;">On<br> </td>
-    </tr>
-  </tbody>
-</table>
-<P CLASS="Para">Here is what the Appearance tab of the Ant editor preference page 
-  looks like.</P>
-<P CLASS="Para">
-<img src="../images/ant_editor_appearance.png" alt="Ant editor appearance preference page" border="0"></P>
-
-
-<h2>Syntax options</h2>
-<p>The Foreground options located on the Syntax tab, allow you to format the font 
-  of comments, constant strings, DTD declarations, processing instructions, tags 
-  and text. The Preview pane allows you to see your changes before you apply them. 
-  Here is what the Syntax tab of the Ant editor preference page looks like.</p>
-<p><img src="../images/ant_editor_syntax.png" alt="Ant editor syntax preference page" border="0"></p>
-     
-<h2>Problems options</h2>
-<p>The Problems options allow you to ignore all buildfile problems or to specify 
-  the specific files that you do not want the Ant Editor to check for problems. 
-  You can also set the severity level for buildfile problems such as task configuration, 
-  an incomplete classpath, property setting tasks, import tasks, and security 
-  problems. Here is what the Problems tab of the Ant editor preference page looks 
-  like.</p>
-<p><img src="../images/ant_editor_problems.png" alt="Ant editor Problems preference page" border="0"></p>
-<h2>Folding options</h2>
-<p>The Folding options allow you to enable folding when opening a new editor and 
-  to specify which region types should be folded. Here is what the Folding tab 
-  of the Ant editor preference page looks like.</p>
-<p><img src="../images/ant_editor_folding.png" alt="Ant editor Folding preference page" border="0"></p>
-<P CLASS="Para"> <img border="0" src="../images/ngrelc.png" alt="Related concepts" > 
-  <br>
-  <a href="../concepts/concepts-antsupport.htm">Ant support</a> </P>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="ref-anteditor.htm">Ant Editor</a><br>
-<a href="../reference/ref-antprefs.htm">Ant preferences</a><br>
-<a href="../reference/ref-antruntimeprefs.htm">Ant runtime preferences</a>
-
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-antformatter.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-antformatter.htm
deleted file mode 100644
index e8a85e3..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-antformatter.htm
+++ /dev/null

@@ -1,82 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Ant Formatter</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Ant Formatter</H1>
-<div class="Para">
-  <p>The following preferences can be changed on the Ant Formatter preference 
-    page.</p>
-</div>
-<table border="1" cellspacing="0" style="width: 100%;">
-  <caption>
-  </caption>
-  <thead>
-  </thead>
-  <tbody>
-  </tbody>
-  <tbody>
-    <tr> 
-      <th width="25%"> <div class="Para">Option</div></th>
-      <th> <div class="Para">Description</div></th>
-      <th> <div class="Para">Default</div></th>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Indentation - Tab size<br> 
-      </td>
-      <td style="vertical-align: top;">This option controls how many spaces are 
-        used to display tabs in the Ant editor.<br> </td>
-      <td style="vertical-align: top;">4<br> </td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Line Wrapping 
-          - Maximum line width</div></td>
-      <td align="left" valign="top"> <div class="Para">This option allows you 
-          to set the maximum line width for the Ant editor. </div></td>
-      <td align="left" valign="top"> <div class="Para">80</div></td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top"> <div class="Para">Line Wrapping - Wrap long 
-          element tags</div></td>
-      <td align="left" valign="top"> <div class="Para">This option allows you 
-          to wrap long element tags. The Preview pane will display a sample buildfile 
-          with this option.</div></td>
-      <td align="left" valign="top"> <div class="Para">Off</div></td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top"> <div class="Para">Line Wrapping - Align final 
-          '&gt;' in multi-line element tags</div></td>
-      <td align="left" valign="top"> <div class="Para">This option allows you 
-          to align the final '&gt;' in multi-line element tags. The Preview pane 
-          will display a sample buildfile with this option.</div></td>
-      <td align="left" valign="top"> <div class="Para">Off</div></td>
-    </tr>
-  </tbody>
-</table>
-
-<P CLASS="Para">Here is what the Ant Formatter preference page looks like.</P>
-<P CLASS="Para">
-<img src="../images/ant_formatter.png" alt="Ant Formatter preference page" border="0"></P>
-
-<P CLASS="Para"> <img border="0" src="../images/ngrelc.png" alt="Related concepts" > 
-  <br>
-  <a href="../concepts/concepts-antsupport.htm">Ant support</a> </P>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="ref-anteditor.htm">Ant Editor</a><br>
-<a href="../reference/ref-antprefs.htm">Ant preferences</a><br>
-<a href="../reference/ref-antruntimeprefs.htm">Ant runtime preferences</a>
-
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-anticons.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-anticons.htm
deleted file mode 100644
index 9843428..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-anticons.htm
+++ /dev/null

@@ -1,270 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-  <head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      External Tools and Ant icons
-    </title>
-  </head>
-  <body>
-    <h1>
-      External Tools and Ant icons
-    </h1>
-    <h2>
-      Objects
-    </h2>
-    <table cellspacing="0" border="1" width="40%">
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/ant_buildfile.png"  alt="Ant buildfiles"><br>
-          </td>
-          <td valign="top">
-            Ant buildfiles<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/ant_target_err.png"  alt="Ant target containing an error"><br>
-          </td>
-          <td valign="top" width="90%">
-            Ant target containing an error<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/invalid_build_tool.png"  alt="Invalid project builder"><br>
-          </td>
-          <td valign="top" width="90%">
-            Invalid project builder<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/defaulttarget_obj.png"  alt="Default target"><br>
-          </td>
-          <td valign="top" width="90%">
-            Default target<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/targetpublic_obj.png"  alt="Ant target"><br>
-          </td>
-          <td valign="top" width="90%">
-            Public Ant target (target with description)<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/targetinternal_obj.png"  alt="Ant internal target"><br>
-          </td>
-          <td valign="top" width="90%">
-            Ant internal target (target with no description)<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/jar_l_obj.png"  alt="Jar file"><br>
-          </td>
-          <td valign="top" width="90%">
-            Jar file<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/property_obj.png"  alt="Ant property"><br>
-          </td>
-          <td valign="top" width="90%">
-            Ant property<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/task_obj.png"  alt="Ant task"><br>
-          </td>
-          <td valign="top" width="90%">
-            Ant task<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/type.png"  alt="Ant type"><br>
-          </td>
-          <td valign="top" width="90%">
-            Ant type<br>
-          </td>
-        </tr>
-         <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/import_obj.png"  alt="Ant import task"><br>
-          </td>
-          <td valign="top" width="90%">
-            Ant import task<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/macrodef_obj.png"  alt="Ant macrodef task"><br>
-          </td>
-          <td valign="top" width="90%">
-            Ant macrodef task<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-    <h2>
-      Launch configurations
-    </h2>
-    <table cellspacing="0" border="1" width="40%">
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/ctool16/external_tools.png"  alt="Launch external tool"><br>
-          </td>
-          <td valign="top" width="90%">
-            Launch external tool<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/ant.png"  alt="Ant launch configuration"><br>
-          </td>
-          <td valign="top">
-            Ant launch configuration<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/ctool16/external_tools.png"  alt="Program launch configuration"><br>
-          </td>
-          <td valign="top" width="90%">
-            Program launch configuration<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/main_tab.png"  alt="Main tab"><br>
-          </td>
-          <td valign="top" width="90%">
-            Main tab<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/clcl16/refresh.png"  alt="Refresh tab"><br>
-          </td>
-          <td valign="top" width="90%">
-            Refresh tab<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/build_tab.png"  alt="Build tab"><br>
-          </td>
-          <td valign="top" width="90%">
-            Build tab<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/clcl16/ant_targets.png"  alt="Targets tab"><br>
-          </td>
-          <td valign="top" width="90%">
-            Targets tab<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/prop_ps.png"  alt="Properties tab"><br>
-          </td>
-          <td valign="top" width="90%">
-            Properties tab<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/classpath.png"  alt="Classpath tab"><br>
-          </td>
-          <td valign="top" width="90%">
-            Classpath tab<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-   <br>
-    <h2>
-      Ant View
-    </h2>
-    <table cellspacing="0" border="1" width="40%">
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/cview16/ant_view.png"  alt="Ant view"><br>
-          </td>
-          <td valign="top" width="90%">
-            Ant view<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/clcl16/add_co.png"  alt="Add buildfile"><br>
-          </td>
-          <td valign="top" width="90%">
-            Add buildfile<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/clcl16/search.png"  alt="Add buildfiles with search"><br>
-          </td>
-          <td valign="top" width="90%">
-            Add buildfiles with search<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/clcl16/run_tool.png"  alt="Run selected buildfile or selected target"><br>
-          </td>
-          <td valign="top" width="90%">
-            Run selected buildfile or selected target<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/clcl16/remove_co.png"  alt="Remove selected buildfiles"><br>
-          </td>
-          <td valign="top" width="90%">
-            Remove selected buildfiles<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/clcl16/removeAll_co.png"  alt="Remove all buildfiles"><br>
-          </td>
-          <td valign="top" width="90%">
-            Remove all buildfiles<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/clcl16/properties.png"  alt="Properties"><br>
-          </td>
-          <td valign="top" width="90%">
-            Properties<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-     
-
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-antprefs.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-antprefs.htm
deleted file mode 100644
index 2d927a4..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-antprefs.htm
+++ /dev/null

@@ -1,76 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Ant</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Ant</H1>
-<P CLASS="Intro"> The following preferences can be changed on the Ant page.</p> 
-<TABLE BORDER="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Option</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Description</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Default</P></TH>
-    </TR>
-  </THEAD>
-  <TBODY>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Names</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          This option allows you to configure the buildfiles that Ant's "-find" 
-          emulation will search for.&nbsp; </P></TD>
-      <TD>build.xml </TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Warn when tools.jar is not on the classpath</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">Displays 
-          warning when tools.jar is not on the classpath.</P></TD>
-      <TD> On</TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Show error dialog when Ant build fails</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">Displays 
-          error message when the Ant build fails.</P></TD>
-      <TD> On</TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Documentation URL</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          This option allows you to browse or the applicable documentation URL</P></TD>
-      <TD> http://ant.apache.org/manual</TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Ant Color Options</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">You 
-          can also configure the color of the Ant build output. </P></TD>
-      <TD>Red</TD>
-    </TR>
-  </TBODY>
-</TABLE>
-<P CLASS="Intro"><img src="../images/ant_prefs.png" alt="Ant preference page" border="0"> </p>
-<p><img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-<br><a href="../concepts/concepts-antsupport.htm">Ant support</a>
-</p>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-antruntimeprefs.htm">Ant runtime preferences</a><br>
-<a href="../reference/ref-anteditorprefs.htm">Ant editor preferences</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-antruntimeprefs.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-antruntimeprefs.htm
deleted file mode 100644
index 7015272..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-antruntimeprefs.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Ant</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Ant Runtime</H1>
-<P CLASS="Para">
-On the classpath page you can add additional classes defining tasks and types to the Ant classpath.</P>
-<P CLASS="Para">
-<img src="../images/Image91_ant_prefs_1.png" alt="Ant classpath preference page" border="0"></P>
-
-<P CLASS="Para">
-On the tasks page you can add tasks defined in one of the classes on the classpath.</P>
-<P CLASS="Para"> <img src="../images/Image91_ant_prefs_2.png" alt="Ant tasks preference page" border="0"></P>
-
-<P CLASS="Para">
-On the types page you can add types defined in one of the classes on the classpath.</P>
-<P CLASS="Para">
-<img src="../images/Image91_ant_prefs_3.png" alt="Ant types preference page" border="0" >
-</P>
-
-<P CLASS="Para">
-On the properties page you can add properties and property files that will be passed into Ant.</P>
-<P CLASS="Para">
-<img src="../images/ant_runtime_properties.png" alt="Ant properties preference page" border="0">
-</P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br><a href="../concepts/concepts-antsupport.htm">Ant support</a>
-</p>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-antprefs.htm">Ant preferences</a><br>
-<a href="../reference/ref-anteditorprefs.htm">Ant editor preferences</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-anttemplates.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-anttemplates.htm
deleted file mode 100644
index 2bebac0..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-anttemplates.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Ant Templates</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Ant Templates</H1>
-<div class="Para">
-  <p>The Ant Templates preference page can be used to create, edit or remove templates. 
-    You can also import templates as well as restore removed templates and revert 
-    to the default templates. The preview pane allows to see what your new or 
-    edited template will look like before applying your changes.</p>
-</div>
-<P CLASS="Para">Here is what the Ant Templates preference page looks like.</P>
-<P CLASS="Para">
-<img src="../images/ant_templates.png" alt="Ant Templates preference page" border="0"></P>
-
-<P CLASS="Para"> <img border="0" src="../images/ngrelc.png" alt="Related concepts" > 
-  <br>
-  <a href="../concepts/concepts-antsupport.htm">Ant support</a> </P>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="ref-anteditor.htm">Ant Editor</a><br>
-<a href="../reference/ref-antprefs.htm">Ant preferences</a><br>
-<a href="../reference/ref-antruntimeprefs.htm">Ant runtime preferences</a>
-
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-antview.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-antview.htm
deleted file mode 100644
index 28c2ac7..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-antview.htm
+++ /dev/null

@@ -1,133 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-         
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-         
-  <meta http-equiv="Content-Style-Type" content="text/css">
-          
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>Ant view</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>    
-</head>
-
-<body bgcolor="#ffffff">
-     
-<h1> Ant view</h1>
-     
-<p class="Para">The Ant view provides a place to view Ant buildfiles and makes it
-easy to execute a buildfile or a given target within a buildfile. You can add files
-to the view and expand buildfiles to reveal the targets defined within them.</p>
-     
-<p>The pop-up menu for this view also allows you to open an editor on a
-buildfile, execute the selected target or buildfile, and configure the launch
-configuration used when executing.</p>
-     
-<p class="Para"> Here is what the Ant view looks like:</p>
-<p class="Para"> <img align="top" border="0"
- src="../images/ant-view.png" alt="Ant View" >
-  </p>
-     
-<div class="Topic">
-<p>Like other views in the Workbench, the Ant view has its own
-      toolbar. Toolbar buttons are provided for adding buildfiles to the view and for
- executing them.</p>
-<p CLASS="Head">
-To add the Ant view to the current perspective, click
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ant.ui.views.AntView)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Window &gt; Show View &gt; Other... &gt; Ant &gt; Ant</b></a>.
-</p>
-       
-<h2>Toolbar</h2>
-       
-<h3>Add Buildfiles</h3>
-     
-<p class="Para">This command prompts you to select buildfiles in the workspace to be added to the view.</p>
-   </div>
-     
-<div class="Topic">     
-<h3>Add Buildfiles with Search</h3>
-     
-<p class="Para">This command searches for buildfiles and adds them to the Ant view. You can
-specify a file name pattern to search for and limit the scope of the search.</p>
-   </div>
-
-<div class="Topic">     
-<h3>Hide Internal Targets</h3>
-     
-<p class="Para">This command filters the Ant view so that internal targets are not displayed. Internal
-targets are targets with no description.</p>
-   </div>
-     
-<div class="Topic">     
-<h3>Run the Default Target of the Selected Buildfile</h3>
-     
-<p class="Para">This command runs the default target of the selected buildfile or the selected target.
-The buildfile is executed using the launch configuration associated with the buildfile. Note that the
-target execution is based on the selection in the view; the targets selected
-in the launch configuration are ignored.</p>
-   </div>
-          
-<h3 class="Para">Remove Selected Buildfile</h3>
-     
-<p class="Para">This command removes the selected buildfiles from the view.</p>
-        
-<h3 class="Para">Remove All Buildfiles</h3>
-     
-<p class="Para">This command removes all buildfiles from the view.</p>
-
-<h2 class="Para">Context menu </h2>
-     
-<p class="Para">The context menu contains a few actions in addition to the actions
-available in the toolbar.&nbsp;&nbsp;</p>
-
-<h3>Run Ant&nbsp;</h3>
-     
-<p class="Para"> This command launches an Ant build for the selected buildfile or for a specific selected target of the buildfile</p>
-
-<h3>Run Ant...&nbsp;</h3>
-     
-<p class="Para"> This command brings up the launch configuration dialog to edit the
-configuration associated with the selected buildfile.</p>
-
-<div class="Topic">     
-<h3> Refresh Buildfiles</h3>
-     
-  <p class="Para"> This command refreshes the contents of the view to reflect the current state of all the represented buildfiles.</p>
-    </div>
-
-<h3>Open With &gt; &nbsp;</h3>
-     
-<p class="Para">This menu allows you to open an editor on the selected buildfile.</p>
-        
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"
- >
-  <br>
-     <a href="../concepts/concepts-antsupport.htm">Ant support</a><br>
-     <a href="../concepts/concepts-exttools.htm">External tools</a></p>
-     
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"
- ><br>
-<a href="../tasks/tasks-ant-running.htm">Running Ant buildfiles</a><br>
-<a href="../tasks/tasks-ant-classpath.htm">Modifying the Ant classpath</a><br>
-<a href="../tasks/tasks-ant-addtasksandtypes.htm">Adding new Ant tasks and types</a><br>
-<a href="../tasks/tasks-ant-version.htm">Using a different version of Ant</a></p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- >
-  <br>
-     <a href="ref-antruntimeprefs.htm">Ant runtime preferences</a><br>
-     <a href="ref-anteditor.htm">Ant Editor</a><br>
-     <a href="ref-anticons.htm">External Tools and Ant icons</a>
-   </p>
-          
-
-      
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-capabilities.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-capabilities.htm
deleted file mode 100644
index 69177e0..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-capabilities.htm
+++ /dev/null

@@ -1,27 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Capabilities</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Capabilities </H1>
-<P CLASS="Para"> The Capabilities preference page helps to simplify the management 
-  of capabilities in downstream products. To access the Capabilities preference 
-  page select Window &gt; Preferences &gt; General &gt; Capabilities.</P>
-<P>Here is what the Capabilities preference page looks like:&nbsp; </P>
-
-
-<P><img src="../images/capabilities.png" alt="Capabilities preference page" border="0" > 
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-cheatsheets.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-cheatsheets.htm
deleted file mode 100644
index c2d567e..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-cheatsheets.htm
+++ /dev/null

@@ -1,143 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" charset="ISO-8859-1" TYPE="text/css">
-<title>Working with cheat sheets</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Working with cheat sheets</h1>
-<P CLASS="Para">Eclipse provides cheat sheets to guide you through some of its 
-  application development processes. Each cheat sheet is designed to help you 
-  complete some task, and it lists the sequence of steps required to help you 
-  achieve that goal. As you progress from one step to the next, the cheat sheet 
-  will automatically launch the required tools for you. If there is a manual step 
-  in the process, the step will tell you to perform the task and click a button 
-  in the cheat sheet to move on to the next step. Also, relevant help information 
-  to guide you through a task is retrieved in a single click so that lengthy documentation 
-  searches will no longer be required. </P>
-<P CLASS="Para">A <a href="ref-composite-cheatsheets.htm">composite cheat sheet</a> 
-is another kind of cheat sheet that was introduced in Eclipse 3.2 and is 
-designed to provide guidance for larger tasks or a group of related tasks.</P>
-<h3>Launching a cheat sheet</h3>
-<p>There are two ways that cheat sheets can be accessed, on the Welcome page or 
-  launched from the Workbench. </p>
-<h4>Accessing a cheat sheet from the Welcome page</h4>
-<ol>
- 
-  <li>When Eclipse is first started, the Welcome page is displayed, on this page 
-    select <strong>Tutorials</strong>.<br>
-	<img src="../images/image92-tutorial.png" alt="Tutorial Icon" border="0" width="95" height="88" ></li>
-  <li> 
-    <p>Then, from the Tutorials page select a cheat sheet. </p>
-    <p>&nbsp;</p>
-    <p></p>
-  </li>
-</ol>
-<h4>Launching a cheat sheet from the Workbench</h4>
-<ol>
-  <li>To launch a cheat sheet from the Workbench, select
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.cheatsheets.openCheatSheet")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <strong>Help &gt; Cheat Sheets</strong></a> from the menu bar.
-  <br>
-  <img src="../images/image92-opencheat.png" alt="Accessing Cheat sheet via Help menu" border="0" width="155" height="157" ></li> 
-  <li>The available cheat sheets are listed, select one and click <strong>OK</strong>.</li>
-</ol>
-<p>The cheat sheet opens as a view. At any time, only one cheat sheet is open 
-  and active. When you launch a cheat sheet, any opened cheat sheet is closed 
-  before the new one is opened. The completion status of closed cheat sheet is 
-  saved.</p>
-<p>The cheat sheet has a toolbar at the top right edge. These icons appear in 
-  the toolbar:</p>
-<ul>
-  <li>
-  <img src="../images/image92-collapse.png" alt="Collapse button" border="0" width="16" height="16">Collapses 
-    all the expanded steps except the current step or expands steps to the last 
-    expanded state. Click to toggle between these two states. </li>
-  <li>
-  <img src="../images/image92-select.png" alt="Select button" border="0" width="16" height="15" >Allows 
-    you to select and open another cheat sheet. The completion status of the active 
-    cheat sheet is saved. Then, the active cheat sheet is closed and the selected 
-    cheat sheet is opened. </li>
-  <li>
-  <img src="../images/image92-hide.png" alt="Hide button" border="0" width="18" height="14" >Hides 
-    the cheat sheet. </li>
-  <li>
-  <img src="../images/image92-save.png" alt="Save button" border="0" width="15" height="16">Saves 
-    the completion status of the active cheat sheet and closes it. <br>
-  </li>
-</ul>
-<h3>Starting the cheat sheet</h3>
-<p> Each cheat sheet has a list of steps and it always begins with an Introduction 
-  step. When you launch a fresh cheat sheet, the Introduction step is expanded 
-  so that you can read a brief description of the cheat sheet. To start working 
-  with the cheat sheet, click <strong> Click to Begin</strong> <strong>
-<img src="../images/image92-begin.png" alt="Click to Begin button" border="0" width="16" height="16"> 
-  </strong>in that step. The next step is expanded and highlighted. You should 
-  also see one or more actions buttons, such as <strong>Click to Perform </strong><strong>
-<img src="../images/image92-perform.png" alt="Click to Perform button" border="0" width="16" height="16"></strong> 
-  in the highlighted step. You can now begin working through the tasks using the 
-  cheat sheet. At any time, the only highlighted step in the cheat sheet is the 
-  current step. </p>
-<h3>Restarting the cheat sheet</h3>
-<p>Any time after starting a cheat sheet, you can restart from the first step 
-  by clicking <strong>Click to Restart </strong><strong>
-<img src="../images/image92-restart.png" alt="Click to Restart button" border="0" width="16" height="16"></strong> 
-  in the Introduction step. If you have already created some artifacts, you will 
-  have to manually clean up the workspace before restarting the cheat sheet.</p>
-<h3>Progressing through the steps</h3>
-<p>In the current step, when you click <strong>Click to Perform 
-<img src="../images/image92-perform.png" alt="Click to Perform button" border="0" width="16" height="16"></strong>, 
-  a tool (which can be a wizard), will be launched and you will be required to 
-  work with that tool. When you finish working with that tool, the next step is 
-  automatically highlighted and it becomes the current step. When the current 
-  step is a manual task, you will need to perform the work and click <strong>Click 
-  to Complete </strong><strong>
-<img src="../images/image92-complete.png" alt="Click to Complete button" border="0" width="16" height="16"></strong> 
-  to move to the next step. A check mark <strong>
-<img src="../images/image92-check.png" alt="Check mark icon" border="0" width="16" height="16"></strong> 
-  appears in the left margin of each completed step.</p>
-<h3>Getting help information for tasks</h3>
-<p>To get step-by-step instructions for that step, click the help link <strong>
-<img src="../images/image92-help.png" alt="Help Link Icon" border="0" width="16" height="16"></strong> 
-  in the step before you click <strong>Click to Perform</strong> <strong>
-<img src="../images/image92-perform.png" alt="Click to Perform button" border="0" width="16" height="16"></strong>, 
-  and the step-by-step instructions on how to work with that tool will be displayed 
-  in the Help window. </p>
-<p>Additional help for entry fields in the tool or wizard may be available by 
-  focusing on the field (use the <strong>Tab</strong> key to position to that 
-  entry) and pressing <strong>F1</strong>.</p>
-<h3>Skipping a step</h3>
-<p>If a current step has a <strong>Click to Skip</strong> option<strong> 
-<img src="../images/image92-skip.png" alt="Click to Skip button" border="0" width="16" height="16"></strong>, 
-  then it is an optional step. You must click <strong>Click to Skip</strong> <strong>
-<img src="../images/image92-skip.png" alt="Click to Skip button" border="0" width="16" height="16"></strong> 
-  to skip the current step, when you do, the step will have the skip mark <strong>
-<img src="../images/image92-skip-mark.png" alt="Skip mark icon" border="0" width="16" height="16"></strong> 
-  in the left margin. If the task does not present <strong>Click to Skip</strong>, 
-  you must perform that step and you cannot skip it.</p>
-<h3>Redoing a step </h3>
-<p>You can redo any step that you may have completed or skipped in the current 
-  cheat sheet. To redo the step, expand the step by clicking its expand <strong>
-<img src="../images/image92-expand.png" alt="Expand Icon" border="0" width="19" height="19"></strong>icon 
-  and then clicking <strong>Click to Redo</strong> <strong>
-<img src="../images/image92-redo.png" alt="Click to Redo button" border="0" width="16" height="16"></strong>. 
-  After redoing a step, the cheat sheet will continue from the redo step.</p>
-<h3>Closing the cheat sheet</h3>
-<p>When you finish the last step in a cheat sheet, it automatically restarts. 
-  You can also close the active cheat sheet by clicking the close icon <strong>
-<img src="../images/image92-close.png" alt="Close icon" border="0" width="16" height="15"></strong> 
-  in the cheat sheet's toolbar. The active cheat sheet saves its completion status 
-  when it is closed so that you can continue where you left off at a later time.<br>
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-composite-cheatsheets.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-composite-cheatsheets.htm
deleted file mode 100644
index e85e394..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-composite-cheatsheets.htm
+++ /dev/null

@@ -1,100 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" charset="ISO-8859-1" TYPE="text/css">
-<title>Working with composite cheat sheets</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Working with composite cheat sheets</h1>
-<P CLASS="Para">Composite cheat sheets provide guidance through a complex 
-problem by breaking that problem into a set of smaller tasks. Each task consists 
-of a series of steps which must be performed in order. Composite cheat sheets 
-are launched in the cheat sheet view and show two panels which will be side by 
-side or one above the other depending on the relative height and width of the 
-view.</P>
-<P CLASS="Para">
-<img border="0" src="../images/cheatsheet_composite_running.png" width="300" height="437"></P>
-<P CLASS="Para">&nbsp;</P>
-<P CLASS="Para">The panel which appears on the left or on top (depending on the 
-view orientation) is called the task explorer and shows all of the tasks which 
-need to be completed and their state. The lower or right panel is called the 
-task detail panel and shows the task which is selected in the explorer.</P>
-<h3>Launching a composite cheat sheet</h3>
-<p>Composite cheat sheets are launched in the same way as any other
-<a href="ref-cheatsheets.htm">cheat sheet</a> by selecting&nbsp;
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.cheatsheets.openCheatSheet")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <strong>Help &gt; Cheat Sheets</strong></a> from the menu bar.</p>
-<h3>The task explorer</h3>
-<p>The task explorer is the tree view which shows the tasks and groups of tasks&nbsp; 
-in a composite cheat sheet. Each task will also have an overlay image at the 
-lower right corner it it is in progress, has been completed or has been skipped. 
-Selecting a task in the task explorer will cause that task to be displayed in 
-the task detail pane. Right clicking on a task in the task explorer brings up a 
-context menu which depending on the state of the task will allow the task to be 
-started, skipped or reset.</p>
-<h3>The task detail pane</h3>
-<p>The task detail pane will show different contents depending on the kind of 
-task and whether it has been started. A cheat sheet task which has not been 
-started will show a description and a button to start the task (or if it cannot 
-be started the reason why not). When in progress a cheat sheet task will show a 
-cheatsheet, and when it has been completed it will show a link to the next task.</p>
-<h3>Task groups</h3>
-<p>There are three kinds of task groups, &quot;set&quot;, &quot;sequence&quot; and &quot;choice&quot;. A 
-sequence represents a set of subtasks that must be performed in order, a set 
-represents a set of subtasks that can be performed in any order, a choice 
-represents a set of tasks only one of which should be performed. A set or 
-sequence is complete when all of its subtasks have been completed. A choice is 
-complete when one of its subtasks has been completed. </p>
-<h3>Cheat sheet tasks</h3>
-<p>A cheat sheet task represents a single
-<a href="ref-cheatsheets.htm">cheat sheet</a>. When a cheat sheet task is first 
-visited the task detail pane shows a description of the task and gives the 
-option to start working on the task and possibly to skip the task. The picture 
-below also shows the images for task sets, sequences and choices. Note that some 
-images are shown in gray, that is because these tasks cannot yet be started 
-because prerequisite tasks have not been completed.</p>
-<p>
-<img border="0" src="../images/cheatsheet_composite_start.png" width="272" height="356"></p>
-<h3>Task dependencies</h3>
-<p>A composite cheat sheet may have dependencies which require one task to be 
-completed before another can be started. An example of where this might happen 
-would be if one task created a project and a second task uses that project. In 
-this case the first task must be completed or skipped before the second task can 
-start.</p>
-<h3>Skipping tasks</h3>
-<p>The author of a composite cheat sheet can choose to make a task or task group 
-optional. If a task is optional it can be skipped, either by right clicking on 
-that task in the task explorer and selecting skip from the context menu, or by 
-clicking on the &quot;Skip this task&quot; hyperlink in the task detail pane. 
-Skipping a task will allow tasks which depend on this task to be started.<br>
-</p>
-<h3>Order of task completion</h3>
-<p>The task detail area will provide hyperlinks which will walk through the 
-tasks in order. It is also possible to perform tasks out of order by selecting 
-the task in the task explorer and starting work on that task. This is useful if 
-you want to go directly to a task of interest without working through all 
-earlier tasks.</p>
-<h3>Restarting tasks</h3>
-<p>Right clicking on the root node in the task explorer shows a menu item 
-&quot;Restart all tasks&quot;. If selected this will reset the state of every task in the 
-composite cheat sheet. Use this only if you want to reset all tasks. The context 
-menu for any other task will have a menu option to reset an individual task. Any 
-tasks which depend on this task will also be reset, and for task groups all 
-subtasks will also be reset.</p>
-<h3>Closing the composite cheat sheet</h3>
-<p>A composite cheat sheet is closed if the cheat sheet view is closed, if 
-Eclipse is closed or if another cheat sheet is opened. The state of each task is 
-saved so that when the composite cheat sheet is reopened its state will be 
-restored.</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-content-type.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-content-type.htm
deleted file mode 100644
index 599843b..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-content-type.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Content Types</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Content Types</H1>
-<P CLASS="Para"> The Content Types preference page allows you to edit content 
-  types, their associated file names and character sets as well as associate arbitrary 
-  file names or file extensions with content types. A content type acts as a description 
-  of a certain class of files (for instance, XML files). Eclipse uses this description 
-  in various scenarios such as editor look up and file comparing. </P>
-<P CLASS="Para">To access the Content Types preference page select <strong>Window 
-  &gt; Preferences &gt; General > Content Types</strong>. Here is what the Content 
-  Types preference page looks like:&nbsp; </P>
-<P><img src="../images/content_type.png" alt="Content types preference page" > 
-</P>
-<p CLASS="Para">By selecting a content type in the topmost tree you can alter 
-  the file names and extensions that are associated with it. <strong>Note</strong>: 
-  Certain items will be marked as "locked". An item is locked if it is one of 
-  the associations provided by the plug-in that declares the content type. In 
-  other words, only user-contributed associations may be removed.</P>
-<p CLASS="Para">Adding an association is as simple as clicking <strong>Add...</strong>. 
-  A dialog will be shown prompting you to enter the file name or extension.</P>
-<p><img src="../images/Image201_filetype.png" alt="New file type dialog" border="0" ></p>
-<p CLASS="Para">In addition to adding and removing file names or extensions, you 
-  may also set the default character set for a given content type. To do this, 
-  simply enter the character set name in the provided field and click <strong>Update</strong>. 
-</P>
-<p><img src="../images/contenttype-pref-charset.png" alt="Image of character set field" ></p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-cvs-decorations.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-cvs-decorations.htm
deleted file mode 100644
index 29cf71a..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-cvs-decorations.htm
+++ /dev/null

@@ -1,75 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>CVS Label Decorations</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">CVS Label Decorations</H1>
-<P CLASS="Para"> Label Decorations are used by CVS to show important synchronization 
-  information about workspace resources. Decorations can effect the text or the 
-  icon of the label associated with a resource. The text decorators are configurable 
-  on the <a href="../tasks/tasks-107b.htm">CVS Label Decorations Preference page</a> which can also be used to indicate 
-  which icons are to be enabled. Here is a description of the icons used by CVS.</P>
-<table width="94%" border="1">
-  <tr>
-    <td align="center"><strong>Decoration</strong></td>
-    <td><strong>Resource type</strong></td>
-    <td><strong>Description</strong></td>
-  </tr>
-  <tr> 
-    <td width="14%" align="center"><img src="../images/version_controlled.png" alt="Version control icon" ></td>
-    <td width="22%">Any</td>
-    <td width="64%">Indicates that the resource is under version control.</td>
-  </tr>
-  <tr> 
-    <td align="center"><img src="../images/dirty_ov.png" alt="Outgoing icon" ></td>
-    <td>Any</td>
-    <td>Indicates that the resource or one of its children contains outgoing changes.</td>
-  </tr>
-  <tr> 
-    <td align="center"><img src="../images/edited_ov.png" alt="Edit local icon" ></td>
-    <td>File</td>
-    <td>Indicates that the project containing the file has been configured to 
-      use watch/edit and the file is being edited locally.</td>
-  </tr>
-  <tr> 
-    <td align="center"><img src="../images/merged_ov.png" alt="Merge conflict icon" ></td>
-    <td>File</td>
-    <td>Indicates that the file contains a merge conflict which has not yet been 
-      resolved. The conflict is considered resolved once the file is modified 
-      and saved.</td>
-  </tr>
-  <tr> 
-    <td align="center"><img src="../images/no_remotedir_ov.png" alt="No remote folder icon" ></td>
-    <td>Project or Folder</td>
-    <td>Indicates that the folder is under version control but does not correspond 
-      to an existing remote directory but is instead most likely a module defined 
-      in the CVSROOT/modules file.</td>
-  </tr>
-  <tr> 
-    <td align="center"><img src="../images/question_ov.png" alt="Not under version control icon" ></td>
-    <td>File or Folder</td>
-    <td>Indicates that the resource is not under version control.</td>
-  </tr>
-</table>
-<P CLASS="Para"><em>Note</em>: Resources that are ignored by CVS will not be decorated 
-  by any of the above CVS decorations.</P>
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" > 
-  <br>
-  <a href="../concepts/cdecorations.htm">Label Decorations</a> </P>
-<P>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-107b.htm">Enabling the CVS resource decorations</a>
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-decorations.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-decorations.htm
deleted file mode 100644
index a909821..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-decorations.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Label Decorations</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Label Decorations</H1>
-<P CLASS="Para">
-Label Decorations allow additional information to be displayed in an item's
-label and icon.</P>
-<P CLASS="Para">
-The Label Decorations preference page provides a description of each decoration
-and allows the selection of which decorations are visible.&nbsp;</P>
-
-
-<P>Here is what the Label Decorations preference page looks like:&nbsp;
-</P>
-
-
-<P><img src="../images/Image84_decorator_preferenc.png" alt="Decorators preference page" border="0">
-</P>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br><a href="../concepts/cdecorations.htm">Label Decorations</a>
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-exttoolsprefs.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-exttoolsprefs.htm
deleted file mode 100644
index 1c1e0c9..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-exttoolsprefs.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>External Tools</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-External Tools</H1>
-<P CLASS="Intro">
-
-The following preferences can be changed on the External Tools page.</p>
-<P>&nbsp;You can configure whether or not you are prompted before external tool project builders are migrated.&nbsp;
-</P>
-
-<P><img src="../images/external_tools_prefs.png" alt="External Tools preference page" border="0" >
-</P>
-
-<p><img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-<br><a href="../concepts/concepts-antsupport.htm">Ant support</a>
-</p>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-antprefs.htm">Ant preferences</a><br>
-<a href="../reference/ref-antruntimeprefs.htm">Ant runtime preferences</a><br>
-<a href="../reference/ref-anteditorprefs.htm">Ant editor preferences</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-fonts.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-fonts.htm
deleted file mode 100644
index cb1141d..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-fonts.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Colors and Fonts</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Colors and Fonts</H1>
-<P CLASS="Para"> Many of the fonts and colors and used by eclipse components can be set using the 
-  Colors and Fonts preference page.</P>
-<P CLASS="Para"> A tree is used to navigate among and show a short preview of 
-  the various colors and fonts. The current face (but not size) of any font is 
-  previewed in its label. Colors are previewed in the icon associated with its 
-  label. Additionally, some categories (Workbench in particular) provide a more 
-  detailed preview of their contributions. This preview is shown below the description 
-  area if available.</P>
-<P CLASS="Para"> Font settings can be changed either by selecting the font from 
-  the list and clicking <strong>Use System Font </strong> to choose the Operating 
-  System font setting or by clicking <strong>Change </strong>to open up a font 
-  selection dialog. <strong>Reset</strong> can be used to return to the default 
-  value.</P>
-<P CLASS="Para"> Color settings can be changed by clicking <strong>color</strong> 
-  to the right of the tree area when a color is selected. <strong>Reset</strong> 
-  can be used to return to the default value.</P>
-
-
-<P>Here is what the Colors and Fonts preference page looks like:&nbsp; </P>
-
-
-<P><img src="../images/Image274_fonts_preference.png" alt="Fonts preference page" border="0" >
-</P>
-
-<p>The Colors and Fonts text field can be used to filter the contents. Simply 
-  type in an entry and any matching results will remain in the tree view.</p>
-<p>Descriptions and previews are provided when the Workbench colors and font settings 
-  are selected.</p>
-<p><img src="../images/Image274_fonts_preference2.png" alt="Fonts preference page" border="0"> 
-</p>
-<P><img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-<br><a href="../tasks/tasks-20.htm">Changing fonts and colors</a>
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-helpserver.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-helpserver.htm
deleted file mode 100644
index 8315f0d..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-helpserver.htm
+++ /dev/null

@@ -1,75 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Help Server</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Help Server</H1>
-<P CLASS="Para">
-Help system includes an internal server that serves help contents to the browser.
-Use this preference page to change the interface and port that the servers uses.
-You should only change these settings if you experience problems and cannot view
-help with the default preferences.
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-<TR>
-<TH align="left">
-<span style="font-weight: 400">Host</span></TH>
-<TH align="left">
-<span style="font-weight: 400">Name or address of a local IP interface
-to be used by the server.</span>
-</TH>
-<TH align="left">
-<span style="font-weight: 400">blank</span></TH>
-</TR>
-<TR>
-<TH align="left">
-<span style="font-weight: 400">Port</span></TH>
-<TH align="left">
-<span style="font-weight: 400">IP port for server to listen on.  If no port is specified
-for the value, a port will be assigned by the operating system.</span>
-</TH>
-<TH align="left">
-<span style="font-weight: 400">blank</span></TH>
-</TR>
-</THEAD>
-<TBODY>
-</TBODY>
-</TABLE>
-
-
-<P>Here is what the Help Server preferences page looks like:&nbsp;&nbsp;
-</P>
-
-
-<P>
-<img src="../images/pref_helpserver.png" alt="Help Server Preference Page" border="0">
-</P>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-keybindings.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-keybindings.htm
deleted file mode 100644
index bc88151..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-keybindings.htm
+++ /dev/null

@@ -1,532 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-List of key bindings
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h2>List of key bindings</h2>
-The list of available key bindings in Eclipse depends on many factors, including
-what view or editor is selected, whether a dialog is open, what plug-ins are
-installed, and what operating and windowing system is being used.  At any
-time, you can obtain a list of available key bindings using Key Assist 
-(<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.showKeyAssist")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Help &gt; Key Assist...</b></a>
-or Ctrl+Shift+L).  The following tables list some 
-popular key bindings available in the Eclipse SDK.
-
-<p>&nbsp;</p>
-<h3><strong>File actions</strong></h3>
-
-<table width="75%" border="1">
-  <tr style="height: 64.5pt;" height="86"> 
-    <td class="xl29" style="height: 64.5pt; width: 126pt;" height="86">New</td>
-    <td class="xl29" style="border-left: medium none; width: 269pt;">Create a 
-      Java element or a new resource. Configure which elements are shown in the 
-      submenu in Window &gt; Customize Perspective. In a Java perspective, by 
-      default action for creating a project, package, class, interface , source 
-      folder, scrapbook, file and folder are available.</td>
-    <td class="xl29" style="border-left: medium none; width: 110pt;">Ctrl + N</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Close</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Close 
-      the current editor. If the editor contains unsaved data, a save request 
-      dialog will be shown.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + F4</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Close 
-      All</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Close all editors. 
-	If editor contains unsaved data, a save request dialog will be shown.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Shift + F4</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Save</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Save 
-      the content of the current editor. Disabled if the editor does not contain 
-      unsaved changes.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + S</td>
-  </tr>
-  <tr style="height: 12.75pt;" height="17"> 
-    <td class="xl25" style="border-top: medium none; height: 12.75pt; width: 126pt;" height="17">Save 
-      As</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Save 
-      the content of the current editor under a new name.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;"></td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Save 
-      All</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Save 
-      the content of all editors with unsaved changes. Disabled if no editor contains 
-      unsaved changes.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Shift + S</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Print</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Prints 
-      the content of the current editor. Enabled when an editor has the focus.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + P</td>
-  </tr>
-  <tr style="height: 51.75pt;" height="69"> 
-    <td class="xl27" style="border-top: medium none; height: 51.75pt; width: 126pt;" height="69">Properties</td>
-    <td class="xl27" style="border-top: medium none; border-left: medium none; width: 269pt;">Opens 
-      the property pages of the select elements. Opened on Java projects the Java 
-      Build Path page and the Javadoc Location page are available. For JAR archives, 
-      configure the JAR's Source Attachment and Javadoc Location here.</td>
-    <td class="xl27" style="border-top: medium none; border-left: medium none; width: 110pt;">Alt 
-      + Enter</td>
-  </tr>
-</table>
-<h3><strong>Edit actions</strong></h3>
-<table width="75%" border="1">
-  <tr style="height: 13.5pt;" height="18"> 
-    <td class="xl29" style="height: 13.5pt; width: 126pt;" height="18">Undo</td>
-    <td class="xl29" style="border-left: medium none; width: 269pt;">Revert the 
-      last change in the editor</td>
-    <td class="xl29" style="border-left: medium none; width: 110pt;">Ctrl + Z</td>
-  </tr>
-  <tr style="height: 12.75pt;" height="17"> 
-    <td class="xl25" style="border-top: medium none; height: 12.75pt; width: 126pt;" height="17">Redo</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Revert 
-      an undone change</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Y</td>
-  </tr>
-  <tr style="height: 38.25pt;" height="51"> 
-    <td class="xl25" style="border-top: medium none; height: 38.25pt; width: 126pt;" height="51">Cut</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Copies 
-      the currently selected text or element to the clipboard and removes the 
-      element. On elements, the remove is not performed before the clipboard is 
-      pasted.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + X</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Copy</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Copies 
-      the currently selected text or elements to the clipboard</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + C</td>
-  </tr>
-  <tr style="height: 38.25pt;" height="51"> 
-    <td class="xl25" style="border-top: medium none; height: 38.25pt; width: 126pt;" height="51">Paste</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Paste 
-      the current content as text to the editor, or as a sibling or child element 
-      to the a currently selected element.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + V</td>
-  </tr>
-  <tr style="height: 12.75pt;" height="17"> 
-    <td class="xl25" style="border-top: medium none; height: 12.75pt; width: 126pt;" height="17">Delete</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Delete 
-      the current text or element selection.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Delete</td>
-  </tr>
-  <tr style="height: 12.75pt;" height="17"> 
-    <td class="xl25" style="border-top: medium none; height: 12.75pt; width: 126pt;" height="17">Select 
-      All</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Select 
-      all the editor content..</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + A</td>
-  </tr>
-  <tr style="height: 12.75pt;" height="17"> 
-    <td class="xl25" style="border-top: medium none; height: 12.75pt; width: 126pt;" height="17">Find 
-      / Replace</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Open 
-      the Find / Replace dialog. Editor only.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + F</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Find 
-      Next</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Finds 
-      the next occurrence of the currently selected text. Editor only.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + K</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Find 
-      Previous</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Finds 
-      the previous occurrence of the currently selected text. Editor only.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Shift + K</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Incremental 
-      Find Next</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Starts 
-      the incremental find mode. After invocation, enter the search text as instructed 
-      in the status bar. Editor only.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + J</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Incremental 
-      Find Previous</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Starts 
-      the incremental find mode. After invocation, enter the search text as instructed 
-      in the status bar. Editor only.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Shift + J</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Add 
-      Task</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Add 
-      a user defined task to the current text selection or selected element.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Alt 
-      + Enter</td>
-  </tr>
-  <tr style="height: 51pt;" height="68"> 
-    <td rowspan="4" class="xl27" style="border-top: medium none; height: 127.5pt; width: 126pt;" height="170">Expand 
-      Selection to</td>
-    <td class="xl27" style="border-top: medium none; border-left: medium none; width: 269pt;">Enclosing 
-      Element: Selects the enclosing expression, block, method in the code. This 
-      action is aware of the Java syntax. It may not function properly when the 
-      code has syntax errors. (Arrow Up).</td>
-    <td rowspan="4" class="xl27" style="border-top: medium none; width: 110pt;">Alt 
-      + Shift + Arrow Keys</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl28" style="border-left: medium none; height: 25.5pt; width: 269pt;" height="34">Next 
-      Element: Selects the current and next element. (Arrow Right)</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl28" style="border-left: medium none; height: 25.5pt; width: 269pt;" height="34">Previous 
-      Element: Selects the current and the previous element (Arrow Left)</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl28" style="border-left: medium none; height: 25.5pt; width: 269pt;" height="34">Restore 
-      Last Selection: After an invocation of Expand Selection to restore the previous selection. (Arrow Down)</td>
-  </tr>
-  <tr style="height: 38.25pt;" height="51"> 
-    <td class="xl25" style="height: 38.25pt; width: 126pt;" height="51">Show Tooltip 
-      Description</td>
-    <td class="xl25" style="border-left: medium none; width: 269pt;">Shows the 
-      value of a hover that would appear at the current cursor location. The dialog 
-      shown is scrollable and does not shorten descriptions.</td>
-    <td class="xl25" style="border-left: medium none; width: 110pt;">F2</td>
-  </tr>
-  <tr style="height: 89.25pt;" height="119"> 
-    <td class="xl25" style="border-top: medium none; height: 89.25pt; width: 126pt;" height="119">Content 
-      Assist</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Opens 
-      a context assist dialog at the current cursor position to bring up Java 
-      code assist proposals and templates. See the Templates preference page for 
-      available templates (Window &gt; Preferences &gt; Java &gt; Editor &gt; 
-      Templates) and go to the Editor preference page (Window &gt; Preferences 
-      &gt; Java &gt; Editor &gt; Code Assist) for configuring the behavior of 
-      code assist.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Space</td>
-  </tr>
-  <tr style="height: 38.25pt;" height="51"> 
-    <td class="xl25" style="border-top: medium none; height: 38.25pt; width: 126pt;" height="51">Quick 
-      Fix</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">If 
-      the cursor is located at a location with problem indication this opens a 
-      context assist dialog at the current cursor to present possible corrections.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + 1</td>
-  </tr>
-  <tr style="height: 51.75pt;" height="69"> 
-    <td class="xl27" style="border-top: medium none; height: 51.75pt; width: 126pt;" height="69">Parameter 
-      Hints</td>
-    <td class="xl27" style="border-top: medium none; border-left: medium none; width: 269pt;">If 
-      the cursor is located at the parameter specification for method reference, 
-      this actions shows a hover with parameter types information.The parameter 
-      at the current cursor location is shown in bold.</td>
-    <td class="xl27" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Shift + Space</td>
-  </tr>
-</table>
-<h3><strong>Navigate actions</strong></h3>
-<table width="75%" border="1">
-  <tr style="height: 26.25pt;" height="35"> 
-    <td class="xl29" style="height: 26.25pt; width: 126pt;" height="35">Open</td>
-    <td class="xl29" style="border-left: medium none; width: 269pt;">Tries to 
-      resolve the element referenced at the current code selection and opens the 
-      file declaring the reference.</td>
-    <td class="xl29" style="border-left: medium none; width: 110pt;">F3</td>
-  </tr>
-  <tr style="height: 63.75pt;" height="85"> 
-    <td class="xl25" style="border-top: medium none; height: 63.75pt; width: 126pt;" height="85">Open 
-      Type Hierarchy</td>
-    <td class="xl26" style="width: 269pt;">Tries to resolve the element referenced 
-      at the current code selection and opens the element in the Type Hierarchy 
-      view. Invoked on elements, opens the type hierarchy of the element. Supported 
-      in the Java editor and views showing Java elements.</td>
-    <td class="xl25" style="border-top: medium none; width: 110pt;">F4</td>
-  </tr>
-  <tr style="height: 102pt;" height="136"> 
-    <td class="xl25" style="border-top: medium none; height: 102pt; width: 126pt;" height="136">Open 
-      External Javadoc</td>
-    <td class="xl25" style="border-left: medium none; width: 269pt;">Opens the 
-      Javadoc documentation of the currently selected element or text selection. 
-      The location of the Javadoc of a JAR or a project is specified in the Javadoc 
-      Location property page on projects or JARs. Note that this external Javadoc 
-      documentation may not be up to date with the Javadoc specified in the current 
-      code. You can create Javadoc documentation for source files in a Java project 
-      using the Javadoc export wizard.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Shift 
-      + F2</td>
-  </tr>
-  <tr style="height: 38.25pt;" height="51"> 
-    <td class="xl25" style="border-top: medium none; height: 38.25pt; width: 126pt;" height="51">Open 
-      Type</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Brings 
-      up the Open Type selection dialog to open a type in the editor.The Open 
-      Type selection dialog shows all types existing in the workspace.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Shift + T</td>
-  </tr>
-  <tr style="height: 51pt;" height="68"> 
-    <td class="xl25" style="border-top: medium none; height: 51pt; width: 126pt;" height="68">Open 
-      Type In Hierarchy</td>
-    <td class="xl26" style="width: 269pt;">Brings up the Open Type selection dialog 
-      to open a type in the editor and the Type Hierarchy view. The Open Type 
-      selection dialog shows all types that exist in the workspace.</td>
-    <td class="xl25" style="border-top: medium none; width: 110pt;">Ctrl + Shift 
-      + H</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Show 
-      Outline</td>
-    <td class="xl25" style="border-left: medium none; width: 269pt;">Opens the 
-      lightweight outliner for the currently selected type.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + O</td>
-  </tr>
-  <tr style="height: 12.75pt;" height="17"> 
-    <td class="xl25" style="border-top: medium none; height: 12.75pt; width: 126pt;" height="17">Go 
-      to Next Problem</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Selects 
-      the next problem. Supported in the Java editor.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + .</td>
-  </tr>
-  <tr style="height: 12.75pt;" height="17"> 
-    <td class="xl25" style="border-top: medium none; height: 12.75pt; width: 126pt;" height="17">Go 
-      to Previous Problem</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Selects 
-      the previous problem. Supported in the Java editor.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + ,</td>
-  </tr>
-  <tr style="height: 12.75pt;" height="17"> 
-    <td class="xl25" style="border-top: medium none; height: 12.75pt; width: 126pt;" height="17">Go 
-      to Last Edit Location</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Reveal 
-      the location where the last edit occurred.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Q</td>
-  </tr>
-  <tr style="height: 26.25pt;" height="35"> 
-    <td class="xl27" style="border-top: medium none; height: 26.25pt; width: 126pt;" height="36">Go 
-      to Line</td>
-    <td class="xl27" style="border-top: medium none; border-left: medium none; width: 269pt;">Opens 
-      an a dialog which allows entering the line number to which the editor should 
-      jump to. Editor only.</td>
-    <td class="xl27" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + L</td>
-  </tr>
-</table>
-<h3><strong>Search actions</strong></h3>
-<table width="75%" border="1">
-  <tr style="height: 13.5pt;" height="18"> 
-    <td class="xl29" style="height: 13.5pt; width: 126pt;" height="18">Search...</td>
-    <td class="xl29" style="border-left: medium none; width: 269pt;">Opens the 
-      search dialog</td>
-    <td class="xl29" style="border-left: medium none; width: 110pt;">Ctrl + H</td>
-  </tr>
-  <tr style="height: 26.25pt;" height="35"> 
-    <td class="xl27" style="border-top: medium none; height: 26.25pt; width: 126pt;" height="35">Occurrences 
-      in File</td>
-    <td class="xl27" style="border-top: medium none; border-left: medium none; width: 269pt;">Finds 
-      all occurrences of the selected Java element in its file</td>
-    <td class="xl27" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Shift + U</td>
-  </tr>
-</table>
-<h3><strong>Project actions</strong></h3>
-<table width="75%" border="1">
-  <tr style="height: 52.5pt;" height="70"> 
-    <td class="xl28" style="height: 52.5pt; width: 126pt;" height="70">Build All</td>
-    <td class="xl28" style="border-left: medium none; width: 269pt;">Builds the 
-      all projects in the workspace. This is an incremental build, means that 
-      the builder analyzes the changes since the last time of build and minimizes 
-      the number of changed files.</td>
-    <td class="xl28" style="border-left: medium none; width: 110pt;">Ctrl + B</td>
-  </tr>
-</table>
-<h3><strong>Source actions</strong></h3>
-<table width="75%" border="1">
-  <tr style="height: 13.5pt;" height="18"> 
-    <td class="xl29" style="height: 13.5pt; width: 126pt;" height="18">Comment</td>
-    <td class="xl29" style="border-left: medium none; width: 269pt;">Comments 
-      out all lines containing the current selection.</td>
-    <td class="xl29" style="border-left: medium none; width: 110pt;">Ctrl + /</td>
-  </tr>
-  <tr style="height: 12.75pt;" height="17"> 
-    <td class="xl25" style="border-top: medium none; height: 12.75pt; width: 126pt;" height="17">Uncomment</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Uncomments 
-      all lines containing the current selection.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + \</td>
-  </tr>
-  <tr style="height: 38.25pt;" height="51"> 
-    <td class="xl25" style="border-top: medium none; height: 38.25pt; width: 126pt;" height="51">Shift 
-      Right</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Increments 
-      the level of indentation of the currently select lines. Only activated when 
-      the selection covers multiple lines or a single whole line.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Tab</td>
-  </tr>
-  <tr style="height: 38.25pt;" height="51"> 
-    <td class="xl25" style="border-top: medium none; height: 38.25pt; width: 126pt;" height="51">Shift 
-      Left</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Decrements 
-      the level of indentation of the currently select lines. Only activated when 
-      the selection covers multiple lines or a single whole line.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Shift 
-      + Tab</td>
-  </tr>
-  <tr style="height: 51pt;" height="68"> 
-    <td class="xl25" style="border-top: medium none; height: 51pt; width: 126pt;" height="68">Format</td>
-    <td class="xl24" style="border-top: medium none; border-left: medium none; width: 269pt;">Uses 
-      the code formatter to format the current text selection. The formatting 
-      options are configured on the Code Formatter preference page (Window &gt; 
-      Preferences &gt; Java &gt; Code Formatter)</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Shift + F</td>
-  </tr>
-  <tr style="height: 140.25pt;" height="187"> 
-    <td class="xl27" style="border-top: medium none; height: 140.25pt; width: 126pt;" height="187">Organize 
-      Imports</td>
-    <td class="xl31" style="border-left: medium none; width: 269pt;">Organizes 
-      the import declarations in the compilation unit currently open or selected. 
-      Unnecessary import declarations are removed, and required import declarations 
-      are ordered as specified in the Organize Import preference page (Window 
-      &gt; Preferences &gt; Java &gt; Organize Import). Organize import can be 
-      executed on incomplete source and will prompt you when a referenced type 
-      name can not be mapped uniquely to a type in the current project. You can 
-      also organize multiple compilation units by invoking the action on a package 
-      or selecting a set of compilation units.</td>
-    <td class="xl27" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Shift + O</td>
-  </tr>
-  <tr style="height: 90pt;" height="120"> 
-    <td class="xl27" style="height: 90pt; width: 126pt;" height="120">Add Import</td>
-    <td class="xl26" style="width: 269pt;">Creates an import declaration for a 
-      type reference currently selected. If the type reference if qualified, the 
-      qualification will be removed if possible. If the referenced type name can 
-      not be mapped uniquely to a type of the current project you will be prompted 
-      to specify the correct type. Add Import tries to follow the import order 
-      as specified in the Organize Import preference page.</td>
-    <td class="xl27" style="width: 110pt;">Ctrl + Shift + M</td>
-  </tr>
-</table>
-<h3><strong>Refactor actions</strong></h3>
-<table width="75%" border="1">
-  <tr style="height: 39pt;" height="52"> 
-    <td class="xl29" style="height: 39pt; width: 126pt;" height="52">Undo</td>
-    <td class="xl29" style="border-left: medium none; width: 269pt;">Does an Undo 
-      of the last refactoring. The refactoring undo buffer is only valid as long 
-      as no other source changes than refactoring have been performed.</td>
-    <td class="xl29" style="border-left: medium none; width: 110pt;">Alt + Shift 
-      + Z</td>
-  </tr>
-  <tr style="height: 38.25pt;" height="51"> 
-    <td class="xl25" style="border-top: medium none; height: 38.25pt; width: 126pt;" height="51">Redo</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Does 
-      a Redo of the last undone refactoring. The refactoring undo/redo buffer 
-      is only valid as long as no other source changes than refactoring have been 
-      performed.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Alt 
-      + Shift + Y</td>
-  </tr>
-  <tr style="height: 89.25pt;" height="119"> 
-    <td class="xl25" style="border-top: medium none; height: 89.25pt; width: 126pt;" height="119">Rename</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Starts 
-      the Rename refactoring dialog: Renames the selected element and (if enabled) 
-      corrects all references to the elements (also in other files). Is available 
-      on methods, fields, local variables, method parameters, types, compilation 
-      units, packages, source folders, projects and on a text selection resolving 
-      to one of these element types.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Alt 
-      + Shift + R</td>
-  </tr>
-  <tr style="height: 102pt;" height="136"> 
-    <td class="xl25" style="border-top: medium none; height: 102pt; width: 126pt;" height="136">Move</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Starts 
-      the Move refactoring dialog: Moves the selected elements and (if enabled) 
-      corrects all references to the elements (also in other files). Can be applied 
-      to one instance method (which can be moved to a component), one or more 
-      static methods, static fields, types, compilation units, packages, source 
-      folders and projects and on a text selection resolving to one of these element 
-      types.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Alt 
-      + Shift + V</td>
-  </tr>
-  <tr style="height: 51pt;" height="68"> 
-    <td class="xl25" style="border-top: medium none; height: 51pt; width: 126pt;" height="68">Inline</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Starts 
-      the Inline refactoring dialog. Inlines local variables, methods or constants. 
-      This refactoring is available on methods, static final fields and text selections 
-      that resolve to methods, static final fields or local variables.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Alt 
-      + Shift + I</td>
-  </tr>
-  <tr style="height: 89.25pt;" height="119"> 
-    <td class="xl27" style="border-top: medium none; height: 89.25pt; width: 126pt;" height="119">Extract 
-      Method</td>
-    <td class="xl24" style="border-top: medium none; border-left: medium none; width: 269pt;">Starts 
-      the Extract Method refactoring dialog. Creates a new method containing the 
-      statements or expression currently selected and replaces the selection with 
-      a reference to the new method. You can use Expand Selection from the Edit menu to get a 
-	  valid selection range. This feature is useful for cleaning up lengthy, cluttered, or overly-complicated methods.</td>
-    <td class="xl27" style="border-top: medium none; border-left: medium none; width: 110pt;">Alt 
-      + Shift + M</td>
-  </tr>
-  <tr class="xl30" style="height: 76.5pt;" height="102"> 
-    <td class="xl25" style="height: 76.5pt; width: 126pt;" height="102">Extract 
-      Local Variable</td>
-    <td class="xl30" style="width: 269pt;">Starts the Extract Variable refactoring 
-      dialog. Creates a new variable assigned to the expression currently selected 
-      and replaces the selection with a reference to the new variable. This refactoring 
-      is available on text selections that resolve to local variables. You can 
-      use Expand Selection from the Edit menu to get a valid selection range.</td>
-    <td class="xl25" style="width: 110pt;">Alt + Shift + L</td>
-  </tr>
-</table>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-search.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-search.htm
deleted file mode 100644
index 822fef7..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-search.htm
+++ /dev/null

@@ -1,97 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"><title>Search</title></head>
-<body>
-
-<h1>Search</h1>
-<p> The Search preference page allows the user to set preferences for searches. 
-</p>
-<p>&nbsp; </p>
-<TABLE BORDER="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Option</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Description</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Default</P></TH>
-    </TR>
-  </THEAD>
-  <TBODY>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Reuse editors to show matches</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          This option allows the user to keep using the same editor for search 
-          results to reduce the number of open editors.</P></TD>
-      <TD> On</TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Bring Search view to front after search</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          This option will display the search view at the front after performing 
-          a search. </P></TD>
-      <TD> On</TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Ignore potential matches</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Select this option if you only want to see exact matches.</P></TD>
-      <TD> Off</TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Emphasize potential matches</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          This option allows you to highlight potential matches in the Search 
-          view. If the Search engine isn't 100% sure about the match then it is 
-          considered a potential match. </P></TD>
-      <TD> On</TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Foreground color for potential matches</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          This option allows you to select the foreground color for potential 
-          matches.</P></TD>
-      <TD>&nbsp; </TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Limit table size for file search results to</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          This option allows you to limit the table size for file search results 
-          to a preset number.</P></TD>
-      <TD>Off </TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Default perspective for the Search view</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          This option allows you to define which perspective should be brought 
-          to the front when there are new search results.</P></TD>
-      <TD>None</TD>
-    </TR>
-  </TBODY>
-</TABLE>
-<p>&nbsp;</p>
-
-<p>Here is what the Search preference page looks like:&nbsp;
-</p>
-
-
-<p><img src="../images/Image276_search_preference.png" alt="Search Preference Page" border="0"> 
-</p>
-
-
-<p>&nbsp;
-</p>
-
-
-
-</body></html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-startup.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-startup.htm
deleted file mode 100644
index 8b51947..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-startup.htm
+++ /dev/null

@@ -1,73 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Startup and Shutdown</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Startup and Shutdown </H1>
-<P CLASS="Para"> The Startup and Shutdown preference page allows the selection 
-  of plug-ins to be automatically activated during workbench startup.&nbsp;</P>
-
-
-<P CLASS="Para">Normally plug-ins are not activated until they are needed.
-However some plug-ins may specify that they wish to be activated during startup.
-This preference page allows the selection of which of these plug-ins will
-actually be activated during startup.</P>
-
-<table BORDER CELLSPACING=0 >
-  <caption>
-  </caption>
-  <THEAD>
-  <br></THEAD>
-  <TBODY>
-  <br></TBODY>
-  <tr> 
-    <th> <div CLASS="Para">Option</div></th>
-    <th> <div CLASS="Para">Description</div></th>
-    <th> <div CLASS="Para">Default</div></th>
-  </tr>
-  <tr> 
-    <td> <div CLASS="Para">Prompt for workspace on startup</div></td>
-    <td> <div CLASS="Para">If this option is turned on then the workbench will 
-        prompt the user each time it is started for what workspace to use.</div></td>
-    <td> <div CLASS="Para">On</div></td>
-  </tr>
-  <tr> 
-    <td> <div CLASS="Para">Refresh workspace on startup</div></td>
-    <td> <div CLASS="Para">If this option is turned on then the workbench will 
-        synchronize its contents with the file system on startup.</div></td>
-    <td> <div CLASS="Para">Off</div></td>
-  </tr>
-  <tr> 
-    <td> <div CLASS="Para">Confirm exit when closing last window</div></td>
-    <td> <div CLASS="Para">If this option is turned on then the workbench will 
-        ask the user if they wish to exit when closing the last window if.</div></td>
-    <td> <div CLASS="Para">On</div></td>
-  </tr>
-  <tr> 
-    <td> <div CLASS="Para">Plug-ins activated on startup</div></td>
-    <td> <div CLASS="Para">This option allows you to select which available plug-ins 
-        should be activated on startup.</div></td>
-    <td> <div CLASS="Para"></div></td>
-  </tr>
-</table>
-
-<P>Here is what the Startup and Shutdown preference page looks like:&nbsp; </P>
-
-
-<P><img src="../images/Image275_startup_preference.png" alt="Startup Preference Page" border="0">
-</P>
-
-
-<P>&nbsp;
-</P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-texteditorprefs.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-texteditorprefs.htm
deleted file mode 100644
index e55577a..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-texteditorprefs.htm
+++ /dev/null

@@ -1,115 +0,0 @@
-<!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en"><html><head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta http-equiv="Content-Style-Type" content="text/css"><title>Text editor preference page</title>
-   
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"></head><body bgcolor="#ffffff">
-
-<h1 class="Head">Text Editor Preference Page</h1>
-<div class="Para"></div>
-
-<div class="Para">The following preferences can be changed on the Text Editor page.</div>
-<h2>Appearance options</h2>
-<table border="1" cellspacing="0" style="width: 100%;">
-  <caption>
-  </caption>
-  <thead>
-  </thead>
-  <tbody>
-  </tbody>
-  <tbody>
-    <tr> 
-      <th width="25%"> <div class="Para">Option</div></th>
-      <th> <div class="Para">Description</div></th>
-      <th> <div class="Para">Default</div></th>
-    </tr>
-    <tr> 
-      <td align="left" valign="top"> <div class="Para">Displayed tab width<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option allows you 
-          to set the displayed tab width for the text editor. </div></td>
-      <td align="left" valign="top"> <div class="Para">4</div></td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top"> <div class="Para">Undo history size<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option allows you 
-          to undo the history size for the text editor. </div></td>
-      <td align="left" valign="top"> <div class="Para">25</div></td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top"> <div class="Para">Highlight current line<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option controls whether 
-          or the current line is highlighted or not.<br>
-        </div></td>
-      <td align="left" valign="top"> On<br> </td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top"> <div class="Para">Show print margin<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option controls whether 
-          the print margin is visible or not.</div></td>
-      <td align="left" valign="top"> <div class="Para">Off</div></td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top"> <div class="Para">Show line numbers<br>
-        </div></td>
-      <td align="left" valign="top">This option controls whether or not line numbers 
-        are shown on the left side of the text editor.<br> </td>
-      <td align="left" valign="top"> Off<br> </td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top"> <div class="Para">Show range indicators<br>
-        </div></td>
-      <td align="left" valign="top">This option controls whether or not range 
-        indicators are shown in the text editor.<br> </td>
-      <td align="left" valign="top"> On<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Support hyperlink style navigation<br> 
-      </td>
-      <td style="vertical-align: top;">This option controls whether or not hyperlink 
-        style navigation is supported.<br> </td>
-      <td style="vertical-align: top;">On<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Hyperlink style navigation 
-        key modifier<br> </td>
-      <td style="vertical-align: top;">This option sets the hyperlink style navigation 
-        key modifier.<br> </td>
-      <td style="vertical-align: top;">Ctrl </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Disable overwrite typing mode<br> 
-      </td>
-      <td style="vertical-align: top;">This option controls whether the overwrite 
-        typing mode is enabled or disabled.<br> </td>
-      <td style="vertical-align: top;">Off<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top;" width="25%">Appearance color options<br> 
-      </td>
-      <td style="vertical-align: top;">This option controls various appearance 
-        colors.<br> </td>
-      <td style="vertical-align: top;"><br> </td>
-    </tr>
-  </tbody>
-</table>
-
-<p></p>
-<p>Here is what the Text editor preference page looks like:
-</p><p><img src="../images/ref-texteditorpref.png" alt="Image of the Text editor preference page"><br>
-
-
-</p><p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="../concepts/concepts-6.htm">Editor</a>
-<br>
-</p><p>&nbsp;<br>
-
-</p>
-
-
-</body></html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/antRunner.htm b/bundles/org.eclipse.platform.doc.user/tasks/antRunner.htm
deleted file mode 100644
index d7cef87..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/antRunner.htm
+++ /dev/null

@@ -1,78 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-         
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-         
-  <meta http-equiv="Content-Style-Type" content="text/css">
-          
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>antRunner application entry point</title>
-    
-</head>
- <body bgcolor="#ffffff">
-     
-<h1> antRunner application entry point</h1>
-     
-<p class="Para">The Ant core plug-in declares a main entry point that allows the running of Eclipse's integrated Ant support in a headless environment.
-An Ant build can then be run directly from the main platform launcher.</p>
-
-
-    <p>This is an example .bat file that shows how to make use of the antRunner application entry point on Windows.
-
-    <pre> 
-echo off
-setlocal
-
-REM ****************************************************
-
-REM The JRE java.exe to be used
-set JAVAEXE="C:\jdk1.4.2\jre\bin\java.exe"
-
-REM The Eclipse startup.jar
-set STARTUPJAR="C:\eclipse\startup.jar"
-
-REM The location of your workspace
-set WORKSPACE=C:\runtime-workspace
-
-REM The buildfile to use for the build
-set BUILDFILE=build.xml
-
-REM ****************************************************
-
-if not exist %JAVAEXE% echo ERROR: incorrect java.exe=%JAVAEXE%, edit this file and correct the JAVAEXE envar
-if not exist %JAVAEXE% goto done
-
-if not exist %STARTUPJAR% echo ERROR: incorrect startup.jar=%STARTUPJAR%, edit this file and correct the STARTUPJAR envar
-if not exist %STARTUPJAR% goto done
-
-if not exist %WORKSPACE% echo ERROR: incorrect workspace=%WORKSPACE%, edit this file and correct the WORKSPACE envar
-if not exist %WORKSPACE% goto done
-
-if not exist %BUILDFILE% echo ERROR: incorrect buildfile=%BUILDFILE%, edit this file and correct the BUILDFILE envar
-if not exist %BUILDFILE% goto done
-
-:run
-@echo on
-%JAVAEXE% -cp %STARTUPJAR% org.eclipse.core.launcher.Main -noupdate -application
-org.eclipse.ant.core.antRunner -data %WORKSPACE% -buildfile %BUILDFILE%
-
-:done
-pause
-</pre>
-    </p>     
-        
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"
- >
-  <br>
-     <a href="../concepts/concepts-antsupport.htm">Ant support</a></p>
-          
-
-      
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/no_help_exists.htm b/bundles/org.eclipse.platform.doc.user/tasks/no_help_exists.htm
deleted file mode 100644
index 8860eeb..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/no_help_exists.htm
+++ /dev/null

@@ -1,21 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE> No Help Exists</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-No Help Exists</H1>
-<p CLASS="Head">There are no available help topics associated with this
-item.&nbsp;&nbsp;&nbsp;</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/running_eclipse.htm b/bundles/org.eclipse.platform.doc.user/tasks/running_eclipse.htm
deleted file mode 100644
index a511910..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/running_eclipse.htm
+++ /dev/null

@@ -1,275 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Running Eclipse</title>
-</head>
-
-<BODY BGCOLOR="#ffffff">
-
-<h1>Running Eclipse</h1>
-<p>After you install (unzip) the Eclipse driver in a directory (such as c:\eclipse),
-start the Workbench by running the Eclipse executable file found in the
-top level install directory. The executable file is called <samp>eclipse.exe</samp> on Windows
-systems and <samp>eclipse</samp> on Linux systems. 
-
-<b>Note:</b> the following discussion describes setting up on Windows systems. Setup on Linux is
-analogous.</p>
-
-<p>If you do not specify otherwise, Eclipse will prompt you for a 
-workspace directory.  The default location for this directory will be a 
-child of your user home directory called "workspace" 
-(for example, c:\Documents and Settings\My Name\workspace). This workspace 
-directory is used as the default content area for your projects
-as well as for holding any required metadata. For shared or
-multi-workspace installs you should explicitly state the location of your
-workspace rather than using the default.  In addition to simply entering a 
-different location at the prompt you may also use the -data command line argument.</p>
-
-<h2>Setting a specific location for the workspace with -data</h2>
-
-<p>To use the <code>-data</code> command line argument, simply add <code>-data <var>your_workspace_location</var></code>
- (for example, <code>-data c:\users\robert\myworkspace</code>)
-to the <b>Target</b> field in the shortcut properties, or include it explicitly on your
-command line.</p>
-
-<h2>Setting the Java VM using -vm</h2>
-
-<p>It is recommended that you explicitly specify which Java VM to
-use when running Eclipse.  This is achieved with the <code>-vm</code> command line
-argument (for example, <code>-vm c:\jre\bin\javaw.exe</code>).  If you don't use 
-<code>-vm</code>, Eclipse will use the first Java VM found on the O/S path.  When you install other products, 
-they may change your path, resulting in a different Java VM being used when you next launch Eclipse.
-</p>
-
-<h1>Advanced Topics in Running Eclipse </h1>
-
-<p>The Eclipse executable and the platform itself offer a number of execution 
-  options of interest to people developing or debugging parts of Eclipse. This 
-  is a list of the commonly used options, for a full list see the Eclipse runtime 
-  options page in the Platform Plug-in Developer Guide. The general form of running 
-  the Eclipse executable is:</p>
-
-<blockquote>
-
-<pre>eclipse [platform options] [-vmargs [Java VM arguments]]</pre>
-
-</blockquote>
-
-<TABLE width="90%" border=1 height="2005">
-  <caption>
-  <b> Eclipse Startup Parameters </b> 
-  </caption>
-  <TBODY>
-    <tr> 
-      <th width="33%"> <b>Command</b></th>
-      <th width="65%"><b>Description</b></th>
-      <TD width="2%"><b>Since</b></TD>
-    </tr>
-    <tr> 
-      <TD vAlign=top width="33%"> <pre><b>-arch</b> <var>architecture</var></pre></TD>
-      <TD width="65%">Defines the processor architecture on which the Eclipse 
-        platform is running. The Eclipse platform ordinarily computes the optimal 
-        setting using the prevailing value of Java <code>os.arch</code> property. 
-        If specified here, this is the value that the Eclipse platform uses. The 
-        value specified here is available to plug-ins as BootLoader.getOSArch(). 
-        Example values: &quot;x86&quot;, &quot;sparc&quot;, &quot;PA-RISC&quot;, 
-        &quot;ppc&quot;.</TD>
-      <TD width="2%">2.0</TD>
-    </tr>
-    <TR> 
-      <TD vAlign=top width="33%"> <PRE><b>-application</b> <var>applicationId</var></PRE></TD>
-      <TD width="65%">The application to run. Applications are declared by plug-ins 
-        supplying extensions to the org.eclipse.core.runtime.applications extension 
-        point. This argument is typically not needed. If specified, the value 
-        overrides the value supplied by the configuration. If not specified, the 
-        Eclipse Workbench is run.</TD>
-      <TD width="2%">1.0</TD>
-    </TR>
-    <tr> 
-      <TD vAlign=top width="33%"> <pre><b>-configuration</b> <var>configurationFileURL</var></pre></TD>
-      <TD width="65%">The location for the Eclipse Platform configuration file, 
-        expressed as a URL. The configuration file determines the location of 
-        the Eclipse platform, the set of available plug-ins, and the primary feature. 
-        Note that relative URLs are not allowed. The configuration file is written 
-        to this location when the Eclipse platform is installed or updated. </TD>
-      <TD width="2%">2.0</TD>
-    </tr>
-    <TR> 
-      <TD vAlign=top width="33%"><PRE><b>-consolelog</b></PRE></TD>
-      <TD width="65%">Mirrors the Eclipse platform's error log to the console 
-        used to run Eclipse. Handy when combined with <code>-debug</code>.</TD>
-      <TD width="2%">1.0</TD>
-    </TR>
-    <tr> 
-      <TD vAlign=top width="33%"> <PRE><b>-data</b> <var>workspacePath</var></PRE></TD>
-      <TD width="65%">The path of the workspace on which to run the Eclipse platform. 
-        The workspace location is also the default location for projects. Relative 
-        paths are interpreted relative to the directory that Eclipse was started 
-        from.</TD>
-      <TD width="2%">1.0</TD>
-    </tr>
-    <TR> 
-      <TD vAlign=top width="33%"> <PRE><b>-debug</b> [<var>optionsFile</var>]</PRE></TD>
-      <TD width="65%"> Puts the platform in debug mode and loads the debug options 
-        from the file at the given location, if specified. This file indicates 
-        which debug points are available for a plug-in and whether or not they 
-        are enabled. If a file location is not given, the platform looks in the 
-        directory that eclipse was started from for a file called ".options". 
-        Both URLs and file system paths are allowed as file locations. </TD>
-      <TD width="2%">1.0</TD>
-    </TR>
-    <tr> 
-      <TD width="33%" height="133" vAlign=top> <PRE><b>-dev</b> [<var>classpathEntries</var>]</PRE></TD>
-      <TD width="65%">Puts the platform in development mode. The optional classpath 
-        entries (a comma separated list) are added to the runtime classpath of 
-        each plug-in. For example, when the workspace contains plug-ins being 
-        developed, specifying <code>-dev bin</code> adds a classpath entry for 
-        each plug-in project's directory named <code>bin</code>, allowing freshly 
-        generated class files to be found there. Redundant or non-existent classpath 
-        entries are eliminated.</TD>
-      <TD width="2%">1.0</TD>
-    </tr>
-    <TR> 
-      <TD vAlign=top width="33%"> <pre><b>-keyring</b> <var>keyringFilePath</var></pre></TD>
-      <TD width="65%"> The location of the authorization database (or &quot;key 
-        ring&quot; file) on disk. This argument must be used in conjunction with 
-        the <code>-password</code> option. Relative paths are interpreted relative 
-        to the directory that Eclipse was started from.</TD>
-      <TD width="2%">1.0</TD>
-    </TR>
-    <tr> 
-      <TD vAlign=top width="33%"> <pre><b>-nl</b> <var>locale</var></pre></TD>
-      <TD width="65%">Defines the name of the locale on which the Eclipse platform 
-        is running. The Eclipse platform ordinarily computes the optimal setting 
-        automatically. If specified here, this is the value that the Eclipse platform 
-        uses. The value specified here is available to plug-ins as BootLoader.getNL(). 
-        Example values: &quot;en_US&quot; and &quot;fr_FR_EURO&quot;.</TD>
-      <TD width="2%">2.0</TD>
-    </tr>
-    <tr> 
-      <TD vAlign=top width="33%"> <PRE><b>-nosplash</b></PRE></TD>
-      <TD width="65%">Runs the platform without putting up the splash screen.</TD>
-      <TD width="2%">1.0</TD>
-    </tr>
-    <tr> 
-      <TD vAlign=top width="33%"> <PRE><b>-os</b> <var>operatingSystem</var></PRE></TD>
-      <TD width="65%">Defines the operating system on which the Eclipse platform 
-        is running. The Eclipse platform ordinarily computes the optimal setting 
-        using the prevailing value of Java <code>os.name</code> property. If specified 
-        here, this is the value that the Eclipse platform uses. The value specified 
-        here is available to plug-ins as BootLoader.getOS(), and used to resolve 
-        occurrences of the <code>$os$</code> variable in paths mentioned in the 
-        plug-in manifest file. Example values: &quot;win32&quot;, &quot;linux&quot;, 
-        &quot;hpux&quot;, &quot;solaris&quot;, &quot;aix&quot;.</TD>
-      <TD width="2%">1.0</TD>
-    </tr>
-    <TR> 
-      <TD vAlign=top width="33%"> <pre><b>-password</b> <var>password</var></pre></TD>
-      <TD width="65%">The password for the authorization database. Used in conjunction 
-        with the <code>-keyring</code> option.</TD>
-      <TD width="2%">1.0</TD>
-    </TR>
-    <tr> 
-      <TD vAlign=top width="33%"> <PRE><b>-perspective</b> <var>perspectiveId</var></PRE></TD>
-      <TD width="65%">The perspective to open in the active workbench window on 
-        startup. If this parameter is not specified, the perspective that was 
-        active on shutdown will be opened.</TD>
-      <TD width="2%">1.0</TD>
-    </tr>
-    <tr> 
-      <TD vAlign=top width="33%"> <pre><b>-plugincustomization</b>
-	  <var>propertiesFile</var></pre></TD>
-      <TD width="65%">The location of a properties file containing default settings 
-        for plug-in preferences. These default settings override default settings 
-        specified in the primary feature. Relative paths are interpreted relative 
-        to the directory that eclipse was started from.</TD>
-      <TD width="2%">2.0</TD>
-    </tr>
-    <tr> 
-      <TD vAlign=top> <pre><b>-product</b> <em>productId</em><br></pre></TD>
-      <TD height="16">The ID of the product to run. The product gives the launched 
-        instance of Eclipse its personality, and determines the product customization 
-        information used. This replaces -feature, which is still supported for 
-        compatibility.</TD>
-      <TD height="16">3.0</TD>
-    </tr>
-    <TR> 
-      <TD vAlign=top width="33%" height="16"><pre><b>-refresh</b> </pre></TD>
-      <TD width="65%" height="16">Option for performing a global refresh of the 
-        workspace on startup. This will reconcile any changes that were made in 
-        the file system since the platform was last run. </TD>
-      <TD width="2%" height="16">1.0</TD>
-    </TR>
-    <TR> 
-      <TD vAlign=top width="33%" height="16"><pre><b>-showlocation</b> </pre></TD>
-      <TD width="65%" height="16">Option for displaying the location of the workspace 
-        in the window title bar. In release 2.0 this option only worked in conjunction 
-        with the -data command line argument.</TD>
-      <TD width="2%" height="16">2.0</TD>
-    </TR>
-    <tr> 
-      <TD vAlign=top width="33%"> <PRE><b>-vm</b> <var>vmPath</var></PRE></TD>
-      <TD width="65%">The location of Java Runtime Environment (JRE) to use to 
-        run the Eclipse platform. If not specified, the JRE is at <code>jre</code>, 
-        sibling of the Eclipse executable. Relative paths are interpreted relative 
-        to the directory that eclipse was started from.</TD>
-      <TD width="2%">1.0</TD>
-    </tr>
-    <tr> 
-      <TD vAlign=top> <PRE><b>-vm</b><strong>args</strong> <em>args</em></PRE></TD>
-      <TD>When passed to the Eclipse, this option is used to customize the operation 
-        of the Java VM used to run Eclipse. If specified, this option must come 
-        at the end of the command line. The given arguments are dependant on VM 
-        that is being run.</TD>
-      <TD>1.0</TD>
-    </tr>
-  </TBODY>
-</TABLE>
-
-<p>All arguments following (but not including) the -vmargs entry are passed
-directly through to the indicated Java VM as virtual machine arguments (that is,
-before the class to run).  <b>Note:</b> If an Eclipse startup argument, such as -data,
-is provided after the Java vm arguments (-vmargs), Eclipse will not start and you will receive 
-a &quot;JVM terminated. Exit code=1&quot; error.
-</p>
-
-<h2>Running on Different VMs&nbsp;</h2>
-<h3>Running Eclipse on J9</h3>
-<p>
-When running Eclipse on J9 version 1.5, it is recommended that you use the following VM
-options:
-</p>
-<blockquote>
-  <pre>eclipse.exe [eclipse arguments] -vm <var>path_to_j9w.exe</var> 
-            -vmargs -ms:32 -mm:2048 -mo:32768 -moi:32768 -mca:32 -mco:128 -mx:2000000</pre>
-</blockquote>
-<p> When running Eclipse on J9 version 2.0, the default arguments chosen by J9W 
-  should be suitable. However, to override the parameters which are automatically 
-  set internally by the Eclipse executable, you must specify -vmargs with no following arguments 
-  as follows: </p>
-<blockquote>
-  <pre>eclipse.exe [eclipse arguments] -vm <var>path_to_j9w.exe</var> -vmargs</pre>
-</blockquote>
-<p>Please refer to the J9 VM documentation and help for further information.</p>
-
-<h3>Running Eclipse on the IBM Developer Kit, Java(TM) Technology Edition VM</h3>
-
-<p>The default VM settings for IBM Developer Kit, Java(TM) Technology Edition 1.3 Linux work well for initial exploration, but
-are not sufficient for large scale development. For large scale development you
-should modify your VM arguments
-to make more heap available. For example, the following setting will allow the Java heap to grow to 256MB:&nbsp;
-</p>
-<blockquote>
-<pre>-vmargs -Xmx256M </pre>
-</blockquote>
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/taccess.htm b/bundles/org.eclipse.platform.doc.user/tasks/taccess.htm
deleted file mode 100644
index 09f965f..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/taccess.htm
+++ /dev/null

@@ -1,95 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Accessing and navigating online help</title>
-</head>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Accessing and navigating online help</h1>
-
-<p>The help browser lets you browse, search, and print online documentation
-for the product. To open the help browser, select <b>Help &gt; Help Contents</b> 
-in the Workbench. This opens the help browser to the bookshelf, which shows the 
-major sets of documentation available.
-</p>
-
-<p>To navigate online help:
-</p>
-
-<ol>
-  <li>Select the desired link on the bookshelf.</li>
-  <li>Expand the topic tree to find the information you are looking for. To
-    view a topic, click the link in the topic tree. </li>
-  <li>Most topics provide a list of links to related topics at the bottom.
-    Follow these links to learn more.</li>
-  <li>Use the <b>Go Forward</b> and <b>Go Back</b> buttons. These behave 
-    the same way back and forward buttons work in an Internet browser, taking 
-    you to topics you have already looked at.</li>
-  <li>To synchronize the navigation frame with the current topic, click the <b>Refresh / Show Current Topic</b> 
-    button <img src="../images/e_synch_nav.png" alt="Refresh / Show Current Topic button" border="0" > or
-    <b>Show in Table of Contents</b> 
-    button <img src="../images/e_synch_toc_nav.png" alt="Show in Table of Contents button" border="0" >. 
-    This is helpful if you have followed several links to related topics in several 
-    files, and want to see where the current topic fits into the navigation path.</li>
-</ol>
-
-<p>As an alternative to browsing the information this way,  use the
-search engine. Type a query into the <b>Search</b> field at the top of the 
-browser and click <b>Go</b>.
-</p>
-
-<p>To see context sensitive help from the Workbench put focus on a particular 
-widget and press F1. For more details, refer to the list of related topics below. 
-</p>
-
-<p>To show documentation about capabilities that are disabled in the application,
- select the <b>Show All Topics</b> 
-    button <img src="../images/e_show_all.png" alt="Show All Topics button" border="0" >.
- When you choose to show all topics in the table of contents, the headings for documentation
- about any disabled activities are shown in the table of contents and also appear in search results.
-</p>
-
-<h2>Maximizing help views</h2>
-
-<p>To increase the space available for viewing the help content, the frame that
-  displays content can be maximized.  To maximize the frame, click the  <b>Maximize</b> button
-<img src="../images/e_maximize.png" alt="Maximize button" border="0" >
-in the toolbar, or double click the toolbar. To return the frame to its original
-size, click the  <b>Restore</b> button
-<img src="../images/e_restore.png" alt="Restore button" border="0" >
-in the toolbar or double click the tool bar again.
-Similarly, you can maximize the frame showing navigation, by double clicking
-  its toolbar.
-</p>
-
-<h2>Printing online help</h2>
-
-<p>To print a topic from the online help:
-</p>
-
-<ol>
-  <li>Select the topic in the navigation frame.</li>
-  <li>Click the <b>Print</b> button <img src="../images/printer.png" alt="Print button" border="0" > 
-    in the Help toolbar.</li>
-  <li>Select the desired printer settings, and click <b>Print</b>.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/chelpsys.htm">Online help system</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tsearch.htm">Searching online help</a><br>
-<a href="tf1help.htm">Accessing context sensitive help</a>
-</p>
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/task-team-cmdlineclient.htm b/bundles/org.eclipse.platform.doc.user/tasks/task-team-cmdlineclient.htm
deleted file mode 100644
index 351f1a9..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/task-team-cmdlineclient.htm
+++ /dev/null

@@ -1,80 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Running the CVS command-line client outside of Eclipse</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Running the CVS command-line client outside of Eclipse</H1>
-<h2>Compatibility</h2>
-<p>Because the Eclipse CVS plug-in stores its meta information in a format that 
-  is compatible with the command-line CVS client you should be able to use a CVS 
-  command line client against Eclipse workspace files on disk. The metadata is 
-  stored in CVS/ sub-directories but you rarely see them within Eclipse. They are 
-  marked as private which causes them to be hidden from view. If you open a (non-Eclipse) 
-  file explorer you will see that these directories and their contents appear 
-  on the file system.</p>
-<h2> Don't forget to refresh!</h2>
-
-
-<p>Whenever you use external tools to modify workspace files, you must perform 
-  a <strong>Refresh</strong> from within Eclipse to make the workspace aware of 
-  the changes. If you get a <em>resource out of sync</em> error in Eclipse it 
-  is a sign that there are resources in Eclipse that have been modified outside 
-  of Eclipse. One solution is to perform a refresh (available from a resource's 
-  popup menu) on any resources or projects that where modified outside of Eclipse. 
-  There is also a preference to refresh automatically.</p>
-<h3>Caveats</h3>
-<p><strong>1. Deleted folders</strong></p>
-<p>You may encounter unexpected behavior when using the command-line CVS client 
-  in conjunction with deleted folders. Eclipse's CVS support keeps track of deleted 
-  folders and their contents so that, on the next synchronization, the Synchronize 
-  view can properly report on the changes. This information is kept outside of 
-  the CVS meta folder structure. This is because in CVS you normally inform the 
-  repository of deletions prior to deleting them locally, which is a different 
-  workflow than we like to support in the Synchronization view. Thus it is recommended 
-  that you do not use the command-line CVS client while you have pending deletions 
-  to commit. In some circumstances it could cause the Synchronize view to display 
-  incorrect contents, although it will not cause any lost work. </p>
-<p><strong>2. CVS directories appear in the workbench</strong></p>
-<p>When you use the command-line CVS the CVS folders can sometimes appear in one of the navigation views. There are some cases where CVS folders are not hidden from the 
-  UI as the user would expect. For instance, CVS folders will appear if a user 
-  imports a CVS project into Eclipse before the CVS plug-in is loaded. To avoid 
-  this, open the CVS Repositories view (thus loading the CVS plug-in) before importing 
-  CVS projects into Eclipse. </p>
-<p><strong>3. The 'extssh' connection method</strong></p>
-<p>The <em>extssh</em> connection method is unique to Eclipse CVS and doesn't 
-  exist in the command-line CVS client. If you are using <em>extssh</em> to connect 
-  to a SSH2 repository and would like to use the command line client for some 
-  CVS operations you can configure the <em>ext</em> connection method to use <em>extssh</em> 
-  when inside Eclipse.</p>
-<ol>
-  <li>Create a new repository location that uses the <em>ext</em> connection method. 
-    The repository path, host, and user should be identical to those in the <em>extssh</em> 
-    location.</li>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.ExtMethodPreferencePage)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <strong>Team &gt; CVS &gt; Ext Connection Method</strong></a> preference page.</li>
-  <li>Enable<strong> Use another connection method type to connect</strong> and 
-    choose <em>extssh</em>.</li>
-  <li>Now when you use the <em>ext</em> connection method inside Eclipse, <em>extssh</em> 
-    will be used instead of an external client.</li>
-</ol>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-95.htm">Changing the properties of a CVS repository location</a><br>
-<a href="tasks-92.htm">Creating a CVS repository location</a><br>
-<a href="tasks-117a.htm">Using projects checked out with another CVS tool</a>
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-1.htm
deleted file mode 100644
index 31626eb..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Customizing the Workbench</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Customizing the Workbench</H1>
-
-<p>Many aspects of the appearance and behavior of the Workbench
- can be customized to suit your individual needs. For example, you can:
-</p>
-
-<ul>
-<li>Rearrange where items appear in the main toolbar.</li>
-<li>Change the key bindings used by editors.</li>
-<li>Change the fonts and colors which are used.</li>
-</ul>
-
-<p>See the Related tasks links for more details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" width="159" height="27"><br>
-<a href="../concepts/concepts-5.htm">Views</a><br>
-<a href="../concepts/concepts-6.htm">Editors</a><br>
-<a href="../concepts/concepts-2.htm">Workbench</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" width="159" height="27"><br>
-<a href="ttoolbars.htm">Rearranging the main toolbar</a><br>
-<a href="tkeybindings.htm">Changing the key bindings</a><br>
-<a href="topenmode.htm">Controlling single and double click behavior</a><br>
-<a href="tasks-20.htm">Changing fonts and colors</a><br>
-<a href="tasks-9.htm">Changing the placement of the tabs</a><br>
-<a href="timpandexp.htm">Importing and Exporting Preferences</a><br>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-100.htm
deleted file mode 100644
index 75cc820..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating a version of a project</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Creating a version of a project</H1>
-
-<P><em>Prerequisite</em>: The project that you want to version must first be in 
-  the workspace.
-</P>
-
-<P><em>Tip</em>: It is often preferable to synchronize resources with the CVS 
-  repository before versioning. This will ensure that there are no outstanding 
-  incoming or outgoing changes that might be accidentally excluded from the version.
-</P>
-
-<P>To make a version of a project:
-</P>
-
-<ol>
-  <li>In one of the navigation views, select the project that you want to version.</li>
-  <li>From the project's context menu, select <b> Team &gt; Tag as Version</b>.</li>
-  <li>Enter the name of the version you wish to create.</li>
-  <li>Click <b>OK</b> to close the Tag Resources dialog and create the version.</li>
-</ol>
-
-<p><em>Tip:</em> You can browse existing versions of your project by clicking 
-  on the <b>Details</b> button in the Tag Resources dialog. Clicking <b>Refresh 
-  from Repository</b> should populate the Existing Versions list. It is sometimes 
-  helpful to see existing versions before naming your new version.
-</p>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-27.htm">Versions</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-17a.htm">Local history</a>
-</P>
-
-<P><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-117.htm">Sharing a new project using CVS</a><br>
-<a href="tasks-118.htm">Versioning projects in the repository</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-107b.htm">Enabling the CVS resource decorations</a> 
-</P>
-   
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-47.htm">CVS</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100a.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-100a.htm
deleted file mode 100644
index 37de826..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100a.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Branching</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Branching</H1>
-
-<P>Creating a branch and releasing resources to that branch is useful in cases 
-  where you are not yet ready to put your changes in the main development flow. 
-  It is also useful for creating incremental patches to existing versions.
-</P>
-
-<P>To create a branch:
-</P>
-
-<ol>
-  <li>From the context menu of the project, select <b>Team &gt; Branch</b>.</li>
-  <li>Enter the Branch Name for the new branch in the text area.</li>
-  <li>If the project in your workspace is not already a version, enter the Version 
-    Name to create in the text area.</li>
-  <li>If you would like to start working in the branch immediately, make sure 
-    the checkbox is selected.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p><em>Note:</em> The Version Name is important; you will need this when you want 
-  to merge your changes later on. It identifies the point at which the branch 
-  was created.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-100b.htm">Merging from a branch</a>
-</p>
-
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-47.htm">CVS</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-100b.htm
deleted file mode 100644
index 70d57f1..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100b.htm
+++ /dev/null

@@ -1,103 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Merging from a branch</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Merging from a branch</H1>
-
-<P>After creating and working in a CVS branch for some time, you may want to merge 
-  your changes from the branch into another branch, or into HEAD. To do this, 
-  you will need to know:
-</P>
-
-<ol>
-  <li>The name of the branch or version that contains your changes.</li>
-  <li>The version from which the branch was created. This is the version name 
-    that you supplied when branching.</li>
-</ol>
-
-<p>To merge your changes:
-</p>
-
-<ol>
-  <li>Ensure that the destination is loaded into your workspace. For example, 
-    if you wish to merge your changes into HEAD, make sure the project is shared 
-    with HEAD in your workspace. To do this, select the project and choose <b>Replace 
-    With &gt; Another Branch or Version</b> from the context menu. Then select 
-    the branch to replace with.</li>
-  <li>Select the project and choose <b>Team &gt; Merge</b>.</li>
-  <li>Enter the branch or version which contains the changes you want to merge.</li>
-  <li>The merge dialog will try to guess an appropriate start point. If that fails, 
-    enter the start point of the merge. This is the version from which the branch 
-    was created. Click <b>Finish</b>.</li>
-  <li>A CVS Merge synchronization will be added to the Synchronize view, showing 
-    all differences between your workspace and the branch with the changes.</li>
-  <li>Load all of the desired changes into the workspace. This may be accomplished 
-    by either manually merging changes, or by choosing <b>Update</b>, <b>Override 
-    and Update</b>, or <b>Mark as Merged</b> from the tree's context menu.</li>
-  <li>After all desired changes are in the workspace, choose <b>Team &gt; Synchronize 
-    with Repository</b>. You may then commit all the changes to the repository.</li>
-</ol>
-<p><em>Tip</em>: If you don't know the start point of the merge, you can choose 
-  to perform the merge directly into the workspace. This relies on the CVS server 
-  to pick an appropriate start point. Because the merge is performed directly 
-  into the workspace, CVS may introduce a text based conflict markup into the 
-  file. This markup is typically hard to deal with so merging directly into the 
-  workspace should only be done when necessary.</p>
-<h3>Merge actions</h3>
-<p>The actions in the merge editor complement the manual merge toolbar actions 
-  that are available in the bottom half of the merge editor.</p>
-<table width="100%" border="0">
-  <tr> 
-    <td width="20%"><strong>Update</strong></td>
-    <td width="80%">Running this action will bring the changes into the file in 
-      the workspace. Any conflicts that are not auto-mergeable will be skipped.</td>
-  </tr>
-  <tr> 
-    <td><strong>Override and Update</strong></td>
-    <td>This action is enabled on files with conflicting changes. Running this 
-      action will discard any local changes you have and replace the file with 
-      the remote contents.</td>
-  </tr>
-  <tr> 
-    <td><strong>Mark as Merged</strong></td>
-    <td>This action will remove the selected changes from the view. The changes 
-      will only reappear if the remote state of the resource changes and the CVS 
-      Merge Synchronization is refreshed.</td>
-  </tr>
-</table>
-<p><em>Tip</em>: You can perform ongoing merges by pinning a CVS Merge Synchronization 
-  in the Synchronize view. This will allow you to keep your workspace up-to-date 
-  with the changes released to a different branch.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-100a.htm">Branching</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-113.htm">Updating</a><br>
-<a href="tasks-114.htm">Committing</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" > 
-  <br>
-  <a href="../reference/ref-47.htm">CVS</a> <br>
-  <a href="../reference/ref-41a.htm">Merge wizard</a><br>
-  <a href="../reference/ref-33a.htm">CVS Merge Synchronization</a></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d.htm
deleted file mode 100644
index ef46c58..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d.htm
+++ /dev/null

@@ -1,98 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Version control life cycle: adding and ignoring resources</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Version control life cycle: adding and ignoring resources</H1>
-
-<p>When committing resources, often there are resources that you do not want to 
-  store in the repository. For example, external editors might create temporary 
-  files in your project, compilation of .java files might create .class files, 
-  or some build operations might result in binary files. When put together, these 
-  generated files may be quite large. They may also be regenerated whenever 
-  a build is performed, resulting in many outgoing changes. Typically these are 
-  not files that one wants to persist in the repository or to share with other 
-  members of a team.
-</p>
-
-<p>Team CVS has two related tasks that allow you to control which files are stored 
-  in the repository: adding a resource to version control, and ignoring a resource. 
-</p>
-  
-<h2>Adding a file to version control</h2>
-
-<p>Team CVS does not automatically add files to version control. Rather, it's 
-  your choice to explicitly add files to version control. This is accomplished 
-  by selecting the <b>Team &gt; Add to Version Control</b> menu.
-</p>
-
-<p>When performed on a file, it will add that file to version control. The result 
-  is that the CVS repository immediately creates an entry so that it can 
-  start maintaining history state for that file. This occurs even before you commit 
-  the file to the repository.
-</p>
-
-<p>When adding a folder or project, the action will recursively descend into sub-folders, 
-  adding those files it finds to version control, provided the files have not 
-  been explicitly ignored. </p>
-
-<p><em>Tip:</em> When committing files, if the selection either directly or recursively 
-  contains files which have not been added to version control, you will be prompted 
-  whether or not you want them added. This is a convenience function to help ensure 
-  that you do not miss committing new resources which were unintentionally never 
-  added. </p>
-
-<h2><i>How may I ignore thee, let me count the ways</i></h2>
-
-<P>There are several facilities that allow you to specify which resources should 
-  be excluded from version control:
-</P>
-
-<ol>
-  <li>There is a global preference which you can use for ignoring files and directories 
-    that match a certain filename pattern. For example, if you create a global 
-    ignore for <samp>/bin</samp>, and any resource that matches &quot;bin&quot; 
-    in any directory in the workspace will be ignored for version control. Use the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.ui.IgnorePreferences)")'>
-    <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-    <b>Team &gt; Ignored Resources</b></a>
-    preference page to globally exclude resources from version control.</li>
-  <li>Any resource marked as <i>derived</i> will be automatically ignored for 
-    version management by Team CVS. Some builders, such as the Java builder, mark 
-    all of its build output (e.g. .class files) as derived.</li>
-  <li>CVS supports the creation of a special <i>.cvsignore</i> file whose contents 
-    describe which files or folders to ignore for version management. The .cvsignore 
-    file only applies the pattern to resources in the <i> same</i> directory as 
-    the .cvsignore file itself.</li>
-</ol>
-
-<P><em>Tip</em>: Once a resource is under version control, it cannot easily be 
-  subsequently ignored. This is why adding to version control is an explicit operation 
-  performed by you the user.
-</P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-100d1.htm">Creating a global ignore pattern</a><br>
-<a href="tasks-100d2.htm">Authoring the CVS .cvsignore file</a><br>
-<a href="tasks-114.htm">Committing</a><br>
-<a href="tasks-113.htm">Updating</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d1.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d1.htm
deleted file mode 100644
index 7239503..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d1.htm
+++ /dev/null

@@ -1,70 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating a global ignore pattern</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Creating a global ignore pattern</H1>
-
-<P>When synchronizing resources, often there are resources that you do not want 
-  to commit to the repository. The Workbench provides a global pattern matching 
-  facility for ignoring resources that can appear anywhere in your project hierarchy.
-</P>
-
-<ol>
-  <li>Open the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.ui.IgnorePreferences)")'>
-    <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-    <b>Team &gt; Ignored Resources</b></a> preference page.
-    This displays a list of resource 
-    name patterns against which resources will be screened, before they are considered 
-    as candidates for version control.</li>
-  <li>Click the <b>Add Pattern...</b> push button and type the pattern that you want to match, 
-    for example <samp>*.obj</samp>.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p>All files with an extension that matches the pattern that you added will be 
-  excluded from version control.
-</p>
-
-<p>The patterns that you define may contain the wildcard characters * and ?. The 
-  asterisk represents any sequence of zero or more characters, the question mark 
-  represents a single character. For example, you can specify a pattern 
-  of <samp>*~</samp>, which would match any temporary files that end with a tilde 
-  (~). Any file or directory that matches any one of the patterns will be ignored 
-  when files are being considered for version control. You can temporarily disable 
-  ignoring the resource name pattern by deselecting it from the list. You do not 
-  have to remove the specified pattern from the list.
-</p>
-  
-<p>It is important to note that the path leading up to the resource name is not 
-  included in the matching. For example, for the file &quot;/path/to/file.txt&quot;, 
-  only the string &quot;file.txt&quot; is matched against the patterns.
-  This facility is not intended for specifying fully-qualified path names but 
-  for specifying globally applicable patterns.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-100d.htm">Version control life cycle: adding and ignoring resources</a><br>
-<a href="tasks-100d1b.htm">Overriding or removing resource ignore patterns</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d1b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d1b.htm
deleted file mode 100644
index 9312166..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d1b.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Overriding or removing resource ignore patterns</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Overriding or removing resource ignore patterns</H1>
-
-<p>After you have added global file-matching patterns to the list of files to 
-  be ignored for version management, you may wish to occasionally override the 
-  &quot;ignore&quot;.
-</p>
-
-<ol>
-  <li>Open the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.ui.IgnorePreferences)")'>
-    <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-    <b>Team &gt; Ignored Resources</b></a> preference page.</li>
-  <li>To temporarily override one or more of the file-matching patterns, clear 
-    their checkboxes.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p>Files that match the patterns you have deselected will be considered for version 
-  control.
-</p>
-
-<p>To permanently remove a pattern, select it and click <b>Remove</b>.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-100d.htm">Version control life cycle: adding and ignoring resources</a><br>
-<a href="tasks-100d1.htm">Creating a global ignore pattern</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d2.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d2.htm
deleted file mode 100644
index c9c85aa..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d2.htm
+++ /dev/null

@@ -1,76 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Authoring the CVS .cvsignore file</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Authoring the CVS .cvsignore file</H1>
-
-<P>When committing resources, often there are resources that you do not want to 
-  add to version control. One way you can do this is by using the CVS &quot;ignore&quot; 
-  facility, which reads the contents of the file <i>.cvsignore</i> to determine 
-  what to ignore.</P>
-
-<P>The <i>.cvsignore</i> file can be added to any directory of a project. Many 
-  existing CVS projects already contain several of these files. This text file 
-  consists of a list of files, directories, or patterns.
-</P>
-
-<P>For example, to add a .cvsignore file to ignore the entire bin directory of
-  an existing project:
-</P>
-
-<ol>
-  <li>In one of the navigation views, select a project that contains a /bin directory. 
-    The bin directory will commonly contain the projects build output. These are 
-    files that are generated from the project's source files and are usually not 
-    version-controlled.</li>
-  <li>From the pop-up menu for the project, select <b> New &gt; File</b>.&nbsp;</li>
-  <li>Type <i>.</i><samp>cvsignore</samp> as the file name, then press <b>Finish</b>. 
-    The file will be created in your project's root directory. You should see 
-    it in one of the navigation views.</li>
-  <li>Enter <samp>bin</samp> in the .cvsignore file and save it.</li>
-  <li>Select the project.&nbsp; From the context menu, select the <b> Team &gt; 
-    Synchronize with Repository</b> menu item.&nbsp; Notice that the bin directory 
-    does not show as an outgoing change. It is ignored.</li>
-</ol>
-
-<P>The cvsignore file consists of a list of files, directories, or patterns. 
-  In a similar way to the global ignore facility, the wildcards * and ? may be 
-  present in any entry in the .cvsignore file. Any file or sub-directory 
-  <i>in the current directory</i> that matches any one of the patterns will 
-  be ignored.
-</P>
-
-<p><b>Tip:</b> In the Team menu and in the Synchronize view resource context menu there is a menu item (<b>Add to .cvsignore</b>)
-for adding a file pattern
-to the appropriate .cvsignore file. This menu item is enabled for resources that are not yet under CVS version
-control.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-100d.htm">Version control life cycle: adding and ignoring resources</a><br>
-<a href="tasks-100d1.htm">Creating a global ignore pattern</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="https://www.cvshome.org/docs/manual/cvs-1.11.16/cvs_18.html#SEC178" target="_blank">www.cvshome.org: Ignoring files via cvsignore</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-101.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-101.htm
deleted file mode 100644
index 7a5021a..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-101.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Comparing resources with repository versions</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Comparing resources with repository versions</H1>
-
-<P>To compare Workbench resources with those in the repository:
-</p>
-
-<ol>
-  <li>Select a resource in one of the navigation views.</li>
-  <li>From the resource's pop-up menu, select one of the following menu items: 
-    <ul>
-      <li><b>Compare With &gt; Latest From &lt;Branch Name&gt;</b> or <strong>&lt;Version&gt;</strong>- 
-        Compare the Workbench resource with the latest resources currently committed 
-        to the branch that the local project is shared with or if the local project 
-        is checked out as a version then compare against the version. A compare 
-        editor will be opened. This editor will display a tree of all resource 
-        differences between the workspace resource and the latest resources in 
-        the repository.</li>
-      <li><b>Compare With &gt; Another Branch or Version</b> - Compare the Workbench 
-        resource with a specific version or branch that you select in the repository. 
-        A compare editor will be opened. The editor will display a tree of all 
-        resource differences between the workspace resource and the resources 
-        in the specified version or branch.</li>
-      <li><b>Compare With &gt; Revision</b> - (available only on a file) Compare 
-        the Workbench file with another revision of the file. A compare editor 
-        will be opened. The editor will display a table of all available revisions 
-        of the selected file. Selecting one of the revisions will show the differences 
-        between the workspace revision and the selected revision. </li>
-    </ul>
-  </li>
-</ol>
-<p><em>Tip</em>: When comparing with a branch or version, you can specify a particular 
-  date instead of a a version or branch tag. This can be done by right clicking 
-  on the <strong>Dates</strong> category in the tag selection list and choosing 
-  <strong>Add Date</strong>. A Date Tag dialog is displayed that allows you to 
-  specify a date and optionally a time. After you click <strong>Ok</strong>, the 
-  date tag will appear in the tag selection list.</p>
-<P CLASS="Intro"><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-29.htm">Three way comparisons</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a></p>
-<p>
-
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-68b.htm">Setting preferences for comparing files</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="../reference/ref-47.htm">CVS</a>
-<br><a href="../reference/ref-25.htm">Compare editor</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-103.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-103.htm
deleted file mode 100644
index bd9ee9e..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-103.htm
+++ /dev/null

@@ -1,73 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Replacing resources in the Workbench</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Replacing resources in the Workbench</H1>
-
-<p>To replace Workbench resources with versions in the repository:
-</p>
-
-<ol>
-  <li>Select a resource in one of the navigation views.</li>
-  <li>From the resource's pop-up menu, select one of the following menu items: 
-    <UL>
-      <LI><b>Replace With &gt; Latest From &lt;Branch Name&gt;</b> or <strong>&lt;Version&gt;</strong> 
-        - replace the Workbench resource with the latest resources currently committed 
-        to the branch that the local project is shared with or if the local project 
-        is checked out as a version then replace with the same version.</LI>
-      <LI><b>Replace With &gt; Another Branch or Version</b> - replace the Workbench 
-        resource with a specific version or branch that you select in the repository. 
-        When you select this option, another window opens, so that you can browse 
-        through the branch and version tags in the repository and select the one 
-        that you want.</LI>
-      <LI><b>Replace With &gt; Revision</b> - (available only on a file) replace 
-        the Workbench file with another revision of the file. When you select 
-        this option, a dialog opens to allow you to select a revision from the 
-        list of available ones. A test window displays the comparison between 
-        the local revision and the selected remote revision.</LI>
-      <LI><strong>Team &gt; Switch to Another Branch or Version</strong> - this 
-        update will replace Workbench resources with those on the tag specified 
-        in the Update dialog. The behavior differs from the above replace operations 
-        in that uncommitted modifications in the Workbench are not replaced but 
-        instead are &quot;moved&quot; to the resources from the selected tag. 
-        For more details on the specifics of this operation, see the CVS documentation 
-        at <a href="https://www.cvshome.org">www.cvshome.org</a> relating to the 
-        use of the <em>-r </em>option with <em>cvs update</em>.</LI>
-    </UL>
-  </li>
-</ol>
-<p><em>Tip</em>: When replacing with a branch or version or when updating, you 
-  can specify a particular date instead of a a version or branch tag. This can 
-  be done by right clicking on the <strong>Dates</strong> category in the tag 
-  selection list and choosing <strong>Add Date</strong>. A Date Tag dialog is 
-  displayed that allows you to specify a date and optionally a time. After you 
-  click <strong>Ok</strong>, the date tag will appear in the tag selection list.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-27.htm">Versions</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-96.htm">Checking out a project from a CVS repository</a><br>
-<a href="tasks-117.htm">Sharing a new project using CVS</a><br>
-<a href="tasks-119.htm">Viewing a file's revision history</a><br>
-<a href="tasks-100a.htm">Branching</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-105.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-105.htm
deleted file mode 100644
index 66b0d1b..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-105.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Changing CVS team settings</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Changing CVS team settings</H1>
-
-<P>You can customize the settings related to a number of CVS team views and operations.
-</p>
-
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.ui.TeamPreferences)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Team</b></a> preference page. You will see a number of general Team options. These options can 
-    be used by any Eclipse integrated repository. In our case, they are all applicable 
-    to CVS.</li>
-  <li>You will also see a
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.CVSPreferences)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Team &gt; CVS</b></a> preference page containing
-  various CVS options.</li>
-  <li>Underneath the <strong>Team &gt; CVS</strong> preference page are several sub-pages. 
-    For example, there are pages for <strong>Watch/Edit</strong>, <strong>Console</strong>, 
-    <strong>Label Decorations</strong> and <strong>SSH2</strong> among others.</li>
-</ol>
-
-<p>In the Preferences dialog, you can search by keywords such as CVS or SSH2 in 
-  order to show only the relevant pages.</p>
-
-<h2>Changing CVS Project Settings</h2>
-<p>You can change CVS project settings in the properties dialog of a project.</p>
-<ul>
-  <li>From the context menu of a view showing the project, select Properties</li>
-  <li>Click on the CVS category</li>
-</ul>
-<p>From this dialog, you can:</p>
-<ul>
-  <li>Enable Watch/Edit on the project.</li>
-  <li>Specify whether new or absent folders should be fetched when an update is 
-    performed.</li>
-  <li>Change the repository location to which the project is associated.</li>
-</ul>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-114.htm">Committing</a>
-</p>
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="../reference/ref-19cvs.htm">CVS Preference pages</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-105a.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-105a.htm
deleted file mode 100644
index 5a2c1a3..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-105a.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Restoring deleted files from the repository</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Restoring deleted files from the repository</H1>
-
-<P>The CVS plug-in allows you to delete files from the CVS repository. If you 
-  delete a managed file and commit the deletion to the server, the file is deleted 
-  from the current branch or version. Although the file has been deleted from 
-  the current branch, the file and its previous revisions are actually still on 
-  the server. The CVS plug-in provides a tool to help restore a file to your workspace 
-  that has previously been deleted from the CVS repository:</p>
-
-<ol>
-  <li>Select a folder managed by CVS and from the context menu select <strong>Team 
-    &gt; Restore from Repository</strong>.</li> 
-  <li>The repository will be searched for deleted files and the list will be shown 
-    in a dialog.</li> 
-  <li>Select a file in the left most pane to display the revisions of the file 
-    that are available in the repository.</li>
-  <li>Select a revision in the right-most pane to view the contents in the bottom 
-    text pane.</li>
-  <li>Check the revision that you would like to restore.</li> 
-  <li>Click <strong>Finish</strong> once you have checked off a revision for each 
-    file you wish to restore.</li>
-  <li>After restoring the file if you want to actually restore the file to the 
-    current branch you have to add then commit the file back into the repository. 
-    If the filename does not change, revision history will be maintained for the 
-    restored file.</li> 
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-114.htm">Committing</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-105b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-105b.htm
deleted file mode 100644
index 19c9c5d..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-105b.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Reverting a branch to a previous version</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Reverting a branch to a previous version</H1>
-<p>
-It is often useful to revert the contents of a branch to those of a specific version. For example, if your current branch contains changes that you no longer want to release you can revert all or a portion of a project to the contents of any version.</p>
-
-<ol>
-  <li>Checkout into your workspace the contents from the branch that you want 
-    to revert. </li>
-  <li>Select <strong>Compare With &gt; Another Branch or Version</strong> on the 
-    resource(s) that you want to revert. </li>
-  <li>From the tag selection dialog box select the version to which you want to 
-    revert the branch.</li>
-  <li>When the compare editor opens, review the differences that are shown and 
-    ensure that they are what you expected. </li>
-  <li>Select the root folder in the compare view and from the context menu select 
-    <strong>Override and Update</strong>. After the operation is completed the 
-    folder or project you compared against will have exactly the same contents 
-    as the remote revision. </li>
-  <li>You can verify this by performing another comparison against the version. 
-    (<strong>Note</strong>: That the CVS preference to <strong>Consider file contents 
-    in comparisons</strong> in the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.ComparePreferences)")'>
-    <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-    <b>Team &gt; CVS &gt; Synchronize/Compare</b></a>
-    preference page should be enabled for this to work.) </li>
-  <li>The comparison should report that there are no changes.</li>
-</ol>
-<p CLASS="Head">Once your workspace contains the new contents, run your tests 
-  then commit the changes to the branch.</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-114.htm">Committing</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-105c.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-105c.htm
deleted file mode 100644
index 2993053..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-105c.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Moving version tags</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Moving version tags</H1>
-<p>Warning: Although many people would prefer a CVS version to be frozen in time and not be modifiable, version and branch tags in CVS are mutable. As a result many are convinced that modifying a version is bad practice, but there are a couple of scenarios where it actually comes in handy. With that said, please be cautious when moving tags around.</p>
-<h2>Moving a tag on a single file</h2>
-<p>Let's say that you have just submitted your build by versioning your project 
-  as R1. But you soon after discover that there is a small change to a file that 
-  should be made and included in the build. Instead of having to re-version the 
-  project you can move the R1 version tag for the modified file.</p>
-<ol>
-  <li>Modify the file(s) Select the file that was modified after R1 was created 
-    and from the context menu select <strong>Team &gt; Show in Resource History</strong>.</li>
-  <li>From within the Resource History view select the revision that should be 
-    marked with the R1 version. </li>
-  <li>From the context menu select <strong>Tag with Existing...</strong>.</li>
-  <li>Select the R1 version from the dialog box and press OK. </li>
-  <li>The resource history view will be updated to confirm that the version had 
-    been moved.</li>
-</ol>
-<h2>Moving a tag from within the repositories view</h2>
-<p>Many projects use a well defined version name for their current stable lineup in HEAD. For example, by versioning HEAD with the STABLE tag the build scripts could simply checkout the STABLE version for builds. As the code evolves the STABLE tag is moved regularly to mark the most current stable lineup. The repositories view provides an action for moving an existing tag.
-</p>
-<ol>
-<li>Open the Repositories view and select a resource.</li>
-<li>From the context menu select <b>Tag with Existing</b></li> 
-<li>A tag selection dialog will appear from which you can select the tag to move. If the tag you wish to apply is not show in the list, you can click <b>Refresh from Repository</b>. If this doesn't find the tag, you can click <b>Configure Tags</b> which opens a dialog that allows you to search for tags on specific files in the repository.</li>
-<li>Then press <b>OK</b> and your tag will be moved. The operation will move an existing tag to the selected resources and can be used to move both version and branch tags.</li>
-</ol>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-114.htm">Committing</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-107b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-107b.htm
deleted file mode 100644
index eb32dbe..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-107b.htm
+++ /dev/null

@@ -1,121 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Enabling the CVS resource decorations</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Enabling the CVS resource decorations</H1>
-
-<P>When enabled, CVS will decorate resources in Workbench views with icon and 
-label decorations that indicate the CVS state of the resource.
-</P>
-
-<P>To enable the CVS decorations:
-</P>
-
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Decorators)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General &gt; Appearance &gt; Label Decorations</b></a>
-  preference page. This page allows the enabling and disabling of all decorations 
-  defined by different plug-ins in the Workbench.</li>
-  <li>Click on the CVS box to enable the CVS decorations.</li>
-  <li> Click <b>OK</b>.</li>
-</ol>
-
-<p><em>Note:</em> In some cases, the decorations may not appear immediately due 
-  to the fact that they are expensive to compute. In those cases, they are calculated 
-  in the background. </p>
-
-<p>To configure the CVS decorations:
-</p>
-
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.CVSDecoratorPreferences)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Team &gt; CVS &gt; Label Decorations</b></a>
-  preference page. This page allows the configuration of how decorations appear on CVS 
-  projects, folders and files.</li>
-  <li>To configure the text label decorations click the <strong>Text</strong> 
-    tab and then: 
-    <ol type="a">
-      <li>Pick the resource type (file, folder, project) for which you want to 
-        change the decoration.</li>
-      <li>Click in the decoration string for that resource type at the location 
-        where the new decoration element should go.</li>
-      <li>Click the <b>Add Variables</b> button for that resource type.</li>
-      <li>Choose the CVS information variable to add. For instance, for files 
-        you could select the <i>added_flag</i> which will be inserted in the decoration 
-        where you placed the cursor. The string <i>{added_flag}</i> will be added 
-        to the decoration string which will decorate newly added resources using 
-        the added resource label (which can be set in the <i>Label Decoration 
-        for Added</i> field).</li>
-    </ol>
-  </li>
-  <li>Repeat the above for any other decorations to be added.</li>
-  <li>Decorations can be removed by deleting the decoration variable name (i.e.<i> 
-    {added_flag}</i>) from the decoration string. In a similar manner, spacing 
-    can be added.</li>
-  <li>To configure icon decorations, click the <strong>Icon</strong> tab simply 
-    enable/disable the icon checkboxes.</li>
-  <li>Click <b>OK</b> or <b>Apply</b> for the new decorations to take effect.</li>
-</ol>
-
-<p><em>Note</em>: Under the <strong>General</strong> tab is an option to disable 
-  the deep dirty decoration of folders. This will make decorator determination 
-  more efficient but will make it harder to find dirty resources in one of the 
-  navigation views. Under the <strong>Synchronize View</strong> tab, the Synchronize 
-  view can be configured to show the synchronization state of a resource as part 
-  of the text label displayed in the Structure Compare pane.</p>
-<p>You can also change the color and font of items based on the item's CVS state. 
-  To set the color and font:</p>
-<ol>
-  <li>Open the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.CVSDecoratorPreferences)")'>
-    <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-    <b>Team &gt; CVS &gt; Label Decorations</b></a>
-    preference page.</li>
-  <li>Check the box to <em>Enable font and color decorations</em>.</li>
-  <li>Next, Open the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.ColorsAndFonts)")'>
-    <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-    <b>General &gt; Appearance &gt; Colors and Fonts</b></a> preference page.</li>
-  <li>In the <strong>CVS</strong> category are the various CVS states for which 
-    you can set the colors and fonts. Set them as desired.</li>
-  <li>You can return to the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.CVSDecoratorPreferences)")'>
-    <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-    <b>Team &gt; CVS &gt; Label Decorations</b></a>
-    preference page to preview the changes.</li>
-  <li>Click <b>OK</b> or <b>Apply</b> for the new decorations to take effect.</li>
-</ol>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-  <a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-  <a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a> 
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-96.htm">Checking out a project from a CVS repository</a><br>
-<a href="tasks-117.htm">Sharing a new project using CVS</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-47.htm">CVS</a><br>
-<a href="../reference/ref-cvs-decorations.htm">CVS Label Decorations</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-110.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-110.htm
deleted file mode 100644
index 7c0bc1f..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-110.htm
+++ /dev/null

@@ -1,95 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Discovering branch and version tags</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Discovering branch and version tags</H1>
-
-<p><em>Prerequisite:</em>Before you can discover the branch and version tags for 
-  a repository, you must have a valid repository location in the CVS Repositories 
-  view. </p>
-<P>To discover existing branch tags for multiple folders in a single repository 
-  location:</p>
-<ol>
-  <li>Switch to the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.team.cvs.ui.cvsPerspective)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  CVS Repository Exploring</a> perspective or add the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.team.ccvs.ui.RepositoriesView)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  CVS Repositories</a> view to the current perspective.</li>
-  <li>In the CVS Repositories view, select a repository location.</li>
-  <li>From the pop-up menu for the CVS Repositories view, select <b>Refresh Branches</b>. 
-    The Refresh Branches dialog will open.</li>
-  <li>In the folder list, select the folders whose tags you would like to refresh. 
-    Alternatively, at the bottom of the dialog, you can choose a working set and 
-    all remote folders whose names match the name of a project in the working 
-    set will become checked.</li>
-  <li>Click <b>Finish</b> to discovered the tags for the checked projects. These 
-    tags will be added to the repositories view. </li>
-</ol>
-<P><em>Note:</em> This operation may be long running especially if the number 
-  of selected folders is large. </p>
-<P><em>Tip</em>: If the above operation does not result in the discovery of any 
-  tags, it is probable that the folder in the repository does not have a .project 
-  file in it. The .project file is the default file used by the tag discovery 
-  process. The file can be changed for individual projects using <strong>Configure 
-  Branches and Versions</strong> (see below).</p>
-<P>To discover existing branch and version tags for a single project folder: </p>
-<ol>
-  <li>Switch to the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.team.cvs.ui.cvsPerspective)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  CVS Repository Exploring</a> perspective or add the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.team.ccvs.ui.RepositoriesView)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  CVS Repositories</a> view to the current perspective.</li>
-  <li>In the CVS Repositories view, expand the repository location.</li>
-  <li>Expand <strong>HEAD</strong> and select the root folder whose tags are to 
-    be discovered.</li>
-  <li>From the pop-up menu for the CVS Repositories view, select <b>Configure 
-    Branches and Versions</b>. The Tag Configuration dialog will open.</li>
-  <li>In the top pane on the left (titled <i>Browse files for tags</i>), expand 
-    one or more projects to find a file that is known to have tags that should 
-    be added to the CVS Repositories view.</li>
-  <li>Select a file in the left top pane. If the file selected has tags defined 
-    on it, they will be displayed in the right top pane (titled <i>New tags found 
-    in selected files</i>).</li>
-  <li>Check or uncheck the tags in the right pane as desired.</li>
-  <li>Click <b>Add Checked Tags</b> to add the checked tags to the list of remembered 
-    tags.</li>
-  <li>Click <b>OK</b> to add the remembered tags to the selected repository location 
-    or project.</li>
-</ol>
-<p><em>Note</em>: You can also set the auto-refresh files by selecting a file 
-  in the files pane and clicking<strong> Add Selected Files</strong> in the lower 
-  right hand portion of the dialog. </p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-27.htm">Versions</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-92.htm">Creating a CVS repository location</a><br>
-<a href="tasks-96.htm">Checking out a project from a CVS repository</a><br>
-<a href="tasks-117.htm">Sharing a new project using CVS</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-113.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-113.htm
deleted file mode 100644
index b934793..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-113.htm
+++ /dev/null

@@ -1,148 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Updating</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Updating</H1>
-
-<P>While you are working on a project in the Workbench, other members of your 
-  team may be committing changes to the copy of the project in the repository. 
-  To get these changes, you may &quot;update&quot; your Workbench to match the 
-  state of the branch. The changes you will see will be specific to the branch 
-  that your Workbench project is configured to share. You control when you choose 
-  to update.
-</P>
-
-<p>The update command can be issued from two places: the <b>Team &gt; Update</b> 
-  menu, or the <b>Synchronize</b> view. In order to understand the difference 
-  between these two commands, it is important to know about the three different 
-  kinds of incoming changes.
-</p>
-
-<ul>
-  <li>A <i>non-conflicting</i> change occurs when a file has been changed remotely 
-    but has not been modified locally.</li>
-  <li>An <i>auto-mergeable conflicting</i> change occurs when an ASCII file has 
-    been changed both remotely and locally (i.e. has non-committed local changes) 
-    but the changes are on different lines.</li>
-  <li>A <i>non-auto-mergeable conflicting</i> change occurs when one or more of 
-    the same lines of an ASCII file or when a binary file has been changed both 
-    remotely and locally (binary files are never auto-mergeable).</li>
-</ul>
-
-<p>When you select <b>Team &gt; Update</b>, the contents of the local resources 
-  will be updated with incoming changes of all of the above three types. For non-conflicting 
-  and auto-mergeable conflicts, there is no additional action required (for auto-mergeable 
-  conflicts, the changed local resource is moved to a file prefixed with &quot;.#&quot; 
-  just in case the auto-merge wasn't what the user wanted). However, for non-auto-mergeable 
-  conflicts, the conflicts are either merged into the local resource using special 
-  CVS specific markup text (for ASCII files) or the changed local resource is 
-  moved to a file prefixed with &quot;.#&quot; (for binary files). This matches 
-  the CVS command line behavior but can be problematic when combined with the Eclipse 
-  auto-build mechanism. Also, it is often desirable to know what incoming changes 
-  there are before updating any local resources. These issues are addressed by 
-  the Synchronize view.
-</p>
-
-<p>To open the Synchronize view in incoming mode:
-</p>
-
-<ol>
-  <li>In one of the navigation views, select the resources which you want to update.</li>
-  <li>From the pop-up menu for the selected resources, select <b>Team &gt; Synchronize 
-    with Repository</b>. The Synchronize view will open.</li>
-  <li>On the toolbar of the Synchronize View, click the <b> Incoming mode</b> 
-    button to filter out any modified Workbench resources (outgoing changes) that 
-    you may have.</li>
-</ol>
-
-<p>In incoming mode, you will see changes that have been committed to the branch 
-  since you last updated. The view will indicate the type of each incoming change. 
-  There are two update commands (available from the context menu of any resource 
-  in the view) to deal with the different types of conflicts: <b>Update</b> and 
-  <b>Override and Update</b>. When you select the <b>Update</b> command in the 
-  Synchronize view, all selected incoming and auto-mergeable conflicting changes 
-  are processed while conflicts that are not auto-mergeable will not be updated 
-  (any files that have been successfully processed are removed from the view). 
-  The <b>Override and Update</b> command operates on conflicts and will replace 
-  the local resources with the remote contents. This &quot;replace&quot; behavior 
-  is rarely what is desired. An alternative is described later. </p>
-
-<p>To update non-conflicting and auto-mergeable files:</p>
-<ol>
-  <li>The Structure Compare pane at the top of the Synchronize view contains the 
-    hierarchy of resources with incoming changes.</li>
-  <li>Select all conflicting files and choose <b>Update </b> from the pop-up menu. 
-    This will update the selected resources that are either incoming changes or 
-    auto-mergeable conflicts and remove them from the view. Conflicts whose contents 
-    are not auto-mergeable will be left in the view.</li>
-</ol>
-
-<p>If your local Workbench contains any outgoing changes that are not auto-mergeable 
-  with incoming changes from the branch, then, instead of performing an <b>Override 
-  and Update</b>, you can merge the differences into your Workbench manually, 
-  as follows:
-</p>
-
-<ol>
-  <li>In the Structure Compare pane, if there is a conflict in the resource list 
-    (represented by red arrows), open it (either by double-clicking or selecting 
-    <strong>Open in Compare Editor</strong> from the context menu).</li>
-  <li>In the Text Compare area of the compare editor, local Workbench data is 
-    represented on the left, and repository branch data is represented on the 
-    right. Examine the differences between the two.</li>
-  <li>Use the text compare area to merge any changes. You can copy changes from 
-    the repository revision of the file to the Workbench copy of the file and 
-    save the merged Workbench file (using the pop-up menu in the left pane).</li>
-  <li>Once you are completed merging the remote changes into a local file, choose 
-    <b>Mark as Merged</b> from the pop-up menu in the Synchronize view. This will 
-    mark the local file as having been updated and allow your changes to be committed.</li>
-</ol>
-
-<p><em>Note:</em> The repository contents are not changed when you update. When 
-  you accept incoming changes, these changes are applied to your Workbench. The 
-  repository is only changed when you commit your outgoing changes.
-</p>
-
-<p><em>Tip:</em> In the Synchronize view, selecting an ancestor of a set of incoming 
-  changes will perform the operation on all the appropriate children. For instance, 
-  selecting the top-most folder and choosing <b>Update </b> will process all incoming 
-  and auto-mergeable conflicting changes and leave all other incoming changes unprocessed. 
-</p>
-
-<p><em>Warning:</em> The behavior of the <b>Override and Update</b> command described 
-  above only applies to the incoming mode of the Synchronize view. In the <b>Incoming/Outgoing 
-  mode</b> of the view, the behavior for incoming changes and conflicts is the 
-  same but the command will revert outgoing changes to whatever the repository 
-  contents are. Exercise great caution if using this command in Incoming/Outgoing 
-  mode. </p>
-
-<p CLASS="Intro"><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-114.htm">Committing</a><br>
-<a href="tasks-113b.htm">Resolving conflicts</a><br>
-<a href="tasks-68.htm">Comparing resources</a><br>
-<a href="tasks-100d.htm">Version control life cycle: adding and ignoring resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="../reference/ref-47.htm">CVS</a>
-<br><a href="../reference/ref-33.htm">Synchronize view</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-113b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-113b.htm
deleted file mode 100644
index 4edafea..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-113b.htm
+++ /dev/null

@@ -1,119 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Resolving conflicts</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Resolving conflicts</H1>
-
-<P>When updating or committing you may encounter conflicts. A conflict occurs 
-  when you have locally modified a resource for which a more recent revision is 
-  available in the branch in the repository. Specifically, the branch will contain 
-  a revision newer than the base revision of your resource. In this situation 
-  you can choose to do one of the following:
-</P>
-
-<ul>
-  <li>You can take the change from the branch, discarding your local work. This 
-    could occur if you have made unintended changes locally, or if you realize 
-    that the revision in the repository is better than yours. Overwriting your 
-    local changes should be done with caution since you are in essence throwing 
-    work out.</li>
-  <li>You can commit your change, subsuming the revision in the repository. This 
-    should be done with great caution since you are in essence throwing away someone 
-    else's work. In particular, the change you are overwriting may have other 
-    dependencies in the branch (for example there may be other incoming changes 
-    which depend on the conflict).</li>
-  <li>You can merge your work and the repository resource, saving locally the 
-    merged resource. You may then later choose to commit this merged result.</li>
-</ul>
-
-<P>Typically, you will want to take the third option, that is to merge, because 
-  of the loss of work issues with the other two choices.
-</P>
-
-<h2><a name="MergingChanges">Manually merging changes</a></h2>
-
-<P>The Synchronize View indicates those resources which are in conflict with the 
-  branch. For a given resource in conflict, typically you will want to merge your 
-  changes with changes in the branch's resource.
-</P>
-
-<P CLASS="Para">For example, let us assume that both you and another team member 
-  have modified the same html page. Opening that resource from the Synchronize 
-  view will display a comparison of the local resource and the branch revision. 
-  By cycling through and merging the individual changes, you can decide for each 
-  change whether to accept the incoming change, reject it, or merge it with your 
-  local changes. When you are finished merging, you save your changes. This overwrites 
-  your local resource with the result of the merge. You can subsequently commit 
-  this merged resource. </P>
-
-<P><em>Tip:</em> When merging changes, it is often convenient to be able to distinguish 
-  which files you have completed merging. When you're done merging a file, you 
-  can pick <b>Mark as Merged</b> from the context menu. This will change the status 
-  of the file from being a conflict to being an outgoing change.
-</P>
-
-<P>You can merge differences in the Synchronization view on two levels:
-</P>
-
-<ul>
-  <li><b>Whole Document</b> - In the Synchronize view, open the resource that 
-    you want to merge in a Compare editor. In the Compare editor, click the Copy 
-    all non-conflicting Changes from Right to Left button to copy all non-conflicting 
-    changes. Conflicting changes will have to copied individually.</li>
-  <li><b>Current Change</b> - In the Text Compare editor, either use the Go to 
-    Next Difference and Go to Previous Difference buttons to navigate to the change 
-    that you want to merge, or simply click in either source pane somewhere in 
-    the desired change difference fragment. Click the Copy current change from 
-    right to left button as needed to overwrite the highlighted fragment either 
-    with the corresponding modification in the branch.</li>
-</ul>
-
-<h2><a name="AutoMergingChanges">Auto merging changes</a></h2>
-
-<p>It is also possible to have your changes automatically merged for you. For 
-  any resource marked as ASCII, performing a <b>Team &gt; Update</b> will automatically 
-  merge into your local resource differences with the branch resource. This works 
-  fine provided there are no lines with conflicting changes. If there are, CVS 
-  inserts special markup in the file to indicate those lines which could not be 
-  merged.
-</p>
-
-<p>Updating from within the Synchronization view works a bit differently. In the 
-  case of a conflict, <strong>Update</strong> will only process files whose contents 
-  contain no conflicts. Files that have content conflicts will be skipped and 
-  left in the Synchronize view as conflicts.</p>
-
-<P>&nbsp;<img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a><br>
-<a href="../concepts/concepts-29.htm">Three way comparisons</a>
-</P>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-113.htm">Updating</a><br>
-<a href="tasks-114.htm">Committing</a><br>
-<a href="tasks-100b.htm">Merging from a branch</a><br>
-<a href="tasks-68.htm">Comparing resources</a><br>
-<a href="tasks-68dg.htm">Merging changes in the Compare editor</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="https://www.cvshome.org/docs/manual/cvs-1.11.16/cvs_10.html#SEC84" target="_blank">www.cvshome.org: Bringing a file up to date</a><br>
-<a href="https://www.cvshome.org/docs/manual/cvs-1.11.16/cvs_10.html#SEC85" target="_blank">www.cvshome.org: Conflicts example</a>
-<br><a href="../reference/ref-25.htm">Compare editor</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-114.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-114.htm
deleted file mode 100644
index 4ba160e..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-114.htm
+++ /dev/null

@@ -1,111 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Committing</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Committing</H1>
-
-<P>You can commit Workbench resources that you have modified to the repository 
-  so that other team members can see your work. Only those changes committed on 
-  that branch will be visible to others working on that branch. The commit command 
-  can be issued from two places: the <b>Team &gt; Commit</b> menu, or the <b>Synchronize</b>
-  view.
-</p>
-
-<P>To commit changes using <b>Team &gt; Commit</b>:
-</p>
-
-<ol>
-  <li>In one of the navigation views, select the resources that you want to commit.</li>
-  <li>Right-click on the resources and select <b>Team &gt; Commit</b> from the 
-    pop-up menu.</li>
-  <li>If there are new files whose file types cannot be determined automatically, 
-    the first page of the Commit dialog will present the unknown types and allow 
-    you to set them appropriately to either ASCII or binary. Click <strong>Next</strong> 
-    to continue.</li>
-  <li>On the Comment page, provide a comment for your changes (for example, <samp>Fixed 
-    the spelling mistakes</samp>).</li>
-</ol>
-
-<P>The Comment page also allows the user to preview the files that are about to 
-  be committed. If any of the files are known to be conflicting changes, the commit 
-  will not be allowed. If there are no known conflicting changes the commit will 
-  be allowed but there could still be conflicting changes on the server (i.e. 
-  conflicting changes on the server become known to the client during a synchronize 
-  operation). If there are conflicting changes on any files that are committed, 
-  the operation will fail. If this occurs, you must either perform an update or 
-  use the Synchronize view to resolve the conflicts. It is considered a more ideal 
-  workflow to always update before committing in order to ensure that you have 
-  the latest state of the repository before committing more changes. </p>
-<P>If one or more of the resources being committed are new and not yet added to 
-  CVS control, they will be added automatically unless they are explicitly removed 
-  by choosing <strong>Remove from View</strong> from the context menu.</p>
-<P>To commit changes in the Synchronize view:
-</p>
-
-<ol>
-  <li>In one of the navigation views, select the resources that you want to commit.</li>
-  <li>Right-click to open the pop-up menu and select <b> Team &gt; Synchronize 
-    with Repository</b>. The Synchronize view will open.</li>
-  <li>On the toolbar of the Synchronize view, select the <b>Outgoing mode</b> 
-    button to show any modified Workbench resources (outgoing changes) that you 
-    may have.</li>
-  <li>If there are conflicts (red arrows), resolve them. To do so. open them in 
-    a Compare editor and use the text compare area to merge resources with conflicts. 
-    You can copy changes from the repository revision of the file to the Workbench 
-    revision of the file and save the merged Workbench resource. Once all the 
-    conflicts in the Structure Compare area have been resolved, perform a <strong>Mark 
-    as Merged</strong> on the resource in the Synchronize view to make the change 
-    an outgoing change and you are ready to commit.</li>
-  <li>In the Structure Compare pane, right-click the top of the hierarchy that 
-    you want to commit, and select <b>Commit</b> from the pop-up menu.</li>
-  <li>In the Commit Comment dialog box, provide a comment for your changes (for 
-    example, <samp>Fixed the spelling mistakes</samp>). Again, if there are new 
-    files of an unknown type, you will be asked to specify what type they should 
-    be. </li>
-</ol>
-
-<P><em>Tip:</em> You can commit files that are in conflict by performing an <b>Override 
-  and Commit</b>. This will commit the Workbench copy of the resource into the 
-  repository and thus remove any of the incoming changes.
-</p>
-
-<P><em>Warning:</em> The behavior of the <b>Override and Commit</b> command described 
-  above only applies to the outgoing mode of the Synchronize view. In the <b>Incoming/Outgoing 
-  mode</b> of the view, the behavior for outgoing changes and conflicts is the 
-  same but the command will revert incoming changes to whatever the local Workbench 
-  contents are. Exercise great caution if using this command in incoming/outgoing 
-  mode. </p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-113.htm">Updating</a><br>
-<a href="tasks-113b.htm">Resolving conflicts</a><br>
-<a href="tasks-68.htm">Comparing resources</a><br>
-<a href="tasks-100d.htm">Version control life cycle: adding and ignoring resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="../reference/ref-47.htm">CVS</a>
-<br><a href="../reference/ref-33.htm">Synchronize view</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-115.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-115.htm
deleted file mode 100644
index 447fabe..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-115.htm
+++ /dev/null

@@ -1,116 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Synchronizing with the repository</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Synchronizing with the repository</H1>
-
-<h2>Method 1: Using the context menu</h2>
-<p>To synchronize resources in the Workbench with those in the repository: </p>
-
-<ol>
-  <li>In one of the navigation views, select the resources that you want to synchronize.</li>
-  <li>Right click and select <b>Team &gt; Synchronize with Repository</b>. The 
-    Synchronize view opens.</li>
-</ol>
-<h2>Method 2: Using the synchronize action</h2>
-<ol>
-  <li> From the Team Synchronizing perspective select the <strong>Synchronize...</strong> 
-    action from the Synchronize <img src="../images/synch_participants.png" alt="" border="0" > 
-    button drop down.</li>
-  <li>Select <strong>CVS</strong> from the list of possible synchronization types 
-    and click <strong>Next</strong>.</li>
-  <li>Select the resource scope for the synchronize by either selecting Workspace, 
-    Selected Resources or Working Set. Then select <strong>Finish.</strong></li>
-  <li>The Synchronize view will open.</li>
-</ol>
-<p> <strong>Note</strong>: The synchronize action is not enabled by default in 
-  other perspectives. You can enable the action to appear in your current perspective 
-  by selecting
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.customizePerspective")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <strong>Window &gt; Customize Perspective</strong></a>. Then click 
-  on the <strong>Commands</strong> tab and check off <strong>Team</strong>.</p>
-<p><em>Tip</em>: If you choose the Workspace scope for your synchronization, you 
-  can then use method 3 below to always have an up-to-date view of your local 
-  modifications available in the Synchronize view without re-running the synchronize 
-  operation. </p>
-<h2>Method 3: Using a pinned CVS Workspace Synchronization in the Synchronize 
-  view</h2>
-<p>Once you have a CVS workspace synchronization in the Synchronize view, you 
-  can pin it. This will prevent it from being replaced by the next CVS workspace 
-  synchronization that is launched using one of the previous 2 methods. Here are 
-  some of the advantages of using a pinned synchronization.</p>
-<ul>
-  <li>The local modification state of the resources being synchronized is kept 
-    up-to-date. This means that, if you modify a file locally that is within the 
-    scope of a synchronization that appears in the Synchronize view, the resource 
-    will appear automatically in the view, if it is not already there.</li>
-  <li>The remote state of all of the resources being synchronized can be refreshed 
-    using the Synchronize <img src="../images/synch_participants.png" alt="" border="0" > 
-    button in the toolbar of the Synchronize view.</li>
-  <li>The remote state of a selection of resources can be refreshed using the 
-    Synchronize command from the context menu in the Synchronize view.</li>
-  <li>You can schedule the refreshing of the remote state to happen at particular 
-    intervals (each hour, for example)</li>
-</ul>
-<p>The implications of this is that you can see you outgoing resources without 
-  re-fetching the remote state from the server (a potentially long running operation). 
-  Also, the fetching of the remote state is run in the background so you can do 
-  other things (e.g. inspect changes) while the remote state is fetched.</p>
-<h3>From within the synchronize view</h3>
-<ol>
-  <li>Use the toolbar buttons to switch modes for this view. There are four modes: 
-    <ul>
-      <li>Incoming mode - shows incoming changes only (resources in the repository 
-        that differ from what is in the Workbench).</li>
-      <li>Outgoing mode - shows outgoing changes only (resources modified in the 
-        Workbench).</li>
-      <li>Incoming/Outgoing mode - shows both incoming and outgoing changes.</li>
-      <li>Conflicts mode = shows only conflicting resources.</li>
-    </ul>
-    <p><em>Important:</em> It is preferable to update resources in the Workbench 
-      first, resolve any conflicts that exist by merging, then commit Workbench 
-      resources to the repository.</p></li>
-  <li>It is possible that someone has committed a new revision of your file since 
-    you started working on it. This will result in a <em>conflict</em>, and care 
-    must be taken to resolve this. For this reason, conflicts are shown in all 
-    modes of the Synchronize view.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a><br>
-<a href="../concepts/concepts-29.htm">Three way comparisons</a></p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-114.htm">Committing</a><br>
-<a href="tasks-113.htm">Updating</a><br>
-<a href="tasks-113b.htm">Resolving conflicts</a><br>
-<a href="tasks-68.htm">Comparing resources</a><br>
-<a href="tasks-68dg.htm">Merging changes in the Compare editor</a><br>
-<a href="tasks-100b.htm">Merging from a branch</a><br>
-<a href="tasks-100d.htm">Version control life cycle: adding and ignoring resources</a><br>
-<a href="tasks-103.htm">Replacing resources in the Workbench</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="../reference/ref-47.htm">CVS</a>
-<br><a href="../reference/ref-33.htm">Synchronize view</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-117.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-117.htm
deleted file mode 100644
index 91b251d..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-117.htm
+++ /dev/null

@@ -1,78 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Sharing a new project using CVS</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Sharing a new project using CVS</H1>
-
-<P>There are several scenarios that can occur when sharing a project using CVS. 
-The most common scenario is sharing a new project using CVS when the project 
-does not already exist remotely.
-</P>
-  
-<P>To share a new project using CVS:
-</P>
-
-<ol>
-  <li>In one of the navigation views, select the project to be shared.</li>
-  <li>Select <b>Team &gt;</b> <b>Share Project...</b> from the project's pop-up 
-    menu. The Share Project wizard opens.</li>
-  <li>From the list of available repository providers, choose <b>CVS</b> and click 
-    <b>Next </b>to go to the next page. <b>(Note</b>: If CVS is not present in 
-    the list, it may be disabled. Clicking on the <strong>Show All Wizards</strong> 
-    button should make it visible.)</li>
-  <li>Select the target repository from the list of known repositories or, if 
-    the target repository is not in this list, choose to create a new repository 
-    location and click <b>Next</b>.</li>
-  <li>If entering a new repository location, enter the repository information 
-    and click <b>Next</b> when completed. <b>(Note</b>: this page is the same 
-    format as the <a href="tasks-92.htm">Creating a CVS repository location</a> 
-    wizard.)</li>
-  <li>Either choose to use the name of the local project as the remote project 
-    name or enter another name and click <strong>Next</strong>.</li>
-  <li>The final page shows you the resources of the new project as outgoing additions. 
-    You can choose to commit or ignore resources from this page. <b>(Note</b>: 
-    If the project already exists remotely, the page will show conflicts on any 
-    files that exist both locally and remotely. Only those files whose contents 
-    do not match are shown.)</li>
-  <li>Click <b>Finish</b> to share the project with the repository. You will be 
-    prompted to commit any resources in the new project that have not yet been 
-    committed or ignored. Choosing to do so will run the commit operation in the 
-    background. </li>
-</ol>
-
-<p><h4>Consequences for Linked Resources</h4>
-As mentioned in <a href="../concepts/concepts-13.htm">Linked resources</a>, different
-providers may handle linked resources differently.  For Team CVS, linked resources
-are allowed but ignored.  Specifically, projects which contain linked resources can be shared with CVS,
-but the linked resources themselves cannot be version controlled.</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-117a.htm">Project checked out with another CVS tool</a><br>
-<a href="tasks-96.htm">Checking out a project from a CVS repository</a><br>
-<a href="tasks-103.htm">Replacing resources in the Workbench</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="../reference/ref-47.htm">CVS</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-117a.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-117a.htm
deleted file mode 100644
index fd18431..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-117a.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Project checked out with another CVS tool</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Project checked out with another CVS tool</H1>
-
-<P CLASS="Para">It is possible to use a CVS project checked out using another 
-  CVS tool into Eclipse. A common concern for those migrating to Eclipse is that 
-  they already have their CVS project checked out on their local machine. You 
-  <em>don't</em> have to check out the contents again to create a project in Eclipse. 
-  When such a project is imported into Eclipse, the CVS plug-in may detect that 
-  CVS folders exist and auto-share the project. However, there are some instance 
-  were this does not occur and the project will need to be shared manually within 
-  Eclipse in order to enable the CVS Team menu operations.</P>
-<P>To share an CVS project that was already checked out:</P>
-
-<ol>
-  <li>In one of the navigation views, select the project to be shared.</li>
-  <li>Select <b>Team &gt;</b> <b>Share Project...</b> from the project's pop-up 
-    menu. The Share Project wizard opens.</li>
-  <li>From the list of available repository providers, choose <b>CVS</b> and click 
-    <b>Next </b>to go to the next page. (<b>Note</b>: If CVS is not present in 
-    the list, it may be disabled. Clicking on the <strong>Show All Wizards</strong> 
-    button should make it visible.)</li>
-  <li>The next page displays the sharing information stored in the CVS folder 
-    of the project. Click <strong>Finish</strong> to share the project and enable 
-    the CVS Team menu operations.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-117.htm">Sharing a new project using CVS</a>
-</p>
-
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-47.htm">CVS</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-117b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-117b.htm
deleted file mode 100644
index a648e9e..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-117b.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Changing the sharing of a project</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Changing the sharing of a project</H1>
-
-<P>If a project is shared with a CVS repository location, you can change the 
-sharing information so it is shared with a different repository location. The
-new location must map to the same repository but can have a different 
-connection method and/or user name.
-</p>
-
-<P>To change the sharing of a project:
-</p>
-
-<ol>
-  <li>In one of the navigation views, select the project whose sharing information is to be changed.</li>
-  <li>Select <b>Properties</b> from the pop-up menu. The properties dialog will open.</li>
-  <li>Select <b>CVS</b> to see the CVS properties page for the project.</li>
-  <li>Click <b>Change Sharing...</b>. A repository selection dialog opens containing 
-    the compatible repository locations. (<strong>Note</strong>: You can change 
-    the sharing to a non-compatible repository location by unchecking the<strong> 
-    Show only compatible repository locations</strong> button.)</li>
-  <li>Select the desired location and click <b>OK</b> to change the sharing for the project.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-92.htm">Creating a CVS repository location</a><br>
-<a href="tasks-95.htm">Changing the properties of a CVS Repository Location</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br>
-<a href="../reference/ref-47.htm">CVS</a><br>
-<a href="../reference/ref-32.htm">CVS Repositories view</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-118.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-118.htm
deleted file mode 100644
index 04b8d49..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-118.htm
+++ /dev/null

@@ -1,70 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Versioning projects in the repository</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Versioning projects in the repository</H1>
-
-<P> You can version a project in the repository without adding the project to 
-  the Workbench.
-</P>
-
-<ol>
-  <li>Switch to the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.team.cvs.ui.cvsPerspective)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  CVS Repository Exploring</a> perspective or add the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.team.ccvs.ui.RepositoriesView)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  CVS Repositories</a> view to the current perspective.</li>
-  <li>In the CVS Repositories view, expand a repository location and find the 
-    project you wish to version.</li>
-  <li>Right-click on the project and select <b>Tag as Version</b>.</li>
-  <li>Enter the name of the version you wish to create.</li>
-  <li>Click <b>OK</b> to close the dialog and create the version.</li>
-</ol>
-
-<p><em>Tip:</em> You can browse existing versions of your project by clicking 
-  on the <b>Details</b> button in the Tag Resources dialog. Clicking <b>Refresh 
-  from Repository</b> should populate the Existing Versions list. It is sometimes 
-  helpful to see existing versions before naming your new version.
-</p>
-
-<p><em>Tip:</em> If the version tag you wish to apply already exists on some of 
-  the resources to be versioned, you can perform a <b>Tag with Existing</b> instead. 
-  This operation will move an existing tag to the selected resources and can be 
-  used to move both version and branch tags. If the tag you wish to apply is not 
-  show in the list, you can click <b>Refresh from Repository</b>. If this doesn't 
-  find the tag, you can click <b>Configure Tags</b> which opens a dialog that 
-  allows you to search for tags on specific files in the repository.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-27b.htm">Branches</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-100.htm">Creating a version of a project</a><br>
-<a href="tasks-117.htm">Sharing a new project using CVS</a><br>
-<a href="tasks-119.htm">Viewing a file's revision history</a><br>
-<a href="tasks-100a.htm">Branching</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-47.htm">CVS</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-119.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-119.htm
deleted file mode 100644
index 5a11af9..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-119.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Viewing a file's revision history</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Viewing a file's revision history</H1>
-
-<P>Every time you commit a file to the CVS repository, a new revision is created. 
-  Each revision is identified by a number (for example, 1.1 or 1.11.3.5). Along 
-  with each revision is stored the author, the date, and a commit comment.
-</P>
-
-<P>To view the resource history for a file:
-</P>
-
-<ol>
-  <li>Select the file in one of the navigation views. From the context menu, choose <b>Team 
-    &gt; Show in Resource History</b>.</li>
-  <li>The CVS Resource History view will open and show a history for the selected 
-    file.</li>
-</ol>
-
-<p><em>Note:</em> The CVS Resource History view also shows you all version and branch 
-  tags that are associated with the file.
-</p>
-
-<p><em>Tip:</em> You can drag and drop a file from one of the navigation views into the CVS 
-  Resource History view instead of choosing the menu item.
-</p>
-
-<p><em>Tip:</em> By clicking on column headings in the CVS Resource History view 
-  you can change the sorting order of the items. </p>
-<p><em>Tip</em>: You can have the CVS Resource History view update automatically 
-  to the history of the file in the active editor by enabling the <strong>Link 
-  with Editor</strong> item in the view's toolbar.</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="../reference/ref-47.htm">CVS</a>
-<br><a href="../reference/ref-32a.htm">CVS Resource History view</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-14.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-14.htm
deleted file mode 100644
index 5fc9418..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-14.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Changing build order</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Changing build order</H1>
-
-<p>By default, the Workbench computes the build order by interpreting project 
-references as prerequisite relationships. Alternatively, you can explicitly 
-define the order in which projects are built.
-</p>
-
-<p>The Build Order preference page allows you to disable the <b>Use default build 
-order</b> option so that you can access the projects list and manipulate 
-the order of it.
-</p>
-
-<p>To define the order in which the Workbench performs builds projects:
-</p>
-
-<ol>
-  <li>Open the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.BuildOrder)")'>
-    <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-    <b>General &gt; Workspace &gt; Build Order</b></a>
-  preference page.</li>
-  <li>Ensure that the <b>Use default build order</b> checkbox is cleared. If 
-    it is selected, the buttons on this page are disabled, and builds are performed 
-    in the order of the project list.</li>
-  <li>(Optional) Click <b>Add Project</b> and <b>Remove Project</b> buttons to 
-    add and remove projects from the list.</li>
-  <li>Select one or more projects in the list and click <b>Up</b> or <b>Down </b>to 
-    to set the preferred project build order.</li>
-  <li>Click <b>OK</b> to close the Preferences dialog.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-22.htm">Builds</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-75.htm">Performing builds manually</a><br>
-<a href="tasks-16.htm">Performing builds automatically</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-16.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-16.htm
deleted file mode 100644
index 47e7cf0..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-16.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Performing builds automatically</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Performing builds automatically</H1>
-
-<P>To indicate that you want the Workbench to perform incremental builds whenever
-resources are saved:
-</P>
-
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workspace)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General &gt; Workspace</b></a>
-  preference page.</li>
-  <li>Select the <b>Build automatically</b> checkbox.</li>
-  <li>Click <b>OK</b> to close the Preferences page. The Workbench will automatically 
-    perform incremental builds of resources modified since the last build. Whenever 
-    a resource is modified, another incremental build occurs.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" width="159" height="27"><br>
-<a href="../concepts/concepts-22.htm">Builds</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" width="159" height="27"><br>
-<a href="tasks-75.htm">Performing builds manually</a><br>
-<a href="tasks-14.htm">Changing build order</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-17.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-17.htm
deleted file mode 100644
index bbfb689..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-17.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Saving resources automatically before a manual build</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Saving resources automatically before a manual build</H1>
-
-<P>To automatically save all modified resources in the Workbench before a manual 
-build is done:
-</P>
-
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workspace)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General &gt; Workspace</b></a>
-  preference page.</li>
-  <li>Select the <b>Save automatically before build</b> checkbox.</li>
-  <li>Click <b>OK</b> to close the Preferences page.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" width="159" height="27"><br>
-<a href="../concepts/concepts-22.htm">Builds</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" width="159" height="27"><br>
-<a href="tasks-73.htm">Building resources</a><br>
-<a href="tasks-75.htm">Performing builds manually</a><br>
-<a href="tasks-14.htm">Changing build order</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-18.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-18.htm
deleted file mode 100644
index 75a9b7b..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-18.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Linking the Navigator view to the active editor</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Linking the Navigator view to the active editor</H1>
-
-<P>When you have multiple files open for editing, you can configure one of the navigation views to automatically bring an open file to the foreground (make its editor 
-  session the active editor) every time you select that open file in one of the navigation views. There are two ways to set this.</P>
-
-<ol>
-  <li>From the Navigator menu, select <b>Link With Editor.</b></li>
-  <li>Click on the Link With Editor icon <img src="../images/synced.png" alt="Link with editor icon" >on 
-    one of the navigation bars.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-6.htm">Editors</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-46.htm">Opening files for editing</a><br>
-<a href="tasks-51.htm">Associating editors with file types</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1a.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-1a.htm
deleted file mode 100644
index 5e136dc..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1a.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working with perspectives</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Working with perspectives</H1>
-<p>Perspectives define the initial set and layout of views in the Workbench window. 
-  They provide a set of functionality aimed at accomplishing a specific type of 
-  task or working with specific types of resources.
-</p>
-
-<p>
-See the Related tasks links for more details.
-</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a><br>
-<a href="../concepts/concepts-5.htm">Views</a><br>
-<a href="../concepts/concepts-21.htm">Fast views</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-28.htm">Switching between perspectives</a><br>
-<a href="tasks-31.htm">Specifying the default perspective</a><br>
-<a href="tasks-9f.htm">Opening perspectives</a><br>
-<a href="tasks-24.htm">Changing where perspectives open</a><br>
-<a href="tasks-9k.htm">Configuring perspectives</a><br>
-<a href="tasks-9i.htm">Saving a user defined perspective</a><br>
-<a href="tasks-9d.htm">Deleting a user defined perspective</a><br>
-<a href="tasks-9j.htm">Resetting perspectives</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-1b.htm
deleted file mode 100644
index 565182a..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1b.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working with views and editors</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Working with views and editors</H1>
-<p>Views and editors are the main visual entities which appear in the Workbench. 
-  In any given perspective there is a single editor area, which can contain multiple 
-  editors, and a number of surrounding views which provide context.
-</p>
-
-<p>The Workbench provides a number of operations for working with views and editors.
-See the Related tasks links for more details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-5.htm">Views</a><br>
-<a href="../concepts/concepts-6.htm">Editors</a><br>
-<a href="../concepts/concepts-21.htm">Fast views</a><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-3.htm">Opening views</a><br>
-<a href="tasks-3e.htm">Moving and docking views</a><br>
-<a href="tasks-3h.htm">Rearranging tabbed views</a><br>
-<a href="tasks-9b.htm">Creating fast views</a><br>
-<a href="tasks-46.htm">Opening files for editing</a><br>
-<a href="tasks-51.htm">Associating editors with file types</a><br>
-<a href="tasks-52.htm">Editing files outside the Workbench</a><br>
-<a href="tasks-3g.htm">Tiling editors</a><br>
-<a href="tasks-3i.htm">Maximizing a view or editor</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1c.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-1c.htm
deleted file mode 100644
index 73d1c8a..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1c.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Navigating and finding resources</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Navigating and finding resources</H1>
-
-<p>The Workbench provides a number of mechanisms for navigating and finding resources.
-See the Related tasks links for more details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/cnav.htm">Navigator view</a><br>
-<a href="../concepts/csearchview.htm">Search view</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-46ag.htm">Finding a resource quickly</a><br>
-<a href="tasks-84b.htm">Searching for files</a><br>
-<a href="tasks-84.htm">Searching for text within a file</a><br>
-<a href="tasks-48.htm">Sorting resources in the Navigator view</a><br>
-<a href="tasks-48b.htm">Showing or hiding files in the Navigator view</a><br>
-<a href="tasks-46bg.htm">Narrowing the scope of the Navigator view</a><br>
-  <a href="tasks-18.htm">Linking the Navigator view to the active editor</a> </p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1d.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-1d.htm
deleted file mode 100644
index f3d92a2..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1d.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Bookmarks, tasks and other markers</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Bookmarks, tasks and other markers</H1>
-
-<p>Markers are objects that may be associated with Workbench resources.
-There are many uses of markers in the Workbench, including providing
-support for bookmarking resources or locations within resources, tracking
-ongoing tasks, or displaying error messages. See the related tasks section
-for more details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" width="159" height="27"><br>
-<a href="../concepts/cbookmrk.htm">Bookmarks</a><br>
-<a href="../concepts/ctskview.htm">Tasks view</a><br>
-<a href="../concepts/concepts-11.htm">Markers</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" width="159" height="27"><br>
-<a href="tasks-81.htm">Creating a bookmark within a file</a><br>
-<a href="tasks-81b.htm">Creating a bookmark for an entire file</a><br>
-<a href="tasks-82.htm">Deleting a bookmark</a><br>
-<a href="tasks-77.htm">Adding line items in the Tasks view</a><br>
-<a href="tasks-77b.htm">Associating a task with a resource</a><br>
-<a href="tasks-78.htm">Deleting tasks</a><br>
-<a href="tasks-79.htm">Filtering the Task view</a><br>
-<a href="tquickfix.htm">Automatically fixing problems</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1e.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-1e.htm
deleted file mode 100644
index 0373043..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1e.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working with projects, folders and resources</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Working with projects, folders and files</H1>
-
-<p>There are three different types of resources in the workbench: projects, folders,
-and files.  Projects are the largest structural unit used by the Workbench. Projects contain
-folders and files, and they can be opened, closed, or built. Folders can contain other folders 
-and files. The Workbench provides a number of mechanisms for working with projects, folders 
-and files.  See the related tasks section for more details.
-</p>
-<p>
-Folders and files directly below projects can be linked to locations in the file system
-outside of the project's location.  These special folders and files are called 
-<a href="../concepts/concepts-13.htm">linked resources</a>.
-</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-2.htm">Workbench</a><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/concepts-17.htm">Resource hierarchies</a><br>
-<a href="../concepts/concepts-13.htm">Linked resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-42.htm">Creating a project</a><br>
-<a href="tasks-47.htm">Closing projects</a><br>
-<a href="tasks-42b.htm">Deleting projects</a><br>
-<a href="tasks-43.htm">Creating a folder</a><br>
-<a href="tasks-44.htm">Creating a file</a><br>
-<a href="tasks-45.htm">Creating linked resources</a><br>
-<a href="tasks-63.htm">Moving resources</a><br>
-<a href="tasks-63cg.htm">Copying resources</a><br>
-<a href="tasks-66.htm">Renaming resources</a><br>
-<a href="tasks-67.htm">Deleting resources</a><br>
-<a href="tasks-49.htm">Viewing resources properties</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1f.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-1f.htm
deleted file mode 100644
index 74ac211..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1f.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working with local history</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Working with local history</H1>
-
-<p>A local edit history of a file is maintained when you create or modify a file. 
-Each time you edit and save the file, a copy is saved so that you can replace 
-the current file with a previous edit or even restore a deleted file.
-You can also compare the contents of 
-all the local edits. Each edit in the local history is uniquely represented 
-by the date and time the file was saved. See the Related tasks links for more
-details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-17a.htm">Local history</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-70.htm">Comparing resources with the local history</a><br>
-<a href="tasks-87.htm">Replacing a resource with local history</a><br>
-<a href="tasks-87b.htm">Restoring deleted resources from local history</a><br>
-<a href="tasks-88.htm">Setting local history preferences</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1g.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-1g.htm
deleted file mode 100644
index 302c684..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1g.htm
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Using the help system</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Using the help system</H1>
-
-<p>The Workbench provides a number of ways to provide help information, including 
-context sensitive help and extensive online documentations. See the Related 
-tasks links for more details. </p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" width="159" height="27"><br>
-<a href="../concepts/chelpsys.htm">Online help system</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" width="159" height="27"><br>
-<a href="tf1help.htm">Accessing context sensitive help</a><br>
-<a href="taccess.htm">Accessing and navigating online help</a><br>
-<a href="tsearch.htm">Searching online help</a><br>
-<a href="tfonts.htm">Setting help fonts and colors for accessibility</a><br>
-<a href="tchgbrws.htm">Changing the web browser used by the help system</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1h.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-1h.htm
deleted file mode 100644
index 725056d..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1h.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working in the team environment</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Working in the team environment with CVS</H1>
-
-<p>The Workbench provides tools to manage, share and synchronize resources. The 
-  CVS standard is supported by default. See the Related tasks links below for 
-  more details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-1i.htm">Working with a CVS repository</a><br>
-<a href="tasks-1j.htm">Working with projects shared with CVS</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1i.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-1i.htm
deleted file mode 100644
index 0d0f30c..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1i.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working with a CVS repository</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Working with a CVS repository</H1>
-
-<p>In the CVS team programming environment, team members do all of their work 
-in their own Workbenches, isolated from others. Eventually they will want to 
-share their work. They do this via a CVS repository. The Workbench provides 
-a number of mechanisms which support working with CVS repositories. See the 
-Related tasks links for more details. </p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-92.htm">Creating a CVS repository location</a><br>
-<a href="tasks-94.htm">Discarding a CVS repository location</a><br>
-<a href="tasks-93.htm">Refreshing the CVS Repositories view</a><br>
-<a href="tasks-110.htm">Discovering branch and version tags</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1j.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-1j.htm
deleted file mode 100644
index d0d38c6..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1j.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working with projects shared with CVS</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Working with projects shared with CVS</H1>
-
-<p>The Workbench provides a number of mechanisms which support working with projects 
-shared via CVS. See the Related tasks links for more details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-117.htm">Sharing a new project using CVS</a><br>
-<a href="tasks-117a.htm">Project checked out with another CVS tool</a><br>
-<a href="tasks-96.htm">Checking out a project from a CVS repository</a><br>
-<a href="tasks-96a.htm">Checking out a module from a CVS repository</a><br>
-<a href="tasks-cvs-10.htm">Disconnecting a project from CVS</a><br>
-<a href="tasks-cvs-11.htm">Setting the CVS keyword substitution mode</a><br>
-<a href="tasks-107b.htm">Enabling the CVS resource decorations</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1k.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-1k.htm
deleted file mode 100644
index 294dcfb..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1k.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Versioning</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Versioning</H1>
-
-<p>Resources can be versioned in order to capture a snapshot of their current state
-at one specific point in time. See the Related tasks links for more details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-27.htm">Versions</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-100.htm">Creating a version of a project</a><br>
-<a href="tasks-107b.htm">Enabling the CVS resource decorations</a><br>
-<a href="tasks-118.htm">Versioning projects in the repository</a><br>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-2.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-2.htm
deleted file mode 100644
index 77cb89e..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-2.htm
+++ /dev/null

@@ -1,78 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Upgrading Eclipse</title>
-</head>
-
-<BODY BGCOLOR="#ffffff">
-
-<h1>Upgrading Eclipse</h1>
-<p>
-If you are upgrading to a newer release of Eclipse from an older release, there are
-simple steps to follow to migrate your workspace to the new release.  Your workspace
-is the directory on disk that contains all of your project files, as well as meta-data such
-as preferences you may have customized.  The steps to follow for upgrading depend on
-whether or not you used the &quot;-data&quot; command line argument when starting 
-Eclipse.  The &quot;-data&quot; argument is recommended because it clearly specifies the 
-location of your workspace.
-</p>
-<p><i>Tip:</i> It doesn't hurt to make a backup of your workspace before
-upgrading.  After you've upgraded your workspace, you won't be able to use it
-again with an older version of Eclipse.  If you ever want to go &quot;back in time&quot;
-to an earlier release, you'll need that backup!
-</p>
-
-<p>The workspace chooser dialog allows the user choose the location of the workspace and is
-shown to the user on first startup in the absence of a -data argument. The default location 
-provided by this dialog will be a "workspace" child of the user's home directory 
-(for example, C:\Documents and Settings\UserName\workspace.)</p> 
-<p>New users with 3.1 should just leave this default, or specify some other location, 
-  but it's not recommended that they place it under the eclipse install directory. They should 
-  not copy the workspace, as the workspace can contain metadata with absolute file system paths, 
-  which will be invalid if the workspace is copied elsewhere.</p>
-<p>In Eclipse 3.0 and earlier, Eclipse's default location for the workspace was 
-  under the Eclipse directory. For example, if the eclipse.exe was in D:\eclipse-SDK-3.0.1\eclipse, 
-  then the default workspace location would be D:\eclipse-SDK-3.0.1\eclipse\workspace.</p>
-<p>To load a workspace created using 3.0 or earlier, they should just point to 
-  the old workspace directory using the workspace chooser, whether it's under 
-  the old install directory or elsewhere.</p>
-<p>&nbsp;</p>
-<h2>Users who use &quot;-data&quot;</h2>
-<p>
-If you were previously using the &quot;-data&quot; argument to start Eclipse, your 
-upgrade path is much easier:</p>
-<ol>
-<li>Install the new version of Eclipse in a new location, separate from any old version
-of Eclipse.</li>
-<li>Start this new version of Eclipse, using the &quot;-data&quot; command line argument to 
-point to your old workspace location.</li>
-</ol>
-<p>See the example in the previous section for an illustration.</p>
-
-<h2>Adding third party plug-ins</h2>
-<p>
-If you have installed extra plug-ins in your Eclipse environment, you will need to add
-these new plug-ins to each new build or version of Eclipse you install.  Before you do
-this, refer to the documentation for those plug-ins to ensure they are compatible
-with the version of Eclipse you are moving to.  There are several ways to add these
-extra plug-ins to your new Eclipse install:</p>
-<ol>
-<li>Copy the directories for each plug-in into the &quot;plugins&quot; directory of your
-new Eclipse version.</li>
-<li>Use an Eclipse update site to re-install those extra plug-ins or features in the
-new version of Eclipse.</li>
-<li>If you are using product extensions, simply copy the &quot;links&quot; directory
-into the new Eclipse version install directory.  For more details on product extensions,
-see the documentation in the Platform Plug-in Developer Guide, under <b>Programmer's
-Guide &gt; Packaging and delivering Eclipse based products &gt; Product extensions</b>.</li>
-</ol>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-20.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-20.htm
deleted file mode 100644
index 17f151b..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-20.htm
+++ /dev/null

@@ -1,136 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Changing fonts and colors</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Changing fonts and colors
-</H1>
-
-<p>By default, the Workbench uses the fonts and colors provided by the operating 
-  system. However, there are a number of ways that this behavior can be customized. 
-</p>
-
-<h2>Fonts</h2>
-
-<p>The Workbench lets you directly configure the following fonts: </p>
-
-<dl>
-  <dt>Banner Font</dt>
-  <dd>Used in PDE editors, welcome pages and in the title area of many wizards. 
-    For instance the New Project wizard uses this font for the top title.</dd>
-  <dt>Dialogue Font</dt>
-  <dd>Used for widgets in dialogs.</dd>
-  <dt>Header Font</dt>
-  <dd>Used as a section heading. For instance the Welcome page for the Eclipse 
-    Platform uses this font for the top title.</dd>
-  <dt>Text Font</dt>
-  <dd>Used in text editors.</dd>
-  <dt>CVS Console Font</dt>
-  <dd>Used in the CVS console.</dd>
-  <dt>Ignored Resource Font</dt>
-  <dd>Used to display resources that are ignored from CVS.</dd>
-  <dt>Outgoing Change Font</dt>
-  <dd>Used to display outgoing changes in CVS.</dd>
-  <dt>Console Font (defaults to text font)</dt>
-  <dd>Used by the debug console.</dd>
-  <dt>Detail Pane Text Font (defaults to text font)</dt>
-  <dd>Used in the detail panes of debug views.</dd>
-  <dt>Memory View Table Font (defaults to text font)</dt>
-  <dd>Used in the table of the memory view.</dd>
-  <dt>Java Editor Text Font (defaults to text font)</dt>
-  <dd>Used by Java editors.</dd>
-  <dt>Properties File Editor Text Font (defaults to text font)</dt>
-  <dd>Used by Properties File editors.</dd>
-  <dt>Compare Text Font (defaults to text font)</dt>
-  <dd>Used by textual compare/merge tools.</dd>
-  <dt>Java Compare Text Font (defaults to text font)</dt>
-  <dd>Used by Java compare/merge tools.</dd>
-  <dt>Java Properties File Compare Text Font (defaults to properties file editor 
-    text font )</dt>
-  <dd>Used by Java properties file compare/merge tools.</dd>
-  <dt>Part Title Font (defaults to properties file editor text font )</dt>
-  <dd>Used for view and editor titles. <strong>Note:</strong> It is recommended 
-    that this font not be bold or italic because the workbench will use bold and 
-    italic versions of this font to display progress.</dd>
-  <dt>View Message Font (defaults to properties file editor text font )</dt>
-  <dd>Used for messages in the view title bar (if present).</dd>
-  
- </dl>
-
-<p>To change these fonts:
-</p>
-
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.ColorsAndFonts)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General &gt; Appearance &gt; Colors and Fonts</b></a>
-  preference page.</li>
-  <li>Select the font you want to change.</li>
-  <li>Click <b>Change</b>.</li>
-  <li>Use the dialog which opens to select a font.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p><strong>Note:</strong> You can also click <b>Use System Font</b> to set the 
-  font to a reasonable value chosen by the operating system. For example, on Windows 
-  this will use the font selected in the Display Properties control panel.</p>
-
-<p>Plug-ins that use other fonts may also provide preference entries to allow them to
-be customized. For example, the Java Development Tools provide a setting for controlling
-the font used by the Java editor (see <b>Java &gt; Java Editor Text Font</b> on the preferences page).
-</p>
-
-<p>In addition to the above, some text is always displayed in the system font. For example, 
-the navigator tree always does this. To change the font used in these areas, you can use the
-configuration tools provided by the operating system (for example, the Display Properties control panel on
-Windows, or the .Xdefaults file in Motif).
-</p>
-
-<h2>Colors</h2>
-
-<p>To set the colors used by the Workbench to display error text and hyperlink text:
-</p>
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.ColorsAndFonts)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General &gt; Appearance &gt; Colors and Fonts</b></a>
-  preference page.</li>
-  <li>Select the color you want to change in the tree view and click the color 
-    bar on the right.</li>
-  <li>Use the dialog which opens to select a color.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p>Plug-ins that use other colors may also provide preference entries to allow them to
-be customized. For example, the searching support provides a preference for controlling
-the color used to display potential matches
-(see the <b>Foreground color for potential matches</b> item on the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.search.preferences.SearchPreferencePage)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>General &gt; Search</b></a> preference page).
-</p>
-
-<p>In general, the Workbench uses the colors that are chosen by the operating 
-  system. To change these colors you can use the configuration tools provided 
-  by the system (for example, the Display Properties control panel on Windows, 
-  or the .Xdefaults file in Motif). </p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/accessibility/fontsandcolors.htm">Fonts and Colors in Eclipse</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-24.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-24.htm
deleted file mode 100644
index 9270c63..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-24.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Changing where perspectives open</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>Changing where perspectives open</H1>
-
-<p>You can change the default behavior for how perspectives are opened in the Workbench.
-</p>
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Perspectives)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General &gt; Perspectives</b></a> preference page.</li>
-  <li>Select either <b>In the same window</b> or <b>In a new window</b> from the
-	<b>Open a new perspective</b> group.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-
-<p CLASS="Para" Label="Type"><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-9f.htm">Opening perspectives</a><br>
-<a href="tasks-31.htm">Specifying the default perspective</a><br>
-<a href="tasks-28.htm">Switching between perspectives</a><br>
-<a href="tasks-9k.htm">Configuring perspectives</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-28.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-28.htm
deleted file mode 100644
index a04f362..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-28.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Switching between perspectives</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Switching between perspectives</H1>
-<P> Open perspectives are represented by icons on the perspective bar. When you 
-  have more than one perspective open, you can switch between them by clicking 
-  the icons on the shortcut bar. </P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." width="159" height="27"><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" width="159" height="27"><br>
-<a href="tasks-9f.htm">Opening perspectives</a><br>
-<a href="tasks-24.htm">Changing where perspectives open</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-3.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-3.htm
deleted file mode 100644
index 7568a69..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-3.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Opening views</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Opening views</H1>
-<P>Perspectives offer pre-defined combinations of views and editors. 
-  To open a view that is not included in the current perspective, select <b>Window 
-  &gt; Show View</b> from the main menu bar.
-</P>
-
-<P>You can create <i>fast views</i> to provide quick access to views that you 
-  use often. </P>
-
-<P>After adding a view to the current perspective, you may wish 
-  to save your new layout by clicking 
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.savePerspective")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Window &gt; Save Perspective As...</b></a>.
-</P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." width="159" height="27"><br>
-<a href="../concepts/concepts-5.htm">Views</a><br>
-<a href="../concepts/concepts-21.htm">Fast views</a><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" width="159" height="27"><br>
-<a href="tasks-3e.htm">Moving and docking views</a><br>
-<a href="tasks-9b.htm">Creating fast views</a><br>
-<a href="tasks-3i.htm">Maximizing a view or editor</a><br>
-<a href="tasks-9j.htm">Resetting perspectives</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-31.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-31.htm
deleted file mode 100644
index 1ba296d..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-31.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Specifying the default perspective</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Specifying the default perspective</H1>
-<P>The default perspective is indicated in the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-Select Perspective</a> dialog (accessible via the <b> Window &gt; Open Perspective 
-  &gt; Other... </b> menu). The pre-defined default perspective is indicated by the 
-  word default in brackets following the perspective name, for example, <strong>Resource 
-  (default)</strong>. </P>
-
-<P>To change the default perspective:</P>
-<ol>
-  <li>Open the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Perspectives)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General &gt; Perspectives</b></a> preference page.</li>
-  <li>Select the perspective that you want to define as the
-    default from the list of available perspectives, and click <b>Make Default</b>.
-    The default indicator moves to the perspective that you selected.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." width="159" height="27"><br>
-<a href="../concepts/concepts-2.htm">The Workbench</a><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" width="159" height="27"><br>
-<a href="tasks-9f.htm">Opening perspectives</a><br>
-<a href="tasks-24.htm">Changing where perspectives open</a><br>
-<a href="tasks-9k.htm">Configuring perspectives</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-33.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-33.htm
deleted file mode 100644
index 6b72429..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-33.htm
+++ /dev/null

@@ -1,82 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Inspecting the current configuration</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Inspecting the current configuration</H1>
-
-<p>The
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.help.aboutAction")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Help &gt; About Eclipse SDK</b></a>
-  dialog shows most of the important information about the features and plug-in configured in 
-  the product. To find out further detailed information about the current configuration:
-</p>
-
-<ol>
-  <li>Open the update configuration manager by clicking
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.update.manageConfiguration")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Help &gt; Software Updates &gt; Manage Configuration</b></a>.
-  This opens the Product Configuration dialog.</li>
-  <li>In the Product Configuration dialog expand the root node (current&nbsp; 
-  configuration).
-    The first tier of items are locations on the local computer where the files
-    for features and plug-ins are stored. For a typical product, all features
-    are installed in a single directory sub-tree. However, a feature that is
-    installed as an extension of another product are usually located in a
-    separate directory sub-tree.</li>
-  <li>Expand the location to see the feature versions installed there.</li>
-  <li>The nesting of the features indicates which child features are included in
-    a given parent feature. Nested features act as a unit.</li>
-  <li>Select a feature version and click <b>Show Properties</b> to open the 
-  Properties dialog which presents more detailed information about the selected feature.</li>
-  <li>Click <b>Show Disabled Features</b> filter on the toolbar of the Product
-    Configuration dialog. Any feature versions that are disabled are now
-    shown (you might not have any). Disabled feature versions are ones that are
-    installed on the local computer but excluded from the current configuration.
-    At most one version of any given feature can be present in a given
-    configuration; usually the ones with the lower version numbers will be in a
-    disabled state.</li>
-  <li>In the Properties dialog of a feature, click <b>Status</b> to find out whether
-    the selected feature is configured exactly as packaged. The status will show
-    when a feature's plug-ins are present at different versions, or disabled due
-    to missing prerequisite plug-ins that are expected to be supplied by some
-    other feature.</li>
-</ol>
-
-<p>
-In this dialog you can revert to a previous install configuration, view the installation history, or
-even add another eclipse product extension. A product extension is a local folder that has a similar
-file layout as the eclipse installation, but with a .eclipseextension marker (instead of .eclipseproduct). 
-If you add a product extension, make sure there are no duplicate features in the extension
-you add.
-</p>
-<p>
-When the install wizard is used to install features in a user selected location, that location
-automatically becomes an eclipse product extension.
-</p>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-25.htm">Features</a>
-</P>
-
-<P><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-34.htm">Installing new features with the update manager</a><br>
-<a href="tasks-36.htm">Updating features with the update manager</a><br>
-<a href="tasks-37.htm">Update Policy</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-34.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-34.htm
deleted file mode 100644
index c2f6b37..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-34.htm
+++ /dev/null

@@ -1,93 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Installing new features with the update manager</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Installing new features with the update manager</H1>
-
-<p>To locate and install a new feature into a product (ordinarily requires web 
-  access):
-</p>
-
-<ol>
-  <li>Open the Install Wizard by clicking
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.update.findAndInstallUpdates")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Help &gt; Software Updates &gt; Find and Install...</b></a>.
-  This opens the wizard. </li>
-  <li>Select the second button, &quot;<b>Search for new features to install</b>&quot; and 
-  click <b>Next</b>.</li>
-  <li>Create a bookmark for an update site where Eclipse features and plug-ins 
-  are published. In the sites to search list, select <b>Add&nbsp; Update Site</b> to 
-  add a remote site, or <b>Add Local Site</b> if the site is available on a local drive 
-  (including a CD), or <b>Add Archived Site</b>, when the site is available locally 
-  but is packaged as a jar or zip file.</li>
-  <li>In the add site dialog, give the site a name such as 
-    &quot;CompanyA&quot; and enter the URL such as
-	&quot;http://companyA.example.com/eclipseupdates&quot;.</li>
-  <li>After adding the site, expand it to the
-    categories of feature versions available at that update site. This will
-    contact the web site to discover what features are available.</li>
-  <li>Select the categories you want to search and click <b>Next</b>.</li>
-  <li>Wait for the search to finish and selecting the features to be added. You 
-  can view the description or more detailed properties for any feature by 
-  selecting the feature and pressing the &quot;Properties&quot; button.</li>
-  <li>Once you're decided which features to install, click <b>Next</b>.</li>
-  <li>Carefully review the license agreements for the  features. If the
-    terms of all these licenses are acceptable, check &quot;I accept the terms
-    in the license agreements&quot;. Do not proceed to download the features if
-    the license terms are not acceptable.</li>
-  <li>If a feature selected for install include optional features, a page will
-    show up allowing you to select whether you want them installed or not.
-    Optional features typically carry functionality that is not essential for
-    proper functioning of the main feature.</li>
-  <li>The Install Location page controls where the new feature's files are to be
-    installed on the local computer. Select the directory into which the product
-    is installed and hit <b>Next</b>. (If the product is installed in a
-    directory to which you do not have write access, you should contact your
-    system administrator and get them to install this feature so that it will be
-    generally available. The other option is to click <b>Add</b> and point to a 
-  directory to which you do have write access.</li>
-  <li><p>Feature versions can be digitally signed by the company that provides
-    them. This allows you to verify more easily that the features and
-    plug-ins that are about to be downloaded and installed are coming from a
-    trusted supplier.</p><br><p><b>Warning:</b> Because of the possibility of harmful or even
-    malicious plug-ins, you should only download features from parties that
-    you trust.</p><br> <p>Click <b>Install</b> to allow the downloading and installing
-    to proceed.</p></li>
-  <li>Once the new feature and plug-ins have been downloaded successfully and
-    their files installed into the product on the local computer, a new
-    configuration that incorporates these features and plug-ins will be
-    formulated. Click <b>Yes</b> when asked to exit and restart the workbench for the
-    changes to take effect. To add other new features at the same time before
-    restarting, click <b>No</b> and repeat. If this was a new feature and can be 
-  dynamically installed into the current configuration, you will also be 
-  presented with a <b>&quot;Apply Now&quot;</b> button. This will not restart the 
-  platform, but configures the feature and the plug-ins into the current 
-  configuration.</li>
-</ol>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-25.htm">Features</a>
-</P>
-
-<P>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-33.htm">Inspecting the current configuration</a><br>
-<a href="tasks-36.htm">Updating features with the update manager</a><br>
-<a href="tasks-38.htm">Restoring a saved configuration</a>
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-35.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-35.htm
deleted file mode 100644
index e264c9a..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-35.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Configuration operations: enable, disable, or uninstall a feature</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Configuration operations: enable, disable, or uninstall a feature</H1>
-
-<p>Current configuration can be browsed, but it can also be operated on to 
-enable/disable/uninstall features, to revert to previous configurations, etc. Open the 
-configuration manager&nbsp; by clicking
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.update.manageConfiguration")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Help &gt; Software Updates &gt; Manage Configuration</b></a>.
-</p>
-
-<ol>
-  <li><b>Disable a feature</b>: select the feature and click on the &quot;Disable&quot; 
-  feature action in&nbsp; the right pane of the dialog or in the context menu. 
-  The action is available only when the feature is currently enabled, and the 
-  feature is either an optional feature or a root feature (not included by other 
-  features).</li>
-  <li><b>Enable a feature</b>: Turn on disabled features filtering from the 
-  dialog toolbar, then select a disabled optional or root feature and click on 
-  the &quot;Enable&quot; feature action in&nbsp; the right pane of the dialog or in&nbsp; 
-  the context menu.</li>
-  <li><b>Uninstall </b>a feature: features installed by you using the update 
-  manager can be uninstalled, provided they are already disabled, or that they 
-  are optional or root features. If the feature is disabled, make sure you turn 
-  on the disabled features filtering from the dialog toolbar. Select the feature 
-  and click on the &quot;Uninstall&quot; feature action in the right page of the dialog or 
-  in the context menu. </li>
-</ol>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-25.htm">Features</a>
-</P>
-
-<P><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-34.htm">Installing new features with the update manager</a><br>
-<a href="tasks-36.htm">Updating features with the update manager</a><br>
-<a href="tasks-37.htm">Saving a configuration</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-36.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-36.htm
deleted file mode 100644
index 23324e3..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-36.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Updating features with the update manager</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Updating features with the update manager</h1>
-
-<p>To check to see whether there are updates for a product's existing features
-  (requires Internet access):
-</p>
-
-<ol>
-  <li>Click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.update.findAndInstallUpdates")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Help &gt; Software Updates &gt; Find and Install...</b></a> and select the 
-  first choice (search for updates). This will contact 
-    the Web sites associated with the product's features to discover what versions 
-    of those features are available. The potential upgrades are presented in on 
-  the next page.</li>
-  <li>Select the feature versions that you wish to upgrade, and click <b>Next</b>.</li>
-  <li>Carefully review the license agreements for the upgraded features. If the 
-    terms of all these licenses are acceptable, check &quot;I accept the terms 
-    in the license agreements.&quot; Do not proceed to download the features if 
-    the license terms are not acceptable.</li>
-  <li><p>Feature versions can be digitally signed by the company that provides them. 
-    This allows the user to verify more easily that the features and plug-ins 
-    that are about to be downloaded and installed are coming from a trusted supplier. </p><br>
-    <p><b>Warning:</b> Because of the possibility of harmful or even malicious plug-ins, 
-    you should only download features from parties that you trust. </p><br><p>Click 
-    <b>Install</b> to allow the downloading and installing to proceed.</p></li>
-  <li>Once all the features and plug-ins have been downloaded successfully and 
-    their files installed into the product on the local computer, a new configuration 
-    that incorporates these features and plug-ins will be formulated. Click <b>Yes</b> 
-    when asked to exit and restart the Workbench for the changes to take effect.</li>
-</ol>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-25.htm">Features</a>
-</P>
-
-<P><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-33.htm">Inspecting the current configuration</a><br>
-<a href="tasks-34.htm">Installing new features with the update manager</a><br>
-<a href="tasks-35.htm">Enable, disable or uninstall a feature</a><br>
-<a href="tasks-37.htm">Update policy control</a><br>
-<a href="tasks-37a.htm">Automatic update scheduler</a><br>
-<a href="tasks-38.htm">Restoring a saved configuration</a>
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-37.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-37.htm
deleted file mode 100644
index a463851..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-37.htm
+++ /dev/null

@@ -1,166 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Eclipse update policy control</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-
-<h1>Eclipse Update Policy Control</h1>
-
-<p>Eclipse Update allows users to search for updates to the currently installed 
-features. For each installed feature, Update uses the embedded URL to 
-connect to the remote server and search for new versions. If there are updates, 
-Eclipse allows users to initiate the install procedure. After downloading, 
-installing and restarting the platform, new feature version is ready for use.</p>
-<p>In companies with many users of the same Eclipse-based product (typically a 
-commercial one), several problems can arise from this model:</p>
-<ol>
-  <li>Updates for very large products (e.g. 500+ plug-ins) are also large. 
-  I/T support teams may not like the idea of hundreds of developers individually 
-  downloading 500MEG updates to their individual machines. In addition to the 
-  bandwidth hit, such a large download request may fail, leading to repeated 
-  attempts and increased developers' downtime.</li>
-  <li>Some companies explicitly don't want the developers downloading updates 
-  directly from the Internet. For example, they can set up a local support team 
-  that may not be ready to handle requests related to the version of the product
-    already available from the provider's update site. They may want to restrict updates and 
-  fixes to the internally approved list. Ideally, they would do that by setting 
-  up 'proxy' update sites on the LAN (behind the firewall).</li>
-  <li>Once updates are set in the proxy sites as above, administrators need a 
-  way of letting users know that updates are available.</li>
-</ol>
-<h2>2. Update policy to the rescue</h2>
-
-<h3>2.1 Support for creating local (proxy) update sites</h3>
-<p>First step for a product administrator would be to set up a local Eclipse 
-update site on a server connected to the company's LAN (behind the firewall). 
-The update site would be a subset of the product's update site on the Internet 
-because it would contain only features and plug-ins related to the updates that 
-the company wants applied at the moment. Technically, this site would be a 
-regular Eclipse update site with site.xml, feature and plug-in archives.</p>
-<p>Administrators would construct this site in two ways:</p>
-<ol>
-  <li>Product support teams would make a zip file of the update site readily 
-  available for this particular purpose. Administrators would simply need to 
-  download the zip file from the product support web page using the tool of 
-  their choice and unzip it in the local server. This approach is useful for 
-  very large zip files that require modern restartable downloading managers 
-  (those that can pick up where they left off in case of the connection 
-  problems).</li>
-  <li>Eclipse Update provides a tool to mirror remote update sites 
-  entirely or allow administrators to select updates and fixes to download.
-  This mirroring capability would be fully automated and would greatly simplify administrator's task 
-  but it relies on Update network connection support.</li>
-</ol>
-<h3>2.2 Common update policy control</h3>
-<p>Since features have the update site URL embedded in the manifest, they are unaware of the local 
-update sites set up by the administrators. It is therefore important to provide <b>
-redirection capability</b>. This and other update policy settings can be set for
-an Eclipse product by creating an update policy file and configuring Update to 
-use that file when searching.</p>
-<p>The file in question uses XML format and can have any name. The file can be set in
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.update.internal.ui.preferences.MainPreferencePage)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Preferences &gt; Install/Update</b></a>
-<font color="#0000FF"> </font>in the <b>Update Policy</b> field. The text field 
-is empty by default: users may set the URL of the update policy file. The file 
-is managed by the local administrator and is shared for all the product 
-installations. Sharing can be achieved in two ways:</p>
-<ul>
-  <li>If users install the product: users are told to open the preference page 
-  and enter the provided URL</li>
-  <li>If administrators install the product: administrators edit the file 'plugin_customization.ini' 
-  in the primary product feature and set the default value of the 'updatePolicyURL' 
-  property as follows:<br>
-  <br>
-&nbsp;&nbsp;&nbsp; <code>org.eclipse.update.core/updatePolicyURL = &lt;URL value&gt;<br>
-  </code><font color="#0000FF"></font><br>
-  <br>
-  This will cause all the installations to have this file set by default.</li>
-</ul>
-<p>The policy file must conform to the following DTD:</p>
-<blockquote>
-  <p><tt>&lt;?xml encoding=&quot;ISO-8859-1&quot;?&gt;</tt></p>
-  <p><tt>&lt;!ELEMENT update-policy (url-map)*&gt;</tt><br>
-  <tt>&lt;!ATTLIST update-policy</tt><br>
-  <tt>&gt;</tt></p>
-  <p><tt>&lt;!ELEMENT url-map EMPTY&gt;<br>
-  &lt;!ATTLIST url-map<br>
-  &nbsp;&nbsp;&nbsp; pattern&nbsp;&nbsp;&nbsp; CDATA #REQUIRED<br>
-  &nbsp;&nbsp;&nbsp; url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA
-  #REQUIRED<br>
-  &gt;</tt></p>
-</blockquote>
-<h4>url-map</h4>
-<ul>
-  <li><b>pattern</b> - a string that represents prefix of a feature ID (up to
-    and including a complete ID). A value of "*" matches all the features.</li>
-  <li><b>url</b> - a URL of the alternative update site that should be used if
-    the feature ID begins with the pattern. If the string is empty, features matching 
-    pattern will not be updateable.</li>
-</ul>
-<p>This element is used to override Update URLs embedded in feature manifests. When
-looking for new updates, Eclipse search will check the update policy (if 
-present) and check if <b>url-map</b> for the matching feature prefix is 
-specified. If a match is found, the mapped URL will be used <b> instead</b> of the 
-embedded one. This way, administrators can configure Eclipse products to search 
-for updates in the local server behind the firewall. Meanwhile, third-party
-features installed by Eclipse Update will continue to be updated using the
-default mechanism because they will not find matches in the policy.</p>
-<p>Several <b>url-map</b> elements may exist in the file. Feature prefixes can be 
-chosen to be less or more specific. For example, to redirect all Eclipse 
-updates, the pattern attribute would be <code>&quot;org.eclipse&quot;</code>. Similarly, it is 
-possible to use a complete feature ID as a pattern if redirection is required on 
-a per-feature basis.</p>
-<p>Patterns in the file may be chosen to progressively narrow the potential
-matches. This may result in multiple matches for a given feature. In this case,
-the <b>match with a longest pattern</b> will be used. For
-example:</p>
-<blockquote>
-<pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
-&lt;update-policy&gt;
-	&lt;url-map pattern=&quot;org.eclipse&quot; url=&quot;URL1&quot;/&gt;
-	&lt;url-map pattern=&quot;org.eclipse.jdt&quot; url=&quot;URL2&quot;/&gt;
-&lt;/update-policy&gt;</pre>
-</blockquote>
-<p>In the case above, all Eclipse features will be updated from URL1, except <code>org.eclipse.jdt</code> that will use URL2.</p>
-<p>Update policy files do not contain translatable strings and therefore do not
-require special NL handling. In general, the files should use UTF-8 encoding.</p>
-<h3>2.3 Automatic discovery of updates</h3>
-<p>The third part of the overall solution is covered by another 
-<a href="tasks-37a.htm">topic</a> but is mentioned here because it is an integral part 
-of the solution. <a href="tasks-37a.htm">Automatic updates</a> will allow Eclipse to run update search on a 
-specified schedule (on each startup (the default), once a day, once a week 
-etc.). </p>
-<h2>3. Summary </h2>
-<p>Here is the complete sequence of steps that comprise the solution:</p>
-<ol>
-  <li>Administrator allocates a server on the company LAN for hosting local 
-  product updates. Initially it contains no update sites. The machine must have
-    an HTTP server running.</li>
-  <li>Administrator sets up an update policy file on that server and instructs 
-  all users to set the update policy preference the provided URL.</li>
-  <li>As the product provider ships updates and fixes on their update sites,
-    administrator downloads supported updates onto the local server.</li>
-  <li>Automatic update executed at the scheduled frequency when the client's
-    product is up picks up the local 
-  updates and notifies the user</li>
-  <li>User chooses to install the discovered updates</li>
-</ol>
-
-<P>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-37a.htm">Automatic Update Scheduler</a><br>
-</P>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-37a.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-37a.htm
deleted file mode 100644
index 9c97bdb..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-37a.htm
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Automatic Update Scheduler</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-
-<h1>Automatic Update Scheduler</h1>
-<p>Eclipse Update is able to search for updates to the installed features 
-on a periodic basis without user assistance. The way this search is performed 
-will be configurable by the user via the preference page. Users will be able to 
-configure scheduling and downloading options.</p>
-<h3>Scheduling options</h3>
-<p>Each time an Eclipse-based product starts, update scheduler plug-in will 
-activate based on the chosen scheduling. Users will be able to choose between:</p>
-<ul>
-  <li>No automatic search</li>
-  <li>On each startup (default)</li>
-  <li>Every day at a specific time (i.e. 3:00PM) *</li>
-  <li>On a scheduled day of the week at a specific time (i.e. Monday 8:00AM) *</li>
-</ul>
-<p>* assuming the application is active. If the application is not active at a 
-scheduled time and the search is past due, it will immediately start on the next 
-startup</p>
-<h3>Downloading options</h3>
-<p>Scheduling options define occurrence of the automated search but do not 
-define what is actually happening when the search is due. Downloading options 
-control this behavior (this set of options is disabled if automatic search is 
-turned off). Users can choose between:</p>
-<ul>
-  <li>Search for updates and notify  when they are available (default)</li>
-  <li>Download new updates automatically and notify  when ready to install 
-  them</li>
-</ul>
-<p>In both cases, Update scheduler will create and initiate a search job that will execute in the background 
-when it is due based on the scheduling options. There will be no messages if no 
-updates were found. If there are updates, the behavior will depend on the 
-selected downloading option.</p>
-<h4>Search and notify</h4>
-<p>If search only is selected, a message box will open, notifying user that new 
-updates have been found:</p>
-<p><font color="#0000FF">New updates have been found for this product. Do you want to 
-download them?</font></p>
-<p><font color="#0000FF">[Yes] [No] </font></p>
-<p>If 'Yes' is pressed, a Update wizard will open, listing detected updates. The 
-same wizard is used when search for updates has been manually initiated using 
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.update.findAndInstallUpdates")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Help &gt; Software Updates &gt; Find and Install...</b></a>.</p>
-<p>If 'No' is pressed, dialog will close and the updates ignored.</p>
-<h4>Download new updates</h4>
-<p>If the second option has been selected (download updates automatically), the 
-search job will be scheduled as before, but when new updates are found, the 
-download will commence immediately. When all the features have been successfully 
-downloaded into the temp. space, a different message box will show up:</p>
-<p><font color="#0000FF">New updates have been found and downloaded. Do you want to install them?</font></p>
-<p><font color="#0000FF">[Yes] [No] </font></p>
-<p>If 'No' is pressed, dialog will close and all the data in the temporary space 
-will be deleted. If 'Yes' is pressed, installation will commence (only a 
-progress monitor will be shown - no wizards). </p>
-<p>If you choose not to install the downloaded features, but later launch the 
-Find and Install wizard for updating, the downloaded files will be reused 
-(they're cached), unless there are newer versions on the server or you have restarted eclipse. </p>
-
-<P>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-36.htm">Updating features with the update manager</a><br>
-</P>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-38.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-38.htm
deleted file mode 100644
index 37bf522..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-38.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Restoring a saved configuration</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Restoring a saved configuration</h1>
-
-<p>A previously saved configuration (or any configuration recorded in the history) 
-  can be restored, thereby backing out of the results of an unsuccessful upgrade. 
-  Restoring a saved configuration does not delete the files for feature and plug-in 
-  versions from the local computer; it merely ignores them and acts as it did 
-  when they were not present. To restore a saved configuration to be the current 
-  configuration:
-</p>
-
-<ol>
-  <li> Select
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.update.manageConfiguration")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Help &gt; Software Updates &gt; Manage Configuration</b></a> to 
-    open the Manage Configuration dialog. </li>
-  <li>In the Product Configuration view, click the Installation History icon and 
-    select the desired configuration. Click <b>Restore</b>.</li>
-  <li>Click <b>Yes</b> when asked to exit and restart the Workbench for the changes 
-    to take effect.</li>
-  <li>Expand the Current Configuration (and children) to confirm that the current 
-    configuration now matches the configuration saved earlier.</li>
-</ol>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-25.htm">Features</a>
-</P>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-33.htm">Inspecting the current configuration</a><br>
-<a href="tasks-37.htm">Update policy control</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-3e.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-3e.htm
deleted file mode 100644
index 6fb6e0e..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-3e.htm
+++ /dev/null

@@ -1,112 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Moving and docking views</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Moving and docking views</H1>
-
-<p>To change the location of a view in the current perspective:
-</p>
-
-<ol>
-  <li>Drag the view by its title bar. Do not release the left
-    mouse button yet.</li>
-  <li>As you move the view around the Workbench, the mouse pointer
-    changes to one of the <i>drop cursors</i> shown in the table below. The drop
-    cursor indicates where the view will be docked if you release the left mouse
-    button. To see the drop cursor change, drag the view over the left, right,
-    top, or bottom border of another view or editor.</li>
-  <li>When the view is in the location that you want, relative to
-    the view or editor area underneath the drop cursor, release the left mouse
-    button.</li>
-  <li>(Optional) If you want to save your changes, select
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.savePerspective")'>
-    <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-    <b>Window &gt; Save Perspective As...</b></a> from the main menu bar.</li>
-  <li>Note that a group of stacked views can be dragged using the empty space to
-    the right of the view tabs.</li>
-</ol>
-
-<p>You can also move a view by using the pop-up menu for the view. (Left-click
-on the icon at the left end of the view's title bar, or right-click anywhere
-else in the view's title bar).
-</p>
-
-<TABLE BORDER="1" cellspacing="0" cellpadding="5">
-  <THEAD>
-  </THEAD>
-  <TBODY>
-    <TR> 
-      <th COLSPAN="1" valign="bottom" align="left" height="38"> Drop cursor </th>
-      <th COLSPAN="1" valign="bottom" align="left" height="38"> Where the view 
-        will be moved to </th>
-    </TR>
-    <TR> 
-      <TD COLSPAN="1" align="center" height="38"> <P CLASS="Para"> <img src="../images/drop_top_source.png" alt=" Up icon" border="0" > 
-        </P></TD>
-      <TD COLSPAN="1" valign="top" align="left" height="38"> <P CLASS="Para"> 
-          Dock above: The view is docked above the view underneath the cursor.</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" align="center" height="38"> <P CLASS="Para"> 
-          <img src="../images/drop_bottom_source.png" alt="  Down icon" border="0" > 
-        </P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left" height="38"> <p CLASS="Para"> 
-          Dock below: The view is docked below the view underneath the cursor.</p> 
-      </TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" align="center" height="38"> <P CLASS="Para"><img align="texttop" border="0" src="../images/drop_right_source.png" alt="Right icon" > 
-        </P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left" height="38"> <p CLASS="Para"> 
-          Dock to the right: The view is docked to the right of the view underneath 
-          the cursor.</p></TD>
-    </TR>
-    <TR> 
-      <TD COLSPAN="1" align="center" height="38"> <img align="texttop" border="0" src="../images/drop_left_source.png" alt=" Left icon" > 
-      </TD>
-      <TD COLSPAN="1" valign="top" align="left" height="38"> Dock to the left: 
-        The view is docked to the left of the view underneath the cursor. </TD>
-    </TR>
-    <TR> 
-      <TD COLSPAN="1" align="center" height="38"> <img align="texttop" border="0" src="../images/drop_stack.png" alt=" Stack views" > 
-      </TD>
-      <TD COLSPAN="1" valign="top" align="left" height="38"> Stack: The view is 
-        docked as a Tab in the same pane as the view underneath the cursor. </TD>
-    </TR>
-    <TR> 
-      <TD COLSPAN="1" align="center" height="38"> <img align="texttop" border="0" src="../images/drop_invalid_source.png" alt=" Restricted icon" > 
-      </TD>
-      <TD COLSPAN="1" valign="top" align="left" height="38"> Restricted: You cannot 
-        dock the view in this area. </TD>
-    </TR>
-  </TBODY>
-</TABLE>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="../concepts/concepts-5.htm">Views</a><br>
-<a href="../concepts/concepts-21.htm">Fast views</a><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-3.htm">Opening views</a><br>
-<a href="tasks-9b.htm">Creating fast views</a><br>
-<a href="tasks-3i.htm">Maximizing a view or editor</a><br>
-<a href="tasks-9i.htm">Saving a user defined perspective</a><br>
-<a href="tasks-9j.htm">Resetting perspectives</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-3g.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-3g.htm
deleted file mode 100644
index 98afd69..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-3g.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Tiling editors</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Tiling editors</H1>
-
-<P>The Workbench allows you to have multiple files open in multiple editors. Unlike
-views, editors cannot be dragged outside the Workbench to create new windows.
-However, you can tile editor sessions within the editor area, in order to view
-source files side by side.
-</P>
-
-<ol>
-  <li>With two or more files open in the editor area, select one of the editor tabs.</li>
-  <li>Holding down the left mouse button, drag that editor over
-    the left, right, top or bottom border of the editor area. Notice that the
-    mouse pointer changes to a &quot;drop cursor&quot; that indicates where the
-    editor session will be moved when you release the mouse button.</li>
-  <li>(Optional) Drag the borders of the editor area or each
-    editor, to resize as desired.</li>
-</ol>
-
-<p>This is a similar operation to moving and docking views inside
-the Workbench, except that all editor sessions must be contained within the
-editor area.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-6.htm">Editors</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-46.htm">Opening files for editing</a><br>
-<a href="tasks-9.htm">Changing the placement of the tabs</a><br>
-<a href="tasks-68.htm">Comparing resources</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-3h.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-3h.htm
deleted file mode 100644
index ead3098..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-3h.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Rearranging tabbed views</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Rearranging tabbed views</H1>
-<p>In addition to dragging and dropping (docking) views inside the Workbench,
-you can rearrange the order of views within a tabbed notebook.
-</p>
-<ol>
-  <li>Click on the tab of the view that you want to move and drag
-    it to where you want it. A stack symbol
-	<img border="0" src="../images/drop_stack.png" alt="drop stack image" >
-	appears as you drag the view across other view tabs.</li>
-  <li>Release the mouse button when you have the view tab in the
-    desired location. The view that you selected is now moved.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-5.htm">Views</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-3e.htm">Moving and docking views</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-3i.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-3i.htm
deleted file mode 100644
index 6f7717d..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-3i.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Maximizing a view or editor</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Maximizing a view or editor</H1>
-<P>You can temporarily maximize a view or editor so that it fills the Workbench window.
-</P>
-
-<ol>
-  <li>Open the menu for the view or editor by clicking the icon at the far left 
-    of its title bar. (You can get the same effect by right-clicking anywhere 
-    in the title bar.)</li>
-  <li>Select <b>Maximize</b>. </li>
-</ol>
-
-<p>To restore the view or editor to its previous position and size:</p>
-
-<ol>
-  <li>Open the menu again.</li>
-  <li>Select <b>Restore</b>.</li>
-</ol>
-
-<p><em>Tip:</em> You can also maximize or restore a view or editor by double-clicking 
-  its title bar or using the <strong>Maximize/Restore </strong>icon.</p>
-  <img border="0" src="../images/max.png" alt="Maximize/Restore Icon">
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." width="159" height="27"><br>
-<a href="../concepts/concepts-5.htm">Views</a><br>
-<a href="../concepts/concepts-21.htm">Fast views</a><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" width="159" height="27"><br>
-<a href="tasks-3.htm">Opening views</a><br>
-<a href="tasks-3e.htm">Moving and docking views</a><br>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-42.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-42.htm
deleted file mode 100644
index 05779d2..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-42.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating a project</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Creating a project</H1>
-
-<P>To create a project:
-</P>
-
-<ol>
-  <li>On the main menu bar, click <b>File &gt; New Project</b>. The New Project 
-    wizard opens.</li>
-  <li>Select a category from the left column and then select the type of project to 
-    create from the right column. Click <b>Next</b>.</li>
-  <li>In the <b>Project name</b> field, type a name for your new
-    project.</li>
-  <li>(Optional) The project that you create will map to a directory structure 
-    in the file system. The default file system location is displayed in the Location 
-    field. If you want to create the project and its contained resources in a 
-    different location, clear the <b>Use default location</b> checkbox and specify 
-    the new location.</li>
-  <li>If you want the new project to be dependent on one or more other projects, 
-    click <b> Next</b> and select the projects to be referenced.</li>
-  <li>Click <b>Finish</b>. The new project is listed in one of the navigation views.</li>
-</ol>
-
-<p><em>Tip:</em> The <b>General &gt; Perspectives &gt;</b> preference page
-allows you to specify the perspective behavior when a new project is created.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/concepts-17.htm">Resource hierarchies</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-43.htm">Creating a folder</a><br>
-<a href="tasks-44.htm">Creating a file</a><br>
-<a href="tasks-63cg.htm">Copying resources</a><br>
-<a href="tasks-63.htm">Moving resources</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-42b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-42b.htm
deleted file mode 100644
index a6dce5c..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-42b.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Deleting projects</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Deleting projects</H1>
-
-<P>To delete a project and remove its contents from the file system:
-</P>
-
-<ol>
-  <li>Select the project in one of the navigation views.</li>
-  <li>Click <b>Delete</b> on the pop-up menu.</li>
-  <li>In the dialog which opens select <b>Also delete contents under ...</b>.</li>
-  <li>Click <b>Yes</b>.</li>
-</ol>
-
-<P>To delete a project from the workspace without removing its contents from the
-file system:
-</P>
-
-<ol>
-  <li>Select the project in one of the navigation views.</li>
-  <li>Click <b>Delete</b> on the pop-up menu.</li>
-  <li>In the dialog which opens select <b>Do not delete contents</b>.</li>
-  <li>Click <b>Yes</b>.</li>
-</ol>
-
-<p CLASS="Para"><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-42.htm">Creating a project</a><br>
-<a href="tasks-47.htm">Closing projects</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-43.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-43.htm
deleted file mode 100644
index b0d025c..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-43.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating a folder</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Creating a folder</H1>
-
-<P>To create a new folder:
-</P>
-
-<ol>
-  <li>In one of the navigation views, right-click the project or folder
-    where you want to create the new folder.</li>
-  <li>From the pop-up menu, select
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.ui.wizards.new.folder)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>New &gt; Folder</b></a>.</li>
-  <li>Enter the name of the new folder and click <b>Finish</b>.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/concepts-17.htm">Resource hierarchies</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-42.htm">Creating a project</a><br>
-<a href="tasks-44.htm">Creating a file</a><br>
-<a href="tasks-45.htm">Creating linked resources</a><br>
-<a href="tasks-63cg.htm">Copying resources</a><br>
-<a href="tasks-63.htm">Moving resources</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-44.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-44.htm
deleted file mode 100644
index 986a7b3..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-44.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating a file</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Creating a file</H1>
-
-<P>To create a file:
-</P>
-
-<ol>
-  <li>In one of the navigation views, right-click the project or folder
-    where you want to create the new file.</li>
-  <li>From the pop-up menu, select
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.ui.wizards.new.file)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>New &gt; File</b></a>.</li>
-  <li>Specify the name of the file, including the file extension (for
-    example, newfile.txt).</li>
-  <li>Click <b>Finish</b>.</li>
-</ol>
-
-<p>The file opens in the editor associated with its type.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources<br></a>
-<a href="../concepts/concepts-17.htm">Resource hierarchies</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-42.htm">Creating a project</a><br>
-<a href="tasks-43.htm">Creating a folder</a><br>
-<a href="tasks-45.htm">Creating linked resources</a><br>
-<a href="tasks-63cg.htm">Copying resources</a><br>
-<a href="tasks-63.htm">Moving resources</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-45.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-45.htm
deleted file mode 100644
index 3951edd..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-45.htm
+++ /dev/null

@@ -1,92 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating linked resources</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Creating linked resources</H1>
-<p>
-Folders and files can be linked to locations in the file system
-outside of the project's location.  These special folders and files are called 
-<a href="../concepts/concepts-13.htm">linked resources</a>.
-</p>
-
-<P>To create a linked folder:
-</P>
-
-<ol>
-  <li>In one of the navigation views, right-click the project 
-    where you want to create the new folder.</li>
-  <li>From the pop-up menu, select
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.ui.wizards.new.folder)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>New &gt; Folder</b></a>.</li>
-  <li>Specify the name of the folder as it will appear in the workbench.  This 
-  name can be different from the name of the folder in the file system.</li>
-  <li>Click <b>Advanced</b>.</li>
-  <li>Check <b>Link to folder in the file system</b>.</li>
-  <li>Enter a file system path, or click <b>Browse</b> to select a folder in the file system.</li>
-  <li>Click <b>Finish</b>.</li>
-</ol>
-
-<P>To create a linked file, follow the same steps as above, except choose
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.ui.wizards.new.file)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>New &gt; File</b></a> instead of
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.ui.wizards.new.folder)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>New &gt; Folder</b></a> in the context menu. </P>
-<P>Linked resource locations can also be specified relative to a variable.  This makes
-it easier to share projects containing linked resources with other team members,
-since it avoids hard-coded absolute file system paths that may vary from one
-machine to the next.
-</P>
-<P>
-To define a linked resource relative to a path variable, do the following after step 5
-above:
-</P>
-<ol start="6">
-  <li>Click the <b>Variables</b> button.</li>
-  <li>In the resulting dialog, select an existing path variable or create a new one.</li>
-  <li>If the chosen variable defines the exact path of the linked resource, click <b>OK</b>.
-  Otherwise, click <b>Extend</b> to specify a file or folder below the location described
-  by the path variable, then click <b>OK</b>.</li>
-  <li>Click <b>Finish</b>.</li>
-</ol>
-<p><em>Tip:</em> The 
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.LinkedResources)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>General &gt; Workspace &gt; Linked Resources</b></a>
-preference page also allows you to define path variables. 
-</p>
-<P>Note that, once you create a linked resource you will not be able to change
-the link target path that you entered in step 6. or 8. above.</P>
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/concepts-17.htm">Resource hierarchies</a><br>
-<a href="../concepts/concepts-13.htm">Linked resources</a>
-</P>
-
-<P><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-42.htm">Creating a project</a><br>
-<a href="tasks-44.htm">Creating a file</a><br>
-<a href="tasks-43.htm">Creating a folder</a><br>
-</P>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="../reference/ref-14b.htm">Linked resources</a> 
-<br><a href="../reference/ref-38.htm">New Folder wizard</a> 
-<br><a href="../reference/ref-39.htm">New File wizard</a> 
-</p>
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-46.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-46.htm
deleted file mode 100644
index 87cbd4d..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-46.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Opening files for editing</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Opening files for editing</H1>
-<p>
-You can launch an editor for a given file in several ways.
-</p>
-
-<ul>
-  <li>By right-clicking the file in one of the navigation views and then
-    selecting <b> Open</b> from the pop-up menu.</li>
-  <li>By double-clicking the file in one of the navigation views.</li>
-  <li>By double-clicking a bookmark that is associated with that file, in the 
-    Bookmarks view.</li>
-  <li>By double-clicking an error or warning, or task record that is associated 
-    with that file, in the Problems view.</li>
-</ul>
-
-<p>All of the above alternatives open the file in the default
-editor for that type of file. To open it in a different editor, select
-<b>Open With</b> from the file's pop-up menu.</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-6.htm">Editors</a><br>
-<a href="../concepts/concepts-6a.htm">External editors</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-51.htm">Associating editors with file types</a><br>
-<a href="tasks-52.htm">Editing files outside the Workbench</a><br>
-  <a href="tasks-18.htm">Linking the Navigator view to the active editor</a><br>
-<a href="tasks-3g.htm">Tiling editors</a><br>
-<a href="tasks-9.htm">Changing the placement of editor tabs</a><br>
-<a href="tasks-68.htm">Comparing resources</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-46ag.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-46ag.htm
deleted file mode 100644
index f725374..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-46ag.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Finding a resource quickly</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Finding a resource quickly</H1>
-
-<P>To navigate to a particular resource in a view such as the Navigator view: 
-</P>
-
-<ol>
-  <li>From <b>Navigate</b> menu, select <b>Go To &gt; Resource</b>.</li>
-  <li>In the window that opens, start typing the name of the
-    resource in the <b>Pattern</b> field. As you type the file name, the system
-    offers a list of possible matches, based on what you have entered so far.</li>
-  <li>Select the resource that you want from the <b>Matching
-    Resources</b> list, and click <b>OK</b>.</li>
-</ol>
-
-<p>The view displays the selected resource.</p>
-<p>
-If you want to open a particular resource in an editor rather than select
-it in a view, you can use the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.navigate.openResource")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Navigate &gt; Open Resource</b></a> action.
-This action presents the same dialog as the <b>Go To &gt; Resource</b> action,
-but immediately opens the matching resource for editing.
-</p>
-<p>You can also do a contextual search for character strings contained within 
-  files in the Workbench. See the links to related tasks below. </p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/concepts-17.htm">Resource hierarchies</a><br>
-<a href="../concepts/cnav.htm">Navigator view</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-84.htm">Searching for text within a file</a><br>
-<a href="tasks-46bg.htm">Narrowing the scope of the Navigator view</a><br>
-<a href="tasks-48.htm">Sorting resources in the Navigator view</a><br>
-<a href="tasks-48b.htm">Showing or hiding files in the Navigator view</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-46bg.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-46bg.htm
deleted file mode 100644
index bb6d570..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-46bg.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Narrowing the scope of the Navigator view</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Narrowing the scope of the Navigator view</H1>
-
-<P>By default, one of the navigation views shows all resources in your Workbench. You can
-focus on a subset of resources by temporarily &quot;going into&quot; a
-project or folder and hiding all other resources.
-</P>
-
-<ol>
-  <li>In one of the navigation views, right-click the project of folder that you want to focus on.</li>
-  <li>From the pop-up menu, select <b>Go Into</b>.</li>
-</ol>
-
-<p>The Navigator now shows only the contents of the selected project or folder. 
-  The title of the Navigator shows the name of the resource you are currently 
-  looking at. You can use the <b>Back</b>, <b>Forward</b>, and <b>Up</b> buttons 
-  on the toolbar of one of the navigation views to change the scope. </p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/cnav.htm">Navigator view</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-48b.htm">Showing or hiding files in the Navigator view</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-47.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-47.htm
deleted file mode 100644
index 8a5bf88..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-47.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Closing projects</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Closing projects</H1>
-
-<P>When a project is closed, it can no longer be changed in the Workbench and 
-its resources no longer appear in the Workbench, but they do still reside on 
-the local file system. Closed projects require less memory. Also, since they 
-are not examined during builds, closing a project can improve build time.
-</P>
-
-<P>To close a project:
-</P>
-
-<ol>
-  <li>Select the project in one of the navigation views.</li>
-  <li>Click <b>Close Project</b> on the pop-up menu.</li>
-</ol>
-
-<P>To re-open the project:
-</P>
-
-<ol>
-  <li>Select the project in one of the navigation views.</li>
-  <li>Click <b>Open Project</b> on the pop-up menu.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/concepts-22.htm">Builds</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-42.htm">Creating a project</a><br>
-<a href="tasks-42b.htm">Deleting projects</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-48.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-48.htm
deleted file mode 100644
index bee1c1b..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-48.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Sorting resources in the Navigator view</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Sorting resources in the Navigator view</H1>
-
-<P>To sort Workbench resources in one of the navigation views by name or by file type:
-</P>
-
-<ol>
-  <li>On the toolbar for one of the navigation views, click the <b>Menu</b>
-    button <img src="../images/ref-79.png" alt="menu button" border="0" >
-    to open the drop-down menu of display options.</li>
-  <li>Select <b>Sort</b>.&nbsp;</li>
-  <li>Select the desired sort option.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/concepts-17.htm">Resource hierarchies</a><br>
-<a href="../concepts/cnav.htm">Navigator view</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-46ag.htm">Finding a resource quickly</a><br>
-<a href="tasks-46bg.htm">Narrowing the scope of the Navigator view</a><br>
-<a href="tasks-48b.htm">Showing or hiding files in the Navigator view</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-48b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-48b.htm
deleted file mode 100644
index 55f97ee..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-48b.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Showing or hiding files in the Navigator view</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Showing or hiding files in the Navigator view</H1>
-
-<P>You can choose to hide system files or generated class files in one of the navigation views. (System files are those that have only a file extension but no file
-name, for example .classpath.)</P>
-
-<ol>
-  <li>On the toolbar for one of the navigation views, click the <b>Menu</b> 
-    button <img src="../images/ref-79.png" alt="Menu button" border="0" >
-	to open the drop-down menu of display options.</li>
-  <li>Select <b>Filter</b>.</li>
-  <li>In the dialog box that opens, select the checkboxes for the
-    types of files that you want to hide.</li>
-</ol>
-<P>In addition, you can restrict the displayed files to a working set.</P>
-<ol>
-  <li>On the toolbar for one of the navigation views, click the <b>Menu</b> 
-    button <IMG src="../images/ref-79.png" alt="Menu button" border="0" >
-	to open the drop-down menu of display options.</li>
-  <li>Choose <B>Select Working Set...</B></li>
-  <li>Select an existing working set from the list or create a new one by selecting
-  <B>New...</B></li>
-</ol>
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/concepts-17.htm">Resource hierarchies</a><br>
-<a href="../concepts/cnav.htm">Navigator view</a><br>
-<a href="../concepts/cworkset.htm">Working sets</a>
-</P>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-49.htm">Viewing resource properties</a><br>
-<a href="tasks-46ag.htm">Finding a resource quickly</a><br>
-<a href="tasks-46bg.htm">Narrowing the scope of the Navigator view</a><br>
-<a href="tasks-48.htm">Sorting resources in the Navigator view</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-49.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-49.htm
deleted file mode 100644
index f3871cb..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-49.htm
+++ /dev/null

@@ -1,48 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Viewing resource properties</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Viewing resource properties</H1>
-
-<P>To display the various properties of a Workbench resource:
-</P>
-
-<ol>
-  <li>Right-click the resource in one of the navigation views.</li>
-  <li>Select <b>Properties</b> from the pop-up menu.</li>
-</ol>
-
-<P>The kinds of properties that are displayed depend on the specific resource 
-you have selected and the features and plug-in that are installed in the Workbench.
-</P> <P><em>Tip:</em> When the resource is selected in one of the navigation views you can also see basic properties for a resource by clicking
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.PropertySheet)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Properties</b></a>.
-</P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="../reference/ref-27.htm">Navigator view</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-48b.htm">Showing or hiding files in the Navigator view</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-51.xhtml b/bundles/org.eclipse.platform.doc.user/tasks/tasks-51.xhtml
deleted file mode 100644
index 48ec984..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-51.xhtml
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." />
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css" />
-<title>Associating editors with file types</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body bgcolor="#ffffff">
-<h1>Associating editors with file types</h1>
-<p>To associate editors with various file types in the Workbench:</p>
-<ol>
-  <li>Open the
-  <a class="command-link" href="javascript:executeCommand(&quot;org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.FileEditors)&quot;)">
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General &gt; Editors &gt; File Associations</b></a> preference page.</li>
-  <li>Select the file type from the <b>File types</b> list, or click <b>Add</b>
-    to add a type that is not already on the list.</li>
-  <li>In the <b>Associated editors</b> list, select the editor that you want 
-    to associate with that file type. To add an editor to the list: 
-    <ol type="a">
-      <li>Click <b>Add</b>. The Editor Selection dialog box opens.</li>
-      <li>Select <b>Internal Editors</b> or <b>External Programs</b>, depending on
-          whether the editor that you want was built for the Workbench or runs outside the Workbench.</li>
-      <li>If you select <b>External Programs</b>, you can click the Browse button to
-          browse the file system.</li>
-      <li>Select the editor from the list and click <b>OK</b>.</li>
-    </ol>
-  </li>
-  <li>Click <b> OK</b> to finish associating the editor with the selected file type.</li>
-</ol>
-
-<p>When you associate an internal editor with a file type, that editor opens in
-the editor area of the Workbench. For example,  if you double-click a file in the
-Navigator or an entry in the Bookmarks or Tasks view it opens in the editor area.
-</p>
-
-<p filter="ws=win32"><img border="0" src="../images/win_only.png" alt="Windows only" />
-Editors that support OLE document mode can also run in the editor area of the Workbench.
-</p>
-
-<p><b>Tip</b>: You can choose to override your default editor selections by
-selecting <b>Open With</b> from the pop-up menu for any resource in one of the navigation views.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" /><br />
-<a href="../concepts/concepts-6.htm">Editors</a><br />
-<a href="../concepts/concepts-6a.htm">External editors</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" /><br />
-<a href="tasks-46.htm">Opening files for editing</a><br />
-<a href="tasks-52.htm">Editing files outside the Workbench</a><br />
-  <a href="tasks-18.htm">Linking the Navigator view to the active editor</a> </p>
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-52.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-52.htm
deleted file mode 100644
index f5d3cac..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-52.htm
+++ /dev/null

@@ -1,48 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Editing files outside the Workbench</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Editing files outside the Workbench</H1>
-<P>To edit a Workbench resource outside the Workbench:</P>
-<ol>
-  <li>Navigate in the file system to the Workbench's installation directory. Go 
-    into the workspace directory and open the file that you want to edit with 
-    the external editor.</li>
-  <li>Edit the file as needed. Save and close it as usual.</li>
-  <li><em>Important</em>: Go back to the Workbench, right-click the edited file 
-    in one of the navigation views, and select <b>Refresh</b> from the pop-up 
-    menu. The Workbench will perform any necessary build or update operations 
-    to process the changes that you made outside the Workbench.</li>
-</ol>
-<p><em>Tip</em>: If you work with external editors regularly, you may want to 
-  enable auto-refresh. This can be done by opening the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workspace)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General &gt; Workspace</b></a> preference page, and checking 
-  the <strong>Refresh automatically</strong> option. When this option is enabled, 
-  any external changes will be automatically discovered by the Workbench. Depending 
-  on the platform this may not happen immediately.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-6.htm">Editors</a><br>
-<a href="../concepts/concepts-6a.htm">External editors</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-46.htm">Opening files for editing</a><br>
-<a href="tasks-51.htm">Associating editors with file types</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-53.xhtml b/bundles/org.eclipse.platform.doc.user/tasks/tasks-53.xhtml
deleted file mode 100644
index 3118df8..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-53.xhtml
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." />
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css" />
-<title>Importing</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body bgcolor="#ffffff">
-<h1 class="Head">Importing</h1>
-
-<p>You can import files into the Workbench in several ways, depending on your operating system:
-</p>
-
-<ul>
-  <li>By using the
-  <a class="command-link" href="javascript:executeCommand(&quot;org.eclipse.ui.file.import&quot;)">
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  Import wizard</a>.</li>
-  <li filter="ws=win32"><img src="../images/win_only.png" alt="For Windows:" border="0" />
-    By dragging files or folders from the file system to one of the navigation views</li>
-  <li filter="ws=win32"><img src="../images/win_only.png" alt="For Windows:" border="0" />
-    By copying files or folders from the file system and pasting them into one of the navigation views</li>
-</ul>
-
-<p>See the related tasks section for more details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" /><br />
-<a href="../concepts/concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" /><br />
-<a href="tasks-55.htm">Importing resources from the file system</a><br />
-<a href="tasks-55bg.htm">Importing resources from an Archive File</a><br />
-<a href="tasks-57.htm">Exporting</a>
-</p>
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-55.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-55.htm
deleted file mode 100644
index bf9b3b6..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-55.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Importing resources from the file system</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Importing resources from the file system</h1>
-
-<p>You can use the Import Wizard to
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import(importWizardId=org.eclipse.ui.wizards.import.FileSystem)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-import resources from the local file system into an existing project</a>.
-</p>
-
-<ol>
-  <li>From the main menu bar, select
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>File &gt; Import...</b></a>. The Import wizard opens.</li>
-  <li>Select <b>General &gt; File System</b> and click <b>Next</b>.</li>
-  <li>Click the <b>Browse</b> button on the next page of the wizard to select
-    the directories from which you would like to add the resources.</li>
-  <li>In the import selection panes, use the following methods to select exactly 
-    the resources you want to add: 
-    <UL>
-      <LI>Expand the hierarchies in the left pane and select or clear the checkboxes 
-        that represent the folders in the selected directory. Then in the right 
-        pane, select or clear checkboxes for individual files.</LI>
-      <LI>Click <b>Filter Types</b> to filter the current selection for files 
-        of a specific type.</LI>
-      <LI>Click <b>Select All</b> to select all resources in the directory, 
-        then go through and deselect the ones that you do not want to add.</LI>
-      <LI>Click <b>Deselect All</b> to deselect all resources in the directory, 
-        then go through and choose individual resources to add.</LI>
-    </UL></li>
-  <li>Specify the Workbench project or folder that will be the import destination.</li>
-  <li>When you have finished specifying your import options, click <b>Finish.</b></li>
-</ol>
-
-<P><em>Tip:</em> You can also import folders and files by dragging them from the 
-  file system and dropping them into one of the navigation views, or by copying 
-  and pasting. </P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-70.htm">Import wizard</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-importproject.htm">Importing existing projects</a><br>
-<a href="tasks-55bg.htm">Importing resources from a ZIP File</a><br>
-<a href="tasks-57.htm">Exporting</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-55bg.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-55bg.htm
deleted file mode 100644
index 48a6b58..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-55bg.htm
+++ /dev/null

@@ -1,66 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Importing resources from an Archive file</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Importing resources from an Archive file</h1>
-
-<P>You can use the Import wizard to
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import(importWizardId=org.eclipse.ui.wizards.import.ZipFile)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-extract files from an archive file into the Workbench</a>. </P>
-
-<ol>
-  <li>From the main menu bar, select
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>File &gt; Import...</b></a>. The Import wizard opens.</li>
-  <li>Select <b>General &gt; Archive File</b> and click <b>Next</b>.</li>
-  <li>Click the <b>Browse</b> button on the next page of the wizard, to select 
-    the archive files that contain the files you want to extract and import into 
-    the Workbench.</li>
-  <li>In the import selection panes, use the following methods to select exactly
-    the resources you want to add:
-    <ul>
-      <li>Expand the hierarchies in the left pane and select or
-        clear the checkboxes that represent the folders in the selected
-        directory. Then in the right pane, select or clear checkboxes for
-        individual files.</li>
-      <li>Click <b>Filter Types</b> to filter the current selection
-        for files of a specific type.</li>
-      <li>Click <b>Select All </b>to select all resources in the
-        directory, then go through and deselect the ones that you do not want to
-        add.</li>
-      <li>Click <b>Deselect All</b> to deselect all resources in
-        the directory, then go through and choose individual resources to add.</li>
-    </ul></li>
-  <li>Specify the Workbench project or folder that will be the import destination.</li>
-  <li>When you have finished specifying your import options. click <b>Finish.</b></li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-70.htm">Import wizard</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-importproject.htm">Importing existing projects</a><br>
-<a href="tasks-55.htm">Importing resources from the file system</a><br>
-<a href="tasks-57.htm">Exporting</a><br>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-57.xhtml b/bundles/org.eclipse.platform.doc.user/tasks/tasks-57.xhtml
deleted file mode 100644
index 1bdccc3..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-57.xhtml
+++ /dev/null

@@ -1,48 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." />
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css" />
-<title>Exporting</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body bgcolor="#ffffff">
-<h1 class="Head">Exporting</h1>
-
-<p>You can export files from the Workbench in several ways, depending on your operating system:
-</p>
-
-<ul>
-  <li>By using the
-  <a class="command-link" href="javascript:executeCommand(&quot;org.eclipse.ui.file.export&quot;)">
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  Export wizard</a>.</li>
-  <li filter="ws=win32"><img src="../images/win_only.png" alt="For Windows:" border="0" /> By
-    dragging files or folders from one of the navigation views to the file system.</li>
-  <li filter="ws=win32"><img src="../images/win_only.png" alt="For Windows:" border="0" /> By
-    copying files or folders from one of the navigation views and pasting them into the file
-    system.</li>
-</ul>
-
-<p>See the related tasks section for more details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" /><br />
-<a href="../concepts/concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" /><br />
-<a href="tasks-59.htm">Exporting resources to the file system</a><br />
-  <a href="tasks-59ag.htm">Exporting resources to an Archive File</a><br />
-<a href="tasks-53.htm">Importing</a>
-</p>
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-59.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-59.htm
deleted file mode 100644
index 8b976b3..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-59.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Exporting resources to the file system</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Exporting resources to the file system</H1>
-
-<P>You can use the Export wizard to
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export(exportWizardId=org.eclipse.ui.wizards.export.FileSystem)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-export resources from the Workbench to the file system</a>.
-</P>
-
-<ol>
-  <li>In one of the navigation views, select the resources that you want to export.</li>
-  <li>From the main menu bar, select
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>File &gt; Export...</b></a>. The Export wizard opens.</li>
-  <li>Select <b>General &gt; File System</b> and click <b>Next</b>.</li>
-  <li>By default, the resources that you selected will be exported, along with
-    all their children. Optionally, use the checkboxes in the left and right
-    panes to select the set of resources to export, and use push buttons such as
-    <b>Select Types</b> to filter the types of files that you want to export.</li>
-  <li>Click the <b>Browse</b> button on the next page of the wizard, to select
-    the directory you would like to export the resources to.</li>
-  <li>Specify the directory in the file system that will be the export destination.</li>
-  <li>Click <b>Finish</b>.</li>
-</ol>
-
-<p><em>Tip:</em> You can also export folders and files by dragging them from
-one of the navigation views to the file system and dropping them in the file system, or
-by copy and paste.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-53.htm">Importing</a><br>
-<a href="tasks-59ag.htm">Exporting resources to a ZIP File</a><br>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-59ag.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-59ag.htm
deleted file mode 100644
index 289d3a4..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-59ag.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Exporting resources to an Archive file</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Exporting resources to an Archive file</h1>
-
-<p>You can use the Export wizard to
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export(exportWizardId=org.eclipse.ui.wizards.export.ZipFile)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-export resources from the Workbench to an archive file in the file system</a>.
-</p>
-
-<ol>
-  <li>In one of the navigation views, select the resources that you want to export.</li>
-  <li>From the main menu bar, select
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>File &gt; Export...</b></a>. The Export wizard opens.</li>
-  <li>Select <b>General &gt; Archive File</b> and click <b>Next</b>.</li>
-  <li>By default, the resources that you selected will be exported along with 
-    their children. Optionally, use the checkboxes in the left and right panes 
-    to select the set of resources to export, and use push buttons such as <b>Select 
-    Types</b> to filter the types of files that you want to export.</li>
-  <li>Specify the path and name of the archive file into which you want to export 
-    the selected resources.</li>
-  <li>Click <b>Finish.</b></li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" width="159" height="27"><br>
-<a href="../concepts/concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" width="159" height="27"><br>
-<a href="tasks-59.htm">Exporting resources to the file system</a><br>
-<a href="tasks-53.htm">Importing</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-63.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-63.htm
deleted file mode 100644
index 2ae2e5c..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-63.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Moving resources</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Moving resources</h1>
-
-<P>You can move resources from one Workbench location to another (for example,
-from one project to another project).
-</P>
-
-<ol>
-  <li>In one of the navigation views, select the resources that you want to move.</li>
-  <li>From the pop-up menu, select <b>Move</b>.</li>
-  <li>In the Folder Selection window, select the project or folder
-    where you want to move the resources to and click <b>OK</b>.</li>
-</ol>
-
-<p><em>Tip:</em> You can also move resources by dragging them from the original
-location to the new location in one of the navigation views.
-</p>
-<P>Moving a linked resource always moves the link and not the resource that it is 
-linked to. E.g., when moving a linked folder the folder contents is not moved on
-the file system. Keep in mind that linked resources can only be moved to a project
-and not to a folder.
-</P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/cnav.htm">Navigator view</a><br>
-<a href="../concepts/concepts-13.htm">Linked resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-46ag.htm">Finding a resource quickly</a><br>
-<a href="tasks-63cg.htm">Copying resources</a><br>
-<a href="tasks-66.htm">Renaming resources</a><br>
-<a href="tasks-67.htm">Deleting resources</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-63cg.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-63cg.htm
deleted file mode 100644
index f1b32a3..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-63cg.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Copying resources</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Copying resources</H1>
-
-<P>You can copy resources from one Workbench location to another (for example, 
-  from one project to another project).
-</P>
-
-<ol>
-  <li>In one of the navigation views, select the resources that you want to copy.</li>
-  <li>From the pop-up menu, select <b>Copy</b>.</li>
-  <li>In one of the navigation views, select the project or folder where you want to copy 
-    the resources to.</li>
-  <li>From the pop-up menu, select <b>Paste</b>.</li>
-</ol>
-
-<P><em>Tip:</em> You can also copy resources by holding down the Ctrl key and
-dragging them from the original location to the new location in one of the navigation views.
-</P>
-<P>Copying a linked resource always copies the link and not the resource that it is 
-linked to. E.g., when copying a linked folder the folder contents is not copied on
-the file system. Instead, a new linked folder is created linking to the same location 
-on the file system. Keep in mind that linked resources can only be copied to a project
-and not to a folder.
-</P>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/cnav.htm">Navigator view</a><br>
-<a href="../concepts/concepts-13.htm">Linked resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-42.htm">Creating a project</a><br>
-<a href="tasks-43.htm">Creating a folder</a><br>
-<a href="tasks-44.htm">Creating a file</a><br>
-<a href="tasks-63.htm">Moving resources</a><br>
-<a href="tasks-66.htm">Renaming resources</a><br>
-<a href="tasks-67.htm">Deleting resources</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-66.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-66.htm
deleted file mode 100644
index 253bbd4..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-66.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Renaming resources</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Renaming resources</H1>
-
-<P>You can rename Workbench resources using the Rename command on the context 
-  menu in one of the navigation views.
-</P>
-
-<ol>
-  <li>In one of the navigation views, right-click the resource that you want to rename.</li>
-  <li>From the pop-up menu, select <b>Rename</b>.</li>
-  <li>Type the new name for the resource.</li>
-  <li>Hit the return key.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/cnav.htm">Navigator view</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-49.htm">Viewing resource properties</a><br>
-<a href="tasks-63.htm">Moving resources</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-67.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-67.htm
deleted file mode 100644
index 9aee16c..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-67.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Deleting resources</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Deleting resources</H1>
-
-<p>To delete a resource from the Workbench:
-</p>
-
-<ol>
-  <li>In one of the navigation views, select the resources that you want to
-    delete. (Hold down the Ctrl key to select more than one resource.)</li>
-  <li>Press the Delete key.</li>
-  <li>Click <b>Yes</b> in the dialog which appears.</li>
-</ol>
-
-<p><em>Tip:</em> You can achieve the same result by selecting <b>Delete</b>
-from the pop-up menu.
-</p>
-<p>
-Deleting resources from the workspace will also delete the corresponding files and/or
-folders from the local file system.  The only exception is linked resources, which are
-not removed from the file system when you delete the link in the workspace.  However,
-deleting child resources of linked folders <em>will</em> delete those resources
-from the local file system.
-</p>
-<p>
-In most cases it is possible to restore deleted files from the local history.  See the related
-tasks for more details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/cnav.htm">Navigator view</a><br>
-<a href="../concepts/concepts-13.htm">Linked resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-42b.htm">Deleting projects</a><br>
-<a href="tasks-42.htm">Creating a project</a><br>
-<a href="tasks-43.htm">Creating a folder</a><br>
-<a href="tasks-44.htm">Creating a file</a><br>
-<a href="tasks-45.htm">Creating linked resources</a><br>
-<a href="tasks-87b.htm">Restoring deleted resources from local history</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-68.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-68.htm
deleted file mode 100644
index 7e91053..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-68.htm
+++ /dev/null

@@ -1,96 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Comparing resources</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Comparing resources</H1>
-
-<p>When a comparison is performed, comparison 
-editors appear in the editor area. The differences between files are highlighted
-in the comparison editors, allowing you to browse and copy changes between the compared 
-resources.
-</p>
-
-<p>To compare resources:
-</p>
-
-<ol>
-  <li>Select one or more resources in one of the navigation views.</li>
-  <li>From the resource's pop-up menu, select <b>Compare With.</b></li>
-</ol>
-
-<p>A tool for viewing differences is opened in the editor area.
-</p>
-
-<p>Here are some of the comparisons that you can perform.&nbsp;
-</p>
-
-<dl>
-  <dt><b>Compare With &gt; Latest from HEAD</b></dt>
-  <dd>compares the selected resource with the version of the same resource that 
-    is currently committed to the active branch. This option is available for 
-    CVS. This ,or a similar option, may or may not be available for other repository 
-    types.</dd>
-  <dt><b>Compare With &gt; Another Branch or Version</b></dt>
-  <dd>compares the selected resource with a version that has been committed to 
-    the repository or to the latest version in a particular branch. This requires 
-    you to choose a version of the resource or a branch from a list. This option 
-    is available for CVS. This, or a similar option, may or may not be available 
-    for other repository types.</dd>
-  <dt><b>Compare With &gt; Each Other</b></dt>
-  <dd>compares two or three selected resources with each other</dd>
-  <dt><b>Compare With &gt; Revision</b></dt>
-  <dd>compares the selected resource with a version of the same resource that 
-    was committed to the active branch. This requires you to choose a revision 
-    of the resource from a list. This option is available for CVS. This, or a 
-    similar option, may or may not be available for other repository types.</dd>
-  <dt><b>Compare With &gt; Local History</b></dt>
-  <dd>compares the selected resource to one that is in the local history, which 
-    is maintained when you save changes. (<em>Tip:</em> to configure the size 
-    and depth of your local history, use the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.FileStates)")'>
-    <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-    <b>General &gt; Workspace &gt; Local History</b></a> preference page.)</dd>
-</dl>
-
-<p><em>Tip:</em> You can customize the behavior of the comparison editor with the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.compare.internal.ComparePreferencePage)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General &gt; Compare/Patch</b></a> preference page.
-  You can select to &quot;synchronize scrolling&quot; of the pane contents, as well 
-  as setting options for showing conflicts with other team members and changing 
-  the default font.</p>
-
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a><br>
-<a href="../concepts/concepts-29.htm">Three way comparisons</a><br>
-<a href="../concepts/concepts-17a.htm">Local history</a></p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-68dg.htm">Merging changes in the Compare editor</a><br>
-<a href="tasks-113b.htm">Resolving conflicts</a><br>
-<a href="tasks-68b.htm">Setting preferences for comparing files</a><br>
-<a href="tasks-101.htm">Comparing resources with repository versions</a><br>
-<a href="tasks-68bg.htm">Understanding the comparison</a><br>
-<a href="tasks-68c.htm">Working with patches</a><br>
-<a href="tasks-3g.htm">Tiling editors</a></p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="../reference/ref-25.htm">Compare editor</a>
-<br><a href="../reference/ref-33.htm">CVS Synchronize view</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-68b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-68b.htm
deleted file mode 100644
index 73500a0..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-68b.htm
+++ /dev/null

@@ -1,158 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Setting preferences for comparing files</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Setting preferences for comparing files</H1>
-
-<P>When you select to compare or synchronize two or more resources in the
-Workbench, one or more comparison editors usually open. To customize how these
-editors behave:
-</P>
-
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.compare.internal.ComparePreferencePage)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General &gt; Compare/Patch</b></a> preference page.</li>
-  <li>Set your preferences and click <b>OK</b>.</li>
-</ol>
-
-<p CLASS="Para">You can configure the following options on the <b>General</b> tab.
-</p>
-
-<TABLE BORDER="1" cellspacing="0" width="540" cellpadding="5">
-  <THEAD>
-    <TR> 
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Option</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Description</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Default</P></TH>
-    </TR>
-  </THEAD>
-  <TBODY>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Open structure compare automatically</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Makes an additional information area visible which shows differences 
-          in the underlying structure of the resources being compared. This information 
-          may not be available for all comparisons.</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          On</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Show additional compare information in the status line</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Causes the status line to display additional context information about 
-          the comparison.</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Off</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Ignore white space</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">Causes 
-          the comparison to ignore differences which are whitespace characters 
-          (spaces, tabs, etc.). Also causes differences in line terminators ( 
-          LF versus CRLF) to be ignored.</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Off</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Automatically save dirty editors before patching</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">
-      	  This option controls whether any unsaved changes are automatically saved before
-      	  a patch is applied.</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Off</P></TD>
-    </TR>
-  </TBODY>
-</TABLE>
-
-<p CLASS="Para">You can configure the following options in the <b>Text Compare</b> tab.
-</p>
-
-<TABLE BORDER="1" cellspacing="0" width="540" cellpadding="5">
-  <THEAD>
-    <TR> 
-      <TH width="122" COLSPAN="1" ROWSPAN="1"> <P CLASS="Para"> Option</P></TH>
-      <TH width="327" COLSPAN="1" ROWSPAN="1"> <P CLASS="Para"> Description</P></TH>
-      <TH width="53" COLSPAN="1" ROWSPAN="1"> <P CLASS="Para"> Default</P></TH>
-    </TR>
-  </THEAD>
-  <TBODY>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Synchronize scrolling between panes in compare viewers</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          The two compare viewers will &quot;lock scroll&quot; along with one 
-          another in order to keep identical and corresponding portions of the 
-          code in each pane side by side.</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          On</P></TD>
-    </TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para"> Initially show ancestor pane</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Sometimes you may want to compare two versions of a resource with
-the previous version from which they were both derived. This is called their <i>common ancestor</i>,
-and it appears in its own comparison pane during a three way comparison.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Off</P>
-</TD>
-</TR>
-   <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Show pseudo conflicts</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Displays conflicts that occur when two developers make the same change, 
-          for example when both add or remove the same line of code.</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Off</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Connect ranges with single line</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Controls whether differing ranges are visually connected by a single
-          line or a range delimited by two lines.</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          On</P></TD>
-    </TR>
-  </TBODY>
-</TABLE>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-29.htm">Three way comparisons</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-68.htm">Comparing resources</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-68dg.htm">Merging changes in the Compare editor</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="../reference/ref-25.htm">Compare editor</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-68bg.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-68bg.htm
deleted file mode 100644
index b8f2f24..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-68bg.htm
+++ /dev/null

@@ -1,77 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Understanding the comparison</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Understanding the comparison</H1>
-
-<p>If you compare two files (file1.txt and file2.txt), the following results
-are shown in the compare editor. The left side shows the contents of file1.txt and the right side
-shows the contents of file2.txt. The lines connecting the left and right panes
-indicate the differences between the files.
-</p>
-
-<p>You can double click on the editor tab to maximize the editor.
-</p>
-
-<p><img src="../images/Image80_compare_editor2.png" alt="Compare view" border="0" >
-</p>
-
-<p>Looking at the numbered changes in the above image:
-</p>
-
-<ul>
-  <li>Starting with the top line (in the left pane) we can see that the difference 
-    bar (in the area of the blue circle) indicates something is missing from the 
-    very top of the left file. If we follow the difference band (see #1) to the 
-    right file we can see that it contains &quot;This is line 1&quot; .</li>
-  <li>The next line &quot;This is line 2.&quot; is white indicating it matches 
-    the right file.</li>
-  <li>Moving onto the next line (colored in gray) we can see that the left file 
-    and right file have different contents for this line (see #2).</li>
-  <li>The next line (&quot;This is line 4&quot;) is once again in white, so we
-    can skip it, since the contents are the same in both.</li>
-  <li>The next line exists in the left file&nbsp; but since it is gray we follow 
-    its difference bar to the right (see #3) and notice that the right file does 
-    not contain the line (see red circle).</li>
-</ul>
-
-<p><em>Hint:</em> On the right-hand side of the comparison, to the right of the
-scrollbar, there is a column which shows a graphical representation of all differences 
-between the resources. You can click on any of the segments displayed there 
-to quickly scroll to that difference.
-</p>
-  
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a><br>
-<a href="../concepts/concepts-29.htm">Three way comparisons</a><br>
-<a href="../concepts/concepts-17a.htm">Local history</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-68.htm">Comparing resources</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-68dg.htm">Merging changes in the Compare editor</a><br>
-<a href="tasks-113b.htm">Resolving conflicts</a><br>
-<a href="tasks-68b.htm">Setting preferences for comparing files</a><br>
-<a href="tasks-101.htm">Comparing resources with repository versions</a><br>
-<a href="tasks-3g.htm">Tiling editors</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br>
-<a href="../reference/ref-25.htm">Compare editor</a><br>
-<a href="../reference/ref-33.htm">CVS Workspace Synchronization</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-68c.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-68c.htm
deleted file mode 100644
index 446d246..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-68c.htm
+++ /dev/null

@@ -1,167 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working with patches</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Working with patches</H1>
-
-<p>Patches allow developers to share work without storing it in a repository. 
-  This is helpful when a developer wants to contribute to a project that is shared 
-  through a repository but does not have write access to the repository. In this 
-  situation, the developer can create a patch and either e-mail it to a developer 
-  who does have write access or attach it to a bug in the bug reporting system 
-  used by the project, depending on the process defined by the project. A developer 
-  that does have write access can then apply the patch to the project and commit 
-  the changes.</p>
-<H2>To create a patch from a CVS project:</H2>
-<ol>
-  <li>Select the resource that contains the modifications to be included in the 
-    patch. Although this can be any folder, it is easiest to select the project 
-    itself because the patch must be applied to the same resource it is generated 
-    from. The patch should also be applied to the same file revisions that it 
-    is generated on so steps should be taken to ensure that the patch is applied 
-    to the same resource line-up (the easiest way to do this is to create the 
-    patch on top of a version).</li>
-  <li>From the popup menu, select <b>Team &gt; Create Patch...</b>. The Create 
-    Patch wizard will open.</li>
-  <li>Choose where the patch should be saved: 
-    <ol type="a">
-      <li><i>Save to Clipboard</i> - this will place the patch on the clipboard 
-        so it can be pasted into a text editor such as an e-mail program.</li>
-      <li><i>Save to File System</i> - this will place the patch in the specified 
-        file in the local file system</li>
-      <li><i>Save in Workspace</i> - this will place the patch in the specified 
-        file inside one of the existing workbench projects.</li>
-    </ol>For small patches it may be reasonable to transfer the patch using the clipboard 
-    but in most cases the local file system in the best option to use. Click <b>Next</b> 
-    to configure how the patch is generated.</li>
-  <li>Choose how to configure the patch:
-    <ol type="a">
-      <li><i>Recurse into sub-folders</i> - If disabled, only the direct children 
-        of the selection are included in the patch. Otherwise, all descendants 
-        are included.</li>
-      <li><i>Include new files in patch</i> - If disabled, only files that are 
-        under CVS version control are included. Otherwise, files that have been 
-        newly created but not added or ignored will also be included.</li>
-      <li><i>Diff output format</i> - Allows the choice of several common diff 
-        output formats. <i>Unified</i> is the format used by many patch application 
-        tools including Eclipse.</li>
-    </ol>
-  </li>
-  <li>Click <b>Finish</b>. </li>
-  <li>Transfer the patch as appropriate for the project being patched.</li>
-</ol>
-<H2>To apply a patch:</H2>
-<ol>
-  <li>Select the resource that the patch was generated on. This resource should 
-    contain the same file revisions as the line-up on which the patch was generated.</li>
-  <li>From the pop-up menu, select <b>Team&gt;Apply Patch...</b>. The Resource 
-    Patcher wizard will open.</li>
-  <li>Indicate where the patch is to be found:
-    <ol type="a">
-      <li><i>File</i> - the patch is in a file on the local file system. Either 
-        type in the full path to the file or use the <b>Browse...</b> button to 
-        find the file.</li>
-      <li><i>Clipboard</i> - the patch is on the clipboard. <b>Warning:</b> It 
-        is safer to use a file based patch. Line endings may not be handled properly 
-        if the clipboard is used and the patch was generated on a different platform 
-        (i.e. Linux vs. Windows).</li>
-    </ol> Click <b>Next</b> to see the effect of applying the patch.</li>
-  <li>The top pane of this page shows whether the patch could be successfully applied
-  to files in your workspace. If you select a leaf item in the tree the bottom pane
-  shows the part of the patch file (known as 'hunk' in patch terminology) in an easy to read
-  side by side presentation. <b>Note:</b> The bottom pane <b>does not</b> show a preview
-  of how resources in your workspace would look after applying the hunk.
-  It just shows the contents of the patch file.
-  
-
-  <ol type="a">
-  	<li>
-  	A checked item indicates that a patch (or hunk) could be successfully
-  	applied to a workspace resource.
-  	You can exclude patches or individual hunks by unchecking them.
-  	</li>
-  	
-    <li>
-    A red exclamation mark indicates that there is a problem with a patch or hunk.
-    <br>
-    This happens if the patch is not 
-    well formed or the revision of one or more files that the patch were generated 
-    on do not match the revisions that the patch is being applied to.
-    <br>
-    You find the reason for the failure in parenthesis.
-    <p>
-    In order to apply the full patch
-    successfully you will have to eliminate the problems (red exclamation marks) and get checked
-    items everywhere by tweaking the options on this wizard page (see 'Options' below).</p>
-  	</li>
-   	
-  </ol>
-  </li>
-  <li>If all is well, click <b>Finish</b> to apply the patch. The workspace will 
-    now contain outgoing changes for each file modified by the patch.</li>
-</ol>
-
-
-<H3>Options for applying a patch</H3>
-
-  	For getting successful matches of your patch file you have the following options:
-   	<ol>
-   	
-   		<li>
-   			Go back to the first page of the Resource Patcher wizard and
-   			select the correct resource to which the patch should be applied.
-   		</li>
-   	
-   	  	<li>
-   	  		If a common prefix of the path names stored in the patch file doesn't match
-   	  		the path names in you current workspace, you can 'Ignore leading path name segments'.
-  		</li>
-
-   	  	<li>
-   	  		Use the 'Ignore whitespace' option to make the matching process
-   	  		independent from whitespace differences between the patch file and files
-   	  		in your workspace. 
-  		</li>
-
-   	  	<li>
-   	  		Adjust the 'Maximum fuzz factor' (patch terminology).
-			This factor determines how far from its original line a hunk is allowed to match.
-			The default is two. So if a hunk does not match at the line given in the patch 
-			file, the Resource Patcher tries to match the hunk 'fuzz' number of lines before
-			or after the position.
-  		</li>
-
-   	  	<li>
-   	  		Use the 'Reverse patch' option for patch files that already have been applied to your
-   	  		workspace. This option is also useful to undo or redo a patch.
-  		</li>
-
-   	</ol>
-
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-68.htm">Comparing resources</a>
-</p>
-
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-47.htm">CVS</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-68dg.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-68dg.htm
deleted file mode 100644
index 526f9d5..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-68dg.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Merging changes in the compare editor</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Merging changes in the compare editor</H1>
-
-<p>The toolbar buttons in the compare editor allows you to merge changes from the left file to the
-right file and vice versa. There are four types of merges you can perform:
-</p>
-
-<ul>
-  <li>Copy All from Left to Right</li>
-  <li>Copy All from Right to Left</li>
-  <li>Copy Current Change from Left to Right</li>
-  <li>Copy Current Change from Right to Left</li>.
-</ul>
-
-<p>The <b>Copy All from Left to Right</b> and <b>Copy All from Right to Left</b>
-actions completely replace the contents of one resource with the other resource.
-</p>
-
-<p>To merge a single change:
-</p>
-
-<ol>
-  <li>Select the highlighted difference that you want to merge.</li>
-  <li>Depending on what you want to do, click either the <b>Copy Current Change 
-    from Right to Left</b> or the <b>Copy Current Change from Left to Right</b> 
-    toolbar button. The selected text is copied from one file to the other.</li>
-  <li>Right click to get the resource's pop-up menu, and select <b>Save</b>.</li>
-</ol>
-
-<p>The image below gives an example of two files (file1.txt and file2.txt) compared.
-</p>
-
-<p><img src="../images/Image80_compare_editor.png" alt="Compare view" border="0" >
-</p>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-29.htm">Three way comparisons</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</P>
-
-<p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-<a href="tasks-68.htm">Comparing resources</a><br>
-<a href="tasks-68bg.htm">Understanding the comparison</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-113b.htm">Resolving conflicts</a><br>
-<a href="tasks-68b.htm">Setting preferences for comparing files</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="../reference/ref-25.htm">Compare editor</a>
-<br><a href="../reference/ref-33.htm">CVS Workspace Synchronization</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-70.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-70.htm
deleted file mode 100644
index b4db011..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-70.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Comparing resources with the local history</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Comparing resources with the local history</H1>
-<p>To compare a Workbench resource with a state in the local history:
-</p>
-
-<ol>
-  <li>In one of the navigation views, select the resource that you want to compare with 
-    a local history state.</li>
-  <li>From the resource's pop-up menu, select <b>Compare With</b> &gt; <b>Local 
-    History</b>. The Compare with Local History page opens.</li>
-  <li>Select a state in the <b>Local History</b> list. The Text Compare editor opens.</li>
-  <li>Click the <b>Select Next Change</b> and <b>Select Previous Change</b> buttons 
-    to browse the changes made between the state in the local history and the 
-    Workbench resource.</li>
-  <li>Click <b>OK</b> when you are finished.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-17a.htm">Local history</a><br>
-<a href="../concepts/concepts-27.htm">Versions</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-87.htm">Replacing a resource with local history</a><br>
-<a href="tasks-87b.htm">Restoring deleted resources from local history</a><br>
-<a href="tasks-88.htm">Setting local history preferences</a><br>
-<a href="tasks-68.htm">Comparing resources</a>
-</p>
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-73.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-73.htm
deleted file mode 100644
index 18313a7..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-73.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Building resources</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Building resources</H1>
-
-<p>There are a number of ways that resources in the Workbench can be built. The 
-scope of a build can be one or more selected projects, a working set, or the entire workspace. 
-</p>
-
-<p>A build will typically only operate on resources that have changed since
-the last build.  A clean build will discard all existing built state, causing the
-next build to operate on all resources within the scope of the build.</p>
-
-<p>Builds can be done automatically (each time resources are modified), or manually, 
-using a menu item or keyboard shortcut. See the Related tasks links for more details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" width="159" height="27"><br>
-<a href="../concepts/concepts-22.htm">Builds</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" width="159" height="27"><br>
-<a href="tasks-75.htm">Performing builds manually</a><br>
-<a href="tasks-16.htm">Performing builds automatically</a><br>
-<a href="tasks-17.htm">Saving resources automatically before a manual build</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-75.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-75.htm
deleted file mode 100644
index 1f98539..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-75.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Performing builds manually</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Performing builds manually</h1>
-
-<P>By default, builds are performed automatically when you save resources. If 
-  you need more control over when builds occur, you can disable automatic building 
-  and manually invoke builds. This is sometimes desirable in cases where you know 
-  building should wait until you finish a large set of changes. The disadvantage 
-  of manual building is that tasks generated to indicate build errors quickly 
-  become out of date until you build. In addition, it is very important that you 
-  remember to manually build before relying on build output (for example, before 
-  running your Java program).
-</P>
-
-<p><em>Note:</em> Some of the menu items described below are only available when 
-the automatic build preference is disabled (ensure
-<b>Project &gt; Build Automatically</b> is not checked).
-</p>
-
-<p>To build projects in the workspace select the projects and click <b>Project 
-  &gt; Build Project</b>. Alternatively, click <b>Project &gt; Build All</b> to
-  build all projects in the workspace. Both of these commands will search through
-  the projects and only build the resources that have changed since the last build.
-  To build all resources, even those that have not changed since the last build,
-  run <b>Project &gt; Clean...</b> before doing the build.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-22.htm">Builds</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-17.htm">Saving resources automatically before a manual build</a><br>
-<a href="tasks-14.htm">Changing build order</a><br>
-<a href="tasks-16.htm">Performing builds automatically</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-77.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-77.htm
deleted file mode 100644
index 81553aa..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-77.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Adding line items in the Tasks view</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Adding line items in the Tasks view</H1>
-
-<P>The Tasks view contains line items for system-generated problems, warnings, and
-errors. You can add your own entries to the table to build a list
-of to-do items, or tasks.
-</P>
-
-<ol>
-  <li>On the toolbar in the Tasks view, click the <b>New Task</b> button
-      <img src="../images/Image52_new_task.png"  alt="New Task button" border="0">.
-      The <b>New Task</b> dialog will open.</li>
-  <li>Type a brief description for the task in the <b>Description</b> field. 
-      The new task is assigned default priority and completed values. 
-      These values may also be modified within the <b>New Task</b> dialog.</li>
-  <li>Press <b>OK</b>.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/ctskview.htm">Tasks view</a><br>
-<a href="../concepts/cbookmrk.htm">Bookmarks</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-78.htm">Deleting tasks</a><br>
-<a href="tasks-77b.htm">Associating a task with a resource</a><br>
-<a href="tasks-79.htm">Filtering the Tasks view</a><br>
-<a href="tasks-81b.htm">Creating a bookmark for an entire file</a><br>
-<a href="tasks-81.htm">Creating a bookmark within a file</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-77b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-77b.htm
deleted file mode 100644
index 0ca4bac..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-77b.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Associating a task with a resource</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<a NAME="elementId-1032839"></a>
-<a NAME="pgfId-1032844"></a>
-<h1>Associating a task with a resource</h1>
-
-<p>You can associate tasks with an editable resource, for instance
-to remind yourself to update a line of source code later.
-</p>
-
-<ol>
-  <li>In one of the navigation views, double-click the resource with which
-      you wish to associate the new task. The resource opens in the editor area.</li>
-  <li>Right-click in the gray border at the left of the editor
-      area, beside the line of text or source code against which you want to log
-      the new task.</li>
-  <li>On the pop-up menu, select <b>Add Task</b>.</li>
-  <li>When prompted, enter a brief description of the task.</li>
-</ol>
-
-<p>A new task icon appears in the border of the editor area, to
-the left of the line where you added the task. When you move the mouse pointer
-over the marker, the description of the task is displayed as a tooltip. The task
-is also added to the Tasks view. You can delete a task either by right-clicking
-its icon in the editor area and selecting <b>Remove Task</b>, or by pressing the 
-Delete key in the Tasks view.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/ctskview.htm">Tasks view</a><br>
-<a href="../concepts/cbookmrk.htm">Bookmarks</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-77.htm">Adding line items in the Tasks view</a><br>
-<a href="tasks-78.htm">Deleting tasks</a><br>
-<a href="tasks-79.htm">Filtering the Tasks view</a><br>
-<a href="tasks-81b.htm">Creating a bookmark for an entire file</a><br>
-<a href="tasks-81.htm">Creating a bookmark within a file</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-78.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-78.htm
deleted file mode 100644
index 85faf0c..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-78.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Deleting tasks</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Deleting tasks</H1>
-
-<P>You can delete associated tasks from the gray border at the left of the editor area.
-</P>
-
-<ol>
-  <li>In the marker bar in the editor area, locate the task marker that you want to delete.</li>
-  <li>From the marker's pop-up menu, select <b>Remove Task</b>.</li>
-  <li>The task marker disappears and the task is removed from the Tasks view.</li>
-</ol>
-
-<p>You can also delete one or more line items from the Tasks view
-by pressing the Delete key or by clicking the <b>Delete</b> button on the Tasks
-view toolbar, or from the pop-up menu.
-</p>
-
-<p><em>Tip:</em> To delete all completed tasks, right-click in the Tasks view and
-select <b>Delete Completed Tasks</b> from the pop-up menu.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" width="159" height="27"><br>
-<a href="../concepts/ctskview.htm">Tasks view</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-79.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-79.htm
deleted file mode 100644
index 8dfd658..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-79.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Filtering the Tasks and Problems views</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Filtering the Tasks and Problems views</H1>
-
-<P>You can filter the tasks or problems that are displayed in the Tasks or Problems 
-  views. For example, you might wish to see only problems that have been logged 
-  by the Workbench, or tasks that you have logged as reminders to yourself. You 
-  can filter items according to which resource or group of resources they are 
-  associated with, by text string within the Description field, by problem severity, 
-  by task priority, or by task status. </P>
-<ol>
-  <li>On the toolbar of the Tasks or Problems view, click <b>Filter</b>.<img src="../images/Image400_filterbutton.png" alt="filter button" border="0">.</li>
-  <li>Select the radio buttons and checkboxes that correspond to
-      your filtering objectives.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" width="159" height="27"><br>
-<a href="../concepts/ctskview.htm">Tasks view</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" width="159" height="27"><br>
-<a href="tasks-77.htm">Adding line items in the Tasks view</a><br>
-<a href="tasks-77b.htm">Associating a task with a resource</a><br>
-<a href="tasks-78.htm">Deleting tasks</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-81.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-81.htm
deleted file mode 100644
index 7db115b..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-81.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating a bookmark within a file</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<a NAME="elementId-1001031"></a>
-<a NAME="pgfId-1001036"></a>
-<h1>Creating a bookmark within a file</h1>
-
-<p>The Workbench allows you to create bookmarks in files that you
-edit so that you can quickly reopen those files from the Bookmarks view
-(<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.BookmarkView)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Bookmarks</b></a>).
-</p>
-
-<ol>
-  <li>With the file open in an editor, right-click in the gray border at the left
-  of the editor area, next to the line of code or text that you want to bookmark.</li>
-  <li>Select <b>Add Bookmark </b>from the pop-up menu.</li>
-  <li>Notice that an icon for the bookmark now appears in the left
-    border of the editor area. A line is also added to the Bookmarks view.)</li>
-</ol>
-
-<p CLASS="Head">You can reopen the file for editing at any time by double-clicking 
-  the bookmark in the Bookmarks view. </p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/cbookmrk.htm">Bookmarks</a><br>
-<a href="../concepts/ctskview.htm">Tasks view</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-81b.htm">Creating a bookmark for an entire file</a><br>
-<a href="tasks-82.htm">Deleting a Bookmark</a><br>
-<a href="tasks-77.htm">Adding line items in the Tasks view</a><br>
-<a href="tasks-77b.htm">Associating a task with a resource</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-81b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-81b.htm
deleted file mode 100644
index 2790987..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-81b.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating a bookmark for an entire file</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<a NAME="elementId-1001031"></a>
-<a NAME="pgfId-1001036"></a>
-
-<h1>Creating a bookmark for an entire file</h1>
-
-<p>You can bookmark individual files in the Workbench, in order to open them
-quickly from the Bookmarks view
-(<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.BookmarkView)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Bookmarks</b></a>)
-later.
-</p>
-
-<ol>
-  <li>In one of the navigation views, select the file that you want to
-    add to your list of bookmarks.</li>
-  <li>From the main Workbench menu select <strong>Edit &gt; Add Bookmark</strong>.</li>
-</ol>
-
-<p>At any time, you can open the bookmarked file for editing by
-double-clicking the bookmark in the Bookmarks view.
-</p>
-
-<p>You can also create bookmarks for specific lines of text or
-source code or within a file. See the list of related topics below.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/cbookmrk.htm">Bookmarks</a><br>
-<a href="../concepts/ctskview.htm">Tasks view</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-81.htm">Creating a bookmark within a file</a><br>
-<a href="tasks-82.htm">Deleting a Bookmark</a><br>
-<a href="tasks-77.htm">Adding line items in the Tasks view</a><br>
-<a href="tasks-77b.htm">Associating a task with a resource</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-82.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-82.htm
deleted file mode 100644
index 2546659..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-82.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Deleting a bookmark</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Deleting a bookmark</H1>
-
-<p>To delete any bookmark:
-</p>
-
-<ol>
-  <li>Open the Bookmarks view
-  (<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.BookmarkView)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Window &gt; Show View &gt; Other... &gt; General &gt; Bookmarks</b></a>).</li>
-  <li>Right-click the bookmark that you want to delete and select <b>Delete</b>
-    from the pop-up menu.</li>
-</ol>
-
-<p>If you have added bookmarks for specific lines within a source
-file, you can also delete them while editing the file by right-clicking the
-bookmark icon in the editor area.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" width="159" height="27"><br>
-<a href="../concepts/cbookmrk.htm">Bookmarks</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" width="159" height="27"><br>
-<a href="tasks-81b.htm">Creating a bookmark for an entire file</a><br>
-<a href="tasks-81.htm">Creating a bookmark within a file</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-84.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-84.htm
deleted file mode 100644
index 506e974..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-84.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Searching for text within a file</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body>
-<h1>Searching for text within a file</h1>
-
-<p>The <b>Go To</b> selection in the pop-up menu for one of the navigation views allows you
-to quickly find a resource in the Workbench by searching resource <i>names</i>.
-</p>
-
-<p>You can also do contextual searches for information that is contained <i>inside</i>
-files in the Workbench. To find all files that contain a particular string of characters:
-</p>
-
-<ol>
-  <li>On the main toolbar, click the 
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.search.ui.openSearchDialog")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Search</b></a> button <img src="../images/Image50_search.png"  alt="search icon" border="0">.</li>
-  <li>Type your search string in the <b>Containing Text</b> field, or use the 
-      pull-down list to select a previously entered search expression.<br> Use <code>\</code> as an escape 
-      character for search strings that contain the special characters <code>*</code>, <code>?</code>, or <code>\</code>, 
-	  (for example: <code>d:\\directory\\filename.ext</code>).</li>
-  <li>Finish entering your search options, (for example, to scope
-      the search to specified file types), and click <b>Search</b>.</li>
-  <li>The Search view displays the results of your search. Right-click on any item in
-      the Search view to open a pop-up menu that allows you to remove items from the
-      list, copy search results to the clipboard, or rerun the search. To open one of
-      the listed files, double-click it or select <b>Go to File</b> from its pop-up
-      menu.</li>
-</ol>
-
-<p>If you close the Search view, you can return to it later by selecting
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.search.ui.views.SearchView)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Search</b></a>.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/csearchview.htm">Search view</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-84b.htm">Searching for files</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-26.htm">Search view</a><br>
-<a href="../reference/ref-45.htm">File search</a>
-</p>
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-84b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-84b.htm
deleted file mode 100644
index da75ae4..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-84b.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Searching for files</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body>
-<h1>Searching for files</h1>
-
-<p>The <b>Go To &gt; Resource</b> action in the <b>Navigate</b> menu 
-allows you to quickly find a resource in the Workbench by searching resource <i>names</i>.
-</p>
-
-<p>You can also do more complex searches for files in the Workbench. For example, 
-to find all files that end with .xml:
-</p>
-
-<ol>
-  <li>On the main toolbar, click the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.search.ui.openSearchDialog")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Search</b></a> button <img src="../images/Image50_search.png" alt="Search icon" border="0" >.</li>
-  <li>Type <code>.xml</code> into the <b>File name patterns</b> field and leave 
-    the <b>Containing text</b> field empty. <br>
-    (You can use the pull-down list to select <code>.xml</code> if it had been previously entered.)</li>
-  <li>Finish entering your search options, for example to scope the search to 
-    specified working sets, and click <b>Search</b>.</li>
-  <li>The Search view displays the results of your search. Right-click on any 
-    item in the Search view to open a pop-up menu that allows you to remove items 
-    from the list, copy search results to the clipboard, or rerun the search. 
-    To open one of the listed files, double-click it or select <b>Go to File</b> 
-    from its pop-up menu.</li>
-</ol>
-<p>
-If you close the Search view, you can return to it later by selecting
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.search.ui.views.SearchView)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Search</b></a>.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/csearchview.htm">Search view</a>
-<a href="../concepts/cworkset.htm"><br>Working sets</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-84.htm">Searching for text within a file</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-26.htm">Search view</a><br>
-<a href="../reference/ref-45.htm">File search</a><br>
-</p>
-
-
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-87.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-87.htm
deleted file mode 100644
index 6cc9510..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-87.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Replacing a resource with local history</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Replacing a resource with local history</H1>
-
-<p>To replace a Workbench resource with a state in the local history:
-</p>
-
-<ol>
-  <li>In one of the navigation views, select the resource that you want to replace with 
-    a local history state.</li>
-  <li>From the resources pop-up menu, select <b>Replace with</b> &gt; <b>Local 
-    History</b>. The Replace from Local History page opens.</li>
-  <li>Select a state from the <b>Local History</b> list. The Text Compare editor opens.</li>
-  <li>Click the <b>Select Next Change</b> and <b>Select Previous Change</b> buttons 
-    to browse through the changes made between states in the local history and 
-    the Workbench resource.</li>
-  <li>Select the state you want to replace, and click <b>Replace</b>.</li>
-</ol>
-
-<P><em>Tip</em>: You can configure your general preferences to specify how many 
-  days to keep files, or how many entries per file you want to keep, or the maximum 
-  file size for files to be kept with the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.FileStates)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General &gt; Workspace &gt; Local History</b></a> preference page.
-</P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-17a.htm">Local history</a><br>
-<a href="../concepts/concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-70.htm">Comparing resources with the local history</a><br>
-<a href="tasks-87b.htm">Restoring deleted resources from the local history</a><br>
-<a href="tasks-88.htm">Setting local history preferences</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-87b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-87b.htm
deleted file mode 100644
index 1f54a1b..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-87b.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Restoring deleted resources from local history</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Restoring deleted resources from local history</H1>
-
-<p>To restore a deleted Workbench resource with a state from the local history:
-</p>
-
-<ol>
-  <li>In one of the navigation views, select the folder or project into which you want to restore  
-    a local history state.</li>
-  <li>From the resource's pop-up menu, select <b>Restore from Local History...</b>.
-  The Restore From Local History dialog opens showing all files that were previously contained
-  in the selected folder or project and all of their sub-folders.</li>
-  <li>Check the files that you want to restore</li>
-  <li>If you don't want to restore just the last state of a file you can 
-  select any other state of the file from the <b>Local History</b> list on the right hand side
-  of the dialog. The bottom pane of the dialog shows the contents of the state.</li>
-  <li>If you are done with all files click <b>Restore</b>.</li>
-</ol>
-
-<P><em>Tip</em>: You can configure your Workbench preferences to specify how many 
-  days to keep files, or how many entries per file you want to keep, or the maximum 
-  file size for files to be kept with the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.FileStates)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General &gt; Workspace &gt; Local History</b></a> preference page.
-</P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-17a.htm">Local history</a><br>
-<a href="../concepts/concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-70.htm">Comparing resources with the local history</a><br>
-<a href="tasks-87.htm">Replacing resources with the local history</a><br>
-<a href="tasks-88.htm">Setting local history preferences</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-88.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-88.htm
deleted file mode 100644
index 452412c..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-88.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Setting local history preferences</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Setting local history preferences</H1>
-
-<p>To indicate the level of local history that should be kept for 
-each resource in the Workbench:
-</p>
-
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.FileStates)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General &gt; Workspace &gt; Local History</b></a> preference page.</li>
-  <li>In the <b>Days to keep files</b> field, type the number of days that you 
-    want to keep records for any one Workbench resource. For example, if you type 
-    7, then a history of saved states from the last seven days will be kept.</li>
-  <li>In the <b>Entries per file</b> field, type the number of states to keep 
-    for any one Workbench resource. Note that when you exceed the number of 
-    entries per file, the oldest changes are discarded to make room for the newer 
-    changes.</li>
-  <li>In the <b>Maximum file size (MB)</b> field, type the maximum file size (in 
-    MB) of a resource for which a local history should be kept. If 
-    the size of the resource exceeds the maximum amount of file size allocated, 
-    no local history is kept for that resource.</li>
-  <li>Click <b>OK</b> to set your preferences and close the Local History Preferences page.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-17a.htm">Local history</a><br>
-<a href="../concepts/concepts-27.htm">Versions</a><br>
-<a href="../concepts/concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-70.htm">Comparing resources with the local history</a><br>
-<a href="tasks-87.htm">Replacing a resource with local history</a><br>
-<a href="tasks-87b.htm">Restoring deleted resources from local history</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-9.htm
deleted file mode 100644
index 1be8f6f..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Changing the placement of the tabs</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Changing the placement of the tabs</H1>
-
-<P>You can change the placement of the tabs.  The tabs for stacked views or editors can appear at the top or bottom
-of the area which contains them.
-</P>
-
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Views)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General &gt; Appearance</b></a> preference page.</li>
-  <li>Select from the choices displayed in the <b>Editor tab positions</b> group 
-    or <b>View tab positions</b> group to control whether you want the tabs at 
-    the top or the bottom.</li>
-  <li>Click <b>Apply</b> or <b>OK</b>.</li>
-  <li>The tabs will immediately move to their new locations.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-5.htm">Views</a><br>
-<a href="../concepts/concepts-6.htm">Editors</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-46.htm">Opening files for editing</a><br>
-<a href="tasks-3g.htm">Tiling editors</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-92.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-92.htm
deleted file mode 100644
index e700eb7..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-92.htm
+++ /dev/null

@@ -1,105 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating a CVS repository location</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Creating a CVS repository location</H1>
-
-<P><em>Prerequisite</em>: A CVS server must already be configured on the host machine to create a
-valid repository location in the Workbench.
-</P>
-
-<P>To create a new repository location:
-</P>
-
-<ol>
-  <li>Open the CVS Repositories view by selecting
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.team.ccvs.ui.RepositoriesView)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Window &gt; Show View &gt; Other... &gt; CVS &gt; CVS Repositories</b></a>.
-  Alternatively, the CVS Repositories view is also shown in the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.team.cvs.ui.cvsPerspective)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  CVS Repository Exploring</a> perspective.</li>
-  <li>On the toolbar, click on <strong>Add CVS Repository</strong> (or from the 
-    context menu of the CVS Repositories View, select <b>New &gt; Repository Location</b>). 
-    The Add CVS Repository wizard opens.</li>
-  <li>Enter the information required to identify and connect to the repository 
-    location: 
-    <ol type="a">
-      <li>In the <b> Host </b> field, type the address of the host. (For example: 
-        <samp>mymachine.com)</samp>. </li>
-      <li>In the <b> Repository path </b> field, type the path to the repository 
-        on the host (for example <samp>/home/repo, d:/repo.)</samp></li>
-      <li>In the <b> User </b> field, type the user name under which you want 
-        to connect to the repository. </li>
-      <li>In the <b>Password</b> field, type the password for the above user name.</li>
-      <li> From the <b> Connection Type</b> list, select the authentication protocol 
-        of the CVS server.&nbsp; There are three connection methods that come 
-        with the Eclipse CVS client: 
-        <ul>
-          <li><b>pserver</b> - a CVS specific connection method.</li>
-          <li><b>extssh</b> - an SSH 2.0 client included with Eclipse</li>
-          <li><b>ext</b> - the CVS ext connection method which uses an external 
-            tool such as SSH to connect to the repository. The tool used by ext 
-            is configured in the <b>Team &gt; CVS &gt; EXT Connection Method</b> 
-            preference page. </li>
-        </ul>
-      </li>
-      <li>If the host uses a custom port, enable <b>Use Port</b> and enter the 
-        port number.</li>
-    </ol>
-  </li>
-  <li>(Optional) Select <b>Validate Connection on Finish</b> if you want to authenticate 
-    the specified user to the specified host when you close this wizard. (If you 
-    do not select this option, the user name will be authenticated later, when 
-    you try to access the contents of the repository.)</li>
-  <li>(Optional) Select <strong>Save Password</strong> if you want to save the 
-    password in the Eclipse keyring file so you do not have to enter the password 
-    again the next time you start Eclipse. The keyring file is stored on your 
-    local drive and does not use strong encryption so you should not enable this 
-    option for sensitive passwords.</li>
-  <li> Click <b>Finish</b>. The repository location is created. </li>
-</ol>
-
-<p><strong>Note</strong>: Prior to Eclipse 3.0, the <strong>extssh</strong> connection 
-  method only supported SSH 1.0. In 3.0, this connection method was upgraded to 
-  support SSH 2.0 as well.</p>
-<p><em>Tip</em>: If you want to use the <strong>extssh</strong> connection method 
-  but want to keep your local workspace (sandbox) compatible with the CVS command 
-  line client, you can use the <strong>ext</strong> connection method and configure 
-  it to use <strong>extssh</strong> from inside Eclipse on the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.ExtMethodPreferencePage)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <strong>Team &gt; CVS &gt; Ext Connection Method</strong></a> preference page.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-  <a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-  <a href="../concepts/concepts-27c.htm">CVS Repositories</a> </p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-94.htm">Discarding a CVS repository location</a><br>
-<a href="tasks-93.htm">Refreshing the CVS repositories view</a><br>
-<a href="tasks-96.htm">Checking out a project from a CVS repository</a><br>
-<a href="tasks-110.htm">Discovering branch and version tags</a><br>
-<a href="tasks-95.htm">Changing the properties of a CVS Repository Location</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br>
-<a href="../reference/ref-47.htm">CVS</a><br>
-<a href="../reference/ref-32.htm">CVS Repositories view</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-93.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-93.htm
deleted file mode 100644
index 9b5f5da..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-93.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Refreshing the CVS Repositories view</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Refreshing the CVS Repositories view</H1>
-
-<P> There are two ways to refresh the CVS Repositories view in order to see the 
-current connection status of all repositories:
-</p>
-
-<ul>
-  <li>Click the <b>Refresh View</b> button on the view's toolbar&nbsp;</li>
-  <li>Press F5 on the keyboard</lI>
-</ul>
-
-<p><em>Note</em>: Refreshing the CVS Repositories view may change the resources 
-  displayed by the view but does not change the branch and version tags known 
-  to the view. Refreshing the tags is discussed in <a href="tasks-110.htm">Discovering 
-  branch and version tags</a></p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-  <a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-  <a href="../concepts/concepts-27c.htm">CVS Repositories</a> </p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-  <a href="tasks-92.htm">Creating a CVS repository location</a><br>
-  <a href="tasks-94.htm">Discarding a CVS repository location</a> <br>
-  <a href="tasks-110.htm">Discovering branch and version tags</a></p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br>
-<a href="../reference/ref-47.htm">CVS</a><br>
-<a href="../reference/ref-32.htm">CVS Repositories view</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-94.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-94.htm
deleted file mode 100644
index 398bf59..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-94.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Discarding a CVS repository location</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Discarding a CVS repository location</H1>
-
-<P><em>Note:</em> You cannot discard a location if you have projects in the Workbench that
-are shared with that location.
-</p>
-
-<P>To discard a CVS repository location:
-</p>
-
-<ol>
-  <li>Switch to the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.team.cvs.ui.cvsPerspective)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  CVS Repository Exploring</a> perspective or add the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.team.ccvs.ui.RepositoriesView)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  CVS Repositories</a> view to the current perspective.</li>
-  <li>In the CVS Repositories view, select the repository location that you want 
-    to delete from the Workbench.</li>
-  <li>Select <b>Discard Location</b> from the pop-up menu or press the DELETE 
-    key.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-92.htm">Creating a CVS repository location</a><a href="tasks-100b.htm"></a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br>
-<a href="../reference/ref-47.htm">CVS</a><br>
-<a href="../reference/ref-32.htm">CVS Repositories view</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-95.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-95.htm
deleted file mode 100644
index 6c20754..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-95.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Changing the properties of a CVS repository location</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Changing the properties of a CVS repository location</H1>
-
-<P>You can change the connection properties of an existing repository location.</p>
-
-<P>To change the properties of a CVS repository location:
-</p>
-
-<ol>
-  <li>Switch to the CVS Repository Exploring perspective or add the CVS Repositories 
-    view to the current perspective.</li>
-  <li>In the CVS Repositories view, select the repository location whose properties 
-    you want to change.</li>
-  <li>Select <b>Properties</b> from the pop-up menu. The properties dialog will 
-    open.</li>
-  <li>Select the <strong>CVS</strong> tab.</li>
-  <li>Change one or more of the location's properties.</li>
-  <li>Click <b>OK</b> to change the properties.</li> 
-</ol>
-
-<p><b>Note:</b> The properties will be changed for all projects shared with the selected repository location.</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-  <a href="tasks-92.htm">Creating a CVS repository location</a><br>
-  <a href="tasks-117b.htm">Changing the sharing of a Project</a><br>
-  <a href="tasks-95a.htm">Changing the encoding of a CVS repository location</a></p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br>
-<a href="../reference/ref-47.htm">CVS</a><br>
-<a href="../reference/ref-32.htm">CVS Repositories view</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-95a.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-95a.htm
deleted file mode 100644
index a889dc7..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-95a.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Changing the encoding of a CVS repository location</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Changing the encoding of a CVS repository location</H1>
-
-<P>You can change encoding of an existing repository location. This encoding will 
-  be used to translate file paths and commit messages from the client encoding 
-  to the server encoding and vice versa. The encoding does not affect the contents 
-  of file. You may use the editor encoding (available from the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.ContentTypes)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <strong>General &gt; Content Types</strong></a> preference page)
-  or resource encodings (available from the <strong>Properties&gt;Info</strong> 
-  page of resources) to configure the Workbench to use the proper file encodings.</p>
-
-<P>To change the server encoding of a CVS repository location: </p>
-
-<ol>
-  <li>Switch to the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.team.cvs.ui.cvsPerspective)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  CVS Repository Exploring</a> perspective or add the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.team.ccvs.ui.RepositoriesView)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  CVS Repositories</a> view to the current perspective.</li>
-  <li>In the CVS Repositories view, select the repository location whose properties 
-    you want to change.</li>
-  <li>Select <b>Properties</b> from the pop-up menu. The properties dialog will 
-    open.</li>
-  <li>Select the <strong>Server Encoding</strong> tab.</li>
-  <li>Choose to set the encoding and either choose or type in the desired encoding.</li>
-  <li>Click <b>OK</b> to change the properties.</li> 
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-  <a href="tasks-92.htm">Creating a CVS repository location</a></p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br>
-<a href="../reference/ref-47.htm">CVS</a><br>
-<a href="../reference/ref-32.htm">CVS Repositories view</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-96.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-96.htm
deleted file mode 100644
index c35ee7b..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-96.htm
+++ /dev/null

@@ -1,135 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Checking out a project from a CVS repository</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Checking out a project from a CVS repository</H1>
-
-<P>Projects can be checked out from a CVS repository into the Workbench using 
-  the Checkout wizard or from the CVS Repositories view.</P>
-<h2>Checking out using the Checkout Wizard</h2>
-<p>It is available from the Import menu, the New &gt; Project menu and the toolbar 
-  of the CVS Repository Exploring perspective. It is also opened when performing 
-  a Checkout As from the CVS Repositories view.</p>
-<ol>
-  <li>Launch the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import(importWizardId=org.eclipse.team.cvs.ui.newProjectCheckout)")'>
-    <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-    Checkout wizard</a>. It is available from the <strong>Import</strong> 
-    menu, the <strong>New &gt; Project</strong> menu and the toolbar of the CVS 
-    Repository Exploring perspective. It is also opened when performing a Checkout 
-    As from the CVS Repositories view. (<strong>Note</strong>: If the CVS capability 
-    is disabled, the Checkout wizard may only be available from the <strong>Import</strong> 
-    menu).</li>
-  <li>Select the desired repository from the list of known repositories or, if 
-    the desired repository is not in this list, choose to create a new repository 
-    location and click <b>Next</b>.</li>
-  <li>If entering a new repository location, enter the repository information 
-    and click <b>Next</b> when completed. <b>(Note</b>: this page is the same 
-    format as the <a href="tasks-92.htm">Creating a CVS repository location</a> 
-    wizard.)</li>
-  <li>Either select one or more modules from the list of existing modules or type 
-    in the name of the module to be checked out. Entering a name is supported 
-    for those situations where obtaining the list of existing modules from the 
-    server is impractical or unsupported. You can also enter a dot (.) as the 
-    module name if the repository is configured to host a single project at its 
-    root. Click <strong>Next</strong> when the module or modules to be checked 
-    out are specified.</li>
-  <li>(Optional) Choose whether to check out one or more selected modules as a 
-    new projects or into an existing project or folder. If one module is selected 
-    and it does not contain a .project file (the Workbench project configuration 
-    file), you will also have the option to configure the project using the New 
-    Project wizard (in order to make the project a Java project, for instance). 
-    Click <strong>Next</strong>.</li>
-  <li>(Optional) For a single project, you can configure the location of the project 
-    to be either the default location or a custom location outside the workspace. 
-    For multiple projects, you can configure the parent folder where all the projects 
-    should be located. Click <strong>Next</strong>.</li>
-  <li>(Optional) Select the tag to check out from and click <strong>Finish</strong>.</li>
-</ol>
-<h2>Checking out from the CVS Repositories view</h2>
-<P>To check out a project from the CVS repositories view to the Workbench: </P>
-
-<ol>
-  <li>Switch to the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.team.cvs.ui.cvsPerspective)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  CVS Repository Exploring</a> perspective or add the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.team.ccvs.ui.RepositoriesView)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  CVS Repositories</a> view to the current perspective.</li>
-  <li>In the CVS Repositories view, expand the repository location.</li>
-  <li>Expand <b>HEAD</b> and select the folders that you want to add as projects 
-    to the Workbench. If you are looking for a folder in a particular version: 
-    <ol type="a">
-      <li>Expand the <b> Versions</b> category and find the folder name 
-        that you want to add to the Workbench.</li>
-      <li>Expand the folder to reveal its versions.</li>
-    </ol>
-	<p>If you are looking for the latest folder in a branch:</p>
-    <ol type="a">
-      <li>Expand the <b> Branches</b> category.</li>
-      <li>Expand the branch that holds the folder that you want to add to the 
-        Workbench.</li>
-    </ol>
-  </li>
-  <li>From the pop-up menu for the selected folders, select one of the following: 
-    <ol type="a">
-      <li><b>Check Out </b> to check out each of the selected folders as a project 
-        in the local workspace with the same name as the folder in the repository.</li>
-      <li><b>Check Out As...</b> to check out the selected folders into a custom 
-        configured project in the local workspace. <em>Note:</em> When multiple 
-        folders are selected, this operations only allows the specification of 
-        a custom parent location for the new projects.</li>
-    </ol>
-  </li>
-  <li>If <b>Check Out As...</b> was chosen on a single project, one of two possible 
-    dialogs is displayed depending on whether the folder in the repository contains 
-    a .project file or not. 
-    <ol type="a">
-      <li>If there is a .project file, the dialog will accept a custom project 
-        name and location.</li>
-      <li>Otherwise, the dialog will be the New Project wizard which allows full 
-        customization of the project (e.g. Java project).</li>
-    </ol>
-  </li>
-</ol>
-
-<p><em>Tip:</em> Any folder, including non-root folders, can be checked out from 
-a CVS repository.
-</p>
-  
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-96a.htm">Checking out a module from a CVS repository</a><br>
-<a href="tasks-96b.htm">Checking out a folder into an existing project</a><br>
-<a href="tasks-92.htm">Creating a CVS repository location</a><br>
-<a href="tasks-103.htm">Replacing resources in the Workbench</a><br>
-<a href="tasks-110.htm">Discovering branch and version tags</a><br>
-<a href="tasks-117.htm">Sharing a new project using CVS</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br>
-  <a href="../reference/ref-47.htm">CVS</a><br>
-  <a href="../reference/ref-32.htm">CVS Repositories view</a><br>
-  <a href="../reference/ref-40a.htm">CVS Checkout wizard</a></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-96a.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-96a.htm
deleted file mode 100644
index 1d86eea..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-96a.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Checking out a module from a CVS repository</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Checking out a module from a CVS repository</H1>
-
-<P>Modules can be defined in the CVSROOT/modules file of a CVS repository. To check out such a module from a 
-CVS repository to the Workbench:
-</P>
-
-<ol>
-  <li>Switch to the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.team.cvs.ui.cvsPerspective)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  CVS Repository Exploring</a> perspective or add the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.team.ccvs.ui.RepositoriesView)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  CVS Repositories</a> view to the current perspective.</li>
-  <li>In the CVS Repositories view, expand the repository location.</li>
-  <li>Expand <b>HEAD</b> and select the modules that you want to add to the Workbench. 
-    <em>Note</em>: Modules appear as root folders of the repository but are associated 
-    with the <img src="../images/tasks-96b-module_rep.png" alt="CVS module icon" border="0" > 
-    icon.</li>
-  <li>From the pop-up menu select <b>Check Out</b>. This will checkout the module 
-    into one or more projects in the local workspace, depending on how the module 
-    is defined in the repository.</li>
-</ol>
-<p><strong>Note</strong>: Defined modules can also be checkout out using the Checkout 
-  Wizard.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-96.htm">Checking out a project from a CVS repository</a><br>
-<a href="tasks-96b.htm">Checking out a folder into an existing project</a><br>
-<a href="tasks-92.htm">Creating a CVS repository location</a><br>
-<a href="tasks-103.htm">Replacing resources in the Workbench</a><br>
-<a href="tasks-110.htm">Discovering branch and version tags</a><br>
-<a href="tasks-117.htm">Sharing a new project using CVS</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br>
-  <a href="../reference/ref-47.htm">CVS</a><br>
-  <a href="../reference/ref-32.htm">CVS Repositories view</a><br>
-  <a href="../reference/ref-40a.htm">CVS Checkout wizard</a></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-96b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-96b.htm
deleted file mode 100644
index eb5693c..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-96b.htm
+++ /dev/null

@@ -1,77 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Checking out a folder into an existing project</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Checking out a folder into an existing project</H1>
-
-<P>To check out a folder from a CVS repository into an existing project in the 
-  Workbench, you can use either the <strong>Checkout</strong> wizard or <strong>Check 
-  Out As</strong> from the CVS Repositories view. Follow these steps to use the 
-  Checkout wizard.</P>
-
-<ol>
-  <li>Launch the <a href="../reference/ref-40a.htm">CVS Checkout wizard</a>.</li>
-  <li>Select the desired repository from the list of known repositories or, if 
-    the desired repository is not in this list, choose to create a new repository 
-    location and click <b>Next</b>. If entering a new repository location, enter 
-    the repository information and click <b>Next</b> when completed.</li>
-  <li>Either select one or more modules from the list of existing modules or type 
-    in the name of the module to be checked out and click <strong>Next</strong>.</li>
-  <li>Choose whether to check out one or more selected modules into an existing 
-    project or folder. you can provide the following information: 
-    <ol>
-      <li><strong>Target folder name</strong>: (only when checking out a single 
-        module) The name of a local folder in which the contents of the remote 
-        folder will be placed. <em>Note</em>: If the local folder exists, its 
-        contents will be deleted and replaced by the contents of the remote folder.</li>
-      <li><strong>Parent of target folder</strong>: The existing local folder 
-        into which the target folders will be created.</li>
-      <li><strong>Checkout sub-folders</strong>: The option to indicate whether 
-        the sub-folders of the remote folder should be checked out as children 
-        of the target folder.</li>
-    </ol>
-  </li>
-  <li>(Optional) Select the tag to check out from and click <strong>Finish</strong>.</li>
-</ol>
-
-<p><em>Note:</em> Only folders within non-shared projects or projects shared with 
-  the same CVS repository as the selected remote folder are valid targets for 
-  the <em>Checkout Into</em> operation. Also, if the target project of the operation 
-  is an unshared project, the project will be connected to the CVS repository 
-  (i.e. the project will become a shared CVS project) but any pre-existing content 
-  will be ignored.</p>
-  
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-96.htm">Checking out a project from a CVS repository</a><br>
-<a href="tasks-96a.htm">Checking out a module from a CVS repository</a><br>
-<a href="tasks-92.htm">Creating a CVS repository location</a><br>
-<a href="tasks-103.htm">Replacing resources in the Workbench</a><br>
-<a href="tasks-110.htm">Discovering branch and version tags</a><br>
-<a href="tasks-117.htm">Sharing a new project using CVS</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br>
-  <a href="../reference/ref-47.htm">CVS</a><br>
-  <a href="../reference/ref-32.htm">CVS Repositories view</a><br>
-  <a href="../reference/ref-40a.htm">CVS Checkout wizard</a></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-9b.htm
deleted file mode 100644
index 038cfbe..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9b.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating fast views</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Creating fast views</H1>
-
-<p>Fast views are hidden views that can be quickly opened and closed. They work 
-  like other views except they do not take up space in your Workbench window.
-</p>
-
-<p>To create a fast view:</p>
-<ol>
-  <li>Click the title bar of the view that you want. Hold the mouse button down.</li>
-  <li>Drag the view to the shortcut bar and release the mouse button. By default the shortcut bar is located in the lower left corner of the window.</li>
-</ol>
-
-<p>The icon for the view that you dragged now appears on the shortcut 
-  bar. You can look at the view by clicking its icon on the shortcut bar. As soon 
-  as you click somewhere else outside the view, it is hidden again.
-</p>
-
-<p>To restore the view to its original location (to delete the fast 
-  view), toggle the fast view item in the view button's context menu.
-</p>
-
-<p>You can also create and restore fast views by selecting <b>Fast 
-  View</b> from the context menu that opens when you click the 
-  icon at the left side of the view's title bar.
-</p>
-  
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="../concepts/concepts-5.htm">Views</a><br>
-<a href="../concepts/concepts-21.htm">Fast views</a><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-9c.htm">Working with fast views</a><br>
-<a href="tasks-3.htm">Opening views</a><br>
-<a href="tasks-3e.htm">Moving and docking views</a><br>
-<a href="tasks-3i.htm">Maximizing a view or editor</a><br>
-<a href="tasks-9i.htm">Saving a user-defined perspective</a><br>
-<a href="tasks-9j.htm">Resetting perspectives</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9c.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-9c.htm
deleted file mode 100644
index 067eb77..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9c.htm
+++ /dev/null

@@ -1,104 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working with fast views</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Working with fast views</H1>
-<p CLASS="Head">If you have converted the Navigator to a fast view it will
-appear in the shortcut bar as shown below.&nbsp;</p>
-<blockquote>
-  <p CLASS="Head"><img src="../images/Image60_fast_view1.png" alt="Show fast view" border="0" ></p>
-</blockquote>
-  <p CLASS="Head">To work with a fast view proceed as follows.</p>
-<TABLE BORDER="0" cellspacing="0" cellpadding="3">
-<THEAD>
-</THEAD>
-<TBODY>
-<TR>
-<TD COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<b>
-1.</b>
-</P>
-</TD>
-<TD COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">In the shortcut bar click on the Navigator fast view button.</P>
-</TD>
-</TR>
-<TR>
-<TD COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<b>2.</b>
-</P>
-</TD>
-<TD COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Observe the Navigator view slides out from the shortcut bar.&nbsp; </P>
-        <P CLASS="Para"> <img src="../images/Image61_nav_fast.png" alt="Fast view" border="0" ></P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<b>3.</b>
-</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-You can use the Navigator fast view as you would normally.&nbsp;&nbsp; </P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<b>4.</b>
-</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-To hide the fast view simply click off of it or click on the Minimize button on
-the fast view's toolbar </P>
-<P CLASS="Para">
-<img src="../images/Image61_fast_minimize.png" alt="Minimize button" border="0" > </P>
-<P CLASS="Para">&nbsp; </P>
-        <P CLASS="Para"><strong>Note:</strong> If you open a file from the Navigator 
-          fast view, the fast view will automatically hide itself to allow you 
-          to work with the file.&nbsp;&nbsp; </P>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-<P>To convert a fast view that has been maximized back to a regular sized view, 
-  select <strong>Restore </strong>from the context menu of the icon in the top 
-  left corner of the view. To reposition a fast view, drag the fast view's title 
-  bar (or close the fast view and then drag its button from the shortcut bar) 
-  and drop it on the workbench like a normal view.</P>
-<p></p>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts."  ><br>
-  <a href="../concepts/concepts-5.htm">Views</a><br>
-  <a href="../concepts/concepts-21.htm">Fast views</a><br>
-  <a href="../concepts/concepts-4.htm">Perspectives</a> </P>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"  ><br>
-<a href="tasks-9b.htm">Creating fast views</a><br>
-<a href="tasks-3.htm">Opening views</a><br>
-<a href="tasks-3e.htm">Docking views</a><br>
-<a href="tasks-3i.htm">Maximizing a view or editor</a><br>
-<a href="tasks-9i.htm">Saving a user defined perspective</a><br>
-<a href="tasks-9j.htm">Resetting perspectives</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9d.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-9d.htm
deleted file mode 100644
index aa04f63..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9d.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Deleting a user defined perspective</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Deleting a user defined perspective</H1>
-<P>You can delete perspectives that you defined yourself, but not
-those that are delivered with the Workbench.</P>
-<ol>
-  <li>Open the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Perspectives)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General &gt; Perspectives</b></a> preference page.</li>
-  <li>From the <b>Available perspectives</b> list, select the one that you want
-    to delete and click <b>Delete</b>.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." width="159" height="27"><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" width="159" height="27"><br>
-<a href="tasks-9i.htm">Saving a user defined perspective</a><br>
-<a href="tasks-9j.htm">Resetting perspectives</a>
-</p>
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9f.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-9f.htm
deleted file mode 100644
index e6523a0..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9f.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Opening perspectives</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Opening perspectives</H1>
-<p>Perspectives provide combinations of views and editors that are
-suited to performing a particular set of tasks. For example, you would normally
-open the Debug perspective to debug a Java program.
-</p>
-
-<p>To open a new perspective:</p>
-<ol>
-  <li>Click the <b>Open Perspective</b> button 
-      <img border="0" src="../images/ref-52.png"  alt="Open Perspective button"> 
-      on the shortcut bar on the left side of the Workbench window. (This provides 
-      the same function as the <b>Window &gt; Open Perspective</b> menu on the menu bar.)</li>
-  <li> To see a complete list of perspectives, select <b>Other...</b>
-    from the drop-down menu.</li>
-  <li>Select the perspective that you want to open.</li>
-</ol>
-
-<p>When the perspective opens, the title bar of the window it is in changes to
-display the name of the perspective. In addition, an icon is added to the shortcut bar, 
-allowing you to quickly switch back to that perspective from other perspectives in the same
-window.
-</p>
-
-<p>
-By default, a perspective will open in the same window.
-If you would rather it opened in a new window, change the setting in the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Perspectives)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>General &gt; Perspectives</b></a> preference page.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-3.htm">Opening views</a><br>
-<a href="tasks-24.htm">Changing where perspectives open</a><br>
-<a href="tasks-31.htm">Specifying the default perspective</a><br>
-<a href="tasks-28.htm">Switching between perspectives</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9i.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-9i.htm
deleted file mode 100644
index a4ecd15..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9i.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Saving a user defined perspective</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Saving a user defined perspective</H1>
-<P>If you have modified a perspective by adding, deleting, or
-moving (docking) views, you can save your changes for future use.
-</P>
-
-<ol>
-  <li>Switch to the perspective that you want to save.</li>
-  <li>Click <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.savePerspective")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Window &gt; Save Perspective As...</b></a>.</li>
-  <li>Type a new name for the perspective into the <b>Name</b> field.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p>The name of the new perspective is added to the <b>Window &gt; Open Perspective</b> menu.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a><br>
-<a href="../concepts/concepts-5.htm">Views</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-9j.htm">Resetting perspectives</a><br>
-<a href="tasks-9d.htm">Deleting a user defined perspective</a><br>
-<a href="tasks-3.htm">Opening views</a><br>
-<a href="tasks-3e.htm">Moving and docking views</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9j.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-9j.htm
deleted file mode 100644
index 8fe5fc4..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9j.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Resetting perspectives</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Resetting perspectives</H1>
-<p>To restore a perspective to its original layout:</p>
-<ol>
-  <li>Open the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Perspectives)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General > Perspectives</b></a> preference page.</li>
-  <li>From the <b>Available perspectives</b> list, select the perspective you want to restore.</li>
-  <li>Click <b>Reset</b>.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-9i.htm">Saving a user defined perspective</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9k.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-9k.htm
deleted file mode 100644
index c68bf23..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9k.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Configuring perspectives</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Configuring perspectives</H1>
-<p>In addition to configuring the layout of your perspective you
-can also control several other key aspects of a perspective. These include:
-</p>
-<ul>
-  <li>The options available on the <b>File &gt; New</b> submenu.</li>
-  <li>The options available on the <b>Window &gt; Open Perspective</b> submenu.</li>
-  <li>The options available on the <b>Window &gt; Show View</b> submenu.</li>
-  <li>Action sets (buttons and menu options) that show up on the toolbar and menu bar.</li>
-</ul>
-
-<p>To configure a perspective:</p>
-<ol>
-  <li>Switch to the perspective that you want to configure.</li>
-  <li>Select <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.customizePerspective")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Window &gt; Customize Perspective...</b></a>.</li>
-  <li>Expand the item that you want to customize.</li>
-  <li>Use the checkboxes to select which elements you want to see
-    on drop-down menus in the selected perspective. Items you do not select will still be
-    accessible by clicking the <b>Other</b> menu option.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-24.htm">Changing where perspectives open</a><br>
-<a href="tasks-31.htm">Specifying the default perspective</a><br>
-<a href="tasks-9i.htm">Saving a user defined perspective</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-activites.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-activites.htm
deleted file mode 100644
index 0de7103..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-activites.htm
+++ /dev/null

@@ -1,27 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Activities Example</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Activities Example</h2>
-<p>The following plug-in contains an example of two different activity techniques. 
-  The first technique demonstrates how activities can be used to filter a specific 
-  contribution, in this case, the Problems view. The second technique is to filter 
-  an entire plug-in.</p>
-<p><strong>Note: </strong>For the end user, Activities are referred to as Capabilities 
-  in the UI.</p>
-<pre CLASS="Para">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;<br>&lt;?eclipse version=&quot;3.0&quot;?&gt;<br>&lt;plugin<br>   id=&quot;org.eclipse.ui.examples.activities.simple&quot;<br>   name=&quot;Simple Activities Plug-in&quot;<br>   version=&quot;1.0.0&quot;<br>   provider-name=&quot;IBM&quot;&gt;<br>   &lt;requires&gt;<br>      &lt;import plugin=&quot;org.eclipse.ui&quot;/&gt;<br>   &lt;/requires&gt;<br>   <br>   &lt;!-- Define the Examples category --&gt;<br>   &lt;extension<br>         point=&quot;org.eclipse.ui.activities&quot;&gt;<br>      &lt;category<br>            description=&quot;Contains bindings declared in the org.eclipse.ui.examples.activities.simple plugin.&quot;<br>            name=&quot;Examples&quot;<br>            id=&quot;org.eclipse.ui.examples.activities.simple.Category&quot;/&gt;<br>   &lt;/extension&gt;<br>   <br>   &lt;!-- The following extension will filter out the Problems View--&gt;<br>   &lt;extension<br>         point=&quot;org.eclipse.ui.activities&quot;&gt;<br>      &lt;activity<br>            description=&quot;Allows usage of the Problems View&quot;<br>            name=&quot;Problems View Filter&quot;<br>            id=&quot;org.eclipse.ui.examples.activities.simple.Problems&quot;/&gt;<br>      &lt;activityPatternBinding<br>            activityId=&quot;org.eclipse.ui.examples.activities.simple.Problems&quot;<br>            pattern=&quot;org\.eclipse\.ui\.ide/org\.eclipse\.ui\.views\.ProblemView&quot;/&gt;<br>      &lt;categoryActivityBinding<br>            activityId=&quot;org.eclipse.ui.examples.activities.simple.Problems&quot;<br>            categoryId=&quot;org.eclipse.ui.examples.activities.simple.Category&quot;/&gt;<br>      &lt;defaultEnablement id=&quot;org.eclipse.ui.examples.activities.simple.Problems&quot;/&gt;<br>   &lt;/extension&gt;<br>   <br>   &lt;!-- The following extension will filter all contributions from the org.eclipse.team* plugins --&gt;<br>   &lt;extension<br>         point=&quot;org.eclipse.ui.activities&quot;&gt;<br>      &lt;activity<br>            id=&quot;org.eclipse.ui.examples.activities.simple.Team&quot;<br>            description=&quot;Filters all &amp;quot;Team&amp;quot; contributions.&quot;<br>            name=&quot;Team Views Filter&quot;/&gt;<br>      &lt;activityPatternBinding<br>            activityId=&quot;org.eclipse.ui.examples.activities.simple.Team&quot;<br>            pattern=&quot;org\.eclipse\.team.*/.*&quot;/&gt;<br>      &lt;categoryActivityBinding<br>            activityId=&quot;org.eclipse.ui.examples.activities.simple.Team&quot;<br>            categoryId=&quot;org.eclipse.ui.examples.activities.simple.Category&quot;/&gt;<br>   &lt;/extension&gt;<br>&lt;/plugin&gt;</pre>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-  <a href="../concepts/concepts-activites.htm">Activities</a> </P>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-  <a href="../reference/ref-activitiespref.htm">Capabilities</a>
-</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-addtasksandtypes.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-addtasksandtypes.htm
deleted file mode 100644
index e7fc1eb..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-addtasksandtypes.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Adding new Ant tasks and types</title>
-<meta name="keyword" content="ant">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Adding new Ant tasks and types</H1>
-
-<p>Add new Ant tasks and types through the Ant preferences page. These tasks and 
-types will be available for buildfiles running in the Workbench without, having 
-to use taskdef or typedef in the script declaration (For more on taskdef or 
-typedef see the Ant documentation in
-<a href="http://ant.apache.org/index.html" target="_blank">http://ant.apache.org</a>).
-</p>
-
-<p>To add a new task or type:</p>
-
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ant.ui.AntRuntimePreferencePage)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Ant &gt; Runtime</b></a> preference page.</li>
-  <li>Click the <b>Tasks</b> tab or the <b>Types</b> tab.</li>
-  <li>Click <b>Add Task</b> or <b>Add Type</b>.</li>
-  <li>Provide a name and class for the task or type.</li>
-  <li>Select the library where the task or type is declared. If the library is not present on the list, 
-    you must add it to the Ant classpath (see the Related task link below).</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-antsupport.htm">Ant Support</a><br>
-<a href="../concepts/concepts-22.htm">Builds</a><br>
-<a href="../concepts/concepts-exttools.htm">External tools</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-exttools-running.htm">Running external tools</a><br>
-<a href="../tasks/tasks-ant-classpath.htm">Modifying the Ant classpath</a><br>
-<a href="../tasks/tasks-ant-version.htm">Using a different version of Ant</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-classpath.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-classpath.htm
deleted file mode 100644
index 7d1ae07..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-classpath.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Modifying the Ant classpath</title>
-<meta name="keyword" content="ant">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Modifying the Ant classpath</H1>
-
-<p>When using an optional or custom task it is usually necessary to add extra 
-  libraries to the classpath. The Ant classpath can be modified globally or per
-  launch configuration.
-</p>
-
-<p>To modify the Ant classpath globally:</p>
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ant.ui.AntRuntimePreferencePage)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Ant &gt; Runtime</b></a> preference page.</li>
-  <li>If you are not on it already, click the <b>Classpath</b> tab.</li>
-  <li>To add a JAR file to the classpath, click <b>Add Jar</b> and select the JAR file.</li>
-  <li>To add a folder to the classpath, click <b>Add Folder</b> and select the folder.</li>
-  <li>To remove an item from the classpath, select it and click <b>Remove</b>.</li>
-  <li>To restore the classpath to the default, click <b>Restore Defaults</b>.</li>
-</ol>
-
-<p>To modify the Ant classpath for a launch configuration:</p>
-<ol>
-  <li>Click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.externalTools.commands.OpenExternalToolsConfigurations")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Run &gt; External Tools &gt; External Tools...</b></a>.</li>
-  <li>Select the Ant configuration whose classpath you wish to modify</li>
-  <li>Select the <b>Classpath</b> tab</li>
-  <li>To add a JAR file to the classpath, click <b>Add Jar</b> and select the JAR file.</li>
-  <li>To add a folder to the classpath, click <b>Add Folder</b> and select the folder.</li>
-  <li>To remove an item from the classpath, select it and click <b>Remove</b>.</li>
-</ol>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-antsupport.htm">Ant support</a><br>
-<a href="../concepts/concepts-exttools.htm">External tools</a><br>
-</P>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="./tasks-ant-running.htm">Running Ant buildfiles</a><br>
-<a href="../tasks/tasks-exttools-running.htm">Running external tools</a><br>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-running.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-running.htm
deleted file mode 100644
index 9a7409d..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-running.htm
+++ /dev/null

@@ -1,61 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Running Ant buildfiles</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Running Ant buildfiles</H1>
-
-<p>To run an Ant buildfile in the Workbench:
-</p>
-<ol>
-  <li>In one of the navigation views, select an XML file.</li>
-  <li>From the file's pop-up menu, select <b>Run Ant...</b>. The launch configuration
-  	dialog opens.</li>
-  <li>Select one or more targets from the <b>Targets</b> tab. The order 
-    in which you select the items is the order in which they will run. The order 
-    is displayed in the <b>Target execution order</b> box at the bottom of the tab.
-    You can change the order of the targets by clicking the <b>Order...</b> button.</li>
-  <li>(Optional) Configure options on the other tabs. For example, on the <b>Main</b> tab,
-    type any required arguments in the <b>Arguments</b> field.</li>
-  <li>Click <b>Run</b>.</li>
-</ol>
-
-<p>The Ant buildfile will run on the selected targets. Unless you disabled the <b>Capture
-output</b> option on the <b>Main</b> tab, the console displays any applicable execution results 
-as the buildfile runs.
-</p>
-
-<p>These steps create a persisted launch configuration. The newly created configuration will
-appear in the launch history under <b>Run &gt; External Tools</b> and will be available in the
-launch configuration dialog which is opened by clicking
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.externalTools.commands.OpenExternalToolsConfigurations")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Run &gt; External Tools &gt; External Tools...</b></a>.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-antsupport.htm">Ant support</a><br>
-<a href="../concepts/concepts-22.htm">Builds</a><br>
-<a href="../concepts/concepts-exttools.htm">External tools</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-exttools-running.htm">Running external tools</a><br>
-<a href="../tasks/tasks-ant-classpath.htm">Modifying the Ant classpath</a><br>
-<a href="../tasks/tasks-ant-version.htm">Using a different version of Ant</a><br>
-<a href="../tasks/tasks-ant-addtasksandtypes.htm">Adding new Ant tasks and types</a><br>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-version.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-version.htm
deleted file mode 100644
index 00f5e7c..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-version.htm
+++ /dev/null

@@ -1,89 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Using a different version of Ant</title>
-<meta name="keyword" content="ant">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Using a different version of Ant</H1>
-
-<P> The Eclipse platform provides Ant 1.6.5 as a plug-in library. When running 
-an Ant buildfile in the Workbench, version 1.6.5 is used by default. It is possible 
-to use different versions, although they are not supported. There are at least 
-two ways of using a different version of Ant:
-</P>
-
-<dl>
-<dt><b>Changing the Ant runtime classpath:</b></dt>
-<dd>When Ant runs a buildfile, it looks for the necessary classes on the Ant classpath. 
-The Ant classpath consists of the plug-ins contributing new tasks, types or 
-libraries, plus the classpath defined in the Ant runtime classpath preferences. To 
-access the preferences, click
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ant.ui.AntRuntimePreferencePage)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Window &gt; Preferences &gt; Ant &gt; Runtime</b></a>. 
-The JARs related to Ant 1.6.5 are grouped under the <b>Ant Home Entries</b> item.
-To change the Ant Home entries, click on the <b>Ant Home...</b> button and choose the Ant
-installation you wish to use.
-
-<p>After you change the Ant classpath, all future Ant builds will use the updated 
-version instead of the default. To restore the Ant classpath to its original 
-state, <b>Restore Defaults</b> button on the preference page.
-</p>
-</dd>
-<dt><b>Using Ant as an external tool:</b></dt>
-<dd>When changing the Ant classpath is not an option, or if you just want to test 
-a newer or beta version of Ant, using it as an external tool is an option. 
-Usually when it is running in the Workbench, the Ant buildfile 
-itself is considered to be a external tool, but this is not the only way. 
-To install a binary distribution of Ant as an external tool (<b>Note:</b> 
-These steps are for Windows, but similar methods can be used for other operating systems): 
-<ol type="a">
-  <li>Download and install the binary version of Ant from
-    <a href="http://ant.apache.org" target="_blank">http://ant.apache.org</a> .</li>
-  <li>Click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.externalTools.commands.OpenExternalToolsConfigurations")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Run &gt; External Tools &gt; External Tools...</b></a>.</li>
-  <li>Click <b>Program</b></li>
-  <li>Click <b>New</b>.</li>
-  <li>Enter a name for your external tool (for example, External Ant).</li>
-  <li>For the <b>Location</b> field, click <b>Browse File System</b>.</li>
-  <li>Find and select a file called <code>ant.bat</code> (it should be 
-  in the <code>bin</code> folder of your Ant installation).</li>
-  <li>In the <b>Arguments</b> field enter the arguments for your 
-    buildfile that would normally enter for running the buildfile outside of the 
-    Workbench.</li>
-  <li>In the <b>Working Directory</b> field enter the directory of your buildfile.</li>
-  <li>Click <b>Run</b> to execute the buildfile.</li>
-</ol>
-
-<p>When you run Ant as an external tool, none of the tasks or types 
-contributed by Eclipse will work. Also, the Ant classpath preference has no 
-effect in the buildfile execution.
-</p>
-</dd>
-</dl>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-antsupport.htm">Ant Support</a><br>
-<a href="../concepts/concepts-exttools.htm">External tools</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="./tasks-ant-running.htm">Running Ant buildfiles</a><br>
-<a href="../tasks/tasks-exttools-running.htm">Running external tools</a><br>
-<a href="../tasks/tasks-ant-classpath.htm">Modifying the Ant classpath</a><br>
-<a href="../tasks/tasks-ant-addtasksandtypes.htm">Adding new Ant tasks and types</a><br>
-</p>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-10.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-10.htm
deleted file mode 100644
index df4e4fb..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-10.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Disconnecting a project from CVS</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Disconnecting a project from CVS</H1>
-
-<P>Disconnect a project from CVS to disable the CVS operations that can be performed 
-  on the project and it resources and optionally to remove the CVS information 
-  (stored in the CVS folders) associated with the project. </P>
-
-<P>To disconnect a project from CVS:
-</P>
-
-<ol>
-  <li>In one of the navigation views, select the project to be disconnected.</li>
-  <li>Select <b>Team &gt; Disconnect</b> from the project's pop-up menu. The Confirm 
-    Disconnect from CVS dialog opens.</li>
-  <li>In the dialog, choose one of: 
-    <ol type="a">
-      <li><b>Delete the CVS meta information</b> - disables the CVS team menu 
-        operations and removes the CVS folders and their contents from the file 
-        system.</li>
-      <li><b>Do not delete the CVS meta information</b> - disables the CVS team menu 
-        operations but leaves the CVS meta information.</li>
-    </ol></li>
-  <li>Click <b>Yes</b> to disconnect the project.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-96.htm">Checking out a project from the CVS repository</a><br>
-<a href="tasks-103.htm">Replacing resources in the Workbench</a><br>
-<a href="tasks-100a.htm">Branching</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-113.htm">Updating</a><br>
-<a href="tasks-113b.htm">Resolving conflicts</a><br>
-<a href="tasks-100b.htm">Merging from a branch</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-47.htm">CVS</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-11.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-11.htm
deleted file mode 100644
index a10755e..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-11.htm
+++ /dev/null

@@ -1,78 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Setting the CVS keyword substitution mode</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Setting the CVS keyword substitution mode</H1>
-
-<P>CVS uses the keyword substitution mode of a file to differentiate binary files 
-from ASCII files and to indicate what type of keyword substitution is to take 
-place when files are committed and checked out.
-</P>
-  
-<P>To set the CVS keyword substitution mode:
-</P>
-
-<ol>
-  <li>In one of the navigation views, select the files or containing folders for which 
-    a change in keyword substitution mode is desired. <b>Note</b>: Ensure that 
-    any new files that are to be committed are added to CVS version control as 
-    the keyword substitution mode can only be set for files that are already under 
-    CVS control.</li>
-  <li>From the pop-up menu, select<b> Team &gt; Change ASCII/Binary Property</b>. 
-    The Set Keyword Substitution Mode wizard will open.</li>
-  <li>The wizard contains a list of all founds found in the selection. On this 
-    page, you can do the following: 
-    <ul>
-      <li>You can enter a file pattern to filter the list of files.</li>
-      <li>You can change the mode for files individually.</li>
-      <li>You can select multiple files and change the mode for the all using 
-        the drop down at the bottom of the page.</li>
-      <li>You can select multiple files and click <strong>Propose</strong> which 
-        determines the mode based on your preference settings.</li>
-      <li>You can check the <em>Show changes </em>options to see all the files 
-        whose mode has been changed in the wizard.</li>
-    </ul>
-  </li>
-  <li>When you are done specifying the new modes for any files, enter the commit 
-    comment to be associated with any file commits. Files will need to be committed 
-    if changing the file type from Binary to ASCII results in a change in the 
-    file content due to line terminator adjustments. Click <b>Finish</b> to apply 
-    the changes.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-92.htm">Creating a CVS repository location</a><br>
-<a href="tasks-96.htm">Checking out a project from the CVS repository</a><br>
-<a href="tasks-103.htm">Replacing resources in the Workbench</a><br>
-<a href="tasks-100a.htm">Branching</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-113.htm">Updating</a><br>
-<a href="tasks-113b.htm">Resolving conflicts</a><br>
-<a href="tasks-100b.htm">Merging from a branch</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-47.htm">CVS</a><br>
-<a href="../reference/ref-20-fileContent.htm">File Content</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-16.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-16.htm
deleted file mode 100644
index e830f69..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-16.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Filtering in the CVS Resource History View</title>
-<meta name="keyword" content="team">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Filtering in the CVS Resource History View</H1>
-<P CLASS="Para">Over time, the revision history for a file can grow drastically. 
-  As a result, it may be difficult to find the revision or revisions that you 
-  are looking for. Using the filtering mechanism of the CVS Resource History view 
-  can help.</P>
-<P CLASS="Para">To set a filter on the CVS Resource History view:</P>
-<ol>
-  <li>Select the <b>Filter History</b> action from the local toolbar of the CVS 
-    Resource History view.</li>
-  <li>Enter any author, comment, or date range that you would like the view to display.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-<p>The view will now display only those revisions that match the criteria you 
-  entered.</p>
-<p><b>Tip:</b> You can remove a date range filter by selecting the first item 
-  (&quot;---&quot;) in the date and month fields.</p>
-<p><b>Tip:</b> You can choose whether the filter should match any or all of the 
-  criteria by selecting the appropriate radio button in the dialog.</p>
-  
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br><a href="../concepts/concepts-26.htm">Team programming with CVS</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="../reference/ref-47.htm">CVS</a>
-<br><a href="../reference/ref-32a.htm">CVS Resource History view</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-annotate.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-annotate.htm
deleted file mode 100644
index 09e6961..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-annotate.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Finding out who to blame with the Annotate command</title>
-  <meta content="team" name="keyword">
-</head>
-<body style="background-color: rgb(255, 255, 255);">
-<h1 class="Head">Finding out who to blame with the Annotate command</h1>
-<p>Let's say you have found a bug on line 65 of a file and you don't understand 
-  the code. Who do you ask, or blame, for the change? Well you could start by 
-  looking at the resource history for the file, but that won't tell you who changed 
-  that particular line. This is why the <span
- style="font-weight: bold;">Annotate</span> command is useful. You can pick any 
-  ASCII file (see note on binary files) and get a listing of who changed what 
-  line. </p>
-<p>The <span style="font-weight: bold;">Show Annotation</span> action
-is
-available form the following places: History View, Repository Explorer,
-Synchronize View, and the Resource and Packages View. When the annotate
-is run you will be able to:</p>
-<ul>
-  <li>
-    <p>Step through changes in the Annotate View and the text editor
-will highlight the associated lines associated with the selected change.</p>
-  </li>
-  <li>
-    <p>You can select a line in the text file and the Annotate View
-will
-select the change that is associated with that line.</p>
-  </li>
-  <li>
-    <p>The History View will show the history for the opened file and
-highlight the revision of the currently selected change. This allow you
-to quickly see the commit comment for a particular change. </p>
-  </li>
-</ul>
-<h2>Only works with text files</h2>
-<p>The annotate command will only work with files that are marked as ASCII in 
-  the CVS repository. Also, the command will open a text file to show the changes 
-  even if the associated editor in the workbench is a non-text editor. For example, 
-  if you run annotate on a plugin.xml file a simple text editor will be opened 
-  instead of the full PDE editor.</p>
-<p><img  alt="Related concepts"
- src="../images/ngrelc.png" border="0"> <br>
-<a href="../concepts/concepts-cvs-watch.htm">Watch/Edit</a><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a> </p>
-<p><img  alt="Related reference"
- src="../images/ngrelr.png" border="0"> <br>
-<a href="../reference/ref-47.htm">CVS</a> </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-passwords.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-passwords.htm
deleted file mode 100644
index 54251f4..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-passwords.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>Password Management</title>
-  <meta name="keyword" content="team">
-  <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-<body style="background-color: rgb(255, 255, 255);">
-<h1 class="Head">Password Management</h1>
-<p>When creating a repository location, an option is provided at the bottom of 
-  the wizard to save the password between sessions. <br>
-</p>
-<p style="text-align: left; margin-left: 40px;"><img src="../images/Image83_cvs_savedpasswords.png">
-<br>
-</p>
-<p>In previous releases, passwords were automatically saved between sessions whereas 
-  now the user has full control over this behavior. There is a caveat to this 
-  though - the password file Eclipse uses to save the password between sessions 
-  is not very secure. It is difficult, but not impossible, for an intruder to 
-  read the file and find your passwords. </p>
-<p>We recommend that, if you have strict security requirements, you <span
- style="font-weight: bold; font-style: italic;">don't</span> save passwords using 
-  this mechanism. Instead, use <a
- href="tasks-cvs-ssh2.htm">keypair authentication</a> provided by the <em>extssh</em> 
-  connection method.</p>
-<p>You can manage the list of passwords that have been cached via the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.PasswordManagementPreferencePage)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<span style="font-weight: bold;">Team &gt; CVS &gt; Password Management</span></a>
- preference page. The page displays the currently saved passwords and allows you to delete 
-  them.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"
- ><br>
-<a href="tasks-92.htm">Creating a CVS repository location</a><br>
-<a href="tasks-cvs-ssh2.htm">Connecting and configuring CVS with SSH</a><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a> </p>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- > <br>
-<a href="../reference/ref-47.htm">CVS</a> </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-project-set.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-project-set.htm
deleted file mode 100644
index d5e3a39..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-project-set.htm
+++ /dev/null

@@ -1,73 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Sharing your workspace setup using Project Sets</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Sharing your workspace setup using Project Sets</H1>
-<P CLASS="Para">Your workspace setup may consist of several projects from one 
-  or more repositories. Once you have setup your workspace, you can share it with 
-  others by exporting a Team Project Set. A project set is a text file that contains 
-  a pointer to each of the projects contained in the project set.When a project 
-  set is imported, these pointers are used to fetch the projects from the repository. 
-  Project sets can include any projects that are mapped to repository tooling 
-  that provides support for them, such as CVS. To export a project set:</P>
-<ol>
-  <li>Setup your workspace with all the projects you want to work on by checking 
-    them out of CVS or obtaining them in any manner appropriate for the repository 
-    tooling you are using.</li>
-  <li>From the <strong>File</strong> menu, choose <strong>Export</strong>. The
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export")'>
-    <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-    Export dialog</a> will open.</li>
-  <li>In the Export dialog, choose <b>Team &gt; Team Project Set</b> and click <strong>Next</strong>. 
-    The dialog will now display all the projects that are eligible for export.</li>
-  <li>Check the projects you wish to include in the project set. Either browse 
-    for or type in the name of the file where you wish to save the project set 
-    and then click <strong>Finish</strong>.</li>
-</ol>
-<P CLASS="Para">Now you have created a project set file. You can now share this 
-  file with others or use it yourself to recreate your workspace. To Import a 
-  project set:</P>
-<ol>
-  <li>From the <strong>File</strong> menu, choose <strong>Import</strong>. This 
-    will open the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import")'>
-    <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-    Import dialog</a>.</li>
-  <li>In the Import dialog, choose <b>Team &gt; Team Project Set</b> and click <strong>Next</strong>.</li>
-  <li>Browse for or type in the name of the file containing the project set and 
-    click Finish.</li>
-  <li>The projects contained in the project set will be fetched from the repository.</li>
-</ol>
-<P CLASS="Para">For CVS, you will be prompted to provide the authentication information 
-  (user name and password) for the repository as it is not included in the project 
-  set. </P>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-96.htm">Checking out a project from a CVS repository</a><br>
-<a href="tasks-96a.htm">Checking out a module from a CVS repository</a><br>
-  <a href="tasks-92.htm">Creating a CVS repository location</a><br>
-  <a href="tasks-117.htm">Sharing a new project using CVS</a></p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br>
-  <a href="../reference/ref-47.htm">CVS</a><br>
-  <a href="../reference/ref-32.htm">CVS Repositories view</a><br>
-  <a href="../reference/ref-40a.htm">CVS Checkout wizard</a></p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-quickdiff.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-quickdiff.htm
deleted file mode 100644
index e9d5be2..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-quickdiff.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>Quick Diff: showing changes in a text editor</title>
-  <meta name="keyword" content="team">
-  <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body style="background-color: rgb(255, 255, 255);">
-<h1 class="Head">Quick Diff: Showing changes in a text editor</h1>
-<p>Instead of using a compare editor, which will show changes between 2
-or
-3 files by showing each file side-by-side, you can enable quick diff
-support and see the changes within the text editor (e.g. any text
-editor based on the Eclipse text editor). This feature can be enabled
-via the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.editors.preferencePages.QuickDiff)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<span style="font-weight: bold;">General &gt; Editors &gt; Text Editors &gt; Quick Diff</span></a>
-preference page. You should select the
-<span style="font-weight: bold;">Latest CVS Revision</span> as the reference
-source. This will annotate the text file with diffs against the
-latest revision in CVS. Here are the following scenarios that are
-useful:</p>
-<ol>
-  <li>
-    <p><span>Open a file and make changes to it. You will see the
-difference <span>annotations marking the changes. Then if you run <span
- style="font-weight: bold;">Team &gt; Replace with latest</span>. The
-annotations are removed and the file is clean. </span></span></p>
-  </li>
-  <li>
-    <p><span>Open a file and make changes to it. You will see the
-difference <span>annotations marking the changes. Then if you run <span
- style="font-weight: bold;">Team &gt; Commit</span> the annotations are
-removed and the file is clean.</span></span></p>
-  </li>
-  <li>
-    <p><span><span>If you synchronize the file with the server and a new revision 
-      is found on the server, the editor will update showing the incoming changes.</span></span></p>
-  </li>
-</ol>
-<p>If you enable showing the differences in the overview ruler, you can, at a 
-  glance, get an idea of how many changes you have made to a file since your last 
-  commit. The differencing happens in a background thread to minimize the impact 
-  on actual editing of the file.</p>
-<p><span style="font-weight: bold;">Note:</span> this feature requires an active 
-  connection to your CVS server so that remote contents can be fetched when an 
-  editor is opened.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"
- > <br>
-<a href="../concepts/concepts-cvs-watch.htm">Watch/Edit</a><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a> </p>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- > <br>
-<a href="../reference/ref-47.htm">CVS</a> </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-ssh2.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-ssh2.htm
deleted file mode 100644
index 8340d14..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-ssh2.htm
+++ /dev/null

@@ -1,106 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Connecting and configuring CVS with SSH</title>
-  <meta content="team" name="keyword">
-  <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-<body style="background-color: rgb(255, 255, 255);">
-<h1 class="Head">Connecting and configuring CVS with SSH</h1>
-<p>Eclipse includes an SSH client for accessing a remote CVS server.
-The
-client supports both the SSH1 and SSH2 protocol versions. To use SSH2
-with a CVS repository select the <span style="font-weight: bold;">extssh</span>
-connection type. </p>
-<p>Different methods can be used to authenticate, 
-  depending on the level of functionality and security you want. User authentication 
-  methods used by the client by default are, in the following order: public-key, 
-  Keyboard-Interactive, and password authentication.</p>
-<h2>Authentication with Public Keys (keypair)</h2>
-<p> Public-key authentication allows you to connect to a remote CVS server without 
-  sending your password over the wire. This is a more secure authentication method 
-  than password authentication. Public-key authentication uses two keys, a private 
-  key that only you have--it should be kept in a secure place and protected with 
-  a password. And the public key, which is placed on the server you wish to gain 
-  access to.</p>
-<p>
-  Eclipse supports generating both keys and you can copy the public key to the 
-  server from within Eclipse. In order to use public key authentication follow 
-  these steps:</p>
-<ol>
-  <li>
-    <p>If you already have a private/public key for the CVS server, simply open the
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ssh2.CVSSSH2Preferences)")'>
-      <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-      <span style="font-weight: bold;">Team &gt; CVS &gt;&nbsp; SSH2 Connection Method</span></a>
-       preference page and on the <span
- style="font-weight: bold;">General </span>tab add your private key to the list 
-      by selecting the <span style="font-weight: bold;">Add Private Key</span> 
-      button. Your key will be used when authenticating.</p>
-  </li>
-  <li>
-    <p>If you don't have a keypair yet, in the preferences page, go to the <span style="font-weight: bold;">Key 
-      Management</span> page.</p>
-  </li>
-  <li>
-    <p>Select either a <span style="font-weight: bold;">Generate RSA key</span> 
-      (if your server supports version 1 of the protocol) or <span
- style="font-weight: bold;">Generate DSA key</span> (for version 2).</p>
-  </li>
-  <li>
-    <p>A public key and private key will be generated. The public key
-will be shown in the read-only text area. </p>
-  </li>
-  <li>
-    <p>The next step is to copy the public key to your server. If your
-server is running an OpenSSH server than you can use the <span
- style="font-weight: bold;">Export via sftp</span> action. Otherwise
-you will have to copy and paste the public key into your remote
-~/.ssh/authorized_keys file.</p>
-  </li>
-  <li>
-    <p>Now you have to provide a password for your private key, and
-save
-it on your computer.</p>
-  </li>
-</ol>
-<p>So now that you have your keypairs generated and installed, the next
-time you create a CVS location to the server you shouldn't enter a
-password. When the connection is initialized, you will be prompted for
-the passphrase for your private key. This is the most secure method of
-authentication, as long as your private key is protected with a
-passphrase.</p>
-<p>
-<span style="font-weight: bold;">Note</span>: exporting the public key
-is only supported on OpenSSH enabled SSH servers.</p>
-<h2>Authentication with Passwords</h2>
-<p>
-If your server is configured to support password authentication, then
-you can simply enter your password when you create a CVS repository
-location and that password will be used when authenticating with the
-server. This is the simplest authentication method, but isn't as secure
-as public keys.<br>
-<br>
-  <span style="font-weight: bold;">Note</span>: It is not recommended that you 
-  save your login passwords using Eclipse. The file that contains the file is 
-  not sufficiently protected against intruders and as such you can comprise the 
-  security of your system. If your company requires strict security practices 
-  then your should use keypair authentication.</p>
-<p><img  alt="Related concepts"
- src="../images/ngrelc.png" border="0"><br>
-<a href="tasks-92.htm">Creating a CVS repository location</a><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a> </p>
-<p><img  alt="Related reference"
- src="../images/ngrelr.png" border="0"> <br>
-<a href="../reference/ref-47.htm">CVS</a> </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-watch.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-watch.htm
deleted file mode 100644
index d4be3d3..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-watch.htm
+++ /dev/null

@@ -1,110 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Finding out who's working on what: watch/edit</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Finding out who's working on what: watch/edit</H1>
-<P CLASS="Para">CVS provides a notification scheme which allows you to know if 
-  someone is modifying a file that you care about. This facility is known as <em>watches</em>. 
-  By setting a <em>watch</em> on a file, you can have CVS notify you via email 
-  (or other) if someone else starts to <em>edit</em> this file. </P>
-<p class="Para">There are two parts to CVS watches: <em>watch</em>, and <em>edit</em>. 
-  The first, <em>watch</em>, is how you specify which files you wish to be notified 
-  about. The second, <em>edit</em>, is how you inform the CVS server (and thus 
-  others) that you are about to modify a file.</p>
-<p class="Para"><em>Edit</em> is useful on its own without ever setting up any 
-  watches and lots of people work this way. This is because when you edit a file, 
-  you will be told immediately if someone else is already editing that file. Since 
-  most people just want to know up front that they may have to merge their changes 
-  on commit, <em>edit</em> on its own is sufficient for most. Another advantage 
-  to using just <em>edit</em> is that it doesn't require any administrative changes 
-  to the server, where as <em>watch</em> does. All that <em>watches</em> gives 
-  above this is the email notification that some file you are watching is being 
-  modified.</p>
-<p class="Para">For these reasons, <em>edit</em> is supported natively by Team 
-  CVS where as <em>watch</em> isn't.</p>
-<h2 class="Para">Setting up Watches</h2>
-<p class="Para">As mentioned, you can't set watches in Team CVS. If you are interested 
-  in doing this, you should consult your cvs documentation. In brief though, this 
-  is what's involved:</p>
-<ol>
-  <li>First, you or your CVS administrator will need to modify the CVSROOT/notify 
-    file. Consult the CVS documentation on watches for details on how to configure 
-    this file. </li>
-  <li>Next, you will need to perform a command line &quot;cvs watch add &lt;filename&gt;&quot; 
-    for each file that you wish to watch. If &lt;filename&gt; is a directory name, 
-    then all files within that directory will be watched.</li>
-</ol>
-<h2>Setting up a Project for Watch/Edit</h2>
-<p>Watches and editing are optional in CVS. To use this facility, you must turn 
-  on this option in the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.WatchEditPreferencePage)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <strong>Team &gt; CVS &gt; Watch/Edit</strong></a>
-  preference page. Select &quot;Configure projects to use Watch/Edit on checkout&quot;, accept 
-  the preference dialog, and then checkout your project. All the files in the 
-  project will be checked out read-only. This tells the CVS client which files 
-  are being edited by you and which aren't (writable files are being edited). 
-  If you've already checked out the project before you turned on this option, 
-  you can either check it out again or enable the &quot;Use Watch/Edit for this 
-  project&quot; option on the project's CVS properties page. Either of these operations 
-  will make the files in the project read-only.</p>
-<h2>Editing</h2>
-<p class="Para"></p>
-<p>Although typical CVS clients require you to perform an explicit edit, Team 
-  CVS automatically issues an edit as soon as you start to modify a file. This 
-  support is built deep into Eclipse, so typing in a text editor, performing Java 
-  refactoring, etc., will all issue a CVS edit for you. You can also perform an 
-  explicit edit via the <strong>Team &gt; Edit</strong> context menu on a resource.</p>
-<p>When an <em>edit</em> is issued, you will be informed immediately if someone 
-  is already editing that file. In addition, everyone who is <em>watching</em> 
-  that file will be notified by the CVS server via email etc. Since watches simply 
-  give you email notification, <em>edit</em> without ever setting up watch lists 
-  is still a useful (and popular) workflow.</p>
-<p>If you prefer, you can turn off automatic issuing of edits. This means you 
-  will need to manually perform a Team &gt; Edit for each file you are working 
-  on. To use this work mode, open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.WatchEditPreferencePage)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <strong>Team &gt; CVS &gt; Watch/Edit</strong></a>
-  preference page
-  and enable &quot;Edit the file without informing the server&quot;. </p>
-<p>Finally, you can see the list of editors of a file at any time by selecting 
-  <strong>Team &gt; Show Editors</strong> from the context menu of that file. 
-</p>
-<h2>Unediting</h2>
-<p>Just as you can tell CVS that you are editing a file, there also needs to be 
-  a way of telling CVS that you are no longer editing that file. This is referred 
-  to as <em>unedit</em>. This way, if someone checks the editors list for a file, 
-  they'll know if someone is still working on that file. This happens in one of 
-  two ways:</p>
-<ul>
-  <li>When you commit an edited file, an unedit is automatically issued.</li>
-  <li>If you discover that you want to back out of the changes to a file, you 
-    can explicit unedit the file. In addition to notifying the server, an explicit 
-    unedit will revert the file to its base (i.e. the workspace will then contain 
-    the copy of the file before you started modifying it).</li>
-</ul>
-<p>&nbsp;</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" > 
-  <br>
-  <a href="../concepts/concepts-cvs-watch.htm">Watch/Edit</a></p>
-<p><a href="../concepts/concepts-26.htm">Team programming with CVS</a> </p>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" > 
-  <br>
-  <a href="../reference/ref-47.htm">CVS</a> </p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-exttools-running.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-exttools-running.htm
deleted file mode 100644
index 60f20a2..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-exttools-running.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Running external tools</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Running external tools</H1>
-
-<p>The Workbench provides a mechanism for running tools that are not part of it.
-To configure an external tool:
-</p>
-
-<ol>
-  <li>Click <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.externalTools.commands.OpenExternalToolsConfigurations")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Run &gt; External Tools &gt; External Tools...</b></a>.
-  </li>
-  <li>Select the Program configuration</li>
-  <li>Click the <b>New</b> button.</li>
-  <li>Enter a name for your external tool (for example, My External Tool).</li>
-  <li>Click the <b>Browse File System</b> button.</li>
-  <li>Find the tool you want to run (for example, on Windows it is usually a file 
-    with the extension .exe or .bat).</li>
-  <li>(Optional) In the <b>Arguments</b> field enter the necessary arguments 
-    for the tool.</li>
-  <li>(Optional)In the <b>Working directory</b> field enter the working directory 
-    for the tool.</li>
-  <li>Click <b>Run</b>.</li>
-</ol>
-
-<p>These steps create a persisted launch configuration. The newly created configuration will
-appear in the launch history under <b>Run &gt; External Tools</b> and will be available in the
-launch configuration dialog which is opened by clicking
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.externalTools.commands.OpenExternalToolsConfigurations")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>Run &gt; External Tools &gt; External Tools...</b></a>.
-</p>
-
-<p>It is also possible to set up and run an external tool to build a project.
-</p>
-
-<ol>
-  <li>Select the desired project.</li>
-  <li>From its pop-up menu choose <b>Properties</b>.</li>
-  <li>Click <b>Builders</b> from the list, and configure the tool as described above.</li>
-</ol>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-exttools.htm">External tools</a><br>
-</P>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="./tasks-ant-running.htm">Running Ant buildfiles</a><br>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-importproject.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-importproject.htm
deleted file mode 100644
index 30c30d7..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-importproject.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Importing existing projects</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Importing existing projects</h1>
-
-<p>You can use the Import Wizard to 
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import(importWizardId=org.eclipse.ui.wizards.import.ExternalProject)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-import an existing project into workspace</a>.
-</p>
-
-<ol>
-  <li>From the main menu bar, select
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>File &gt; Import...</b></a>. The Import wizard opens.</li>
-  <li>Select <b>General &gt; Existing Project into Workspace</b> and click <b>Next</b>.</li>
-  <li> Choose either <strong>Select root directory </strong>or <strong>Select 
-    archive file</strong> and click the associated <b>Browse</b> to locate the 
-    directory or file containing the projects.</li>
-  <li>Under <strong>Projects</strong> select the project or projects which you 
-    would like to import.</li>
-  <li>Click <b>Finish</b> to start the import.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"><br>
-<a href="../reference/ref-70.htm">Import wizard</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" width="159" height="27"><br>
-<a href="tasks-55.htm">Importing resources from the file system</a><br>
-<a href="tasks-55bg.htm">Importing resources from a ZIP File</a><br>
-<a href="tasks-57.htm">Exporting</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-team-1.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-team-1.htm
deleted file mode 100644
index b83dea2..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-team-1.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Setting the content type of a file extension</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Setting the content type of a file extension</H1>
-<P CLASS="Para">CVS repositories distinguish between files that contain ASCII 
-  data and those that do not. For ASCII files, additional helpful functionality 
-  is available to the user. This includes:</P>
-<ul>
-  <li>Proper end of line conversion between the client and the server. This ensures 
-    that a Windows user and a UNIX user can work on the same file without introducing 
-    incompatibilities.</li>
-  <li>Auto merging of conflicts. If a file contains both incoming and outgoing 
-    changes but none on the same line as another, then the file may be automatically 
-    merged when updating.</li>
-</ul>
-<p class="Para">Certain file types invariably contain either ASCII data or binary 
-  data. For example, *.txt files usually contain ASCII data, and *.exe files usually 
-  contain binary data. Eclipse comes with a pre-defined set of file types, which 
-  you may add to or modify.</p>
-<P CLASS="Para">To set the content type associated with a file extension: </P>
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.ui.TextPreferences)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>Team &gt; File Content</b></a> preference page. 
-    This page displays a list of file extensions and content type (ASCII or Binary) 
-    for file extensions whose content type is known.</li>
-  <li> 
-    <p CLASS="Para">To add a file extension, click the <b>Add Extension</b> button and enter 
-      the file extension in the text prompt that appears. Once <b>OK</b> is clicked, 
-      the extension will be added to the list with a content type of ASCII.</p>
-  </li>
-  <li>To change the content type for an existing file extension, select the file 
-    extension entry and click the <b>Change</b> button. This will toggle the type 
-    from ASCII to Binary or vice versa.</li>
-  <li>To remove a file extension, select the file extension entry and click the 
-    <b>Remove</b> button.<br>
-  </li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br><a href="../concepts/concepts-26.htm">Team programming with CVS</a>
-</p>
-
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="../reference/ref-47.htm">CVS</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tchgbrws.htm b/bundles/org.eclipse.platform.doc.user/tasks/tchgbrws.htm
deleted file mode 100644
index cb9651e..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tchgbrws.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Changing how help information is displayed</title>
-</head>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Changing how help information is displayed</h1>
-
-<h2>Help browser</h2>
-<p>The help system can be accessed in help view, or separate help window. The
-  help window may have a form of a simple window with an embedded browser, or
-  be one of the web browser available on your system.</p>
-<p>If embedded web browser is supported on your system, help uses an embedded
-  help browser to display help, whenever possible. When a
-  modal window is showing on the screen, that would prevent interacting with
-  the embedded browser, requesting help opens an external browser. If embedded
-  browser is used on your system and you prefer to always use external browser,
-you may select this behavior in help preferences.</p>
-<h2>Context help</h2>
-<p>By default, context-sensitive help for workbench elements is displayed in
-  the help view. Context-sensitive help for dialogs is displayed adjacent to
-  the dialog,
-  in a window similar to the help view. If you prefer to display context help
-  in infopops when working in the workbench, in dialogs or both, change the selection
-  in the help preference page.</p>
-<h2>Displaying topics</h2>
-<p>A topic selected in the help view can be displayed in place, in the help view,
-  or in the editor area. You may indicate suitable way in the help preferences.
-  On some platforms, with no embedded browser, the topics will always be displayed
-  in an external browser.</p>
-<p>
-<img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="../reference/ref-18.htm">Help preference page</a>
-</p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tf1help.htm b/bundles/org.eclipse.platform.doc.user/tasks/tf1help.htm
deleted file mode 100644
index 7b0471a..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tf1help.htm
+++ /dev/null

@@ -1,89 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Accessing context-sensitive help</title>
-</head>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Accessing context-sensitive help</h1>
-
-<p>To access the context-sensitive help for a given widget:</p>
-
-<ol>
-  <li>Select the widget by putting focus on it (see the table below).</li>
-  <li>Press <code>F1</code> key. On GTK windowing system use <code>Ctrl+F1</code>, and on
-    Carbon windowing system use <code>Help</code> key instead of <code>F1</code>.</li>
-</ol>
-
-<p>This displays a description of the selected widget, 
-and usually, a list of links to related information, in the help view. If you
-  want more information than what is shown in the description, click a link to
-one of the related topic, or one of the search results appearing in the dynamic
-  help section in the help view.</p>
-<p>Depending
-    on help preference settings, requesting context-sensitive help may display
-  context help in an <em>infopop</em> instead of help view. You can dismiss
-  the 
-infopop by clicking outside it, or by pressing <b>Esc</b>. If you want more information
-than what is shown in the infopop, click a link to the related information. This
-opens the Help browser to the selected topic and
-closes the infopop. The list of related links stays in the left hand frame, 
-so you do not have to press <code>F1</code> again if you are interested in other
-topics related 
-to the same widget.</p>
-<p>To access context sensitive help for a widget, you must put focus on it and 
-then press <code>F1</code>. The following table shows how to put focus on some of the different 
-kinds of widgets.
-</p>
-
-<table border="1" width="500" cellspacing="0" cellpadding="5" summary="Widget selection table">
-  <tr>
-    <th>Widget type</th>
-    <th>How to select it</th>
-  </tr>
-  <tr>
-    <td>Menu item (for example <strong>Save</strong> in the <strong>File</strong> menu)</td>
-    <td>Let your mouse pointer rest over it so that it is highlighted, but don't click on it.</td>
-  </tr>
-  <tr>
-    <td>Field</td>
-    <td>Put the cursor in the field.</td>
-  </tr>
-  <tr>
-    <td>Button (for example <b>Cancel</b> button on a Dialog)</td>
-    <td>Tab until the button is in focus.</td>
-  </tr>
-  <tr>
-    <td>List</td>
-    <td>Click an item in the list.</td>
-  </tr>
-  <tr>
-    <td>View or pane</td>
-    <td>Click the title bar of the View or pane.</td>
-  </tr>
-  <tr>
-    <td>checkbox</td>
-    <td>Click the checkbox (which changes its state) or use the Tab key
-      to bring it into focus.</td>
-  </tr>
-</table>
-
-<p><em>Note:</em> Context-sensitive help via <code>F1</code> is unavailable from toolbar
-buttons. Instead, let your mouse pointer hover over a toolbar button to view tooltip help
-for buttons.
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" WIDTH="159" HEIGHT="27"><br>
-<a href="taccess.htm">Accessing and navigating online help</a>
-</p>
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tfonts.xhtml b/bundles/org.eclipse.platform.doc.user/tasks/tfonts.xhtml
deleted file mode 100644
index 0fcbdaf..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tfonts.xhtml
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." />
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css" />
-<title>Setting help fonts and colors for accessibility</title>
-</head>
-
-<body bgcolor="#ffffff">
-<h1>Setting help fonts and colors for accessibility</h1>
-
-<p>The help browser uses your operating system's settings for the font colors,
-styles, and sizes. Users with visual impairments may wish to
-change some of these settings to increase the readability of the documentation.
-</p>
-
-<p> <img src="../images/win_only.png" alt="The following information applies to Windows." border="0" /> 
-In addition, on Windows platforms using Microsoft Internet Explorer, the help 
-browser uses a component of Internet Explorer to display documentation, so changes 
-you make to its display settings also affect the help display. To change the 
-help browser's font and color settings:
-</p>
-
-<ol>
-  <li>Open Microsoft Internet Explorer.</li>
-  <li>Select <b>Tools &gt; Internet Options</b>.</li>
-  <li>On the <b>General</b> page, click the <b>Colors</b>, <b>Fonts</b>, or <b>Accessibility</b> button.</li>
-  <li>Set the formatting options you desire.</li>
-  <li>Optionally, you can specify a cascading style sheet (CSS) to apply to the content.</li>
-  <li>Click <b>OK</b> and exit Internet Explorer.</li>
-  <li>Restart the Workbench. Open the Help perspective and browse the documentation to see the changes.</li>
-</ol>
-
-<p><b>Note:</b> The help system also uses the Icon font setting on the Display Properties <b>Appearance</b> tab.</p>
-
-<p>For more information about creating a CSS, consult a CSS reference. The W3 
-Consortium (www.w3.org) has an extensive collection of information about CSS 
-and links to valuable resources.
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" width="159" height="27" /><br />
-<a href="taccess.htm">Accessing and navigating online help</a>
-</p>
-
-
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/timpandexp.htm b/bundles/org.eclipse.platform.doc.user/tasks/timpandexp.htm
deleted file mode 100644
index 8ebabb1..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/timpandexp.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Importing and Exporting Preferences</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h2>Importing and Exporting Preferences</h2>
-<p CLASS="Para">Preference files can be both imported to and exported from the 
-  Workbench allowing you to easily share individual or group preferences. </p>
-<p CLASS="Para">The Import wizard can be used to import preferences from the local 
-  file system to the Workbench.</p>
-<p CLASS="Para">To import a preference file:</p>
-<ol>
-  <li>Select 
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <strong>File &gt; Import</strong></a>.</li>
-  <li>In the Import wizard select <strong>General &gt; Preferences</strong> and click <strong>Next</strong>.</li>
-  <li>Click <strong>Browse...</strong> and locate the Preferences file on the 
-    local file system.</li>
-  <li>Select one of the following: 
-    <ul>
-      <li><strong>Import all</strong> to accept all of the preferences defined 
-        in the file.</li>
-      <li><strong>Choose specific preferences to import</strong> to select only 
-        specified preferences defined in the file.</li>
-    </ul>
-  </li>
-  <li>Click <strong>Finish</strong>.</li>
-</ol>
-<p CLASS="Para">&nbsp;</p>
-<p CLASS="Para">The Export wizard can be used to export preferences from the Workbench 
-  to the local file system.</p>
-<p CLASS="Para">To export a preference file:</p>
-<ol>
-  <li>Select
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <strong>File &gt; Export</strong></a>.</li>
-  <li>In the Export wizard select <strong>General &gt; Preferences</strong> and click <strong>Next</strong>.</li>
-  <li>Select one of the following: 
-    <ul>
-      <li><strong>Export all</strong> to add all of the preferences to the file.</li>
-      <li><strong>Choose specific preferences to export</strong> to add only specified 
-        preferences to the file.</li>
-    </ul>
-  </li>
-  <li>Click <strong>Browse...</strong> and locate the preferences file on the 
-    local file system.</li>
-  <li>Click <strong>Finish</strong></li>
-</ol>
-<p><strong>Note:</strong> If no changes have been made to the original preference 
-  settings the preferences file will be empty.</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tkeybindings.htm b/bundles/org.eclipse.platform.doc.user/tasks/tkeybindings.htm
deleted file mode 100644
index ed626b0..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tkeybindings.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Changing the key bindings</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Changing the key bindings</H1>
-<p>
-The function of the keyboard can be extensively customized in Eclipse.
-</p>
-<p>
-Use the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Keys)")'>
-<img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-<b>General &gt; Keys</b></a> preference page to 
-<a href="../concepts/accessibility/keyboardshortcuts.htm">assign key sequences</a> to many of the commands in Eclipse. </p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/accessibility/keyboardshortcuts.htm">Keys</a><br>
-<a href="../concepts/accessibility/navigation.htm">Navigating the user interface by using the keyboard</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/topenmode.htm b/bundles/org.eclipse.platform.doc.user/tasks/topenmode.htm
deleted file mode 100644
index 11fa94c..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/topenmode.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Controlling single and double click behavior</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Controlling single and double click behavior</H1>
-
-<p>You can control how the Workbench responds to single and double clicks. To do this:
-</p>
-
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workbench)")'>
-  <img src="PLUGINS_ROOT/PRODUCT_PLUGIN/command_link.png"/>
-  <b>General</b></a> preference page.</li>
-  <li>Select the behavior you want to change from the <b>Open mode</b> group.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p>The effect of these selections varies by view. For example, in one of the navigation 
-  views: </p>
-
-<dl>
-<dt>Double click</dt>
-<dd>Will cause a single click on a resource to select it, and a 
-double click to open it in an editor.</dd>
-<dt>Single click</dt>
-<dd>Will cause a single click on a resource to both select it and
-immediately open an editor on it.</dd>
-</dl>
-
-<p>The checkboxes under the <b>Single click</b> radio button further refine
-the single click behavior. Checking <b>Select on hover</b> will cause the resource
-to be selected if you hover over it with the mouse. Checking <b>Open when using
-arrow keys</b> will cause the resource to be opened if you use the arrow keys to
-navigate to it.
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-10.htm">Workbench</a><br>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tquickfix.htm b/bundles/org.eclipse.platform.doc.user/tasks/tquickfix.htm
deleted file mode 100644
index 078c329..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tquickfix.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Automatically fixing problems</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Automatically fixing problems</H1>
-
-<P>Problems displayed in the Problems view may offer a <b>Quick Fix</b> menu option 
-  in the context menu. Selecting this menu option will present one or more possible 
-  fixes that can be automatically applied for you. </P>
-
-<P>Certain Java problems may be resolved using the Quick Fix feature. For example, 
-  a missing import statement in a Java file will result in a Quick Fix suggestion 
-  to add the import statement or change the type name to a name that is already 
-  imported. </P>
-
-<ol>
-  <li>In the Problems view, right-click the task you want to Quick Fix.</li>
-  <li>Select <b>Quick Fix</b> from the pop-up menu.</li>
-  <li>Choose from one of the suggested fixes.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-11.htm">Markers</a><br>
-<a href="../concepts/ctskview.htm">Tasks view</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-31.htm">Tasks view</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tsearch.htm b/bundles/org.eclipse.platform.doc.user/tasks/tsearch.htm
deleted file mode 100644
index 324fe21..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tsearch.htm
+++ /dev/null

@@ -1,169 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Searching online help</title>
-</head>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Searching online help</h1>
-
-<p>The help system includes a powerful text search engine that runs simple 
-or complex queries on the documentation to help you find the information you
-are looking for.
-</p>
-
-<p>To search the online help:
-</p>
-
-<ol>
-  <li>Select <strong>Help &gt; Search</strong>. type the term or terms for which
-    you want to search.
-  </li>
-  <li>Click <b>Go</b> or press Enter. The result set will be shown below.</li>
-  <li>To view the content of a topic in the result set, select it. Hits within 
-  the selected topic are highlighted.</li>
-</ol>
-
-<p><em>Tip:</em> You can also search local documentation from inside help browser
-  by typing the term in the search field of the toolbar. The results will be
-  shown in the Search view.
-Click a result to open the topic in the contents area.</p>
-
-<h2>Refining the search results in the help view</h2>
-
-<p>If the result set is very large, the information you are looking for might
-  not appear in the top 10 or 15 results. You can then refine the search to reduce
-  the number of results. </p>
-<p>To refine a search: </p>
-<ol>
-  <li>Click the <b>Search Scope </b> link. to expand search scope section.</li>
-  <li>Click
-      the <b>Advanced Settings</b> link. Search Scope preference dialog
-      opens.</li>
-  <li>Click <b>Local Help</b> from the list.</li>
-  <li>Select <b>Search only the following topics</b> button to narrow down the
-    search scope.</li>
-  <li>In the working set content tree, <b>select</b> the topics to which you
-    want to narrow the search.</li>
-  <li>Click <b>OK</b>, to activate the changes and return to search page in the
-    help view.</li>
-  <li>Click <b>Go</b> again. The results will be shown in the Search Results
-    view in the Help browser.</li>
-</ol>
-<h2>Extending the search scope</h2>
-<p>If you cannot locate information in the local help, you can extend search
-  scope to remote info-center or search engines.</p>
-<p>To enable search engines: </p>
-<ol>
-  <li>Click the <b>Search Scope </b> link. to expand search scope section. The
-    list of search engine is displayed.</li>
-  <li> Select the ones that contain information you are looking for.</li>
-</ol>
-<p>In addition to search engines provided, you may define additional search engines.</p>
-<p>To define a new search engine: </p>
-<ol>
-  <li>Click the <b>Search Scope </b> link. to expand search scope section. </li>
-  <li>Click the <b>Advanced Settings</b> link. Search Scope preference dialog
-    opens.</li>
-  <li>Click <b>New</b>.</li>
-  <li>Select the search engine type.</li>
-  <li>Click <strong>OK</strong>.</li>
-  <li>Provide a name and a description</li>
-  <li>Select engine specific settings and scope below. For the remote search
-    engines, accessed using URL, fill in a full URL to query the engine. Use <code>{expression}</code> in
-    the place of search expression.</li>
-</ol>
-<h2>Defining multiple search scopes</h2>
-<p>By default, changing search scope modifies the search scope named &quot;default&quot;.
-  You can define multiple search scope. They will be saved, allowing to quickly
-  change search scope to one of them.</p>
-<p>To define a new search scope:</p>
-<ol>
-  <li>Click the current search scope name, beside the <b>Search Scope </b> link.
-    .Search Scope Sets dialog appears.</li>
-  <li>Click <strong>New</strong>.</li>
-  <li>Type a name, and confirm.</li>
-  <li>Select the newly created search scope.</li>
-  <li>Click <strong>OK</strong>. The new search scope becomes current.</li>
-</ol>
-<p>Changes to the search scope affect current search scope.</p>
-<h2>Local search query syntax</h2>
-<p>Remember the following search expression rules:
-</p>
-<ul>
-  <li>Unless otherwise stated, there is an implied AND between all search terms. 
-    In other words, topics that contain all the search terms will be returned. 
-    For example: 
-    <pre>Java project</pre>
-    <p>returns topics that contain the word <i>Java</i> and the word <i>project</i>, 
-      but does not return topics that contain only one of these words.</p></li>
-  <li>Use OR before optional terms . For example: 
-    <pre>applet OR application</pre>
-    <p>returns topics that contain the word <i>applet</i> or the word <i>application</i> 
-      (or both).</p></li>
-  <li>Use NOT before terms you want to exclude from search results. For example: 
-    <pre>servlet NOT ejb</pre>  
-    <p>returns topics that contain the word <i>servlet</i> and do not contain 
-      the word <i>ejb</i>. <b>Note:</b> NOT only works as a binary operator (that 
-      is, &quot;NOT servlet&quot; is not a valid expression).</p></li>
-  <li>Use ? for a single-character wildcard and * for a multi-character wildcard. 
-    For example: 
-    <pre>par?</pre>
-    <p>returns topics that contain <i>part</i> or <i>park</i>, but not <i> participate</i>. 
-      On the other hand:</p>
-    <pre>par*</pre>
-    <p>returns topics that contain <i>part</i>, <i>park</i>, <i>participate</i>,
-      <i>pardon</i>, and so on. <b>Note:</b> The search engine does not accept
-      terms with a wild card at first character position.</p></li>
-  <li>Use double quotation marks around terms you want treated as a phrase. For 
-    example: 
-    <pre>&quot;creating projects&quot;</pre>
-    <p>returns topics that contain the entire phrase <i>creating projects</i>, 
-      and not <i>creating</i> or <i>project</i> on its own.</p></li>
-  <li>Punctuation acts as term delimiters. For example:
-    <pre>plugin.xml</pre>
-    <p>returns hits on topics that contain <i>plugin.xml</i>, <i>plugin</i>, and 
-      <i>xml</i>, which is likely broader than you want. If you want to find just 
-      those topics containing <i>plugin.xml</i>, use double quotes, as in:</p>
-    <pre>&quot;plugin.xml&quot;</pre></li>
-  <li>The search engine ignores character case. For example: 
-    <pre>Workbench</pre>
-    <p>returns topics that contain 'workbench', 'Workbench', 'WorkBench', and 
-      'WORKBENCH'.</p></li>
-  <li>The following stop words are common English words which will be ignored 
-    (not searched for) if they appear in the search expression: a, and, are, as, 
-    at, be, but, by, in, into, is, it, no, not, of, on, or, s, such, t, that, 
-    the, their, then, there, these, they, to, was, will, with.</li>
-  <li>The search engine does &quot;fuzzy&quot; searches and word stemming. If 
-    you enter <i>create</i>, it will return hits on topics that contain <i>creates</i>, 
-    <i>creating</i>, <i>creator</i>, and so on.  To prevent search engine from stemming
-    terms, enclose them in double quotes.</li>
-</ul>
-	
-<h2>Search index generation</h2>
-<p>The first time you search the online help, the help system might initiate
-  an  index-generation process. This process builds the indexes for the search
-  engine 
-to use. It may take several minutes, depending on the amount of documentation
-  and whether prebuilt indexes are installed. Results of the search will be available
-  upon completion of the indexing process.</p>
-
-<p>Each time you add or modify the documentation set (for example, when you install 
-a new feature or update an existing one), the index will be updated to reflect 
-the new information set.
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="taccess.htm">Accessing and navigating online help</a>
-</p>
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/ttoolbars.htm b/bundles/org.eclipse.platform.doc.user/tasks/ttoolbars.htm
deleted file mode 100644
index 94b5853..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/ttoolbars.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Rearranging the main toolbar</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Rearranging the main toolbar</H1>
-<p>
-You can rearrange sections of the main toolbar. Toolbar sections are divided
-by a thin vertical line.
-</p>
-
-<ol>
-  <li> Make sure the toolbar is unlocked. The toolbar is unlocked if it has thick 
-    vertical bars next to the thin vertical toolbar dividers.<br>
-    <img src="../images/Image90_locked_toolbar.png" alt="Locked toolbar" border="0" > 
-    <img src="../images/Image90_unlocked_toolbar.png" alt="Unlocked toolbar" border="0" ><br>
-    If it is locked, unlock the toolbar by right clicking the toolbar and selecting 
-    the <b>Lock the Toolbars</b> menu item. </li>
-  <li> Grab the section of the toolbar you want to rearrange by moving the mouse 
-    over the thick vertical line on the left side of the desired segment. The 
-    mouse cursor changes its shape to indicate that you can click to move the 
-    toolbar section. </li>
-  <li> Click and hold the left mouse button to grab the toolbar section. </li>
-  <li> Move the section left and right or up and down. Release the mouse button 
-    to place it in the new location. </li>
-  <li> To prevent accidental changes to the toolbar lock it again by right clicking 
-    the toolbar and selecting the <b>Lock the Toolbars</b> menu item. </li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<a href="../concepts/concepts-18.htm"><br>Toolbars</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/3.0_tag.png b/bundles/org.eclipse.platform.doc.user/tips/images/3.0_tag.png
deleted file mode 100644
index 1f21366..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/3.0_tag.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/3.1_tag.png b/bundles/org.eclipse.platform.doc.user/tips/images/3.1_tag.png
deleted file mode 100644
index 212829d..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/3.1_tag.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/add_bkmrk.png b/bundles/org.eclipse.platform.doc.user/tips/images/add_bkmrk.png
deleted file mode 100644
index e46c64a..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/add_bkmrk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/annotations-preferences.png b/bundles/org.eclipse.platform.doc.user/tips/images/annotations-preferences.png
deleted file mode 100644
index bd96253..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/annotations-preferences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/backgroundpref.png b/bundles/org.eclipse.platform.doc.user/tips/images/backgroundpref.png
deleted file mode 100644
index caf8489..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/backgroundpref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/backward_nav.png b/bundles/org.eclipse.platform.doc.user/tips/images/backward_nav.png
deleted file mode 100644
index 5122778..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/backward_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/bookmarks_view.png b/bundles/org.eclipse.platform.doc.user/tips/images/bookmarks_view.png
deleted file mode 100644
index 14211b3..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/bookmarks_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/capabilities-page.png b/bundles/org.eclipse.platform.doc.user/tips/images/capabilities-page.png
deleted file mode 100644
index 09c760d..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/capabilities-page.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/changelog-obj.gif b/bundles/org.eclipse.platform.doc.user/tips/images/changelog-obj.gif
deleted file mode 100644
index f988003..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/changelog-obj.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/collapse-all.png b/bundles/org.eclipse.platform.doc.user/tips/images/collapse-all.png
deleted file mode 100644
index 778fa9a..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/collapse-all.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/compare-merge-button.png b/bundles/org.eclipse.platform.doc.user/tips/images/compare-merge-button.png
deleted file mode 100644
index d84936e..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/compare-merge-button.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/compare-showancestor.png b/bundles/org.eclipse.platform.doc.user/tips/images/compare-showancestor.png
deleted file mode 100644
index feb97ee..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/compare-showancestor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/editor-tiles.png b/bundles/org.eclipse.platform.doc.user/tips/images/editor-tiles.png
deleted file mode 100644
index d434af5..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/editor-tiles.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/fastview-drag.png b/bundles/org.eclipse.platform.doc.user/tips/images/fastview-drag.png
deleted file mode 100644
index 6d47994..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/fastview-drag.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/help-working-set.png b/bundles/org.eclipse.platform.doc.user/tips/images/help-working-set.png
deleted file mode 100644
index 5df6e27..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/help-working-set.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/key-assist.png b/bundles/org.eclipse.platform.doc.user/tips/images/key-assist.png
deleted file mode 100644
index 806fcba..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/key-assist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/key-bindings.png b/bundles/org.eclipse.platform.doc.user/tips/images/key-bindings.png
deleted file mode 100644
index d91d0d7..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/key-bindings.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/keyboard-shortcut.png b/bundles/org.eclipse.platform.doc.user/tips/images/keyboard-shortcut.png
deleted file mode 100644
index 500ebf4..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/keyboard-shortcut.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/last_edit_pos.png b/bundles/org.eclipse.platform.doc.user/tips/images/last_edit_pos.png
deleted file mode 100644
index 2643256..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/last_edit_pos.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/link-with-editor.png b/bundles/org.eclipse.platform.doc.user/tips/images/link-with-editor.png
deleted file mode 100644
index 7ebe7cd..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/link-with-editor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/mini-view.png b/bundles/org.eclipse.platform.doc.user/tips/images/mini-view.png
deleted file mode 100644
index af7da3b..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/mini-view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/path-vars.png b/bundles/org.eclipse.platform.doc.user/tips/images/path-vars.png
deleted file mode 100644
index 881308e..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/path-vars.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/pb-context-menu.png b/bundles/org.eclipse.platform.doc.user/tips/images/pb-context-menu.png
deleted file mode 100644
index 38f0c04..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/pb-context-menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/perspective-other.png b/bundles/org.eclipse.platform.doc.user/tips/images/perspective-other.png
deleted file mode 100644
index a80dda9..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/perspective-other.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/pin-editor.png b/bundles/org.eclipse.platform.doc.user/tips/images/pin-editor.png
deleted file mode 100644
index fe3d91d..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/pin-editor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/props-view.png b/bundles/org.eclipse.platform.doc.user/tips/images/props-view.png
deleted file mode 100644
index 4c1b056..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/props-view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/quickdiff-hover.png b/bundles/org.eclipse.platform.doc.user/tips/images/quickdiff-hover.png
deleted file mode 100644
index f2e1769..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/quickdiff-hover.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/restore-local.png b/bundles/org.eclipse.platform.doc.user/tips/images/restore-local.png
deleted file mode 100644
index 758b8b4..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/restore-local.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/show-in.png b/bundles/org.eclipse.platform.doc.user/tips/images/show-in.png
deleted file mode 100644
index f40c2f3..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/show-in.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/team-project-set.png b/bundles/org.eclipse.platform.doc.user/tips/images/team-project-set.png
deleted file mode 100644
index 4a44fd9..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/team-project-set.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/team_contents_icon.png b/bundles/org.eclipse.platform.doc.user/tips/images/team_contents_icon.png
deleted file mode 100644
index e27b59d..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/team_contents_icon.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/userdialog.png b/bundles/org.eclipse.platform.doc.user/tips/images/userdialog.png
deleted file mode 100644
index 297e3af..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/userdialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/platform_tips.html b/bundles/org.eclipse.platform.doc.user/tips/platform_tips.html
deleted file mode 100644
index 8a75a6a..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/platform_tips.html
+++ /dev/null

@@ -1,753 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Platform Tips and Tricks</title>
-</head>
-
-<body>
-
-<h2>Tips and Tricks</h2>
-
-
-<p>The following tips and tricks give some helpful ideas for increasing your
-productivity. They are divided into the following sections:</p>
-<ul>
-<li><a href="#Workbench">Workbench</a></li>
-<li><a href="#Ant">Ant</a></li>
-<li><a href="#Help">Help</a></li>
-<li><a href="#CVS">Team - CVS</a></li>
-</ul>
-
-<h3><a name="Workbench">Workbench</a></h3>
-
-<table border="1" cellpadding="10" cellspacing="0" width="600">
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Now, where was I?</b></td>
-    <td width="80%" valign="top" align="left">Workbench editors keep a navigation 
-      history. If&nbsp; you open a second editor while you're editing, you 
-      can press <b>Navigate &gt; Backward</b>  (Alt+Left Arrow, or the <img border="0" src="images/backward_nav.png" alt="Left arrow icon" >
-      back arrow 
-      on the workbench toolbar) to go back to the last editor. This makes working with several open editors a whole lot easier.</td>
-  </tr>
-  <tr>
-	<td valign="top" align="left" width="20%">
-		<b>Finding a string incrementally</b></td>
-    <td valign="top" align="left" width="80%">
-        Use <b>Edit &gt; Incremental Find Next</b>  (Ctrl+J) or <b>Edit &gt; Incremental Find Previous</b>
-        (Ctrl+Shift+J)
-        to enter the incremental find mode, and start typing the string to match.
-        Matches are found incrementally as you type.
-        The search string is shown in the status line. Press Ctrl+J or
-        Ctrl+Shift+J to go to the next or previous match. Press Enter or Esc to
-        exit incremental find mode.
-	</td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Go to last edit location</b></td>
-    <td width="80%" valign="top" align="left"><b>Navigate &gt; Go
-      to Last Edit Location</b> (Ctrl+Q) takes you back to
-      the place where you last made a change. A corresponding button marked <img border="0" src="images/last_edit_pos.png" alt="Go to last edit position icon" >
-      is shown in the toolbar. If this toolbar button does not appear in your perspective, you can 
-    add it by selecting <b>Window &gt; Customize Perspective &gt; Other &gt;
-      Editor Navigation</b>.</td>
-  </tr>
-	<TR>
-		<TD width="20%" valign="top" align="left">
-      <B>Shortcuts for manipulating lines</B>
-      <P><IMG border="0" src="images/3.0_tag.png"  alt="New in 3.0"></P>
-      </TD><TD width="80%" valign="top">
-      
-			All text editors based on the
-			Eclipse editor framework support editing functions, including
-			moving lines up or down (Alt+Arrow Up and Alt+Arrow Down), copying lines (Ctrl+Alt+Arrow Up and Ctrl+Alt+Arrow Down), inserting
-			a new line above or below the current line (Ctrl+Shift+Enter and
-			Shift+Enter), and converting to lowercase or uppercase (Ctrl+Shift+Y
-			and Ctrl+Shift+X).
-			</TD>
-		
-	</TR>
-		<TR>
-			<TD width="20%" valign="top" align="left"><B>Quick Diff: seeing what has changed as you edit</B><P><IMG border="0" src="images/3.0_tag.png"  alt="New in 3.0"></P>
-			</TD>
-			
-    <TD width="80%" valign="top"> Quick Diff provides color-coded change indication 
-      while you are typing. It can be turned on for text editors using either 
-      the ruler context menu, Ctrl+Shift+Q or for all new editors on the <B>General 
-      &gt; Editors &gt; Text Editors &gt; Quick Diff</B> preference page. The 
-      colors show additions, deletions, and changes to the editor buffer as compared 
-      to a reference, for example, the contents of the file on disk or its latest 
-      CVS revision. 
-      <P><img src="images/quickdiff-hover.png"  alt="Quick Diff"></P>
-			<P>When the mouse cursor is placed over a change in the vertical
-			ruler, a hover displays the original content, which can be restored using the ruler's context
-			menu. The context menu also allows you to switch between the references and
-			enable/disable Quick Diff.</P></TD>
-		</TR>
-		<TR>
-			<TD width="20%" valign="top" align="left"><b>Customizing the presentation of 
-      annotations</b>
-			<p><IMG
-				border="0" src="images/3.0_tag.png"  alt="New in 3.0"></p></TD>
-			
-    <TD width="80%" valign="top"> You can customize the presentation of annotations 
-      in editors on the <B>General &gt; Editors &gt; Text Editors &gt; Annotations</B> 
-      preference page: 
-      <P><img src="images/annotations-preferences.png" alt="Annotations preference page" title="Annotations Preference Page">
-</P>
-			</TD>
-		</TR>
-     <tr>
-    <td width="20%" valign="top" align="left"><b>Managing screen real estate 
-      with fast views</b></td>
-    <td width="80%" valign="top" align="left">Use fast views to free up screen 
-      real estate while keeping views easily accessible. Clicking on the icon 
-      for a fast view temporarily reveals it over top of the other views. The 
-      fast view retracts as soon you click outside of it. The <b>Fast View</b> 
-      command in the view's system menu toggles whether it is a fast view. You 
-      can also create a fast view by dragging a view onto the shortcut bar at 
-      the left.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Opening editors using drag and 
-      drop</b></td>
-    <td width="80%" valign="top" align="left">You can open an editor on an item 
-      by dragging the item from a view like the Navigator or Package Explorer 
-      and dropping it over the editor area.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Restoring deleted resources</b></td>
-    <td width="80%" valign="top" align="left">Select a container resource and 
-      use <b>Restore from Local History</b> to restore deleted files. You can 
-      restore more than one file at one time. 
-      <p align="center"><img src="images/restore-local.png"  border="0" alt="Restore from local history dialog" align="left"></p></td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Like to start afresh each session?</b></td>
-    <td width="80%" valign="top" align="left">A setting on the <b>General &gt; 
-      Editors</b> preference page closes all open editors automatically whenever 
-      you exit. This makes start-up cleaner and a bit faster.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Better UI for editor / view 
-      synchronization</b></td>
-    <td width="80%" valign="top" align="left">The <b>Navigate &gt; Show In</b> 
-      command provides a uniform way to navigate from an open editor to a view 
-      showing the corresponding file (e.g., in the resource Navigator view), or 
-      from a file selected in one view to the same file in a different view (e.g., 
-      from the resource Navigator view to the Packages Explorer view).
-      <p>Typing Alt+Shift+W opens a shortcut menu with the available view
-      targets.</p>
-      <p><img src="images/show-in.png" alt="Shortcut menu for Show in command"  border="0"></p>
-    </td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>User customizable<br>
-      key bindings</b></td>
-    <td width="80%" valign="top" align="left">If you find yourself repeatedly 
-      doing some command, you might be able to streamline things by assigning 
-      a key sequence to trigger that command. Assigning new key bindings, and 
-      viewing existing bindings, is done from the <b>General &gt; Keys</b> preference 
-      page. 
-      <p><img src="images/key-bindings.png" alt="Key bindings preference dialog"></p></td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Faster workspace navigation</b></td>
-    <td width="80%" valign="top" align="left"><b>Navigate &gt; Open Resource</b> 
-      (Ctrl+Shift+R) brings up a dialog that allows you to quickly locate and 
-      open an editor on any file in the workspace. In the same vein, <b>Navigate 
-      &gt; Go To &gt; Resource</b> expands and selects the resource in the Navigator 
-      view itself, if it has focus.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Tiling the editor work area</b></td>
-    <td width="80%" valign="top" align="left">You can use drag and drop to modify 
-      the layout of your editor work area. Grab an editor tab and drag it to the 
-      edge of the editor work area. The arrow dock icons (e.g., <img src="../images/drop_left_source.png" align="texttop" border="0" alt="Left arrow icon">) 
-      indicate which way the editor work area will split. 
-      <p><img src="images/editor-tiles.png" alt="Tiled editor work area"  border="0"></p></td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Linking view to current open 
-      editor</b></td>
-    <td width="80%" valign="top" align="left"> <p>The resource Navigator view 
-        (and similar views) is not tightly linked to the currently open editor 
-        by default. This means that closing or switching editors does not change 
-        the selection in the Navigator view. Toggling the <b>Link with Editor</b> 
-        button in the Navigator view toolbar ties the view to always show the 
-        current file being edited. </p>
-      <p align="center"><img src="images/link-with-editor.png" alt="Package explorer linked with editor"  border="0"></p></td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Copying and moving resources</b></td>
-    <td width="80%" valign="top" align="left">You can drag and drop files and 
-      folders within the Navigator view to move them around. Hold down the Ctrl 
-      key to make copies.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Importing files</b></td>
-    <td width="80%" valign="top" align="left">You can quickly import files and 
-      folders into your workspace by dragging them from the file system (e.g., 
-      from a Windows Explorer window) and dropping them into the Navigator view. 
-      The files and folder are always copied into the project; the originals are 
-      not affected. Copy and paste also work.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Exporting files</b></td>
-    <td width="80%" valign="top" align="left">Dragging files and folder from the 
-      Navigator view to the file system (e.g., to a Windows Explorer window) exports 
-      the files and folders. The files and folder are always copied; workspace 
-      resources are not affected. Copy and paste also work.</td>
-  </tr>
-  <tr> 
-    <td valign="top" align="left" width="20%"> <strong>Global find/replace</strong> 
-    </td>
-    <td valign="top" align="left" width="80%"> Use <strong>Search &gt; File</strong> 
-      from the main menu to specify the text that you want to replace and the scope
-      in which you want to replace it. Then press <b>Replace...</b>.</td>
-  </tr>
-  <TR>
-		<TD width="20%" valign="top" align="left"><B>Replace from Search view</B>
-		</TD>
-		<TD width="80%" valign="top" align="left">You can replace the matches in the files by using <B>Replace...</B> or <B>Replace
-			Selected...</B> from the context menu in the Search view.</TD>
-  </TR>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Collapsing all open items</b></td>
-    <td width="80%" valign="top" align="left">Use the <b>Collapse All</b> button 
-      on the toolbar of the Navigator view (and similar views) to collapse all 
-      expanded project and folder items. 
-      <p align="center"><img src="images/collapse-all.png" alt="Collapse all button on navigator toolbar" > </p> </td></tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Open editors with a single click</b></td>
-    <td width="80%" valign="top" align="left">Use the Open mode setting on the 
-      <b>General </b> preference page to activate single click opening for editors. 
-      In single click mode, a single click on a file in the Navigator view (and 
-      similar views) selects and immediately opens it. </td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Next / previous navigation</b></td>
-    <td width="80%" valign="top" align="left">You can use Ctrl+. and Ctrl+, to 
-      navigate to the next or previous search match, editor error, or compare 
-      difference. These are the shortcut keys for <b>Navigate &gt; Next</b> and 
-      <b>Navigate &gt; Previous</b>.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Describing your configuration</b></td>
-    <td width="80%" valign="top" align="left">When reporting a problem, it's often 
-      important to be able to capture details about your particular setup. The 
-      <b> Configuration Details</b> button on the <b>Help &gt; About <i>Product</i></b> 
-      dialog opens a file containing various pieces of information about your 
-      setup, including plug-in versions, preference settings, and the contents 
-      of the internal log file. You can save this, and attach the file to your 
-      problem report.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Workspace project management</b></td>
-    <td width="80%" valign="top" align="left">Use the <b>Project &gt; Close Project</b> 
-      command to manage projects within your workspace. When a project is closed, 
-      its resources are temporarily &quot;offline&quot; and no longer appear in 
-      the Workbench (they are still sitting in the local file system). Closed 
-      projects require less memory. Also, since they are not examined during builds, 
-      closing a project can improve build times. </td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Restoring a perspective's layout</b></td>
-    <td width="80%" valign="top" align="left">Rearranging and closing the views 
-      in a perspective can sometimes render it unrecognizable and hard to work 
-      with. To return it to a familiar state, use <b>Window &gt; Reset Perspective</b>. 
-    </td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Pinning editors</b></td>
-    <td width="80%" valign="top" align="left">When the <b> Close editors automatically</b> 
-      preference is active (found on the <b> General &gt; Editors</b> preference 
-      page), you can stop an editor from being closed by using the <b>Pin Editor</b> 
-      button which appears in the workbench toolbar. 
-      <p><img src="images/pin-editor.png" alt="Pin editor button"  border="0"></p></td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Importing an existing project</b></td>
-    <td width="80%" valign="top" align="left">If you import an existing project, 
-      the resources files for the project are <i>not</i> copied. If you check 
-      the properties of the project, you'll see that the project's location in 
-      the file system is the location you specified.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Reordering editor tabs</b></td>
-    <td width="80%" valign="top" align="left">You can rearrange the order of open 
-      editors by using drag and drop. Grab the editor tab and drag it to the position 
-      you want the editor to appear. When positioning editors, the stack icon 
-      <img src="../images/drop_stack.png"  align="texttop" border="0" alt="Stack icon"> 
-      indicates a valid spot to drop.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Deleting completed tasks</b></td>
-    <td width="80%" valign="top" align="left">Use the <b>Delete Completed Tasks</b> 
-      command in the Task view context menu to remove all completed tasks from 
-      the Tasks view. This is more convenient than individually selecting and 
-      deleting completed tasks.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Quick navigation between views, 
-      editors and perspectives</b></td>
-    <td width="80%" valign="top" align="left">A look at the <b>Window &gt; Navigation</b> 
-      menu reveals a number of ways to quickly navigate between the various views, 
-      editors, perspectives, and menus in the workbench. These commands have keyword 
-      accelerators such as <b>Ctrl+F6</b> for switching between editors, <b>Ctrl+F7</b> 
-      for switching between views, <b>Ctrl+F8</b> for switching between perspectives, 
-      and <b>F12</b> for activating the editor. 
-      <p><img src="images/keyboard-shortcut.png" alt="Keyboard shortcuts menu"  border="0"></p> 
-      <p>To directly navigate to a particular view you can define a keyboard shortcut 
-        to a view via the <b>General &gt; Keys</b> preference page.</p></td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Maximizing a view or editor</b></td>
-    <td width="80%" valign="top" align="left">You can maximize a view or editor 
-      by double-clicking on the view's title bar or the editor's tab. Double-click 
-      again to restore it to its usual size.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Viewing resource properties</b></td>
-    <td width="80%" valign="top" align="left">Use the Properties view (<b>Window 
-      &gt; Show View &gt; Properties</b>) when viewing the properties for many 
-      resources. Using this view is faster than opening the Properties dialog 
-      for each resource. 
-      <p><img src="images/props-view.png" alt="Resource properties dialog"  border="0"></p></td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Quickly find a resource</b></td>
-    <td width="80%" valign="top" align="left">Use the <b>Navigate &gt; Go To &gt; 
-      Resource</b> command to quickly find a resource. If the <b>Go To &gt; Resource</b> 
-      command does not appear in your perspective, you can add it by selecting 
-      <b>Window &gt; Customize Perspective &gt; Other &gt; Resource Navigation</b>.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Extra resource information</b></td>
-    <td width="80%" valign="top" align="left">Label decorations are a general 
-      mechanism for showing extra information about a resource. Use the<b> General 
-      &gt; Label Decorations</b> preference page to select which of the available 
-      kinds of decorations you want to see.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Filtering resources</b></td>
-    <td width="80%" valign="top" align="left">The Navigator and Tasks views both 
-      support filtering of their items. You control which items are visible by 
-      applying filters or working sets. The <b>Filters</b> commands are found 
-      on the view menu. The working set is selected using the <b>Select Working 
-      Set</b> command in the Navigator view menu. In the Tasks view, a working 
-      set can be selected from within the <b>Filters</b> dialog.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Customizing toolbar and menu 
-      bar</b></td>
-    <td width="80%" valign="top" align="left">You can customize which items appear 
-      on the main toolbar and menu bar using the <b>Window &gt; Customize Perspective</b> 
-      command. 
-      <p><img src="images/perspective-other.png" alt="Customizing toolbar and menu bar"  border="0"></p></td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Quick fix in Tasks view</b></td>
-    <td width="80%" valign="top" align="left">You can use the <b>Quick Fix</b> 
-      command in the Tasks view to suggest an automatic fix for the selected item. 
-      The <b>Quick Fix</b> command is only enabled when there is a suggested fix.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Creating path variables</b></td>
-    <td width="80%" valign="top" align="left">When creating a linked folder or 
-      file, you can specify the target location relative to a path variable. By 
-      using path variables, you can share projects containing linked resources 
-      without requiring team members to have exactly the same path in the file 
-      system. You can define a path variable at the time you create a linked resource, 
-      or via the <b> General &gt; Workspace &gt; Linked Resources</b> preference 
-      page. 
-      <p align="center"><img src="images/path-vars.png" alt="Path variables dialog"></p></td>
-  </tr>
-  <tr> 
-    <td valign="top" align="left" width="20%"> <strong>Comparing zip archives 
-      with each other or with a folder</strong> </td>
-    <td valign="top" align="left" width="80%"> Select two zip archives or one 
-      archive and a folder in the resource Navigator view and choose <strong>Compare 
-      With &gt; Each Other</strong> from the view's popup menu. Any differences 
-      between the two inputs are opened in a Compare editor. The top pane shows 
-      all the archive entries that differ. Double clicking on an item performs 
-      a content compare in the bottom pane. 
-      <p> This works in any context where a file comparison is involved. So if 
-        a CVS Synchronize operation lists an archive in the resource tree, you 
-        can double click on it in order to drill down into changes within the 
-        archive.</p></td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Switch workspace</b>
-    		<P><IMG border="0" src="images/3.0_tag.png"  alt="New in 3.0"></P></td>
-    <td width="80%" valign="top" align="left"><p>Instead of shutting down eclipse and restarting 
-    	with a different workspace you can instead use the 
-    	<strong>File &gt; Switch Workspace</strong>.</p>
-    	
-      <p>This trick is also useful when you change certain preferences that require 
-        a restart to take effect (such as the <strong>General &gt; Appearance</strong> 
-        Presentation preference). To restart quickly simply switch workspaces 
-        to your current workspace.</p>
-    </td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Ctrl+E Editor List</b>
-    		<P><IMG border="0" src="images/3.0_tag.png"  alt="New in 3.0"></P></td>
-    <td width="80%" valign="top" align="left">You can quickly switch editors using 
-      the Ctrl+E keybinding which opens a list of all open editors. The list supports 
-      type-ahead to find the editor as well as allows you to close editors using 
-      a popup menu or the Delete key. </td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>View Minimizing</b>
-    		<P><IMG border="0" src="images/3.0_tag.png"  alt="New in 3.0"></P></td>
-    <td width="80%" valign="top" align="left">Running out of space? Try minimizing 
-      your unused views to reclaim screen real-estate. Each view stack contains 
-      a minimize icon along side the maximize icon. 
-      <p align="center"><img src="images/mini-view.png" alt="Minimized View Stack"  border="0" align="left"></p></td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Detached Views</b>
-    		<P><IMG border="0" src="images/3.0_tag.png"  alt="New in 3.0"></P></td>
-    <td width="80%" valign="top" align="left">In 3.0 it's possible to dock a view 
-      in its own window, separate from the workbench window. To do so, simply 
-      drag a view outside of the workbench window. To return it to the workbench 
-      window, drag it back. </td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Fast Views and the Perspective 
-      Bar</b>
-      		<P><IMG border="0" src="images/3.0_tag.png"  alt="New in 3.0"></P></td>
-    <td width="80%" valign="top" align="left">The fast view and perspective bars 
-      are independent entities in 3.0 and they may be docked independent of one 
-      another. 
-      <p>By default the Perspective Bar is located in the upper right hand corner 
-        of the screen. It may also be docked on the top left, under the main toolbar 
-        or to the far left. It may be moved via the perspective bar context menu 
-        or via the <strong>General &gt; Appearance</strong> preference page. </p>
-      <p align="left"><img src="images/pb-context-menu.png" alt="Perspective Bar Context Menu"  border="0"></p>
-      <p>By default the Fast View Bar is located in the bottom left hand corner 
-        of the screen. Like the Perspective Bar, it may be docked elsewhere. This 
-        may be done by dragging the area to either the left or right side of the 
-        screen (or back to the bottom if it is already in one of these positions).</p> 
-      <p align="left"><img src="images/fastview-drag.png" alt="Fast View Area"  border="0"></p></td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Key Binding Assistance</b>
-    		<P><IMG border="0" src="images/3.0_tag.png"  alt="New in 3.0"></P></td>
-    <td width="80%" valign="top" align="left"><p>Eclipse supports key bindings 
-        that contain more than one key stroke. Examples of such key bindings are 
-        "Ctrl+X S" ("Save" in the Emacs key configuration) or "Alt+Shift+Q Y" 
-        ("Open Synchronize View" in the Default key configuration). It is hard 
-        to learn these keys, and it can also be hard to remember them if you don't 
-        use them very often. It is now possible to get a little pop-up showing 
-        you the possible completions for the keys you have pressed already.</p>
-      <p align="left"><img src="images/key-assist.png" alt="Key Assist"  border="0"></p>
-      <p>In the preferences, under <strong>General > Keys</strong>, there is an 
-        &quot;Advanced&quot; tab. Go to this tab, and check &quot;Help Me With Multi-Stroke Keyboard 
-        Shortcuts&quot;.</p></td>
-  </tr>
-  <tr> 
-    <td valign="top" align="left"><strong>Always Run in Background</strong>
-    		<P><IMG border="0" src="images/3.0_tag.png"  alt="New in 3.0"></P></td>
-    <td valign="top" align="left"><p>In Eclipse 3.0 many operations can be optionally 
-        run in the background so that you can continue working while they complete.</p>
-      <p><img src="images/userdialog.png" alt="Progress dialog with Run in background button" ></p>
-      <p>In the <strong>General</strong> preference page you can choose to always 
-        run in background so that you never get the initial dialog for these operations.</p>
-      <p><img src="images/backgroundpref.png" alt="Always run in background preference" ></p></td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Disabling Unused Capabilities</b>
-    		<P><IMG border="0" src="images/3.0_tag.png"  alt="New in 3.0"></P></td>
-    <td width="80%" valign="top" align="left"><p>If there are parts of the Eclipse 
-        Platform that you never use (for instance, you don't use CVS repositories 
-        or you don't develop Plug-ins) it's possible that you can disable them 
-        from the UI entirely. Segments of the Workbench that may be filtered can 
-        be found in the <strong>General &gt; Capabilities</strong> preference 
-        page. By disabling capabilities you are able to hide views, perspectives, 
-        preference pages and other assorted contributions.</p>
-	    
-      <p align="left"><img src="images/capabilities-page.png" alt="Capabilities Preference Page"></p>
-    </td>
-  </tr>  
-</table>
-
-<h3><a name="Ant">Ant</a></h3>
-<table border="1" cellpadding="10" cellspacing="0" width="600">
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Launching from the Context menu</b>
-    <p><b><img border="0" src="images/3.0_tag.png" 
-				alt="New in 3.0"></b></p></td>
-    <td width="80%" valign="top" align="left">You can launch an Ant build from 
-      the context menu. Select an Ant buildfile and then choose <b>Run &gt; Ant 
-      Build</b> from the context menu. To configure options before running the 
-      build, use <b>Run &gt; Ant Build...</b>, which will open the launch configuration 
-      dialog. A build can also be started from the Ant editor outline context 
-      menu.</td>
-  </tr>
-   <tr>
-    <td width="20%" valign="top" align="left"><b>Specification of JRE</b>
-    <p><b><img border="0" src="images/3.0_tag.png" 
-				alt="New in 3.0"></b></p></td>
-    <td width="80%" valign="top" align="left">You can specify the JRE that an 
-      Ant build occurs in using the <b>JRE</b> tab of the launch configuration 
-      dialog for an Ant launch configuration. The build can be set to run in a 
-      separate JRE (the default setting) or the same JRE as the Eclipse workspace. 
-      Note that some Eclipse specific tasks require that the build occurs in the 
-      same JRE as Eclipse.</td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Running Ant targets in the Ant view</b></td>
-    <td width="80%" valign="top" align="left">You can double click on a target
-      in the Ant view to run it (equivalent to selecting the target and choosing
-      the <b>Run</b> command from the context menu). </td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Terminating Ant builds</b></td>
-    <td width="80%" valign="top" align="left">The <b>Terminate</b> command in the
-      console (or Debug view) can be used to terminate an Ant build running in
-      the background.</td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Ant output and hyperlinks</b></td>
-    <td width="80%" valign="top" align="left">The output from Ant builds is
-      written to the <b>Console</b> view in the same hierarchical format seen
-      when running Ant from the command line. Ant tasks (for example &quot;[mkdir]&quot;)
-      are hyperlinked to the associated Ant buildfile, and javac error reports
-      are hyperlinked to the associated Java source file and line number.
-      <p>The Console supports hyperlinks for javac and jikes as well as the
-        Eclipse Java compiler. All such error reports are hyperlinked to the associated 
-        Java source file and line number.</p></td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Ant can find it</b></td>
-    <td width="80%" valign="top" align="left"> When the <b>Run &gt; External Tools &gt; Run As &gt; Ant Build</b>
-      launch shortcut is used, it searches for the buildfile
-      to execute starting in the folder of the selected resource and working its way
-      upwards (some will recognize this as Ant's &quot;-find&quot;
-      feature).
-      The names of buildfiles to search for are specified in the Ant preference page.</td>
-  </tr>
-</table>
-
-<h3><a name="Help">Help</a></h3>
-<table border="1" cellpadding="10" cellspacing="0" width="600">
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Help bookmarks</b></td>
-    <td width="80%" valign="top" align="left">You can now keep your own list of
-      bookmarks to pages in help books. Create a bookmark with the <img border="0" src="images/add_bkmrk.png" alt="Bookmark document icon" >
-      <b>Bookmark Document</b>  button on the toolbar of the Help browser. The
-      bookmarks show up in the <img border="0" src="images/bookmarks_view.png" alt="Bookmarks icon" >
-      <b>Bookmarks</b>  tab.</td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Help search scope</b></td>
-    <td width="80%" valign="top" align="left">Help search scope allows narrowing
-     searches down as far as a section of a book, or expanding searches
-     to remote search engines in addition to local documentation.
-     Working sets are persisted from one session to the next, and can be used
-     in workbench help searches.  Search scope of local documentation also
-     applies when searching from within the Help browser. 
-      <p><img border="0" src="images/help-working-set.png" align="left"  alt="Help working set dialog"></p>
-    </td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Context-sensitive
-    infopops</b></td>
-    <td width="80%" valign="top" align="left">If you are familiar
-      with infopops used in previous releases, you can configure Help to use
-      infopops instead of help view for context sensitive help, via a setting
-      on the<b> Help</b> preference page.</td>
-  </tr>
-</table>
-
-<h3><a name="CVS">Team - CVS</a></h3>
-
-<table border="1" cellpadding="10" cellspacing="0" width="600">
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>CVS Watch/Edit</b></td>
-    <td width="80%" valign="top" align="left">The &quot;edit&quot; portion of 
-      CVS Watch/Edit is now supported. Through settings on the <b>Team &gt; CVS 
-      &gt; Watch/Edit</b> preference page (which must be set before the projects 
-      are added to your workspace), you can choose to automatically notify the 
-      CVS server whenever you start to edit a file. In turn, the CVS server will 
-      notify others on the watch list for that file. When you go to edit a file, 
-      you are warned if there are others editing the same file. <b>Team &gt; Show 
-      Editors</b> on a file's context menu lists everyone currently working on 
-      the file. There are also <b>Team &gt; Edit</b> and <b>Unedit</b> commands.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Working set for imported team 
-      projects</b></td>
-    <td width="80%" valign="top" align="left">There is an option to create a working 
-      set for projects imported into the workspace via <b>Import &gt; Team Project 
-      Set</b>. This works for all types of repositories. 
-      <p><img border="0" src="images/team-project-set.png"  alt="Team project set import dialog"></p></td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>CVS now supports working sets</b></td>
-    <td width="80%" valign="top" align="left">Users can now define working sets 
-      which will limit the number of projects shown in the CVS Repositories view.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Comparing different versions</b></td>
-    <td width="80%" valign="top" align="left">Select any folder or file in the 
-      CVS Repositories view and choose <b>Compare With</b> from context menu to 
-      compare it against another version, branch, or date.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Restoring deleted files from 
-      CVS</b></td>
-    <td width="80%" valign="top" align="left">Deleted files can now be queried 
-      and restored from the CVS repository using the <b>Team &gt; Restore from 
-      Repository </b>command, which is available on CVS projects and folders.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Pin a Synchronization</b> <p><b><img border="0" src="images/3.0_tag.png" 
-				alt="New in 3.0"></b></p></td>
-    <td width="80%" valign="top" align="left">You can now have multiple synchronizations 
-      defined and available in the Synchronize View. Use the pin toolbar button 
-      in the Synchronize View to pin a synchronization. The next time you synchronize 
-      a new synchronization will be created. This way you can synchronize different 
-      sets of resources.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Checkout Wizard</b> <p><b><img border="0" src="images/3.0_tag.png" 
-				alt="New in 3.0"></b></p></td>
-    <td width="80%" valign="top" align="left">You can now checkout projects in 
-      one easy step via the <b>File > Import > Checkout projects from CVS wizard</b>. 
-      This also allows checking out projects from a CVS server that doesn't support 
-      browsing of its contents.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Browsing changes by CVS change 
-      set</b> <p><b><img border="0" src="images/3.0_tag.png" 
-				alt="New in 3.0"></b></p></td>
-    <td width="80%" valign="top" align="left">You can browse a set of changes 
-      shown in the Synchronize View grouped logically by author, comment, and 
-      date. Enable the layout by clicking on the Change Set <img alt src="images/changelog-obj.gif"> 
-      toolbar button. This layout can be used in the Incoming mode when synchronizing 
-      and when comparing.</td>
-  </tr>
-  <tr> 
-    <td valign="top" align="left"><p><strong>Group outgoing changes</strong></p>
-      <p><b><img border="0" src="images/3.1_tag.png" 
-				alt="New in 3.1"></b></p></td>
-    <td valign="top" align="left">You can group outgoing changes into change sets 
-      in the Synchronize View. To enable this, switch to Outgoing mode and enable 
-      the Change Set <img alt src="images/changelog-obj.gif"> toolbar button. 
-      You can then create outgoing change sets and assign changes to them.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Schedule a synchronize</b> <p><b><img border="0" src="images/3.0_tag.png" 
-				alt="New in 3.0"></b></p></td>
-    <td width="80%" valign="top" align="left">You can schedule that a certain 
-      synchronization run periodically. You can schedule any CVS synchronization 
-      from within the Synchronize View via the <b>Schedule...</b> action in the 
-      view's dropdown menu.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Want to release changes to an 
-      existing branch</b> <p><b><img border="0" src="images/3.0_tag.png" 
-				alt="New in 3.0"></b></p></td>
-    <td width="80%" valign="top" align="left">If you have changes in your workspace 
-      that you would like to commit to another branch than the one currently connected 
-      to, you can run the <b>Team > Switch to Another Branch or Version</b> command 
-      and switch to another branch. This operation won't modify the changed files 
-      and you can then commit them to the other branch.</td>
-  </tr>
-  <tr> 
-    <td valign="top" align="left" width="20%"><strong>Sharing your CVS lineup 
-      with others</strong></td>
-    <td valign="top" align="left" width="80%"><p CLASS="Head">You can save the 
-        list of projects shared with CVS into a team project set. This provides 
-        an easy way of re-creating your workspace with shared CVS projects. </p>
-      <ol>
-        <li>Once you have checked out the set of projects from the CVS repository, 
-          select <strong>File &gt; Export</strong> from the main menu.</li>
-        <li> Select <strong>Team Project Set</strong> from the list and then select 
-          the projects to be exported. The generated file can be shared with your 
-          team to allow quick setups of your development environment. </li>
-        <li>To import the project set select <strong>File &gt; Import</strong> 
-          and select <strong>Team Project Set</strong>. The projects will be checked 
-          out of CVS and a repository location will automatically be created.</li>
-      </ol></td>
-  </tr>
-  <tr> 
-    <td valign="top" align="left" width="20%"><strong>Reverting a managed CVS 
-      file that was edited, but not committed</strong></td>
-    <td valign="top" align="left" width="80%"><p CLASS="Head">There are a two 
-        ways of doing this:</p>
-      <ol>
-        <li>Select the file and from the context menu select <b> Replace With 
-          &gt; Latest from HEAD</b>.</li>
-      </ol>
-      <p>or</p>
-      <ol>
-        <li>Select the file or a parent folder and from the context menu select 
-          <strong>Team &gt; Synchronize with Repository</strong>.</li>
-        <li>Next switch to incoming/outgoing mode using the toolbar button in 
-          the view.</li>
-        <li>Select the file and from the context menu select <strong>Override 
-          and Update</strong>.</li>
-      </ol></td>
-  </tr>
-  <tr> 
-    <td valign="top" align="left" width="20%"> <b>Show ancestor pane in 3-way 
-      compares</b> </td>
-    <td valign="top" align="left" width="80%"> Whenever a CVS synchronization 
-      results in a conflict, it is helpful to view the common ancestor on which 
-      the two conflicting versions are based. 
-      <p> You can view the common ancestor by toggling the <b>Show Ancestor Pane</b> 
-        button in the compare viewer's local toolbar.</p> 
-      <p> <img src="images/compare-showancestor.png"  alt="Show Ancestor Pane button in compare viewer" border="0"> </p>
-      <p> If you always want to have the ancestor pane open automatically for 
-        conflicts, you can check the option <b>Initially show ancestor pane</b> 
-        on the Text Compare tab of the Compare/Patch preference page.</p> </td>
-  </tr>
-  <TR> 
-    <TD width="20%" valign="top" align="left"><B>Merge in Compare editor</B> <P><IMG border="0" src="images/3.0_tag.png"  alt="New in 3.0"></P></TD>
-    <TD width="80%" valign="top" align="left">You can merge incoming changes in 
-      the compare editor with one click. Hover over the small square in the middle 
-      of the line connecting two ranges of an incoming or conflicting change. 
-      A button appears that allows you to accept the change. 
-      <P><IMG border="0" src="images/compare-merge-button.png" alt="Merge button" ></P>
-      <P>Note that for this the option <B>Connect ranges with single line</B> 
-        on the <B>General &gt; Compare/Patch &gt; Text Compare</B> preference 
-        page has to be enabled.</P></TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left"><p><strong>Content assist for branching and 
-        merging</strong></p>
-      <p><b><img border="0" src="images/3.1_tag.png" 
-				alt="New in 3.1"></b></p></TD>
-    <TD valign="top" align="left">When branching and merging with CVS, you can 
-      use content assist in the tag fields to help select an appropriate tag. 
-      For instance, when branching, you can use content assist to pick a tag from 
-      the list of branch tags that exist on the other projects in your workspace. 
-      When merging, you can use content assist to pick the branch that contains 
-      the changes you are merging. The merge wizard will also try to pick the 
-      proper start tag for you so you do not have to pick it manually.</TD>
-  </TR>
-  <TR>
-    <TD valign="top" align="left"><p><strong>Filtering in tag selection dialogs</strong></p>
-      <p><b><img border="0" src="images/3.1_tag.png" 
-				alt="New in 3.1"></b></p></TD>
-    <TD valign="top" align="left">There are several CVS operations that allow 
-      the user to specify a tag (e.g. Replace With Branch or Version, Compare 
-      With Branch or Version, Checkout, etc.). These dialogs now allow you to 
-      type in part of the tag name (or simple name filters using the * and ? wildcard 
-      characters) and display all the tags that match what you have typed so far. 
-      This greatly simplifies finding the desired tag when performing these operations.</TD>
-  </TR>
-</table>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/toc.xml b/bundles/org.eclipse.platform.doc.user/toc.xml
deleted file mode 100644
index e04505d..0000000
--- a/bundles/org.eclipse.platform.doc.user/toc.xml
+++ /dev/null

@@ -1,24 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define the top level topics                                                   -->
-<!-- ============================================================================= -->
-
-<toc label="Workbench User Guide">
-	<topic label="Getting started">
-		<link toc="topics_GettingStarted.xml" />
-	</topic>
-	<topic label="Concepts">
-		<link toc="topics_Concepts.xml" />
-	</topic>
-	<topic label="Tasks">
-		<link toc="topics_Tasks.xml" />
-	</topic>
-	<topic label="Reference">
-		<link toc="topics_Reference.xml" />
-	</topic>
-	<topic label="Tips and tricks" href="tips/platform_tips.html"/>
-	<topic label="What's new" href="whatsNew/platform_whatsnew.html"/>
-	<topic label="Documentation Images" href="doc.html"/>
-	<topic label="Legal" href="notices.html"/>
-</toc>

diff --git a/bundles/org.eclipse.platform.doc.user/topics_Concepts.xml b/bundles/org.eclipse.platform.doc.user/topics_Concepts.xml
deleted file mode 100644
index 80ec375..0000000
--- a/bundles/org.eclipse.platform.doc.user/topics_Concepts.xml
+++ /dev/null

@@ -1,76 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ========================== -->
-<!-- Define topics for the Concepts -->
-<!-- ========================== -->
-<toc label="Concepts">
-<!-- <topic label="What's new in this release" /> -->
-<topic label="Workbench" href="concepts/concepts-2.htm" >
-
-<!--  <topic label="Workspace" /> -->
-
-  <topic label="Resources" href="concepts/concepts-12.htm" />
-  <topic label="Resource hierarchies" href="concepts/concepts-17.htm" />
-  <topic label="Linked resources" href="concepts/concepts-13.htm" />
-  <topic label="Path variables" href="concepts/cpathvars.htm" />
-  <topic label="Working sets" href="concepts/cworkset.htm"/>
-<!--  <topic label="Projects and project natures" /> -->
-  <topic label="Builds" href="concepts/concepts-22.htm" />
-  <topic label="Local history" href="concepts/concepts-17a.htm" />
-<!--  <topic label="Class path and build class path" /> -->
-</topic>
-<anchor id="c_afterworkbench" />
-<topic label="Perspectives" href="concepts/concepts-4.htm" >
-<!--  <topic label="Resource perspective" /> -->
-</topic>
-<anchor id="c_afterperspectives" />
-<topic label="Editors" href="concepts/concepts-6.htm" >
-  <topic label="External editors" href="concepts/concepts-6a.htm" />
-</topic>
-<anchor id="c_aftereditors" />
-<topic label="Views" href="concepts/concepts-5.htm" >
-  <topic label="Fast views" href="concepts/concepts-21.htm" />
-  <topic label="Navigator view" href="concepts/cnav.htm" />
-  <topic label="Help view" href="concepts/chelpview.htm" />
-  <topic label="Tasks view" href="concepts/ctskview.htm" />
-  <topic label="Problems view" href="concepts/cprbview.htm" />
-  <topic label="Outline view" href="concepts/coutline.htm" />
-  <topic label="Properties view" href="concepts/cpropview.htm" />
-  <topic label="Search view" href="concepts/csearchview.htm" />
-</topic>
-<anchor id="c_afterviews" />
-<topic label="Toolbars" href="concepts/concepts-18.htm" />
-<anchor id="c_aftertoolbars" />
-<topic label="Markers" href="concepts/concepts-11.htm" />
-<anchor id="c_aftermarkers" />
-<topic label="Bookmarks" href="concepts/cbookmrk.htm" />
-<anchor id="c_afterbookmarks" />
-<topic label="Label decorations" href="concepts/cdecorations.htm" />
-<anchor id="c_afterdecorations" />
-<topic label="Help system" href="concepts/chelpsys.htm" />
-<anchor id="c_afterhelp" />
-<topic label="External tools" href="concepts/concepts-exttools.htm" >
-  <topic label="Ant support" href="concepts/concepts-antsupport.htm"/>
-</topic>
-<anchor id="c_afterexternaltools" />
-<topic label="Team programming with CVS" href="concepts/concepts-26.htm" >
-  <topic label="Versions" href="concepts/concepts-27.htm" />
-  <topic label="Branches" href="concepts/concepts-27b.htm" />
-  <topic label="CVS Repositories" href="concepts/concepts-27c.htm" />
-  <topic label="Three way comparisons" href="concepts/concepts-29.htm" />
-  <topic label="Synchronizing with a CVS repository" href="concepts/concepts-30.htm" />
-  <topic label="Watch/Edit" href="concepts/concepts-cvs-watch.htm" />
-</topic>
-<anchor id="c_afterteam" />
-
-<topic label="Accessibility features in Eclipse" href="concepts/accessibility/accessmain.htm">
-    <topic label="Navigating the user interface using the keyboard"  href="concepts/accessibility/navigation.htm"/>
-    <topic label="Fonts and colors in Eclipse"  href="concepts/accessibility/fontsandcolors.htm"/>
-</topic>
-<anchor id="c_afteraccessibility" />
-
-<topic label="Features" href="concepts/concepts-25.htm" >
-</topic>
-<anchor id="c_afterfeatures" />
-
-</toc>

diff --git a/bundles/org.eclipse.platform.doc.user/topics_GettingStarted.xml b/bundles/org.eclipse.platform.doc.user/topics_GettingStarted.xml
deleted file mode 100644
index b1a5ac7..0000000
--- a/bundles/org.eclipse.platform.doc.user/topics_GettingStarted.xml
+++ /dev/null

@@ -1,158 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ========================== -->
-<!-- Define topics for the GettingStarted -->
-<!-- ========================== -->
-<toc label="GettingStarted" extradir="gettingStarted/intro.htm">
-   <topic label="Basic tutorial" href="gettingStarted/qs-01.htm">
-      <topic label="The Workbench" href="gettingStarted/qs-02a.htm"/>
-      <topic label="Editors and views" href="gettingStarted/qs-02b.htm">
-         <topic label="Editors" href="gettingStarted/qs-02d.xhtml"/>
-         <topic label="Views" href="gettingStarted/qs-02e.htm"/>
-      </topic>
-          
-      <topic label="A simple project" href="gettingStarted/qs-07a.htm">
-         <topic label="Using the File menu" href="gettingStarted/qs-07b.htm"/>
-         <topic label="Using the popup" href="gettingStarted/qs-07c.htm"/>
-         <topic label="Using the New button" href="gettingStarted/qs-07d.htm"/>
-      </topic>
- 
-      <topic label="Closing an editor" href="gettingStarted/qs-10b.htm"/>
-
-      <topic label="Navigating resources" href="gettingStarted/qs-12.htm">
-         <topic label="Opening resources in the Navigator" href="gettingStarted/qs-12b.htm"/>
-         <topic label="Go To" href="gettingStarted/qs-12c.htm"/>
-         <topic label="Go Into" href="gettingStarted/qs-12d.htm"/>
-      </topic>
-
-      <topic label="Files" href="gettingStarted/qs-13.htm"/>
-
-      <topic label="Exporting files" href="gettingStarted/qs-24a.xhtml">
-      </topic>
-
-      <topic label="Importing files" href="gettingStarted/qs-31a.htm">
-         <topic label="Drag and drop or copy and paste" href="gettingStarted/qs-31b.htm"/>
-         <topic label="Import wizard" href="gettingStarted/qs-31c.htm"/>
-      </topic>
-
-      <topic label="Deleting resources" href="gettingStarted/qs-32.htm"/>
-	  
-      <topic label="Working with other editors" href="gettingStarted/qs-34a.xhtml">
-         <topic label="External editors" href="gettingStarted/qs-34b.xhtml"/>
-         <topic label="Embedded editors" href="gettingStarted/qs-34c.xhtml"
-             filter="ws=win32"/>
-         <topic label="Editing files outside the Workbench" href="gettingStarted/qs-34d.htm"/>
-	 </topic>
-
-      <topic label="Copying, renaming and moving" href="gettingStarted/qs-35.htm">
-         <topic label="Copying" href="gettingStarted/qs-35b.htm"/>
-         <topic label="Renaming" href="gettingStarted/qs-35c.htm"/>
-         <topic label="Moving" href="gettingStarted/qs-35d.htm"/>
-      </topic>
-
-      <topic label="Searching" href="gettingStarted/qs-36.htm">
-         <topic label="Starting a search" href="gettingStarted/qs-36a.htm"/>
-         <topic label="The Search view" href="gettingStarted/qs-36b.htm"/>
-      </topic>
-
-      <topic label="Tasks and markers" href="gettingStarted/qs-37-2b.htm">
-         <topic label="Unassociated tasks" href="gettingStarted/qs-37-2d.htm"/>
-         <topic label="Associated tasks" href="gettingStarted/qs-37-2d2.htm"/>
-         <topic label="Opening files" href="gettingStarted/qs-37-2f.htm"/>
-      </topic>
-
-      <topic label="Bookmarks" href="gettingStarted/qs-37-3b.htm">
-         <topic label="Adding and viewing bookmarks" href="gettingStarted/qs-37-3c.htm"/>
-         <topic label="Using bookmarks" href="gettingStarted/qs-37-3e.htm"/>
-        <topic label="Removing bookmarks" href="gettingStarted/qs-37-3f.htm"/>
-      </topic>
-
-      <topic label="Rearranging views and editors" href="gettingStarted/qs-39.htm">
-         <topic label="Drop cursors" href="gettingStarted/qs-39c.htm"/>
-         <topic label="Rearranging views" href="gettingStarted/qs-39d.htm"/>
-         <topic label="Tiling editors" href="gettingStarted/qs-39e.htm"/>
-         <topic label="Rearranging tabbed views" href="gettingStarted/qs-39f.htm" />
-         <topic label="Maximizing" href="gettingStarted/qs-39g.htm"/>
-      </topic>
-
-      <topic label="Fast views" href="gettingStarted/qs-40.htm">
-         <topic label="Creating fast views" href="gettingStarted/qs-40a.htm"/>
-         <topic label="Working with fast views" href="gettingStarted/qs-40b.htm"/>
-      </topic>
-
-      <topic label="Perspectives" href="gettingStarted/qs-43.htm">
-         <topic label="New perspectives" href="gettingStarted/qs-43b.htm"/>
-         <topic label="New windows" href="gettingStarted/qs-43c.htm"/>
-         <topic label="Saving perspectives" href="gettingStarted/qs-43e.htm"/>
-         <topic label="Configuring perspectives" href="gettingStarted/qs-43f.htm"/>
-      </topic>
-
-      <topic label="Comparing" href="gettingStarted/qs-52.htm">
-         <topic label="Simple compare" href="gettingStarted/qs-52c.htm"/>
-         <topic label="Understanding the comparison" href="gettingStarted/qs-52d.htm"/>
-         <topic label="Working with the comparison" href="gettingStarted/qs-52e.htm"/>
-      </topic>
-
-      <topic label="Local history" href="gettingStarted/qs-55.htm"/>
-	  
-	  <topic label="Responsive UI" href="gettingStarted/qs-responsiveUI.htm"/>	
-
-      <topic label="Exiting the Workbench" href="gettingStarted/qs-55b.htm"/>
-
-   </topic>
-   
-   <anchor id="gs_afterbasic" />
-
-   <topic label="Team CVS tutorial" href="gettingStarted/qs-60_team.htm">
-      <topic label="Setting up a CVS repository" href="gettingStarted/qs-60a_setup.htm"/>
-      <topic label="Starting offline" href="gettingStarted/qs-61c_offline.htm"/>
-
-      <topic label="Sharing the project" href="gettingStarted/qs-61d_repoloca.htm">
-         <topic label="Specifying a repository location" href="gettingStarted/qs-61d_repolocb.htm"/>
-         <topic label="Repository locations" href="gettingStarted/qs-61e_whatisloc.htm"/>
-         <topic label="Sharing a project" href="gettingStarted/qs-61f_syncproject.htm"/>
-      </topic>
-
-      <topic label="Working with another user" href="gettingStarted/qs-64a_another.htm">
-         <topic label="Checking out a project" href="gettingStarted/qs-64b_fredadd.htm"/>
-         <topic label="Another user making changes" href="gettingStarted/qs-64b_fredmod.htm"/>
-         <topic label="Making our own changes" href="gettingStarted/qs-64c_catch_mod.htm"/>
-         <topic label="Working with conflicting changes" href="gettingStarted/qs-64c_catch_sync_view.htm"/>
-         <topic label="Replacing" href="gettingStarted/qs-70_replace.htm"/>
-         <topic label="Versioning your project" href="gettingStarted/qs-74_version.htm"/>
-         <topic label="A quick review" href="gettingStarted/qs-74_review.htm"/>
-      </topic>
-
-   </topic>
-
-   <anchor id="gs_afterteam" />
-
-   <topic label="Ant &amp; external tools tutorial" href="gettingStarted/qs-80_ant.htm">
-     <topic label="Eclipse Ant basics" href="gettingStarted/qs-81_basics.htm">
-       <topic label="Creating Ant buildfiles" href="gettingStarted/qs-82_create.htm"/>
-       <topic label="Editing Ant buildfiles" href="gettingStarted/qs-83_edit.htm"/>
-       <topic label="Running Ant buildfiles" href="gettingStarted/qs-84_run_ant.htm"/>
-       <topic label="Saving &amp; Reusing Ant options" href="gettingStarted/qs-85_ant_configs.htm"/>
-       <topic label="Using the Ant view" href="gettingStarted/qs-85a_ant_view.htm"/>
-     </topic>
-     <topic label="Use cases for Ant in Eclipse" href="gettingStarted/qs-86_use_cases.htm">     
-       <topic label="Deploying Eclipse plug-ins" href="gettingStarted/qs-87_plugin_deploy.htm">
-         <topic label="Creating a HelloWorld plug-in" href="gettingStarted/qs-88_create_plugin.htm"/>
-         <topic label="Generating the build.xml file" href="gettingStarted/qs-89_generate_buildxml.htm"/>
-         <topic label="Building a .jar file for the plug-in" href="gettingStarted/qs-90_build_jar.htm"/>
-         <topic label="More plug-in deployment options" href="gettingStarted/qs-91_build_options.htm"/>
-       </topic>      
-       <topic label="Ant buildfiles as project builders" href="gettingStarted/qs-92_project_builders.htm">
-         <topic label="Creating a project builder Ant buildfile" href="gettingStarted/qs-93_project_builder.htm"/>
-         <topic label="Executing project builders" href="gettingStarted/qs-94_run_pj.htm"/>       
-       </topic>      
-     </topic>	
-     <topic label="External tools" href="gettingStarted/qs-95_external_tools.htm">
-       <topic label="Non-Ant project builders" href="gettingStarted/qs-96_non_ant_pjs.htm"/>
-       <topic label="Stand-alone external tools" href="gettingStarted/qs-97_standalone_ets.htm"/>
-     </topic>	
-   </topic>
-   
-   <anchor id="gs_afterant" />
-   
-</toc>

diff --git a/bundles/org.eclipse.platform.doc.user/topics_Reference.xml b/bundles/org.eclipse.platform.doc.user/topics_Reference.xml
deleted file mode 100644
index f667c00..0000000
--- a/bundles/org.eclipse.platform.doc.user/topics_Reference.xml
+++ /dev/null

@@ -1,151 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ========================== -->
-<!-- Define topics for the Reference -->
-<!-- ========================== -->
-<toc label="Reference">
-
-<!-- <topic label="Keyboard shortcuts" /> -->
-<topic label="Crash recovery" href="reference/ref-8.htm" />
-
-<anchor id="r_aftercrash" />
-
-	<topic label="Preferences" href="reference/ref-72.htm">
-		<topic label="Accessibility" href="reference/ref-7.htm"></topic>
-		<topic label="Annotations" href="reference/ref-22.htm"></topic>
-		<topic label="Ant" href="reference/ref-antprefs.htm"></topic>
-		<topic label="Ant Code Assist" href="reference/ref-antcodeassist.htm"></topic>		
-		<topic label="Ant Editor" href="reference/ref-anteditorprefs.htm"></topic>		
-		<topic label="Ant Formatter" href="reference/ref-antformatter.htm"></topic>		
-		<topic label="Ant Runtime" href="reference/ref-antruntimeprefs.htm"></topic>
-		<topic label="Ant Templates" href="reference/ref-anttemplates.htm"></topic>	
-		<topic label="Appearance" href="reference/ref-16.htm"></topic>
-		<topic label="Automatic Updates" href="reference/ref-21a.htm"></topic>
-		<topic label="Build Order" href="reference/ref-17.htm"></topic>
-		<topic label="Capabilities" href="reference/ref-activitiespref.htm"></topic>
-		<topic label="Colors and Fonts" href="reference/ref-fonts.htm"></topic>
-		<topic label="Compare/Patch" href="reference/ref-11.htm"></topic>
-		<topic label="Content Types" href="reference/ref-content-type.htm"></topic>
-		<topic label="CVS" href="reference/ref-19cvs.htm"></topic>
-		<topic label="CVS Console" href="reference/ref-19cvs-console.htm"></topic>
-		<topic label="CVS Ext Connection Method" href="reference/ref-19cvs-ext.htm"></topic>
-		<topic label="CVS Label Decorations" href="reference/ref-19cvs-decorations.htm"></topic>
-		<topic label="CVS Password Management" href="reference/ref-19cvs-password.htm"></topic>
-		<topic label="CVS SSH2 Connection Method" href="reference/ref-19cvs-ssh2.htm"></topic>
-		<topic label="CVS Synchronize/Compare" href="reference/ref-19cvs-sync.htm"></topic>
-		<topic label="CVS Watch/Edit" href="reference/ref-19cvs-watch-edit.htm"></topic>
-		<topic label="Editors" href="reference/ref-12.htm"></topic>
-		<topic label="External Tools" href="reference/ref-exttoolsprefs.htm"></topic>
-		<topic label="File Associations" href="reference/ref-13.htm"></topic>
-		<topic label="General" href="reference/ref-10.htm"></topic>
-		<topic label="Help" href="reference/ref-18.htm"></topic>
-		<topic label="Help Server" href="reference/ref-helpserver.htm"></topic>
-		<topic label="Install/Update" href="reference/ref-21.htm"></topic>
-		<topic label="Keys" href="concepts/accessibility/keyboardshortcuts.htm"></topic>
-		<topic label="Label Decorations" href="reference/ref-decorations.htm"></topic>
-		<topic label="Linked Resources" href="reference/ref-14b.htm"></topic>
-		<topic label="Local History" href="reference/ref-14.htm"></topic>
-		<topic label="Perspectives" href="reference/ref-15.htm"></topic>
-		<topic label="Quick Diff" href="reference/ref-35.htm"></topic>
-		<topic label="Search" href="reference/ref-search.htm"></topic>
-		<topic label="Spelling" href="reference/ref-36.htm"></topic>
-		<topic label="Startup and Shutdown" href="reference/ref-startup.htm"></topic>
-		<topic label="Team" href="reference/ref-19.htm"></topic>
-		<topic label="Team File Content" href="reference/ref-20-fileContent.htm"></topic>
-		<topic label="Team Ignored Resources" href="reference/ref-20.htm"></topic>
-		<topic label="Text editors" href="reference/ref-texteditorprefs.htm"></topic>
-		<topic label="Web Browser" href="reference/ref-42.htm"></topic>
-		<topic label="Workspace" href="reference/ref-9.htm"></topic>
-	</topic>
-    
-    <anchor id="r_afterpref" />
-	
-	<topic label="Team support with CVS">
-		<topic label="CVS" href="reference/ref-47.htm"></topic>
-		<topic label="CVS Repositories view" href="reference/ref-32.htm"></topic>
-		<topic label="CVS Workspace Synchronization" href="reference/ref-33.htm"></topic>
-		<topic label="CVS Resource History view" href="reference/ref-32a.htm"></topic>
-		<topic label="CVS Console" href="reference/ref-32b.htm"></topic>
-		<topic label="Add CVS Repository wizard" href="reference/ref-40.htm"></topic>
-		<topic label="CVS Checkout wizard" href="reference/ref-40a.htm"></topic>
-		<topic label="CVS Sharing wizard" href="reference/ref-40b.htm"></topic>
-		<topic label="Merge wizard" href="reference/ref-41a.htm"></topic>
-		<topic label="CVS Merge Synchronization" href="reference/ref-33a.htm"></topic>
-		<topic label="Ignoring resources from version control" href="reference/ref-48a.htm" ></topic>
-		<topic label="CVS Label Decorations" href="reference/ref-cvs-decorations.htm"></topic>
-	</topic>
-	
-	<anchor id="r_afterteam" />
-	
-<topic label="User interface information" >
-	<topic label="Development environment">
-		<topic label="Workbench toolbar" href="reference/ref-2.htm"></topic>
-		<topic label="Perspective Bar" href="reference/ref-3.htm"></topic>
-		<topic label="Fast View Bar" href="reference/ref-3a.htm"></topic>
-		<topic label="View toolbars" href="reference/ref-4.htm"></topic>
-		<topic label="Builds" href="reference/ref-5.htm"></topic>
-		<topic label="Perspectives" href="reference/ref-6.htm"></topic>
-		<topic label="Local history" href="reference/ref-6a.htm"></topic>		
-		<topic label="List of key bindings" href="reference/ref-keybindings.htm"></topic>
-	</topic>
-
-
-	<topic label="Views and editors">
-		<topic label="Workbench window layout" href="reference/ref-23.htm"></topic>
-		<topic label="Editor area" href="reference/ref-24.htm"></topic>
-		<topic label="Compare editor" href="reference/ref-25.htm"></topic>
-		<topic label="Search view" href="reference/ref-26.htm"></topic>
-		<topic label="Navigator view" href="reference/ref-27.htm"></topic>
-		<topic label="Bookmarks view" href="reference/ref-28.htm"></topic>
-		<topic label="Properties view" href="reference/ref-29.htm"></topic>
-		<topic label="Outline view" href="reference/ref-30.htm"></topic>
-		<topic label="CVS views" href="reference/ref-30a.htm"></topic>
-        <topic label="Tasks view" href="reference/ref-31.htm"></topic>
-		<topic label="Problems view" href="reference/ref-31a.htm"></topic>
-		<topic label="Ant editor" href="reference/ref-anteditor.htm"></topic>
-		<topic label="Ant view" href="reference/ref-antview.htm"></topic>
-		<topic label="Help window" href="reference/ref-34.htm"></topic>
-	</topic>
-
-	<topic label="Wizards">
-		<topic label="New Project wizard" href="reference/ref-37.htm"></topic>
-		<topic label="New Folder wizard" href="reference/ref-38.htm"></topic>
-		<topic label="New File wizard" href="reference/ref-39.htm"></topic>
-		<topic label="CVS Wizards" href="reference/ref-39a.htm"></topic>
-        <topic label="Import wizard" href="reference/ref-70.htm"></topic>
-		<topic label="Export wizard" href="reference/ref-71.htm"></topic>
-	</topic>
-
-
-	<topic label="Help contents">
-		<topic label="Workbench User Guide" href="reference/ref-43.htm"></topic>
-		<topic label="Working with Cheat Sheets" href="reference/ref-cheatsheets.htm">
-		    <topic label="Working with Composite Cheat Sheets" href="reference/ref-composite-cheatsheets.htm"></topic>
-		</topic>
-	</topic>
-
-	<topic label="Search">
-		<topic label="File search" href="reference/ref-45.htm"></topic>
-	</topic>
-
-	<topic label="Workbench menus">
-		<topic label="File menu" href="reference/ref-56.htm"></topic>
-		<topic label="Edit menu" href="reference/ref-57.htm"></topic>
-		<topic label="Navigate menu" href="reference/ref-58.htm"></topic>
-		<topic label="Project menu" href="reference/ref-59.htm"></topic>
-		<topic label="Window menu" href="reference/ref-60.htm"></topic>
-		<topic label="Help menu" href="reference/ref-61.htm"></topic>
-	</topic>
-
-	<topic label="Icons and buttons">
-		<topic label="Navigator view icons" href="reference/ref-65.htm"></topic>
-		<topic label="Editor area marker bar" href="reference/ref-66.htm"></topic>
-		<topic label="Tasks view" href="reference/ref-67.htm"></topic>
-		<topic label="Toolbar buttons" href="reference/ref-68.htm"></topic>
-		<topic label="External Tools and Ant Icons" href="reference/ref-anticons.htm"></topic>
-	</topic>
-</topic>
-
-<anchor id="r_afteruser" />
-
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/topics_Tasks.xml b/bundles/org.eclipse.platform.doc.user/topics_Tasks.xml
deleted file mode 100644
index 1d81bf7..0000000
--- a/bundles/org.eclipse.platform.doc.user/topics_Tasks.xml
+++ /dev/null

@@ -1,227 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ========================== -->
-<!-- Define topics for the Tasks -->
-<!-- ========================== -->
-<toc label="Tasks">
-
-<topic label="Running Eclipse" href="tasks/running_eclipse.htm" />
-
-<anchor id="t_afterrunning" />
-
-<topic label="Upgrading Eclipse" href="tasks/tasks-2.htm" />
-
-<anchor id="t_afterupgrading" />
-
-<topic label="Working with perspectives" href="tasks/tasks-1a.htm" >
-  <topic label="Switching between perspectives" href="tasks/tasks-28.htm" />
-  <topic label="Specifying the default perspective" href="tasks/tasks-31.htm" />
-  <topic label="Opening perspectives" href="tasks/tasks-9f.htm" />
-  <topic label="Changing where perspectives open" href="tasks/tasks-24.htm" />
-  <topic label="Configuring perspectives" href="tasks/tasks-9k.htm" />
-  <topic label="Saving a user defined perspective" href="tasks/tasks-9i.htm" />
-  <topic label="Deleting a user defined perspective" href="tasks/tasks-9d.htm" />
-  <topic label="Resetting perspectives" href="tasks/tasks-9j.htm" />
-</topic>
-
-<anchor id="t_afterworking_perspectives" />
-
-<topic label="Working with views and editors"  href="tasks/tasks-1b.htm" >
-  <topic label="Opening views" href="tasks/tasks-3.htm" />
-  <topic label="Moving and docking views" href="tasks/tasks-3e.htm" />
-  <topic label="Rearranging tabbed views" href="tasks/tasks-3h.htm" />
-  <topic label="Creating fast views" href="tasks/tasks-9b.htm" />
-  <topic label="Working with fast views" href="tasks/tasks-9c.htm" />
-  <topic label="Opening files for editing" href="tasks/tasks-46.htm" />
-  <topic label="Associating editors with file types" href="tasks/tasks-51.xhtml" />
-  <topic label="Editing files outside the Workbench" href="tasks/tasks-52.htm" />
-  <topic label="Tiling editors" href="tasks/tasks-3g.htm" />
-  <topic label="Maximizing a view or editor" href="tasks/tasks-3i.htm" />
-</topic>
-
-<anchor id="t_afterworking_views" />
-
-<topic label="Customizing the Workbench" href="tasks/tasks-1.htm" >
-  <topic label="Rearranging the main toolbar" href="tasks/ttoolbars.htm" />
-  <topic label="Changing the key bindings" href="tasks/tkeybindings.htm" />
-  <topic label="Changing fonts and colors" href="tasks/tasks-20.htm" />
-  <topic label="Changing the placement of the tabs" href="tasks/tasks-9.htm" />
-  <topic label="Controlling single and double click behavior" href="tasks/topenmode.htm" />
-  <topic label="Importing and Exporting Preferences" href="tasks/timpandexp.htm"/>
-</topic>
-
-<anchor id="t_aftercustomizing" />
-
-<topic label="Working with projects, folders and files" href="tasks/tasks-1e.htm" >
-  <topic label="Creating a project" href="tasks/tasks-42.htm" />
-  <topic label="Closing projects" href="tasks/tasks-47.htm" />
-  <topic label="Deleting projects" href="tasks/tasks-42b.htm" />
-  <topic label="Creating a folder" href="tasks/tasks-43.htm" />
-  <topic label="Creating a file" href="tasks/tasks-44.htm" />
-  <topic label="Creating linked resources" href="tasks/tasks-45.htm" />
-  <topic label="Moving resources" href="tasks/tasks-63.htm" />
-  <topic label="Copying resources" href="tasks/tasks-63cg.htm" />
-  <topic label="Renaming resources" href="tasks/tasks-66.htm" />
-  <topic label="Deleting resources" href="tasks/tasks-67.htm" />
-  <topic label="Viewing resources properties" href="tasks/tasks-49.htm" />
-</topic>
-
-<anchor id="t_afterworking_projects" />
-
-
-<topic label="Navigating and finding resources" href="tasks/tasks-1c.htm" >
-  <topic label="Finding a resource quickly" href="tasks/tasks-46ag.htm" />
-  <topic label="Searching for files" href="tasks/tasks-84b.htm" />  
-  <topic label="Searching for text within a file" href="tasks/tasks-84.htm" />
-  <topic label="Sorting resources in the Navigator view" href="tasks/tasks-48.htm" />
-  <topic label="Showing or hiding files in the Navigator view" href="tasks/tasks-48b.htm" />
-  <topic label="Narrowing the scope of the Navigator view" href="tasks/tasks-46bg.htm" />
-  <topic label="Linking the Navigator view to the active editor" href="tasks/tasks-18.htm" />
-</topic>
-
-<anchor id="t_afternavigating" />
-
-<topic label="Bookmarks, tasks and other markers" href="tasks/tasks-1d.htm" >
-  <topic label="Creating a bookmark within a file" href="tasks/tasks-81.htm" />
-  <topic label="Creating a bookmark for an entire file" href="tasks/tasks-81b.htm" />
-  <topic label="Deleting a bookmark" href="tasks/tasks-82.htm" />
-  <topic label="Adding line items in the Tasks view" href="tasks/tasks-77.htm" />
-  <topic label="Associating a task with a resource" href="tasks/tasks-77b.htm" />
-  <topic label="Deleting tasks" href="tasks/tasks-78.htm" />
-  <topic label="Filtering the Tasks and Problems views" href="tasks/tasks-79.htm" />
-  <topic label="Automatically fixing problems" href="tasks/tquickfix.htm" />
-</topic>
-
-<anchor id="t_afterbookmarks" />
-
-<topic label="Comparing resources" href="tasks/tasks-68.htm" >
-  <topic label="Setting preferences for comparing files" href="tasks/tasks-68b.htm" />
-  <topic label="Understanding the comparison" href="tasks/tasks-68bg.htm" />
-  <topic label="Merging changes in the compare editor" href="tasks/tasks-68dg.htm" />
-</topic>
-
-<anchor id="t_aftercomparing" />
-
-<topic label="Working with local history" href="tasks/tasks-1f.htm" >
-  <topic label="Comparing resources with the local history" href="tasks/tasks-70.htm" />
-  <topic label="Replacing a resource with local history" href="tasks/tasks-87.htm" />
-  <topic label="Restoring deleted resources from local history" href="tasks/tasks-87b.htm" />
-  <topic label="Setting local history preferences" href="tasks/tasks-88.htm" />
-</topic>
-
-<anchor id="t_afterworking_local" />
-
-<topic label="Importing" href="tasks/tasks-53.xhtml" >
-  <topic label="Importing existing projects" href="tasks/tasks-importproject.htm" />
-  <topic label="Importing resources from the file system" href="tasks/tasks-55.htm" />
-  <topic label="Importing resources from an Archive file" href="tasks/tasks-55bg.htm" />
-</topic>
-
-<anchor id="t_afterimporting" />
-
-<topic label="Exporting" href="tasks/tasks-57.xhtml" >
-  <topic label="Exporting resources to the file system" href="tasks/tasks-59.htm" />
-  <topic label="Exporting resources to an Archive file" href="tasks/tasks-59ag.htm" />
-</topic>
-
-<anchor id="t_afterexporting" />
-
-<topic label="Building resources" href="tasks/tasks-73.htm" >
-  <topic label="Performing builds automatically" href="tasks/tasks-16.htm" />
-  <topic label="Performing builds manually" href="tasks/tasks-75.htm" />
-  <topic label="Saving resources automatically before a manual build" href="tasks/tasks-17.htm" />
-  <topic label="Changing build order" href="tasks/tasks-14.htm" />
-  <topic label="Running external tools" href="tasks/tasks-exttools-running.htm" />
-  <topic label="Running Ant buildfiles" href="tasks/tasks-ant-running.htm">
-    <topic label="Modifying the Ant classpath" href="tasks/tasks-ant-classpath.htm"/>
-    <topic label="Using a different version of Ant" href="tasks/tasks-ant-version.htm"/>
-    <topic label="Adding new Ant tasks and types" href="tasks/tasks-ant-addtasksandtypes.htm"/>
-  </topic>
-</topic>
-
-<anchor id="t_afterbuilding" />
-
-<!-- help topics -->
-<topic label="Using the help system" href="tasks/tasks-1g.htm" >
-  <topic label="Changing how help information is displayed" href="tasks/tchgbrws.htm" />
-  <topic label="Accessing context-sensitive help" href="tasks/tf1help.htm" />
-  <topic label="Accessing and navigating online help" href="tasks/taccess.htm" />
-  <topic label="Searching online help" href="tasks/tsearch.htm" />
-  <topic label="Setting help fonts and colors for accessibility" href="tasks/tfonts.xhtml"
-     filter="ws=win32"/>
-</topic>
-
-<anchor id="t_afterusing" />
-
-<!-- team topics -->
-<topic label="Working in the team environment with CVS" href="tasks/tasks-1h.htm" >
-  <topic label="Working with a CVS repository" href="tasks/tasks-1i.htm" >
-    <topic label="Creating a CVS repository location" href="tasks/tasks-92.htm" />
-	<topic label="Connecting and configuring CVS with SSH" href="tasks/tasks-cvs-ssh2.htm" />
-	<topic label="Password Management" href="tasks/tasks-cvs-passwords.htm" />
-    <topic label="Discarding a CVS repository location" href="tasks/tasks-94.htm" />
-    <topic label="Refreshing the CVS Repositories View" href="tasks/tasks-93.htm" />
-    <topic label="Discovering branch and version tags" href="tasks/tasks-110.htm" />
-    <topic label="Changing the properties of a CVS repository location" href="tasks/tasks-95.htm" />
-    <topic label="Changing the encoding of a CVS repository location" href="tasks/tasks-95a.htm" />
-    <topic label="Setting the content type of a file extension" href="tasks/tasks-team-1.htm" />
-  </topic>
-  <topic label="Working with projects shared with CVS" href="tasks/tasks-1j.htm" >
-      <topic label="Enabling the CVS resource decorations" href="tasks/tasks-107b.htm" />
-	  <topic label="Sharing a new project using CVS" href="tasks/tasks-117.htm" />
-	  <topic label="Project checked out with another CVS tool" href="tasks/tasks-117a.htm" />
-	  <topic label="Checking out a project from a CVS repository" href="tasks/tasks-96.htm" />
-	  <topic label="Checking out a module from a CVS repository" href="tasks/tasks-96a.htm" />
-	  <topic label="Checking out a folder into an existing project" href="tasks/tasks-96b.htm" />
-	  <topic label="Disconnecting a project from CVS" href="tasks/tasks-cvs-10.htm" />
-	  <topic label="Setting the CVS keyword substitution mode" href="tasks/tasks-cvs-11.htm" />
-	  <topic label="Filtering in the CVS Resource History view" href="tasks/tasks-cvs-16.htm" />
-	  <topic label="Changing the sharing of a project" href="tasks/tasks-117b.htm" />
-	  <topic label="Sharing your workspace setup using Project Sets" href="tasks/tasks-cvs-project-set.htm" />
-  </topic>
-  <topic label="Synchronizing with the repository" href="tasks/tasks-115.htm" >
-    <topic label="Updating" href="tasks/tasks-113.htm" />
-    <topic label="Committing" href="tasks/tasks-114.htm" />
-    <topic label="Version control life cycle: adding and ignoring resources" href="tasks/tasks-100d.htm" >
-      <topic label="Creating a global ignore pattern" href="tasks/tasks-100d1.htm" />
-      <topic label="Authoring the CVS .cvsignore file" href="tasks/tasks-100d2.htm" />
-      <topic label="Overriding or removing resource ignore patterns" href="tasks/tasks-100d1b.htm" />
-    </topic>
-    <topic label="Resolving conflicts" href="tasks/tasks-113b.htm" />
-    <topic label="Branching" href="tasks/tasks-100a.htm" />
-    <topic label="Merging from a branch" href="tasks/tasks-100b.htm" />
-    <topic label="Viewing a file's revision history" href="tasks/tasks-119.htm" />
-  </topic>
-  <topic label="Versioning" href="tasks/tasks-1k.htm" >
-    <topic label="Creating a version of a project" href="tasks/tasks-100.htm" />    
-    <topic label="Versioning projects in the repository" href="tasks/tasks-118.htm" />
-  </topic>
-  <topic label="Comparing resources with repository versions" href="tasks/tasks-101.htm" />
-  <topic label="Working with patches" href="tasks/tasks-68c.htm" />
-  <topic label="Replacing resources in the workbench" href="tasks/tasks-103.htm" />
-  <topic label="Finding out who's working on what: watch/edit" href="tasks/tasks-cvs-watch.htm" />
-  <topic label="Finding out who's to blame with Annotate" href="tasks/tasks-cvs-annotate.htm" />
-  <topic label="Quick Diff: Showing changes in a text editor" href="tasks/tasks-cvs-quickdiff.htm" />
-  <topic label="Changing CVS team settings" href="tasks/tasks-105.htm" />
-  <topic label="Restoring deleted files from the repository" href="tasks/tasks-105a.htm" />
-  <topic label="Reverting a branch to a previous version" href="tasks/tasks-105b.htm" />
-  <topic label="Moving version tags" href="tasks/tasks-105c.htm" />
-  <topic label="Running the CVS command-line client outside of Eclipse" href="tasks/task-team-cmdlineclient.htm" />
-</topic>
-
-<anchor id="t_afterworking_team" />
-
-
-<!-- install update topics -->
-<topic label="Updating features with the update manager" href="tasks/tasks-36.htm" >
-  <topic label="Inspecting the current configuration" href="tasks/tasks-33.htm" />
-  <topic label="Restoring a saved configuration" href="tasks/tasks-38.htm" />
-  <topic label="Installing new features with the update manager" href="tasks/tasks-34.htm" />
-  <topic label="Enable, disable, uninstall a feature" href="tasks/tasks-35.htm" />
-  <topic label="Update policy" href="tasks/tasks-37.htm" />
-  <topic label="Automatic update scheduler" href="tasks/tasks-37a.htm" />
-</topic>
-
-<anchor id="t_afterupdating" />
-
-</toc>

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/advanced_gc.jpg b/bundles/org.eclipse.platform.doc.user/whatsNew/images/advanced_gc.jpg
deleted file mode 100644
index cb83413..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/advanced_gc.jpg
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/ant-external-documentation.gif b/bundles/org.eclipse.platform.doc.user/whatsNew/images/ant-external-documentation.gif
deleted file mode 100644
index dfe08e8..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/ant-external-documentation.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/ant-hyperlink.gif b/bundles/org.eclipse.platform.doc.user/whatsNew/images/ant-hyperlink.gif
deleted file mode 100644
index f1b391a..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/ant-hyperlink.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/ant_dep_callstack.gif b/bundles/org.eclipse.platform.doc.user/whatsNew/images/ant_dep_callstack.gif
deleted file mode 100644
index 502c626..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/ant_dep_callstack.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/ant_folding.gif b/bundles/org.eclipse.platform.doc.user/whatsNew/images/ant_folding.gif
deleted file mode 100644
index 47d2e4a..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/ant_folding.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/attributes.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/attributes.png
deleted file mode 100644
index 3822304..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/attributes.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/bidi.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/bidi.png
deleted file mode 100644
index b7e1a15..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/bidi.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/book.css b/bundles/org.eclipse.platform.doc.user/whatsNew/images/book.css
deleted file mode 100644
index a4eedda..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/book.css
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/branching.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/branching.png
deleted file mode 100644
index c1a2ee6..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/branching.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/breakpoint_workingsets.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/breakpoint_workingsets.png
deleted file mode 100644
index e6806a0..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/breakpoint_workingsets.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/build_targets.gif b/bundles/org.eclipse.platform.doc.user/whatsNew/images/build_targets.gif
deleted file mode 100644
index 1e4b442..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/build_targets.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/capabilities.gif b/bundles/org.eclipse.platform.doc.user/whatsNew/images/capabilities.gif
deleted file mode 100644
index 85facc6..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/capabilities.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/changelog-obj.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/changelog-obj.png
deleted file mode 100644
index 3df9347..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/changelog-obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/colon-slash.gif b/bundles/org.eclipse.platform.doc.user/whatsNew/images/colon-slash.gif
deleted file mode 100644
index a5ebf66..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/colon-slash.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/commit-wizard.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/commit-wizard.png
deleted file mode 100644
index 7771c5e..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/commit-wizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/contenttypes.gif b/bundles/org.eclipse.platform.doc.user/whatsNew/images/contenttypes.gif
deleted file mode 100644
index 8805409..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/contenttypes.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/control.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/control.png
deleted file mode 100644
index f1f6668..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/control.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/cpy.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/cpy.png
deleted file mode 100644
index a0f8775..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/cpy.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/cvsfail.gif b/bundles/org.eclipse.platform.doc.user/whatsNew/images/cvsfail.gif
deleted file mode 100644
index a03d6a9..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/cvsfail.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/demo.gif b/bundles/org.eclipse.platform.doc.user/whatsNew/images/demo.gif
deleted file mode 100644
index 5c37070..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/demo.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/detachview1.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/detachview1.png
deleted file mode 100644
index a7d9f4d..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/detachview1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/detachview2.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/detachview2.png
deleted file mode 100644
index e1898fa..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/detachview2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/dynamic-help.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/dynamic-help.png
deleted file mode 100644
index ac98e79..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/dynamic-help.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/export-targz.gif b/bundles/org.eclipse.platform.doc.user/whatsNew/images/export-targz.gif
deleted file mode 100644
index 0a59d40..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/export-targz.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/file-types.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/file-types.png
deleted file mode 100644
index 0e5984d..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/file-types.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/gc-caps-joins.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/gc-caps-joins.png
deleted file mode 100644
index a88eea1..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/gc-caps-joins.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/help-view.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/help-view.png
deleted file mode 100644
index 74667a8..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/help-view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/hyperlinking.gif b/bundles/org.eclipse.platform.doc.user/whatsNew/images/hyperlinking.gif
deleted file mode 100644
index 43ad6a9..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/hyperlinking.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/importmultiple.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/importmultiple.png
deleted file mode 100644
index 522823d..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/importmultiple.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/importwiz.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/importwiz.png
deleted file mode 100644
index c520d63..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/importwiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/intro-launch-bar.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/intro-launch-bar.png
deleted file mode 100644
index e857fa5..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/intro-launch-bar.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/jard_plugins.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/jard_plugins.png
deleted file mode 100644
index 88c4afb..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/jard_plugins.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/keycompletions.gif b/bundles/org.eclipse.platform.doc.user/whatsNew/images/keycompletions.gif
deleted file mode 100644
index caea879..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/keycompletions.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/line-delimiter.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/line-delimiter.png
deleted file mode 100644
index 9c23ef8..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/line-delimiter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/linkwidget.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/linkwidget.png
deleted file mode 100644
index d5ec53e..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/linkwidget.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/mirrors.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/mirrors.png
deleted file mode 100644
index 4c25bc0..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/mirrors.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/moveable.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/moveable.png
deleted file mode 100644
index 2348c74..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/moveable.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/multi-line-search.gif b/bundles/org.eclipse.platform.doc.user/whatsNew/images/multi-line-search.gif
deleted file mode 100644
index c95cdc4..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/multi-line-search.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/new-plugin-rcp.gif b/bundles/org.eclipse.platform.doc.user/whatsNew/images/new-plugin-rcp.gif
deleted file mode 100644
index 90ee55c..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/new-plugin-rcp.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/occur.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/occur.png
deleted file mode 100644
index 936a830..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/occur.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/outgoing-commit-sets.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/outgoing-commit-sets.png
deleted file mode 100644
index 55fbe37..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/outgoing-commit-sets.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/perf-example.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/perf-example.png
deleted file mode 100644
index 632022e..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/perf-example.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/platform01.gif b/bundles/org.eclipse.platform.doc.user/whatsNew/images/platform01.gif
deleted file mode 100644
index d51c884..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/platform01.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/platform02.gif b/bundles/org.eclipse.platform.doc.user/whatsNew/images/platform02.gif
deleted file mode 100644
index f32de99..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/platform02.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/pref.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/pref.png
deleted file mode 100644
index 74e0408..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/pref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/preferences.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/preferences.png
deleted file mode 100644
index 88b7802..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/preferences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/rename.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/rename.png
deleted file mode 100644
index 3fc7dac..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/rename.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/select-required.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/select-required.png
deleted file mode 100644
index 00da2ab..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/select-required.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/shared-preferences.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/shared-preferences.png
deleted file mode 100644
index 44f3614..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/shared-preferences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/sites-import-export.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/sites-import-export.png
deleted file mode 100644
index 2060443..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/sites-import-export.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/spinner_float.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/spinner_float.png
deleted file mode 100644
index 1086d01..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/spinner_float.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/strike_underline.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/strike_underline.png
deleted file mode 100644
index 6897f37..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/strike_underline.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/swtlauncher.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/swtlauncher.png
deleted file mode 100644
index 31ab877..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/swtlauncher.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/tag-filtering.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/tag-filtering.png
deleted file mode 100644
index 29b436f..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/tag-filtering.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/team-decorators.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/team-decorators.png
deleted file mode 100644
index 1a1ca47..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/team-decorators.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/templates.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/templates.png
deleted file mode 100644
index 32eb799..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/templates.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/treetable.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/treetable.png
deleted file mode 100644
index f562b86..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/treetable.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/undo_history_size.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/undo_history_size.png
deleted file mode 100644
index 7ba8a52..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/undo_history_size.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/undosample.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/undosample.png
deleted file mode 100644
index 6826dc4..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/undosample.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/workspace.gif b/bundles/org.eclipse.platform.doc.user/whatsNew/images/workspace.gif
deleted file mode 100644
index 6382104..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/workspace.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/xpbuttons.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/xpbuttons.png
deleted file mode 100644
index ef6f927..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/xpbuttons.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/platform_whatsnew.html b/bundles/org.eclipse.platform.doc.user/whatsNew/platform_whatsnew.html
deleted file mode 100644
index f22dfc8..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/platform_whatsnew.html
+++ /dev/null

@@ -1,1019 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse Platform What's New in 3.1</title>
-</head>
-
-<body>
-
-<h2>What's New in 3.1</h2>
-<p>This document contains descriptions of some of the more interesting or
-significant changes made to the Eclipse Platform for the 3.1 release of
-Eclipse since 3.0. It is broken into several sections:</p>
-<ul>
-<li><a href="#Platform">Platform Changes</a></li>
-<li><a href="#SWT">SWT</a></li>
-<li><a href="#TeamCVS">Team/CVS</a></li>
-<li><a href="#Ant">Ant</a></li>
-<li><a href="#Debug">Debug</a></li>
-</ul>
-
-<!-- *************************************************** -->
-<a name="Platform"></a>
-<table cellpadding="10" cellspacing="0" width="600">
-  <colgroup>
-  <col width="20%" valign="top" align="right">
-  <col width="80%" valign="top" align="left">
-  </colgroup>
-  <tbody>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Significant performance enhancements</b></p></td>
-      <td width="70%" valign="top"> <p>Performance has been significantly enhanced
-      across the board versus the R3.0 release.</p><p>We have also added debugging
-      support that can continually monitor performance while the workbench
-      is running, and have made pervasive benchmarking tests
-      part of the standard test suites. The results of these tests are linked off of the download
-      page for each build. Here is an example of (part of) the output:</p>
-        <p><img src="images/perf-example.png" alt="Example performance graph"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Support for 
-          bi-directional text</b></p></td>
-      <td width="70%" valign="top"> <p>Support for bi-directional languages (BIDI), 
-          has been extended across the platform. Window layout orientation can 
-          be configured from the command line, and a suitable default orientation 
-          is inferred from the locale. Note that SWT fully supports BIDI on Windows 
-          only.</p>
-        <p><img src="images/bidi.png" alt="Screenshot of mirrored Eclipse perspective" ></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td valign="top" align="left"> <p align="right"><b>New undo/redo API</b></p></td>
-      <td valign="top"> <p>Applications can now access a platform undoable operation 
-          history using API in org.eclipse.core.commands.operations. IUndoableOperation 
-          defines the interface for operations that can be undone and redone. 
-          Views and editors can provide access to the undo and redo support by 
-          using the UndoActionHandler and RedoActionHandler provided in org.eclipse.ui.operations. 
-        </p>
-        <p><img src="images/undosample.png" ></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Filtering 
-          preferences and properties</b></p></td>
-      <td width="70%" valign="top"><p>The Preferences and Properties dialogs now 
-        have a field for filtering the pages displayed to just those that have 
-        names or keywords that match the specified prefix. The example below shows 
-        matches for the keyword &quot;tab&quot;.</p> <p><img src="images/preferences.png" alt="Screenshot of new preferences dialog" ></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Navigating 
-          preferences and properties</b></p></td>
-      <td width="70%" valign="top">General support for linking preference and 
-        property pages allows pages with related settings to refer to each other 
-        and provide quick access to the other page. Combined with web-style forward 
-        and backward navigation in the top right-hand corner, it is now much easier 
-        to work with a set of related preference pages. 
-        <p><img src="images/workspace.gif" alt="Screenshot showing preference linking" ></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Importing 
-          multiple projects</b></p></td>
-      <td width="70%" valign="top">The <b>Import &gt; Existing Project into Workspace</b> 
-        command now allows you to search for all projects under a specified location 
-        and import any projects found in one go. You can now also import existing 
-        projects from TAR and ZIP archive files. 
-        <p><img src="images/importmultiple.png" ></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Import and export 
-          to tar.gz format</b></p></td>
-      <td width="70%" valign="top">The <b>Import</b> and <b>Export &gt; Zip File</b> 
-        wizards now support the tar.gz compressed archive file format popular 
-        on UNIX systems. The wizards have been renamed <b>Import</b> and <b>Export 
-        &gt; Archive File</b> accordingly. 
-        <p><img src="images/export-targz.gif" alt="Screenshot showing export to tar.gz" ></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Editor lookup 
-          based on content type</b></p></td>
-      <td width="70%" valign="top">When determining the appropriate editor to 
-        open for a given file, the file's content type is now taken into account. 
-        Editors may now advertise that they are capable of working on certain 
-        content types as well as their traditional file name and extensions. </td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>File names 
-          containing colon and backslash characters</b></p></td>
-      <td width="70%" valign="top">It was previously not possible to create resources 
-        in Eclipse with names containing colon (':') and backslash ('\') characters. 
-        Such characters are now permitted when running Eclipse on operating systems 
-        such as Linux that allow such characters in file names. Care must be taken 
-        when file names must be meaningful across multiple operating environments; 
-        Windows, in particular, does not allow either of these characters in file 
-        names. 
-        <p><img src="images/colon-slash.gif" alt="Screenshot showing :\ in filename" ></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Support for 
-          executable and archive attributes</b></p></td>
-      <td width="70%" valign="top">You can now view and change OS-specific file 
-        attributes such as the executable bit (Unix-based) and the archive bit 
-        (Windows). CVS will now preserve these attributes when you check files 
-        out of, or commit files to, a repository, and import wizards will preserve 
-        the attributes of files and directories that are imported from a local 
-        file system. 
-        <p><img src="images/attributes.png" ></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="30%"> <p align="right"><b>Line delimiter 
-          support</b></p></td>
-      <td style="vertical-align: top"> <p>You can now set the line delimiter that 
-          is used when creating new text files. You can provide a single setting 
-          for the entire workspace, or for a given project. In addition, line 
-          delimiter conversions can now be applied to projects, folders, and files, 
-          not just to the contents of a single editor.</p>
-        <p><img src="images/line-delimiter.png" alt="Screenshot of default delimiter dialog"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Single JAR 
-          plug-ins</b></p></td>
-      <td width="70%" valign="top"> <p>Eclipse now provides the ability to ship 
-          a plug-in packaged as a single JAR file rather than as a directory of 
-          files. Think of this as folding the plug-in metadata (plugin.xml etc.) 
-          into its code JAR. This move has a number of benefits ranging from smaller 
-          footprint to easier/faster install to fitting better with the standard 
-          Java notion of JARs.</p>
-        <p>In Eclipse 3.1 most plug-ins are shipped as JARs in all distributions. 
-          This format is the new best practice for Eclipse packaging.</p>
-        <p><img src="images/jard_plugins.png" alt="Screenshot showing JAR'ed plugins" ></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td valign="top" align="left" width="30%"> <p align="right"><b>Improved 
-          editor context menus</b></p></td>
-      <td width="70%" valign="top" align="left"> Many commands that were only 
-        available in other views are now right at your finger tips in the editor 
-        context menu. For example, you can commit files to CVS or run and debug 
-        Java programs and Ant builds from the editor's context menu. 
-        <p><img src="images/platform01.gif" alt="Screenshot showing team contributions on Editor menu" title="Team contributions on Editor menu"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>View all 
-          keyboard shortcuts</b></p></td>
-      <td width="70%" valign="top">While working with your favorite editors and 
-        views in Eclipse, just press Ctrl+Shift+L to see a full list of the currently 
-        available key bindings. This is a great way to learn what is available 
-        in the UI and to speed up your productivity by learning more key bindings. 
-        This information is also available in the improved <b>General &gt; Keys</b> 
-        preference page. 
-        <p><img border="0" src="images/keycompletions.gif" alt="Screenshot of keybindings" ></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td valign="top" align="left" width="30%"> <p align="right"><b>Detached 
-          view behavior</b></p></td>
-      <td width="70%" valign="top" align="left"> <p>Eclipse 3.1 (on platforms 
-          that support it) now has improved detached view support. It is now much 
-          easier to place them wherever desired, including over another Eclipse 
-          window. </p>
-        <p>First check &quot;Detached&quot; from the menu or drag the view tab 
-          out to create.</p>
-        <p><img src="images/detachview1.png" ></p>
-        <p>Then place where you choose, drag and drop other views into the same 
-          window. Use the menu or drag the view tab to put it back in the 
-          Workbench window.</p>
-        <p><img src="images/detachview2.png" > </p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td valign="top" align="left"> <p align="right"><b>Perspective button dragging</b></p></td>
-      <td valign="top" align="left"> Eclipse 3.1 now supports re-ordering of perspective 
-        buttons in the Perspective switcher, as well as the ability to open a 
-        new window on a perspective by dragging that perspective outside the perspective 
-        switcher. 
-        <p><img src="images/platform02.gif" alt="Screenshot showing perspective button dragging" title="Perspective button dragging"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td valign="top" align="left" width="30%"> <p align="right"><b>Animations</b></p></td>
-      <td width="70%" valign="top" align="left"> The workbench supports more animations 
-        to help users understand where UI elements are going. Creating a fast 
-        view for example is now animated. This can be enabled/disabled via a preference 
-        in <b>General > Appearance > Enable animations</b>. </td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td valign="top" align="left"> <div align="right"> <b>Improved error dialog 
-          for background operations</b> </div></td>
-      <td valign="top"> <p>The error dialog for displaying background operations 
-          is now more consistent with the error dialogs displayed elsewhere in 
-          the workbench. Extra buttons are shown when additional information is 
-          available, such as this dialog resulting from a failed CVS operation:</p> 
-        <p><img src="images/cvsfail.gif" alt="Screenshot showing CVS error dialog"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" align="left" valign="top"> <p align="right"><b>Import and 
-          export of preferences</b></p></td>
-      <td width="70%" valign="top"> <p>The Import/Export wizards now support preferences. 
-          You can choose to import or export all changed settings, or only specific 
-          preferences where supported. </p>
-        <p><img src="images/importwiz.png"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Content type 
-          preference page</b></p></td>
-      <td width="70%" valign="top">A new preference page to edit content types 
-        and their associated file names and character sets has been added under 
-        the General/Editors preference page. 
-        <p><img src="images/contenttypes.gif" alt="Screenshot of content type dialog" ></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>New capabilities 
-          preference page</b></p></td>
-      <td width="70%" valign="top">A new capabilities preference page has been 
-        introduced to simplify management of capabilities in large Eclipse-based 
-        products. 
-        <p><img src="images/capabilities.gif" alt="Screenshot of capabilities preference page" ></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="30%"> <p align="right"><b>Word completion</b></p></td>
-      <td valign="top" width="70%">In any text editor you can complete a 
-        prefix to a word occurring in all currently open editors or buffers. The 
-        default key binding for word completion is <b>Alt+/</b> (<b>Ctrl+.</b> on the Mac).</td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="30%"> <p align="right"><b>Open untitled 
-          files</b></p></td>
-      <td width="70%" valign="top">A text editor can be opened without creating 
-        a file first. Simply go to <b>File &gt; New &gt; Untitled Text File</b>.</td> </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="30%"> <p align="right"><b>Shared editor 
-          preferences</b></p></td>
-      <td valign="top" width="70%">The <b>General &gt; Editors &gt; Text Editors</b> 
-        preference page contains settings for all text editors. Preferences previously 
-        duplicated on the Text and Java editor pages have been merged, and other 
-        text-based editors can also be expected to honor those settings where 
-        applicable in the future. 
-        <p><img src="images/shared-preferences.png"  alt="Screenshot of shared editor preferences"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="30%"> <p align="right"><b>Preference 
-          for undo history size</b></p></td>
-      <td valign="top" width="70%">The undo history size can be set for text 
-        editors on the <b>General &gt; Editors &gt; Text Editors</b> preference 
-        page: 
-        <p><img alt="Picture of undo history size preference" title="Undo history size preference" src="images/undo_history_size.png"></p></td>
-    </tr>
-
-  <tr>
-    <td colspan="2">
-      <hr>
-    </td>
-  </tr>
-  <tr>
-    <td width="30%" valign="top" align="left">
-      <p align="right"><b>Hyperlink support</b></p>
-    </td>
-    <td width="70%" valign="top">Hyperlink support, which was restricted to
-      the Java editor, has been generalized and moved down to Platform Text.
-      General hyperlinking preferences are available on the <b>General &gt;
-      Editors &gt; All Text Editors</b> preference page, and simple URL
-      hyperlinking now works in the standard Text editor:
-      <p><img title="Hyperlinking in Text editor" alt="Picture of hyperlinking in Text editor" src="images/hyperlinking.gif"></p>
-      
-      <p>The Web Browser support is used to show the link, see <b>General &gt; Web Browser</b> preference page for details.</p>
-
-      <p>All <tt>SourceViewer</tt>s that are configured with a <tt>SourceViewerConfiguration</tt>
-      automatically get URL hyperlinking.</p>
-    </td>
-  </tr>
-     <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-  <tr>
-    <td align="left" valign="top" width="30%"><p align="right"><b>Undoing first 
-        change clears dirty indicator</b></p></td>
-    
-    <td valign="top" width="70%"> The dirty indicator (*) in the editor tab 
-      goes away if the initial change is undone.</td>
-  </tr>
-     <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Multi-line 
-          text search and replace</b></p></td>
-      <td valign="top">Regular expression patterns used in text searches will 
-        match text straddling lines. 
-        <p><img alt="Mutli line search" src="images/multi-line-search.gif" ></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Welcome launch 
-          bar</b></p></td>
-      <td width="70%" valign="top">When the 'Go to the Workbench' link is selected 
-        in Eclipse SDK welcome, the entire Welcome page is collapsed into a new 
-        Welcome launch bar which appears in the lower left Workbench window trim area 
-        by default. The Welcome launch bar allows new users to quickly restore 
-        the last Welcome page, or jump to one of the main pages using the shortcuts. 
-        <p>While the platform controls the basic behavior and the 'Restore' button, 
-          background and foreground color as well as the shortcuts are contributed 
-          via the welcome extension. See the plug-in manifest for the org.eclipse.platform 
-          for an example of a Welcome launch bar definition.</p>
-        <p align="center"><img border="0" src="images/intro-launch-bar.png" alt="Screenshot of Welcome launch bar"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>New Help 
-          view</b></p></td>
-      <td width="70%" valign="top">Help has been brought closer to where you work 
-        with the introduction of the Help view. It contains various pages that 
-        provide assistance when you need it. If you press F1, the view will open 
-        with the topics related to what you are working on at the moment. You 
-        can also switch to All Topics and see what else is there in the local 
-        help. The new documentation search spanning local help, remote InfoCenters, 
-        Eclipse.org, and the web is now directly accessible from the Help menu 
-        (via <b>Help &gt; Search Help</b>). 
-        <p align="center"><img border="0" src="images/help-view.png" alt="Screenshot of new help view"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Dynamic Help 
-          now available for all dialogs</b></p></td>
-      <td width="70%" valign="top">The new dynamic help that was added to the 
-        workbench window in M5 is now available in dialogs as well. When triggered 
-        by the system-specific help shortcut (F1 on Windows, Shift-F1 on Linux 
-        GTK etc.), a shell opens aligned with the dialog showing the related help 
-        information. Multi-page dialogs like wizards, preferences, launch configurations, 
-        searches, etc. trigger the help pane to update its content as you flip 
-        from page to page. 
-        <p><img border="0" src="images/dynamic-help.png" alt="Screenshot showing dynamic help"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Downloading 
-          of updates in background</b></p></td>
-      <td width="70%" valign="top">The Update Manager's install wizard (<b>Help 
-        &gt; Software Updates &gt; Find and Install</b>) now allows downloading 
-        of plug-ins in the background. This way you can continue working while 
-        plug-ins are being downloaded. Once everything is downloaded, the install 
-        phase (unzipping the jar files and moving them to the installation directory) 
-        is still controlled by a modal dialog.</td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Import/export 
-          update sites bookmarks</b></p></td>
-      <td width="70%" valign="top">You can now export your update site bookmarks 
-        to a file. This makes it easy to migrate your bookmarks from build to 
-        build, share them across multiple Eclipse installs, or give them to other 
-        developers. 
-        <p><img border="0" src="images/sites-import-export.png" alt="Screenshot showing Import/Export buttons"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Update site 
-          mirrors</b></p></td>
-      <td width="70%" valign="top">Update sites can now specify a list of servers 
-        that mirror their content. As features are looked up on a mirrored update 
-        site, you're prompted to pick any of the available mirrors. 
-        <p><img border="0" src="images/mirrors.png" alt="Screenshot showing mirrors"></p>
-        <p>(See bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=69008">69008</a> 
-          for details on how to specify mirrors in the site.xml.)</p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Improved 
-          handling of feature dependencies</b></p></td>
-      <td width="70%" valign="top">When installing a feature that depends on other 
-        features, the install wizard lets you automatically include all available 
-        dependencies. Press the <b>Select Required</b> button to include all pre-requisites 
-        of the selected features, and then <b>Install All</b> to complete the 
-        install. 
-        <p> <img border="0" src="images/select-required.png" alt="Screenshot of Select Required button"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>RCP delta 
-          pack</b></p></td>
-      <td width="70%" valign="top">A new RCP delta pack is now available (it's 
-        listed under the RCP SDK section of the download page). It contains all 
-        the OS-specific fragments of the RCP plug-ins, and is aimed at RCP developers 
-        that need to create a family of downloads of their application for different 
-        OSes. It beats having to download all the OS-specific RCP binary drops.</td>
-    </tr>
-    <!-- *********************** SWT *********************** -->
-    <tr> 
-      <td colspan="2"><hr> <a name="SWT"></a></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="left"><b>SWT Browser 
-          widget improvements</b></p></td>
-      <td width="70%" valign="top"> <p>Many improvements have been made to the 
-          SWT Browser widget. Highlights include:</p> 
-        <ul>
-          <li>On Windows, new windows can now be opened in a stand-alone Internet 
-            Explorer browser.</li>
-          <li>On Linux, the browser now works with Mozilla 1.7 GTK2 as well as 
-            with Mozilla 1.4 GTK2 and above.</li>
-          <li>A new execute method passes an arbitrary string of JavaScript commands 
-            to be directly evaluated by the underlying native JavaScript engine 
-            (Internet Explorer on Windows, Mozilla on Linux, Safari on the Mac) 
-            in the context of the HTML document that is currently loaded in the 
-            browser widget.</li>
-        </ul>
-        <p><img border="0" src="images/demo.gif" alt="Screenshot of embedded browser view"></p>
-        <p>The new Browser Demo example (shown above) illustrates how to integrate 
-          HTML content with the SWT Browser widget into an application. The easy 
-          way to get the SWT samples is via the new welcome page.</p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>New spinner 
-          widget</b></p></td>
-      <td width="70%" valign="top" align="left">SWT now provides a spinner widget 
-        on all window systems. See <code>org.eclipse.swt.widgets.Spinner</code>. 
-        <p><img border="0" src="images/spinner_float.png" alt="Screenshot of SWT spinner widgets"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>GC.setLineCap, 
-          GC.setLineJoin</b></p></td>
-      <td width="70%" valign="top" align="left"><code>GC.setLineCap</code> lets 
-        you control how the end of a line should be drawn (flat, round, or square 
-        styles as shown in the top line of the figure below). <code>GC.setLineJoin</code> 
-        allows you to control how one line attaches to another one in methods 
-        like <code>GC.drawPolylines</code> or <code>GC.drawPolygon</code>. Join 
-        styles are bevel, round, and miter (bottom row) 
-        <p><img border="0" src="images/gc-caps-joins.png" alt="Screenshot showing new SWT line styles" ></p>
-        <p>See the SWT snippet <a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet168.java?rev=HEAD&amp;content-type=text/vnd.viewcvs-markup">for 
-          drawing lines with different cap and join styles</a>.</p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Mouse wheel 
-          events</b></p></td>
-      <td width="70%" valign="top" align="left">SWT now provides events when the 
-        user spins the mouse wheel. Note that the default behavior of scrolling 
-        the scroll bar continues to work as before. See <code>SWT.MouseWheel</code>.</td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Improved 
-          layout support</b></p></td>
-      <td width="70%" valign="top" align="left">There are new methods on <code>Composite</code> 
-        and <code>Layout</code> to allow applications to improve layout performance 
-        and to force the laying out of all children even when there is an intermediate 
-        parent that does not resize. 
-        <ul>
-          <li><code>Composite.layout(Control[])</code></li>
-          <li><code>Composite.layout(boolean, boolean)</code></li>
-          <li><code>Composite.setLayoutDeferred(boolean)</code></li>
-          <li><code>Layout.flushCache(Control)</code></li>
-        </ul></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Remove widgets 
-          from Layout</b></p></td>
-      <td width="70%" valign="top" align="left"> <p><code>RowData</code> and <code>GridData</code> 
-          have a new <code>exclude</code> attribute for removing the associated 
-          widget from the layout management. Previously, applications had to dispose 
-          and recreate widgets to achieve this effect.</p>
-        <p>For more details, see the example <a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet175.java?rev=HEAD&amp;content-type=text/vnd.viewcvs-markup">snippet</a>.</p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>SWT for Solaris-GTK+</b></p></td>
-      <td width="70%" valign="top" align="left">Solaris-GTK has joined the lineup 
-        of supported configurations for which SWT and Eclipse are routinely built.</td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Selection 
-          clipboard</b></p></td>
-      <td width="70%" valign="top" align="left">Unix users on both GTK and Motif 
-        can now select text and paste it with the middle mouse button.</td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Native tree 
-          with columns</b></p></td>
-      <td width="70%" valign="top" align="left"> <p>The SWT <code>Tree</code> 
-          widget can now display multiple columns. New API in Tree, TreeItem, 
-          and TreeColumn provides the same support for columns as Table. This 
-          obsoletes the <code>TableTree</code> widget, which is now deprecated.</p> 
-        <p><img border="0" src="images/treetable.png" alt="Screenshot of multi-column Tree"></p>
-        <p>For more details see the example <a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet170.java?rev=HEAD&amp;content-type=text/vnd.viewcvs-markup">snippet</a>.</p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Reorderable 
-          table columns</b></p></td>
-      <td width="70%" valign="top" align="left"> <p>The display order of columns 
-          in a table can be changed by dragging the column header (as well as 
-          being set programmatically).</p> 
-        <p><img border="0" src="images/moveable.png" alt="Screenshot of Table column being moved"></p>
-        <p>For more details see the example <a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet181.java?rev=HEAD&amp;content-type=text/vnd.viewcvs-markup">snippet</a>.</p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-    <td width="30%" valign="top" align="left"> <p align="right"><b> 
-          Standalone SWT download is now an Eclipse project</b></p></td>
-      <td width="70%" valign="top" align="left"> <p>For developers of standalone
-      SWT applications, the SWT component is available as a separate download.  For
-      Eclipse 3.1, the SWT download can now be easily imported into your workspace as a project.</p>
-      <ol><li>Download SWT for standalone applications. A standalone version of SWT is 
-         available on the same download page as the Eclipse SDK. Look for the section 
-         titled SWT Binary and Source. Do not extract the archive file, just save it to 
-         disk.</li>
-         <li>Select <b>Import...</b> from the <b>File</b> menu.</li>
-         <li>Select <b>Existing Projects into Workspace</b> and click on the <b>Next</b> button.</li>
-         <li>Select <b>Select archive file:</b> and use the <b>Browse</b> button to locate the SWT 
-         standalone archive you have previously downloaded.</li>
-         <li>Click on the <b>Finish</b> button.</li></ol>
-      <p>The org.eclipse.swt project you have imported defines the location of the native libraries
-      so you can run your application with the standard Java or JUnit launchers.</p>
-      </td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-    <td width="30%" valign="top" align="left"> <p align="right"><b>Starting 
-          SWT standalone applications using PDE</b></p></td>
-      <td width="70%" valign="top" align="left"> <p>In 3.1, the core Eclipse plug-ins,
-      including SWT, are packaged as single JAR files rather than as a directory of files.
-      The SWT plug-in JAR now contains everything including the native libraries.</p>
-      <p>In order to run a standalone SWT application, the native libraries must be placed 
-      on the java library path.  If you use the SWT Binary and Source download this is resolved for you 
-      but sometimes it is useful to build against the SWT plug-in from the Eclipe SDK.
-      In Eclipse 3.0, standalone SWT developers added the native libraries using -Djava.library.path.  
-      In Eclipse 3.1, since the native libraries are inside a JAR, developers cannot 
-      easily locate the libraries.</p>
-      <p>To run and debug your SWT application using the SWT plug-in from
-      Eclipse, you can use the SWT application launcher to locate the native libraries. A shortcut to the 
-      launcher is available in the context menu of your Java class via 
-      <b>Run As &gt; SWT Application</b>.</p>
-        <p><img border="0" src="images/swtlauncher.png" alt="Screenshot of SWT application launching" ></p>
-      <p>Please note that the SWT application launcher may be unnecessary in future releases.</p>
-      </td>
-    </tr>
-    <tr>
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Advanced 
-          graphics</b></p></td>
-      <td width="70%" valign="top" align="left"> <p>New API has been added for 
-          advanced graphics operations such as path for curves and lines, alpha 
-          blending and transformations. This new API requires the <a href="http://cairographics.org/introduction" target="_blank">Cairo 
-          Vector engine</a> on GTK and Motif, and <a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/gdicpp/GDIPlus/GDIPlus.asp" target="_blank">GDI+</a> 
-          on Windows.</p> 
-        <p><img border="0" src="images/advanced_gc.jpg" alt="Screenshot showing advanced GC features in use" ></p>
-        <p>For more details see the example <a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet10.java?rev=HEAD&amp;content-type=text/vnd.viewcvs-markup">snippet</a>.</p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Windows XP 
-          look and feel for Buttons</b></p></td>
-      <td width="70%" valign="top" align="left"> <p>Under Windows XP, buttons 
-          with images now show the expected look and feel for the current skin. </p>
-        <p><img border="0" src="images/xpbuttons.png" alt="Screenshot of image buttons on XP"></p>
-        <p>For more details on Windows XP skins, see the <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-swt-home/faq.html#xpthemes">SWT 
-          FAQ</a>.</p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>New Link 
-          widget</b></p></td>
-      <td width="70%" valign="top" align="left"> <p>The new <code>Link</code> 
-          widget displays text containing hyperlinks.</p>
-        <p><img border="0" src="images/linkwidget.png" alt="Screenshot of new link widget"></p>
-        <p>For more details, see the example <a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet183.java?rev=HEAD&amp;content-type=text/vnd.viewcvs-markup">snippet</a>.</p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Strike through 
-          and underline in StyledText</b></p></td>
-      <td width="70%" valign="top" align="left"> <p>Text can be underlined or 
-          a strike can be drawn through it with the new <code>StyleRange.underline</code> 
-          and <code>StyleRange.strikeout</code> fields.</p>
-        <p><img border="0" src="images/strike_underline.png" alt="Screenshot showing new SWT text styles"></p>
-        <p>For more details see the example <a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet189.java?rev=HEAD&amp;content-type=text/vnd.viewcvs-markup">snippet</a>.</p></td>
-    </tr>
-    <!-- *************************************************** -->
-    <tr> 
-      <td colspan="2"><hr> <a name="TeamCVS"></a></td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="30%"> <p align="right"><b>CVS outgoing 
-          change sets<br>
-          </b></p></td>
-      <td valign="top" width="70%">Outgoing change sets allow you to organize 
-        outgoing changes into logical groups before they are committed. To enable 
-        outgoing change sets, put the Synchronize view into Outgoing mode, click 
-        on the change set button <img alt src="images/changelog-obj.png"> in the 
-        Synchronize View, then select an outgoing change and choose <b>Add To 
-        &gt; New Change Set...</b> from the context menu. You can also appoint 
-        a change set as the default and have all subsequent outgoing changes added 
-        to that set automatically. Commands on the context menu allow outgoing 
-        changes to be moved between change sets. When the change set is committed 
-        to the CVS repository, the comment associated with the change set is used 
-        as the CVS commit comment. 
-        <p><img src="images/outgoing-commit-sets.png" alt="Screenshot of outgoing change sets"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="30%"> <p align="right"><b>Colorful 
-          CVS label decorations<br>
-          </b></p></td>
-      <td valign="top" width="70%">CVS label decorations can be configured to 
-        use color and font to highlight file states. You can enable color and 
-        font decorations for CVS on the <b>Team &gt; CVS &gt; Label decorations</b> 
-        preference page and configure them for outgoing changes and for ignored 
-        files via the <b>General &gt; Colors and Fonts &gt; CVS</b> preference 
-        page. 
-        <p><img src="images/team-decorators.png" alt="Screenshot of colored CVS label decorations"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td valign="top" align="left"> <div align="center"> <strong>Support for 
-          CVSNT</strong> </div></td>
-      <td valign="top">Thanks to the efforts of the CVSNT developers, the Eclipse 
-        CVS client can now supports CVSNT. CVSNT version greater than 2.0.58b 
-        have been tested with Eclipse 3.1.</td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>CVS commit 
-          review</b></p></td>
-      <td width="70%" valign="top">The commit dialog now includes a list of the 
-        files that are being committed. This makes it easy to browse the files 
-        while writing the commit comment, and to hold back certain files by removing 
-        them from the list. It's especially useful when committing directly from 
-        the Package Explorer or Navigator view. 
-        <p><img src="images/commit-wizard.png" alt="Screenshot of commit review"></p>
-        <p>There are also CVS preferences (<b>Team &gt; CVS</b>) for determining 
-          whether commit comments are mandatory and for specifying the maximum 
-          number of files that should be displayed when committing.</p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>CVS improved 
-          file type support</b></p></td>
-      <td width="70%" valign="top">CVS now prompts whenever a file with an unknown 
-        file type is about to be committed. This allows you to explicitly configure 
-        a file type instead of CVS picking binary as the default. Also, file type 
-        decisions can now be based on the file name alone (e.g. Makefile), not 
-        just the file extension. 
-        <p><img src="images/file-types.png" alt="Screenshot of file type support"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>CVS branch 
-          and merge</b></p></td>
-      <td width="70%" valign="top">The CVS branch wizard now lets you use content 
-        assist to pick a branch from a project already branched in your workspace. 
-        <p><img src="images/branching.png" alt="Screenshot of branching"></p>
-        <p>When merging you can simply specify the end tag and the wizard will 
-          automatically find the appropriate start tag. If a start tag is not 
-          available, you can still merge without seeing a preview in the Synchronize 
-          view.</p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>CVS filtering 
-          tags</b></p></td>
-      <td width="70%" valign="top">The tag selection dialog used by the CVS replace 
-        and compare commands to select a branch or version now shows matching 
-        tags live as you type. 
-        <p><img src="images/tag-filtering.png" alt="Screenshot of tag filtering"></p></td>
-    </tr>
-    <!-- *************************************************** -->
-    <tr> 
-      <td colspan="2"><hr> <a name="Ant"></a></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Ant debugger</b></p></td>
-      <td width="70%" valign="top">The new Ant debugger helps you debug the execution 
-        of your Ant buildfiles. It includes the standard debugger features like 
-        breakpoints, stepping, dependency call stack, and run-to-line support. 
-        <p><img src="images/ant_dep_callstack.gif" title="Debug view" alt="Ant dependency call stack" ></p>
-        The presentation of Ant properties are also grouped in the Variables view 
-        for your convenience: 
-        <ul>
-          <li>System: Ant properties set from the System for the the build</li>
-          <li>User: properties such as those set using the -D option</li>
-          <li>Runtime: all properties set during the execution of the build</li>
-        </ul></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Folding in 
-          the<br>
-          Ant Editor</b></p></td>
-      <td width="70%" valign="top"> The Ant editor now supports folding of build 
-        file regions. Hovering over a folded Ant element lets you peek at the 
-        hidden code. You can quickly control folding presentation of a buildfile 
-        from the editor ruler menu. 
-        <p><img src="images/ant_folding.gif" alt="Screenshot of code folding in the Ant editor" title="Ant Code Folding" > </p>
-      </td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Rename in 
-          File for the Ant editor</b></p></td>
-      <td width="70%" valign="top"> <p>You can now rename occurrences of properties 
-          and targets within the same buildfile within the Ant editor. To activate 
-          use the editor context menu or the Alt-Shift-R keyboard shortcut when 
-          the cursor is located within the occurrence to rename.</p>
-        <p><img src="images/rename.png" alt="Screenshot showing rename in Ant editor"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Mark Occurrences 
-          in the Ant editor</b></p></td>
-      <td width="70%" valign="top"> <p>You can now enable the Ant editor to mark 
-          occurrences of properties and targets. Mark occurrences is controlled 
-          via the Ant editor preferences and editor toolbar action.</p>
-        <p><img src="images/pref.png" alt="Screenshot showing Ant mark occurrences preference" ></p>
-        <p><img src="images/occur.png" alt="Screenshot of highlighted occurrences" ></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Hyperlink 
-          navigation in Ant editor</b></p></td>
-      <td width="70%" valign="top"> <p>The Ant Editor supports hyperlink navigation 
-          using the Ctrl key modifier. The key modifier can be changed from the 
-          <b>Ant &gt; Editor &gt; Navigation</b> preference page.</p> 
-        <p><img src="images/ant-hyperlink.gif" title="Ant Hyperlink Support" alt="Ant hyperlink support"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Ant editor 
-          selected elements only</b></p></td>
-      <td width="70%" valign="top">The Ant editor can now be scoped to show only 
-        the selected source element in a buildfile. As with other editors, it 
-        is hooked up to the <b>Show source of selected elements only</b> toggle 
-        button in the Eclipse tool bar.</td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Improved 
-          Ant navigation</b></p></td>
-      <td width="70%" valign="top">In the Ant editor, <b>Navigate &gt; Open declaration</b> 
-        (F3) will now navigate you to the referenced target or property.</td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Errors now 
-          show in external Ant buildfiles</b></p></td>
-      <td width="70%" valign="top">Error and warning annotations now show even 
-        for Ant buildfiles that are opened using <b>File &gt; Open External File...</b></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Ant manual 
-          at your fingertips</b></p></td>
-      <td width="70%" valign="top"> <p>In the Ant editor, place your cursor on 
-          the name of an Ant task, type, etc. and press <b>Shift+F2</b> to open 
-          a browser on the relevant page in the Ant manual.</p> 
-        <p><img src="images/ant-external-documentation.gif" title="Ant External Documentation" alt="Ant external documentation" ></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Ant target 
-          per build kind</b></p></td>
-      <td width="70%" valign="top"> <p>The Targets tab for an Ant builder allows 
-          you to specify the target(s) that should be executed for each build 
-          kind. This includes the target to execute when you invoke a &quot;Clean&quot;.</p> 
-        <p><img src="images/build_targets.gif" title="Builder properties dialog" alt="Targets tab" ></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>More control 
-          over error reporting in the Ant editor</b></p></td>
-      <td width="70%" valign="top"> <p>You can now set the Ant editor to ignore 
-          all buildfile problems. As well you can specify specific buildfile names 
-          that the editor should not report problems for. Both settings are controlled 
-          using the Ant editor preferences for Problems.</p>
-        <p><img src="images/control.png" alt="Screenshot of Ant error reporting preferences" ></p></td>
-    </tr>
-    <!-- *************************************************** -->
-    <tr> 
-      <td colspan="2"><hr> <a name="Debug"></a></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Console EOF</b></p></td>
-      <td width="70%" valign="top">In the Console view you can signal end-of-file 
-        to a program waiting for input by pressing <b>Ctrl+Z</b> on Windows (<b>Ctrl+D</b> 
-        on Linux).</td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Console encoding</b></p></td>
-      <td width="70%" valign="top">The console can be configured to display output 
-        using a character encoding different from the default encoding. To set 
-        the console encoding for an application, use the <b>Console Encoding</b> 
-        settings on the Common tab of a launch configuration.</td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Capturing 
-          program output</b></p></td>
-      <td width="70%" valign="top"> <p>A program's output can now be captured 
-          in a file in addition to being written to the console. The behavior 
-          is controlled by settings found on the <b>Common</b> tab of launch configurations.</p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Multiple 
-          console views</b></p></td>
-      <td width="70%" valign="top"> <p>If you find you need to see multiple consoles 
-          at once, you can now open additional Console views via the <b>New Console 
-          View</b> command found on the <b>Open Console</b> drop-down menu in 
-          the Console view.</p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-    <tr> 
-      <td width="30%" valign="top" align="left"> <p align="right"><b>Breakpoint 
-          organization</b></p></td>
-      <td width="70%" valign="top"> <p>The Breakpoints view allows breakpoints 
-          to be grouped by type, project, file, or working sets, and supports 
-          nested groupings. You can use breakpoint working sets to group breakpoints 
-          into problem-specific sets that can be quickly enabled and disabled 
-          as a whole. Newly-created breakpoints are automatically placed into 
-          the default breakpoint working set (displayed in bold). You can copy 
-          and paste and drag and drop breakpoints between breakpoint working sets, 
-          and a breakpoint can be placed in more than one breakpoint working set.</p> 
-        <p><img src="images/breakpoint_workingsets.png" title="Breakpoints view" alt="Breakpoints view showing working sets"></p></td>
-    </tr>
-    <tr> 
-      <td colspan="2"><hr></td>
-    </tr>
-  </tbody>
-</table>
-
-<!-- ****************** END OF N&N TABLE ****************** -->
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/workbench.png b/bundles/org.eclipse.platform.doc.user/workbench.png
deleted file mode 100644
index c3f7d3f..0000000
--- a/bundles/org.eclipse.platform.doc.user/workbench.png
+++ /dev/null
Binary files differ