Skip to main content
diff options
authorDani Megert2006-01-09 10:36:07 +0000
committerDani Megert2006-01-09 10:36:07 +0000
commit930615297b5451f8e2bd9f77c966098b917a0d19 (patch)
treecbc31f55a78713ee03b91e52d2b0b34725e57243 /org.eclipse.core.filebuffers/schema
parent5740ec31811066e91e098aef1975e27d5a0aec86 (diff)
Added space
Diffstat (limited to 'org.eclipse.core.filebuffers/schema')
1 files changed, 1 insertions, 1 deletions
diff --git a/org.eclipse.core.filebuffers/schema/documentCreation.exsd b/org.eclipse.core.filebuffers/schema/documentCreation.exsd
index 9b0316211..844b2dba5 100644
--- a/org.eclipse.core.filebuffers/schema/documentCreation.exsd
+++ b/org.eclipse.core.filebuffers/schema/documentCreation.exsd
@@ -9,7 +9,7 @@
This extension point is used to customize the document creation behavior of this plug-in's default text file buffer manager. It allows to specify which document factory should be used in order to create the document instance of a text file buffer created for a certain file content type, file extension, or file name.
-<h6 class=CaptionFigColumn id=header>Deprecated since 3.2:</h6> This extension must no longer be used. We urge existing clients to remove their contribution:
+<h6 class=CaptionFigColumn id=header>Deprecated since 3.2: </h6> This extension must no longer be used. We urge existing clients to remove their contribution:
<li>the file buffer manager now provides an <code>ISynchronizable</code> document. Clients which need a synchronized document can set a lock object. <em>To overwrite an existing lock object is considered bad practice and can break other clients: if the document already has a lock object set then this one should be used by the client</em>.</li>
<li>clients which need a different <code>org.eclipse.jface.text.IDocument</code> implementation create the corresponding document in their document provider. The custom document will wrap the document provided by the file buffer.</li>

Back to the top