blob: b3a91adac389bd5e4c2e1a431134141b0be082e8 [file] [log] [blame]
dacarverbf4bd9f2008-10-18 01:08:59 +00001###############################################################################
2# feature.properties
3# contains externalized strings for feature.xml
4# "%foo" in feature.xml corresponds to the key "foo" in this file
5# java.io.Properties file (ISO 8859-1 with "\" escapes)
6# This file should be translated.
7
8# "featureName" property - name of the feature
9featureName=Vex XML Editor (Incubating)
10
11# "copyright" property - copyright notice
12copyright=Copyright (c) 2004, 2008 John Krasnay and others.\n\
13All rights reserved. This program and the accompanying materials\n\
14are made available under the terms of the Eclipse Public License v1.0\n\
15which accompanies this distribution, and is available at\n\
16http://www.eclipse.org/legal/epl-v10.html\n\
17\n\
18Contributors:\n\
19 John Krasnay - initial API and implementation\n\
20 David Carver (Standards for Technology in Automotive Retail - http://www.starstandard.org)\n\
21 Ed Burnette - (SAS) - http://www.sas.com/\n
22# "providerName" property - name of the company that provides the feature
23providerName=Eclipse.org
24
25# "updateSiteName" property - label for the update site
26updateSiteName=The Eclipse Web Tools Platform (WTP) Project update site
27
28# "description" property - description of the feature
29description=A CSS-styled editor for document-style XML documents such as DocBook and XHTML
30
31# "licenseURL" property - URL of the "Feature License"
32# do not translate value - just change to point to a locale-specific HTML page
33licenseURL=http://www.eclipse.org/org/documents/epl-v10.php
34
35# "license" property - text of the "Feature Update License"
36# should be plain text version of license agreement pointed to be "licenseURL"
37license=\
38ECLIPSE FOUNDATION SOFTWARE USER AGREEMENT\n\
39June 06, 2007\n\
40\n\
41Usage Of Content\n\
42\n\
43THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR\n\
44OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT").\n\
45USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS\n\
46AGREEMENT AND/OR THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR\n\
47NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU\n\
48AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT\n\
49AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS\n\
50OR NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE\n\
51TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS\n\
52OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED\n\
53BELOW, THEN YOU MAY NOT USE THE CONTENT.\n\
54\n\
55Applicable Licenses\n\
56\n\
57Unless otherwise indicated, all Content made available by the Eclipse Foundation\n\
58is provided to you under the terms and conditions of the Eclipse Public\n\
59License Version 1.0 ("EPL"). A copy of the EPL is provided with this\n\
60Content and is also available at http://www.eclipse.org/legal/epl-v10.html.\n\
61For purposes of the EPL, "Program" will mean the Content.\n\
62\n\
63Content includes, but is not limited to, source code, object code,\n\
64documentation and other files maintained in the Eclipse.org CVS\n\
65repository ("Repository") in CVS modules ("Modules") and made available\n\
66as downloadable archives ("Downloads").\n\
67\n\
68 - Content may be structured and packaged into modules to facilitate delivering,\n\
69 extending, and upgrading the Content. Typical modules may include plug-ins ("Plug-ins"),\n\
70 plug-in fragments ("Fragments"), and features ("Features").\n\
71 - Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java? ARchive)\n\
72 in a directory named "plugins".\n\
73 - A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material.\n\
74 Each Feature may be packaged as a sub-directory in a directory named "features".\n\
75 Within a Feature, files named "feature.xml" may contain a list of the names and version\n\
76 numbers of the Plug-ins and/or Fragments associated with that Feature.\n\
77 - Features may also include other Features ("Included Features"). Within a Feature, files\n\
78 named "feature.xml" may contain a list of the names and version numbers of Included Features.\n\
79\n\
80Features may also include other Features ("Included Features"). Files named\n\
81"feature.xml" may contain a list of the names and version numbers of\n\
82Included Features.\n\
83\n\
84The terms and conditions governing Plug-ins and Fragments should be\n\
85contained in files named "about.html" ("Abouts"). The terms and\n\
86conditions governing Features and Included Features should be contained\n\
87in files named "license.html" ("Feature Licenses"). Abouts and Feature\n\
88Licenses may be located in any directory of a Download or Module\n\
89including, but not limited to the following locations:\n\
90\n\
91 - The top-level (root) directory\n\
92 - Plug-in and Fragment directories\n\
93 - Inside Plug-ins and Fragments packaged as JARs\n\
94 - Sub-directories of the directory named "src" of certain Plug-ins\n\
95 - Feature directories\n\
96\n\
97Note: if a Feature made available by the Eclipse Foundation is installed using the\n\
98Eclipse Update Manager, you must agree to a license ("Feature Update\n\
99License") during the installation process. If the Feature contains\n\
100Included Features, the Feature Update License should either provide you\n\
101with the terms and conditions governing the Included Features or inform\n\
102you where you can locate them. Feature Update Licenses may be found in\n\
103the "license" property of files named "feature.properties". Such Abouts,\n\
104Feature Licenses and Feature Update Licenses contain the terms and\n\
105conditions (or references to such terms and conditions) that govern your\n\
106use of the associated Content in that directory.\n\
107\n\
108THE ABOUTS, FEATURE LICENSES AND FEATURE UPDATE LICENSES MAY REFER\n\
109TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS.\n\
110SOME OF THESE OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):\n\
111\n\
112 - Common Public License Version 1.0 (available at http://www.eclipse.org/legal/cpl-v10.html)\n\
113 - Apache Software License 1.1 (available at http://www.apache.org/licenses/LICENSE)\n\
114 - Apache Software License 2.0 (available at http://www.apache.org/licenses/LICENSE-2.0)\n\
115 - IBM Public License 1.0 (available at http://oss.software.ibm.com/developerworks/opensource/license10.html)\n\
116 - Metro Link Public License 1.00 (available at http://www.opengroup.org/openmotif/supporters/metrolink/license.html)\n\
117 - Mozilla Public License Version 1.1 (available at http://www.mozilla.org/MPL/MPL-1.1.html)\n\
118 - Common Development and Distribution License (CDDL) Version 1.0 (available at http://www.sun.com/cddl/cddl.html)\n\
119\n\
120IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR\n\
121TO USE OF THE CONTENT. If no About, Feature License or Feature Update License\n\
122is provided, please contact the Eclipse Foundation to determine what terms and conditions\n\
123govern that particular Content.\n\
124\n\
125Cryptography\n\
126\n\
127Content may contain encryption software. The country in which you are\n\
128currently may have restrictions on the import, possession, and use,\n\
129and/or re-export to another country, of encryption software. BEFORE\n\
130using any encryption software, please check the country's laws,\n\
131regulations and policies concerning the import, possession, or use,\n\
132and re-export of encryption software, to see if this is permitted.\n\
133\n\
134Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.\n
135########### end of license property ##########################################