Content deleted Content added
Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0 |
m Task 70: Update syntaxhighlight tags - remove use of deprecated <source> tags |
||
Line 92:
An example relationship file (''word/_rels/document.xml.rels''), is:
<
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<Relationships
Line 105:
TargetMode="External" />
</Relationships>
</syntaxhighlight>
As such, images referenced in the document can be found in the relationship file by looking for all relationships that are of type <code><nowiki>http://schemas.microsoft.com/office/2006/relationships/image</nowiki></code>. To change the used image, edit the relationship.
Line 111:
The following code shows an example of inline markup for a [[hyperlink]]:
<
<w:hyperlink r:id="rId2" w:history="1"
xmlns:r="http://schemas.openxmlformats.org/officeDocument/2006/relationships"
xmlns:w="http://schemas.openxmlformats.org/wordprocessingml/2006/main">
</syntaxhighlight>
In this example, the [[Uniform Resource Locator]] (URL) is in the Target attribute of the Relationship referenced through the relationship Id, "rId2" in this case. Linked images, templates, and other items are referenced in the same way.
Line 121:
Pictures can be embedded or linked using a tag:
<
<v:imagedata w:rel="rId1" o:title="example" />
</syntaxhighlight>
This is the reference to the image file. All references are managed via relationships. For example, a document.xml has a relationship to the image. There is a _rels directory in the same directory as document.xml, inside _rels is a file called document.xml.rels. In this file there will be a relationship definition that contains type, ID and ___location. The ID is the referenced ID used in the XML document. The type will be a reference schema definition for the media type and the ___location will be an internal ___location within the ZIP package or an external ___location defined with a URL.
Line 133:
An example document properties file (''docProps/core.xml'') that uses Dublin Core metadata, is:
<
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<cp:coreProperties xmlns:cp="http://schemas.openxmlformats.org/package/2006/metadata/core-properties"
Line 150:
<cp:contentStatus>Final</cp:contentStatus>
</cp:coreProperties>
</syntaxhighlight>
== Document markup languages ==
Line 176:
Patrick Durusau, the editor of [[OpenDocument|ODF]], has viewed the markup style of OOXML and ODF as representing two sides of a debate: the "element side" and the "attribute side". He notes that OOXML represents "the element side of this approach" and singles out the <code>KeepNext</code> element as an example:
<
<w:pPr>
<w:keepNext/>
…
</w:pPr>
</syntaxhighlight>
In contrast, he notes ODF would use the single attribute <code>fo:keep-next</code>, rather than an element, for the same semantic.<ref>{{ cite web
Line 216:
The following Office MathML example defines the [[fraction (mathematics)|fraction]]: <math>\frac{\pi}{2}</math>
<
<m:oMathPara><!-- mathematical block container used as a paragraph -->
<m:oMath><!-- mathematical inline formula -->
Line 225:
</m:oMath>
</m:oMathPara>
</syntaxhighlight>
Some have queried the need for Office MathML (OMML) instead advocating the use of [[MathML]], a [[World Wide Web Consortium|W3C]] recommendation for the "inclusion of mathematical expressions in Web pages" and "machine to machine communication".<ref>{{cite web| url=http://www.zdnet.com.au/news/software/soa/Microsoft-Office-dumped-by-Science-and-Nature/0,130061733,339278690,00.htm| title=Microsoft Office dumped by Science and Nature| publisher=ZDNet Australia| date=18 June 2007}}</ref> Murray Sargent has answered some of these issues in a blog post, which details some of the philosophical differences between the two formats.<ref>http://blogs.msdn.com/b/murrays/archive/2006/10/07/mathml-and-ecma-math-_2800_omml_2900_-.aspx</ref>
| |||