This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/openoffice-org.git
The following commit(s) were added to refs/heads/asf-staging by this push:
new 3a74fa9d8a git-site-role commit from build_staging.sh
3a74fa9d8a is described below
commit 3a74fa9d8ad7d14e2c8bd84208d47c798ab56de7
Author: jenkins <[email protected]>
AuthorDate: Sun Jan 4 14:46:39 2026 +0000
git-site-role commit from build_staging.sh
---
content/feed.xml | 4 ++--
content/xml/xml_advocacy.html | 56 +++++++++++++++++++++----------------------
2 files changed, 30 insertions(+), 30 deletions(-)
diff --git a/content/feed.xml b/content/feed.xml
index 5c0fb8b4cc..c1f17280d7 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, 4 Jan 2026 14:25:43 +0000</pubDate>
- <lastBuildDate>Sun, 4 Jan 2026 14:25:43 +0000</lastBuildDate>
+ <pubDate>Sun, 4 Jan 2026 14:43:50 +0000</pubDate>
+ <lastBuildDate>Sun, 4 Jan 2026 14:43:50 +0000</lastBuildDate>
</channel>
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>