From 85149fb05ecae9480940e33737aa94ea192b6a99 Mon Sep 17 00:00:00 2001
From: Markus Keller
Date: Mon, 25 Feb 2013 19:14:16 +0100
Subject: converted line delimiters to Unix
---
.../schema/annotationModelCreation.exsd | 280 +++++++++----------
.../schema/documentCreation.exsd | 308 ++++++++++-----------
.../schema/documentSetup.exsd | 292 +++++++++----------
3 files changed, 440 insertions(+), 440 deletions(-)
(limited to 'org.eclipse.core.filebuffers/schema')
diff --git a/org.eclipse.core.filebuffers/schema/annotationModelCreation.exsd b/org.eclipse.core.filebuffers/schema/annotationModelCreation.exsd
index f680a735c..4936b18cc 100644
--- a/org.eclipse.core.filebuffers/schema/annotationModelCreation.exsd
+++ b/org.eclipse.core.filebuffers/schema/annotationModelCreation.exsd
@@ -1,140 +1,140 @@
-
-
-
-
-
-
-
-
- This extension point is used to customize the annotation model creation behavior of this plug-in's default text file buffer manager. It allows to specify which annotation model factory should be used in order to create the annotation model instance of a text file buffer created for a certain file content type, file extension, or file name.
-
-
-
-
-
-
-
-
-
-
-
- a fully qualified identifier of the target extension point
-
-
-
-
-
-
- an optional identifier of the extension instance
-
-
-
-
-
-
- an optional name of the extension instance
-
-
-
-
-
-
-
-
-
-
-
-
- The specification of a annotation model factory. In order to find a factory for a given file the attributes of each factory specification are consulted in the following sequence: contentTypeId, fileNames, extensions. If multiple, equally specific factory specifications are found for a given file it is not specified which factory is used.
-
-
-
-
-
-
- a fully qualified name of the factory implementation class. This class must implement the <code>org.eclipse.core.filebuffers.IAnnotationModelFactory</code> interface.
-
-
-
-
-
-
-
-
-
- a comma separated list of file extensions for which this factory should be used
-
-
-
-
-
-
- a comma separated list of file names for which this factory should be used
-
-
-
-
-
-
- the id of a content type as defined by the <code>org.eclipse.core.runtime.contentTypes</code> extension point for which this factory should be used
-
-
-
-
-
-
-
-
-
-
-
- 3.0
-
-
-
-
-
-
-
-
- <pre>
- <extension
- point="org.eclipse.core.filebuffers.annotationModelCreation">
- <factory
- extensions="xzy"
- class="org.eclipse.ui.texteditor.ResourceMarkerAnnotationModelFactory">
- </factory>
- </extension>
-</pre>
-
-
-
-
-
-
-
-
- Annotation model factories have to implement org.eclipse.core.filebuffers.IAnnotationModelFactory.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Copyright (c) 2001, 2004 IBM Corporation and others.<br>
-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 <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>
-
-
-
-
+
+
+
+
+
+
+
+
+ This extension point is used to customize the annotation model creation behavior of this plug-in's default text file buffer manager. It allows to specify which annotation model factory should be used in order to create the annotation model instance of a text file buffer created for a certain file content type, file extension, or file name.
+
+
+
+
+
+
+
+
+
+
+
+ a fully qualified identifier of the target extension point
+
+
+
+
+
+
+ an optional identifier of the extension instance
+
+
+
+
+
+
+ an optional name of the extension instance
+
+
+
+
+
+
+
+
+
+
+
+
+ The specification of a annotation model factory. In order to find a factory for a given file the attributes of each factory specification are consulted in the following sequence: contentTypeId, fileNames, extensions. If multiple, equally specific factory specifications are found for a given file it is not specified which factory is used.
+
+
+
+
+
+
+ a fully qualified name of the factory implementation class. This class must implement the <code>org.eclipse.core.filebuffers.IAnnotationModelFactory</code> interface.
+
+
+
+
+
+
+
+
+
+ a comma separated list of file extensions for which this factory should be used
+
+
+
+
+
+
+ a comma separated list of file names for which this factory should be used
+
+
+
+
+
+
+ the id of a content type as defined by the <code>org.eclipse.core.runtime.contentTypes</code> extension point for which this factory should be used
+
+
+
+
+
+
+
+
+
+
+
+ 3.0
+
+
+
+
+
+
+
+
+ <pre>
+ <extension
+ point="org.eclipse.core.filebuffers.annotationModelCreation">
+ <factory
+ extensions="xzy"
+ class="org.eclipse.ui.texteditor.ResourceMarkerAnnotationModelFactory">
+ </factory>
+ </extension>
+</pre>
+
+
+
+
+
+
+
+
+ Annotation model factories have to implement org.eclipse.core.filebuffers.IAnnotationModelFactory.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Copyright (c) 2001, 2004 IBM Corporation and others.<br>
+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 <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>
+
+
+
+
diff --git a/org.eclipse.core.filebuffers/schema/documentCreation.exsd b/org.eclipse.core.filebuffers/schema/documentCreation.exsd
index a125476ad..45e738b29 100644
--- a/org.eclipse.core.filebuffers/schema/documentCreation.exsd
+++ b/org.eclipse.core.filebuffers/schema/documentCreation.exsd
@@ -1,154 +1,154 @@
-
-
-
-
-
-
-
-
- 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.
-<br>
-<br>
-<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:
-<ul>
-<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>
-</ul>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- a fully qualified identifier of the target extension point
-
-
-
-
-
-
- an optional identifier of the extension instance
-
-
-
-
-
-
- an optional name of the extension instance
-
-
-
-
-
-
-
-
-
-
-
-
- The specification of a document factory. In order to find a factory for a given file the attributes of each factory specification are consulted in the following sequence: contentTypeId, fileNames, extensions. If multiple, equally specific factory specifications are found for a given file it is not specified which factory is used.
-
-
-
-
-
-
- a fully qualified name of the factory implementation class. This class must implement the <code>org.eclipse.core.filebuffers.IDocumentFactory</code> interface.
-
-
-
-
-
-
-
-
-
- a comma separated list of file extensions for which this factory should be used
-
-
-
-
-
-
- a comma separated list of file names for which this factory should be used
-
-
-
-
-
-
- the id of a content type as defined by the <code>org.eclipse.core.runtime.contentTypes</code> extension point for which this factory should be used
-
-
-
-
-
-
-
-
-
-
-
- 3.0
-
-
-
-
-
-
-
-
- <pre>
-<extension
- id="org.eclipse.jdt.debug.ui.SnippetDocumentFactory"
- name="%snippetDocumentFactory.name"
- point="org.eclipse.core.filebuffers.documentCreation">
- <factory
- extensions="jpage"
- class="org.eclipse.jdt.internal.debug.ui.snippeteditor.SnippetDocumentFactory">
- </factory>
-</extension>
-</pre>
-
-
-
-
-
-
-
-
- Document factories have to implement org.eclipse.core.filebuffers.IDocumentFactory.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Copyright (c) 2001, 2006 IBM Corporation and others.<br>
-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 <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>
-
-
-
-
+
+
+
+
+
+
+
+
+ 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.
+<br>
+<br>
+<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:
+<ul>
+<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>
+</ul>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ a fully qualified identifier of the target extension point
+
+
+
+
+
+
+ an optional identifier of the extension instance
+
+
+
+
+
+
+ an optional name of the extension instance
+
+
+
+
+
+
+
+
+
+
+
+
+ The specification of a document factory. In order to find a factory for a given file the attributes of each factory specification are consulted in the following sequence: contentTypeId, fileNames, extensions. If multiple, equally specific factory specifications are found for a given file it is not specified which factory is used.
+
+
+
+
+
+
+ a fully qualified name of the factory implementation class. This class must implement the <code>org.eclipse.core.filebuffers.IDocumentFactory</code> interface.
+
+
+
+
+
+
+
+
+
+ a comma separated list of file extensions for which this factory should be used
+
+
+
+
+
+
+ a comma separated list of file names for which this factory should be used
+
+
+
+
+
+
+ the id of a content type as defined by the <code>org.eclipse.core.runtime.contentTypes</code> extension point for which this factory should be used
+
+
+
+
+
+
+
+
+
+
+
+ 3.0
+
+
+
+
+
+
+
+
+ <pre>
+<extension
+ id="org.eclipse.jdt.debug.ui.SnippetDocumentFactory"
+ name="%snippetDocumentFactory.name"
+ point="org.eclipse.core.filebuffers.documentCreation">
+ <factory
+ extensions="jpage"
+ class="org.eclipse.jdt.internal.debug.ui.snippeteditor.SnippetDocumentFactory">
+ </factory>
+</extension>
+</pre>
+
+
+
+
+
+
+
+
+ Document factories have to implement org.eclipse.core.filebuffers.IDocumentFactory.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Copyright (c) 2001, 2006 IBM Corporation and others.<br>
+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 <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>
+
+
+
+
diff --git a/org.eclipse.core.filebuffers/schema/documentSetup.exsd b/org.eclipse.core.filebuffers/schema/documentSetup.exsd
index a7d7d7b99..52fdca6bd 100644
--- a/org.eclipse.core.filebuffers/schema/documentSetup.exsd
+++ b/org.eclipse.core.filebuffers/schema/documentSetup.exsd
@@ -1,146 +1,146 @@
-
-
-
-
-
-
-
-
- This extension point is used to customize the initialization process of a document for a text file buffer manager by this plug-in's default text file buffer manager. It allows to specify which document setup participant should be involved in the initialization process for a text file buffer created for a certain file content type, file extension, or file name.
-<p>
-<strong>Note:</strong> Participants have to be aware of the existence of other participants i.e. they should always setup a document in a way that does not interfere with others. E.g., when a participant wants to install partitioning on the document, it must use the <code>org.eclipse.jface.text.IDocumentExtension3</code> API and choose a unique partitioning id.
-As of 3.2, a warning is written to the log file if this isn't followed.
-</p>
-
-
-
-
-
-
-
-
-
-
-
- a fully qualified identifier of the target extension point
-
-
-
-
-
-
- an optional identifier of the extension instance
-
-
-
-
-
-
- an optional name of the extension instance
-
-
-
-
-
-
-
-
-
-
-
-
- The specification of a document setup participant. In order find all participants for a given file the attributes of each participant specification are consulted in the following sequence: contentTypeId, fileNames, extensions. If multiple participants are found, the sequence in which they are called is not specified.
-
-
-
-
-
-
- the fully qualified name of the participant implementation class. This class must implement the <code>org.eclipse.core.filebuffers.IDocumentSetupParticipant</code> interface.
-
-
-
-
-
-
-
-
-
- a comma separated list of file extensions for which this participant should be used
-
-
-
-
-
-
- a comma separated list of file names for which this participant should be used
-
-
-
-
-
-
- the id of a content type as defined by the <code>org.eclipse.core.runtime.contentTypes</code> extension point for which this participant should be used.
-
-
-
-
-
-
-
-
-
-
-
- 3.0
-
-
-
-
-
-
-
-
- <pre>
- <extension
- id="JavaDocumentSetupParticipant"
- name="%javaDocumentSetupParticipant"
- point="org.eclipse.core.filebuffers.documentSetup">
- <participant
- extensions="java"
- class="org.eclipse.jdt.internal.ui.javaeditor.JavaDocumentSetupParticipant">
- </participant>
- </extension>
-</pre>
-
-
-
-
-
-
-
-
- Document setup participants have to implement org.eclipse.core.filebuffers.IDocumentSetupParticipant.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Copyright (c) 2001, 2006 IBM Corporation and others.<br>
-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 <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>
-
-
-
-
+
+
+
+
+
+
+
+
+ This extension point is used to customize the initialization process of a document for a text file buffer manager by this plug-in's default text file buffer manager. It allows to specify which document setup participant should be involved in the initialization process for a text file buffer created for a certain file content type, file extension, or file name.
+<p>
+<strong>Note:</strong> Participants have to be aware of the existence of other participants i.e. they should always setup a document in a way that does not interfere with others. E.g., when a participant wants to install partitioning on the document, it must use the <code>org.eclipse.jface.text.IDocumentExtension3</code> API and choose a unique partitioning id.
+As of 3.2, a warning is written to the log file if this isn't followed.
+</p>
+
+
+
+
+
+
+
+
+
+
+
+ a fully qualified identifier of the target extension point
+
+
+
+
+
+
+ an optional identifier of the extension instance
+
+
+
+
+
+
+ an optional name of the extension instance
+
+
+
+
+
+
+
+
+
+
+
+
+ The specification of a document setup participant. In order find all participants for a given file the attributes of each participant specification are consulted in the following sequence: contentTypeId, fileNames, extensions. If multiple participants are found, the sequence in which they are called is not specified.
+
+
+
+
+
+
+ the fully qualified name of the participant implementation class. This class must implement the <code>org.eclipse.core.filebuffers.IDocumentSetupParticipant</code> interface.
+
+
+
+
+
+
+
+
+
+ a comma separated list of file extensions for which this participant should be used
+
+
+
+
+
+
+ a comma separated list of file names for which this participant should be used
+
+
+
+
+
+
+ the id of a content type as defined by the <code>org.eclipse.core.runtime.contentTypes</code> extension point for which this participant should be used.
+
+
+
+
+
+
+
+
+
+
+
+ 3.0
+
+
+
+
+
+
+
+
+ <pre>
+ <extension
+ id="JavaDocumentSetupParticipant"
+ name="%javaDocumentSetupParticipant"
+ point="org.eclipse.core.filebuffers.documentSetup">
+ <participant
+ extensions="java"
+ class="org.eclipse.jdt.internal.ui.javaeditor.JavaDocumentSetupParticipant">
+ </participant>
+ </extension>
+</pre>
+
+
+
+
+
+
+
+
+ Document setup participants have to implement org.eclipse.core.filebuffers.IDocumentSetupParticipant.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Copyright (c) 2001, 2006 IBM Corporation and others.<br>
+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 <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>
+
+
+
+
--
cgit v1.2.1