1--The folder contains extensions which use in the description.xml the following:
2
3-The <publisher> element
4-The <release-notes> element
5
6Both element contain localized child elements.
7
8The following table shows what localized item is used, when the Office the locale
9en-US uses.
10
11
12Localization:
13
14Installed office en-US
15         | publisher     | release notes
16=============================================
17pub1.oxt | en-US         | en-US
18---------------------------------------------
19pub2.oxt | en-US-region1 | en-US-region1
20---------------------------------------------
21pub3.oxt | en            | en
22---------------------------------------------
23pub4.oxt | en-GB         | en-GB
24---------------------------------------------
25pub5.oxt | de            | de
26
27
28================================================================================
29pub6.oxt
30================================================================================
31like pub1 but without release notes.
32
33
34================================================================================
35pub7.oxt
36================================================================================
37like pub1 but without publisher name.
38
39================================================================================
40pub8.oxt
41================================================================================
42Need not be committed in extensions/www/testarea/desktop.
43
44pub8.oxt is intended for tests with extensions.services.openoffice.org.
45It does not contain <update-information>. That is, the Extension Manager will obtain
46the update information from the repository as feed:
47
48http://updateext.services.openoffice.org/ProductUpdateService/check.Update
49
50pub8.oxt provides <publisher> and <release-notes>. These information should be transferred
51in the update feed and not those entered in the repository.
52
53Test
54----
55Repository:
56
57-Create the new extension in the repository.
58-Provide a company name and a URL to the company website. This setting should be ignored
59 when generating the udpate feed. Instead the publisher name from the extension is used.
60 Enter "Publisher Title" : some arbitrary company
61 "Publisher URL": any arbitrary URL but not:
62 http://extensions.openoffice.org/testarea/desktop/publisher/publisher_en-US.html
63
64-Create a new release for the extension. Upload the version 2.0 (update/pub8.oxt).
65 Provide release notes. These release notes should later not be seen when clicking on
66 the release notes link.
67
68
69Office:
70-Install version 1.0 of the extension:
71 desktop/test/deployment/update/publisher/pub8.oxt
72
73-Run the update in the Extension Manager
74
75
76Result:
77The Update Dialog should show the publisher name as provided in the description.xml. For example,
78when lang=en-US was selected: My OpenOffice en-US
79
80A release notes link is displayed with an URL to the release notes as provided in
81the description.xml. For example, when lang=en-US was selected:
82"http://extensions.openoffice.org/testarea/desktop/publisher/publisher_en-US.html
83
84
85================================================================================
86pub9.oxt
87================================================================================
88Need not be committed in extensions/www/testarea/desktop.
89
90pub9.oxt is intended for tests with extensions.services.openoffice.org.
91It does not contain <update-information>. That is, the Extension Manager will obtain
92the update information from the repository as feed:
93
94http://updateext.services.openoffice.org/ProductUpdateService/check.Update
95
96pub9.oxt provides <publisher>. That means the update feed should
97contain the <publisher> as provided by the extension and the release notes as entered
98in the repository.
99
100Test
101----
102Repository:
103
104-Create the new extension in the repository.
105-Provide a company name and a URL to the company website. This setting should be ignored
106 when generating the udpate feed. Instead the publisher name from the extension is used.
107 Enter "Publisher Title" : some arbitrary company name
108 "Publisher URL": any arbitrary URL but not:
109 http://extensions.openoffice.org/testarea/desktop/publisher/publisher_en-US.html
110
111-Create a new release for the extension. Upload the version 2.0 (update/pub9.oxt).
112 Provide release notes. These release notes should later be displayed when clicking on
113 the release notes link.
114
115
116Office:
117-Install version 1.0 of the extension:
118 desktop/test/deployment/update/publisher/pub9.oxt
119
120-Run the update in the Extension Manager
121
122
123Result:
124The Update Dialog should show the publisher name as provided in the description.xml. For example,
125when lang=en-US was selected: My OpenOffice en-US
126
127A release notes link is displayed with an URL to the release notes as provided in the release notes
128field on the edit page for the extension in the repository.
129
130================================================================================
131pub10.oxt
132================================================================================
133Need not be committed in extensions/www/testarea/desktop.
134
135pub10.oxt is intended for tests with extensions.services.openoffice.org.
136It does not contain <update-information>. That is, the Extension Manager will obtain
137the update information from the repository as feed:
138
139http://updateext.services.openoffice.org/ProductUpdateService/check.Update
140
141pub10.oxt provides <release-notes>. That means the update feed should
142contain the <release-notes> as provided by the extension and the publisher name/URLs as entered
143in the repository.
144
145Test
146----
147Repository:
148
149-Create the new extension in the repository.
150-Provide a company name and a URL to the company website. They should then be in the udpate
151 feed.
152
153-Create a new release for the extension. Upload the version 2.0 (update/pub10.oxt).
154 Provide release notes. These release notes should NOT  be displayed when clicking on
155 the release notes link. Instead the release notes provided by pub10.oxt should be displayed.
156
157
158Office:
159-Install version 1.0 of the extension:
160 desktop/test/deployment/update/publisher/pub10.oxt
161
162-Run the update in the Extension Manager
163
164
165Result:
166The Update Dialog should show the publisher name as provided in the repository.
167
168A release notes link is displayed with an URL to the release notes as provided in the
169pub10.oxt.  For example, when the locale of the office is en-US then this page will be
170displayed:
171For example,
172when lang=en-US was selected: My OpenOffice en-US
173
174================================================================================
175pub11.oxt
176================================================================================
177Need not be committed in extensions/www/testarea/desktop.
178
179pub11.oxt is intended for tests with extensions.services.openoffice.org.
180It does not contain <update-information>. That is, the Extension Manager will obtain
181the update information from the repository as feed:
182
183http://updateext.services.openoffice.org/ProductUpdateService/check.Update
184
185pub10.oxt neither provides <release-notes> nor <publisher>. That means the update feed should
186contain these data as provided by the user on the repository web site.
187
188Test
189----
190Repository:
191
192-Create the new extension in the repository.
193-Provide a company name and a URL to the company website. They should then be in the udpate
194 feed.
195
196-Create a new release for the extension. Upload the version 2.0 (update/pub11.oxt).
197 Provide release notes. These release notes should be displayed when clicking on
198 the release notes link.
199
200
201Office:
202-Install version 1.0 of the extension:
203 desktop/test/deployment/update/publisher/pub11.oxt
204
205-Run the update in the Extension Manager
206
207
208Result:
209The Update Dialog should show the publisher name as provided in the repository.
210
211A release notes link is displayed which leads to the release notes kept in the repository.
212
213