This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/openoffice-org.git
The following commit(s) were added to refs/heads/asf-site by this push:
new e800c5f1b9 git-site-role commit from copy_staging.sh
e800c5f1b9 is described below
commit e800c5f1b94401ba13fdcd170c275c9ce3a1725c
Author: jenkins <[email protected]>
AuthorDate: Tue Jan 6 10:17:00 2026 +0000
git-site-role commit from copy_staging.sh
---
content/bugs/bug_writing_guidelines.html | 61 ++++++++---------
content/bugs/issues.html | 50 +++++++-------
content/certification/index.html | 14 ++--
content/feed.xml | 4 +-
content/xml/faq.html | 52 +++++++--------
content/xml/filter/index.html | 108 +++++++++++++++----------------
content/xml/modules.html | 2 +-
content/xml/project_tools.html | 16 ++---
content/xml/research.html | 2 +-
content/xml/uses.html | 4 +-
content/xml/xfilter.html | 28 ++++----
content/xml/xml_advocacy.html | 56 ++++++++--------
12 files changed, 187 insertions(+), 210 deletions(-)
diff --git a/content/bugs/bug_writing_guidelines.html
b/content/bugs/bug_writing_guidelines.html
index 50fcf35780..6aa94dfdc1 100644
--- a/content/bugs/bug_writing_guidelines.html
+++ b/content/bugs/bug_writing_guidelines.html
@@ -31,19 +31,19 @@
<h4>Why you should read this</h4>
-
-<p> Simply put, the more effectively you report an issue, the more likely an
engineer will actually fix it. These issue writing guidelines are an attempt at
a general tutorial on writing effective issue reports for novice issue writers;
not every sentence may precisely apply to your software project.
-
+<p> Simply put, the more effectively you report an issue, the more likely a
developer will actually fix it.
+ These issue writing guidelines are an attempt at a general tutorial on
writing effective issue reports for novice issue writers;
+ not every sentence may precisely apply to your software project.
<br>
<br>
<h4>How to Write a Useful Issue Report</h4>
<blockquote>
<p>Useful issue reports are ones that get issues fixed. A useful issue report
normally has two qualities:</p></blockquote>
+<ol>
+ <li> <b>Reproducible.</b> If adeveloper can't see it or conclusively prove
that it exists, the engineer will probably stamp it "WORKSFORME" or "INVALID",
and move on to the next issue. Every detail you can provide helps. </li><br><br>
-<ol> <li><b>Reproducible.</b> If an engineer can't see it or conclusively
prove that it exists, the engineer will probably stamp it "WORKSFORME" or
"INVALID", and move on to the next issue. Every detail you can provide helps.
</li><br><br>
-
-<li> <b>Specific.</b> The quicker the engineer can isolate the issue to a
specific problem, the more likely it'll be expediently fixed. <b></b>(If a
programmer or tester has to decipher an issue, they spend more time cursing the
submitter than fixing or testing the problem.) </li> </ol>
+ <li> <b>Specific.</b> The quicker the developer can isolate the issue to a
specific problem, the more likely it'll be expediently fixed. <b></b>(If a
programmer or tester has to decipher an issue, they spend more time cursing the
submitter than fixing or testing the problem.) </li> </ol>
<blockquote> Let's say the application you're testing is a web browser. You
crash at foo.com, and want to write up an issue report: </blockquote>
@@ -53,17 +53,17 @@
<b>Good:</b> "I crashed each time when I opened the attached spreadsheet
document using the 10.13.00 build on a Win NT 4.0 (Service Pack 5) system. I
also rebooted into Linux (RedHat 6.2), and reproduced this problem using the
10.13.00 Linux build.
<p>When I removed the chart from the document I was able to load it without
any trouble." </blockquote>
<br>
-<h4>How to enter a useful Issue Report into IssueZilla</h4>
-<blockquote> In order to file an Issue, you must be a registered user of
OpenOffice.org. Registering is easy: simply click on the "Join" link in the
left navbar and follow the instructions. It takes all of a few minutes. If you
are a registered user, click on the "My Issues" link in the left navbar or on
the <a href="//project_issues.html" target="_blank">"Bugs and Issues"</a> link
on the navbar. The latter is a more comprehensive page which provides a
explanation of IssueZilla and also [...]
-<p> Go to the <a href="//issues/query.cgi" target="_blank">IssueZilla Query
Page</a> to determine whether the defect you've discovered is a known issue and
has already been reported. (If your issue is the 37th duplicate of a known
issue, you're more likely to annoy the engineer. Annoyed engineers fix fewer
issues.)
+<h4>How to enter a useful Issue Report into Bugzilla</h4>
+<blockquote> In order to file an Issue, you must be a registered user of
Apache OpenOffice. Registering is easy: simply click on the "Join" link in the
left navbar and follow the instructions. It takes all of a few minutes. If you
are a registered user, click on the "My Issues" link in the left navbar or on
the <a href="//project_issues.html" target="_blank">"Bugs and Issues"</a> link
on the navbar. The latter is a more comprehensive page which provides a
explanation of IssueZilla and al [...]
+<p> Go to the <a href="https://bz.apache.org/ooo/enter_bug.cgi";
target="_blank">Bugzilla Query Page</a> to determine whether the defect you've
discovered is a known issue and has already been reported. (If your issue is
the 37th duplicate of a known issue, you're more likely to annoy the engineer.
Annoyed developers fix fewer issues.)
-<p>Next, be sure that you've reproduced your issue using a recent build.
(Engineers tend to be most interested in problems afflicting the code base that
they're actively working on, rather than those in a code base that's hundreds
of issue fixes obsolete.)<br> <br> If you've discovered a new issue using a
current build, report it in IssueZilla: </blockquote>
+<p>Next, be sure that you've reproduced your issue using a recent build.
(Developers tend to be most interested in problems afflicting the code base
that they're actively working on, rather than those in a code base that's
hundreds of issue fixes obsolete.)<br> <br> If you've discovered a new issue
using a current build, report it in Bugzilla: </blockquote>
-<ol> <li> <p>From your IssueZilla main page, choose "Enter a new issue".</p>
</li>
+<ol> <li> <p>From your Bugzilla main page, choose "Enter a new issue".</p>
</li>
<li> <p>Select the product that you've found an issue in.</p> </li>
-<li> <p>Enter your E-mail address, Password, and press the "Login" button. (If
you don't yet have a password, leave the password text box empty, and press the
"E-mail me a password" button instead. You'll receive an E-mail message with
your password shortly.)</p> </li> </ol>
+<li> <p>Enter your E-mail address, Password, and press the "Login" button. (If
you don't yet have a password, leave the password text box empty, and press the
"E-mail me a password" button instead. You'll shortly receive an E-mail message
with your password.)</p> </li> </ol>
<h4>Now, fill out the form. Here's what it all means:</h4>
@@ -72,9 +72,9 @@
<blockquote> <b>Product: In which product did you find the issue?</b><br> You
just filled this out on the last page. </blockquote>
<blockquote> <b>Version: In which product version did you first find the
issue?</b><br>
- If applicable. </blockquote>
+ If applicable.</blockquote>
-<blockquote> <b>Component: In which component does the issue exist?</b><br>
IssueZilla requires that you select a component to enter an issue. (If they all
look meaningless, click on the Component link, which links to descriptions of
each component, to help you make the best choice.) </blockquote>
+<blockquote> <b>Component: In which component does the issue exist?</b><br>
Bugzilla requires that you select a component to enter an issue. (If they all
look meaningless, click on the Component link, which links to descriptions of
each component, to help you make the best choice.) </blockquote>
<blockquote> <b>Platform: On which hardware platform did you find this
issue? </b>(e.g., Sun, PC)</><br> If you know the issue happens on all hardware
platforms, choose 'All'. Otherwise, select the platform that you found the
issue on, or "Other" if your platform isn't listed. </blockquote>
@@ -88,11 +88,11 @@
<blockquote > <br><i> Who will be following up on the issue?</i> </blockquote>
-<blockquote> <b>Assigned To: Which engineer should be responsible for fixing
this issue?</b><br> IssueZilla will automatically assign the issue to a default
engineer upon submitting an issue report; the text box exists to allow you to
manually assign it to a different engineer. (To see the list of default
engineers for each component, click on the Component link.) </blockquote>
+<blockquote> <b>Assigned To: Which developer should be responsible for fixing
this issue?</b><br> Bugzilla will automatically assign the issue to a default
developer upon submitting an issue report; the text box exists to allow you to
manually assign it to a different engineer. (To see the list of default
developers for each component, click on the Component link.) </blockquote>
<blockquote> <b>Cc: Who else should receive e-mail updates on changes to this
issue?</b><br> List the full e-mail addresses of other individuals who should
receive an e-mail update upon every change to the issue report. You can enter
as many e-mail addresses as you'd like; e-mail addresses must be separated by
commas, with no spaces between the addresses. </blockquote>
-<blockquote> <br> <i>What else can you tell the engineer about the issue?
</i></blockquote>
+<blockquote> <br> <i>What else can you tell the developer about the issue?
</i></blockquote>
<blockquote> <b>URL: On what URL did you discover this issue?</b><br> If you
encountered the issue on a particular URL, please provide it (or, them) here.
</blockquote>
@@ -108,31 +108,24 @@
<li> <blockquote> <b>Unix:</b> please provide a minimized stack trace.
</blockquote> </li> </ul>
<p><strong>Attachments.</strong><em> </em>
-It may be the
- case you need to add an attachment(s) to an Issue, either the one you file
- or another one. You can do it; the limit is 10MB, but please keep any
attachment
- small, as there are still some using
- 56K
- connections.
- Attaching
- a file to an issue is a two-step procedure and is not obvious. You must
first
- submit the issue or locate the issue to which you wish to attach the file.
- Then, you can add the file as an attachment to that issue. There will be a
link
- in the issue body that reads:
+It may be the case you need to add an attachment(s) to an Issue, either the
one you file
+or another one. You can do it; the limit is 10MB, but please keep any
attachment
+small, as there are still some using 56K connections.
+Attaching a file to an issue is a two-step procedure and is not obvious. You
must first
+submit the issue or locate the issue to which you wish to attach the file.
+ Then, you can add the file as an attachment to that issue. There will be a
link in the issue body that reads:
<blockquote> Create a new attachment (proposed patch, testcase,
etc.)</blockquote>
<p> <strong>Hints</strong>: Reduce the size of your file as much as possible.
And, if you are
- uploading an HTML document, be sure to compress it first (Zip or tar it),
- otherwise it
- may get corrupted when others try to download it.
- <p><strong>MIME types</strong>: Select the correct mime type for you
attachment from the MIME type
- pulldown panel For OpenOffice.org 2.x documents, choose the corresponding
- "application/vnd.oasis.opendocument."
+uploading an HTML document, be sure to compress it first (Zip or tar it),
otherwise it
+may get corrupted when others try to download it.
+<p><strong>MIME types</strong>: Select the correct mime type for you
attachment from the MIME type
+pulldown panel For Apache OpenOffice documents, choose the corresponding
"application/vnd.oasis.opendocument."
<p>You're done!
After double-checking your entries for any possible errors, press the
"Commit" button,
and your issue report will now be in the IssueZilla database.<br>
<hr>
-<p>(These Bug Writing Guidelines were originally written for Mozilla by <a
href= "mailto:[email protected]";><b>Eli Goldberg</b></a>. Thanks to
Claudius Gayle, Peter Mock, Chris Pratt, Louis Suarez-Potts, Tom Schutter,
Rainer Bielefeld, and Chris Yeh for contributing to this document. Constructive
<a href="mailto:[email protected]"; >suggestions and feedback</a>
are welcome.)
+<p>(These Bug Writing Guidelines were originally written for Mozilla by <a
href= "mailto:[email protected]";><b>Eli Goldberg</b></a>. Thanks to
Claudius Gayle, Peter Mock, Chris Pratt, Louis Suarez-Potts, Tom Schutter,
Rainer Bielefeld, and Chris Yeh for contributing to this document. Constructive
<a href="mailto:[email protected]"; >suggestions and feedback</a> are
welcome.)
</blockquote>
</div>
diff --git a/content/bugs/issues.html b/content/bugs/issues.html
index ed85c74282..1d6132008b 100644
--- a/content/bugs/issues.html
+++ b/content/bugs/issues.html
@@ -7,7 +7,7 @@
<link href="/css/ooo.css" rel="stylesheet" type="text/css">
-<title>Got Issues? (Last updated 2002-06-03)</title>
+<title>Got Issues? (Last updated 2026-01-05)</title>
<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
@@ -30,7 +30,7 @@
<h2>Got Issues?</h2>
-<p><i>Last updated 2002-06-03</i></p>
+<p><i>Last updated 2026-01-05</i></p>
<br>
@@ -48,16 +48,15 @@
possibly help out or offer feedback
</p>
<br>
- <h4>What Is IssueZilla?</h4>
+ <h4>What Is Bugzilla?</h4>
- <p>IssueZilla, a proprietary tool, is based on Mozilla's open-source <a
- href="http://www.mozilla.org/bugs/";>Bugzilla</a>, but has been
+ <p>Bugzilla is Mozilla's open-source <a
href="http://www.mozilla.org/bugs/";>Bugzilla</a>, but has been
generalized by <a href="http://www.collab.net";>CollabNet</a> to handle all
kinds of issues, not just code-based
- issues. On OpenOffice.org, the supported issue-types now include:
+ issues. On Apache OpenOffice, the supported issue-types now include:
DEFECT, ENHANCEMENT, FEATURE, TASK and PATCH. We can add issue types in
the future as necessary, and these can be reported against specific
components of a project, for example 'documentation', 'code', 'ui',
- 'definition'. OpenOffice.org's projects are 'api', 'chart', 'database
+ 'definition'. Apache OpenOffice's projects are 'api', 'chart', 'database
access', 'drawing', 'formula editor', 'presentation', 'spreadsheet',
'word processor' and 'xml' to name just a few. Take a look at the
projects/products list to see all of them.
@@ -68,9 +67,9 @@
<h4>What do you have an issue with?</h4>
<p>Do you want to report an issue with a milestone build or with a copy
- of OpenOffice.org that you compiled yourself? IssueZilla is the place
+ of Apache OpenOffice that you compiled yourself? Bugzilla is the place
to submit issue reports for software distributed by
- OpenOffice.org. This page gives an overview of how IssueZilla works.
+ Apache OpenOffice. This page gives an overview of how Bugzilla works.
Read the <a
href="//bugs/bug_writing_guidelines.html">issue
writing guidelines</a> as well, for tips on how to write useful issue
@@ -87,19 +86,16 @@
<dt><b>Project</b></dt>
<dd>
- OpenOffice.org is composed of different projects. Carefully
- read the <a
- href="/projects/">project
- descriptions</a> if you're unsure of which project to attribute
+ Apache OpenOffice is composed of different projects. Carefully read the
<a
+ href="/projects/">project descriptions</a> if you're unsure of which
project to attribute
your issue to (visit the projects themselves for fuller descriptions).
The project you choose determines which person
- IssueZilla assigns the issue to.
+ Bugzilla assigns the issue to.
</dd>
<dt><b>Status Whiteboard</b></dt>
<dd>
- The Status Whiteboard is used for writing short notes about the
- issue.
+ The Status Whiteboard is used for writing short notes about the issue.
</dd>
<dt><b>Keywords</b></dt>
@@ -113,13 +109,13 @@
</dt>
<dd>
- Developers can post <tt>helpwanted</tt> notices, and IssueZilla can
+ Developers can post <tt>helpwanted</tt> notices, and Bugzilla can
help match-make other developers and apprentices who wish to help
out with a TASK. Developers should Write <tt>helpwanted</tt> in the
Keywords field of an issues, perhaps changing the issue-type of the
defect or enhancement to 'TASK'. Others searching for things to do
will find it and even accept the issue or TASK. People interested
- in getting involved can search IssueZilla for issues and
+ in getting involved can search Bugzilla for issues and
ENHANCEMENTs marked <tt>helpwanted</tt>. Maybe one of them will
have the expertise and resources to help you with your problem.
</dd>
@@ -190,13 +186,13 @@
<h4>Life Cycle Of An Issue</h4>
<p>What happens to an issue when it is first reported depends on who
- reported it. New IssueZilla accounts by default create issues which are
+ reported it. New Bugzilla accounts by default create issues which are
<tt>UNCONFIRMED</tt>.
- Currently, on IssueZilla, the quality assurance is done by
+ Currently, on Bugzilla, the quality assurance is done by
a list of users subscribed to a "virtual user"
issues@<project>.openoffice.org.
<p>
- You then use your regular IssueZilla account to
+ You then use your regular Bugzilla account to
login, then view, then further "workflow" the issue.
<br>
<P><A NAME="emailreply"></A>
@@ -208,12 +204,12 @@
all changes in bugs of this project.
</p>
- <p>If you are a registered OpenOffice.org user, you
+ <p>If you are a registered Apache OpenOffice user, you
can create <tt>UNCONFIRMED</tt> issues.
When an issue is confirmed and becomes <tt>NEW</tt>, the
developer will probably look at the issue and either accept it or give
it to someone else. If the issue remains new and inactive for more than
- a week, IssueZilla nags the issue's owner with email until action is
+ a week, Bugzilla nags the issue's owner with email until action is
taken. Whenever an issue is reassigned or has its component changed,
its status is set back to <tt>NEW</tt>. The <tt>NEW</tt> status means
that the issue is newly added to a particular developer's plate, not
@@ -250,7 +246,7 @@
<dd>
The problem described is not a issue, or not a issue in
- OpenOffice.org.
+ Apache OpenOffice.
</dd>
<dt><b>WONTFIX</b></dt>
@@ -293,10 +289,10 @@
<dt><b>MOVED</b></dt>
<dd>
- The issue was specific to a particular OpenOffice.org-based
- distribution and didn't affect OpenOffice.org code. One such
+ The issue was specific to a particular Apache OpenOffice-based
+ distribution and didn't affect Apache OpenOffice code. One such
scenario are defects reported against Sun's product version of
- OpenOffice.org. The issue was moved to the bug database of the
+ Apache OpenOffice. The issue was moved to the bug database of the
distributor of the affected OpenOffice.org derivative.
</dd>
</dl>
diff --git a/content/certification/index.html b/content/certification/index.html
index 8eb67e5b6a..4c39c8a152 100644
--- a/content/certification/index.html
+++ b/content/certification/index.html
@@ -15,7 +15,7 @@
//messages: set your own; use as many as you'd like; set up Hyperlinks to
//URLs as you normally do: <a target=... href="... URL ...">..message..</a>;
var singletext=new Array();
-singletext[0]='<h3>Certification Wiki</h3><p>Feel free to <a
href="http://wiki.services.openoffice.org/wiki/Certification";>review the
wiki</a> and get up to date to what we are doing.</p>';
+singletext[0]='<h3>Certification Wiki</h3><p>Feel free to <a
href="https://wiki.openoffice.org/wiki/Certification";>review the wiki</a> and
get up to date to what we are doing.</p>';
singletext[1]='<h3>Beta tester needed</h3><p>Learn how can you become a beta
tester for the certification.</p>';
//singletext[...]='...';
//-- end Parameters and message -->
@@ -48,12 +48,12 @@ singletext[1]='<h3>Beta tester needed</h3><p>Learn how can
you become a beta tes
<!-- The campaign class is taken directly from the homepage on the CSS link -->
<div class="campaign"><h2>Where to begin ?</h2>
- <p><a href="http://wiki.services.openoffice.org/wiki/Certification";>The
very active Wiki Page</a>, here we put all the things who most be change
frequently</p>
+ <p><a href="https://wiki.openoffice.org/wiki/Certification";>The very
active Wiki Page</a>, here we put all the things who most be change
frequently</p>
</div>
<div class="homebox">
<h2>Mision of the Certification Project</h2>
-<p> The OpenOffice.org Certification Project will develop and manage a
+<p> The Apache OpenOffice Certification Project will develop and manage a
global skills-certification program through a network of training and
support partner organizations in both the private and public sector.
We will develop a set of skills standards as well as a flexible,
@@ -90,11 +90,11 @@
if(document.getElementById||document.all){document.write('<div style="position:r
<ul>
<div class="MyBox">
<div class="MyPicBox">
- <li>a more <a href="gen_index.html">general category</a> listing
OpenOffice.org usage in schools and universities and documentation for
developers</li>
+ <li>a more <a href="gen_index.html">general category</a> listing Apache
OpenOffice usage in schools and universities and documentation for
developers</li>
</div>
<div class="MyPicBox">
- <li>examples of existing projects and applications involving both
Education world and OpenOffice.org project guidelines ...</li>
+ <li>examples of existing projects and applications involving both
Education world and Apache OpenOffice project guidelines ...</li>
</div>
</div>
<div class="MyPicBox">
@@ -102,7 +102,7 @@
if(document.getElementById||document.all){document.write('<div style="position:r
</div>
<div class="MyPicBox">
- <li>a <a
href="http://wiki.services.openoffice.org/wiki/Education/Certification/Petition";>
+ <li>a <a
href="https://wiki.openoffice.org/wiki/Education/Certification/Petition";>
Statements</a> that define the project as they explain the way to evolve.</li>
</div>
</ul>
@@ -111,7 +111,7 @@ Statements</a> that define the project as they explain the
way to evolve.</li>
Join us on the :</p>
<ul>
- <li><a
href="http://certification.openoffice.org/servlets/ProjectMailingListList";>[email protected]</a>
mailing list for development or localization of tools purposes</li>
+ <li><a mailto:[email protected]
[email protected]</a> mailing list for development or
localization of tools purposes</li>
</ul>
</div>
diff --git a/content/feed.xml b/content/feed.xml
index 7e1d0eaa92..5eabd3cd46 100644
--- a/content/feed.xml
+++ b/content/feed.xml
@@ -6,8 +6,8 @@
<atom:link href="http://localhost:8820/feed.xml"; rel="self"
type="application/rss+xml" />
<description>OpenOffice.org Feed</description>
<language>en-us</language>
- <pubDate>Sun, 21 Dec 2025 22:02:13 +0000</pubDate>
- <lastBuildDate>Sun, 21 Dec 2025 22:02:13 +0000</lastBuildDate>
+ <pubDate>Mon, 5 Jan 2026 13:12:48 +0000</pubDate>
+ <lastBuildDate>Mon, 5 Jan 2026 13:12:48 +0000</lastBuildDate>
</channel>
diff --git a/content/xml/faq.html b/content/xml/faq.html
index 82e047f4a6..5e626fce9f 100644
--- a/content/xml/faq.html
+++ b/content/xml/faq.html
@@ -7,7 +7,7 @@
<link href="/css/ooo.css" rel="stylesheet" type="text/css">
-<title>OpenOffice.org XML file format FAQ</title>
+<title>Apache OpenOffice XML file format FAQ</title>
<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
@@ -25,11 +25,11 @@
<div id="content">
- <p><strong>Note:</strong>This FAQ is for the OpenOffice.org XML file
format only. OASIS OpenDocument/ISO/IEC 26300 FAQs are available at <a
href="http://www.oasis-open.org/committees/office/faq.php";>OASIS</a> and <a
href="http://opendocument.xml.org/faq";>opendocument.xml.org</a>.<p>
+ <p><strong>Note:</strong>This FAQ is for the Apache OpenOffice XML file
format only. OASIS OpenDocument/ISO/IEC 26300 FAQs are available at <a
href="http://www.oasis-open.org/committees/office/faq.php";>OASIS</a> and <a
href="http://opendocument.xml.org/faq";>opendocument.xml.org</a>.<p>
<a name="top"></a><p><img alt=""
src="http://www.openoffice.org/branding/images/start_blue_bar.gif";> <font
size="-1"><b>MOST FREQUENTLY ASKED QUESTIONS:
QUESTIONS</b></font> <img alt=""
src="http://www.openoffice.org/branding/images/end_blue_bar.gif";></p><ol>
<li><a href="#1">
- Which OpenOffice.org application uses XML-based file formats?
+ Which Apache OpenOffice application uses XML-based file formats?
</a></li>
<li><a href="#2">
@@ -87,27 +87,27 @@
</ol><p><img alt=""
src="http://www.openoffice.org/branding/images/start_blue_bar.gif";> <font
size="-1"><b>MOST FREQUENTLY ASKED QUESTIONS:
ANSWERS</b></font> <img alt=""
src="http://www.openoffice.org/branding/images/end_blue_bar.gif";></p>
<ol><a name="1"></a><li value="1"><b>
- Which OpenOffice.org application uses XML-based file formats?
+ Which Apache OpenOffice application uses XML-based file formats?
</b><p><answer>
- All OpenOffice.org applications use XML-based file formats. All
+ All Apache OpenOffice applications use XML-based file formats. All
applications (except Math) use the same format as defined in our <a
href="xml_specification.pdf">specification</a>.
The Math component uses our package structure and format (see
- below), but uses <a href="http://www.w3.org/Math/";>MathML</a>
+ below), but uses <a href="https://www.w3.org/Math/";>MathML</a>
inside the package.
</answer></p><br></li></ol><a href="#top">Back to top</a><hr
noshade="noshade" size="1" align="left"><br>
<ol><a name="2"></a><li value="2"><b>
What are the default file extensions for XML-based documents?
</b><answer>
- <table summary="OpenOffice.org XML file types">
- <tr> <th>Writer</th> <td>sxw</td> </tr>
- <tr> <th>Calc</th> <td>sxc</td> </tr>
- <tr> <th>Draw</th> <td>sxd</td> </tr>
- <tr> <th>Impress</th> <td>sxi</td> </tr>
- <tr> <th>Math</th> <td>sxm</td> </tr>
- <tr> <th>Writer<br>global document</th> <td>sxg</td> </tr>
+ <table summary="Apache OpenOffice XML file types">
+ <tr> <th>Writer</th> <td>odt</td> </tr>
+ <tr> <th>Calc</th> <td>ods</td> </tr>
+ <tr> <th>Draw</th> <td>odg</td> </tr>
+ <tr> <th>Impress</th> <td>otp</td> </tr>
+ <tr> <th>Math</th> <td>odf</td> </tr>
+ <tr> <th>Writer<br>hoofddocument</th> <td>odm</td> </tr>
</table>
- <p>XML is also used in other OpenOffice.org files
+ <p>XML is also used in other Apache OpenOffice files
(e.g. configuration) which are not covered in the <tt>xmloff</tt>
project.</p>
</answer><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade"
size="1" align="left"><br>
@@ -117,7 +117,7 @@
</b><answer>
<p>Our documents use packages that contain the XML data alongside
binary data such as images. The packages use the well known ZIP format.
- Just open an sxw/sxc/... file with a ZIP-tool of your choice, and
+ Just open an odt/ods/... file with a ZIP-tool of your choice, and
you get access to the unadulterated XML.</p>
<p>The document meta data (in the meta.xml stream) is not
compressed. This allows for easy searching and extraction of the
@@ -171,13 +171,13 @@
</tr>
<tr>
<th>Basic/</th>
- <td>directory containing StarBasic macros</td>
+ <td>directory containing OpenOffice Basic macros</td>
</tr>
<tr>
<th>Obj.../</th>
<td>directories containing embedded objects, such as charts;
each directory contains one such object, stored in its native format.
- For OpenOffice.org objects that is its XML representation, for other
+ For Apache OpenOffice objects that is its XML representation, for other
objects it's usually a binary format.</td>
</tr>
</table>
@@ -193,7 +193,7 @@
OpenOffice.org DTD, will be preserved if they are attached to
<code><style:properties></code> elements in style
definitions. All other alien content will be discarded by the
- OpenOffice.org import filters.</p>
+ Apache OpenOffice import filters.</p>
<p>Since you can attach styles to arbitrary text ranges, you can
use this mechanism to attach your information to arbitrary text
ranges, too.</p>
@@ -207,7 +207,7 @@
But I really, really want plain XML. No compression, no binary
data, no nothing. Just plain XML. Can I have that, please?
</b><answer>
- <p>For purposes of import and export, we provide <a
href="http://udk.openoffice.org/";>UNO</a>-based services that
+ <p>For purposes of import and export, we provide <a
href="https://www.openoffice.org/udk/";>UNO</a>-based services that
allow you to import or export XML data through the SAX
interface. A documentation of this technique is available <a
href="filter/">here</a>.</p>
<p>Also, it is planned to allow plain XML files (without packages)
@@ -242,7 +242,7 @@
<p>Those formats are not used because they do not have a
suitable level of presentation for office documents. When we found an
established format (like the ones mentioned above) contains
- concepts that are used in OpenOffice.org as well, then we
+ concepts that are used in Apache OpenOffice as well, then we
generally adopted their representation for those concepts in our
XML format. We hope this will ease transformation between the
formats.</p>
@@ -272,7 +272,7 @@
<ol><a name="11"></a><li value="11"><b>
I found a bug. What do I do?
</b><answer>
- <p>Report it using <a
href="http://www.openoffice.org/issues/enter_bug.cgi";>IssueZilla</a>. Try
+ <p>Report it using <a href="https://bz.apache.org/ooo/";>BugZilla</a>. Try
to give a detailed description of what went wrong. Don't forget to
include the document in which the error occurred. (After submission
of the bug, choose "create attachment".)</p>
@@ -290,8 +290,8 @@
There are many things you can do to help.
<ol>
<li>You can spread the word, e.g. by telling your friends and
- co-workers about OpenOffice.org.</li>
- <li>You can use the OpenOffice.org applications and report any
+ co-workers about Apache OpenOffice.</li>
+ <li>You can use the Apache OpenOffice applications and report any
bugs you find.</li>
<li>You can program transformation from our format into others
(and vice versa).</li>
@@ -304,13 +304,11 @@
my favorite question in here?
</b><p><answer>
If your question is not answered here, ask it on our mailing
- list. You can view the archives <a
href="http://xml.openoffice.org/xml-dev/";>here</a>. Instructions
- for joining the list are on our <a
href="http://xml.openoffice.org";>project homepage</a>.
+ list. Instructions for joining the list are on our <a
href="https://www.openoffice.org/xml/";>project homepage</a>.
</answer></p><br></li></ol><a href="#top">Back to top</a><hr
noshade="noshade" size="1" align="left"><br>
-
-<p><small>FAQ maintained by <a
href="mailto:[email protected]";>dvo</a>.</small></p>
+<p><small>FAQ maintained by <a href="mailto:[email protected]";>dev
mailinglist</a>.</small></p>
</div>
diff --git a/content/xml/filter/index.html b/content/xml/filter/index.html
index b40c644da4..9d2757bd60 100644
--- a/content/xml/filter/index.html
+++ b/content/xml/filter/index.html
@@ -8,7 +8,7 @@
<link href="/css/ooo.css" rel="stylesheet" type="text/css">
<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
- <TITLE>OpenOffice.org filters using the XML based file format</TITLE>
+ <TITLE>OpenOffice filters using the XML based file format</TITLE>
<META NAME="GENERATOR" CONTENT="StarOffice/5.2 (Win32)">
<META NAME="AUTHOR" CONTENT="Daniel Vogelheim">
<META NAME="CREATED" CONTENT="20010131;13260648">
@@ -44,8 +44,6 @@
filters using the XML based file format</FONT></FONT></P>
<P><BR><BR>
</P>
-<P><BR><BR>
-</P>
<P><B>Abstract</B>: This document explains the implementation of
OpenOffice.org import and export filter components, focusing on
filter components based on the OpenOffice.org XML file format. It is
@@ -53,8 +51,6 @@ intended as a brief introduction to developers that want to
implement
OpenOffice.org filters for foreign file formats.</P>
<P><BR><BR>
</P>
-<P><BR><BR>
-</P>
<DIV ID="Inhaltsverzeichnis1">
<DIV ID="Inhaltsverzeichnis1_Head">
<P ALIGN=LEFT STYLE="margin-top: 0.42cm; page-break-after:
avoid"><FONT FACE="Arial, sans-serif"><FONT SIZE=4 STYLE="font-size:
16pt"><B>Table
@@ -103,14 +99,12 @@ OpenOffice.org filters for foreign file formats.</P>
</DIV>
<P><BR><BR>
</P>
-<P><BR><BR>
-</P>
-<H1><A NAME="1.Preliminaries|outline"></A>1Preliminaries</H1>
+<H1><A NAME="1.Preliminaries|outline"></A>1 Preliminaries</H1>
<P>They are several ways to get information into or out of
-OpenOffice.org: You can</P>
+OpenOffice: You can</P>
<OL>
<LI><P>link against the application core,</P>
- <LI><P>use the OpenOffice.org API,</P>
+ <LI><P>use the OpenOffice API,</P>
<LI><P>use the XML file format.</P>
</OL>
<P>Each of these ways has unique advantages and disadvantages, that I
@@ -148,11 +142,11 @@ significant difficulty in conversion between formats is
the
conceptual mapping from the one format to the other, a clean,
well-structured view of the document may turn out to be beneficial.</P>
<H1><A NAME="2.TheInnardsofanOpenOffice.orgFilterComponent|outline"></A>
-2The Innards of an OpenOffice.org Filter Component</H1>
+2 The Innards of an Apache OpenOffice Filter Component</H1>
<P>First, we will try to get an overview of the import and export
process using UNO components. Let's first attempt to gain a view
of...</P>
-<H2><A NAME="2.1.TheBigPicture|outline"></A>2.1The Big Picture</H2>
+<H2><A NAME="2.1.TheBigPicture|outline"></A>2.1 The Big Picture</H2>
<P>An in-memory OpenOffice.org document is represented by it's
document model. On disk, the same document is represented as a file.
An import component must turn the latter into the former as shown by
@@ -175,7 +169,7 @@ services and interfaces:
illustrations) the gray part marks the part a filter implementer will
have to program, while the white parts are already built into
OpenOffice.org.</P>
-<P>If the implementer decides to make use of the OpenOffice.org API
+<P>If the implementer decides to make use of the Apache OpenOffice API
directly, this diagram is the proper starting point: The filter
writer must create a class that implements the <CODE>ImportFilter</CODE>
service. To achieve this, the the <CODE>InputStream</CODE> must be
@@ -184,7 +178,7 @@ then be interpreted, and the OpenOffice.org document can be
constructed by calling the appropriate methods of the document model.
(The available methods of course depend on the kind of document, as
described by the document service.)</P>
-<H2><A NAME="2.2.WhereXMLComesIn...|outline"></A>2.2Where XML Comes
+<H2><A NAME="2.2.WhereXMLComesIn...|outline"></A>2.2 Where XML Comes
In...</H2>
<P>If the advantages of an XML based import or export are desired,
the filter implementer may make use of the existing XML import and
@@ -211,7 +205,7 @@ methods to generate the XML representation. Additionally, a
filter
component (labelled "Filter Wrapper" in the diagram) needs
to be written that instantiates XML import component and the
self-written import filter.</P>
-<H2><A NAME="2.3.Waiter,theExportPlease!|outline"></A>2.3Waiter, the
+<H2><A NAME="2.3.Waiter,theExportPlease!|outline"></A>2.3 Waiter, the
Export Please!</H2>
<P>The export into a foreign format may of course be implemented in
the same fashion. Instead of the <CODE>ImportFilter</CODE>
@@ -225,7 +219,7 @@ For an XML-based export filter, the schematic looks like
this:</P>
4: an XML-based export filter</I></FONT></P>
</SPAN><BR CLEAR=LEFT><BR><BR>
</P>
-<H2><A NAME="2.4.ASecondLookattheFilterWrapper|outline"></A>2.4A
+<H2><A NAME="2.4.ASecondLookattheFilterWrapper|outline"></A>2.4 A
Second Look at the Filter Wrapper</H2>
<P>How do the built-in XML export or import components cooperate with
the self-programmed filter? As was briefly mentioned above, the
@@ -265,9 +259,9 @@ interface to the XML export. For calls to the filter method
of
<CODE>XFilter</CODE>, it additionally has to pass the
<CODE>MediaDescriptor</CODE> on to the XML-based export filter.
The means by which this should happen is left to the implementer.</P>
-<H2><A NAME="2.5.TheServices|outline"></A>2.5The Services</H2>
+<H2><A NAME="2.5.TheServices|outline"></A>2.5 The Services</H2>
<P>We should now have a closer look at the involved services:</P>
-<P>The service <CODE><A
HREF="http://api.openoffice.org/common/ref/com/sun/star/document/ImportFilter.html";>com.sun.star.document.ImportFilter</A></CODE>
+<P>The service <CODE><A
HREF="https://www.openoffice.org/api/docs/common/ref/com/sun/star/document/ImportFilter.html";>com.sun.star.document.ImportFilter</A></CODE>
describes a generic import filter. The core of the service is
provided by the interfaces <CODE>XImporter</CODE> and <CODE>XFilter</CODE>
(see below). <CODE>XImporter</CODE> supplies the filter object with
@@ -281,7 +275,7 @@ parameters to the filter at initialization time, while the
<CODE>XPropertySet</CODE> can be used to get information from and
about the filter component. It is generally read-only.</P>
<P>The twin of the <CODE>ImportFilter</CODE> is the service
-<CODE><A
HREF="http://api.openoffice.org/common/ref/com/sun/star/document/ExportFilter.html";>com.sun.star.document.ExportFilter</A></CODE>.
+<CODE><A
HREF="https://www.openoffice.org/api/docs/common/ref/com/sun/star/document/ExportFilter.html";>com.sun.star.document.ExportFilter</A></CODE>.
The main interfaces are <CODE>XExporter</CODE> and <CODE>XFilter</CODE>.
The <CODE>XExporter</CODE> supplies the filter with the source
document, whereas the <CODE>XFilter</CODE> starts the filter process.
@@ -289,7 +283,7 @@ The <CODE>MediaDescriptor</CODE> that gets passed into the
<CODE>XFilter</CODE> describes the output file. The <CODE>ExportFilter</CODE>
supports the <CODE>XInitialization</CODE> and
<CODE>XPropertySet</CODE> interfaces, just like the
<CODE>ImportFilter</CODE>.</P>
-<P>The <CODE><A
HREF="http://api.openoffice.org/common/ref/com/sun/star/document/MediaDescriptor.html";>com.sun.star.document.MediaDescriptor</A></CODE>
+<P>The <CODE><A
HREF="https://www.openoffice.org/api/docs/common/ref/com/sun/star/document/MediaDescriptor.html";>com.sun.star.document.MediaDescriptor</A></CODE>
finally collects all information about a source or target file to be
imported from or exported to. It contains meta information (such as
the file name), as well as an <CODE>InputStream</CODE> which can be
@@ -302,27 +296,27 @@ obtained from the <CODE>MediaDescriptor</CODE> prevents
the
<P>The document model cannot be described by a single service, as it
obviously has to vary greatly, depending on the type of document (e.g.,
text or spreadsheet.) An example for a document model service is the
-<CODE><A
HREF="http://api.openoffice.org/common/ref/com/sun/star/text/AdvancedTextDocument.html";>com.sun.star.text.AdvancedTextDocument</A></CODE>
+<CODE><A
HREF="https://www.openoffice.org/api/docs/common/ref/com/sun/star/text/AdvancedTextDocument.html";>com.sun.star.text.AdvancedTextDocument</A></CODE>
service. What is important in this context, is that all document model
services support the <CODE>XComponent</CODE> interface.</P>
-<H2><A NAME="2.6.Interfaces|outline"></A>2.6Interfaces</H2>
-<P>The <CODE><A
HREF="http://api.openoffice.org/common/ref/com/sun/star/xml/sax/XDocumentHandler.html";>com.sun.star.document.X</A><A
HREF="http://api.openoffice.org/common/ref/com/sun/star/document/XFilter.html";>Filter</A></CODE>
+<H2><A NAME="2.6.Interfaces|outline"></A>2.6 Interfaces</H2>
+<P>The <CODE><A
HREF="https://www.openoffice.org/api/docs/common/ref/com/sun/star/xml/sax/XDocumentHandler.html";>com.sun.star.document.X</A><A
HREF="https://www.openoffice.org/api/docs/common/ref/com/sun/star/document/XFilter.html";>Filter</A></CODE>
interface features only two methods: <CODE>filter(…)</CODE> and
<CODE>cancel()</CODE>. The former starts the filtering process based
for the given <CODE>MediaDescriptor</CODE>, while the latter cancels
an ongoing filter process. <CODE>XFilter</CODE> must be implemented
for both, import and export filters.</P>
-<P>The interface <CODE><A
HREF="http://api.openoffice.org/common/ref/com/sun/star/xml/sax/XDocumentHandler.html";>com.sun.star.document.X</A><A
HREF="http://api.openoffice.org/common/ref/com/sun/star/document/XImporter.html";>Importer</A></CODE>
+<P>The interface <CODE><A
HREF="https://www.openoffice.org/api/docs/common/ref/com/sun/star/xml/sax/XDocumentHandler.html";>com.sun.star.document.X</A><A
HREF="https://www.openoffice.org/api/docs/common/ref/com/sun/star/document/XImporter.html";>Importer</A></CODE>
is used for setting up an import before the
<CODE>filter(<CODE>…</CODE>)</CODE>
method from the <CODE>XFilter</CODE> interface is called. The
<CODE>XImporter</CODE> supplies the document with its (empty) target
document, i.e., the document whose content is about to be read from
file.</P>
-<P>The <CODE><A
HREF="http://api.openoffice.org/common/ref/com/sun/star/xml/sax/XDocumentHandler.html";>com.sun.star.document.X</A><A
HREF="http://api.openoffice.org/common/ref/com/sun/star/document/XExporter.html";>Exporter</A></CODE>
+<P>The <CODE><A
HREF="https://www.openoffice.org/api/docs/common/ref/com/sun/star/xml/sax/XDocumentHandler.html";>com.sun.star.document.X</A><A
HREF="https://www.openoffice.org/api/docs/common/ref/com/sun/star/document/XExporter.html";>Exporter</A></CODE>
is structured identically to the <CODE>XImporter</CODE> interface. It
is used to set the target document, i.e., the document whose content
should be written to file.</P>
-<P>The <CODE><A
HREF="http://api.openoffice.org/common/ref/com/sun/star/xml/sax/XDocumentHandler.html";>com.sun.star.xml.sax.XDocumentHandler</A></CODE>
+<P>The <CODE><A
HREF="https://www.openoffice.org/api/docs/common/ref/com/sun/star/xml/sax/XDocumentHandler.html";>com.sun.star.xml.sax.XDocumentHandler</A></CODE>
is the core interface for handling XML data in OpenOffice.org. It is
part of the SAX interface. It has methods for all parts of XML
documents, like start or end of elements or runs of characters. The
@@ -331,7 +325,7 @@ and outgoing XML data, thus allowing chaining of components
handling
XML. A component that processes XML data should implement the
<CODE>XDocumentHandler</CODE> interface. A component that will
generate XML data should call the methods of an <CODE>XDocumentHandler</CODE>
-to output the events. The <CODE><A
HREF="http://api.openoffice.org/common/ref/com/sun/star/xml/sax/XExtendedDocumentHandler.html";>XExtendedDocumentHandler</A></CODE>,
+to output the events. The <CODE><A
HREF="https://www.openoffice.org/api/docs/common/ref/com/sun/star/xml/sax/XExtendedDocumentHandler.html";>XExtendedDocumentHandler</A></CODE>,
being derived from <CODE>XDocumentHandler</CODE>, provides
an extended version that can also handle comments. If the extended
functionality is desired, the <CODE>XDocumentHandler</CODE> should be
@@ -342,26 +336,26 @@ but rather make sure they could also work with the plain
<CODE>XDocumentHandler</CODE>. Since all vital parts of XML can be
handled through <CODE>XDocumentHandler</CODE>, this should not pose
much of a problem.</P>
-<P>The interface <CODE><A
HREF="http://api.openoffice.org/common/ref/com/sun/star/lang/XComponent.html";>com.sun.star.lang.XComponent</A></CODE>
+<P>The interface <CODE><A
HREF="https://www.openoffice.org/api/docs/common/ref/com/sun/star/lang/XComponent.html";>com.sun.star.lang.XComponent</A></CODE>
is the parent interface for all document models. Actual documents
derive from this model to provide model specific functionality, such
-as <CODE><A
HREF="http://api.openoffice.org/common/ref/com/sun/star/text/XTextDocument.html";>XTextDocument</A></CODE>.
+as <CODE><A
HREF="https://www.openoffice.org/api/docs/common/ref/com/sun/star/text/XTextDocument.html";>XTextDocument</A></CODE>.
A filter will have to query at runtime whether it can handle the
supplied <CODE>XModel</CODE>.</P>
<P>Initialization of components can be supported through the
-<CODE><A
HREF="http://api.openoffice.org/common/ref/com/sun/star/lang/XInitialization.html";>com.sun.star.lang.XInitialization</A></CODE>
+<CODE><A
HREF="https://www.openoffice.org/api/docs/common/ref/com/sun/star/lang/XInitialization.html";>com.sun.star.lang.XInitialization</A></CODE>
interface.</P>
<P>Properties of the filters can be queried using the
-<CODE><A
HREF="http://api.openoffice.org/common/ref/com/sun/star/beans/XPropertySet.html";>com.sun.star.beans.XPropertySet</A></CODE>
+<CODE><A
HREF="https://www.openoffice.org/api/docs/common/ref/com/sun/star/beans/XPropertySet.html";>com.sun.star.beans.XPropertySet</A></CODE>
interface. The names of the supported properties are part of the
service description. In general, <CODE>XPropertySet</CODE>
implementations support both reading and writing, but the intended
use for filter components is to be read-only.</P>
<P><BR><BR>
</P>
-<H2><A NAME="2.7.Built-inComponents|outline"></A>2.7Built-in
+<H2><A NAME="2.7.Built-inComponents|outline"></A>2.7 Built-in
Components</H2>
-<P>All of OpenOffice.org's applications have built-in XML import and
+<P>All of OpenOffice's applications have built-in XML import and
export components. The component names are summarized in the
following table:</P>
<TABLE WIDTH=100% BORDER=1 BORDERCOLOR="#000000" CELLPADDING=4 CELLSPACING=0>
@@ -450,20 +444,20 @@ character streams and turn them into SAX function calls.
Their names
are <CODE>com.sun.star.xml.sax.Writer</CODE> and
<CODE>com.sun.star.xml.sax.Parser</CODE>, respectively.</P>
<H2><A NAME="2.8.RegisteringaNewFilterWiththeApplication|outline"></A>
-2.8Registering a New Filter With the Application</H2>
+2.8 Registering a New Filter With the Application</H2>
<P>There is a final, crucial step that will not be covered here:
Registering a filter with the application. The registration process
will make sure that the application knows the filter, and also knows
which files the filter can be applied to. The filter registration is
-described <A
HREF="http://framework.openoffice.org/documentation/filters/index.html";>here</A>.
+described <A
HREF="https://www.openoffice.org/framework/documentation/filters/index.html";>here</A>.
</P>
-<H1><A NAME="3.Codeexamples|outline"></A>3Code examples</H1>
+<H1><A NAME="3.Codeexamples|outline"></A>3 Code examples</H1>
<P>This chapter is intended to give brief code examples for the
crucial steps in creating XML-based import or export filters. We'll
start with the filter wrapper, followed by short examples for
importing into and export from the XML filters.</P>
<H2><A NAME="3.1.TheFilterWrapper:InstantiatingtheXMLFilters|outline"></A>
-3.1The Filter Wrapper: Instantiating the XML Filters</H2>
+3.1 The Filter Wrapper: Instantiating the XML Filters</H2>
<P>The filter wrapper needs to instantiate the built-in XML import or
export components. The following code snippet will demonstrate this
for an XML-based export filter.</P>
@@ -503,7 +497,7 @@ for an XML-based export filter.</P>
<CODE>// Now we have the two components in xHandler and xExporter and can
start </CODE>
<CODE>// calling the XFilter and XExporter methods. Note that the xHandler
needs</CODE>
<CODE>// to be informed about its MediaDescriptor.</CODE></PRE><H2>
-<A NAME="3.2.ExportingthroughtheXMLfilter|outline"></A>3.2Exporting
+<A NAME="3.2.ExportingthroughtheXMLfilter|outline"></A>3.2 Exporting
through the XML filter</H2>
<P>The following code snippet could be located in a filter wrapper
for an XML-based export filter. The following two methods implement
@@ -531,7 +525,7 @@ It only delegates to it's two components.</P>
<CODE> xFilter->filter(aDescriptor);</CODE>
<CODE>}</CODE>
</PRE><H2>
-<A NAME="3.3.Import:WritingintotheXMLFilter|outline"></A>3.3Import:
+<A NAME="3.3.Import:WritingintotheXMLFilter|outline"></A>3.3 Import:
Writing into the XML Filter</H2>
<P>The next example should detail how an import filter would
communicate with the XML import component. Basically, it only needs
@@ -620,7 +614,7 @@ xHandler->endElement(
// close document
xHandler->endDocument();
</PRE><H1>
-<A NAME="4.Appendix|outline"></A>4Appendix</H1>
+<A NAME="4.Appendix|outline"></A>4 Appendix</H1>
<H2><A NAME="4.1.OthersUses|outline"></A>4.1 Other Uses</H2>
<P>This chapter briefly mentions a few other uses of XML-based filter
components that provide additional value and versatility.</P>
@@ -628,7 +622,7 @@ components that provide additional value and
versatility.</P>
format conversion tools. This would, for example, enable batch
conversion of legacy documents. The XML-based filter components allow
us to do that with little extra effort. Let us recall that an
-XML-based import filter uses OpenOffice.org's built-in XML import to
+XML-based import filter uses OpenOffice's built-in XML import to
generate the document. It calls the (generic) <CODE>XDocumentHandler</CODE>
interface after it has been supplied with the <CODE>XDocumentHandler</CODE>
implementation by the filter wrapper. Now if the filter wrapper
@@ -678,29 +672,29 @@ users would not be forced to upgrade their application to
make use of
the new filter. Also, users of newer application versions could still
use filters developed for the older format.
</P>
-<H2><A NAME="4.2.Resources|outline"></A>4.2Resources</H2>
+<H2><A NAME="4.2.Resources|outline"></A>4.2 Resources</H2>
<P>The following resources may provide additional information:</P>
<UL>
<LI><P ALIGN=LEFT>Tutorial "How to register a component":
- <A
HREF="http://framework.openoffice.org/documentation/filters/index.html";>http://framework.openoffice.org/documentation/filters/index.html</A></P>
+ <A
HREF="https://www.openoffice.org/framework/documentation/filters/index.html";>https://www.openoffice.org/framework/documentation/filters/index.html</A></P>
<LI><P ALIGN=LEFT>XML file format specification:
- <A
HREF="http://xml.openoffice.org/xml_specification.pdf";>http://xml.openoffice.org/xml_specification.pdf</A></P>
+ <A
HREF="https://www.openoffice.org/xml/xml_specification.pdf";>https://www.openoffice.org/xml/xml_specification.pdf</A></P>
<LI><P ALIGN=LEFT>Tutorial "A Component in C++":
- <A
HREF="http://udk.openoffice.org/cpp/man/component_tutorial.html";>http://udk.openoffice.org/cpp/man/component_tutorial.html</A></P>
- <LI><P ALIGN=LEFT>OpenOffice.org API Reference:
- <A
HREF="http://api.openoffice.org/common/ref/";>http://api.openoffice.org/common/ref/</A></P>
- <LI><P ALIGN=LEFT>OpenOffice.org XML Homepage:
- <A HREF="http://xml.openoffice.org/";>http://xml.openoffice.org</A></P>
- <LI><P ALIGN=LEFT>OpenOffice.org Framework Homepage:
- <A
HREF="http://framework.openoffice.org/";>http://framework.openoffice.org</A></P>
- <LI><P ALIGN=LEFT>OpenOffice.org API Homepage:
- <A HREF="http://api.openoffice.org/";>http://api.openoffice.org/</A></P>
- <LI><P ALIGN=LEFT>OpenOffice.org UNO Homepage:
- <A HREF="http://udk.openoffice.org/";>http://udk.openoffice.org/</A></P>
+ <A
HREF="https://www.openoffice.org/udk/cpp/man/component_tutorial.html";>https://www.openoffice.org/udk/cpp/man/component_tutorial.html</A></P>
+ <LI><P ALIGN=LEFT>Apache OpenOffice API Reference:
+ <A
HREF="https://www.openoffice.org/api/docs/common/ref/";>https://www.openoffice.org/api/docs/common/ref/</A></P>
+ <LI><P ALIGN=LEFT>Apache OpenOffice XML Homepage:
+ <A
HREF="https://www.openoffice.org/xml/";>https://www.openoffice.org/xml/</A></P>
+ <LI><P ALIGN=LEFT>Apache OpenOffice Framework Homepage:
+ <A
HREF="https://www.openoffice.org/framework/";>https://www.openoffice.org/framework/</A></P>
+ <LI><P ALIGN=LEFT>Apache OpenOffice API Homepage:
+ <A
HREF="https://www.openoffice.org/api/";>https://www.openoffice.org/api/</A></P>
+ <LI><P ALIGN=LEFT>Apache OpenOffice UNO Homepage:
+ <A
HREF="https://www.openoffice.org/udk/";>https://www.openoffice.org/udk/</A></P>
</UL>
<HR>
-<P>The <A HREF="http://xml.openoffice.org/";>xmloff</A> development
-team <BR>Summarized by <A HREF="mailto:[email protected]";>dvo</A></P>
+<P>The <A HREF="https://www.openoffice.org/xml/";>xmloff</A> development
+team <BR>Summarized by <A HREF="mailto:[email protected]";>dvo</A></P>
</div>
diff --git a/content/xml/modules.html b/content/xml/modules.html
index 1adb458994..dd50a0856d 100644
--- a/content/xml/modules.html
+++ b/content/xml/modules.html
@@ -26,7 +26,7 @@
<link rel="stylesheet" type="text/css" href="xmloff.css" media="screen" />
-<p>This page is outdated. A list of <a
href="http://wiki.services.openoffice.org/wiki/Xml/Modules";>Source Code Modules
in the OpenOffice.org XML Project</a> is available in the <a
href="http://wiki.services.openoffice.org/wiki/Xml/Modules";>Wiki</a>.
+<p>This page is outdated. A list of <a
href="https://wiki.openoffice.org/wiki/Xml/Modules";>Source Code Modules in the
OpenOffice.org XML Project</a> is available in the <a
href="https://wiki.openoffice.org/wiki/Xml/Modules";>Wiki</a>.
</div>
diff --git a/content/xml/project_tools.html b/content/xml/project_tools.html
index 61f5b4ef4b..e3a9e99418 100644
--- a/content/xml/project_tools.html
+++ b/content/xml/project_tools.html
@@ -59,15 +59,15 @@ Thus:
</div>
-<div class="label"><strong><a
href="http://wiki.services.openoffice.org/wiki/Xml";>Wiki</a></strong></div>
+<div class="label"><strong><a
href="https://wiki.openoffice.org/wiki/Xml";>Wiki</a></strong></div>
<div class="body">
- <div><a href="http://wiki.services.openoffice.org/wiki/Xml/Efforts";>Current
Efforts</a> </div>
- <div><a
href="http://wiki.services.openoffice.org/wiki/Xml/ContributionAreas";>Contributions</a>
</div>
- <div><a
href="http://wiki.services.openoffice.org/wiki/Xml/ArticlesAndBooks";>Articles
and Books</a> </div>
- <div><a href="http://wiki.services.openoffice.org/wiki/Xml/Research";>Reports
and Research</a> </div>
- <div><a href="http://wiki.services.openoffice.org/wiki/Xml/Tools";>Tools</a>
</div>
- <div><a
href="http://wiki.services.openoffice.org/wiki/Xml/Filters";>Filters</a> </div>
- <div><a
href="http://wiki.services.openoffice.org/wiki/Xml/Modules";>Modules</a> </div>
+ <div><a href="https://wiki.openoffice.org/wiki/Xml/Efforts";>Current
Efforts</a> </div>
+ <div><a
href="hhttps://wiki.openoffice.org/wiki/Xml/ContributionAreas";>Contributions</a>
</div>
+ <div><a
href="https://wiki.openoffice.org/wiki/Xml/ArticlesAndBooks";>Articles and
Books</a> </div>
+ <div><a href="https://wiki.openoffice.org/wiki/Xml/Research";>Reports and
Research</a> </div>
+ <div><a href="https://wiki.openoffice.org/wiki/Xml/Tools";>Tools</a> </div>
+ <div><a href="https://wiki.openoffice.org/wiki/Xml/Filters";>Filters</a>
</div>
+ <div><a href="https://wiki.openoffice.org/wiki/Xml/Modules";>Modules</a>
</div>
</div>
diff --git a/content/xml/research.html b/content/xml/research.html
index 1a6818530b..74840c67b8 100644
--- a/content/xml/research.html
+++ b/content/xml/research.html
@@ -26,7 +26,7 @@
<link rel="stylesheet" type="text/css" href="xmloff.css" media="screen" />
-<p>This page is outdated. A list of <a
href="http://wiki.services.openoffice.org/wiki/Xml/Research";>Reports and
Research Documents covering the OpenDocument format</a> is available in the <a
href="http://wiki.services.openoffice.org/wiki/Xml/Research";>Wiki</a>.
+<p>This page is outdated. A list of <a
href="http://wiki.openoffice.org/wiki/xml/Research";>Reports and Research
Documents covering the OpenDocument format</a> is available in the <a
href="http://wiki.openoffice.org/wiki/xml/Research";>Wiki</a>.
</div>
diff --git a/content/xml/uses.html b/content/xml/uses.html
index 2a843d15b1..8beae92b31 100644
--- a/content/xml/uses.html
+++ b/content/xml/uses.html
@@ -7,7 +7,7 @@
<link href="/css/ooo.css" rel="stylesheet" type="text/css">
-<title>XML/OpenDocument Tools at OpenOffice.org</title>
+<title>XML/OpenDocument Tools at Apache OpenOffice</title>
<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
@@ -26,7 +26,7 @@
<link rel="stylesheet" type="text/css" href="xmloff.css" media="screen" />
-<p>This page is outdated. A list of <a
href="http://wiki.services.openoffice.org/wiki/Xml/Tools";>OpenDocument related
tools</a> is available in the <a
href="http://wiki.services.openoffice.org/wiki/Xml/Tools";>Wiki</a>.
+<p>This page is outdated. A list of <a
href="https://wiki.openoffice.org/wiki/Xml/Tools";>OpenDocument related
tools</a> is available in the <a
href="https://wiki.openoffice.org/wiki/Xml/Tools";>Wiki</a>.
</div>
diff --git a/content/xml/xfilter.html b/content/xml/xfilter.html
index 86f0e3f279..2c23662152 100644
--- a/content/xml/xfilter.html
+++ b/content/xml/xfilter.html
@@ -47,10 +47,9 @@ tool.</p>
<h2>Use</h2>
<ol>
-
<li>You need:
<ul>
- <li>an installed OOo</li>
+ <li>an installed AOO</li>
<li>xfilter binaries for that build</li>
<li>the regcomp binary from the ODK</li>
</ul>
@@ -61,7 +60,6 @@ tool.</p>
<li>Call the starter script with parameters for the component name
and input file. The starter script will register the libraries and
then call the actual xfilter program.</li>
-
</ol>
<p>Example:</p>
@@ -69,41 +67,40 @@ tool.</p>
<ul>
<li>Windows:
<pre>
-> copy xfilter.exe xfiltermi.dll xfilter.bat <i><OOo
directory></i>\program
-> cd <i><OOo directory></i>\program
+> copy xfilter.exe xfiltermi.dll xfilter.bat <i><AOO
directory></i>\program
+> cd <i><AOO directory></i>\program
> xfilter.bat com.sun.comp.hwpimport.HwpImportFilter input.hwp
</pre>
</li>
<li>*nix:
<pre>
-> cp xfilter libxfilter??.so xfilter.sh <i><OOo directory></i>/program
-> cd <i><OOo directory></i>/program
+> cp xfilter libxfilter??.so xfilter.sh <i><AOO directory></i>/program
+> cd <i><AOO directory></i>/program
> xfilter.sh com.sun.comp.hwpimport.HwpImportFilter input.hwp
</pre>
</li>
</ul>
-
<h2>Implementation Detail</h2>
<p>The program consists of a starter application, which initializes
-the <a href="http://udk.openoffice.org/";>UNO runtime</a> and the <a
-href="http://ucb.openoffice.org/";>UCB</a> to provide for UNO component
+the <a href="https://www.openoffice.org/udk/";>UNO runtime</a> and the <a
+href="https://www.openoffice.org/ucb/";>UCB</a> to provide for UNO component
instantiation and input/output functionality, respectively. Then, the
starter program instantiates the filter component (as given on the
command line), and imitates the use of the component through the <a
-href="http://api.openoffice.org/common/ref/com/sun/star/document/XImporter.html";>XImporter</a>
+href="https://www.openoffice.org/api/docs/common/ref/com/sun/star/document/XImporter.html";>XImporter</a>
and <a
-href="http://api.openoffice.org/common/ref/com/sun/star/document/XFilter.html";>XFilter</a>
+href="https://www.openoffice.org/api/docs/common/ref/com/sun/star/document/XFilter.html";>XFilter</a>
interfaces.</p>
-<p>Limitations in the emulation of the OOo filter invocation are:
+<p>Limitations in the emulation of the AOO filter invocation are:
<ul>
<li>The <code>XImporter::setTargetDocument()</code> call received an
empty reference where the document model is expected</li>
<li>The <code>XFilter::filter()</code> call receives a
- <a
href="http://api.openoffice.org/common/ref/com/sun/star/document/MediaDescriptor.html";>MediaDescriptor</a>,
+ <a
href="https://www.openoffice.org/api/docs/common/ref/com/sun/star/document/MediaDescriptor.html";>MediaDescriptor</a>,
which contains only an URL and an opened
XInputStream for the input file.</li>
<li>Additional services or components usually provided for and
@@ -121,7 +118,6 @@ interfaces.</p>
</ul>
</p>
-
<h2>Source code</h2>
<p>The source code for this probably isn't very interesting, but you
@@ -142,7 +138,7 @@
href="http://xml.openoffice.org/source/browse/xml/filtertools/source/";>online</a
<p>
<small>
- Please direct comments and suggestions to the <a
href="mailto:[email protected]";>xml-dev</a> mailing list (<a
href="http://xml.openoffice.org/servlets/SummarizeList?listName=dev";>archive</a>)
or to <a href="mailto:[email protected]";>dvo</a>.
+ Please direct comments and suggestions to the <a
href="mailto:[email protected]";>xml-dev</a> mailing list (<a
href="http://xml.openoffice.org/servlets/SummarizeList?listName=dev";>archive</a>)
or to <a href="mailto:[email protected]";>dev mailing list</a>.
</small>
</p>
diff --git a/content/xml/xml_advocacy.html b/content/xml/xml_advocacy.html
index a6c78a8db8..212582e3cf 100644
--- a/content/xml/xml_advocacy.html
+++ b/content/xml/xml_advocacy.html
@@ -45,7 +45,7 @@ StarOffice XML based file format</FONT></FONT></P>
<FONT FACE="Arial, sans-serif"><FONT SIZE=3>To boldly go where no
office suite has gone before</FONT></FONT></P>
<H1>1Introduction</H1>
-<P>StarOffice 6.0 and OpenOffice.org use a new, XML based file format
+<P>StarOffice 6.0 and Apache OpenOffice use a XML based file format
for all its documents. The constituent parts of an office document,
content, layout and meta information, are stored as XML streams
inside a ZIP file, along with embedded graphics and objects contained
@@ -64,11 +64,11 @@ parties with a way to participate in the evolution of the
format.</P>
format, followed by a chapter in which benefits can be derived from
these features for various types of users. Finally, a conclusion will
be presented.</P>
-<H1>2How It Works – The Means</H1>
+<H1>2 How It Works – The Means</H1>
<P>This chapter will highlight several technicalities of the XML
based file format. The following chapter will then show how to put
these into use.</P>
-<H2>2.1Separation of Content, Layout, and Meta Information</H2>
+<H2>2.1 Separation of Content, Layout, and Meta Information</H2>
<P STYLE="font-style: normal">An office document contains content,
for example the text of a letter, or the data in a spreadsheet, along
with layout information, which describes how the content should look
@@ -82,7 +82,7 @@ file format stores content, layout, meta information, images
and
embedded objects in separate streams of a ZIP based package file. The
whole file contains the whole document, the individual streams
contain the constituent parts of the document.</P>
-<H2>2.2Standards Based</H2>
+<H2>2.2 Standards Based</H2>
<P>When creating the XML based file format, we tried to gain as much
as was possible from related standards. The very use of XML is one
example. The ZIP format we use for packages are in widespread use.
@@ -91,8 +91,8 @@ Dublin Core, or SVG. For Math, we use MathML. This allows easy
transformation from and into those formats, and also it allows people
to quickly understand our format, if they are already familiar with
those formats we make use of.</P>
-<H2>2.3Uniform Representation of Formatting and Layout Information</H2>
-<P>The StarOffice and OpenOffice.org applications distinguish between
+<H2>2.3 Uniform Representation of Formatting and Layout Information</H2>
+<P>The StarOffice and Apache OpenOffice applications distinguish between
formatting through styles and <I>direct</I> formatting, which means
applying formatting directly to text or cell ranges. In the XML
format, these different ways to format a document use the same
@@ -100,7 +100,7 @@ style-based representation. The <I>direct</I> formatting is
automatically converted into <I>automatic styles</I>, which is a
style-based formatting equivalent of the <I>direct</I> formatting the
user applied to the document.</P>
-<H2>2.4Structured Format</H2>
+<H2>2.4 Structured Format</H2>
<P STYLE="font-style: normal">A primary design goal of the XML format
was to represent all structured information contained in an document
as XML structures, thus making the document fully accessible to
@@ -109,7 +109,7 @@ example, an XHTML/CSS solution, where all CSS formatting
information
is encoded in a text-only format. This way, all layout information
appears as a single string to an XSLT processor, making it very hard
to process the layout information in any way.</P>
-<H2>2.5Idealized Format</H2>
+<H2>2.5 Idealized Format</H2>
<P><SPAN STYLE="font-style: normal">Our XML file format is a properly
designed file format, as opposed </SPAN>to a mere XML dump o<SPAN
STYLE="font-style: normal">f
core structures with all their implementation details and
@@ -120,9 +120,9 @@ the format may also be used by applications other than
StarOffice and
OpenOffice.org. Throughout the development of the format, great care
was taken to make sure the file format is easy to process. Also, the
idealized representation makes it easier to improve the StarOffice
-and OpenOffice.org applications without having to make major changes
+and Apache OpenOffice applications without having to make major changes
to the format itself.</SPAN></P>
-<H2>2.6Common Format Across All Office Applications</H2>
+<H2>2.6 Common Format Across All Office Applications</H2>
<P STYLE="font-style: normal">The same format is used across all
office applications. Similar concepts in the different applications
always use the same XML representation. For example, spreadsheet
@@ -132,7 +132,7 @@ different. This has great advantages when processing or
generating
StarOffice files: The same code works for all applications. For
example, a single XSLT style sheet can process both spreadsheets and
text documents.</P>
-<H2>2.7Open For Extensions and Supplemental Information</H2>
+<H2>2.7 Open For Extensions and Supplemental Information</H2>
<P STYLE="font-style: normal">Arbitrary XML attributes may be
attached to style information and will be preserved when editing such
a modified file with StarOffice. Because all formatting information
@@ -141,12 +141,12 @@ can be formatted using styles, this allows arbitrary
information to
be attached to any part of the document content. Further means to add
supplemental information, such as allowing complete streams to be
part of the packages, may be added.</P>
-<H1>3What You Gain – The Ends</H1>
+<H1>3 What You Gain – The Ends</H1>
<P>The previous chapter has highlighted several features and
mechanisms of our new file format. This chapter will look at how this
helps different groups of users.</P>
-<H2>3.1Office Users</H2>
-<P>To the user of StarOffice and OpenOffice.org, the main benefits
+<H2>3.1 Office Users</H2>
+<P>To the user of StarOffice and Apache OpenOffice, the main benefits
may be summarized as increased robustness, openness, document
longevity, and version interoperability. In additional, the user will
gain additional benefits as the document processing and additional
@@ -196,7 +196,7 @@ information, then now you can simply look at them. Or if
you need to
quickly find a certain document, just use Unix grep or the Windows
Explorer context menu to search through the meta information, which
are stored as plain text.</P>
-<H2>3.2Document Processing and Developers</H2>
+<H2>3.2 Document Processing and Developers</H2>
<P>Advanced users and developers may want to make use of the new
freedom the StarOffice XML file brings them, and use and process
StarOffice files with other tools and applications. There are several
@@ -216,7 +216,7 @@ HTML, you can make them available through the World Wide
Web. Similar
transformations are into WAP or XSL-FO are possible.
</P>
<P>An example of transforming our documents into HTML is available on
-the OpenOffice.org website, and another one is available through the
+the Apache OpenOffice website, and another one is available through the
xml.com website (see reference at the end of this paper).
</P>
<H3>Easy Import and Export of Other File Formats</H3>
@@ -236,7 +236,7 @@ This approach has several advantages:</P>
to each other. This can be used to convert between two
non-StarOffice formats.</P>
<LI><P>Import and Export components can be integrated into
- StarOffice and OpenOffice.org, or they can be used stand-alone. In
+ StarOffice and Apache OpenOffice, or they can be used stand-alone. In
the latter mode, they could be used e.g. for batch conversion of
many files. Also, they can be used to view StarOffice XML documents
without having to start the full StarOffice application.</P>
@@ -265,7 +265,7 @@ these formats. Examples are:</P>
low resolution to high resolution ones before giving a document to a
print shop.</P>
</OL>
-<H2>3.3Solution Providers</H2>
+<H2>3.3 Solution Providers</H2>
<P>A generic office suite may not be the right solution for everyone.
Often, significant improvements to productivity can be achieved by
using custom software solutions tailored exactly to the requirements
@@ -329,24 +329,24 @@ recreate the entire formatting and layout logic. Once
again, the
separation of content and layout helps, as it allows painless
generation of the plain content data, which can then be combined with
professional, artistic layout information.</P>
-<H1>4Conclusion</H1>
-<P>The upcoming StarOffice 6.0 and OpenOffice.org both feature a new
+<H1>4 Conclusion</H1>
+<P>StarOffice 6.0 and Apache OpenOffice both feature a new
XML based file format, which stores document content, layout, and
meta information as XML inside of a ZIP package, along with embedded
graphics and objects. This organization as well as many details in
the XML format itself provide many advantages to various groups of
users, creating a win-win situation for all end users, developers and
solution providers that make use of it.</P>
-<H1>5Online Resources and Further information</H1>
-<P ALIGN=LEFT>OpenOffice.org XML Homepage: <A
HREF="http://xml.openoffice.org/";>http://xml.openoffice.org/</A></P>
-<P ALIGN=LEFT>StarOffice/OpenOffice.org XML based file format
-definition: <A
HREF="http://xml.openoffice.org/xml_specification.pdf";>http://xml.openoffice.org/xml_specification.pdf</A></P>
-<P ALIGN=LEFT>The StarOffice/OpenOffice.org API:
-<A HREF="http://api.openoffice.org/";>http://api.openoffice.org/</A></P>
+<H1>5 Online Resources and Further information</H1>
+<P ALIGN=LEFT>Apache OpenOffice XML Homepage: <A
HREF="https://www.openoffice.org/xml/";>https://www.openoffice.org/xml/</A></P>
+<P ALIGN=LEFT>StarOffice/Apache OpenOffice XML based file format
+definition: <A
HREF="https://www.openoffice.org/xml/xml_specification.pdf";>https://www.openoffice.org/xml/xml_specification.pdf</A></P>
+<P ALIGN=LEFT>The StarOffice/Apache OpenOffice API:
+<A
HREF="https://www.openoffice.org/api/";>https://www.openoffice.org/api/</A></P>
<P ALIGN=LEFT>“Adventures with OpenOffice and XML” by Matt
Sergeant: <A
HREF="http://www.xml.com/pub/a/2001/02/07/openoffice.html";>http://www.xml.com/pub/a/2001/02/07/openoffice.html</A></P>
-<P ALIGN=LEFT>OpenOffice.org Filter-Development Using XML:
-<A
HREF="http://xml.openoffice.org/filter/";>http://xml.openoffice.org/filter/</A></P>
+<P ALIGN=LEFT>Apache OpenOffice Filter-Development Using XML:
+<A
HREF="https://www.openoffice.org/xml/filter/";>https://www.openoffice.org/xml/filter/</A></P>
</div>
![http://www.openoffice.org/branding/images/start_blue_bar.gif"](http://www.openoffice.org/branding/images/start_blue_bar.gif"){kind=link}
![http://www.openoffice.org/branding/images/end_blue_bar.gif"](http://www.openoffice.org/branding/images/end_blue_bar.gif"){kind=link}